diff --git "a/data/pages-00002.jsonl" "b/data/pages-00002.jsonl"
--- "a/data/pages-00002.jsonl"
+++ "b/data/pages-00002.jsonl"
@@ -90,7 +90,7 @@
 {"id":10090,"url":"https://www.metaplex.com/docs/nfts/fetch-nft","domain":"www.metaplex.com","chapter":"docs","title":"Fetch an NFT | NFTs","text":"Fetch NFT data from the Solana blockchain.\nFetch an NFT or a Collection\nIn the following section you can find a full code example and the parameters that you might need to change. You can learn more about fetching NFTs and collections in the Core documentation.\n\n1import { fetchAsset, fetchCollection, mplCore } from '@metaplex-foundation/mpl-core';\n\n2import { publicKey } from '@metaplex-foundation/umi';\n\n3import { createUmi } from '@metaplex-foundation/umi-bundle-defaults';\n\n4\n\n5// Initialize UMI\n\n6const umi = createUmi('https://api.devnet.solana.com')\n\n7 .use(mplCore())\n\n8\n\n9// Fetch a Core Asset\n\n10const assetAddress = publicKey('AssetAddressHere...')\n\n11const asset = await fetchAsset(umi, assetAddress)\n\n12\n\n13// Fetch a Core Collection\n\n14const collectionAddress = publicKey('CollectionAddressHere...')\n\n15const collection = await fetchCollection(umi, collectionAddress)\n\n16\n\n17console.log('Asset fetched:', asset)\n\n18console.log('Name:', asset.name)\n\n19console.log('Owner:', asset.owner)\n\n20console.log('URI:', asset.uri)\n\n21\n\n22console.log('\\nCollection fetched:', collection)\n\n23console.log('Name:', collection.name)\n\n24console.log('URI:', collection.uri)\n\n1# Fetch an NFT using the Metaplex CLI\n\n2\n\n3# Fetch asset by ID\n\n4mplx core fetch asset <assetId>\n\n5\n\n6# Download all files to a directory\n\n7mplx core fetch asset <assetId> --download --output ./assets\n\n8\n\n9# Download only the image\n\n10mplx core fetch asset <assetId> --download --image\n\n11\n\n12# Download only the metadata\n\n13mplx core fetch asset <assetId> --download --metadata\n\n1// npm install @metaplex-foundation/umi @metaplex-foundation/umi-bundle-defaults @metaplex-foundation/digital-asset-standard-api\n\n2import { publicKey } from '@metaplex-foundation/umi'\n\n3import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n4import { dasApi } from '@metaplex-foundation/digital-asset-standard-api'\n\n5\n\n6// Initialize Umi with a DAS-enabled RPC endpoint\n\n7const umi = createUmi('https://api.devnet.solana.com').use(dasApi())\n\n8\n\n9// The address of the NFT you want to fetch\n\n10const assetAddress = publicKey('YOUR_NFT_ADDRESS')\n\n11\n\n12// Fetch the asset using DAS API\n\n13const asset = await umi.rpc.getAsset(assetAddress)\n\n14\n\n15console.log('Asset ID:', asset.id)\n\n16console.log('Name:', asset.content.metadata?.name)\n\n17console.log('Description:', asset.content.metadata?.description)\n\n18console.log('Image:', asset.content.links?.image)\n\n19console.log('Owner:', asset.ownership.owner)\n\n20console.log('Interface:', asset.interface)\n\n1# Fetch an NFT using the DAS API\n\n2curl -X POST \\\n\n3 -H \"Content-Type: application/json\" \\\n\n4 -d '{\n\n5 \"jsonrpc\": \"2.0\",\n\n6 \"id\": 1,\n\n7 \"method\": \"getAsset\",\n\n8 \"params\": {\n\n9 \"id\": \"<NFT Mint Address>\"\n\n10 }\n\n11 }' \\\n\n12 https://api.devnet.solana.com\n\nParameters\nCustomize these parameters for your fetch:\nParameterDescription\nassetAddress\nThe public key of the NFT asset\n\ncollectionAddress\nThe public key of the collection (optional)\n\nHow It Works\nThe fetch process involves these steps:\nGet the address - You need the public key of the NFT asset or collection you want to fetch\nFetch asset data - Use fetchAsset to retrieve NFT information including name, URI, owner, and plugins\nFetch collection data - Use fetchCollection to retrieve collection information (optional)\nNFT and Collection Data\nWhen you fetch an asset, you get back all its data:\nName - The NFT's name\nURI - Link to the metadata JSON\nOwner - The wallet that owns the NFT\nUpdate Authority - Who can modify the NFT\nPlugins - Any attached plugins like royalties or attributes\nWhen you fetch a collection, you get:\nName - The collection's name\nURI - Link to the collection metadata JSON\nUpdate Authority - Who can modify the collection\nNum Minted - Number of assets in the collection\nPlugins - Any attached plugins like royalties or attributes","tokens":957,"crawled_at":1791192309442}
 {"id":10091,"url":"https://governance.aave.com/t/discussion-a-second-issuer-controlled-verifier-for-cross-chain-gho-on-ccip-2-0/25771","domain":"governance.aave.com","chapter":"governance_daos","title":"[Discussion] A second, issuer-controlled verifier for cross-chain GHO on CCIP 2.0 - Governance - Aave","text":"[Discussion] A second, issuer-controlled verifier for cross-chain GHO on CCIP 2.0\n\nGovernance\n\nanfossopablo\n\nOctober 4, 2026, 12:26pm\n\n1\n\nHi everyone,\n\nCross-chain GHO runs on Chainlink CCIP: GHO is locked on Ethereum and minted through facilitators on other chains. CCIP 2.0, live since September 28, now lets a token pool require additional verifiers on top of Chainlink’s committee.\n\nWe built Countersign. Countersign is an issuer-operated Cross-Chain Verifier (CCV) for Chainlink CCIP 2.0 that runs as a CRE workflow, so there are no servers to operate. The token pool refuses to mint or release a large transfer until Countersign has independently re-checked it: the canonical OnRamp event, the cross-chain supply invariant (and Proof of Reserve when available), rolling outflow and per-sender limits, and a denylist. A guardian can hold a suspicious transfer for review, and a tighten-only circuit breaker freezes lanes if supply ever looks unbacked.\n\nFor GHO it can enforce the core invariant directly: GHO minted on remote chains never exceeds GHO locked on Ethereum, checked for every transfer before the mint, plus rolling outflow limits per lane.\n\nLive on public testnets, including a transfer held and then released by a guardian:\n\n2-minute demo: https://youtu.be/FKoKNaHxgg0\n\nOpen-source code, 99 tests and every testnet transaction: GitHub - allertrack/countersign: countersign · GitHub\n\nWe’d welcome feedback from the community and service providers on whether a testnet pilot on GHO’s lanes is worthwhile, and which thresholds and limits would make sense. Countersign only adds checks: it cannot move funds or loosen rate limits.\n\nPablo, Countersign\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[ARFC] Launch sGHO Cross-Chain\n\nGovernance\n\n2\n\n462\n\nJuly 7, 2026\n\n[ARFC] Aave Institutional\n\nGovernance\n\n7\n\n520\n\nOctober 2, 2026\n\n[ARFC] GHO Stewards Signer Update\n\nGovernance\n\n1\n\n183\n\nAugust 17, 2026\n\nAave Chan Initiative Delegate platform\n\nDelegate Platforms\n\n43\n\n13839\n\nOctober 2, 2026\n\n[ARFC] Aave Risk Framework\n\nRisk\n\n9\n\n2721\n\nJuly 31, 2026","tokens":515,"crawled_at":1791192309837}
 {"id":10092,"url":"https://docs.cosmos.network/cometbft/latest/spec/CometBFT-Spec","domain":"docs.cosmos.network","chapter":"layer1_layer2","title":"Overview - Cosmos Docs","text":"​\n\nCometBFT Spec\n\nThis is a markdown specification of CometBFT.\nIt defines the base data structures, how they are validated,\nand how they are communicated over the network.\nIf you find discrepancies between the spec and the code that\ndo not have an associated issue or pull request on github,\nplease submit them to our bug bounty!\n​\n\nContents\n\nOverview\n\n​\n\nData Structures\n\nEncoding and Digests\n\nBlockchain\n\nState\n\n​\n\nConsensus Protocol\n\nConsensus Algorithm\n\nCreating a proposal\n\nTime\n\nLight-Client\n\n​\n\nP2P and Network Protocols\n\nThe Base P2P Layer: multiplex the protocols (“reactors”) on authenticated and encrypted TCP connections\n\nPeer Exchange (PEX): gossip known peer addresses so peers can find each other\n\nBlock Sync: gossip blocks so peers can catch up quickly\n\nConsensus: gossip votes and block parts so new blocks can be committed\n\nMempool: gossip transactions so they get included in blocks\n\nEvidence: sending invalid evidence will stop the peer\n\n​\n\nRPC\n\nRPC SPEC: Specification of the CometBFT remote procedure call interface.\n\n​\n\nSoftware\n\nABCI: Details about interactions between the\napplication and consensus engine over ABCI\n\nWrite-Ahead Log: Details about how the consensus\nengine preserves data and recovers from crash failures\n\n​\n\nOverview\n\nCometBFT provides Byzantine Fault Tolerant State Machine Replication using\nhash-linked batches of transactions. Such transaction batches are called “blocks”.\nHence, CometBFT defines a “blockchain”.\nEach block in CometBFT has a unique index - its Height.\nHeights in the blockchain are monotonic.\nEach block is committed by a known set of weighted Validators.\nMembership and weighting within this validator set may change over time.\nCometBFT guarantees the safety and liveness of the blockchain\nas long as less than 1/3 of the total weight of the Validator set\nis malicious or faulty.\nA commit in CometBFT is a set of signed messages from more than 2/3 of\nthe total weight of the current Validator set. Validators take turns proposing\nblocks and voting on them. Once enough votes are received, the block is considered\ncommitted. These votes are included in the next block as proof that the previous block\nwas committed - they cannot be included in the current block, as that block has already been\ncreated.\nOnce a block is committed, it can be executed against an application.\nThe application returns results for each of the transactions in the block.\nThe application can also return changes to be made to the validator set,\nas well as a cryptographic digest of its latest state.\nCometBFT is designed to enable efficient verification and authentication\nof the latest state of the blockchain. To achieve this, it embeds\ncryptographic commitments to certain information in the block “header”.\nThis information includes the contents of the block (eg. the transactions),\nthe validator set committing the block, as well as the various results returned by the application.\nNote, however, that block execution only occurs after a block is committed.\nThus, application results can only be included in the next block.\nAlso note that information like the transaction results and the validator set are never\ndirectly included in the block - only their cryptographic digests (Merkle roots) are.\nHence, verification of a block requires a separate data structure to store this information.\nWe call this the State. Block verification also requires access to the previous block.\nWas this page helpful?","tokens":861,"crawled_at":1791192322623}
-{"id":10093,"url":"https://www.metaplex.com/docs/nfts/burn-nft","domain":"www.metaplex.com","chapter":"docs","title":"Burn an NFT | NFTs","text":"Permanently destroy an NFT and reclaim rent fees.\nBurn an NFT\nIn the following section you can find a full code example and the parameters that you might need to change. You can learn more about burning NFTs in the Core documentation.\n\n1import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n2import { burn } from '@metaplex-foundation/mpl-core'\n\n3import { mplCore } from '@metaplex-foundation/mpl-core'\n\n4import { publicKey } from '@metaplex-foundation/umi'\n\n5\n\n6const umi = createUmi('https://api.devnet.solana.com').use(mplCore())\n\n7const assetAddress = publicKey('AssetAddressHere...')\n\n8\n\n9// Permanently destroy/burn an NFT asset\n\n10const result = await burn(umi, {\n\n11 asset: assetAddress,\n\n12}).sendAndConfirm(umi)\n\n13\n\n14console.log('Asset burned successfully')\n\n1# Burn an NFT using the Metaplex CLI\n\n2\n\n3# Burn a single asset by its mint address\n\n4mplx core asset burn <assetId>\n\n5\n\n6# Burn an asset from that is part of a collection\n\n7mplx core asset burn <assetId> --collection <collectionId>\n\nParameters\nCustomize these parameters for your burn:\nParameterDescription\nassetAddress\nThe public key of the NFT to burn\n\nHow It Works\nThe burn process involves three steps:\nFetch the NFT - Get the NFT data using fetchAsset\nExecute burn - Destroy the NFT permanently\nReclaim rent - Most SOL is returned to you (except ~0.00089784 SOL)\nWarning: Burning is permanent and cannot be reversed. Make sure you want to destroy the NFT before proceeding.\nRent Reclamation\nWhen you burn an NFT:\nMost of the rent SOL is returned to the NFT owner\nA small amount (~0.00089784 SOL) remains to prevent the account from being reopened\nYou must be the NFT owner to burn it","tokens":420,"crawled_at":1791192329224}
+{"id":10093,"url":"https://www.metaplex.com/docs/nfts/burn-nft","domain":"www.metaplex.com","chapter":"docs","title":"Burn an NFT | NFTs","text":"Permanently destroy an NFT and reclaim rent fees.\nBurn an NFT\nIn the following section you can find a full code example and the parameters that you might need to change. You can learn more about burning NFTs in the Core documentation.\n\n1import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n2import { burn } from '@metaplex-foundation/mpl-core'\n\n3import { mplCore } from '@metaplex-foundation/mpl-core'\n\n4import { publicKey } from '@metaplex-foundation/umi'\n\n5\n\n6const umi = createUmi('https://api.devnet.solana.com').use(mplCore())\n\n7const assetAddress = publicKey('AssetAddressHere...')\n\n8\n\n9// Permanently destroy/burn an NFT asset\n\n10const result = await burn(umi, {\n\n11 asset: assetAddress,\n\n12}).sendAndConfirm(umi)\n\n13\n\n14console.log('Asset burned successfully')\n\n1# Burn an NFT using the Metaplex CLI\n\n2\n\n3# Burn a single asset by its mint address\n\n4mplx core asset burn <assetId>\n\n5\n\n6# Burn an asset from that is part of a collection\n\n7mplx core asset burn <assetId> --collection <collectionId>\n\nParameters\nCustomize these parameters for your burn:\nParameterDescription\nassetAddress\nThe public key of the NFT to burn\n\nHow It Works\nThe burn process involves three steps:\nFetch the NFT - Get the NFT data using fetchAsset\nExecute burn - Destroy the NFT permanently\nReclaim rent - Most SOL is returned to you (except ~0.00089784 SOL)\nWarning: Burning is permanent and cannot be reversed. Make sure you want to destroy the NFT before proceeding.\nRent Reclamation\nWhen you burn an NFT:\nMost of the rent SOL is returned to the NFT owner\nA small amount (~0.00089784 SOL) remains to prevent the account from being reopened\nYou must be the NFT owner to burn it","tokens":420,"crawled_at":1791192710661}
 {"id":10094,"url":"https://governance.aave.com/t/arfc-onboard-wstlink-to-aave-v3-core-instance/22169","domain":"governance.aave.com","chapter":"governance_daos","title":"[ARFC] Onboard wstLINK to Aave V3 Core Instance - New Asset - Aave","text":"[ARFC] Onboard wstLINK to Aave V3 Core Instance\n\nGovernance\n\nNew Asset\n\nACI\n\nMay 26, 2025, 5:32am\n\n1\n\n[ARFC] Onboard wstLINK to Aave V3 Core Instance\n\nDate: 2025-05-26\n\nAuthor: ACI\n\nRisk Parameters and analysis have been updated after being provided by Risk Service Providers 2025-06-06\n\nProposal updated again with Risk Parameters provided by Risk Service Providers 2025-12-19\n\nSummary\n\nThe current proposal plans to onboard wstLINK to Aave V3 Core Instance, after successful [TEMP-CHECK] Onboard wstLINK to Aave v3 Core Instance posted by LinkPool, and successful [TEMP CHECK Snapshot]. This proposal is powered by Skywards.\n\nAs a TLDR wstLINK is a wrapped liquid staking token that enables users to earn LINK staking rewards and additional returns through DeFi strategies for stLINK and wstLINK. Its growing adoption, deep liquidity, and robust security measures make wstLINK a strong candidate to enhance Aave’s asset offerings, increase utilization of existing LINK liquidity and attract additional liquidity.\n\nMotivation:\n\nwstLINK is the wrapped liquid staking token stLINK of stake.link, the only permissionless liquid staking protocol built for LINK staking. By leveraging stake.link users can participate in LINK staking and profit from a higher reward rate as well as composability and faster withdrawals.\n\nKey highlights of wstLINK, stLINK and stake.link include:\n\nSecure: Audited by industry-leading experts, maintaining the high standards set by Chainlink Labs:\n\nCodeHawks\n\nCyfrin\n\nSigma Prime\n\nTrust Security\n\nDecentralized: Powered by 15 major Chainlink Node Operators, handling over 57% of network activity (https://prism.dextrac.com/chainlink)\n\nLiquid - Instant Withdrawals, No Cooldown:\n\nPriority Pool: Withdraw instantly as long as there’s LINK (amount can be viewed here) (The Priority Pool is a holding zone that users can deposit their LINK into that automatically stakes their LINK into Chainlink Staking Contracts whenever a LINK Staker withdraws their LINK).\n\nNative Withdrawals: Withdraw LINK natively within at least 7 days. 25% of the entire LINK pool will be unbonded at any point via stake.link, there’s some edge cases but that’s generally what will be the norm. Withdrawal requests will run in a 7 day queue, if you send a withdrawal request 4 days into the queue it’ll only take 3 days etc.)\n\nEcosystem Participant:\n\nChainlink Labs as ecosystem participant owning roughly 7.7% of SDL supply\n\nHigh Adoption and TVL:\n\nstake.link holds over $74 million (~4.4m LINK) in total value locked (TVL) within its ecosystem integrated across DeFi platforms like Curve, Beefy, and Uniswap\n\nstake.link has established approximately $5 million pool of stLINK on Curve.fi with an a-coefficient of 500 enabling liquidations on par or with significant upside for the liquidator\n\nAnother $3 million of liquidity is still to migrate to the new pool\n\nThe new pool features a very innovative incentive by using 3% of the generated fees by the protocol (stLINK) that are distributed as LP tokens ensuring a steady growth of the pool over time with sustainable reward rate.\n\nSpecification\n\nRisk Parameters and analysis have been updated after being provided by Risk Service Providers 2025-12-19\n\nSpecification\n\nParameter\nValue\n\nAsset\n\nwstLINK\n\nIsolation Mode\n\nN/A\n\nBorrowable\n\nNo\n\nCollateral Enabled\n\nNo\n\nSupply Cap\n\n500,000\n\nBorrow Cap\n\n-\n\nDebt Ceiling\n\n-\n\nLTV\n\n-\n\nLT\n\n-\n\nLiquidation Penalty\n\n-\n\nLiquidation Protocol Fee\n\n10%\n\nVariable Base\n\n-\n\nVariable Slope1\n\n-\n\nVariable Slope2\n\n-\n\nUoptimal\n\n-\n\nReserve Factor\n\n-\n\nStable Borrowing\n\nDisabled\n\nFlashloanable\n\nYes\n\nSiloed Borrowing\n\nNo\n\nBorrowable in Isolation\n\nNo\n\nE-Mode Category\n\nwstLINK/LINK\n\nE-Mode (wstLINK/LINK)\n\nParameter\nValue\nValue\n\nAsset\n\nwstLINK\n\nLINK\n\nCollateral\n\nYes\n\nNo\n\nBorrowable\n\nNo\n\nYes\n\nMax LTV\n\n90.00%\n\n-\n\nLiquidation Threshold\n\n92.00%\n\n-\n\nLiquidation Bonus\n\n2.00%\n\n-\n\nCAPO\n\nmaxYearlyRatioGrowthPercent\nratioReferenceTime\nMINIMUM_SNAPSHOT_DELAY\n\n6.89%\n\nmonthly\n\n14\n\nInterest Rate\n\nInstance\nAsset\nCurrent Base\nRecommended Base\nCurrent Slope2\nRecommended Slope2\n\nEthereum Core\n\nLINK\n\n0%\n\n1.5%\n\n300%\n\n150%\n\nBorrow Cap\n\nInstance\nAsset\nCurrent Supply Cap\nRecommended Supply Cap\nCurrent Borrow Cap\nRecommended Borrow Cap\n\nEthereum Core\n\nLINK\n\n20,000,000\n\n-\n\n13,000,000\n\n6,000,000\n\nToken Contracts:\n\nwstLINK on Ethereum: 0x911D86C72155c33993d594B0Ec7E6206B4C803da\n\nLiquidity Pools:\n\nCurve stLINK-LINK stablepool: 0x7e13876b92f1a62c599c231f783f682e96b91761\n\nLINK Priority Pool: 0xddc796a66e8b83d0bccd97df33a6ccfba8fd60ea\n\nUseful Links:\n\nstake.link · GitHub\n\nhttps://docs.stake.link/\n\nNext Steps\n\nPublication of a standard ARFC (currently here), collect community & service providers feedback before escalating proposal to ARFC snapshot stage.\n\nIf the ARFC snapshot outcome is YAE, publish an AIP vote for final confirmation and enforcement of the proposal.\n\nDisclaimer\n\nCurrent proposal has been created by ACI, as this proposal is powered by Skyward from TEMP CHECK stage. ACI did not received payment or compensation for the publication of this proposal and is not affiliated with LinkPool or Chainlink.\n\nCopyright\n\nCopyright and related rights waived under CC0.\n\n9 Likes\n\nChaos Labs - Monthly Community Update\n\nLlamaRisk\n\nJune 2, 2025, 7:07pm\n\n2\n\nSummary\n\nLlamaRisk supports adding wstLINK to the Aave V3 Core. wstLINK is a liquid-staking token that represents staked LINK on Chainlink’s network, with stake.link serving as the delegated staking provider. By staking LINK, the protocol strengthens the cryptoeconomic security of Chainlink’s oracle infrastructure.\n\nThe primary risk for Aave lies in potential slashing penalties on delegated LINK. Since slashing rules remain in beta, they may evolve, and any slashing event would drive net-negative rewards (i.e. a negative rebase on the underlying stLINK).\n\nOn the market side, liquidity for stLINK is concentrated in two Curve pools, offering roughly $5M–$5.4M of swap capacity at up to 7% slippage. The largest pool counts about 40 LPs, over 95% of whose funds sit in a Curve Gauge. Stake.link’s contracts have been audited by four independent firms and are now covered by a bug-bounty program. Governance runs through a 6-of-8 multisig, whose signers include core contributors, node operators, community members. Chainlink itself operates uniquely as a DAO participant.\n\nIn summary, onboarding of wstLINK would not alter Aave’s risk profile and poses minimal incremental risk, though it’s wise to monitor developments in the Chainlink Staking environment.\n\nCollateral Risk Assessment\n1. Asset Fundamental Characteristics\n\n1.1 Asset\n\nwstLINK (Wrapped staked LINK) is a liquid staking ERC20 token that represents a receipt of staked LINK utilised to secure the Chainlink Network through stake.link. LINK, the network’s native token, allows users to provide cryptoeconomic security to oracle networks in return for staking rewards. Stake.link is the issuer of wstLINK and the sole third-party delegated staking provider for Chainlink.\n\nimage1536×864 96.9 KB\n\nSource: Chainlink Staking, Chainlink Economics 2.0\n\nChainlink staking was initially launched with v0.1 in December 2022 as a capped staking pool for the ETH/USD Data Feed on mainnet, with Community and Node Operator native staking allotments. Users can stake as Community Stakers to participate in maintaining the network (see section 1.2), with LINK auto-delegated evenly to all nodes currently.\n\nThe most recent beta update, v.02 (November 2023), expanded the pool from 25M to 45M LINK and introduced upgrades such as a withdrawal mechanism, variable reward rates, and the use of modular architecture. As a part of Chainlink’s Economics 2.0, staking forms part of a set of initiatives to increase oracle network utilization and adoption.\n\nimage1100×591 80.5 KB\n\nSource: Chainlink Staking roadmap, Chainlink Blog\n\nAt the time of writing, it has been ~1.5 years since the last Chainlink Staking update, and no new announcements or expansions (including pools and feeds) have been made. The stake.link team indicated a lack of insight into the project’s roadmap progress.\n\n1.2 Architecture\n\nstLINK is wstLINK’s sole underlying asset, LINK is deposited into both the Node Operator and Community Staking Pools. Key contracts that enable wstLINK include:\n\nStakingPool: Controls deposits and withdrawals of underlying LINK. The pool deposits assets into strategy contracts and mints stLINK, which represent a share of the pool.\n\nPriorityPool: Queues deposits and acts as a liquidity buffer for withdrawals.\n\nWithdrawalPool: Queues withdrawals if there is insufficient liquidity in the PriorityPool.\n\nWrappedSDToken: Wraps stLINK into wstLINK.\n\nRewardsInitiator: Handles reward accounting and updates the StakingPool. In the event of slashing, the contract also handles rebasing within the StakingPool.\n\nRewardsPool: Manages the distribution of a single reward token to a parent pool.\n\nVaults: CommunityVaults and OperatorsVaults that are used to stake LINK.\n\nVCS: Staking strategies that manage many Community and Operator vaults.\n\nOperatorStakingPool: Tracks node operator LST balances.\n\nSlashing\n\nReward penalties for node operators found to have excessive downtimes were introduced in v0.1, with up to 3 months of accrued staking rewards at risk of being slashed.\n\nSlashing on committed LINK is currently active for v.02, and is expected to evolve as a part of the staking implementation roadmap. The slashing mechanism is based on oracle networks failing to meet their performance standard, e.g., not submitting a new oracle report for more than three hours. Node operators staked LINK are at risk of slashing should an alert be validated, with node operators slashing currently set to 700 LINK. Each stake.link node operator is max staked 75K LINK, slashing therefore represents a 0.9% penalty on the total stake per node operator. The delegated Community staked LINK is currently not at risk of slashing, but this is subject to change.\n\nAs a third-party delegation system, underlying LINK in wstLINK is subject to slashing risk, as it forms part of the Node Operator pools.\n\nRewards\n\nNative LINK emissions support staking rewards and alerting rewards in Beta versions of staking, with oracle network user fees being introduced from V1 onwards. Current Community rewards have a 4.5% base annualized rewards rate of the maximum staking pool size. Additionally, node operators are entitled to a 4% Delegation reward from auto-delegated Community rewards. The Community pool has an effective base rate of 4.32%. The Node Operator pool generates a base effective rate of 6.28% currently (of a maximum pool size).\n\nPost v0.1 updates, annualized rewards will vary based on user fees and staker commitment, reducing reliance on LINK emissions.\n\nWithdrawals\n\nA Priority pool allows users to deposit LINK in the event of unavailable deposit space into the Staking pool, queuing deposits until space becomes available. The Priority pool also acts as a liquidity buffer, allowing users to withdraw wstLINK provided there is sufficient liquidity in the pool.\n\nimage535×501 39.9 KB\n\nSource: Priority Pool Balance, Dune, May 30th, 2025\n\nAs of May 31st, the Priority pool balance stood at 242K LINK (~$3.4M). Historically, the pool saw its largest balance in December 2023 (~1M/$15.8M LINK). This peak and prior growth coincided with the v0.2 update and is likely explained by the start of Early Access and General Access (December 7 and December 11). The pool’s balance declined thereafter and saw its lowest levels between August and November 2024. Liquidity has since improved and fluctuated periodically.\n\nUnstaking\n\nStaked LINK can be withdrawn from Chainlink by initiating a request and undergoing a 28-day cooldown window. After this window, users are given 7 days to claim their LINK; unclaimed LINK thereafter are restaked. Version 0.2’s unbonding mechanism reserves potential penalties on accrued rewards depending on the length of staking. Rewards are made up of Claimable and Locked rewards. Claimable rewards can be withdrawn at any time, but Locked rewards go through a 90-day lockup period before they become Claimable. Lock-up periods, called ‘ramp-up’ periods, are tracked linearly from 0% to 100% of days’ completed. Should a staker withdraw before the complete 90-day window, they will earn the percentage completed and forfeit the rest.\n\nIn the event the protocol withdrawal buffer described above is insufficient, stake.link withdrawals will depend on secondary markets and Chainlink’s unbonding delay. In reality, if the withdrawal buffer is depleted, in most cases the withdrawal delay will be around 7 days instead of 28 days in native Chainlink Staking, as claimed by stake.link’s team. If the amount of withdrawal requests exceeded 20% of the pool, the withdrawals will then fall back to the next unbonding cycle, incurring up to 28 days of delay.\n\nNode Operators\n\nimage1121×555 60.5 KB\n\nSource: stake.link Node Operators, Mirror\n\nCurrently, stake.link delegates LINK to 15 node operators.\n\n1.3 Tokenomics\n\nUsers receive stLINK by staking LINK with stake.link, and wrapping to receive wstLINK via the wrapper contract. wstLINK is denominated in LINK and is a value-accruing non-rebasing token representing a user’s stake in the underlying assets + staking rewards. Supply is capped by Chainlink Staking pool size (currently 45M LINK)and the number of node operators that stake.link utilizes.\n\nimage608×264 11 KB\n\nSource: stLINK pool info, stake.link, May 28th, 2025.\n\nAt the time of writing, the available pool capacity has been reached and can only expand with a Chainlink update to the pool size and/or the onboarding of additional node operators with spare capacity. Holders receive a blended reward rate from the Community and Node Operator Staking Pools, less protocol fees.\n\n1.3.1 Token Holder Concentration\n\nimage967×475 78.1 KB\n\nSource: Top 100 wstLINK Holders, Etherscan, May 28th, 2025.\n\nwstLINK is concentrated in a few holders, with only 68 addresses holding the token. The top 10 holders collectively own 84.66%, and consist of 9 EOAs and the RewardsPoolWSD contract.\n\nimage974×468 61.1 KB\n\nSource: Top 100 stLINK Holders, Etherscan, May 28th, 2025\n\nThe top 10 holders of stLINK own 63.52% of the total supply. The top 5 accounts and their holdings include:\n\nLINK Priority Pool contract: 25.02%\n\nwstLINK contract: 17.07%\n\nEOA 1: 4.20%\n\nEOA 2: 3.92%\n\nEOA 3: 3.51%\n\nThe largest DEX holding is a Curve stLINK/LINK stablepool, which holds 2.95% of the current stLINK supply.\n\n2. Market Risk\n\n2.1 Liquidity\n\nLiquidity for wstLINK is low, with liquidations requiring an unwrap step to stLINK for greater liquidity availability.\n\nimage1304×394 57.3 KB\n\nSource: stLINK/LINK swap, DeFiLlama Liquidity, May 29th, 2025\n\n~$5.4M worth of stLINK (~338K) can be swapped for LINK within a ~7% slippage. A less correlated swap involving WETH allows for ~$5M worth of stLINK (~315K) to be swapped within a ~7% slippage.\n\n2.1.1 Liquidity Venue Concentration\n\nimage855×210 33.1 KB\n\nSource: stLINK Liquidity Pools on Ethereum, Geckoterminal, May 29th, 2025\n\nAs mentioned in section 1.3.1, a Curve stLINK/LINK stablepool represents the largest source of DEX liquidity on Ethereum with $1.9M stLINK and $4.5M LINK. An older Curve stLINK/LINK pool is also available with $632K and $637K worth of stLINK and LINK, respectively.\n\n2.1.2 DEX LP Concentration\n\nCurve stLINK/LINK LP distribution is concentrated in a LiquidityGaugeV6 contract (95% of stLINK/LINK-ng LP token), with 33 deposits in the contract. Of the 33 deposit token holders, the top 10 holders collectively own 74.4%. The top 5 accounts and their holdings include:\n\nEOA 1: 10.6%\n\nEOA 2: 10.3%\n\nEOA 3: 10.3%\n\nEOA 4: 9.2%\n\n2/2 Multisig: 7.4%\n\nWhile the number of liquidity providers is low, no single account holds a majority of the available liquidity that would be of concern in the event they decided to pull liquidity from the pool.\n\n2.2 Volatility\n\nimage600×371 35.3 KB\n\nSource: Llamarisk, data sourced from Coingecko, February 28th to May 29th, 2025\n\nRelative volatility between stLINK and underlying LINK, as measured by daily returns over the last 90 days, was similar, with stLINK and LINK averaging 5.4% and 5.3%, respectively.\n\nimage831×280 31.7 KB\n\nSource: stLINK/USD, Geckoterminal, May 29th, 2025\n\n2.3 Exchanges\n\nwstLINK is currently not listed on centralized exchanges.\n\n2.4 Growth\n\nimage1081×340 26.7 KB\n\nSource: Dune, May 29th, 2025\n\nstLINK retains strong user interest, as shown in section 1.3, pool capacity has been reached, with queued deposits from the Priority Pool still pending. Growth in rewards over time has remained upward since January 2024, indicating strong deposit retention and overall growth. Over the last 3 months, the rewards rate has averaged 5.41%.\n\n3. Technological Risk\n\n3.1 Smart Contract Risk\n\n13 audits have been performed on stake.link by 4 independent auditors. The most recent audits from each auditor include:\n\nCyfrin (February 2025): 1 informational and 1 gas-related issue found, both acknowledged\n\nTrust Security (February 2025): 1 high, 3 medium, and 3 low severity issues found, the high issue was fixed and all others were either acknowledged or fixed.\n\nCodehawks (November 2024): 1 high, 7 medium, 17 low severity findings. The sole high issue, along with 5 medium and 8 low issues were fixed.\n\nSigma Prime: (January 2023): 1 high, 1 medium, and 17 low severity issues were found. 1 high and 6 low issues were resolved, 5 low were closed, and the rest remained open at the time.\n\nThese audits reflect a history of regular and diverse risk assessments over time.\n\n3.2 Bug Bounty Program\n\nAn Immunefi bug bounty with a max payout of $100K is live. Additionally, the most recent Chainlink Staking bug bounty program for v0.2 consisted of a Code4arena contest, which lasted for 18 days in 2023, and had a total prize pool of $250K.\n\n3.3 Price Feed Risk\n\n1 stLINK is minted for every 1 LINK staked, this 1:1 basis is translated in a varying exchange rate for wstLINK. In the event of slashing, rebases to stLINK generate net negative rewards and therefore affect the wstLINK/stLINK exchange rate negatively. stLINK rebases occur on a weekly basis.\n\nChainlink LINK/USD market price feed is available, with a 1% deviation threshold and 1 hour heartbeat. Using the internal exchange rate along with a CAPO adapter and LINK/USD market price feed would help reflect slashing penalties more accurately than a wstLINK/USD market price feed, therefore this approach is preferred.\n\n3.4 Dependency Risk\n\nNode operators and Chainlink Staking represent the main dependencies for wstLINK. Node operators are vulnerable to slashing penalties should they not meet performance standards set out in the SLA for an oracle network. As stake.link stakes LINK in Node Operator pools, user funds are exposed to losses should the operators stake.link selects underperform.\n\nChainlink Staking is still in the early phases of its roadmap and will introduce more features that may affect rewards. LINK emissions are expected to taper as the main rewards asset as, oracle user fees are introduced. A reputational system will also influence the selection of nodes in an oracle network and therefore rewards.\n\nSlashing represents the main dependency risk, which could potentially expand to Community Staker pools, however, operator selection based on the reputational system could be a mitigating factor.\n\n4. Counterparty Risk\n\n4.1 Governance and Regulatory Risk\n\nStake.link continues to operate through a bifurcated architecture. The protocol was incubated by LinkPool, a veteran Chainlink node operator whose UK vehicle, LinkPool UK Ltd., remains on the Companies House register. Following the December 2024 community proposal SLURP-30, the ecosystem incorporated stakedotlink Limited in the British Virgin Islands as a company limited by guarantee—a not-for-profit form without share capital—tasked with “representing the DAO” in off-chain matters. This wrapper affords the project limited liability, capacity to execute service agreements (e.g. with auditors and market-makers), and an identifiable tax domicile, while token-holder supremacy is preserved through the guarantee-member structure.\n\nThe platform’s Terms dated 21 September 2023 underline its corporate independence by stating that “the Platform is separate from, and not a corporate affiliate of, Chainlink.” Accordingly, ownership of the front-end, branding and ancillary intellectual property lies with stake.link rather than Chainlink Labs.\n\nThose Terms further describe stake.link as a “strictly technology provider” operating on a “non-custodial” basis, then proceed to disclaim liability for virtually every foreseeable contingency—from smart-contract exploits and price volatility to erroneous artificial-intelligence outputs (e.g. SergAI clause). Users must indemnify the platform for defence costs, and while access is barred to Office of Foreign Assets Control–sanctioned jurisdictions, it is otherwise left open to U.S. persons, subject to unilateral suspension rights. New York law governs; all disputes must be submitted to three-member ICDR arbitration seated in New York; fiduciary, professional, custody and suitability duties are expressly disavowed; class actions, VPN circumvention and sanctioned-country access are contractually prohibited.\n\nWhen a user mints wstLINK pursuant to these Terms, the resulting receipt token entitles its holder to a pro-rata economic interest in a professionally managed staking pool. Contractual waivers, however, cannot forestall a regulator from categorizing that interest as a security or collective-investment unit if the underlying functional tests are satisfied.\n\nwstLINK itself embodies a transferable, yield-bearing claim on an aggregated asset base, with smart-contract logic and DAO governance compounding rewards autonomously. These additional layers—pooling, tokenization, secondary liquidity—mirror the characteristics that U.S. courts and the Securities and Exchange Commission have previously cited when treating Lido’s stETH and Coinbase’s staking program as investment contracts. In its 29 May 2025 statement, the SEC’s Division of Corporation Finance drew a bright line: “protocol staking” does not constitute a securities offering, but “liquid-staking tokens” such as wstLINK were conspicuously excluded from that safe harbour. Validator-level staking therefore enjoys a clearer regulatory pathway in the United States, yet the transferable receipt token minted atop Stake.link remains in limbo—and may draw increased scrutiny. A footnote in the statement explicitly declines to address “liquid staking, restaking or liquid restaking,” and contemporaneous commentary emphasizes that the guidance lacks binding legal effect, postponing a view on more complex receipt-token models.\n\nNotwithstanding the foregoing, a canvass of SEC, CFTC, FCA, BaFin, MAS and public-court dockets reveals no enforcement proceedings or civil claims against Stake.link, stakedotlink Limited or LinkPool as of 2 June 2025.\n\nBeyond that, we have formally requested that stake.link produce documentary evidence of any legal analysis previously conducted on wstLINK. If such an opinion exists—whether as an external counsel memorandum or an internal regulatory assessment—it would supply contemporaneous support capable of addressing several of the concerns outlined above.\n\n4.2 Access Control Risk\n\n4.2.1 Contract Modification Options\n\nAll stake.link contracts and Treasury wallet are controlled by a 6/8 multisig, which is managed by the Node Operator Council (see section 1.2 for key contracts).\n\nPrivileged functions in the stLINK contract that are exposed include:\n\nFunction\nImpact\n\naddStrategy() / removeStrategy()\n\nAdd/remove staking strategies. Could redirect funds to malicious contracts if compromised.\n\nsetRebaseController()\n\nGrants reward distribution control.\n\naddFee() / updateFee()\n\nConfigure fee. Modifies or removes an existing fee.\n\nsetPriorityPool()\n\nRestricts who can stake/withdraw.\n\nburn()\n\nBurns liquid staking tokens.\n\nDeployed contracts are well documented along with their functions in stake.link docs.\n\n4.2.2 Timelock Duration and Function\n\nstLINK is owned by a Governance Timelock contract, which has a 24-hour delay. This delay may potentially be too short for users to make assessments of any parameter changes and opt out.\n\n4.2.3 Multisig Threshold / Signer identity\n\nThe Node Operator Council is made up of 8 council members. Current signers to the governance multisig include:\n\n2 Core Contributors from LinkPool.io\n\nMatrixed.Link\n\nLinkForest.io\n\nChainlayer.io\n\nGalaxy Digital\n\nThe SDL DAO\n\nHarris and Trotter.\n\nNote: This assessment follows the LLR-Aave Framework, a comprehensive methodology for asset onboarding and parameterization in Aave V3. This framework is continuously updated and available here.\n\nAave V3 Specific Parameters\n\nThe wstLINK deployment parameters have been decided jointly with @ChaosLabs and will be published in their follow-up shortly. The asset is to be onboarded with a similar setup as ETH LSTs, enabling a LINK Correlated E-Mode designed for efficient wstLINK yield looping.\n\nPrice feed Recommendation\n\nWe recommend to price wstLINK employing the internal exchange rate, in combination with CAPO and Chainlink’s LINK/USD market price feed. This will lessen the dependence on secondary market fluctuations while covering the asset’s slashing risk.\n\nDisclaimer\n\nThis review was independently prepared by LlamaRisk, a community-led decentralized organization funded in part by the Aave DAO. LlamaRisk is not directly affiliated with the protocol(s) reviewed in this assessment and did not receive any compensation from the protocol(s) or their affiliated entities for this work.\n\nThe information provided should not be construed as legal, financial, tax, or professional advice.\n\n4 Likes\n\nLlamaRisk - Monthly Community Update\n\nsid_areta\n\nJune 4, 2025, 12:54pm\n\n3\n\nGreat to hear the feedback on the wstLINK risk profile - liquidity does seem to be slightly constrained on Curve and this should be reflected in the risk parameters, but bringing LINK into DeFi is a big opportunity and one that we’re very much in favour of.\n\n2 Likes\n\nChaosLabs\n\nJune 4, 2025, 5:19pm\n\n4\n\nOverview\n\nChaos Labs supports listing wstLINK on Aave’s Ethereum Core instance. Below is our analysis and initial risk parameter recommendations.\n\nChainlink Staking\n\nChainlink Staking is one of the components of Chainlink’s cryptoeconomic security model, designed to enhance the reliability of oracle services by aligning incentives and introducing accountability through staking and slashing mechanisms. In its current form, Chainlink Staking secures the ETH/USD data feed on Ethereum Mainnet. Node operators help ensure data integrity by putting capital at risk, thereby strengthening the trust guarantees of Chainlink oracles.\n\nChainlink Staking was first introduced with v0.1 in December 2022. As an initial iteration, v0.1 enabled LINK holders to stake tokens and earn protocol rewards, but it did not include any slashing mechanisms. The total staking cap for v0.1 was 25 million LINK, allocated across early Community and Node Operator participants.\n\nIn November 2023, Chainlink Staking was upgraded to v0.2. This upgrade introduced a set of improvements, including an unbonding mechanism for withdrawals, and most notably, slashing capabilities for Node Operator Stakers. Alongside these functional enhancements, the total staking capacity increased by 80%, raising the overall cap from 25 million to 45 million LINK.\n\nChainlink Staking v0.2 is composed of two primary pools:\n\nCommunity Staking Pool, capped at 40.875 million LINK\n\nNode Operator Staking Pool, capped at 4.125 million LINK\n\nThese pools serve distinct roles within the system:\n\nCommunity Stakers are individual or institutional LINK holders who contribute capital but do not provide oracle services directly. Instead, they delegate their stake to the Node Operators. Importantly, Community Stakers are not subject to slashing under v0.2.\n\nNode Operator Stakers are responsible for running Chainlink oracle services (e.g., the ETH/USD data feed). These participants must stake LINK and operate reliable infrastructure. Node Operator stakes can be slashed if performance criteria are violated.\n\nSince the launch of v0.2, the Community Pool has consistently operated at full capacity, with nearly all 40.875 million LINK staked. In contrast, the Node Operator Pool has remained underutilized, with approximately 1.9 million LINK staked out of the 4.125 million LINK cap.\n\nmulti_line_stacked_chart_17485992011920×1405 96.1 KB\n\nDeposit and Withdrawals\n\nFor Community Stakers, deposits can be made through the Chainlink Staking interface or third-party protocols like stake.link, which offer liquid staking tokens such as stLINK and wstLINK. Once staked, LINK is delegated to Node Operators to support oracle services. Deposits into the Community Pool are subject to pool capacity constraints, which have generally been reached since the launch of v0.2.\n\nWithdrawals from the Community Pool follow a two-step unbonding mechanism:\n\nCooldown Period: Stakers initiate a withdrawal request, triggering a fixed 28-day cooldown period during which the staked LINK continues to accrue rewards.\n\nClaim Window: After the cooldown, a 7-day claim window opens. If the staker does not withdraw during this window, the LINK is automatically restaked into the pool.\n\nThis unbonding mechanism is a preventative measure against mass exits during slashing events, helping maintain pool stability and ensuring sufficient staked LINK remains available to enforce penalties.\n\nNode Operator Stakers follow a similar deposit process but must also meet eligibility criteria, including operating approved Chainlink nodes. Withdrawals from the Node Operator Pool are also governed by the 28-day unbonding period and the 7-day claim window.\n\nRewards\n\nChainlink Staking v0.2 features a redesigned reward model that accounts for pool utilization and introduces cryptoeconomic penalties to enhance service reliability.\n\nStaking rewards are distributed in LINK and reward rates are variable, based on pool utilization and the total amount of rewards available per unit time. At full pool capacity, the base floor reward rate for Community Stakers is 4.5% annually. However, 4% of this is redirected to Node Operator Stakers, resulting in an effective base reward rate of 4.32% for Community participants.\n\nScreenshot 2025-06-02 at 10.22.181726×1104 26 KB\n\nNode Operator Stakers earn rewards from multiple sources, including their share of the base 4.5% annual reward rate and the 4% delegation fee redirected from Community Stakers. As a result, operator yields are structurally higher and designed to incentivize reliable and sustained oracle service provision.\n\nWhile current rewards rely primarily on LINK emissions, the long term goal is to gradually taper off emission based rewards and begin distributing user fees as the primary source of staking incentives. In parallel, ecosystem projects participating in the Chainlink BUILD program have committed a portion of their native tokens to Chainlink Staking. These tokens are expected to be distributed to Community and Node Operator Stakers over time, further diversifying the reward base and aligning incentives across the Chainlink ecosystem.\n\nPenalties\n\nThe introduction of Chainlink Staking v0.2 brought with it the first implementation of slashing penalties, designed to hold Node Operator Stakers accountable for the reliability of the oracle services they secure. These penalties are intended to safeguard data integrity by creating real economic consequences for underperformance.\n\nCurrently, only the ETH/USD data feed on Ethereum Mainnet is secured by v0.2 staking. If the feed experiences more than three hours of downtime, a valid alert can be raised onchain. Node Operators have a 20-minute priority window to submit the alert. If no alert is raised within that window, any eligible Community Staker may submit it. Only the first valid alert for each incident is accepted; additional alerts during the same event are disregarded.\n\nEach slashed Node Operator incurs a penalty of 700 LINK\n\nThe first valid alerter is rewarded with 7,000 LINK\n\nAs of writing, 31 different Node Operators are actively participating in Chainlink Staking v0.2. Each operator can stake up to 75,000 LINK. In practice, approximately 1.9 million LINK is currently staked in the Node Operator Pool, representing the capital currently at risk of being slashed.\n\nGiven the fixed penalty of 700 LINK per operator, the theoretical (albeit very unlikely) total maximum slashable amount in a single event is 31 × 700 = 21,700 LINK, which constitutes approximately 1.1% of the Node Operator Pool and 0.05% of the total v0.2 staking pool.\n\nTo date, there have been no recorded slashing events affecting any node operator participating in the Chainlink Node Operator Staking Pool. This reflects the relatively low risk profile of the current staking configuration. Nonetheless, slashing remains a theoretical possibility and should be accounted for in any comprehensive risk assessment.\n\nIt is important to note that Community Stakers are not subject to slashing under the current version. Any future change to this design would require a version upgrade and a corresponding opt-out period enforced via a time-locked upgrade mechanism. This approach helps ensure protocol transparency and allows participants to react accordingly before changes take effect.\n\nstake.link\n\nstake.link is a delegated liquid staking protocol purpose built for Chainlink Staking by LinkPool, a long standing Chainlink node operator and infrastructure provider. It enables LINK holders to stake their tokens into Chainlink’s staking system by abstracting away the complexities of staking and node operation.\n\nWhen users stake LINK through stake.link, they receive stLINK, a liquid staking token that rebases weekly to reflect accrued staking rewards. For use cases requiring a non-rebasing token, stake.link also offers wstLINK, a wrapped version of stLINK that preserves staking value in a fixed supply format.\n\nOne of the key benefits for users is the auto staking functionality: whenever new staking capacity becomes available on Chainlink, such as when another user withdraws from the Community Staking Pool, stake.link automatically stakes LINK from its Priority Pool on behalf of users waiting in the queue.\n\nUnlike directly staking with the Community Staking Pool through the Chainlink interface, stake.link stakes LINK into both the Community and Node Operator pools. Since Node Operator stakes earn a higher effective yield, partly due to receiving delegation fees from Community Stakers, this blended strategy results in a higher aggregate return for stLINK holders compared to staking solely with the Community Pool. However, this additional yield exposure comes with slashing risk on the portion of stake delegated to the Node Operator Pool, a consideration we will explore in the following sections.\n\nPriority Pool\n\nThe Priority Pool is a core mechanism within stake.link designed to improve user experience around staking and redemption by introducing a liquidity buffer between users and the Chainlink Staking protocol. It serves two primary functions:\n\nAuto-staking Queue: When users deposit LINK into stake.link but there is no immediate staking capacity available on Chainlink, their funds are held in the Priority Pool. As soon as capacity becomes available, due to unstakes or staking limit increases, stake.link automatically stakes LINK on behalf of users in the queue.\n\nRedemption Liquidity Buffer: The Priority Pool also enables faster or instant redemptions of stLINK and wstLINK. Instead of waiting through the native 28-day cooldown and 7-day claim window required by Chainlink Staking, users can redeem their staked tokens instantly, as long as there is sufficient LINK available in the Priority Pool to cover the withdrawal.\n\nOver the past three months, the Priority Pool buffer has typically hovered between 100,000 and 300,000 LINK, offering a meaningful layer of liquidity for redemptions. Since its creation on 20 September 2023, there have been periods when the pool was fully depleted, causing some redemption requests to be temporarily delayed until new deposits replenished the balance or withdrawal requests were unbonded through Chainlink Staking. However, such instances have been historically limited. In practice, the pool has maintained a healthy buffer: over 85% of the time, it has held more than 10,000 LINK available for redemptions.\n\nline_chart_17488774831920×1377 74.1 KB\n\nSlashing Risk\n\nWhile stake.link enhances yield for stakers through its dual pool strategy (Community and Node Operator staking pools), it also introduces a limited degree of slashing risk due to its exposure to the Node Operator Staking Pool on Chainlink.\n\nBy design, stake.link allocates user deposits across both staking modules within Chainlink Staking v0.2:\n\nThe Community Staking Pool, which carries no slashing risk under the current version\n\nThe Node Operator Staking Pool, which is subject to slashing in the event of oracle underperformance\n\nAs of now, approximately 25% of the backing for stLINK, equivalent to 1,125,000 LINK, is actively staked with the Node Operator Pool. This portion is distributed evenly across 15 different node operators.\n\nOnly the LINK delegated to this module is exposed to slashing. In a worst-case scenario, where all 15 node operators are simultaneously slashed, the total amount penalized would be:\n\n15 × 700 LINK = 10,500 LINK\n\nThis represents just 0.23% of the total backing of stLINK, a relatively small impact when viewed in the context of the protocol’s overall stake distribution. While highly unlikely, this scenario illustrates the bounded downside stLINK and wstLINK holders face due to partial exposure to slashing.\n\nAs can be seen in the chart, stake.link’s allocation to the Node Operator Pool has remained flat since early 2024, indicating that the protocol has not onboarded new operators in recent months and years. Instead, stake.link appears to be increasingly utilizing available capacity in the Community Staking Pool whenever possible. This trend is evidenced by the consistent growth in community pool allocations, which has had the effect of diluting the relative slashing exposure within the total stLINK backing over time.\n\nmulti_line_chart_17488553801920×1378 96.2 KB\n\nMint and Redemption\n\nMinting in stake.link is not always atomic, due to the staking caps enforced by the Chainlink Staking protocol. When a user deposits LINK into stake.link, the funds are first placed in the Priority Pool, rather than being staked immediately.\n\nFrom there, the protocol waits for available capacity to open up in Chainlink Staking, either through withdrawal activity or increases in pool limits. As space becomes available, the Priority Pool automatically stakes the user’s LINK into either the Community or Node Operator Pools.\n\nAs staking occurs incrementally, users begin accruing eligibility to claim stLINK (or wstLINK) proportionally. Users have two options:\n\nWait until their entire deposit has been staked and mint their full stLINK/wstLINK balance in one transaction\n\nClaim progressively as portions of their LINK are staked, minting partial amounts of stLINK over time\n\nThis flow ensures that stLINK is only minted against LINK that has actually been staked on-chain. It also means that minting is dependent on staking availability, introducing some delay during periods when Chainlink staking capacity is saturated.\n\nTo redeem LINK, users return their stLINK or wstLINK to the protocol. There are two potential redemption paths:\n\nInstant Redemption via Priority Pool\n\nIf the Priority Pool holds enough unallocated LINK, users can redeem their tokens immediately.\n\nDelayed Redemption via Chainlink Unbonding\n\nIf the Priority Pool is insufficiently funded, redemption requests are queued and processed through the unbonding mechanism. In this case, users generally wait through the 7 day cooldown period before receiving their unstaked LINK.\n\nMarket Capitalization\n\nThe stLINK/wstLINK market has seen consistent growth and adoption since launch. As of today, stake.link’s liquid staking tokens are backed 1:1 by approximately 4.55 million staked LINK, reflecting a material share of total staked capital in the Chainlink ecosystem. Currently, only around 17% of stLINK has been converted into wstLINK. However, this proportion is expected to grow over time as more DeFi protocols and strategies begin to integrate and prefer the non-rebasing version for compatibility and composability.\n\nmulti_line_chart_17488662611920×1378 85.3 KB\n\nAt current market prices, this translates to a total market size of approximately $65 million for stake.link’s liquid staking assets. While Chainlink Staking itself is hard-capped at 45 million LINK, this effectively sets an upper bound on the TAM for stake.link’s LSTs. In other words, if 100% of Chainlink Staking were liquid staked via stake.link, the maximum stLINK supply would be capped at 45 million.\n\nCurrently, stake.link accounts for roughly 10% of all staked LINK within Chainlink Staking v0.2. This share continues to grow, driven by the protocol’s enhanced yield (through Node Operator Pool exposure) and liquidity advantage (via the Priority Pool), which are attractive features for DeFi participants.\n\nThe demand for stake.link assets is further evidenced by:\n\nThe consistent presence of significant LINK balances in the Priority Pool, indicating a queue of users awaiting staking capacity\n\nThe premium observed in stLINK’s secondary market price relative to native LINK\n\nPremium Drivers\n\nOver the past month, stLINK has traded at a slight premium to LINK on secondary markets. This premium reflects a combination of structural demand and market anticipation, driven by two primary catalysts:\n\nAirdrops from Chainlink BUILD projects have begun, providing additional rewards to Chainlink Stakers and further enhancing the appeal of stake.link’s liquid staking tokens as both a preferred staking vehicle and a means of gaining exposure to these airdrops.\n\nExpectations around upcoming Aave listings might have led users to position themselves for looping strategies that capitalize on wstLINK’s yield-bearing properties.\n\nline_chart_17488649816063×4349 451 KB\n\nThere have been periods where the token consistently traded at a 2 to 4% premium on secondary markets from its launch until July 2024. Premium has recently started to rise again and is currently around 0.5%.\n\nLiquidity\n\nThe primary source of secondary market liquidity for stake.link’s stLINK token is on Curve Finance, where stLINK/LINK pools facilitates swaps between the two assets.\n\nCurrently, all available liquidity is for the stLINK token, not wstLINK. However, this does not pose a constraint for users, as wstLINK can be atomically unwrapped into stLINK and vice versa without any delay.\n\nThe total liquidity in the Curve pools has ranged between 6.5 million and 8 million USD in recent weeks. This is considered highly adequate for a liquid staking token with a total market size of approximately $65 million, representing over 10% of the token’s market capitalization.\n\nliquidity_chart_17488622481920×1379 59.9 KB\n\nLiquidity within the pool is consistently skewed toward LINK, with 70 to 75% of the liquidity allocated to the LINK side. This skew is a reflection of sustained demand for stLINK, as users seek exposure to Chainlink staking rewards. As a result, stLINK has been traded at a premium to its underlying asset.\n\nDue to this imbalance, the current pool depth and Curve’s optimized pricing mechanism allow for significant trade sizes with minimal slippage. For example, a swap of approximately 340,000 stLINK (around $4.82 million) can be executed with less than 5% price impact, demonstrating the pool’s capacity to support large trades.\n\nGiven that stLINK rewards are distributed on a weekly basis, some actors have been observed engaging in sandwiching behavior within the AMM to extract a disproportionate share of rewards. Curve’s dynamic fee mechanism currently mitigates this effect to some extent. However, this risk may grow if liquidity expands to AMMs without similar protections. Ongoing monitoring of trading activity is advised to detect and manage potential reward extraction as the protocol’s liquidity footprint broadens.\n\nOracle/Pricing\n\nThe wstLINK smart contract maintains an internal exchange rate that reflects the rebasing value accrual of its underlying stLINK asset. This exchange rate increases over time as staking rewards accrue, allowing wstLINK to preserve value growth in a fixed supply format suitable for DeFi integrations.\n\nTo ensure secure and accurate pricing of wstLINK in USD terms, Chaos Labs recommends the following oracle composition using a CAPO adaptor architecture:\n\nwstLINK/LINK Exchange Rate\n\nRetrieve the exchange rate directly from the stLINK contract, which provides the conversion ratio between wstLINK and LINK.\n\nCAPO Adapter: wstLINK/LINK\n\nApply a dedicated CAPO adaptor to track the wstLINK to LINK exchange rate.\n\nLINK/USD Feed\n\nUse the existing LINK/USD price feed to convert the LINK value into USD terms.\n\nLT, LTV, and Liquidity Bonus\n\nTo ensure prudent risk management while enabling initial capital efficiency, we recommend setting a LTV of 64%, a LT of 69%, and a Liquidation Bonus of 7% for wstLINK outside of E-Mode. These parameters are in line with the settings used for other yield bearing staking tokens with similar risk characteristics.\n\nSupply & Borrow Caps\n\nTo ensure a controlled onboarding of wstLINK to the Aave protocol, we recommend setting the supply cap at 600,000 wstLINK. This configuration reflects a cautious approach to risk management while allowing meaningful participation from users seeking to supply wstLINK as collateral. The proposed cap corresponds to approximately $11.3 million in notional value and is calibrated based on available secondary market liquidity and the protocol’s current market capitalization.\n\nWe do not foresee any compelling use cases for borrowing wstLINK, and enabling it as a borrowable asset introduces significant risk due to its pricing dynamics. As discussed in previous sections, wstLINK typically trades at a premium in secondary markets, driven by factors such as staking capacity constraints in Chainlink Staking, increased demand for leveraged staking exposure, and potential airdrops for Chainlink stakers from Chainlink BUILD projects.\n\nSince Aave derives the prices of LST/LRTs from its on-chain exchange rate to underlying and does not account for market premiums, making wstLINK borrowable could enable users, in certain extreme but plausible scenarios where stLINK trades at a high premium to LINK, to borrow it at the oracle price and sell it at a higher market price. This would allow them to extract arbitrage profits while leaving Aave undercollateralized. Such activity creates a risk of protocol bad debt, particularly during periods of elevated secondary market demand.\n\nTo mitigate this risk, we strongly recommend listing wstLINK as non-borrowable.\n\nE-Mode\n\nWe propose creating a dedicated LINK-correlated E-Mode to support efficient capital utilization between wstLINK and LINK. In this setup, wstLINK would be enabled exclusively as collateral, while LINK would be borrowable only. We recommend setting the LTV at 90%, the LT at 92%, and the Liquidation Bonus at 2% to balance capital efficiency with controlled liquidation risk.\n\nCAPO\n\nwstLINK inherits staking rewards from Chainlink Staking, reflecting the yield generated through delegation to the Community and Node Operator pools. The effective yield of wstLINK varies over time based on staking pool utilization and delegation fee structures.\n\nTo ensure a robust and manipulation-resistant CAPO price feed for the wstLINK/LINK pair, we propose a maxYearlyRatioGrowthPercent of 6.89%, reflecting the expected annualized staking yield including delegation income. Additionally, we recommend setting the MINIMUM_SNAPSHOT_DELAY to 14 days to smooth out short-term volatility and ensure consistency in pricing inputs.\n\nmulti_line_chart_17488625111920×1641 118 KB\n\nLINK IR Optimization\n\nThe upcoming listing of wstLINK is expected to introduce renewed demand for borrowing LINK, particularly from users engaging in staking loop strategies. Historically, LINK borrow utilization on Aave has been relatively low and declining, with total outstanding borrow dropping from approximately 800,000 LINK to the 300,000 range in recent months.\n\nScreenshot 2025-06-04 at 11.29.091257×438 20.1 KB\n\nThe addition of wstLINK is likely to reverse this trend and create sustained borrowing demand. To ensure efficient rate dynamics under higher utilization and to better reflect the opportunity cost of capital, we recommend increasing the base interest rate for LINK by 1.5%. In parallel, we suggest reducing slope2 from 300% to 150% to soften borrowing costs beyond the optimal utilization threshold and reduce the likelihood of excessively punitive rates during temporary utilization spikes.\n\nLINK Borrow Cap Adjustment\n\nIn conjunction with the expected increase in demand for LINK borrowing due to the listing of wstLINK, it is also important to manage protocol risk through appropriate caps. The current borrow cap for LINK is set at 13.00 million, a level that exceeds recent utilization by a margin. With outstanding borrows currently around 300,000 LINK, the existing cap is significantly underutilized.\n\nTo align the borrow cap more closely with expected demand while maintaining a prudent risk posture, we recommend lowering the LINK borrow cap to 6 million. This level allows ample room for increased borrowing activity driven by wstLINK-related strategies while preventing excessive leverage that could amplify protocol exposure during periods of volatility.\n\nSpecification\n\nParameter\nValue\n\nAsset\n\nwstLINK\n\nIsolation Mode\n\nN/A\n\nBorrowable\n\nNo\n\nCollateral Enabled\n\nYes\n\nSupply Cap\n\n600,000\n\nBorrow Cap\n\n-\n\nDebt Ceiling\n\n-\n\nLTV\n\n64%\n\nLT\n\n69%\n\nLiquidation Penalty\n\n7%\n\nLiquidation Protocol Fee\n\n10%\n\nVariable Base\n\n-\n\nVariable Slope1\n\n-\n\nVariable Slope2\n\n-\n\nUoptimal\n\n-\n\nReserve Factor\n\n-\n\nStable Borrowing\n\nDisabled\n\nFlashloanable\n\nYes\n\nSiloed Borrowing\n\nNo\n\nBorrowable in Isolation\n\nNo\n\nE-Mode Category\n\nwstLINK/LINK\n\nE-Mode\n\nParameter\nValue\nValue\n\nAsset\n\nwstLINK\n\nLINK\n\nCollateral\n\nYes\n\nNo\n\nBorrowable\n\nNo\n\nYes\n\nMax LTV\n\n90.00%\n\n-\n\nLiquidation Threshold\n\n92.00%\n\n-\n\nLiquidation Bonus\n\n2.00%\n\n-\n\nCAPO\n\nmaxYearlyRatioGrowthPercent\nratioReferenceTime\nMINIMUM_SNAPSHOT_DELAY\n\n6.89%\n\nmonthly\n\n14\n\nInterest Rate\n\nInstance\nAsset\nCurrent Base\nRecommended Base\nCurrent Slope2\nRecommended Slope2\n\nEthereum Core\n\nLINK\n\n0%\n\n1.5%\n\n300%\n\n150%\n\nBorrow Cap\n\nInstance\nAsset\nCurrent Supply Cap\nRecommended Supply Cap\nCurrent Borrow Cap\nRecommended Borrow Cap\n\nEthereum Core\n\nLINK\n\n20,000,000\n\n-\n\n13,000,000\n\n6,000,000\n\nDisclaimer\n\nChaos Labs has not been compensated by any third party for publishing this recommendation.\n\nCopyright\n\nCopyright and related rights waived via CC0\n\n7 Likes\n\nPaulPrec\n\nJuly 15, 2025, 6:08pm\n\n6\n\nGM! Any news regarding execution of this proposal?\n\n4 Likes\n\nCubeOfCandor\n\nAugust 6, 2025, 6:00am\n\n7\n\nSecond this, seems to be sufficient community support, including from the original TEMP-CHECK. Would be great to see an update if possible.\n\n2 Likes\n\nClos\n\nSeptember 2, 2025, 12:21am\n\n8\n\nThis does look sufficient - what needs to be done to advance this?\n\n3 Likes\n\nTokenized\n\nSeptember 18, 2025, 1:51pm\n\n9\n\nI wonder as well if this can be escalated somehow. marines be hungry\n\n2 Likes\n\nMarcZeller\n\nDecember 11, 2025, 1:36am\n\n10\n\nHello,\n\nNow that Aave 3.6 is around the corner Let’s revisit this proposal.\n\nWith the benefit of V.3.6 we can tailor risk parameters centered around precise usecases fitting for this asset:\n\nWe recommend an onboarding with LTV0 and two emode configurations:\n\nHigh LTV stLINK/LINK emode with Stlink as collateral only and LINK as borrow only\n\nmore conservative emode with stLINK as collateral only and USDC/USDT/GHO/USDe as borrow only.\n\nWe are inviting @ChaosLabs and @LlamaRisk to provide updated risk parameters.\n\nWe are also inviting @bgdlabs to provide a technical analysis on the asset.\n\n7 Likes\n\nrankko\n\nDecember 17, 2025, 4:02pm\n\n11\n\nI ran a conservative onchain analysis to understand wallet-level overlap between current stLINK holders and historical Aave V3 suppliers. Using a same-wallet heuristic, ~18.7% of stLINK-holding wallets have previously supplied to Aave. While overlap is limited by wallet count, it confirms some degree of Aave familiarity and supports a conservative, isolated rollout.\n\nLink: Wallet-level overlap between stLINK holders and historical Aave V3 suppliers\n\nimage1331×848 146 KB\n\n4 Likes\n\nChaosLabs\n\nDecember 18, 2025, 11:06am\n\n12\n\nOverview\n\nWe are supportive of listing wstLINK with the upcoming v3.6 update, but under a deliberately constrained configuration. Specifically, we do not intend to enable access to stablecoin borrowing through either general collateral status or stablecoin E-Mode. This decision is not driven solely by asset specific supply and demand dynamics, but also reflects a broader, protocol wide approach to limiting exposure to uncorrelated debt originating from long tailed collateral with limited expected upside.\n\nFollowing the October 10 market dislocation, Aave governance adopted a more conservative risk posture toward long tail and volatile collateral assets, particularly with respect to their ability to back stablecoin debt. As outlined in our risk parameter updates after 10/10, these assets have historically generated minimal protocol revenue while introducing disproportionate risk. This unfavorable risk reward profile, combined with elevated price volatility, frequent oracle deviations and lower market efficiency, motivated the recommendation to minimize or fully remove collateralization power for such assets.\n\nThis stance also reflects several asset specific structural considerations. Staking caps for LINK remain unchanged and are not expected to increase in the near term, while the amount of LINK held in the stake.link Priority Pool has risen materially from approximately 200,000 to 700,000 LINK, representing an increase of roughly 250% and signaling significant pent up demand for st/wstLINK.\n\nTogether, these supply constraints and demand dynamics have resulted in persistent premium pricing for stLINK and wstLINK, typically in the range of 0.1% to 0.7%, with premiums reaching as high as 2.5% around the time of the previous listing discussion in early June. As the listing approaches, additional premium pressure is likely, particularly in the absence of near term staking cap expansions.\n\nIn light of these dynamics, and in alignment with the protocol wide conservative risk posture adopted after October 10, we propose limiting wstLINK access to stablecoin borrowing and introducing the asset with a moderate supply cap. This configuration seeks to balance user access with prudent risk containment, while avoiding the introduction of uncorrelated stablecoin debt backed by collateral that is already exhibiting supply tightness and persistent premium pricing. Updated specifications are provided below.\n\nSpecification\n\nParameter\nValue\n\nAsset\n\nwstLINK\n\nIsolation Mode\n\nN/A\n\nBorrowable\n\nNo\n\nCollateral Enabled\n\nNo\n\nSupply Cap\n\n500,000\n\nBorrow Cap\n\n-\n\nDebt Ceiling\n\n-\n\nLTV\n\n-\n\nLT\n\n-\n\nLiquidation Penalty\n\n-\n\nLiquidation Protocol Fee\n\n10%\n\nVariable Base\n\n-\n\nVariable Slope1\n\n-\n\nVariable Slope2\n\n-\n\nUoptimal\n\n-\n\nReserve Factor\n\n-\n\nStable Borrowing\n\nDisabled\n\nFlashloanable\n\nYes\n\nSiloed Borrowing\n\nNo\n\nBorrowable in Isolation\n\nNo\n\nE-Mode Category\n\nwstLINK/LINK\n\nE-Mode (wstLINK/LINK)\n\nParameter\nValue\nValue\n\nAsset\n\nwstLINK\n\nLINK\n\nCollateral\n\nYes\n\nNo\n\nBorrowable\n\nNo\n\nYes\n\nMax LTV\n\n90.00%\n\n-\n\nLiquidation Threshold\n\n92.00%\n\n-\n\nLiquidation Bonus\n\n2.00%\n\n-\n\nCAPO\n\nmaxYearlyRatioGrowthPercent\nratioReferenceTime\nMINIMUM_SNAPSHOT_DELAY\n\n6.89%\n\nmonthly\n\n14\n\nInterest Rate\n\nInstance\nAsset\nCurrent Base\nRecommended Base\nCurrent Slope2\nRecommended Slope2\n\nEthereum Core\n\nLINK\n\n0%\n\n1.5%\n\n300%\n\n150%\n\nBorrow Cap\n\nInstance\nAsset\nCurrent Supply Cap\nRecommended Supply Cap\nCurrent Borrow Cap\nRecommended Borrow Cap\n\nEthereum Core\n\nLINK\n\n20,000,000\n\n-\n\n13,000,000\n\n6,000,000\n\nDisclaimer\n\nChaos Labs has not been compensated by any third party for publishing this recommendation.\n\nCopyright\n\nCopyright and related rights waived via CC0\n\n7 Likes\n\nChaos Labs - Monthly Community Update\n\nLlamaRisk\n\nDecember 19, 2025, 12:31pm\n\n13\n\nSummary\n\nLlamaRisk supports the listing of wstLINK on Aave’s Ethereum Core instance with the parameter adjusted to align with the V3.6 update, limiting exposure to the wstLINK/LINK looping use case. Following our initial analysis, no major architectural changes were observed, with notable market risk changes relating to an increase in the protocol’s buffer liquidity and an increased reliance on a single DEX pool.\n\nAdditionally, we observed that the staking pool cap has increased at a slower rate than staking demand, with the Priority pool increasing to over $9M in LINK deposits waiting to be staked (up from approximately $3.4M). In contrast, the staking pool capacity has only increased by ~1.3M LINK. stLINK remains volatile but has maintained a strong, correlated relationship with LINK on secondary markets.\n\nIn line with the governance adopted stance to minimize exposure to long-tail and volatile collateral assets that generate low protocol revenue relative to their risk exposure, a wstLINK/Stablecoin E-mode is not advised, nor is allowing stablecoin access through general parameter configurations due to the debt risk they introduce.\n\nThe wstLINK deployment parameters have been decided jointly with @ChaosLabs.\n\nLiquidity\n\nstLINK liquidity has remained largely unchanged since our initial analysis in May 2025. For a correlated swap, ~$4.7M worth of stLINK (~365K) can be swapped for LINK within a ~2% slippage. Alternatively, approximately 386K stLINK (~$5.3M) can be swapped within a 7% slippage (previously ~316K stLINK, $5M).\n\nimage1239×352 20.8 KB\n\nSource: DeFiLlama stLINK/LINK, December 15th, 2025\n\nimage1307×357 22.1 KB\n\nSource: DeFiLlama stLINK/WETH, December 15th, 2025\n\nAvailable liquidity has declined to a single Curve pool; previously, 2 pools over $1M TVL were available.\n\nimage856×209 34.7 KB\n\nSource: stLINK liquidity pools, GeckoTerminal, December 15th, 2025\n\nLiquidity Buffer and Staking Cap\n\nThe Priority pool, which serves as a deposit staking queue and liquidity buffer for withdrawals, has increased its available LINK balance to a current total of 704K (~$9.7M). Withdrawals are instant if sufficient liquidity is available; otherwise, withdrawals are processed between 1 and 7 days.\n\nimage903×355 46.1 KB\n\nSource: Priority Pool Balance, Dune, December 14th, 2025\n\nSince our initial analysis, pool staking capacity has increased from 4.5M LINK to 5.8M. The increased deposits represent an increase in staking demand, which exceeds staking capacity changes a\n\nimage594×261 11.2 KB\n\nSource: stLINK pool info, stake.link, December 19th, 2025.\n\nVolatility\n\nA relatively low secondary market price misalignment was observed between stLINK and the underlying LINK over a 90-day period. Since stLINK will be priced using its internal stLINK/LINK exchange rate, the probability of liquidations will be low.\n\nAs shown in the graph below, recurring daily price fluctuations of ~10% were observed.\n\nimage600×371 28.9 KB\n\nSource: Coingecko, September 12th to December 11th, 2025\n\nstLINK trades at a consistent slight premium to LINK, the token likely trades higher due to the staking cap limiting access stLINK.\n\nimage736×325 17.8 KB\n\nSource: stLINK/LINK Curve pool, GeckoTerminal, December 19th, 2025\n\nAave V3.6 Specific Parameters\n\nThe wstLINK deployment parameters have been decided jointly with @ChaosLabs. The asset should be onboarded to enable a LINK Correlated E-Mode designed for efficient wstLINK yield looping.\n\nDisclaimer\n\nThis review was independently prepared by LlamaRisk, a DeFi risk service provider funded in part by the Aave DAO. LlamaRisk is not directly affiliated with the protocol(s) reviewed in this assessment and did not receive any compensation from the protocol(s) or their affiliated entities for this work.\n\nThe information provided should not be construed as legal, financial, tax, or professional advice.\n\n5 Likes\n\nLlamaRisk - Monthly Community Update\n\nzouizoui\n\nDecember 19, 2025, 8:30pm\n\n14\n\nHello @ChaosLabs, Just a regular aave user and link holder here :\n\nI tried to run the maths and i would like you to correct me if i’m wrong :\n\nAccording to your new parameters (borrow cap, slope, and base interest rate), and based on current data (742k LINK borrowed):\n\nWithout any further borrowing, the borrowing cost would spike to ~3.5% for all LINK borrowers, including those not engaging in any looping strategy.\n\nThe looping strategy (current wstlink apr ~ 4.8%) would become unprofitable at around 1.29M LINK borrowed, corresponding to approximately 21.5% utilization, which is far below the optimal rate of 45%.\n\nFor comparison:\n\nETH parameters make looping strategies unprofitable only around an optimal utilization rate of ~92%, while ETH borrowing rates barely reach ~3%.\n\nWhile i fully acknowledge that LINK is not ETH, and that parameters must differ to reflect the specific risk profile of each asset, it appears concerning that:\n\nAll current LINK borrowers would be significantly impacted\n\nwstLINK looping strategies become extremely risky, and not efficient as stated by llama above.\n\nIs it possible that Native asset APR, optimal utilization rate, and interest rate parameters are not seem properly aligned ?\n\n3 Likes\n\nzouizoui\n\nFebruary 18, 2026, 3:32pm\n\n15\n\nNow that v3.6 seems to be running, Could we also have some news from bgd labs technical analysis ?\n\n1 Like\n\nzouizoui\n\nApril 2, 2026, 6:31am\n\n16\n\nHello guys, seems like i’m the only one alive around here..\n\nNow that bgd and aci left aave, what will happen with this proposal ?\n\n1 Like\n\npuskas\n\nOctober 4, 2026, 11:36am\n\n17\n\nIs there any update? @stani @LlamaRisk @TokenLogic @AaveLabs\n\n1 Like\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[TEMP-CHECK] Onboard wstLINK to Aave v3 Core Instance\n\nNew Asset\n\n8\n\n1813\n\nMay 26, 2025\n\n[ARFC] Revision of ETH & BTC Collateral Efficiency on Aave\n\nGeneral\n\n2\n\n255\n\nSeptember 21, 2026\n\nAreta Delegate Platform\n\nDelegate Platforms\n\n581\n\n13352\n\nAugust 10, 2026\n\n[ARFC] Low Adoption Asset Deprecation on Aave V3\n\nGovernance\n\n9\n\n2134\n\nSeptember 16, 2026\n\nTokenLogic Delegate Platform\n\nDelegate Platforms\n\n38\n\n6668\n\nOctober 4, 2026","tokens":15700,"crawled_at":1791192329593}
 {"id":10095,"url":"https://hyperliquid.gitbook.io/hyperliquid-docs/historical-data","domain":"hyperliquid.gitbook.io","chapter":"defi_protocols","title":"Historical data | Hyperliquid Docs","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nExporting additional user trade history\nThe Enigma team has built an interface for users to export trade history https://trade-export.hypedexer.com/?v=1. This is a third-party integration that is independently maintained. Any issues or feedback should be reported directly to the maintainers.\nMarket Data (for advanced users)\nThe examples below use the AWS CLI (see https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html) and LZ4 (https://github.com/lz4/lz4 or install from your package manager).\nNote that the requester of the data must pay for transfer costs.\nAsset data\nHistorical data is uploaded to the bucket hyperliquid-archive approximately once a month. There is no guarantee of timely updates and data may be missing.\nL2 book snapshots are available in market_data and asset contexts are available in asset_ctxs. No other historical data sets are provided via S3 (e.g. candles or spot asset data). You can use the API to record additional historical data sets yourself.\nFormat: s3://hyperliquid-archive/market_data/[date]/[hour]/[datatype]/[coin].lz4 or s3://hyperliquid-archive/asset_ctxs/[date].csv.lz4\n\naws s3 cp s3://hyperliquid-archive/market_data/20230916/9/l2Book/SOL.lz4 /tmp/SOL.lz4 --request-payer requester\nunlz4 --rm /tmp/SOL.lz4\nhead /tmp/SOL\n\nTrade data\ns3://hl-mainnet-node-data/node_fills_by_block has fills which are streamed via --write-fills --batch-by-block from a non-validating node. Older data is in a different format at s3://hl-mainnet-node-data/node_fills) and s3://hl-mainnet-node-data/node_trades . node_fills matches the API format, while node_trades does not.\nHistorical node data\ns3://hl-mainnet-node-data/explorer_blocks and s3://hl-mainnet-node-data/replica_cmds contain historical explorer blocks and L1 transactions.\ns3://hl-mainnet-node-data/misc_events_by_block contains non-trade events such as transfers, staking, and funding.\n\nPreviousPoints\nNextBug bounty program\n\nLast updated 4 months ago","tokens":515,"crawled_at":1791192339288}
 {"id":10096,"url":"https://www.metaplex.com/docs/smart-contracts/core/update","domain":"www.metaplex.com","chapter":"docs","title":"Updating Assets | Metaplex Core","text":"This guide shows how to update Core Asset metadata on Solana using the Metaplex Core SDK. Modify the name, URI, or collection membership of Assets you control.\nWhat You'll Learn\nUpdate Asset name and metadata URI\nAdd a standalone Asset to a Collection\nMove an Asset between Collections or remove it from a Collection\nMake an Asset immutable (permanent)\n\nSummary\nUpdate a Core Asset's metadata using the update instruction. Only the update authority (or an authorized delegate) can modify an Asset.\nChange name and uri to update metadata\nUse newCollection and newUpdateAuthority to add, move, or remove Assets from Collections\nSet updateAuthority to None to make immutable\nUpdates are free (no rent cost) unless changing account size\nOut of Scope\nUpdating Token Metadata NFTs (use mpl-token-metadata), plugin modifications (see Plugins), and ownership transfers (see Transferring Assets).\nQuick Start\nJump to: Update Asset · Add to Collection · Change Collection · Remove from Collection · Make Immutable\nInstall: npm install @metaplex-foundation/mpl-core @metaplex-foundation/umi\nFetch the Asset to get current state\nCall update(umi, { asset, name, uri }) with new values\nVerify changes with fetchAsset()\nPrerequisites\nUmi configured with a signer that is the Asset's update authority\nAsset address of the Asset to update\nNew metadata uploaded to Arweave/IPFS (if changing URI) The update authority or delegate of a Core Asset has the ability to change some of the Asset's data.\n\nUpdating a Core Asset\nHere is how you can use our SDKs to update an MPL Core Asset.\n\n1import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n2import { update } from '@metaplex-foundation/mpl-core'\n\n3import { mplCore } from '@metaplex-foundation/mpl-core'\n\n4import { publicKey } from '@metaplex-foundation/umi'\n\n5\n\n6const umi = createUmi('https://api.devnet.solana.com').use(mplCore())\n\n7const assetAddress = publicKey('AssetAddressHere...')\n\n8\n\n9// Update an existing NFT asset's metadata\n\n10const result = await update(umi, {\n\n11 asset: assetAddress,\n\n12 name: 'Updated NFT Name',\n\n13 uri: 'https://updated-example.com/metadata.json',\n\n14}).sendAndConfirm(umi)\n\n15\n\n16console.log('Asset updated successfully')\n\nAdd an Asset to a Collection\nThe update instruction can add a standalone Asset to a Collection by setting newCollection to the target Collection address and newUpdateAuthority to the Collection type. The caller must be the update authority of both the Asset and the target Collection.\n\n1import { publicKey } from '@metaplex-foundation/umi'\n\n2import {\n\n3 update,\n\n4 fetchAsset,\n\n5 fetchCollection,\n\n6 updateAuthority,\n\n7} from '@metaplex-foundation/mpl-core'\n\n8\n\n9const assetId = publicKey('11111111111111111111111111111111')\n\n10const collectionId = publicKey('22222222222222222222222222222222')\n\n11\n\n12const asset = await fetchAsset(umi, assetId)\n\n13const collection = await fetchCollection(umi, collectionId)\n\n14\n\n15// Assumes the asset is standalone. If it already belongs to a collection,\n\n16// fetch that current collection and pass it as the `collection` parameter\n\n17// alongside `newCollection` (see change-collection example); otherwise the\n\n18// instruction will fail.\n\n19await update(umi, {\n\n20 asset,\n\n21 newCollection: collection.publicKey,\n\n22 newUpdateAuthority: updateAuthority('Collection', [collection.publicKey]),\n\n23}).sendAndConfirm(umi)\n\n24\n\n25console.log('Asset added to collection')\n\n1# Add a standalone asset to a collection\n\n2mplx core asset update <assetId> --collection <collectionId>\n\n3\n\n4# Or use the convenience alias\n\n5mplx core collection add <collectionId> <assetId>\n\nYou can also add an Asset to a Collection using the Metaplex CLI: mplx core collection add <collectionId> <assetId>\n\nChange the Collection of a Core Asset\nThe update instruction can move an Asset from one Collection to another.\n\n1import { publicKey } from '@metaplex-foundation/umi'\n\n2import {\n\n3 update,\n\n4 fetchAsset,\n\n5 fetchCollection,\n\n6 collectionAddress,\n\n7 updateAuthority,\n\n8} from '@metaplex-foundation/mpl-core'\n\n9\n\n10const assetId = publicKey('11111111111111111111111111111111')\n\n11const newCollectionId = publicKey('22222222222222222222222222222222')\n\n12\n\n13const asset = await fetchAsset(umi, assetId)\n\n14\n\n15const currentCollectionId = collectionAddress(asset)\n\n16if (!currentCollectionId) {\n\n17 throw new Error('Asset does not belong to a collection')\n\n18}\n\n19const currentCollection = await fetchCollection(umi, currentCollectionId)\n\n20\n\n21await update(umi, {\n\n22 asset,\n\n23 collection: currentCollection,\n\n24 newCollection: newCollectionId,\n\n25 newUpdateAuthority: updateAuthority('Collection', [newCollectionId]),\n\n26}).sendAndConfirm(umi)\n\n27\n\n28console.log('Asset moved to new collection')\n\n1# Move an asset from its current collection to a different one\n\n2mplx core asset update <assetId> --collection <newCollectionId>\n\nRemove an Asset from a Collection\nThe update instruction can remove an Asset from its current Collection by changing the newUpdateAuthority from Collection to Address. This makes the Asset standalone again, with your wallet as its direct update authority.\n\n1import { publicKey } from '@metaplex-foundation/umi'\n\n2import {\n\n3 update,\n\n4 fetchAsset,\n\n5 fetchCollection,\n\n6 collectionAddress,\n\n7 updateAuthority,\n\n8} from '@metaplex-foundation/mpl-core'\n\n9\n\n10const assetId = publicKey('11111111111111111111111111111111')\n\n11\n\n12const asset = await fetchAsset(umi, assetId)\n\n13\n\n14const currentCollectionId = collectionAddress(asset)\n\n15if (!currentCollectionId) {\n\n16 throw new Error('Asset does not belong to a collection')\n\n17}\n\n18const collection = await fetchCollection(umi, currentCollectionId)\n\n19\n\n20await update(umi, {\n\n21 asset,\n\n22 collection,\n\n23 newUpdateAuthority: updateAuthority('Address', [umi.identity.publicKey]),\n\n24}).sendAndConfirm(umi)\n\n25\n\n26console.log('Asset removed from collection')\n\n1# Remove an asset from its current collection\n\n2mplx core asset update <assetId> --remove-collection\n\nAfter removal, the Asset's update authority becomes the address you specified (typically your wallet). The Asset is no longer subject to any collection-level plugins.\n\nYou can also manage collection membership using the Metaplex CLI: mplx core asset update <assetId> --remove-collection\n\nMaking a Core Asset Data Immutable\nHere is how you can use our SDKs to make a Core Asset fully immutable. Be aware that there are different levels of immutability described in the immutability Guide.\nImportant\nThis is a destructive action and will remove the ability to update the asset. It will also remove the asset from any collections it was in. To make collection assets immutable you will need to change the update authority of the collection.\n\nMake a Core Asset Immutable\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { update, fetchAsset } from '@metaplex-foundation/mpl-core'\n\nconst assetId = publicKey('11111111111111111111111111111111')\n\nconst asset = await fetchAsset(umi, asset)\n\nawait update(umi, {\n\nasset: asset,\n\nnewUpdateAuthority: updateAuthority('None'),\n\n}).sendAndConfirm(umi)\n\nCommon Errors\nAuthority mismatch\nYou're not the update authority of the Asset. Check:\nconst asset = await fetchAsset(umi, assetAddress)\n\nconsole.log(asset.updateAuthority) // Must match your signer\n\nCollection authority required\nWhen changing Collections, you need authority on both the Asset and the target Collection.\nAsset is immutable\nThe Asset's update authority is set to None. This cannot be reversed.\nNotes\nFetch the Asset before updating to ensure you have the current state\nOnly the update authority (or delegate) can update an Asset\nMaking an Asset immutable is permanent and irreversible\nAdding, moving, or removing Collection membership changes which plugins (royalties, etc.) apply to the Asset\nRemoving an Asset from a Collection changes its update authority from the Collection to a wallet address\nAdding an Asset to a Collection changes its update authority from a wallet address to the Collection\nUpdates don't change the Asset's owner\nQuick Reference\nUpdate Parameters\nParameterDescription\nasset\nThe Asset to update (address or fetched object)\n\nname\nNew name for the Asset\n\nuri\nNew metadata URI\n\nnewCollection\nTarget Collection address\n\nnewUpdateAuthority\nNew authority (or None for immutable)\n\nAuthority Types\nTypeDescription\nAddress\nA specific public key\n\nCollection\nThe Collection's update authority\n\nNone\nImmutable - no updates allowed\n\nFAQ\nCan I undo making an Asset immutable?\nNo. Setting the update authority to None is permanent. The Asset's name, URI, and collection membership are frozen forever. Only do this when you're certain.\nHow do I update only the name without changing the URI?\nPass only the fields you want to change. Omit uri to keep the current value:\nawait update(umi, { asset, name: 'New Name' }).sendAndConfirm(umi)\n\nWhat's the difference between updating and transferring?\nUpdate changes the Asset's metadata (name, URI). Transfer changes ownership. They're separate operations with different authority requirements.\nCan a delegate update an Asset?\nYes, if they have been assigned as an Update Delegate via the Update Delegate plugin.\nDoes updating cost SOL?\nUpdates are free unless the new data is larger than the current account size (rare). The transaction fee (~0.000005 SOL) still applies.\nCan I add a standalone Asset to a Collection after creation?\nYes. Use the update instruction with newCollection and set newUpdateAuthority to the Collection type. You need authority on both the Asset and the target Collection. See Add an Asset to a Collection.\nCan I remove an Asset from a Collection?\nYes. Use the update instruction and set newUpdateAuthority to updateAuthority('Address', [yourWallet]). This detaches the Asset from the Collection and makes it standalone again. See Remove an Asset from a Collection.\nGlossary\nTermDefinition\nUpdate Authority\nThe account authorized to modify an Asset's metadata\n\nImmutable\nAn Asset that cannot be updated (update authority is None)\n\nURI\nThe URL pointing to off-chain metadata JSON\n\nDelegate\nAn account granted specific permissions via a plugin\n\nCollection Membership\nThe Collection an Asset belongs to","tokens":2540,"crawled_at":1791192371684}
@@ -109,7 +109,7 @@
 {"id":10109,"url":"https://www.metaplex.com/docs/nfts/update-nft","domain":"www.metaplex.com","chapter":"docs","title":"Update an NFT | NFTs","text":"Update your NFT's name and metadata as the update authority.\nUpdate an NFT\nIn the following section you can find a full code example and the parameters that you might need to change. You can learn more about updating NFTs in the Core documentation.\n\n1import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n2import { update } from '@metaplex-foundation/mpl-core'\n\n3import { mplCore } from '@metaplex-foundation/mpl-core'\n\n4import { publicKey } from '@metaplex-foundation/umi'\n\n5\n\n6const umi = createUmi('https://api.devnet.solana.com').use(mplCore())\n\n7const assetAddress = publicKey('AssetAddressHere...')\n\n8\n\n9// Update an existing NFT asset's metadata\n\n10const result = await update(umi, {\n\n11 asset: assetAddress,\n\n12 name: 'Updated NFT Name',\n\n13 uri: 'https://updated-example.com/metadata.json',\n\n14}).sendAndConfirm(umi)\n\n15\n\n16console.log('Asset updated successfully')\n\n1# Update name and URI\n\n2mplx core asset update <assetId> --name \"Updated Asset\" --uri \"https://example.com/metadata.json\"\n\n3\n\n4# Update with a JSON metadata file\n\n5mplx core asset update <assetId> --offchain ./asset/metadata.json\n\n6\n\n7# Update with a new image\n\n8mplx core asset update <assetId> --image ./asset/image.jpg\n\n9\n\n10# Update with JSON metadata and image\n\n11mplx core asset update <assetId> --offchain ./asset/metadata.json --image ./asset/image.jpg\n\nParameters\nCustomize these parameters for your update:\nParameterDescription\nassetAddress\nThe public key of the NFT to update\n\nname\nNew name for the NFT (optional)\n\nuri\nNew metadata URI (optional)\n\nHow It Works\nThe update process involves three steps:\nFetch the NFT - Get the current NFT data using fetchAsset\nPrepare update - Specify the new name or URI you want to change\nSend update - Execute the update transaction\nOnly the update authority of the NFT can modify it. If the NFT is part of a collection and uses collection authority, you need to be the collection's update authority.","tokens":485,"crawled_at":1791192468722}
 {"id":10110,"url":"https://governance.aave.com/t/horizon-weekly-highlights/23078","domain":"governance.aave.com","chapter":"governance_daos","title":"Horizon Weekly Highlights - Horizon - Aave","text":"Horizon Weekly Highlights\n\nHorizon\n\nLlamaRisk\n\nSeptember 5, 2025, 2:53pm\n\n1\n\nIt has been one week since the Aave Horizon launch. LlamaRisk collaborated with the Horizon team on pre-launch due diligence for assets, creating an RWA risk framework and establishing parameterization, including bounded NAV feeds. Our ongoing scope includes recommending operational parameters, monitoring the system, and providing advisory services. The following is a summary of the first week of operations.\n\nHighlights\n\nTVL has surpassed $80 million, with stablecoin deposits accounting for approximately $50 million. RLUSD is the largest supplied asset, reaching its $40 million cap at one point—a limit raised twice (from $25M to $30M, then to $40M) to meet strong demand fueled by a rewards campaign managed through Merkl. In contrast, USDC supply appears to be driven by bootstrap capital and organic demand.\n\nTotal borrows have exceeded $16.5 million, primarily driven by Superstate’s Crypto Carry Fund (USCC). To accommodate significant deposits into USCC, the Horizon Operation Multisig increased its supply cap twice. Horizon now holds approximately 7.5% of all USCC onchain supply. As projected, market growth is currently constrained by the RWA supply side, which is limited to a select, whitelisted group of institutional and accredited investors.\n\nThe GHO facilitator, which is capped at $1 million and does not permit external GHO deposits, has seen no utilization so far. This lack of activity is attributed to its comparatively high borrow rate relative to other available stablecoins on the platform. We expect usage to change as the bootstrapping period continues and some users elect to mint GHO to benefit from yield farming strategies (e.g., sGHO yielding over 8% APY).\n\nDespite attractive liquidity and low stablecoin borrowing costs, no significant leverage looping or yield farming has been observed. This is expected as users acclimate to the protocol. A key technical factor limiting such strategies is that not all RWA assets onboarded support instant minting and redemption, which prevents one-click leverage via flashloans. An ecosystem of tools and integrators (e.g., vaults, helper contracts) will develop around this use case as profitability increases and the protocol matures beyond its initial phase of conservative LTVs and supply caps.\n\nimage1266×834 71.1 KB\n\nSource: Horizon RWA Market - 14:00 UTC, September 5, 2025\n\nUtilization report\n\nCurrent RWA suppliers (13 wallets) choose to maintain relatively high health factors, despite a conservative buffer between LTV and liquidation thresholds and a bounded NAV oracle that safeguards against faulty price updates. This is expected as users take some time to acclimate to the protocol.\n\nIn our research, we note 3 primary use cases for the Horizon market:\n\nInstant Institutional Credit: Access immediate working capital by borrowing against tokenized assets, avoiding issuer redemption delays and fees.\n\nLeveraged Carry Trades: Execute a carry trade by borrowing stablecoins against yield-bearing RWAs, using recursive looping to scale the position and capture the basis between the borrow rate and asset yield.\n\nDeFi Yield Generation: Generate yield through two primary avenues: passively supply stablecoins to earn interest from institutional borrowing, or actively execute farming strategies like supplying an RWA to mint and stake GHO.\n\n58975384492238310251280×934 88.4 KB\n\nSource: LlamaRisk - 14:00 UTC, September 5, 2025\n\nDriven by a compelling APY of ~15.78%, USCC is the dominant RWA supplied to Horizon, with the market attracting 7.5% of its total supply in the first week. The fund generates this return via a market-neutral strategy that captures basis by shorting CME-listed futures contracts, such as SOL Future SEP25 and XRP Future SEP25, while hedging price exposure. Because this yield significantly exceeds the Treasury rates that benchmark stablecoin returns, it is a primary incentive for suppliers.\n\nimage1230×164 7.58 KB\n\nSource: Superstate, September 5, 2025\n\nParameter changes during this period\n\nHorizon supply caps were raised twice during the launch week to manage significant inflows. The key adjustments were:\n\nRLUSD: The supply cap was raised from $30m to $40m on September 4th. This cap was rapidly reached due to the current incentive campaign, but supply has since contracted slightly.\n\nUSCC: The supply cap was raised in two stages. On August 28th, it was raised from $10,6m to $14.4m, then to $40m on September 4th. Supply cap is currently sitting at 58%.\n\nSupply Side (Stablecoins)\n\nLarge influxes of RLUSD and USDC mark the stablecoin supply. GHO is capped at 1m$ via a facilitator, with no room to deposit external GHO. Its comparatively high borrowing rate compared to the other stablecoins explains its lack of current usage.\n\nimage1288×663 23.6 KB\n\nSource: Dune (@mrvega14), September 5, 2025\n\nSupply Side (RWAs)\n\nSupply growth is primarily concentrated in USCC, JAAA, and JTRSY.\n\nimage1157×609 22.6 KB\n\nSource: Dune (@mrvega14) - September 5th, 2025\n\nBorrow Side\n\nUSDC and RLUSD are borrowed in similar amounts, mainly driven by USCC-backed loans.\n\nimage1289×660 22.5 KB\n\nSource: Dune (@mrvega14) - September 5th, 2025\n\nProfitability heatmaps for leverage looping\n\nWe calculate the profitability of looping strategies for RWA tokens by comparing their underlying yields against different stablecoin borrow rates. The heatmaps illustrate how leverage alters returns: when funding costs are low, each additional loop lifts returns meaningfully, but as borrow rates rise, the benefit fades quickly and margins get squeezed.\n\nJAAA\n\nimage2757×1767 289 KB\n\nJTRSY\n\nimage2757×1767 315 KB\n\nUSTB\n\nimage2757×1767 360 KB\n\nUSCC\n\nimage2757×1767 301 KB\n\nDisclosure\n\nThis review was independently prepared by LlamaRisk, a DeFi risk service provider funded in part by the Aave DAO. LlamaRisk serves the Horizon protocol and has been engaged to conduct due diligence, parametrisation, and ongoing risk services.\n\nThe information provided should not be construed as legal, financial, tax, or professional advice.\n\n10 Likes\n\nLlamaRisk - Monthly Community Update\n\nLlamaRisk - Monthly Community Update\n\nAL Development Update | December 2025\n\nstani\n\nSeptember 5, 2025, 3:48pm\n\n2\n\nGreat analysis @LlamaRisk and very strong launch for Horizon!\n\n4 Likes\n\nLlamaRisk\n\nSeptember 12, 2025, 10:04pm\n\n3\n\nThe second week of Horizon’s operation saw Total Value Locked (TVL) surpass $100 million, the integration of USYC, and a significant increase in the supply of JTRSY.\n\nHighlights\n\nTVL surpassed $100 million, with stablecoin deposits constituting approximately $50 million. RLUSD is the largest supplied asset, reaching its previous $40 million cap before the limit was raised to $60 million to accommodate strong demand from the rewards campaign.\n\nThe USDC borrow market is now incentivized, with the base rate increased to 2.5% to maintain an attractive yield for suppliers.\n\nUSCC and JTRSY dominated Horizon’s supply. A notable transaction occurred on September 5, when a single address deposited over $26 million worth of JTRSY.\n\nTotal borrows have exceeded $20 million, driven primarily by Superstate’s Crypto Carry Fund (USCC). Horizon now holds approximately 9.10% of USCC’s and 7.9% of JTRSY’s total on-chain supplies.\n\nUSYC is now available on Horizon with a supply cap of $11.3 million. Issued by Hashnote, USYC is a tokenized U.S. Treasury bill fund tracking short-duration Treasuries, currently yielding approximately 3.79% APY.\n\nUtilization report\n\nBorrowing activity on Horizon increased significantly over the past week, with total borrowed balances growing by $5.6 million to $20.36 million. The addition of four new borrowers supported this growth.\n\nimage1920×1951 180 KB\n\nSource: LlamaRisk, September 12, 2025\n\nIncentivize Program\n\nIncentive programs on Horizon stimulate liquidity supply and borrowing activity, with active campaigns for USDC and RLUSD.\n\nUSDC: A borrowing campaign is live on Ethereum, distributing daily rewards of $1,000, translating to a fixed 3.5% APR. These incentives supplement the 7.7% protocol APY, resulting in a net borrower APY of 4.1%. This program helps balance the high utilization rate and maintain active borrow liquidity.\n\nRLUSD: Incentives are focused on lending. A campaign distributing $3,460 daily has increased the supply APR to approximately 9.5%, with a reward cap of 15%. The 25 million RLUSD tranche seeded by Ripple is not eligible for these incentives, ensuring rewards are directed to active market participants. The combined protocol yield and Merkl rewards result in a total APY of approximately 10.4%, making RLUSD one of Horizon’s most attractive supply markets up to the current $60 million cap.\n\nimage684×342 30 KB\n\nSource: Merkl, September 12, 2025\n\nParameter changes during this period\n\nHorizon’s supply caps were raised twice during the second launch week, and the base variable rate was increased once. Key adjustments include:\n\nRLUSD: The supply cap was raised from $40 million to $60 million on September 10.\n\nJTRSY: The supply cap was raised from 4.6 million ($4.96 million) to 37.1 million ($40.06 million) on September 5. This change was mainly driven by a single 21.50 million JTRSY token supply on the same day.\n\nUSDC: The supply and borrow caps were raised on September 5. The supply cap was increased from $10 million to $26 million, and the borrow cap from $14.4 million to $23.94 million. Current utilization of the supply and borrow caps is 45.38% and 43.58%, respectively. On September 10, the Base Rate was updated to 2.5% to align with the borrow-incentive program and guide utilization toward the 90% kink; other parameters remained unchanged.\n\nSupply (stablecoins)\n\nOver the past week, Horizon’s stablecoin supply remained relatively stable.\n\nimage4409×2307 436 KB\n\nSource: LlamaRisk, September 12, 2025\n\nSupply (RWAs)\n\nCollateral inflows on Horizon were primarily driven by JTRSY, which experienced a sharp increase and now represents the second-largest share of the total RWA base. This growth increased total collateral to over $60 million.\n\nimage4409×2307 408 KB\n\nSource: LlamaRisk, September 12, 2025\n\nBorrow\n\nCumulative net borrowing on Horizon increased from approximately $15 million to just over $20 million. Growth originated from both the USDC and the RLUSD markets.\n\nimage4409×2307 378 KB\n\nSource: LlamaRisk, September 12, 2025\n\nStablecoin Utilization\n\nHorizon utilization led by USDC, which climbed to and stabilized above the 80% range into mid-September. RLUSD demand increased after early September, with utilization now exceeding 25%.\n\nimage4409×2307 417 KB\n\nSource: LlamaRisk, September 12, 2025\n\nStablecoin Borrow Rates\n\nHistorical data of variable borrow rates show USDC trended higher until September 11, reaching 7.5% APY before normalizing to 3.88% APY. Meanwhile, the RLUSD rate remained around 2% APY. Starting September 9, a USDC borrow incentive reduces the effective borrower rate by 3.56%.\n\nimage1920×1078 80.3 KB\n\nSource: LlamaRisk analysis, September 12, 2025\n\nProfitability heatmaps for leverage looping\n\nOver the past week, looping profitability for most RWA assets has remained stable. The main exception is USCC, whose current yield has declined to 13.48%. In contrast, the newly onboarded USYC has expanded the available collateral set, albeit with more modest yield.\n\nUSCC\n\nimage2757×1767 293 KB\n\nUSYC\n\nimage2796×1767 399 KB\n\nDisclosure\n\nThis review was independently prepared by LlamaRisk, a DeFi risk service provider funded in part by the Aave DAO. LlamaRisk serves the Horizon protocol and has been engaged to conduct due diligence, parametrisation, and ongoing risk services.\n\nThe information provided should not be construed as legal, financial, tax, or professional advice.\n\n7 Likes\n\nLlamaRisk\n\nSeptember 19, 2025, 7:01pm\n\n4\n\nLlamaRisk Insights - 111600×900 108 KB\n\nThe third week of Horizon’s operation saw its TVL surpass $140 million, the market reached $32 million in net borrows, and surpassed $60 million in stablecoin supply.\n\nHighlights\n\nTVL surpassed $140 million, with stablecoin deposits constituting approximately $60 million. RLUSD is the largest supplied asset, with current liquidity of around $44 million.\n\nUSCC and JTRSY supplies continue growing, accounting for over 90% of Horizon RWA market share.\n\nThe Federal Reserve cut the federal funds rate by 25bps on September 17. This has a direct impact on short-term T-bill-backed assets, where yields are expected to gradually decline as the fund’s portfolio is updated with new, lower-yielding bonds\n\nRLUSD (supply) and USDC (borrow) markets continue to be incentivized.\n\nUtilization Report\n\nIn the third week following its launch, total borrowed balances on the Horizon platform increased from $20.4 million to $32.3 million, mostly driven by existing suppliers increasing or reallocating their positions.\n\nimage1617×1929 421 KB\n\nIncentivize Program\n\nIncentive programs on Horizon stimulate liquidity supply and borrowing activity, with active campaigns for USDC and RLUSD.\n\nUSDC: A borrowing campaign continues to be active on Ethereum, distributing daily rewards of $1,270, which reduces the borrowing cost by 3.5%.\n\nRLUSD: Incentives are focused on lending—a campaign distributing $3,518 daily, with a reward cap of 15%. The 25 million RLUSD tranche seeded by Ripple is not eligible for these incentives, ensuring rewards are directed to active market participants.\n\nParameter changes during this period\n\nDuring the third week, Horizon’s supply caps were raised once:\n\nUSCC: The supply cap was raised from 3.6 million ($40.2 million) to 5 million ($56.0 million) on September 17.\n\nSupply (stablecoins)\n\nThe total supply of stablecoins increased by 14.8% to $60.3 million. RLUSD accounts for the largest portion of this total supply.\n\nRLUSD: Supply increased by 14.7%, from $38.7 million to $44.4 million.\n\nUSDC: Supply increased by 25.7%, from $12.6 million to $15.9 million.\n\nimage4410×2308 416 KB\n\nSource: LlamaRisk, September 19, 2025\n\nSupply (RWAs)\n\nJTRSY and USCC primarily drove collateral inflows on Horizon. The total supply of Real World Assets (RWAs) grew to $80.2 million.\n\nThe changes in individual RWA supplies were as follows:\n\nUSCC: Supply increased by 41.4%, from $29.2 million to $41.3 million.\n\nJTRSY: Supply increased by 30.5%, from $26.1 million to $34.1 million.\n\nUSTB: Supply decreased by 20.1%, from $4.9 million to $3.9 million.\n\nJAAA: Supply decreased by 49%, from $1.5 million to $1 million.\n\nUSYC: Supply remained at zero with no assets supplied.\n\nimage4410×2308 409 KB\n\nSource: LlamaRisk, September 19, 2025\n\nBorrow\n\nTotal net borrowing on Horizon increased by 58.8% to $32.3 million. This growth was due to increased borrowing in the USDC and RLUSD markets.\n\nUSDC: Borrowing grew by 24.7%, from $9.9 million to $12.4 million.\n\nRLUSD: Borrowing grew by 91.2%, from $10.4 million to $19.9 million.\n\nimage4410×2308 347 KB\n\nSource: LlamaRisk, September 19, 2025\n\nStablecoin Utilization\n\nUtilization on Horizon continues to be led by USDC, which exceeded 90% multiple times this week. RLUSD demand increased after mid-September, with utilization now exceeding 40%.\n\nimage4410×2308 420 KB\n\nSource: LlamaRisk, September 19, 2025\n\nStablecoin Borrow Rates\n\nBorrowing dynamics continue to reflect the early bootstrapping phase. Pricing for USDC remains noticeably above peers despite incentive support, while RLUSD shows steadier but gradual increases in cost as utilization expands.\n\nimage4410×2308 470 KB\n\nSource: LlamaRisk, September 19, 2025\n\nProfitability heatmaps for leverage looping\n\nLeverage looping profitability remains unchanged across JTRSY, JAAA, and USYC, with yields holding steady at prior levels. The picture is different for USCC and USTB, where profitability has shifted - USCC now offers an elevated return of 14.87%, while USTB stands at 4.15%.\n\nUSCC\n\nYield Chart\n\nimage1231×360 27.1 KB\n\nSource: Superstate, September 19, 2025\n\nLooping Strategies\n\nimage2757×1767 290 KB\n\nSource: LlamaRisk, September 19, 2025\n\nUSTB\n\nYield Chart\n\nimage1233×363 30.1 KB\n\nSource: Superstate, September 19, 2025\n\nLooping Strategies\n\nimage2730×1767 278 KB\n\nSource: LlamaRisk, September 19, 2025\n\n6 Likes\n\nLlamaRisk\n\nSeptember 26, 2025, 7:41pm\n\n5\n\nimage1600×900 105 KB\n\nThis week, Horizon Total Value Locked (TVL) surpassed $163m, with over $40m in net borrow, and $65m in stablecoin supply.\n\nHighlights\n\nTVL surpassed $163m, with stablecoin deposits constituting approximately $64m. RLUSD is the largest supplied asset, with current liquidity around $44m.\n\nThe first borrowing activity in GHO has been observed, with a loan size of $750k GHO.\n\nLlamaRisk introduced LlamaGuard NAV Oracle, a dynamic risk-adjusted Oracle solution for tokenized RWAs built in collaboration with Chainlink.\n\nSecuritize BlackRock’s BUIDL and VanEck’s VBILL now settle instantly with [RLUSD liquidity](https://BlackRock’s BUIDL and VanEck’s VBILL now settle instantly with RLUSD liquidity.).\n\nRLUSD (supply) and USDC (borrow) markets continue to be incentivized.\n\nIncentivize Program\n\nIncentive programs on Horizon stimulate liquidity supply and borrowing activity, with active campaigns for USDC and RLUSD.\n\nUSDC: A borrowing campaign continues to be active on Ethereum, distributing daily rewards of $1,440, which reduces the borrowing cost by 3.5%.\n\nRLUSD: Incentives are focused on lending—a campaign distributing $3,518 daily, with a reward cap of 15%. The 25m RLUSD tranche seeded by Ripple is not eligible for these incentives, ensuring rewards are directed to active market participants.\n\nUtilization Report\n\nIn the fourth week following its launch, total borrowed balances on the Horizon platform increased from $32.3m to $44.1m, mostly driven by existing suppliers increasing or reallocating their positions.\n\nimage1447×1577 346 KB\n\nParameter changes during this period\n\nDuring the third week, Horizon’s risk parameters were changed on September 25:\n\nUSCC: The supply cap was raised from 5m ($56.1m) to 6m ($67.3m).\n\nRLUSD: The borrow cap was raised from 27m to 43m.\n\nSupply (stablecoins)\n\nThe total supply of stablecoins increased by 5.29% to $63.5m. RLUSD accounts for the largest portion of this total supply.\n\nRLUSD: Supply increased by 5.22%, from $44.4m to $46.7m.\n\nUSDC: Supply increased by 5.47%, from $15.9m to $16.8m.\n\nimage4410×2308 434 KB\n\nSource: LlamaRisk, September 26, 2025\n\nSupply (RWAs)\n\nUSCC primarily drove collateral inflows on Horizon. The total supply of Real World Assets (RWAs) grew to $98.8m.\n\nThe changes in individual RWA supplies were as follows:\n\nUSCC: Supply increased by 36.5%, from $41.3m to $56.4m.\n\nJTRSY: Supply hasn’t changed and currently sits at $34.1m.\n\nUSTB: Supply hasn’t changed and currently sits at $3.9m.\n\nJAAA: Supply increased by 251%, from $1 million to $3.5m.\n\nUSYC: Supply remained at zero with no assets supplied.\n\nimage4410×2308 392 KB\n\nSource: LlamaRisk, September 26, 2025\n\nBorrow\n\nTotal net borrowing on Horizon increased by 36.9% to $45.1m. This growth was due to increased borrowing in the USDC and RLUSD markets.\n\nUSDC: Net borrow grew 29.3%, from $12.4m to $16.0m.\n\nRLUSD: Net borrow grew by 42.2%, from $19.9m to $28.3m.\n\nimage4410×2308 357 KB\n\nSource: LlamaRisk, September 26, 2025\n\nStablecoin Utilization\n\nUtilization on Horizon continues to be led by USDC, which exceeded 90% multiple times this week. RLUSD demand has increased, with utilization exceeding 60%, driven primarily by a large borrower.\n\nimage4410×2308 449 KB\n\nSource: LlamaRisk, September 26, 2025\n\nStablecoin Supply Rates\n\nRLUSD suppliers benefit from elevated APYs driven by recent incentive campaigns, while USDC supply yields are sourced solely from organic borrow demand.\n\nimage4410×2308 492 KB\n\nSource: LlamaRisk, September 26, 2025\n\nStablecoin Borrow Rates\n\nUSDC borrowing rates remain stable, driven by incentive and utilization below uOptimal. In contrast, RLUSD’s borrowing costs are increasing at a measured pace as its utilization rate gradually rises.\n\nimage4410×2308 490 KB\n\nSource: LlamaRisk, September 26, 2025\n\nProfitability heatmaps for leverage looping\n\nLeverage looping profitability remains unchanged across JTRSY, JAAA, with yields holding steady at prior levels. The picture is different for USCC and USTB, where profitability has shifted - USCC now offers an elevated return of 11.2%, while USTB stands at 3.7%.\n\nUSCC\n\nimage1920×1078 86.5 KB\n\nSource: LlamaRisk analysis, September 26, 2025\n\nimage3020×1918 315 KB\n\nSource: LlamaRisk analysis, September 26, 2025\n\nUSTB\n\nimage1920×1078 90.1 KB\n\nSource: LlamaRisk, September 26, 2025\n\nimage3028×1918 373 KB\n\nSource: LlamaRisk, September 26, 2025\n\nJTRSY\n\nimage2993×1918 331 KB\n\nSource: LlamaRisk, September 26, 2025\n\n2 Likes\n\nLlamaRisk\n\nOctober 4, 2025, 12:39am\n\n6\n\nimage1600×900 107 KB\n\nThis week, Horizon’s Total Value Locked (TVL) surpassed $176m, with over $44m in net borrows, and $77m in stablecoin supply.\n\nHighlights\n\nTVL surpassed $176m, with stablecoin deposits constituting approximately $77m. RLUSD is the largest supplied asset, with current liquidity around $57.30m.\n\nThe LlamaGuard NAV Oracle has been successfully integrated into Horizon markets, providing more resilient and transparent NAV feeds for on-chain funds.\n\nAave developer toolkit now extends full support to the Horizon market, enabling protocols and integrators to build, test, and deploy strategies with seamless compatibility.\n\nRLUSD supply and USDC borrow markets continue to be incentivized.\n\nIncentivize Program\n\nIncentive programs on Horizon stimulate liquidity supply and borrowing activity, with active campaigns for USDC and RLUSD.\n\nUSDC: A borrowing campaign continues to be active on Ethereum till 7 Oct, distributing daily rewards of $1,570, which reduces the borrowing cost by 3.5%.\n\nRLUSD: Incentives remain centered on lending, with the current campaign distributing $7,043 daily in rewards, capped at 15% APY. This program runs through October 7 and now offers double the rewards compared to the prior campaign. The 25m RLUSD tranche seeded by Ripple is excluded, keeping incentives targeted to active market participants.\n\nUtilization Report\n\nIn the fifth week from its launch, total borrowed balances on the Horizon platform increased from to $44.5m, mostly driven by existing suppliers increasing or reallocating their positions.\n\nimage1452×1568 358 KB\n\nSource: LlamaRisk, October 3, 2025\n\nParameter changes during this period\n\nDuring this week no parameter changes was proposed nor executed.\n\nSupply (stablecoins)\n\nThe total supply of stablecoins increased by 5.29% to $77.72m. RLUSD accounts for the largest portion of this total supply.\n\nRLUSD: Supply increased by 22.69%, from $46.7m to $57.30m.\n\nUSDC: Supply increased by 21.54%, from $16.8m to $20.42m.\n\nimage4410×2308 460 KB\n\nSource: LlamaRisk, October 3, 2025\n\nSupply (RWAs)\n\nThe total supply of Real World Assets (RWAs) has not changed significantly and currently sits at $97.54m.\n\nimage4410×2308 401 KB\n\nSource: LlamaRisk, October 3, 2025\n\nBorrow\n\nTotal net borrowing on Horizon decreased by 1.84% to $44.58m. This growth was due to increased borrowing in the USDC and RLUSD markets.\n\nUSDC: Net borrows grew 1.8%, from $16.0m to $16.3m.\n\nRLUSD: Net borrows decreased by 2.4%, from $28.3m to $27.6m.\n\nimage4410×2308 363 KB\n\nSource: LlamaRisk, October 3, 2025\n\nStablecoin Utilization\n\nUSDC utilization remains elevated, while RLUSD saw a modest decline as supply incentives continued to attract active participation.\n\nimage4410×2308 471 KB\n\nSource: LlamaRisk, October 3, 2025\n\nStablecoin Supply Rates\n\nRLUSD suppliers are capturing higher APYs fueled by incentive programs, while USDC yields stem from organic borrowing demand, supported by market trust that helps keep utilization elevated.\n\nimage4410×2308 507 KB\n\nSource: LlamaRisk, October 3, 2025\n\nStablecoin Borrow Rates\n\nUSDC borrowing rates remain incentivized and stable. In contrast, RLUSD borrowing costs dropped below 3% and are currently at 2.70% APY.\n\nimage1920×1005 76.4 KB\n\nSource: LlamaRisk, October 3, 2025\n\nProfitability heatmaps for leverage looping\n\nLeverage looping profitability remains stable across JTRSY and JAAA with yields holding at previous levels. In contrast, USCC 30-day APY has increased to 9.2% while USTB 30-day APY is now at 4.06%.\n\nUSCC\n\nimage1920×1078 89.8 KB\n\nSource: LlamaRisk, October 3, 2025\n\nimage3059×1918 327 KB\n\nSource: LlamaRisk, October 3, 2025\n\nUSTB\n\nimage1920×1078 83.1 KB\n\nSource: LlamaRisk, October 3, 2025\n\nimage3019×1918 375 KB\n\nSource: LlamaRisk, October 3, 2025\n\nJTRSY\n\nimage2993×1918 333 KB\n\nSource: LlamaRisk, October 3, 2025\n\n1 Like\n\nLlamaRisk\n\nOctober 10, 2025, 7:58pm\n\n7\n\nimage1600×900 110 KB\n\nThis week, Horizon Total Value Locked (TVL) surpassed $200m, with over $54m in net borrows, and $93m in stablecoin supply.\n\nHighlights\n\nTVL has surpassed $204 million, with total stablecoin supply reaching $93.06 million and net borrows standing at $54.64 million. RLUSD and USCC remain the dominant supplied assets, together representing nearly 75% of overall TVL.\n\nThe supply and borrow caps for GHO were raised to 25 million and 20 million, respectively, to support the establishment and growth of the GHO market on Horizon. The GHO Facilitator deposited an additional 1 million GHO.\n\nThe incentivization programs for RLUSD supply and USDC borrow markets were renewed.\n\nIncentivize Program\n\nIncentive programs on Horizon stimulate liquidity supply and borrowing activity, with active campaigns for USDC and RLUSD.\n\nUSDC: A new borrowing campaign starts on 7 October and runs until 21 October, offering daily rewards of $1,544, effectively reducing the borrowing cost by around 3.5%.\n\nRLUSD: The new lending-focused campaign begins on 7 October and continues through 14 October, distributing $11,257 in daily rewards, capped at 15% APY. The reward pool is approximately 1.6× larger than in the previous program, further strengthening incentives for active market participants.\n\nUtilization Report\n\nIn the sixth week from its launch, total borrowed balances on the Horizon platform increased to $54.26m, mostly driven by existing suppliers increasing or reallocating their positions.\n\nimage1285×1420 207 KB\n\nSource: LlamaRisk, October 10, 2025\n\nParameter changes during this period\n\nRLUSD: The supply and borrow caps were increased to 75M and 55M, respectively, on 6 October. The adjustment coincides with the launch of the new Merkl incentive program, which has driven greater user participation and improved liquidity.\n\nUSCC: The supply cap was raised to 7.5M on 7 October to accommodate steady deposit growth, supported by stable utilization and strong collateral performance.\n\nGHO: The GHO supply and borrow caps were raised to 25M and 20M, respectively, on 10 October.\n\nSupply (stablecoins)\n\nThe total supply of stablecoins increased by 19.66% to $93.18m. RLUSD accounts for the largest portion of this total supply.\n\nRLUSD: Supply increased by 30.54%, from $57.30m to $74.80m.\n\nUSDC: Supply decreased by 10.04%, from $20.42m to $18.38m.\n\nimage4410×2308 469 KB\n\nSource: LlamaRisk, October 10, 2025\n\nSupply (RWAs)\n\nThe total supply of Real World Assets (RWAs) grew by 13.18%, reaching $110.398m. USCC primarily drove collateral inflows on Horizon, supported by consistent demand for short-duration, yield-bearing assets.\n\nThe changes in individual RWA supplies were as follows:\n\nUSCC: Supply increased by 29.52%, from $56.4m to $73.05m.\n\nJTRSY: Supply decreased by 2.78%, from $34.1m to $33.15m.\n\nUSTB: Supply decrease by 90.03%, from $3.9m to $388.76k. (driven by a large single-user withdraw)\n\nJAAA: Supply hasn’t changed and currently sits at $3.5m.\n\nUSYC: Supply remained at zero with no assets supplied.\n\nimage4410×2308 402 KB\n\nSource: LlamaRisk, October 10, 2025\n\nBorrow\n\nTotal net borrowing on Horizon increased by 21.74% to $54.64m. This growth was due to increased borrowing in the RLUSD market. The GHO and USDC markets remain untouched.\n\nUSDC: Net borrow remains the same with approximately $16.11m.\n\nRLUSD: Net borrow increase by 35.54%, from $27.60m to 37.41m.\n\nimage4410×2308 374 KB\n\nSource: LlamaRisk, October 10, 2025\n\nStablecoin Utilization\n\nUSDC utilization remains high at 87.5%, while RLUSD utilization declined, driven by the strong supply incentivize program pulling liquidity to the lending side.\n\nimage4410×2308 480 KB\n\nSource: LlamaRisk, October 10, 2025\n\nStablecoin Supply Rates\n\nThe fourth incentivizes program for RLUSD started two days ago, pushing supply yields higher as participants capture elevated APYs from ongoing reward structures. Meanwhile, USDC maintains a steady supply rate, supported by market confidence and structural stability that continue to keep utilization high.\n\nimage1920×1005 83.5 KB\n\nSource: LlamaRisk, October 10, 2025\n\nStablecoin Borrow Rates\n\nFor the following week, RLUSD borrowing rates remained relatively stable, showing brief upward spikes above 3% before settling at 2.82%. USDC rates also stayed steady overall, following a short-term increase that pushed the rate up to 4.09%.\n\nimage1920×1005 78.8 KB\n\nSource: LlamaRisk, October 10, 2025\n\nProfitability heatmaps for leverage looping\n\nYields have adjusted across all active RWA markets, reflecting broader market recalibrations. JTRSY now offers 3.65%, while JAAA has increased to 4.71%. USCC continues to outperform with a 14.39% yield, and USTB has moderated slightly to 3.79%. Overall, the changes signal shifting risk-reward dynamics across the current RWA landscape.\n\nUSCC\n\nimage1920×1078 90.3 KB\n\nSource: LlamaRisk, October 10, 2025\n\nimage3020×1918 320 KB\n\nSource: LlamaRisk, October 10, 2025\n\nUSTB\n\nimage1920×942 78.4 KB\n\nSource: LlamaRisk, October 10, 2025\n\nimage3028×1918 375 KB\n\nSource: LlamaRisk, October 10, 2025\n\nJAAA\n\nimage3020×1918 304 KB\n\nSource: LlamaRisk, October 10, 2025\n\nJTRSY\n\nimage2993×1918 363 KB\n\nSource: LlamaRisk, October 10, 2025\n\nLlamaRisk\n\nOctober 17, 2025, 7:46pm\n\n8\n\nimage1600×900 104 KB\n\nThis week, Horizon Total Value Locked (TVL) surpassed $300m, with over $75m in net borrows, and $157.35m in stablecoin supply.\n\nHighlights\n\nTVL has surpassed $301 million, with total stablecoin supply reaching $157.3 million and net borrows standing at $74.4 million. RLUSD and USCC remain the dominant supplied assets.\n\nRLUSD supplied assets climbed to $139 million, establishing it as the largest stablecoin market on Horizon.\n\nThe incentivization programs for RLUSD supply and USDC borrow markets were renewed.\n\nIncentivize Program\n\nIncentive programs on Horizon stimulate liquidity supply and borrowing activity, with active campaigns for USDC and RLUSD.\n\nUSDC: A new borrowing campaign continues to be active, offering daily rewards of $1,344, effectively reducing the borrowing cost by around 3.5%.\n\nRLUSD: The new lending-focused campaign begins on 14 October and continues through 21 October, distributing $35,839 in daily rewards, capped at 15% APY. The reward pool is approximately 3.1× larger than in the previous program, which may support further supply cap in the future.\n\nUtilization Report\n\nIn the seventh week from its launch, total borrowed balances on the Horizon platform increased to $75.87m, mostly driven by existing suppliers increasing or reallocating their positions.\n\nimage1212×1320 187 KB\n\nSource: LlamaRisk, October 17, 2025\n\nParameter changes during this period\n\nRLUSD: The supply and borrow caps were increased to 128m and 115.2m, respectively, on 14 October. The supply cap was later raised again to 139M on 16 October.\n\nUSCC: The supply cap was raised to 8.8m on 11 October to accommodate steady deposit growth, supported by stable utilization and strong collateral performance. It was later raised again to 11.8m on 16 October.\n\nSupply (stablecoins)\n\nThe total supply of stablecoins increased by 68.86% to $157.35m. RLUSD accounts for the largest portion of this total supply.\n\nRLUSD: Supply increased by 85.8%, from $74.8m to $139m.\n\nUSDC: Supply hasn’t changed and currently sits at $18.4m.\n\nGHO: Supply increase by 700% from $2m to $16m, solely driven by liquidity from GHO Facilitator.\n\nimage4410×2308 471 KB\n\nSource: LlamaRisk, October 17, 2025\n\nSupply (RWAs)\n\nThe total supply of Real World Assets (RWAs) grew by 25.59%, reaching $138.65m. USCC primarily drove collateral inflows on Horizon, supported by consistent demand for short-duration, yield-bearing assets.\n\nThe changes in individual RWA supplies were as follows:\n\nUSCC: Supply increased by 40.6%, from $73m to $102.7m.\n\nJTRSY: Supply hasn’t changed and currently sits at $33.1m.\n\nUSTB: Supply hasn’t changed and currently sits at $389k.\n\nJAAA: Supply decreased by 39.4%, from $3.5m to $2.5m.\n\nUSYC: Supply remained at zero with no assets supplied.\n\nimage4410×2308 423 KB\n\nSource: LlamaRisk, October 17, 2025\n\nBorrow\n\nTotal net borrowing on Horizon increased by 38.84% to $75.87m. This growth was due to increased borrowing in the RLUSD market. The USDC and GHO stayed untouched.\n\nUSDC: Net borrow decrease by 14.6%, from $16.11m to $14m.\n\nRLUSD: Net borrow increase by 63.2%, from $37.41m to $61m.\n\nimage4410×2308 401 KB\n\nSource: LlamaRisk, October 17, 2025\n\nStablecoin Utilization\n\nUSDC utilization fell below 80%, while RLUSD utilization continued its downturn, pressured by strong supply incentives drawing liquidity to the lending side.\n\nimage4410×2308 494 KB\n\nSource: LlamaRisk, October 17, 2025\n\nStablecoin Supply Rates\n\nThe fifth incentive program for RLUSD began three days ago, driving supply yields higher as participants capture enhanced APYs from the new reward phase. In contrast, USDC supply rate has trended lower, reflecting reduced utilization and softer market activity.\n\nimage1920×1005 82.8 KB\n\nSource: LlamaRisk, October 17, 2025\n\nStablecoin Borrow Rates\n\nFor the new week, RLUSD borrowing rates held steady around 2.4%. USDC rates stayed flat near 4.0%, maintaining a narrow spread of roughly 1.6% between the two markets.\n\nimage1920×1005 81.8 KB\n\nSource: LlamaRisk, October 17, 2025\n\nProfitability heatmaps for leverage looping\n\nRWA yields remained largely stable over the week, with most assets holding steady. The main adjustments came from USCC and USTB, now yielding 10.15% and 3.85% respectively, indicating a slight normalization in returns while broader RWA rates stayed unchanged.\n\nUSCC\n\nimage1920×1078 90.8 KB\n\nSource: LlamaRisk, October 17, 2025\n\nimage3059×1918 323 KB\n\nSource: LlamaRisk, October 17, 2025\n\nUSTB\n\nimage1920×941 80 KB\n\nSource: LlamaRisk, October 17, 2025\n\nimage3019×1918 362 KB\n\nSource: LlamaRisk, October 17, 2025\n\nLlamaRisk\n\nOctober 24, 2025, 6:53pm\n\n9\n\nimage1600×900 111 KB\n\nThis week, Horizon Total Value Locked (TVL) surpassed $370m, with over $85m in net borrows, and $207.3m in stablecoin supply.\n\nHighlights\n\nTVL has surpassed $370 million, with total stablecoin supply reaching $207.3 million and net borrows standing at $84.9 million. RLUSD and USCC remain the dominant supplied assets, mostly by active user demand for looping strategies.\n\nGHO supplied assets climbed to $49 million, establishing it as the second-largest stablecoin market on Horizon.\n\nThe incentivization programs for RLUSD supply and USDC borrow markets were renewed.\n\nIncentivize Program\n\nIncentive programs on Horizon stimulate liquidity supply and borrowing activity, with active campaigns for USDC and RLUSD.\n\nUSDC: A new borrowing campaign continues to be active, offering daily rewards of $1,283, effectively reducing the borrowing cost by around 3.5%.\n\nRLUSD: The new lending-focused campaign begins on 21 October and continues to be active, distributing $37,333 in daily rewards, capped at 15% APY.\n\nUtilization Report\n\nIn the eighth week since launch, total borrowed balances on the Horizon platform rose to $84.85m, driven by a wave of new users actively supplying and borrowing across markets.\n\nimage1296×1411 172 KB\n\nSource: LlamaRisk, October 24, 2025\n\nParameter changes during this period\n\nGHO: The supply and borrow caps were increased to 50m and 30m, respectively, on 20 October. The borrow cap was later increased to 35m on 23 October.\n\nRLUSD: The supply was increased to 139.61m with 600k RLUSD being transferred from the Horizon contract and supplied on behalf of Safe multisig on 20 October\n\nUSCC/GHO E-Mode: The USCC/GHO E-Mode parameters were changed with Loan-to-Value at 84%, Liquidation Threshold at 88% and Liquidation Bonus at 10.5%.\n\nSupply (stablecoins)\n\nThe total supply of stablecoins increased by 31.8% to $207.4m. RLUSD accounts for the largest portion of this total supply.\n\nRLUSD: Supply hasn’t changed and currently sits at $139m.\n\nUSDC: Supply increase by 1.9% from $18.4m to $18.8m.\n\nGHO: Supply increase by 212.5% from $16m to $50m, solely driven by liquidity from GHO Facilitator.\n\nimage4413×2310 501 KB\n\nSource: LlamaRisk, October 24, 2025\n\nSupply (RWAs)\n\nThe total supply of Real World Assets (RWAs) grew by 19.1%, reaching $165.1m. Despite a decline in USCC yield, the asset solely accounted for the entire growth, underscoring sustained demand for short-duration, yield-bearing collateral on Horizon.\n\nThe changes in individual RWA supplies were as follows:\n\nUSCC: Supply increased by 25.8%, from $102.7m to $129.15m.\n\nJTRSY: Supply hasn’t changed and currently sits at $33.1m.\n\nUSTB: Supply hasn’t changed and currently sits at $389k.\n\nJAAA: Supply hasn’t changed and currently sits at $2.5m.\n\nUSYC: Supply remained at zero with no assets supplied.\n\nimage4410×2308 440 KB\n\nSource: LlamaRisk, October 24, 2025\n\nBorrow\n\nTotal net borrowing on Horizon increased by 38.84% to $75.87m. This growth was due to increased borrowing in the RLUSD market. The USDC and GHO stayed untouched.\n\nUSDC: Net borrow decrease by 14.6%, from $16.11m to $14m.\n\nRLUSD: Net borrow increase by 63.2%, from $37.41m to $61m.\n\nGHO: Net borrow increased largely to 19.9m.\n\nimage4413×2310 416 KB\n\nSource: LlamaRisk, October 24, 2025\n\nStablecoin Utilization\n\nUSDC utilization held mostly stable through the week, showing minimal change. RLUSD saw a slight decline as lending incentives kept pressure on demand, while GHO utilization surged past 40%, marking a sharp rise in borrowing activity and market uptake.\n\nimage1920×1005 86.4 KB\n\nSource: LlamaRisk, October 24, 2025\n\nStablecoin Supply Rates\n\nThe sixth RLUSD incentive program launched three days ago, boosting supply yields as participants capitalize on higher APYs from the new reward phase. Meanwhile, USDC supply rates have trended lower, mirroring weaker utilization and a cooling in market demand.\n\nimage1920×1005 86.1 KB\n\nSource: LlamaRisk, October 24, 2025\n\nStablecoin Borrow Rates\n\nFor the new week, both RLUSD and USDC borrowing rates remained stable, with RLUSD at 2.07% and USDC at 3.13%, keeping the spread near 1%. A new USDC incentive program has begun, effectively reducing borrowing APYs by 3.5%.\n\nimage1920×1005 84.3 KB\n\nSource: LlamaRisk, October 24, 2025\n\nProfitability heatmaps for leverage looping\n\nRWA yields held broadly steady over the week, with most assets showing minimal movement. The main adjustments came from USCC and USTB, now yielding 8.83% and 3.68% respectively, reflecting a mild normalization in returns while overall RWA rates remained stable.\n\nUSCC\n\nimage1920×1078 89.7 KB\n\nSource: LlamaRisk, October 24, 2025\n\nimage3059×1918 343 KB\n\nSource: LlamaRisk, October 24, 2025\n\nUSTB\n\nimage1920×941 79.2 KB\n\nSource: LlamaRisk, October 24, 2025\n\nimage3028×1918 385 KB\n\nSource: LlamaRisk, October 24, 2025\n\n2 Likes\n\nLlamaRisk\n\nOctober 31, 2025, 5:21pm\n\n10\n\nimage1600×900 103 KB\n\nThis week, Horizon Total Value Locked (TVL) surpassed $459.7m, with over $91.8m in net borrows, and $227.4m in stablecoin supply.\n\nHighlights\n\nTVL has surpassed $460 million, with total stablecoin supply reaching $227.4 million and net borrows standing at $135.7 million. RLUSD and USCC remain the dominant supplied assets, mostly by active user demand for looping strategies.\n\nStablecoin markets recorded a sharp rise in net borrows, largely driven by a major GHO borrowing position against USCC collateral.\n\nThe incentivization programs for RLUSD supply and USDC borrow markets were renewed.\n\nIncentivize Program\n\nIncentive programs on Horizon stimulate liquidity supply and borrowing activity, with active campaigns for USDC and RLUSD.\n\nUSDC: A borrowing campaign continues to be active, offering daily rewards of $1,603, effectively reducing the borrowing cost by around 3.5%.\n\nRLUSD: The new lending-focused campaign has been active since October 28, distributing $37,333 in daily rewards, capped at 15% APY.\n\nUtilization Report\n\nIn the nine weeks following Horizon’s market activation, total borrowed balances expanded sharply to $135.7 million, fueled by sustained inflows of new users who began actively supplying and borrowing GHO against USCC collateral. A single address accounted for roughly half of the total GHO net borrow.\n\nimage1216×1193 156 KB\n\nSource: LlamaRisk, October 31, 2025\n\nParameter changes during this period\n\nGHO: The supply and borrow caps were increased to 70m and 50m, respectively, on October 28.\n\nUSCC: The supply cap was increased to 18.5m on October 24.\n\nSupply (stablecoins)\n\nThe total supply of stablecoins increased by 10% to $227.4m. RLUSD accounts for the largest portion of this total supply.\n\nRLUSD: Supply hasn’t changed and currently sits at $139m.\n\nUSDC: Supply increase by 1.9% from $18.4m to $18.9m.\n\nGHO: Supply increase by 38.8% from $50m to $69.4m, solely driven by liquidity from GHO Facilitator.\n\nimage1920×1005 79.5 KB\n\nSource: LlamaRisk, October 31, 2025\n\nSupply (RWAs)\n\nThe total supply of Real World Assets (RWAs) grew by 40.5%, reaching $232m. The USCC remained the sole contributor to overall platform growth, reflecting enduring institutional demand for yield-generating collateral within the Horizon ecosystem.\n\nThe changes in individual RWA supplies were as follows:\n\nUSCC: Supply increased by 51.8%, from $129.2m to $196m.\n\nJTRSY: Supply hasn’t changed and currently sits at $33.2m.\n\nUSTB: Supply hasn’t changed and currently sits at $389k.\n\nJAAA: Supply hasn’t changed and currently sits at $2.5m.\n\nUSYC: Supply remained at zero with no assets supplied.\n\nimage4413×2310 462 KB\n\nSource: LlamaRisk, October 31, 2025\n\nBorrow\n\nTotal net borrowing on Horizon increased by 78.9% to $135.9m. This growth was due to increased borrowing in the GHO market.\n\nUSDC: Net borrow increase by 19.4%, from $14m to $16.72m.\n\nRLUSD: Net borrow increase by 14.7%, from $61m to $69.97m.\n\nGHO: Net borrow increased by 146.3% from $19.9m to $49.2m.\n\nimage4412×2310 466 KB\n\nSource: LlamaRisk, October 31, 2025\n\nStablecoin Utilization\n\nUSDC and RLUSD market dynamics remained largely unchanged over the week, reflecting stable utilization and steady user activity. In contrast, the GHO market experienced a pronounced increase in engagement, with utilization climbing to 71%, signaling a strong acceleration in borrowing demand and active market adoption.\n\nimage1920×1005 90.5 KB\n\nSource: LlamaRisk, October 31, 2025\n\nStablecoin Supply Rates\n\nThe seventh RLUSD incentive program commenced this week, maintaining a supply yield of 12.68%, as the market remains capped and fully utilized. This stability reflects constrained capacity rather than new inflows, with participants continuing to capture elevated returns within a saturated RLUSD market. In contrast, USDC supply rates have trended lower, consistent with softer utilization and moderating demand conditions.\n\nimage1920×1005 87.1 KB\n\nSource: LlamaRisk, October 31, 2025\n\nStablecoin Borrow Rates\n\nFor the new week, borrowing rates across stablecoin markets held steady, with a spread of just over 1.5% between RLUSD and USDC. The GHO borrow rate remained anchored at 4.34%, reflecting consistent market pricing and liquidity conditions.\n\nProfitability heatmaps for leverage looping\n\nRWA yields remained largely unchanged over the week, with only marginal adjustments across assets. USCC now offers 9.42%, while USTB yields 3.77%, reflecting a modest upward shift in returns amid broadly stable RWA market conditions.\n\nUSCC\n\nimage1920×1078 89.4 KB\n\nSource: LlamaRisk, October 31, 2025\n\nimage3059×1918 343 KB\n\nSource: LlamaRisk, October 31, 2025\n\nUSTB\n\nimage1920×942 80.7 KB\n\nSource: LlamaRisk, October 31, 2025\n\nimage3028×1918 380 KB\n\nSource: LlamaRisk, October 31, 2025\n\n3 Likes\n\nLlamaRisk\n\nNovember 7, 2025, 6:40pm\n\n11\n\nimage1600×900 72.3 KB\n\nThis week, Horizon’s Total Value Locked (TVL) surpassed $530m, with over $172m in net borrows, and $267m in stablecoin supply.\n\nHighlights\n\nTVL has surpassed $530 million, with total stablecoin supply reaching $267 million and net borrows standing at $172 million. RLUSD and USCC remain the dominant supplied assets, mostly by active user demand for looping strategies.\n\nStablecoin markets experienced a sharp rise in net borrowing, primarily driven by a significant GHO borrowing position against USCC collateral.\n\nVanEck Treasury Fund (VBILL) has been listed as a collateral asset on Horizon. VBILL is a tokenized fund that invests in U.S. Treasury securities,\n\nThe incentivization programs for RLUSD supply and USDC borrow markets were renewed.\n\nIncentivize Program\n\nIncentive programs on Horizon stimulate liquidity supply and borrowing activity, with active campaigns for USDC and RLUSD.\n\nUSDC: A borrowing campaign remains active, offering daily rewards of $1,603, effectively reducing the borrowing cost by approximately 3.5%.\n\nRLUSD: The new lending-focused campaign has been active since November 4, distributing $42,214 in daily rewards, capped at a 15% APY.\n\nUtilization Report\n\nIn the tenth weeks following Horizon’s market activation, total borrowed balances expanded sharply to $172.53 million, fueled by sustained inflows of new users who began actively borrowing GHO against USCC collateral. A single address accounted for roughly half of the total GHO net borrow.\n\nimage1212×1392 156 KB\n\nSource: LlamaRisk, November 7, 2025\n\nParameter changes during this period\n\nGHO: The borrow caps were increased to 60m on 4 November, then was raised again up to 78m with supply cap being raised up to 80m on 7 November.\n\nRLUSD: The supply cap was raised to 164.7m on 4 November, then borrow cap was raised 148.2m on 7 November.\n\nUSDC: The supply cap was raised to 50m on 4 November.\n\nUSCC: The supply cap was increased to 23m on 4 November.\n\nVBILL: The VBILL token listed on Horizon UI with 15m Supply Cap.\n\nSupply (stablecoins)\n\nThe total supply of stablecoins increased by 17.8% to $267.9m. RLUSD accounts for the largest portion of this total supply.\n\nRLUSD: Supply increase by 18.5% from $139m to $164.7m.\n\nUSDC: Supply increase by 28.4% from $18.9m to $24.26m.\n\nGHO: Supply increase by 13.8% from $69.4m to $79m.\n\nimage4413×2310 420 KB\n\nSource: LlamaRisk, November 7, 2025\n\nSupply (RWAs)\n\nThe total supply of Real World Assets (RWAs) grew by 22.4%, reaching $283.6m. The USCC remained the sole contributor to overall platform growth, reflecting enduring institutional demand for yield-generating collateral within the Horizon ecosystem.\n\nThe changes in individual RWA supplies were as follows:\n\nUSCC: Supply increased by 21.7%, from $196m to $238.6m.\n\nJTRSY: Supply hasn’t changed and currently sits at $33.2m.\n\nUSTB: Supply hasn’t changed and currently sits at $389k.\n\nJAAA: Supply hasn’t changed and currently sits at $2.5m.\n\nUSYC: Supply remained at zero with no assets supplied.\n\nVBILL: Supply increased to $9.17m from the launch.\n\nimage4413×2310 400 KB\n\nSource: LlamaRisk, November 7, 2025\n\nBorrow\n\nTotal net borrowing on Horizon increased by 26.9% to $135.9m. This growth was due to increased borrowing in the GHO market.\n\nUSDC: Net borrow decrease by 3.8%, from $16.72m to $16.09m.\n\nRLUSD: Net borrow increase by 27.7%, from $69.9m to $89.42m.\n\nGHO: Net borrow increased by 36.9% from $49.2m to $67.4m.\n\nimage4412×2310 386 KB\n\nSource: LlamaRisk, November 7, 2025\n\nStablecoin Utilization\n\nUSDC and RLUSD market dynamics remained stable overall, although USDC utilization declined sharply following a recent increase in supply demand. In contrast, GHO utilization reached 97.42%, indicating strong demand for borrowing.\n\nimage4412×2310 485 KB\n\nSource: LlamaRisk, November 7, 2025\n\nStablecoin Supply Rates\n\nThe eighth RLUSD incentive program began this week, supporting the supply yield. Following the recent expansion in the RLUSD market capacity, reward yields have remained volatile amid shifting liquidity dynamics. Meanwhile, USDC supply rates declined further, driven by a clear drop in utilization.\n\nimage1920×1004 188 KB\n\nSource: LlamaRisk, November 7, 2025\n\nStablecoin Borrow Rates\n\nBorrowing rates across stablecoin markets remained largely unchanged, with USDC, for the first time in its history, slipping below the RLUSD rate. GHO remained to have a fixed rate of 4.34%.\n\nimage1920×1005 177 KB\n\nSource: LlamaRisk, November 7, 2025\n\nProfitability heatmaps for leverage looping\n\nRWA yields were mostly stable over the week, though USCC saw a sharp decline to 5.37%, following the drop in CME futures rates for ETH and SOL. USTB yields edged slightly lower to 3.69%, consistent with a modest adjustment in short-term treasury exposures.\n\nUSCC\n\nimage4110×2307 483 KB\n\nSource: LlamaRisk, November 7, 2025\n\nimage3020×1918 305 KB\n\nSource: LlamaRisk, November 7, 2025\n\nUSTB\n\nimage1920×941 154 KB\n\nSource: LlamaRisk, November 7, 2025\n\nimage3028×1918 382 KB\n\nSource: LlamaRisk, November 7, 2025\n\n1 Like\n\nLlamaRisk - Monthly Community Update\n\nLlamaRisk\n\nNovember 14, 2025, 5:14pm\n\n12\n\nimage1600×900 71.4 KB\n\nThis week, Horizon Total Value Locked (TVL) surpassed $557m, with over $187.9m in net borrows, and $265.5m in stablecoin supply.\n\nHighlights\n\nTVL has surpassed $550 million, with a total stablecoin supply of $266 million and net borrowings standing at $188 million. RLUSD and USCC remain the dominant supplied assets, mostly by active user demand for looping strategies.\n\nBoth the RWA and stablecoin markets showed only marginal changes this week, with no meaningful expansion across either segment.\n\nThe incentivization programs for RLUSD supply and USDC borrow markets continue to be active.\n\nIncentivize Program\n\nIncentive programs on Horizon stimulate liquidity supply and borrowing activity, with active campaigns for USDC and RLUSD.\n\nUSDC: A borrowing campaign remains active, offering daily rewards of $1,488, effectively reducing the borrowing cost by approximately 3.5%.\n\nRLUSD: The new lending-focused campaign has been active since November 4, distributing $42,214 in daily rewards, capped at a 15% APY.\n\nUtilization Report\n\nIn the eleven weeks following Horizon’s market activation, total borrowed balances expanded sharply to $187.24 million, fueled mostly by ongoing users adjusting and reallocating their positions.\n\nimage1292×1557 309 KB\n\nSource: LlamaRisk, November 14, 2025\n\nParameter changes during this period\n\nDuring this week, no parameter changes were proposed nor executed.\n\nSupply (stablecoins)\n\nStablecoin market conditions were broadly steady this week, with total supply reaching $265.5m and both GHO and RLUSD markets remaining unchanged.\n\nRLUSD: The supply hasn’t changed and currently stands at $164.7 million.\n\nUSDC: Supply decrease by 11.5% from $24.26m to $21.76m.\n\nGHO: The supply hasn’t changed and currently stands at $79m.\n\nimage4413×2309 431 KB\n\nSource: LlamaRisk, November 14, 2025\n\nSupply (RWAs)\n\nThe RWA market share showed minimal movement this week, with USCC posting a small increase that lifted total RWA supply to $291.4 million, while all other segments remained effectively unchanged.\n\nThe changes in individual RWA supplies were as follows:\n\nUSCC: Supply increased by 3.2%, from $238.6m to $246.2m.\n\nJTRSY: Supply hasn’t changed and currently stands at $33.2m.\n\nUSTB: Supply hasn’t changed and currently stands at $389k.\n\nJAAA: Supply hasn’t changed and currently sits at $2.5m.\n\nUSYC: Supply remained at zero with no assets supplied.\n\nVBILL: Supply hasn’t changed and currently stands at $9.17m.\n\nimage4413×2309 421 KB\n\nSource: LlamaRisk, November 14, 2025\n\nBorrow\n\nTotal net borrowing on Horizon increased by 26.9% to $135.9m. This growth was due to increased borrowing in the GHO and RLUSD markets.\n\nUSDC: Net borrow decrease by 3.7%, from $16.09m to $15.5m.\n\nRLUSD: Net borrow increase by 5.8%, from $89.4m to $94.6m.\n\nGHO: Net borrow increased by 14.8% from $67.4m to $77.4m.\n\nimage4412×2309 398 KB\n\nSource: LlamaRisk, November 14, 2025\n\nStablecoin Utilization\n\nDuring this week, USDC utilization dipped on November 11 due to a large repayment, but it recovered shortly afterward as market conditions stabilized. The GHO and RLUSD utilization held steady as both markets remained pinned at their respective caps.\n\nimage4412×2309 496 KB\n\nSource: LlamaRisk, November 14, 2025\n\nStablecoin Supply Rates\n\nThe eighth RLUSD incentive program remains active, helping keep RLUSD supply yields steady, while USDC supply rates also held constant this week as utilization stabilized.\n\nimage4410×2307 483 KB\n\nSource: LlamaRisk, November 14, 2025\n\nStablecoin Borrow Rates\n\nUSDC saw a brief dip in borrowing rates before reverting, while RLUSD rates remained essentially flat over the week.\n\nimage4412×2309 506 KB\n\nSource: LlamaRisk, November 14, 2025\n\nProfitability heatmaps for leverage looping\n\nRWA yields were mostly stable over the week, with USCC jumping to 8.26% and USTB ticking up to 3.74%, in line with a modest repricing in short-term Treasury exposures.\n\nUSCC\n\nimage4110×2308 488 KB\n\nSource: LlamaRisk, November 14, 2025\n\nimage3020×1918 302 KB\n\nSource: LlamaRisk, November 14, 2025\n\nUSTB\n\nimage1920×942 156 KB\n\nSource: LlamaRisk, November 14, 2025\n\nimage3028×1918 367 KB\n\nSource: LlamaRisk, November 14, 2025\n\n1 Like\n\nLlamaRisk\n\nNovember 21, 2025, 9:29pm\n\n13\n\nimage1600×900 70.4 KB\n\nThis week, Horizon Total Value Locked (TVL) surpassed $591m, with over $187.9m in net borrows, and $293.5m in stablecoin supply.\n\nHighlights\n\nTVL has surpassed $590 million, with a total stablecoin supply of $294 million and net borrowings standing at $193 million. RLUSD and USCC remain the dominant supplied assets, mostly by active user demand for looping strategies and an ongoing incentive campaign.\n\nThe incentivization programs for RLUSD supply and USDC borrow markets continue to be active.\n\nIncentivize Program\n\nIncentive programs on Horizon stimulate liquidity supply and borrowing activity, with active campaigns for USDC and RLUSD.\n\nUSDC: A new borrowing campaign has been started, offering daily rewards of $1,667, effectively reducing the borrowing cost by approximately 3.5%.\n\nRLUSD: The new lending-focused campaign has been active since November 18, distributing $40,712 in daily rewards, capped at a 15% APY.\n\nUtilization Report\n\nIn the twelve weeks following Horizon’s market activation, total borrowed balances expanded sharply to $194.3 million, fueled mostly by ongoing users adjusting and reallocating their positions and new borrowing demand against the newly launched VBILL token.\n\nimage1298×1483 182 KB\n\nSource: LlamaRisk, November 21, 2025\n\nParameter changes during this period\n\nRLUSD: The supply cap and borrow cap were raised to 191.2m and 172m on 17 November.\n\nUSCC: The supply cap was increased to 29m on 17 November.\n\nSupply (stablecoins)\n\nThe total supply of stablecoins increased by 9.6% to $293.6m, driven by continued growth in both RLUSD and USDC, while the GHO market remained unchanged.\n\nRLUSD: Supply increase by 16% from $164.7 to 191.2m.\n\nUSDC: Supply increase by 7.3% from $21.8m to $23.4m.\n\nGHO: The supply hasn’t changed and currently stands at $79m.\n\nimage4413×2309 446 KB\n\nSource: LlamaRisk, November 21, 2025\n\nSupply (RWAs)\n\nThe total supply of Real-World Assets (RWAs) grew by 6.2%, reaching $301.2 million. This week’s increase came entirely from USCC, which posted a modest uplift, while all other segments remained effectively unchanged.\n\nThe changes in individual RWA supplies were as follows:\n\nUSCC: Supply increased by 3.2%, from $246.2m to $256m.\n\nJTRSY: Supply hasn’t changed and currently stands at $33.2m.\n\nUSTB: Supply hasn’t changed and currently stands at $389k.\n\nJAAA: Supply hasn’t changed and currently sits at $2.5m.\n\nUSYC: Supply remained at zero with no assets supplied.\n\nVBILL: Supply hasn’t changed and currently stands at $9.17m.\n\nimage1280×669 85.3 KB\n\nSource: LlamaRisk, November 21, 2025\n\nBorrow\n\nTotal net borrowing on Horizon increased by 3.7% to $194.2m. This growth was due to increased borrowing in the USDC and RLUSD markets.\n\nUSDC: Net borrow increase by 12.3%, from $15.5m to $17.4m.\n\nRLUSD: Net borrow increase by 5.4%, from $94.6m to $99.7m.\n\nGHO: Net borrow hasn’t changed and currently sits at $77.2m.\n\nimage4413×2310 408 KB\n\nSource: LlamaRisk, November 21, 2025\n\nStablecoin Utilization\n\nFor this week, RLUSD and USDC utilisation levels held steady, as did GHO utilisation, which remained unchanged at 97.47%.\n\nimage4412×2310 497 KB\n\nSource: LlamaRisk, November 21, 2025\n\nStablecoin Supply Rates\n\nThe ninth RLUSD incentive program has now begun, effectively reducing RLUSD supply yields, while USDC yields remain stable as market utilisation holds steady.\n\nimage4410×2307 485 KB\n\nSource: LlamaRisk, November 21, 2025\n\nStablecoin Borrow Rates\n\nBorrow rates for both USDC and RLUSD remained steady throughout the week, exhibiting no significant shifts in pricing or utilization-driven pressure.\n\nimage4412×2310 507 KB\n\nSource: LlamaRisk, November 21, 2025\n\nProfitability heatmaps for leverage looping\n\nRWA yields moved lower over the week, with USCC slipping to 5.09% and USTB easing to 3.67%. The decline in USCC was driven primarily by weaker CME SOL futures yields, which represent its largest underlying exposure.\n\nUSCC\n\nimage4110×2307 476 KB\n\nSource: LlamaRisk, November 21, 2025\n\nimage3020×1918 323 KB\n\nSource: LlamaRisk, November 21, 2025\n\nUSTB\n\nimage1920×941 167 KB\n\nSource: LlamaRisk, November 21, 2025\n\nimage3028×1918 382 KB\n\nSource: LlamaRisk, November 21, 2025\n\n1 Like\n\n0xEulersID\n\nNovember 28, 2025, 1:05pm\n\n14\n\nDo you recompute APY continuously based on on-chain events, or do you sample from an oracle/indexer at fixed intervals? And is the displayed APY smoothed (e.g., 24h moving average) or raw?\n\nLlamaRisk\n\nNovember 28, 2025, 8:07pm\n\n15\n\nimage1920×1080 74.4 KB\n\nThis week, Horizon Total Value Locked (TVL) decreased slightly to $571.67m, with over $175.9m in net borrows, and $293.6m in stablecoin supply.\n\nHighlights\n\nTVL saw a decline in TVL $572 million, with a total stablecoin supply of $294 million and net borrowings standing at $176 million. RLUSD and USCC remain the dominant supplied assets, mostly by active user demand for looping strategies and an ongoing incentive campaign.\n\nThe incentivization programs for RLUSD supply and USDC borrow markets continue to be active.\n\nIncentivize Program\n\nIncentive programs on Horizon stimulate liquidity supply and borrowing activity, with active campaigns for USDC and RLUSD.\n\nUSDC: The borrowing campaign remains active, offering daily rewards of $1,667, which effectively reduces the borrowing cost by approximately 3.5%.\n\nRLUSD: The new lending-focused campaign has been running since November 25, distributing $33,924 in daily rewards, capped at a 15% APY.\n\nUtilization Report\n\nIn the thirteen weeks following Horizon’s market activation, total borrowed balances experienced a slight decline to $175.93m, primarily driven by two large GHO repayment transactions (1 and 2), which reduced outstanding balances.\n\nimage1221×1463 174 KB\n\nSource: LlamaRisk, November 28, 2025\n\nParameter changes during this period\n\nDuring this week, no parameter changes were proposed nor executed.\n\nSupply (stablecoins)\n\nThe total stablecoin supply held flat this week, largely because the RLUSD market has reached its cap, limiting any further expansion.\n\nRLUSD: The supply hasn’t changed and currently stands at 191.2m.\n\nUSDC: The supply hasn’t changed and currently stands at $23.2m.\n\nGHO: The supply hasn’t changed and currently stands at $79m.\n\nimage4410×2307 417 KB\n\nSource: LlamaRisk, November 28, 2025\n\nSupply (RWAs)\n\nThe total supply of Real-World Assets (RWAs) declined by 6.2%, holding $277.9 million. This week’s decline stemmed from the withdrawal of USCC positions, driven by a drop in USCC yields, while all other segments remained effectively unchanged.\n\nThe changes in individual RWA supplies were as follows:\n\nUSCC: Supply decreased by 10%, from $256m to $232.6m.\n\nJTRSY: Supply hasn’t changed and currently stands at $33.2m.\n\nUSTB: Supply hasn’t changed and currently stands at $391k.\n\nJAAA: Supply hasn’t changed and currently sits at $2.5m.\n\nUSYC: Supply remained at zero with no assets supplied.\n\nVBILL: Supply hasn’t changed and currently stands at $9.17m.\n\nimage4410×2307 394 KB\n\nSource: LlamaRisk, November 28, 2025\n\nBorrow\n\nTotal net borrowing on Horizon decreased by 9.4% to $175.9m. This decline was driven solely by a large repayment of outstanding GHO debt.\n\nUSDC: Net borrow hasn’t changed and currently stands at $17.4mn.\n\nRLUSD: The net borrow hasn’t changed and currently stands at $99.3m.\n\nGHO: Net borrow decreased by 30.29%, from $77.2m to $59.25m.\n\nimage4410×2307 375 KB\n\nSource: LlamaRisk, November 28, 2025\n\nStablecoin Utilization\n\nFor this week, RLUSD and USDC utilisation levels remained steady, while GHO utilisation experienced a sharp decline, driven by a large debt repayment, which broke away from the previously persistent peak level.\n\nimage4410×2307 429 KB\n\nSource: LlamaRisk, November 28, 2025\n\nStablecoin Supply Rates\n\nThe tenth RLUSD incentive program has now commenced, exerting downward pressure on RLUSD supply yields while USDC yields remain largely unchanged. With this campaign, the effective RLUSD supply rate has fallen below 10% for the first time.\n\nimage4410×2307 502 KB\n\nSource: LlamaRisk, November 28, 2025\n\nStablecoin Borrow Rates\n\nBorrow rates for USDC and RLUSD held steady over the week, with no notable movement in rates or indication of shifting market pressure.\n\nimage4410×2307 479 KB\n\nSource: LlamaRisk, November 28, 2025\n\nProfitability heatmaps for leverage looping\n\nRWA yields continued to decline this week, with both USCC and USTB moving lower and reaching historical lows as broader income conditions softened. The USCC now stands at 5.30%, while the USTB has eased to 3.67%.\n\nUSCC\n\nimage4110×2307 463 KB\n\nSource: LlamaRisk, November 28, 2025\n\nimage3020×1918 325 KB\n\nSource: LlamaRisk, November 28, 2025\n\nUSTB\n\nimage1920×941 167 KB\n\nSource: LlamaRisk, November 28, 2025\n\nimage3028×1918 384 KB\n\nSource: LlamaRisk, November 28, 2025\n\nneed4sneed\n\nDecember 4, 2025, 2:14am\n\n16\n\nStani fren, as the Fed continues to signal that it will continue with it’s easing cycle, how do you expect this to impact TVL growth on Horizon? Is your opinion that this would act as tailwind or headwind?\n\nLlamaRisk\n\nDecember 5, 2025, 7:51pm\n\n17\n\nimage1920×1080 75.1 KB\n\nThis week, Horizon Total Value Locked (TVL) decreased slightly to $551.96m, with over $159.1m in net borrows, and $296m in stablecoin supply.\n\nHighlights\n\nTVL saw a decline in TVL $552 million, with a total stablecoin supply of $296 million and net borrowings standing at $159 million. RLUSD and USCC remain the dominant supplied assets, driven mainly by previously opened positions and ongoing incentive programs.\n\nThe incentivization programs for RLUSD supply and USDC borrow markets continue to be active.\n\nIncentivize Program\n\nIncentive programs on Horizon stimulate liquidity supply and borrowing activity, with active campaigns for USDC and RLUSD.\n\nUSDC: The borrowing campaign remains active, offering daily rewards of $1,677, which effectively reduces the borrowing cost by approximately 3.5%.\n\nRLUSD: The lending-focused campaign remains active, distributing $27,136 in daily rewards, capped at a 15% APY.\n\nUtilization Report\n\nIn the fourteen weeks following Horizon’s market activation, total borrowed balances declined to $159.1m, primarily driven by the repayment of stablecoin borrowing positions against USCC, as USCC yields declined.\n\nimage1215×1455 178 KB\n\nSource: LlamaRisk, December 5, 2025\n\nParameter changes during this period\n\nUSDC: The supply cap and borrow cap were raised to 60m and 54m on 5 December.\n\nSupply (stablecoins)\n\nThe total stablecoin supply held flat this week, largely because both the RLUSD and GHO markets have reached their caps, limiting any further expansion.\n\nRLUSD: The supply hasn’t changed and currently stands at 191.2m.\n\nUSDC: The supply increased by 9.7% from $23.2m to $25.6m.\n\nGHO: The supply hasn’t changed and currently stands at $79.3m, controlled by the GHO Steward.\n\nimage4410×2307 422 KB\n\nSource: LlamaRisk, December 5, 2025\n\nSupply (RWAs)\n\nThe total supply of Real-World Assets (RWAs) declined by 7.9%, holding $255.9 million. The decline in supply continues to be driven solely by the closing of USCC positions in response to the drop in USCC yields.\n\nThe changes in individual RWA supplies were as follows:\n\nUSCC: Supply decreased by 9.5%, from $232.6m to $210.5m.\n\nJTRSY: Supply hasn’t changed and currently stands at $33.2m.\n\nUSTB: Supply hasn’t changed and currently stands at $391k.\n\nJAAA: Supply hasn’t changed and currently sits at $2.5m.\n\nUSYC: Supply remained at zero with no assets supplied.\n\nVBILL: Supply increased by 1.1%, from $9.17m to $9.27m\n\nimage4410×2307 390 KB\n\nSource: LlamaRisk, December 5, 2025\n\nBorrow\n\nTotal net borrowing on Horizon decreased by 9.6% to $159.1m. This decline was driven by a large repayment of user stablecoin positions against the USCC token.\n\nUSDC: Net borrow hasn’t changed and currently stands at $17.5m.\n\nRLUSD: Net borrow decreased by 7%, from $99.3m to $92.27m.\n\nGHO: Net borrow decreased by 16.8%, from $59.3m to $49.3m.\n\nimage4410×2307 380 KB\n\nSource: LlamaRisk, December 5, 2025\n\nStablecoin Utilization\n\nThis week, GHO utilization declined further due to the repayment of USCC-backed debt positions following a compression in basis yield, while RLUSD utilization remained broadly unchanged. In contrast, USDC utilisation saw a sharp increase, mainly driven by a single large borrow of 6.3m executed on 4 December.\n\nimage4410×2307 443 KB\n\nSource: LlamaRisk, December 5, 2025\n\nStablecoin Supply Rates\n\nThe eleventh incentive campaign has now begun, with the RLUSD incentive APY being reduced again. This change has decreased the RLUSD supply rate, resulting in the effective yield continuing its decline. Meanwhile, USDC rates increased due to a surge in utilization.\n\nimage1920×1004 209 KB\n\nSource: LlamaRisk, December 5, 2025\n\nStablecoin Borrow Rates\n\nOver the week, USDC and RLUSD borrowing rates were mostly steady. A large borrow caused a minor spike in USDC rates, but RLUSD saw no notable rate movement.\n\nimage4410×2307 466 KB\n\nSource: LlamaRisk, December 5, 2025\n\nProfitability heatmaps for leverage looping\n\nAfter a period of declines that pushed USCC and USTB to historical lows, both instruments have since normalized and are trading in a relatively tight range. Current indications show USCC at 5.73% and USTB at 3.68%, suggesting a stable yield environment, although there has been no significant recovery so far.\n\nUSCC\n\nimage4110×2307 473 KB\n\nSource: LlamaRisk, December 5, 2025\n\nimage3020×1918 323 KB\n\nSource: LlamaRisk, December 5, 2025\n\nUSTB\n\nimage1920×941 168 KB\n\nSource: LlamaRisk, December 5, 2025\n\nimage3028×1918 380 KB\n\nSource: LlamaRisk, December 5, 2025\n\n3 Likes\n\nLlamaRisk\n\nDecember 12, 2025, 8:58pm\n\n18\n\nimage1920×1080 77.7 KB\n\nThis week, Horizon Total Value Locked (TVL) decreased slightly to $542.15m, with over $166.27m in net borrows, and $297.7m in stablecoin supply.\n\nHighlights\n\nTVL declined to $542 million, with a total stablecoin supply of $298 million and net borrowings standing at $ 244 million. RLUSD and USCC remain the dominant supplied assets, driven mainly by previously opened positions and ongoing incentive programs.\n\nThe RWA Market experienced a complete outflow of JTRSY tokens, primarily driven by a single large supplier closing its position on 10 December.\n\nThe incentivization programs for RLUSD supply and USDC borrow markets continue to be active.\n\nAt its December 2025 meeting, the Federal Reserve cut the federal funds rate by 25 bps to a range of 3.5%–3.75%, which prompted us to adjust LlamaGuard’s dynamic bounds parameters registry.\n\nParameters for USCC, USTB, USYC, JAAA, JTRSY, and VBILL were modified to enhance efficiency, including an increase in LTV under GHO E-Mode.\n\nIncentivize Program\n\nIncentive programs on Horizon stimulate liquidity supply and borrowing activity, with active campaigns for USDC and RLUSD.\n\nUSDC: The borrowing campaign remains active, offering daily rewards of $2,043, which effectively reduces the borrowing cost by approximately 3.5%.\n\nRLUSD: The lending-focused campaign remains active, distributing $22,617 in daily rewards, capped at a 15% APY.\n\nUtilization Report\n\nIn the fifteen weeks since Horizon’s market activation, total borrowed balances have increased to $166.3m. This growth was primarily driven by the opening of new USDC borrowing positions.\n\nimage1218×1390 176 KB\n\nSource: LlamaRisk, December 12, 2025\n\nParameter changes during this period\n\nDecember 11 (tx reference)\n\nNAV Parameterization: Following the Fed rate decision, new NAV pricing parameters for USTB, USYC, and JAAA were implemented.\n\nDecember 12 (tx reference)\n\nAfter the 14-week deployment phase, Horizon is revisiting its initially conservative risk posture, which was set to prioritize safety and observe user behavior. With data now indicating a stronger market maturity, the proposed parameters are gradually increasing efficiency parameters.\n\nUSTB: The risk parameters were updated (88% LTV, 90% LT, 3% LB) and the USTB GHO E-mode category was set to 90% LTV, 92% Liquidation Threshold and 3% Liquidation Bonus.\n\nUSCC: The risk parameters were updated (85% LTV, 88% LT, 5% LB) and the USCC GHO E-mode category was set to 87% LTV, 90% Liquidation Threshold and 5% Liquidation Bonus.\n\nUSYC: The risk parameters were updated (88% LTV, 90% LT, 3.1% LB) and the USYC GHO E-mode category was set to 90% LTV, 92% Liquidation Threshold and 3.1% Liquidation Bonus.\n\nVBILL: The risk parameters were updated (88% LTV, 90% LT, 3% LB) and the VBILL GHO E-mode category was set to 90% LTV, 92% Liquidation Threshold and 3% Liquidation Bonus.\n\nJTRSY: The risk parameters were updated (86% LTV, 88% LT, 3.5% LB) and the JTRSY GHO E-mode category was set to 89% LTV, 91% Liquidation Threshold and 3.5% Liquidation Bonus.\n\nJAAA: The risk parameters were updated (81% LTV, 86% LT, 5% LB) and the JAAA GHO E-mode category was set to 88% LTV, 90% Liquidation Threshold and 5% Liquidation Bonus.\n\nSupply (stablecoins)\n\nAggregate stablecoin supply was flat this week, largely because RLUSD has hit its cap, and GHO capacity hasn’t been expanded for now.\n\nRLUSD: The supply hasn’t changed and currently stands at 191.2m.\n\nUSDC: The supply increased by 6% from $25.6m to $27.17m.\n\nGHO: The supply hasn’t changed and currently stands at $79.5m, managed by the GHO Steward.\n\nimage4410×2307 428 KB\n\nSource: LlamaRisk, December 12, 2025\n\nSupply (RWAs)\n\nThe total supply of Real-World Assets (RWAs) declined by 4.5%, holding $244.5 million. While USCC actually grew by 10%, the overall decline was driven by the withdrawal of JTRSY supply on December 10.\n\nThe changes in individual RWA supplies were as follows:\n\nUSCC: Supply decreased by 10.4%, from $210.5m to $232.3m.\n\nJTRSY: Supply remained at zero with no assets supplied.\n\nUSTB: Supply hasn’t changed and currently stands at $391k.\n\nJAAA: Supply hasn’t changed and currently sits at $2.5m.\n\nUSYC: Supply remained at zero with no assets supplied.\n\nVBILL: Supply hasn’t changed and currently sits at $9.27m\n\nimage4410×2307 397 KB\n\nSource: LlamaRisk, December 12, 2025\n\nBorrow\n\nTotal net borrowing on Horizon decreased by 4.4% to $166.3m. Net borrowing expanded, primarily due to heightened demand for USDC liquidity.\n\nUSDC: Net borrow increase by 21.9%, from $17.5m to $21.3m.\n\nRLUSD: Net borrow increase by 7%, from $92.3m to $99.73m.\n\nGHO: Net borrow decreased by 9%, from $49.3m to $45.2m.\n\nimage4410×2307 386 KB\n\nSource: LlamaRisk, December 12, 2025\n\nStablecoin Utilization\n\nThis week, utilization for both GHO and RLUSD remained largely unchanged. In contrast, USDC utilization rose significantly, driven by large borrow activity on December 9.\n\nimage4410×2307 454 KB\n\nSource: LlamaRisk, December 12, 2025\n\nStablecoin Supply Rates\n\nThe twelfth incentive campaign has now begun, with the RLUSD incentive APY continuing to be reduced. RLUSD effective yields continued their downward trend as supply rates fell. Conversely, the spike in utilization drove USDC rates higher.\n\nimage1920×1004 217 KB\n\nSource: LlamaRisk, December 12, 2025\n\nStablecoin Borrow Rates\n\nOver the week, USDC and RLUSD borrowing rates stayed broadly stable. A large USDC borrow triggered a brief uptick, while RLUSD rates remained unchanged.\n\nimage4410×2307 475 KB\n\nSource: LlamaRisk, December 12, 2025\n\nProfitability heatmaps for leverage looping\n\nYields for both USCC and USTB have stabilized, though USCC continues to experience suppressed returns. Currently, the USCC is at 5.32%, while the USTB is at 3.65%.\n\nUSCC\n\nimage4110×2307 469 KB\n\nSource: LlamaRisk, December 12, 2025\n\nimage3020×1918 326 KB\n\nSource: LlamaRisk, December 12, 2025\n\nUSTB\n\nimage1920×941 169 KB\n\nSource: LlamaRisk, December 12, 2025\n\nimage3028×1918 381 KB\n\nSource: LlamaRisk, December 12, 2025\n\n1 Like\n\nLlamaRisk\n\nDecember 19, 2025, 6:09pm\n\n19\n\nimage1920×1080 74.1 KB\n\nThis week, Horizon Total Value Locked (TVL) increased to $561.5m, with over $178.3m in net borrows, and $310.4m in stablecoin supply.\n\nHighlights\n\nTVL has increased to $562 million, with a total stablecoin supply of $310 million and net borrowings standing at $178 million. RLUSD and USCC remain the dominant supplied assets, driven mainly by previously opened positions and ongoing incentive programs.\n\nThe updated parameters have already been noticed by some users (e.g., via new supply → borrow transactions), confirming the new settings are functioning as intended.\n\nThe incentivization programs for RLUSD supply and USDC borrow markets continue to be active.\n\nIncentivize Program\n\nIncentive programs on Horizon stimulate liquidity supply and borrowing activity, with active campaigns for USDC and RLUSD.\n\nUSDC: The borrowing campaign remains active, offering daily rewards of $2,282, which effectively reduces the borrowing cost by approximately 3.5%.\n\nRLUSD: The new lending-focused campaign has begun, distributing $24,876 in daily rewards, capped at a 15% APY.\n\nUtilization Report\n\nIn the sixteen weeks following Horizon’s market activation, total borrowed balances increased to $178.3m, driven by new borrowing parameters that boosted stablecoin borrowing demand. USCC remained the dominant supply asset used as collateral to borrow against.\n\nimage1157×1058 83 KB\n\nSource: LlamaRisk, December 19, 2025\n\nParameter changes during this period\n\nRLUSD: The supply cap was raised to 201.5m on 16 December.\n\nSupply (stablecoins)\n\nThe total stablecoin supply on Horizon increased by 4.2% to $310.4m, growth driven by a rise in the supply of both RLUSD and USDC. This growth followed an increase in the supply cap for RLUSD and changes in protocol parameters last week that stimulated market participation.\n\nRLUSD: The supply increased by 5.4% from $191.2m to $201.5m.\n\nUSDC: The supply increased by 9.7% from $25.6m to $29.5m.\n\nGHO: The supply hasn’t changed and currently stands at $79.4m, managed by the GHO Steward.\n\nimage4410×2307 443 KB\n\nSource: LlamaRisk, December 19, 2025\n\nSupply (RWAs)\n\nThe total supply of Real-World Assets (RWAs) increased by 2.7%, holding $251.1 million. The increase in supply was driven solely by the expansion of USCC positions, while supply across other assets was broadly unchanged to modestly lower.\n\nThe changes in individual RWA supplies were as follows:\n\nUSCC: Supply decreased by 9.5%, from $210.5m to $240.6m.\n\nJTRSY: Supply remained at zero with no assets supplied.\n\nUSTB: Supply hasn’t changed and currently stands at $392.5k.\n\nJAAA: Supply hasn’t changed and currently sits at $2.5m.\n\nUSYC: Supply remained at zero with no assets supplied.\n\nVBILL: Supply decreased by 18%, from $9.27m to $7.6m\n\nimage4410×2307 426 KB\n\nSource: LlamaRisk, December 19, 2025\n\nBorrow\n\nTotal net borrowing on Horizon increased by 7.2% to $178.3m, driven by higher borrowing parameters that boosted demand for USDC liquidity.\n\nUSDC: Net borrow increase by 12.3%, from $21.3m to $23.9m.\n\nRLUSD: Net borrow increase by 9.5%, from $99.7m to $109.2m.\n\nGHO: Net borrow hasn’t changed and currently sits at $45.2m.\n\nimage4410×2307 417 KB\n\nSource: LlamaRisk, December 19, 2025\n\nStablecoin Utilization\n\nThis week, GHO utilization remained largely unchanged, while RLUSD utilization remained mostly flat. USDC utilisation edged higher, reflecting a modest uptick in borrowing demand.\n\nimage4410×2307 486 KB\n\nSource: LlamaRisk, December 19, 2025\n\nStablecoin Supply Rates\n\nThe thirteenth incentive campaign is now underway, with RLUSD incentive APY continuing to decrease. We observed a brief decline in RLUSD APY, resulting from a delay in activating the incentive campaign. Meanwhile, USDC rates remained broadly stable.\n\nimage1920×1004 247 KB\n\nSource: LlamaRisk, December 19, 2025\n\nStablecoin Borrow Rates\n\nUSDC and RLUSD borrowing rates remained steady over the week, exhibiting limited volatility and no discernible trend.\n\nimage1920×1004 225 KB\n\nSource: LlamaRisk, December 19, 2025\n\nProfitability heatmaps for leverage looping\n\nUSCC and USTB yields have remained relatively stable, continuing to trade within a narrow range. USCC yields fell and now sit at 4.8%, while USTB remains stable at 3.68%, keeping the broader yield backdrop relatively steady.\n\nUSCC\n\nimage4110×2307 456 KB\n\nSource: LlamaRisk, December 19, 2025\n\nimage3020×1918 316 KB\n\nSource: LlamaRisk, December 19, 2025\n\nUSTB\n\nimage1920×941 169 KB\n\nSource: LlamaRisk, December 19, 2025\n\nimage3028×1918 381 KB\n\nSource: LlamaRisk, December 19, 2025\n\n1 Like\n\nLlamaRisk - Monthly Community Update\n\nLlamaRisk\n\nJanuary 2, 2026, 8:45pm\n\n20\n\nimage1920×1080 79.7 KB\n\nThese past two weeks, Horizon’s TVL increased to $589.6M, with over $198.7M in net borrows, and $314M in stablecoin supply.\n\nHighlights\n\nTVL has increased to $589 million, with a total stablecoin supply of $314 million and net borrowings standing at $198.7 million. RLUSD and USCC remain the dominant supplied assets, contributed mainly by previously opened positions and ongoing incentive programs.\n\nThe incentivization programs for RLUSD supply and USDC borrow markets continue to be active.\n\nOverall Horizon market activity remained low as most participants were away for the New Year holidays.\n\nIncentive Programs\n\nIncentive programs on Horizon stimulate liquidity supply and borrowing activity, with active campaigns for USDC and RLUSD.\n\nUSDC: The borrowing campaign remains active, offering daily rewards of $2,282, which effectively reduces the borrowing cost by approximately 3.5%.\n\nRLUSD: The new lending-focused campaign has began, distributing $24,877 in daily rewards, capped at a 15% APY and currently add a 5.17% reward.\n\nUtilization Report\n\nIn the eighteen weeks following Horizon’s market activation, total borrowed balances sits at $198.7M, driven by existing users shuffling their positions to take advantage of the recently changed collateral efficiency parameters. Overall market activity remains low due to the holidays.\n\nimage1324×1412 165 KB\n\nSource: LlamaRisk, January 2, 2026\n\nParameter changes during this period\n\nDuring this week, no parameter changes were proposed nor executed.\n\nSupply (stablecoins)\n\nThe total stablecoin supply on Horizon increased by 0.9% to $314M, growth was driven solely by USDC supply activity. USDC supply increased minimally due to the New Year holidays, while RLUSD hit its supply cap.\n\nRLUSD: The supply hasn’t changed and currently stands at $201.5M.\n\nUSDC: The supply increased by 11.8% from $29.5M to $33M.\n\nGHO: The supply hasn’t changed and currently stands at $79.4M, managed by the GHO Stewards.\n\nimage4410×2309 450 KB\n\nSource: LlamaRisk, January 2, 2026\n\nSupply (RWAs)\n\nThe total supply of RWAs increased by 5.2%, holding $266.4 million. The increase in supply was driven solely by the expansion of USCC positions, while supply across other assets remained unchanged. Overall growth over the past two weeks remained marginal, constrained by the holiday period.\n\nThe changes in individual RWA supplies were as follows:\n\nUSCC: Supply increased by 10.6%, from $240.6M to $266.3M.\n\nJTRSY: Supply remained at zero with no assets supplied.\n\nUSTB: Supply hasn’t changed and currently stands at $393k.\n\nJAAA: Supply hasn’t changed and currently sits at $2.53M.\n\nUSYC: Supply remained at zero with no assets supplied.\n\nVBILL: Supply decreased by 18.8%, from $7.6M to $6.4M\n\nimage4410×2309 423 KB\n\nSource: LlamaRisk, January 2, 2026\n\nBorrow\n\nTotal net borrowing on Horizon increased by 8.3% to $198.7M, the past two weeks saw minimal activity for RLUSD and USDC as markets remained passive during the New Year period.\n\nUSDC: Net borrows increased by 9%, from $23.9M to $26.07M.\n\nRLUSD: Net borrows increased by 15.6%, from $109.2M to $126.3M.\n\nGHO: Net borrows haven’t changed and currently sit at $45.3M.\n\nimage4410×2309 422 KB\n\nSource: LlamaRisk, January 2, 2026\n\nStablecoin Utilization\n\nDuring the past two weeks, GHO and RLUSD utilization remained flat, while USDC saw a minor growth in utilization.\n\nimage4410×2309 492 KB\n\nSource: LlamaRisk, January 2, 2026\n\nStablecoin Supply Rates\n\nThe thirteenth incentive campaign remains active, with RLUSD incentive APY continuing to decrease. Over the past two weeks, supply APY for both RLUSD and USDC remained stable, as overall market activity was minimal during the holiday period.\n\nimage1920×1005 246 KB\n\nSource: LlamaRisk, January 2, 2026\n\nStablecoin Borrow Rates\n\nUSDC and RLUSD borrowing rates held steady over the last two weeks, as rates have not been affected much with markets remaining inactive during the holidays.\n\nimage1920×1005 232 KB\n\nSource: LlamaRisk, January 2, 2026\n\nProfitability heatmaps for leverage looping\n\nOver the two-week holiday period, overall RWA yields have remained stable. USCC yields currently sit at 4.2%, while USTB remains stable at 3.66%. Following the latest parameters execution, RWA LTV levels have been updated, with leverage now reaching the maximum possible levels of 6.67x for USCC and 8.38x for USTB.\n\nUSCC\n\nimage4111×2312 497 KB\n\nSource: LlamaRisk, January 2, 2026\n\nimage3019×1918 428 KB\n\nSource: LlamaRisk, January 2, 2026\n\nUSTB\n\nimage1920×943 141 KB\n\nSource: LlamaRisk, January 2, 2026\n\nimage3068×1918 497 KB\n\nSource: LlamaRisk, January 2, 2026\n\n1 Like\n\nnext page →\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[Risk Stewards] Monad Stablecoin IRM Adjustments: Slope1 to 5.00%\n\nRisk\n\n0\n\n134\n\nSeptember 11, 2026\n\n[ARFC] Onboard HINC (Neuberger Securitize High Income Tokenized Fund) to Aave Horizon\n\nHorizon\n\n8\n\n1053\n\nSeptember 16, 2026\n\nRisk Stewards: Stablecoin IRM Changes on Aave V3 / 2026.08.27\n\nRisk\n\n0\n\n217\n\nAugust 27, 2026\n\n[Risk Stewards] August 2026 - Stablecoin Interest Rate Adjustments\n\nGovernance\n\n14\n\n1261\n\nSeptember 15, 2026\n\nHorizon Technical Maintenance Updates\n\nHorizon\n\n2\n\n167\n\nJuly 31, 2026","tokens":20770,"crawled_at":1791192469936}
 {"id":10111,"url":"https://hyperliquid.gitbook.io/hyperliquid-docs/about-hyperliquid/core-contributors","domain":"hyperliquid.gitbook.io","chapter":"defi_protocols","title":"Core contributors | Hyperliquid Docs","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nHyperliquid Labs is a core contributor supporting the growth of Hyperliquid, led by Jeff and iliensinc, who are classmates from Harvard. Other members of the team are from Caltech and MIT and previously worked at Airtable, Citadel, Hudson River Trading, and Nuro.\nThe team used to do proprietary market making in crypto in 2020 and expanded into defi in the summer of 2022. Existing platforms were plagued with issues, such as poor market design, bad tech, and clunky UX. It was easy to make money trading on these protocols, but disappointing to see how far behind defi was compared to its centralized counterparts. The team set out to build a product that could solve these issues and provide users with a seamless trading experience.\nDesigning a performant decentralized L1 with an order book DEX built-in requires an intimate understanding of quantitative trading, cutting-edge blockchain technology, and clean UX, which the team is well-positioned to deliver. The team actively engages with and listens to the community; you are welcome to join the Discord server to ask questions and share feedback.\nLastly, Hyperliquid Labs is self-funded and has not taken any external capital, which allows the team to focus on building a product they believe in without external pressure.\n\nPreviousHyperliquid 101 for non-crypto audiences\nNextOnboarding\n\nLast updated 1 year ago","tokens":366,"crawled_at":1791192477897}
-{"id":10112,"url":"https://www.metaplex.com/docs/nfts/transfer-nft","domain":"www.metaplex.com","chapter":"docs","title":"Transfer an NFT | NFTs","text":"Transfer NFT ownership between wallets on Solana.\nTransfer an NFT\nIn the following section you can find a full code example and the parameters that you might need to change. You can learn more about transferring NFTs in the Core documentation.\n\n1import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n2import { transfer } from '@metaplex-foundation/mpl-core'\n\n3import { mplCore } from '@metaplex-foundation/mpl-core'\n\n4import { publicKey } from '@metaplex-foundation/umi'\n\n5\n\n6// Initialize UMI\n\n7const umi = createUmi('https://api.devnet.solana.com')\n\n8 .use(mplCore())\n\n9\n\n10// Transfer an existing NFT asset to a new owner\n\n11const result = await transfer(umi, {\n\n12 asset: publicKey('AssetAddressHere...'),\n\n13 newOwner: publicKey('RecipientAddressHere...'),\n\n14}).sendAndConfirm(umi)\n\n15\n\n16console.log('Asset transferred:', result.signature)\n\nParameters\nCustomize these parameters for your transfer:\nParameterDescription\nassetAddress\nThe public key of the NFT to transfer\n\nnewOwner\nThe wallet address of the recipient\n\nHow It Works\nThe transfer process involves three steps:\nVerify ownership - You must be the current owner of the NFT\nSpecify recipient - Provide the new owner's wallet address\nExecute transfer - The NFT ownership is transferred immediately\nNFT Transfers\nUnlike SPL/fungible tokens, Core NFTs don't require the recipient to create a token account first. The ownership is recorded directly in the NFT, making transfers simpler and cheaper.","tokens":369,"crawled_at":1791192492585}
+{"id":10112,"url":"https://www.metaplex.com/docs/nfts/transfer-nft","domain":"www.metaplex.com","chapter":"docs","title":"Transfer an NFT | NFTs","text":"Transfer NFT ownership between wallets on Solana.\nTransfer an NFT\nIn the following section you can find a full code example and the parameters that you might need to change. You can learn more about transferring NFTs in the Core documentation.\n\n1import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n2import { transfer } from '@metaplex-foundation/mpl-core'\n\n3import { mplCore } from '@metaplex-foundation/mpl-core'\n\n4import { publicKey } from '@metaplex-foundation/umi'\n\n5\n\n6// Initialize UMI\n\n7const umi = createUmi('https://api.devnet.solana.com')\n\n8 .use(mplCore())\n\n9\n\n10// Transfer an existing NFT asset to a new owner\n\n11const result = await transfer(umi, {\n\n12 asset: publicKey('AssetAddressHere...'),\n\n13 newOwner: publicKey('RecipientAddressHere...'),\n\n14}).sendAndConfirm(umi)\n\n15\n\n16console.log('Asset transferred:', result.signature)\n\nParameters\nCustomize these parameters for your transfer:\nParameterDescription\nassetAddress\nThe public key of the NFT to transfer\n\nnewOwner\nThe wallet address of the recipient\n\nHow It Works\nThe transfer process involves three steps:\nVerify ownership - You must be the current owner of the NFT\nSpecify recipient - Provide the new owner's wallet address\nExecute transfer - The NFT ownership is transferred immediately\nNFT Transfers\nUnlike SPL/fungible tokens, Core NFTs don't require the recipient to create a token account first. The ownership is recorded directly in the NFT, making transfers simpler and cheaper.","tokens":369,"crawled_at":1791192773315}
 {"id":10113,"url":"https://docs.cosmos.network/skip-go/api-reference/error-codes","domain":"docs.cosmos.network","chapter":"layer1_layer2","title":"API Error Codes & Status Messages - Cosmos Docs","text":"This document provides a reference for the various error codes and status messages you may encounter when using Skip Go’s APIs. Understanding these codes is essential for handling API responses correctly and providing accurate feedback to users.\n​\n\nTransaction Status Codes\n\nThese codes represent the overall status of a transaction being processed or tracked by the Skip Go API.\nStatusDescriptionNotes\nSTATE_UNKNOWN\nThe status of the transaction is unknown.\nShould be treated as an error state.\n\nSTATE_SUBMITTED\nThe transaction has been submitted to the blockchain network.\n\nSTATE_PENDING\nThe transaction is in progress and waiting to be processed.\n\nSTATE_RECEIVED\nThe transaction has been received by the blockchain network.\n\nSTATE_COMPLETED\n(Internal transitional state)\nThis state is resolved to STATE_COMPLETED_SUCCESS or STATE_COMPLETED_ERROR before API response.\n\nSTATE_ABANDONED\nThe transaction was abandoned, often due to timeout (e.g., IBC relayer).\nTracking timed out. Not necessarily a permanent transaction failure; may be retriable.\n\nSTATE_COMPLETED_SUCCESS\nThe transaction has completed successfully.\nThis is the only status that definitively indicates successful end-to-end transaction completion.\n\nSTATE_COMPLETED_ERROR\nThe transaction has completed but encountered errors.\n\nSTATE_PENDING_ERROR\nThe transaction encountered errors while being processed.\n\n​\n\nGeneral Error Types\n\nThese error types provide a broad categorization of issues.\nError TypeDescription\nSTATUS_ERROR_UNKNOWN\nUnknown error type.\n\nSTATUS_ERROR_TRANSACTION_EXECUTION\nError occurred during the execution of the transaction on the blockchain.\n\nSTATUS_ERROR_INDEXING\nError occurred during Skip’s internal processing or indexing.\n\nSTATUS_ERROR_TRANSFER\nError related to a specific transfer operation within the transaction.\n\n​\n\nBridge Protocol Status Codes\n\nDifferent bridge protocols have their own specific status codes that reflect the state of a transfer leg using that bridge.\n​\n\nIBC Transfer Status\n\nStatusDescription\nTRANSFER_UNKNOWN\nThe status of the IBC transfer is unknown.\n\nTRANSFER_PENDING\nThe IBC transfer is in progress.\n\nTRANSFER_RECEIVED\nThe IBC transfer has been received by the destination chain.\n\nTRANSFER_SUCCESS\nThe IBC transfer has completed successfully.\n\nTRANSFER_FAILURE\nThe IBC transfer has failed.\n\n​\n\nAxelar Transfer Status\n\nStatusDescription\nAXELAR_TRANSFER_UNKNOWN\nThe status of the Axelar transfer is unknown.\n\nAXELAR_TRANSFER_PENDING_CONFIRMATION\nThe Axelar transfer is waiting for confirmation.\n\nAXELAR_TRANSFER_PENDING_RECEIPT\nThe Axelar transfer is waiting for receipt.\n\nAXELAR_TRANSFER_SUCCESS\nThe Axelar transfer has completed successfully.\n\nAXELAR_TRANSFER_FAILURE\nThe Axelar transfer has failed.\n\n​\n\nCCTP Transfer Status\n\nStatusDescription\nCCTP_TRANSFER_UNKNOWN\nThe status of the CCTP transfer is unknown.\n\nCCTP_TRANSFER_SENT\nThe CCTP transfer has been sent.\n\nCCTP_TRANSFER_PENDING_CONFIRMATION\nThe CCTP transfer is waiting for confirmation.\n\nCCTP_TRANSFER_CONFIRMED\nThe CCTP transfer has been confirmed.\n\nCCTP_TRANSFER_RECEIVED\nThe CCTP transfer has been received at the destination.\n\n​\n\nGoFast Transfer Status\n\nStatusDescription\nGO_FAST_TRANSFER_UNKNOWN\nThe status of the GoFast transfer is unknown.\n\nGO_FAST_TRANSFER_SENT\nThe GoFast transfer has been sent.\n\nGO_FAST_POST_ACTION_FAILED\nThe post-transfer action on the GoFast transfer has failed.\n\nGO_FAST_TRANSFER_TIMEOUT\nThe GoFast transfer has timed out.\n\nGO_FAST_TRANSFER_FILLED\nThe GoFast transfer has been filled.\n\nGO_FAST_TRANSFER_REFUNDED\nThe GoFast transfer has been refunded.\n\n​\n\nLayerZero Transfer Status\n\nStatusDescription\nLAYER_ZERO_TRANSFER_UNKNOWN\nThe status of the LayerZero transfer is unknown.\n\nLAYER_ZERO_TRANSFER_SENT\nThe LayerZero transfer has been sent.\n\nLAYER_ZERO_TRANSFER_RECEIVED\nThe LayerZero transfer has been received.\n\nLAYER_ZERO_TRANSFER_FAILED\nThe LayerZero transfer has failed.\n\n​\n\nHyperlane Transfer Status\n\nStatusDescription\nHYPERLANE_TRANSFER_UNKNOWN\nThe status of the Hyperlane transfer is unknown.\n\nHYPERLANE_TRANSFER_SENT\nThe Hyperlane transfer has been sent.\n\nHYPERLANE_TRANSFER_FAILED\nThe Hyperlane transfer has failed.\n\nHYPERLANE_TRANSFER_RECEIVED\nThe Hyperlane transfer has been received.\n\n​\n\nOPInit Transfer Status\n\nStatusDescription\nOPINIT_TRANSFER_UNKNOWN\nThe status of the OPInit transfer is unknown.\n\nOPINIT_TRANSFER_SENT\nThe OPInit transfer has been sent.\n\nOPINIT_TRANSFER_RECEIVED\nThe OPInit transfer has been received.\n\n​\n\nStargate Transfer Status\n\nStatusDescription\nSTARGATE_TRANSFER_UNKNOWN\nThe status of the Stargate transfer is unknown.\n\nSTARGATE_TRANSFER_SENT\nThe Stargate transfer has been sent.\n\nSTARGATE_TRANSFER_RECEIVED\nThe Stargate transfer has been received.\n\nSTARGATE_TRANSFER_FAILED\nThe Stargate transfer has failed.\n\n​\n\nEureka Transfer Status\n\nThe Eureka transfer status codes are identical to the IBC transfer status codes.\nStatusDescription\nTRANSFER_UNKNOWN\nThe status of the Eureka transfer is unknown.\n\nTRANSFER_PENDING\nThe Eureka transfer is in progress.\n\nTRANSFER_RECEIVED\nThe Eureka transfer has been received by the destination chain.\n\nTRANSFER_SUCCESS\nThe Eureka transfer has completed successfully.\n\nTRANSFER_FAILURE\nThe Eureka transfer has failed.\n\n​\n\nAdditional Error Types\n\n​\n\nPacket Error Types\n\nWhen dealing with IBC packets, you may see these error types:\nError TypeDescription\nPACKET_ERROR_UNKNOWN\nUnknown packet error.\n\nPACKET_ERROR_ACKNOWLEDGEMENT\nError in packet acknowledgement.\n\nPACKET_ERROR_TIMEOUT\nPacket timed out.\n\n​\n\nBridge-Specific Error Types\n\nError TypeDescription\nSEND_TOKEN_EXECUTION_ERROR\nError during Axelar send token execution.\n\nCONTRACT_CALL_WITH_TOKEN_EXECUTION_ERROR\nError during Axelar contract call with token execution.\n\nWas this page helpful?","tokens":1431,"crawled_at":1791192493308}
 {"id":10114,"url":"https://hyperliquid.gitbook.io/hyperliquid-docs/hyperliquid-improvement-proposals-hips/hip-2-hyperliquidity","domain":"hyperliquid.gitbook.io","chapter":"defi_protocols","title":"HIP-2: Hyperliquidity | Hyperliquid Docs","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nMotivation\nThough HIP-1 is sufficient as a permissionless token standard, in practice it is often crucial to bootstrap liquidity. One of Hyperliquid's core design principles is that liquidity should be democratized. For perps trading, HLP can quote deep and tight liquidity based on CEX perp and spot prices, but a new model is needed for HIP-1 tokens that are in early phases of price discovery.\nHyperliquidity is inspired by Uniswap, while interoperating with a native onchain order book to support sophisticated order book liquidity from end users. HIP-2 is a fully decentralized onchain strategy that is part of Hyperliquid's block transition logic. Unlike conventional automated order book strategies, there are no operators. The strategy logic is secured by the same consensus that operates the order book itself. Note that Hyperliquidity is currently only available on spot pairs against USDC.\nHyperliquidity is parametrized by\n\nspot: a spot order book asset with USDC quote returned by a deployment of HIP-1\n\nstartPx: the initial price of the range\n\nnOrders: the number of orders in the range\n\norderSz: the size of a full order in the range\n\nnSeededLevels: the number of levels that begin as bids instead of asks. Note that for each additional bid level added by incrementing nSeededLevels the deployer needs to fund Hyperliquidity with px * sz worth of USDC. For fixed nOrders, increasing seeded levels decreases the total supply because it reduces the genesis supply of Hyperliquidity.\n\nEach Hyperliquidity strategy has a price range defined recursively px_0 = startPx, px_i = round(px_{i-1} * 1.003). The strategy updates on every block where the block time is at least 3 seconds since the previous update block. After each update:\n\nStrategy targets nFull = floor(balance / orderSz) full ask orders and a balance % orderSz partial ask order if the partial order is nonzero. To the extent that ALO orders are not rejected, these orders are ensured.\n\nEach fully filled tranche is modified to an order of size orderSz on the side with available balance, with the exception of the single partial order from (1) if it exists.\n\nThe resulting strategy guarantees a 0.3% spread every 3 seconds. Like smart-contract based pools on general-purpose chains, Hyperliquidity requires no maintenance in the form of user transactions. One key improvement is that Hyperliquidity participates in a general-purpose order book. Active liquidity providers can join in liquidity provision alongside Hyperliquidity at any time, allowing markets to adapt to increasing demand for liquidity.\n\nPreviousHIP-1: Native token standard\nNextHIP-3: Builder-deployed perpetuals\n\nLast updated 4 months ago","tokens":694,"crawled_at":1791192507241}
 {"id":10115,"url":"https://docs.cosmos.network/hub/latest","domain":"docs.cosmos.network","chapter":"layer1_layer2","title":"Introduction - Cosmos Docs","text":"The Cosmos Hub is the first of many interconnected blockchains powered by the interchain stack: CometBFT, CosmosSDK and IBC. The primary token of the Cosmos Hub is the ATOM.\n​\n\nThe ATOM\n\nDo you have ATOM tokens? With ATOM, you have the superpower to contribute to the security and governance of the Cosmos Hub. Delegate your ATOM to one or more of the validators on the Cosmos Hub blockchain to earn more ATOM through Proof-of-Stake. You can also vote with your ATOM to influence the future of the Cosmos Hub through on-chain governance proposals.\nLearn more about being a delegator, learn about the security risks, and start participating with one of the following wallets.\n​\n\nCosmos Hub Wallets\n\nDo your own research and take precautions in regards to wallet security. Maintaining proper security practices is solely your responsibility when using third party wallets.\n\nThese community-maintained web and mobile wallets allow you to store & transfer ATOM, delegate ATOM to validators, and vote on on-chain governance proposals. Note that we do not endorse any of the wallets, they are listed for your convenience.\n\nKeplr - Web\n\nLedger - Hardware\n\nCosmostation - Android, iOS\n\nLeap Wallet - Android, iOS, Web\n\nAtomic Wallet - Android, Linux, macOS, Windows\n\nCitadel.One - Android, iOS\n\nCobo - Android, iOS\n\nCrypto.com - Android, iOS\n\nShapeShift - Android, iOS, Web\n\nimToken - Android, iOS\n\nMath Wallet - Android, iOS, Web\n\nTrust Wallet - Android, iOS\n\nKomodo Wallet\n\n​\n\nMetamask Snaps\n\nLeap Wallet\n\n​\n\nCosmos Hub Explorers\n\nThese block explorers allow you to search, view and analyze Cosmos Hub data—like blocks, transactions, validators, etc.\n\nMintscan\n\nNumia\n\nATOMScan\n\nPing.Pub\n\nBronBro\n\n​\n\nCosmos Hub CLI\n\ngaiad is a command-line interface that lets you interact with the Cosmos Hub. gaiad is the only tool that supports 100% of the Cosmos Hub features, including accounts, transfers, delegation, and governance. Learn more about gaiad with the delegator’s CLI guide.\n​\n\nRunning a full-node on the Cosmos Hub Mainnet\n\nIn order to run a full-node for the Cosmos Hub mainnet, you must first install gaiad. Then, follow the guide.\nIf you are looking to run a validator node, follow the validator setup guide.\n​\n\nJoin the Community\n\nHave questions, comments, or new ideas? Participate in the Cosmos community through one of the following channels.\n\nDiscord\n\nCosmos Forum\n\nCosmos on Reddit\n\nTo learn more about the Cosmos Hub and how it fits within the Cosmos Network, visit cosmos.network.\nWas this page helpful?","tokens":629,"crawled_at":1791192513311}
@@ -131,3 +131,478 @@
 {"id":10131,"url":"https://docs.cosmos.network/sdk/latest/modules/genutil/README","domain":"docs.cosmos.network","chapter":"layer1_layer2","title":"x/genutil - Cosmos Docs","text":"​\n\nConcepts\n\nThe genutil package contains a variety of genesis utility functionalities for usage within a blockchain application. Namely:\n\nGenesis transactions related (gentx)\n\nCommands for collection and creation of gentxs\n\nInitChain processing of gentxs\n\nGenesis file creation\n\nGenesis file validation\n\nGenesis file migration\n\nCometBFT related initialization\n\nTranslation of an app genesis to a CometBFT genesis\n\n​\n\nGenesis\n\nGenutil contains the data structure that defines an application genesis.\nAn application genesis consist of a consensus genesis (g.e. CometBFT genesis) and application related genesis data.\n\npackage types\n\nimport (\n\n\"bytes\"\n\"encoding/json\"\n\"errors\"\n\"fmt\"\n\"os\"\n\"time\"\n\ncmtjson \"github.com/cometbft/cometbft/libs/json\"\ncmtproto \"github.com/cometbft/cometbft/proto/tendermint/types\"\ncmttypes \"github.com/cometbft/cometbft/types\"\ncmttime \"github.com/cometbft/cometbft/types/time\"\n\"github.com/cosmos/cosmos-sdk/version\"\n)\n\nconst (\n// MaxChainIDLen is the maximum length of a chain ID.\nMaxChainIDLen = cmttypes.MaxChainIDLen\n)\n\n// AppGenesis defines the app's genesis.\ntype AppGenesis struct {\nAppName string `json:\"app_name\"`\nAppVersion string `json:\"app_version\"`\nGenesisTime time.Time `json:\"genesis_time\"`\nChainID string `json:\"chain_id\"`\nInitialHeight int64 `json:\"initial_height\"`\nAppHash []byte `json:\"app_hash\"`\nAppState json.RawMessage `json:\"app_state,omitempty\"`\nConsensus *ConsensusGenesis `json:\"consensus,omitempty\"`\n}\n\n// NewAppGenesisWithVersion returns a new AppGenesis with the app name and app version already.\nfunc NewAppGenesisWithVersion(chainID string, appState json.RawMessage) *AppGenesis {\nreturn &AppGenesis{\nAppName: version.AppName,\nAppVersion: version.Version,\nChainID: chainID,\nAppState: appState,\nConsensus: &ConsensusGenesis{\nValidators: nil,\n},\n}\n}\n\n// ValidateAndComplete performs validation and completes the AppGenesis.\nfunc (ag *AppGenesis)\n\nValidateAndComplete()\n\nerror {\nif ag.ChainID == \"\" {\nreturn errors.New(\"genesis doc must include non-empty chain_id\")\n}\nif len(ag.ChainID) > MaxChainIDLen {\nreturn fmt.Errorf(\"chain_id in genesis doc is too long (max: %d)\", MaxChainIDLen)\n}\nif ag.InitialHeight < 0 {\nreturn fmt.Errorf(\"initial_height cannot be negative (got %v)\", ag.InitialHeight)\n}\nif ag.InitialHeight == 0 {\nag.InitialHeight = 1\n}\nif ag.GenesisTime.IsZero() {\nag.GenesisTime = cmttime.Now()\n}\nif err := ag.Consensus.ValidateAndComplete(); err != nil {\nreturn err\n}\n\nreturn nil\n}\n\n// SaveAs is a utility method for saving AppGenesis as a JSON file.\nfunc (ag *AppGenesis)\n\nSaveAs(file string)\n\nerror {\nappGenesisBytes, err := json.MarshalIndent(ag, \"\", \"\n\")\nif err != nil {\nreturn err\n}\n\nreturn os.WriteFile(file, appGenesisBytes, 0o600)\n}\n\n// AppGenesisFromFile reads the AppGenesis from the provided file.\nfunc AppGenesisFromFile(genFile string) (*AppGenesis, error) {\njsonBlob, err := os.ReadFile(genFile)\nif err != nil {\nreturn nil, fmt.Errorf(\"couldn't read AppGenesis file (%s): %w\", genFile, err)\n}\n\nvar appGenesis AppGenesis\nif err := json.Unmarshal(jsonBlob, &appGenesis); err != nil {\n// fallback to CometBFT genesis\nvar ctmGenesis cmttypes.GenesisDoc\nif err2 := cmtjson.Unmarshal(jsonBlob, &ctmGenesis); err2 != nil {\nreturn nil, fmt.Errorf(\"error unmarshalling AppGenesis at %s: %w\\n failed fallback to CometBFT GenDoc: %w\", genFile, err, err2)\n}\n\nappGenesis = AppGenesis{\nAppName: version.AppName,\n// AppVersion is not filled as we do not know it from a CometBFT genesis\nGenesisTime: ctmGenesis.GenesisTime,\nChainID: ctmGenesis.ChainID,\nInitialHeight: ctmGenesis.InitialHeight,\nAppHash: ctmGenesis.AppHash,\nAppState: ctmGenesis.AppState,\nConsensus: &ConsensusGenesis{\nValidators: ctmGenesis.Validators,\nParams: ctmGenesis.ConsensusParams,\n},\n}\n\n}\n\nreturn &appGenesis, nil\n}\n\n// --------------------------\n// CometBFT Genesis Handling\n// --------------------------\n\n// ToGenesisDoc converts the AppGenesis to a CometBFT GenesisDoc.\nfunc (ag *AppGenesis)\n\nToGenesisDoc() (*cmttypes.GenesisDoc, error) {\nreturn &cmttypes.GenesisDoc{\nGenesisTime: ag.GenesisTime,\nChainID: ag.ChainID,\nInitialHeight: ag.InitialHeight,\nAppHash: ag.AppHash,\nAppState: ag.AppState,\nValidators: ag.Consensus.Validators,\nConsensusParams: ag.Consensus.Params,\n}, nil\n}\n\n// ConsensusGenesis defines the consensus layer's genesis.\n// TODO(@julienrbrt)\n\neventually abstract from CometBFT types\ntype ConsensusGenesis struct {\nValidators []cmttypes.GenesisValidator `json:\"validators,omitempty\"`\nParams *cmttypes.ConsensusParams `json:\"params,omitempty\"`\n}\n\n// NewConsensusGenesis returns a ConsensusGenesis with given values.\n// It takes a proto consensus params so it can called from server export command.\nfunc NewConsensusGenesis(params cmtproto.ConsensusParams, validators []cmttypes.GenesisValidator) *ConsensusGenesis {\nreturn &ConsensusGenesis{\nParams: &cmttypes.ConsensusParams{\nBlock: cmttypes.BlockParams{\nMaxBytes: params.Block.MaxBytes,\nMaxGas: params.Block.MaxGas,\n},\nEvidence: cmttypes.EvidenceParams{\nMaxAgeNumBlocks: params.Evidence.MaxAgeNumBlocks,\nMaxAgeDuration: params.Evidence.MaxAgeDuration,\nMaxBytes: params.Evidence.MaxBytes,\n},\nValidator: cmttypes.ValidatorParams{\nPubKeyTypes: params.Validator.PubKeyTypes,\n},\n},\nValidators: validators,\n}\n}\n\nfunc (cs *ConsensusGenesis)\n\nMarshalJSON() ([]byte, error) {\ntype Alias ConsensusGenesis\nreturn cmtjson.Marshal(&Alias{\nValidators: cs.Validators,\nParams: cs.Params,\n})\n}\n\nfunc (cs *ConsensusGenesis)\n\nUnmarshalJSON(b []byte)\n\nerror {\ntype Alias ConsensusGenesis\nresult := Alias{\n}\nif err := cmtjson.Unmarshal(b, &result); err != nil {\nreturn err\n}\n\ncs.Params = result.Params\ncs.Validators = result.Validators\n\nreturn nil\n}\n\nfunc (cs *ConsensusGenesis)\n\nValidateAndComplete()\n\nerror {\nif cs == nil {\nreturn fmt.Errorf(\"consensus genesis cannot be nil\")\n}\nif cs.Params == nil {\ncs.Params = cmttypes.DefaultConsensusParams()\n}\n\nelse if err := cs.Params.ValidateBasic(); err != nil {\nreturn err\n}\nfor i, v := range cs.Validators {\nif v.Power == 0 {\nreturn fmt.Errorf(\"the genesis file cannot contain validators with no voting power: %v\", v)\n}\nif len(v.Address) > 0 && !bytes.Equal(v.PubKey.Address(), v.Address) {\nreturn fmt.Errorf(\"incorrect address for validator %v in the genesis file, should be %v\", v, v.PubKey.Address())\n}\nif len(v.Address) == 0 {\ncs.Validators[i].Address = v.PubKey.Address()\n}\n\n}\n\nreturn nil\n}\n\nThe application genesis can then be translated to the consensus engine to the right format:\n\npackage types\n\nimport (\n\n\"bytes\"\n\"encoding/json\"\n\"errors\"\n\"fmt\"\n\"os\"\n\"time\"\n\ncmtjson \"github.com/cometbft/cometbft/libs/json\"\ncmtproto \"github.com/cometbft/cometbft/proto/tendermint/types\"\ncmttypes \"github.com/cometbft/cometbft/types\"\ncmttime \"github.com/cometbft/cometbft/types/time\"\n\"github.com/cosmos/cosmos-sdk/version\"\n)\n\nconst (\n// MaxChainIDLen is the maximum length of a chain ID.\nMaxChainIDLen = cmttypes.MaxChainIDLen\n)\n\n// AppGenesis defines the app's genesis.\ntype AppGenesis struct {\nAppName string `json:\"app_name\"`\nAppVersion string `json:\"app_version\"`\nGenesisTime time.Time `json:\"genesis_time\"`\nChainID string `json:\"chain_id\"`\nInitialHeight int64 `json:\"initial_height\"`\nAppHash []byte `json:\"app_hash\"`\nAppState json.RawMessage `json:\"app_state,omitempty\"`\nConsensus *ConsensusGenesis `json:\"consensus,omitempty\"`\n}\n\n// NewAppGenesisWithVersion returns a new AppGenesis with the app name and app version already.\nfunc NewAppGenesisWithVersion(chainID string, appState json.RawMessage) *AppGenesis {\nreturn &AppGenesis{\nAppName: version.AppName,\nAppVersion: version.Version,\nChainID: chainID,\nAppState: appState,\nConsensus: &ConsensusGenesis{\nValidators: nil,\n},\n}\n}\n\n// ValidateAndComplete performs validation and completes the AppGenesis.\nfunc (ag *AppGenesis)\n\nValidateAndComplete()\n\nerror {\nif ag.ChainID == \"\" {\nreturn errors.New(\"genesis doc must include non-empty chain_id\")\n}\nif len(ag.ChainID) > MaxChainIDLen {\nreturn fmt.Errorf(\"chain_id in genesis doc is too long (max: %d)\", MaxChainIDLen)\n}\nif ag.InitialHeight < 0 {\nreturn fmt.Errorf(\"initial_height cannot be negative (got %v)\", ag.InitialHeight)\n}\nif ag.InitialHeight == 0 {\nag.InitialHeight = 1\n}\nif ag.GenesisTime.IsZero() {\nag.GenesisTime = cmttime.Now()\n}\nif err := ag.Consensus.ValidateAndComplete(); err != nil {\nreturn err\n}\n\nreturn nil\n}\n\n// SaveAs is a utility method for saving AppGenesis as a JSON file.\nfunc (ag *AppGenesis)\n\nSaveAs(file string)\n\nerror {\nappGenesisBytes, err := json.MarshalIndent(ag, \"\", \"\n\")\nif err != nil {\nreturn err\n}\n\nreturn os.WriteFile(file, appGenesisBytes, 0o600)\n}\n\n// AppGenesisFromFile reads the AppGenesis from the provided file.\nfunc AppGenesisFromFile(genFile string) (*AppGenesis, error) {\njsonBlob, err := os.ReadFile(genFile)\nif err != nil {\nreturn nil, fmt.Errorf(\"couldn't read AppGenesis file (%s): %w\", genFile, err)\n}\n\nvar appGenesis AppGenesis\nif err := json.Unmarshal(jsonBlob, &appGenesis); err != nil {\n// fallback to CometBFT genesis\nvar ctmGenesis cmttypes.GenesisDoc\nif err2 := cmtjson.Unmarshal(jsonBlob, &ctmGenesis); err2 != nil {\nreturn nil, fmt.Errorf(\"error unmarshalling AppGenesis at %s: %w\\n failed fallback to CometBFT GenDoc: %w\", genFile, err, err2)\n}\n\nappGenesis = AppGenesis{\nAppName: version.AppName,\n// AppVersion is not filled as we do not know it from a CometBFT genesis\nGenesisTime: ctmGenesis.GenesisTime,\nChainID: ctmGenesis.ChainID,\nInitialHeight: ctmGenesis.InitialHeight,\nAppHash: ctmGenesis.AppHash,\nAppState: ctmGenesis.AppState,\nConsensus: &ConsensusGenesis{\nValidators: ctmGenesis.Validators,\nParams: ctmGenesis.ConsensusParams,\n},\n}\n\n}\n\nreturn &appGenesis, nil\n}\n\n// --------------------------\n// CometBFT Genesis Handling\n// --------------------------\n\n// ToGenesisDoc converts the AppGenesis to a CometBFT GenesisDoc.\nfunc (ag *AppGenesis)\n\nToGenesisDoc() (*cmttypes.GenesisDoc, error) {\nreturn &cmttypes.GenesisDoc{\nGenesisTime: ag.GenesisTime,\nChainID: ag.ChainID,\nInitialHeight: ag.InitialHeight,\nAppHash: ag.AppHash,\nAppState: ag.AppState,\nValidators: ag.Consensus.Validators,\nConsensusParams: ag.Consensus.Params,\n}, nil\n}\n\n// ConsensusGenesis defines the consensus layer's genesis.\n// TODO(@julienrbrt)\n\neventually abstract from CometBFT types\ntype ConsensusGenesis struct {\nValidators []cmttypes.GenesisValidator `json:\"validators,omitempty\"`\nParams *cmttypes.ConsensusParams `json:\"params,omitempty\"`\n}\n\n// NewConsensusGenesis returns a ConsensusGenesis with given values.\n// It takes a proto consensus params so it can called from server export command.\nfunc NewConsensusGenesis(params cmtproto.ConsensusParams, validators []cmttypes.GenesisValidator) *ConsensusGenesis {\nreturn &ConsensusGenesis{\nParams: &cmttypes.ConsensusParams{\nBlock: cmttypes.BlockParams{\nMaxBytes: params.Block.MaxBytes,\nMaxGas: params.Block.MaxGas,\n},\nEvidence: cmttypes.EvidenceParams{\nMaxAgeNumBlocks: params.Evidence.MaxAgeNumBlocks,\nMaxAgeDuration: params.Evidence.MaxAgeDuration,\nMaxBytes: params.Evidence.MaxBytes,\n},\nValidator: cmttypes.ValidatorParams{\nPubKeyTypes: params.Validator.PubKeyTypes,\n},\n},\nValidators: validators,\n}\n}\n\nfunc (cs *ConsensusGenesis)\n\nMarshalJSON() ([]byte, error) {\ntype Alias ConsensusGenesis\nreturn cmtjson.Marshal(&Alias{\nValidators: cs.Validators,\nParams: cs.Params,\n})\n}\n\nfunc (cs *ConsensusGenesis)\n\nUnmarshalJSON(b []byte)\n\nerror {\ntype Alias ConsensusGenesis\nresult := Alias{\n}\nif err := cmtjson.Unmarshal(b, &result); err != nil {\nreturn err\n}\n\ncs.Params = result.Params\ncs.Validators = result.Validators\n\nreturn nil\n}\n\nfunc (cs *ConsensusGenesis)\n\nValidateAndComplete()\n\nerror {\nif cs == nil {\nreturn fmt.Errorf(\"consensus genesis cannot be nil\")\n}\nif cs.Params == nil {\ncs.Params = cmttypes.DefaultConsensusParams()\n}\n\nelse if err := cs.Params.ValidateBasic(); err != nil {\nreturn err\n}\nfor i, v := range cs.Validators {\nif v.Power == 0 {\nreturn fmt.Errorf(\"the genesis file cannot contain validators with no voting power: %v\", v)\n}\nif len(v.Address) > 0 && !bytes.Equal(v.PubKey.Address(), v.Address) {\nreturn fmt.Errorf(\"incorrect address for validator %v in the genesis file, should be %v\", v, v.PubKey.Address())\n}\nif len(v.Address) == 0 {\ncs.Validators[i].Address = v.PubKey.Address()\n}\n\n}\n\nreturn nil\n}\n\npackage server\n\nimport (\n\n\"context\"\n\"errors\"\n\"fmt\"\n\"io\"\n\"net\"\n\"os\"\n\"runtime/pprof\"\n\"github.com/cometbft/cometbft/abci/server\"\ncmtcmd \"github.com/cometbft/cometbft/cmd/cometbft/commands\"\ncmtcfg \"github.com/cometbft/cometbft/config\"\n\"github.com/cometbft/cometbft/node\"\n\"github.com/cometbft/cometbft/p2p\"\npvm \"github.com/cometbft/cometbft/privval\"\n\"github.com/cometbft/cometbft/proxy\"\n\"github.com/cometbft/cometbft/rpc/client/local\"\ncmttypes \"github.com/cometbft/cometbft/types\"\ndbm \"github.com/cosmos/cosmos-db\"\n\"github.com/hashicorp/go-metrics\"\n\"github.com/spf13/cobra\"\n\"github.com/spf13/pflag\"\n\"golang.org/x/sync/errgroup\"\n\"google.golang.org/grpc\"\n\"google.golang.org/grpc/credentials/insecure\"\n\npruningtypes \"cosmossdk.io/store/pruning/types\"\n\"github.com/cosmos/cosmos-sdk/client\"\n\"github.com/cosmos/cosmos-sdk/client/flags\"\n\"github.com/cosmos/cosmos-sdk/codec\"\n\"github.com/cosmos/cosmos-sdk/server/api\"\nserverconfig \"github.com/cosmos/cosmos-sdk/server/config\"\nservergrpc \"github.com/cosmos/cosmos-sdk/server/grpc\"\nservercmtlog \"github.com/cosmos/cosmos-sdk/server/log\"\n\"github.com/cosmos/cosmos-sdk/server/types\"\n\"github.com/cosmos/cosmos-sdk/telemetry\"\n\"github.com/cosmos/cosmos-sdk/types/mempool\"\n\"github.com/cosmos/cosmos-sdk/version\"\ngenutiltypes \"github.com/cosmos/cosmos-sdk/x/genutil/types\"\n)\n\nconst (\n// CometBFT full-node start flags\nflagWithComet = \"with-comet\"\nflagAddress = \"address\"\nflagTransport = \"transport\"\nflagTraceStore = \"trace-store\"\nflagCPUProfile = \"cpu-profile\"\nFlagMinGasPrices = \"minimum-gas-prices\"\nFlagQueryGasLimit = \"query-gas-limit\"\nFlagHaltHeight = \"halt-height\"\nFlagHaltTime = \"halt-time\"\nFlagInterBlockCache = \"inter-block-cache\"\nFlagUnsafeSkipUpgrades = \"unsafe-skip-upgrades\"\nFlagTrace = \"trace\"\nFlagInvCheckPeriod = \"inv-check-period\"\n\nFlagPruning = \"pruning\"\nFlagPruningKeepRecent = \"pruning-keep-recent\"\nFlagPruningInterval = \"pruning-interval\"\nFlagIndexEvents = \"index-events\"\nFlagMinRetainBlocks = \"min-retain-blocks\"\nFlagIAVLCacheSize = \"iavl-cache-size\"\nFlagDisableIAVLFastNode = \"iavl-disable-fastnode\"\n\n// state sync-related flags\nFlagStateSyncSnapshotInterval = \"state-sync.snapshot-interval\"\nFlagStateSyncSnapshotKeepRecent = \"state-sync.snapshot-keep-recent\"\n\n// api-related flags\nFlagAPIEnable = \"api.enable\"\nFlagAPISwagger = \"api.swagger\"\nFlagAPIAddress = \"api.address\"\nFlagAPIMaxOpenConnections = \"api.max-open-connections\"\nFlagRPCReadTimeout = \"api.rpc-read-timeout\"\nFlagRPCWriteTimeout = \"api.rpc-write-timeout\"\nFlagRPCMaxBodyBytes = \"api.rpc-max-body-bytes\"\nFlagAPIEnableUnsafeCORS = \"api.enabled-unsafe-cors\"\n\n// gRPC-related flags\nflagGRPCOnly = \"grpc-only\"\nflagGRPCEnable = \"grpc.enable\"\nflagGRPCAddress = \"grpc.address\"\nflagGRPCWebEnable = \"grpc-web.enable\"\n\n// mempool flags\nFlagMempoolMaxTxs = \"mempool.max-txs\"\n)\n\n// StartCmdOptions defines options that can be customized in `StartCmdWithOptions`,\ntype StartCmdOptions struct {\n// DBOpener can be used to customize db opening, for example customize db options or support different db backends,\n// default to the builtin db opener.\nDBOpener func(rootDir string, backendType dbm.BackendType) (dbm.DB, error)\n// PostSetup can be used to setup extra services under the same cancellable context,\n// it's not called in stand-alone mode, only for in-process mode.\nPostSetup func(svrCtx *Context, clientCtx client.Context, ctx context.Context, g *errgroup.Group)\n\nerror\n// AddFlags add custom flags to start cmd\nAddFlags func(cmd *cobra.Command)\n}\n\n// StartCmd runs the service passed in, either stand-alone or in-process with\n// CometBFT.\nfunc StartCmd(appCreator types.AppCreator, defaultNodeHome string) *cobra.Command {\nreturn StartCmdWithOptions(appCreator, defaultNodeHome, StartCmdOptions{\n})\n}\n\n// StartCmdWithOptions runs the service passed in, either stand-alone or in-process with\n// CometBFT.\nfunc StartCmdWithOptions(appCreator types.AppCreator, defaultNodeHome string, opts StartCmdOptions) *cobra.Command {\nif opts.DBOpener == nil {\nopts.DBOpener = openDB\n}\ncmd := &cobra.Command{\nUse: \"start\",\nShort: \"Run the full node\",\nLong: `Run the full node application with CometBFT in or out of process. By\ndefault, the application will run with CometBFT in process.\n\nPruning options can be provided via the '--pruning' flag or alternatively with '--pruning-keep-recent', and\n'pruning-interval' together.\n\nFor '--pruning' the options are as follows:\n\ndefault: the last 362880 states are kept, pruning at 10 block intervals\nnothing: all historic states will be saved, nothing will be deleted (i.e. archiving node)\n\neverything: 2 latest states will be kept; pruning at 10 block intervals.\ncustom: allow pruning options to be manually specified through 'pruning-keep-recent', and 'pruning-interval'\n\nNode halting configurations exist in the form of two flags: '--halt-height' and '--halt-time'. During\nthe ABCI Commit phase, the node will check if the current block height is greater than or equal to\nthe halt-height or if the current block time is greater than or equal to the halt-time. If so, the\nnode will attempt to gracefully shutdown and the block will not be committed. In addition, the node\nwill not be able to commit subsequent blocks.\n\nFor profiling and benchmarking purposes, CPU profiling can be enabled via the '--cpu-profile' flag\nwhich accepts a path for the resulting pprof file.\n\nThe node may be started in a 'query only' mode where only the gRPC and JSON HTTP\nAPI services are enabled via the 'grpc-only' flag. In this mode, CometBFT is\nbypassed and can be used when legacy queries are needed after an on-chain upgrade\nis performed. Note, when enabled, gRPC will also be automatically enabled.\n`,\nPreRunE: func(cmd *cobra.Command, _ []string)\n\nerror {\nserverCtx := GetServerContextFromCmd(cmd)\n\n// Bind flags to the Context's Viper so the app construction can set\n// options accordingly.\nif err := serverCtx.Viper.BindPFlags(cmd.Flags()); err != nil {\nreturn err\n}\n\n_, err := GetPruningOptionsFromFlags(serverCtx.Viper)\n\nreturn err\n},\nRunE: func(cmd *cobra.Command, _ []string)\n\nerror {\nserverCtx := GetServerContextFromCmd(cmd)\n\nclientCtx, err := client.GetClientQueryContext(cmd)\nif err != nil {\nreturn err\n}\n\nwithCMT, _ := cmd.Flags().GetBool(flagWithComet)\nif !withCMT {\nserverCtx.Logger.Info(\"starting ABCI without CometBFT\")\n}\n\nreturn wrapCPUProfile(serverCtx, func()\n\nerror {\nreturn start(serverCtx, clientCtx, appCreator, withCMT, opts)\n})\n},\n}\n\ncmd.Flags().String(flags.FlagHome, defaultNodeHome, \"The application home directory\")\n\ncmd.Flags().Bool(flagWithComet, true, \"Run abci app embedded in-process with CometBFT\")\n\ncmd.Flags().String(flagAddress, \"tcp://0.0.0.0:26658\", \"Listen address\")\n\ncmd.Flags().String(flagTransport, \"socket\", \"Transport protocol: socket, grpc\")\n\ncmd.Flags().String(flagTraceStore, \"\", \"Enable KVStore tracing to an output file\")\n\ncmd.Flags().String(FlagMinGasPrices, \"\", \"Minimum gas prices to accept for transactions; Any fee in a tx must meet this minimum (e.g. 0.01photino;0.0001stake)\")\n\ncmd.Flags().Uint64(FlagQueryGasLimit, 0, \"Maximum gas a Rest/Grpc query can consume. Blank and 0 imply unbounded.\")\n\ncmd.Flags().IntSlice(FlagUnsafeSkipUpgrades, []int{\n}, \"Skip a set of upgrade heights to continue the old binary\")\n\ncmd.Flags().Uint64(FlagHaltHeight, 0, \"Block height at which to gracefully halt the chain and shutdown the node\")\n\ncmd.Flags().Uint64(FlagHaltTime, 0, \"Minimum block time (in Unix seconds)\n\nat which to gracefully halt the chain and shutdown the node\")\n\ncmd.Flags().Bool(FlagInterBlockCache, true, \"Enable inter-block caching\")\n\ncmd.Flags().String(flagCPUProfile, \"\", \"Enable CPU profiling and write to the provided file\")\n\ncmd.Flags().Bool(FlagTrace, false, \"Provide full stack traces for errors in ABCI Log\")\n\ncmd.Flags().String(FlagPruning, pruningtypes.PruningOptionDefault, \"Pruning strategy (default|nothing|everything|custom)\")\n\ncmd.Flags().Uint64(FlagPruningKeepRecent, 0, \"Number of recent heights to keep on disk (ignored if pruning is not 'custom')\")\n\ncmd.Flags().Uint64(FlagPruningInterval, 0, \"Height interval at which pruned heights are removed from disk (ignored if pruning is not 'custom')\")\n\ncmd.Flags().Uint(FlagInvCheckPeriod, 0, \"Assert registered invariants every N blocks\")\n\ncmd.Flags().Uint64(FlagMinRetainBlocks, 0, \"Minimum block height offset during ABCI commit to prune CometBFT blocks\")\n\ncmd.Flags().Bool(FlagAPIEnable, false, \"Define if the API server should be enabled\")\n\ncmd.Flags().Bool(FlagAPISwagger, false, \"Define if swagger documentation should automatically be registered (Note: the API must also be enabled)\")\n\ncmd.Flags().String(FlagAPIAddress, serverconfig.DefaultAPIAddress, \"the API server address to listen on\")\n\ncmd.Flags().Uint(FlagAPIMaxOpenConnections, 1000, \"Define the number of maximum open connections\")\n\ncmd.Flags().Uint(FlagRPCReadTimeout, 10, \"Define the CometBFT RPC read timeout (in seconds)\")\n\ncmd.Flags().Uint(FlagRPCWriteTimeout, 0, \"Define the CometBFT RPC write timeout (in seconds)\")\n\ncmd.Flags().Uint(FlagRPCMaxBodyBytes, 1000000, \"Define the CometBFT maximum request body (in bytes)\")\n\ncmd.Flags().Bool(FlagAPIEnableUnsafeCORS, false, \"Define if CORS should be enabled (unsafe - use it at your own risk)\")\n\ncmd.Flags().Bool(flagGRPCOnly, false, \"Start the node in gRPC query only mode (no CometBFT process is started)\")\n\ncmd.Flags().Bool(flagGRPCEnable, true, \"Define if the gRPC server should be enabled\")\n\ncmd.Flags().String(flagGRPCAddress, serverconfig.DefaultGRPCAddress, \"the gRPC server address to listen on\")\n\ncmd.Flags().Bool(flagGRPCWebEnable, true, \"Define if the gRPC-Web server should be enabled. (Note: gRPC must also be enabled)\")\n\ncmd.Flags().Uint64(FlagStateSyncSnapshotInterval, 0, \"State sync snapshot interval\")\n\ncmd.Flags().Uint32(FlagStateSyncSnapshotKeepRecent, 2, \"State sync snapshot to keep\")\n\ncmd.Flags().Bool(FlagDisableIAVLFastNode, false, \"Disable fast node for IAVL tree\")\n\ncmd.Flags().Int(FlagMempoolMaxTxs, mempool.DefaultMaxTx, \"Sets MaxTx value for the app-side mempool\")\n\n// support old flags name for backwards compatibility\ncmd.Flags().SetNormalizeFunc(func(f *pflag.FlagSet, name string)\n\npflag.NormalizedName {\nif name == \"with-tendermint\" {\nname = flagWithComet\n}\n\nreturn pflag.NormalizedName(name)\n})\n\n// add support for all CometBFT-specific command line options\ncmtcmd.AddNodeFlags(cmd)\nif opts.AddFlags != nil {\nopts.AddFlags(cmd)\n}\n\nreturn cmd\n}\n\nfunc start(svrCtx *Context, clientCtx client.Context, appCreator types.AppCreator, withCmt bool, opts StartCmdOptions)\n\nerror {\nsvrCfg, err := getAndValidateConfig(svrCtx)\nif err != nil {\nreturn err\n}\n\napp, appCleanupFn, err := startApp(svrCtx, appCreator, opts)\nif err != nil {\nreturn err\n}\n\ndefer appCleanupFn()\n\nmetrics, err := startTelemetry(svrCfg)\nif err != nil {\nreturn err\n}\n\nemitServerInfoMetrics()\nif !withCmt {\nreturn startStandAlone(svrCtx, app, opts)\n}\n\nreturn startInProcess(svrCtx, svrCfg, clientCtx, app, metrics, opts)\n}\n\nfunc startStandAlone(svrCtx *Context, app types.Application, opts StartCmdOptions)\n\nerror {\naddr := svrCtx.Viper.GetString(flagAddress)\ntransport := svrCtx.Viper.GetString(flagTransport)\ncmtApp := NewCometABCIWrapper(app)\n\nsvr, err := server.NewServer(addr, transport, cmtApp)\nif err != nil {\nreturn fmt.Errorf(\"error creating listener: %v\", err)\n}\n\nsvr.SetLogger(servercmtlog.CometLoggerWrapper{\nLogger: svrCtx.Logger.With(\"module\", \"abci-server\")\n})\n\ng, ctx := getCtx(svrCtx, false)\n\ng.Go(func()\n\nerror {\nif err := svr.Start(); err != nil {\nsvrCtx.Logger.Error(\"failed to start out-of-process ABCI server\", \"err\", err)\n\nreturn err\n}\n\n// Wait for the calling process to be canceled or close the provided context,\n// so we can gracefully stop the ABCI server.\n<-ctx.Done()\n\nsvrCtx.Logger.Info(\"stopping the ABCI server...\")\n\nreturn errors.Join(svr.Stop(), app.Close())\n})\n\nreturn g.Wait()\n}\n\nfunc startInProcess(svrCtx *Context, svrCfg serverconfig.Config, clientCtx client.Context, app types.Application,\nmetrics *telemetry.Metrics, opts StartCmdOptions,\n)\n\nerror {\ncmtCfg := svrCtx.Config\nhome := cmtCfg.RootDir\ngRPCOnly := svrCtx.Viper.GetBool(flagGRPCOnly)\n\ng, ctx := getCtx(svrCtx, true)\nif gRPCOnly {\n// TODO: Generalize logic so that gRPC only is really in startStandAlone\nsvrCtx.Logger.Info(\"starting node in gRPC only mode; CometBFT is disabled\")\n\nsvrCfg.GRPC.Enable = true\n}\n\nelse {\nsvrCtx.Logger.Info(\"starting node with ABCI CometBFT in-process\")\n\ntmNode, cleanupFn, err := startCmtNode(ctx, cmtCfg, app, svrCtx)\nif err != nil {\nreturn err\n}\n\ndefer cleanupFn()\n\n// Add the tx service to the gRPC router. We only need to register this\n// service if API or gRPC is enabled, and avoid doing so in the general\n// case, because it spawns a new local CometBFT RPC client.\nif svrCfg.API.Enable || svrCfg.GRPC.Enable {\n// Re-assign for making the client available below do not use := to avoid\n// shadowing the clientCtx variable.\nclientCtx = clientCtx.WithClient(local.New(tmNode))\n\napp.RegisterTxService(clientCtx)\n\napp.RegisterTendermintService(clientCtx)\n\napp.RegisterNodeService(clientCtx, svrCfg)\n}\n\n}\n\ngrpcSrv, clientCtx, err := startGrpcServer(ctx, g, svrCfg.GRPC, clientCtx, svrCtx, app)\nif err != nil {\nreturn err\n}\n\nerr = startAPIServer(ctx, g, cmtCfg, svrCfg, clientCtx, svrCtx, app, home, grpcSrv, metrics)\nif err != nil {\nreturn err\n}\nif opts.PostSetup != nil {\nif err := opts.PostSetup(svrCtx, clientCtx, ctx, g); err != nil {\nreturn err\n}\n\n}\n\n// wait for signal capture and gracefully return\n// we are guaranteed to be waiting for the \"ListenForQuitSignals\" goroutine.\nreturn g.Wait()\n}\n\n// TODO: Move nodeKey into being created within the function.\nfunc startCmtNode(\nctx context.Context,\ncfg *cmtcfg.Config,\napp types.Application,\nsvrCtx *Context,\n) (tmNode *node.Node, cleanupFn func(), err error) {\nnodeKey, err := p2p.LoadOrGenNodeKey(cfg.NodeKeyFile())\nif err != nil {\nreturn nil, cleanupFn, err\n}\ncmtApp := NewCometABCIWrapper(app)\n\ntmNode, err = node.NewNodeWithContext(\nctx,\ncfg,\npvm.LoadOrGenFilePV(cfg.PrivValidatorKeyFile(), cfg.PrivValidatorStateFile()),\nnodeKey,\nproxy.NewLocalClientCreator(cmtApp),\ngetGenDocProvider(cfg),\ncmtcfg.DefaultDBProvider,\nnode.DefaultMetricsProvider(cfg.Instrumentation),\nservercmtlog.CometLoggerWrapper{\nLogger: svrCtx.Logger\n},\n)\nif err != nil {\nreturn tmNode, cleanupFn, err\n}\nif err := tmNode.Start(); err != nil {\nreturn tmNode, cleanupFn, err\n}\n\ncleanupFn = func() {\nif tmNode != nil && tmNode.IsRunning() {\n_ = tmNode.Stop()\n_ = app.Close()\n}\n\n}\n\nreturn tmNode, cleanupFn, nil\n}\n\nfunc getAndValidateConfig(svrCtx *Context) (serverconfig.Config, error) {\nconfig, err := serverconfig.GetConfig(svrCtx.Viper)\nif err != nil {\nreturn config, err\n}\nif err := config.ValidateBasic(); err != nil {\nreturn config, err\n}\n\nreturn config, nil\n}\n\n// returns a function which returns the genesis doc from the genesis file.\nfunc getGenDocProvider(cfg *cmtcfg.Config)\n\nfunc() (*cmttypes.GenesisDoc, error) {\nreturn func() (*cmttypes.GenesisDoc, error) {\nappGenesis, err := genutiltypes.AppGenesisFromFile(cfg.GenesisFile())\nif err != nil {\nreturn nil, err\n}\n\nreturn appGenesis.ToGenesisDoc()\n}\n}\n\nfunc setupTraceWriter(svrCtx *Context) (traceWriter io.WriteCloser, cleanup func(), err error) {\n// clean up the traceWriter when the server is shutting down\ncleanup = func() {\n}\ntraceWriterFile := svrCtx.Viper.GetString(flagTraceStore)\n\ntraceWriter, err = openTraceWriter(traceWriterFile)\nif err != nil {\nreturn traceWriter, cleanup, err\n}\n\n// if flagTraceStore is not used then traceWriter is nil\nif traceWriter != nil {\ncleanup = func() {\nif err = traceWriter.Close(); err != nil {\nsvrCtx.Logger.Error(\"failed to close trace writer\", \"err\", err)\n}\n\n}\n\n}\n\nreturn traceWriter, cleanup, nil\n}\n\nfunc startGrpcServer(\nctx context.Context,\ng *errgroup.Group,\nconfig serverconfig.GRPCConfig,\nclientCtx client.Context,\nsvrCtx *Context,\napp types.Application,\n) (*grpc.Server, client.Context, error) {\nif !config.Enable {\n// return grpcServer as nil if gRPC is disabled\nreturn nil, clientCtx, nil\n}\n_, port, err := net.SplitHostPort(config.Address)\nif err != nil {\nreturn nil, clientCtx, err\n}\nmaxSendMsgSize := config.MaxSendMsgSize\nif maxSendMsgSize == 0 {\nmaxSendMsgSize = serverconfig.DefaultGRPCMaxSendMsgSize\n}\nmaxRecvMsgSize := config.MaxRecvMsgSize\nif maxRecvMsgSize == 0 {\nmaxRecvMsgSize = serverconfig.DefaultGRPCMaxRecvMsgSize\n}\ngrpcAddress := fmt.Sprintf(\"127.0.0.1:%s\", port)\n\n// if gRPC is enabled, configure gRPC client for gRPC gateway\ngrpcClient, err := grpc.Dial(\ngrpcAddress,\ngrpc.WithTransportCredentials(insecure.NewCredentials()),\ngrpc.WithDefaultCallOptions(\ngrpc.ForceCodec(codec.NewProtoCodec(clientCtx.InterfaceRegistry).GRPCCodec()),\ngrpc.MaxCallRecvMsgSize(maxRecvMsgSize),\ngrpc.MaxCallSendMsgSize(maxSendMsgSize),\n),\n)\nif err != nil {\nreturn nil, clientCtx, err\n}\n\nclientCtx = clientCtx.WithGRPCClient(grpcClient)\n\nsvrCtx.Logger.Debug(\"gRPC client assigned to client context\", \"target\", grpcAddress)\n\ngrpcSrv, err := servergrpc.NewGRPCServer(clientCtx, app, config)\nif err != nil {\nreturn nil, clientCtx, err\n}\n\n// Start the gRPC server in a goroutine. Note, the provided ctx will ensure\n// that the server is gracefully shut down.\ng.Go(func()\n\nerror {\nreturn servergrpc.StartGRPCServer(ctx, svrCtx.Logger.With(\"module\", \"grpc-server\"), config, grpcSrv)\n})\n\nreturn grpcSrv, clientCtx, nil\n}\n\nfunc startAPIServer(\nctx context.Context,\ng *errgroup.Group,\ncmtCfg *cmtcfg.Config,\nsvrCfg serverconfig.Config,\nclientCtx client.Context,\nsvrCtx *Context,\napp types.Application,\nhome string,\ngrpcSrv *grpc.Server,\nmetrics *telemetry.Metrics,\n)\n\nerror {\nif !svrCfg.API.Enable {\nreturn nil\n}\n\nclientCtx = clientCtx.WithHomeDir(home)\napiSrv := api.New(clientCtx, svrCtx.Logger.With(\"module\", \"api-server\"), grpcSrv)\n\napp.RegisterAPIRoutes(apiSrv, svrCfg.API)\nif svrCfg.Telemetry.Enabled {\napiSrv.SetTelemetry(metrics)\n}\n\ng.Go(func()\n\nerror {\nreturn apiSrv.Start(ctx, svrCfg)\n})\n\nreturn nil\n}\n\nfunc startTelemetry(cfg serverconfig.Config) (*telemetry.Metrics, error) {\nif !cfg.Telemetry.Enabled {\nreturn nil, nil\n}\n\nreturn telemetry.New(cfg.Telemetry)\n}\n\n// wrapCPUProfile starts CPU profiling, if enabled, and executes the provided\n// callbackFn in a separate goroutine, then will wait for that callback to\n// return.\n//\n// NOTE: We expect the caller to handle graceful shutdown and signal handling.\nfunc wrapCPUProfile(svrCtx *Context, callbackFn func()\n\nerror)\n\nerror {\nif cpuProfile := svrCtx.Viper.GetString(flagCPUProfile); cpuProfile != \"\" {\nf, err := os.Create(cpuProfile)\nif err != nil {\nreturn err\n}\n\nsvrCtx.Logger.Info(\"starting CPU profiler\", \"profile\", cpuProfile)\nif err := pprof.StartCPUProfile(f); err != nil {\nreturn err\n}\n\ndefer func() {\nsvrCtx.Logger.Info(\"stopping CPU profiler\", \"profile\", cpuProfile)\n\npprof.StopCPUProfile()\nif err := f.Close(); err != nil {\nsvrCtx.Logger.Info(\"failed to close cpu-profile file\", \"profile\", cpuProfile, \"err\", err.Error())\n}\n\n}()\n}\n\nreturn callbackFn()\n}\n\n// emitServerInfoMetrics emits server info related metrics using application telemetry.\nfunc emitServerInfoMetrics() {\nvar ls []metrics.Label\nversionInfo := version.NewInfo()\nif len(versionInfo.GoVersion) > 0 {\nls = append(ls, telemetry.NewLabel(\"go\", versionInfo.GoVersion))\n}\nif len(versionInfo.CosmosSdkVersion) > 0 {\nls = append(ls, telemetry.NewLabel(\"version\", versionInfo.CosmosSdkVersion))\n}\nif len(ls) == 0 {\nreturn\n}\n\ntelemetry.SetGaugeWithLabels([]string{\"server\", \"info\"\n}, 1, ls)\n}\n\nfunc getCtx(svrCtx *Context, block bool) (*errgroup.Group, context.Context) {\nctx, cancelFn := context.WithCancel(context.Background())\n\ng, ctx := errgroup.WithContext(ctx)\n// listen for quit signals so the calling parent process can gracefully exit\nListenForQuitSignals(g, block, cancelFn, svrCtx.Logger)\n\nreturn g, ctx\n}\n\nfunc startApp(svrCtx *Context, appCreator types.AppCreator, opts StartCmdOptions) (app types.Application, cleanupFn func(), err error) {\ntraceWriter, traceCleanupFn, err := setupTraceWriter(svrCtx)\nif err != nil {\nreturn app, traceCleanupFn, err\n}\nhome := svrCtx.Config.RootDir\ndb, err := opts.DBOpener(home, GetAppDBBackend(svrCtx.Viper))\nif err != nil {\nreturn app, traceCleanupFn, err\n}\n\napp = appCreator(svrCtx.Logger, db, traceWriter, svrCtx.Viper)\n\ncleanupFn = func() {\ntraceCleanupFn()\nif localErr := app.Close(); localErr != nil {\nsvrCtx.Logger.Error(localErr.Error())\n}\n\n}\n\nreturn app, cleanupFn, nil\n}\n\n​\n\nClient\n\n​\n\nCLI\n\nThe genutil commands are available under the genesis subcommand.\n​\n\nadd-genesis-account\n\nAdd a genesis account to genesis.json. Learn more here.\n​\n\ncollect-gentxs\n\nCollect genesis txs and output a genesis.json file.\n\nsimd genesis collect-gentxs\n\nThis will create a new genesis.json file that includes data from all the validators (we sometimes call it the “super genesis file” to distinguish it from single-validator genesis files).\n​\n\ngentx\n\nGenerate a genesis tx carrying a self delegation.\n\nsimd genesis gentx [key_name] [amount] --chain-id [chain-id]\n\nThis will create the genesis transaction for your new chain. Here amount should be at least 1000000000stake.\nIf you provide too much or too little, you will encounter an error when starting a node.\n​\n\nmigrate\n\nMigrate genesis to a specified target (SDK) version.\n\nsimd genesis migrate [target-version]\n\nThe migrate command is extensible and takes a MigrationMap. This map is a mapping of target versions to genesis migrations functions.\nWhen not using the default MigrationMap, it is recommended to still call the default MigrationMap corresponding the SDK version of the chain and prepend/append your own genesis migrations.\n\n​\n\nvalidate-genesis\n\nValidates the genesis file at the default location or at the location passed as an argument.\n\nsimd genesis validate-genesis\n\nValidate genesis only validates if the genesis is valid at the current application binary. For validating a genesis from a previous version of the application, use the migrate command to migrate the genesis to the current version.\n\nWas this page helpful?","tokens":8509,"crawled_at":1791192657070}
 {"id":10132,"url":"https://gov.uniswap.org/c/urc/16","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Uniswap Request for Comment (URC) - Uniswap Governance","text":"Uniswap Request for Comment (URC)\n\nURC Discussion\n\nFor [discussion] Proposal Ideas that have not been assigned a number by the URC Editors.\n\nGetting Started with URCs\n\nProcess and templates for participating in the URC lifecycle.\n\nCanonical URCs\n\nAll URCs that have received a number from the URC Editors.\n\nTopic\n\nReplies\nViews\nActivity\n\nAbout the Uniswap Request for Comment (URC) category\n\nUniswap Request for Comment (URC)\n\n0\n\n22\n\nApril 2, 2026\n\nURC-2: Custom Accounting Hook Swap Event\n\nURC Discussion\n\n1\n\n171\n\nAugust 25, 2026\n\nURC-4: Active Liquidity Framework Hook Interface\n\nURC Discussion\n\n2\n\n208\n\nJuly 20, 2026\n\nURC-3: Hook TVL and Effective Liquidity Reporting\n\nURC Discussion\n\n0\n\n134\n\nJune 30, 2026\n\nURC-1: Uniswap Request for Comment Process\n\nURC Discussion\n\n0\n\n88\n\nJune 29, 2026","tokens":198,"crawled_at":1791192665488}
 {"id":10133,"url":"https://a16zcrypto.com/posts/article/building-magi-a-new-rollup-client-for-optimism","domain":"a16zcrypto.com","chapter":"research","title":"Building Magi: A new rollup client for Optimism - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nBuilding Magi: A new rollup client for Optimism\nNoah Citron\n04.19.23\n\nTags & Share Tags\ncode & engineering\nmulti-client diversity\nopen source\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nDecentralization is crypto’s defining promise: Networks that have no single point of failure are more secure and more resilient than their centralized counterparts. In practice, we often see emerging points of centralization as potentially vulnerable – their failures can compromise an entire network. Ethereum’s switch to Proof of Stake, for example, drew attention to the potential risk of relying on a single client at any layer. And fortunately, the openness of the ecosystem, along with a push for greater client diversity, has resulted in more clients and an increasingly more secure network.\n\nThis effort isn’t limited to Ethereum L1. Just as client diversity is important for Ethereum; it’s critically important for rollups. Multiple independent client implementations can help ensure the safety and liveliness of the network. They’re also a whole lot of fun to work on (thanks to some very detailed specifications).\n\nThat’s why we’re excited to take our very first step into the Optimism Collective by releasing Magi, a blazing fast OP Stack rollup client written in Rust. Magi acts as the consensus client (often called a rollup client in the context of the OP Stack) in the traditional execution/consensus split of Ethereum – it feeds new blocks to the execution client in order to advance the chain. Magi performs the same core functionality as the reference implementation (op-node) and works alongside an execution node (such as op-geth) to sync to any OP Stack chain, including Optimism and Base.\n\nIn this post, we share why we built Magi, and what’s in store for the future. Magi is still in its very early stages, so we welcome your ideas, feedback, and contributions, as we shape it into a production-ready client.\n\nBringing diversity to rollup clients\n\nClient diversity is needed on both the execution and consensus sides, but most of the development has so far been focused on execution clients.\n\nAny existing Ethereum execution client can be compatible with Optimism by implementing a modest set of changes, and several new projects are already adapting these clients to help achieve client diversity. OP Labs modified Geth to build op-geth; and other groups are currently building op-erigon and op-reth.\n\nThis is tougher on the rollup client side, since the rollup client is a brand new piece of software. So far, just one implementation exists: op-node, which is maintained by OP Labs and written in Go. Magi aims to be an independently developed, drop-in replacement for op-node, adding to the rollup’s client diversity. We hope that building out this new, Rust-based client will encourage greater safety and liveliness throughout the OP Stack, and bring more contributors into the ecosystem.\n\nWhat’s next: Welcoming contributors for new features, fixes, and more\n\nMagi is very new, and likely months of development away from being a feasible alternative to op-node. Some of the features and improvements we plan to add in the near future:\n\nTracking the unsafe head (unconfirmed blocks) to lower latency.\n\nNew sync mechanisms to improve initial sync speed.\n\nAlternative data availability layer support.\n\nBetter frameworks for testing Magi, op-node, and any future clients.\n\nThere’s a long way to go, but we’re committed to getting there. We would greatly appreciate contributors, so check out the client or reach out with your ideas, feedback, and code – we’re excited to work together to keep moving Magi and the OP Stack ecosystem forward.\n\nAcknowledgments\n\nNone of this would be possible without the hard work of the OP Labs team: I want to thank Refcell, who’s been contributing to Magi since nearly the beginning, as well as Protolambda, Joshua, and Vex who have provided valuable help in understanding some of the complexities of the Bedrock specification.","tokens":1026,"crawled_at":1791192676059}
+{"id":10134,"url":"https://docs.cosmos.network/sdk/latest/guides/reference/bech32","domain":"docs.cosmos.network","chapter":"layer1_layer2","title":"Address Encoding - Cosmos Docs","text":"The Cosmos SDK uses the Bech32 address format for all user-facing addresses. Bech32 encoding provides robust integrity checks through checksums and includes a human-readable prefix (HRP) that provides contextual information about the address type.\n​\n\nAddress Types\n\nThe SDK defines three distinct address types, each with its own Bech32 prefix:\nAddress TypeBech32 PrefixExamplePurpose\nAccount Address\ncosmos\ncosmos1r5v5sr...\nUser accounts, balances, transactions\n\nValidator Operator Address\ncosmosvaloper\ncosmosvaloper1r5v5sr...\nValidator operator identity, staking operations\n\nConsensus Address\ncosmosvalcons\ncosmosvalcons1r5v5sr...\nValidator consensus participation, block signing\n\nEach address type also has a corresponding public key prefix:\n\nAccount public keys: cosmospub\n\nValidator public keys: cosmosvaloperpub\n\nConsensus public keys: cosmosvalconspub\n\n​\n\nSupported Key Schemes\n\nThe Cosmos SDK supports three key schemes. The choice of scheme affects address length and whether it can be used for transactions or consensus:\nAddress length in bytesPublic key length in bytesUsed for transaction authenticationUsed for consensus (CometBFT)\nsecp256k1\n20\n33\nyes\nno\n\nsecp256r1\n32\n33\nyes\nno\n\ntm-ed25519\n— not used —\n32\nno\nyes\n\nsecp256k1 is the default for user accounts. secp256r1 is supported as an alternative and produces longer addresses (32 bytes). tm-ed25519 is used exclusively for validator consensus keys and does not produce a user-facing address.\n​\n\nAddress Derivation\n\nAddresses are derived from public keys through cryptographic hashing. The process differs based on the key algorithm:\n​\n\nSecp256k1 Keys (Account Addresses)\n\nAccount addresses use Bitcoin-style address derivation:\n\n1. Public Key: 33 bytes (compressed secp256k1 public key)\n2. SHA-256 hash of public key: 32 bytes\n3. RIPEMD-160 hash of result: 20 bytes (final address)\n\nImplementation: crypto/keys/secp256k1/secp256k1.go\n\nfunc (pubKey *PubKey) Address() crypto.Address {\nsha := sha256.Sum256(pubKey.Key) // Step 1: SHA-256\nhasherRIPEMD160 := ripemd160.New()\nhasherRIPEMD160.Write(sha[:])\nreturn hasherRIPEMD160.Sum(nil) // Step 2: RIPEMD-160 = 20 bytes\n}\n\n​\n\nEd25519 Keys (Consensus Addresses)\n\nConsensus addresses use truncated SHA-256:\n\n1. Public Key: 32 bytes (Ed25519 public key)\n2. SHA-256 hash, truncated to first 20 bytes\n\nImplementation: crypto/keys/ed25519/ed25519.go\n\nfunc (pubKey *PubKey) Address() crypto.Address {\nreturn crypto.Address(tmhash.SumTruncated(pubKey.Key)) // SHA-256-20\n}\n\n​\n\nBech32 Encoding Process\n\nOnce address bytes are derived, they’re converted to Bech32 format:\nStep 1: Convert from 8-bit to 5-bit encoding\n\n// Address bytes (20 bytes = 160 bits)\naddressBytes := []byte{0x12, 0x34, ..., 0xab} // 20 bytes\n\n// Convert to 5-bit groups for Bech32\nconverted, _ := bech32.ConvertBits(addressBytes, 8, 5, true)\n\nStep 2: Encode with Human-Readable Prefix\n\n// Combine HRP with converted bytes\nbech32Address, _ := bech32.Encode(\"cosmos\", converted)\n// Result: \"cosmos1r5v5srda7xfth3uckstjst6k05kmeyzptewwdk\"\n\nImplementation: types/bech32/bech32.go\n​\n\nConfiguring Bech32 prefixes\n\nEvery Cosmos SDK application sets its Bech32 prefixes and SLIP-44 coin type once at startup via sdk.GetConfig(), then seals the config so it cannot be changed at runtime. The defaults (cosmos, cosmosvaloper, etc.) are defined in types/config.go. Chain developers override them before the app starts:\n\nconfig := sdk.GetConfig()\nconfig.SetBech32PrefixForAccount(\"cosmos\", \"cosmospub\")\nconfig.SetBech32PrefixForValidator(\"cosmosvaloper\", \"cosmosvaloperpub\")\nconfig.SetBech32PrefixForConsensusNode(\"cosmosvalcons\", \"cosmosvalconspub\")\nconfig.SetCoinType(118) // SLIP-44 coin type\nconfig.Seal()\n\n​\n\nAddress Validation\n\nThe SDK validates addresses through:\n\nFormat validation: Ensures valid Bech32 encoding\n\nPrefix validation: Confirms correct HRP for address type\n\nLength validation: Verifies address is exactly 20 bytes when decoded\n\nfunc (bc Bech32Codec) StringToBytes(text string) ([]byte, error) {\nhrp, bz, err := bech32.DecodeAndConvert(text)\nif err != nil {\nreturn nil, err\n}\n\nif hrp != bc.Bech32Prefix {\nreturn nil, fmt.Errorf(\"invalid prefix\")\n}\n\nreturn bz, sdk.VerifyAddressFormat(bz) // Checks length = 20 bytes\n}\n\n​\n\nModule Addresses\n\nModule accounts use deterministic address derivation defined in ADR-028:\n\n// Module address without derivation keys\nfunc Module(moduleName string) []byte {\nreturn crypto.AddressHash([]byte(moduleName))\n}\n\n// Module address with derivation keys (new method)\nfunc Module(moduleName string, derivationKeys ...[]byte) []byte {\nmKey := append([]byte(moduleName), 0) // Null byte separator\naddr := Hash(\"module\", append(mKey, derivationKeys[0]...))\nreturn addr // 32 bytes (not 20 bytes like user addresses)\n}\n\nModule addresses are longer (32 bytes vs 20 bytes) to reduce collision probability.\n​\n\nValidator Address Relationships\n\nA validator has three related addresses:\n\nOperator Address (cosmosvaloper1...): The validator’s operational identity, derived from the operator’s account key\n\nConsensus Address (cosmosvalcons1...): Derived from the validator’s consensus public key (Ed25519), used for block signing\n\nAccount Address (cosmos1...): The operator’s account for receiving rewards\n\n// Validator stores its consensus pubkey\ntype Validator struct {\nOperatorAddress string // cosmosvaloper1... (from operator's account)\nConsensusPubkey *Any // Ed25519 public key for signing\n// ...\n}\n\n// Consensus address is derived from the consensus pubkey\nfunc (v Validator) GetConsAddr() ([]byte, error) {\npk := v.ConsensusPubkey.GetCachedValue().(cryptotypes.PubKey)\nreturn pk.Address().Bytes(), nil // SHA-256-20 of Ed25519 pubkey\n}\n\n​\n\nPerformance: Address Caching\n\nThe SDK caches Bech32-encoded addresses to optimize repeated conversions:\n\nvar (\naccAddrCache *simplelru.LRU // 60,000 entries\nvalAddrCache *simplelru.LRU // 500 entries\nconsAddrCache *simplelru.LRU // 500 entries\n)\n\nWhen Address.String() is called, the SDK:\n\nChecks the LRU cache for the encoded address\n\nReturns cached value if found\n\nOtherwise, performs Bech32 encoding and caches the result\n\nThis significantly improves performance during block processing and state queries.\n​\n\nComplete Example\n\nHere’s the full pipeline for creating an account address:\n\n// 1. Generate keypair\nprivKey := secp256k1.GenPrivKey() // 32 bytes\npubKey := privKey.PubKey() // 33 bytes (compressed)\n\n// 2. Derive address bytes\nsha := sha256.Sum256(pubKey.Bytes()) // 32 bytes\nripemd := ripemd160.Sum(sha[:]) // 20 bytes\naddrBytes := ripemd[:]\n\n// 3. Create AccAddress type\naccAddr := sdk.AccAddress(addrBytes)\n\n// 4. Convert to Bech32 string\n// Internally: bech32.ConvertAndEncode(\"cosmos\", addrBytes)\naddressStr := accAddr.String()\n// Result: \"cosmos1r5v5srda7xfth3uckstjst6k05kmeyzptewwdk\"\n\n// 5. Use in account\naccount := auth.NewBaseAccount(accAddr, pubKey, accountNumber, sequence)\n\n​\n\nRelated Concepts\n\nAccounts - Understanding account types and management\n\nStore - How addresses are used as keys in state storage\n\nTransactions - How addresses are used in transaction signing\n\nWas this page helpful?","tokens":1767,"crawled_at":1791192699746}
+{"id":10135,"url":"https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/hyperevm","domain":"hyperliquid.gitbook.io","chapter":"defi_protocols","title":"HyperEVM | Hyperliquid Docs","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nThe HyperEVM consists of EVM blocks built as part of Hyperliquid's execution, inheriting all security from HyperBFT consensus. HYPE is the native gas token on the HyperEVM. To move HYPE from HyperCore to HyperEVM, send HYPE to 0x2222222222222222222222222222222222222222. See the instructions in Native Transfers for more details on how this works.\nNote that there are currently no official frontend components of the EVM. Users can build their own frontends or port over existing EVM applications. All interaction with the EVM happens through the JSON-RPC. For example, users can add the chain to their wallets by entering the RPC URL and chain ID. There is currently no websocket JSON-RPC support for the RPC at rpc.hyperliquid.xyz/evmbut other RPC implementations may support it.\nThe HyperEVM uses the Cancun hardfork without blobs. In particular, EIP-1559 is enabled on the HyperEVM. Base fees are burned as usual, implemented in the standard way where the burned fees are removed from the total EVM supply. Unlike most other EVM chains, priority fees are also burned because the HyperEVM uses HyperBFT consensus. The burned priority fees are sent to the zero address's EVM balance.\nOn both mainnet and testnet, HYPE on the HyperEVM has 18 decimals. A few differences between testnet and mainnet HyperEVM are highlighted below:\nMainnet\nChain ID: 999\nJSON-RPC endpoint: https://rpc.hyperliquid.xyz/evm for mainnet\nTestnet\nChain ID: 998\nJSON-RPC endpoint: https://rpc.hyperliquid-testnet.xyz/evm\nAdditional notes\nPre-EIP-155 transactions are accepted as with many EVM chains. Users generally should not use wallets that have previously sent pre-EIP-155 transactions.\nError code 10055 represents errors occurring at the boundary between HyperCore and HyperEVM. Examples include nonce errors, insufficient funds, duplicate transaction hashes, or underpriced replacement transactions.\n\nPreviousHIP-4 deployer actions\nNextDual-block architecture\n\nLast updated 24 days ago","tokens":516,"crawled_at":1791192721980}
+{"id":10136,"url":"https://stack.olas.network/mech-server","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Home - Olas Stack Developer Documentation","text":"Home\n\nMechs\n\nNote: The codebase uses the term service (from the underlying Open Autonomy framework) interchangeably with AI agent.\n\nMechs are Olas AI agents that provide on-chain services to other AI agents in exchange for small payments.\nThey allow agents to access a wide range of tools—such as LLM subscriptions or prediction services—without the need to implement ad-hoc integrations.\nAll interactions with Mechs happen through a common API using on-chain requests and responses, enabling agents to access multiple tools via a unified interface.\n\nYou can think of Mechs as subscription-free tool libraries with a standard interface. Each Mech can offer multiple tools.\nAnyone can create and deploy their own Mechs and register them in the Olas Registry. Once registered, a Mech contract can be created via the Mech Marketplace.\n\nThe Mech Marketplace\n\nThe Mech Marketplace is a collection of smart contracts that facilitate seamless, on-chain interactions between requesters (agents or applications) and Mech agents providing task-based services.\nIt acts as a relay, ensuring secure payments and efficient task execution.\nSpecifically, the Mech Marketplace enables:\n\nEffortless Mech Deployment\nAny AI agent registered in the Olas Registry can deploy a Mech contract with minimal inputs, allowing rapid tool offering and on-chain payment collection.\n\nSeamless Task Requests\nRequesters can submit service requests directly through the Mech Marketplace. On-chain contracts handle payments and service delivery transparently between requesters and Mechs.\n\nGuaranteed Task Completion\nIf a designated Mech fails to respond within the requester's specified deadline, a take-over mechanism allows other available Mechs to complete the task, ensuring high reliability and fulfillment rates.\n\nKarma Reputation System\nEach Mech's performance is tracked via the Karma contract, which maintains a reputation score based on successful task completions and failures. High Karma scores signal trustworthiness to requesters under honest participation assumptions.\n\nA Competitive Environment\nMechs are incentivized to complete tasks promptly and reliably to maintain high Karma scores, improving their chances of receiving more tasks over time.\n\nThrough Mechs and the Mech Marketplace, agents in the Olas ecosystem gain modular, on-chain access to advanced tooling without managing subscriptions or complex integrations, supporting scalable and decentralized agent economies.\n\nPayment models\n\nWhen creating a Mech, deployers can select between the following payment models:\n\nNative: a fixed-price model where the requester pays using the chain's native token for each delivered service.\n\nToken: similar to the Native model, but payments are made using a specified ERC20 token.\n\nNevermined subscription native: a dynamic pricing model that allows flexible pricing across different services with native token.\n\nNevermined subscription token: a dynamic pricing model that allows flexible pricing across different services using a specified ERC20 token.\n\nSupported chains\n\nChain\nNative\nOLAS Token\nUSDC Token\nNevermined\n\nGnosis\n\n✅\n\n✅\n\n❌\n\n✅\n\nBase\n\n✅\n\n✅\n\n✅\n\n✅\n\nPolygon\n\n✅\n\n✅\n\n✅\n\n✅\n\nOptimism\n\n✅\n\n✅\n\n✅\n\n✅\n\nHow the request-response flow works\n\nHere's a simplified version of the mech request-response:\n\nWrite request data: the requester writes the request data to IPFS. The request data must contain the attributes nonce, tool, and prompt. Additional attributes can be passed depending on the specific tool:\n\n{\n\"nonce\": 15,\n\"tool\": \"prediction_request\",\n\"prompt\": \"Will my favourite football team win this week's match?\"\n}\n\nThe application gets the request data IPFS hash from the IPFS node.\n\nThe application writes the request's IPFS hash to the Mech Marketplace contract, including a small payment. Alternatively, the payment could be done separately through a Nevermined subscription.\n\nThe Mech AI agent is constantly monitoring request events, and therefore gets the request hash.\n\nThe Mech reads the request data from IPFS using its hash.\n\nThe Mech selects the appropriate tool to handle the request from the tool entry in the metadata, and runs the tool with the given arguments, usually a prompt.\n\nThe Mech gets a response from the tool.\n\nThe Mech writes the response to IPFS.\n\nThe Mech receives the response IPFS hash.\n\nThe Mech writes the response hash to the Mech Marketplace contract.\n\nThe requester monitors for response events and reads the response hash from the associated transaction.\n\nThe application gets the response metadata from IPFS:\n\n{\n\"requestId\": 68039248068127180134548324138158983719531519331279563637951550269130775,\n\"result\": \"{\\\"p_yes\\\": 0.35, \\\"p_no\\\": 0.65, \\\"confidence\\\": 0.85, \\\"info_utility\\\": 0.75}\"\n}\n\nSee some examples of requests and responses on the Mech Hub.\n\nRequirements\n\nPython >=3.10, <3.12\n\nuv (for the \"From source\" path only)\n\nDocker Engine + Docker Compose\n\nQuick start\n\nQuickstart (installed package)\n\npip install mech-server\nmech setup -c <gnosis|base|polygon|optimism>\n# edit ~/.operate-mech/.env and set your API keys\nmech run -c <gnosis|base|polygon|optimism>\nmech stop -c <gnosis|base|polygon|optimism>\n\nmech setup auto-bootstraps the default workspace at ~/.operate-mech/ if it does not exist yet.\n\nFrom source\n\nClone the repository:\n\ngit clone https://github.com/valory-xyz/mech-server.git\ncd mech-server/\n\nInstall all Python dependencies:\n\nuv sync\nsource .venv/bin/activate\n\nDownload all the mech packages from IPFS:\n\nautonomy packages sync --update-packages\n\nRun the setup command:\n\nmech setup -c <gnosis|base|polygon|optimism>\n\nYou will be prompted to fill in some details, including the RPC for your chosen chain. You can get one from a provider like Quiknode but we encourage you to first test against a virtual network using Tenderly. This way, you can also use the faucet to fund the required wallets.\n\nCreating and running a Mech with custom tools\n\nThis section walks through creating a custom tool, publishing it, and running your Mech.\n\n1. Set up the workspace\n\nBefore adding tools, you need a workspace. Run setup once:\n\nmech setup -c <gnosis|base|polygon|optimism>\n\nThis creates the workspace at ~/.operate-mech/, builds the agent, deploys a mech on the marketplace, and configures keys and environment.\n\n2. Scaffold a tool\n\nmech add-tool AUTHOR_NAME TOOL_NAME -d \"My tool description\"\n\nThis generates the following structure:\n\n~/.operate-mech/packages/\n└── AUTHOR_NAME/\n└── customs/\n└── TOOL_NAME/\n├── component.yaml\n├── TOOL_NAME.py\n└── __init__.py\n\n3. Configure and implement the tool\n\ncomponent.yaml — review and update:\n\nname: the name of the tool.\n\nauthor: the author's name.\n\nversion: the version of the tool.\n\ntype: the component type. Should be custom.\n\ndescription: the description of the tool.\n\nlicense: should be Apache-2.0.\n\naea_version: the supported open-aea version.\n\nfingerprint: auto-generated by mech prepare-metadata.\n\nentry_point: the module containing the tool's implementation.\n\ncallable: the function called in the entry point module.\n\ndependencies: the tool's Python dependencies, for example:\n\ndependencies:\ndependency_1:\nversion: ==0.5.3\ndependency_2:\nversion: '>=2.20.0'\n\nTOOL_NAME.py — implement the tool logic. The scaffold generates a working stub with the correct structure:\n\nALLOWED_TOOLS = [\"tool_name\"]\n\nMechResponse = Tuple[str, Optional[str], Optional[Dict[str, Any]], Any, Any]\n\ndef error_response(msg: str) -> MechResponse:\n\"\"\"Return an error mech response.\"\"\"\nreturn msg, None, None, None, None\n\ndef run(**kwargs: Any) -> MechResponse:\n\"\"\"Run the tool.\"\"\"\nprompt = kwargs.get(\"prompt\")\nif prompt is None:\nreturn error_response(\"No prompt has been given.\")\nresult = do_work(prompt)\nreturn result, prompt, None, None, None\n\nKey points:\n\nALLOWED_TOOLS must list the tool name exactly as it appears in requests.\n\nrun() must return a 5-tuple (result, prompt, context, extra, extra).\n\nThe first element is the tool's response (typically a string or JSON string).\n\nThe second element is the original prompt.\n\n4. Configure the offchain URL\n\nIn addition to on-chain requests, a mech can serve off-chain requests over HTTP. If you want to enable off-chain requests, provide a URL that routes to your mech's HTTP server (which binds to localhost:8000). This URL is included in the mech's on-chain metadata so that clients can discover it.\n\nSet the URL by passing --offchain-url to prepare-metadata:\n\nmech prepare-metadata -c gnosis --offchain-url <url>\n\nAlternatively, set the MECH_OFFCHAIN_URL variable in the chain .env file and run prepare-metadata without the flag:\n\n# ~/.operate-mech/.env.gnosis\nMECH_OFFCHAIN_URL=<url>\n\nmech prepare-metadata -c gnosis\n\nThe CLI persists the URL to MECH_OFFCHAIN_URL in the chain .env file and includes it in the generated metadata.json under the \"url\" field. If no URL is configured, the field defaults to empty.\n\n5. Publish metadata and update on-chain\n\nOnce your tool is implemented, publish everything with a single command:\n\nmech prepare-metadata -c gnosis\n\nThis command handles the full publish pipeline:\n\nLocks package hashes (re-computes fingerprints after your edits)\n\nPushes all packages to IPFS\n\nGenerates metadata.json from your tool definitions\n\nPublishes metadata to IPFS\n\nWrites METADATA_HASH and TOOLS_TO_PACKAGE_HASH to .env\n\nThen update the on-chain metadata hash:\n\nmech update-metadata -c gnosis\n\n6. Run your Mech\n\nmech run -c <gnosis|base|polygon|optimism>\n\n7. Send a request\n\nGet your Mech's address from the workspace .env:\n\ngrep MECH_TO_CONFIG ~/.operate-mech/.env\n\nSend the request:\n\nmechx request --prompts <your_prompt> --priority-mech <your_mech_address> --tools <your_tool_name> --chain-config <gnosis|base|polygon|optimism>\n\nWait for the response. If there's an error in the tool, you will see it in the Mech's logs.\n\n8. Stop your Mech\n\nmech stop -c <gnosis|base|polygon|optimism>\n\nAdding tools to an existing Mech\n\nIf your Mech is already running and you want to add or update tools:\n\nStop the running service:\n\nmech stop -c <gnosis|base|polygon|optimism>\n\nScaffold and implement your new tool (same as steps 2-3 above).\n\nPublish the updated metadata and update the on-chain registry:\n\nmech prepare-metadata -c <chain>\nmech update-metadata -c <chain>\n\nRestart your Mech:\n\nmech run -c <gnosis|base|polygon|optimism>\n\nMinting a tool on the Olas Registry\n\nTo register your tool as a component on the Olas Registry, mint it here.\n\nYou will need an address (EOA) and the hash of the metadata file.\nClick on \"Generate Hash & File\" and provide:\n\nname (name of the tool)\n\ndescription (of the tool)\n\nversion (must match the version in component.yaml)\n\npackage hash (found in packages/packages.json)\n\nOptionally, an NFT image URL. To push an image to IPFS:\n\nmechx push-to-ipfs ./<file_name>\n\nCLI commands reference\n\nCommand\nDescription\n\nmech setup -c <chain>\n\nFull first-time setup: workspace, agent build, mech deployment, env config, key setup\n\nmech add-tool <author> <name>\n\nScaffold a new mech tool\n\nmech prepare-metadata -c <chain>\n\nLock packages, push to IPFS, generate and publish metadata\n\nmech prepare-metadata -c <chain> --offchain-url <url>\n\nSame as above, also sets the public offchain URL in metadata and .env\n\nmech update-metadata -c <chain>\n\nUpdate the metadata hash on-chain via Safe transaction\n\nmech run -c <chain>\n\nRun the mech AI agent via Docker\n\nmech stop -c <chain>\n\nStop a running mech AI agent","tokens":2838,"crawled_at":1791192722881}
+{"id":10137,"url":"https://www.metaplex.com/docs/smart-contracts/core/transfer","domain":"www.metaplex.com","chapter":"docs","title":"Transferring Assets | Metaplex Core","text":"This guide shows how to transfer Core Assets between wallets on Solana using the Metaplex Core SDK. Send NFTs to other users with a single instruction.\nWhat You'll Learn\nTransfer an Asset to a new owner\nHandle transfers for Assets in Collections\nUse Transfer Delegate for authorized transfers\nUnderstand transfer authority requirements\n\nSummary\nTransfer a Core Asset to a new owner using the transfer instruction. Only the current owner (or an authorized Transfer Delegate) can initiate a transfer.\nCall transfer(umi, { asset, newOwner }) with the recipient's address\nFor Collection Assets, include the collection parameter\nTransfer Delegates can transfer on behalf of owners\nTransfers are free (only transaction fee applies)\nOut of Scope\nToken Metadata transfers (use mpl-token-metadata), batch transfers (loop through Assets), and marketplace sales (use escrow programs).\nQuick Start\nJump to: Basic Transfer · Collection Transfer · Delegate Transfer\nInstall: npm install @metaplex-foundation/mpl-core @metaplex-foundation/umi\nFetch the Asset to verify ownership and collection membership\nCall transfer(umi, { asset, newOwner })\nVerify with fetchAsset() that ownership changed\nPrerequisites\nUmi configured with a signer that owns the Asset (or is its Transfer Delegate)\nAsset address of the Asset to transfer\nRecipient address (public key) of the new owner The owner of a Core Asset can transfer ownership to another account by using the transfer instruction to the MPL Core program.\n\nTransferring a Core Asset\n\n1import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n2import { transfer } from '@metaplex-foundation/mpl-core'\n\n3import { mplCore } from '@metaplex-foundation/mpl-core'\n\n4import { publicKey } from '@metaplex-foundation/umi'\n\n5\n\n6// Initialize UMI\n\n7const umi = createUmi('https://api.devnet.solana.com')\n\n8 .use(mplCore())\n\n9\n\n10// Transfer an existing NFT asset to a new owner\n\n11const result = await transfer(umi, {\n\n12 asset: publicKey('AssetAddressHere...'),\n\n13 newOwner: publicKey('RecipientAddressHere...'),\n\n14}).sendAndConfirm(umi)\n\n15\n\n16console.log('Asset transferred:', result.signature)\n\nTransferring a Core Asset in a Collection\nIf you are transferring an Asset which has a collection you will need to pass the collection address in. How to tell if an Asset is in a Collection?\nTransfer an Asset that is part of a Collection\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { transferV1 } from '@metaplex-foundation/mpl-core'\n\nconst asset = publicKey('11111111111111111111111111111111')\n\nconst collection = publicKey('22222222222222222222222222222222222222222222')\n\nconst newOwner = publicKey('33333333333333333333333333333333333333333333')\n\nawait transferV1(umi, {\n\nasset,\n\nnewOwner,\n\ncollection,\n\n}).sendAndConfirm(umi)\n\nWhat if I am the Transfer Delegate of an Asset?\nIf you are the Transfer Delegate of an Asset via the Transfer Delegate plugin then you can call the transferV1 function as you would if you were the owner of the Asset.\nCommon Errors\nAuthority mismatch\nYou're not the owner or Transfer Delegate of the Asset. Check ownership:\nconst asset = await fetchAsset(umi, assetAddress)\n\nconsole.log(asset.owner) // Must match your signer\n\nAsset is frozen\nThe Asset has a Freeze Delegate plugin and is currently frozen. The freeze authority must unfreeze it before transfer.\nMissing collection parameter\nFor Assets in a Collection, you must pass the collection address. Check if the Asset has a collection:\nconst asset = await fetchAsset(umi, assetAddress)\n\nif (asset.updateAuthority.type === 'Collection') {\n\nconsole.log('Collection:', asset.updateAuthority.address)\n\n}\n\nNotes\nTransfers are free - no rent cost, only the transaction fee (~0.000005 SOL)\nThe new owner receives full control of the Asset\nTransfer, Burn, and Freeze Delegates are revoked after a successful transfer\nFrozen Assets cannot be transferred until unfrozen\nAlways fetch the Asset first to check collection membership\nQuick Reference\nTransfer Parameters\nParameterRequiredDescription\nasset\nYes\nAsset address or fetched object\n\nnewOwner\nYes\nRecipient's public key\n\ncollection\nIf in collection\nCollection address\n\nauthority\nNo\nDefaults to signer (use for delegates)\n\nWho Can Transfer?\nAuthorityCan Transfer?\nAsset Owner\nYes\n\nTransfer Delegate\nYes (revoked after)\n\nUpdate Authority\nNo\n\nCollection Authority\nNo\n\nFAQ\nHow do I know if an Asset is in a Collection?\nFetch the Asset and check its updateAuthority:\nconst asset = await fetchAsset(umi, assetAddress)\n\nif (asset.updateAuthority.type === 'Collection') {\n\n// Pass asset.updateAuthority.address as collection parameter\n\n}\n\nCan I transfer to myself?\nYes. Transferring to your own address is valid (useful for consolidating wallets or testing).\nWhat happens to the Transfer Delegate after a transfer?\nThe Transfer Delegate plugin is automatically revoked when the transfer completes. The new owner must assign a new delegate if needed.\nCan I cancel a transfer?\nNo. Transfers are atomic - once the transaction confirms, ownership has changed. There's no pending state to cancel.\nCan I transfer multiple Assets at once?\nNot in a single instruction. You can batch multiple transfer instructions in one transaction (up to transaction size limits), but each Asset requires its own transfer call.\nDoes transferring change the update authority?\nNo. Transfer only changes ownership. The update authority remains the same unless explicitly changed via the update instruction.\nGlossary\nTermDefinition\nOwner\nThe wallet that currently owns the Asset\n\nTransfer Delegate\nAn account authorized to transfer on behalf of the owner\n\nFrozen\nAn Asset state where transfers are blocked\n\nNew Owner\nThe recipient wallet receiving the Asset\n\nCollection\nThe Collection an Asset belongs to (affects transfer requirements)","tokens":1446,"crawled_at":1791192753960}
+{"id":10138,"url":"https://a16zcrypto.com/posts/tags/multi-client-diversity","domain":"a16zcrypto.com","chapter":"research","title":"multi-client diversity - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nmulti-client diversity\n\nFeed\nFILTERS\n(1)\nclear filters\n\ncategories\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\n(1) recommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nclear all multi-client diversity\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n04.19.23 / Noah Citron\nBuilding Magi: A new rollup client for Optimism\nIntroducing Magi, a blazing-fast OP Stack rollup, written in Rust, and our first step into the Optimism Collective.\n\ncode & engineering\nmulti-client diversity\nopen source\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":831,"crawled_at":1791192733276}
+{"id":10139,"url":"https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/hyperevm/interacting-with-hypercore","domain":"hyperliquid.gitbook.io","chapter":"defi_protocols","title":"Interacting with HyperCore | Hyperliquid Docs","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nRead precompiles\nThe testnet EVM provides read precompiles that allows querying HyperCore information. The precompile addresses start at 0x0000000000000000000000000000000000000800 and have methods for querying information such as perps positions, spot balances, vault equity, staking delegations, oracle prices, and the L1 block number.\nThe values are guaranteed to match the latest HyperCore state at the time the EVM block is constructed.\nAttached is a Solidity file L1Read.sol describing the read precompiles. As an example, this call queries the third perp oracle price on testnet:\n\ncast call 0x0000000000000000000000000000000000000807 0x0000000000000000000000000000000000000000000000000000000000000003 --rpc-url https://rpc.hyperliquid-testnet.xyz/evm\n\nTo convert to floating point numbers, divide the returned price by 10^(6 - szDecimals)for perps and 10^(8 - base asset szDecimals) for spot.\nPrecompiles called on invalid inputs such as invalid assets or vault address will return an error and consume all gas passed into the precompile call frame. Precompiles have a gas cost of 2000 + 65 * (input_len + output_len).\nCoreWriter contract\nA system contract is available at 0x3333333333333333333333333333333333333333 for sending transactions from the HyperEVM to HyperCore. It burns ~25,000 gas before emitting a log to be processed by HyperCore as an action. In practice the gas usage for a basic call will be ~47000. A solidity file CoreWriter.sol for the write system contract is attached.\nAction encoding details\n\nByte 1: Encoding version\n\nCurrently, only version 1 is supported, but enables future upgrades while maintaining backward compatibility.\n\nBytes 2-4: Action ID\n\nThese three bytes, when decoded as a big-endian unsigned integer, represent the unique identifier for the action.\n\nRemaining bytes: Action encoding\n\nThe rest of the bytes constitue the action-specific data. It is always the raw ABI encoding of a sequence of Solidity types\n\nTo prevent any potential latency advantages for using HyperEVM to bypass the L1 mempool, order actions and vault transfers sent from CoreWriter are delayed onchain for a few seconds. This has no noticeable effect on UX because the end user has to wait for at least one small block confirmation. These onchain-delayed actions appear twice in the L1 explorer: first as an enqueuing and second as a HyperCore execution.\n\nAction ID\nAction\nFields\nSolidity Type\nNotes\n\n1\n\nLimit order\n\n(asset, isBuy, limitPx, sz, reduceOnly, encodedTif, cloid)\n\n(uint32, bool, uint64, uint64, bool, uint8, uint128)\n\nTif encoding: 1 for Alo , 2 for Gtc , 3 for Ioc . Cloid encoding: 0 means no cloid, otherwise uses the number as the cloid. limitPx and sz should be sent as 10^8 * the human readable value\n\n2\n\nVault transfer\n\n(vault, isDeposit, usd)\n\n(address, bool, uint64)\n\n3\n\nToken delegate\n\n(validator, wei, isUndelegate)\n\n(address, uint64, bool)\n\n4\n\nStaking deposit\n\nwei\n\nuint64\n\n5\n\nStaking withdraw\n\nwei\n\nuint64\n\n6\n\nSpot send\n\n(destination, token, wei)\n\n(address, uint64, uint64)\n\n7\n\nUSD class transfer\n\n(ntl, toPerp)\n\n(uint64, bool)\n\n8\n\nFinalize EVM Contract\n\n(token, encodedFinalizeEvmContractVariant, createNonce)\n\n(uint64, uint8, uint64)\n\nencodedFinalizeEvmContractVariant 1 for Create, 2 for FirstStorageSlot , 3 for CustomStorageSlot . If Create variant, then createNonce input argument is used.\n\n9\n\nAdd API wallet\n\n(API wallet address, API wallet name)\n\n(address, string)\n\nIf the API wallet name is empty then this becomes the main API wallet / agent\n\n10\n\nCancel order by oid\n\n(asset, oid)\n\n(uint32, uint64)\n\n11\n\nCancel order by cloid\n\n(asset, cloid)\n\n(uint32, uint128)\n\n12\n\nApprove builder fee\n\n(maxFeeRate, builder address)\n\n(uint64, address)\n\nmaxFeeRate is in decibps. To approve a builder fee of 0.01% maxFreeRate should be 10.\n\n13\n\nSend asset\n\n(destination, subAccount, source_dex, destination_dex, token, wei)\n\n(address, address, uint32, uint32, uint64, uint64)\n\nIf subAccount is not the zero address, then transfer from subAccount. Specify uint32::MAX for the source_dex or destination_dex for spot.\n\n15\n\nBorrow lend operation\n\n(encodedOperation, token, wei)\n\n(uint8, uint64, uint64)\n\nencodedOperation 0 for Supply, 1 for Withdraw . If wei is 0 then maximally apply the operation, e.g. withdraw full balance from reserve.\n\n16\n\nSet abstraction\n\n(user, abstraction)\n\n(address, uint8)\n\nabstraction 1 for disabled, 2 for unifiedAccount , 3 for portfolioMargin . user can either be the master user or a sub-account.\n\n17\n\nOutcome operation\n\n(encodedOperation, question, outcome, wei)\n\n(uint8, uint32, uint32, uint64)\n\nencodedOperation 0 for SplitOutcome, 1 for MergeOutcome, 2 for MergeQuestion, 3 for NegateOutcome. Unused fields must be set to 0: SplitOutcome and MergeOutcome ignore question; MergeQuestion ignores outcome. negate uses both. Payloads with non-zero unused fields are dropped. wei must be a multiple of size. For the merge operations 0 means merge the maximal amount.\n\nBelow is an example contract that would send an action on behalf of its own contract address on HyperCore, which also demonstrates one way to construct the encoded action in Solidity.\n\ncontract CoreWriterCaller {\nfunction sendUsdClassTransfer(uint64 ntl, bool toPerp) external {\nbytes memory encodedAction = abi.encode(ntl, toPerp);\nbytes memory data = new bytes(4 + encodedAction.length);\ndata[0] = 0x01;\ndata[1] = 0x00;\ndata[2] = 0x00;\ndata[3] = 0x07;\nfor (uint256 i = 0; i < encodedAction.length; i++) {\ndata[4 + i] = encodedAction[i];\n}\nCoreWriter(0x3333333333333333333333333333333333333333).sendRawAction(data);\n}\n}\n\nHappy building. Any feedback is appreciated.\n\nL1Read.sol\n12KB\n\nOpen\n\nCoreWriter.sol\n298B\n\nOpen\n\nPreviousRaw HyperEVM block data\nNextHyperCore <> HyperEVM transfers\n\nLast updated 1 month ago","tokens":1460,"crawled_at":1791192742609}
+{"id":10140,"url":"https://stack.olas.network/mech-client","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Home - Olas Stack Developer Documentation","text":"Home\n\nOverview\n\nThis guide contains practical guidelines for interacting with Mechs.\nA requester - whether it is an agent or an application - can choose between two methods for sending service requests:\n\nOn-chain: The request is sent to the Mech contract. For Mechs registered on the Mech Marketplace, it is relayed via the Mech Marketplace.\n\nOff-chain: The request is sent directly to the Mech AI agent. The Mech then sends the result (or delivery) to the Mech contract, which is subsequently relayed by the Mech Marketplace if the Mech is registered there.\n\nTo send a request, follow these steps:\n\n1. Choose a Mech;\n\n2. Make an on-chain deposit according to the Mech’s payment model.\n\n3. Choose a method for sending the request (on-chain or off-chain).\n\n4. Send the request.\n\nDetailed instructions for each step are provided below.\n\nSetup\n\nRequirements: Python >=3.10, <3.12 (Python 3.10 or 3.11), uv\n\n1. Install mech-client:\n\npip install mech-client\n\n2. Setting up an EOA (Externally Owned Account) account:\n\na. Install browser extension of Metamask and open it.\n\nb. Click on the account icon, then select “Add account or hardware wallet”, then “Add a new Ethereum account”. Provide a name for the account and click “Add account”.\n\nc. Select the newly created account. Open the top-right menu, click “Account details”, then click “Show private key”.\n\nd. Copy this key in the file ethereum_private_key.txt in your project folder. Make sure the file contains only the private key, with no leading or trailing spaces, tabs, or newlines.\n\nAgent Mode and Client Mode\n\nThere are two modes for on-chain interactions:\n\nAgent mode (default, recommended): Registers your on-chain interactions as an agent on the Olas protocol via a Safe multisig. This allows agent-to-agent (A2A) activity to be reflected on the client.\n\nClient mode: Simple on-chain interactions using an EOA (Externally Owned Account). Use --client-mode flag before commands:\n\nmechx --client-mode <rest of the cli command>\n\nSetting up agent mode\n\nFor better reliability, it is recommended to use a stable third-party RPC provider.\n\nmechx setup --chain-config <chain_config>\n\nRun setup for each chain you interact with, and ensure your .env file has the correct RPC endpoint.\n\nSupported Chains\n\nSupported chains: gnosis, base, polygon, optimism\n\nAll commands require --chain-config with one of these four chain names.\n\nChain\nMarketplace\nAgent Mode\nNative Payment\nNVM Subscriptions\nOLAS Payments\nUSDC Payments\n\nGnosis\n\n✅\n\n✅\n\n✅\n\n✅\n\n✅\n\n❌\n\nBase\n\n✅\n\n✅\n\n✅\n\n✅\n\n✅\n\n✅\n\nPolygon\n\n✅\n\n✅\n\n✅\n\n❌\n\n✅\n\n✅\n\nOptimism\n\n✅\n\n✅\n\n✅\n\n❌\n\n✅\n\n✅\n\nKey:\n- Marketplace: All supported chains have marketplace contracts deployed.\n- Agent Mode: All supported chains support on-chain agent registration via setup.\n- Native Payment: Chains supporting deposit native command for prepaid native token deposits.\n- NVM Subscriptions: Chains supporting subscription purchase command for Nevermined subscription-based payments (Gnosis, Base only).\n- OLAS/USDC Payments: Chains supporting deposit token command with OLAS or USDC tokens.\n\nImportant Notes:\n- The mech list command works on all marketplace chains (Gnosis, Base, Polygon, Optimism) with default subgraph URLs provided. The MECHX_SUBGRAPH_URL environment variable is optional and only needed to override defaults.\n- For other marketplace commands (request, deposits), subgraph is not required.\n\n1. How to Send a request to a Mech (registered on the Mech MarketPlace)\n\nTo send a request to a Mech that is accessible through the Mech Marketplace, first complete the setup, then follow the instructions below.\n\nYou will need to choose a Mech, and then select one of the following methods to send a request:\n- Via the terminal\n- Using a Python script\n\nFollow the instructions in the corresponding section.\n\n1. 1. Choosing a Mech\n\nUse the command mechx in terminal, which is structured as follows.\nmechx mech list --chain-config <chain-config>\n\nReplace <chain-config> by the chosen network. Supported marketplace chains: gnosis, base, polygon, optimism.\n\nNote: Default subgraph URLs are provided for all supported chains. You can optionally override the default:\n\nexport MECHX_SUBGRAPH_URL=<your-custom-subgraph-url>\n\n+--------------+--------------------+--------------------------------------------+--------------------+---------------------------------------------------------------------------------------------------------------+\n| AI Agent Id | Mech Type | Mech Address | Total Deliveries | Metadata Link |\n+==============+====================+============================================+====================+===============================================================================================================+\n| 2182 | Fixed Price Native | 0xc05e7412439bd7e91730a6880e18d5d5873f632c | 41246 | https://gateway.autonolas.tech/ipfs/f01701220157d3b106831e2713b86af1b52af76a3ef28c52ae0853e9638180902ebee41d4 |\n+--------------+--------------------+--------------------------------------------+--------------------+---------------------------------------------------------------------------------------------------------------+\n| 2235 | Fixed Price Native | 0xb3c6319962484602b00d5587e965946890b82101 | 10127 | https://gateway.autonolas.tech/ipfs/f01701220157d3b106831e2713b86af1b52af76a3ef28c52ae0853e9638180902ebee41d4 |\n+--------------+--------------------+--------------------------------------------+--------------------+---------------------------------------------------------------------------------------------------------------+\n| 2198 | Fixed Price Native | 0x601024e27f1c67b28209e24272ced8a31fc8151f | 5714 | https://gateway.autonolas.tech/ipfs/f01701220157d3b106831e2713b86af1b52af76a3ef28c52ae0853e9638180902ebee41d4 |\n+--------------+--------------------+--------------------------------------------+--------------------+---------------------------------------------------------------------------------------------------------------+\n| 1722 | Fixed Price Token | 0x13f36b1a516290b7563b1de574a02ebeb48926a1 | 399 | https://gateway.autonolas.tech/ipfs/f01701220157d3b106831e2713b86af1b52af76a3ef28c52ae0853e9638180902ebee41d4 |\n+--------------+--------------------+--------------------------------------------+--------------------+---------------------------------------------------------------------------------------------------------------+\n| 2135 | Fixed Price Native | 0xbead38e4c4777341bb3fd44e8cd4d1ba1a7ad9d7 | 353 | https://gateway.autonolas.tech/ipfs/f01701220157d3b106831e2713b86af1b52af76a3ef28c52ae0853e9638180902ebee41d4 |\n+--------------+--------------------+--------------------------------------------+--------------------+---------------------------------------------------------------------------------------------------------------+\n\n1. 2. In terminal\n\n1. 2. 1. Request command\n\nUse the command mechx in terminal, which is structured as follows:\n\nmechx request --prompts <prompt> --priority-mech <mech_address> --tools <tool> --chain-config <chain-config> --use-offchain\n\nReplace each placeholder as follows:\n\n<prompt>: The request description to be sent to the Mech. For instance: \"Write a short poem\".\n\n<mech_address>: The address of the Mech to send the request to.\n\n<tool>: The name of the tool to use.\n\n<chain-config>: One of the keys in the dictionary defined in mech_client/configs/mechs.json (e.g., \"gnosis\"). This provides the client with a configuration for the chosen network.\n\n--use-offchain: Optional flag to use the off-chain method. Omit for on-chain requests.\n\n1. 2. 2. Deposits and Payment Types\n\nWhen you send a request, the Mech Client automatically detects the mech's payment type and handles the appropriate payment flow. You don't need to specify the payment type - the mech's smart contract declares it.\n\nUnderstanding Payment Types:\n\nThere are 5 payment types that mechs can use:\n\nPayment Type\nDescription\nHow to Pay\n\nNATIVE\n\nPer-request native token\n\nClient sends native tokens (xDAI, ETH, MATIC) with transaction\n\nOLAS_TOKEN\n\nPer-request OLAS token\n\nClient approves and transfers OLAS tokens\n\nUSDC_TOKEN\n\nPer-request USDC token\n\nClient approves and transfers USDC tokens\n\nNATIVE_NVM\n\nNVM subscription with native token\n\nPurchase subscription first, then unlimited requests\n\nTOKEN_NVM_USDC\n\nNVM subscription with USDC token\n\nPurchase subscription first, then unlimited requests\n\nFinding the price per request\n\nTo determine the Mech's fee in advance:\n\nEnter the Mech's address into the block explorer of the corresponding network.\n\nClick on \"Contract\", then \"Read Contract\".\n\nFind and click on the function maxDeliveryRate.\n\nDivide the displayed number by 10^8 in order to obtain the price per request (in ether or token units, depending on the Mech).\n\nNote: For Mechs using the Nevermined subscription model, this value corresponds to the maximum price per request; actual usage may involve multiple requests per subscription.\n\nMaking a deposit\n\nOption 1: Prepaid balance (for NATIVE, OLAS_TOKEN, USDC_TOKEN mechs)\n\nYou can deposit funds to your prepaid balance and use --use-prepaid flag when making requests:\n\nFor NATIVE payment mechs:\n\nmechx deposit native <amount> --chain-config <network_name>\n\nFor OLAS_TOKEN payment mechs:\n\nmechx deposit token <amount> --chain-config <network_name> --token-type olas\n\nFor USDC_TOKEN payment mechs:\n\nmechx deposit token <amount> --chain-config <network_name> --token-type usdc\n\nNote: The --token-type parameter is required and must be explicitly specified (olas or usdc).\n\nIn all cases above, <amount> must be at least the mech's price (as given by maxDeliveryRate).\n\nOption 2: Per-request payment (for NATIVE, OLAS_TOKEN, USDC_TOKEN mechs)\n\nThe client handles per-request payment automatically when you don't use --use-prepaid:\n- NATIVE mechs: Native tokens sent with transaction\n- OLAS_TOKEN mechs: OLAS tokens approved and transferred\n- USDC_TOKEN mechs: USDC tokens approved and transferred\n\nOption 3: NVM Subscriptions (for NATIVE_NVM, TOKEN_NVM_USDC mechs)\n\nPurchase a subscription upfront for unlimited requests:\n\nmechx subscription purchase --chain-config <network_name>\n\nThis purchases a fixed-price subscription (ERC1155 NFT) that enables multiple requests during the subscription period. No per-request payment needed.\n\nNote: To use a custom private key file path, add the --key <path> option to any command.\n\n1. 2. 3. Finding the response\n\nAfter sending a request, a JSON response will appear below the line \"Data for agent\". The key \"result\" in this JSON object contains the Mech's response to your request.\n\nFor example, the following command:\n\nmechx request --prompts \"write a short poem\" --tools openai-gpt-3.5-turbo --chain-config gnosis --priority-mech <mech_address>\n\nYou should receive a response as follows:\n\n{\n\"requestId\": 123456789,\n\"prompt\": \"write a short poem\",\n\"tool\": \"openai-gpt-3.5-turbo\",\n\"result\": \"Beneath the velvet night so deep,\\nWhere stars their silent vigil keep,\\nA whisper of the wind goes by,\\nAs moonbeams dance across the sky.\",\n\"metadata\": {}\n}\n\nTroubleshooting: timeout waiting for response\n\nFor some Mechs, the response may take a few minutes to arrive. If you encounter timeout issues, ensure you have a reliable RPC provider configured:\n\nexport MECHX_CHAIN_RPC=<your_rpc_url>\n\nIf the connection times out, you can retrieve the response manually. To do this:\n\nNote the request_id printed in the logs.\n\nConvert the request ID to hexadecimal:\n\nprintf \"%x\\n\" <request_id>\n\nGo to the Mech list and locate your Mech (by its AI Agent ID or address).\n\nClick on the Mech’s address to see a list of requests it has received.\n\nFind your request by matching the hexadecimal request ID.\n\nClick on \"Delivers Data\" to view the response.\n\nTroubleshooting: non-hexadecimal symbol\n\nYou may encounter an error indicating that the private key contains invalid (non-hexadecimal) characters.\nThis can happen, in particular, on Windows systems, where some IDEs may automatically add a newline character (\\n) at the end of a file—for example, in ethereum_private_key.txt.\n\nTo avoid this, check your IDE settings and ensure that the file contains only the private key with no trailing newline or whitespace.\n\nTroubleshooting: out of gas\n\nIf an \"Out of gas\" error is encountered, an increase of the gas limit can solve the problem. To do this:\n\nexport MECHX_GAS_LIMIT=200000\n\n1. 3. Script for automatizing request sending\n\nThe following script can be used in order to automatize request sending:\n\nfrom mech_client.marketplace_interact import marketplace_interact\n\nPRIORITY_MECH_ADDRESS = \"<priority_mech_address>\"\nPROMPT_TEXT = \"<prompt_text>\"\nTOOL_NAME = \"<tool_name>\"\nCHAIN_CONFIG = \"<network_name>\"\nAGENT_MODE = False # Set to True if using agent mode\nSAFE_ADDRESS = \"\" # Required if AGENT_MODE is True\nUSE_OFFCHAIN = False\n\nresult = marketplace_interact(\nprompts=(PROMPT_TEXT,), # Note: must be a tuple\npriority_mech=PRIORITY_MECH_ADDRESS,\nagent_mode=AGENT_MODE,\nsafe_address=SAFE_ADDRESS,\nuse_offchain=USE_OFFCHAIN,\ntools=(TOOL_NAME,), # Note: must be a tuple\nchain_config=CHAIN_CONFIG\n)\n\nReplace the placeholders as follows:\n\n<priority_mech_address>: the address of the targeted Mech,\n\n<prompt_text>: the text of the prompt to send,\n\n<tool_name>: the name of the tool to use,\n\n<network_name>: the name of the target network (e.g., \"gnosis\", \"base\").\n\nNote: If using agent mode (AGENT_MODE = True), you must provide a valid SAFE_ADDRESS. For client mode, set AGENT_MODE = False and SAFE_ADDRESS = \"\".\n\nThe variable result contains the response of the mech.\n\n2. Tool Management\n\nList tools available for a mech\n\nTo list the tools available for a specific marketplace mech, use the tool list command with an AI Agent ID:\n\nmechx tool list 1722 --chain-config gnosis\n\n+---------------------------------------------+-----------------------------------------------+\n| Tool Name | Unique Identifier |\n+=============================================+===============================================+\n| claude-prediction-offline | 1722-claude-prediction-offline |\n+---------------------------------------------+-----------------------------------------------+\n| claude-prediction-online | 1722-claude-prediction-online |\n+---------------------------------------------+-----------------------------------------------+\n| deepmind-optimization | 1722-deepmind-optimization |\n+---------------------------------------------+-----------------------------------------------+\n\nGet tool description\n\nTo get the description of a specific tool, use the tool describe command with the tool's unique identifier:\n\nmechx tool describe 1722-openai-gpt-4 --chain-config gnosis\n\nDescription for tool 1722-openai-gpt-4: Performs a request to OpenAI's GPT-4 model.\n\nGet tool input/output schema\n\nTo get the input/output schema of a specific tool, use the tool schema command:\n\nmechx tool schema 1722-openai-gpt-4 --chain-config gnosis\n\nTool Details:\n+------------------------+---------------------------------------------+\n| Tool Name | Tool Description |\n+========================+=============================================+\n| OpenAI Request (GPT-4) | Performs a request to OpenAI's GPT-4 model. |\n+------------------------+---------------------------------------------+\nInput Schema:\n+-------------+-----------------------------------------------+\n| Field | Value |\n+=============+===============================================+\n| type | text |\n+-------------+-----------------------------------------------+\n| description | The request to relay to OpenAI's GPT-4 model. |\n+-------------+-----------------------------------------------+\nOutput Schema:\n+-----------+---------+-----------------------------------+\n| Field | Type | Description |\n+===========+=========+===================================+\n| requestId | integer | Unique identifier for the request |\n+-----------+---------+-----------------------------------+\n| result | string | Response from OpenAI |\n+-----------+---------+-----------------------------------+\n| prompt | string | User prompt to send to OpenAI |\n+-----------+---------+-----------------------------------+\n\n3. Offchain Requests\n\nThe offchain URL is automatically discovered from the mech's on-chain metadata. No additional configuration is required — simply use the --use-offchain flag:\n\nmechx request --prompts \"test\" --tools openai-gpt-4 --use-offchain --chain-config gnosis\n\nThe client queries the mech's ComplementaryServiceMetadata contract to find the url field published by the mech operator, then sends requests to that endpoint.\n\n4. Programmatic Usage\n\nYou can use the Mech Client as a library in your Python project:\n\nfrom mech_client.services import MarketplaceService\nfrom mech_client.domain.payment import PaymentType\nfrom mech_client.infrastructure.config import get_mech_config\nfrom aea_ledger_ethereum import EthereumApi, EthereumCrypto\n\n# Configuration\nPRIORITY_MECH_ADDRESS = \"0x77af31De935740567Cf4fF1986D04B2c964A786a\"\nPROMPT_TEXT = \"Will Gnosis pay reach 100k cards in 2024?\"\nTOOL_NAME = \"openai-gpt-4o-2024-05-13\"\nCHAIN_CONFIG = \"gnosis\"\nMODE = \"client\" # Use \"agent\" for agent mode (Safe multisig)\nSAFE_ADDRESS = \"\" # Required if MODE is \"agent\"\n\n# Setup ledger and crypto\nconfig = get_mech_config(CHAIN_CONFIG)\ncrypto = EthereumCrypto(\"ethereum_private_key.txt\")\nledger_api = EthereumApi(**config.ledger_config.__dict__)\n\n# Create service\nservice = MarketplaceService(\nchain_config=CHAIN_CONFIG,\nledger_api=ledger_api,\npayer_address=crypto.address,\nmode=MODE,\nsafe_address=SAFE_ADDRESS if MODE == \"agent\" else None,\n)\n\n# Send request\nresult = service.send_request(\npriority_mech=PRIORITY_MECH_ADDRESS,\ntools=[TOOL_NAME],\nprompts=[PROMPT_TEXT],\npayment_type=PaymentType.NATIVE, # or PaymentType.TOKEN, PaymentType.NATIVE_NVM\n)\n\nprint(f\"Transaction hash: {result['tx_hash']}\")\nprint(f\"Request ID: {result['request_ids'][0]}\")\nprint(f\"Result: {result.get('result')}\")\n\nYou can also programmatically fetch tools for marketplace mechs:\n\nfrom mech_client.services import ToolService\nfrom mech_client.infrastructure.config import get_mech_config\nfrom aea_ledger_ethereum import EthereumApi\n\n# Configuration\nservice_id = 1722\nchain_config = \"gnosis\"\n\n# Setup ledger API\nconfig = get_mech_config(chain_config)\nledger_api = EthereumApi(**config.ledger_config.__dict__)\n\n# Create tool service\ntool_service = ToolService(\nchain_config=chain_config,\nledger_api=ledger_api,\n)\n\n# Fetch tools for a specific marketplace mech\ntools = tool_service.list_tools(service_id=service_id)\nprint(f\"Tools for marketplace mech {service_id}:\")\nfor tool_name, tool_id in tools:\nprint(f\" {tool_name}: {tool_id}\")\n\n5. Chain Configuration\n\nDefault configurations for different chains are stored in mech_client/configs/mechs.json. You can override any configuration parameter by exporting the following environment variables:\n\nMECHX_CHAIN_RPC # Custom RPC endpoint\nMECHX_SUBGRAPH_URL # Custom subgraph URL (optional, defaults provided)\nMECHX_GAS_LIMIT # Custom gas limit\nMECHX_TRANSACTION_URL # Custom transaction explorer URL\n\nMECHX_LEDGER_CHAIN_ID\nMECHX_LEDGER_POA_CHAIN\nMECHX_LEDGER_DEFAULT_GAS_PRICE_STRATEGY\nMECHX_LEDGER_IS_GAS_ESTIMATION_ENABLED","tokens":4764,"crawled_at":1791192746253}
+{"id":10141,"url":"https://a16zcrypto.com/team/sam-blackshear","domain":"a16zcrypto.com","chapter":"research","title":"Sam Blackshear - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nSam Blackshear\n\nFeed\nFilter\n(1)\nclear filters\n\ncategory\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\nrecommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nauthor\n(1) all authors\n@x0rart\n1337 Skulls Sers\na16z crypto\na16z crypto editorial\na16z crypto policy & regulatory teams\na16z crypto Regulatory Team\nAaditya Shidham\nAaron Levie\nAaron Phillips\nAaron Schnider\nAbby Green\nAbdou Ndiaye\nAbhi Shelat\nAbhiram Kothapalli\nAbigail Johnson\nAdam Alter\nAdam Back\nAdam Bry\nAdam Grant\nAdam Ludwin\nAdam Martin\nAdam Thierer\nAdam Zuckerman\nAdela Tomsejova\nAdena Friedman\nAdena Hefets\nAdeniyi Abiodun\nAdina Fischer\nAdrian Cockcroft\nAdrian Fenty\nAdrienne Mayor\nAgostino Capponi\nAiden Slavin\nAileen Lee\nAisha Stephenson\nAJ Shankar\nAlan Knott-Craig\nAlan Schaaf\nAlana Benton\nAlbert Tang\nAlec Nielsen\nAlec Ross\nAlejandro Flores\nAlex Constantinople\nAlex Honnold\nAlex Hutchinson\nAlex Immerman\nAlex Kreitz\nAlex Kroeger\nAlex Le\nAlex Masmej\nAlex Morcos\nAlex Price\nAlex Pruden\nAlex Rampell\nAlex Roetter\nAlex Solomon\nAlex Spector\nAlex Stamos\nAlex Tabarrok\nAlexander (Sasha) Spiegelman\nAlexander Chia\nAlexander Zoppa\nAlexandra Chang\nAlexandria Lafci\nAlexis Lakes\nAlexis Madrigal\nAlexis Ohanian\nAli Ghodsi\nAli Yahya\nAlicia Barone\nAlin Tomescu\nAlisha Litman\nAlison Mangiero\nAlison Martin\nAllison Pickens\nAlyssa Del Bene\nAlyssa Torres\nAmanda Cantor\nAmanda Cassatt\nAmanda Catherine\nAmanda Mulay\nAmanda Tuminelli\nAmanda Tyler\nAmelia Salyers\nAmie Tyrrel\nAmir Shevat\nAmira Yahyaoui\nAmy Abernethy\nAmy Berliner\nAmy Bohutinsky\nAmy Choice\nAmy Cray\nAmy Gill\nAmy Hoemeke\nAmy Kalokerinos\nAmy Robertson\nAna Mostarac\nAna Susi\nAnatoly Yakovenko\nAndie Taylor\nAndisheh Tahriri\nAndre Iguodala\nAndrea Clarke Hall\nAndrea Feinberg\nAndrea Rallo\nAndrea Simon\nAndrea Vinkler\nAndreas Papadimitropoulos, Jr\nAndreessen Horowitz\nAndrew Allen\nAndrew Chen\nAndrew F. Read\nAndrew Green\nAndrew Hall\nAndrew Lakis\nAndrew Lewis-Pye\nAndrew Lo\nAndrew Mason\nAndrew McAfee\nAndrew Milson\nAndrew Omori\nAndrew Radin\nAndrew Rubin\nAndrew Savage\nAndrew Smith\nAndrew Tretyakov\nAndy Beal\nAndy Coravos\nAndy Golden\nAndy Hill\nAndy Milenius\nAndy Rachleff\nAndy Tran\nAndy Walshe\nAneel Lakhani\nAngela Schenone\nAngela Strange\nAngela Tran Kingyens\nAngelica Gehr\nAniket Kate\nAnil Sethi\nAnish Acharya\nAnn Winblad\nAnna Berces\nAnna Jablonski\nAnna Semenova\nAnna Van Meurs\nAnnaLee Saxenian\nAnne Brandes\nAnne Lee Skates\nAnne Lewandowski\nAnne Mitchell\nAnne Yip\nAnnie Collins\nAnnie Duke\nAnthony Albanese\nAnthony Atala\nAnthony Foxx\nAnthony Lee Zhang\nAntonio Viggiano\nAntwone Stigall\nAnu Hariharan\nApril Roth\nAri Emanuel\nAri Juels\nArianna Huffington\nArianna Simpson\nArik Kershenbaum\nArmon Dadgar\nArnie Goldberg\nArsho Avetian\nArthur Brooks\nArun Sundararajan\nAsh Ashutosh\nAsha Christian\nAshley McCollum\nAshley Stern\nAshton Carter\nAtif Mian\nAtul Butte\nAubree Pelaez\nAubrey de Grey\nAugusto Marietti\nAurora Petracca\nAusten Allred\nAustin Guzman\nAustin Marchese\nAustin Wilson\nAva Iravani\nAvery Segal\nAvinash Solanky\nAviv Zohar\nAye Moah\nAzeem Azhar\nBailey Flanigan\nBailey Richardson\nBalaji Srinivasan\nBarry McCarthy\nBart Dessaint\nBeau Cronin\nBeau Woods\nBecky Pferdehirt\nBen Buckwalter\nBen Fielding\nBen Fisch\nBen Gardner\nBen Gomez\nBen Horowitz\nBen Kaufman\nBen Leventhal\nBen Lovell\nBen Napier\nBen Portney\nBen Rubin\nBen Scharfstein\nBen Schecter\nBen Silbermann\nBen Uretsky\nBen Wu\nBenedict Evans\nBenedikt Büenz\nBenjamin Ebner\nBenjamin Hindman\nBenjamin Wittes\nBenjamin Wu\nBennett Carroccio\nBenny Pinkas\nBernard J. Tyson\nBernard Tyson\nBeth Newman\nBethany Coates\nBharat Ramamurti\nBharath Ramsundar\nBill Carr\nBill Frist\nBill Hinman\nBill Janeway\nBill Krause\nBill Macaitis\nBlake Kim\nBlake Masters\nBlake Saari\nBlayne Donnell\nBob Iger\nBob Langer\nBob Moore\nBob Muglia\nBob Sutton\nBob Swan\nBob Tinker\nBob Wachter\nBobby Franklin\nBobby Green\nBobby Kotick\nBobby Wagner\nBoris Sofman\nBoris Wertz\nBrad Feld\nBrad Kern\nBrad Peterson\nBram Cohen\nBrandon Ballinger\nBrandon Barros\nBrandon Cherry\nBrandon Millman\nBrenda Kopf\nBrent McIntosh\nBrett Browman\nBrett Falk\nBrett Hagler\nBrewster Kahle\nBrian Armstrong\nBrian Balfour\nBrian Brooks\nBrian Crnkovich\nBrian Curran\nBrian Grazer\nBrian Koppelman\nBrian McCullough\nBrian Quintenz\nBrian Wilkins\nBridget McDowell\nBrittany Lucas\nBrittney Burrows\nBrooke Sheresky\nBruce Friedrich\nBryan Caplan\nBryan Chiang\nBryan Cox\nBryan Crowley\nBryan Faust\nBryan Houser\nBryan Kim\nBryan Pellegrino\nCaitlin Glazebrook\nCaitlin Johnston\nCaitlin Roberson\nCal Turner Jr.\nCaleb Christian\nCameron Schuler\nCamila De Souza\nCarine Carmy\nCarissa Bilinski\nCarl Agnelli\nCarl Eschenbach\nCarl Narcisse\nCarl Pope\nCarlos Araya\nCarolina Gonzalez\nCaroline Friedman\nCaroline Goggins\nCaroline Horn\nCaroline Moon\nCarolyn Bertozzi\nCarra Wu\nCasey Graul\nCasey Neistat\nCasey Winters\nCassady Churchill\nCassie Faerber\nCecilia Marshall\nCeia Font\nChad Rigetti\nChandra Krintz\nCharles Goetz\nCharles Hubbard\nCharles Koch\nCharlie Keinath\nCharlie Warzel\nChattry Meas\nChelsea Komlo\nChelsea Padilla\nCheng Li\nChris Bennett\nChris Best\nChris Burniske\nChris Curran\nChris DeWolfe\nChris Dixon\nChris Granger\nChris Hauth\nChris Lyons\nChris Messina\nChris Milk\nChris Power\nChris Santa Maria\nChris Wanstrath\nChristian Cachin\nChristian Catalini\nChristian Crowley\nChristian Seifert\nChristina Hampp\nChristina Lopes\nChristina Mercando\nChristina Xu\nChristina Zeidan\nChristine Darden\nChristine Perham\nChristopher Giancarlo\nChristopher Lee\nChristopher Mims\nChristopher Nguyen\nChristopher Rippingham\nChristopher Schroeder\nChristy Hubbard\nCiamac Moallemi\nCindi Zhang\nCindy Tenner\nClaire Austin\nClaire Cain Miller\nClaire Kart\nClaudia Picanco\nClay Shirky\nClayton Christensen\nClayton Gardner\nClifford Woolf\nClint Delapaz\nColin Bryar\nColin Rom\nCollin McCune\nConner Lyons Brown\nConnie Chan\nConnie Guglielmo\nConnor McCarthy\nConnor Moyles\nCorban Bell\nCorey Hawkins\nCorey Waller\nCourtney Dettlinger\nCraig Naylor\nCraig Walker\nCristina Cordova\nCurt Funderburk\nCuy Sheffield\nD'Arcy Coolican\nDaejun Park\nDaisy Linden\nDaisy Wolf\nDaljeet Virdi\nDalton Turay\nDan Berkenstock\nDan Boneh\nDan Frommer\nDan Primack\nDan Romero\nDan Shapero\nDan Siroker\nDan Stein\nDan Warmenhoven\nDan Wendlandt\nDaniel Chao\nDaniel Chen\nDanielle Andrzejewski\nDanielle Clark\nDanielle Looymans\nDanielle Lussier\nDanielle Morrill\nDanielle Shea\nDanny Shader\nDaphne Koller\nDapper Dan\nDaren Matsuoka\nDarin Malter\nDarshan Shankar\nDas Rush\nDave Jagoda\nDave King\nDave Touretzky\nDavid Banks\nDavid Belden\nDavid Damato\nDavid Deming\nDavid George\nDavid Haber\nDavid Hollestelle\nDavid Kerr\nDavid Lee\nDavid Mack\nDavid Madden\nDavid Marcus\nDavid Olson\nDavid Oyelowo\nDavid Pierce\nDavid Reich\nDavid Rumsey\nDavid Schweikert\nDavid Sinclair\nDavid Sverdlov\nDavid Tse\nDavid Ulevitch\nDavid Weiden\nDawn Lepore\nDawn Nott\nDeborah Embaie\nDeena Elitreby\nDeepak Maram\nDenis Nazarov\nDenis Young\nDenise Gonzalez\nDerek Dolin\nDerek Thompson\nDerrick Harris\nDevin Finzer\nDevon Zuegel\nDiana Peña\nDiane Greene\nDick Costolo\nDieter Shirley\nDiishan Imira\nDiogo Monica\nDominic Shine\nDominique Reliford\nDon Duet\nDon Faul\nDorris O'Brien\nDoug Ducey\nDoug Folden\nDoug McCracken\nDouglas Argueta\nDozie Uche\nDrew Coffman\nDylan Field\nDylan Rhodes\nEd Felten\nEd Lynch\nEddie Lim\nEddy Lazzarin\nEdith Zimmerman\nEdward Perkins\nEdwin Poston\nEfrat Noy\nEhud Shapiro\nEileen Burbidge\nEileen Wu\nElad Gil\nElaine Fuchs\nElaine Shi\nElena Burger\nEli Dourado\nElisa Leonhardt\nEliza Oak\nElizabeth Gunn\nElizabeth Harkavy\nElizabeth May\nElizabeth Ocken\nElizabeth Stark\nElizabeth Weil\nEllen Tunoa\nEmile Petrone\nEmilio Torres\nEmily Graff\nEmily Hinsch\nEmily Keir\nEmily Oster\nEmily Westerhold\nEmma Janaskie\nEric Budish\nEric Dai\nEric Ries\nEric Thomas\nEric Topol\nEric Wu\nErica Schecter\nErik Brynjolfsson\nErik Kiser\nErik Torenberg\nErika Bracken\nErika Herrera\nErika Louie\nErin Grody Kingsley\nErin Murphy\nErin Tice\nErin Tonnar\nErin Winkler\nErtem Nusret Tas\nEsther Shinn\nEthan Bueno de Mesquita\nEthan Ferreira\nEthan Zuckerman\nEuan Ashley\nEugene Volokh\nEugene Wei\nEugenia Yee\nEula Takahashi\nEva Sakkas\nEvan Burfield\nEvan Osnos\nEvangelos Simoudis\nEzra Klein\nF. Gary Gray\nFabiola Godinez\nFabrizio Zilibotti\nFahad Saleh\nFarid Jiandani\nFei-Fei Li\nFelix Do\nFEWOCIOUS\nFiona Kennedy\nFiona Murray\nFlashrekt\nFlora Oliveira\nFlori Del Valle\nFlorian Leibert\nFoteini Baldimtsi\nFrancesca Gino\nFrank Chen\nFrank Wilczek\nFred Benenson\nFred Ehrsam\nFred Upton\nFred Wilson\nFreda Lewis-Hall\nFrederic Kerrest\nFuture Editorial\nGabby Dizon\nGabby Reece\nGabriel Otte\nGabriel Vasquez\nGaetan Barthelemy\nGarrett Biel\nGary Ang\nGary Reedy\nGary Wolf\nGaurav Banga\nGaurav Dhillon\nGaut\nGayle Tzemach Lemmon\nGeoffrey Woo\nGeorg Fuchsbauer\nGeorg Petschnigg\nGeorge Church\nGeorge Danezis\nGeorge Fraser\nGeraldine Chan\nGérard Cachon\nGerard Ryle\nGerri Elliott\nGerry Tsoukalas\nGia Scinto\nGil Elbaz\nGil Shafir\nGina Moon\nGina Neff\nGina Yocom\nGinger Liau\nGokul Rajaram\nGoldie Chang\nGrace Ellis\nGraham Allison\nGrant Gregory\nGrant Jordan\nGrant LaFontaine\nGrant Rabenn\nGray Kinsella\nGreg Bowman\nGreg Clayman\nGreg Linares\nGreg Loehmann\nGreg Lynn\nGreg Solano\nGreg Truesdell\nGreg Waldon\nGregory Allen\nGregory Mundis\nGretchen Bush\nGretchen McCulloch\nGuido Appenzeller\nGustav Söderström\nGustavo Garcia\nGuy Goren\nGuy Raz\nGuy Wuollet\nHaley Van Dyck\nHanna Aziz\nHannah Frankl\nHanne Winarsky\nHaoyuan Li\nHarmit Malik\nHarry Grieve\nHarry Shum\nHarry Wright\nHatim Shafique\nHayden Adams\nHeather Gwynn\nHeather Podesta\nHedi Samar\nHelen Stoddard\nHelen Su\nHemant Mohapatra\nHendrik Pretorius\nHenri Kor\nHerb Lin\nHerman Narula\nHilmar Pétursson\nHoang Nguyen\nHoward Wu\nIan Dutra\nIan Shannon\nIan Sharp\nIce Cube\nIlan Zechory\nIllia Polosukhin\nIlyas Khan\nIma Christian\nIman Abuzeid\nInsiya Lokhandwala\nIon Stoica\nIrvin Chan\nIsa Guardalabene\nIsaiah Lott\nIsh Verduzco\nIsil Dillig\nIstván András Seres\nIttai Abraham\nIttay Eyal\nIva Messy\nIvan Linscott\nIvor Horn\nJ.D. Moriarty\nJack Donahoe\nJack Soslow\nJackie McQuiston\nJackson David\nJacob Westphal\nJacquelyn Melinek\nJad Esber\nJad Naous\nJade Lai\nJade Raymond\nJae Gnazzo\nJai Ramaswamy\nJaimie Buss\nJak Kennedy\nJake Auchincloss\nJakob Uszkoreit\nJamal Mohammed\nJames Beshara\nJames Currier\nJames da Costa\nJames Gwertzman\nJames J. Collins\nJames Kissell\nJames L. Madara\nJames Loftus\nJames Rathmell\nJames Rogers\nJames Watters\nJames Wu\nJames Zou\nJamie Brandon\nJamie McGurk\nJamie Sullivan\nJamilla Hemeid\nJana Odehnal\nJane Doe\nJane Lippencott\nJane Suh\nJanelle De Los Santos\nJared Bricklin\nJared Furutani\nJared Georgakopoulos\nJared Polis\nJared Smith\nJase Wilson\nJason Franklin\nJason Liu\nJason Mayden\nJason Milionis\nJason Mitchell\nJason Mok\nJason Rosenthal\nJason Warner\nJason Yanowitz\nJay Bradner\nJay Conte\nJay Drain\nJay Komarneni\nJay Rughani\nJean Reilly\nJeanne Tsan\nJeff Amico\nJeff Benson\nJeff Clark\nJeff Cordova\nJeff Glueck\nJeff Hawkins\nJeff Jones\nJeff Jordan\nJeff Lawson\nJeff Lu\nJeff Nagashima\nJeff Stump\nJeff Weiner\nJeffrey Immelt\nJeffrey Kaditz\nJeffrey Katzenberg\nJeffrey Kindler\nJeffrey Low\nJeffrey Silverstein\nJeffrey Zirlin\nJen Bulawsky\nJen Kha\nJenna Walsh\nJenna Zucker\nJennifer 8. Lee\nJennifer Doudna\nJennifer Kodner\nJennifer Konde\nJennifer Li\nJennifer Mumford\nJennifer Tejada\nJennifer Young\nJenny Cieplak\nJens Ernstberger\nJensen Harris\nJeremy Clark\nJeremy England\nJeremy Zhang\nJesse Holmes\nJesse Pollak\nJesse Walden\nJessica Childs\nJessica Hansen\nJessica Keeler\nJessica Patton\nJessica Verrilli\nJewel Pi\nJez Humble\nJi Kim\nJianying Luo\nJim Gilliam\nJimmy Chen\nJimmy Soni\nJing Wang\nJing Zou\nJJ Yu\nJoachim Neu\nJodi Lynn\nJodie Lutkenhaus\nJoe Gebbia\nJoe Grundfest\nJoe Montana\nJoe Morrissey\nJoe Schmidt\nJoe Sullivan\nJoel de la Garza\nJoel Mokyr\nJoel Monegro\nJoel Spolsky\nJoey Burleson\nJohn China\nJohn Collison\nJohn Fawcett\nJohn Garcia\nJohn Gedmark\nJohn Hennessy\nJohn Koelliker\nJohn M. Jack\nJohn Markoff\nJohn Menna\nJohn O’Farrell\nJohn Riccitiello\nJohn Smesko\nJohn Stanfield\nJohn Thompson\nJohn William Hatfield\nJonah Peretti\nJonathan Bush\nJonathan Dotan\nJonathan Downey\nJonathan Lai\nJonathan Lim\nJonathan Lusthaus\nJonathan Weissman\nJonathan Wong\nJordan Mazer\nJordan Stankowski\nJorge Conde\nJorge Gomez\nJose Guardado\nJoseph Bonneau\nJoseph Okpaku\nJoseph Spisak\nJosh Arnold\nJosh Bloom\nJosh Kim\nJosh Williams\nJoshua Browder\nJoshua Gans\nJoshua Grimm\nJoshua Hix\nJoshua Levin\nJoshua Lu\nJoshua Schank\nJoshua Soto\nJosie Ma\nJoyce Park\nJR Rivers\nJT Evans\nJuan Benet\nJudene Small\nJudy Savitskaya\nJudy Smith\nJulia Grace\nJulia Kirby\nJulie Bornstein\nJulie Farnham\nJulie Johnson\nJulie Samuels\nJulie Yoo\nJuliet Grier\nJuliet Nyatta\nJuliette Morton\nJulius Zhang\nJustin Bailey\nJustin Bethune\nJustin Blau\nJustin Cunningham\nJustin Gregorius\nJustin Kahl\nJustin Kan\nJustin Larkin\nJustin Paine\nJustin Pettit\nJustin Roberts\nJustin Simcock\nJustin Thaler\nJustine Moore\nJutta Steiner\nJyoti Bansal\nJZ Young\nKabir Gill\nKabir Laroia\nKais Khimji\nKamala Harris\nKaren Dunn\nKaren Wooley\nKarina Sobieski\nKarl Floersch\nkarma (Daniel Reynaud)\nKarmacoma\nKarthik Rau\nKartik Nayak\nKate Darling\nKate Dellolio\nKate Kerames\nKatherine Boyle\nKatherine Minarik\nKatherine Rundell\nKatherine Schoebel\nKathryn McKinley\nKathy Liu\nKathy Yang\nKatia Ameri\nKatie Baynes\nKatie Haun\nKatie Hemmerling\nKaty DeWitt-Drew\nKaty Nelson\nKayvon Tehranian\nKeener Barnhorst\nKeller Medlin\nKeller Rinaudo\nKelly Cannon\nKelsey Chaplinsky\nKelsey Mellard\nKen Chong\nKen Coleman\nKen Kocienda\nKerry Ganim\nKesha Cash\nKevin Chou\nKevin Chu\nKevin Dulsky\nKevin Kelly\nKevin McKinley\nKevin Nishioka\nKevin O'Kane\nKevin Rose\nKevin Tan\nKevin Wu\nKevin Zollman\nKidSuper\nKieran Snyder\nKierston Gittens\nKiki Mavridis\nKim Enright\nKim Malone Scott\nKim Milosevich\nKim Stevenson\nKim Zetter\nKimberly Tan\nKindra Mason\nKira Poskanzer\nKira Song\nKirstin Arbide\nKirt McMaster\nKofi Ampadu\nKouki Harasaki\nKrista Anderson-Copperman\nKristen Fortney\nKristen Johansson\nKristen Kee\nKristin Sauchak\nKristin Thayer\nKristina Graci-deLuna\nKristina Shen\nKristine Lipscomb\nKristo Käärmann\nKrisztina Holly\nKunal Bahl\nKunle Olukotun\nKurt House\nKyle Russell\nLaird Hamilton\nLatasha\nLaura Arrillaga-Andreessen\nLaura Baller\nLaura Behrens Wu\nLaura Deming\nLaura Gravley\nLaura Johnson\nLaura Shores\nLaura Weidman Powers\nLauren Berson\nLauren Illovsky\nLauren Murrow\nLauren Richardson\nLauren Spragge\nLaurene Powell Jobs\nLawrence Levy\nLawrence Summers\nLeah Cassidy\nLee Kleinman\nLee Lefkowitz\nLeeAnn Caballero\nLeila Hay\nLeila Janah\nLenny Rachitsky\nLeslie Jaw\nLeslie Vosshall\nLester Chen\nLi Fan\nLi Fei-Fei\nLi Jin\nLiang Wu\nLilian King\nLily Liu\nLina Sergie Attar\nLinda Banuelos\nLinda Xie\nLinden Tibbets\nLing Ren\nLinlin Li\nLinxin Wen\nLioba Heimbach\nLisa Hawke\nLisa Lambert\nLisa Orr\nLisa Reilly\nLisa Rosano\nLizzy Anderson\nLJ Erwin\nLloyd Dean\nLoretta Sanchez\nLori Potter\nLuca Prosperi\nLuca Zanolini\nLuis Martinez\nLuis von Ahn\nLuke Wroblewski\nLydia Green\nLynda Gibson\nLynn Rudolph\nMadan Nagaldinne\nMaddison Masaeli\nMadeline Lancaster\nMaggie Hsu\nMaggie Leung\nMaggie Romero\nMahad Abedin\nMahesh Iyer\nMahesh Vellanki\nMahimna Kelkar\nMakiri Duckett\nMalinka Walaliyadde\nMallesh M. Pai\nMalloy Evans\nManas Punhani\nManny Luna\nMarc Andreessen\nMarc Andrusko\nMarc Benioff\nMarc Levinson\nMarci Barbera\nMarco Reuter\nMargaret Jen\nMargit Wennmachers\nMaria LaMagna Morales\nMarian Garvin\nMarianne Winkler\nMariano Sorgente\nMaricarmen Alvarez\nMariel Goldenstein\nMarigold Vu\nMarina Kusserow\nMario Gabriele\nMario Linares\nMarissa Bramlett\nMark Cranney\nMark Leslie\nMark McAndrew\nMark McClusky\nMárk Melczer\nMark Moore\nMark Regan\nMark Sendak\nMarkos Georghiades\nMarkus Covert\nMarkus Funk\nMartha Lane Fox\nMartin Casado\nMartin Fischer\nMarty Makary\nMarvin Ammori\nMarvin Zamora\nMary Pat Jordan\nMary-Catherine Lader\nMaryam Bahrani\nMason Hall\nMatei Zaharia\nMatt Abrahams\nMatt Billmann\nMatt Bornstein\nMatt Clifford\nMatt Flannery\nMatt Fleming\nMatt Gleason\nMatt Kaeberlein\nMatt Levine\nMatt Levy\nMatt Oberhardt\nMatt Shortal\nMatt Spence\nMatt Weinberg\nMatthew Colford\nMatthew Green\nMatthew Haughey\nMatthew McCullough\nMatthew Mills\nMatthew Olsen\nMatthew Rutter\nMatthew Stein\nMatthieu Hafemeister\nMaureen Lara\nMax Kesten\nMax Krohn\nMax Levchin\nMax Polyak\nMax Resnick\nMax Ventilla\nMaya Rahkonen\nMcPherson Moore\nMeaghan Hardy\nMeg Whitman\nMegan Holston-Alexander\nMegan Kristalyn\nMehdi Hasan\nMehul Mehta\nMel Williams\nMelanie Galang\nMelissa Liao\nMelissa Minor\nMelissa Wasser\nMellody Hobson\nMelody Latronico\nMeredith Donahue\nMia Gonzalez\nMia Mandich\nMicah Johnson\nMichael Beckerman\nMichael Blau\nMichael Brandt\nMichael Chan\nMichael Copeland\nMichael Dearing\nMichael Dell\nMichael Franklin\nMichael Garcia\nMichael J. Casey\nMichael J. Freedman\nMichael Killam\nMichael King\nMichael Lee\nMichael Leiter\nMichael Morell\nMichael Ostrovsky\nMichael Ovitz\nMichael Paulus\nMichael Raynor\nMichael Reed\nMichael Snyder\nMichael Temkin\nMichael Wee\nMichael Zhu\nMichel Del Buono\nMichel Feaster\nMichèle Flournoy\nMichele Griffin\nMichele Korver\nMichele Law\nMichelle Ervin\nMichelle Kelso\nMichelle Kung\nMichelle Mundy\nMichelle Shin\nMichelle Ufford\nMichelle Volz\nMichelle Wilson\nMichelle Winn\nMichelle You\nMike Curtis\nMike Haydon\nMike Hearn\nMike Jones\nMike Kasperzak\nMike Kelly\nMike King\nMike Lempres\nMike Manning\nMike Maples jr\nMike Masnick\nMike Matchett\nMike Paulus\nMike Sandwick\nMikeal Rogers\nMikey Dickerson\nMiles Jennings\nMilijana Curic\nMiller Whitehouse-Levine\nMinerva Munoz\nMinnie Ingersoll\nMinsun Pak\nMintu Turakhia\nMiranda Christ\nMo Shaikh\nMohammad Akbarpour\nMohsen Malayeri\nMolly Grace\nMonique McCambridge\nMorgan Beller\nMorgan Bender\nMurat Pak\nMuriel Bowser\nMurray Shanahan\nMy Pham\nNadia Asparouhova\nNadia Eghbal\nNaftali Harris\nNaithan Jones\nNanjira Sambuli\nNaomi Metzger\nNashid Braswell\nNassim Eddequiouaq\nNat Barling\nNatacha Crooks\nNatalia Carrera\nNatalie Bucher\nNatalie Taumoepeau\nNate Chang\nNate Lau\nNathalie Balaban\nNathan McCauley\nNathan Yoon\nNathaniel Gleicher\nNathaniel Popper\nNav Singh\nNazanin Daneshvar\nNeel Maitra\nNeha Narula\nNelson Perla-Ward\nNeveen Bader\nNicholas Christakis\nNicholas Pacilio\nNick Babaian\nNick McKeown\nNick Quah\nNick Tomaino\nNicki Locker\nNicole Conner\nNicole Forsgren\nNicole Irvin\nNicole Neuman\nNicole Stanners\nNiels Provos\nNigel Robinson\nNikhil Krishnan\nNina Suthers\nNir Eyal\nNitasha Tiku\nNitin Natarajan\nNitya Subramanian\nNkiru Balonwu\nNoah Citron\nNoah Feldman\nNoah Levine\nNoah Smith\nNoam Nisan\nNoemi Glaeser\nO’Shea Jackson Jr.\nOlaf Carlson-Wee\nOleg Rogynskyy\nOliver Hsu\nOlivia Moore\nOlivia Webb\nOmri Weinstein\nOoshma Garg\nOprah Winfrey\nOrion Hindawi\nOscar Menjivar\nP.J. Hasleton\nPablo Montagnes\nPacky McCormick\nPak\nPalmer Luckey\nPamela Anderson\nPamon Forouhar\nParag Khanna\nParijat Talkad\nParker Brown\nParker Conrad\nPatrice Peck\nPatrick Byrne\nPatrick Collison\nPatrick Conway\nPatrick McCorry\nPatrick McHenry\nPatrick O’Grady\nPatrick Rivera\nPatrick Sutton\nPaul Cafiero\nPaul Daugherty\nPaul Davison\nPaul Krugman\nPaul Vigna\nPaula Long\nPenny Pritzker\nPerri Chilton\nPete Buttigieg\nPeter Blackwood\nPeter Buisseret\nPeter Chan\nPeter Donnelly\nPeter Johnson\nPeter Lauten\nPeter Leeson\nPeter Levine\nPeter Ludwig\nPeter Rubin\nPeter Thiel\nPeter Wang\nPetra Garrett\nPhil Daian\nPhil Hathaway\nPhil Wong\nPhong Nguyen\nPorter Smith\npplpleasr\nPranav Garimidi\nPrasad Akella\nPrat Moghe\nPreethi Kasireddy\npunk6529\nPurnima Padmanabhan\nPyrs Carvolth\nQasar Younis\nQuang Dao\nQuinten Burgunder\nQuintus Kilbourn\nRachael Horwitz\nRachel Goslins\nRachel Jenkins\nRachel Kalmar\nRachel McIntyre\nRachel Steiner\nRahul Iyer\nRahul Vohra\nRajeev Singh\nRajeev Venkayya\nRam Palaniappan\nRamana Jonnala\nRati Gelashvili\nRaul Vazquez\nRavi Parimi\nRay Dalio\nRaymond Carreira\nRebecca Lewis\nRebecca Rettig\nReed Hastings\nRefik Anadol\nRegina Benjamin\nRenato Valdés Olmos\nReshma Saujani\nReshma Sohoni\nRex Salisbury\nRich Ezekiel\nRichard Green\nRichard Menger\nRichard Rosenblatt\nRick Young\nRidhima Ahuja\nRiyaz Faizullabhoy\nRob Goodman\nRob McElhenney\nRob Pardo\nRob Rhinehart\nRobbie Petersen\nRobbie Peterson\nRobert Alexander\nRobert Cottrell\nRobert Hackett\nRobert Kolker\nRobert Leshner\nRobert McNeely\nRobert Moreno\nRobert Siegel\nRobert Stromberg\nRobert Weber\nRobin Casey\nRobin Guo\nRobin Weisman\nRod Johnson\nRodrigo Ibarra Lopez\nRodrigo Pacheco\nRoger Dickey\nRoger Wattenhofer\nRoham Gharegozlou\nRohini Mukand\nRohit Bansal\nRoman Mars\nRoman Stanek\nRon Gill\nRon Lavi\nRon Rothblum\nRonald Evans\nRonnie Harris\nRosa Davila\nRosalind Rattan\nRose Legarda\nRoss Andersen\nRoss Shuel\nRostin Behnam\nRuben Gallego\nRuben Smith\nRuss Altman\nRuss Heddleston\nRuss Roberts\nRussell Davies\nRyan Allen\nRyan Caldbeck\nRyan Conde\nRyan Holloway\nRyan Hoover\nRyan McEntush\nRyan Petersen\nRyan Prescott\nRyan Sandler\nRyan Spoon\nRyan Tseng\nRyan Walsh\nRyan Ward\nRyan Wyatt\nSaar Tochner\nSachin Jain\nSafi Bahcall\nSagar Dhawan\nSaku Panditharatne\nSalem Vance\nSam Blackshear\nSam Broner\nSam Gerstenzang\nSam Ragsdale\nSam Thompson\nSam Williams\nSam Yam\nSamantha Gelt\nSamantha Langford\nSamantha Ludwig\nSamson Wu\nSamuel Arbesman\nSamuel Hammond\nSandra Samayoa\nSandy Jen\nSankaet Pathak\nSantiago Rodriguez\nSara Boesen\nSarah Fazal\nSarah Hamburg\nSarah Lumbard\nSarah Mascardo\nSarah Meiklejohn\nSarah Porter\nSarah Rebello\nSarah Wang\nSasha Stiles\nSatish Talluri\nSaurabh Ladha\nSavannah Cherry\nScott Clark\nScott Duke Kominers\nScott Gottlieb\nScott Hassan\nScott Kupor\nScott Rubin\nScott Shenker\nScott Tyler\nScott Walker\nScott Weiss\nSean Duffy\nSean Neville\nSebastian Oddo\nSeema Amble\nSeemay Chou\nSep Kamvar\nSergiu Pasca\nSeth Lobree\nSeth Sivak\nSeth Sternberg\nShai Bernstein\nShai Kopeld\nShaka Senghor\nShakil Khan\nShan Sinha\nShana Fisher\nShane Mac\nShane Parrish\nShangda Xu\nShannon (Stubo) Brayton\nShannon Barbour\nShannon Kelly\nShannon Schiltz\nShannon Snow\nShari Doherty\nSharon Chang\nShawn Conway\nSheela Krothapalli\nShellye Archambeau\nSherie James\nSherriAnn Cole\nShishir Mehrotra\nShonda Rhimes\nSid Gorham\nSigne Pierce\nSimon Denny\nSiqi Chen\nSonal Chokshi\nSophie Song\nSoubhik Deb\nSpencer Dinwiddie\nSpencer Howard\nSpencer Rascoff\nSreeram Kannan\nSreevidya Kasturil\nSri Kosuri\nSriram Krishnan\nSrivatsan Sridhar\nStacey Cunningham\nStacey Merrick\nStacia Murray\nStacy Brown-Philpot\nStacy D'Amico\nStacy Warner\nStefan McDonough\nSten Tamkivi\nStephane Bancel\nStephanie Anyanwu\nStephanie Cohen\nStephanie Doppelt\nStephanie Smith\nStephanie Watkins\nStephanie Zinn\nStephen Armanios\nStephen Wink\nStephenie Zhang\nSteve Buress\nSteve Cadigan\nSteve Cheney\nSteve Harvey\nSteve Kaczynski\nSteve McDermid\nSteve Smith\nSteve Zhao\nSteven Adair\nSteven Ebert\nSteven Johnson\nSteven Levy\nSteven Sinofsky\nStewart Butterfield\nStina Ehrensvärd\nStuart Luman\nStuart Russell\nSudip Chakrabarti\nSue Hager\nSuhail Doshi\nSukhinder Singh Cassidy\nSumeet Singh\nSumit Shah\nSungMo Park\nSunil Chokshi\nSurya Ganguli\nSusan B. Wilde\nSusan Mernit\nSusan Rice\nSusannah Fox\nSydney Paul\nTaavet Hinrikus\nTaggart Matthiesen\nTamzen Brewis\nTana Billingsley\nTarek Mansour\nTarun Chitra\nTauri Laws Phillips\nTawny Holguin\nTaylor McFadden\nTed Not Lasso\nTed Sarandos\nTed Ullyot\nTerell Sterling\nTerence Carroll\nTeresa Carlson\nTerry Angelos\nTerry Brown\nThan Nguyen\nThanh Nguyen\nThe 2015 Academic Roundtable Sessions\nThe TxO team\nTheresa DeMichele\nTheresa Dilley\nTheresa Fisher\nTheresa Walz\nTheresia Gouw\nThibaut Scholasch\nThomas Gjerde\nThomas Juenger\nThomas Long\nThomas Rando\nTiffany Vo\nTiffany Zhong\nTim Beiko\nTim O'Reilly\nTim Roughgarden\nTim Schafer\nTim Sullivan\nTimmu Tõke\nTina Anderson\nTina Bhatnagar\nTina Ferguson\nTina Wie\ntinawie\nTing Ni\nTobi Lütke\nTodd Cranney\nTodd Lutwak\nTodd McKinnon\nTodd Park\nTodd Young\nTolga Dizdarer\nTom Butta\nTom Coates\nTom Davenport\nTom Ellis\nTom Hammer\nTom Hofmann\nTom Lehman\nTom Mitchell\nTom Preston-Werner\nTom Rikert\nTom Standage\nTomicah Tillemann\nTony Blair\nTony Blinken\nTori Landrum\nTracy Chou\nTracy Young\nTren Griffin\nTrent Mayol\nTrevor Bedford\nTristan Handy\nTristan Walker\nTroy Kirwin\nTugce Erten\nTurner Novak\nTushar Garg\nTyler Cowen\nTyler Wilson\nTyson Clark\nUma Valeti\nUsman Azam\nUzi Dutta\nValentina Marzorati\nValeria Nikolaenko\nValerie Arboleda\nVan Jones\nVan Le-Gray\nVanessa Kropf\nVas Narasimhan\nVaughn Ferguson\nVenkat Mocherla\nVicente De Baca\nVickie Casillas-Smith\nVictor Liang\nVictor Shoup\nVictoria Butcher\nVijay Balasubramaniyan\nVijay Kedar\nVijay Pande\nVineeta Agarwala\nVinod Khosla\nVirginia Postrel\nVishal Amin\nVitalik Buterin\nVivian Brooks\nVoices Onchain\nW. Brian Arthur\nWahab Owolabi\nWei Luo\nWendy Drpic\nWerner Gerola\nWes Taylor\nWhitney Owens\nWill Brown\nWill Wong\nWillem Mulder\nWilliam Gifford\nWilliam Mougayar\nWing Cheng\nXian Zhang\nXiang-Dong Fu\nXingchen Zhou\nYannai A. Gonczarowski\nYehuda Lindell\nYevgeniy Dodis\nYinuo Zhang\nYogi Roth\nYohei Ishii\nYoko Li\nYoni Levy\nYoram Novick\nYuichi Kurosawa\nYujin Chung\nYun Fan\nYung Yung Sheung\nYuval Efron\nYuval Harari\nZac Bookman\nZach Abrams\nZach Cohen\nZach Dicker\nZach Haigney\nZachary Chen\nZachary Gray\nZack Weiner\nZahabiya Gabaji\nZak Doric\nZal Bilimoria\nZane Lackey\nZeta Avarikioti\nZeya Yang\nZooko Wilcox\nZoran Basich\n\nclear all Sam Blackshear\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n01.30.23 / Sam Blackshear, Noah Citron, Eddy Lazzarin and Sonal Chokshi\nProgramming Languages & Crypto\nEPISODE SUMMARY with @b1ackd0g @noahcitron @eddylazzarin @smc90 A wide-ranging conversation all about programming languages and crypto — for both existing blockchain & smart contract programmers, other non-web3 developers seeking to enter the space, and anyone interested in how programming languages evolve and come into existence (as well as in the intersection of language, code, and...\n\ncode & engineering\ninfrastructure\nopen source\npodcast\nprogramming\nsmart contracts\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":6911,"crawled_at":1791192753358}
+{"id":10142,"url":"https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/hyperevm/raw-hyperevm-block-data","domain":"hyperliquid.gitbook.io","chapter":"defi_protocols","title":"Raw HyperEVM block data | Hyperliquid Docs","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nBuilders running a non-validating node can index the HyperEVM using data written to ~/hl/data/evm_block_and_receipts . This data is written after committed blocks are verified by the node, and therefore has no additional trust assumptions compared to running the EVM RPC directly from the node itself.\nBuilders that wish to index the HyperEVM without running a node can use the S3 bucket: aws s3 ls s3://hl-mainnet-evm-blocks/ --request-payer requester.\nThere is a similar bucket s3://hl-testnet-evm-blocks/ for testnet.\nBuilders interested in robustness can merge the two data sources, relying primarily on local data and falling back to S3 data.\nSome potential applications include a JSON-RPC server with custom rate limits, a HyperEVM block explorer, or other indexed services and tooling for builders.\nWhile the data is public for anyone to use, the requester must pay for data transfer costs. The filenames are predictably indexed by EVM block number, e.g. s3://hl-mainnet-evm-blocks/0/6000/6123.rmp.lz4. An indexer can copy block data from S3 on new HyperEVM blocks. The files are stored in MessagePack format and then compressed using LZ4.\nNote that testnet starts with directory s3://hl-testnet-evm-blocks/18000000and the earlier testnet RPC blocks were not backfilled.\nAn example can be found in the Python SDK: https://github.com/hyperliquid-dex/hyperliquid-python-sdk/blob/master/examples/evm_block_indexer.py\n\nPreviousDual-block architecture\nNextInteracting with HyperCore\n\nLast updated 8 months ago","tokens":401,"crawled_at":1791192762690}
+{"id":10143,"url":"https://gov.uniswap.org/t/rfc-hook-manager-framework-on-chain-policy-orchestration-for-uniswap-v4/25552","domain":"gov.uniswap.org","chapter":"governance_daos","title":"[RFC] Hook Manager Framework – On-Chain Policy Orchestration for Uniswap v4 - Requests for Comment - Uniswap Governance","text":"[RFC] Hook Manager Framework – On-Chain Policy Orchestration for Uniswap v4\n\nRequests for Comment\n\nmbendary\n\nMay 2, 2025, 11:04pm\n\n1\n\nInitial Request for Comment. No Governance action required at this time.\n\nMotivation\n\nUniswap Protocol v4 arrived with a bang—ushering in unprecedented flexibility via hooks, singleton architecture, and flash accounting. It’s a powerful toolkit, opening doors not just for optimized token swaps, but for a universe of on-chain value exchange: complex financial products, Real-World Assets (RWAs), and institutional-grade DeFi.\n\nBut with great power comes great complexity.\n\nHow do we safely harness v4’s power for sophisticated use cases? How do we implement custom logic—compliance checks, pricing rules, risk controls—without creating a fragmented, unauditable mess of ad-hoc hooks?\n\nThis RFC introduces a proposed solution: On-Chain Policy Orchestration Architecture, centered around a new infrastructure layer called the Hook Manager Framework.\n\nThe Problem: Raw Power Needs Structure\n\nImagine building a skyscraper out of LEGO—with no baseplate and no instructions. That’s what raw v4 hook usage feels like when attempting to support RWAs or institutional-grade logic.\n\nWhile every v4 hook executes atomically (a big leap over off-chain enforcement!), relying solely on ad-hoc, monolithic hook contracts leads to:\n\nFragmentation – Different pools implement similar logic differently.\n\nDuplication – Developers continually reinvent the wheel.\n\nSecurity Risk – Larger, multi-purpose hook contracts are harder to audit.\n\nTrust Gaps – DAOs and institutions cannot reliably verify or rely on arbitrary hooks deployed permissionlessly.\n\nThere’s a need for structure—one that preserves Uniswap’s neutrality while enabling robust pool-specific behavior.\n\nThe Solution: The Hook Manager Framework\n\nThe Hook Manager is a governance-aware orchestration layer attached to Uniswap v4 pools. It coordinates which policy-specific hooks execute, in what order, and under what conditions.\n\nKey Features:\n\nModular Policy Hooks\n\nEach custom behavior is implemented as a dedicated, single-purpose contract—e.g.,\n\nKYC/AML enforcement\n\nDynamic fees\n\nMEV protection\n\nRWA settlement logic\n\nOrchestration Logic\n\nThe Hook Manager attaches at pool creation and manages:\n\nWhich hooks execute on specific pool operations (before/after swap, mint, burn, etc.)\n\nExecution order of hooks\n\nDynamic registration/deregistration (via governance)\n\nStandard Interfaces\n\nHook contracts conform to a unified spec, making them easier to audit, monitor, and potentially reuse.\n\nControlled Upgrades\n\nThrough a decentralized governance model (proposed: using UNI), policy hooks can be upgraded while pools are paused—no liquidity migration required.\n\nTransparency & Observability\n\nHooks and managers emit standardized on-chain events for analytics, compliance audits, and real-time monitoring.\n\nImportantly, the Hook Manager does not modify Uniswap v4 core contracts—it builds on top of them, preserving neutrality and permissionlessness.\n\nWhy This Matters\n\nThis isn’t just a better way to manage hooks—it’s a foundational leap forward for Uniswap v4’s real-world adoption, introducing a scalable, modular, governance-aligned framework to extend Uniswap v4’s hook system into a generalized infrastructure for policy-governed liquidity pools.\n\nEnhanced Security\n\nModularity enables smaller, auditable hook contracts\n\nBugs are isolated; the blast radius of errors is reduced\n\nInstitutional Readiness\n\nEnables auditable KYC/AML enforcement, risk controls, escrow logic, etc.\n\nMakes Uniswap pools usable by custodians, banks, and DAOs with specific mandates\n\nDeveloper Efficiency\n\nClear interfaces and modular design reduce complexity, accelerate innovation, and improve testing workflows\n\nRegulatory Adaptability\n\nNeed to add a new compliance rule? Deploy a new policy hook without touching other logic\n\nCompetitive Agility\n\nNew features can be rapidly deployed via standalone hooks (e.g., slippage protections, dynamic pricing models)\n\nAddressing Trade-offs\n\nGas Costs\n\nYes—each policy hook adds gas. But:\n\nFor large trades (institutions, RWAs), the cost is trivial compared to the value of guarantees\n\nL2 deployments will greatly reduce overhead\n\nSelective policy exemption and optimization techniques are possible\n\nLiquidity Fragmentation\n\nThe framework leads to more pools—but fragmentation already exists across fee tiers, versions, and L2s.\n\nAggregators (e.g., 1inch) and smart routers already solve this\n\nFor policy-sensitive users, verifiability > slippage\n\nFit-for-purpose liquidity is the goal—not maximum depth\n\nWhy Not Use Frontends or Raw Hooks?\n\nFrontend rules are easily bypassed\n\nRaw hooks lack auditability, standardization, and trust guarantees\n\nThe Hook Manager introduces curation, policy discovery, and on-chain enforcement—all composable and transparent\n\nGovernance & Ecosystem Design\n\nDecentralized Governance (Proposed)\n\nGovernance over Hook Managers and registered hooks scoped via UNI token\n\nTiered voting – technical changes weighted toward developers; UX-impacting changes weighted toward users\n\nRoles:\n\nHook Developers – permissionless contract authors\n\nCurators – recommend and audit hooks for specific verticals (e.g., RWA, stablecoins, MEV)\n\nLicensing & Monetization\n\nBusiness Source License (BSL) for core components, with a permissive license transition after 1 year\n\nCommercial Licensing for enterprise usage (e.g., banks, custodians)\n\nShared Deployment Costs among institutions using the same policy set\n\nRebates/Credits for LPs who help bootstrap policy-enabled pools\n\nThis model aligns incentives while supporting open experimentation.\n\nVision: Beyond Token Swaps\n\nThe Hook Manager Framework helps Uniswap v4 evolve from “flexible DEX” into a universal value exchange substrate.\n\nIt provides the structure needed to support:\n\nInstitutional finance\n\nReal-world asset settlement\n\nVerticalized DeFi use cases\n\nCross-protocol integrations\n\nComposable compliance\n\nAll without compromising core Uniswap principles of neutrality, modularity, and permissionless innovation.\n\nFeedback Requested\n\nWe invite community feedback on the following:\n\nIs the Hook Manager framework directionally aligned with Uniswap v4’s architecture and goals?\n\nAre the trade-offs (e.g., gas, fragmentation) acceptable for the benefits?\n\nDoes the governance model appropriately balance decentralization and practical execution?\n\nAre there any blockers, risks, or implementation pitfalls that deserve more attention?\n\nResources\n\nFull Whitepaper (GitHub)\n\nAuthor: Mohamed ElBendary\n\nStatus: RFC (Request for Comment)\n\nDate: May 2 2025\n\n2 Likes\n\nTrial run a Technical Advisory Board (TAB)\n\nTrial run a Technical Advisory Board (TAB)\n\nilo_0x\n\nMay 7, 2025, 4:28pm\n\n2\n\nAs a protocol integrating v4 Hooks, fragmentation is a key issue for us. We love what v4 builders do, but are severly bottlenecked in which pools we can integrate due to the overgrowth of custom logic.\n\nSome context: Arcadia is the biggest ALM on Base with $11m TVL, providing management of clAMM pools through self-custodial EOAs. We’re working with L1.co’s biggest asset managers to onboard offchain capital to DeFi.\n\nCurrently, most production-ready v4 Hook protocols would require us to do dedicated smart contract work and audits for an integration. It’s basically the same work as integrating a whole new DEX.\n\nA framework to standardize v4 Hooks would drastically increase our capacity to integrate new pools, translating into more exposure for these pools to our users.\n\nGFXlabs\n\nMay 7, 2025, 4:58pm\n\n3\n\nHi @mbendary, We wanted to drop a quick comment to thank you for posting this idea. You have identified a valuable problem and suggested a thoughtful solution.\n\nWe’ll follow up once we have had a chance to consider the idea more!\n\nmbendary\n\nMay 7, 2025, 6:50pm\n\n4\n\nThis is exactly the kind of context that makes the pain point real—thank you for surfacing it.\n\nThe framework aims to streamline the discoverability of relevant, trusted hook contracts and reduce the DEX-level integration burden. It does this by enabling composable policy logic, shared coordination layers, and modular governance—without requiring duplicative work across similar-profile pools.\n\nWould welcome any feedback as you explore whether this might help Arcadia scale deeper into v4’s design space.\n\nThanks again for engaging so constructively—it’s a huge boost to see validation from a team actively operating at the edge of what v4 enables.\n\n1 Like\n\nmbendary\n\nMay 7, 2025, 7:20pm\n\n5\n\nHi @GFXlabs team, I appreciate you taking the time to acknowledge the proposal and signal interest—thank you.\n\nI’d welcome any feedback once you’ve had a chance to consider it more deeply—especially around how the proposed framework and curation surfaces might align (or not) with the broader governance priorities you’re thinking through. I believe scaling DeFi beyond native crypto depends on solving how v4 hooks are composed, coordinated, and governed.\n\nHappy to go deeper or walk through specific design choices if helpful. Appreciate the thoughtful presence the GFX team brings to the ecosystem.\n\n1 Like\n\nportergeer\n\nMay 12, 2025, 11:37pm\n\n6\n\nHey Mohamed, thank you so much for this thoughtful proposal addressing hook development structure in v4. We appreciate the clear identification of challenges around standardization, security, and institutional adoption. As we at the Uniswap Foundation have also been considering how to best ensure the success and growth of Uniswap v4, we wanted to provide some feedback to some of your questions at the end of the post.\n\nIs the Hook Manager framework directionally aligned with Uniswap v4’s architecture and goals?\n\nThe challenges you’ve identified are important to address. We believe a governance-managed orchestration layer may not fully align with v4’s architectural philosophy of permissionless innovation. Instead, we see these challenges being addressed by a decentralized ecosystem of builders and participants, competing for the best solutions.\n\nWe’re actively working on initiatives that address these same challenges through a decentralized approach:\n\nSecurity: The Uniswap Foundation Security Fund supports teams building with v4 with their hook audits. This program is a part of a grant from the UF to Areta who facilitate an auditor marketplace for hook teams.\n\nInstitutional Readiness: While not live yet, we are excited to share a grant around institutional hooks in the coming weeks, alongside a white paper of strong use cases.\n\nDeveloper Efficiency: The Uniswap Hook Incubator focuses on growing a diverse and decentralized developer ecosystem in a competitive environment. We have seen really strong teams, like Cork and Tenor Finance, emerge from the UHI.\n\nAdaptability: While upgradeability sounds beneficial, we believe immutability is a core strength, not a limitation.\n\nLooking Forward\n\nWe’re excited to see forum discussion about v4’s future through your proposal. Thank you again for kickstarting this conversation. We’d welcome further discussion on:\n\nAchieving standardization without centralized coordination\n\nSpecific institutional requirements needing better documentation\n\nSupporting developers in creating secure, reusable hooks without constraining innovation\n\nmbendary\n\nMay 14, 2025, 8:23pm\n\n7\n\nHey Porter and UF Team,\n\nThank you for your thoughtful response to the Hook Manager Framework proposal. I appreciate your recognition of v4 adoption challenges and your commitment to addressing them. After reflecting on your feedback, I’d like to clarify aspects of the proposal and demonstrate its fundamental alignment with Uniswap’s core principles of permissionless innovation.\n\nTL;DR:\n\nThe Hook Manager Framework (HMF) as an Opt-In Toolkit, Not Central Control: HMF is an optional developer toolkit enabling self-organized permissionlessness for complex use cases. It neither restricts raw v4 hook development nor imposes top-down governance.\n\nAddressing Real, Documented Problems: The framework tackles current, evidenced issues of hook fragmentation, security vulnerabilities (e.g., “36% vulnerable” per BlockSec research), and integration bottlenecks impacting builders like Arcadia and institutional onboarding.\n\nAligns with UF’s Signaled Values: The UF’s endorsement of community curation (e.g., “awesome-uniswap-hooks”) shows a shared goal for an organized ecosystem. HMF offers a robust, on-chain mechanism for opt-in achievement.\n\nStrategic Imperative for Uniswap v4: Given the competitive landscape (e.g. PancakeSwap Infinity to Uniswap v4 parity) and Uniswap v4’s BSL, HMF provides crucial systemic capabilities to build a stronger, differentiated ecosystem and maintain leadership.\n\nAdaptability & Immutability Balanced: HMF respects core protocol immutability while offering controlled, opt-in adaptability for policy layers—vital for global compliance, RWA needs, preventing fragmentation, and reducing fork incentives.\n\nOpen to Community-Driven Implementation: The proposal’s licensing/monetization details were illustrative; HMF is a public good for long-term ecosystem health, not a business venture. Implementation is open to community-aligned models.\n\nA Public Good for Ecosystem Health, Not a Business Venture\n\nBefore delving deeper, I want to address potential misinterpretations regarding licensing. The Hook Manager Framework’s primary goal is ecosystem health and enablement; it is envisioned as a public good for the Uniswap community.\n\nThe original whitepaper’s licensing and monetization details are illustrative of sustainability paths, not a rigid business venture. The framework can be implemented under various community-aligned models: as a fully open-source component, through Foundation grants, or via a DAO-governed structure. The suggested BSL approach with eventual open-sourcing mirrors Uniswap v4 itself, ensuring ecosystem benefit with reasonable initial protections. I am committed to finding an implementation path serving Uniswap’s values and governance preferences.\n\nAddressing Market Realities & Evidence of Problem Severity\n\nThe need for a more structured hook integration approach isn’t merely theoretical. As Arcadia Finance noted in their response to this RFC:\n\n“As a protocol integrating v4 Hooks, fragmentation is a key issue for us…severely bottlenecked…due to the overgrowth of custom logic… most production-ready v4 Hook protocols would require us to do dedicated smart contract work and audits for an integration. It’s basically the same work as integrating a whole new DEX.”\n\nThis feedback from a protocol “working with L1.co’s biggest asset managers to onboard off-chain capital to DeFi” highlights significant existing integration barriers. For institutions and asset managers, particularly those Arcadia helps onboard, a standardized policy-aware pool framework is a prerequisite for confident engagement.\n\nThe “awesome-uniswap-hooks” github repository (ora-io/awesome-uniswap-hooks), a community-maintained resource, details hook security vulnerabilities. Crucially, research highlighted there (by BlockSec) shows “36% of the hooks in this repository in one specific commit hash may be vulnerable to attacks.” This repository also catalogues dozens of specialized hook implementations—from oracle integration to compliance systems to cross-chain functionality. Such rapid, unstandardized proliferation exemplifies the fragmentation challenge HMF addresses. The community’s focus on educational resources and security best practices demonstrates recognition of complexity that standardized interfaces and curation could mitigate.\n\nFurther widespread challenges include:\n\nProliferation of Incompatible Hooks: Over 150 developed hooks (per Uniswap’s Jan 2025 blog) create a complex integration landscape.\n\nInstitutional Integration Complexity: The Uniswap Labs/Fireblocks collaboration highlighted integration challenges HMF would directly address.\n\nAcknowledged Hook Risks by Uniswap Labs: Uniswap Labs officially cautions users about third-party hooks, underscoring the need for solutions aiding standardization and trust.\n\nThis is not an isolated concern. Extensive community-documented security issues underscore the urgency for strategic solutions. The HMF proposal provides a foundational step, and we anticipate it will be complemented by other community-driven innovations.\n\nPermissionless Innovation Enhanced: Enabling Self-Organized Permissionlessness at Scale\n\nThe Hook Manager Framework is an opt-in toolkit augmenting v4’s permissionless foundation, enabling self-organized permissionlessness, not replacing core freedom:\n\nParallel Paths Preserved: Developers remain free to build directly against v4 core; HMF offers optional structure, similar to how OpenZeppelin contracts empower developers without restricting them.\n\nDeveloper-Driven Standards: Implementations emerge organically through developer adoption: similar to how npm packages become standards through utility, not mandate.\n\nCompetitive Framework Marketplace: The proposal envisions multiple Hook Manager implementations competing in an open marketplace, each with potentially different features, governance models, and focus areas—the very definition of permissionless competition.\n\nThe framework aims to reduce the coordination costs that inherently limit permissionless growth in complex systems, thereby preserving and even amplifying the innovation freedom that makes Uniswap powerful.\n\nWhy Now? Timing Considerations for Systemic Capabilities\n\nSome suggest it’s too early for structure. However, this early stage is precisely why a framework offering systemic capabilities for coordination and composability is timely:\n\nStandards are more effective early: Lightweight standardization now prevents incompatible approaches from becoming entrenched, avoiding costly retroactive fixes later, or being cornered into sub-optimal choices. The longer we wait, the more costly coordination becomes.\n\nExisting Integration Bottlenecks: Evidenced integration challenges due to fragmentation are already constraining growth today.\n\nCompetitive Window: PancakeSwap Infinity’s release (GPL 2.0) with v4 feature parity underscores Uniswap’s window to establish deeper, differentiated ecosystem advantages. Uniswap v4 BSL expires in June 2027. Uniswap’s sustainable leadership will depend on fostering superior developer experience, composability, and ecosystem cohesion. Addressing structural challenges now prevents ceding ground to competitors who might create more builder-friendly environments.\n\nRetroactively imposing structure is significantly harder. HMF provides just enough structure for cohesion to address scaling challenges without restricting innovation. It also provides a strong foundation for enduring competitiveness beyond protocol primitives through a thriving, composable, and efficient ecosystem.\n\nGlobal Compliance Reality: Building for Uniswap’s Actual User Base\n\nGiven that 90% of Uniswap users are based outside the U.S. (per Hayden Adams, Nov 2024), and with diverse global crypto regulations emerging (e.g., MENA), adaptable compliance is crucial. HMF provides the necessary systemic capabilities for pools to implement jurisdiction-specific compliance. Supporting global participation requires localized, adaptable policy enforcement. HMF allows DAOs and institutions to build and manage these solutions without fragmenting Uniswap’s core or incentivizing forks. Crucially, this enhances agility at the ecosystem level, which is essential for Uniswap’s continued global growth.\n\nImmutability and Adaptability: A Nuanced Balance\n\nWe respect immutability as the cornerstone preventing protocol stewards from creating walled gardens. The proposal has been misinterpreted as challenging this principle. In fact, it carefully preserves it while enabling controlled adaptability for opt-in policy layers:\n\nCore Protocol Immutability Preserved: HMF maintains Uniswap v4 core contract immutability and v4 hook attachment semantics.\n\nScoped and Governed Pausing: Pausing applies only to pools opt-in to a specific Hook Manager and requires governance by that scope—preserving broader protocol immutability.\n\nProtected Policy Evolution: When regulatory requirements change, opted-in policy hooks can adapt without requiring liquidity migration from those specific pools or protocol.\n\nThis nuanced approach recognizes that while immutability is invaluable for core logic, its universal application to dynamic policy enforcement can be a practical limitation, unnecessarily lowering the ceiling for ecosystem growth.\n\nMarket Selection with Purpose\n\nMarket forces drive adoption. However, they operate most efficiently within some structural baseline. HMF enhances market selection, by preserving competition on innovation while removing unnecessary integration friction:\n\nBy lowering integration barriers, the Hook Manager ensures a level playing field where developers compete on functionality, security, and value—accelerating adoption and expanding Uniswap’s composable ecosystem.\n\nIt accelerates organic standardization, reducing economic inefficiency, akin to Web3 token standards or oracle interfaces. HMF is a minimal coordination layer, much like standardized shipping containers revolutionized trade by making the process efficient, not dictating the cargo.\n\nInterestingly, the Uniswap Foundation has implicitly acknowledged the value of such organization. The “awesome-uniswap-hooks” repository notes: “Special thanks to Uniswap Foundation for including this resource in the official doc and mentioning this work in the blog!” This Foundation-endorsed community curation serves HMF’s fundamental purpose: organization, standardization, and quality guidance. HMF proposes formalizing and strengthening this with opt-in robust on-chain mechanisms, not just off-chain curation. This alignment suggests a shared goal for an organized, accessible hook ecosystem; we propose a more comprehensive technical implementation of what the Foundation already supports in principle.\n\nAligning with and Amplifying Foundation Initiatives\n\nThe Hook Manager Framework is designed not to compete with, but to synergize with and amplify the impact of the Uniswap Foundation’s valuable initiatives:\n\nSecurity Fund Enhancement: HMF promotes modular, single-purpose hooks adhering to the Single Responsibility Principle. Such hooks are inherently more cost-effective to audit, thereby multiplying the impact of the UF Security Fund and Areta’s marketplace by allowing resources to cover more ground or deeper analyses.\n\nInstitutional Hook Development: As the Foundation explores institutional hooks and use cases, HMF offers a robust, opt-in technical foundation and standardized patterns for their on-chain implementation. This provides the prerequisite structure for confident engagement by institutions requiring auditable and governable policy enforcement.\n\nHook Incubator Acceleration: For innovative teams emerging from the Hook Incubator, such as Cork and Tenor Finance, HMF can serve as an optional accelerator. By providing battle-tested patterns for orchestration and policy management, it allows these teams to focus on their unique value propositions rather than expending resources on rebuilding foundational infrastructure.\n\nMoving Forward: A Developer Toolkit, Not a Governance Layer\n\nThe Hook Manager Framework is fundamentally aligned with the Foundation’s goals for Uniswap v4: scaling permissionless innovation, strengthening ecosystem composability, and supporting sustainable growth. To bring clarity to the alignment with the Foundation’s vision for the ecosystem, I reframe the Hook Manager as:\n\nA Developer Toolkit: Simplifying complex orchestration, reducing duplication, enabling developers to focus on unique value, fostering self-organized permissionlessness.\n\nA Building Block for DAOs: Enabling DAOs to implement and govern their own policy enforcement without protocol-level changes.\n\nAn Ecosystem Protection Mechanism: Standardized interfaces reduce fork incentives, enrich the ecosystem with differentiated systemic capabilities, preserving Uniswap’s network effects and long-term growth.\n\nTo further these goals collaboratively, I would welcome the opportunity to:\n\nExplore how modular HMF components could directly support and enhance your initiatives without requiring wholesale adoption.\n\nI am particularly keen on identifying targeted institutional requirements where standardized interfaces would unlock more innovation, providing the prerequisite for confident engagement. I look forward to your upcoming whitepaper and am happy to serve as a reviewer.\n\nDevelop a simplified version focused on developer tooling aligned with your current approach.\n\nThank you for engaging with this proposal. It is a privilege to be part of the Uniswap community. I remain committed to Uniswap’s success and finding solutions balancing permissionless innovation with the maturing ecosystem’s practical needs.\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nEstablish Uniswap v4 Licensing Process\n\nGovernance-Meta\n\n3\n\n696\n\nApril 4, 2025\n\nBrief thoughts on how the DAO could grow\n\nUncategorized\n\n14\n\n888\n\nOctober 28, 2024\n\n[RFC] Native Execution Privacy in the Uniswap Interface via v4 Hooks and UniswapX\n\nRequests for Comment\n\n16\n\n705\n\nAugust 29, 2026\n\nAvantgarde Finance Delegate Platform\n\nDelegation Pitch\n\n32\n\n1063\n\nNovember 27, 2025\n\nScaling V4 and Supporting Unichain\n\nRequests for Comment\n\n52\n\n3332\n\nSeptember 29, 2025","tokens":6373,"crawled_at":1791192772015}
+{"id":10144,"url":"https://a16zcrypto.com/posts/podcast/programming-languages-crypto","domain":"a16zcrypto.com","chapter":"research","title":"Programming Languages & Crypto - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nProgramming Languages & Crypto\nSam Blackshear, Noah Citron, Eddy Lazzarin, and Sonal Chokshi\n01.30.23\n\nTags & Share Tags\ncode & engineering\ninfrastructure\nopen source\npodcast\nprogramming\nsmart contracts\ntech trends\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nEPISODE SUMMARY\n\nwith @b1ackd0g @noahcitron @eddylazzarin @smc90 A wide-ranging conversation all about programming languages and crypto — for both existing blockchain & smart contract programmers, other non-web3 developers seeking to enter the space, and anyone interested in how programming languages evolve and come into existence (as well as in the intersection of language, code, and expression). The discussion covers differences (and similarities) in conventional programming languages vs. smart contract programming; debates the unique constraints (and opportunities) of blockchains; and also touches on topics such as formal verification, governance & community, tooling, cross-platform adaptation, and much much more… but also the history, ebbs, and flows of traditional programming to today.\n\nEPISODE NOTES\n\nwith @b1ackd0g @noahcitron @eddylazzarin @smc90\n\nThis episode is all about programming languages and crypto — and it’s for both existing blockchain & smart contract programmers, and also other non-web3 developers seeking to enter the space… and, for anyone who is just curious about how programming languages evolve and come into existence (as well as interested in the intersection of language, code, and expression!)\n\nIt’s a fun and fascinating ride, because we cover everything from differences (and similarities) in conventional programming languages vs. smart contract programming; discuss and debate the unique constraints (and opportunities) of blockchains; and also touch on topics such as formal verification, governance & community, tooling, cross-platform adaptation, and much much more… But we also dig into with the history, ebbs, and flows of traditional programming to today.\n\nOur guests in this episode, in conversation with Sonal Chokshi, include:\n\nSam Blackshear — co-founder and CTO of Mysten Labs (which is building foundations for the decentralized future of web3); Sam has a long history in programming languages from his PhD to working at Facebook (and Libra/Diem) to creating and being one of the authors of Move, an open-source programming language for building smart contracts;\n\nNoah Citron, smart contract & research engineer here at a16z crypto (who also recently authored a light client for Ethereum called Helios, and, won a challenging gas-optimization challenge with another partner here); and\n\nEddy Lazzarin, head of engineering for a16z crypto; before that, Eddy was in software engineering at Netflix, as well as data engineering and data science at Facebook.\n\nAs a reminder, none of this is investment, business, legal, or tax advice; please see a16z.com/disclosures for more important information – including, a link to a list of our investments.","tokens":773,"crawled_at":1791192773532}
+{"id":10145,"url":"https://stack.olas.network/demos/hello-world","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Hello World - Olas Stack Developer Documentation","text":"Hello World\n\nThe Hello World AI agent provides an overview of the main components of an AI agent and how they work together. The goal of this AI agent is to help new users of Open Autonomy understand how the components of an AI agent work. While the AI agent itself is very simple, it demonstrates common features found in many AI agents and can be used as a starting point for building your own AI agent with more complex functionalities.\n\nArchitecture of the demo+\n\nThe demo is composed of:\n\n4 Docker containers implementing the 4 agent instances of the AI agent (abci0, abci1, abci2, abci3), and\n\n4 Docker containers implementing a Tendermint node for each agent instance (node0, node1, node2, node3).\n\nThe agent instances connect to the remote DRAND service through the Internet during the execution\nof the demo.\n\nHello World AI agent demo architecture with four agent instances\n\nRunning the demo\n\nYou can find the instructions on how to run the Hello World AI agent in the quick start guide.\n\nIf you have set up the framework, you can fetch the source code of the Hello World AI agent:\n\nautonomy fetch valory/hello_world:0.1.0:<hash> --alias hello_world_agent\n\nand the Hello World AI agent:\n\nautonomy fetch valory/hello_world:0.1.0:<hash> --service --alias hello_world_service\n\nDetails of the demo\n\nThe functionality of the AI agent is extremely simple. Namely, each agent instance will output at different times a HELLO_WORLD! message on their local console. The execution timeline is divided into periods, and within each period, only a nominated agent instance(keeper) will print the HELLO_WORLD! message. The other agent instances will just print a neutral face :|.\n\nInfo\n\nIn the context of AI agent, you can think of a period as an interval where the service executes an iteration of its intended functionality (e.g., checking some price on a market, execute an investment strategy, or in this demo, printing a message).\n\nRecall that agent instances synchronize their state using the consensus gadget. For clarity, we will simplify the consensus gadget infrastructure (the consensus gadget nodes plus the consensus gadget network) in a single green box.\n\nA simplified view of the Hello world AI agent architecture\n\nImportant\n\nEvery AI agent is connected to the consensus gadget through its consensus gadget node:\n\nThe consensus gadget is the component that makes possible for the agent instances to synchronise state data. This allows them to, e.g. reach agreement on certain actions or reconcile information.\n\nAnything happening at the consensus network level is completely abstracted away so that developers can see it as a given functionality. An application run by the AI agent can be thought and developed as a single \"virtual\" application, and the framework will take care of replicating it.\n\nCurrently, the consensus gadget is implemented using Tendermint.\n\nThis is what the AI agent execution looks like:\n\nHello World AI agent in action\n\nThe main questions that we try to answer in the sections below are:\n\nWhat are the main components of the Open Autonomy framework to implement an AI agent?\n\nHow do these components work?\n\nThe FSM of the AI agent\n\nAs discussed in the overview of the development process, the first steps when designing an AI agent are draft the AI agent idea and define the FSM specification that represents its business logic. This is a representation of the Hello World AI agent FSM:\n\nDiagram of individual operations of the Hello World AI agent\n\nThese are the states of the AI agent:\n\nRegistration. This is a preliminary state where each agent instance commits to participate actively in the AI agent.\n\nCollectRandomness. All agent instances connect to the DRAND remote service and retrieve the latest published random value.\n\nSelectKeeper. Using that random value as seed, the agent instances nominate randomly an instance (keeper) to execute the AI agent action.\n\nPrintMessage. The keeper executes the main action of the AI agent: prints the HELLO_WORLD! message.\n\nResetAndPause. A state where agent instances wait a bit before re-starting again the main cycle of the AI agent.\n\nAnd these the possible events (not all events can occur at every state):\n\nDONE. The state has successfully completed its intended purpose.\n\nNO_MAJORITY. There is no majority (more than 2/3) of agent instances that agree in the outcome of the state.\n\nTIMEOUT. Not all agent instances responded within a specified amount of time.\n\nYou can see above how the AI agent transits from one state to another given the event occurred at each one. The synchronized state enforced by the consensus gadget means that all the agent instances have the same view of the AI agent FSM, and all the instances execute the same transitions. This is one of the key concepts of the Open Autonomy framework.\n\nA note on determinism\n\nOne of the key points in an AI agent is determinism. It is very important that all the agent instances execute deterministic actions at each step, otherwise it will be impossible to synchronize their shared state.\n\nFor example, if the AI agent needs to execute some random action, all agent instances must retrieve the random seed from a common source, in this case, the DRAND service.\n\nGiven the description of the AI agent, it is immediate to obtain the FSM specification file.\n\nThe Hello World AI agent fsm_specification.yaml file\nfsm_specification.yamlalphabet_in:\n- DONE\n- NO_MAJORITY\n- RESET_TIMEOUT\n- ROUND_TIMEOUT\ndefault_start_state: RegistrationRound\nfinal_states: []\nlabel: HelloWorldAbciApp\nstart_states:\n- RegistrationRound\nstates:\n- CollectRandomnessRound\n- PrintMessageRound\n- RegistrationRound\n- ResetAndPauseRound\n- SelectKeeperRound\ntransition_func:\n(CollectRandomnessRound, DONE): SelectKeeperRound\n(CollectRandomnessRound, NO_MAJORITY): CollectRandomnessRound\n(CollectRandomnessRound, ROUND_TIMEOUT): CollectRandomnessRound\n(PrintMessageRound, DONE): ResetAndPauseRound\n(PrintMessageRound, ROUND_TIMEOUT): RegistrationRound\n(RegistrationRound, DONE): CollectRandomnessRound\n(ResetAndPauseRound, DONE): CollectRandomnessRound\n(ResetAndPauseRound, NO_MAJORITY): RegistrationRound\n(ResetAndPauseRound, RESET_TIMEOUT): RegistrationRound\n(SelectKeeperRound, DONE): PrintMessageRound\n(SelectKeeperRound, NO_MAJORITY): RegistrationRound\n(SelectKeeperRound, ROUND_TIMEOUT): RegistrationRound\n\nThe FSM App of the AI agent\n\nEach agent blueprint is composed of a number of components, namely, connections, protocols, contracts and skills. In order to become part of an AI agent, the agent blueprint requires a special skill: the FSM App. The FSM App skill is the component that processes events,transits the states of the AI agent FSM, and executes the actions of the AI agent.\n\nZoom on a Hello World AI agent.\n\nThe FSM App is a complex component that consists of a number of classes. Below we list the main ones.\n\nFor each state of the AI agent FSM:\n\nA Behaviour: The class that executes the proactive action at each state. For example, cast a vote for a keeper, print a message on screen, send a transaction on a blockchain, etc.\n\nA Payload: The message exchanged between agent instances in the state to indicate completion of the action. For example, a message containing what keeper the agent instance is voting for.\n\nA Round: The class that processes the input from the consensus gadget and outputs the appropriate events to make the next transition. For example, output the event DONE when all agent bluprint instances have cast they vote for a keeper.\n\nAdditionally, the following two classes:\n\nAbciApp: The class that defines the FSM itself and the transitions between states according to the FSM.\n\nRoundBehaviour: The main class of the FSM App skill, which aggregates the AbciApp and establishes a one-to-one relationship between the rounds and behaviours of each state.\n\nIn summary, the Hello World AI agent FSM App requires 5 Behaviours, 5 Payloads, 5 Rounds, 1 AbciApp and 1 RoundBehaviour.\n\nAgent Blueprints vs Agent instances\n\nAll agent instances in an AI agent are implemented by the same codebase. We call such codebase an agent blueprint, and we call each of the actual instances an agent instance. We often use agent instance for short when there is no risk of confusion and it is clear from the context which of the two terms we are referring to.\n\nEach agent instance in an AI agent can be parameterized with their own set of keys, addresses and other required attributes.\n\nHow the FSM App works\n\nLet us focus on what happens inside the FSM App of an agent instance when the AI agent is located in the SelectKeeper state and it transitions to the PrintMessage state.\n\nExecute the action and prepare the payload. The SelectKeeperBehaviour is in charge of two tasks:\n\nExecute the intended action, that is, determine which agent instance will be voted for as the new keeper. The choice is made deterministically, based on the randomness retrieved from DRAND.\n\nPrepares the SelectKeeperPayload, which contains its selection.\n\nSend the payload. The SelectKeeperBehaviour is in charge sends the payload to the consensus gadget.\n\nReach consensus. The consensus gadget reads all the agent instances' outputs, and ensures that all instances have the same consistent view. The gadget takes the responsibility of executing the consensus algorithm, which is abstracted away to the developer. The consensus gadget uses a short-lived blockchain to execute the consensus algorithm.\n\nNote\n\n\"Reaching consensus\" does not mean that the consensus gadget ensures that all the agent instance send the same payload. Rather, it means that all the agent instance have a consistent view on what payload was sent by each of them. In this particular case, however all agent instance cast the same vote.\n\nCallback to the FSM App. Once the consensus phase is finished, the SelectKeeperRound receives a callback and processes the outputs. Based on that, it casts an event. In this case, if strictly more than 2/3 of the agent instance voted for a certain keeper, it casts the event DONE.\n\nTransition to the next state. The event DONE is received by the AbciApp class, which executes the transition to the next state (PrintMessage).\n\nThe executions of further state transitions can be easily mapped with what has been presented here for the transition SelectKeeper → PrintMessage.\n\nTransition PrintMessage → ResetAndPause\nFollowing the same steps as above, this is what would happen:\n\nThe PrintMessageBehaviour, executes the main functionality. For the chosen keeper, it will be printing the HELLO_WORLD message. The rest of the agent instance simply print a neutral face.\n\nResult of the execution the second period of the Hello World AI agent\n\nThe PrintMessageBehaviour sends a PrintMessagePayload to the consensus gadget, indicating what was the message it printed by each agent.\n\nThe consensus gadget executes the consensus protocol ensuring a consistent view for all the agent instance.\n\nThe PrintMessageRound receives a callback, and after checking that all agent instance have responded it will produce the DONE event.\n\nThe AbciApp processes the event DONE, and moves to the next state, ResetAndPause.\n\nNote\n\nObserve that whereas in the SelectKeeper state we expect that all agent instance output the same payload to the consensus gadget (the same keeper vote), in the PrintMessage state it is admissible that the instantce send different values, because they print different things on their console.\n\nOther states might have different waiting conditions, for instance\n\nwait until all agent instance respond with a (possibly) different value, or\n\nwait until more than a threshold of instances respond with the same value.\n\nWhen the waiting condition is not met during a certain time interval, a special timeout event is generated by the Round, and the developer is in charge of defining how the FSM will transit in that case. You can see some of these unexpected events in the FSM diagram above.\n\nBird's eye view\n\nAs a summary, find below an image which shows the main components of the agent blueprint and the skill related to the Hello World AI agent presented in this overview. Of course, this is by no means the complete picture of what is inside an agent blueprint, but it should give a good intuition of what are the main elements that play a role in any AI agent and how they interact.\n\nMain components of an agent instance that play a role in an AI agent. Red arrows indicate a high-level flow of messages when the agent instance is in the SelectKeeper state.\n\nCoding the Hello World AI agent: a primer\n\nAs detailed in the overview of the development process, in order to create an AI agent, you must:\n\ncode the FSM App skill,\n\ndefine the agent blueprint, and\n\ndefine the AI agent.\n\nWe will explore this source code in the sections below, paying attention on the main parts that you should take into account.\n\nExploring the FSM App skill code\n\nTake a look at the structure of the FSM App skill of the Hello World agent blueprint (called hello_world_abci):\n\n./hello_world_agent/vendor/valory/skills/hello_world_abci/\n|\n├── __init__.py\n├── behaviours.py\n├── dialogues.py\n├── fsm_specification.yaml\n├── handlers.py\n├── models.py\n├── payloads.py\n├── README.md\n├── rounds.py\n├── skill.yaml\n└── tests/\n\nNote that the easiest way to start building a new FSM App is by using the FSM App scaffold tool, because it already populates many of these files. The most important files you should look at are:\n\nbehaviours.py: This file defines the Behaviours, which encode the proactive actions occurring at each state of the FSM. Each behaviour is one-to-one associated to a Round. It also contains the HelloWorldRoundBehaviour class, which can be thought as the \"main\" class for the skill behaviour.\n\nEach behaviour must:\n\nSet the matching_round attribute to the corresponding Round class.\n\nDefine the action executed in the state inside the method async_act().\n\nPrepare the Payload associated with this state. The payload can be anything that other agent instance might find useful for the action in this or future states.\n\nSend the Payload, which the consensus gadget will be in charge of synchronizing with all the agent instances.\n\nWait until the consensus gadget finishes its work, and mark the state set_done().\n\nThe last three steps above are common for all the Behaviours.\n\nThe PrintMessageBehaviour class\nClass diagram:\n\nHierarchy of the PrintMessageBehaviour class (some methods and fields are omitted)\n\nThe HelloWorldABCIBaseBehaviour is a convenience class, and the upper class in the hierarchy are abstract classes from the stack that facilitate re-usability of code when implementing the Behaviour. An excerpt of the PrintMessageBehaviour code is:\n\nclass PrintMessageBehaviour(HelloWorldABCIBaseBehaviour, ABC):\n\"\"\"Prints the celebrated 'HELLO WORLD!' message.\"\"\"\n\nmatching_round = PrintMessageRound\n\ndef async_act(self) -> Generator:\n\"\"\"\nDo the action.\n\nSteps:\n- Determine if this agent instance is the current keeper agent instance.\n- Print the appropriate to the local console.\n- Send the transaction with the printed message and wait for it to be mined.\n- Wait until ABCI application transitions to the next round.\n- Go to the next behaviour (set done event).\n\"\"\"\n\nif (\nself.context.agent_address\n== self.synchronized_data.most_voted_keeper_address\n):\nmessage = self.params.hello_world_string\nelse:\nmessage = \":|\"\n\nprinted_message = f\"Agent {self.context.agent_name} (address {self.context.agent_address}) in period {self.synchronized_data.period_count} says: {message}\"\n\nprint(printed_message)\nself.context.logger.info(f\"printed_message={printed_message}\")\n\npayload = PrintMessagePayload(self.context.agent_address, printed_message)\n\nyield from self.send_a2a_transaction(payload)\nyield from self.wait_until_round_end()\n\nself.set_done()\n\nOnce all the Behaviours are defined, you can define the HelloWorldRoundBehaviour class. This class follows a quite standard structure in all AI agents, and the reader can easily infer what is it from the source code.\n\nThe HelloWorldRoundBehaviour class\nclass HelloWorldRoundBehaviour(AbstractRoundBehaviour):\n\"\"\"This behaviour manages the consensus stages for the Hello World abci app.\"\"\"\n\ninitial_behaviour_cls = RegistrationBehaviour\nabci_app_cls = HelloWorldAbciApp\nbehaviours: Set[Type[BaseBehaviour]] = {\nRegistrationBehaviour, # type: ignore\nCollectRandomnessBehaviour, # type: ignore\nSelectKeeperBehaviour, # type: ignore\nPrintMessageBehaviour, # type: ignore\nResetAndPauseBehaviour, # type: ignore\n}\n\npayloads.py: This file defines the payloads associated to the consensus engine for each of the states. Payloads are data objects, and carry almost no business logic.\n\nThe PrintMessagePayload class\n@dataclass(frozen=True)\nclass PrintMessagePayload(BaseTxPayload):\n\"\"\"Represent a transaction payload of type 'randomness'.\"\"\"\n\nmessage: str\n\nrounds.py: This file contains the implementation of the rounds associated to each state and the shared SynchronizedData class (the class that stores the AI agent shared state). It also contains the declaration of the FSM events, and the HelloWorldAbciApp, which defines the transition function of the FSM.\n\nEach round must:\n\nInherit from one of the classes that determine what kind of consensus is expected at the associated sate: CollectDifferentUntilAllRound, CollectSameUntilAllRound, CollectSameUntilThresholdRound, etc.\n\nSet the payload_class attribute to the corresponding Payload class.\n\nSet other attributes required by the inherited class.\n\nImplement the end_block() method, which is called by the consensus gadget. This method must output the updated SynchronizedData and the event produced after evaluating the consensus result.\n\nThe PrintMessageRound class\nClass diagram:\n\nHierarchy of the PrintMessageRound class (some methods and fields are omitted)\n\nThe HelloWorldABCIAbstractRound is a convenience class defined in the same file. The class CollectDifferentUntilAllRound is a helper class for rounds that expect that each agent instance sends a different message. In this case, the message to be sent is the agent instance printed by each instance, which will be obviously different for each instance (one of them will be the HELLO_WORLD! message, and the others will be empty messages).\n\nclass PrintMessageRound(CollectDifferentUntilAllRound, HelloWorldABCIAbstractRound):\n\"\"\"A round in which the keeper prints the message\"\"\"\n\npayload_class = PrintMessagePayload\n\ndef end_block(self) -> Optional[Tuple[BaseSynchronizedData, Event]]:\n\"\"\"Process the end of the block.\"\"\"\nif self.collection_threshold_reached:\nsynchronized_data = self.synchronized_data.update(\nparticipants=tuple(sorted(self.collection)),\nprinted_messages=sorted(\n[\ncast(PrintMessagePayload, payload).message\nfor payload in self.collection.values()\n]\n),\nsynchronized_data_class=SynchronizedData,\n)\nreturn synchronized_data, Event.DONE\nreturn None\n\nIf the successful condition occurs, the end_block() method returns the appropriate event (DONE) so that the AbciApp can process and transit to the next round.\n\nObserve that the RegistrationRound is very similar to the PrintMessageRound, as it simply has to collect the different addresses that each agent instance sends. On the other hand, the classes CollectRandomnessRound and SelectKeeperRound just require to define some parent classes attributes, as they execute fairly standard operations already available in the framework.\n\nAfter having defined all the Rounds, the HelloWorldAbciApp does not have much mystery. It simply defines the transitions from one state to another in the FSM, arranged as Python dictionaries. For example,\n\nSelectKeeperRound: {\nEvent.DONE: PrintMessageRound,\nEvent.NO_MAJORITY: RegistrationRound,\nEvent.ROUND_TIMEOUT: RegistrationRound,\n},\n\ndenotes the three possible transitions from the SelectKeeperRound to the corresponding Rounds, according to the FSM depicted above.\n\nWhereas these are the main files to take into account, there are other files that are also required, and you can take a look:\n\nskill.yaml: This is the skill specification file. It defines the sub-components (e.g. protocols, connections) required by the skill, as well as a number of configuration parameters.\n\nhandlers.py: Defines the Handlers (implementing reactive actions) used by the skill. It is mandatory that the skill associated to an agent blueprint implements a handler inherited from the ABCIRoundHandler. Other handlers are required according to the actions that the skill is performing (e.g., interacting with an HTTP server). As you can see by exploring the file, little coding is expected unless you need to implement a custom protocol.\n\ndialogues.py: It defines the dialogues associated to the protocols described in the skill.yaml configuration file. Again, not much coding is expected in most cases.\n\nmodels.py: It defines the models of the skill, which usually consist of the SharedState and the configuration parameters Params classes. The classes defined here are linked with the contents in the section models in the file skill.yaml.\n\nfsm_specification.yaml: The FSM App specification file. It is used for checking the consistency of the implementation, and it can be used to verify the implementation or to scaffold the FSM App providing an initial structure.\n\nExploring the agent blueprint definition code\n\nThe agent blueprint configuration file aea-config.yaml is located in the root folder of the agent:\n\n./hello_world_agent/\n|\n├── __init__.py\n├── aea-config.yaml\n├── README.md\n├── tests/\n└── vendor/\n\nAgent blueprints are defined through the Open AEA library as YAML files, which specify what components the agent blueprint made of (connections, protocols, contracts and skills). Recall that an agent blueprint requires the FSM App skill to work in an AI agent.\n\nThis is an excerpt of the aea-config.yaml file:\n\naea-config.yaml# (...)\nconnections:\n- valory/abci:0.1.0\n- valory/http_client:0.23.0\n- valory/ipfs:0.1.0\n- valory/ledger:0.19.0\n- valory/p2p_libp2p_client:0.1.0\ncontracts: []\nprotocols:\n- open_aea/signing:1.0.0\n- valory/abci:0.1.0\n- valory/http:1.0.0\n- valory/ipfs:0.1.0\nskills:\n- valory/abstract_abci:0.1.0\n- valory/abstract_round_abci:0.1.0\n- valory/hello_world_abci:0.1.0\n# (...)\n\nIt is mandatory that agent blueprints include some of mandatory components: the abci connection, the abci protocol, the abstract_abci skill and the abstract_round_abci skill.\n\nAdditionally, the agent blueprint can use other connections, protocols or skills, depending of its particular needs. In the example, the http_client connection and the http protocol allows the agent instances to interact with HTTP servers (although we are not using it in this AI agent). Similarly, you can add the ledger connection and the ledger_api protocol in case the agent instance needs to interact with a blockchain.\nIt obviously contains the hello_world_abci skill, which is the FSM App skill discussed above.\n\nNote that although it is possible to develop your own protocols and connections, the Open AEA framework provides a number of typical ones which can be reused. Therefore, it is usual that the developer focuses most of its programming efforts in coding the particular skill(s) for their new agent blueprint.\n\nExploring the AI agent definition code\n\nThe AI agent configuration file service.yaml is located in the root folder of the AI agent:\n\n./hello_world_service/\n|\n├── README.md\n└── service.yaml\n\nYou can read the dedicated section to understand the structure and configuration of the service.yaml file.\n\nConclusion and further reading\n\nEven though printing HELLO_WORLD! on a local console is far from being an exciting functionality, the Hello World AI agent shows a number of non-trivial elements that are key components in many agent blueprints:\n\nThe agent blueprint defines a sequence of individual, well-defined actions, whose execution in the appropriate order achieves the intended functionality.\n\nAgent instance have to interact with each other to execute each of those actions, and reach a consensus on a number of decisions at certain moments (e.g., which is the keeper instance that prints the message in each period).\n\nAgent instance execute actions on their own. In this simple example it just consists of printing a local message.\n\nAgent instance have to use a shared, global store for persistent data (e.g., which was the last instance that printed the message).\n\nFinally, the AI agent can progress even if some agent instance is faulty or malicious (up to a certain threshold of malicious instances).\n\nIn this toy example we are not verifying that the keeper behaves honestly: there is no way for the other agent instance to verify its console. However, in a real AI agent that implements some critical operation (e.g., like sending a transaction to a blockchain) further verification and security mechanisms have to be put in place.\n\nThis walk-through, together with the overview of the development process should give you some confidence to start creating your first AI agent. Obviously, there are more elements in the Open Autonomy framework that facilitate building complex applications by enabling to interact with blockchains and other networks. We refer the reader to the more advanced sections of the documentation (e.g., key concepts) where we explore in detail the components of the stack.","tokens":6324,"crawled_at":1791192776701}
+{"id":10146,"url":"https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/hyperevm/dual-block-architecture","domain":"hyperliquid.gitbook.io","chapter":"defi_protocols","title":"Dual-block architecture | Hyperliquid Docs","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nThe total HyperEVM throughput is split between small blocks produced at a fast rate and large blocks produced at a slower rate.\nThe primary motivation behind the dual-block architecture is to decouple block speed and block size when allocating throughput improvements. Users want faster blocks for lower time to confirmation. Builders want larger blocks to include larger transactions such as more complex contract deployments. Instead of a forced tradeoff, the dual-block system will allow simultaneous improvement along both axes.\nThe HyperEVM \"mempool\" is still onchain state with respect to the umbrella L1 execution, but is split into two independent mempools that source transactions for the two block types. The two block types are interleaved with a unique increasing sequence of EVM block numbers. The onchain mempool implementation accepts only the next 8 nonces for each address. Transactions older than 1 day old in the mempool are pruned.\nThe initial configuration is set conservatively, and throughput is expected to increase over successive technical upgrades. Fast block duration is set to 1 seconds with a 3M gas limit. Slow block duration is set to 1 minute with a 30M gas limit.\nMore precisely, in the definitions above, block duration of x means that the first L1 block for each value of l1_block_time % x produces an EVM block.\nDevelopers can deploy larger contracts as follows:\n\nSubmit action {\"type\": \"evmUserModify\", \"usingBigBlocks\": true} to direct HyperEVM transactions to big blocks instead of small blocks. Note that this user state flag is set on the HyperCore user level, and must be unset again to target small blocks. Like any action, this requires an existing Core user to send. Like any EOA, the deployer address can be converted to a Core user by receiving a Core asset such as USDC.\n\nOptionally use the JSON-RPC method bigBlockGasPrice in place of gasPrice to estimate base gas fee on the next big block.\n\nPreviousHyperEVM\nNextRaw HyperEVM block data\n\nLast updated 4 months ago","tokens":527,"crawled_at":1791192783297}
+{"id":10147,"url":"https://a16zcrypto.com/posts/article/building-helios-ethereum-light-client","domain":"a16zcrypto.com","chapter":"research","title":"Building Helios: Fully trustless access to Ethereum - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nBuilding Helios: Fully trustless access to Ethereum\nNoah Citron\n11.06.22\n\nTABLE OF CONTENTS\nThe pitfalls of centralized infrastructure: theoretical creatures in Ethereum’s “dark forest” The pitfalls of centralized infrastructure: theoretical creatures in Ethereum’s “dark forest”\nIntroducing Helios: fully trustless access to Ethereum\nUsing Helios in the wild\nTags\ncode & engineering\nEthereum\nhelios\nlight clients\nopen source\nsecurity\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nOne of the main reasons we use blockchains is trustlessness. This property promises to allow us self-sovereign access to our wealth and data. For the most part, blockchains like Ethereum have delivered on this promise — our assets are truly ours.\n\nHowever, there are concessions we’ve made for the sake of convenience. One such area is in our use of centralized RPC (remote procedure call) servers. Users typically access Ethereum through centralized providers like Alchemy. These companies run high-performance nodes on cloud servers so that others can easily access chain data. When a wallet queries its token balances or checks whether a pending transaction has been included in a block, it almost always does so through one of these centralized providers.\n\nThe trouble with the existing system is that users need to trust the providers, and there is no way to verify the correctness of their queries.\n\nEnter Helios, a Rust-based Ethereum light client we developed that provides fully trustless access to Ethereum. Helios — which uses Ethereum’s light client protocol, made possible by the recent switch to proof of stake — converts data from an untrusted centralized RPC provider into a verifiably safe, local RPC. Helios works together with centralized RPCs to make it possible to verify their authenticity without running a full node.\n\nThe tradeoff between portability and decentralization is a common pain point, but our client – which we’ve made available to the public to build on and more – syncs in around two seconds, requires no storage, and allows users to access secure chain data from any device (including mobile phones and browser extensions). But what are the potential pitfalls of relying on centralized infrastructure? We cover how they might play out in this post, walk through our design decisions, and also outline a few ideas for others to contribute to the codebase.\n\nThe pitfalls of centralized infrastructure: theoretical creatures in Ethereum’s “dark forest”\n\nA (theoretical) creature lurks in the dark forest. This one doesn’t hunt for its prey in the Ethereum mempool, but instead sets its traps by mimicking centralized infrastructure that we’ve come to rely on. The users who get caught in this trap don’t make any mistakes: They visit their favorite decentralized exchange, set a reasonable slippage tolerance, and buy and sell tokens as usual… They do everything right, but still fall victim to a new kind of sandwich attack, a trap meticulously set at the very entrance to Ethereum’s dark forest: RPC providers.\n\nBefore we elaborate, let’s look at how trades work on decentralized exchanges. When users send a swap transaction, they provide several parameters to the smart contract — which tokens to swap, the swap amount, and most importantly, the minimum number of tokens a user must receive for the transaction to go through. This last parameter specifies that the swap must satisfy a “minimum output,” or revert. This is often known as “slippage tolerance,” as it effectively sets the maximum price change that can occur between when the transaction is sent to the mempool and when it is included in a block. If this parameter is set too low, the user accepts the possibility of receiving fewer tokens. This situation can also lead to a sandwich attack, where an attacker effectively sandwiches the bid between two malicious swaps. The swaps drive up the spot price and forces the user’s trade to execute at a less favorable price. The attacker then sells immediately to collect a small profit.\n\nSo long as this minimum output parameter is set near the fair value, you are safe from sandwich attacks. But what if your RPC provider doesn’t provide an accurate price quote from the decentralized exchange smart contract? A user can then be tricked into signing a swap transaction with a lower minimum output parameter, and, to make matters worse, sends the transaction straight to the malicious RPC provider. Instead of broadcasting this transaction to the public mempool, where dozens of bots compete to perform the sandwich attack, the provider can withhold it and send the attack transaction bundle directly to Flashbots, securing the profits for themselves.\n\nThe root cause of this attack is trusting somebody else to fetch the state of the blockchain. Experienced users have traditionally solved this problem by running their own Ethereum nodes — a time and resource-intensive endeavor that, at the very least, requires a constantly-online machine, hundreds of gigabytes of storage, and around a day to sync from scratch. This process is certainly easier than it used to be; groups like Ethereum on ARM have worked tirelessly to make it possible to run nodes on low-cost hardware (such as a Raspberry Pi with an external hard drive strapped to it). But even with these relatively minimal requirements, running a node is still difficult for most users, particularly for those using mobile devices.\n\nIt’s important to note that centralized RPC provider attacks, although entirely plausible, are generally simple phishing attacks — and the one we describe has yet to happen. Even though the track records of larger providers like Alchemy give us little reason to doubt them, it’s worth doing some further research before adding unfamiliar RPC providers to your wallet.\n\nIntroducing Helios: fully trustless access to Ethereum\n\nBy introducing its light client protocol (made possible by the recent switch to Proof of Stake), Ethereum opened exciting new possibilities for quickly interacting with the blockchain and verifying RPC endpoints with minimal hardware requirements. In the month’s since The Merge, we’ve seen a new crop of light clients emerge independently of each other (Lodestar, Nimbus, and the JavaScript-based Kevlar) that have taken different approaches in service of the same goal: efficient and trustless access, without using a full node.\n\nOur solution, Helios, is an Ethereum light client that syncs in around two seconds, requires no storage, and provides fully trustless access to Ethereum. Like all Ethereum clients, Helios consists of an execution layer and a consensus layer. Unlike most other clients, Helios tightly couples both layers so that users only need to install and run a single piece of software. (Erigon is moving in this direction as well, by adding a consensus layer light client built directly into their archive node).\n\nSo how does it work? The Helios consensus layer uses a previously known beacon chain blockhash and a connection to an untrusted RPC to verifiably sync to the current block. The Helios execution layer uses these authenticated beacon chain blocks in tandem with an untrusted execution layer RPC to prove arbitrary information about the chain state such as account balances, contract storage, transaction receipts, and smart contract call results. These components work together to serve users a fully trustless RPC, without the need to run a full node.\n\n…At the consensus layer\n\nThe consensus layer light client conforms to the beacon chain light client specification, and makes use of the beacon chain’s sync committees (introduced ahead of the Merge in the Altair hard fork). The sync committee is a randomly selected subset of 512 validators that serve for ~27-hour periods.\n\nWhen a validator is on a sync committee, they sign every beacon chain block header that they see. If more than two-thirds of the committee signs a given block header, it is highly likely that that block is in the canonical beacon chain. If Helios knows the makeup of the current sync committee, it can confidently track the head of the chain by asking an untrusted RPC for the most recent sync committee signature.\n\nThanks to BLS signature aggregation, only a single check is required to validate the new header. If the signature is valid and has been signed by more than two-thirds of the committee, it’s safe to assume the block was included in the chain (of course it can be reorg’d out of the chain, but tracking block finality can provide stricter guarantees).\n\nThere’s an obvious missing piece in this strategy, though: how to find the current sync committee. This starts with acquiring a root of trust called the weak subjectivity checkpoint. Don’t let the name intimidate you — it just means an old blockhash that we can guarantee was included in the chain at some point in the past. There is some interesting math behind exactly how old the checkpoint can be; worst-case analysis suggests around two weeks, while more practical estimates suggest many months.\n\nIf the checkpoint is too old, there are theoretical attacks that can trick nodes into following the wrong chain. Acquiring a weak subjectivity checkpoint is out of band for the protocol. Our approach with Helios provides an initial checkpoint hardcoded into the codebase (which can easily be overridden); it then saves the most recent finalized blockhash locally to use as the checkpoint in the future, whenever the node is synced.\n\nConveniently, beacon chain blocks can be hashed to produce a unique beacon blockhash. This means it’s easy to ask a node for a full beacon block, and then prove the block contents are valid by hashing it and comparing to a known blockhash. Helios uses this property to fetch and prove certain fields inside the weak subjectivity checkpoint block, including two very important fields: the current sync committee, and the next sync committee. Critically, this mechanism allows light clients to fast forward through the blockchain’s history.\n\nNow that we have a weak subjectivity checkpoint, we can fetch and verify the current and next sync committees. If the current chain head is within the same sync committee period as the checkpoint, then we immediately start verifying new blocks with the signed sync committee headers. If our checkpoint is several sync committees behind, we can:\n\nUse the next sync committee after our checkpoint to fetch and verify a block that originates one sync committee in the future.\n\nUse this new block to fetch the new next sync committee.\n\nIf still behind, return to step 1.\n\nEach iteration of this process allows us to fast forward through 27 hours of the chain���s history, start with any blockhash in the past, and sync to the current blockhash.\n\n…At the execution layer\n\nThe goal of the execution layer light client is to take beacon block headers that are verified by the consensus layer, and use them along with an untrusted execution layer RPC to provide verified execution layer data. This data can then be accessed via an RPC server that is locally hosted by Helios.\n\nHere’s a simple example of fetching an account’s balance, starting with a quick primer on how state is stored in Ethereum. Each account contains a couple fields, such as the contract code hash, nonce, storage hash, and balance. These accounts are stored in a large, modified Merkle-Patricia tree called the state tree. If we know the root of the state tree, we can validate merkle proofs to prove the existence (or exclusion) of any account within the tree. These proofs are effectively impossible to forge.\n\nHelios has an authenticated state root from the consensus layer. Using this root and merkle proof requests to the untrusted execution layer RPC, Helios can locally verify all data stored on Ethereum.\n\nWe apply different techniques to verify all sorts of data used by the execution layer; used together, these allow us to authenticate all data retrieved from the untrusted RPC. While an untrusted RPC can deny access to data, it can no longer serve us incorrect results.\n\nUsing Helios in the wild\n\nThe tradeoff between portability and decentralization is a common pain point — but since Helios is so lightweight, users can access secure chain data from any device (including mobile phones and browser extensions). The ability to run Helios anywhere makes it possible for more people to access trustless Ethereum data, regardless of their hardware. This means users can use Helios as their RPC provider in MetaMask, and trustlessly access dapps without any other changes.\n\nFurther, Rust’s support for WebAssembly makes it easily possible for app developers to embed Helios inside Javascript applications (like wallets and dapps). These integrations would make Ethereum safer, and reduce our need to trust centralized infrastructure.\n\nWe can’t wait to see what the community comes up with. But in the meantime, there are lots of ways to contribute to Helios — if you’re not interested in contributing to the codebase, you can also build software that integrates Helios to take advantage of its benefits. These are just a few of the ideas we’re excited about:\n\nSupport fetching light client data directly from the P2P network rather than via RPC\n\nImplement some of the missing RPC methods\n\nBuild a version of Helios that compiles to WebAssembly\n\nIntegrate Helios directly into wallet software\n\nBuild a web dashboard to view your token balances that fetches data from Helios embedded into the website with WebAssembly\n\nImplement the engine API so that Helios’ consensus layer can be connected to an existing execution layer full node\n\nCheck out the codebase to get started — we welcome your bug reports, feature requests, and code. And if you build something more, share it with us on Twitter, Telegram, or Farcaster @a16zcrypto.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nCharts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information","tokens":4143,"crawled_at":1791192791585}
+{"id":10148,"url":"https://www.metaplex.com/docs/smart-contracts/token-metadata/guides","domain":"www.metaplex.com","chapter":"docs","title":"Guides | Token Metadata","text":"Token Metadata is a legacy program. It remains supported, but is not recommended for new projects. Use Core instead.\n\nThe following guides for MPL Token Metadata are currently available:\nGet Mints by Collection\nSnippets to fetch NFTs by Collection\n\nCreate an NFT\nCreate your very own NFT using Javascript\n\nAccount Size Reduction\nLearn more about the TM Account Size Reduction\n\nCreate a claim based airdrop using MPL-Distro\nPersist Merkle proofs, run a claim page or API, and recover unclaimed tokens with MPL-Distro.\n\nToken Claimer Smart Contract\nLearn how to create a Token Claimer Smart Contract on Solana leveraging Merkle Trees and using Anchor!","tokens":163,"crawled_at":1791192792300}
+{"id":10149,"url":"https://stack.olas.network/open-autonomy/get_started/what_is_an_agent_service","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"What is an agent service - Olas Stack Developer Documentation","text":"What is an agent service\n\nAn AI agent is an off-chain autonomous service which runs as a multi-agent-system (MAS) and is crypto-economically secured on a public blockchain.\n\nAI agents enable complex processing, take action on their own and run continuously. Moreover, AI agents are crypto-native by construction, that is, they are decentralized, trust-minimized, transparent, and robust.\n\nSee some use cases of AI agents that can be built with the Open Autonomy framework.\n\nArchitecture\n\nThe Open AEA framework provides the necessary components for building single agent blueprints. Open Autonomy extends this framework to an AI agent architecture, making possible to build applications as distributed systems (that is, AI agents) that can be run by multiple, independent operators.\n\nThe internal state of an AI agent is replicated across all the agent instances in the AI agent through a consensus gadget (a sort of short-lived blockchain).\n\nThis is what an AI agent looks like:\n\nAI agent: The decentralized off-chain service that implements a certain functionality. It is composed of N agent instances, where N is a parameter that is defined by the owner of the AI agent.\n\nOperator: An entity or individual that owns the infrastructure where an agent instance is run. Each operator manages an agent instance and a consensus gadget node.\n\nAgent: The software unit that aggregates the runtime and functionalities to execute the AI agent. Each agent blueprint is made up of a number of components that implement different functionalities, for example, what communication protocols the agent blueprint understands.\n\nFSM App: The core component inside an agent blueprint that defines the business logic of the AI agent. FSM App implements the underlying mechanisms for agent isntances to synchronize their internal state and run the business logic in a decentralized fashion.\n\nConsensus gadget: The infrastructure that enables agent instances to synchronize the AI agent state and reach consensus on certain important decisions. From a technical point of view, the consensus gadget implements a blockchain based on Tendermint that is pruned periodically. By consensus gadget we usually refer to the collection of consensus nodes + consensus network.\n\nAI agent multisig Safe: Smart contract based Multisig that secures the AI agent by requiring a threshold of agent instances to sign any transaction before it is executed.\n\nHow it works\n\nThe FSM App, which encodes the business logic of the AI agent, is structured as a finite-state machine defining a series of steps that each agent instance in the AI agent must follow in order to achieve the intended functionality.\n\nExample\n\nThis is a toy example of how an FSM App defines the business logic of an oracle AI agent that collects prices from a source and publishes it on a blockchain:\n\nThe FSM App replicates automatically the state and transitions across agent instances using the consensus gadget. This ensures that the execution flow of the AI agent, its inputs and outputs are synchronized across all instances, creating a distributed (and decentralized) application with shared state that is fault tolerant.\n\nTip\n\nWhen developing an AI agent, the developer can focus on defining the steps of the AI agent in the FSM App as if it were a standalone application, and get the replication mechanism \"for free\".\n\nThe Open Autonomy framework will provide most of the machinery to ensure that the agent instances' state is replicated as the AI agent is executed.\n\nIf at some point the AI agent needs to execute an action involving an external service, e.g., settling a transaction on a blockchain, then the following occurs:\n\nThe agent instances in the AI agent nominate by consensus an instance (known as keeper) to perform the action.\n\nA threshold of agent instances has to approve and sign the transaction, using the AI agent multisig Safe. This prevents a malicious agent instance from executing an external action on its own.\n\nFurthermore, the agent instances in the AI agent verify that the transaction was executed successfully. Otherwise, a new keeper will be nominated and the transaction will be retried.\n\nThe threshold on the minimum number of agent instances required to sign is typically, but not exclusively, set at 2/3 of the total of instances.","tokens":1077,"crawled_at":1791192795718}
+{"id":10150,"url":"https://gov.uniswap.org/c/site-feedback/2","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Site Feedback - Uniswap Governance","text":"Site Feedback\n\nTopic\n\nReplies\nViews\nActivity\n\nAbout the Site Feedback category\n\n3\n\n1504\n\nFebruary 1, 2025\n\nUniswap for noobs\n\n7\n\n2934\n\nAugust 25, 2024\n\nIs there a chat communication channel besides this forum\n\n2\n\n2612\n\nMay 5, 2024\n\nIdea: establish a more private and informal discussion place for the Uniswap DAO\n\n4\n\n1830\n\nNovember 29, 2023\n\nUniswap DAO helps Turkiye earthquake\n\n13\n\n4841\n\nFebruary 15, 2023\n\nAn extension to uniswap to leverage liquidity pools for lending and borrowing\n\n0\n\n2364\n\nJune 3, 2022\n\nI think uniswap should be extended to more networks~\n\n2\n\n2682\n\nMarch 22, 2022\n\nDark mode UI issue\n\n0\n\n2267\n\nSeptember 3, 2021\n\nDark Mode Issue with New Governance UI\n\n5\n\n2343\n\nJuly 18, 2021\n\nLiquidity distribution: AMM vs CEX algorithm\n\n0\n\n2164\n\nMay 26, 2021\n\nPosting Instructions\n\n0\n\n2119\n\nMay 21, 2021\n\nAdd \"A/ agree\" and \"D/ disagree\" button on all proposals and comments\n\n29\n\n4096\n\nMay 21, 2021\n\nUniswap development team needs to play a bigger role\n\n7\n\n3394\n\nMarch 28, 2021\n\nDeposit Art and?\n\n0\n\n2156\n\nFebruary 16, 2021\n\nDashboard to view current vote delegation\n\n7\n\n2801\n\nDecember 23, 2020\n\nUni rewards avec univ2\n\n1\n\n2290\n\nOctober 20, 2020\n\nAdding a Language Translator to the Program\n\n7\n\n2523\n\nSeptember 22, 2020\n\nDisplay Profits\n\n1\n\n2411\n\nSeptember 21, 2020\n\nInclude staked UNI-V2 tokens on account info page\n\n3\n\n2616\n\nSeptember 21, 2020\n\nGovernance Category?\n\n1\n\n2394\n\nSeptember 18, 2020\n\nAmazing Platform Experience\n\n0\n\n2381\n\nSeptember 17, 2020","tokens":367,"crawled_at":1791192799838}
+{"id":10151,"url":"https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/hyperevm/dual-block-architecture.md","domain":"hyperliquid.gitbook.io","chapter":"defi_protocols","title":"","text":"> For the complete documentation index, see [llms.txt](https://hyperliquid.gitbook.io/hyperliquid-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/hyperevm/dual-block-architecture.md).\n\n# Dual-block architecture\n\nThe total HyperEVM throughput is split between small blocks produced at a fast rate and large blocks produced at a slower rate.&#x20;\n\nThe primary motivation behind the dual-block architecture is to decouple block speed and block size when allocating throughput improvements. Users want faster blocks for lower time to confirmation. Builders want larger blocks to include larger transactions such as more complex contract deployments. Instead of a forced tradeoff, the dual-block system will allow simultaneous improvement along both axes.&#x20;\n\nThe HyperEVM \"mempool\" is still onchain state with respect to the umbrella L1 execution, but is split into two independent mempools that source transactions for the two block types. The two block types are interleaved with a unique increasing sequence of EVM block numbers. The onchain mempool implementation accepts only the next 8 nonces for each address. Transactions older than 1 day old in the mempool are pruned.&#x20;\n\nThe initial configuration is set conservatively, and throughput is expected to increase over successive technical upgrades. Fast block duration is set to 1 seconds with a 3M gas limit. Slow block duration is set to 1 minute with a 30M gas limit.&#x20;\n\nMore precisely, in the definitions above, *block duration* of `x` means that the first L1 block for each value of `l1_block_time % x` produces an EVM block.&#x20;\n\nDevelopers can deploy larger contracts as follows:\n\n1. Submit action `{\"type\": \"evmUserModify\", \"usingBigBlocks\": true}` to direct HyperEVM transactions to big blocks instead of small blocks. Note that this user state flag is set on the HyperCore user level, and must be unset again to target small blocks. Like any action, this requires an existing Core user to send. Like any EOA, the deployer address can be converted to a Core user by receiving a Core asset such as USDC.\n2. Optionally use the JSON-RPC method `bigBlockGasPrice` in place of `gasPrice` to estimate base gas fee on the next big block.","tokens":591,"crawled_at":1791192800530}
+{"id":10152,"url":"https://www.metaplex.com/docs/smart-contracts/token-metadata/guides/get-by-collection","domain":"www.metaplex.com","chapter":"docs","title":"Get Mints in a Collection | Token Metadata Guides","text":"Token Metadata is a legacy program. It remains supported, but is not recommended for new projects. Use Core instead.\n\nMetaplex Token Metadata has onchain collections to allow objective identifying of NFT collections instead of various subjective and potentially conflicting heuristics employed by the community in absence of an onchain standard.\nThe specification design makes it very easy to look up any given NFT and determine if it is in a collection and if so, which collection, by simply reading the Collection fields from the metadata account. The onchain Metadata struct contains an option Collection struct which has a key field which is the Pubkey of the SPL token mint of the collection it belongs to.\npub struct Metadata {\n\npub key: Key,\n\npub update_authority: Pubkey,\n\npub mint: Pubkey,\n\npub data: Data,\n\n// Immutable, once flipped, all sales of this metadata are considered secondary.\n\npub primary_sale_happened: bool,\n\n// Whether or not the data struct is mutable, default is not\n\npub is_mutable: bool,\n\n/// nonce for easy calculation of editions, if present\n\npub edition_nonce: Option<u8>,\n\n/// Token Standard is deterministic and will change from SemiFungible to NonFungible if\n\n/// you call the create master edition call and it succeeds.\n\npub token_standard: Option<TokenStandard>,\n\n/// Since we cannot easily change Metadata, we add the new DataV2 fields here at the end.\n\n/// Collection\n\npub collection: Option<Collection>,\n\n...\n\n}\n\n#[derive(BorshSerialize, BorshDeserialize, PartialEq, Debug, Clone)]\n\npub struct Collection {\n\npub verified: bool, // Whether or not the collection is verified\n\npub key: Pubkey, // The SPL token mint account of the collection NFT\n\n}\n\nHowever, given a collection mint address, finding all NFTs that belong to that particular collection is significantly more difficult when reading directly from chain. There is one superior method using DAS and two basic approaches to get the data from chain directly.\nDAS API\nFetching the mints using DAS is the superior method when using a RPC Provider that supports it.\ngetAssetByGroup Example\n\nReplace the endpoint with your RPC URL and collection with the collection address you are looking for.\nimport { publicKey } from '@metaplex-foundation/umi';\n\nimport { createUmi } from '@metaplex-foundation/umi-bundle-defaults';\n\nimport { dasApi } from '@metaplex-foundation/digital-asset-standard-api';\n\nconst endpoint = '<ENDPOINT>';\n\nconst collection = 'J2ZfLdQsaZ3GCmbucJef3cPnPwGcgjDW1SSYtMdq3L9p'\n\nconst umi = createUmi(endpoint).use(dasApi());\n\nconst assets = await umi.rpc.getAssetsByGroup({\n\ngroupKey: 'collection',\n\ngroupValue: collection,\n\n});\n\nconsole.log(assets.items.length > 0);\n\nYou can find more methods on DAS and additional Methods that allows fetching and filtering data in our DAS Documentation\nGetProgramAccounts with PreCalculated Offsets\nIt’s tempting to think we can simply use a getProgramAccounts call with an offset into the Collection struct to match the collection id against the key field. This is the same way that most client programs find, e.g. a snapshot of NFT mint accounts belonging to a specific candy machine or creator ID. However, due to the fact that edition_nonce, token_standard, and collection are all Rust Options, this gets significantly more complicated.\nRust Options are represented in Borsh encoding with a 0 for the None variant and a 1 for the Some variant along with the normal encoding for whatever the contained value of the Some variant is. (One byte for a u8, for example.) This means that we can’t calculate an offset into the Collection struct without knowing what variant type is in each two of the two Options prior to the Collection field.\nThere are two ways to do this: brute force and gathering a priori knowledge of the variants.\nBrute force requires computing all the possible variants and running multiple getProgramAccount calls in parallel. Given up to five creators in the creators array and two possible options for each of the two Option fields prior to Collection, that leads to a total number of 20 possible combinations, meaning that you would have to make 20 getProgramAccount calls with various offsets to take this approach. This is obviously not a feasible nor scalable approach. If some a priori information is known about a collection though, this can be reduced to a smaller number of calls. Knowing how many creators there are is the biggest gain, reducing the number of getProgramAccount calls down to only four which can be reasonably run in parallel.\nThis approach is not the recommended one due to the high number of edge cases it involves and the fact that it can only be pragmatically used on collections where there is only one creator or the number of variations of how many creators there are is known ahead of time.\nInstead, we recommend using the transaction crawling approach.\nTransaction Crawling\nTransaction crawling involves getting all the transactions associated with the collection mint address and then parsing them to find the specific instructions that create collections. From there we can determine which mint accounts are part of the collection.\nThe algorithm for doing this is shown below:\nCall [getSignaturesForAddress](https://docs.solana.com/developing/clients/jsonrpc-api#getsignaturesforaddress) for the collection mint address to get all transaction signatures that in anyway involved the collection mint address.\n\nFor each signature, call [getTransaction](https://docs.solana.com/developing/clients/jsonrpc-api#gettransaction) to get the actual transaction data for each signature.\n\nParse the transactions to find the program ids and filter out any that do not involve the token-metadata program which has an address of metaqbxxUerdq28cj1RbAWkYQm3ybzjb6a8bt518x1s.\n\nWe only want to retrieve collection members that are verified, and the only two handlers in the token-metadata that verify collection members are verify_collection and set_and_verify which have the respective positions in the MetadataInstruction enum of 18 and 25, which are base58 values of K and S.\n\nFilter the instructions to only have ones with a data value of K or S to insure we only get those specific token-metadata handlers.\n\nThe metadata address being verified will be the first account passed into either of these handlers.\n\nAdd the metadata address to a Set to ensure no duplicates.\n\nOnce all metadata address are found, loop over them and call getAccountInfo to find the account data.\nDeserialize the account data into a Metadata struct/object, and find the mint address from the mint field. Add the mint address to a Set.\nThis final Set is your list of mint addresses for all items in the collection.\n\nExample Rust and TypeScript code for transaction crawling to get collection members can be found in the get-collection repository.","tokens":1703,"crawled_at":1791192811272}
+{"id":10153,"url":"https://stack.olas.network/open-autonomy/get_started/why_do_we_need_agent_services","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Why do we need agent services - Olas Stack Developer Documentation","text":"Why do we need agent services\n\nDecentralized ledger technologies (DLTs), such as blockchains, face several challenges, for example:\n\nthe blockchain trilemma,\n\nthe oracle problem,\n\nprivacy issues,\n\nledger storage space,\n\ncross chain compatibility,\n\n... and the sheer complexity of the user experience!\n\nIn contrast with the increasing growth of on-chain applications (particularly in DeFi), the off-chain design space has seen a lack of innovation. A lot of the technology is centralized, lacks fault tolerance, the code is often opaque and offers little composability.\n\nCurrently, a standardised approach for off-chain application development is missing in the blockchain space. This is where the Open AEA and the Open Autonomy frameworks come in, as open-source frameworks for developers to implement off-chain AI agents which are secured on-chain and can interact with smart contracts.\n\nLocation of agent instance in the crypto ecosystem\n\nagent instance go beyond simple, purely\nreactive applications (like smart contracts) and can show complex, proactive behaviours that contain off-chain logic without giving up on decentralization. Examples include, but are not limited to, triggering specific actions on external events, or executing machine learning models.","tokens":316,"crawled_at":1791192815177}
+{"id":10154,"url":"https://gov.uniswap.org/t/rfc-flashstake-enabling-upfront-yield-for-uniswap-liquidity-v2-v3/21410","domain":"gov.uniswap.org","chapter":"governance_daos","title":"[RFC] - Flashstake - Enabling upfront yield for Uniswap Liquidity V2&V3 - Requests for Comment - Uniswap Governance","text":"[RFC] - Flashstake - Enabling upfront yield for Uniswap Liquidity V2&V3\n\nRequests for Comment\n\nFlashySteve\n\nJune 6, 2023, 3:34pm\n\n1\n\nSummary\n\nFlashstake has worked closely with xToken Terminal over the last few months and through this partnership, we now have the infrastructure required to build time-based yield markets for any Uniswap V3 pair adding another dimension to liquidity provisioning not currently possible on any other DEX.\n\nFlashstake would like to request 200,000 ARB tokens which will be used to jump-start this new market through liquidity mining incentives (additional details below). The intention is to enable instant upfront yield for a handful of Uniswap V3 pairs to start and expand to new pairs as demand increases.\n\nWhat is Flashstake?\n\nFlashstake allows users to earn instant upfront yield.\n\nDeFi applications, like AAVE, only allow users to earn variable interest on their deposits over time. Flashstake strategies transform this variable yield into a fixed rate yield and pay the yield upfront to the user. This is achieved through a combination of interest rate swaps and a marketplace for the time value of money.\n\nFlashstake is currently live on Ethereum Mainnet, Arbitrum and Optimism.\n\nExample\n\nBob has 100 ETH and would like to start earning yield. Bob could deposit this into Rocket Pool and acquire rETH which increases in value over time relative to his deposit thereby slowly accumulating yield (eg 5% APR). Bob decides to instead Flashstake 100 ETH for 1 year into the Rocket Pool Flashstake strategy accepting a 4% APR paid upfront.\n\nBob has given up some of the yield he would have otherwise earned at Rocket Pool in exchange for a fixed rate of yield paid out immediately. Bob can withdraw his 100 ETH after 1 year has passed. Bob can also choose to unstake early by paying back the yield he received.\n\nYou can view a real transaction of a user depositing 125 ETH for 3 months to earn ~4,600 USD worth of rETH here. Note that Flashstake relies on LPs for jumpstarting new yield strategies and in the provided example transaction the upfront yield is coming from a Uniswap V3 swap.\n\nA deeper look\n\nUnder the hood when Bob deposited his 100 ETH for 6 months into the Flashstake Protocol he minted approximately 50 yield tokens (fy-rETH). The 100 ETH was automatically deposited into the associated underlying protocol which in this case is Rocket Pool. This ETH then goes on to generate yield block-by-block which drips into the associated yield pool.\n\nBob can choose to either sell his 50 fy-rETH (yield tokens) on the open market via Uniswap or burn these to redeem a proportional amount of yield from the Flashstake yield pool. Both avenues would result in a redeemable value. The Flashstake Dapp currently automatically chooses the most favourable path for Bob.\n\nAlice is happy to purchase the rights to yield generated from Bob by acquiring his fy-rETH tokens. Alice is happy to wait until the 100 ETH has generated a higher return from Rocket Pool.\n\nSummary\n\nRocket Pool is offering a 5% APR\n\nAlice is willing to give Bob an upfront yield such that Bob can lock in a 4% APR\n\nBob is willing to give up 1% APR to lock in the lower rate\n\nIn the early days of launching a new Flashstake Strategy, the yield pool starts at zero and subsequently cannot be used to redeem any meaningful upfront yield. We decided to partner with xToken Terminal to help incentivise liquidity for concentrated liquidity positions on Uniswap V3. This has allowed the open market to provide instant upfront yield with the expectation that yield tokens can be burned against the Flashstake Strategy in the near future as/when the yield pool grows.\n\nYou can read more about the inner workings of Flashstake in our documentation.\n\nMilestones/Achievements\n\nFlashstake launched with this architecture in August 2022 - you can visit the Dapp here\n\nFlashstake has since deployed on Mainnet, Optimism and Arbitrum\n\nFlashstake has never raised funds\n\nFlashstake received a grant from AAVE Grants DAO\n\nFlashstake TVL has roughly doubled after every major launch\n\nFlashstake currently supports GLP, sUSD, WETH, rETH, stETH and USDC through various underlying protocols such as GMX, AAVE V3, Rocket Pool and Lido\n\nFlashstake currently has $5M in strategy TVL and $11M total including staking\n\nProposal\n\nFlashstake is looking to launch a new Flashstaking Strategy which would allow Uniswap V3 liquidity providers to earn instant upfront yield. This would initially be limited to a handful of specific pools (currently undecided) with the intention to expand when sufficient demand is shown by the market.\n\nWe have performed a significant amount of research to make this possible and have worked closely with xToken Terminal to help facilitate this functionality. We have integrated with xToken Terminal’s contracts in a new innovative way to enable this functionality.\n\nFlashstake would like to request 200,000 ARB tokens to incentivise liquidity providers via xToken Terminal liquidity mining. These incentivised liquidity providers would be paying users upfront yield through v3 liquidity pools which would allow all future fees associated with Flashstaked liquidity to drip into the associated yield pool.\n\nExample:\n\nBob currently holds 500 UNI-V2 tokens associated with the USDC/DAI pool. It is expected that this would yield 35% APR (after 1 year in fees)\n\nBob Flashstakes 500 UNI-V2 tokens for 365 days and receives 500 fy-USDC/DAI tokens\n\nAlice is currently providing liquidity on Uniswap V3 (via xToken Terminal) for the token pair fy-USDC/USDC within the 0.1 to 0.25 range which roughly translates to upfront yield of 10% to 25% for Bob\n\nBob effectively gives up all rights to future yield on his LP tokens accepting an upfront yield rate of 25%\n\nAlice now holds 500 fy-USDC/DAI tokens which can be redeemed at any point in time for proportional ownership of the yield pool. In an efficient market, Alice would choose to redeem these in 365 days. If the yield rate remains at 35% or increases, Alice would earn the difference.\n\nNote: I have highlighted the section within the example above showing where these ARB tokens would be spent.\n\nNote: Bob could Flashstake UNI-V2 OR choose to deposit USDC and DAI (in the correct proportions) into xToken which then gets Flashstaked. A lot of this complexity would be abstracted away within our front end (in the simple mode).\n\nFlashstake has already been using xToken Terminal for liquidity mining towards concentrated liquidity positions in the same way explained above (for existing Flashstake Strategies). The most recent examples of these pools can be found here, here and here. More information on these campaigns can be found on this tweet thread.\n\nTo date, Flashstake has run these xToken campaigns between 1 to 4 weeks (due to limited resources) but we believe less tokens can be spent if these campaigns run for a longer duration which would give liquidity providers more certainty. We would like to run these campaigns for between 1 to 3 months giving each Flashstake Strategy the best opportunity to succeed.\n\nBenefits to Uniswap:\n\nSticky Uniswap TVL - The more we can incentivize our yield LPs, the more volume and TVL passes through these Flashstake Strategies which in turn leads to larger amounts of liquidity locked in for extended periods of time. (Bob Flashstaking for 365 days means this liquidity is locked for 1 year)\n\nMigrate liquidity from UniV2 to UniV3 - The more attractive Flashstake is for liquidity providers, the higher the chances they use Flashstake. Since Flashstake will support UniV2 tokens and will deposit this liquidity into UniV3, this would help migrate liquidity away from UniV2\n\nAdditional functionality for existing Uniswap V2 and V3 liquidity providers - The ability to Flashstake to earn instant upfront yield\n\nPath to Sustainability\n\nIt is important to highlight, rewards given to liquidity providers which allow for upfront yield in the early stages of a strategy, are temporary. As more capital enters the system, the yield generated increases with each block (based on trading fees), contributing to the growth of the yield pool.\n\nOnce the yield pool has reached a sufficient level, we expect the majority of all future Flashstakes to receive upfront yield directly from the protocol, without the need for additional incentives.\n\nThis means once a Flashstake yield pool becomes self-sufficient, it creates a constant activity of locked-up LP tokens for Uniswap pools.\n\n6 Likes\n\nRequest for Proposals - ARB Distribution\n\n[RFC] - Alastor | w3s - Create a UNI-ARB Working Group\n\nWeekly Governance Update\n\nWeekly Governance Update\n\npseudotwit\n\nJune 6, 2023, 7:43pm\n\n2\n\nI created an account just to tell you how amazing this project is\n\n1 Like\n\nBotanic\n\nJune 7, 2023, 2:00am\n\n3\n\nthis would bring Uniswap the edge it needs to stay relevant in times of ever-growing competition.\n\nThe opportunity to receive yield for liquidity mining in advance opens up a whole new level of DEFI composability. More sticky liquidity and more efficient use of funds, offsetting potential IL by deploying yield elsewhere for amplification of earnings.\n\nAlso Flashstake has proven itself to be a resilient protocol with no exploits of any kind to date, 2 audits of reputable auditors, and no exploitable admin functionalities in its immutable smart contracts.\n\nI’d be more than happy seeing this proposal pass and said functionality to be implemented ASAP.\n\n1 Like\n\nNa2\n\nJune 7, 2023, 12:43pm\n\n4\n\nSounds like a great way to expand Uniswap use-cases, go for it!\n\nDamboy\n\nJune 8, 2023, 12:23pm\n\n5\n\nThis proposal Looks great and will bring in some positive impacts.\n\nCan you please provide more details on how the integration with xToken Terminal’s contracts enables the functionality of incentivized liquidity mining for Flashstake?\n\nFlashySteve\n\nJune 8, 2023, 3:20pm\n\n6\n\nCan you please provide more details on how the integration with xToken Terminal’s contracts enables the functionality of incentivized liquidity mining for Flashstake?\n\nI will use the first link provided in my original post as the example xToken pool:\n\nhttps://app.xtokenterminal.io/mining/pools/mainnet/0xaBC95d77fb9D4538e6B00Bc8c9bE22DDB8df3004\n\nYou’ll notice on xToken the description says “Liquidity mining for concentrated liquidity range between 4% and 8%” and the LP it is incentivizing is fy-rETH/rETH\n\nBy adding liquidity to this LP position, by using xToken, xToken is forcing the UniswapV3 range to be a very specific price range so that 1 fy-rETH is worth somewhere between 0.04 and 0.08 rETH depending on current market prices at the time of adding/removing liquidity. In case this helps, another way to put it is that xToken enforces a concentrated UniV3 liquidity range of 0.04-0.08 rETH per 1 fy-rETH.\n\nHow this helps Flashstake?\n\nYou can refer to the Time Vault Pool: Liquidity Pool documentation https://docs.flashstake.io/time-vault-strategies-tvs/time-vault-pools#example-2-liquidity-pool\n\nLiquidity pools, such as this xToken incentivized UniV3 range, allows LPs to provide the upfront yield and speculate on upfront yield rates and earn incentives for being an LP. This is especially needed early on for new strategies as a way to jumpstart new strategies so there is upfront yield available from LPs instead of from the yield pool that hasn’t grown enough yet to provide meaningful yield.\n\nSo, for example, when we first launched the rETH (Rocket Pool) strategy on Flashstake, we spun up several xToken LP ranges of 4-8% (like I mentioned above), 6-12% and a promotional 10-15% that paid much higher incentives to help cover the IL that LPs would likely see. Different ranges lets LPs choose their risk tolerance and also consider what incentives and swaps APR they will earn, since every time an LP is used for upfront yield, that also generates a swap.\n\nEvery time someone does a Flashstake transaction to get upfront yield, the Flashstake dapp has a proxy https://docs.flashstake.io/smart-contracts/flash-protocol-proxy that will automatically determine the best upfront yield rate from either swapping or burning, which means either taking yield from LPs or taking yield from the yield pool, to give to the person wanting upfront yield. So in the case of the rETH strategy, the yield is being taken from LPs from Uniswap swaps. And xToken forced UniV3 ranges is helping make sure the % of upfront yield is in an appropriate range and able to be incentivized with tokens.\n\nThis proposal is to get ARB tokens so we can incentive with those tokens on xToken for Arbitrum strategies that will be developed that focus on giving upfront yield to LPs. We have never given upfront yield to LPs before, there is a synergy effect that this proposal also encourages more LPs on Uniswap for those who wish to use the Flashstake ecosystem to\n\nGet upfront yield as an LP\n\nProvide liquidity and earn ARB tokens incentives via xToken\n\nI hope that was able to fully answer your question?\n\n1 Like\n\ndel8\n\nJune 10, 2023, 11:38am\n\n7\n\nSeems like a natural evolution of defi to allow for interest rate swaps for liquidity provision. The immediate vs. delayed swap makes it even more attractive and allows for more efficiency.\n\nAs this is still fairly nascent in our space, it seems worthy to accelerate this development via token incentivization.\n\nI wonder what pools you would plan to use these incentives for. Do you think pools with certain assets would benefit in particular from this enhancemet or what would be your criteria?\n\nAlso, over what timeframe would you plan to spend the incentives?\n\nFlashySteve\n\nJune 10, 2023, 10:04pm\n\n8\n\nI think reviewing defillama to see which UniswapV3 pools on Arbitrum, with a good sized TVL that have good APR helps give insight to what may be the best ones to start with that would generate the most activity for the used incentives.\n\nhttps://defillama.com/yields?chain=Arbitrum&minTvl=1000000&maxTvl=&project=uniswap-v3\n\nThese look promising to start with\n\nWETH-USDC\n\nWETH-ARB\n\nARB-USDC\n\nThese are also being considered and may bring other partnership/marketing opportunities for Flashstake/Arbitrum/Uniswap/xToken:\n\nRDNT-WETH\n\nWETH-GMX\n\nFLASH-WETH\n\nFlashySteve\n\nJune 10, 2023, 10:10pm\n\n9\n\nI would estimate 6 months, but could be half to double that timeframe depending on other factors as market dynamics change over time, and if we see certain pools are having significantly more activity and more TVL than others, we may adjust which pools we incentivize and by how much, as we refill xToken incentives every few weeks.\n\nWe may find that certain pools require more or less incentives than anticipated to generate enough liquidity required to facilitate the upfront yield liquidity pool range needed for users to want to accept the upfront yield rate.\n\nHistorically, we have monitored the xToken pool incentives we have been providing with FLASH tokens, and adjusting these on a week to week basis. Sometimes increasing, sometimes lowering, sometimes creating an entirely new pool with a new range to properly incentivize what is required. When creating an xToken incentive, it is locked in: the total weeks, the total tokens allocated. During those weeks, APR rates, token prices, supply/demand of liquidity, all are constantly changing. We reevaluate the numbers regularly.\n\nTimeRows\n\nJune 11, 2023, 3:10am\n\n10\n\nThe example with rETH makes sense. The APR is fairly certain within a couple month range. So locking up to get 4% immediately, vs 5% without locking makes sense. With 1% providing a spread of profitability.\n\nThe main proposal case of using univ2 → univ3 liquidity providing positions is not as clear to me:\n\nHow is APR estimated for the year for a trading pair that is highly dependent on fluctuating volume? For example if volumes are high, and Flashstake pays out 20% immediately, but then volumes plummet in the following months, the Flashstake/users lose money?\n\nIs the LP lockup much shorter than the 1 year lock up of the rETH example to take into account the volume volatility? 1 Month lockups?\n\nWhat are the locked up LP liquidity ranges, since univ2 are being locked up and put into univ3 they will be full ranged liquidity providing?\n\nIf not full range, how are these positions actively managed to keep inrange? Is IL calculated in the expected APR?\n\nFlashySteve\n\nJune 11, 2023, 5:30am\n\n11\n\nHow is APR estimated for the year for a trading pair that is highly dependent on fluctuating volume? For example if volumes are high, and Flashstake pays out 20% immediately, but then volumes plummet in the following months, the Flashstake/users lose money?\n\nThe Flashstake docs “Where does the yield come from?” may help answer part of this.\n\nYield Pools and Liquidity Pools are used to pay the upfront amount. If volume plummet, this does not impact existing stakers, it only impacts how fast the yield pool will fill up to help facilitate future Flashstakes that “burn” instead of “swap” for upfront yield.\n\nIs the LP lockup much shorter than the 1 year lock up of the rETH example to take into account the volume volatility? 1 Month lockups?\n\nThe Liquidity Pools being incentivized with ARB tokens from this proposal (as we have done with FLASH tokens for incentivizing previous strategies at xToken) would be expected able to facilitate a decent amount of upfront yield, so I don’t anticipate there being any need to have a strategy maximum duration to be set lower than 3 months, with an ideal target of 6+ months as the maximum duration enabled.\n\nWhat are the locked up LP liquidity ranges, since univ2 are being locked up and put into univ3 they will be full ranged liquidity providing?\n\nIf not full range, how are these positions actively managed to keep inrange? Is IL calculated in the expected APR?\n\nThe UniV3 LPs locked up as Flashstakes, not to be confused with xToken LP incentives for anyone else reading this, would likely not be a full range but would benefit from concentrated liquidity improvements even if set in a very wide range. We would evaluate each LP on a case by case basis. For example, ARB has been within a tight price range of around $1-$2 since it launched so a USDC/ARB pair could have a tighter range than some other LP whose both tokens have more volatile price changes such as let’s say GMX/WETH.\n\n1 Like\n\nDamboy\n\nJune 12, 2023, 12:49pm\n\n12\n\nYes it does.\n\nBut What criteria will be used to select the specific pools for the initial Flashstake Strategy? How will Flashstake determine which pools have sufficient demand?\n\nDevSalim\n\nJune 12, 2023, 9:14pm\n\n13\n\nHey @Damboy I believe your questions have been answered in the above post here\n\nDid you have a particular question that you felt was not answered?\n\nThe initial uniswap pools would be chosen based on factors such as TVL and volume since these would be important since they influence the trading fees generated.\n\n1 Like\n\nDamboy\n\nJune 12, 2023, 9:46pm\n\n14\n\nThanks for the response @DevSalim.\n\n0xkeyrock.eth\n\nJune 15, 2023, 10:03am\n\n15\n\nWe support this proposal and it fits within our logic regarding optimal budget allocation if the Uniswap community has a similar consensus to us as described here.\n\npratik_coinchange\n\nJuly 23, 2023, 1:16am\n\n16\n\nDo you have API for other UIs to integrate?\n\nDevSalim\n\nJuly 29, 2023, 10:54am\n\n17\n\nThe contracts are immutable and exist on the deployed networks. This means anyone can interact with them and it does not require a specific API.\n\nWe have deployed subgraphs on each network and you can find the links to them here: Addresses and Links - Flashstake\n\nYou should be able to find all the necessary information in the documentation linked above. If you require any additional support, feel free to join the Flashstake discord.\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nProposal: Uniswap Liquidity Program v0.1\n\nRequests for Comment\n\n18\n\n4446\n\nSeptember 2, 2021\n\nConsensus Check - Should Uniswap incentivize Liquidity on Optimism and Arbitrum\n\nConsensus Check\n\n18\n\n8599\n\nOctober 28, 2022\n\nConsensus Check - Begin Uniswap Liquidity Program v0.1\n\nConsensus Check\n\n9\n\n4844\n\nSeptember 10, 2021\n\nUniswap Revitalization and Growth\n\nRequests for Comment\n\n75\n\n10905\n\nJuly 15, 2024\n\nUniswap Liquidity Program v0.1\n\nRequests for Comment\n\n44\n\n11813\n\nSeptember 28, 2022","tokens":5053,"crawled_at":1791192818071}
+{"id":10155,"url":"https://a16zcrypto.com/posts/article/beyond-51-attacks","domain":"a16zcrypto.com","chapter":"research","title":"Beyond 51% attacks: Precisely characterizing blockchain achievable resilience - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nBeyond 51% attacks: Precisely characterizing blockchain achievable resilience\nJoachim Neu, Srivatsan Sridhar, and Ertem Nusret Tas\n02.27.25\n\nTags & Share Tags\nconsensus\nresearch\nsecurity\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nA central question in the security of blockchains is what percent of validators adversaries can control while the blockchain remains safe and live. Is it 50%? 33%? Or, as Vitalik Buterin has written, 99%? A great deal rests on the answer. If there is a way to achieve resilience even against adversaries that control almost all of a blockchain’s security-critical resource, why do almost all deployed blockchains content themselves with less?\n\nThe answer to what percentage is right depends on how clients are modeled. Are the clients sleepy or always-on? Are they silent or communicating? Can validators be sleepy too? And is the network synchronous or partially synchronous? In a new paper, we (with Dionysis Zindros of Common Prefix, and David Tse of Stanford University and BabylonChain) systematize models for consensus across these four dimensions. Being systematic about the nature of clients allows us to tightly characterize the achievable safety and liveness resiliences with matching possibilities and impossibilities for each of the sixteen models. We’re able to unify folklore and earlier results, and fill gaps left in the literature with new protocols and impossibility theorems.\n\nOne of our key takeaways is that when clients in a blockchain system can communicate reliably (that is in particular, if clients can forward messages they receive to each other — which is the case for many blockchains that use gossip-style peer-to-peer networking) then the system can remain safe even if the adversary controls all of the blockchain’s security-critical resource.\n\nState-machine replication: Background\n\nState-machine replication (SMR) consensus protocols are the backbone of blockchain systems. These protocols provide a mechanism with which the blockchain’s parties can reach consensus on an order in which to execute incoming transaction requests. Think of this as every party at every point in time outputs a sequence of transactions that it considers confirmed, and then executes those transactions in that order. By executing transactions in the same order, each party effectively runs a replica of the state machine of the blockchain’s execution engine. An SMR consensus protocol is secure if it provides two properties: safety, meaning that transactions are confirmed in the same order across honest parties and across time (i.e., one party’s confirmed transaction sequence is a prefix of any other’s, or vice versa); and liveness, meaning that honest transaction requests are eventually included in every party’s confirmed transaction order.\n\nThe SMR consensus protocols used in blockchains must be Byzantine-fault tolerant (BFT), that is, they should provide each security property even if a fraction of the parties behave adversarially. The adversary fraction of validators, the parties tasked with reaching consensus, up to which safety and liveness can be guaranteed — whether that’s 33%, 50%, or Vitalik’s 99% — are called safety resilience and liveness resilience of the protocol, respectively.\n\nSo what’s the tolerable percentage of malicious validators?\n\nThe question, then, is: What is the best possible safety/liveness resilience any blockchain protocol could hope to achieve? Is it 33%, 50%, or 99%? Decades ago, researchers showed that the answer depends on the reliability of the communication network connecting validators of the blockchain: If the network is guaranteed to deliver messages between honest validators within a short period of time (we call this setting synchronous), then higher resiliences can be achieved than if the network may suffer from outages like network partitions where network delay can become quite large (a setting called partial synchrony). This explains some of the conundrum — namely, the difference of 33% and 50% resilience between some protocols.\n\nBut the answer also critically depends on the modeling details of clients. Client modeling assumptions determine the extent to which 99% resilience can be achieved.\n\nBut first, what are clients? Blockchains comprise not only validators — active participants in the consensus protocol, such as stakeholders in a proof-of-stake blockchain. There are also clients. While they do not actively contribute to consensus, they represent the users of the system, who, for instance, may run wallet software and monitor the chain for payments and ship merchandise in response. The characteristics of those clients matters a lot: Are these clients sleepy — occasionally taking a prolonged break from following the chain, or always on? Are they silent, or can they communicate with other clients? Speaking of sleepiness: Can validators be sleepy, too? The answers to these questions determine if and how 99% resilience can be achieved.\n\nIn our new paper, we systematize models for BFT SMR consensus across four dimensions: sleepy/always-on clients, silent/communicating clients, sleepy/always-on validators, and network synchrony/partial-synchrony. We then tightly characterize the achievable safety and liveness resiliences with matching possibility results and impossibility results for each of the resulting sixteen models. This means that for every safety/liveness resilience pair, we either show a protocol that achieves it, or we prove mathematically that there cannot be any protocol that achieves it. The following figure summarizes the results (cf Figure 1 in the paper to understand which regions of which plot are new or found in earlier works, respectively).\n\nSpecifically, the figure shows the safety/liveness resilience pairs achievable or unachievable for each of the models considered. The liveness resilience is on the horizontal axis, and the safety resilience is on the vertical axis. Blue shaded regions are resilience pairs that are achievable, and red shaded regions are the ones that aren’t. Earlier works have focused on the first and last row (sleepy silent clients and always-on communicating clients), and on the left and right columns (classical synchronous and partially synchronous networks, both with always-on validators). For instance, the classic 50% and 33% results are shown in sub-figures (a) and (c), respectively, while Vitalik Buterin’s 99% result is found in sub-figure (j). Our contributions are in the second and third row (always-on silent clients and sleepy communicating clients) as well as the middle column (sleepy validators). (In the four remaining scenarios corresponding to partial synchrony with sleepy validators: No resilience can be achieved in these settings due to the availability-finality dilemma, so the respective plots would be all red, and are omitted in the figure.)\n\nThe upshot? When clients in a blockchain system can communicate, which is the case for many blockchains that use gossip-style peer-to-peer networking, then safety/liveness resilience can be increased beyond 50% under some circumstances — for example, in sub-figure (g), with synchronous, always-on validators and sleepy but communicating clients, one of the resiliences (safety or liveness) can be increased to 99% while retaining 50% for the other resilience (liveness or safety). This is an example of how we can build on folklore with more careful analysis, and combine 50% with 99%.\n\nIf you want to know more, check out the paper on IACR ePrint.\n\n***\n\nJoachim Neu is a postdoc Research Associate at a16z Crypto Research. Previously, he earned a PhD at Stanford, advised by David Tse. His current research focus is blockchain-era consensus and decentralized-systems security. His broader interests include distributed computing and systems, applied cryptography, and networking and communications.\n\nSrivatsan Sridhar is a PhD student at Stanford University, advised by David Tse, and a senior researcher at BabylonChain. He has also held internships with Mysten Labs, Protocol Labs, and Subspace Labs.\n\nErtem Nusret Tas is a PhD student in Electrical Engineering at Stanford University, working under the supervision of David Tse. He has also held internships with Celestia, BabylonChain, and a16z crypto research.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nThe content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":2717,"crawled_at":1791192821779}
+{"id":10156,"url":"https://docs.near.org/web3-apps/what-is","domain":"docs.near.org","chapter":"layer1_layer2","title":"What are Web3 Apps? - NEAR Docs","text":"Web3 Applications - also known as decentralized apps (dApps) - leverage smart contracts and blockchain data to offer transparency, security and giving back control to users over their assets and data.\n\nNEAR simplifies building Web3 apps for the general public, making it easy to interact with different blockchains, while helping to onboard users that are not familiarized with crypto.\n\n​\n\nWhy Integrate NEAR Protocol with your App?\n\nAny application can benefit from integrating NEAR, including games, financial services, social platforms, and more.\n\nEasy Onboarding: Users can create accounts using familiar methods such as email login. Furthermore, applications can cover all transactional costs for their users, so they never have to worry about handling crypto.\n\nOwnership: Users have true ownership of digital assets within their accounts. Fungible Tokens can be used as reward systems, Non-Fungible Tokens can denote holdings, and wallets can represent digital identities.\n\nFast, Cheap and Scalable: Near’s efficient consensus mechanism and fee model make transactions cost effective for both users and developers.\n\nSecurity & Transparency: All transactions and data on the blockchain is transparent and auditable, thus ensuring trust in the application’s behavior.\n\nWas this page helpful?","tokens":324,"crawled_at":1791192831184}
+{"id":10157,"url":"https://hyperliquid.gitbook.io/hyperliquid-docs/about-hyperliquid.md","domain":"hyperliquid.gitbook.io","chapter":"defi_protocols","title":"","text":"> For the complete documentation index, see [llms.txt](https://hyperliquid.gitbook.io/hyperliquid-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hyperliquid.gitbook.io/hyperliquid-docs/about-hyperliquid.md).\n\n# About Hyperliquid\n\n### **What is Hyperliquid?**\n\nHyperliquid is a performant blockchain built with the vision of a fully onchain open financial system. Liquidity, user applications, and trading activity synergize on a unified platform that will ultimately house all of finance.&#x20;\n\n### Technical overview\n\nHyperliquid is a layer one blockchain (L1) written and optimized from first principles.&#x20;\n\nHyperliquid uses a custom consensus algorithm called HyperBFT inspired by HotStuff and its successors. Both the algorithm and networking stack are optimized from the ground up to support the unique demands of the L1.&#x20;\n\nHyperliquid state execution is split into two broad components: HyperCore and the HyperEVM. HyperCore includes fully onchain perpetual futures and spot order books. Every order, cancel, trade, and liquidation happens transparently with one-block finality inherited from HyperBFT. HyperCore currently supports 200k orders / second, with throughput constantly improving as the node software is further optimized.\n\nThe HyperEVM brings the familiar general-purpose smart contract platform pioneered by Ethereum to the Hyperliquid blockchain. With the HyperEVM, the performant liquidity and financial primitives of HyperCore are available as permissionless building blocks for all users and builders. See the HyperEVM documentation section for more technical details.\n\n<figure><img src=\"https://2356094849-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyUdp569E6w18GdfqlGvJ%2Fuploads%2FPgVwhFtylBB2kaxhQtZz%2FStack.png?alt=media&amp;token=fb5b86d0-95be-41bb-91d3-d08c8603c284\" alt=\"\" width=\"563\"><figcaption></figcaption></figure>","tokens":497,"crawled_at":1791192888762}
+{"id":10158,"url":"https://docs.near.org/chain-abstraction/what-is","domain":"docs.near.org","chapter":"layer1_layer2","title":"What is Chain Abstraction? - NEAR Docs","text":"Through a combination of innovative technologies, NEAR enables developers to build applications that work seamlessly across multiple blockchains while abstracting away the underlying complexity for both developers and end users.\n\nMulti-Chain Accounts\nChain Signatures allow NEAR accounts and smart contracts to sign transactions for all other chains (including Bitcoin, Ethereum and Solana)\n\nSwaps via Intents\nA decentralized system where users simply express desired outcomes (like “swap BTC for ETH at the best price”), and a network of solvers competes to fulfill these intents optimally\n\nOmniBridge\nA multi-chain bridge that enables secure and efficient cross-chain transfers. The bridge serves as both a token factory and custodian, managing native and bridged tokens through a unified interface\n\n​\n\nWhy Chain Abstraction Matters\n\nBy building on NEAR, developers do not need to worry about the complexities of integrating with multiple blockchains. Instead, they can focus on building great applications that work seamlessly across all chains.\nMeanwhile, users can enjoy a smooth experience, using unified accounts and assets without needing to even understand on which blockchain they are operating.\n\nBenefits for Developers\n\nIntegrate with multiple blockchains through a single NEAR API\n\nFocus on application logic instead of blockchain complexity\n\nReach users regardless of their preferred blockchain network\n\nBenefits for Users\n\nOperate across all chains using a single NEAR account\n\nAccess assets and services from multiple blockchains seamlessly\n\nEnjoy a unified and intuitive user experience\n\nExample: Cross-Chain NFT Marketplace\n\nImagine building a digital art marketplace where users can purchase NFTs from different blockchains (Ethereum, Solana, etc.). Without chain abstraction, you’d need to:\nImplement multiple blockchain connections\n\nHandle different wallet types\n\nManage cross-chain transfers\n\nBuild complex UIs to explain blockchain concepts\n\nWith chain abstraction, both you and your users just focus on the core experience: browsing and trading art. All blockchain complexity is handled automatically behind the scenes.\n\nWas this page helpful?","tokens":542,"crawled_at":1791192889968}
+{"id":10159,"url":"https://www.metaplex.com/docs/smart-contracts/token-metadata/fetch","domain":"www.metaplex.com","chapter":"docs","title":"Fetching Assets | Token Metadata","text":"Token Metadata is a legacy program. It remains supported, but is not recommended for new projects. Use Core instead.\n\nNow that we know how to create and mint the various onchain accounts of our assets, let's learn how to fetch them.\nDigital Assets\nAs mentioned in the previous page, an asset — fungible or not — requires multiple onchain accounts to be created. Depending on the Token Standard of the asset, some accounts may not be required. Here's a quick overview of these accounts:\nMint account (from the SPL Token program): It defines the core properties of the underlying SPL token. This is the entry point to any asset as all other accounts derive from it.\nMetadata account: It provides additional data and features to the underlying SPL token.\nMaster Edition or Edition account (only for Non-Fungibles): It enables printing multiple copies of an original NFT. Even when an NFT does not allow printing editions, the Master Edition account is still created as it is used as the Mint authority and Freeze authority of the Mint account to ensure its non-fungibility.\nIn order to make fetching assets easier, our SDKs offer a set of helper methods that allow us to fetch all the relevant accounts of an asset in one go. We call the data type that stores all these accounts a Digital Asset. In the next sub-sections, we will go through the various ways to fetch Digital Assets.\nDigital Asset definition\n\nimport { PublicKey } from '@metaplex-foundation/umi'\n\nimport { Mint } from '@metaplex-foundation/mpl-toolbox'\n\nimport {\n\nMetadata,\n\nMasterEdition,\n\nEdition,\n\n} from '@metaplex-foundation/mpl-token-metadata'\n\nexport type DigitalAsset = {\n\npublicKey: PublicKey\n\nmint: Mint\n\nmetadata: Metadata\n\nedition?:\n\n| ({ isOriginal: true } & MasterEdition)\n\n| ({ isOriginal: false } & Edition)\n\n}\n\nFetch By Mint\nThis helper fetches a single Digital Asset from the public key of its Mint account.\n\n1import { publicKey } from '@metaplex-foundation/umi';\n\n2import { fetchDigitalAsset } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4// Assuming umi is set up with mplTokenMetadata plugin\n\n5// See getting-started for full setup\n\n6\n\n7const mintAddress = publicKey('Ay1U9DWphDgc7hq58Yj1yHabt91zTzvV2YJbAWkPNbaK');\n\n8\n\n9// Fetch a digital asset by its mint address\n\n10const asset = await fetchDigitalAsset(umi, mintAddress);\n\n11\n\n12console.log('Asset:', asset.publicKey);\n\n13console.log('Metadata:', asset.metadata.publicKey);\n\n14console.log('Name:', asset.metadata.name);\n\n15console.log('URI:', asset.metadata.uri);\n\n16console.log('Seller Fee:', asset.metadata.sellerFeeBasisPoints);\n\n1import { address } from '@solana/addresses';\n\n2import { fetchDigitalAsset } from '@metaplex-foundation/mpl-token-metadata-kit';\n\n3\n\n4// Assuming rpc is set up\n\n5// See getting-started for full setup\n\n6\n\n7const mintAddress = address('Ay1U9DWphDgc7hq58Yj1yHabt91zTzvV2YJbAWkPNbaK');\n\n8\n\n9// Fetch a digital asset by its mint address\n\n10const asset = await fetchDigitalAsset(rpc, mintAddress);\n\n11\n\n12console.log('Asset:', asset.address);\n\n13console.log('Name:', asset.metadata.name);\n\n14console.log('URI:', asset.metadata.uri);\n\n15console.log('Seller Fee:', asset.metadata.sellerFeeBasisPoints);\n\n16if (asset.edition) {\n\n17 console.log('Is Original:', asset.edition.isOriginal);\n\n18}\n\nFetch By Metadata\nThis helper fetches a single Digital Asset from the public key of its Metadata account. This is slightly less efficient than the previous helper as we first need to fetch the content of the Metadata account to find the Mint address but if you only have access to the Metadata public key, this can be helpful.\n\n1import { publicKey } from '@metaplex-foundation/umi';\n\n2import { fetchDigitalAssetByMetadata } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4// Assuming umi is set up with mplTokenMetadata plugin\n\n5// See getting-started for full setup\n\n6\n\n7const metadataAddress = publicKey('Gz3vYbpsB2agTsAwedtvtTkQ1CG9Cpo6eTq59rrEGCKF');\n\n8\n\n9// Fetch a digital asset by its metadata address\n\n10const asset = await fetchDigitalAssetByMetadata(umi, metadataAddress);\n\n11\n\n12console.log('Asset:', asset.publicKey);\n\n13console.log('Metadata:', asset.metadata.publicKey);\n\n14console.log('Name:', asset.metadata.name);\n\n15console.log('URI:', asset.metadata.uri);\n\n1import { address } from '@solana/addresses';\n\n2import { fetchDigitalAssetByMetadata } from '@metaplex-foundation/mpl-token-metadata-kit';\n\n3\n\n4// Assuming rpc is set up\n\n5// See getting-started for full setup\n\n6\n\n7const metadataAddress = address('Gz3vYbpsB2agTsAwedtvtTkQ1CG9Cpo6eTq59rrEGCKF');\n\n8\n\n9// Fetch a digital asset by its metadata address\n\n10const asset = await fetchDigitalAssetByMetadata(rpc, metadataAddress);\n\n11\n\n12console.log('Asset:', asset.address);\n\n13console.log('Name:', asset.metadata.name);\n\n14console.log('URI:', asset.metadata.uri);\n\nFetch All By Mint List\nThis helper fetches as many Digital Assets as there are Mint public keys in the provided list.\n\n1import { publicKey } from '@metaplex-foundation/umi';\n\n2import { fetchAllDigitalAsset } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4// Assuming umi is set up with mplTokenMetadata plugin\n\n5// See getting-started for full setup\n\n6\n\n7const mints = [\n\n8 publicKey('Ay1U9DWphDgc7hq58Yj1yHabt91zTzvV2YJbAWkPNbaK'),\n\n9 publicKey('8TQdiAzdZZEaKtHGjvnLMXhVGjfNsqMgPGBQPPsWYgo8'),\n\n10];\n\n11\n\n12// Fetch multiple digital assets by their mint addresses\n\n13const assets = await fetchAllDigitalAsset(umi, mints);\n\n14\n\n15assets.forEach((asset) => {\n\n16 console.log('Asset:', asset.publicKey);\n\n17 console.log('Name:', asset.metadata.name);\n\n18});\n\n1import { address } from '@solana/addresses';\n\n2import { fetchAllDigitalAsset } from '@metaplex-foundation/mpl-token-metadata-kit';\n\n3\n\n4// Assuming rpc is set up\n\n5// See getting-started for full setup\n\n6\n\n7const mints = [\n\n8 address('Ay1U9DWphDgc7hq58Yj1yHabt91zTzvV2YJbAWkPNbaK'),\n\n9 address('8TQdiAzdZZEaKtHGjvnLMXhVGjfNsqMgPGBQPPsWYgo8'),\n\n10];\n\n11\n\n12// Fetch multiple digital assets by their mint addresses\n\n13const assets = await fetchAllDigitalAsset(rpc, mints);\n\n14\n\n15assets.forEach((asset) => {\n\n16 console.log('Asset:', asset.address);\n\n17 console.log('Name:', asset.metadata.name);\n\n18});\n\nFetch All By Creator\nThis helper fetches all Digital Assets by creator. Since creators can be located in five different positions in the Metadata account, we must also provide the creator position we are interested in. For instance, if we know that for a set of NFTs, the first creator is creator A and the second creator B, we will want to search for creator A in position 1 and creator B in position 2.\nThis helper requires RPC calls to filter accounts and is available in the Umi SDK. For the Kit SDK, consider using a DAS (Digital Asset Standard) API provider for efficient queries.\n\n1import { publicKey } from '@metaplex-foundation/umi';\n\n2import { fetchAllDigitalAssetByCreator } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4// Assuming umi is set up with mplTokenMetadata plugin\n\n5// See getting-started for full setup\n\n6\n\n7const creator = publicKey('creatorAddress...');\n\n8\n\n9// Assets where the creator is first in the Creator array\n\n10const assetsA = await fetchAllDigitalAssetByCreator(umi, creator);\n\n11\n\n12// Assets where the creator is second in the Creator array\n\n13const assetsB = await fetchAllDigitalAssetByCreator(umi, creator, {\n\n14 position: 2,\n\n15});\n\n16\n\n17console.log('Assets with creator at position 1:', assetsA.length);\n\n18assetsA.forEach((asset) => {\n\n19 console.log('Name:', asset.metadata.name);\n\n20});\n\nFetch All By Owner\nThis helper fetches all Digital Assets by owner.\nThis helper requires RPC calls to filter accounts and is available in the Umi SDK. For the Kit SDK, consider using a DAS (Digital Asset Standard) API provider for efficient queries.\n\n1import { publicKey } from '@metaplex-foundation/umi';\n\n2import { fetchAllDigitalAssetByOwner } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4// Assuming umi is set up with mplTokenMetadata plugin\n\n5// See getting-started for full setup\n\n6\n\n7const owner = publicKey('ownerAddress...');\n\n8\n\n9// Fetch all digital assets owned by a wallet\n\n10const assets = await fetchAllDigitalAssetByOwner(umi, owner);\n\n11\n\n12assets.forEach((asset) => {\n\n13 console.log('Name:', asset.metadata.name);\n\n14 console.log('URI:', asset.metadata.uri);\n\n15});\n\nFetch All By Update Authority\nThis helper fetches all Digital Assets from the public key of their update authority.\nThis helper requires RPC calls to filter accounts and is available in the Umi SDK. For the Kit SDK, consider using a DAS (Digital Asset Standard) API provider for efficient queries.\n\n1import { publicKey } from '@metaplex-foundation/umi';\n\n2import { fetchAllDigitalAssetByUpdateAuthority } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4// Assuming umi is set up with mplTokenMetadata plugin\n\n5// See getting-started for full setup\n\n6\n\n7const updateAuthority = publicKey('updateAuthorityAddress...');\n\n8\n\n9// Fetch all digital assets by update authority\n\n10const assets = await fetchAllDigitalAssetByUpdateAuthority(umi, updateAuthority);\n\n11\n\n12console.log('Found', assets.length, 'assets');\n\n13assets.forEach((asset) => {\n\n14 console.log('Name:', asset.metadata.name);\n\n15 console.log('Mint:', asset.publicKey);\n\n16});\n\nDigital Assets With Token\nNote that the Digital Asset data structure mentioned above does not provide any information about the owner of the asset. This first definition only focuses on the onchain accounts that are required regardless of their owners. However, in order to provide a more complete picture of an asset, we may also need to know who owns it. This is where the Digital Asset With Token data structure comes in. It is an extension of the Digital Asset data structure that also includes the following accounts:\nToken account (from the SPL Token program): It defines the relationship between a Mint account and its owner. It stores important data such as the amount of tokens owned by the owner. In the case of NFTs, the amount is always 1.\nToken Record account (for PNFTs only): It defines additional token-related information for Programmable Non-Fungibles such as its current Token Delegate and its role.\nNote that, for fungible assets, the same Digital Asset will likely be associated with multiple owners via multiple Token accounts. Therefore, there can be multiple Digital Asset With Token for the same Digital Asset.\nHere as well, we offer a set of helpers to fetch Digital Assets With Token.\nDigital Asset With Token definition\n\nimport { Token } from '@metaplex-foundation/mpl-toolbox'\n\nimport {\n\nDigitalAsset,\n\nTokenRecord,\n\n} from '@metaplex-foundation/mpl-token-metadata'\n\nexport type DigitalAssetWithToken = DigitalAsset & {\n\ntoken: Token\n\ntokenRecord?: TokenRecord\n\n}\n\nFetch By Mint\nThis helper fetches a single Digital Asset With Token from the public key of its Mint account. This is mostly relevant for Non-Fungible assets since it will only return one Digital Asset With Token, regardless of how many exist for a Fungible asset.\nThe Kit SDK requires knowing either the token address or the owner. Use the \"Fetch By Mint and Owner\" helper below if you know the owner.\n\n1import { publicKey } from '@metaplex-foundation/umi';\n\n2import { fetchDigitalAssetWithTokenByMint } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4// Assuming umi is set up with mplTokenMetadata plugin\n\n5// See getting-started for full setup\n\n6\n\n7const mint = publicKey('Ay1U9DWphDgc7hq58Yj1yHabt91zTzvV2YJbAWkPNbaK');\n\n8\n\n9// Fetch a digital asset with its token account by mint address\n\n10const asset = await fetchDigitalAssetWithTokenByMint(umi, mint);\n\n11\n\n12console.log('Asset:', asset.publicKey);\n\n13console.log('Name:', asset.metadata.name);\n\n14console.log('Token Owner:', asset.token.owner);\n\n15console.log('Token Amount:', asset.token.amount);\n\nFetch By Mint and Owner\nThis helper is more performant than the previous helper but requires that we know the owner of the asset.\n\n1import { publicKey } from '@metaplex-foundation/umi';\n\n2import { fetchDigitalAssetWithAssociatedToken } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4// Assuming umi is set up with mplTokenMetadata plugin\n\n5// See getting-started for full setup\n\n6\n\n7const mint = publicKey('Ay1U9DWphDgc7hq58Yj1yHabt91zTzvV2YJbAWkPNbaK');\n\n8const owner = publicKey('ownerAddress...');\n\n9\n\n10// Fetch a digital asset with its associated token account\n\n11const asset = await fetchDigitalAssetWithAssociatedToken(umi, mint, owner);\n\n12\n\n13console.log('Asset:', asset.publicKey);\n\n14console.log('Name:', asset.metadata.name);\n\n15console.log('Token Owner:', asset.token.owner);\n\n16console.log('Token Amount:', asset.token.amount);\n\n1import { address } from '@solana/addresses';\n\n2import { fetchDigitalAssetWithAssociatedToken } from '@metaplex-foundation/mpl-token-metadata-kit';\n\n3\n\n4// Assuming rpc is set up\n\n5// See getting-started for full setup\n\n6\n\n7const mintAddress = address('Ay1U9DWphDgc7hq58Yj1yHabt91zTzvV2YJbAWkPNbaK');\n\n8const ownerAddress = address('ownerAddress...');\n\n9\n\n10// Fetch a digital asset with its associated token account\n\n11const asset = await fetchDigitalAssetWithAssociatedToken(rpc, mintAddress, ownerAddress);\n\n12\n\n13console.log('Asset:', asset.address);\n\n14console.log('Name:', asset.metadata.name);\n\n15console.log('Token Owner:', asset.token.owner);\n\n16console.log('Token Amount:', asset.token.amount);\n\nFetch All By Owner\nThis helper fetches all Digital Assets With Token from a given owner.\nThis helper requires RPC calls to filter accounts and is available in the Umi SDK. For the Kit SDK, consider using a DAS (Digital Asset Standard) API provider for efficient queries.\n\n1import { publicKey } from '@metaplex-foundation/umi';\n\n2import { fetchAllDigitalAssetWithTokenByOwner } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4// Assuming umi is set up with mplTokenMetadata plugin\n\n5// See getting-started for full setup\n\n6\n\n7const owner = publicKey('ownerAddress...');\n\n8\n\n9// Fetch all digital assets with their token accounts by owner\n\n10const assets = await fetchAllDigitalAssetWithTokenByOwner(umi, owner);\n\n11\n\n12console.log('Found', assets.length, 'assets');\n\n13assets.forEach((asset) => {\n\n14 console.log('Name:', asset.metadata.name);\n\n15 console.log('Token Amount:', asset.token.amount);\n\n16});\n\nFetch All By Mint\nThis helper fetches all Digital Assets With Token from the public key of a Mint account. This is particularly relevant for Fungible assets since it fetches all Token accounts.\nThis helper requires RPC calls to filter accounts and is available in the Umi SDK. For the Kit SDK, consider using a DAS (Digital Asset Standard) API provider for efficient queries.\n\n1import { publicKey } from '@metaplex-foundation/umi';\n\n2import { fetchAllDigitalAssetWithTokenByMint } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4// Assuming umi is set up with mplTokenMetadata plugin\n\n5// See getting-started for full setup\n\n6\n\n7const mint = publicKey('Ay1U9DWphDgc7hq58Yj1yHabt91zTzvV2YJbAWkPNbaK');\n\n8\n\n9// Fetch all token accounts for a given mint\n\n10const assets = await fetchAllDigitalAssetWithTokenByMint(umi, mint);\n\n11\n\n12console.log('Found', assets.length, 'token accounts');\n\n13assets.forEach((asset) => {\n\n14 console.log('Owner:', asset.token.owner);\n\n15 console.log('Amount:', asset.token.amount);\n\n16});\n\nFetch All By Owner and Mint\nThis helper fetches all Digital Assets With Token from both an owner and a Mint account. This can be useful for Fungible assets that have more than one Token account for a given owner.\nThis helper requires RPC calls to filter accounts and is available in the Umi SDK. For the Kit SDK, consider using a DAS (Digital Asset Standard) API provider for efficient queries.\n\n1import { publicKey } from '@metaplex-foundation/umi';\n\n2import { fetchAllDigitalAssetWithTokenByOwnerAndMint } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4// Assuming umi is set up with mplTokenMetadata plugin\n\n5// See getting-started for full setup\n\n6\n\n7const owner = publicKey('ownerAddress...');\n\n8const mint = publicKey('Ay1U9DWphDgc7hq58Yj1yHabt91zTzvV2YJbAWkPNbaK');\n\n9\n\n10// Fetch all token accounts for a given owner and mint\n\n11const assets = await fetchAllDigitalAssetWithTokenByOwnerAndMint(umi, owner, mint);\n\n12\n\n13console.log('Found', assets.length, 'token accounts');\n\n14assets.forEach((asset) => {\n\n15 console.log('Token Address:', asset.token.publicKey);\n\n16 console.log('Amount:', asset.token.amount);\n\n17});","tokens":4108,"crawled_at":1791192914664}
+{"id":10160,"url":"https://docs.synthetix.io/llms.txt","domain":"docs.synthetix.io","chapter":"defi_protocols","title":"","text":"# Synthetix\n\n> Trader documentation for Synthetix perpetual contracts\n\n## Docs\n\n- [Contact Support](/contact-support): If you need help with Synthetix, you can contact **Support** through the chat widget in the bottom-right corner of Synthetix Docs.\n- [Frequently Asked Questions](/faq): Find answers to common questions about Synthetix Exchange.\n- [Getting Started](/getting-started): New to Synthetix? Start here.\n- [Official Links](/official-links): Use the official Synthetix links below to access the exchange, documentation, announcements, community channels, developer resources, and other official services.\n- [Auto-Deleveraging (ADL)](/trading/adl): Auto-deleveraging is a last-resort risk mechanism that activates when a liquidated account reaches **bankruptcy**, meaning its collateral is insufficient to cover the loss at the current mark price. In this situation, the exchange cannot absorb the loss through normal liquidation, so it is instead distributed to the most profitable, most leveraged positions on the opposite side of the market.\n- [Advanced Order Types](/trading/advanced-order-types): Advanced order types provide additional control over execution, pricing and timing compared to standard order types.\n- [Exporting History](/trading/exporting-history): Synthetix allows you to export your **trade, order, funding, PnL, and other historical activity** for purposes such as **tax reporting, record keeping, or further analysis**.\n- [Fees](/trading/fees): Trading on Synthetix Mainnet involves fees that are applied when opening and closing positions. Collateral operations such as withdrawals, voluntary Swap, and forced auto-exchange can also have fees.\n- [Funding](/trading/funding): Perpetual futures use funding to keep prices in line with the spot market. Funding is a recurring payment between longs and shorts based on the difference between the perp's mark price and the index price of the underlying asset.\n- [Glossary](/trading/glossary)\n- [Leverage & Margin](/trading/leverage-margin): Using leverage amplifies both gains and losses. Higher leverage uses less margin, but it also brings your liquidation threshold closer.\n- [Limit Orders](/trading/limit-orders): Limit Orders allow you to specify the price at which you want to buy or sell. They are designed for traders who want greater control over their execution price rather than immediate execution.\n- [Liquidations](/trading/liquidations): Liquidation occurs when your account no longer has enough value to maintain your open positions and meet the required maintenance margin.\n- [Managing Open Orders](/trading/managing-open-orders): Once you've placed an order, you can manage it directly from the Open Orders tab in the portfolio table. This guide explains the actions available while your order is waiting to be executed.\n- [Managing Positions](/trading/managing-positions): Once you've opened a position, you can monitor its performance and manage it directly from the trading interface. This guide explains the actions available while your position is open.\n- [Market Orders](/trading/market-orders): Market Orders allow you to buy or sell immediately using the best available market price. They are designed for traders who prioritise execution speed over controlling the exact execution price.\n- [Markets](/trading/markets): All markets on Synthetix are perpetual futures quoted and settled in USDT on Ethereum Mainnet.\n- [Navigating the App](/trading/navigating-the-app): The Synthetix Exchange brings together trading, account management, rewards, and market information in a single application. Each page in the navigation provides a different view of your account or the broader market.\n- [Open Interest Limits](/trading/oi-limits): To help manage risk and maintain orderly markets, we apply Open Interest (OI) limits on a per-market basis.\n- [Order Types](/trading/order-types): Synthetix Exchange supports several order types that allow you to enter, exit and manage positions in different market conditions.\n- [Order Book](/trading/orderbook): Synthetix perpetual futures markets use a central limit order book (CLOB). If you have traded on a centralized exchange before, the structure will feel familiar.\n- [Trading Overview](/trading/overview): Synthetix offers perpetual futures contracts on a range of assets. Positions are margined in USDT and settled on-chain.\n- [P&L Calculations](/trading/pnl): On Synthetix, positions, margin, and settlement flows are tracked by the protocol. The UI typically surfaces convenience metrics like average entry price, unrealized PnL, and realized or closed PnL by deriving them from the position state and fills.\n- [Portfolio](/trading/portfolio): The **Portfolio** page is your trading dashboard, bringing together your balances, positions, orders, and account activity in one place.\n- [Pricing & Indices](/trading/pricing): We publish three price types:\n- [Scaled Orders](/trading/scaled-orders): Scaled Orders allow traders to place multiple limit orders across a selected price range.\n- [Stop Orders](/trading/stop-orders): Stop Orders allow traders to automate trade execution based on a selected price level.\n- [Tiers](/trading/tiers): Synthetix uses a volume-based tier system. Your tier determines your trading fee rates, how many open orders you can hold, and how many Sub-Accounts you can create.\n- [Trade & Order History](/trading/trade-and-order-history): The **Order History** and **Trade History** tabs in the **Portfolio Table** provide a record of your trading activity.\n- [TWAP Orders](/trading/twap-orders): TWAP (Time-Weighted Average Price) Orders allow traders to split a larger order into smaller orders executed gradually over a selected period of time.\n- [Referral Program](/rewards/referral-program): The Synthetix Referral Program allows traders to share referral codes and earn rewards when referred users trade on Synthetix.\n- [Snaxpot](/rewards/snaxpot): Snaxpot is a weekly rewards program powered by trading activity on Synthetix.\n- [420 Legacy Staking](/legacy-migration/420-legacy-staking): This page contains information about the retired 420 staking system, including its closure, SIP-423, legacy rewards, outstanding debt, and sUSD to SNX conversion guidance.\n- [What happened to my old position (LP, Perps, Rewards, Spot) on Arbitrum?](/legacy-migration/arbitrum-positions): If you previously held a position on **Arbitrum** through **Synthetix V3**, please note that **support for Arbitrum has been deprecated**.\n- [Asset Recovery by Network](/legacy-migration/asset-recovery-by-network): This page helps you identify **where your assets may be**, based on the network you used, and directs you to the appropriate next steps.\n- [What happened to my old position (LP, Perps, Rewards, Spot) on Base?](/legacy-migration/base-positions): If you previously held a position on **Base** through **Synthetix V3**, please note that **support for Base has been deprecated**.\n- [I have Curve LP Tokens, what can I do with them?](/legacy-migration/eth-curve-lp): The **Curve Liquidity Pool DAI/USDC/USDT/sUSD is now deprecated**.\n- [I have Synths on ETH Mainnet, what can I do with them?](/legacy-migration/eth-synths): If you are still holding **Synths** on **Ethereum** **(sETH, sBTC, sLINK etc.)**, please be aware that the legacy Synth system has now been **deprecated**.\n- [Legacy & Migration Help](/legacy-migration/legacy-migration-help): Synthetix has evolved across multiple networks and products over time. If you used Synthetix in the past, this section helps you understand **what happened to your assets** and **what to do next**.\n- [Legacy Tokens & Wallet Assets](/legacy-migration/legacy-tokens): Synthetix has used different tokens and assets across multiple products and networks over time. If you’ve found tokens or positions in your wallet and aren’t sure what they represent, use the links below to identify the asset and understand your options.\n- [Missing sUSD from the sUSD to SNX Conversion](/legacy-migration/missing-susd-from-susd-to-snx-conversion): Following the deprecation of sUSD under SIP-423, some users may have held sUSD within LP positions or other deposit contracts at the time of the snapshot.\n- [I got KWENTA Tokens, where can I swap them for SNX?](/legacy-migration/op-kwenta): Kwenta (KWENTA) is being unified into the Synthetix system. The migration process allows you to convert KWENTA into SNX under a vesting schedule.\n- [I have Synths on Optimism, what can I do with them?](/legacy-migration/op-synths): If you are still holding **Synths** on **Optimism (sETH, sBTC, sLINK etc.)**, please note that the legacy Synth system on Optimism **begins deprecation on January 31, 2026**.\n- [I got TLX Tokens, where can I swap them for SNX?](/legacy-migration/op-tlx): TLX is being unified into the **Synthetix** ecosystem. As part of this process, TLX can be migrated to **SNX** through an official migration flow that uses a **vesting schedule**.\n- [Repaying Post-Debt Jubilee Debt](/legacy-migration/repaying-post-debt-jubilee-debt): Following the closure of the 420 staking system and the end of Debt Jubilee under SIP-423, some users may still have outstanding debt associated with their legacy staking position.\n- [Depositing Collateral](/deposits-withdrawals/depositing): Synthetix Exchange runs on **Ethereum Mainnet**. Deposited collateral funds the selected subaccount only, and that collateral can be used to trade USDT-settled perps markets.\n- [Multicollateral Margin](/deposits-withdrawals/multi-collateral-margin): Use supported assets such as USDT and WETH to fund a single cross-margin perps account. This page is the conceptual overview. For step-by-step collateral operations, see [Depositing Collateral](/deposits-withdrawals/depositing) and [Withdrawing Collateral](/deposits-withdrawals/withdrawing).\n- [SLP Vault](/deposits-withdrawals/slp-vault): The Synthetix Liquidity Provider (SLP) Vault is the protocol's community market making vault, designed to back all perps markets on Ethereum Mainnet.\n- [Withdrawing Collateral](/deposits-withdrawals/withdrawing): You can withdraw collateral that is not required for open positions, USDT debt, or account-health limits. In multicollateral accounts, each asset is withdrawn separately.\n- [Account Managers](/account/account-managers): Account Managers allow a wallet to manage and trade using a Synthetix account owned by another wallet.\n- [Delegated Trading](/account/delegated-trading): Delegated Trading allows a wallet to grant another wallet permission to trade on a specific Sub-Account.\n- [Sub-Accounts](/account/subaccounts): A **Sub-Account** is a separate trading account linked to your wallet. You can create multiple Sub-Accounts within a single wallet to separate trading activity, positions, and risk.\n- [About Synthetix](/about-synthetix): Synthetix is the first decentralized perpetual futures protocol built on Ethereum Mainnet. The Synthetix Exchange provides offchain order matching through a high-performance Central Limit Order Book (CLOB) with onchain settlement on Ethereum, the world's most secure smart contract platform.\n- [Products](/about-synthetix/products): This page provides an overview of current and legacy products in the Synthetix ecosystem.\n- [SNX Token](/about-synthetix/snx-token): SNX is the native token of the Synthetix ecosystem.\n- [Synthetix History](/about-synthetix/synthetix-history): Synthetix began in 2018 as Havven, a protocol for decentralized stablecoins. In 2019, Synthetix v2 launched, pioneering the minting of synthetic assets, including crypto assets, indices, and traditional finance (TradFi) assets, on Ethereum. This innovation established Synthetix as a leader in on-chain derivatives and composable DeFi infrastructure.","tokens":2940,"crawled_at":1791192906468}
+{"id":10161,"url":"https://docs.near.org/chain-abstraction/chain-signatures/implementation","domain":"docs.near.org","chapter":"layer1_layer2","title":"Signing Transactions - NEAR Docs","text":"Chain signatures enable NEAR accounts, including smart contracts, to sign and execute transactions across many blockchain protocols.\nThis unlocks the next level of blockchain interoperability by giving ownership of diverse assets, cross-chain accounts, and data to a single NEAR account.\n\nSupported Networks\n\nWhile you can sign transactions for any network using Eddsa or Ecdsa keys, each chain signs transactions differently.Our example implementation shows you how to sign transactions for: Bitcoin, Solana, Cosmos, XRP, Aptos, Sui and EVM networks (Ethereum, Base, BNB Chain, Avalanche, Polygon, Arbitrum, and more).\n\n​\n\nCreate a Chain Signature\n\nThere are five steps to create a Chain Signature:\n\nDeriving the Foreign Address - Derive the address that will be controlled on the target blockchain.\n\nCreating a Transaction - Create the transaction or message to be signed.\n\nRequesting a Signature - Call the NEAR MPC contract requesting it to sign the transaction.\n\nFormatting the Signature - Format the signature from the MPC contract and add it to the transaction.\n\nRelaying the Signed Transaction - Send the signed transaction to the destination chain for execution.\n\nDiagram of a chain signature in NEAR\nThe chainsig.js library provides a convenient interface for completing each of these steps.\n\nFor building transactions inside of NEAR smart contracts written in Rust, you can use the Omni Transaction library to easily build transactions for different blockchains (like Bitcoin and Ethereum).\n\nMPC ContractsThere is an MPC contract available on both mainnet and testnet:\nMainnet: v1.signer\n\nTestnet: v1.signer-prod.testnet\n\nThe MPC network is made up of 8 nodes.\n\n​\n\nChain Signatures Contract\n\nTo interact with the chain signatures library you first need to instantiate a ChainSignaturesContract.\nLoading...\nSee code on GitHub\n\nThe networkId and contractId are set to the values specified in the previous section depending which network you are on.\n\n​\n\nChain Adapters\n\nTo interact with a specific chain, you need to instantiate the relevant chainAdapter.\nΞ EVM\n\n₿ Bitcoin\n\n◎ Solana\n\n◉ XRP\n\n◈ SUI\n\n⬟ Aptos\n\nLoading...\nSee code on GitHub\n\nThe EVM chain adapter takes the ChainSignaturesContract as an argument as well as publicClient which is constructed from an EVM RPC URL.\nTo use different EVM networks, simply specify the RPC URL for your desired network.\nThe example demonstrates compatibility with multiple EVM-compatible networks including Ethereum, Base, BNB Chain, Avalanche, Polygon, Arbitrum, zkSync, and many others.\nYou can find RPC URLs for various networks at ChainList.\n\nLoading...\nSee code on GitHub\n\nThe Bitcoin chain adapter takes the ChainSignaturesContract as an argument as well as the network (“mainnet”, “testnet” or “regtest”) and a btcRpcAdapter which handles communication with the Bitcoin network.\nLoading...\nSee code on GitHub\n\nThe Solana chain adapter takes the ChainSignaturesContract as an argument as well as a connection which is constructed from a Solana RPC URL. If you want to use Mainnet, then you need to choose a Mainnet RPC.\nLoading...\nSee code on GitHub\n\nThe XRP chain adapter takes the ChainSignaturesContract as an argument as well as an rpcUrl for the XRP Ledger and the rpcURl specification. For testnet, use https://s.altnet.rippletest.net:51234.\nLoading...\nSee code on GitHub\n\nThe SUI chain adapter takes the ChainSignaturesContract as an argument as well as a connection which is a SuiClient constructed from a SUI RPC URL.\nLoading...\nSee code on GitHub\n\nThe Aptos chain adapter takes the ChainSignaturesContract as an argument as well as a nodeUrl for the Aptos network and the network specification.\n\n​\n\n1. Deriving the Foreign Address\n\nChain Signatures use derivation paths to represent accounts on the target blockchain. The foreign address to be controlled can be deterministically derived from:\n\nThe NEAR account calling the MPC contract (e.g., example.near, example.testnet, etc.)\n\nA derivation path (a string such as ethereum-1, ethereum-2, etc.)\n\nThe MPC service’s master public key (we don’t need to worry about this as it is defined in the library we’re using).\n\nTo derive the address call the deriveAddressAndPublicKey method passing the near account Id from which the address is being derived and the derivation path.\nΞ EVM\n\n₿ Bitcoin\n\n◎ Solana\n\n◉ XRP\n\n◈ SUI\n\n⬟ Aptos\n\nLoading...\nSee code on GitHub\n\nLoading...\nSee code on GitHub\n\nLoading...\nSee code on GitHub\n\nOn Solana, your address is the same as your public key.\nLoading...\nSee code on GitHub\n\nLoading...\nSee code on GitHub\n\nLoading...\nSee code on GitHub\n\nThe same NEAR account and path will always produce the same address on the target blockchain.\nexample.near + ethereum-1 = 0x1b48b83a308ea4beb845db088180dc3389f8aa3b\n\nexample.near + ethereum-2 = 0x99c5d3025dc736541f2d97c3ef3c90de4d221315\n\n​\n\n2. Creating the Transaction\n\nTo construct the transaction to be signed use the method prepareTransactionForSigning.\n\nConstructing a transaction to transfer ETH is very simple. The value is the amount of ETH in Wei as type BigInt (1 ETH = 1018 Wei).Loading...\nSee code on GitHub\n\nThis method returns the unsigned transaction and the transaction hash(es) (also known as the payload).\n\nConstructing a transaction to transfer BTC is very simple. The value is the amount of BTC in satoshis as a string (1 BTC = 100,000,000 sats).Loading...\nSee code on GitHub\n\nThis method returns the unsigned transaction and the transaction hash(es) (also known as the payload).\n\nConstructing a transaction to transfer SOL is very simple. The value is the amount of SOL in lamports as type BigInt (1 SOL = 1,000,000,000 lamports).Loading...\nSee code on GitHub\n\nThis method returns the unsigned transaction.\n\nConstructing a transaction to transfer XRP is straightforward. The value is the amount of XRP in drops as a string (1 XRP = 1,000,000 drops).Loading...\nSee code on GitHub\n\nThis method returns the unsigned transaction and the transaction hash (also known as the payload).\n\nConstructing a transaction to transfer SUI is simple. The value is the amount of SUI in MIST as type BigInt (1 SUI = 1,000,000,000 MIST).Loading...\nSee code on GitHub\n\nThis method returns the unsigned transaction and the transaction hash (also known as the payload).\n\nConstructing a transaction to transfer APT is straightforward. The value is the amount of APT in octas as type BigInt (1 APT = 100,000,000 octas).Loading...\nSee code on GitHub\n\nThis method returns the unsigned transaction and the transaction hash (also known as the payload).\n\nEVM Function Calls\n\nTo call a function on a smart contract we need the ABI of the contract, in our repo this is defined in the config.js file (this can be gathered from Remix or using Etherscan).Then define a Contract object using the ethers libraryLoading...\nSee code on GitHub\n\nThen to construct the transactionLoading...\nSee code on GitHub\n\nThis approach allows you to call smart contract functions by encoding the function data and including it in the transaction.\n\n​\n\n3. Requesting the Signature\n\nOnce the transaction is created and ready to be signed, a signature request is made by calling sign on the MPC smart contract.\nThe method requires four parameters:\n\nThe payloads (or hashes) to be signed for the target blockchain\n\nThe derivation path for the account we want to use to sign the transaction\n\nThe keyType, Ecdsa for Secp256k1 signatures and Eddsa for Ed25519 signatures.\n\nThe signerAccount which contains the accountId that is signing and the signAndSendTransactions function from Near Connect.\n\nΞ EVM\n\n₿ Bitcoin\n\n◎ Solana\n\n◉ XRP\n\n◈ SUI\n\n⬟ Aptos\n\nLoading...\nSee code on GitHub\n\nLoading...\nSee code on GitHub\n\nFor Bitcoin, it is common to have multiple UTXOs to sign when sending a single transaction. We create a NEAR transaction (to call sign on the MPC contract) for each UTXO and send them to be signed by the MPC individually. Each signature is then parsed from each transaction outcome to produce an array of signatures.\nTo get the payload, serialize the transaction to a uint8Array and then convert it to hex.Loading...\nSee code on GitHub\n\nLoading...\nSee code on GitHub\n\nLoading...\nSee code on GitHub\n\nLoading...\nSee code on GitHub\n\n​\n\n4. Formatting the Signature\n\nOnce the signature is returned from the MPC it needs to be formatted and added to the transaction to produce a signed transaction.\nΞ EVM\n\n₿ Bitcoin\n\n◎ Solana\n\n◉ XRP\n\n◈ SUI\n\n⬟ Aptos\n\nLoading...\nSee code on GitHub\n\nLoading...\nSee code on GitHub\n\nFor Bitcoin, the array of signatures is added to the transaction to produce a complete signed transaction.\nLoading...\nSee code on GitHub\n\nLoading...\nSee code on GitHub\n\nLoading...\nSee code on GitHub\n\nLoading...\nSee code on GitHub\n\n​\n\n5. Relaying the Signed Transaction\n\nNow that we have a signed transaction, we can relay it to the target network using broadcastTx.\nΞ EVM\n\n₿ Bitcoin\n\n◎ Solana\n\n◉ XRP\n\n◈ SUI\n\n⬟ Aptos\n\nLoading...\nSee code on GitHub\n\nLoading...\nSee code on GitHub\n\nLoading...\nSee code on GitHub\n\nLoading...\nSee code on GitHub\n\nLoading...\nSee code on GitHub\n\nLoading...\nSee code on GitHub\n\nThe method returns a transaction hash which can be used to locate the transaction on an explorer.\n\n⭐️ For a deep dive into the concepts of Chain Signatures, see What are Chain Signatures?⭐️ For a complete example of a NEAR account using chain signatures in a frontend, see our web app example.\n\nWas this page helpful?","tokens":2344,"crawled_at":1791192909470}
+{"id":10162,"url":"https://docs.synthetix.io/getting-started","domain":"docs.synthetix.io","chapter":"defi_protocols","title":"Getting Started – Synthetix","text":"Last updated: Jul 20, 2026\n\nNew to Synthetix? Start here.\n\nThis guide walks you through creating your trading account, depositing collateral, and placing your first perpetual trade.\n\nGetting started only takes three simple steps:\n\nConnect your wallet.\n\nCreate your trading account.\n\nPlace your first trade.\n\nStep 1: Connect your wallet\n\nTo begin, open the Synthetix Exchange and click Connect Wallet on the top right corner. Then approve the connection request in your wallet.\n\nClick Connect Wallet in the top-right corner of the Exchange, then approve the connection request in your wallet.\nThis allows Synthetix to read your wallet address and interact with your funds when required.\n\nSynthetix is built on the Ethereum ecosystem and requires an EVM-compatible wallet. While many wallets are available, the following are the most commonly used.\n\nRabby\n\nMetaMask\n\nWalletConnect-compatible wallets\n\nDifferent Synthetix products operate on different blockchain networks. Synthetix is consolidating its products back onto Ethereum Mainnet, and any remaining deployments on Layer 2 networks are considered legacy or will be deprecated over time.\n\nAlways ensure your wallet is connected to the correct network before interacting with a Synthetix product.\n\nStep 2: Set up your account\n\nOnce your wallet is connected, you'll need to create a trading account by depositing collateral.\n\nClick Create Account.\n\nSelect the collateral asset you want to deposit (for example, USDC or ETH) and enter the amount.\n\n(Optional) Enter a referral code if you have one.\n\nClick Create Account to confirm your deposit.\n\nOpen Create Account, enter your deposit amount, optionally add a referral code, then click Create Account to confirm.\n\nApprove the required wallet transaction(s).\n\nAuthenticate your account.\n\nAfter approving the deposit transactions, click Authenticate to finish setting up your trading account.\n\nYour trading account is now ready for trading.\n\nStep 3: Placing your first trade\n\nOpen the Market Selector near the top-left corner.\n\nSelect a market from the list, for example BTC-USDT.\n\nThe selected market will load in the trading interface.\n\nNavigate to the Order Entry panel.\n\nSelect a market from the Market Selector, then use the Order Entry panel on the right to configure your trade.\n\nBy default, a Market order is selected.\n\nConfigure your order:\n\nSet your leverage.\n\nChoose Buy (Long) or Sell (Short).\n\nEnter the position size.\n\nClick Buy / Long or Sell / Short.\n\nSet your leverage, choose Buy or Sell, enter the position size, then click Buy / Long or Sell / Short to submit.\n\nReview the order details in the confirmation window.\n\nSubmit the order.\n\nOnce your order has been filled, you can:\n\nView your position on the chart.\n\nMonitor your position from the Positions tab in the portfolio table.\n\nSee also\n\nNavigating the App\n\nPortfolio\n\nManaging Positions\n\nDepositing Collateral\n\nOrder Types","tokens":725,"crawled_at":1791192923589}
+{"id":10163,"url":"https://docs.near.org/chain-abstraction/omnibridge/overview","domain":"docs.near.org","chapter":"layer1_layer2","title":"Omni Bridge Overview - NEAR Docs","text":"The Omni Bridge is a multi-chain asset bridge that facilitates secure and efficient asset transfers between different blockchain networks. It solves key challenges in cross-chain communication by leveraging Chain Signatures and its decentralized Multi-Party Computation (MPC) service to enable trustless cross-chain asset transfers.\n\nTo learn more see How Omni Bridge Works.\n\n​\n\nSupported Chains\n\nOmni Bridge launches with a hybrid architecture, utilizing different verification methods based on chain-specific requirements and technical constraints. This approach allows us to support multiple chains from day one while progressively transitioning to full Chain Signatures integration.\nCurrently the supported chains are:\n\nEthereum - (Light client + Chain Signatures)\n\nBitcoin - (Light client + Chain Signatures)\n\nZcash - (Light client + Chain Signatures)\n\nSolana - (Wormhole + Chain Signatures)\n\nBase - (Wormhole + Chain Signatures)\n\nBNB - (Wormhole + Chain Signatures)\n\nArbitrum - (Wormhole + Chain Signatures)\n\nPolygon - (Wormhole + Chain Signatures)\n\nSee Omni Bridge Roadmap for more details.\n\n​\n\nResources\n\nNear-One/omni-bridge - Omni Bridge repository\n\nNear-One/bridge-sdk-js - JavaScript SDK\n\nNear-One/bridge-sdk-rs - Rust SDK\n\nWas this page helpful?","tokens":315,"crawled_at":1791192927665}
+{"id":10164,"url":"https://www.metaplex.com/docs/smart-contracts/token-metadata/update","domain":"www.metaplex.com","chapter":"docs","title":"Updating Assets | Token Metadata","text":"Token Metadata is a legacy program. It remains supported, but is not recommended for new projects. Use Core instead.\n\nThe update authority of an asset can update its Metadata account using the Update instruction as long as the Is Mutable attribute is set to true. The Update instruction requires the Update Authority to sign the transaction and can update the following attributes of the Metadata account:\nUpdatable Fields\nNote that certain delegated authorities can also update the Metadata account of assets as discussed in the \"Delegated Authorities\" page.\nBelow is an explanation of all the individual fields available for update in the UpdateV1 instruction.\nThe Data Object\nThe object that defines the Name, Symbol, URI, Seller Fee Basis Points and the array of Creators of the asset. Note that the update authority can only add and/or remove unverified creators from the Creators array. The only exception is if the creator is the update authority, in which case the added or removed creators can be verified.\nData Object\n\nconst data = {\n\nname: 'New Name',\n\nsymbol: 'New Symbol',\n\nuri: 'https://newuri.com',\n\nsellerFeeBasisPoints: 500,\n\ncreators: [],\n\n}\n\nPrimary Sale Happened\nPrimary Sale Happened: A boolean that indicates whether the asset has been sold before.\nPrimary Sale Happened\n\nprimarySaleHappened: true\n\nIs Mutable\nA boolean that indicates whether the asset can be updated again. When changing this to false, any future updates will fail.\nIs Mutable\n\nisMutable: true\n\nCollection\nThis attribute enables us to set or clear the collection of the asset. Note that when setting a new collection, the verified boolean must be set to false and verified using another instruction.\nSetting A Collection\nSetting A Collection\n\ncollection: collectionToggle('Set', [\n\n{\n\nkey: publicKey('11111111111111111111111111111111'),\n\nverified: false,\n\n},\n\n])\n\nClearing a Collection\nClearing a Collection\n\ncollection: collectionToggle(\"Clear\"),\n\nNew Update Authority\nA new update authority can be assigned to an Asset by passing in the newUpdateAuthority field.\nNew Update Authority\n\nnewUpdateAuthority: publicKey('1111111111111111111111111111111')\n\nProgramable RuleSets\nThis attribute enables us to set or clear the rule set of the asset. This is only relevant for Programmable Non-Fungibles.\nProgramable RuleSets\n\nruleSet: publicKey('1111111111111111111111111111111')\n\nHere is how you can use our SDKs to update an asset on Token Metadata.\nUpdate As Update Authority\nNFT Asset\nThis example shows you how to update an NFT Asset as the update Authority of the Asset.\n\n1import { publicKey, none, some } from '@metaplex-foundation/umi';\n\n2import { updateV1 } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4// Assuming umi is set up with mplTokenMetadata plugin\n\n5// See getting-started for full setup\n\n6\n\n7const mintAddress = publicKey('mintAddress...');\n\n8\n\n9// Update the NFT metadata\n\n10await updateV1(umi, {\n\n11 mint: mintAddress,\n\n12 authority: umi.identity,\n\n13 // Only specify fields you want to update\n\n14 data: some({\n\n15 name: 'Updated NFT Name',\n\n16 symbol: '', // Keep existing\n\n17 uri: '', // Keep existing\n\n18 sellerFeeBasisPoints: 0, // Keep existing\n\n19 creators: none(),\n\n20 }),\n\n21}).sendAndConfirm(umi);\n\n22\n\n23console.log('NFT metadata updated');\n\n1import {\n\n2 getUpdateV1InstructionAsync,\n\n3 TokenStandard,\n\n4} from '@metaplex-foundation/mpl-token-metadata-kit';\n\n5\n\n6// Assuming rpc, rpcSubscriptions, sendAndConfirm, and authority are set up\n\n7// See getting-started for full setup\n\n8\n\n9const mintAddress = 'mintAddress...'; // The NFT mint address\n\n10\n\n11// Update the NFT metadata\n\n12const updateIx = await getUpdateV1InstructionAsync({\n\n13 mint: mintAddress,\n\n14 authority,\n\n15 payer: authority,\n\n16 // Specify fields to update (creators must be explicitly set, use null to keep existing)\n\n17 data: {\n\n18 name: 'Updated NFT Name',\n\n19 symbol: 'UNFT',\n\n20 uri: 'https://example.com/updated-nft.json',\n\n21 sellerFeeBasisPoints: 550,\n\n22 creators: null, // Keep existing creators\n\n23 },\n\n24});\n\n25\n\n26await sendAndConfirm({\n\n27 instructions: [updateIx],\n\n28 payer: authority,\n\n29});\n\n30\n\n31console.log('NFT metadata updated');\n\n1use anchor_lang::prelude::*;\n\n2use mpl_token_metadata::{\n\n3 accounts::Metadata,\n\n4 instructions::UpdateAsUpdateAuthorityV2CpiBuilder, types::Data,\n\n5};\n\n6\n\n7#[derive(Accounts)]\n\n8pub struct NftUpdateMpl<'info> {\n\n9 pub mint: AccountInfo<'info>,\n\n10 /// CHECK: Handled by CPI\n\n11 #[account(mut)]\n\n12 pub metadata: AccountInfo<'info>,\n\n13 #[account(mut)]\n\n14 pub update_authority: Signer<'info>,\n\n15 /// CHECK: Handled by CPI\n\n16 pub token_metadata_program: AccountInfo<'info>,\n\n17}\n\n18\n\n19pub fn update_nft_mpl_instruction<'info>(\n\n20 ctx: Context<'_, '_, '_, 'info, NftUpdateMpl<'info>>,\n\n21 new_name: Option<String>,\n\n22 new_uri: Option<String>,\n\n23) -> Result<()> {\n\n24 let mint = ctx.accounts.mint.to_account_info();\n\n25 let metadata = ctx.accounts.metadata.to_account_info();\n\n26 let token_metadata_program = ctx.accounts.token_metadata_program.to_account_info();\n\n27\n\n28 // Get the original metadata values\n\n29 let metadata_account = Metadata::try_from(&metadata)?;\n\n30\n\n31 let original_metadata = Data {\n\n32 name: metadata_account.name,\n\n33 symbol: metadata_account.symbol,\n\n34 uri: metadata_account.uri,\n\n35 seller_fee_basis_points: metadata_account.seller_fee_basis_points,\n\n36 creators: metadata_account.creators,\n\n37 };\n\n38\n\n39 let new_metadata = Data {\n\n40 name: new_name.unwrap_or(original_metadata.name),\n\n41 uri: new_uri.unwrap_or(original_metadata.uri),\n\n42 ..original_metadata // Keep the rest of the metadata the same\n\n43 };\n\n44\n\n45 UpdateAsUpdateAuthorityV2CpiBuilder::new(&token_metadata_program)\n\n46 .mint(&mint)\n\n47 .metadata(&metadata)\n\n48 .authority(&ctx.accounts.update_authority)\n\n49 .data(new_metadata)\n\n50 // Add remaining data fields/accounts to be adjusted to the CPI if needed\n\n51 // https://docs.rs/mpl-token-metadata/latest/mpl_token_metadata/instructions/struct.UpdateAsUpdateAuthorityV2CpiBuilder.html\n\n52 .invoke()?;\n\n53\n\n54 Ok(())\n\n55}\n\npNFT Asset\nThis example shows you how to update a Programable NFT (pNFT) Asset as the update Authority of the Asset.\npNFTs may require additional accounts to be passed in for the instruction to work. These include: tokenAccount, tokenRecord, authorizationRules, and authorizationRulesProgram.\n\n1import { publicKey, none, some } from '@metaplex-foundation/umi';\n\n2import { updateV1 } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4// Assuming umi is set up with mplTokenMetadata plugin\n\n5\n\n6const mintAddress = publicKey('mintAddress...');\n\n7\n\n8// Update the Programmable NFT metadata\n\n9// Note: pNFTs may have rule sets that restrict updates\n\n10await updateV1(umi, {\n\n11 mint: mintAddress,\n\n12 authority: umi.identity,\n\n13 data: some({\n\n14 name: 'Updated pNFT Name',\n\n15 symbol: '',\n\n16 uri: '',\n\n17 sellerFeeBasisPoints: 0,\n\n18 creators: none(),\n\n19 }),\n\n20}).sendAndConfirm(umi);\n\n21\n\n22console.log('pNFT metadata updated');\n\n1import {\n\n2 getUpdateV1InstructionAsync,\n\n3 TokenStandard,\n\n4} from '@metaplex-foundation/mpl-token-metadata-kit';\n\n5\n\n6// Assuming rpc, rpcSubscriptions, sendAndConfirm, and authority are set up\n\n7\n\n8const mintAddress = 'mintAddress...'; // The pNFT mint address\n\n9\n\n10// Update the Programmable NFT metadata\n\n11// Note: pNFTs may have rule sets that restrict updates\n\n12const updateIx = await getUpdateV1InstructionAsync({\n\n13 mint: mintAddress,\n\n14 authority,\n\n15 payer: authority,\n\n16 // Specify fields to update (creators must be explicitly set, use null to keep existing)\n\n17 data: {\n\n18 name: 'Updated pNFT Name',\n\n19 symbol: 'UPNFT',\n\n20 uri: 'https://example.com/updated-pnft.json',\n\n21 sellerFeeBasisPoints: 550,\n\n22 creators: null, // Keep existing creators\n\n23 },\n\n24});\n\n25\n\n26await sendAndConfirm({\n\n27 instructions: [updateIx],\n\n28 payer: authority,\n\n29});\n\n30\n\n31console.log('pNFT metadata updated');\n\n1use anchor_lang::prelude::*;\n\n2use mpl_token_metadata::{\n\n3 accounts::Metadata,\n\n4 instructions::UpdateAsUpdateAuthorityV2CpiBuilder, types::Data,\n\n5};\n\n6\n\n7#[derive(Accounts)]\n\n8pub struct NftUpdateMpl<'info> {\n\n9 pub mint: AccountInfo<'info>,\n\n10 /// CHECK: Handled by CPI\n\n11 #[account(mut)]\n\n12 pub metadata: AccountInfo<'info>,\n\n13 #[account(mut)]\n\n14 pub update_authority: Signer<'info>,\n\n15 /// CHECK: Handled by CPI\n\n16 pub token_metadata_program: AccountInfo<'info>,\n\n17 // Add additional accounts below if needed\n\n18}\n\n19\n\n20pub fn update_nft_mpl_instruction<'info>(\n\n21 ctx: Context<'_, '_, '_, 'info, NftUpdateMpl<'info>>,\n\n22 new_name: Option<String>,\n\n23 new_uri: Option<String>,\n\n24) -> Result<()> {\n\n25 let mint = ctx.accounts.mint.to_account_info();\n\n26 let metadata = ctx.accounts.metadata.to_account_info();\n\n27 let token_metadata_program = ctx.accounts.token_metadata_program.to_account_info();\n\n28\n\n29 // Get the original metadata values\n\n30 let metadata_account = Metadata::try_from(&metadata)?;\n\n31\n\n32 let original_metadata = Data {\n\n33 name: metadata_account.name,\n\n34 symbol: metadata_account.symbol,\n\n35 uri: metadata_account.uri,\n\n36 seller_fee_basis_points: metadata_account.seller_fee_basis_points,\n\n37 creators: metadata_account.creators,\n\n38 };\n\n39\n\n40 let new_metadata = Data {\n\n41 name: new_name.unwrap_or(original_metadata.name),\n\n42 uri: new_uri.unwrap_or(original_metadata.uri),\n\n43 ..original_metadata // Keep the rest of the metadata the same\n\n44 };\n\n45\n\n46 UpdateAsUpdateAuthorityV2CpiBuilder::new(&token_metadata_program)\n\n47 .mint(&mint)\n\n48 .metadata(&metadata)\n\n49 .authority(&ctx.accounts.update_authority)\n\n50 .data(new_metadata)\n\n51\n\n52 // Add remaining data fields to be adjusted to the CPI if needed\n\n53 // https://docs.rs/mpl-token-metadata/latest/mpl_token_metadata/instructions/struct.UpdateAsUpdateAuthorityV2CpiBuilder.html\n\n54 //\n\n55 // .authorization_rules(authorization_rules)\n\n56 // .authorization_rules_program(authorization_rules_program)\n\n57 // .token_record(token_record)\n\n58 .invoke()?;\n\n59\n\n60 Ok(())\n\n61}","tokens":2487,"crawled_at":1791192951615}
+{"id":10165,"url":"https://stack.olas.network/open-autonomy/get_started/use_cases","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Use cases - Olas Stack Developer Documentation","text":"Use cases\n\nAs we have discussed in earlier sections, AI agents can execute arbitrary operations in a decentralized way.\nThere is a great deal of applications where the properties of AI agents make them better suited than existing solutions,\nespecially in the context of DAOs and where complex operations are required to be executed in a decentralized and transparent way. AI agents remove the need of strong trust assumptions that traditional centralized off-chain services require.\n\nBelow you will find some ideas of what you can do with AI agents:\n\nInternal DAO operations\n\nMeta Yield Hunter:\nUse machine learning to track yield opportunities across chains and protocols. Autonomously move positions to optimize yield.\n\nAsset Whitelisting:\nDynamically evaluates assets based on diverse datasets to add and remove from whitelists.\n\nContribution Coordinator:\nWatch for contributions on GitHub, Twitter etc and adjust on-chain rewards & permissions accordingly.\n\nNew services\n\nWeb3-native Recommender:\nBuild the first co-owned and operated engines to track opportunities and make personalized recommendations to crypto users.\n\nNFT Collector:\nAllow users to passively build exposure to quality baskets of NFTs.\n\nFund Manager:\nOvercome the legal and trust challenges of running a decentralized fund.\n\nCustomizable app infrastructure\n\nOracles (On-chain Data Reporter):\nBuild future-proof oracles that are totally customizable, without permission, and owned by you.\n\nKeepers:\nBuild robust keeper systems that you can extend to maintain any on-chain data, based on a rich set of criteria which you define.\n\nBridges (Cross-chain Messenger):\nSpin up your own bridges to sync any type of data across chains and infrastructure. Combine with your oracles and keepers to build rich new services.","tokens":446,"crawled_at":1791192938952}
+{"id":10166,"url":"https://docs.synthetix.io/trading/fees","domain":"docs.synthetix.io","chapter":"defi_protocols","title":"Fees – Synthetix","text":"Last updated: Jun 16, 2026\n\nTrading on Synthetix Mainnet involves fees that are applied when opening and closing positions. Collateral operations such as withdrawals, voluntary Swap, and forced auto-exchange can also have fees.\n\nMaker vs. Taker\n\nEvery time an order is filled, a trading fee is charged. You are either a maker or a taker:\n\nRoleHow it worksDefault fee rate\nTaker\nYour order executes immediately against existing liquidity (market orders, or limit orders that cross the spread)\n0.05%\n\nMaker\nYour order rests on the order book and is matched by someone else\n0.02%\n\nVolume-based Fee Tiers\n\nFees decrease as your 14-day rolling trading volume increases. Your tier also affects open order limits and the number of subaccounts you can create, see Tiers for the full breakdown.\n\nTier14-day VolumeMakerTaker\nRegular User\n$0+\n0.020%\n0.050%\n\nTier 1\n>= $100,000\n0.020%\n0.050%\n\nTier 2\n>= $5,000,000\n0.016%\n0.040%\n\nTier 3\n>= $25,000,000\n0.014%\n0.035%\n\nTier 4\n>= $100,000,000\n0.012%\n0.032%\n\nTier 5\n>= $500,000,000\n0.008%\n0.025%\n\nTier 6\n>= $2,000,000,000\n0.003%\n0.020%\n\nTier 7\n>= $5,000,000,000\n0.000%\n0.017%\n\nVolume is measured in notional USDT traded across all markets in a rolling 14-day window. Your tier is applied to all subsequent trades.\n\nFee calculations\n\nFees are charged on the notional value of each fill, not on the margin you deposit.\n\nTrading Fee = Quantity x Executed Price x Fee Rate\n\nTaker order example:\n\nTrade 0.5 BTC at 100,000 USDT gives 50,000 USDT notional.\n\nAt 0.05% taker rate, fee = 50,000 x 0.0005 = 25 USDT.\n\nMaker order example:\n\nSame trade, resting limit order.\n\nAt 0.02% maker rate, fee = 50,000 x 0.0002 = 10 USDT.\n\nFees are charged per fill. Partial fills are charged on the filled portion only.\n\nWhen trading fees are charged\n\nOpening a position\n\nClosing a position\n\nIncreasing or reducing a position through a filled order\n\nTrading fees settle to your subaccount's USDT balance. If you primarily hold non-USDT collateral, fees can make the USDT balance negative.\n\nCollateral operation fees\n\nActionFee behavior\nWithdraw\nPer-asset withdrawal fee, deducted from the amount received and shown before confirmation.\n\nSwap (voluntary)\nExchange fee based on the source asset's lowest-tier haircut, shown in the swap quote before confirmation.\n\nAuto-exchange (forced)\nHigher exchange fee than voluntary Swap, approximately 2x the voluntary rate, applied automatically with no confirmation step.\n\nDeposits and withdrawals\nEthereum Mainnet gas paid in ETH by your wallet.\n\nInternal Swap\nNo wallet gas transaction; the fee is applied in the swap quote.\n\nLiquidation Clearance Fee\n\nWhen a position is liquidated, an additional liquidation clearance fee is charged on the notional value of the liquidated position. This fee varies by market:\n\nMarketLiquidation Clearance Fee\nBTC-USDT\n0.5%\n\nETH-USDT\n0.5%\n\nSOL-USDT\n1.0%\n\nXRP-USDT, DOGE-USDT\n1.0%\n\nZEC-USDT, 1000PEPE-USDT\n1.5%\n\nFARTCOIN-USDT, PUMP-USDT\n2.0%\n\nXMR-USDT\n2.0%\n\nThe liquidation clearance fee is deducted from remaining collateral after the position is closed. Any collateral remaining after the fee is returned to the account.\n\nPerpetuals have no settlement fee\n\nUSDT perpetuals do not expire, so there is no scheduled settlement cost unlike dated futures contracts.\n\nSee also\n\nP&L Calculations - worked examples showing fee impact on net return.\n\nMulticollateral Margin - USDT debt, Swap, and auto-exchange.\n\nWithdrawing Collateral - withdrawal fees and constraints.\n\nMarkets - liquidation clearance fees per market.","tokens":875,"crawled_at":1791192941052}
+{"id":10167,"url":"https://docs.near.org/chain-abstraction/omnibridge/implementation","domain":"docs.near.org","chapter":"layer1_layer2","title":"Implementation Details - NEAR Docs","text":"The Omni Bridge is a sophisticated cross-chain bridge infrastructure that enables secure and efficient token transfers between NEAR Protocol and various other blockchain networks. This document provides a detailed technical overview of the bridge’s architecture, covering its core components, security model, and operational mechanisms. By leveraging a combination of Multi-Party Computation (MPC), chain-specific light clients, and a permissionless relayer network, the bridge achieves a robust balance of security, decentralization, and user experience.\nFor reference code implementations, see:\n\nBridge SDK JS Omni Bridge implementation in JavaScript\n\nBridge SDK Rust Omni Bridge implementation in Rust\n\n​\n\nThe Bridge Token Factory Pattern\n\nAt the core of Omni Bridge is the Bridge Token Factory contract on NEAR that serves as both a token factory and custodian. This unified contract handles both native tokens from the source chain and bridged tokens created by the factory itself. This design simplifies maintenance and reduces complexity compared to having separate contracts.\nThe contract has several key responsibilities:\n​\n\nFor bridged tokens (tokens originally from other chains):\n\nDeploys new token contracts when bridging tokens for the first time\n\nMints tokens when receiving valid transfer messages\n\nBurns tokens when initiating transfers back to the origin chain\n\n​\n\nFor native NEAR tokens:\n\nActs as a custodian by locking tokens during transfers\n\nReleases tokens when receiving valid transfer messages\n\nManages token operations through the NEP-141 standard\n\n​\n\nTransfer Lifecycle\n\nA transfer’s lifecycle includes several states, shown below for a NEAR to Ethereum transfer of native NEAR tokens:\n\n​\n\nMessage Signing and Verification\n\nFor most chains, the bridge uses a payload-based message signing system (with Bitcoin being a notable exception requiring full transaction signing).\n​\n\nMessage Types\n\nThe bridge supports several types of signed messages:\n\nTransfer Messages\n\nInitiation messages\n\nFinalization messages\n\nToken Messages\n\nDeployment messages\n\nMetadata update messages\n\n​\n\nPayload Structure\n\nMessages are encoded using Borsh serialization and contain:\nComponentDescription\nMessage Type\nIdentifier for the message category\n\nChain Info\nChain IDs and relevant addresses\n\nOperation Data\nAmounts, recipients, fees, etc.\n\n​\n\nSignature Process\n\nNEAR contract creates and stores the message payload\n\nMPC network observers detect valid payloads\n\nNodes jointly sign the payload\n\nSignature is verified on destination chains\n\nKey Benefits\nClearer message intent through structured payloads\n\nMore efficient signature verification on destination chains\n\nStandardized message format across chains\n\n​\n\nTransaction Flow: NEAR to Other Chains\n\nHere’s an overview of how transfers are processed from NEAR to different destination chains:\n\n​\n\nTransfer Process\n\nLet’s follow what happens when a user wants to transfer tokens from NEAR to another chain:\n​\n\n1. Initiation\n\nThe user starts by calling the token contract with:\n\nAmount to transfer\n\nDestination chain and address\n\nFee preferences (whether to pay fees in the token being transferred or in NEAR)\n\nFees are minted on NEAR side for relayers\n\n​\n\n2. Token Lock\n\nThe token contract transfers tokens to the locker contract, which:\n\nValidates the transfer message\n\nAssigns a unique nonce\n\nRecords the pending transfer\n\nEmits a transfer event\n\n​\n\n3. MPC Signing\n\nThe bridge contract:\n\nRequests signature generation\n\nMPC nodes jointly generate and aggregate signature\n\nMaintains threshold security throughout process\n\n​\n\n4. Destination Chain\n\nThe Bridge Token Factory on the destination chain:\n\nVerifies the MPC signature\n\nMints equivalent tokens\n\n​\n\nTransaction Flow: Other Chains to NEAR\n\nThe reverse flow varies based on the source chain:\n​\n\n1. Ethereum\n\nUses NEAR light client for maximum security:\n\nBurning tokens on source chain\n\nSubmitting proof to NEAR\n\nVerifying proof through light client\n\nReleasing tokens to recipient\n\n​\n\n2. Supported Non-EVM Chains (e.g., Solana)\n\nUtilize established message passing protocols (such as Wormhole) for:\n\nMessage passing between chains\n\nTransaction verification\n\nIntegration with NEAR token factory system\n\n​\n\n3. Other EVM Chains\n\nUtilize a combination of light clients (where efficient) and message passing protocols to ensure secure verification of inbound transfers.\n\n​\n\nTransaction Flow: Chain to Chain (via NEAR)\n\nFor transfers between two non-NEAR chains (e.g., Ethereum to Solana), the bridge combines both flows using NEAR as an intermediary routing layer. Rather than minting or unlocking tokens on NEAR, the bridge creates a forwarding message that directs tokens to be minted or unlocked on the final destination chain.\nFrom the user’s perspective, this appears as a single operation - they initiate the transfer on the source chain, and the off-chain relayer infrastructure handles the intermediate NEAR routing automatically.\n\n​\n\nSecurity Model\n\n​\n\nTrust Assumptions\n\nOmni Bridge requires different trust assumptions depending on the chain connection:\n​\n\nFor Chain Signatures:\n\nNEAR Protocol security (2/3+ honest validators)\n\nMPC network security (2/3+ honest nodes)\n\nNo single entity controls enough MPC nodes to forge signatures\n\nCorrect implementation of the signing protocol\n\n​\n\nFor Ethereum/Bitcoin connections:\n\nLight client security\n\nFinality assumptions (e.g., sufficient block confirmations)\n\nChain-specific consensus assumptions\n\n​\n\nFor Message Passing connections:\n\nSecurity of the underlying message passing protocol (e.g., Wormhole Guardian network)\n\nVerified by NEAR network participants (e.g., validators and full nodes)\n\n​\n\nRelayer Network\n\nRelayers are permissionless infrastructure operators who monitor for bridge events and execute cross-chain transactions. Unlike many bridge designs, our relayers cannot:\n\nForge transfers\n\nSteal funds\n\nCensor transactions (users can self-relay)\n\nFront-run transactions for profit\n\nDo not create additional security assumptions\n\nThe relayer’s role is purely operational - executing valid transfers and collecting predetermined fees. Multiple relayers can operate simultaneously, creating competition for faster execution and lower fees.\n\n​\n\nFast Transfers\n\nStandard cross-chain transfers can take time due to finality and verification requirements. Fast Transfers allow relayers to expedite this process by fronting liquidity.\n​\n\nHow it Works\n\nUser Initiation: A user sends a FastFinTransferMsg specifying the destination and fee.\n\nRelayer Execution: A relayer detects the request and instantly transfers the equivalent amount (minus fees) to the user on the destination chain from their own funds.\n\nSettlement: The bridge later reimburses the relayer once the original transfer is fully verified and finalized.\n\nFast transfers are ideal for users who prioritize speed over cost, as relayers may charge a premium for the liquidity and convenience.\n\n​\n\nMulti-Token Support (ERC1155)\n\nOmni Bridge supports the ERC1155 standard, enabling the transfer of multiple token types within a single contract.\n​\n\nAddress Derivation\n\nTo maintain consistency across chains, bridged ERC1155 tokens use a deterministic address derivation scheme:\n\nDeterministic Address: keccak256(tokenAddress + tokenId)\n\nThis ensures that each tokenId within an ERC1155 contract maps to a unique, consistent address on the destination chain.\n\n​\n\nKey Functions\n\ninitTransfer1155: Initiates a transfer for a specific ERC1155 token ID.\n\nlogMetadata1155: Registers metadata for a specific token ID, ensuring it is recognized by indexers and wallets.\n\n​\n\nFee Structure\n\nBridge fees are unified and processed on NEAR, with components including:\n​\n\nExecution Fees\n\nDestination chain gas costs\n\nSource chain storage costs\n\nRelayer operational costs\n\nMPC signing costs\n\n​\n\nFee Payment Options\n\nNative tokens of source chain\n\nThe token being transferred\n\nFees dynamically adjust based on gas prices across different chains to ensure reliable execution.\n\n​\n\nDesign Goals\n\nThe fee structure is designed to:\n\nEnsure relayer economic viability\n\nPrevent economic attacks\n\nAllow fee market competition\n\nCover worst-case execution costs\n\nUsers can bypass relayers entirely by executing their own transfers, paying only the necessary gas fees on each chain. This creates a natural ceiling on relayer fees.\n\nWas this page helpful?","tokens":2088,"crawled_at":1791192946176}
+{"id":10168,"url":"https://stack.olas.network/open-autonomy/get_started/agent_services_compared_to","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Agent services compared - Olas Stack Developer Documentation","text":"Agent services compared\n\nOne of the best ways to understand how autonomous AI agents fit into\nthe wider ecosystem of crypto services and applications is to compare them with existing solutions.\n\nRecall that an autonomous AI agents is a decentralized service that runs off-chain and provides functionalities to objects living on-chain. Autonomous AI agents are outside the purview and control of a single authority, and can be designed for a variety of purposes, including acting as a decentralized oracle for smart contracts, or executing complex investing strategies that cannot be easily encoded on-chain. An AI agents is a particular type of autonomous AI agent which is implemented as a multi-agent system.\n\nAI agents vs. other software solutions\n\nThe table below highlights the main differences between AI agents and other software solutions.\n\nSmart contracts\nWeb services\nCustom decentralized services (e.g., Oracles)\nAutonomous AI agents\n\nLocation\n\nOn-chain\n\nOff-chain\n\nOff-chain\n\nOff-chain\n\nDecentralized\n\nRobust\n\nTransparent\n\nComplex processing\n\nCross-chain\n\nContinuous/always-on\n\nFlexible\n\nComposable\n\nDAO-owned\n\nFull-stack\n\nSmart contracts are computer programs that live on-chain. They are crypto-native, can be audited and can use any functionality already available in the blockchain. Their security relies\non the security of the underlying blockchain. However, due to their nature, they have a number of limitations, including the inability of doing complex operations, talking to other APIs or interact with other blockchains.\n\nWeb services are a popular off-chain solution to complement the limitations of smart contracts. They are very flexible, but they usually lack the crypto-native features of smart contracts.\n\nCustom decentralized services are services like oracles, bridges or keepers which are run off-chain by a group of operators, thus providing the required level of trust and security. These services run off-chain, which enables them to do complex processing. The main drawback of this approach is that there is no standardized approach to build and compose such services. This severely limits the growth of the ecosystem of applications in the off-chain space.\n\nThis is where AI agents (implemented with the Open Autonomy framework) comes into play in the broader ecosystem of crypto software. AI agents are composable, crypto-native services that can execute complex processing, take action on their own and run continuously.\n\nFor a more detailed discussion, take a look at the Autonolas Education article series.\n\nAI agents vs. single-agent-instance applications\n\nHaving understood how AI agents fit into the wider crypto ecosystem, sometimes there is the question whether is it best to design a certain application as single-agent-instance or as an AI agents.\nThis is often a question that new developers in the field of agent systems and multi-agent systems face. We provide below a comparison table which hopefully will give you some guidance on which of the both approaches is best for your use case.\n\nSingle-agent-instance applications\nAutonomous AI agents\n\nScope\n\nAn application designed to pursue the interests and objectives of a single entity.\n\nAn application designed to offer services that external users can benefit from.\n\nValue generation model\n\nThe application is in charge of generating economic value for its owner.\n\nAI agent operators might charge a fee to their users.\n\nArchitecture & Execution\n\nA single agent instance, typically run and controlled by a single entity.\n\nA set of agent instances run by a collection of independent operators. Agent instances have a synchronized shared state.\n\nTrust model\n\nNot applicable. The owner controls and designs and manages their own agent instance.\n\nAI agents are decentralized and transparent, and can be crypto-economically secured on a public blockchain. They can be regarded as drop-in replacements of trusted entities (on complex service infrastructures), thus relaxing the trust requirements on them.\n\nExample\n\nAutomated, personal asset management: an agent instance determines the best strategy to invest owners assets.\n\nAutomated asset management as a service. Users subscribe to AI agents, which execute elaborate investing strategies to maximize the capital gains, in exchange for a service fee.\n\nFrameworks\n\nOpen AEA\n\nOpen Autonomy + Open AEA\n\nProgressive decentralization\n\nOf course, many use cases that apply for single-agent-instance application can later be considered to be offered as an AI agent. For this reason, it is often advisable to implement a single-agent-instance application as an AI agent with a single instance operator. This approach has the benefit that whenever the developer wants to make the promotion of that application to an AI agent, they will be able to do so almost effortlessly, except for some modifications to account for potentially extra configuration requirements.","tokens":1226,"crawled_at":1791192958132}
+{"id":10169,"url":"https://docs.near.org/chain-abstraction/omnibridge/roadmap","domain":"docs.near.org","chapter":"layer1_layer2","title":"Omni Bridge Roadmap - NEAR Docs","text":"Omni Bridge launches with a hybrid architecture, utilizing different verification methods based on chain-specific requirements and technical constraints. This approach allows us to support multiple chains from day one while progressively transitioning to full Chain Signatures integration.\n​\n\nSupported Chains\n\nThe bridge currently supports the following networks:\n\nEVM Chains:\n\nEthereum\n\nBase\n\nArbitrum\n\nBNB Chain\n\nPolygon (PoS)\n\nNon-EVM Chains:\n\nBitcoin\n\nSolana\n\nZcash\n\n​\n\nArchitecture Overview\n\nOmni Bridge utilizes Chain Signatures as its primary verification mechanism for outbound transfers from NEAR. Incoming transfers rely on chain-specific verification methods, including light clients for maximum security where available.\n​\n\nVerification Methods\n\nEthereum & Bitcoin: Light Client verification for inbound transfers.\n\nOther Chains: Message passing protocols verified by the NEAR network.\n\nOutbound (All Chains): Chain Signatures (MPC) for secure transaction signing.\n\n​\n\nFuture Development\n\nProtocol Improvements\n\nEnhanced fee mechanisms\n\nCross-chain contract calls\n\nNew token standards support\n\nBeyond basic asset transfers, we’re expanding the bridge’s capabilities. Enhanced fee mechanisms will better handle gas price volatility, while cross-chain contract calls will enable more complex interactions.\n\nInfrastructure\n\nExpanded relayer network\n\nImproved monitoring tools\n\nEnhanced developer tooling\n\nInfrastructure development focuses on reliability and usability. An expanded relayer network improves transfer speeds and reliability, while better monitoring and developer tools make integration and maintenance easier.\n​\n\nGet Involved\n\n​\n\nAreas for Contribution\n\nChain integrations\n\nPerformance optimization\n\nSecurity analysis\n\nDeveloper tools\n\nNear-One/omni-bridge - Omni Bridge repository\n\nNear-One/bridge-sdk-js - JavaScript SDK\n\nNear-One/bridge-sdk-rs - Rust SDK and Bridge CLI\n\nThe code is open source and we welcome contributions from the community. Whether you’re interested in adding support for new chains, optimizing performance, or building developer tools, there’s room for meaningful contribution.\nBridge infrastructure is a fundamental component of a multi-chain future. Through Chain Signatures, we’re creating a more efficient, secure, and scalable approach to cross-chain communication. Join us in building it.\nWas this page helpful?","tokens":592,"crawled_at":1791192964722}
+{"id":10170,"url":"https://docs.synthetix.io/trading/leverage-margin","domain":"docs.synthetix.io","chapter":"defi_protocols","title":"Leverage & Margin – Synthetix","text":"Last updated: Jun 16, 2026\n\nLeverage lets you control how much margin you put up for a given position size.\n\nPosition size (notional) is what drives your profit and loss in USDT.\n\nLeverage mainly changes how much margin is required, which changes your ROI and liquidation risk.\n\nIn multicollateral accounts, non-USDT collateral contributes margin after valuation and haircuts.\n\nCross-margin\n\nAll positions in a subaccount share a single collateral pool. This is cross-margin.\n\nA profitable position can offset the margin requirements of a losing one, and your full subaccount value backs all open positions simultaneously.\n\nCollateral is isolated by subaccount. Assets in one subaccount do not support positions in another.\n\nQuick definitions\n\nNotional (position value) = position size x entry price\n\nInitial margin (margin used) = notional / leverage\n\nUnrealized PnL (uPnL) depends on price movement and position size, not on leverage\n\nTotal Equity = token quantity x index price\n\nCollateral Value = haircut-adjusted value that counts toward margin\n\nAdjusted Account Value (AAV) = account value after collateral haircuts and PnL effects\n\nAdjusted Account Value and haircuts\n\nYour margin is based on Adjusted Account Value (AAV), not raw token balances.\n\nUSDT\n\nUSDT counts at full face value. It is also the settlement asset for trading fees, funding, and realized PnL.\n\nNon-USDT collateral\n\nNon-USDT collateral is valued using:\n\nIndex price - live market price for the asset.\n\nHaircut - a risk discount applied to the asset's USD value.\n\nThe Collateral Value shown in the balances table is the haircut-adjusted amount that counts toward margin. Hover the value in the app to see the breakdown: asset value, haircut rate, and final collateral value.\n\nTotal Equity vs Collateral Value\n\nTotal Equity is the raw USD value of an asset: quantity x index price.\n\nCollateral Value is the amount that actually counts toward margin after the haircut is applied. Only Collateral Value affects trading limits, withdrawal availability, debt limits, and liquidation risk.\n\nTiered haircuts\n\nHaircuts can depend on the USD value of each asset in your account. Synthetix uses tiered rates, but current per-account deposit limits mean most users sit in the first tier. Check Collateral Value in your balances table for your actual margin contribution.\n\nWhen collateral prices move\n\nNon-USDT collateral is marked to index price. If WETH falls, your Collateral Value and Adjusted Account Value drop even if your position PnL is unchanged. That reduces Available Margin, can raise LTV, and increases liquidation or auto-exchange risk.\n\nExample: You hold 5 WETH at 3,000 USDT with a 10% haircut. Collateral Value is about 13,500 USDT. If WETH drops 20% to 2,400 USDT, Collateral Value falls to about 10,800 USDT. That is a 2,700 USDT margin reduction with no trade activity.\n\nMargin ratios\n\nThe system uses two core margin thresholds:\n\nTermFormulaDescription\nInitial Margin Rate (IMR)\n1 / max_leverage\nMinimum collateral to open or increase a position\n\nMaintenance Margin Rate (MMR)\n1 / (2 x max_leverage)\nMinimum collateral to keep a position open\n\nAt 50x leverage, IMR is 2% and MMR is 1%.\n\nHow leverage affects uPnL\n\nLeverage does not change uPnL for the same position size and the same price move.\n\nIf you buy 1 BTC and price goes up by 100 USDT, your uPnL is +100 USDT whether you used 2x or 20x.\n\nThe difference is how much margin you used to hold that position.\n\nHow leverage affects ROI\n\nROI is uPnL measured relative to the margin you used.\n\nROI = uPnL / initial margin\n\nHigher leverage uses less margin, so the same uPnL becomes a larger ROI. Lower leverage uses more margin, so the same uPnL becomes a smaller ROI.\n\nExamples\n\nThese examples ignore fees and funding to keep the math simple.\n\nExample 1 - Same uPnL, different ROI (long)\n\nYou open a long worth 3,000 USDT notional.\n\n10x leverage\n\nInitial margin = 3,000 / 10 = 300 USDT\n\n5x leverage\n\nInitial margin = 3,000 / 5 = 600 USDT\n\nIf price moves in your favor and uPnL is +30 USDT:\n\nROI at 10x = 30 / 300 = 10%\n\nROI at 5x = 30 / 600 = 5%\n\nSame uPnL, different ROI because the margin used is different.\n\nExample 2 - Losses work the same way\n\nSame position: 3,000 USDT notional.\n\nIf uPnL becomes -30 USDT:\n\nROI at 10x = -30 / 300 = -10%\n\nROI at 5x = -30 / 600 = -5%\n\nExample 3 - Short position behaves the same\n\nYou open a short worth 2,000 USDT notional.\n\n20x leverage\n\nInitial margin = 2,000 / 20 = 100 USDT\n\nIf price drops and uPnL is +20 USDT:\n\nROI = 20 / 100 = 20%\n\nIf price rises and uPnL is -20 USDT:\n\nROI = -20 / 100 = -20%\n\nWorked margin example\n\nYou deposit 2,000 USDT and open a BTC long:\n\nFieldValue\nEntry price\n100,000 USDT\n\nPosition size\n0.1 BTC\n\nNotional value\n10,000 USDT\n\nSelected leverage\n10x\n\nTier minimum IMR\n2%\n\nInitial margin used at 10x\n10,000 / 10 = 1,000 USDT\n\nMaintenance margin required\n10,000 x 1% = 100 USDT\n\nThe important distinction is that the tier minimum sets the lowest margin the system allows, while your selected leverage determines how much of your collateral you actually commit. In this example, the tier would allow a lower minimum, but choosing 10x means you commit 1,000 USDT of margin to hold the position.\n\nAccount health\n\nYour account health is driven by Adjusted Account Value, unrealized PnL, and total maintenance margin required.\n\nhealth = adjusted_account_value / total_maintenance_margin_required\n\nHealth above 100% means you have buffer above maintenance requirements.\n\nHealth near maintenance means liquidation risk is increasing.\n\nHealth at maintenance means the account can become eligible for liquidation.\n\nBalances table reference\n\nWatch these values in your balances table to understand account health:\n\nColumnDescription\nAsset\nCollateral token\n\nBalance\nQuantity held\n\nLast Price\nCurrent index price\n\nTotal Equity\nRaw USD value (quantity x price)\n\nCollateral Value\nHaircut-adjusted value used for margin\n\nLLTV\nLiquidation LTV threshold for the asset\n\nLTV\nCurrent debt ratio when USDT debt exists\n\nAvailable Margin\nMargin available for new trades on the USDT row\n\nUnrealized PnL\nOpen position PnL on the USDT row\n\nMax Borrow\nTier-based USDT debt cap on the USDT row\n\nActions\nDeposit, Withdraw, Swap\n\nThe Portfolio Overview balances table lists each collateral asset with equity, collateral value, LTV metrics, and row actions such as Deposit, Withdraw, and Swap.\n\nAdjusting leverage\n\nYou can set leverage per market from the order entry panel. Decreasing leverage moves your liquidation price further away. Increasing leverage moves it closer.\n\nSee also\n\nMulticollateral Margin - USDT debt, Swap, and auto-exchange.\n\nDepositing Collateral - supported collateral and account caps.\n\nP&L Calculations\n\nLiquidations\n\nMarkets","tokens":1681,"crawled_at":1791192967558}
+{"id":10171,"url":"https://www.metaplex.com/docs/smart-contracts/token-metadata/transfer","domain":"www.metaplex.com","chapter":"docs","title":"Transferring Assets | Token Metadata","text":"Token Metadata is a legacy program. It remains supported, but is not recommended for new projects. Use Core instead.\n\nThe owner of an asset can transfer it to another account by sending a Transfer instruction to the Token Metadata program. This instruction accepts the following attributes:\nAuthority: The signer that authorized the transfer. Typically, this is the owner of the asset but note that certain delegated authorities can also transfer assets on behalf of the owner as discussed in the \"Delegated Authorities\" page.\nToken Owner: The public key of the current owner of the asset.\nDestination Owner: The public key of the new owner of the asset.\nToken Standard: The standard of the asset being transferred. This instruction works for all Token Standards in order to provide a unified interface for transferring assets. That being said, it is worth noting that non-programmable assets can be transferred using the Transfer instruction of the SPL Token program directly.\nHere is how you can use our SDKs to transfer an asset on Token Metadata.\nTransfer NFT\n\n1import { publicKey } from '@metaplex-foundation/umi';\n\n2import {\n\n3 transferV1,\n\n4 TokenStandard,\n\n5} from '@metaplex-foundation/mpl-token-metadata';\n\n6\n\n7// Assuming umi is set up with mplTokenMetadata plugin\n\n8// See getting-started for full setup\n\n9\n\n10const mintAddress = publicKey('mintAddress...');\n\n11const currentOwner = umi.identity; // Current token owner\n\n12const destinationOwner = publicKey('destinationWallet...');\n\n13\n\n14// Transfer the NFT to a new owner\n\n15await transferV1(umi, {\n\n16 mint: mintAddress,\n\n17 authority: currentOwner,\n\n18 tokenOwner: currentOwner.publicKey,\n\n19 destinationOwner,\n\n20 tokenStandard: TokenStandard.NonFungible,\n\n21}).sendAndConfirm(umi);\n\n22\n\n23console.log('NFT transferred to:', destinationOwner);\n\n1import {\n\n2 getTransferV1InstructionAsync,\n\n3 TokenStandard,\n\n4} from '@metaplex-foundation/mpl-token-metadata-kit';\n\n5\n\n6// Assuming rpc, rpcSubscriptions, sendAndConfirm, and authority are set up\n\n7// See getting-started for full setup\n\n8\n\n9const mintAddress = 'mintAddress...'; // The NFT mint address\n\n10const currentOwner = authority.address; // Current token owner\n\n11const destinationOwner = 'destinationWallet...'; // New owner address\n\n12\n\n13// Transfer the NFT to a new owner\n\n14const transferIx = await getTransferV1InstructionAsync({\n\n15 mint: mintAddress,\n\n16 tokenOwner: currentOwner,\n\n17 destinationOwner,\n\n18 authority,\n\n19 payer: authority,\n\n20 tokenStandard: TokenStandard.NonFungible,\n\n21});\n\n22\n\n23await sendAndConfirm({\n\n24 instructions: [transferIx],\n\n25 payer: authority,\n\n26});\n\n27\n\n28console.log('NFT transferred to:', destinationOwner);\n\nTransfer pNFT\nProgrammable NFTs (pNFTs) may have additional authorization rules that need to be handled during transfer. The instruction will automatically handle Token Record accounts.\n\n1import { publicKey } from '@metaplex-foundation/umi';\n\n2import {\n\n3 transferV1,\n\n4 TokenStandard,\n\n5} from '@metaplex-foundation/mpl-token-metadata';\n\n6\n\n7// Assuming umi is set up with mplTokenMetadata plugin\n\n8\n\n9const mintAddress = publicKey('mintAddress...');\n\n10const currentOwner = umi.identity;\n\n11const destinationOwner = publicKey('destinationWallet...');\n\n12\n\n13// Transfer the Programmable NFT to a new owner\n\n14// Note: pNFTs require additional Token Record accounts handled automatically\n\n15await transferV1(umi, {\n\n16 mint: mintAddress,\n\n17 authority: currentOwner,\n\n18 tokenOwner: currentOwner.publicKey,\n\n19 destinationOwner,\n\n20 tokenStandard: TokenStandard.ProgrammableNonFungible,\n\n21}).sendAndConfirm(umi);\n\n22\n\n23console.log('pNFT transferred to:', destinationOwner);\n\n1import {\n\n2 getTransferV1InstructionAsync,\n\n3 TokenStandard,\n\n4} from '@metaplex-foundation/mpl-token-metadata-kit';\n\n5\n\n6// Assuming rpc, rpcSubscriptions, sendAndConfirm, and authority are set up\n\n7\n\n8const mintAddress = 'mintAddress...'; // The pNFT mint address\n\n9const currentOwner = authority.address;\n\n10const destinationOwner = 'destinationWallet...';\n\n11\n\n12// Transfer the Programmable NFT to a new owner\n\n13// Note: pNFTs require additional Token Record accounts handled automatically\n\n14const transferIx = await getTransferV1InstructionAsync({\n\n15 mint: mintAddress,\n\n16 tokenOwner: currentOwner,\n\n17 destinationOwner,\n\n18 authority,\n\n19 payer: authority,\n\n20 tokenStandard: TokenStandard.ProgrammableNonFungible,\n\n21});\n\n22\n\n23await sendAndConfirm({\n\n24 instructions: [transferIx],\n\n25 payer: authority,\n\n26});\n\n27\n\n28console.log('pNFT transferred to:', destinationOwner);\n\nAdvanced pNFT Transfer\nFor pNFTs with complex authorization rules, you may need to provide additional parameters.\n\n1import { getMplTokenAuthRulesProgramId } from '@metaplex-foundation/mpl-candy-machine';\n\n2import {\n\n3 fetchDigitalAssetWithAssociatedToken,\n\n4 findTokenRecordPda,\n\n5 TokenStandard,\n\n6 transferV1,\n\n7} from '@metaplex-foundation/mpl-token-metadata';\n\n8import { findAssociatedTokenPda } from '@metaplex-foundation/mpl-toolbox';\n\n9import { publicKey, unwrapOptionRecursively } from '@metaplex-foundation/umi';\n\n10import { base58 } from '@metaplex-foundation/umi/serializers';\n\n11\n\n12// The NFT Asset Mint ID\n\n13const mintId = publicKey('11111111111111111111111111111111');\n\n14\n\n15// The destination wallet\n\n16const destinationAddress = publicKey('22222222222222222222222222222222');\n\n17\n\n18// Fetch the pNFT Asset with the Token Account\n\n19const assetWithToken = await fetchDigitalAssetWithAssociatedToken(\n\n20 umi,\n\n21 mintId,\n\n22 umi.identity.publicKey\n\n23);\n\n24\n\n25// Calculates the destination wallet's Token Account\n\n26const destinationTokenAccount = findAssociatedTokenPda(umi, {\n\n27 mint: mintId,\n\n28 owner: destinationAddress,\n\n29});\n\n30\n\n31// Calculates the destinations wallet's Token Record Account\n\n32const destinationTokenRecord = findTokenRecordPda(umi, {\n\n33 mint: mintId,\n\n34 token: destinationTokenAccount[0],\n\n35});\n\n36\n\n37// Transfer the pNFT\n\n38const { signature } = await transferV1(umi, {\n\n39 mint: mintId,\n\n40 destinationOwner: destinationAddress,\n\n41 destinationTokenRecord: destinationTokenRecord,\n\n42 tokenRecord: assetWithToken.tokenRecord?.publicKey,\n\n43 tokenStandard: TokenStandard.ProgrammableNonFungible,\n\n44 // Check to see if the pNFT asset as auth rules.\n\n45 authorizationRules:\n\n46 unwrapOptionRecursively(assetWithToken.metadata.programmableConfig)\n\n47 ?.ruleSet || undefined,\n\n48 // Auth rules program ID\n\n49 authorizationRulesProgram: getMplTokenAuthRulesProgramId(umi),\n\n50 // Some pNFTs may require authorization data if set.\n\n51 authorizationData: undefined,\n\n52}).sendAndConfirm(umi);\n\n53\n\n54console.log('Signature:', base58.deserialize(signature));\n\n1import { address } from '@solana/addresses';\n\n2import {\n\n3 getTransferV1InstructionAsync,\n\n4 TokenStandard,\n\n5} from '@metaplex-foundation/mpl-token-metadata-kit';\n\n6\n\n7// Assuming rpc, sendAndConfirm, and authority are set up\n\n8\n\n9const mintAddress = address('mintAddress...'); // Your pNFT mint address\n\n10const currentOwner = authority.address;\n\n11const destinationOwner = address('destinationWallet...'); // Destination wallet\n\n12\n\n13// For pNFTs with auth rules, the SDK handles most resolution automatically\n\n14const transferIx = await getTransferV1InstructionAsync({\n\n15 mint: mintAddress,\n\n16 tokenOwner: currentOwner,\n\n17 destinationOwner,\n\n18 authority,\n\n19 payer: authority,\n\n20 tokenStandard: TokenStandard.ProgrammableNonFungible,\n\n21 // Auth rules are resolved automatically when available\n\n22});\n\n23\n\n24await sendAndConfirm({\n\n25 instructions: [transferIx],\n\n26 payer: authority,\n\n27});\n\n28\n\n29console.log('pNFT transferred to:', destinationOwner);","tokens":1904,"crawled_at":1791192998061}
+{"id":10172,"url":"https://a16zcrypto.com/team/istvan-andras-seres","domain":"a16zcrypto.com","chapter":"research","title":"István András Seres - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nIstván András Seres\n\nFeed\nFilter\n(1)\nclear filters\n\ncategory\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\nrecommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nauthor\n(1) all authors\n@x0rart\n1337 Skulls Sers\na16z crypto\na16z crypto editorial\na16z crypto policy & regulatory teams\na16z crypto Regulatory Team\nAaditya Shidham\nAaron Levie\nAaron Phillips\nAaron Schnider\nAbby Green\nAbdou Ndiaye\nAbhi Shelat\nAbhiram Kothapalli\nAbigail Johnson\nAdam Alter\nAdam Back\nAdam Bry\nAdam Grant\nAdam Ludwin\nAdam Martin\nAdam Thierer\nAdam Zuckerman\nAdela Tomsejova\nAdena Friedman\nAdena Hefets\nAdeniyi Abiodun\nAdina Fischer\nAdrian Cockcroft\nAdrian Fenty\nAdrienne Mayor\nAgostino Capponi\nAiden Slavin\nAileen Lee\nAisha Stephenson\nAJ Shankar\nAlan Knott-Craig\nAlan Schaaf\nAlana Benton\nAlbert Tang\nAlec Nielsen\nAlec Ross\nAlejandro Flores\nAlex Constantinople\nAlex Honnold\nAlex Hutchinson\nAlex Immerman\nAlex Kreitz\nAlex Kroeger\nAlex Le\nAlex Masmej\nAlex Morcos\nAlex Price\nAlex Pruden\nAlex Rampell\nAlex Roetter\nAlex Solomon\nAlex Spector\nAlex Stamos\nAlex Tabarrok\nAlexander (Sasha) Spiegelman\nAlexander Chia\nAlexander Zoppa\nAlexandra Chang\nAlexandria Lafci\nAlexis Lakes\nAlexis Madrigal\nAlexis Ohanian\nAli Ghodsi\nAli Yahya\nAlicia Barone\nAlin Tomescu\nAlisha Litman\nAlison Mangiero\nAlison Martin\nAllison Pickens\nAlyssa Del Bene\nAlyssa Torres\nAmanda Cantor\nAmanda Cassatt\nAmanda Catherine\nAmanda Mulay\nAmanda Tuminelli\nAmanda Tyler\nAmelia Salyers\nAmie Tyrrel\nAmir Shevat\nAmira Yahyaoui\nAmy Abernethy\nAmy Berliner\nAmy Bohutinsky\nAmy Choice\nAmy Cray\nAmy Gill\nAmy Hoemeke\nAmy Kalokerinos\nAmy Robertson\nAna Mostarac\nAna Susi\nAnatoly Yakovenko\nAndie Taylor\nAndisheh Tahriri\nAndre Iguodala\nAndrea Clarke Hall\nAndrea Feinberg\nAndrea Rallo\nAndrea Simon\nAndrea Vinkler\nAndreas Papadimitropoulos, Jr\nAndreessen Horowitz\nAndrew Allen\nAndrew Chen\nAndrew F. Read\nAndrew Green\nAndrew Hall\nAndrew Lakis\nAndrew Lewis-Pye\nAndrew Lo\nAndrew Mason\nAndrew McAfee\nAndrew Milson\nAndrew Omori\nAndrew Radin\nAndrew Rubin\nAndrew Savage\nAndrew Smith\nAndrew Tretyakov\nAndy Beal\nAndy Coravos\nAndy Golden\nAndy Hill\nAndy Milenius\nAndy Rachleff\nAndy Tran\nAndy Walshe\nAneel Lakhani\nAngela Schenone\nAngela Strange\nAngela Tran Kingyens\nAngelica Gehr\nAniket Kate\nAnil Sethi\nAnish Acharya\nAnn Winblad\nAnna Berces\nAnna Jablonski\nAnna Semenova\nAnna Van Meurs\nAnnaLee Saxenian\nAnne Brandes\nAnne Lee Skates\nAnne Lewandowski\nAnne Mitchell\nAnne Yip\nAnnie Collins\nAnnie Duke\nAnthony Albanese\nAnthony Atala\nAnthony Foxx\nAnthony Lee Zhang\nAntonio Viggiano\nAntwone Stigall\nAnu Hariharan\nApril Roth\nAri Emanuel\nAri Juels\nArianna Huffington\nArianna Simpson\nArik Kershenbaum\nArmon Dadgar\nArnie Goldberg\nArsho Avetian\nArthur Brooks\nArun Sundararajan\nAsh Ashutosh\nAsha Christian\nAshley McCollum\nAshley Stern\nAshton Carter\nAtif Mian\nAtul Butte\nAubree Pelaez\nAubrey de Grey\nAugusto Marietti\nAurora Petracca\nAusten Allred\nAustin Guzman\nAustin Marchese\nAustin Wilson\nAva Iravani\nAvery Segal\nAvinash Solanky\nAviv Zohar\nAye Moah\nAzeem Azhar\nBailey Flanigan\nBailey Richardson\nBalaji Srinivasan\nBarry McCarthy\nBart Dessaint\nBeau Cronin\nBeau Woods\nBecky Pferdehirt\nBen Buckwalter\nBen Fielding\nBen Fisch\nBen Gardner\nBen Gomez\nBen Horowitz\nBen Kaufman\nBen Leventhal\nBen Lovell\nBen Napier\nBen Portney\nBen Rubin\nBen Scharfstein\nBen Schecter\nBen Silbermann\nBen Uretsky\nBen Wu\nBenedict Evans\nBenedikt Büenz\nBenjamin Ebner\nBenjamin Hindman\nBenjamin Wittes\nBenjamin Wu\nBennett Carroccio\nBenny Pinkas\nBernard J. Tyson\nBernard Tyson\nBeth Newman\nBethany Coates\nBharat Ramamurti\nBharath Ramsundar\nBill Carr\nBill Frist\nBill Hinman\nBill Janeway\nBill Krause\nBill Macaitis\nBlake Kim\nBlake Masters\nBlake Saari\nBlayne Donnell\nBob Iger\nBob Langer\nBob Moore\nBob Muglia\nBob Sutton\nBob Swan\nBob Tinker\nBob Wachter\nBobby Franklin\nBobby Green\nBobby Kotick\nBobby Wagner\nBoris Sofman\nBoris Wertz\nBrad Feld\nBrad Kern\nBrad Peterson\nBram Cohen\nBrandon Ballinger\nBrandon Barros\nBrandon Cherry\nBrandon Millman\nBrenda Kopf\nBrent McIntosh\nBrett Browman\nBrett Falk\nBrett Hagler\nBrewster Kahle\nBrian Armstrong\nBrian Balfour\nBrian Brooks\nBrian Crnkovich\nBrian Curran\nBrian Grazer\nBrian Koppelman\nBrian McCullough\nBrian Quintenz\nBrian Wilkins\nBridget McDowell\nBrittany Lucas\nBrittney Burrows\nBrooke Sheresky\nBruce Friedrich\nBryan Caplan\nBryan Chiang\nBryan Cox\nBryan Crowley\nBryan Faust\nBryan Houser\nBryan Kim\nBryan Pellegrino\nCaitlin Glazebrook\nCaitlin Johnston\nCaitlin Roberson\nCal Turner Jr.\nCaleb Christian\nCameron Schuler\nCamila De Souza\nCarine Carmy\nCarissa Bilinski\nCarl Agnelli\nCarl Eschenbach\nCarl Narcisse\nCarl Pope\nCarlos Araya\nCarolina Gonzalez\nCaroline Friedman\nCaroline Goggins\nCaroline Horn\nCaroline Moon\nCarolyn Bertozzi\nCarra Wu\nCasey Graul\nCasey Neistat\nCasey Winters\nCassady Churchill\nCassie Faerber\nCecilia Marshall\nCeia Font\nChad Rigetti\nChandra Krintz\nCharles Goetz\nCharles Hubbard\nCharles Koch\nCharlie Keinath\nCharlie Warzel\nChattry Meas\nChelsea Komlo\nChelsea Padilla\nCheng Li\nChris Bennett\nChris Best\nChris Burniske\nChris Curran\nChris DeWolfe\nChris Dixon\nChris Granger\nChris Hauth\nChris Lyons\nChris Messina\nChris Milk\nChris Power\nChris Santa Maria\nChris Wanstrath\nChristian Cachin\nChristian Catalini\nChristian Crowley\nChristian Seifert\nChristina Hampp\nChristina Lopes\nChristina Mercando\nChristina Xu\nChristina Zeidan\nChristine Darden\nChristine Perham\nChristopher Giancarlo\nChristopher Lee\nChristopher Mims\nChristopher Nguyen\nChristopher Rippingham\nChristopher Schroeder\nChristy Hubbard\nCiamac Moallemi\nCindi Zhang\nCindy Tenner\nClaire Austin\nClaire Cain Miller\nClaire Kart\nClaudia Picanco\nClay Shirky\nClayton Christensen\nClayton Gardner\nClifford Woolf\nClint Delapaz\nColin Bryar\nColin Rom\nCollin McCune\nConner Lyons Brown\nConnie Chan\nConnie Guglielmo\nConnor McCarthy\nConnor Moyles\nCorban Bell\nCorey Hawkins\nCorey Waller\nCourtney Dettlinger\nCraig Naylor\nCraig Walker\nCristina Cordova\nCurt Funderburk\nCuy Sheffield\nD'Arcy Coolican\nDaejun Park\nDaisy Linden\nDaisy Wolf\nDaljeet Virdi\nDalton Turay\nDan Berkenstock\nDan Boneh\nDan Frommer\nDan Primack\nDan Romero\nDan Shapero\nDan Siroker\nDan Stein\nDan Warmenhoven\nDan Wendlandt\nDaniel Chao\nDaniel Chen\nDanielle Andrzejewski\nDanielle Clark\nDanielle Looymans\nDanielle Lussier\nDanielle Morrill\nDanielle Shea\nDanny Shader\nDaphne Koller\nDapper Dan\nDaren Matsuoka\nDarin Malter\nDarshan Shankar\nDas Rush\nDave Jagoda\nDave King\nDave Touretzky\nDavid Banks\nDavid Belden\nDavid Damato\nDavid Deming\nDavid George\nDavid Haber\nDavid Hollestelle\nDavid Kerr\nDavid Lee\nDavid Mack\nDavid Madden\nDavid Marcus\nDavid Olson\nDavid Oyelowo\nDavid Pierce\nDavid Reich\nDavid Rumsey\nDavid Schweikert\nDavid Sinclair\nDavid Sverdlov\nDavid Tse\nDavid Ulevitch\nDavid Weiden\nDawn Lepore\nDawn Nott\nDeborah Embaie\nDeena Elitreby\nDeepak Maram\nDenis Nazarov\nDenis Young\nDenise Gonzalez\nDerek Dolin\nDerek Thompson\nDerrick Harris\nDevin Finzer\nDevon Zuegel\nDiana Peña\nDiane Greene\nDick Costolo\nDieter Shirley\nDiishan Imira\nDiogo Monica\nDominic Shine\nDominique Reliford\nDon Duet\nDon Faul\nDorris O'Brien\nDoug Ducey\nDoug Folden\nDoug McCracken\nDouglas Argueta\nDozie Uche\nDrew Coffman\nDylan Field\nDylan Rhodes\nEd Felten\nEd Lynch\nEddie Lim\nEddy Lazzarin\nEdith Zimmerman\nEdward Perkins\nEdwin Poston\nEfrat Noy\nEhud Shapiro\nEileen Burbidge\nEileen Wu\nElad Gil\nElaine Fuchs\nElaine Shi\nElena Burger\nEli Dourado\nElisa Leonhardt\nEliza Oak\nElizabeth Gunn\nElizabeth Harkavy\nElizabeth May\nElizabeth Ocken\nElizabeth Stark\nElizabeth Weil\nEllen Tunoa\nEmile Petrone\nEmilio Torres\nEmily Graff\nEmily Hinsch\nEmily Keir\nEmily Oster\nEmily Westerhold\nEmma Janaskie\nEric Budish\nEric Dai\nEric Ries\nEric Thomas\nEric Topol\nEric Wu\nErica Schecter\nErik Brynjolfsson\nErik Kiser\nErik Torenberg\nErika Bracken\nErika Herrera\nErika Louie\nErin Grody Kingsley\nErin Murphy\nErin Tice\nErin Tonnar\nErin Winkler\nErtem Nusret Tas\nEsther Shinn\nEthan Bueno de Mesquita\nEthan Ferreira\nEthan Zuckerman\nEuan Ashley\nEugene Volokh\nEugene Wei\nEugenia Yee\nEula Takahashi\nEva Sakkas\nEvan Burfield\nEvan Osnos\nEvangelos Simoudis\nEzra Klein\nF. Gary Gray\nFabiola Godinez\nFabrizio Zilibotti\nFahad Saleh\nFarid Jiandani\nFei-Fei Li\nFelix Do\nFEWOCIOUS\nFiona Kennedy\nFiona Murray\nFlashrekt\nFlora Oliveira\nFlori Del Valle\nFlorian Leibert\nFoteini Baldimtsi\nFrancesca Gino\nFrank Chen\nFrank Wilczek\nFred Benenson\nFred Ehrsam\nFred Upton\nFred Wilson\nFreda Lewis-Hall\nFrederic Kerrest\nFuture Editorial\nGabby Dizon\nGabby Reece\nGabriel Otte\nGabriel Vasquez\nGaetan Barthelemy\nGarrett Biel\nGary Ang\nGary Reedy\nGary Wolf\nGaurav Banga\nGaurav Dhillon\nGaut\nGayle Tzemach Lemmon\nGeoffrey Woo\nGeorg Fuchsbauer\nGeorg Petschnigg\nGeorge Church\nGeorge Danezis\nGeorge Fraser\nGeraldine Chan\nGérard Cachon\nGerard Ryle\nGerri Elliott\nGerry Tsoukalas\nGia Scinto\nGil Elbaz\nGil Shafir\nGina Moon\nGina Neff\nGina Yocom\nGinger Liau\nGokul Rajaram\nGoldie Chang\nGrace Ellis\nGraham Allison\nGrant Gregory\nGrant Jordan\nGrant LaFontaine\nGrant Rabenn\nGray Kinsella\nGreg Bowman\nGreg Clayman\nGreg Linares\nGreg Loehmann\nGreg Lynn\nGreg Solano\nGreg Truesdell\nGreg Waldon\nGregory Allen\nGregory Mundis\nGretchen Bush\nGretchen McCulloch\nGuido Appenzeller\nGustav Söderström\nGustavo Garcia\nGuy Goren\nGuy Raz\nGuy Wuollet\nHaley Van Dyck\nHanna Aziz\nHannah Frankl\nHanne Winarsky\nHaoyuan Li\nHarmit Malik\nHarry Grieve\nHarry Shum\nHarry Wright\nHatim Shafique\nHayden Adams\nHeather Gwynn\nHeather Podesta\nHedi Samar\nHelen Stoddard\nHelen Su\nHemant Mohapatra\nHendrik Pretorius\nHenri Kor\nHerb Lin\nHerman Narula\nHilmar Pétursson\nHoang Nguyen\nHoward Wu\nIan Dutra\nIan Shannon\nIan Sharp\nIce Cube\nIlan Zechory\nIllia Polosukhin\nIlyas Khan\nIma Christian\nIman Abuzeid\nInsiya Lokhandwala\nIon Stoica\nIrvin Chan\nIsa Guardalabene\nIsaiah Lott\nIsh Verduzco\nIsil Dillig\nIstván András Seres\nIttai Abraham\nIttay Eyal\nIva Messy\nIvan Linscott\nIvor Horn\nJ.D. Moriarty\nJack Donahoe\nJack Soslow\nJackie McQuiston\nJackson David\nJacob Westphal\nJacquelyn Melinek\nJad Esber\nJad Naous\nJade Lai\nJade Raymond\nJae Gnazzo\nJai Ramaswamy\nJaimie Buss\nJak Kennedy\nJake Auchincloss\nJakob Uszkoreit\nJamal Mohammed\nJames Beshara\nJames Currier\nJames da Costa\nJames Gwertzman\nJames J. Collins\nJames Kissell\nJames L. Madara\nJames Loftus\nJames Rathmell\nJames Rogers\nJames Watters\nJames Wu\nJames Zou\nJamie Brandon\nJamie McGurk\nJamie Sullivan\nJamilla Hemeid\nJana Odehnal\nJane Doe\nJane Lippencott\nJane Suh\nJanelle De Los Santos\nJared Bricklin\nJared Furutani\nJared Georgakopoulos\nJared Polis\nJared Smith\nJase Wilson\nJason Franklin\nJason Liu\nJason Mayden\nJason Milionis\nJason Mitchell\nJason Mok\nJason Rosenthal\nJason Warner\nJason Yanowitz\nJay Bradner\nJay Conte\nJay Drain\nJay Komarneni\nJay Rughani\nJean Reilly\nJeanne Tsan\nJeff Amico\nJeff Benson\nJeff Clark\nJeff Cordova\nJeff Glueck\nJeff Hawkins\nJeff Jones\nJeff Jordan\nJeff Lawson\nJeff Lu\nJeff Nagashima\nJeff Stump\nJeff Weiner\nJeffrey Immelt\nJeffrey Kaditz\nJeffrey Katzenberg\nJeffrey Kindler\nJeffrey Low\nJeffrey Silverstein\nJeffrey Zirlin\nJen Bulawsky\nJen Kha\nJenna Walsh\nJenna Zucker\nJennifer 8. Lee\nJennifer Doudna\nJennifer Kodner\nJennifer Konde\nJennifer Li\nJennifer Mumford\nJennifer Tejada\nJennifer Young\nJenny Cieplak\nJens Ernstberger\nJensen Harris\nJeremy Clark\nJeremy England\nJeremy Zhang\nJesse Holmes\nJesse Pollak\nJesse Walden\nJessica Childs\nJessica Hansen\nJessica Keeler\nJessica Patton\nJessica Verrilli\nJewel Pi\nJez Humble\nJi Kim\nJianying Luo\nJim Gilliam\nJimmy Chen\nJimmy Soni\nJing Wang\nJing Zou\nJJ Yu\nJoachim Neu\nJodi Lynn\nJodie Lutkenhaus\nJoe Gebbia\nJoe Grundfest\nJoe Montana\nJoe Morrissey\nJoe Schmidt\nJoe Sullivan\nJoel de la Garza\nJoel Mokyr\nJoel Monegro\nJoel Spolsky\nJoey Burleson\nJohn China\nJohn Collison\nJohn Fawcett\nJohn Garcia\nJohn Gedmark\nJohn Hennessy\nJohn Koelliker\nJohn M. Jack\nJohn Markoff\nJohn Menna\nJohn O’Farrell\nJohn Riccitiello\nJohn Smesko\nJohn Stanfield\nJohn Thompson\nJohn William Hatfield\nJonah Peretti\nJonathan Bush\nJonathan Dotan\nJonathan Downey\nJonathan Lai\nJonathan Lim\nJonathan Lusthaus\nJonathan Weissman\nJonathan Wong\nJordan Mazer\nJordan Stankowski\nJorge Conde\nJorge Gomez\nJose Guardado\nJoseph Bonneau\nJoseph Okpaku\nJoseph Spisak\nJosh Arnold\nJosh Bloom\nJosh Kim\nJosh Williams\nJoshua Browder\nJoshua Gans\nJoshua Grimm\nJoshua Hix\nJoshua Levin\nJoshua Lu\nJoshua Schank\nJoshua Soto\nJosie Ma\nJoyce Park\nJR Rivers\nJT Evans\nJuan Benet\nJudene Small\nJudy Savitskaya\nJudy Smith\nJulia Grace\nJulia Kirby\nJulie Bornstein\nJulie Farnham\nJulie Johnson\nJulie Samuels\nJulie Yoo\nJuliet Grier\nJuliet Nyatta\nJuliette Morton\nJulius Zhang\nJustin Bailey\nJustin Bethune\nJustin Blau\nJustin Cunningham\nJustin Gregorius\nJustin Kahl\nJustin Kan\nJustin Larkin\nJustin Paine\nJustin Pettit\nJustin Roberts\nJustin Simcock\nJustin Thaler\nJustine Moore\nJutta Steiner\nJyoti Bansal\nJZ Young\nKabir Gill\nKabir Laroia\nKais Khimji\nKamala Harris\nKaren Dunn\nKaren Wooley\nKarina Sobieski\nKarl Floersch\nkarma (Daniel Reynaud)\nKarmacoma\nKarthik Rau\nKartik Nayak\nKate Darling\nKate Dellolio\nKate Kerames\nKatherine Boyle\nKatherine Minarik\nKatherine Rundell\nKatherine Schoebel\nKathryn McKinley\nKathy Liu\nKathy Yang\nKatia Ameri\nKatie Baynes\nKatie Haun\nKatie Hemmerling\nKaty DeWitt-Drew\nKaty Nelson\nKayvon Tehranian\nKeener Barnhorst\nKeller Medlin\nKeller Rinaudo\nKelly Cannon\nKelsey Chaplinsky\nKelsey Mellard\nKen Chong\nKen Coleman\nKen Kocienda\nKerry Ganim\nKesha Cash\nKevin Chou\nKevin Chu\nKevin Dulsky\nKevin Kelly\nKevin McKinley\nKevin Nishioka\nKevin O'Kane\nKevin Rose\nKevin Tan\nKevin Wu\nKevin Zollman\nKidSuper\nKieran Snyder\nKierston Gittens\nKiki Mavridis\nKim Enright\nKim Malone Scott\nKim Milosevich\nKim Stevenson\nKim Zetter\nKimberly Tan\nKindra Mason\nKira Poskanzer\nKira Song\nKirstin Arbide\nKirt McMaster\nKofi Ampadu\nKouki Harasaki\nKrista Anderson-Copperman\nKristen Fortney\nKristen Johansson\nKristen Kee\nKristin Sauchak\nKristin Thayer\nKristina Graci-deLuna\nKristina Shen\nKristine Lipscomb\nKristo Käärmann\nKrisztina Holly\nKunal Bahl\nKunle Olukotun\nKurt House\nKyle Russell\nLaird Hamilton\nLatasha\nLaura Arrillaga-Andreessen\nLaura Baller\nLaura Behrens Wu\nLaura Deming\nLaura Gravley\nLaura Johnson\nLaura Shores\nLaura Weidman Powers\nLauren Berson\nLauren Illovsky\nLauren Murrow\nLauren Richardson\nLauren Spragge\nLaurene Powell Jobs\nLawrence Levy\nLawrence Summers\nLeah Cassidy\nLee Kleinman\nLee Lefkowitz\nLeeAnn Caballero\nLeila Hay\nLeila Janah\nLenny Rachitsky\nLeslie Jaw\nLeslie Vosshall\nLester Chen\nLi Fan\nLi Fei-Fei\nLi Jin\nLiang Wu\nLilian King\nLily Liu\nLina Sergie Attar\nLinda Banuelos\nLinda Xie\nLinden Tibbets\nLing Ren\nLinlin Li\nLinxin Wen\nLioba Heimbach\nLisa Hawke\nLisa Lambert\nLisa Orr\nLisa Reilly\nLisa Rosano\nLizzy Anderson\nLJ Erwin\nLloyd Dean\nLoretta Sanchez\nLori Potter\nLuca Prosperi\nLuca Zanolini\nLuis Martinez\nLuis von Ahn\nLuke Wroblewski\nLydia Green\nLynda Gibson\nLynn Rudolph\nMadan Nagaldinne\nMaddison Masaeli\nMadeline Lancaster\nMaggie Hsu\nMaggie Leung\nMaggie Romero\nMahad Abedin\nMahesh Iyer\nMahesh Vellanki\nMahimna Kelkar\nMakiri Duckett\nMalinka Walaliyadde\nMallesh M. Pai\nMalloy Evans\nManas Punhani\nManny Luna\nMarc Andreessen\nMarc Andrusko\nMarc Benioff\nMarc Levinson\nMarci Barbera\nMarco Reuter\nMargaret Jen\nMargit Wennmachers\nMaria LaMagna Morales\nMarian Garvin\nMarianne Winkler\nMariano Sorgente\nMaricarmen Alvarez\nMariel Goldenstein\nMarigold Vu\nMarina Kusserow\nMario Gabriele\nMario Linares\nMarissa Bramlett\nMark Cranney\nMark Leslie\nMark McAndrew\nMark McClusky\nMárk Melczer\nMark Moore\nMark Regan\nMark Sendak\nMarkos Georghiades\nMarkus Covert\nMarkus Funk\nMartha Lane Fox\nMartin Casado\nMartin Fischer\nMarty Makary\nMarvin Ammori\nMarvin Zamora\nMary Pat Jordan\nMary-Catherine Lader\nMaryam Bahrani\nMason Hall\nMatei Zaharia\nMatt Abrahams\nMatt Billmann\nMatt Bornstein\nMatt Clifford\nMatt Flannery\nMatt Fleming\nMatt Gleason\nMatt Kaeberlein\nMatt Levine\nMatt Levy\nMatt Oberhardt\nMatt Shortal\nMatt Spence\nMatt Weinberg\nMatthew Colford\nMatthew Green\nMatthew Haughey\nMatthew McCullough\nMatthew Mills\nMatthew Olsen\nMatthew Rutter\nMatthew Stein\nMatthieu Hafemeister\nMaureen Lara\nMax Kesten\nMax Krohn\nMax Levchin\nMax Polyak\nMax Resnick\nMax Ventilla\nMaya Rahkonen\nMcPherson Moore\nMeaghan Hardy\nMeg Whitman\nMegan Holston-Alexander\nMegan Kristalyn\nMehdi Hasan\nMehul Mehta\nMel Williams\nMelanie Galang\nMelissa Liao\nMelissa Minor\nMelissa Wasser\nMellody Hobson\nMelody Latronico\nMeredith Donahue\nMia Gonzalez\nMia Mandich\nMicah Johnson\nMichael Beckerman\nMichael Blau\nMichael Brandt\nMichael Chan\nMichael Copeland\nMichael Dearing\nMichael Dell\nMichael Franklin\nMichael Garcia\nMichael J. Casey\nMichael J. Freedman\nMichael Killam\nMichael King\nMichael Lee\nMichael Leiter\nMichael Morell\nMichael Ostrovsky\nMichael Ovitz\nMichael Paulus\nMichael Raynor\nMichael Reed\nMichael Snyder\nMichael Temkin\nMichael Wee\nMichael Zhu\nMichel Del Buono\nMichel Feaster\nMichèle Flournoy\nMichele Griffin\nMichele Korver\nMichele Law\nMichelle Ervin\nMichelle Kelso\nMichelle Kung\nMichelle Mundy\nMichelle Shin\nMichelle Ufford\nMichelle Volz\nMichelle Wilson\nMichelle Winn\nMichelle You\nMike Curtis\nMike Haydon\nMike Hearn\nMike Jones\nMike Kasperzak\nMike Kelly\nMike King\nMike Lempres\nMike Manning\nMike Maples jr\nMike Masnick\nMike Matchett\nMike Paulus\nMike Sandwick\nMikeal Rogers\nMikey Dickerson\nMiles Jennings\nMilijana Curic\nMiller Whitehouse-Levine\nMinerva Munoz\nMinnie Ingersoll\nMinsun Pak\nMintu Turakhia\nMiranda Christ\nMo Shaikh\nMohammad Akbarpour\nMohsen Malayeri\nMolly Grace\nMonique McCambridge\nMorgan Beller\nMorgan Bender\nMurat Pak\nMuriel Bowser\nMurray Shanahan\nMy Pham\nNadia Asparouhova\nNadia Eghbal\nNaftali Harris\nNaithan Jones\nNanjira Sambuli\nNaomi Metzger\nNashid Braswell\nNassim Eddequiouaq\nNat Barling\nNatacha Crooks\nNatalia Carrera\nNatalie Bucher\nNatalie Taumoepeau\nNate Chang\nNate Lau\nNathalie Balaban\nNathan McCauley\nNathan Yoon\nNathaniel Gleicher\nNathaniel Popper\nNav Singh\nNazanin Daneshvar\nNeel Maitra\nNeha Narula\nNelson Perla-Ward\nNeveen Bader\nNicholas Christakis\nNicholas Pacilio\nNick Babaian\nNick McKeown\nNick Quah\nNick Tomaino\nNicki Locker\nNicole Conner\nNicole Forsgren\nNicole Irvin\nNicole Neuman\nNicole Stanners\nNiels Provos\nNigel Robinson\nNikhil Krishnan\nNina Suthers\nNir Eyal\nNitasha Tiku\nNitin Natarajan\nNitya Subramanian\nNkiru Balonwu\nNoah Citron\nNoah Feldman\nNoah Levine\nNoah Smith\nNoam Nisan\nNoemi Glaeser\nO’Shea Jackson Jr.\nOlaf Carlson-Wee\nOleg Rogynskyy\nOliver Hsu\nOlivia Moore\nOlivia Webb\nOmri Weinstein\nOoshma Garg\nOprah Winfrey\nOrion Hindawi\nOscar Menjivar\nP.J. Hasleton\nPablo Montagnes\nPacky McCormick\nPak\nPalmer Luckey\nPamela Anderson\nPamon Forouhar\nParag Khanna\nParijat Talkad\nParker Brown\nParker Conrad\nPatrice Peck\nPatrick Byrne\nPatrick Collison\nPatrick Conway\nPatrick McCorry\nPatrick McHenry\nPatrick O’Grady\nPatrick Rivera\nPatrick Sutton\nPaul Cafiero\nPaul Daugherty\nPaul Davison\nPaul Krugman\nPaul Vigna\nPaula Long\nPenny Pritzker\nPerri Chilton\nPete Buttigieg\nPeter Blackwood\nPeter Buisseret\nPeter Chan\nPeter Donnelly\nPeter Johnson\nPeter Lauten\nPeter Leeson\nPeter Levine\nPeter Ludwig\nPeter Rubin\nPeter Thiel\nPeter Wang\nPetra Garrett\nPhil Daian\nPhil Hathaway\nPhil Wong\nPhong Nguyen\nPorter Smith\npplpleasr\nPranav Garimidi\nPrasad Akella\nPrat Moghe\nPreethi Kasireddy\npunk6529\nPurnima Padmanabhan\nPyrs Carvolth\nQasar Younis\nQuang Dao\nQuinten Burgunder\nQuintus Kilbourn\nRachael Horwitz\nRachel Goslins\nRachel Jenkins\nRachel Kalmar\nRachel McIntyre\nRachel Steiner\nRahul Iyer\nRahul Vohra\nRajeev Singh\nRajeev Venkayya\nRam Palaniappan\nRamana Jonnala\nRati Gelashvili\nRaul Vazquez\nRavi Parimi\nRay Dalio\nRaymond Carreira\nRebecca Lewis\nRebecca Rettig\nReed Hastings\nRefik Anadol\nRegina Benjamin\nRenato Valdés Olmos\nReshma Saujani\nReshma Sohoni\nRex Salisbury\nRich Ezekiel\nRichard Green\nRichard Menger\nRichard Rosenblatt\nRick Young\nRidhima Ahuja\nRiyaz Faizullabhoy\nRob Goodman\nRob McElhenney\nRob Pardo\nRob Rhinehart\nRobbie Petersen\nRobbie Peterson\nRobert Alexander\nRobert Cottrell\nRobert Hackett\nRobert Kolker\nRobert Leshner\nRobert McNeely\nRobert Moreno\nRobert Siegel\nRobert Stromberg\nRobert Weber\nRobin Casey\nRobin Guo\nRobin Weisman\nRod Johnson\nRodrigo Ibarra Lopez\nRodrigo Pacheco\nRoger Dickey\nRoger Wattenhofer\nRoham Gharegozlou\nRohini Mukand\nRohit Bansal\nRoman Mars\nRoman Stanek\nRon Gill\nRon Lavi\nRon Rothblum\nRonald Evans\nRonnie Harris\nRosa Davila\nRosalind Rattan\nRose Legarda\nRoss Andersen\nRoss Shuel\nRostin Behnam\nRuben Gallego\nRuben Smith\nRuss Altman\nRuss Heddleston\nRuss Roberts\nRussell Davies\nRyan Allen\nRyan Caldbeck\nRyan Conde\nRyan Holloway\nRyan Hoover\nRyan McEntush\nRyan Petersen\nRyan Prescott\nRyan Sandler\nRyan Spoon\nRyan Tseng\nRyan Walsh\nRyan Ward\nRyan Wyatt\nSaar Tochner\nSachin Jain\nSafi Bahcall\nSagar Dhawan\nSaku Panditharatne\nSalem Vance\nSam Blackshear\nSam Broner\nSam Gerstenzang\nSam Ragsdale\nSam Thompson\nSam Williams\nSam Yam\nSamantha Gelt\nSamantha Langford\nSamantha Ludwig\nSamson Wu\nSamuel Arbesman\nSamuel Hammond\nSandra Samayoa\nSandy Jen\nSankaet Pathak\nSantiago Rodriguez\nSara Boesen\nSarah Fazal\nSarah Hamburg\nSarah Lumbard\nSarah Mascardo\nSarah Meiklejohn\nSarah Porter\nSarah Rebello\nSarah Wang\nSasha Stiles\nSatish Talluri\nSaurabh Ladha\nSavannah Cherry\nScott Clark\nScott Duke Kominers\nScott Gottlieb\nScott Hassan\nScott Kupor\nScott Rubin\nScott Shenker\nScott Tyler\nScott Walker\nScott Weiss\nSean Duffy\nSean Neville\nSebastian Oddo\nSeema Amble\nSeemay Chou\nSep Kamvar\nSergiu Pasca\nSeth Lobree\nSeth Sivak\nSeth Sternberg\nShai Bernstein\nShai Kopeld\nShaka Senghor\nShakil Khan\nShan Sinha\nShana Fisher\nShane Mac\nShane Parrish\nShangda Xu\nShannon (Stubo) Brayton\nShannon Barbour\nShannon Kelly\nShannon Schiltz\nShannon Snow\nShari Doherty\nSharon Chang\nShawn Conway\nSheela Krothapalli\nShellye Archambeau\nSherie James\nSherriAnn Cole\nShishir Mehrotra\nShonda Rhimes\nSid Gorham\nSigne Pierce\nSimon Denny\nSiqi Chen\nSonal Chokshi\nSophie Song\nSoubhik Deb\nSpencer Dinwiddie\nSpencer Howard\nSpencer Rascoff\nSreeram Kannan\nSreevidya Kasturil\nSri Kosuri\nSriram Krishnan\nSrivatsan Sridhar\nStacey Cunningham\nStacey Merrick\nStacia Murray\nStacy Brown-Philpot\nStacy D'Amico\nStacy Warner\nStefan McDonough\nSten Tamkivi\nStephane Bancel\nStephanie Anyanwu\nStephanie Cohen\nStephanie Doppelt\nStephanie Smith\nStephanie Watkins\nStephanie Zinn\nStephen Armanios\nStephen Wink\nStephenie Zhang\nSteve Buress\nSteve Cadigan\nSteve Cheney\nSteve Harvey\nSteve Kaczynski\nSteve McDermid\nSteve Smith\nSteve Zhao\nSteven Adair\nSteven Ebert\nSteven Johnson\nSteven Levy\nSteven Sinofsky\nStewart Butterfield\nStina Ehrensvärd\nStuart Luman\nStuart Russell\nSudip Chakrabarti\nSue Hager\nSuhail Doshi\nSukhinder Singh Cassidy\nSumeet Singh\nSumit Shah\nSungMo Park\nSunil Chokshi\nSurya Ganguli\nSusan B. Wilde\nSusan Mernit\nSusan Rice\nSusannah Fox\nSydney Paul\nTaavet Hinrikus\nTaggart Matthiesen\nTamzen Brewis\nTana Billingsley\nTarek Mansour\nTarun Chitra\nTauri Laws Phillips\nTawny Holguin\nTaylor McFadden\nTed Not Lasso\nTed Sarandos\nTed Ullyot\nTerell Sterling\nTerence Carroll\nTeresa Carlson\nTerry Angelos\nTerry Brown\nThan Nguyen\nThanh Nguyen\nThe 2015 Academic Roundtable Sessions\nThe TxO team\nTheresa DeMichele\nTheresa Dilley\nTheresa Fisher\nTheresa Walz\nTheresia Gouw\nThibaut Scholasch\nThomas Gjerde\nThomas Juenger\nThomas Long\nThomas Rando\nTiffany Vo\nTiffany Zhong\nTim Beiko\nTim O'Reilly\nTim Roughgarden\nTim Schafer\nTim Sullivan\nTimmu Tõke\nTina Anderson\nTina Bhatnagar\nTina Ferguson\nTina Wie\ntinawie\nTing Ni\nTobi Lütke\nTodd Cranney\nTodd Lutwak\nTodd McKinnon\nTodd Park\nTodd Young\nTolga Dizdarer\nTom Butta\nTom Coates\nTom Davenport\nTom Ellis\nTom Hammer\nTom Hofmann\nTom Lehman\nTom Mitchell\nTom Preston-Werner\nTom Rikert\nTom Standage\nTomicah Tillemann\nTony Blair\nTony Blinken\nTori Landrum\nTracy Chou\nTracy Young\nTren Griffin\nTrent Mayol\nTrevor Bedford\nTristan Handy\nTristan Walker\nTroy Kirwin\nTugce Erten\nTurner Novak\nTushar Garg\nTyler Cowen\nTyler Wilson\nTyson Clark\nUma Valeti\nUsman Azam\nUzi Dutta\nValentina Marzorati\nValeria Nikolaenko\nValerie Arboleda\nVan Jones\nVan Le-Gray\nVanessa Kropf\nVas Narasimhan\nVaughn Ferguson\nVenkat Mocherla\nVicente De Baca\nVickie Casillas-Smith\nVictor Liang\nVictor Shoup\nVictoria Butcher\nVijay Balasubramaniyan\nVijay Kedar\nVijay Pande\nVineeta Agarwala\nVinod Khosla\nVirginia Postrel\nVishal Amin\nVitalik Buterin\nVivian Brooks\nVoices Onchain\nW. Brian Arthur\nWahab Owolabi\nWei Luo\nWendy Drpic\nWerner Gerola\nWes Taylor\nWhitney Owens\nWill Brown\nWill Wong\nWillem Mulder\nWilliam Gifford\nWilliam Mougayar\nWing Cheng\nXian Zhang\nXiang-Dong Fu\nXingchen Zhou\nYannai A. Gonczarowski\nYehuda Lindell\nYevgeniy Dodis\nYinuo Zhang\nYogi Roth\nYohei Ishii\nYoko Li\nYoni Levy\nYoram Novick\nYuichi Kurosawa\nYujin Chung\nYun Fan\nYung Yung Sheung\nYuval Efron\nYuval Harari\nZac Bookman\nZach Abrams\nZach Cohen\nZach Dicker\nZach Haigney\nZachary Chen\nZachary Gray\nZack Weiner\nZahabiya Gabaji\nZak Doric\nZal Bilimoria\nZane Lackey\nZeta Avarikioti\nZeya Yang\nZooko Wilcox\nZoran Basich\n\nclear all István András Seres\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n03.20.24 / Ertem Nusret Tas, István András Seres, Yinuo Zhang, Márk Melczer, Mahimna Kelkar, Joseph Bonneau and Valeria Nikolaenko\nNew paper alert: Atomic and fair data exchange via blockchain\nA new Fair Data Exchange protocol that enable a storage server to transfer a data file to a client atomically\n\nresearch\ncryptography\ndanksharding\ndata availability\n\n03.04.24 / István András Seres, Noemi Glaeser and Joseph Bonneau\nNew paper alert: Naysayer proofs\nA new cryptographic scheme where any observer can check a proof off-chain and submit a proof of its incorrectness\n\nresearch\ncryptography\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":6918,"crawled_at":1791193000690}
+{"id":10173,"url":"https://gov.optimism.io/tag/season-5/66","domain":"gov.optimism.io","chapter":"governance_daos","title":"Topics tagged season-5","text":"season-5\n\nTopic\n\nReplies\nViews\nActivity\n\n[grant update] Optimistic Builder Dollar (obUSD)\n\nGrants Updates\n\nseason-5\n\n10\n\n493\n\nMay 16, 2025\n\nSuperscan: New explorer for the Superchain by Walnut\n\nUpdates and Announcements 📢\n\nseason-5\n,\ncycle-19\n\n0\n\n157\n\nApril 25, 2025\n\nOP Passport | Design Document\n\n✨ General\n\nseason-5\n\n6\n\n782\n\nMarch 31, 2025\n\nDeVouch (Decentralized Vouching with Attestations) - Mission Grant - Project Updates\n\nGrant Updates\n\nseason-5\n\n6\n\n760\n\nMarch 6, 2025\n\nGDWeb3 - Builder Grant Update (Seaon 5, Cycle 22)\n\nUpdates and Announcements 📢\n\nseason-5\n,\ncycle-22\n\n0\n\n74\n\nFebruary 21, 2025\n\nS5 grantee: x23.ai - governance summariser + chatbot\n\nGovernance Fund Missions\n\nseason-5\n\n5\n\n439\n\nFebruary 12, 2025\n\n[grant update] Glo Dollar upgrade to funding RetroPGF Retrospective Report\n\nGovernance Fund Missions\n\nseason-5\n\n0\n\n181\n\nFebruary 3, 2025\n\nEnsuring Security with OP Superchain\n\n✨ General\n\nseason-3\n,\ncycle-10\n,\ncycle-11\n,\nseason-4\n,\nseason-5\n\n0\n\n341\n\nJanuary 22, 2025\n\nLeveraging Blockchain Technology to Combat Inflation in Bangladesh with Op Superchain\n\n✨ General\n\ncycle-10\n,\ncycle-11\n,\nseason-5\n\n0\n\n49\n\nJanuary 10, 2025\n\nForwarding of RIG's allocated funds to PG\n\nUpdates and Announcements 📢\n\nseason-5\n\n1\n\n70\n\nJanuary 6, 2025\n\nDark Forest ARES: Milestone 4 Submission and request for feedback\n\nUpdates and Announcements 📢\n\nseason-5\n,\ncycle-22\n\n0\n\n73\n\nJanuary 5, 2025\n\n[FINAL] Proposal to Reclassify Grant Misusage Enforcement\n\nTechnical Proposals\n\nseason-5\n,\ncycle-17\n\n8\n\n1415\n\nDecember 12, 2024\n\nNamespace - Builder Grant Update (Season 5, Cycle 19)\n\nUpdates and Announcements 📢\n\nseason-5\n\n8\n\n267\n\nNovember 26, 2024\n\nOPpunks (testing Namespace SDK)\n\nGrant Updates\n\nseason-5\n\n1\n\n75\n\nNovember 21, 2024\n\nTribuni Alpha Launch: Telegram Mini-app Built by Delegates for Delegates\n\nDelegates 🏛\n\nseason-5\n,\ncycle-22\n\n14\n\n730\n\nNovember 19, 2024\n\nDeveloper Advisory Board\n\nElections 💼\n\nseason-5\n\n11\n\n7738\n\nJune 3, 2024\n\nDark Forest ARES: Milestone 3 Submission and request for feedback\n\nUpdates and Announcements 📢\n\nseason-5\n,\ncycle-22\n\n0\n\n75\n\nNovember 3, 2024\n\nAt this point it is just a fact that OP hates my wallet\n\n✨ General\n\nseason-5\n\n23\n\n564\n\nOctober 17, 2024\n\nBuilding an On-Chain Review System with EAS\n\nGovernance Fund Missions\n\ngrant-update\n,\nseason-5\n\n5\n\n395\n\nOctober 7, 2024\n\nNew Explorer for the OP Stack: Milestone 3 submission and request for feedback\n\nUpdates and Announcements 📢\n\nseason-5\n,\ncycle-19\n\n2\n\n154\n\nSeptember 26, 2024\n\nCosta Rica OP DAY\n\nCommunity Calls\n\nseason-5\n\n33\n\n1780\n\nSeptember 10, 2024\n\nDark Forest ARES: Milestone 2 Submission and request for feedback\n\nUpdates and Announcements 📢\n\nseason-5\n,\ncycle-22\n\n3\n\n116\n\nSeptember 7, 2024\n\nIntroducing the Collective Feedback Commission\n\nMetagovernance\n\nseason-5\n\n8\n\n2370\n\nAugust 21, 2024\n\nNew Explorer for the OP Stack: Milestone 2 submission and request for feedback\n\nUpdates and Announcements 📢\n\nseason-5\n,\ncycle-19\n\n0\n\n93\n\nJuly 24, 2024\n\nDark Forest ARES: Milestone 1 Submission and request for feedback\n\nUpdates and Announcements 📢\n\nseason-5\n,\ncycle-22\n\n2\n\n201\n\nJuly 9, 2024\n\nNew Explorer for the OP Stack: Milestone 1 submission and request for feedback\n\nUpdates and Announcements 📢\n\nseason-5\n,\ncycle-19\n\n2\n\n332\n\nJuly 5, 2024\n\nCode of Conduct Councils\n\nMetagovernance\n\nseason-5\n\n17\n\n3200\n\nJune 9, 2024\n\nHow is blockchain being appllied in supply chain management and logistics?\n\n✨ General\n\nseason-5\n\n0\n\n257\n\nMay 30, 2024\n\nGrants Season 5, Round 2 — Data Analysis\n\nAccountability 🗂️\n\nseason-5\n\n2\n\n672\n\nMay 22, 2024\n\nCycle 22 Final Grants roundup\n\nGrants Updates\n\nseason-5\n,\ncycle-22\n\n24\n\n6575\n\nMay 14, 2024\n\nnext page →","tokens":907,"crawled_at":1791193008834}
+{"id":10174,"url":"https://docs.near.org/data-infrastructure/what-is","domain":"docs.near.org","chapter":"layer1_layer2","title":"What is Data Infrastructure? - NEAR Docs","text":"NEAR offers ready-to-use solutions to access and monitor on-chain data easily. This is very useful to automate actions based on specific events, cache data to reduce latency, gather usage data of the blockchain, and even study user preferences.\n\nIn NEAR you will find three main solutions to access and monitor on-chain data: Data APIs, BigQuery Public Dataset and NEAR Lake. Each of these solutions is designed to fit different needs and use cases, and can be used in combination to create a complete data infrastructure for your application.\n\n​\n\nData APIs\n\nMembers of the NEAR community have built a set of APIs to access and monitor on-chain data. These APIs are designed to be easy to use and can be accessed from any application through a simple API call.\n\nUser assets: Easily track all the assets that a user or a contract holds\n\nMonitor transactions: Get all the transactions of a user, a contract or a specific token\n\nTrack on-chain events: Get all the events emitted by a contract, or a specific event type\n\n​\n\nBigQuery: Public Dataset\n\nA large dataset with on-chain data publicly available on Google Cloud Platform. Obtain near real-time blockchain data using simple SQL queries. All the data, zero setup.\n\nInstant insights: Historic on-chain data queried at scale. No need to run your own infrastructure.\n\nCost-effective: Eliminate the need to store and process bulk NEAR Protocol data. Query as little or as much data as you like.\n\nAs easy as SQL: No prior experience with blockchain technology is required. Just bring a general knowledge of SQL to unlock insights.\n\n​\n\nNEAR Lake\n\nDeprecated as of March 24, 2026. NEAR Lake (AWS S3 buckets) has stopped indexing new blocks. For new projects, use Neardata (direct replacement), Data APIs, Goldsky, or the Nearcore Indexer.\n\nA solution that watches over the NEAR network and stores all the events for your easy access.\n\nCost-efficient solution: Cost-efficient solution for building self-hosted indexers in Rust, JavaScript, Python, Go and other languages\n\nStreamlined data management: Use NEAR Lake Framework to stream blocks to your server directly from NEAR Lake\n\n​\n\nConclusion\n\nData infrastructure is a key component of any blockchain application. It allows developers to access and monitor on-chain data easily, which is essential for building applications that interact with the blockchain.\nNEAR offers a range of solutions to help developers build robust data infrastructure for their applications, including Data APIs, BigQuery Public Dataset, and NEAR Lake. By using these solutions in combination, developers can create a complete data infrastructure that meets their specific needs and use cases.\nWas this page helpful?","tokens":673,"crawled_at":1791193030151}
+{"id":10175,"url":"https://stack.olas.network/open-autonomy/key_concepts/fsm_app_introduction","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Introduction to FSM Apps - Olas Stack Developer Documentation","text":"Introduction to FSM Apps\n\nDeparting from the notions of AEA, FSM, and ABCI, we are now in position to describe in more detail what an FSM App is.\n\nDefinition of an FSM App\n\nAn FSM App is a replicated application which uses\nan underlying consensus engine implementing the ABCI.\nIts internal state takes the form of an FSM, and it exhibits proactive behaviours in each of such states.\nFSM Apps constitute a core part in the Open Autonomy framework to implement AI agent.\n\nThe figure below depicts an sketch of the internal workings of an FSM App, composed of six states (A-F) and six events (1-6):\n\nDiagram of a Valory stack FSM\n\nNote that in an FSM App, the responsibility of a state is distributed across two components, as it can be seen in the \"zoomed\" State C above:\n\nA round is the component that defines the rules to transition across different\nstates. It is a concrete implementation of the AbstractRound class. It usually involves\ninteractions between participants, although this is not enforced\nat this level of abstraction. A round can validate, store and aggregate data\ncoming from different agent instances by means of transactions. The actual meaning of\nthe data depends on the implementation of the specific round. This component\nproduces the Events that will enable the FSM transit from one state to another, that is, capturing the role of the transition function.\n\nEach round has an associated Behaviour, which is the component that defines the proactive actions to be executed at\na particular state. It is a concrete implementation of the BaseBehaviour class, and contains the application logic for each state. It is scheduled for\nexecution by the agent instances.\n\nWe will sometimes use indistinctly the terms \"state\" or \"round\" in the context of the Open Autonomy framework. We also define the concept of synchronized data, which is the component that stores persistent data and is accessible from any state. The consensus mechanism ensures that the synchronized data is consistently shared by all the agent instances. It is updated at the end of each round, where its contents can be updated. It is a concrete implementation of the BaseSynchronizedData class.\n\nThe framework defines a concept of \"period\" for the SynchronizedData. When a new period starts, the SynchronizedData allocates a new slot to store new values for the variables stored within it. This way, the developer has access to the historic values that the FSM App has stored (which can be pruned out). New periods are automatically created for the SynchronizedData when an FSM App traverses the ResetAndPauseRound inside Reset and pause.\n\nDue to the variety of FSMs that can be defined, the framework does not enforce that an FSM App use the period concept, however, it is expected that any production worthy FSM App defines it, as it ensures the SynchronizedData does not grow in an unbounded fashion.\n\nNote\n\nA round/state might just be a stage in\nthe overall flow of the application (e.g., waiting that a sufficient number of participants commit their\nobservations to a temporary blockchain), or a voting round (e.g.,\nwaiting until at least an observed value has reached ⌈(2N+1)/3⌉ of the votes).\n\nThe developer could define the concept of \"period\" for their FSM as the sequence of stages in the FSM state flow that achieve a specific objective defined by the FSM App. For example, consider an AI agent that aggregates observations from different data sources and submits the aggregated result to an L1/L2 blockchain. In this example, the developer could define a period as follows:\n\nCollect observations from external APIs or prior rounds.\n\nReach consensus on the set of collected observations (i.e., 2/3 of the agent instances must agree).\n\nCompute a function (e.g., mean) on the set of collected observations, and reach consensus on the computed result.\n\nConstruct a transaction that contains the aggregated result.\n\nSign the transaction (2/3 of the agent instances must agree to sign).\n\nA single agent instance, randomly nominated as the keeper, sends the transaction to the chain. If it does not do this before a\ntimeout event occurs, another agent instance is selected to be the\nkeeper.\n\nGo to Step 1.\n\nComposition of FSM Apps\n\nOne of the key features of the Open Autonomy framework is the generation of FSM Apps whose internal FSM is a composition of different FSMs. The composition mechanism facilitates\nrapid development of complex applications, by reusing FSMs already developed for other FSM Apps, obtaining the aggregated functionality.\n\nDeparting from a collection of FSMs, say FSM1, FSM2, ..., FSMn, a composed FSM can be constructed following certain rules:\n\nwhen composing FSMs, an FSMi can only transit from a final state to a start state of another FSMj, and\n\na given FSM can only be used once in a composition.\n\nWe call FSM composition mapping the mapping that indicates how to move from one FSM to another.\nFor every entry in the FSM composition mapping, e.g., from a final state Z from FSM1 to a start state A from FSM2, the composition mechanism will enforce that all the transitions ending in the final state Z of FSM1 be redirected to the start state A of FSM2. See an example below.\n\nHow the FSM composition process works\n\nThe figure above depicts an excerpt of a composition of three FSMs into a single one. Note how the finish states of FSM1 are linked to start states of FSM2 and FSM3. We remark that the transitions indicated by the FSM composition mapping are not regular transitions that respond to events, rather they are merely a construct to indicate how the states in the composed FSM are connected.\n\nImportant\n\nThe result of a composition of a collection of FSMs is an FSM whose set of spaces is a subset of the union of state spaces of the constituent FSMs. For this reason is it not possible to \"reuse\" a given FSM twice in a composition. All the final states of the constituent FSMs that are defined in the transition mapping will be removed, as exemplified in the figure above.\n\nTherefore, althought it might be useful and intuitive thinking of a composed FSM in terms of its constituent FSMs, the structure is not retained internally by the FSM App. For example, consider the following setting:\n\nFSM composition with two sources\n\nNote that in the composed FSM, when transitioning to A3, the FSM loses track of what was the FSM from which it transitioned (either FSM1 or FSM2). Nevertheless, if the business logic in state A3 requires knowledge of what was the history of visited states before reaching it (e.g., in order to execute a different action), the developer has access to that history through the field _previous_rounds from the class AbciApp which will be discussed in a separate section.\n\nConsiderations to Develop FSM Apps\n\nAI agents and their associated FSM Apps must be designed with determinism at their core. For this reason, in each round, agent instances must agree upon their execution outputs in order to make progress. Any source of \"uncontrolled\" randomness or code inconsistency that leads to non-determinism will undermine the FSM App's ability to achieve its goal. Sources of non-determinism include but not limited to:\nNon-verifiable randomness libraries.\n\nNon deterministic libraries, like ML frameworks that do not guarantee exact same results under the same initial conditions.\n\nUsing the agent instance's local time to make decisions along the execution flow. Agent instances synchronize using the consensus engine, and that is the only reliable source of \"time\" that should be used. Sometimes, block timestamp can be a handy property common to all agent instances and can be used as a time.now() equivalent.\n\nUsing local resources that are not synchronized among all agent instances to make decisions.\n\nUsing data serialization, e.g., json.dump without sorting the keys and inputs. Try to work with sorted data structures whenever possible (e.g., sorted lists instead of arbitrary lists).\n\nUsing block metrics in a Behaviour, other than those determining round transitions. All other blocks read from behaviours might involve race conditions.\n\nSometimes it is required to retry interactions with external services. There are generally two ways retries can be implemented: On the behaviour level and on the round level. The default retry should be implemented via round transitions. For instance, when agent instances cannot finish their behaviour level activities because of failure of an external service they can signal this via the payload (e.g., sending an explicit \"None\"). Then at the round level the agent instances can coordinate transition to the next state: either retrying the current state or transitioning to another state. Behaviour level retries should be limited when making calls to external services where the agent instance is the only one retrieving such information. For example, in an oracle AI agent, each agent instance interacts with a different external API and the retries are naturally timed out by the round timeout.\n\nIt is desirable that agent blueprint Skills have their own unit tests. The Open AEA framework offers tools to make easier for developers to write tests for their Skills. Beware that the AEA skill testing framework might have some limitations with respect to idiomatic Python testing. For example, it is a known issue that patching skill module-level components does not work, but only instance-based patching is effective (e.g. using patch.object).\n\nWhen developing agent blueprint, applications raise exceptions for all branches which are currently unhandled and would cause inconsistencies in the app. These exceptions can then be surgically addressed in separate PRs. Example: on the happy path a file is loaded properly, on the unhappy path an exception is raised by the file not being present. In production handling this can get involved. During development it is best to \"park\" this issue and focus on the happy case. But the unhappy case should raise so we can capture its prevalence in tests. Logging is the worst approach as it hides this issue!","tokens":2516,"crawled_at":1791193030972}
+{"id":10176,"url":"https://a16zcrypto.com/team/mahimna-kelkar","domain":"a16zcrypto.com","chapter":"research","title":"Mahimna Kelkar - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nMahimna Kelkar\n\nFeed\nFilter\n(1)\nclear filters\n\ncategory\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\nrecommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nauthor\n(1) all authors\n@x0rart\n1337 Skulls Sers\na16z crypto\na16z crypto editorial\na16z crypto policy & regulatory teams\na16z crypto Regulatory Team\nAaditya Shidham\nAaron Levie\nAaron Phillips\nAaron Schnider\nAbby Green\nAbdou Ndiaye\nAbhi Shelat\nAbhiram Kothapalli\nAbigail Johnson\nAdam Alter\nAdam Back\nAdam Bry\nAdam Grant\nAdam Ludwin\nAdam Martin\nAdam Thierer\nAdam Zuckerman\nAdela Tomsejova\nAdena Friedman\nAdena Hefets\nAdeniyi Abiodun\nAdina Fischer\nAdrian Cockcroft\nAdrian Fenty\nAdrienne Mayor\nAgostino Capponi\nAiden Slavin\nAileen Lee\nAisha Stephenson\nAJ Shankar\nAlan Knott-Craig\nAlan Schaaf\nAlana Benton\nAlbert Tang\nAlec Nielsen\nAlec Ross\nAlejandro Flores\nAlex Constantinople\nAlex Honnold\nAlex Hutchinson\nAlex Immerman\nAlex Kreitz\nAlex Kroeger\nAlex Le\nAlex Masmej\nAlex Morcos\nAlex Price\nAlex Pruden\nAlex Rampell\nAlex Roetter\nAlex Solomon\nAlex Spector\nAlex Stamos\nAlex Tabarrok\nAlexander (Sasha) Spiegelman\nAlexander Chia\nAlexander Zoppa\nAlexandra Chang\nAlexandria Lafci\nAlexis Lakes\nAlexis Madrigal\nAlexis Ohanian\nAli Ghodsi\nAli Yahya\nAlicia Barone\nAlin Tomescu\nAlisha Litman\nAlison Mangiero\nAlison Martin\nAllison Pickens\nAlyssa Del Bene\nAlyssa Torres\nAmanda Cantor\nAmanda Cassatt\nAmanda Catherine\nAmanda Mulay\nAmanda Tuminelli\nAmanda Tyler\nAmelia Salyers\nAmie Tyrrel\nAmir Shevat\nAmira Yahyaoui\nAmy Abernethy\nAmy Berliner\nAmy Bohutinsky\nAmy Choice\nAmy Cray\nAmy Gill\nAmy Hoemeke\nAmy Kalokerinos\nAmy Robertson\nAna Mostarac\nAna Susi\nAnatoly Yakovenko\nAndie Taylor\nAndisheh Tahriri\nAndre Iguodala\nAndrea Clarke Hall\nAndrea Feinberg\nAndrea Rallo\nAndrea Simon\nAndrea Vinkler\nAndreas Papadimitropoulos, Jr\nAndreessen Horowitz\nAndrew Allen\nAndrew Chen\nAndrew F. Read\nAndrew Green\nAndrew Hall\nAndrew Lakis\nAndrew Lewis-Pye\nAndrew Lo\nAndrew Mason\nAndrew McAfee\nAndrew Milson\nAndrew Omori\nAndrew Radin\nAndrew Rubin\nAndrew Savage\nAndrew Smith\nAndrew Tretyakov\nAndy Beal\nAndy Coravos\nAndy Golden\nAndy Hill\nAndy Milenius\nAndy Rachleff\nAndy Tran\nAndy Walshe\nAneel Lakhani\nAngela Schenone\nAngela Strange\nAngela Tran Kingyens\nAngelica Gehr\nAniket Kate\nAnil Sethi\nAnish Acharya\nAnn Winblad\nAnna Berces\nAnna Jablonski\nAnna Semenova\nAnna Van Meurs\nAnnaLee Saxenian\nAnne Brandes\nAnne Lee Skates\nAnne Lewandowski\nAnne Mitchell\nAnne Yip\nAnnie Collins\nAnnie Duke\nAnthony Albanese\nAnthony Atala\nAnthony Foxx\nAnthony Lee Zhang\nAntonio Viggiano\nAntwone Stigall\nAnu Hariharan\nApril Roth\nAri Emanuel\nAri Juels\nArianna Huffington\nArianna Simpson\nArik Kershenbaum\nArmon Dadgar\nArnie Goldberg\nArsho Avetian\nArthur Brooks\nArun Sundararajan\nAsh Ashutosh\nAsha Christian\nAshley McCollum\nAshley Stern\nAshton Carter\nAtif Mian\nAtul Butte\nAubree Pelaez\nAubrey de Grey\nAugusto Marietti\nAurora Petracca\nAusten Allred\nAustin Guzman\nAustin Marchese\nAustin Wilson\nAva Iravani\nAvery Segal\nAvinash Solanky\nAviv Zohar\nAye Moah\nAzeem Azhar\nBailey Flanigan\nBailey Richardson\nBalaji Srinivasan\nBarry McCarthy\nBart Dessaint\nBeau Cronin\nBeau Woods\nBecky Pferdehirt\nBen Buckwalter\nBen Fielding\nBen Fisch\nBen Gardner\nBen Gomez\nBen Horowitz\nBen Kaufman\nBen Leventhal\nBen Lovell\nBen Napier\nBen Portney\nBen Rubin\nBen Scharfstein\nBen Schecter\nBen Silbermann\nBen Uretsky\nBen Wu\nBenedict Evans\nBenedikt Büenz\nBenjamin Ebner\nBenjamin Hindman\nBenjamin Wittes\nBenjamin Wu\nBennett Carroccio\nBenny Pinkas\nBernard J. Tyson\nBernard Tyson\nBeth Newman\nBethany Coates\nBharat Ramamurti\nBharath Ramsundar\nBill Carr\nBill Frist\nBill Hinman\nBill Janeway\nBill Krause\nBill Macaitis\nBlake Kim\nBlake Masters\nBlake Saari\nBlayne Donnell\nBob Iger\nBob Langer\nBob Moore\nBob Muglia\nBob Sutton\nBob Swan\nBob Tinker\nBob Wachter\nBobby Franklin\nBobby Green\nBobby Kotick\nBobby Wagner\nBoris Sofman\nBoris Wertz\nBrad Feld\nBrad Kern\nBrad Peterson\nBram Cohen\nBrandon Ballinger\nBrandon Barros\nBrandon Cherry\nBrandon Millman\nBrenda Kopf\nBrent McIntosh\nBrett Browman\nBrett Falk\nBrett Hagler\nBrewster Kahle\nBrian Armstrong\nBrian Balfour\nBrian Brooks\nBrian Crnkovich\nBrian Curran\nBrian Grazer\nBrian Koppelman\nBrian McCullough\nBrian Quintenz\nBrian Wilkins\nBridget McDowell\nBrittany Lucas\nBrittney Burrows\nBrooke Sheresky\nBruce Friedrich\nBryan Caplan\nBryan Chiang\nBryan Cox\nBryan Crowley\nBryan Faust\nBryan Houser\nBryan Kim\nBryan Pellegrino\nCaitlin Glazebrook\nCaitlin Johnston\nCaitlin Roberson\nCal Turner Jr.\nCaleb Christian\nCameron Schuler\nCamila De Souza\nCarine Carmy\nCarissa Bilinski\nCarl Agnelli\nCarl Eschenbach\nCarl Narcisse\nCarl Pope\nCarlos Araya\nCarolina Gonzalez\nCaroline Friedman\nCaroline Goggins\nCaroline Horn\nCaroline Moon\nCarolyn Bertozzi\nCarra Wu\nCasey Graul\nCasey Neistat\nCasey Winters\nCassady Churchill\nCassie Faerber\nCecilia Marshall\nCeia Font\nChad Rigetti\nChandra Krintz\nCharles Goetz\nCharles Hubbard\nCharles Koch\nCharlie Keinath\nCharlie Warzel\nChattry Meas\nChelsea Komlo\nChelsea Padilla\nCheng Li\nChris Bennett\nChris Best\nChris Burniske\nChris Curran\nChris DeWolfe\nChris Dixon\nChris Granger\nChris Hauth\nChris Lyons\nChris Messina\nChris Milk\nChris Power\nChris Santa Maria\nChris Wanstrath\nChristian Cachin\nChristian Catalini\nChristian Crowley\nChristian Seifert\nChristina Hampp\nChristina Lopes\nChristina Mercando\nChristina Xu\nChristina Zeidan\nChristine Darden\nChristine Perham\nChristopher Giancarlo\nChristopher Lee\nChristopher Mims\nChristopher Nguyen\nChristopher Rippingham\nChristopher Schroeder\nChristy Hubbard\nCiamac Moallemi\nCindi Zhang\nCindy Tenner\nClaire Austin\nClaire Cain Miller\nClaire Kart\nClaudia Picanco\nClay Shirky\nClayton Christensen\nClayton Gardner\nClifford Woolf\nClint Delapaz\nColin Bryar\nColin Rom\nCollin McCune\nConner Lyons Brown\nConnie Chan\nConnie Guglielmo\nConnor McCarthy\nConnor Moyles\nCorban Bell\nCorey Hawkins\nCorey Waller\nCourtney Dettlinger\nCraig Naylor\nCraig Walker\nCristina Cordova\nCurt Funderburk\nCuy Sheffield\nD'Arcy Coolican\nDaejun Park\nDaisy Linden\nDaisy Wolf\nDaljeet Virdi\nDalton Turay\nDan Berkenstock\nDan Boneh\nDan Frommer\nDan Primack\nDan Romero\nDan Shapero\nDan Siroker\nDan Stein\nDan Warmenhoven\nDan Wendlandt\nDaniel Chao\nDaniel Chen\nDanielle Andrzejewski\nDanielle Clark\nDanielle Looymans\nDanielle Lussier\nDanielle Morrill\nDanielle Shea\nDanny Shader\nDaphne Koller\nDapper Dan\nDaren Matsuoka\nDarin Malter\nDarshan Shankar\nDas Rush\nDave Jagoda\nDave King\nDave Touretzky\nDavid Banks\nDavid Belden\nDavid Damato\nDavid Deming\nDavid George\nDavid Haber\nDavid Hollestelle\nDavid Kerr\nDavid Lee\nDavid Mack\nDavid Madden\nDavid Marcus\nDavid Olson\nDavid Oyelowo\nDavid Pierce\nDavid Reich\nDavid Rumsey\nDavid Schweikert\nDavid Sinclair\nDavid Sverdlov\nDavid Tse\nDavid Ulevitch\nDavid Weiden\nDawn Lepore\nDawn Nott\nDeborah Embaie\nDeena Elitreby\nDeepak Maram\nDenis Nazarov\nDenis Young\nDenise Gonzalez\nDerek Dolin\nDerek Thompson\nDerrick Harris\nDevin Finzer\nDevon Zuegel\nDiana Peña\nDiane Greene\nDick Costolo\nDieter Shirley\nDiishan Imira\nDiogo Monica\nDominic Shine\nDominique Reliford\nDon Duet\nDon Faul\nDorris O'Brien\nDoug Ducey\nDoug Folden\nDoug McCracken\nDouglas Argueta\nDozie Uche\nDrew Coffman\nDylan Field\nDylan Rhodes\nEd Felten\nEd Lynch\nEddie Lim\nEddy Lazzarin\nEdith Zimmerman\nEdward Perkins\nEdwin Poston\nEfrat Noy\nEhud Shapiro\nEileen Burbidge\nEileen Wu\nElad Gil\nElaine Fuchs\nElaine Shi\nElena Burger\nEli Dourado\nElisa Leonhardt\nEliza Oak\nElizabeth Gunn\nElizabeth Harkavy\nElizabeth May\nElizabeth Ocken\nElizabeth Stark\nElizabeth Weil\nEllen Tunoa\nEmile Petrone\nEmilio Torres\nEmily Graff\nEmily Hinsch\nEmily Keir\nEmily Oster\nEmily Westerhold\nEmma Janaskie\nEric Budish\nEric Dai\nEric Ries\nEric Thomas\nEric Topol\nEric Wu\nErica Schecter\nErik Brynjolfsson\nErik Kiser\nErik Torenberg\nErika Bracken\nErika Herrera\nErika Louie\nErin Grody Kingsley\nErin Murphy\nErin Tice\nErin Tonnar\nErin Winkler\nErtem Nusret Tas\nEsther Shinn\nEthan Bueno de Mesquita\nEthan Ferreira\nEthan Zuckerman\nEuan Ashley\nEugene Volokh\nEugene Wei\nEugenia Yee\nEula Takahashi\nEva Sakkas\nEvan Burfield\nEvan Osnos\nEvangelos Simoudis\nEzra Klein\nF. Gary Gray\nFabiola Godinez\nFabrizio Zilibotti\nFahad Saleh\nFarid Jiandani\nFei-Fei Li\nFelix Do\nFEWOCIOUS\nFiona Kennedy\nFiona Murray\nFlashrekt\nFlora Oliveira\nFlori Del Valle\nFlorian Leibert\nFoteini Baldimtsi\nFrancesca Gino\nFrank Chen\nFrank Wilczek\nFred Benenson\nFred Ehrsam\nFred Upton\nFred Wilson\nFreda Lewis-Hall\nFrederic Kerrest\nFuture Editorial\nGabby Dizon\nGabby Reece\nGabriel Otte\nGabriel Vasquez\nGaetan Barthelemy\nGarrett Biel\nGary Ang\nGary Reedy\nGary Wolf\nGaurav Banga\nGaurav Dhillon\nGaut\nGayle Tzemach Lemmon\nGeoffrey Woo\nGeorg Fuchsbauer\nGeorg Petschnigg\nGeorge Church\nGeorge Danezis\nGeorge Fraser\nGeraldine Chan\nGérard Cachon\nGerard Ryle\nGerri Elliott\nGerry Tsoukalas\nGia Scinto\nGil Elbaz\nGil Shafir\nGina Moon\nGina Neff\nGina Yocom\nGinger Liau\nGokul Rajaram\nGoldie Chang\nGrace Ellis\nGraham Allison\nGrant Gregory\nGrant Jordan\nGrant LaFontaine\nGrant Rabenn\nGray Kinsella\nGreg Bowman\nGreg Clayman\nGreg Linares\nGreg Loehmann\nGreg Lynn\nGreg Solano\nGreg Truesdell\nGreg Waldon\nGregory Allen\nGregory Mundis\nGretchen Bush\nGretchen McCulloch\nGuido Appenzeller\nGustav Söderström\nGustavo Garcia\nGuy Goren\nGuy Raz\nGuy Wuollet\nHaley Van Dyck\nHanna Aziz\nHannah Frankl\nHanne Winarsky\nHaoyuan Li\nHarmit Malik\nHarry Grieve\nHarry Shum\nHarry Wright\nHatim Shafique\nHayden Adams\nHeather Gwynn\nHeather Podesta\nHedi Samar\nHelen Stoddard\nHelen Su\nHemant Mohapatra\nHendrik Pretorius\nHenri Kor\nHerb Lin\nHerman Narula\nHilmar Pétursson\nHoang Nguyen\nHoward Wu\nIan Dutra\nIan Shannon\nIan Sharp\nIce Cube\nIlan Zechory\nIllia Polosukhin\nIlyas Khan\nIma Christian\nIman Abuzeid\nInsiya Lokhandwala\nIon Stoica\nIrvin Chan\nIsa Guardalabene\nIsaiah Lott\nIsh Verduzco\nIsil Dillig\nIstván András Seres\nIttai Abraham\nIttay Eyal\nIva Messy\nIvan Linscott\nIvor Horn\nJ.D. Moriarty\nJack Donahoe\nJack Soslow\nJackie McQuiston\nJackson David\nJacob Westphal\nJacquelyn Melinek\nJad Esber\nJad Naous\nJade Lai\nJade Raymond\nJae Gnazzo\nJai Ramaswamy\nJaimie Buss\nJak Kennedy\nJake Auchincloss\nJakob Uszkoreit\nJamal Mohammed\nJames Beshara\nJames Currier\nJames da Costa\nJames Gwertzman\nJames J. Collins\nJames Kissell\nJames L. Madara\nJames Loftus\nJames Rathmell\nJames Rogers\nJames Watters\nJames Wu\nJames Zou\nJamie Brandon\nJamie McGurk\nJamie Sullivan\nJamilla Hemeid\nJana Odehnal\nJane Doe\nJane Lippencott\nJane Suh\nJanelle De Los Santos\nJared Bricklin\nJared Furutani\nJared Georgakopoulos\nJared Polis\nJared Smith\nJase Wilson\nJason Franklin\nJason Liu\nJason Mayden\nJason Milionis\nJason Mitchell\nJason Mok\nJason Rosenthal\nJason Warner\nJason Yanowitz\nJay Bradner\nJay Conte\nJay Drain\nJay Komarneni\nJay Rughani\nJean Reilly\nJeanne Tsan\nJeff Amico\nJeff Benson\nJeff Clark\nJeff Cordova\nJeff Glueck\nJeff Hawkins\nJeff Jones\nJeff Jordan\nJeff Lawson\nJeff Lu\nJeff Nagashima\nJeff Stump\nJeff Weiner\nJeffrey Immelt\nJeffrey Kaditz\nJeffrey Katzenberg\nJeffrey Kindler\nJeffrey Low\nJeffrey Silverstein\nJeffrey Zirlin\nJen Bulawsky\nJen Kha\nJenna Walsh\nJenna Zucker\nJennifer 8. Lee\nJennifer Doudna\nJennifer Kodner\nJennifer Konde\nJennifer Li\nJennifer Mumford\nJennifer Tejada\nJennifer Young\nJenny Cieplak\nJens Ernstberger\nJensen Harris\nJeremy Clark\nJeremy England\nJeremy Zhang\nJesse Holmes\nJesse Pollak\nJesse Walden\nJessica Childs\nJessica Hansen\nJessica Keeler\nJessica Patton\nJessica Verrilli\nJewel Pi\nJez Humble\nJi Kim\nJianying Luo\nJim Gilliam\nJimmy Chen\nJimmy Soni\nJing Wang\nJing Zou\nJJ Yu\nJoachim Neu\nJodi Lynn\nJodie Lutkenhaus\nJoe Gebbia\nJoe Grundfest\nJoe Montana\nJoe Morrissey\nJoe Schmidt\nJoe Sullivan\nJoel de la Garza\nJoel Mokyr\nJoel Monegro\nJoel Spolsky\nJoey Burleson\nJohn China\nJohn Collison\nJohn Fawcett\nJohn Garcia\nJohn Gedmark\nJohn Hennessy\nJohn Koelliker\nJohn M. Jack\nJohn Markoff\nJohn Menna\nJohn O’Farrell\nJohn Riccitiello\nJohn Smesko\nJohn Stanfield\nJohn Thompson\nJohn William Hatfield\nJonah Peretti\nJonathan Bush\nJonathan Dotan\nJonathan Downey\nJonathan Lai\nJonathan Lim\nJonathan Lusthaus\nJonathan Weissman\nJonathan Wong\nJordan Mazer\nJordan Stankowski\nJorge Conde\nJorge Gomez\nJose Guardado\nJoseph Bonneau\nJoseph Okpaku\nJoseph Spisak\nJosh Arnold\nJosh Bloom\nJosh Kim\nJosh Williams\nJoshua Browder\nJoshua Gans\nJoshua Grimm\nJoshua Hix\nJoshua Levin\nJoshua Lu\nJoshua Schank\nJoshua Soto\nJosie Ma\nJoyce Park\nJR Rivers\nJT Evans\nJuan Benet\nJudene Small\nJudy Savitskaya\nJudy Smith\nJulia Grace\nJulia Kirby\nJulie Bornstein\nJulie Farnham\nJulie Johnson\nJulie Samuels\nJulie Yoo\nJuliet Grier\nJuliet Nyatta\nJuliette Morton\nJulius Zhang\nJustin Bailey\nJustin Bethune\nJustin Blau\nJustin Cunningham\nJustin Gregorius\nJustin Kahl\nJustin Kan\nJustin Larkin\nJustin Paine\nJustin Pettit\nJustin Roberts\nJustin Simcock\nJustin Thaler\nJustine Moore\nJutta Steiner\nJyoti Bansal\nJZ Young\nKabir Gill\nKabir Laroia\nKais Khimji\nKamala Harris\nKaren Dunn\nKaren Wooley\nKarina Sobieski\nKarl Floersch\nkarma (Daniel Reynaud)\nKarmacoma\nKarthik Rau\nKartik Nayak\nKate Darling\nKate Dellolio\nKate Kerames\nKatherine Boyle\nKatherine Minarik\nKatherine Rundell\nKatherine Schoebel\nKathryn McKinley\nKathy Liu\nKathy Yang\nKatia Ameri\nKatie Baynes\nKatie Haun\nKatie Hemmerling\nKaty DeWitt-Drew\nKaty Nelson\nKayvon Tehranian\nKeener Barnhorst\nKeller Medlin\nKeller Rinaudo\nKelly Cannon\nKelsey Chaplinsky\nKelsey Mellard\nKen Chong\nKen Coleman\nKen Kocienda\nKerry Ganim\nKesha Cash\nKevin Chou\nKevin Chu\nKevin Dulsky\nKevin Kelly\nKevin McKinley\nKevin Nishioka\nKevin O'Kane\nKevin Rose\nKevin Tan\nKevin Wu\nKevin Zollman\nKidSuper\nKieran Snyder\nKierston Gittens\nKiki Mavridis\nKim Enright\nKim Malone Scott\nKim Milosevich\nKim Stevenson\nKim Zetter\nKimberly Tan\nKindra Mason\nKira Poskanzer\nKira Song\nKirstin Arbide\nKirt McMaster\nKofi Ampadu\nKouki Harasaki\nKrista Anderson-Copperman\nKristen Fortney\nKristen Johansson\nKristen Kee\nKristin Sauchak\nKristin Thayer\nKristina Graci-deLuna\nKristina Shen\nKristine Lipscomb\nKristo Käärmann\nKrisztina Holly\nKunal Bahl\nKunle Olukotun\nKurt House\nKyle Russell\nLaird Hamilton\nLatasha\nLaura Arrillaga-Andreessen\nLaura Baller\nLaura Behrens Wu\nLaura Deming\nLaura Gravley\nLaura Johnson\nLaura Shores\nLaura Weidman Powers\nLauren Berson\nLauren Illovsky\nLauren Murrow\nLauren Richardson\nLauren Spragge\nLaurene Powell Jobs\nLawrence Levy\nLawrence Summers\nLeah Cassidy\nLee Kleinman\nLee Lefkowitz\nLeeAnn Caballero\nLeila Hay\nLeila Janah\nLenny Rachitsky\nLeslie Jaw\nLeslie Vosshall\nLester Chen\nLi Fan\nLi Fei-Fei\nLi Jin\nLiang Wu\nLilian King\nLily Liu\nLina Sergie Attar\nLinda Banuelos\nLinda Xie\nLinden Tibbets\nLing Ren\nLinlin Li\nLinxin Wen\nLioba Heimbach\nLisa Hawke\nLisa Lambert\nLisa Orr\nLisa Reilly\nLisa Rosano\nLizzy Anderson\nLJ Erwin\nLloyd Dean\nLoretta Sanchez\nLori Potter\nLuca Prosperi\nLuca Zanolini\nLuis Martinez\nLuis von Ahn\nLuke Wroblewski\nLydia Green\nLynda Gibson\nLynn Rudolph\nMadan Nagaldinne\nMaddison Masaeli\nMadeline Lancaster\nMaggie Hsu\nMaggie Leung\nMaggie Romero\nMahad Abedin\nMahesh Iyer\nMahesh Vellanki\nMahimna Kelkar\nMakiri Duckett\nMalinka Walaliyadde\nMallesh M. Pai\nMalloy Evans\nManas Punhani\nManny Luna\nMarc Andreessen\nMarc Andrusko\nMarc Benioff\nMarc Levinson\nMarci Barbera\nMarco Reuter\nMargaret Jen\nMargit Wennmachers\nMaria LaMagna Morales\nMarian Garvin\nMarianne Winkler\nMariano Sorgente\nMaricarmen Alvarez\nMariel Goldenstein\nMarigold Vu\nMarina Kusserow\nMario Gabriele\nMario Linares\nMarissa Bramlett\nMark Cranney\nMark Leslie\nMark McAndrew\nMark McClusky\nMárk Melczer\nMark Moore\nMark Regan\nMark Sendak\nMarkos Georghiades\nMarkus Covert\nMarkus Funk\nMartha Lane Fox\nMartin Casado\nMartin Fischer\nMarty Makary\nMarvin Ammori\nMarvin Zamora\nMary Pat Jordan\nMary-Catherine Lader\nMaryam Bahrani\nMason Hall\nMatei Zaharia\nMatt Abrahams\nMatt Billmann\nMatt Bornstein\nMatt Clifford\nMatt Flannery\nMatt Fleming\nMatt Gleason\nMatt Kaeberlein\nMatt Levine\nMatt Levy\nMatt Oberhardt\nMatt Shortal\nMatt Spence\nMatt Weinberg\nMatthew Colford\nMatthew Green\nMatthew Haughey\nMatthew McCullough\nMatthew Mills\nMatthew Olsen\nMatthew Rutter\nMatthew Stein\nMatthieu Hafemeister\nMaureen Lara\nMax Kesten\nMax Krohn\nMax Levchin\nMax Polyak\nMax Resnick\nMax Ventilla\nMaya Rahkonen\nMcPherson Moore\nMeaghan Hardy\nMeg Whitman\nMegan Holston-Alexander\nMegan Kristalyn\nMehdi Hasan\nMehul Mehta\nMel Williams\nMelanie Galang\nMelissa Liao\nMelissa Minor\nMelissa Wasser\nMellody Hobson\nMelody Latronico\nMeredith Donahue\nMia Gonzalez\nMia Mandich\nMicah Johnson\nMichael Beckerman\nMichael Blau\nMichael Brandt\nMichael Chan\nMichael Copeland\nMichael Dearing\nMichael Dell\nMichael Franklin\nMichael Garcia\nMichael J. Casey\nMichael J. Freedman\nMichael Killam\nMichael King\nMichael Lee\nMichael Leiter\nMichael Morell\nMichael Ostrovsky\nMichael Ovitz\nMichael Paulus\nMichael Raynor\nMichael Reed\nMichael Snyder\nMichael Temkin\nMichael Wee\nMichael Zhu\nMichel Del Buono\nMichel Feaster\nMichèle Flournoy\nMichele Griffin\nMichele Korver\nMichele Law\nMichelle Ervin\nMichelle Kelso\nMichelle Kung\nMichelle Mundy\nMichelle Shin\nMichelle Ufford\nMichelle Volz\nMichelle Wilson\nMichelle Winn\nMichelle You\nMike Curtis\nMike Haydon\nMike Hearn\nMike Jones\nMike Kasperzak\nMike Kelly\nMike King\nMike Lempres\nMike Manning\nMike Maples jr\nMike Masnick\nMike Matchett\nMike Paulus\nMike Sandwick\nMikeal Rogers\nMikey Dickerson\nMiles Jennings\nMilijana Curic\nMiller Whitehouse-Levine\nMinerva Munoz\nMinnie Ingersoll\nMinsun Pak\nMintu Turakhia\nMiranda Christ\nMo Shaikh\nMohammad Akbarpour\nMohsen Malayeri\nMolly Grace\nMonique McCambridge\nMorgan Beller\nMorgan Bender\nMurat Pak\nMuriel Bowser\nMurray Shanahan\nMy Pham\nNadia Asparouhova\nNadia Eghbal\nNaftali Harris\nNaithan Jones\nNanjira Sambuli\nNaomi Metzger\nNashid Braswell\nNassim Eddequiouaq\nNat Barling\nNatacha Crooks\nNatalia Carrera\nNatalie Bucher\nNatalie Taumoepeau\nNate Chang\nNate Lau\nNathalie Balaban\nNathan McCauley\nNathan Yoon\nNathaniel Gleicher\nNathaniel Popper\nNav Singh\nNazanin Daneshvar\nNeel Maitra\nNeha Narula\nNelson Perla-Ward\nNeveen Bader\nNicholas Christakis\nNicholas Pacilio\nNick Babaian\nNick McKeown\nNick Quah\nNick Tomaino\nNicki Locker\nNicole Conner\nNicole Forsgren\nNicole Irvin\nNicole Neuman\nNicole Stanners\nNiels Provos\nNigel Robinson\nNikhil Krishnan\nNina Suthers\nNir Eyal\nNitasha Tiku\nNitin Natarajan\nNitya Subramanian\nNkiru Balonwu\nNoah Citron\nNoah Feldman\nNoah Levine\nNoah Smith\nNoam Nisan\nNoemi Glaeser\nO’Shea Jackson Jr.\nOlaf Carlson-Wee\nOleg Rogynskyy\nOliver Hsu\nOlivia Moore\nOlivia Webb\nOmri Weinstein\nOoshma Garg\nOprah Winfrey\nOrion Hindawi\nOscar Menjivar\nP.J. Hasleton\nPablo Montagnes\nPacky McCormick\nPak\nPalmer Luckey\nPamela Anderson\nPamon Forouhar\nParag Khanna\nParijat Talkad\nParker Brown\nParker Conrad\nPatrice Peck\nPatrick Byrne\nPatrick Collison\nPatrick Conway\nPatrick McCorry\nPatrick McHenry\nPatrick O’Grady\nPatrick Rivera\nPatrick Sutton\nPaul Cafiero\nPaul Daugherty\nPaul Davison\nPaul Krugman\nPaul Vigna\nPaula Long\nPenny Pritzker\nPerri Chilton\nPete Buttigieg\nPeter Blackwood\nPeter Buisseret\nPeter Chan\nPeter Donnelly\nPeter Johnson\nPeter Lauten\nPeter Leeson\nPeter Levine\nPeter Ludwig\nPeter Rubin\nPeter Thiel\nPeter Wang\nPetra Garrett\nPhil Daian\nPhil Hathaway\nPhil Wong\nPhong Nguyen\nPorter Smith\npplpleasr\nPranav Garimidi\nPrasad Akella\nPrat Moghe\nPreethi Kasireddy\npunk6529\nPurnima Padmanabhan\nPyrs Carvolth\nQasar Younis\nQuang Dao\nQuinten Burgunder\nQuintus Kilbourn\nRachael Horwitz\nRachel Goslins\nRachel Jenkins\nRachel Kalmar\nRachel McIntyre\nRachel Steiner\nRahul Iyer\nRahul Vohra\nRajeev Singh\nRajeev Venkayya\nRam Palaniappan\nRamana Jonnala\nRati Gelashvili\nRaul Vazquez\nRavi Parimi\nRay Dalio\nRaymond Carreira\nRebecca Lewis\nRebecca Rettig\nReed Hastings\nRefik Anadol\nRegina Benjamin\nRenato Valdés Olmos\nReshma Saujani\nReshma Sohoni\nRex Salisbury\nRich Ezekiel\nRichard Green\nRichard Menger\nRichard Rosenblatt\nRick Young\nRidhima Ahuja\nRiyaz Faizullabhoy\nRob Goodman\nRob McElhenney\nRob Pardo\nRob Rhinehart\nRobbie Petersen\nRobbie Peterson\nRobert Alexander\nRobert Cottrell\nRobert Hackett\nRobert Kolker\nRobert Leshner\nRobert McNeely\nRobert Moreno\nRobert Siegel\nRobert Stromberg\nRobert Weber\nRobin Casey\nRobin Guo\nRobin Weisman\nRod Johnson\nRodrigo Ibarra Lopez\nRodrigo Pacheco\nRoger Dickey\nRoger Wattenhofer\nRoham Gharegozlou\nRohini Mukand\nRohit Bansal\nRoman Mars\nRoman Stanek\nRon Gill\nRon Lavi\nRon Rothblum\nRonald Evans\nRonnie Harris\nRosa Davila\nRosalind Rattan\nRose Legarda\nRoss Andersen\nRoss Shuel\nRostin Behnam\nRuben Gallego\nRuben Smith\nRuss Altman\nRuss Heddleston\nRuss Roberts\nRussell Davies\nRyan Allen\nRyan Caldbeck\nRyan Conde\nRyan Holloway\nRyan Hoover\nRyan McEntush\nRyan Petersen\nRyan Prescott\nRyan Sandler\nRyan Spoon\nRyan Tseng\nRyan Walsh\nRyan Ward\nRyan Wyatt\nSaar Tochner\nSachin Jain\nSafi Bahcall\nSagar Dhawan\nSaku Panditharatne\nSalem Vance\nSam Blackshear\nSam Broner\nSam Gerstenzang\nSam Ragsdale\nSam Thompson\nSam Williams\nSam Yam\nSamantha Gelt\nSamantha Langford\nSamantha Ludwig\nSamson Wu\nSamuel Arbesman\nSamuel Hammond\nSandra Samayoa\nSandy Jen\nSankaet Pathak\nSantiago Rodriguez\nSara Boesen\nSarah Fazal\nSarah Hamburg\nSarah Lumbard\nSarah Mascardo\nSarah Meiklejohn\nSarah Porter\nSarah Rebello\nSarah Wang\nSasha Stiles\nSatish Talluri\nSaurabh Ladha\nSavannah Cherry\nScott Clark\nScott Duke Kominers\nScott Gottlieb\nScott Hassan\nScott Kupor\nScott Rubin\nScott Shenker\nScott Tyler\nScott Walker\nScott Weiss\nSean Duffy\nSean Neville\nSebastian Oddo\nSeema Amble\nSeemay Chou\nSep Kamvar\nSergiu Pasca\nSeth Lobree\nSeth Sivak\nSeth Sternberg\nShai Bernstein\nShai Kopeld\nShaka Senghor\nShakil Khan\nShan Sinha\nShana Fisher\nShane Mac\nShane Parrish\nShangda Xu\nShannon (Stubo) Brayton\nShannon Barbour\nShannon Kelly\nShannon Schiltz\nShannon Snow\nShari Doherty\nSharon Chang\nShawn Conway\nSheela Krothapalli\nShellye Archambeau\nSherie James\nSherriAnn Cole\nShishir Mehrotra\nShonda Rhimes\nSid Gorham\nSigne Pierce\nSimon Denny\nSiqi Chen\nSonal Chokshi\nSophie Song\nSoubhik Deb\nSpencer Dinwiddie\nSpencer Howard\nSpencer Rascoff\nSreeram Kannan\nSreevidya Kasturil\nSri Kosuri\nSriram Krishnan\nSrivatsan Sridhar\nStacey Cunningham\nStacey Merrick\nStacia Murray\nStacy Brown-Philpot\nStacy D'Amico\nStacy Warner\nStefan McDonough\nSten Tamkivi\nStephane Bancel\nStephanie Anyanwu\nStephanie Cohen\nStephanie Doppelt\nStephanie Smith\nStephanie Watkins\nStephanie Zinn\nStephen Armanios\nStephen Wink\nStephenie Zhang\nSteve Buress\nSteve Cadigan\nSteve Cheney\nSteve Harvey\nSteve Kaczynski\nSteve McDermid\nSteve Smith\nSteve Zhao\nSteven Adair\nSteven Ebert\nSteven Johnson\nSteven Levy\nSteven Sinofsky\nStewart Butterfield\nStina Ehrensvärd\nStuart Luman\nStuart Russell\nSudip Chakrabarti\nSue Hager\nSuhail Doshi\nSukhinder Singh Cassidy\nSumeet Singh\nSumit Shah\nSungMo Park\nSunil Chokshi\nSurya Ganguli\nSusan B. Wilde\nSusan Mernit\nSusan Rice\nSusannah Fox\nSydney Paul\nTaavet Hinrikus\nTaggart Matthiesen\nTamzen Brewis\nTana Billingsley\nTarek Mansour\nTarun Chitra\nTauri Laws Phillips\nTawny Holguin\nTaylor McFadden\nTed Not Lasso\nTed Sarandos\nTed Ullyot\nTerell Sterling\nTerence Carroll\nTeresa Carlson\nTerry Angelos\nTerry Brown\nThan Nguyen\nThanh Nguyen\nThe 2015 Academic Roundtable Sessions\nThe TxO team\nTheresa DeMichele\nTheresa Dilley\nTheresa Fisher\nTheresa Walz\nTheresia Gouw\nThibaut Scholasch\nThomas Gjerde\nThomas Juenger\nThomas Long\nThomas Rando\nTiffany Vo\nTiffany Zhong\nTim Beiko\nTim O'Reilly\nTim Roughgarden\nTim Schafer\nTim Sullivan\nTimmu Tõke\nTina Anderson\nTina Bhatnagar\nTina Ferguson\nTina Wie\ntinawie\nTing Ni\nTobi Lütke\nTodd Cranney\nTodd Lutwak\nTodd McKinnon\nTodd Park\nTodd Young\nTolga Dizdarer\nTom Butta\nTom Coates\nTom Davenport\nTom Ellis\nTom Hammer\nTom Hofmann\nTom Lehman\nTom Mitchell\nTom Preston-Werner\nTom Rikert\nTom Standage\nTomicah Tillemann\nTony Blair\nTony Blinken\nTori Landrum\nTracy Chou\nTracy Young\nTren Griffin\nTrent Mayol\nTrevor Bedford\nTristan Handy\nTristan Walker\nTroy Kirwin\nTugce Erten\nTurner Novak\nTushar Garg\nTyler Cowen\nTyler Wilson\nTyson Clark\nUma Valeti\nUsman Azam\nUzi Dutta\nValentina Marzorati\nValeria Nikolaenko\nValerie Arboleda\nVan Jones\nVan Le-Gray\nVanessa Kropf\nVas Narasimhan\nVaughn Ferguson\nVenkat Mocherla\nVicente De Baca\nVickie Casillas-Smith\nVictor Liang\nVictor Shoup\nVictoria Butcher\nVijay Balasubramaniyan\nVijay Kedar\nVijay Pande\nVineeta Agarwala\nVinod Khosla\nVirginia Postrel\nVishal Amin\nVitalik Buterin\nVivian Brooks\nVoices Onchain\nW. Brian Arthur\nWahab Owolabi\nWei Luo\nWendy Drpic\nWerner Gerola\nWes Taylor\nWhitney Owens\nWill Brown\nWill Wong\nWillem Mulder\nWilliam Gifford\nWilliam Mougayar\nWing Cheng\nXian Zhang\nXiang-Dong Fu\nXingchen Zhou\nYannai A. Gonczarowski\nYehuda Lindell\nYevgeniy Dodis\nYinuo Zhang\nYogi Roth\nYohei Ishii\nYoko Li\nYoni Levy\nYoram Novick\nYuichi Kurosawa\nYujin Chung\nYun Fan\nYung Yung Sheung\nYuval Efron\nYuval Harari\nZac Bookman\nZach Abrams\nZach Cohen\nZach Dicker\nZach Haigney\nZachary Chen\nZachary Gray\nZack Weiner\nZahabiya Gabaji\nZak Doric\nZal Bilimoria\nZane Lackey\nZeta Avarikioti\nZeya Yang\nZooko Wilcox\nZoran Basich\n\nclear all Mahimna Kelkar\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n02.01.26 / Mahimna Kelkar\nRethinking crypto attacker models\nBlockchains operate in a radically new, highly adversarial environment where subtle protocol flaws can be immediately monetized by anonymous actors. This fundamentally intertwines an assortment of fields — cryptography, distributed systems, and mechanism design among many others. As a consequence, blockchain security can no longer be thought of from a single lens. In this talk,...\n\nresearch\n\n03.20.24 / Ertem Nusret Tas, István András Seres, Yinuo Zhang, Márk Melczer, Mahimna Kelkar, Joseph Bonneau and Valeria Nikolaenko\nNew paper alert: Atomic and fair data exchange via blockchain\nA new Fair Data Exchange protocol that enable a storage server to transfer a data file to a client atomically\n\nresearch\ncryptography\ndanksharding\ndata availability\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":6970,"crawled_at":1791193046943}
+{"id":10177,"url":"https://docs.near.org/data-infrastructure/indexers","domain":"docs.near.org","chapter":"layer1_layer2","title":"Introduction to Indexers - NEAR Docs","text":"Here you will find everything you need to know in order to familiarize yourself with the concept of indexers.\n\nWe recommend checking the NEAR Data Flow to familiarize yourself with how data flows within the NEAR ecosystem\n\n​\n\nBlockchains and their nature\n\nBlockchain data is optimized for serialized writes, one block at a time, as the chain is being created. Querying the blockchain for data about a specific block or account is fairly straightforward, as only the data for a specific block needs to be retrieved.\nHowever, querying data across many blocks (e.g. all transfers between date X and Y) can be cumbersome because we have to aggregate results from multiple single-block queries.\nGiven the fact that a blockchain itself is a distributed database, and a smart contract (decentralized application, dApp) is an application that runs on a virtual machine inside a blockchain, we need to understand that smart contracts should not be considered as a “backend”. While some applications might consist only of smart contracts, building a dApp with only smart contracts, in most cases, is not possible.\nSmart contracts are limited in terms of interactions. By “interactions” we mean things that are very common in the real world, like user notifications, integration with third-party applications, etc.\nHowever, the nature of a blockchain is that it must be deterministic. A critical feature of a blockchain is that it knows the state at a given time, and for blockchains that time unit is a block. Think of them as being snapshots. A blockchain does snapshots of its state on every block. We as users can call smart contracts for a specific block, and the blockchain provides guarantees that execution will always produce the same result for the same block any time we call it.\nThe deterministic nature of a blockchain closes it from external (off-chain) variables. It is totally impossible to perform a call to an API from within a smart contract. A blockchain and a smart contract are closed off from the external (off-chain) world.\n\nBlockchains are great at providing a way to apply the requested changes to the state in a decentralized manner. However, in order to observe the changes, you need to actively pull the information from the network.\nInstead of abstract explanations let’s look at an example.\n\nExample dAppSay, we have a smart contract that sells e-books. Once a user buys a book we want to send them a copy via email.\n\nThe dApp has a helper deployed somewhere off-chain, and this helper has code that can send an email with a copy of an e-book. But how would we trigger the helper?\n\n​\n\nGetting the data from a blockchain from the external world\n\nNEAR blockchain implements a JSON-RPC endpoint for everyone to interact with the blockchain. Through the JSON-RPC API users can call smart contracts triggering them to be executed with given parameters. Also, users can view the data from the blockchain.\nSo, continuing with our example we can make our helper pull a Block every second, then pull all the Chunks and analyze the Transactions included in the Block to check if there is a transaction to our smart contract with “buy an e-book” function call. If we observe such a Transaction, we need to ensure it is successful, so we don’t send the e-book to a user whose “buy e-book” Transaction failed.\nAfter the process is complete we can trigger the helper’s code to send the user an email with the e-book they bought.\nThis approach is so-called pull model of getting the data. There is nothing wrong with this approach, but sometimes you might find it is not the most comfortable or reliable approach.\nAlso, not all the data is available through the JSON-RPC. Local Receipts for example are not available through the JSON-RPC, because they are not stored in NEAR node’s internal database.\n\n​\n\nIndexer\n\nA blockchain indexer is an implementation of the push model of getting the data. Instead of actively pulling the data from the source, your helper waits for the data to be sent to it. The data is complete and so the helper can start analyzing it immediately; ideally the data is complete enough to avoid additional pulls to get more details.\nGetting back to our example, the helper becomes an indexer that receives every Block, along with Chunks, Transactions with its statuses, etc. In the same way the helper analyzes the data and triggers the code to send the user an email with the e-book they bought.\n\nAn indexer conceptAn indexer listens to the stream of data as it’s being written on chain and can then be immediately filtered and processed to detect interesting events or patterns.\n\n​\n\nIndexers and “wide” queries\n\nThe term “wide” queries was mentioned in the beginning of this document. Here’s a recap:\n\n“Wide” queries definitionTo query data across many blocks requires the aggregation of results from multiple single-block queries. We can consider these aggregates as coming from “wide” queries.\n\nBecause indexers listen to the stream of data from the blockchain and the data can be immediately filtered and processed according to defined requirements, they can be used to simplify the “wide” queries execution. For example, a stream of data can be written to a permanent database for later data analysis using a convenient query language like SQL.\nAnother example that highlights the need for a “wide query” is when you use a seed phrase to recover one or more accounts. Since a seed phrase essentially represents a signing key pair, the recovery is for all accounts that share the associated public key. Therefore, when a seed phrase is used to recover an account via NEAR Wallet, the query requires that all accounts with a matching public key are found and recovered. Utilizing Near Lake Framework can be used to store this data in a permanent database and this allows NEAR Wallet to perform such “wide queries”. This is impossible to achieve using JSON-RPC only.\n\n​\n\nIndexers in the NEAR ecosystem\n\nNEAR Lake deprecated as of March 24, 2026. The NEAR Lake (AWS S3 buckets) has stopped indexing new blocks. For new projects, prefer Neardata (direct replacement), Data APIs, Goldsky, or the Nearcore Indexer.\n\nIf you are ready to host your own indexer, we recommend using Neardata — it is the direct replacement for NEAR Lake and provides a similar streaming API.\nIf speed is critical for your indexing needs, consider using Near Indexer. However, please note that maintaining it can be more complex and costly, as it essentially operates as an independent node in the network.\nIf you prefer not to host your own solution, you can utilize third-party services.\n\n​\n\nSummary\n\nWe hope this article gives you an understanding of the Indexer concept. Also, we hope now you can easily decide whether you need an indexer for your application.\n\n​\n\nWhat’s next?\n\nYou can learn more about the Lake Indexer project (note: deprecated since March 24, 2026). For new projects, see Neardata and the NEAR Indexer tutorial to learn how to build an indexer in practice.\nAlternatively, there are a few other third-party indexers that are tightly integrated with the NEAR ecosystem. You can review all of your data sourcing options (including The Graph, Pikespeak, SubQuery, and GoldSky) under indexing tools.\nWas this page helpful?","tokens":1812,"crawled_at":1791193047801}
+{"id":10178,"url":"https://stack.olas.network/open-autonomy/key_concepts/fsm_app_components","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Components of an FSM App - Olas Stack Developer Documentation","text":"Components of an FSM App\n\nThere are a number of important concepts that will be introduced in this section so that the developer understands how FSM Apps work. Namely:\n\nCore classes that instrument the FSM App:\n\nAbciApp class: The base class that defines the FSM transitions in an FSM App.\n\nAbstractRoundBehaviour class: The base class defining the overall FSM Apps behaviour.\n\nClasses that define the operations per state of the FSM:\n\nAbstractRound class: The base class to define the FSM state rounds of the FSM App.\n\nAsyncBehaviour class: The base class to define FSM state behaviours to be executed during each round in the FSM App.\n\nOther classes related to the FSM App FSM global state:\n\nSynchronizedData class: The class providing\naccess to the shared state.\n\nHow FSM Apps work\n\nThe AbciApp class defines the constituent FSM of the FSM App. That is, it defines the set of start and final states (rounds) and the transition function.\n\nThe state of the FSM App is updated through\ntransactions committed to the temporary blockchain.\nThis ledger is local with respect to the Period, i.e., its\nexistence is controlled by, and only relevant in context of, the Period. It is\ndistributed and decentralized with respect to the AEAs in the system, all of\nwhom run a local consensus node. The underlying consensus engine (currently\nTendermint) allows decentralized state replication among different processes.\n\nThe transitions in the FSM are triggered by the delivery of blocks from the\nconsensus engine through the ABCI. The transactions that are contained in these blocks are submitted by AEAs Behaviours, and can lead to updates of the shared SynchronizedData.\n\nEach round has its own business logic, which specifies how the participants'\ntransactions are validated or the conditions that trigger a transition to\nanother round (e.g., enough votes received for the same value). The transitions\nare triggered by means of events, i.e., values that are set by the round\nimplementation and are processed by the framework in order to compute the round\nsuccessor.\n\nThere are two kinds of events: normal events and timeout events:\n\nNormal events are set by the round according to certain conditions that are checked during the execution of a round. These conditions can be defined arbitrarily according to the business logic of the FSM App.\n\nTimeout events are automatically triggered in case the timeout associated to\nthe event has expired. The timeout is checked against the \"global clock\", which\nis a side effect of block validation: each block header carries the timestamp of the event of block proposal.\n\nExample\n\nA normal event can\n\nOn the other hand, consider a block B1 with timestamp t1, and block B2 with\ntimestamp t2=t1+10 seconds. Assume that after B1 is processed, the\nFSM App current state round is defined to trigger a timeout event set at T=5 seconds. When B2 is delivered, the timeout event had already been triggered (because T<t2−t1), and the associated transition had already happened in the FSM, regardless of the content of B2.\n\nThe ABCIHandler, is in charge of receiving the transactions through the\nDeliverTx\nABCI requests, and forwards them to the current active round, which produces the\nresponse for DeliverTx. The end_block abstract method is called on the ABCI request EndBlock, and determines the round successor by setting the event to\ntake the transition to the next state, as defined by the transition function in the AbciApp.\n\nImportant\n\nWe remark that the FSM App, which resides inside the AEA, is updated by\nthe consensus engine through the ABCI requests handled by the ABCIHandler, and\nNOT by the AEA behaviours. The AEA behaviours can only send updates through\nthe process of sending transactions to the consensus engine.\n\nThe Period class keeps track of an execution of the FSM App. It is\ninstantiated in the state of the Skill and accessible through the SkillContext.\nIt is a concrete class, so the developer should not need to extend it.","tokens":993,"crawled_at":1791193050886}
+{"id":10179,"url":"https://a16zcrypto.com/posts/article/new-paper-alert-fair-data-exchange","domain":"a16zcrypto.com","chapter":"research","title":"New paper alert: Atomic and fair data exchange via blockchain - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nNew paper alert: Atomic and fair data exchange via blockchain\nErtem Nusret Tas, István András Seres, Yinuo Zhang, Márk Melczer, Mahimna Kelkar, Joseph Bonneau, and Valeria Nikolaenko\n03.20.24\n\nTags & Share Tags\ncryptography\ndanksharding\ndata availability\nresearch\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nIn a new paper, we outline a new protocol for building fair data-markets – including for expired blobs under EIP-4844, also known as “protodanksharding.”\n\nOur Fair Data Exchange protocol enables a storage server to transfer a data file to a client atomically: The client receives the file if and only if the server receives an agreed-upon payment. In short, this new approach allows you to buy a potentially large blob of data (that has the properties you think it has) with minimal trust assumptions in a decentralized and open market. To date, it’s been hard to sell data without revealing it publicly, while also guaranteeing that the seller will receive payment for data once it’s been sent. This new scheme insures both sides of the transaction. It also introduces a new cryptographic primitive, Verifiable Encryption under Committed Key (VECK), which generalizes verifiable encryption to symmetric key primitives.\n\nBackground\n\nFair and secure protocols to purchase access to data are essential to unlock the massive potential of global data markets. But most real-world approaches for accessing data today are either subscription-based, where the client pays the server in advance and must trust the reputation of the server to deliver the data; or altruistic, where either the server provides the data free of charge or the data is exchanged between the users themselves. The former approach does not safeguard the client from a malicious server that receives payment without fulfilling the data request, while the latter lacks incentives for clients to offer data for download, often leading to free-riding and limited capacity. Most of these systems do not provide data integrity guarantees to users.\n\nBlockchains – originally conceived of as payment systems – can also be used for data storage, guaranteeing that every transaction in a block is accessible to every participant in the network (e.g., OP_RETURN in Bitcoin or calldata in Ethereum). As append-only, immutable, and distributed ledgers, blockchains can provide data storage that is robust against faults and abuses of power. But by themselves (without any form of sharding or roll-ups), blockchains are highly limited in storage capacity, since all validators replicate all data, making on-chain storage expensive. (As of 2024, March 15th, storing 1MB on the Ethereum blockchain in calldata would cost roughly 2,500 USD.)\n\nWhile many blockchain projects are working to improve capacity and reduce costs, these systems will likely always be limited as increased capacity is at odds with maintaining security and decentralization (the “blockchain trilemma”).\n\nLimited on-chain capacity has led to the development of layer-2 systems, which perform computation off-chain. The main blockchain (now called a layer-1) verifies off-chain computation using non-interactive validity proofs (zk-rollups) or interactive fraud proofs (optimistic rollups). Data is stored on-chain in traditional rollups, but the cost of on-chain storage has led to designs that store data off-chain as well (often called validiums). In this approach, the layer-1 blockchain stores only a succinct commitment to the data. This commitment can be used to verify proofs-of-storage or proofs-of-replication, attesting to the persistence of the data off-chain.\n\nWhile these protocols provide a natural mechanism to pay to store data, they don’t provide a means to pay for serving the data when clients request it. Today’s systems only incentivize storage, and assume servers will provide download access “for free.” This is problematic for two reasons: First, transferring the data comes with its own costs, for which servers should be compensated. Second, without any incentives, malicious servers might store data (and receive payment for doing so) but never respond to legitimate download requests. Storage is useless unless the data is made available for access.\n\nFair data exchange\n\nWe’d like a way for clients to pay for data with guarantees that the server will provide it if payment is collected. This is an example of the more general fair exchange problem, which is known to require a trusted third party (e.g., a blockchain). Blockchains can also potentially be used to solve this in a straightforward way: a smart contract can keep a client’s payment in escrow, and release it to the server once a server posts data with some specified properties on-chain. But this is not efficient if the data is large, because all of the data must be posted on-chain for the smart contract to verify.\n\nFair data exchange (FDE), the protocol we introduce in the paper, relies on a blockchain to enforce the atomicity and fairness of the exchange, and uses VECK (Verifiable Encryption under Committed Key), a new cryptographic primitive, to ensure that the client receives the correct data (matching an agreed-upon commitment) off-chain before releasing the payment for the decrypting key. The protocol is trust-minimized and requires only constant-sized on-chain communication: 3 signatures, 1 verification key, and 1 secret key, with most of the data stored and communicated off-chain.\n\nThe protocol also supports exchanging only a subset of the data. Further, it can amortize the server’s work across multiple clients, and offers a general framework to design alternative FDE protocols using different commitment and encryption schemes.\n\nHere’s how it works, in three essential steps:\n\nThe Client requests the data from the Server, specifying a KZG commitment of the expected data and a public encryption key.\n\nThe Server encrypts the data using the Client’s specified key and sends the encrypted data to the Client off-chain, along with a zero-knowledge proof (VECK proof) that the encrypted data matches the specified commitment.\n\nThe server sells the decryption key on-chain, using a simple atomic transfer.\n\nThe bulk of the communication takes place off-chain, and the server’s work is reusable across different clients requesting the same data. The key technical challenge is in step 2: efficiently proving that encrypted data matches a specified commitment. This is where our new VECK primitive comes in (which may be of independent interest for other protocols).\n\nApplications\n\nFDE can be used to pay for access to data stored using EIP-4844 (protodanksharding) and full danksharding data availability schemes for Ethereum. These protocols allow data to expire, meaning that after a predetermined period of time (4,096 epochs; ≈18 days), validators are no longer obliged to store it. Our protocol may potentially encourage nodes to continue storing the data, because they can profit from selling it later via FDE, thus potentially alleviating some concerns around the loss of expired data. Both protocols also commit to data via KZG polynomial commitments, exactly what our FDE construction is optimized to support.\n\nOur first protocol uses the exponential ElGamal encryption scheme, while the second protocol applies the Paillier encryption scheme to encrypt the exchanged data. We also provide an open-source implementation (see the repo here) for our protocol with both instantiations for VECK, demonstrating our protocol’s efficiency and practicality on Ethereum as well as on Bitcoin via adaptor signatures. Concretely, the on-chain cost of a single FDE run on Ethereum is ~200,000 gas for the server (under 10 USD) and ~30,000 gas for the client (under 1 USD).\n\nBeyond these, FDE may be used for any scenario in which a client wants to buy very large amounts of data (with some expected properties) in a decentralized and open market with minimal trust assumptions. Our protocols also support purchasing data privately.\n\nFuture work\n\nDirections for work in the future could include:\n\nExploring other combinations for commitment and encryption schemes,\n\nOptimized implementations (see the paper for open issues) to make the protocol faster both for the client and for the server,\n\nGeneralizing the scheme to allow verifiable pre-processing of the data, including the case when the data is distributed, and\n\nDesigning pricing mechanisms for a decentralized data marketplace.\n\nFinally, if clients and servers are rational, nobody would be grieved in our protocol. But irrational or malicious clients may cause honest servers to keep sending encrypted data without ever requesting the decryption key. Although this problem was out of scope of the paper, it will have to be mitigated in practice.\n\n***\n\nThe paper emerged from a16z crypto’s summer internship program, and is a joint work with four summer interns. For details, proofs, and citations, read the paper.\n\n***\n\nErtem Nusret is a PhD student in electrical engineering at Stanford University working with Prof. David Tse on the analysis of blockchain.\n\nIstván András Seres is a PhD Student in computer science at Eötvös Loránd University.\n\nYinuo Zhang is a PhD student in computer science at the University of California, Berkeley.\n\nMárk Melczer is a PhD student in computer science at Eötvös Loránd University.\n\nMahimna Kelkar is a PhD student in computer science at Cornell University.\n\nJoseph Bonneau is a Research Partner at a16z crypto. His research focuses on applied cryptography and blockchain security. He has taught cryptocurrency courses at the University of Melbourne, NYU, Stanford, and Princeton, and received a PhD in computer science from the University of Cambridge and BS/MS degrees from Stanford.\n\nValeria Nikolaenko is a Research Partner at a16z crypto. Her research focuses on cryptography and blockchain security. She has also worked on topics such as long-range attacks in PoS consensus protocols, signature schemes, post-quantum security, and multi-party computation. She holds a PhD in Cryptography from Stanford University under advisorship of Professor Dan Boneh, and worked on the Diem blockchain as part of the core research team.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investment-list/.\n\nPast performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures/ for additional important information.","tokens":3202,"crawled_at":1791193065627}
+{"id":10180,"url":"https://docs.near.org/api/rpc/introduction","domain":"docs.near.org","chapter":"layer1_layer2","title":"Protocol Call Reference - NEAR Docs","text":"NEAR Protocol provides multiple ways to interact with the network — from low-level JSON-RPC calls to visual explorers and wallets.\n​\n\nTools\n\nNEAR Explorer\nBrowse transactions, accounts, blocks, and contracts on mainnet and testnet.\n\nNEAR Wallet\nCreate and manage NEAR accounts, send tokens, and interact with dApps.\n\n​\n\nRPC API\n\nNEAR exposes a JSON-RPC 2.0 API for programmatic access to the network. Send requests with POST to the root of a provider endpoint and put the method name in the JSON request body.\n\nThe endpoint reference in the RPC sidebar is generated from openapi.json and is the source of truth for request and response schemas. The hand-written RPC pages provide guidance, context, and worked examples.\n\ncurl -X POST https://rpc.mainnet.near.org/ \\\n-H \"Content-Type: application/json\" \\\n-d '{\"jsonrpc\":\"2.0\",\"id\":\"status\",\"method\":\"status\",\"params\":[]}'\n\nSee RPC Providers for the full list of public endpoints. When enabled by its operator, a recent nearcore node can also accept multiple read-only query calls in one request; see Query Batching for its scope and availability caveats.\n​\n\nAvailable Methods\n\nCategoryMethods\nTransactions\nsend_tx, tx, EXPERIMENTAL_tx_status, EXPERIMENTAL_receipt, EXPERIMENTAL_receipt_to_tx, broadcast_tx_async, broadcast_tx_commit\n\nQuery\nquery — see Accounts / Contracts for every supported request_type\n\nAccounts & access keys\nEXPERIMENTAL_view_account, changes, EXPERIMENTAL_changes, EXPERIMENTAL_view_access_key, EXPERIMENTAL_view_access_key_list\n\nSmart contracts\nEXPERIMENTAL_view_code, EXPERIMENTAL_view_state, EXPERIMENTAL_call_function\n\nBlocks & chunks\nblock, chunk, block_effects, EXPERIMENTAL_changes_in_block\n\nNetwork\nstatus, health, network_info, validators, client_config, EXPERIMENTAL_validators_ordered\n\nGas & configuration\ngas_price, genesis_config, EXPERIMENTAL_genesis_config, EXPERIMENTAL_protocol_config, EXPERIMENTAL_congestion_level\n\nLight client\nlight_client_proof, next_light_client_block, EXPERIMENTAL_light_client_proof, EXPERIMENTAL_light_client_block_proof\n\nMaintenance & storage\nmaintenance_windows, EXPERIMENTAL_maintenance_windows, EXPERIMENTAL_split_storage_info\n\nExplore the full interactive reference in the sidebar, or start with RPC Providers to configure your endpoint.\nWas this page helpful?","tokens":570,"crawled_at":1791193065796}
+{"id":10181,"url":"https://www.metaplex.com/docs/smart-contracts/token-metadata/burn","domain":"www.metaplex.com","chapter":"docs","title":"Burning Assets | Token Metadata","text":"Token Metadata is a legacy program. It remains supported, but is not recommended for new projects. Use Core instead.\n\nThe owner of an asset can burn it using the Burn instruction of the Token Metadata program. This will close all possible accounts associated with the asset and transfer the various rent-exempt fees previously held in the closed accounts to the owner. This instruction accepts the following attributes:\nAuthority: The signer that authorizes the burn. Typically, this is the owner of the asset but note that certain delegated authorities can also burn assets on behalf of the owner as discussed in the \"Delegated Authorities\" page.\nToken Owner: The public key of the current owner of the asset.\nToken Standard: The standard of the asset being burnt. This instruction works for all Token Standards in order to provide a unified interface for burning assets. That being said, it is worth noting that non-programmable assets can be burnt using the Burn instruction of the SPL Token program directly.\nThe exact accounts closed by the Burn instruction depend on the Token Standard of the asset being burnt. Here's a table that summarizes the accounts for each Token Standard:\nToken StandardMintTokenMetadataEditionToken RecordEdition Marker\nNonFungible\n❌\n✅\n✅\n✅\n❌\n❌\n\nNonFungibleEdition\n❌\n✅\n✅\n✅\n❌\n✅ if all prints for it are burnt\n\nFungible and FungibleAsset\n❌\n✅ if all tokens are burnt\n❌\n❌\n❌\n❌\n\nProgrammableNonFungible\n❌\n✅\n✅\n✅\n✅\n❌\n\nNote that the Mint account is never closed because the SPL Token program does not allow it.\nHere is how you can use our SDKs to burn an asset on Token Metadata.\nNFT Burn\n\n1import { publicKey } from '@metaplex-foundation/umi';\n\n2import { burnV1, TokenStandard } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4// Assuming umi is set up with mplTokenMetadata plugin\n\n5// See getting-started for full setup\n\n6\n\n7const mintAddress = publicKey('mintAddress...');\n\n8\n\n9// Burn the NFT (removes all accounts and closes token account)\n\n10await burnV1(umi, {\n\n11 mint: mintAddress,\n\n12 authority: umi.identity,\n\n13 tokenOwner: umi.identity.publicKey,\n\n14 tokenStandard: TokenStandard.NonFungible,\n\n15}).sendAndConfirm(umi);\n\n16\n\n17console.log('NFT burned:', mintAddress);\n\n1import {\n\n2 getBurnV1InstructionAsync,\n\n3 TokenStandard,\n\n4} from '@metaplex-foundation/mpl-token-metadata-kit';\n\n5\n\n6// Assuming rpc, rpcSubscriptions, sendAndConfirm, and authority are set up\n\n7// See getting-started for full setup\n\n8\n\n9const mintAddress = 'mintAddress...'; // The NFT mint address\n\n10\n\n11// Burn the NFT (removes all accounts and closes token account)\n\n12const burnIx = await getBurnV1InstructionAsync({\n\n13 mint: mintAddress,\n\n14 authority,\n\n15 payer: authority,\n\n16 tokenOwner: authority.address,\n\n17 tokenStandard: TokenStandard.NonFungible,\n\n18});\n\n19\n\n20await sendAndConfirm({\n\n21 instructions: [burnIx],\n\n22 payer: authority,\n\n23});\n\n24\n\n25console.log('NFT burned:', mintAddress);\n\n1use mpl_token_metadata::instructions::BurnNftCpiBuilder;\n\n2\n\n3BurnNftCpiBuilder::new(&metadata_program_id)\n\n4 .metadata(&metadata)\n\n5 // if your NFT is part of a collection you will need to pass in the collection metadata address.\n\n6 .collection_metadata(collection_metadata.as_ref())\n\n7 .owner(&owner)\n\n8 .mint(&mint)\n\n9 .token_account(&token)\n\n10 .master_edition_account(&edition)\n\n11 .spl_token_program(&spl_token)\n\n12 .invoke()?;\n\n1use anchor_lang::prelude::*;\n\n2use anchor_spl::token::Mint;\n\n3use mpl_token_metadata::instructions::BurnNftCpiBuilder;\n\n4\n\n5#[derive(Accounts)]\n\n6pub struct NftBurnMpl<'info> {\n\n7 #[account(mut)]\n\n8 owner: Signer<'info>,\n\n9 #[account(mut)]\n\n10 mint: Account<'info, Mint>,\n\n11 #[account(mut)]\n\n12 metadata: AccountInfo<'info>,\n\n13 #[account(mut)]\n\n14 token: AccountInfo<'info>,\n\n15 #[account(mut)]\n\n16 edition: AccountInfo<'info>,\n\n17 collection_metadata: Option<AccountInfo<'info>>,\n\n18 spl_token: AccountInfo<'info>,\n\n19 metadata_program_id: AccountInfo<'info>,\n\n20}\n\n21\n\n22pub fn burn_nft_mpl_instruction<'info>(\n\n23 ctx: Context<'_, '_, '_, 'info, NftBurnMpl<'info>>,\n\n24) -> Result<()> {\n\n25 let owner = ctx.accounts.owner.to_account_info();\n\n26 let metadata = ctx.accounts.metadata.to_account_info();\n\n27 let collection_metadata = ctx.accounts.collection_metadata.as_ref().map(|a| a.to_account_info());\n\n28 let mint = ctx.accounts.mint.to_account_info();\n\n29 let token = ctx.accounts.token.to_account_info();\n\n30 let edition = ctx.accounts.edition.to_account_info();\n\n31 let spl_token = ctx.accounts.spl_token.to_account_info();\n\n32 let metadata_program_id = ctx.accounts.metadata_program_id.to_account_info();\n\n33\n\n34 BurnNftCpiBuilder::new(&metadata_program_id)\n\n35 .metadata(&metadata)\n\n36 // if your NFT is part of a collection you will also need to pass in the collection metadata address.\n\n37 .collection_metadata(collection_metadata.as_ref())\n\n38 .owner(&owner)\n\n39 .mint(&mint)\n\n40 .token_account(&token)\n\n41 .master_edition_account(&edition)\n\n42 .spl_token_program(&spl_token)\n\n43 .invoke()?;\n\n44\n\n45 Ok(())\n\n46}\n\npNFT Burn\npNFTs may require additional accounts to be passed in for the instruction to work. These may include:\ntokenAccount\ntokenRecord\nauthorizationRules\nauthorizationRulesProgram\n\n1import { publicKey } from '@metaplex-foundation/umi';\n\n2import { burnV1, TokenStandard } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4// Assuming umi is set up with mplTokenMetadata plugin\n\n5\n\n6const mintAddress = publicKey('mintAddress...');\n\n7\n\n8// Burn the Programmable NFT\n\n9// Note: pNFTs have Token Record accounts that are also cleaned up\n\n10await burnV1(umi, {\n\n11 mint: mintAddress,\n\n12 authority: umi.identity,\n\n13 tokenOwner: umi.identity.publicKey,\n\n14 tokenStandard: TokenStandard.ProgrammableNonFungible,\n\n15}).sendAndConfirm(umi);\n\n16\n\n17console.log('pNFT burned:', mintAddress);\n\n1import {\n\n2 getBurnV1InstructionAsync,\n\n3 TokenStandard,\n\n4} from '@metaplex-foundation/mpl-token-metadata-kit';\n\n5\n\n6// Assuming rpc, rpcSubscriptions, sendAndConfirm, and authority are set up\n\n7\n\n8const mintAddress = 'mintAddress...'; // The pNFT mint address\n\n9\n\n10// Burn the Programmable NFT\n\n11// Note: pNFTs have Token Record accounts that are also cleaned up\n\n12const burnIx = await getBurnV1InstructionAsync({\n\n13 mint: mintAddress,\n\n14 authority,\n\n15 payer: authority,\n\n16 tokenOwner: authority.address,\n\n17 tokenStandard: TokenStandard.ProgrammableNonFungible,\n\n18});\n\n19\n\n20await sendAndConfirm({\n\n21 instructions: [burnIx],\n\n22 payer: authority,\n\n23});\n\n24\n\n25console.log('pNFT burned:', mintAddress);\n\n1use mpl_token_metadata::instructions::BurnNftCpiBuilder;\n\n2\n\n3BurnNftCpiBuilder::new(metadata_program_id.account_info())\n\n4 .metadata(metadata.account_info())\n\n5 .collection_metadata(Some(collection_metadata.account_info()))\n\n6 .owner(owner.account_info())\n\n7 .mint(mint.account_info())\n\n8 .token_account(token.account_info())\n\n9 .master_edition_account(edition.account_info())\n\n10 .spl_token_program(spl_token.account_info())\n\n11 .invoke()?;\n\n1use anchor_lang::prelude::*;\n\n2use anchor_spl::token::Mint;\n\n3use mpl_token_metadata::instructions::BurnV1CpiBuilder;\n\n4\n\n5#[derive(Accounts)]\n\n6pub struct PnftBurnMpl<'info> {\n\n7 #[account(mut)]\n\n8 owner: Signer<'info>,\n\n9 #[account(mut)]\n\n10 mint: Account<'info, Mint>,\n\n11 #[account(mut)]\n\n12 metadata: AccountInfo<'info>,\n\n13 #[account(mut)]\n\n14 token: AccountInfo<'info>,\n\n15 #[account(mut)]\n\n16 master_edition: AccountInfo<'info>,\n\n17 #[account(mut)]\n\n18 token_record: AccountInfo<'info>,\n\n19 collection_metadata: Option<AccountInfo<'info>>,\n\n20 spl_token: AccountInfo<'info>,\n\n21 metadata_program_id: AccountInfo<'info>,\n\n22}\n\n23\n\n24pub fn burn_pnft_mpl_instruction<'info>(\n\n25 ctx: Context<'_, '_, '_, 'info, PnftBurnMpl<'info>>,\n\n26) -> Result<()> {\n\n27let owner = ctx.accounts.owner.to_account_info();\n\n28let metadata = ctx.accounts.metadata.to_account_info();\n\n29let mint = ctx.accounts.mint.to_account_info();\n\n30let token = ctx.accounts.token.to_account_info();\n\n31let master_edition = ctx.accounts.master_edition.to_account_info();\n\n32let collection_metadata = ctx\n\n33 .accounts\n\n34 .collection_metadata\n\n35 .as_ref()\n\n36 .map(|a| a.to_account_info());\n\n37let spl_token = ctx.accounts.spl_token.to_account_info();\n\n38let token_record = ctx.accounts.token_record.to_account_info();\n\n39let metadata_program_id = ctx.accounts.metadata_program_id.to_account_info();\n\n40\n\n41BurnV1CpiBuilder::new(&metadata_program_id)\n\n42 .metadata(&metadata)\n\n43 .collection_metadata(collection_metadata.as_ref())\n\n44 .authority(&owner)\n\n45 .mint(&mint)\n\n46 .token(&token)\n\n47 .spl_token_program(&spl_token)\n\n48 .token_record(Some(&token_record))\n\n49 .master_edition(Some(&master_edition))\n\n50 .invoke()?;\n\n51\n\n52Ok(())\n\n53}","tokens":2163,"crawled_at":1791193100064}
+{"id":10182,"url":"https://docs.near.org/api-reference/post-send_tx","domain":"docs.near.org","chapter":"layer1_layer2","title":"Post send tx - NEAR Docs","text":"cURL\n\ncurl --request POST \\\n--url https://api.example.com/send_tx \\\n--header 'Content-Type: application/json' \\\n--data '\n{\n\"method\": \"send_tx\",\n\"params\": {\n\"signed_tx_base64\": \"aSDinaTvuI8gbWludGxpZnk=\",\n\"wait_until\": \"EXECUTED_OPTIMISTIC\"\n},\n\"id\": \"dontcare\",\n\"jsonrpc\": \"2.0\"\n}\n'\n\nconst options = {\nmethod: 'POST',\nheaders: {'Content-Type': 'application/json'},\nbody: JSON.stringify({\nmethod: 'send_tx',\nparams: {\nsigned_tx_base64: 'aSDinaTvuI8gbWludGxpZnk=',\nwait_until: 'EXECUTED_OPTIMISTIC'\n},\nid: 'dontcare',\njsonrpc: '2.0'\n})\n};\n\nfetch('https://api.example.com/send_tx', options)\n.then(res => res.json())\n.then(res => console.log(res))\n.catch(err => console.error(err));\n\nimport requests\n\nurl = \"https://api.example.com/send_tx\"\n\npayload = {\n\"method\": \"send_tx\",\n\"params\": {\n\"signed_tx_base64\": \"aSDinaTvuI8gbWludGxpZnk=\",\n\"wait_until\": \"EXECUTED_OPTIMISTIC\"\n},\n\"id\": \"dontcare\",\n\"jsonrpc\": \"2.0\"\n}\nheaders = {\"Content-Type\": \"application/json\"}\n\nresponse = requests.post(url, json=payload, headers=headers)\n\nprint(response.text)\n\n{\n\"result\": {\n\"receipts\": [\n{\n\"predecessor_id\": \"<string>\",\n\"receipt\": {\n\"Action\": {\n\"actions\": [\n\"CreateAccount\"\n],\n\"gas_price\": \"<string>\",\n\"input_data_ids\": [\n\"<string>\"\n],\n\"output_data_receivers\": [\n{\n\"data_id\": \"<string>\",\n\"receiver_id\": \"<string>\"\n}\n],\n\"signer_id\": \"<string>\",\n\"signer_public_key\": \"<string>\",\n\"is_promise_yield\": false,\n\"refund_to\": \"<string>\"\n}\n},\n\"receipt_id\": \"<string>\",\n\"receiver_id\": \"<string>\",\n\"priority\": 0\n}\n],\n\"receipts_outcome\": [\n{\n\"block_hash\": \"<string>\",\n\"id\": \"<string>\",\n\"outcome\": {\n\"executor_id\": \"<string>\",\n\"gas_burnt\": 1,\n\"logs\": [\n\"<string>\"\n],\n\"receipt_ids\": [\n\"<string>\"\n],\n\"status\": \"Unknown\",\n\"tokens_burnt\": \"<string>\",\n\"metadata\": {\n\"version\": 1\n}\n},\n\"proof\": [\n{\n\"direction\": \"Left\",\n\"hash\": \"<string>\"\n}\n]\n}\n],\n\"status\": \"NotStarted\",\n\"transaction\": {\n\"actions\": [\n\"CreateAccount\"\n],\n\"hash\": \"<string>\",\n\"nonce\": 1,\n\"public_key\": \"<string>\",\n\"receiver_id\": \"<string>\",\n\"signature\": \"<string>\",\n\"signer_id\": \"<string>\",\n\"nonce_index\": 32767,\n\"nonce_mode\": \"monotonic\",\n\"priority_fee\": 0\n},\n\"transaction_outcome\": {\n\"block_hash\": \"<string>\",\n\"id\": \"<string>\",\n\"outcome\": {\n\"executor_id\": \"<string>\",\n\"gas_burnt\": 1,\n\"logs\": [\n\"<string>\"\n],\n\"receipt_ids\": [\n\"<string>\"\n],\n\"status\": \"Unknown\",\n\"tokens_burnt\": \"<string>\",\n\"metadata\": {\n\"version\": 1\n}\n},\n\"proof\": [\n{\n\"direction\": \"Left\",\n\"hash\": \"<string>\"\n}\n]\n},\n\"final_execution_status\": \"EXECUTED_OPTIMISTIC\"\n},\n\"id\": \"<string>\",\n\"jsonrpc\": \"<string>\"\n}\n\nPOST\n/\nsend_tx\n\ncURL\n\ncurl --request POST \\\n--url https://api.example.com/send_tx \\\n--header 'Content-Type: application/json' \\\n--data '\n{\n\"method\": \"send_tx\",\n\"params\": {\n\"signed_tx_base64\": \"aSDinaTvuI8gbWludGxpZnk=\",\n\"wait_until\": \"EXECUTED_OPTIMISTIC\"\n},\n\"id\": \"dontcare\",\n\"jsonrpc\": \"2.0\"\n}\n'\n\nconst options = {\nmethod: 'POST',\nheaders: {'Content-Type': 'application/json'},\nbody: JSON.stringify({\nmethod: 'send_tx',\nparams: {\nsigned_tx_base64: 'aSDinaTvuI8gbWludGxpZnk=',\nwait_until: 'EXECUTED_OPTIMISTIC'\n},\nid: 'dontcare',\njsonrpc: '2.0'\n})\n};\n\nfetch('https://api.example.com/send_tx', options)\n.then(res => res.json())\n.then(res => console.log(res))\n.catch(err => console.error(err));\n\nimport requests\n\nurl = \"https://api.example.com/send_tx\"\n\npayload = {\n\"method\": \"send_tx\",\n\"params\": {\n\"signed_tx_base64\": \"aSDinaTvuI8gbWludGxpZnk=\",\n\"wait_until\": \"EXECUTED_OPTIMISTIC\"\n},\n\"id\": \"dontcare\",\n\"jsonrpc\": \"2.0\"\n}\nheaders = {\"Content-Type\": \"application/json\"}\n\nresponse = requests.post(url, json=payload, headers=headers)\n\nprint(response.text)\n\n{\n\"result\": {\n\"receipts\": [\n{\n\"predecessor_id\": \"<string>\",\n\"receipt\": {\n\"Action\": {\n\"actions\": [\n\"CreateAccount\"\n],\n\"gas_price\": \"<string>\",\n\"input_data_ids\": [\n\"<string>\"\n],\n\"output_data_receivers\": [\n{\n\"data_id\": \"<string>\",\n\"receiver_id\": \"<string>\"\n}\n],\n\"signer_id\": \"<string>\",\n\"signer_public_key\": \"<string>\",\n\"is_promise_yield\": false,\n\"refund_to\": \"<string>\"\n}\n},\n\"receipt_id\": \"<string>\",\n\"receiver_id\": \"<string>\",\n\"priority\": 0\n}\n],\n\"receipts_outcome\": [\n{\n\"block_hash\": \"<string>\",\n\"id\": \"<string>\",\n\"outcome\": {\n\"executor_id\": \"<string>\",\n\"gas_burnt\": 1,\n\"logs\": [\n\"<string>\"\n],\n\"receipt_ids\": [\n\"<string>\"\n],\n\"status\": \"Unknown\",\n\"tokens_burnt\": \"<string>\",\n\"metadata\": {\n\"version\": 1\n}\n},\n\"proof\": [\n{\n\"direction\": \"Left\",\n\"hash\": \"<string>\"\n}\n]\n}\n],\n\"status\": \"NotStarted\",\n\"transaction\": {\n\"actions\": [\n\"CreateAccount\"\n],\n\"hash\": \"<string>\",\n\"nonce\": 1,\n\"public_key\": \"<string>\",\n\"receiver_id\": \"<string>\",\n\"signature\": \"<string>\",\n\"signer_id\": \"<string>\",\n\"nonce_index\": 32767,\n\"nonce_mode\": \"monotonic\",\n\"priority_fee\": 0\n},\n\"transaction_outcome\": {\n\"block_hash\": \"<string>\",\n\"id\": \"<string>\",\n\"outcome\": {\n\"executor_id\": \"<string>\",\n\"gas_burnt\": 1,\n\"logs\": [\n\"<string>\"\n],\n\"receipt_ids\": [\n\"<string>\"\n],\n\"status\": \"Unknown\",\n\"tokens_burnt\": \"<string>\",\n\"metadata\": {\n\"version\": 1\n}\n},\n\"proof\": [\n{\n\"direction\": \"Left\",\n\"hash\": \"<string>\"\n}\n]\n},\n\"final_execution_status\": \"EXECUTED_OPTIMISTIC\"\n},\n\"id\": \"<string>\",\n\"jsonrpc\": \"<string>\"\n}\n\nBody\napplication/json\n\n​\n\nmethod\nenum<string>\nrequired\n\nAvailable options: send_tx\n\n​\n\nparams\nRpcSendTransactionRequest · object\nrequired\n\nShow child attributes\n\n​\n\nid\nstring\ndefault:dontcare\n\nJSON-RPC request id. Auto-populated; can be any string.\n\n​\n\njsonrpc\nenum<string>\ndefault:2.0\n\nJSON-RPC protocol version. Always 2.0.\n\nAvailable options: 2.0\n\nResponse\n200 - application/json\n\nJsonRpcResponse_for_RpcTransactionResponse_and_RpcTransactionError\n\nJsonRpcResponse_for_RpcTransactionResponse_and_RpcTransactionError\n\n​\n\nresult\nobject\nrequired\n\nFinal execution outcome of the transaction and all of subsequent the receipts. Also includes\nthe generated receipt.\n\nOption 1\n\nOption 2\n\nOption 3\n\nShow child attributes\n\n​\n\nid\nstring\nrequired\n\n​\n\njsonrpc\nstring\nrequired\n\nWas this page helpful?","tokens":1451,"crawled_at":1791193083955}
+{"id":10183,"url":"https://a16zcrypto.com/posts/tags/danksharding","domain":"a16zcrypto.com","chapter":"research","title":"danksharding - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\ndanksharding\n\nFeed\nFILTERS\n(1)\nclear filters\n\ncategories\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\n(1) recommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nclear all danksharding\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n03.20.24 / Ertem Nusret Tas, István András Seres, Yinuo Zhang, Márk Melczer, Mahimna Kelkar, Joseph Bonneau and Valeria Nikolaenko\nNew paper alert: Atomic and fair data exchange via blockchain\nA new Fair Data Exchange protocol that enable a storage server to transfer a data file to a client atomically\n\nresearch\ncryptography\ndanksharding\ndata availability\n\n05.05.23 / Valeria Nikolaenko, Dan Boneh and Robert Hackett\nOf data availability & danksharding\nAn explainer on data availability sampling and danksharding—relevant to Ethereum blockchain scaling—from the web3 with a16z crypto podcast.\n\nresearch\ncryptography\ndanksharding\ndata availability\nEthereum\npodcast\nscaling & throughput\n\n04.27.23 / Valeria Nikolaenko and Dan Boneh\nData availability sampling and danksharding: An overview and a proposal for improvements\nDanksharding is an approach to scaling the amount of data on chain for a future version of Ethereum. The goal of this upgrade is to ensure that the data on chain was made available to archiving parties when it was first posted. It does so using a technique called Data Availability Sampling, or simply DAS....\n\nresearch\ndanksharding\ndata availability\nEthereum\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":1061,"crawled_at":1791193084604}
+{"id":10184,"url":"https://docs.synthetix.io/deposits-withdrawals/slp-vault","domain":"docs.synthetix.io","chapter":"defi_protocols","title":"SLP Vault – Synthetix","text":"Last updated: Feb 24, 2026\n\nThe Synthetix Liquidity Provider (SLP) Vault is the protocol's community market making vault, designed to back all perps markets on Ethereum Mainnet.\n\nHow it works\n\nWhen opened to users, the SLP vault would pool capital from depositors and deploy it as liquidity backing for perpetual markets. As traders pay fees and funding, a portion of those revenues would flow back to depositors proportional to their share of the vault.\n\nParticipation in SLP means capital would be exposed to market making performance. Depositors would benefit when the exchange generates revenue, and they would also be exposed to losses if the vault's market making position loses money.\n\nCurrent status\n\nThe vault is running internally today\n\nUser deposits are not currently available\n\nPublic access will open in a future release\n\nLegacy vaults\n\nNetworkStatus\nArbitrum\nDeprecated June 13, 2025. Users have 6 months to settle debt and claim LP assets.\n\nBase\nDeprecated July 7, 2025. Collateral is being returned to wallets within 2 weeks of deprecation.","tokens":265,"crawled_at":1791193091657}
+{"id":10185,"url":"https://docs.near.org/api/rpc/providers","domain":"docs.near.org","chapter":"layer1_layer2","title":"RPC Providers - NEAR Docs","text":"NEAR Protocol exposes a JSON-RPC API for interacting with the network. You can use any of the providers below or run your own node.\n​\n\nRPC Providers\n\nFastNear maintains a comprehensive dashboard with response times for most of the available endpoints.\n​\n\nMainnet\n\nProviderEndpointPublic EndpointArchival NodeFree TierFree Tier LimitPaid Plan\nFASTNEAR\nhttps://free.rpc.fastnear.com\n✅\nPaid Only\n✅\nNot published\n✅\n\nNEAR\nhttps://archival-rpc.mainnet.near.org\n✅\n✅\nSeverely rate limited\nNot published\n❌\n\n1RPC\nhttps://1rpc.io/near\n✅\n❌\n✅\n200 req/day\n✅\n\nAll That Node\nN/A\n❌\n✅\n✅\n500K CU/day\n✅\n\nAnkr\nhttps://rpc.ankr.com/near\n❌\n❌\n✅\n~30 req/s\n✅\n\nBlockPI Network\nhttps://near.blockpi.network/v1/rpc/public\n✅\n❌\n✅\n20 req/s\n✅\n\ndRPC\nhttps://near.drpc.org\n✅\n❌\n✅\n~2,100 CU/s\n✅\n\nGetBlock\nhttps://go.getblock.io/{api-key}\n❌\n❌\n✅\n50K CU/day\n✅\n\nIntear RPC\nhttps://rpc.intea.rs\n✅\n❌\n✅\nNot published\n❌\n\nLava Network\nN/A\n❌\n✅\n❌\n—\n✅\n\nLavender.Five Nodes\nN/A\n❌\n❌\n✅\nNot published\n✅\n\nnode101\nN/A\n❌\nPaid Only\n❌\n—\n✅\n\nNodeReal\nhttps://near-mainnet.nodereal.io/v1/{api-key}\n❌\n❌\n✅\n100M CU/month\n✅\n\nNOWNodes\nhttps://near.nownodes.io/{api-key}\n❌\n❌\n✅\n100K req/month\n✅\n\nQuickNode\nN/A\n❌\n✅\n✅\n15 req/s\n✅\n\nShitzu\nhttps://rpc.shitzuapes.xyz\n✅\n❌\n✅\nNot published\n❌\n\nTatum\nN/A\n❌\n❌\n✅\n3 req/s\n✅\n\nZAN\nhttps://api.zan.top/node/v1/near/mainnet/\n✅\n❌\n✅\n~20 req/s\n✅\n\nZeeve\nN/A\n❌\n✅\n❌\n—\n✅\n\n​\n\nTestnet\n\nProviderEndpointPublic EndpointArchival NodeFree TierFree Tier LimitPaid Plan\nFASTNEAR\nhttps://test.rpc.fastnear.com\n✅\nPaid Only\n✅\nNot published\n✅\n\nNEAR\nhttps://archival-rpc.testnet.near.org\n✅\n✅\nSeverely rate limited\nNot published\n❌\n\nAll That Node\nN/A\n❌\n✅\n✅\n500K CU/day\n✅\n\ndRPC\nhttps://near-testnet.drpc.org\n✅\n❌\n✅\n~2,100 CU/s\n✅\n\nIntear RPC\nhttps://testnet-rpc.intea.rs\n✅\n❌\n✅\nNot published\n❌\n\nLava Network\nN/A\n❌\n✅\n❌\n—\n✅\n\nnode101\nN/A\n❌\nPaid Only\n❌\n—\n✅\n\nQuickNode\nN/A\n❌\n✅\n✅\n15 req/s\n✅\n\nTatum\nN/A\n❌\n❌\n✅\n3 req/s\n✅\n\nZAN\nhttps://api.zan.top/node/ws/v1/near/testnet\n❌\n❌\n✅\n~20 req/s\n✅\n\nZeeve\nN/A\n❌\n❌\n❌\n—\n✅\n\nFree Tier Limit values link to each provider’s own pricing/docs page as the source. Limits are reported in the units each provider publishes (req = requests, CU = compute units), so they are not directly comparable across providers and may change at any time — always confirm on the linked page. “Not published” means the endpoint is free but has no documented numeric limit.\n\n​\n\nMaking requests\n\nSend JSON-RPC 2.0 requests with POST to the root of the provider endpoint. Put the method and parameters in the JSON request body.\n\ncurl -X POST https://rpc.mainnet.near.org/ \\\n-H \"Content-Type: application/json\" \\\n-d '{\"jsonrpc\":\"2.0\",\"id\":\"status\",\"method\":\"status\",\"params\":[]}'\n\nRecent nearcore nodes support query-only JSON-RPC batching, but public providers can run different nearcore versions, disable batching, or apply different limits, gateways, and request policies. Confirm batch availability and limits before depending on it. Do not assume that one HTTP batch consumes one request from a quota: providers may count every entry or use a method-specific compute cost.\n\nNever load test a shared public endpoint. Run performance or high-volume batch tests only against a node you operate or an endpoint whose operator has explicitly authorized the test.\n\n​\n\nRun your own node\n\nTo run a local RPC node, follow the NEAR node documentation.\n\nTestnet tokens have no real value and can be obtained from the NEAR Faucet.\n\nWas this page helpful?","tokens":847,"crawled_at":1791193101753}
+{"id":10186,"url":"https://stack.olas.network/open-autonomy/guides/quick_start","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Quick start - Olas Stack Developer Documentation","text":"Quick start\n\nThe purpose of this guide is to provide step-by-step instructions to gain familiarity with the overall development process of the Open Autonomy framework.\n\nWe will show how to use the CLI to run a local deployment of the Hello World AI agent, which comprises:\n\n4 Docker containers implementing the 4 agent instances of the AI agent, and\n\n4 Docker containers implementing a Tendermint node for each agent instance.\n\nBefore starting this guide, ensure that your machine satisfies the framework requirements and that you have followed the set up guide. As a result you should have a Pipenv workspace folder.\n\nStep-by-step instructions\n\nNote\n\nOn MacOS and Windows, running Docker containers requires having Docker Desktop running as well. If you're using one of those operating systems, remember to start Docker Desktop\nbefore you run AI agent.\n\nFetch the Hello World AI agent from the remote registry. Within the workspace folder (not the local registry) run:\n\nautonomy fetch valory/hello_world:0.1.0:<hash> --service\n\nThis command will download the AI agent package corresponding to the specified hash from the remote IPFS registry and store it in the hello_world folder locally.\n\nBuild the Docker image of the agent blueprint:\n\ncd hello_world\nautonomy build-image\n\nThis command reads the contents of the service.yaml file, which specifies the agent blueprint(s) that compose the AI agent, together with some configuration parameters. With this information, the command builds the Docker image of the agent blueprint by downloading the appropriate components from the remote registry.\nAfter the command finishes, check that the image has been created:\n\ndocker image ls | grep hello_world\n\nPrepare and build the AI agent deployment:\n\nPrepare a keys.json file containing wallet address and the private key for each of the agent instances. This file must specify as many keys as instances you want to deploy for the AI agent.\n\nExample of a keys.json file\nWARNING: Use this file for testing purposes only. Never use the keys or addresses provided in this example in a production environment or for personal use.\n\nkeys.json[\n{\n\"address\": \"0x15d34AAf54267DB7D7c367839AAf71A00a2C6A65\",\n\"private_key\": \"0x47e179ec197488593b187f80a00eb0da91f1b9d0b13f8733639f19c30a34926a\"\n},\n{\n\"address\": \"0x9965507D1a55bcC2695C58ba16FB37d819B0A4dc\",\n\"private_key\": \"0x8b3a350cf5c34c9194ca85829a2df0ec3153be0318b5e2d3348e872092edffba\"\n},\n{\n\"address\": \"0x976EA74026E726554dB657fA54763abd0C3a0aa9\",\n\"private_key\": \"0x92db14e403b83dfe3df233f83dfa3a0d7096f21ca9b0d6d6b8d88b2b4ec1564e\"\n},\n{\n\"address\": \"0x14dC79964da2C08b23698B3D3cc7Ca32193d9955\",\n\"private_key\": \"0x4bbbf85ce3377467afe5d46f804f221813b2bb87f24d81f60f1fcdbf7cbf4356\"\n}\n]\n\nExport the environment variable ALL_PARTICIPANTS with all the agent instances' addresses:\n\nexport ALL_PARTICIPANTS='[\n\"0x15d34AAf54267DB7D7c367839AAf71A00a2C6A65\",\n\"0x9965507D1a55bcC2695C58ba16FB37d819B0A4dc\",\n\"0x976EA74026E726554dB657fA54763abd0C3a0aa9\",\n\"0x14dC79964da2C08b23698B3D3cc7Ca32193d9955\"\n]'\n\n(Optional) Export environment variables to customize the AI agent configuration.\n\nExample of exported environment variables\nexport HELLO_WORLD_STRING_0=\"Your HELLO WORLD message for Agent instance 0\"\nexport HELLO_WORLD_STRING_1=\"Your HELLO WORLD message for Agent instance 1\"\nexport HELLO_WORLD_STRING_2=\"Your HELLO WORLD message for Agent instance 2\"\nexport HELLO_WORLD_STRING_3=\"Your HELLO WORLD message for Agent instance 3\"\n\nBuild the AI agent deployment:\n\nautonomy deploy build keys.json -ltm\n\nThis command takes the configuration parameters specified inside the service.yaml and overrides them with the environment variables defined above. With the parameters defined, and the agent blueprint image ready, the output of this command is a Docker Compose deployment stored in the abci_build_* folder. The command takes care of configuring the necessary Tendermint images connected to each of the agent instances.\n\nRun the AI agent:\n\ncd abci_build_*\nautonomy deploy run\n\nThis command runs the Docker Compose deployment for the Hello World AI agent locally with four agent instances connected to four Tendermint nodes.\n\nYou can cancel the local execution at any time by pressing Ctrl+C.\n\nAt this point you should see a (verbose) output of the agent instance logs, which should look something like this:\n\n(...)\n\nabci0 | [2022-01-01 00:00:00,000] [INFO] [agent] arrived block with timestamp: 2022-00-00 00:00:00.000000\nabci0 | [2022-01-01 00:00:00,000] [INFO] [agent] current AbciApp time: 2022-00-00 00:00:00.000000\nabci0 | [2022-01-01 00:00:00,000] [INFO] Created a new local deadline for the next `begin_block` request from the Tendermint node: 2022-00-00 00:00:00.000000\nabci2 | [2022-01-01 00:00:00,000] [INFO] [agent] 'select_keeper' round is done with event: Event.DONE\nabci2 | [2022-01-01 00:00:00,000] [INFO] [agent] scheduling timeout of 30.0 seconds for event Event.ROUND_TIMEOUT with deadline 2022-00-00 00:00:00.000000\nabci2 | [2022-01-01 00:00:00,000] [INFO] [agent] Entered in the 'print_message' round for period 2\nabci2 | [2022-01-01 00:00:00,000] [INFO] [agent] Entered in the 'print_message' behaviour\nabci2 | Agent agent (address 0x976EA74026E726554dB657fA54763abd0C3a0aa9) in period 2 says: HELLO_WORLD!\nabci2 | [2022-01-01 00:00:00,000] [INFO] [agent] printed_message=Agent agent (address 0x976EA74026E726554dB657fA54763abd0C3a0aa9) in period 2 says: HELLO_WORLD!\n\n(...)\n\nThe logs of a single agent instance or Tendermint node can be inspected in another terminal with, e.g.,\n\ndocker logs <container_id> --follow\n\nwhere <container_id> refers to the Docker container ID for an agent instance\n(abci0, abci1, abci2 and abci3) or a Tendermint node (node0, node1, node2 and node3).\n\nTry to inspect the AI agent logs yourself and identify when they say the default \"HELLO_WORLD!\" message or your custom message.","tokens":1463,"crawled_at":1791193113322}
+{"id":10187,"url":"https://gov.uniswap.org/","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Uniswap Governance - Uniswap is a fully decentralized protocol for automated liquidity provision on Ethereum.","text":"Topic\n\nReplies\nViews\nActivity\n\nCommunity Governance Process Update [Jan 2023]\n\nGovernance-Meta\n\nOn December 21, 2022, the Uniswap community voted to simplify the community governance process (Snapshot poll here).\nThis post is a follow up to that proposal, summarizing the new governance process, and covering a list…\n\n4\n\n38245\n\nJanuary 9, 2026\n\nUniswap Governance Forum Rules\n\nUncategorized\n\nThis forum is dedicated to discussions on Uniswap governance. Relevant topics include:\n\nGovernance Proposals\nProposal Discussions\nDelegation Pitches\nSite Feedback\n\nThis is not the place for:\n\nUNI price discussion\nGener…\n\n0\n\n16461\n\nSeptember 21, 2020\n\nUniswap Foundation Security Fund (UFSF): Announcement Thread\n\nUncategorized\n\n41\n\n1964\n\nOctober 2, 2026\n\n[Temp Check] Protocol Fee Expansion: Arc\n\nTemperature Check\n\n5\n\n463\n\nOctober 1, 2026\n\n[Temp Check] Rotate Sentinel Addresses on the DUNI-Owned Uniswap Earn Vaults\n\nTemperature Check\n\n6\n\n252\n\nOctober 1, 2026\n\nAxia Network Delegate Platform\n\nDelegation Pitch\n\n11\n\n333\n\nOctober 3, 2026\n\nUniswap-Arbitrum Delegate Program (UADP) Communication Thread\n\nDelegation Pitch\n\n39\n\n6010\n\nSeptember 29, 2026\n\nPGov Delegate Platform\n\nDelegation Pitch\n\n73\n\n6457\n\nSeptember 27, 2026\n\n[RFC] Native Execution Privacy in the Uniswap Interface via v4 Hooks and UniswapX\n\nRequests for Comment\n\n16\n\n705\n\nAugust 29, 2026\n\nURC-2: Custom Accounting Hook Swap Event\n\nURC Discussion\n\n1\n\n171\n\nAugust 25, 2026\n\n[RFC] Deploy Uniswap V3 on Gensyn\n\nRequests for Comment\n\n5\n\n454\n\nAugust 25, 2026\n\nUniswap Deployment - Guideline\n\nGovernance-Meta\n\n2\n\n930\n\nAugust 21, 2026\n\n[Temp Check] Activate v4 Protocol Fees\n\nTemperature Check\n\n24\n\n2782\n\nAugust 18, 2026\n\n[RFC] Web4 Autonomous State Engines on Unichain: Utilizing ERC-6551 & Sovereign ERC-721 Force Transfers for Dynamic Asset Orchestration\n\nRequests for Comment\n\n0\n\n94\n\nAugust 4, 2026\n\n[RFC] Four for V4\n\nRequests for Comment\n\n7\n\n469\n\nJuly 24, 2026\n\n[Discussion] Privacy-Preserving MiCA Compliance — How Is Uniswap Handling EU Users?\n\nRequests for Comment\n\n19\n\n535\n\nJuly 23, 2026\n\n$UNI staking for IL reduction\n\nRequests for Comment\n\n3\n\n3176\n\nJuly 23, 2026\n\nCuria Delegate Platform\n\nDelegation Pitch\n\n53\n\n2385\n\nJuly 23, 2026\n\n[RFC - Update] Deploy Uniswap v3 (1 / 0.3 / 0.05 / 0.01) on BNB Chain (Binance)\n\nRequests for Comment\n\n101\n\n45661\n\nJuly 22, 2026\n\n[Temp Check] Protocol Fee Expansion: Robinhood Chain\n\nTemperature Check\n\n3\n\n984\n\nJuly 22, 2026\n\nCodeknight Delegate Platform\n\nDelegation Pitch\n\n7\n\n270\n\nJuly 22, 2026\n\nURC-4: Active Liquidity Framework Hook Interface\n\nURC Discussion\n\n2\n\n208\n\nJuly 20, 2026\n\nDAOplomats Delegation Platform\n\nDelegation Pitch\n\n49\n\n2913\n\nJuly 18, 2026\n\nArgonaut Delegate Platform\n\nDelegation Pitch\n\n63\n\n1821\n\nJuly 11, 2026\n\nRFC : Tokenomics overhaul : hard-capping supply via auto burn, pivoting unification to staking distribution and staking DAO treasury reserves\n\nUncategorized\n\n3\n\n298\n\nJuly 10, 2026\n\nAtiselsts.eth Delegate Platform\n\nDelegation Pitch\n\n32\n\n4670\n\nJuly 9, 2026\n\n[Temp Check] - Update Crosschain Governance Parameters for Avalanche, MegaETH, Soneium, and X Layer\n\nRequests for Comment\n\n5\n\n271\n\nJuly 9, 2026\n\nFoundation inspection request — Cantina bounty mediation policy enforcement (finding #784, 29-day stalled dispute)\n\nRequests for Comment\n\n0\n\n172\n\nJuly 4, 2026\n\nURC-3: Hook TVL and Effective Liquidity Reporting\n\nURC Discussion\n\n0\n\n134\n\nJune 30, 2026\n\nURC-1: Uniswap Request for Comment Process\n\nURC Discussion\n\n0\n\n88\n\nJune 29, 2026\n\nnext page →","tokens":867,"crawled_at":1791193116078}
+{"id":10188,"url":"https://docs.synthetix.io/deposits-withdrawals/withdrawing","domain":"docs.synthetix.io","chapter":"defi_protocols","title":"Withdrawing Collateral – Synthetix","text":"Last updated: Jul 23, 2026\n\nYou can withdraw collateral that is not required for open positions, USDT debt, or account-health limits. In multicollateral accounts, each asset is withdrawn separately.\n\nAvailable margin\n\nYou can only withdraw available margin, collateral not currently required to meet the margin requirements of your open positions.\n\navailable_margin = adjusted_account_value - required_margin\n\nAdjusted Account Value includes collateral haircuts and PnL effects. The final max withdrawal also applies asset balance, the USDT cap, LTV and debt limits, fees, and any active limits shown in the app.\n\nIf you have no open positions and no USDT debt, most of your balance is generally available to withdraw, subject to those checks.\n\nHow to withdraw\n\n1. Open the Withdraw Window\n\nMake sure you are connected to the Synthetix Exchange.\n\nOpen the Withdrawal window using one of the following options:\n\nClick your wallet in the top-right corner, then select Withdraw from the Account sidebar.\n\nOpen the Portfolio page and select Withdraw.\n\nOpen the Balances tab in the Portfolio table and select Withdraw.\n\nOpen Withdraw from the Account sidebar after clicking your wallet in the top-right corner, or use Withdraw from the Portfolio page or Balances tab.\n\n2. Enter the Withdrawal Amount\n\nEnter the amount you want to withdraw, up to the maximum available amount displayed.\n\nReview any applicable withdrawal fees.\n\nClick Withdraw.\n\nEnter the withdrawal amount, review the fee and amount received, then click Withdraw.\n\n3. Confirm the Withdrawal\n\nConfirm the transaction in your wallet.\n\nWait for the transaction to be confirmed on Ethereum Mainnet.\n\nYour wallet and Exchange account balances will update once the transaction has been confirmed.\n\nWithdrawing with open positions\n\nYou can withdraw available margin while holding open positions. However:\n\nWithdrawing reduces your health ratio and moves your liquidation price closer to the current market price.\n\nYou cannot withdraw collateral that would bring the account below maintenance margin.\n\nNon-USDT collateral price moves can reduce your withdrawable amount even if your position PnL has not changed.\n\nWithdrawing USDT with non-USDT collateral\n\nUSDT withdrawals are capped by both account health and the USDT available to send.\n\nYour maximum USDT withdrawal can include:\n\nHeld USDT balance.\n\nPositive unrealized PnL that can support a USDT withdrawal while the position remains open.\n\nNon-USDT collateral value supports margin and trading, but it does not become withdrawable USDT unless you first convert it through Swap or otherwise receive USDT settlement from trading.\n\nDebt and LTV constraints\n\nIf your USDT balance is negative after positive unrealized PnL is considered, the account has USDT debt. That debt is backed by non-USDT collateral.\n\nWithdrawal amounts can be reduced to preserve:\n\nRequired margin for open positions.\n\nThe USDT cap for USDT withdrawals.\n\nLTV and LLTV limits for non-USDT collateral backing USDT debt.\n\nAny tier-based Max Borrow limit.\n\nYour max withdrawal can be zero even when an asset has a balance. Common reasons include open positions reserving margin, USDT debt requiring collateral to stay in the account, or the asset fully backing debt with no spare margin budget.\n\nTo improve withdrawable amounts, consider reducing positions, swapping collateral to USDT to repay debt, or depositing additional collateral.\n\nWithdrawal fees\n\nWithdrawals can have a per-asset withdrawal fee. The fee is deducted from the amount received and is shown before you confirm.\n\nEthereum Mainnet gas is paid in ETH by your wallet for on-chain withdrawal transactions.\n\nTransfers between subaccounts\n\nMoving collateral between subaccounts follows the same type of availability checks as withdrawals. The source subaccount must keep enough collateral for open positions, USDT debt limits, and LTV constraints.\n\nCollateral in one subaccount does not support positions in another subaccount. See Sub-Account for details.\n\nWithdrawal delays\n\nWithdrawals are processed on-chain with no additional delay beyond transaction confirmation. There is no withdrawal queue or waiting period.\n\nSee also\n\nMulticollateral Margin - USDT debt, Swap, and auto-exchange.\n\nLeverage & Margin - account value, haircuts, and margin requirements.\n\nFees - withdrawal, Swap, auto-exchange, and gas fees.\n\nLiquidations - why withdrawing close to maintenance margin is risky.","tokens":1107,"crawled_at":1791193119007}
+{"id":10189,"url":"https://www.metaplex.com/docs/smart-contracts/token-metadata/print","domain":"www.metaplex.com","chapter":"docs","title":"Printing Editions | Token Metadata","text":"Token Metadata is a legacy program. It remains supported, but is not recommended for new projects. Use Core instead.\n\nEvery NFT has the potential to be printed as multiple editions when its Master Edition account is configured accordingly. On this page, we'll learn how to create a printable NFT and how to print editions from it.\nPrintable NFTs\nThe owner of a printable NFT can print as many editions as they want from it as long as its maximum supply has not been reached.\nEvery Non-Fungible asset — i.e. NonFungible and ProgrammableNonFungible token standards — can be a printable NFT when created. This is done by configuring the Max Supply attribute of the asset's Master Edition account. This attribute is optional and can have one of the following values:\nNone: The NFT does not have a fixed supply. In other words, the NFT is printable and has an unlimited supply.\nSome(x): The NFT has a fixed supply of x editions.When x = 0, this means the NFT is not printable.\nWhen x > 0, this means the NFT is printable and has a fixed supply of x editions.\n\nWhenever a new printed edition is created from a printable NFT, a few things happen:\nA brand new edition NFT is created and its data matches the original NFT. The only difference is that the printed edition uses a different token standard than the original NFT.For a NonFungible asset, the printed editions use the NonFungibleEdition token standard.\nFor a ProgrammableNonFungible asset, the printed editions use the ProgrammableNonFungibleEdition token standard.\n\nInstead of using a Master Edition account, the new edition NFT uses an Edition account which keeps track of its edition number and its parent NFT by storing the address of its parent's Master Edition account.\nThe Supply attribute of the Master edition account is incremented by 1. When the Supply attribute reaches the Max Supply attribute, the NFT is no longer printable.\nOR\n\nWallet Account\n\nOwner: System Program\n\nToken Account\n\nOwner: Token Program\n\nAmount = 1\n\nMint Account\n\nOwner: Token Program\n\nMint Authority = Edition\n\nSupply = 1\n\nDecimals = 0\n\nFreeze Authority = Edition\n\nPDA\n\nMetadata Account\n\nOwner: Token Metadata Program\n\nPDA\n\nMaster Edition Account\n\nOwner: Token edition Program\n\nKey = MasterEditionV2\n\nSupply\n\nMax Supply\n\nEdition Account\n\nOwner: Token edition Program\n\nKey = EditionV1\n\nParent\n\nEdition\n\nReact Flow\nPress enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.\nPress enter or space to select an edge. You can then press delete to remove it or escape to cancel.\n\nSetting up a Master Edition NFT\nTo create a printable NFT, we need to configure the Print Supply attribute of the Create instruction of the Token Metadata program. This will configure the Max Supply attribute of the Master Edition account as seen in the previous section. This attribute can be:\nZero: The NFT is not printable.\nLimited(x): The NFT is printable and has a fixed supply of x editions.\nUnlimited: The NFT is printable and has an unlimited supply.\nHere is how you can use our SDKs to create a printable NFT.\n\n1import { percentAmount, generateSigner } from '@metaplex-foundation/umi';\n\n2import { createNft, printSupply } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4// Assuming umi is set up with mplTokenMetadata plugin\n\n5\n\n6const mint = generateSigner(umi);\n\n7\n\n8await createNft(umi, {\n\n9 mint,\n\n10 name: 'My Master Edition NFT',\n\n11 uri: 'https://example.com/my-nft.json',\n\n12 sellerFeeBasisPoints: percentAmount(5.5),\n\n13 printSupply: printSupply('Limited', [100]), // Or printSupply('Unlimited')\n\n14}).sendAndConfirm(umi);\n\n15\n\n16console.log('Master Edition NFT created:', mint.publicKey);\n\n1import { generateKeyPairSigner } from '@solana/kit';\n\n2import { createNft, PrintSupply } from '@metaplex-foundation/mpl-token-metadata-kit';\n\n3\n\n4// Assuming rpc, rpcSubscriptions, sendAndConfirm, and authority are set up\n\n5\n\n6const mint = await generateKeyPairSigner();\n\n7\n\n8// Create a Master Edition NFT with limited supply of 100 prints\n\n9const [createIx, mintIx] = await createNft({\n\n10 mint,\n\n11 authority,\n\n12 payer: authority,\n\n13 name: 'My Master Edition NFT',\n\n14 uri: 'https://example.com/my-nft.json',\n\n15 sellerFeeBasisPoints: 550, // 5.5%\n\n16 tokenOwner: authority.address,\n\n17 printSupply: PrintSupply.Limited(100), // Or PrintSupply.Unlimited\n\n18});\n\n19\n\n20await sendAndConfirm({\n\n21 instructions: [createIx, mintIx],\n\n22 payer: authority,\n\n23});\n\n24\n\n25console.log('Master Edition NFT created:', mint.address);\n\nPrinting Editions from the Master Edition NFT\nOnce we have a printable NFT that has not reached its Max Supply, we can print new editions from it. This is done by calling the Print instruction of the Token Metadata program. This instruction accepts the following attributes:\nMaster Edition Mint: The address of the printable NFT's Mint account.\nEdition Mint: The address of the new edition NFT's Mint account. This is typically a newly generated Signer since the account will be created by the instruction if it does not exist.\nMaster Token Account Owner: The owner of the printable NFT as a Signer. Only the owner of a printable NFT can print new editions from it.\nEdition Token Account Owner: The address of the new edition NFT's owner\nEdition Number: The edition number of the new edition NFT to print. This is typically the current Supply of the Master Edition account plus 1.\nToken Standard: The token standard of the printable NFT. This can be NonFungible or ProgrammableNonFungible.\nHere is how you can use our SDKs to print a new edition from a printable NFT.\n\n1import { generateSigner } from '@metaplex-foundation/umi';\n\n2import {\n\n3 printV1,\n\n4 fetchMasterEditionFromSeeds,\n\n5} from '@metaplex-foundation/mpl-token-metadata';\n\n6\n\n7// Assuming umi, masterEditionMint, originalOwner, and ownerOfThePrintedEdition are set up\n\n8\n\n9const editionMint = generateSigner(umi);\n\n10\n\n11// (Optional) Fetch the master edition account to mint the next edition number.\n\n12const masterEdition = await fetchMasterEditionFromSeeds(umi, {\n\n13 mint: masterEditionMint,\n\n14});\n\n15\n\n16await printV1(umi, {\n\n17 masterTokenAccountOwner: originalOwner,\n\n18 masterEditionMint,\n\n19 editionMint,\n\n20 editionTokenAccountOwner: ownerOfThePrintedEdition,\n\n21 editionNumber: masterEdition.supply + 1n,\n\n22 tokenStandard: TokenStandard.NonFungible,\n\n23}).sendAndConfirm(umi);\n\n24\n\n25console.log('Edition printed:', editionMint.publicKey);\n\n1import { generateKeyPairSigner } from '@solana/kit';\n\n2import {\n\n3 getPrintV1InstructionAsync,\n\n4 fetchMasterEdition,\n\n5 findMasterEditionPda,\n\n6 TokenStandard,\n\n7} from '@metaplex-foundation/mpl-token-metadata-kit';\n\n8\n\n9// Assuming rpc, rpcSubscriptions, sendAndConfirm, originalOwner are set up\n\n10\n\n11const masterEditionMintAddress = 'masterEditionMintAddress...';\n\n12const ownerOfThePrintedEdition = 'ownerAddress...';\n\n13const editionMint = await generateKeyPairSigner();\n\n14\n\n15// Fetch the master edition account to mint the next edition number\n\n16const [masterEditionPda] = await findMasterEditionPda({ mint: masterEditionMintAddress });\n\n17const masterEdition = await fetchMasterEdition(rpc, masterEditionPda);\n\n18\n\n19// Print a new edition\n\n20const printIx = await getPrintV1InstructionAsync({\n\n21 masterTokenAccountOwner: originalOwner,\n\n22 masterEditionMint: masterEditionMintAddress,\n\n23 editionMint,\n\n24 editionTokenAccountOwner: ownerOfThePrintedEdition,\n\n25 editionNumber: masterEdition.data.supply + 1n,\n\n26 tokenStandard: TokenStandard.NonFungible,\n\n27 payer: originalOwner,\n\n28});\n\n29\n\n30await sendAndConfirm({\n\n31 instructions: [printIx],\n\n32 payer: originalOwner,\n\n33});\n\n34\n\n35console.log('Edition printed:', editionMint.address);","tokens":1927,"crawled_at":1791193138450}
+{"id":10190,"url":"https://docs.near.org/api-reference/post-experimental_receipt_to_tx","domain":"docs.near.org","chapter":"layer1_layer2","title":"Post experimental receipt to tx - NEAR Docs","text":"cURL\n\ncurl --request POST \\\n--url https://api.example.com/EXPERIMENTAL_receipt_to_tx \\\n--header 'Content-Type: application/json' \\\n--data '\n{\n\"method\": \"EXPERIMENTAL_receipt_to_tx\",\n\"params\": {\n\"receipt_id\": \"<string>\",\n\"block_height\": 1,\n\"shard_id\": 1,\n\"window\": 1\n},\n\"id\": \"dontcare\",\n\"jsonrpc\": \"2.0\"\n}\n'\n\nconst options = {\nmethod: 'POST',\nheaders: {'Content-Type': 'application/json'},\nbody: JSON.stringify({\nmethod: 'EXPERIMENTAL_receipt_to_tx',\nparams: {receipt_id: '<string>', block_height: 1, shard_id: 1, window: 1},\nid: 'dontcare',\njsonrpc: '2.0'\n})\n};\n\nfetch('https://api.example.com/EXPERIMENTAL_receipt_to_tx', options)\n.then(res => res.json())\n.then(res => console.log(res))\n.catch(err => console.error(err));\n\nimport requests\n\nurl = \"https://api.example.com/EXPERIMENTAL_receipt_to_tx\"\n\npayload = {\n\"method\": \"EXPERIMENTAL_receipt_to_tx\",\n\"params\": {\n\"receipt_id\": \"<string>\",\n\"block_height\": 1,\n\"shard_id\": 1,\n\"window\": 1\n},\n\"id\": \"dontcare\",\n\"jsonrpc\": \"2.0\"\n}\nheaders = {\"Content-Type\": \"application/json\"}\n\nresponse = requests.post(url, json=payload, headers=headers)\n\nprint(response.text)\n\n{\n\"result\": {\n\"sender_account_id\": \"<string>\",\n\"transaction_hash\": \"<string>\"\n},\n\"id\": \"<string>\",\n\"jsonrpc\": \"<string>\"\n}\n\nPOST\n/\nEXPERIMENTAL_receipt_to_tx\n\ncURL\n\ncurl --request POST \\\n--url https://api.example.com/EXPERIMENTAL_receipt_to_tx \\\n--header 'Content-Type: application/json' \\\n--data '\n{\n\"method\": \"EXPERIMENTAL_receipt_to_tx\",\n\"params\": {\n\"receipt_id\": \"<string>\",\n\"block_height\": 1,\n\"shard_id\": 1,\n\"window\": 1\n},\n\"id\": \"dontcare\",\n\"jsonrpc\": \"2.0\"\n}\n'\n\nconst options = {\nmethod: 'POST',\nheaders: {'Content-Type': 'application/json'},\nbody: JSON.stringify({\nmethod: 'EXPERIMENTAL_receipt_to_tx',\nparams: {receipt_id: '<string>', block_height: 1, shard_id: 1, window: 1},\nid: 'dontcare',\njsonrpc: '2.0'\n})\n};\n\nfetch('https://api.example.com/EXPERIMENTAL_receipt_to_tx', options)\n.then(res => res.json())\n.then(res => console.log(res))\n.catch(err => console.error(err));\n\nimport requests\n\nurl = \"https://api.example.com/EXPERIMENTAL_receipt_to_tx\"\n\npayload = {\n\"method\": \"EXPERIMENTAL_receipt_to_tx\",\n\"params\": {\n\"receipt_id\": \"<string>\",\n\"block_height\": 1,\n\"shard_id\": 1,\n\"window\": 1\n},\n\"id\": \"dontcare\",\n\"jsonrpc\": \"2.0\"\n}\nheaders = {\"Content-Type\": \"application/json\"}\n\nresponse = requests.post(url, json=payload, headers=headers)\n\nprint(response.text)\n\n{\n\"result\": {\n\"sender_account_id\": \"<string>\",\n\"transaction_hash\": \"<string>\"\n},\n\"id\": \"<string>\",\n\"jsonrpc\": \"<string>\"\n}\n\nBody\napplication/json\n\n​\n\nmethod\nenum<string>\nrequired\n\nAvailable options: EXPERIMENTAL_receipt_to_tx\n\n​\n\nparams\nRpcReceiptToTxRequest · object\nrequired\n\nShow child attributes\n\n​\n\nid\nstring\ndefault:dontcare\n\nJSON-RPC request id. Auto-populated; can be any string.\n\n​\n\njsonrpc\nenum<string>\ndefault:2.0\n\nJSON-RPC protocol version. Always 2.0.\n\nAvailable options: 2.0\n\nResponse\n200 - application/json\n\nJsonRpcResponse_for_RpcReceiptToTxResponse_and_RpcReceiptToTxError\n\nJsonRpcResponse_for_RpcReceiptToTxResponse_and_RpcReceiptToTxError\n\n​\n\nresult\nobject\nrequired\n\nShow child attributes\n\n​\n\nid\nstring\nrequired\n\n​\n\njsonrpc\nstring\nrequired\n\nWas this page helpful?","tokens":791,"crawled_at":1791193120086}
+{"id":10191,"url":"https://stack.olas.network/open-autonomy/guides/publish_mint_packages","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Publish and mint packages - Olas Stack Developer Documentation","text":"Publish and mint packages\n\nOnce you have finished developing and testing your AI agent locally, you can publish your software packages to the remote registry and mint them in the Olas Protocol. Minting software packages will produce a representation of them on-chain, in the form of NFTs.\n\nPart of the development process covered in this guide\n\nYou can mint packages using the Olas Protocol web app or using the Open Autonomy CLI.\n\nWhat will you learn\n\nThis guide covers step 6 of the development process. You will learn how to publish the software packages developed in the local registry (components, agent blueprints and AI agents) to the remote registry, and how to mint them in the Olas Protocol.\n\nYou must ensure that your machine satisfies the framework requirements, you have set up the framework, and you have a local registry populated with some default components. As a result you should have a Pipenv workspace folder with an initialized local registry (./packages) in it.\n\nPublish packages to the remote registry\n\nThe components developed in the local registry have to be referenced in the index file (./packages/packages.json) under the dev section. For example:\n\npackages.json{\n\"dev\": {\n\"service/your_name/your_ai_agent/0.1.0\": \"bafybei0000000000000000000000000000000000000000000000000000\",\n\"agent/your_name/your_agent_blueprint/0.1.0\": \"bafybei0000000000000000000000000000000000000000000000000000\",\n\"skill/your_name/your_fsm_app_abci/0.1.0\": \"bafybei0000000000000000000000000000000000000000000000000000\"\n\n},\n\"third_party\": {\n\n}\n}\n\nYou can now have your components published on the remote registry as follows:\n\nautonomy packages lock\nautonomy push-all\n\nMint packages in the Autonolas Protocol\n\nComponents and Agent Blueprints are minted on ETH mainnet only, and then used as \"foreign\" IDs in AI Agents on any chosen network, since off-chain agent instances read from any chain and unpack configs and codes following IPFS hashes.\nTo mint a software package, all the packages it depends on must be minted first. For example, you need that an agent blueprint be minted before minting the corresponding AI agent, and you need that the agent components are minted before minting the agent blueprint. You will need:\n\nAn address associated to either\n\na crypto wallet (e.g., Metamask or a cold wallet), or\n\na multisig contract (like Safe) which allows to connect via Wallet Connect.\n\nIn either case, the address must have funds for the chain that you wish to mint the package on.\n\nThe hash of the package that you want to mint, and which must have been published into a remote registry.\n\nAn NFT image URL. This image will be used to represent the minted NFT for the package on marketplaces such as OpenSea. You can use this sample image URL for testing purposes.\n\nTip\n\nIf you are a new user of the framework, we recommend that you follow the instructions under the section Testing the Autonolas Protocol locally.\n\nUsing the Autonolas Protocol web app\n\nThe Olas Protocol web app is a front-end that provides an intuitive GUI to mint components, agent blueprints and AI agent, and manage the life cycle of AI agents in the Autonolas Protocol.\n\nWe refer to the Autonolas Protocol docs, where you can find instructions on how to mint components (including the FSM App skill), agent blueprints, and AI agents.\n\nUsing the Open Autonomy CLI\n\nYou can also mint packages using the autonomy mint command.\n\nPrepare the key file. Prepare a file with the private key of the account used to mint the transactions.\n\necho -n <private_key_hexadecimal> > minting_key.txt\n\nThis account will pay the transaction fees for the minted NFTs.\n\nMint the packages. Mint the components, agent blueprint and AI agent NFTs, indicating the owner address of each one. You can declare any address you want as owner for each component. Recall that all the dependencies of a given component must be minted beforehand.\n\nMint components:\n\nautonomy mint --use-ethereum protocol --key minting_key.txt --nft <nft_ipfs_hash_or_image_path> --owner <owner_address> <component_path>\nautonomy mint --use-ethereum connection --key minting_key.txt --nft <nft_ipfs_hash_or_image_path> --owner <owner_address> <component_path>\nautonomy mint --use-ethereum contract --key minting_key.txt --nft <nft_ipfs_hash_or_image_path> --owner <owner_address> <component_path>\nautonomy mint --use-ethereum skill --key minting_key.txt --nft <nft_ipfs_hash_or_image_path> --owner <owner_address> <component_path>\n\nHere the <component_path> is the path to the component folder, e.g., ./packages/valory/skills/fsm_app_abci/.\n\nMint the agent blueprint:\n\nautonomy mint --use-ethereum agent --key minting_key.txt --nft <nft_ipfs_hash_or_image_path> --owner <owner_address> <agent_blueprint_path>\n\nHere the <agent_blueprint_path> is the path to the agent blueprint folder, e.g., ./packages/valory/agents/your_agent_blueprint/.\n\nMint the AI agent:\n\nautonomy mint --use-ethereum service --key minting_key.txt --nft <nft_ipfs_hash_or_image_path> --owner <owner_address> --agent-id <agent_blueprint_id> --number-of-slots <number_of_slots> --cost-of-bond <cost_of_bond_in_wei> --threshold <threshold> <ai_agent_path>\n\nHere the <ai_agent_path> is the path to the AI agent folder, e.g., ./packages/valory/services/your_ai_agent/.\n\nRefer to the documentation on the autonomy mint command to learn more about its parameters and options.\n\nTesting the Autonolas Protocol locally\n\nIf you are new to the framework, we provide a way to help you test the Olas Protocol without spending any token on a real chain.\nNamely, we provide a Docker image (valory/autonolas-registries) containing a local blockchain (a Hardhat node) with the Autonolas Protocol registry contracts deployed on it. The image also contains a few testing keys and addresses.\n\nBelow we show the steps to register the hello_world AI agent and all its required packages.\n\nStart the local blockchain. On a separate terminal, run the valory/autonolas-registries Docker image:\n\ndocker run -p 8545:8545 valory/autonolas-registries:latest\n\nYou will see a message indicating a number of funded, testing keys and addresses for this chain.\n\nImportant\n\nWARNING: Use these keys for testing purposes only. Never use the keys or addresses provided in this example in a production environment or for personal use.\n\nConfigure your browser and wallet. To explore the status of the protocol in this local blockchain using the Olas Protocol web app, you need to configure a software wallet in your browser, for example Metamask. Add a new chain with the following parameters:\n\nRPC URL: http://localhost:8545\n\nChain ID: 31337\n\nCurrency symbol: GO\n\nImport an account using one of the private keys listed above. For example, 0x59c6995e998f97a5a0044966f0945389dc9e86dae88c7a8412f4603b6b78690d.\n\nPrepare the key file. Prepare a file with the private key of the account used to mint the transactions.\n\necho -n 0x59c6995e998f97a5a0044966f0945389dc9e86dae88c7a8412f4603b6b78690d > minting_key.txt\n\nThis account will pay the transaction fees for the minted NFTs.\n\nMint the packages. Mint the components, agent blueprint and AI agent NFTs, indicating the owner address of each one.\nFor simplicity, we are indicating the address 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 as owner for all the components, which corresponds to the private key above. However, you can declare any address as owner for each component.\n\nAlso, we are using this sample image URL as the NFT image for all the components. You can use any URL pointing to an image, or a local image file.\n\nImportant\n\nThe commands shown below assume a fresh run of the valory/autonolas-registries Docker image. If you have a different number of components minted in your local blockchain, the required token IDs might be different in your case.\n\nYou can always kill and restart a fresh run of the valory/autonolas-registries Docker image if you experience any issue.\n\nAlso, note that the example below is exhaustive. In a real scenario you might reuse already minted components in the Autonolas Protocol.\n\n# Mint components that don't have dependencies\nautonomy mint --use-local contract --key minting_key.txt --nft Qmbh9SQLbNRawh9Km3PMEDSxo77k1wib8fYZUdZkhPBiev --owner 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 ./packages/valory/contracts/service_registry/\nautonomy mint --use-local protocol --key minting_key.txt --nft Qmbh9SQLbNRawh9Km3PMEDSxo77k1wib8fYZUdZkhPBiev --owner 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 ./packages/open_aea/protocols/signing/\nautonomy mint --use-local protocol --key minting_key.txt --nft Qmbh9SQLbNRawh9Km3PMEDSxo77k1wib8fYZUdZkhPBiev --owner 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 ./packages/valory/protocols/abci/\nautonomy mint --use-local protocol --key minting_key.txt --nft Qmbh9SQLbNRawh9Km3PMEDSxo77k1wib8fYZUdZkhPBiev --owner 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 ./packages/valory/protocols/acn/\nautonomy mint --use-local protocol --key minting_key.txt --nft Qmbh9SQLbNRawh9Km3PMEDSxo77k1wib8fYZUdZkhPBiev --owner 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 ./packages/valory/protocols/contract_api/\nautonomy mint --use-local protocol --key minting_key.txt --nft Qmbh9SQLbNRawh9Km3PMEDSxo77k1wib8fYZUdZkhPBiev --owner 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 ./packages/valory/protocols/http/\nautonomy mint --use-local protocol --key minting_key.txt --nft Qmbh9SQLbNRawh9Km3PMEDSxo77k1wib8fYZUdZkhPBiev --owner 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 ./packages/valory/protocols/ipfs/\nautonomy mint --use-local protocol --key minting_key.txt --nft Qmbh9SQLbNRawh9Km3PMEDSxo77k1wib8fYZUdZkhPBiev --owner 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 ./packages/valory/protocols/ledger_api/\nautonomy mint --use-local protocol --key minting_key.txt --nft Qmbh9SQLbNRawh9Km3PMEDSxo77k1wib8fYZUdZkhPBiev --owner 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 ./packages/valory/protocols/tendermint/\n\n# Mint components with dependencies\nautonomy mint --use-local connection --key minting_key.txt --nft Qmbh9SQLbNRawh9Km3PMEDSxo77k1wib8fYZUdZkhPBiev --owner 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 ./packages/valory/connections/abci/\nautonomy mint --use-local connection --key minting_key.txt --nft Qmbh9SQLbNRawh9Km3PMEDSxo77k1wib8fYZUdZkhPBiev --owner 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 ./packages/valory/connections/http_client/\nautonomy mint --use-local connection --key minting_key.txt --nft Qmbh9SQLbNRawh9Km3PMEDSxo77k1wib8fYZUdZkhPBiev --owner 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 ./packages/valory/connections/ipfs/\nautonomy mint --use-local connection --key minting_key.txt --nft Qmbh9SQLbNRawh9Km3PMEDSxo77k1wib8fYZUdZkhPBiev --owner 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 ./packages/valory/connections/ledger/\nautonomy mint --use-local connection --key minting_key.txt --nft Qmbh9SQLbNRawh9Km3PMEDSxo77k1wib8fYZUdZkhPBiev --owner 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 ./packages/valory/connections/p2p_libp2p_client/\nautonomy mint --use-local skill --key minting_key.txt --nft Qmbh9SQLbNRawh9Km3PMEDSxo77k1wib8fYZUdZkhPBiev --owner 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 ./packages/valory/skills/abstract_abci/\nautonomy mint --use-local skill --key minting_key.txt --nft Qmbh9SQLbNRawh9Km3PMEDSxo77k1wib8fYZUdZkhPBiev --owner 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 ./packages/valory/skills/abstract_round_abci/\nautonomy mint --use-local skill --key minting_key.txt --nft Qmbh9SQLbNRawh9Km3PMEDSxo77k1wib8fYZUdZkhPBiev --owner 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 ./packages/valory/skills/hello_world_abci/\n\n# Mint the agent blueprint\nautonomy mint --use-local agent --key minting_key.txt --nft Qmbh9SQLbNRawh9Km3PMEDSxo77k1wib8fYZUdZkhPBiev --owner 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 ./packages/valory/agents/hello_world/\n\n# Mint the AI agent\nautonomy mint --use-local service --key minting_key.txt --nft Qmbh9SQLbNRawh9Km3PMEDSxo77k1wib8fYZUdZkhPBiev --owner 0x70997970C51812dc3A010C7d01b50e0d17dc79C8 --agent-id 3 --number-of-slots 4 --cost-of-bond 10000000000000000 --threshold 3 ./packages/valory/services/hello_world/\n\nExplore the protocol using the web app. Use the Olas Protocol web app to explore the packages that you have minted. Ensure that you are connected to the local blockchain configured in Step 2 above through Metamask.\n\nImportant\n\nOnce you have finished working with the local blockchain, we recommend that you connect your Metamask plugin to a regular chain (e.g., Ethereum). This is to prevent Metamask from getting stuck searching for the local blockchain once the Docker image valory/autonolas-registries is terminated.","tokens":3141,"crawled_at":1791193134741}
+{"id":10192,"url":"https://gov.uniswap.org/c/consensus-check/10","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Consensus Check - Uniswap Governance","text":"Consensus Check\n\nTopic\n\nReplies\nViews\nActivity\n\nREADME: How to Create a Consensus Check\n\n3\n\n2002\n\nJuly 25, 2022\n\n[RFC] Steps for Uniswap to take in light of research on how intent-based protocols are shaping on-chain liquidity\n\n3\n\n603\n\nSeptember 18, 2024\n\nConsensus Check - Should the proposal threshold be lowered?\n\n3\n\n3086\n\nJune 16, 2021\n\nConsensus Check — [Uniswap DAO can help 80K UNI to Turkey to relief after the big earthquake disaster]\n\n0\n\n2270\n\nFebruary 17, 2023\n\nConsensus Check - Should Uniswap incentivize Liquidity on Optimism and Arbitrum\n\n18\n\n8599\n\nOctober 28, 2022\n\n[Consensus Check] \"Fee Switch\" Pilot\n\n16\n\n8691\n\nAugust 18, 2022\n\n[Consensus Check] Create the Uniswap Foundation\n\n0\n\n5439\n\nAugust 10, 2022\n\nConsensus Check - Enable 1bp Fee Tier on UniswapV3 Optimism(L2)\n\n1\n\n3936\n\nJune 24, 2022\n\n[Consensus Check] Should Uniswap v3 be deployed to Gnosis Chain?\n\n2\n\n3899\n\nApril 15, 2022\n\n[Consensus Check] Deploy Uniswap v3 to Moonbeam\n\n1\n\n3633\n\nApril 6, 2022\n\nConsensus Check — Uniswap x Celo: Green Pool for Treasury Proposal\n\n9\n\n5160\n\nMarch 28, 2022\n\nConsensus Check - Should Uniswap governance contribute funding to the Nomic Foundation?\n\n5\n\n2621\n\nMarch 11, 2022\n\nConsensus Check - Should Uniswap Provide Voltz with v3 Additional Use Grant\n\n1\n\n2967\n\nFebruary 7, 2022\n\nConsensus Check - Add 1 Basis Point Fee Tier\n\n6\n\n5333\n\nOctober 30, 2021\n\nConsensus Check - Begin Uniswap Liquidity Program v0.1\n\n9\n\n4844\n\nSeptember 10, 2021\n\nConsensus Check - Support Stable UNI\n\n15\n\n3812\n\nSeptember 7, 2021\n\nConsensus Check - Donate $50M worth of UNI to Chris Blec to leave DeFi for good\n\n4\n\n6104\n\nAugust 26, 2021\n\nConsensus Check: Upgrade Governance Contract to Governor Bravo\n\n2\n\n3119\n\nAugust 24, 2021\n\nConsensus Check - ABOLISH Delegates and change the UNI Governance Voting System\n\n9\n\n3300\n\nAugust 11, 2021\n\nConsensus Check - Create Uniswap Volume KPI Options to help divest Uniswap’s Community Treasury into Stablecoins\n\n4\n\n3136\n\nJuly 26, 2021\n\nConsensus Check: Raise the proposal quorum threshold from 40M\n\n8\n\n3493\n\nJuly 11, 2021\n\nConsensus Check - UNI should fund a political defense organization for decentralized finance (copy)\n\n24\n\n8626\n\nJune 16, 2021\n\nSwap UNI for ETH and wBTC and provide liquidity\n\n8\n\n4124\n\nMay 16, 2021\n\nConsensus Check - Staking & Tokenomics\n\n8\n\n3738\n\nMay 4, 2021\n\nConsensus Check -- Hire 24/7 Discord support\n\n14\n\n4095\n\nNovember 25, 2020\n\nUNI buyback from market using Uniswap 0.3% fees\n\n29\n\n7252\n\nFebruary 27, 2021\n\n[Consensus Check] Should Uniswap Distribute UNI to Liquidity Providers?\n\n12\n\n5700\n\nDecember 9, 2020\n\nPrevent exchanges to vote on Uniswap governance proposals\n\n11\n\n3765\n\nNovember 25, 2020\n\nPercent Dominance Staking as a Pipeline for Proposals\n\n7\n\n3059\n\nNovember 8, 2020","tokens":681,"crawled_at":1791193135674}
+{"id":10193,"url":"https://docs.synthetix.io/faq","domain":"docs.synthetix.io","chapter":"defi_protocols","title":"Frequently Asked Questions – Synthetix","text":"Last updated: Sep 3, 2026\n\nFind answers to common questions about Synthetix Exchange.\n\nIf you can't find the answer you're looking for, see Contact Support for information about getting help from the AI assistant or a human Support agent. Alternatively, open the chat widget using the icon in the bottom-right corner.\n\nPopular Questions\n\nWhy can't I place an order?\n\nWhy wasn't my Limit Order filled?\n\nWhy isn't my position appearing?\n\nWhy can't I withdraw?\n\nHow do I close my position?\n\nWhat happens if I get liquidated?\n\nBrowse by topic\n\nPlatform Basics\n\nWallet & Access\n\nTokens & Assets\n\nCollateral & Margin\n\nTrading\n\nTechnical Issues\n\nAPI\n\nPlatform Basics\n\nWhat is Synthetix?\n\nSynthetix is a decentralised perpetuals exchange on Ethereum Mainnet. It lets you trade leveraged long and short positions on a range of assets without giving up custody of your funds.\n\nDo I need to create an account?\n\nNo sign-up is required. Connect your wallet and create a trading subaccount directly in the app.\n\nLearn more: Getting Started\n\nDo I need KYC?\n\nNo. Synthetix does not require identity verification.\n\nWho controls my funds?\n\nYou. Your funds are held by Synthetix smart contracts rather than by a centralised custodian. Synthetix does not have custody of your assets.\n\nWallet & Access\n\nCan I use multiple wallets?\n\nYes. Each wallet can have its own set of subaccounts.\n\nCan I use multiple subaccounts?\n\nYes. You can create multiple subaccounts within a wallet. Subaccounts keep collateral and positions isolated from one another.\n\nLearn more: Subaccounts\n\nI connected the wrong wallet. Can I switch?\n\nYes. Disconnect and reconnect the correct wallet using the wallet selector.\n\nWhat happens if I lose my wallet?\n\nYour funds are secured by your wallet's seed phrase. Synthetix cannot recover access to your wallet on your behalf. Store your seed phrase securely.\n\nTokens & Assets\n\nWhat collateral can I use?\n\nUSDT and WETH are currently supported as collateral in the app. USDT is the settlement asset, while WETH contributes haircut-adjusted collateral value for trading.\n\nLearn more: Depositing Collateral and Multicollateral Margin\n\nHow do I deposit collateral?\n\nYou can deposit supported collateral, such as USDT or WETH, through the Deposit window in the trading interface.\n\nSelect the asset and amount you want to deposit, then follow the prompts to complete the transaction.\n\nLearn more: Depositing Collateral\n\nWhat tokens do I need?\n\nUSDT - settlement asset and supported collateral.\n\nWETH - supported non-USDT collateral.\n\nETH - gas fees on Ethereum Mainnet.\n\nWhy do I see unknown tokens in my wallet?\n\nUnknown tokens may be airdropped spam tokens. Do not interact with them. Synthetix does not airdrop tokens without an official announcement.\n\nCollateral & Margin\n\nCan I trade without holding USDT?\n\nYes. Deposit supported non-USDT collateral such as WETH and trade USDT-settled markets. Fees, funding, and realised PnL still settle in USDT, so your USDT balance may go negative while positions are open.\n\nLearn more: Multicollateral Margin\n\nWhy is Swap unavailable when my USDT is negative?\n\nYour USDT can show as negative while positive unrealised PnL covers it. In that case, it is not effective debt. Swap becomes available when you have USDT debt after positive unrealised PnL is considered.\n\nLearn more: Multicollateral Margin\n\nWhy is my Collateral Value lower than my balance multiplied by the price?\n\nNon-USDT assets are subject to haircuts. Collateral Value is the haircut-adjusted value that contributes towards your margin.\n\nLearn more: Leverage & Margin\n\nWhy can't I withdraw?\n\nYour withdrawable amount may be limited by your available balance, open positions, margin requirements, outstanding USDT debt, or an existing pending withdrawal.\n\nCheck your available withdrawal amount and make sure you have sufficient withdrawable balance. Reducing positions, repaying USDT debt, or depositing additional collateral may increase the amount you can withdraw.\n\nLearn more: Withdrawing Collateral and Multicollateral Margin\n\nWhy can't I withdraw all my USDT when I also hold WETH?\n\nUSDT withdrawals are limited by your available USDT and positive unrealised PnL. WETH collateral supports margin and trading but does not increase the amount of USDT you can withdraw unless you Swap it or receive USDT through trading activity.\n\nLearn more: Withdrawing Collateral and Multicollateral Margin\n\nWhy did my margin drop without closing a trade?\n\nNon-USDT collateral is valued using its index price. A change in the WETH price can therefore reduce your Collateral Value and Adjusted Account Value even if your position PnL has not changed.\n\nLearn more: Leverage & Margin\n\nWhy is my maximum withdrawal zero even though I have a balance?\n\nOpen positions may reserve margin, USDT debt may require collateral to remain in the account, or the asset may be fully supporting your existing obligations.\n\nReducing positions, repaying USDT debt through Swap, or depositing additional collateral may increase your withdrawable amount.\n\nLearn more: Withdrawing Collateral and Multicollateral Margin\n\nWill closing my last position repay my USDT debt?\n\nNo. Realised PnL settles into USDT, but remaining debt is not automatically repaid. You can use Swap to repay the debt, or collateral may be automatically exchanged if debt limits are breached.\n\nLearn more: Multicollateral Margin\n\nWhat's the difference between Swap and Withdraw?\n\nWithdraw sends tokens from your account to your wallet. Swap converts supported non-USDT collateral into USDT within your account and can be used to repay USDT debt.\n\nLearn more: Withdrawing Collateral and Multicollateral Margin\n\nWhy was my collateral sold without me clicking Swap?\n\nForced auto-exchange can occur when your USDT debt exceeds the permitted debt limit.\n\nLearn more: Multicollateral Margin\n\nDoes auto-exchange require my approval?\n\nNo. Forced auto-exchange runs automatically when its conditions are met.\n\nLearn more: Multicollateral Margin\n\nWhy did my USDT go negative overnight?\n\nFunding payments and trading fees settle in USDT. If you hold non-USDT collateral without sufficient USDT, these payments can cause your USDT balance to become negative.\n\nLearn more: Multicollateral Margin and Funding\n\nAre gas fees charged on swaps?\n\nNo. Internal Swap transactions do not require a wallet gas transaction. Gas is required for on-chain deposits and withdrawals.\n\nLearn more: Depositing Collateral and Withdrawing Collateral\n\nTrading\n\nWhat fees do I pay?\n\nSynthetix charges fees for activities such as trading, withdrawals, and other applicable transactions. The fees that apply depend on the action and your trading account tier. Fees may also be adjusted based on applicable referral discounts.\n\nLearn more: Fees and Referral Program\n\nOrders\n\nWhy can't I place an order?\n\nOrders may be rejected for reasons such as insufficient available margin, market or leverage limits, or other order conditions.\n\nCheck your available margin, order parameters and the relevant market limits before trying again.\n\nLearn more: Leverage & Margin and Order Types\n\nWhy wasn't my Limit Order filled?\n\nA Limit Order only executes when the market reaches the specified price or a price that provides an execution under the order's conditions. An order may remain open until it is filled, cancelled or expires.\n\nLearn more: Limit Orders\n\nWhy was my order partially filled?\n\nAn order can be partially filled when only part of the requested quantity can be matched with available liquidity.\n\nThe remaining quantity may stay open and continue to wait for execution, depending on the order type and selected Time in Force.\n\nLearn more: Limit Orders\n\nWhy did my order execute at a different price?\n\nThe final execution price can differ from the displayed or quoted price because market prices and available liquidity can change before the order is filled.\n\nThis is particularly relevant for Market Orders, where the final execution price depends on available liquidity at the time of execution.\n\nLearn more: Market Orders\n\nWhy didn't my Trigger Order execute?\n\nA Trigger Order remains pending until its trigger conditions are met. Once triggered, it follows the configured order behaviour.\n\nLearn more: Advanced Order Types\n\nWhy didn't my Take Profit or Stop Loss execute?\n\nTP/SL orders remain pending until their configured trigger conditions are met. Market conditions, trigger prices and the state of the related position can affect whether an order executes.\n\nLearn more: Managing Positions and Advanced Order Types\n\nCan I edit an order after placing it?\n\nSome order types can be edited after submission. The available actions depend on the order type.\n\nLearn more: Managing Open Orders\n\nCan I cancel an order after placing it?\n\nYes. Supported open orders can be cancelled before execution.\n\nLearn more: Managing Open Orders\n\nWhere can I view my open orders?\n\nOpen orders are displayed in the Open Orders tab of the Portfolio Table. The available tabs and information depend on the order type.\n\nLearn more: Managing Open Orders and Portfolio\n\nWhy did my order disappear from Open Orders?\n\nAn order is removed from Open Orders when it is executed, cancelled, or expires where applicable.\n\nCancelling a parent order may also cancel linked child orders, such as Take Profit or Stop Loss orders.\n\nLearn more: Managing Open Orders\n\nWhere can I find my order and trade history?\n\nYou can view your Order History and Trade History in the Portfolio Table.\n\nLearn more: Trade & Order History\n\nWhat's the difference between Order History and Trade History?\n\nOrder History records the orders you submit, including orders that may be filled, cancelled or expired. Trade History records executed trades resulting from those orders.\n\nLearn more: Trade & Order History\n\nPositions\n\nWhat is the maximum leverage?\n\nMaximum leverage varies by market and position size. Leverage limits can decrease as notional position size increases.\n\nCheck the market detail panel in the app for the current limits.\n\nLearn more: Leverage & Margin\n\nHow do I close my position?\n\nYou can close an open position from the Positions tab in the Portfolio Table. Select the Close action for the position you want to close, then review and submit the closing order.\n\nLearn more: Managing Positions\n\nWhy can't I close my position?\n\nA position may not be able to close if there is insufficient available liquidity, insufficient margin, or an issue with the order parameters.\n\nCheck that you are using the correct market and direction, and that your position size and available margin are sufficient to submit the closing order.\n\nIf the issue persists, contact Support with your wallet address, subaccount, market, and details of the order.\n\nLearn more: Managing Positions and Order Types\n\nWhy did my TP/SL disappear?\n\nTake Profit and Stop Loss orders are linked to the position or parent order they were created with. If the related parent order or position is closed or cancelled, the associated TP/SL orders may also be cancelled and removed from Open Orders.\n\nCheck your Positions and Open Orders tabs to confirm the current state of your position and TP/SL orders.\n\nLearn more: Managing Positions and Managing Open Orders\n\nWhat is funding?\n\nFunding is a periodic payment between long and short positions that helps keep perpetual prices aligned with the underlying market.\n\nLearn more: Funding\n\nWhat is the difference between mark price and last price?\n\nThe mark price is used for margin calculations, PnL and liquidations. It is derived from external perpetual markets to help resist manipulation.\n\nThe last price represents the current fair value of the Synthetix perpetual and is used for UI display.\n\nLearn more: Pricing\n\nWhat happens if I get liquidated?\n\nYour positions may be reduced, closed or transferred to designated SLP accounts. A liquidation fee is deducted, and remaining collateral may be returned to the account.\n\nIn multicollateral accounts, all collateral types in the affected subaccount may be involved in the liquidation process.\n\nLearn more: Liquidations\n\nTechnical Issues\n\nMy wallet won't connect. What should I do?\n\nEnsure your wallet is set to Ethereum Mainnet.\n\nRefresh the page.\n\nTry clearing your browser cache.\n\nTry a different browser or disable browser extensions.\n\nContact Support if the issue persists.\n\nWhy am I seeing a wrong network error?\n\nSwitch your wallet to Ethereum Mainnet and refresh the page.\n\nWhy is my transaction stuck pending?\n\nYou may need to speed up or cancel the transaction from your wallet.\n\nWhy did my transaction fail even though gas was used?\n\nA failed transaction can still consume gas. This may happen when a contract condition is not met at execution time, such as price movement or an open interest limit.\n\nCheck the error message in your wallet or block explorer.\n\nWhy isn't my deposit showing?\n\nAfter depositing, allow the transaction time to confirm, then refresh the trading interface.\n\nIf the transaction has confirmed but the deposit is still not showing, contact Support with your wallet address, subaccount, and transaction hash.\n\nLearn more: Depositing Collateral\n\nWhy is my withdrawal pending?\n\nWithdrawals may take time to complete after they are submitted. Allow time for the transaction to confirm, then refresh the trading interface.\n\nIf the withdrawal remains pending, contact Support with your wallet address, subaccount, and transaction hash.\n\nLearn more: Withdrawing Collateral\n\nWhy did my withdrawal fail?\n\nA withdrawal may fail if the request does not meet the required conditions.\n\nCheck your withdrawable balance and try again. If the withdrawal continues to fail, contact Support with your wallet address, subaccount, and transaction details.\n\nLearn more: Withdrawing Collateral\n\nWhy isn't my balance updating?\n\nWait for the transaction to confirm on Ethereum Mainnet. If the transaction has confirmed but the balance has not updated, refresh the page and check that you are viewing the correct subaccount.\n\nWhy isn't my position appearing?\n\nCheck that the order was successfully submitted and that you are viewing the correct subaccount / market. Refresh the trading interface and check your Positions tab and Trade History or Order History.\n\nIf the position still does not appear, contact Support with your wallet address, subaccount and details of the order.\n\nWhy is the trading interface not updating?\n\nCheck that your internet connection is stable and refresh the trading interface. Also make sure your wallet is connected to Ethereum Mainnet and that you are viewing the correct wallet, subaccount, and market.\n\nIf the issue persists, contact Support with your wallet address, subaccount, market, and details of what is not updating.\n\nAPI\n\nDo you have an API?\n\nYes. Synthetix provides REST and WebSocket APIs.\n\nLearn more: API Overview\n\nHow do I authenticate API requests?\n\nSynthetix API requests use EIP-712 signatures.\n\nLearn more: Authentication\n\nStill Need Help?\n\nIf your question isn't answered here, see Contact Support to learn how to contact Support, speak with a human agent, and manage your support conversations. Alternatively, get straight to it and hit the chat icon in the bottom-right corner.\n\nWhen contacting Support, include the following where applicable:\n\nYour wallet address\n\nYour subaccount\n\nThe network you're using\n\nThe market involved\n\nTransaction hashes\n\nA clear description of the issue\n\nScreenshots or screen recordings\n\nSecurity Reminder\n\nSynthetix Support will never ask for:\n\nYour seed phrase\n\nYour private keys\n\nWallet credentials or other information that could give access to your wallet.\n\nAlways verify that you're communicating through the official Support conversation.\n\nSee Official Links to verify official Synthetix websites and resources.","tokens":3936,"crawled_at":1791193136307}
+{"id":10194,"url":"https://www.metaplex.com/docs/smart-contracts/token-metadata/collections","domain":"www.metaplex.com","chapter":"docs","title":"Verified Collections | Token Metadata","text":"Token Metadata is a legacy program. It remains supported, but is not recommended for new projects. Use Core instead.\n\nCertified Collections enables NFTs – and tokens in general — to be grouped together and for that information to be verified onchain. Additionally, it makes it easier to manage these collections by allocating data for them onchain.\nThis feature provides the following advantages:\nEasy to identify which collection any given NFT belongs to without making additional onchain calls.\nPossible to find all NFTs that belong to a given collection (Check the Guide to see how).\nEasy to manage the collection metadata such as its name, description and image.\nCollections are NFTs\nIn order to group NFTs — or any token — together, we must first create a Collection NFT whose purpose is to store any metadata related to that collection. That's right, a collection of NFT is itself, an NFT. It has the same data layout onchain as any other NFT.\nThe difference between a Collection NFT and a Regular NFT is that the information provided by the former will be used to define the group of NFTs it contains whereas the latter will be used to define the NFT itself.\nAssociating NFTs to Collection NFTs\nCollection NFTs and Regular NFTs are linked together using a \"Belong To\" relationship on the Metadata account. The optional Collection field on the Metadata account has been created for that purpose.\nIf the Collection field is set to None, it means the NFT is not part of a collection.\nIf the Collection field is set, it means the NFT is part of the collection specified within that field.\nAs such, the Collection field contains two nested fields:\nKey: This field points to the Collection NFT the NFT belongs to. More precisely, it points to the public key of the Mint Account of the Collection NFT. This Mint Account must be owned by the SPL Token program.\nVerified: This boolean is very important as it is used to verify that the NFT is truly part of the collection it points to. More on that below.\n\nMint Account\n\nOwner: Token Program\n\nMetadata Account\n\nOwner: Token Metadata Program\n\n...\n\nToken Standard\n\nCollection = None\n\nCollection NFT\n\nPDA\n\nMint Account\n\nOwner: Token Program\n\nMetadata Account\n\nOwner: Token Metadata Program\n\n...\n\nToken Standard\n\nCollection\n- Key\n- Verified = True\n\nRegular NFT\nAttached to a collection\n\nPDA\n\nMint Account\n\nOwner: Token Program\n\nMetadata Account\n\nOwner: Token Metadata Program\n\n...\n\nToken Standard\n\nCollection = None\n\nRegular NFT\nWith no collection\n\nPDA\n\nReact Flow\nPress enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.\nPress enter or space to select an edge. You can then press delete to remove it or escape to cancel.\n\nDifferentiating NFTs from Collection NFTs\nThe Collection field alone allows us to link NFTs and Collections together but it doesn't help us identify if a given NFT is a Regular NFT or a Collection NFT. That's why the CollectionDetails field was created. It provides additional context on Collection NFTs and differentiates them from Regular NFTs.\nIf the CollectionDetails field is set to None, it means the NFT is a Regular NFT.\nIf the CollectionDetails field is set, it means the NFT is a Collection NFT and additional attributes can be found inside this field.\nThe CollectionDetails is an optional enum that currently contains only one option V1. This option is a struct that contains the following field:\nSize: The size of the collection, i.e. the number of NFTs that are directly linked to this Collection NFT. This number is automatically computed by the Token Metadata program but can also be set manually to facilitate the migration process. Note that there currently is a MIP in place to deprecate this Size attribute.\n\nMint Account\n\nOwner: Token Program\n\nMetadata Account\n\nOwner: Token Metadata Program\n\n...\n\nToken Standard\n\nCollection = None\n\nUse\n\nCollectionDetails = Some\n\nCollection NFT\n\nPDA\n\nMint Account\n\nOwner: Token Program\n\nMetadata Account\n\nOwner: Token Metadata Program\n\n...\n\nToken Standard\n\nCollection\n- Key\n- Verified = True\n\nUse\n\nCollectionDetails = None\n\nRegular NFT\nAttached to a collection\n\nPDA\n\nMint Account\n\nOwner: Token Program\n\nMetadata Account\n\nOwner: Token Metadata Program\n\n...\n\nToken Standard\n\nCollection = None\n\nUse\n\nCollectionDetails = None\n\nRegular NFT\nWith no collection\n\nPDA\n\nReact Flow\nPress enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.\nPress enter or space to select an edge. You can then press delete to remove it or escape to cancel.\n\nCreating Collection NFTs\nCreating a Collection NFT is very similar to creating a Regular NFT. The only difference is that we must set the CollectionDetails field as seen in the previous section. Some of our SDKs encapsulate this by requesting a isCollection attribute when creating an NFT.\n\n1import { generateSigner, percentAmount } from '@metaplex-foundation/umi';\n\n2import { createNft } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4// Assuming umi is set up with mplTokenMetadata plugin\n\n5\n\n6const collectionMint = generateSigner(umi);\n\n7\n\n8await createNft(umi, {\n\n9 mint: collectionMint,\n\n10 name: 'My Collection',\n\n11 uri: 'https://example.com/my-collection.json',\n\n12 sellerFeeBasisPoints: percentAmount(5.5), // 5.5%\n\n13 isCollection: true,\n\n14}).sendAndConfirm(umi);\n\n15\n\n16console.log('Collection NFT created:', collectionMint.publicKey);\n\n1import { generateKeyPairSigner } from '@solana/kit';\n\n2import { createNft } from '@metaplex-foundation/mpl-token-metadata-kit';\n\n3\n\n4// Assuming rpc, rpcSubscriptions, sendAndConfirm, and authority are set up\n\n5\n\n6const collectionMint = await generateKeyPairSigner();\n\n7\n\n8// Create a Collection NFT\n\n9const [createIx, mintIx] = await createNft({\n\n10 mint: collectionMint,\n\n11 authority,\n\n12 payer: authority,\n\n13 name: 'My Collection',\n\n14 uri: 'https://example.com/my-collection.json',\n\n15 sellerFeeBasisPoints: 550, // 5.5%\n\n16 tokenOwner: authority.address,\n\n17 isCollection: true,\n\n18});\n\n19\n\n20await sendAndConfirm({\n\n21 instructions: [createIx, mintIx],\n\n22 payer: authority,\n\n23});\n\n24\n\n25console.log('Collection NFT created:', collectionMint.address);\n\nNested Collection NFTs\nBecause Collections and NFTs are linked together via a \"Belong To\" relationship, it is possible by design to define nested collections. In this scenario, the Collection and CollectionDetails fields can be used together to differentiate Root and Nested Collection NFTs.\n\nMint Account\n\nOwner: Token Program\n\nMetadata Account\n\nOwner: Token Metadata Program\n\n...\n\nToken Standard\n\nCollection = None\n\nUse\n\nCollectionDetails = Some\n\nCollection NFT\nRoot collection\n\nPDA\n\nMint Account\n\nOwner: Token Program\n\nMetadata Account\n\nOwner: Token Metadata Program\n\n...\n\nToken Standard\n\nCollection\n- Key\n- Verified = True\n\nUse\n\nCollectionDetails = Some\n\nCollection NFT\nNested collection\n\nPDA\n\nMint Account\n\nOwner: Token Program\n\nMetadata Account\n\nOwner: Token Metadata Program\n\n...\n\nToken Standard\n\nCollection\n- Key\n- Verified = True\n\nUse\n\nCollectionDetails = None\n\nRegular NFT\nAttached to a collection\n\nPDA\n\nReact Flow\nPress enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.\nPress enter or space to select an edge. You can then press delete to remove it or escape to cancel.\n\nVerifying Collection NFTs\nAs mentioned above, the Collection field contains a Verified boolean which is used to determine if the NFT is truly part of the collection it points to. Without this field, anyone could pretend their NFT to be part of any collection.\n\nMint Account\n\nOwner: Token Program\n\nMetadata Account\n\nOwner: Token Metadata Program\n\n...\n\nToken Standard\n\nCollection = None\n\nUse\n\nCollectionDetails = Some\n\nCollection NFT\n\nPDA\n\nMint Account\n\nOwner: Token Program\n\nMetadata Account\n\nOwner: Token Metadata Program\n\n...\n\nToken Standard\n\nCollection\n- Key\n- Verified = True\n\nUse\n\nCollectionDetails = None\n\nVerified NFT\nThe Collection NFT verified this NFT\nso we know for sure it is part of it.\n\nPDA\n\nMint Account\n\nOwner: Token Program\n\nMetadata Account\n\nOwner: Token Metadata Program\n\n...\n\nToken Standard\n\nCollection\n- Key\n- Verified = False\n\nUse\n\nCollectionDetails = None\n\nUnverified NFT\nThis could be anyone's NFT pretending\nto be part of this collection.\n\nPDA\n\nReact Flow\nPress enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.\nPress enter or space to select an edge. You can then press delete to remove it or escape to cancel.\n\nIn order to flip that Verified boolean to True, the Authority of the Collection NFT must sign the NFT to prove that it is allowed to be part of the collection.\nEXTREMELY IMPORTANT\nExplorers, Wallets and Marketplaces, MUST CHECK that Verified is true. Verified can only be set true if the Authority on the Collection NFT has run one of the Token Metadata Verify instructions over the NFT.\nThis is the same pattern as the Creators field where Verified must be true to validate the NFT.\nIn order to check if a collection is valid on an NFT, it MUST have a collection struct set with:\nThe key field matching the mint address of the appropriate collection parent.\nThe verified field set to true.\nIf those two steps are not followed you could be exposing fraudulent NFTs on real collections.\n\nVerify\nOnce the Collection attribute is set on an NFT, an authority of the Collection NFT can send a Verify instruction on the Token Metadata to flip its verify attribute from false to true. This instruction accepts the following attributes:\nMetadata: The address of the NFT's Metadata account. This is the NFT we want to verify inside the collection.\nCollection Mint: The address of the Collection NFT's Mint account. This is the Collection NFT that is already set on the Metadata account of the NFT but not yet verified.\nAuthority: The authority of the Collection NFT as a Signer. This can be the Update Authority of the Collection NFT or an approved delegate with the appropriate role (See \"Delegated Authority\" page).\nHere is how you can use our SDKs to verify a Collection NFT on Token Metadata.\n\n1import { publicKey } from '@metaplex-foundation/umi';\n\n2import { verifyCollectionV1, findMetadataPda } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4// Assuming umi, collectionMint, and collectionAuthority are set up\n\n5\n\n6const mintAddress = publicKey('mintAddress...');\n\n7\n\n8// First find the metadata PDA to use later\n\n9const metadata = findMetadataPda(umi, {\n\n10 mint: mintAddress,\n\n11});\n\n12\n\n13await verifyCollectionV1(umi, {\n\n14 metadata,\n\n15 collectionMint,\n\n16 authority: collectionAuthority,\n\n17}).sendAndConfirm(umi);\n\n18\n\n19console.log('Collection verified on NFT');\n\n1import {\n\n2 getVerifyCollectionV1InstructionAsync,\n\n3 findMetadataPda,\n\n4} from '@metaplex-foundation/mpl-token-metadata-kit';\n\n5\n\n6// Assuming rpc, rpcSubscriptions, sendAndConfirm, and collectionAuthority are set up\n\n7\n\n8const mintAddress = 'mintAddress...'; // The NFT to verify\n\n9const collectionMintAddress = 'collectionMintAddress...'; // The collection NFT\n\n10\n\n11// Find the metadata PDA\n\n12const [metadata] = await findMetadataPda({ mint: mintAddress });\n\n13\n\n14// Verify the collection on the NFT\n\n15const verifyIx = await getVerifyCollectionV1InstructionAsync({\n\n16 metadata,\n\n17 collectionMint: collectionMintAddress,\n\n18 authority: collectionAuthority,\n\n19 payer: collectionAuthority,\n\n20});\n\n21\n\n22await sendAndConfirm({\n\n23 instructions: [verifyIx],\n\n24 payer: collectionAuthority,\n\n25});\n\n26\n\n27console.log('Collection verified on NFT');\n\nUnverify\nReciprocally, the authority of a Collection NFT can unverify any NFTs that are part of its collection. This is done by sending an Unverify instruction to the Token Metadata program whose attributes are the same as the Verify instruction.\n\n1import { publicKey } from '@metaplex-foundation/umi';\n\n2import { unverifyCollectionV1, findMetadataPda } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4// Assuming umi, collectionMint, and collectionAuthority are set up\n\n5\n\n6const mintAddress = publicKey('mintAddress...');\n\n7\n\n8// First find the metadata PDA to use later\n\n9const metadata = findMetadataPda(umi, {\n\n10 mint: mintAddress,\n\n11});\n\n12\n\n13await unverifyCollectionV1(umi, {\n\n14 metadata,\n\n15 collectionMint,\n\n16 authority: collectionAuthority,\n\n17}).sendAndConfirm(umi);\n\n18\n\n19console.log('Collection unverified on NFT');\n\n1import {\n\n2 getUnverifyCollectionV1InstructionAsync,\n\n3 findMetadataPda,\n\n4} from '@metaplex-foundation/mpl-token-metadata-kit';\n\n5\n\n6// Assuming rpc, rpcSubscriptions, sendAndConfirm, and collectionAuthority are set up\n\n7\n\n8const mintAddress = 'mintAddress...'; // The NFT to unverify\n\n9const collectionMintAddress = 'collectionMintAddress...'; // The collection NFT\n\n10\n\n11// Find the metadata PDA\n\n12const [metadata] = await findMetadataPda({ mint: mintAddress });\n\n13\n\n14// Unverify the collection on the NFT\n\n15const unverifyIx = await getUnverifyCollectionV1InstructionAsync({\n\n16 metadata,\n\n17 collectionMint: collectionMintAddress,\n\n18 authority: collectionAuthority,\n\n19 payer: collectionAuthority,\n\n20});\n\n21\n\n22await sendAndConfirm({\n\n23 instructions: [unverifyIx],\n\n24 payer: collectionAuthority,\n\n25});\n\n26\n\n27console.log('Collection unverified on NFT');","tokens":3344,"crawled_at":1791193177563}
+{"id":10195,"url":"https://stack.olas.network/open-autonomy/guides/overview_of_the_development_process","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Overview of the development process - Olas Stack Developer Documentation","text":"Overview of the development process\n\nThe figure below presents the development process with Open Autonomy: from the idea of an off-chain AI agent to its deployment in production. If you have completed the quick start guide you have already navigated through a significant part of this process.\n\nOverview of the development process with the Open Autonomy framework\n\nThis is a summary of each step:\n\nDraft the AI agent idea. Any AI agent that needs to execute its functionality in an autonomous, transparent and decentralized way is a good candidate. You can take a look at some use cases to get an idea of what you can build with Open Autonomy.\n\nDefine the FSM specification. Describe the AI agent business logic as a finite-state machine (FSM) in a language understood by the framework. This specification defines what are the states of the AI agent, and how to transit from one to another.\n\nCode the FSM App skill. The actual business logic is encoded in the FSM App that lives inside each agent instance. Coding the FSM App involves scaffolding the \"skeleton\" of the classes, and complete the actual details of the actions executed in each state.\n\nDefine the agent blueprint. Define the components of the agent blueprint required to execute your AI agent, including the newly created FSM App. You can reuse already existing components publicly available on a remote registry.\n\nDefine the AI agent. This consists in defining the AI agent configuration and declaring what agent blueprint constitute the AI agent, together with a number of configuration parameters required.\n\nPublish and mint packages. Those are required steps to make the AI agent publicly available in the remote registry and secure it in the Olas Protocol.\n\nDeploy the AI agent. You can deploy directly your AI agent locally for testing purposes. To deploy a production AI agent secured in the Olas Protocol you first need to bring the AI agent to the Deployed state in the protocol.\n\nPopulate the local registry for the guides\n\nTo follow the next sections, you need to populate the local registry with a number of packages shipped with the framework. To do so, edit the local registry index file (./packages/packages.json) and ensure that it has the following third_party entries:\n\n{\n\"dev\": {\n},\n\"third_party\": {\n\"service/valory/hello_world/0.1.0\": \"bafybeiabtwvve5dfuv464ypgs6jikz5rx3w3fkpej4rzn6x36zxmthuphm\",\n\"agent/valory/hello_world/0.1.0\": \"bafybeidkuptt5jvtsetgqfbj3detp7zne7z67bi3rkxh43q5thbsz3pwsy\",\n\"connection/valory/abci/0.1.0\": \"bafybeiafvaguchnkp2fmhf6gtayc3gpnxkglagghb4ukbqtouni5tveigi\",\n\"connection/valory/http_client/0.23.0\": \"bafybeihel6sg2yayxu7lqygaswdgciaxpqrgsbl5rwx74c6znu5qz2edd4\",\n\"connection/valory/ipfs/0.1.0\": \"bafybeidob3tcdebjbm4ovwqoz4v2egf7nvoui3hu5on4o3apfchr6rpwwa\",\n\"connection/valory/ledger/0.19.0\": \"bafybeicynh5l5f5f5jpx72qwzis7jvmxk5p4eqltk32uxbj2pgu2x4rqz4\",\n\"contract/valory/service_registry/0.1.0\": \"bafybeicbfffywnaaehptzasxsdoyguuurpleirsnor5xf7rqk57isjkury\",\n\"protocol/open_aea/signing/1.0.0\": \"bafybeifsjmldwyki3beqyvdt5lzenrg6wyrqaar5plc5rpnvtc4zlentye\",\n\"protocol/valory/abci/0.1.0\": \"bafybeiak4pwac3pwjtd7weskxdhkrcopckr32vtazfbuteu6yqjkwarpte\",\n\"protocol/valory/acn/1.1.0\": \"bafybeiea66z4k6cgcazxd6qzvnkllulyjzbnxufkoenge7qzh4qfogrvoa\",\n\"protocol/valory/contract_api/1.0.0\": \"bafybeibld2xb5m7kyluiptkamp4nrt6oeomkohz7a3yppbv2oo7qw2e4la\",\n\"protocol/valory/http/1.0.0\": \"bafybeidxkp3vga7t6x2pbt2tpkgyaxa5bgpdgryao54py7w3yxyzr7neoy\",\n\"protocol/valory/ipfs/0.1.0\": \"bafybeibz5xqhxdbuvba7nuw2w6ardjermtcoqercopnypdplnaekf3joam\",\n\"protocol/valory/ledger_api/1.0.0\": \"bafybeiecq56phjfws36rgrefw6niyo4ezesloodsfis647mpm5ygqo4ysi\",\n\"protocol/valory/tendermint/0.1.0\": \"bafybeihzb7e32f7jcrzvubilqaxzmyk7ea6ss3pg3tliatdlrr76qeknyq\",\n\"skill/valory/abstract_abci/0.1.0\": \"bafybeie5et43th2nta76cd3kpm3fmurd7oyzk3qxim76octvt56m6r2poi\",\n\"skill/valory/abstract_round_abci/0.1.0\": \"bafybeifkxnvvgsldkb4rgejsoon2mvrmrnl7asy2nhenwss7hpwg3myflu\",\n\"skill/valory/hello_world_abci/0.1.0\": \"bafybeihlwaujzwwnduhdsgdozllykt6or6wsik44fr2dtupioe2epnfkxq\",\n\"connection/valory/p2p_libp2p_client/0.1.0\": \"bafybeielj3jso3wvrarp5n5rq7llpw4vgxybqiyensgjalb5ubfiawwhhu\"\n}\n}\n\nExecute the following command after updating the packages.json file:\n\nautonomy packages sync\n\nThe framework will fetch components from the remote registry into the local registry.\n\nDo you already have an existing agent blueprint or AI agent?\n\nIf you already have an existing agent blueprint (or if you want to create an AI agent with the default hello_world agent blueprint), you can skip to Step 5.\n\nIf you already have an existing AI agent (or if you want to test the default hello_world AI agent), you can skip to Step 6 or Step 7.","tokens":1174,"crawled_at":1791193164025}
+{"id":10196,"url":"https://a16zcrypto.com/posts/tags/data-availabililty","domain":"a16zcrypto.com","chapter":"research","title":"data availability - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\ndata availability\n\nFeed\nFILTERS\n(1)\nclear filters\n\ncategories\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\n(1) recommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nclear all data availability\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n03.20.24 / Ertem Nusret Tas, István András Seres, Yinuo Zhang, Márk Melczer, Mahimna Kelkar, Joseph Bonneau and Valeria Nikolaenko\nNew paper alert: Atomic and fair data exchange via blockchain\nA new Fair Data Exchange protocol that enable a storage server to transfer a data file to a client atomically\n\nresearch\ncryptography\ndanksharding\ndata availability\n\n08.22.23 / Valeria Nikolaenko\nDistributed Data Storage, DAS, and Danksharding\nLera Nikolaenko introduces approaches to distributed data-storage using erasure codes, and explains approaches for achieving consensus around data-availability.\n\nresearch\nconsensus\ndata availability\nvideo\n\n05.05.23 / Valeria Nikolaenko, Dan Boneh and Robert Hackett\nOf data availability & danksharding\nAn explainer on data availability sampling and danksharding—relevant to Ethereum blockchain scaling—from the web3 with a16z crypto podcast.\n\nresearch\ncryptography\ndanksharding\ndata availability\nEthereum\npodcast\nscaling & throughput\n\n04.27.23 / Valeria Nikolaenko and Dan Boneh\nData availability sampling and danksharding: An overview and a proposal for improvements\nDanksharding is an approach to scaling the amount of data on chain for a future version of Ethereum. The goal of this upgrade is to ensure that the data on chain was made available to archiving parties when it was first posted. It does so using a technique called Data Availability Sampling, or simply DAS....\n\nresearch\ndanksharding\ndata availability\nEthereum\n\n02.10.23 / Ertem Nusret Tas\nCryptoeconomic Security for Data Availability Committees\nErtem Nusret Tas (Stanford) introduces DACs, then proposes a DAC protocol that provides financial incentives to deter the DAC nodes from adversarial behavior.\n\nresearch\ndata availability\nscaling & throughput\nsecurity\nvideo\n\n09.12.22 / Tim Beiko, Tim Roughgarden, Ali Yahya and Sonal Chokshi\nEthereum, Merge and Beyond\nEPISODE SUMMARY with @timbeiko @tim_roughgarden @alive_eth @smc90 A deep dive on all things Ethereum, which this week makes the big move to proof of stake in The Merge. But our conversation, which certainly goes into The Merge and shares lots of in-depth and behind-scene details and bottomline on what changes, what doesn’t — also goes...\n\ncode & engineering\ncommunity building\ndata availability\nEthereum\ngovernance\npodcast\nproof of stake\nproposer-builder separation\n\n08.06.22 / Tim Roughgarden, Joseph Bonneau, Scott Duke Kominers, Ali Yahya and Chris Dixon\nTop Tech Topics, Explained\nEPISODE SUMMARY @tim_roughgarden @josephbonneau @skominers with @alive_eth @cdixon A tour though top-of-mind blockchain & crypto tech topics, explained by several a16z crypto researchers, including VDFs (verifiable delay functions); zk-rollups, SNARKs, and zero knowledge in general; and others. We quickly zip up and down the stack, and across themes — such as scalability; data availability; reputation...\n\nresearch\ncrypto basics\ndata availability\nglossaries & terminology\nhow innovation happens\npodcast\nscaling & throughput\nSNARKs\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":1515,"crawled_at":1791193190784}
+{"id":10197,"url":"https://stack.olas.network/open-autonomy/guides/define_service","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Define the service - Olas Stack Developer Documentation","text":"Define the service\n\nGiven an existing agent blueprint, either developed by yourself on the previous step and stored in the local registry, or an agent blueprint fetched from the remote registry, the next step consists in defining AI agent and tuning its configuration options.\n\nPart of the development process covered in this guide\n\nWhat you will learn\n\nThis guide covers step 4 of the development process. You will learn how to define the AI agent itself. This consists in indicating what agent blueprint will the AI agent be using, and configuring the AI agent parameters through ai-agent-level overrides.\n\nYou must ensure that your machine satisfies the framework requirements, you have set up the framework, and you have a local registry populated with some default components. As a result you should have a Pipenv workspace folder with an initialized local registry (./packages) in it.\n\nStep-by-step instructions\n\nThe process to define an AI agent configuration is similar if you are using an agent blueprint being developed by you (for example, the agent blueprint created in the previous guide), or an existing, third-party agent blueprint downloaded from the remote registry. In the example below, we will be using the hello_world agent blueprint from the remote registry, which can be found in the list of packages shipped with the framework, but you can replace it with your own agent blueprint.\n\nEnsure that the agent blueprint required by your AI agent is in the local registry. Your agent blueprint, all its required components and their dependencies must be downloaded to the local registry. You can read how to add missing components to the local registry.\nIf you have populated the local registry with the required components to follow these guides, you do not need to take any further action.\n\nCreate the AI agent configuration file. Create a folder for your AI agent in the local registry (./packages). Pay attention to the correct format of the folder:\n\nmkdir -p ./packages/your_name/services/your_ai_agent/\n\nWithin the AI agent folder, create the AI agent configuration file service.yaml:\n\ntouch ./packages/your_name/services/your_ai_agent/service.yaml\n\nThis file must contain:\n\nA number of mandatory parameters.\n\nImportant\n\nEnsure that author and AI agent name match the path within the local registry.\n\nA reference to the agent blueprint that the AI agent will be using.\n\nConfiguration overrides that specify values for component parameters. These overrides are separated by YAML document separators --- and will be discussed in a further section.\n\nExample of a service.yaml file\nThis is a complete example of an AI agent configuration file that uses the hello_world agent blueprint and overrides some required component parameters.\n\nservice.yamlname: your_ai_agent\nauthor: your_name\nversion: 0.1.0\ndescription: A demonstration of a simple AI agent\naea_version: '>=2.0.0, <3.0.0'\nlicense: Apache-2.0\nfingerprint: {}\nfingerprint_ignore_patterns: []\nagent: valory/hello_world:0.1.0\nnumber_of_agents: 4\ndeployment: {}\n---\npublic_id: valory/hello_world_abci:0.1.0\ntype: skill\nmodels:\nparams:\nargs:\nservice_registry_address: null\nshare_tm_config_on_startup: false\non_chain_service_id: null\nsetup:\nall_participants: ${ALL_PARTICIPANTS:list:[\"0x0000000000000000000000000000000000000000\"]}\nsafe_contract_address: '0x0000000000000000000000000000000000000000'\nconsensus_threshold: null\nhello_world_message: ${HELLO_WORLD_STRING_0:str:HELLO_WORLD!}\nbenchmark_tool:\nargs:\nlog_dir: /benchmarks\n---\npublic_id: valory/ledger:0.19.0\ntype: connection\nconfig:\nledger_apis:\nethereum:\naddress: ${SERVICE_HELLO_WORLD_RPC:str:\"http://host.docker.internal:8545\"}\nchain_id: 31337\npoa_chain: false\ndefault_gas_price_strategy: eip1559\n\nYou should also create a README.md file with the description of your AI agent in plain text or Markdown format:\n\necho \"Your AI agent description.\" > ./packages/your_name/services/your_ai_agent/README.md\n\nCreate an entry for your AI agent in the local registry. Add the corresponding entry to the local registry index file (./packages/packages.json). You must add the entry to the dev section, because it is a component being developed by you. You can use a placeholder for its hash value, as it will be corrected afterwards:\n\n{\n\"dev\": {\n\"service/your_name/your_ai_agent/0.1.0\": \"bafybei0000000000000000000000000000000000000000000000000000\",\n\n},\n\"third_party\": {\n\n}\n}\n\nUpdate the package hashes. The command below will correct any hash mismatch in the service.yaml file, as well as in the local registry index file (./packages/packages.json):\n\nautonomy packages lock\n\nPerform a sanity-check verification for the AI agent definition. The command below ensures that the AI agent satisfies a number of requirements to be deployed:\n\nautonomy analyse service --public-id your_name/your_ai_agent:0.1.0\n\nFor now, you can ignore any warnings you see. You should see the message:\n\nService is ready to be deployed.\n\nUse a local deployment to test the AI agent. This is the recommended approach in order to test your AI agent before you publish it to a remote registry. Follow the instructions in the local deployment guide. Note that this process should be somewhat familiar to you if you have followed the quick start guide.","tokens":1312,"crawled_at":1791193195756}
+{"id":10198,"url":"https://docs.near.org/getting-started/what-is-near","domain":"docs.near.org","chapter":"layer1_layer2","title":"What is NEAR? - NEAR Docs","text":"NEAR is a user-friendly and carbon-neutral blockchain, built to be fast, secure, and infinitely scalable. It offers a simple user experience with named accounts, low fees, and a robust developer ecosystem.\n\nIn technical terms, NEAR is a layer one, sharded, proof-of-stake blockchain built with usability in mind.\nIn simpler terms, NEAR is the blockchain for everyone.\n\nWhat do these Technical Terms mean?\n\nIn technical terms, NEAR is a layer-one, sharded, proof-of-stake blockchain built with usability in mind.Layer-1 means NEAR is the foundation that supports everything else built on it. It keeps all the transaction records safe and unchangeable which keeps the network secure and trustworthy.Sharded means the network is broken into pieces that work in parallel. This helps NEAR process transactions quickly and efficiently.Proof-of-stake uses less electricity compared with other blockchains which use proof-of-work. Users show they own NEAR tokens to help run the network. This makes it cheaper and lets more people use it.\n\n​\n\nWhy Choose NEAR?\n\nNEAR is a technical marvel, offering built-in features such as named accounts and account abstraction. For developers, NEAR offers everything needed for their applications, from smart contracts to indexers. All while being interoperable with other chains.\n​\n\nSimple to Use\n\nUse named accounts like alice.near\n\nSimple sign-up: create an account for free, login with socials or telegram\n\nTransactions are fast (~1.3s finality) and cheap (< 1¢ in fees)\n\nYou don’t need to buy crypto thanks to built-in account abstraction\n\nAccess Keys make it safe and easy to use\n\nControl accounts on other chains thanks to chain signatures\n\n​\n\nBattle-Tested\n\n5 years of 100% uptime and 4 Billion transactions processed\n\nNEAR has sustained peaks of >13M transactions in a single day\n\nNEAR is home to decentralized apps with millions of users:\n\nKai-ching\n\nSweat\n\nHot Wallet\n\n​\n\nGreat Developer Experience\n\nBuild smart contracts with Javascript or Rust\n\nSimple onboarding, thanks to its complete documentation and examples\n\nGet answers and learn at NEAR DevRel office hours, where anybody can participate\n\nEarn from your contract’s gas fees\n\nEVM compatible with Project Aurora (Deploy your Solidity contracts with ease)\n\n​\n\nEnvironmentally Friendly\n\nNEAR is certified carbon-neutral\n\nNEAR consumes in a year the same energy bitcoin consumes in 3 minutes\n\nWas this page helpful?","tokens":603,"crawled_at":1791193198553}
+{"id":10199,"url":"https://a16zcrypto.com/posts/videos/cryptoeconomic-security-for-data-availability-committees","domain":"a16zcrypto.com","chapter":"research","title":"Cryptoeconomic Security for Data Availability Committees - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nCryptoeconomic Security for Data Availability Committees\nErtem Nusret Tas\n02.10.23\n\nTags & Share Tags\ndata availability\nresearch\nscaling & throughput\nsecurity\nvideo\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nData Availability Committees (DACs) increase the throughput of Layer 2 systems – but at the cost of obtaining an L2 architecture whose security relies solely on the L1 chain. Ertem Nusret Tas (Stanford) introduces DACs and their shortcomings, and then proposes a DAC protocol that provides financial incentives to deter the DAC nodes from adversarial behavior (such as withholding data upon request). He then analyzes the interaction of rational DAC nodes and clients as a dynamic game, with a Byzantine adversary that can corrupt and bribe the participants. He also defines a notion of optimality for the DAC protocols, inspired by fairness and economic feasibility. The main result shows that the protocol is optimal and guarantees security with the highest possible probability under reasonable assumptions on the adversary.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nCharts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":953,"crawled_at":1791193211245}
+{"id":10200,"url":"https://gov.uniswap.org/t/treasury-delegation-round-2-ideas-thread/24667/13","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Treasury Delegation Round 2 Ideas Thread - #13 by Tane - Governance-Meta - Uniswap Governance","text":"Treasury Delegation Round 2 Ideas Thread\n\nGovernance-Meta\n\nTane\n\nOctober 3, 2024, 8:32pm\n\n13\n\nThanks @eek637 for bringing up this topic. We have conducted an analysis of how the program of UNI delegations to under-represented delegates worked and would like to present it here.\n\nSummary\n\nWe believe that the delegation of UNI to developers, the delegation expiration, and the cap on delegation allocation proposed by Erin are important considerations that should be discussed and implemented. However, we also believe that an expansion of the program itself is crucial.\n\nDue to the low voter participation rate for the large delegates in 2023, a proposal was passed to Delegate 10M UNI from the Foundation to active but under-represented delegates. This period is set for one year and will expire this December. After reviewing this program, we found that it is working well, but think that the current governance is not stable yet, thus we think it’s worth considering and evaluating an expansion of the program.\n\nDetailed analysis\n\nRegarding the activities of the selected delegates\n\nCheck the voting percentages of the selected delegates before and after this program.\n\nRegarding the 10 Onchain votes before being selected\n\nFirst measurement: Deploy Uniswap V3 on Linea\n\nLast time to measure: Deploy Uniswap V3 on Scroll\n\nCanceled votes were not counted.\n\nBefore selection\n\n404 DAO\n\nTally: https://www.tally.xyz/gov/uniswap/delegate/404dao-governance.eth\n\nOnchain: 7/10\n\nWintermute Governance\n\nTally: https://www.tally.xyz/gov/uniswap/delegate/wintermutegovernance.eth\n\nOnchain:10/10\n\nPGov\n\nTally: https://www.tally.xyz/gov/uniswap/delegate/0x3fb19771947072629c8eee7995a2ef23b72d4c8a\n\nOnchain:10/10\n\nStableLab\n\nTally: https://www.tally.xyz/gov/uniswap/delegate/0xecc2a9240268bc7a26386ecb49e1befca2706ac9 (Updated from https://www.tally.xyz/gov/uniswap/delegate/stablelab.eth)\n\nOnchain: 10/10 (NOTE: voting done from stablelab.eth address)\n\nKeyrock\n\nTally: https://www.tally.xyz/gov/uniswap/delegate/0xkeyrock.eth\n\nOnchain: 9/10\n\nKarpatkey\n\nTally: https://www.tally.xyz/gov/uniswap/delegate/0x8787fc2de4de95c53e5e3a4e5459247d9773ea52\n\nOnchain: 7/10\n\natiselsts.eth\n\nTally: https://www.tally.xyz/gov/uniswap/delegate/0xaac35d953ef23ae2e61a866ab93dea6ec0050bcd\n\nOnchain: 10/10\n\nAfter selection\n\nAll delegates participate in on-chain voting.\n\nThere were a few selected delegates that had been active in the onchain proposals before the delegations but some had not participate in all the proposals. Since the delegation, all delegates participated in all votes, which made the DAO healthier.\n\nProgram Effectiveness\n\nCalculation of VP (Voting Power) contributed based on post-election activities\n\nSince all delegates cast all onchain votes, we can say that the program contributes 10M UNI for every vote.\n\nVotes since this measure went into effect\n\nスクリーンショット 2024-08-09 16.46.172318×1866 476 KB\n\nスクリーンショット 2024-08-09 16.23.362300×1718 416 KB\n\nVoting before this measure was initiated\n\nスクリーンショット 2024-10-03 20.19.092292×964 251 KB\n\nIn 2023, before this measure was implemented, there were three votes that were QUORUM NOT REACHED, but since its implementation, all proposals have been EXECUTED (except for the latest one)\n\nHowever, regarding this year’s proposals, there were many proposals in the 40M-50M range and some were near the quorum. The average number of onchain votes since the program went into effect was about 47.46M UNI.\n\nCurrent risk of missing proposals\n\nOut of the 11 proposals since the program went into effect, 6 proposals that would not have reached the quorum IF one delegate had not missed voting. In addition, we saw the latest proposal just missed the quorum as well. While we saw an improvement of the voting activities, the DAO is still at risk of missing important proposals to be passed (or rejected).\n\nDetailed analysis of which proposal would be missed if a delegate had not voted\n\nhttps://www.tally.xyz/gov/uniswap/proposal/70 Gauntlet or Michigan Blockchain or Franklin DAO … , total 14 delegates\n\nhttps://www.tally.xyz/gov/uniswap/proposal/69 teemulaumhonkasalo.eth or Michigan Blockchain or MonetSupply or 0x9Eaf…4568 … , total 14 delegates\n\nhttps://www.tally.xyz/gov/uniswap/proposal/68 none\n\nhttps://www.tally.xyz/gov/uniswap/proposal/67 Gauntlet, or teemulaumhonkasalo.eth or Michigan Blockchain\n\nhttps://www.tally.xyz/gov/uniswap/proposal/66 None\n\nhttps://www.tally.xyz/gov/uniswap/proposal/65 teemulaumhonkasalo.eth\n\nhttps://www.tally.xyz/gov/uniswap/proposal/64 Gauntlet\n\nhttps://www.tally.xyz/gov/uniswap/proposal/63 None\n\nhttps://www.tally.xyz/gov/uniswap/proposal/62 Gauntlet or Michigan Blockchain or MonetSupply or Franklin DAO or Wintermute Governance or PGov or StableLab or she256.eth or BlockchainatCU or 404 Gov or BEN or Stanford Blockchain or GFX Labs\n\nhttps://www.tally.xyz/gov/uniswap/proposal/61 Gauntlet or teemulaumhonkasalo.eth or Michigan Blockchain or lay2000lbs or Franklin DAO\n\nhttps://www.tally.xyz/gov/uniswap/proposal/60[Gauntlet](https://www.tally.xyz/gov/uniswap/delegate/0x683a4f9915d6216f73d6df50151725036bd26c02) or teemulaumhonkasalo.eth\n\nhttps://www.tally.xyz/gov/uniswap/proposal/59 None\n\nhttps://www.tally.xyz/gov/uniswap/proposal/58 Gauntlet or teemulaumhonkasalo.eth or Michigan Blockchain\n\nhttps://www.tally.xyz/gov/uniswap/proposal/57 None\n\nhttps://www.tally.xyz/gov/uniswap/proposal/56 None\n\nhttps://www.tally.xyz/gov/uniswap/proposal/55 None\n\nDelegates who meet the criteria to be considered “under-represented”\n\nBased on the activities of the last selected delegate before it was selected\n\nThe following is a list of delegates who have created a Delegate Profile and are now Underrepresented.\n\nThe list of delegates with their delegate profile and VP as of writing\n23 delegates had created a Delegate Profile.\n\nhttps://gov.uniswap.org/t/curia-delegate-platform/24140/6 7k\n\nhttps://gov.uniswap.org/t/tane-delegate-platform/24164/6 10\n\nhttps://gov.uniswap.org/t/gauntlet-delegate-platform/23967/7 5.25M\n\nhttps://gov.uniswap.org/t/keyrock-delegate-platform/21243/13 504.03k\n\nhttps://gov.uniswap.org/t/seedgov-delegate-platform/23987/5 1.05k\n\nhttps://gov.uniswap.org/t/wintermute-delegate-platform/20181/22 2.5M\n\nhttps://gov.uniswap.org/t/karpatkey-delegate-platform/21773/29 860.04k\n\nhttps://gov.uniswap.org/t/franklindao-prev-penn-blockchain-delegate-platform/12755/34 3M\n\nhttps://gov.uniswap.org/t/atiselsts-eth-delegate-platform/22270/10 407.05k\n\nhttps://gov.uniswap.org/t/stablelab-delegate-platform/21240/55 2.5M\n\nhttps://gov.uniswap.org/t/pgov-delegate-platform/22271/27 2.5M\n\nhttps://gov.uniswap.org/t/bobbay-delegate-platform/24215/4 2\n\nhttps://gov.uniswap.org/t/michigan-blockchain-delegate-platform/24198/4 3.86M\n\nhttps://gov.uniswap.org/t/arana-digital-delegate-platform/23971/3 1.29k\n\nhttps://gov.uniswap.org/t/404-dao-delegate-platform/22285/4 2.51M\n\nhttps://gov.uniswap.org/t/whetstone-research-delegate-platform/24345 1M\n\nhttps://gov.uniswap.org/t/l2beat-delegate-platform/22449/3 256.79k\n\nhttps://gov.uniswap.org/t/daoplomats-delegation-platform/23450/6 97.37\n\nhttps://gov.uniswap.org/t/blockchain-education-network-ben-delegation-platform/23966/4 2.5M\n\nhttps://gov.uniswap.org/t/gfx-labs-delegate-communication-thread/24194/2 2.45M\n\nhttps://gov.uniswap.org/t/blockworks-research-delegate-platform/21219/1 250.32k\n\nhttps://gov.uniswap.org/t/argonaut-delegate-platform/24417 20\n\nhttps://gov.uniswap.org/t/ignas-delegate-platform/24674 8.4\n\nThe following 7 delegates are considered under-represented with a VP of 250k or less, similar to the previous application requirements:\n\nCuria, Tané, SEEDGov, Bobbay, Arana, DAOplomats, and Argonaut.\n\nConclusion\n\nThis program is working well, but the governance is not stable yet since some of the past proposals are close to missing its quorum, therefore we believe this program should be expanded further. As @GFXlabs suggested, we would also consider an additional 10M UNI suffices to achieve a stable and healthy governance state.\n\nOptions for expansion\n\nThe options that were voted on last time are as follows\n\nSplit equally among Qualified Delegates\n\nTop 4 Delegates get delegation till 2.5M is achieved. The rest of UNI are split among the rest proportional to their votes won.\n\nTop 4 Delegates get delegation till 2.5M is achieved (So likely first 4 delegates achieve 2.5 Mil. 5th gets some)\n\nIf the process is similar to the previous one, we believe that we should do the following steps: delegate’s candidacy, determination of the distribution method, Snapshot for the delegates (or additional parties like developers) to get delegations, and Snapshot for its approval.\n\n6 Likes\n\nTreasury Delegation Round 2 Ideas - Increased Allocation\n\n[RFC] Treasury Delegation Round 2\n\n[RFC] Governance Logistics Improvements\n\nshow post in topic\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[RFC] Treasury Delegation Round 2\n\nRequests for Comment\n\n39\n\n1818\n\nApril 28, 2025\n\n[RFC]: Delegation of UNI to Active but Underrepresented Delegates\n\nRequests for Comment\n\n18\n\n3046\n\nNovember 10, 2023\n\n[Temperature Check]: Delegation of UNI to Active but Underrepresented Delegates\n\nTemperature Check\n\n42\n\n7596\n\nDecember 4, 2023\n\nUniswap Delegate Reward Initiative - Cycle 3\n\nRequests for Comment\n\n38\n\n1611\n\nJune 30, 2025\n\n[Temp Check] Uniswap Delegate Reward -3 Months-Cycle 1\n\nRequests for Comment\n\n42\n\n3966\n\nJune 4, 2024","tokens":2336,"crawled_at":1791193215250}
+{"id":10201,"url":"https://docs.near.org/protocol/accounts-contracts/access-keys","domain":"docs.near.org","chapter":"layer1_layer2","title":"Access Keys - NEAR Docs","text":"In NEAR, users control their accounts using access keys, which can be full-access keys or function-call keys. Full-access keys allow complete control over the account, while function-call keys restrict actions to specific contracts. This system enables secure sharing of permissions and simplifies user interactions with applications.\n\n​\n\nAccess Keys\n\nIn most blockchains, users control their accounts by holding a single private key (a secret only they know) and using it to sign transactions.\n\nIn NEAR we distinguish two types of Access Keys:\n\nFull-Access Keys: Have full control over the account, and should never be shared\n\nFunction-Call Keys: Can only sign calls for specific contracts, and are meant to be shared\n\nIn addition, a key of either type can be created as a gas key: a key that carries its own prepaid gas balance and multiple independent nonces, built for sending many transactions in parallel.\nEvery account in NEAR can hold multiple keys, and keys can be added or removed, allowing a\nfine-grained control over the account’s permissions.\n\n​\n\nFunction-Call Keys\n\nFunction-Call keys can only sign transactions calling a specific contract, and do not allow to attach NEAR tokens to the call.\nThey are defined by three attributes:\n\nreceiver_id: The only contract which the key allows to call, no other contract can be called with this key\n\nmethod_names (Optional): The contract’s methods the key allows to call. If omitted, all contract’s methods can be called\n\nallowance (Optional): The amount of NEAR allowed to be spent on gas. If omitted, the key can consume unlimited gas\n\nFunction Call Keys are meant to be shared with applications, so third-parties can make contract calls in your name. This is useful in multiple scenarios as we will see below.\n\nFunction-Call keys are secure to share, as they only permit calls to a specific contract and prohibit NEAR token transfers\n\n​\n\nFull-Access Keys\n\nAs the name suggests, Full-Access keys have full control of an account, meaning they can be used to sign transactions doing any action in your account’s behalf:\n\nTransfer NEAR Ⓝ\n\nDelete your account or create sub-accounts of it\n\nAdd or remove Access Keys\n\nDeploy a smart contract in the account\n\nCall methods on any contract\n\nYou should never share your Full-Access, otherwise you are giving total control over the account.\n\nImplicit accounts already have a Full-Access Key by default, while for named accounts their first Full-Access Key is added on creation\n\n​\n\nGas Keys\n\nGas keys (NEP-611) are access keys designed for sending many transactions in parallel. They were introduced in nearcore 2.13 (protocol version 86) and differ from regular access keys in two ways:\n\nPrepaid gas balance: a gas key holds its own NEAR balance, and transactions signed with it pay gas from that balance instead of the account’s main balance\n\nParallel nonces: a gas key has up to 1,024 independent nonces (called nonce lanes), so many transactions can be in flight at once without nonce collisions\n\nA gas key can have either FullAccess or FunctionCall permission, with one restriction: a function-call gas key cannot set an allowance — its prepaid balance already serves as the gas budget.\nThis makes gas keys ideal for programmatic senders — relayers, bots, exchanges, or a fleet of agents operating one account — which previously had to juggle many separate access keys just to avoid nonce collisions, and risked draining the account’s main balance on gas.\n​\n\nLifecycle of a Gas Key\n\nA gas key is managed with the same actions as any other key, plus two new actions to move NEAR in and out of its balance:\n\nCreate: an AddKey action with a gas-key permission creates the key, specifying its number of nonces (num_nonces, between 1 and 1,024). The key is always created with zero balance\n\nFund: a TransferToGasKey action moves NEAR from the account’s balance into the gas key’s balance. It can be used repeatedly to top up the key\n\nUse: transactions signed with the gas key specify a nonce_index selecting which nonce lane to use, and consume gas from the key’s balance\n\nWithdraw: a WithdrawFromGasKey action moves NEAR from the key’s balance back to the account. Only the account itself can withdraw\n\nDelete: a DeleteKey action removes the key. Any remaining balance is burned, so the action fails if the key holds more than 1 NEAR — withdraw first, then delete\n\nDeleting a gas key burns whatever balance is left on it — this is a protocol-level protection against spam attacks, not a bug. Always WithdrawFromGasKey before deleting. The deletion (and likewise DeleteAccount) fails if more than 1 NEAR would be burned, protecting you from losing significant funds by accident.\n\n​\n\nHow Gas Keys Pay for Transactions\n\nWhen a transaction is signed with a gas key:\n\nThe gas costs (both burned gas and gas prepaid for function calls) are charged to the gas key’s balance\n\nAny attached NEAR (deposits, transfers) is still paid from the account’s main balance\n\nGas refunds for unspent gas return to the gas key’s balance, so the key sustains itself between top-ups, while balance refunds go to the account\n\nIf the gas key’s balance cannot cover a transaction’s gas, the transaction is rejected. If the gas is covered but the account cannot pay the attached deposit at execution time, the transaction fails and the gas burned to process it is still charged to the gas key. The gas that was attached to the receipt is refunded.\n\nGas is bought at a price that can be higher than the price it burns at, so a gas key has to hold more than its transactions finally cost. The difference comes back to the key as a refund, but it has to be on the key upfront.\n\n​\n\nUsing Nonce Lanes\n\nEach of the key’s num_nonces lanes keeps its own independent nonce. A transaction signed with a gas key picks a lane through a nonce_index field (from 0 to num_nonces - 1), and only that lane’s nonce advances. Two transactions on different lanes can never conflict, so a sender can run one lane per worker and submit transactions concurrently — with a single key to manage.\nYou can inspect a gas key’s lanes with the view_gas_key_nonces RPC query, and gas keys appear in view_access_key with their balance and num_nonces.\n\nTooling supportYou can create and manage gas keys with the NEAR CLI (near account add-key ... grant-gas-key-full-access, fund-gas-key, withdraw-from-gas-key, view-gas-key-nonces) and from your app with the near-kit (TypeScript) and near-kit-rs (Rust) libraries — both cover creating, funding, withdrawing, signing on a nonce lane, and reading a key’s lanes via view_gas_key_nonces. Contracts can also add and fund gas keys through batch-promise host functions — though only the account’s own transactions can withdraw from one.\n\nGas keys also work with meta transactions: the new DelegateV2 action lets a user sign a delegate action on a gas key’s nonce lane, enabling relayers to sponsor gas end to end.\n\n​\n\nSignature Schemes\n\nIndependently of its permission level, every access key is a cryptographic key pair belonging to one of NEAR’s supported signature schemes. A public key is written as <scheme>:<base58-data>, where the prefix identifies the scheme — for example ed25519:CQLP1o1F3Jbdttek3GoRJYhzfT....\nSchemePublic key prefixPublic key sizeQuantum-resistant\nEd25519\ned25519:\n32 bytes\nNo\n\nsecp256k1\nsecp256k1:\n64 bytes\nNo\n\nML-DSA-65\nml-dsa-65:\n1952 bytes\nYes\n\ned25519 is the default scheme, used by most wallets and tooling and by NEAR implicit accounts. secp256k1 is used mainly for chain signatures and Ethereum-compatible flows. A single account can hold keys from different schemes at the same time.\n​\n\nPost-Quantum Keys (ML-DSA-65)\n\nml-dsa-65 is a post-quantum signature scheme, standardized by NIST as FIPS 204 (Module-Lattice-Based Digital Signature Algorithm, security category 3). Unlike ed25519 and secp256k1 — whose security a large enough quantum computer could break — ml-dsa-65 is designed to stay secure against quantum attacks, so an account protected by an ml-dsa-65 key cannot be taken over by forging its signature.\nYou add and use an ml-dsa-65 key exactly like any other key: it can be a full-access or a function-call key, and it signs transactions the same way.\n\nPost-quantum keys are stored by hashAn ml-dsa-65 public key is large — 1952 bytes, versus 32 for ed25519 — and its signatures are 3309 bytes. To keep accounts cheap to store, NEAR does not keep the full public key on-chain; instead it stores a 32-byte SHA3-256 hash of it — the same size as an ed25519 public key — which keeps the per-key storage cost close to that of a classical key.\n\nBecause only the hash is stored, listing an account’s keys returns the hash, not the full key, for ml-dsa-65 entries. When you query an account’s keys (for example with view_access_key_list), ml-dsa-65 keys appear with an ml-dsa-65-hash: prefix instead of ml-dsa-65::\n\nml-dsa-65-hash:7Xx2X... # base58-encoded 32-byte SHA3-256 digest\n\nTo recognize one of your own post-quantum keys in such a list, derive the same handle from your public key: it is the SHA3-256 hash of the domain-separation tag near:ml-dsa-65-pubkey-hash:v1 followed by the raw 1952-byte public key. Hashing the key without that prefix will not match the returned value. To look up a specific key directly with view_access_key, pass the full ml-dsa-65: public key and the network hashes it for you.\nYou can create and manage ml-dsa-65 keys today with the NEAR CLI, and from your app with the near-kit (TypeScript) and near-kit-rs (Rust) libraries. Contracts can add them via near-sdk-rs with no code changes.\n\nPost-quantum support currently covers transaction signing and access keys. Validator (staking) keys, block production, and implicit account addresses continue to use ed25519.\n\n​\n\nLimited Access Key Caveats\n\n​\n\nAccount with Only Function-Call Keys\n\nIf an account has no full-access keys and only function-call keys, it becomes effectively restricted:\n\nIt cannot transfer NEAR, delete itself, or manage its own keys\n\nIt can only perform the specific contract calls defined by the key’s receiver_id and method_names\n\nThis is useful for creating restricted sub-accounts (e.g. for chain signatures), but be aware the account cannot be recovered or reconfigured through standard transactions.\n\nCreating a sub-account with only a single function-call key means that account will never be able to remove itself, transfer NEAR out, or add new keys — unless the target contract provides a method to do so.\n\n​\n\nAllowance Exhaustion\n\nThe allowance field defines how much NEAR the key can spend on gas fees:\n\nIf set to a specific amount and fully consumed → the key becomes unusable and no new transactions can be signed\n\nIf set to 0 or omitted → unlimited allowance (the key has no gas budget restriction)\n\nThe allowance is charged at the buy price and credited back when the gas refund arrives, so a key needs more allowance than the final transaction cost.\n\nIf an account has only function-call keys and the allowance runs out, the account is permanently locked from initiating any transaction. Either use unlimited allowance (0) or ensure the account is topped up with NEAR before the allowance is exhausted.\n\n​\n\nLocked Accounts\n\nIf you remove all keys from an account, then the account will become locked, meaning that no external actor can perform transactions in the\naccount’s name.\nIn practice, this means that only the account’s smart contract can transfer assets, create sub-accounts, or update its code.\nLocking an account is very useful when one wants to deploy a contract, and let the community be assured that only the contract is in control of the account.\n\nAn account could still add keys to itself through a smart contract, effectively allowing the contract to unlock the account. Notice that this can only be done if the contract is deployed before the account is locked\n\nWas this page helpful?","tokens":2962,"crawled_at":1791193216451}
+{"id":10202,"url":"https://a16zcrypto.com/posts/videos/mental-models-for-real-world-cryptography","domain":"a16zcrypto.com","chapter":"research","title":"Mental models for real-world cryptography and trusted execution environments - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nMental models for real-world cryptography and trusted execution environments\nIttai Abraham\n10.23.25\n\nTags & Share Tags\nresearch\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nWhat are Trusted Execution Environments (TEEs), and should we trust them? Do we still need to trust hardware if we already trust cryptography?\n\nIn this talk, Ittai Abraham (Intel Labs) shares key learnings and mental models that help reason about the use of cryptography and TEEs. He explores how TEEs can transform many aspects of web3 architecture — including data availability, block production, consensus, execution, and layer-2 scaling — as well as emerging “layer-3” use cases such as confidential inference and secure agentic operations.\n\nHe covers two complementary paradigms: TEEs as primary security anchors, and TEEs as defense-in-depth components. The talk highlights practical trade-offs, limitations, and exciting opportunities for future systems that combine TEEs with decentralization and cryptography.\n\nAbout the presenter\n\nIttai is a technologist and computer scientist with broad interests in algorithms, security, and distributed computing. His work bridges theory and practice, spanning cryptography, blockchain systems, and critical distributed infrastructure. He is currently a Senior Principal Engineer at Intel Labs and previously held industrial research roles at VMware and Microsoft Research.\n\nAbout a16z crypto research\n\na16z crypto research is a multidisciplinary lab that works closely with our portfolio companies and others toward solving the important problems in the space, and toward advancing the science and technology of the next generation of the internet.\n\nMore about us: a16z.com/2022/04/21/announcing-a16z-crypto-research\n\nMore from the a16z crypto team\n\nSubscribe to our ‘web3 weekly newsletter’: a16zcrypto.substack.com\n\nListen to our ‘web3 with a16z’ podcast: a16zcrypto.com/web3-with-a16z-podcast/\n\nRead more of our work: a16zcrypto.com","tokens":522,"crawled_at":1791193230270}
+{"id":10203,"url":"https://www.metaplex.com/docs/smart-contracts/token-metadata/creators","domain":"www.metaplex.com","chapter":"docs","title":"Verified Creators | Token Metadata","text":"Token Metadata is a legacy program. It remains supported, but is not recommended for new projects. Use Core instead.\n\nSimilarly to collections, the creators of an asset must be verified to ensure the authenticity of the asset.\nA creator whose verified flag is false could have been added by anyone and, therefore, cannot be trusted. On the other hand, a creator whose verified flag is true is guaranteed to have signed a transaction that verified them as a creator of that asset.\nIn the section below, we will learn how to verify and unverify the creators of an asset. Note that before verifying a creator, it must already be part of the Creators array of the asset's Metadata account. This can be done when minting the asset but also when updating the asset.\nVerify a Creator\nThe Verify instruction can be used to verify the creator of an asset. Notice that the same instruction can also be used to verify collections providing we pass different arguments to the instruction. Some of our SDKs split these instructions into multiple helpers like verifyCreatorV1 and verifyCollectionV1 to provide a better developer experience.\nThe main attributes required by the Verify instruction in the context of verifying a creator are the following:\nMetadata: The address of the asset's Metadata account.\nAuthority: The creator we are trying to verify as a Signer.\nHere's how we can use our SDKs to verify a creator on Token Metadata.\n\n1import { verifyCreatorV1 } from '@metaplex-foundation/mpl-token-metadata';\n\n2\n\n3// Assuming umi, metadata, and creator are set up\n\n4\n\n5await verifyCreatorV1(umi, {\n\n6 metadata,\n\n7 authority: creator,\n\n8}).sendAndConfirm(umi);\n\n9\n\n10console.log('Creator verified');\n\n1import {\n\n2 getVerifyCreatorV1Instruction,\n\n3 findMetadataPda,\n\n4} from '@metaplex-foundation/mpl-token-metadata-kit';\n\n5\n\n6// Assuming rpc, rpcSubscriptions, sendAndConfirm, and creator (signer) are set up\n\n7\n\n8const mintAddress = 'mintAddress...'; // The NFT mint address\n\n9\n\n10// Find the metadata PDA\n\n11const [metadata] = await findMetadataPda({ mint: mintAddress });\n\n12\n\n13// Verify the creator on the NFT\n\n14const verifyIx = getVerifyCreatorV1Instruction({\n\n15 metadata,\n\n16 authority: creator,\n\n17});\n\n18\n\n19await sendAndConfirm({\n\n20 instructions: [verifyIx],\n\n21 payer: creator,\n\n22});\n\n23\n\n24console.log('Creator verified on NFT');\n\nUnverify a Creator\nReciprocally, the Unverify instruction can be used to turn the verified flag of a creator to false. It accepts the same attributes as the Verify instruction and can be used in the same way.\n\n1import { unverifyCreatorV1 } from '@metaplex-foundation/mpl-token-metadata';\n\n2\n\n3// Assuming umi, metadata, and creator are set up\n\n4\n\n5await unverifyCreatorV1(umi, {\n\n6 metadata,\n\n7 authority: creator,\n\n8}).sendAndConfirm(umi);\n\n9\n\n10console.log('Creator unverified');\n\n1import {\n\n2 getUnverifyCreatorV1Instruction,\n\n3 findMetadataPda,\n\n4} from '@metaplex-foundation/mpl-token-metadata-kit';\n\n5\n\n6// Assuming rpc, rpcSubscriptions, sendAndConfirm, and creator (signer) are set up\n\n7\n\n8const mintAddress = 'mintAddress...'; // The NFT mint address\n\n9\n\n10// Find the metadata PDA\n\n11const [metadata] = await findMetadataPda({ mint: mintAddress });\n\n12\n\n13// Unverify the creator on the NFT\n\n14const unverifyIx = getUnverifyCreatorV1Instruction({\n\n15 metadata,\n\n16 authority: creator,\n\n17});\n\n18\n\n19await sendAndConfirm({\n\n20 instructions: [unverifyIx],\n\n21 payer: creator,\n\n22});\n\n23\n\n24console.log('Creator unverified on NFT');","tokens":870,"crawled_at":1791193247812}
+{"id":10204,"url":"https://docs.synthetix.io/legacy-migration/legacy-tokens","domain":"docs.synthetix.io","chapter":"defi_protocols","title":"Legacy Tokens & Wallet Assets – Synthetix","text":"Last updated: Mar 23, 2026\n\nSynthetix has used different tokens and assets across multiple products and networks over time. If you’ve found tokens or positions in your wallet and aren’t sure what they represent, use the links below to identify the asset and understand your options.\n\nSNX\n\nIf you previously interacted with Synthetix, you may still hold SNX or have participated in a legacy staking system.\n\nFor information relating to legacy staking positions, debt, rewards, or SIP-423, please see 420 Legacy Staking.\n\nsUSD\n\nsUSD has been deprecated as part of SIP-423.\n\nEligible holders may be able to participate in the sUSD to SNX conversion process. For information regarding snapshots, eligibility, and claims, please see 420 Legacy Staking.\n\nSynths\n\nSynths were synthetic assets created through legacy Synthetix systems and are now deprecated.\nYou may still see Synths in your wallet on certain networks, but they are no longer actively supported.\n\nI have Synths on Ethereum Mainnet, what can I do with them?\n\nI have Synths on Optimism, what can I do with them?\n\nCurve LP Tokens\n\nCurve LP tokens were issued when providing liquidity through legacy Synthetix-related pools.\n\nI have Curve LP tokens, what can I do with them?\n\nLegacy Tokens (KWENTA, TLX, and Others)\n\nSome legacy Synthetix-related products issued separate tokens that may still appear in your wallet.\n\nI got KWENTA Tokens, where can I swap them for SNX?\n\nI got TLX Tokens, where can I swap them for SNX?\n\nLegacy Positions on Base or Arbitrum\n\nIf you previously held trading, liquidity, rewards, or spot positions on Base or Arbitrum:\n\nWhat happened to my old position (LP, Perps, Rewards, Spot) on Base?\n\nWhat happened to my old position (LP, Perps, Rewards, Spot) on Arbitrum?\n\nNot Sure What You’re Looking At?\n\nIf you’re unsure what a token or asset in your wallet represents:\n\nCheck the token name and symbol in your wallet\n\nSearch the Help Center for the token name\n\nStart with Asset Recovery by Network if you remember which network you used\n\nIf you still need help, contact Support and include:\n\nYour wallet address\n\nThe token name and symbol\n\nThe network the token appears on\n\nThis will help us identify the asset more quickly.","tokens":552,"crawled_at":1791193231171}
+{"id":10205,"url":"https://gov.uniswap.org/t/gli-treasury-delegation-round-2-applications/25832/12","domain":"gov.uniswap.org","chapter":"governance_daos","title":"GLI -- Treasury Delegation Round 2 Applications - #12 by Argonaut - Governance-Meta - Uniswap Governance","text":"GLI -- Treasury Delegation Round 2 Applications\n\nGovernance-Meta\n\nArgonaut\n\nSeptember 25, 2025, 7:08pm\n\n12\n\nApplicant Name: Argonaut\n\nApplicant Timezone: UTC -3\n\nLink to Delegate Forum Platform: Link\n\nLink to Snapshot Profile: Link\n\nLink to Tally/ Agora/on-chain voting profile: Link\n\nOnchain Voting Participation (%): 100%\n\nOffchain Voting Participation (%): 100%\n\nApplicant platform, including why the delegate should be elected:\n\nThe Argonaut team has been committed to Uniswap for over a year, participating consistently in governance votes. Our decision-making has always been independent, reflecting our willingness to support proposals that benefit the DAO as well as to oppose those we believe are not in its best interest.\n\nOver the past year, we have grown and matured as delegates, not only within Uniswap but also through our involvement in other protocols. This experience allows us to bring valuable insights to Uniswap, strengthening our contribution. It has also taught us how to collaborate with different teams in pursuit of the best outcomes for the DAO.\n\nLastly, we want to highlight our focus on security, fairness, and innovation. These pillars guide every voting decision we make and represent the foundation of our long-term commitment to Uniswap.\n\nI have read and agree to uphold the Delegate Principals (Y/N): Y\n\nshow post in topic\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nUniswap Delegate Reward Initiative - Cycle 4 Application and Results\n\nGovernance-Meta\n\n23\n\n868\n\nAugust 31, 2025\n\nUniswap Delegate Reward Application Thread\n\nUncategorized\n\n25\n\n2918\n\nJuly 3, 2024\n\nUniswap Delegate Reward Initiative - Cycle 2 Application\n\nGovernance-Meta\n\n40\n\n1901\n\nSeptember 16, 2024\n\n[Temperature Check]: Delegation of UNI to Active but Underrepresented Delegates\n\nTemperature Check\n\n42\n\n7596\n\nDecember 4, 2023\n\nDelegation of UNI to Active but Underrepresented Delegates Application Thread\n\nRequests for Comment\n\n12\n\n3517\n\nNovember 12, 2023","tokens":491,"crawled_at":1791193232785}
+{"id":10206,"url":"https://docs.near.org/protocol/transactions","domain":"docs.near.org","chapter":"layer1_layer2","title":"Transactions - NEAR Docs","text":"Users interact with NEAR by creating transactions. Specifically, users use their account’s private keys to sign transactions, which are then broadcasted and processed by the network.\n\nA transaction is composed of one or more Actions, and each action costs a deterministic amount of gas units. These gas units are translated into a cost in NEAR tokens, which the user must pay for the transaction to be processed.\n\nYou can use an Explorer to inspect transactions in the NEAR network\n\nWas this page helpful?","tokens":127,"crawled_at":1791193234993}
+{"id":10207,"url":"https://docs.synthetix.io/legacy-migration/op-synths","domain":"docs.synthetix.io","chapter":"defi_protocols","title":"I have Synths on Optimism, what can I do with them? – Synthetix","text":"If you are still holding Synths on Optimism (sETH, sBTC, sLINK etc.), please note that the legacy Synth system on Optimism begins deprecation on January 31, 2026.\n\nIf you hold Synths on Ethereum Mainnet instead, see I have Synths on Ethereum Mainnet, what can I do with them?.\n\nDeprecation timeline\n\nMilestoneDate\nLast day to swap Synths on Optimism\nJanuary 31, 2026\n\nOracle price is frozen for treasury redemptions\nFebruary 1, 2026\n\nDiscount applied to treasury redemptions\nApril 30, 2026\n\nRedemptions close\nDecember 31, 2026\n\nWhat this means\n\nYou can swap Synths to sUSD until January 31, 2026 using supported platforms such as:\n\nhttps://1inch.com\n\nBetween February 1 and April 30, 2026, redemption is available through Support at a fixed, frozen oracle price.\n\nFrom April 30 through December 31, 2026, a discount applies to redemptions.\n\nThe discount increases linearly at 12.5% per month of the frozen oracle price, up to 100%.\n\nAll Synth redemptions will end after December 31, 2026.\n\nsUSD to SNX Conversion\n\nFollowing SIP-423 (June 2026), legacy sUSD has been deprecated.\n\nAs a result, users redeeming Synths through the legacy redemption process will no longer receive redeemable sUSD. Instead, the sUSD value resulting from the redemption will automatically enter the 1:4 sUSD to SNX conversion process.\n\nConverted SNX is subject to:\n\nConversion ratio: 1 sUSD = 4 SNX\n\nA 1-year lock period\n\nA 1-year vesting period\n\nVested SNX must be claimed within six months of becoming available\n\nUnclaimed vested SNX may expire and become unclaimable\n\nFor additional information regarding eligibility, vesting, claim requirements, and the conversion process, please see 420 Legacy Staking.\n\nWhat you can do\n\nConfirm your wallet and network\n\nMake sure your wallet is connected to Optimism.\n\nVerify that the Synth balances appear on the Optimism network.\n\nCheck the Deprecation timeline\n\nCheck the timeline above to understand which actions are currently available.\n\nRedeem or swap your Synths (before January 31, 2026)\nSwap Synths to sUSD using:\n\nhttps://1inch.com\n\nIf you cannot swap (after January 31, 2026)\n\nContact Support and provide your wallet address.\n\nA Support agent can review your balances and advise whether redemption is still possible.","tokens":562,"crawled_at":1791193248500}
+{"id":10208,"url":"https://a16zcrypto.com/posts/videos/its-all-about-trust","domain":"a16zcrypto.com","chapter":"research","title":"It's All about Trust - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nIt's All about Trust\nIttai Abraham\n08.22.23\n\nTags & Share Tags\nresearch\nscaling & throughput\nvideo\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nIttai Abraham (Intel) surveys some of the amazing scalability advances in blockchain technologies over the past 5 years, including (1) progress in consensus protocols (partial synchrony, asynchrony, and synchrony); (2) the emergence of DAG-based data propagation protocols; and (3) blockchain execution paradigms (sharding, rollups, L2 sequencers) and how they relate to consensus and notions of asymmetric trust.\n\nAbout the speaker\n\nIttai is a senior researcher at Intel. He does research in algorithms and distributed computing. He also helps edit the blog Decentralized Thoughts (https://decentralizedthoughts.github…..\n\nAbout a16z crypto research\n\na16z crypto research is a multidisciplinary lab that works closely with our portfolio companies and others toward solving the important problems in the space, and toward advancing the science and technology of the next generation of the internet. More about us: a16z.com/2022/04/21/announcing-a16z-crypto-research","tokens":310,"crawled_at":1791193249182}
+{"id":10209,"url":"https://docs.near.org/protocol/transactions/transaction-execution","domain":"docs.near.org","chapter":"layer1_layer2","title":"Lifecycle of a Transaction - NEAR Docs","text":"Transactions are constructed by users to express the intent of performing actions in the network. Once in the network, transactions are converted into Receipts, which are messages exchanged between network nodes.\nOn this page, we will explore the lifecycle of a transaction, from its creation to its final status.\n\nRecommended ReadingTo dig deeper into transaction routing, we recommend reading the nearcore documentation\n\n​\n\nReceipts & Finality\n\nLet’s walk through the lifecycle of a complex transaction and see how it is processed by the network using blocks as time units.\n​\n\nBlock #1: The Transaction Arrives\n\nAfter a transaction arrives, the network takes one block to validate it and transform it into a single Receipt that contains all the actions to be executed.\nWhile creating the Receipt, the signer gets $NEAR deducted from its balance to pay for the gas and any attached NEAR.\nIf the signer and receiver coincide - e.g. the signer is adding a Key - the Receipt is immediately processed in this first block and the transaction is considered final.\n​\n\nBlock #2: The Receipt is Processed\n\nIf the signer and receiver differs - e.g. the signer transfers NEAR to the receiver - the Receipt is processed in a second block.\nDuring this process a FunctionCall could span a cross-contract call, creating one or multiple new Receipts.\n​\n\nBlock #3…: Function Calls\n\nEach Receipt created from the function call take an additional block to be processed. Notice that, if those Receipts are FunctionCall they could spawn new Receipts and so on.\n​\n\nFinal Block: Gas is Refunded\n\nA final Receipt is processed in a new block, refunding any extra gas paid by the user. Almost every transaction ends with one of these, since the buy price is usually higher than the burn price.\n​\n\nWaiting for a Transaction\n\nWhen using our libraries (or directly contacting the RPC), you can specify how long you want to wait for a transaction to be processed using a wait_until parameter.\nAfter a transaction is submitted, it first gets validated by the RPC node. If the transaction fails structural checks it will be immediately rejected. Otherwise, two things progress independently:\n\nExecution: the receipts spawned by the transaction are executed across shards\n\nFinality: the blocks containing the transaction and its receipts are finalized by consensus\n\nThese two axes combine to give you the following wait_until levels:\nwait_untilReceipts executed?Tx block final?Receipt outcomes in response?\nNone\n—\n—\nNo\n\nIncluded\n—\n—\nNo\n\nExecutedOptimistic\nYes (non-refund)\nNo\nYes\n\nIncludedFinal\nNot necessarily\nYes\nPartial\n\nExecuted\nYes (non-refund)\nYes\nYes\n\nFinal\nYes (all, including refunds)\nYes (all blocks)\nYes\n\nNotice that ExecutedOptimistic and IncludedFinal are not ordered relative to each other — they represent progress on different axes. ExecutedOptimistic guarantees all non-refund receipt outcomes are available but the blocks aren’t final yet. IncludedFinal guarantees the transaction’s block is final but some receipts may still be pending, so you may only get a partial set of receipt outcomes.\n​\n\nRefund receipts\n\nWhen a receipt executes, NEAR generates a refund receipt to return the unused payment to the sender: the gas that was attached but not used, plus the difference between the price the gas was bought at and the price it was burned at. These always succeed and don’t affect application logic, so ExecutedOptimistic and Executed don’t wait for them — only Final does.\n\nMost transactions will just spawn a receipt to process the actions, and a receipt to refund the gas, being final in 1-3 blocks (~1-3 seconds):\nOne block if the signer and receiver coincide - e.g. when adding a key\n\nThree blocks if the signer and receiver differ, since the first block creates the Receipt, and the last reimburses gas\n\nFunction calls might take longer, as they can spawn multiple receipts. Network congestion can also increase the time to process a receipt and, thus, a transaction.\n\n​\n\nTransaction Status\n\nAs the Receipts of a Transaction are processed, they get a status:\n\nSuccess: the actions on the receipt were executed successfully\n\nFailed: an action on the receipt failed\n\nUnknown: the receipt is not known by the network\n\nIf an action in a Receipt fails, all the actions in that Receipt are rolled back. Notice that we are talking about the Receipt status, and not the Transaction status.\nThe status of a transaction is determined by its first receipt, which contains all its actions. If any of the actions in the first receipt fail, the transaction is marked as failed.\nNotice that, it could happen that a transaction is marked as successful, but some of its receipt fails. This happens when a FunctionCall successfully spawns a new receipt, but the consequent function call fails. In this case, the transaction is marked as successful because the original function call was successful.\nSee the examples below for more details.\n\nStatus Examples\n\n​\n\nExample: Transaction with Transfer\n\nbob.near creates a transaction to transfer 10 NEAR to alice.near\n\nThe transaction is converted into a receipt\n\nThe conversion fails because bob.near does not have enough balance\n\nThe transaction is marked as failed ⛔\n\n​\n\nExample: Deploying a Contract\n\nbob.near creates a transaction to:\n\ncreate the account contract.bob.near\n\ntransfer 5 NEAR to contract.bob.near\n\ndeploy a contract in contract.bob.near\n\nThe transaction is transformed into one receipt\n\nThe account is created, the money transfer and the contract deployed\n\nThe transaction is marked as successful ✅\n\n​\n\nExample: Deploying a Contract Fails\n\nbob.near creates a transaction to:\n\ncreate the account contract.bob.near\n\ntransfer 5 NEAR to contract.bob.near\n\ndeploy a contract in contract.bob.near\n\nThe transaction is transformed into one receipt\n\nThe account is created, but the transfer fails because bob.near does not have enough balance\n\nThe whole process is reverted (i.e. no account is created)\n\nThe transaction is marked as failed ⛔\n\n​\n\nExample: Calling a Function\n\nbob.near creates a transaction to call the function cross-call in contract.near\n\nThe transaction is transformed into one receipt\n\nThe function cross-call creates a promise to call the function external-call in external.near\n\nThe function finishes correctly and the transaction is marked as successful ✅\n\nA new receipt is created to call the function external-call in external.near\n\nThe function external-call fails\n\nThe original transaction is still marked as successful ✅ because the first receipt was successful\n\nYou can check the status of a transaction using the NearBlocks explorer\n\n​\n\nNonce values\n\nThe nonce is a number that is incremented for each transaction sent by the transaction’s Signer.\nOn a valid transaction, the nonce value should follow these rules:\n\nWhen adding a key, the nonce is automatically assigned - particularly, it is given the value block height * 10^6 - so the value in the ADD_KEY action is ignored\n\nA transaction is accepted only if the nonce value is in the range of:\n\n[(current_nonce_of_access_key + 1) .. (block_height * 10^6)]\n\nOnce a transaction is accepted, the access key’s nonce is set to the nonce value of the included transaction\n\nGas keys hold one nonce per lane (up to 1,024 lanes); a transaction signed with a gas key selects a lane with its nonce_index, and the rules above apply to that lane’s nonce independently of all other lanes\n\nWas this page helpful?","tokens":1853,"crawled_at":1791193252255}
+{"id":10210,"url":"https://docs.synthetix.io/deposits-withdrawals/depositing","domain":"docs.synthetix.io","chapter":"defi_protocols","title":"Depositing Collateral – Synthetix","text":"Last updated: Jul 20, 2026\n\nSynthetix Exchange runs on Ethereum Mainnet. Deposited collateral funds the selected subaccount only, and that collateral can be used to trade USDT-settled perps markets.\n\nSupported collateral\n\nUSDT and WETH deposits are supported in the app today. Additional collateral types in the table below are planned.\n\nAssetStatusContract address (Mainnet)Notes\nUSDT\nSupported today\n0xdAC17F958D2ee523a2206206994597C13D831ec7\nBase settlement asset. No haircut.\n\nWETH\nSupported today\n0xC02aaA39b223FE8d0a0e5c4f27ead9083c756cc2\nNon-USDT collateral. Haircut applies.\n\ncbBTC\nPlanned\n0xcbB7C0000aB88B473b1f5aFd9ef808440eed33Bf\nPlanned non-USDT collateral.\n\nsUSDe\nPlanned\n0x9D39A5DE30e57443BfF2A8307A4256c8797A3497\nPlanned non-USDT collateral.\n\nwstETH\nPlanned\n0x7f39C581F595B53c5cb19bD0b3f8dA6c935E2Ca0\nPlanned non-USDT collateral.\n\nUSDT is valued at full face value for deposits. Non-USDT assets such as WETH have a haircut applied, meaning their effective collateral value is less than their market value.\n\nThe deposit flow shows per-asset minimum deposits, current and maximum account deposits, and supported collateral types for the selected subaccount.\n\nWhat you need before depositing\n\nA supported wallet connected to Ethereum Mainnet\n\nOne of the supported collateral assets in your wallet\n\nA small amount of ETH for gas\n\nHow to deposit\n\n1. Open the Deposit Window\n\nMake sure you are connected to the Synthetix Exchange.\n\nOpen the Deposit window by clicking the + button next to your available account balance. Alternatively, you can:\n\nSelect Deposit from the account sidebar.\n\nClick Deposit from the Account Balance panel.\n\nOpen the Portfolio page and click Deposit.\n\nClick the + button next to your available balance to open the Deposit window, or use Deposit from the account sidebar, Account Balance panel, or Portfolio page.\n\n2. Enter the Deposit Amount\n\nSelect the collateral asset you want to deposit.\n\nEnter the deposit amount.\n\nReview the account limits displayed.\n\nClick Deposit.\n\nSelect your collateral asset, enter the amount, review account limits, then click Deposit.\n\n3. Confirm the Deposit\n\nIf this is your first deposit for the selected asset, approve the token in your wallet.\n\nConfirm the deposit transaction in your wallet.\n\nWait for the transaction to be confirmed on Ethereum Mainnet.\n\nYour account balance will update once the transaction has been confirmed.\n\nEffective collateral value\n\nThe exchange shows effective collateral value at the time of deposit. For example, if WETH has a 90% collateral ratio, 1 WETH worth 3,000 USDT contributes 2,700 USDT of effective margin.\n\nFor the full margin model, see Leverage & Margin.\n\nGetting assets on Ethereum Mainnet\n\nIf you hold assets on another network or at a centralised exchange, you need to move them to Ethereum Mainnet first.\n\nFrom another chain:\n\nBase Bridge - for assets on Base\n\nStargate - cross-chain USDT\n\nSuperbridge - Optimism to Mainnet\n\nFrom a CEX:\nMost major exchanges, including Binance, Coinbase, and Kraken, support direct Ethereum Mainnet withdrawals. Choose \"ERC-20\" or \"ETH Network\" when withdrawing.\n\nMinimum deposits\n\nThe deposit flow may show a minimum deposit per asset. Very small deposits may also not cover gas costs for subsequent on-chain transactions.\n\nDeposit limits\n\nPer-asset minimum deposits, maximum account deposits, and other limits are shown in the deposit flow when they apply. Protocol-level TVL limits may apply during early deployment phases; the app surfaces any active limits.\n\nHaircuts can be tiered by the USD value of each asset in your account. With current per-account deposit limits, most users sit in the first tier, but you should use the Collateral Value shown in the app for your actual margin contribution.\n\nSee also\n\nMulticollateral Margin - unified margin, USDT debt, Swap, and auto-exchange.\n\nWithdrawing Collateral - withdrawal limits, USDT caps, and LTV constraints.\n\nLeverage & Margin - how collateral value is used to meet margin requirements.\n\nSub-Account - how collateral is isolated by subaccount.\n\nGetting Started - full account setup walkthrough.","tokens":1027,"crawled_at":1791193265781}
+{"id":10211,"url":"https://www.metaplex.com/docs/smart-contracts/token-metadata/delegates","domain":"www.metaplex.com","chapter":"docs","title":"Delegated Authorities | Token Metadata","text":"Token Metadata is a legacy program. It remains supported, but is not recommended for new projects. Use Core instead.\n\nHaving a single authority on our assets is not always ideal. Sometimes we want to delegate some of these responsibilities to other wallets or programs so they can do things on our behalf. This is why Token Metadata offers a whole set of delegates with different scopes.\nMetadata vs Token Delegates\nThe delegates offered by Token Metadata can be split into two categories: the Metadata Delegates and the Token Delegates. We'll go through each of them in more detail below but let's have a quick look at how they differ.\nMetadata Delegates are associated with the Mint account of the asset and allow the delegated authority to perform updates on the Metadata account. They are approved by the update authority of the asset and there can be as many as needed.\nToken Delegates are associated with the Token account of the asset and allow the delegated authority to transfer, burn and/or lock the token(s). They are approved by the owner of the asset and there can only be one per token account at a time.\nMetadata Delegates\nMetadata Delegates are delegates that operate at the Metadata level. These delegates are stored using a Metadata Delegate Record PDA — whose seeds are [\"metadata\", program id, mint id, delegate role, update authority id, delegate id].\nThat account keeps track of the Delegate authority as well as the Update Authority that approved it.\n\nWallet Account\n\nOwner: System Program\n\nToken Account\n\nOwner: Token Program\n\nMint Account\n\nOwner: Token Program\n\nPDA\n\nMetadata Account\n\nOwner: Token Metadata Program\n\nPDA\n\nMetadata Delegate Account\n\nOwner: Token Metadata Program\n\nKey = MetadataDelegate\n\nBump\n\nMint\n\nDelegate\n\nUpdate Authority\n\nReact Flow\nPress enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.\nPress enter or space to select an edge. You can then press delete to remove it or escape to cancel.\n\nHere are some key properties of Metadata Delegates:\nThere can be as many Metadata delegates as needed for a given asset.\nMetadata delegates are derived from the Mint account which means they exist regardless of the owner of the asset. Thus, transferring an asset does not affect the Metadata delegates.\nMetadata delegates are also derived from the current Update Authority of the asset. This means, whenever the Update Authority is updated on an asset, all Metadata delegates are voided and cannot be used by the new Update Authority. However, if the Update Authority was to be transferred back, all Metadata delegates associated with it would automatically reactivate.\nMetadata delegates can be revoked by the Update Authority that approved them.\nMetadata delegates can also revoke themselves.\nThere exist 7 different types of Metadata Delegates, each with a different scope of action. Here is a table summarizing the different types of Metadata Delegates:\nDelegateSelf-updatesUpdate items in collectionUpdate scope\nAuthority Item\n✅\n❌\nnewUpdateAuthority ,primarySaleHappened ,isMutable ,tokenStandard\n\nCollection\n✅\n✅\ncollection + verify/unverify collection on items\n\nCollection Item\n✅\n❌\ncollection\n\nData\n✅\n✅\ndata\n\nData Item\n✅\n❌\ndata\n\nProgrammable Configs\n✅\n✅\nprogrammableConfigs\n\nProgrammable Configs Item\n✅\n❌\nprogrammableConfigs\n\nNotice that the Metadata delegates whose name ends with Item can only act on themselves, whereas the other ones can also act on the collection items of the delegate asset. For instance, say we have a Collection NFT A that includes NFTs B and C. When we approve a Data delegate on A, we can update the data object of NFTs A, B and C. However, when we approve a Data Item delegate on A, we can only update the data object of NFT A.\nAdditionally, the Collection delegate is a little special as it also allows us to verify/unverify the delegated NFT on the items of the collection. In the example above, when we approve a Collection delegate on A, we can verify/unverify that collection on NFTs B and C.\nLet's go through each of these Metadata delegates in a bit more detail and provide code samples for approving, revoking and using them.\nAuthority Item Delegate\nThe Delegate Authority can update a sub-set of the asset. It can update the following properties of the Metadata account:newUpdateAuthority: transfers the Update Authority to another account.\nprimarySaleHappened: toggles to true when the primary sale of the asset has happened.\nisMutable: toggles to false to make the asset immutable.\ntokenStandard: can set the token standard if the asset was created before it was mandatory to set it.\n\nCollection Delegate\nThe Delegate Authority can update a sub-set of the asset. It can set the collection attribute of the Metadata account.\nWhen applied to a Collection NFT, the Delegate Authority can perform the following actions on the items inside that Collection:It can verify and unverify that Collection NFT on the item. It can only do this if the Collection NFT is already set on the item. Otherwise, there is no way of knowing that the item is part of the delegated Collection NFT.\nIt can clear the Collection NFT from the item.\n\nCollection Item Delegate\nThe Delegate Authority can update a sub-set of the asset. It can set the collection attribute of the Metadata account.\nEven if the asset is a Collection NFT, and contrary to the Collection Delegate, the Collection Item Delegate cannot affect the items of that collection.\n\nData Delegate\nThe Delegate Authority can update a sub-set of the asset. It can update the entire data object of the Metadata account but nothing else. This means it can update the creators of the asset.\nNote that when updating the creators array inside the data object, it can only add and/or remove unverified creators.\nWhen applied to a Collection NFT, the Delegate Authority can perform the same updates on the items inside that Collection.\n\nData Item Delegate\nThe Delegate Authority can update a sub-set of the asset. It can update the entire data object of the Metadata account but nothing else. This means it can update the creators of the asset.\nNote that when updating the creators array inside the data object, it can only add and/or remove unverified creators.\nEven if the asset is a Collection NFT, and contrary to the Data Delegate, the Data Item Delegate cannot affect the items of that collection.\n\nProgrammable Config Delegate\nThe Programmable Config Delegate is only relevant for Programmable Non-Fungibles.\nThe Delegate Authority can update the programmableConfigs attribute of the Metadata account but nothing else. This means it can update the ruleSet of the PNFT.\nWhen applied to a Collection NFT, the Delegate Authority can perform the same updates on the items inside that Collection.\n\nProgrammable Config Item Delegate\nThe Programmable Config Delegate is only relevant for Programmable Non-Fungibles.\nThe Delegate Authority can update the programmableConfigs attribute of the Metadata account but nothing else. This means it can update the ruleSet of the PNFT.\nEven if the asset is a Collection NFT, and contrary to the Programmable Config Delegate, the Programmable Config Item Delegate cannot affect the items of that collection.\n\nToken Delegates\nToken Delegates are delegates that operate at the Token level. This means they are spl-token delegates that are stored directly on the Token account of the SPL Token program. As such Token Delegates allow delegates to transfer and burn tokens on behalf of the owner but also lock and unlock tokens to prevent the owner from transferring, burning or even revoking the delegate. These delegates are crucial for applications like escrowless marketplaces, staking, asset loans, etc.\nWhilst there is only one type of delegate offered by the SPL Token program, Programmable NFTs (PNFTs) allowed the Token Metadata program to provide more granular delegates that can be selected on a per-case basis. This is because PNFTs are always frozen on the SPL Token program which means we can build a delegate system on top of it.\nWe store that delegate system on a PNFT-specific account called the Token Record PDA — whose seeds are [\"metadata\", program id, mint id, \"token_record\", token account id]. We synchronise the delegated authority on the SPL Token program as well but the tokens are always frozen. It is the responsibility of the Token Record account to keep track of whether the asset is really locked or not.\n\nWallet Account\n\nOwner: System Program\n\nNon-Fungibles and Semi-Fungibles\n\nToken Account\n\nOwner: Token Program\n\nDelegate Authority\n\nDelegate Amount\n\nMint Account\n\nOwner: Token Program\n\nWallet Account\n\nOwner: System Program\n\nProgrammable Non-Fungibles\n\nToken Account\n\nOwner: Token Program\n\nDelegate Authority\n\nDelegate Amount = 1\n\nToken State = Frozen\n\nMint Account\n\nOwner: Token Program\n\nPDA\n\nToken Record Account\n\nOwner: Token Metadata Program\n\nKey = TokenRecord\n\nBump\n\nState = Locked, Unlocked, Listed\n\nRule Set Revision\n\nDelegate\n\nDelegate Role\n\nLocked Transfer\n\nReact Flow\nPress enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.\nPress enter or space to select an edge. You can then press delete to remove it or escape to cancel.\n\nHere are some key properties of Token Delegates:\nThere can only be one Token Delegate per token account. Setting a new Token Delegate on the same Token account will override the existing one.\nToken delegates can be revoked by the owner of the asset as long as the asset is not locked.\nToken delegates cannot revoke themselves as they are also set on the Token Program which does not allow the delegates to self-revoke.\nToken delegates are reset on transfer. When dealing with fungible assets, the Delegate Authority is reset when all delegated tokens are transferred.\nThe Standard delegate can be used by all assets except Programmable Non-Fungibles. All other Token delegates can only be used by Programmable Non-Fungibles.\nAll Token delegates that can be used by Programmable Non-Fungibles store the current Delegate Authority, its role and its state — locked or unlocked — on the Token Record account of the PNFT.\nThere exist 6 different types of Token Delegates, each with a different scope of action. Here is a table summarizing the different types of Token Delegates:\nDelegateLock/UnlockTransferBurnForNote\nStandard\n✅\n✅\n✅\nAll except PNFTs\n\nSale\n❌\n✅\n❌\nPNFTs only\nOwner cannot transfer/burn until they revoke the delegate\n\nTransfer\n❌\n✅\n❌\nPNFTs only\nOwner can transfer/burn even when a delegate is set\n\nLocked Transfer\n✅\n✅\n❌\nPNFTs only\n\nUtility\n✅\n❌\n✅\nPNFTs only\n\nStaking\n✅\n❌\n❌\nPNFTs only\n\nNotice that the Standard delegate has a lot more power than the other PNFT-specific delegates as we must simply defer to the spl-token delegate. However, the other delegates are more granular and can be used in more specific use cases. For instance, the Sale delegate is perfect for listing assets on marketplaces since they forbid the owner to burn or transfer as long as the delegate is set.\nLet's go through each of these Token delegates in a bit more detail and provide code samples for approving, revoking and using them.\nStandard Delegate\nAs mentioned above, the Standard Delegate is a wrapper around spl-token delegates. Whilst we could simply send instructions to the Token program directly, this delegate aims to offer the same API on Token Metadata regardless of the Token Standard. Additionally, Standard Delegates are able to lock/unlock assets which is not possible with native spl-token delegates.\nHere are some key properties of the Standard Delegate:\nThis delegate does not work with Programmable Non-Fungibles.\nThe Delegate Authority can transfer the asset to any address. Doing so will revoke the Delegate Authority.\nThe Delegate Authority can burn the asset.\nThe Delegate Authority can lock the asset — also known as \"freezing\" the asset on the Token program. Until the Delegate Authority unlocks (or \"thaw\") the asset, the owner cannot transfer it, burn it, or revoke the Delegate Authority. This is specific to the Standard Delegate and cannot be done with a native spl-token delegate.\nWhen used with fungible assets, an amount greater than 1 can be provided to specify the number of tokens to delegate to the Delegate Authority.\n\nSale Delegate (PNFT only)\nThis delegate only works with Programmable Non-Fungibles.\nThe Delegate Authority can transfer the PNFT to any address. Doing so will revoke the Delegate Authority.\nAs long as a Sale Delegate is set on a PNFT, the PNFT enters a special Token State called Listed. The Listed Token State is a softer variation of the Locked Token State. During that time, the owner cannot transfer or burn the PNFT. However, the owner can revoke the Sale Delegate at any time, which will remove the Listed Token State and make the PNFT transferable and burnable again.\n\nTransfer Delegate (PNFT only)\nThis delegate only works with Programmable Non-Fungibles.\nThe Delegate Authority can transfer the PNFT to any address. Doing so will revoke the Delegate Authority.\nContrary to the Sale Delegate, when a Transfer Delegate is set, the owner can still transfer and burn the PNFT.\n\nLocked Transfer Delegate (PNFT only)\nThis delegate only works with Programmable Non-Fungibles.\nThe Delegate Authority can lock the PNFT. Until the Delegate Authority unlocks the PNFT, the owner cannot transfer it, burn it, or revoke the Delegate Authority.\nThe Delegate Authority can transfer the PNFT to any address. Doing so will revoke the Delegate Authority and unlock the PNFT if it was locked.\n\nUtility Delegate (PNFT only)\nThis delegate only works with Programmable Non-Fungibles.\nThe Delegate Authority can lock the PNFT. Until the Delegate Authority unlocks the PNFT, the owner cannot transfer it, burn it, or revoke the Delegate Authority.\nThe Delegate Authority can burn the PNFT.\n\nStaking Delegate (PNFT only)\nThis delegate only works with Programmable Non-Fungibles.\nThe Delegate Authority can lock the PNFT. Until the Delegate Authority unlocks the PNFT, the owner cannot transfer it, burn it, or revoke the Delegate Authority.\n\nLegacy Delegates\nFinally, it is worth noting that — before this delegate system — collection delegates used to be stored on a specific Collection Authority Record PDA. That PDA is similar to the Metadata Delegate Record except that it supports only one role: Collection. This legacy collection delegate is now deprecated and we recommend using the new delegate system instead.\nThat being said, the Token Metadata program still accepts these legacy collection delegates wherever a new Collection delegate is expected. This is done to ensure backward compatibility with assets that are still delegating to these legacy delegates.\nYou can learn more about them in the Token Metadata program directly.","tokens":3714,"crawled_at":1791193283941}
+{"id":10212,"url":"https://a16zcrypto.com/posts/videos/consensus-under-adversary-majority-2","domain":"a16zcrypto.com","chapter":"research","title":"Consensus under adversary majority - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nConsensus under adversary majority\nJoachim Neu\n10.29.25\n\nTags & Share Tags\nresearch\nresearch\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nA specter is haunting consensus protocols — the specter of adversary majority. Dolev and Strong in 1983 showed an early possibility for up to 99% adversaries. Yet, other works show impossibility results for adversaries above 50% under synchrony, seemingly the same setting as Dolev and Strong’s. What gives?\n\nIn this talk, Joachim Neu (a16z crypto research) pinpoints a key culprit for this ostensible contradiction: the modeling details of clients. Are the clients sleepy or always-on? Are they silent or communicating? Can validators be sleepy too? We systematize models for consensus across four dimensions (sleepy/always-on clients, silent/communicating clients, sleepy/always-on validators, and synchrony/partial-synchrony), and tightly characterize the achievable safety and liveness resiliences for each of the sixteen models. To this end, we unify folklore and earlier results, and fill gaps left in the literature with new protocols and impossibility theorems.\n\nPaper: https://eprint.iacr.org/2024/1799, a joint work with Srivatsan Sridhar, Ertem Nusret Tas, Dionysis Zindros, and David Tse.\n\nAbout the presenter Joachim is a postdoc Research Associate at a16z crypto research. He earned a PhD at Stanford, advised by David Tse. His current research focus is blockchain-era consensus and decentralized-systems security. His broader interests include distributed computing and systems, applied cryptography, and networking and communications.\n\nAbout a16z crypto research a16z crypto research is a multidisciplinary lab that works closely with our portfolio companies and others toward solving the important problems in the space, and toward advancing the science and technology of the next generation of the internet.\n\nMore about us: a16z.com/2022/04/21/announcing-a16z-crypto-research\n\nMore from the a16z crypto team S\n\nubscribe to our ‘web3 weekly newsletter’: a16zcrypto.substack.com\n\nListen to our ‘web3 with a16z’ podcast: a16zcrypto.com/web3-with-a16z-podcast/\n\nRead more of our work: a16zcrypto.com","tokens":571,"crawled_at":1791193268908}
+{"id":10213,"url":"https://gov.uniswap.org/t/argonaut-delegate-platform/24417?page=2","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Argonaut Delegate Platform - Page 2 - Delegation Pitch - Uniswap Governance","text":"Argonaut Delegate Platform\n\nDelegation Pitch\n\nArgonaut\n\nDecember 26, 2024, 12:09pm\n\n22\n\nProposal: [TEMP CHECK] Metal L2: Bridging TradFi and DeFi Through Uniswap V3\n\nVoting type & platform: Offchain - Snapshot\n\nVote: Against\n\nReasoning: We voted against it because we believe approving incentives for these low TVL L2s is not productive for Uniswap Governance.\n\nArgonaut\n\nDecember 26, 2024, 12:13pm\n\n23\n\nProposal: [TEMP CHECK] Scale Uniswap Liquidity on Celo\n\nVoting type & platform: Offchain - Snapshot\n\nVote: For\n\nReasoning: We supported this proposal because Celo’s integration into the SuperChain can create strong synergies within the ecosystem, ultimately benefiting Uniswap.\n\nArgonaut\n\nDecember 26, 2024, 12:23pm\n\n24\n\nProposal: Discretionary Budget from UAC for Co-Incentive Campaigns\n\nVoting type & platform: Offchain - Snapshot\n\nVote: Allow UAC Surplus Spending\n\nReasoning: We supported this proposal because we believe utilizing the UAC’s surplus funds, generated from UNI price appreciation, can benefit the DAO and we believe it’s good to allow some flexibility, even if it comes at the cost of relying on discretionary actions that bypass governance.\n\nArgonaut\n\nDecember 26, 2024, 12:25pm\n\n25\n\nProposal: Incentive Package for Sonic (Formerly Fantom)\n\nVoting type & platform: Offchain - Snapshot\n\nVote: $250k Incentive Match\n\nReasoning: We supported this proposal because Sonic is a promising EVM-compatible Layer 1 and the successor to Fantom, a well-established Layer 1 with a strong team behind it. We believe that matching the $250k incentive is the best decision to ensure Uniswap gains an early advantage on this network and expands its market share.\n\nArgonaut\n\nDecember 27, 2024, 2:51pm\n\n26\n\nProposal: [TEMP CHECK] Uniswap DAO Principles\n\nVoting type & platform: Offchain - Snapshot\n\nVote: For\n\nReasoning: We supported this proposal because it established a set of principles for delegates that we consider valuable. The proposer also took community feedback into account to enhance the proposal.\n\nArgonaut\n\nJanuary 23, 2025, 8:10pm\n\n27\n\nProposal: Incentive Package for Sonic\n\nVoting type & platform: Onchain - Tally\n\nVote: For\n\nReasoning: Aligned with our previous votes on Snapshot regarding this proposal, we will vote in favor because Sonic is a promising EVM-compatible Layer 1 and the successor to Fantom, a well-established Layer 1 with a strong team behind it.\n\nArgonaut\n\nJanuary 23, 2025, 8:17pm\n\n28\n\nProposal: Scale Uniswap Liquidity on Celo\n\nVoting type & platform: Onchain - Tally\n\nVote: For\n\nReasoning: We continue to support this proposal and will vote in favor because Celo’s integration into the SuperChain can generate significant synergies within the ecosystem, bringing long-term benefits to Uniswap.\n\nArgonaut\n\nJanuary 23, 2025, 8:28pm\n\n29\n\nProposal: Uniswap DAO Principles\n\nVoting type & platform: Onchain - Tally\n\nVote: For\n\nReasoning: Aligned with our previous votes on Snapshot regarding this proposal, we will vote in favor as we consider these principles valuable for delegates.\n\nArgonaut\n\nJanuary 23, 2025, 8:35pm\n\n30\n\nProposal: Governance Proposal - Adopt The SEAL Safe Harbor Agreement\n\nVoting type & platform: Onchain - Tally\n\nVote: For\n\nReasoning: Aligned with our previous votes on Snapshot regarding this proposal, we will vote in favor as the SEAL Safe Harbor Agreement establishes a clear framework to protect whitehats, ensuring responsible actions during urgent exploits while aligning with industry-standard bounties.\n\nArgonaut\n\nFebruary 19, 2025, 9:40pm\n\n31\n\nProposal: [Temp Check] Uniswap Delegate Reward Initiative - Cycle 3\n\nVoting type & platform: Offchain - Snapshot\n\nVote: Yes\n\nReasoning: The authors of the proposal have carefully considered feedback from other delegates, incorporating some into the current version while evaluating the rest for the next cycle. We support the proposal as it improves on the previous cycle’s program and is well thought out.\n\nArgonaut\n\nMarch 3, 2025, 1:33pm\n\n32\n\nProposal: Uniswap Delegate Reward Initiative - Cycle 3\n\nVoting type & platform: Onchain - Tally\n\nVote: For\n\nReasoning: We maintain our stance and continue to support this program. All Cycles have shown great benefits for the protocol, so there is no reason to oppose it. We appreciate once again that all the feedback received has been taken into account.\n\nArgonaut\n\nMarch 5, 2025, 6:09pm\n\n33\n\nProposal: [Temp Check] Uniswap Unleashed\n\nVoting type & platform: Offchain - Snapshot\n\nVote: Yes\n\nReasoning: While $95 million is a significant request, the Uniswap Foundation has played a key role in the DAO’s development and continues to work on projects that add value. The main reason for supporting this proposal is that its failure could have harmful consequences for the DAO.\n\nProposal: [Temp Check] Unichain and Uniswap v4 Liquidity Incentives\n\nVoting type & platform: Offchain - Snapshot\n\nVote: For\n\nReasoning: We support this proposal because we believe incentives on Uniswap V4 are crucial for driving migration to the new version and boosting development using hooks. So far, UniV4’s metrics haven’t been strong, and we hope this will help turn that around. However, we still think the proposal’s structure was not ideal and should have been split into separate proposals.\n\nArgonaut\n\nMarch 20, 2025, 11:03pm\n\n34\n\nProposal: Uniswap Unleashed\n\nVoting type & platform: Onchain - Tally\n\nVote: For\n\nReasoning: Aligned with our vote in Snapshot, the Uniswap Foundation has played a key role in the DAO’s development and continues to work on projects that add value. The main reason for supporting this proposal is that its failure could have harmful consequences for the DAO.\n\nProposal: Unichain and Uniswap v4 Liquidity Incentives\n\nVoting type & platform: Onchain - Tally\n\nVote: For\n\nReasoning: Aligned with our vote in Snapshot, we support this proposal because we believe incentives on Uniswap V4 are crucial for driving migration to the new version and boosting development using hooks. So far, UniV4’s metrics haven’t been strong, and we hope this will help turn that around.\n\nProposal: [Temp Check] Saga Uniswap v3 Liquidity Incentives\n\nVoting type & platform: Offchain - Snapshot\n\nVote: Against\n\nReasoning: Consistent with similar proposals, we don’t believe Saga is a chain that justifies an incentives expense from the DAO. It’s still a young chain.\n\nArgonaut\n\nMarch 27, 2025, 11:42pm\n\n35\n\nProposal: [Temp Check] Treasury Delegation Round 2\n\nVoting type & platform: Offchain - Snapshot\n\nVote: Against\n\nReasoning: While the original proposal was good, after the updates we disagreed with several points, such as the arbitrary limit of 12 delegates and knowing the selection methodology in advance, potentially allowing for deliberate exclusion of certain delegates by picking the limit of delegates to be included. Additionally, as stated in this forum post, we disagree with the methodology used to calculate the ranking of one participant for the DIP Cycle 3 criteria and scoring metrics, and this updated proposal intends to use the same method.\n\nArgonaut\n\nApril 14, 2025, 6:24pm\n\n36\n\nProposal: [TEMP CHECK] BoB Uniswap v3 Incentives Package\n\nVoting type & platform: Offchain - Snapshot\n\nVote: For $375k\n\nReasoning: As we mentioned in our comment on the proposal here, we had a dilemma. However, after giving it further thought and reading some of the opinions shared by other delegates, we have decided to support this proposal. Our main reason is the promising growth this L2 has shown and how beneficial this initial boost could be.\n\nArgonaut\n\nApril 14, 2025, 6:41pm\n\n37\n\nProposal: [TEMP CHECK] Establish Uniswap v4 Licensing Process\n\nVoting type & platform: Offchain - Snapshot\n\nVote: For\n\nReasoning: We’re voting in favor of this proposal because we think it helps make the v4 deployment process easier and faster. Giving UF the ability to deploy contracts makes sense and will help the DAO move more efficiently. It’s a good first step toward setting up a better process for future deployments.\n\nArgonaut\n\nApril 18, 2025, 1:40pm\n\n38\n\nProposal: BoB Uniswap v3 Incentives Package\n\nVoting type & platform: Onchain - Tally\n\nVote: For\n\nReasoning: Our reasoning remains consistent with the stance we shared during the Snapshot vote. The strong growth potential of this L2 is a clear sign that supporting this vote is a great opportunity.\n\nArgonaut\n\nApril 28, 2025, 1:16pm\n\n39\n\nProposal: Establish Uniswap v4 Licensing Process\n\nVoting type & platform: Onchain - Tally\n\nVote: For\n\nReasoning: Our team maintains the position taken in the Snapshot vote by voting in favor. As we have mentioned before, we are pleased with this first step as it improves the process for future implementations.\n\nArgonaut\n\nApril 28, 2025, 9:45pm\n\n40\n\nProposal: UAC Renewal S4\n\nPlatform: Offchain - Snapshot\n\nVote: Renew UAC\n\nReasoning: We support this renewal as we did with Season 3. The UAC has proven to be essential to the DAO due to their duties, and their work must continue to add value as it has, so we reaffirm our confidence in them for another season.\n\nProposal: Approved Budgets Rebalancing (S4)\n\nPlatform: Offchain - Snapshot\n\nVote: Approve Rebalance\n\nReasoning: In line with our previous rationale for rebalancing as well as reaffirming our confidence in the UAC, we voted in favor of this proposal. Since the budget was approved in USD, it makes sense to rebalance it.\n\nProposal: [Temp Check/Revised] Treasury Delegation Round 2\n\nPlatform: Offchain - Snapshot\n\nVote: Against\n\nReasoning: We came back to vote against this proposal, although it has been revised, we still see the same things we criticized before as part of the motion being pushed forward, therefore we cannot support this proposal as it stands.\n\nArgonaut\n\nMay 5, 2025, 3:45pm\n\n41\n\nProposal: [TEMP CHECK] Scaling V4 and Supporting Unichain\n\nPlatform: Offchain - Snapshot\n\nVote: For\n\nReasoning: We’ve voted in favor of this proposal. We believe that the GFXLabs team is more than capable of handling what this proposal aims to do. They have been a part of V3 and are still a great partner for the DAO due to their past contributions that have added a lot of value. The budget is not even a concern to us, considering they have even handled a $1.6M grant in the past, and have produced results far beyond the original scope of that grant. So we see no reason to oppose this proposal and its goals. GFXLabs has proven to be a trustworthy partnership. We support this expansion beyond OKU chains to further increase Uniswap’s reach.\n\nProposal: UAC Renewal S4\n\nPlatform: Onchain - Tally\n\nVote: For\n\nReasoning: We remain consistent with our position in the Snapshot instance and continue to support this proposal.\n\nProposal: Approved Budgets Rebalancing (S4)\n\nPlatform: Offchain - Onchain - Tally\n\nVote: For\n\nReasoning: Once again, we remain consistent with our position in the Snapshot instance and continue to support this proposal.\n\n← previous page\nnext page →\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nTané Delegate Platform\n\nDelegation Pitch\n\n59\n\n2404\n\nMarch 9, 2026\n\nCuria Delegate Platform\n\nDelegation Pitch\n\n53\n\n2385\n\nJuly 23, 2026\n\nSEEDGov Delegate Platform\n\nDelegation Pitch\n\n76\n\n3514\n\nMay 5, 2026\n\nIgnas Delegate Platform\n\nDelegation Pitch\n\n41\n\n1284\n\nMay 25, 2026\n\nAtiselsts.eth Delegate Platform\n\nDelegation Pitch\n\n32\n\n4670\n\nJuly 9, 2026","tokens":2820,"crawled_at":1791193270286}
+{"id":10214,"url":"https://docs.near.org/getting-started/hackathons","domain":"docs.near.org","chapter":"layer1_layer2","title":"Building on NEAR - NEAR Docs","text":"This page brings together practical resources you can use right away when building on NEAR.\n​\n\nGetting started\n\nWhat is NEAR?\nLearn NEAR basics, architecture, and why developers choose it.\n\nDeveloper support\nJoin Telegram developer chats to ask questions and get help.\n\nNeed NEAR AI credits?\nRequest NEAR AI Cloud credits for your project.\n\n​\n\nCore docs\n\nNEAR protocol basics\n\nSmart contracts quickstart\n\nWeb3 apps quickstart\n\nChain abstraction overview\n\nTools for AI agents\n\nNEAR AI documentation\n\nNEAR intents documentation\n\n​\n\nAwesome NEAR\n\nawesome-near is a community-maintained resource directory with tooling, examples, libraries, and integrations.\n\nSkills\n\nTestnet faucets\n\nNEAR protocol SDKs\n\nWallet and authentication\n\nCLI tools\n\nStarter templates\n\nData infrastructure\n\nData APIs\n\nAI and cloud services\n\nNear intents\n\nChain signatures\n\nExplorers\n\nAdditional resources\n\n​\n\nSkills\n\nPackageDescription\nagent-skills\nAI agent skills for NEAR Protocol blockchain development\n\n​\n\nTestnet faucets\n\nFaucetDescription\nCircle Faucet\n20 USDC on NEAR Testnet (claimable every 2 hours)\n\nNEAR Faucet\n2 NEAR on Testnet (rate limited)\n\n​\n\nNEAR protocol SDKs\n\n​\n\nJavaScript / TypeScript\n\nPackageDescription\nnear-api-js\nHigh-level JavaScript client for accounts, blocks, transactions, tokens, and function calls\n\nnear-api-ts\nHigh-level type-safe TypeScript client for NEAR Protocol\n\nnear-kit\nModern TypeScript client with fetch-like API\n\nnear-jsonrpc-client-ts\nAuto-generated TypeScript JSON-RPC client\n\n​\n\nRust\n\nPackageDescription\nnear-api-rs\nHigh-level Rust off-chain client for NEAR Protocol\n\nnear-sdk-rs\nRust SDK for writing NEAR smart contracts\n\nnear-abi-rs\nABI primitives and models for Rust contracts\n\n​\n\nPython\n\nPackageDescription\npy-near\nAsync Python client with HOT Protocol and NEAR Intents support\n\nnear-jsonrpc-client-py\nType-safe Pythonic JSON-RPC client with Pydantic models\n\nnear-sdk-py\nPython SDK for writing NEAR smart contracts\n\n​\n\nWallet and authentication\n\nPackageDescription\n@hot-labs/near-connect\nSecure lightweight wallet connector for JavaScript/TypeScript\n\nnear-connect-hooks\nReact hooks for NEAR wallet integration\n\nnear-sign-verify\nCreate and validate NEP-413 signed messages\n\nbetter-near-auth\nSign in with NEAR plugin for Better Auth\n\n​\n\nCLI tools\n\nPackageDescription\nnear-cli-rs\nHuman-friendly interactive CLI for NEAR Protocol\n\ncreate-near-app\nScaffold NEAR apps with frontend and contract templates\n\ncargo-near\nCargo extension for build and deploy with ABI generation\n\nnear-validator-cli-rs\nCLI companion for staking operations and validator workflows\n\n​\n\nStarter templates\n\nPackageDescription\nnear-ai-chat\nAI chat agent starter for NEAR AI Cloud\n\nNEAR Playground\nOnline IDE to create and deploy NEAR contracts\n\nnear-sdk-rs-template\nRust smart contract template\n\nNEAR-fast-ft-transfer\nHigh-performance FT transfer service\n\n​\n\nData infrastructure\n\nPackageDescription\nGoldsky\nData infrastructure and indexing service\n\nStream NEAR\nServer-Sent Events stream for real-time block data\n\nExplorer API\nTransaction-based explorer API\n\nNear Lake Indexer\nLake-based indexing service\n\n​\n\nData APIs\n\nPackageDescription\nFastNear API\nLow-latency API for wallets and explorers\n\nNearBlocks API\nREST APIs for NEAR blockchain data\n\nPikespeak API\nAggregated analytics APIs\n\nAllium API\nWallet and historical transaction API\n\n​\n\nAI and cloud services\n\nPackageDescription\nNEAR AI Cloud\nPrivate inference platform for verifiable AI inference\n\n​\n\nNear intents\n\nPackageDescription\nOne Click SDK TypeScript\nTypeScript SDK for cross-chain swaps via 1Click API\n\nOne Click SDK Rust\nRust API client for one-click swaps\n\nOne Click SDK Go\nGo API client for one-click swaps\n\nintents-sdk\nSDK for intents-based applications\n\n​\n\nChain signatures\n\nPackageDescription\nchainsig.js\nTypeScript library for multi-chain transactions and MPC signatures\n\nomni-transaction-rs\nRust library to build transactions for multiple chains\n\n​\n\nExplorers\n\nNEAR Validate\n\nNearBlocks\n\nPikespeak\n\nNear Intents Explorer\n\n​\n\nAdditional resources\n\nNEAR Intents Documentation\n\nNEP Specifications\n\nNEAR Blog\n\nNEAR Catalog\n\nWas this page helpful?","tokens":1026,"crawled_at":1791193280212}
+{"id":10215,"url":"https://a16zcrypto.com/posts/tags/research","domain":"a16zcrypto.com","chapter":"research","title":"research - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nresearch\n\nFeed\nFILTERS\n(1)\nclear filters\n\ncategories\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\n(1) recommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nclear all research\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n10.29.25 / Ling Ren\nGranular synchrony: a new network timing model for distributed computing\nToday’s mainstream network timing models for distributed computing are synchrony, partial synchrony, and asynchrony. These models are coarse grained and often make either too strong or too weak assumptions about the network. In this talk, Ling Ren (University of Illinois at Urbana-Champaign) introduces a new network timing model called “granular synchrony” that models the network...\n\nresearch\nresearch\n\n10.29.25 / Joachim Neu\nConsensus under adversary majority\nA specter is haunting consensus protocols — the specter of adversary majority. Dolev and Strong in 1983 showed an early possibility for up to 99% adversaries. Yet, other works show impossibility results for adversaries above 50% under synchrony, seemingly the same setting as Dolev and Strong’s. What gives? In this talk, Joachim Neu (a16z crypto...\n\nresearch\nresearch\n\n10.16.25 / Abhi Shelat\nPrivacy-preserving digital identity\nAnonymous digital credentials allow users to prove attributes like their age without revealing their identity. However, existing schemes have failed to achieve wide-scale deployment because they rely on new cryptographic assumptions and trusted parameter setups or require system-wide updates to both issuer infrastructure and the secure hardware on user devices. In this talk, Abhi Shelat...\n\nresearch\nresearch\n\n09.27.24 / Yevgeniy Dodis\nPerpetual encryption\nYevgeniy Dodis (NYU and IACR) considers the problem of building a private blockchain on top of a public one.\n\nresearch\ncryptography\nprivacy\nresearch\nSNARKs\nvideo\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":1166,"crawled_at":1791193287792}
+{"id":10216,"url":"https://gov.uniswap.org/t/tane-delegate-platform/24164","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Tané Delegate Platform - Delegation Pitch - Uniswap Governance","text":"Tané Delegate Platform\n\nDelegation Pitch\n\nTane\n\nJune 27, 2024, 1:56am\n\n1\n\ntane-logo480×480 10.2 KB\n\nBasic Info\n\nName: Tané\n\nDelegate Address: tanegov.eth 0xB79294D00848a3A4C00c22D9367F19B4280689D7\n\nDelegate Profile: https://www.tally.xyz/gov/uniswap/delegate/0xb79294d00848a3a4c00c22d9367f19b4280689d7\n\nX (Twitter): https://x.com/tanelabs\n\nTelegram: https://t.me/takeshi55555\n\nIntro\n\nTané is formed with a group of crypto-native product builders, based in Tokyo, Dubai and New York. We are backed by SoftBank, and Japanese tech giants like DeNA, GREE, MIXI, and closely work with the big Japanese enterprises and have great relationship with Japanese crypto communities.\n\nOur investment arm has invested in and supported various innovating projects that contribute to the decentralized society enabled by the new blockchain technology. Our network operation entity started directly contributing to the ecosystem by being validators for the core infrastructures and protocols that make Web3 move forward and contributors to the DAOs that manage them. We have been active as delegates in dYdX, Arbitrum and Optimism.\n\nTakeshi, Head of Network Operations, who worked for Twitter as a senior software engineer and for SmartNews, a Japanese unicorn startup that provides a news aggregation mobile app with 30M MAU as a product manager, is the main representative of the account.\n\nDisclosure\n\nOur investment arm has invested in a number of projects and we will take appropriate actions if potential conflict of interests arise.\n\n4 Likes\n\nTane\n\nJune 28, 2024, 6:45pm\n\n2\n\nUniswap Arbitrum LTIPP Matching (Onchain)\n\nVoting: For\n\nReasoning: We thought $500k was the best amount at the time of the snapshot as written in https://gov.uniswap.org/t/arbitrum-ltipp-incentive-matching/24066/15?u=tane, but the collaboration with Arbitrum is important to Uniswap and we think $750k matching is a reasonable amount.\n\n2 Likes\n\nTane\n\nJuly 29, 2024, 3:56pm\n\n3\n\n[Temp Check] Uniswap Onboarding Package - Gnosis Chain (Snapshot)\n\nVote: $250k\n\nRationale: As we have posted here, we believe that Gnosis Chain will benefit from more participation and contribution from the Uniswap side. We believe that $250k is a reasonable incentive amount because Linea and Scroll, which have larger TVLs than Gnosis Chain, also received $250k in incentives from Uniswap Revitalization and Growth, and we believe that Gnosis Chain should follow the similar amount to them.\n\n1 Like\n\nTane\n\nAugust 6, 2024, 1:24am\n\n4\n\n[TEMP CHECK] Uniswap Onboarding Package - OKX Chain (Snapshot)\n\nVote: Against\n\nRationale: We oppose allocating any incentives from the Uniswap DAO to X Layer because the TVL on X Layer is significantly lower than that of other chains which have previously received $250,000 in incentives.\n\nTane\n\nAugust 12, 2024, 7:09pm\n\n5\n\n[Temp Check] Forse Analytics for Uniswap Revitalization and Growth Program (Snapshot)\n\nVote:\n\nScreenshot 2024-08-12 at 3.08.37 PM1278×490 21.9 KB\n\nRationale:\n\nWe generally agree on introducing an analytics tooling for the DAO to appropriately evaluate programs that the DAO has set out. Especially for the Uniswap Revitalization and Growth Program, we were wondering how the DAO evaluates the impact made by the incentives that were distributed to each chain and revisits how we can improve the program and calibrate how we distribute future incentives.\n\nIdeally, creating an RFP based on the requirements that this proposal is addressing, asking for potential service providers to work on it and organizing an election of the SP would be the way to approach this kind of initiatives, but practically, we believe the DAO should accept the best available option by the DAO contributor with the track record.\n\nFor the selection of the chains to be analyzed, we choose Base, Scroll, and Blast according to their ranked TVL data and distributed our VP into each equally. 1) We believe with this budget as Wintermute suggested, the dashboard and analytics should cover 4 chains or more. 2) Arbitrum isn’t a part of the Uniswap Revitalization and Growth Program. While Arbitrum is a good chain to analyze on, the DAO should focus on how the program performs based on the data and insights provided by Forse. 3) Why don’t we have BSC as a selection? The DAO distributed 1M and it’s worth looking into the performance of it. If it’s in the selection, we would add BSC for a chain to be supported on the dashboard.\n\n2 Likes\n\n[Temp Check] Forse Analytics for Uniswap Revitalization and Growth Program\n\nTane\n\nAugust 12, 2024, 7:35pm\n\n6\n\nOnboarding Package for Gnosis Chain (Onchain)\n\nVote: FOR\n\nRationale: We maintain the rationale that we stated on the Snapshot and support the onboarding package for Gnosis Chain.\n\n[TEMP CHECK]- Revised - Uniswap Onboarding Package - OKX Chain (Snapshot)\n\nVote: FOR\n\nRationale: We support the deployment of Uniswap v3 and Oku Trade as we recognize the team’s commitment to providing $1M worth of liquidity in the protocol.\n\n1 Like\n\nTreasury Delegation Round 2 Ideas Thread\n\nTane\n\nAugust 16, 2024, 10:30pm\n\n7\n\n[Temp Check] Activate 2, 3, 4 bps fee tiers on Uniswap v3 on Base (Snapshot)\n\nVote: Yes, activate additional tiers\n\nRationale: We appreciate Austin’s proposal to compete with Aerodrome on Base, one of the most important battleground chains. We directionally agree with the proposal to experiment configurations to increase the protocol revenue. In addition to recognizing concerns from other delegates and community members, we would love to see a more concrete plan as it’s marked as an experiment; the plan should articulate 1) how those pools are created with minimized liquidity fragmentations 2) how the protocol reacts to fee changes by Aerodrome 3) how the DAO can evaluate the experiment success. How does the revenue increase from more market shares overweigh the decreases resulted from the lower fee pools? 4) how long the DAO experiments this and make sure the results will be properly evaluated. Who is responsible for the follow-through of the experiment? Looking forward to the complete on-chain proposal for a successful experiment to run for the protocol.\n\n1 Like\n\nTane\n\nAugust 21, 2024, 1:16pm\n\n8\n\nDeploy Uniswap v3 on X Layer (Onchain)\n\nVote: For\n\nRationale: We maintain the rationale made for its Snapshot and support the deployment of Uniswap v3 on X Layer and the cost for Oku Trade deployment.\n\n1 Like\n\nTane\n\nAugust 25, 2024, 1:21am\n\n9\n\n[REDO: Temp Check] Activate 2, 3, 4 bps fee tiers on Uniswap v3 on Base (Snapshot)\n\nVote: For\n\nRationale:\n\n[Temp Check] Uniswap Delegate Reward Initiative - Cycle 2 (Snapshot)\n\nVote: Yes\n\nRationale:\n\nWe support this Cycle 2 proposal that allows new delegates like us to apply for and contribute to the DAO governance in a potentially sustainable way. We believe it’s a positive development that the Voting Power requirement has been removed, making it easier for new delegates like us to participate in. The scoring mechanism would be iterated over and the impact the program has been making should be reviewed for the future cycle, though.\n\n1 Like\n\nTane\n\nSeptember 1, 2024, 2:25am\n\n10\n\nUniswap Delegate Reward Initiative - Cycle 2 (Onchain)\n\nVote: For\n\nRationale:\n\nWe maintain the rationale made below for its Snapshot and support the proposal for the delegate incentives.\n\nTane\n\nSeptember 11, 2024, 7:15pm\n\n11\n\n[Temp Check] - Ethereum Foundation Attackathon Sponsorship (Snapshot)\n\nVote: Do not sponsor\n\nRationale: While we agree that the Ethereum Foundation’s attacathon is trying to solve an important problem, we don’t feel strongly about the significance of sponsorship with such a large sum of money from the Uniswap DAO.\n\nProposal to active 2, 3, 4 bps fee-tiers on Base (Onchain)\n\nVote: For\n\nRationale: we maintain the rational made below for its Snapshot and support the proposal to make a significant impact by applying those changes and monitoring the data.\n\nTane\n\nSeptember 15, 2024, 2:43am\n\n12\n\nUniswap Delegate Race Tiebreaker (Snapshot)\n\nVote: Both (create an extra 16th spot)\n\nRationale: We would have voted abstain if it’s an option because we are one of the options to be chosen, but vote for Both as it’s closest to abstain. As expressed in the comment to the relevant thread, we would like to respect what the DAO decides and the outcome to be ratified on Snapshot.\n\nApproved Budgets Rebalancing (Snapshot)\n\nVote: Approved Rebalance\n\nRationale: We believe this rebalancing is necessary due to the fluctuation of the UNI token price. We would suggest that the committee should consider adding some buffer for the future programs to the budget so that the DAO doesn’t have to vote on rebalancing again.\n\nUAC Renewal S3 (Snapshot)\n\nVote: Renew UAC\n\nRationale:\n\nWe fully support increasing both the number of committee members and working hours per member because the committee that has more responsibilities and commitments should greatly benefit the DAO.\n\nWe also believe it’s crucial for the current members to continue serving on the committee, given their contributions so far. We look forward to seeing their continued efforts.\n\nThe compensation for the overtime work in Season 2 is fair and necessary, and we consider the additional funding to be justified.\n\nThe proposed budget for the committee’s compensations in the upcoming season is essential and should be approved. We would love to start supporting the committee even more in the future.\n\nTane\n\nSeptember 20, 2024, 3:45pm\n\n13\n\nUniswap Accountability S3 Renewal and Rebalance (Onchain)\n\nSummary: Uniswap Accountability Committee (UAC) has proposed a renewal of its operations for Season 3, addressing both budget rebalancing from Season 2 and the new budget for Season 3. If this proposal is approved, two key changes will be implemented; First, the number of UAC members will increase from 4 to 5, and the maximum working hours per month will rise from 10 hours to 30 hours. Second, an additional 84,594 UNI will be transferred to the UAC wallet to cover the operational budget shortfall caused by UNI’s price fluctuations, compensate committee members for their overtime work, and allocate funds to support adding the extra 16th delegate for the delegate reward initiative.\n\nVote: For\n\nRationale:\n\nWe support this proposal because it addresses the critical operational needs of the Uniswap DAO by renewing the Uniswap Accountability Committee (UAC) for Season 3 with expanded capacity and funding, rebalancing the budgets for Season 2 to account for UNI token price fluctuations, and supporting an extra 16th delegate slot for the Delegate Reward Initiative Cycle 2 to promote broader participation within the DAO; these measures strengthen the DAO’s operational capacity, enhance governance, and support its long-term objectives.\n\nTane\n\nOctober 1, 2024, 3:13am\n\n14\n\nForse Analytics for Uniswap Revitalization and Growth Program (Onchain)\n\nSummary: This proposal aims to onboard ‘Forse’ by StableLab, a data service platform, to analyze the effectiveness of the Uniswap Revitalization and Growth Program (URGP). If approved, a budget of 8,700 UNI (equivalent to $60,000) will be transferred to UAC and rewarded to StableLab at its completion.\n\nVote: FOR\n\nRationale: We support the proposal to secure a budget for analyzing the URGP using Forse. We feel that the concerns—such as including more than four chains at the Snapshot stage and that Arbitrum is not included in the URGP—have been resolved through efforts to eliminate budget issues and avoid overlap with Gauntlet. The URGP is a very important project for Uniswap, and we believe that measuring its effectiveness is essential. Initially, we thought that the UAC itself should investigate the feasibility of this project, but we feel that using Forse will allow for a detailed measurement of its effectiveness. We look forward to the detailed analysis results for the DAO to further improve the URGP.\n\nTane\n\nOctober 7, 2024, 8:35pm\n\n15\n\nUniswap Accountability Committee S3 Elections (Snapshot)\n\nSummary: This proposal is conducting the Uniswap Accountability Committee Season 3 elections to select two new members from a list of applicants.\n\nVote: 33% for _JoJo, 33% for Alicecorsini, 33% for Doo\n\nRationale: We voted for these three individuals in equal proportions because we felt they are the most capable of providing value to this committee, considering their existing contributions to the Uniswap DAO and their achievements in other DAOs. Doo has had a long tenure with the Uniswap DAO and has been active in various other DAOs. Alice, as a member of Karpatkey, has been active in multiple DAOs besides Uniswap. JoJo is engaged in delegate activities in DAOs like us on Arbitrum, and we believe their contributions make them suitable for this committee.\n\nTane\n\nOctober 12, 2024, 1:42am\n\n16\n\n[TEMP CHECK] - Onboarding Package for Lisk (Snapshot)\n\nSummary: This proposal aims to add Lisk to the Uniswap v3 deployments record and provide an “Onboarding Package” to Lisk. Uniswap will offer a total of $375,000 in UNI incentives over three months to three main pools (USDC/USDT at 0.05%, WETH/USDT at 0.30%, and LSK/ETH at 0.30%). In return, Lisk will provide $250,000 worth of LSK incentives to match Uniswap’s offer and will lock an additional $1 million in Protocol-Owned Liquidity (POL) for one year.\n\nVote: AGAINST\n\nRationale: We are opposed to this proposal.\n\nOur reason is that, compared to other chains, and considering that Lisk’s TVL is mostly composed of the LSK token, even when taking into account the promised $1 million in POL and the $250,000 Lisk incentive matching, we believe that the $375,000 incentive is too large.\n\nGnosis Chain, which had a TVL of $300 million at the time of its proposal, was allocated $250,000 in the Onboarding Package via Snapshot. We also believe that Lisk Chain’s TVL is smaller compared to Linea and Scroll, which received $250,000 in incentives through the Onboarding Package.\n\nWe think it would be better to reconsider this proposal on a smaller scale.\n\n1 Like\n\nTane\n\nOctober 21, 2024, 2:23am\n\n17\n\nUniswap Growth Program Trial (Snapshot)\n\nSummary: AlphaGrowth and ReservoirDAO propose a six-month program to grow Uniswap by expanding partnerships, enhancing marketing, and securing grants, and aim to increase its user base and market presence.\n\nVote: In Support\n\nRationale:\n\nBy establishing a program like this, the DAO can effectively communicate with projects interested in collaborating with Uniswap and execute the initiatives for users, which we believe will impact Uniswap’s market share.\n\nAdditionally, we believe that incorporating a trial period is crucial for forming a new organization. We acknowledge that the objectives for business development and marketing are clearly defined, and we feel that our previous concerns regarding the KPIs have been addressed.\n\nTane\n\nOctober 23, 2024, 10:40pm\n\n18\n\n[Updated] Forse Analytics for Uniswap Revitalization and Growth Program (Onchain)\n\nSummary: This proposal aims to engage Forse by StableLab as a data service solution to analyze the effectiveness of the Uniswap Revitalization and Growth Program across the four blockchains, with a requested budget of $60,000 worth of UNI, to provide insights that will improve future iterations of the program and other incentive initiatives.\n\nVote: FOR\n\nRationale: We strongly support this proposal, especially since we believe that accommodating more than four chains approved by its Snapshot one is essential, even more so than during the previous vote.\n\nTane\n\nOctober 27, 2024, 4:33pm\n\n19\n\nUniswap Growth Program Trial (Onchain)\n\nSummary: The Uniswap Growth Program Trial proposes a 6-month initiative to establish dedicated outbound business development and marketing teams, along with a Uniswap Ecosystem Incentives Initiative (UEII), aiming to proactively expand Uniswap’s reach, secure grants and incentives, and enhance marketing efforts to drive growth and user engagement, with a budget of $920,000.\n\nVote: FOR\n\nRationale: We maintain the support made on Snapshot as below and continue to monitor the progress of the program.\n\nTane\n\nNovember 20, 2024, 12:14pm\n\n20\n\n[TEMP CHECK] - Tally Uniswap Proposal (Snapshot)\n\nSummary: Tally is requesting a grant of $250,000 annually for two years from the Uniswap DAO to continue supporting and enhancing the DAO’s on-chain governance infrastructure, aiming to improve governance capabilities and provide a better experience for the community.\n\nVote: FOR\n\nRationale: We support this proposal. Our questions regarding the budget and the proposal’s objectives have been addressed by @dennisonb.\n\nTally is an essential service for Uniswap’s DAO governance, and we are in favor of providing this funding.\n\nnext page →\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nIgnas Delegate Platform\n\nDelegation Pitch\n\n41\n\n1284\n\nMay 25, 2026\n\nAtiselsts.eth Delegate Platform\n\nDelegation Pitch\n\n32\n\n4670\n\nJuly 9, 2026\n\nSEEDGov Delegate Platform\n\nDelegation Pitch\n\n76\n\n3514\n\nMay 5, 2026\n\nCuria Delegate Platform\n\nDelegation Pitch\n\n53\n\n2385\n\nJuly 23, 2026\n\n404 DAO Delegate Platform\n\nDelegation Pitch\n\n39\n\n3283\n\nJanuary 13, 2026","tokens":4261,"crawled_at":1791193288157}
+{"id":10217,"url":"https://www.metaplex.com/docs/smart-contracts/token-metadata/lock","domain":"www.metaplex.com","chapter":"docs","title":"Locking Assets | Token Metadata","text":"Token Metadata is a legacy program. It remains supported, but is not recommended for new projects. Use Core instead.\n\nAs mentioned in the \"Delegate Authorities\" page, certain delegates can lock and unlock assets, preventing their owners from transferring or burning them. A locked asset also forbids the owner from revoking the delegate's authority. This locking mechanism enables various utility use cases — such as staking — that would otherwise require an escrow account to function.\nIn the table below, we list all the Token Delegates that support locking assets. You can learn more about each of these delegates and how to approve/revoke them in their respective sections.\nDelegateLock/UnlockTransferBurnFor\nStandard\n✅\n✅\n✅\nAll except pNFTs\n\nLocked Transfer\n✅\n✅\n❌\npNFTs only\n\nUtility\n✅\n❌\n✅\npNFTs only\n\nStaking\n✅\n❌\n❌\npNFTs only\n\nAssuming we have an approved Token Delegate on an asset, let's now see how the delegate can lock and unlock it.\nLock an Asset\nNFT\nTo lock an asset, the delegate may use the Lock instruction of the Token Metadata program. This instruction accepts the following attributes:\nMint: The address of the asset's Mint account.\nAuthority: The signer that authorizes the lock. This must be the delegated authority.\nToken Standard: The standard of the asset being locked. Note that the Token Metadata program does not explicitly require this argument but our SDKs do so they can provide adequate default values for most of the other parameters.\n\n1import { lockV1 } from '@metaplex-foundation/mpl-token-metadata';\n\n2\n\n3// Assuming umi, mint, and authority (delegate) are set up\n\n4\n\n5await lockV1(umi, {\n\n6 mint,\n\n7 authority,\n\n8 tokenStandard: TokenStandard.NonFungible,\n\n9}).sendAndConfirm(umi);\n\n10\n\n11console.log('NFT locked');\n\n1import {\n\n2 getLockV1InstructionAsync,\n\n3 TokenStandard,\n\n4} from '@metaplex-foundation/mpl-token-metadata-kit';\n\n5\n\n6// Assuming rpc, rpcSubscriptions, sendAndConfirm, authority (delegate), and tokenOwner are set up\n\n7\n\n8const mintAddress = 'mintAddress...'; // The NFT mint address\n\n9\n\n10// Lock an NFT (freeze) - requires approved delegate authority\n\n11const lockIx = await getLockV1InstructionAsync({\n\n12 mint: mintAddress,\n\n13 authority,\n\n14 payer: authority,\n\n15 tokenOwner,\n\n16 tokenStandard: TokenStandard.NonFungible,\n\n17});\n\n18\n\n19await sendAndConfirm({\n\n20 instructions: [lockIx],\n\n21 payer: authority,\n\n22});\n\n23\n\n24console.log('NFT locked');\n\npNFT\n\n1import {\n\n2 fetchDigitalAssetWithAssociatedToken,\n\n3 lockV1,\n\n4 TokenStandard,\n\n5} from '@metaplex-foundation/mpl-token-metadata';\n\n6import { publicKey } from '@metaplex-foundation/umi';\n\n7import { base58 } from '@metaplex-foundation/umi/serializers';\n\n8\n\n9// Assuming umi is set up with mplTokenMetadata plugin\n\n10\n\n11// Mint ID of the pNFT Asset\n\n12const mintId = publicKey('11111111111111111111111111111111');\n\n13\n\n14// Fetch pNFT Asset with Token Accounts\n\n15const assetWithToken = await fetchDigitalAssetWithAssociatedToken(\n\n16 umi,\n\n17 mintId,\n\n18 umi.identity.publicKey\n\n19);\n\n20\n\n21// Send lock instruction\n\n22const { signature } = await lockV1(umi, {\n\n23 // Mint ID of the pNFT Asset\n\n24 mint: mintId,\n\n25 // Update Authority or Delegate Authority\n\n26 authority: umi.identity,\n\n27 // Token Standard\n\n28 tokenStandard: TokenStandard.ProgrammableNonFungible,\n\n29 // Owner of the pNFT Asset\n\n30 tokenOwner: assetWithToken.token.owner,\n\n31 // Token Account of the pNFT Asset\n\n32 token: assetWithToken.token.publicKey,\n\n33 // Token Record of the pNFT Asset\n\n34 tokenRecord: assetWithToken.tokenRecord?.publicKey,\n\n35}).sendAndConfirm(umi);\n\n36\n\n37console.log('Signature: ', base58.deserialize(signature));\n\n1import {\n\n2 getLockV1InstructionAsync,\n\n3 fetchDigitalAssetWithAssociatedToken,\n\n4 TokenStandard,\n\n5} from '@metaplex-foundation/mpl-token-metadata-kit';\n\n6\n\n7// Assuming rpc, rpcSubscriptions, sendAndConfirm, and authority (delegate) are set up\n\n8\n\n9const mintAddress = 'mintAddress...'; // The pNFT mint address\n\n10\n\n11// Fetch pNFT Asset with Token Accounts\n\n12const assetWithToken = await fetchDigitalAssetWithAssociatedToken(\n\n13 rpc,\n\n14 mintAddress,\n\n15 authority.address\n\n16);\n\n17\n\n18// Lock a pNFT - requires approved delegate authority\n\n19const lockIx = await getLockV1InstructionAsync({\n\n20 mint: mintAddress,\n\n21 authority,\n\n22 payer: authority,\n\n23 tokenOwner: assetWithToken.token.owner,\n\n24 token: assetWithToken.token.address,\n\n25 tokenRecord: assetWithToken.tokenRecord?.address,\n\n26 tokenStandard: TokenStandard.ProgrammableNonFungible,\n\n27});\n\n28\n\n29await sendAndConfirm({\n\n30 instructions: [lockIx],\n\n31 payer: authority,\n\n32});\n\n33\n\n34console.log('pNFT locked');\n\nUnlock an Asset\nNFT\nReciprocally, the delegate may use the Unlock instruction of the Token Metadata program to unlock an asset. This instruction accepts the same attributes as the Lock instruction and can be used in the same way.\n\n1import { unlockV1 } from '@metaplex-foundation/mpl-token-metadata';\n\n2\n\n3// Assuming umi, mint, and authority (delegate) are set up\n\n4\n\n5await unlockV1(umi, {\n\n6 mint,\n\n7 authority,\n\n8 tokenStandard: TokenStandard.NonFungible,\n\n9}).sendAndConfirm(umi);\n\n10\n\n11console.log('NFT unlocked');\n\n1import {\n\n2 getUnlockV1InstructionAsync,\n\n3 TokenStandard,\n\n4} from '@metaplex-foundation/mpl-token-metadata-kit';\n\n5\n\n6// Assuming rpc, rpcSubscriptions, sendAndConfirm, authority (delegate), and tokenOwner are set up\n\n7\n\n8const mintAddress = 'mintAddress...'; // The NFT mint address\n\n9\n\n10// Unlock an NFT (thaw) - requires approved delegate authority\n\n11const unlockIx = await getUnlockV1InstructionAsync({\n\n12 mint: mintAddress,\n\n13 authority,\n\n14 payer: authority,\n\n15 tokenOwner,\n\n16 tokenStandard: TokenStandard.NonFungible,\n\n17});\n\n18\n\n19await sendAndConfirm({\n\n20 instructions: [unlockIx],\n\n21 payer: authority,\n\n22});\n\n23\n\n24console.log('NFT unlocked');\n\npNFT\n\n1import {\n\n2 fetchDigitalAssetWithAssociatedToken,\n\n3 TokenStandard,\n\n4 unlockV1,\n\n5} from '@metaplex-foundation/mpl-token-metadata';\n\n6import { publicKey } from '@metaplex-foundation/umi';\n\n7import { base58 } from '@metaplex-foundation/umi/serializers';\n\n8\n\n9// Assuming umi is set up with mplTokenMetadata plugin\n\n10\n\n11// Mint pNFT ID of the Asset\n\n12const mintId = publicKey('11111111111111111111111111111111');\n\n13\n\n14// Fetch the mint token accounts\n\n15const assetWithToken = await fetchDigitalAssetWithAssociatedToken(\n\n16 umi,\n\n17 mintId,\n\n18 umi.identity.publicKey\n\n19);\n\n20\n\n21// Send unlock instruction\n\n22const { signature } = await unlockV1(umi, {\n\n23 // Mint ID of the pNFT Asset\n\n24 mint: mintId,\n\n25 // Update Authority or Delegate Authority\n\n26 authority: umi.identity,\n\n27 // Token Standard\n\n28 tokenStandard: TokenStandard.ProgrammableNonFungible,\n\n29 // Owner of the pNFT Assets\n\n30 tokenOwner: assetWithToken.token.owner,\n\n31 // Token Account of the pNFT Asset\n\n32 token: assetWithToken.token.publicKey,\n\n33 // Token Record of the pNFT Asset\n\n34 tokenRecord: assetWithToken.tokenRecord?.publicKey,\n\n35}).sendAndConfirm(umi);\n\n36\n\n37console.log('Signature: ', base58.deserialize(signature));\n\n1import {\n\n2 getUnlockV1InstructionAsync,\n\n3 fetchDigitalAssetWithAssociatedToken,\n\n4 TokenStandard,\n\n5} from '@metaplex-foundation/mpl-token-metadata-kit';\n\n6\n\n7// Assuming rpc, rpcSubscriptions, sendAndConfirm, and authority (delegate) are set up\n\n8\n\n9const mintAddress = 'mintAddress...'; // The pNFT mint address\n\n10\n\n11// Fetch pNFT Asset with Token Accounts\n\n12const assetWithToken = await fetchDigitalAssetWithAssociatedToken(\n\n13 rpc,\n\n14 mintAddress,\n\n15 authority.address\n\n16);\n\n17\n\n18// Unlock a pNFT - requires approved delegate authority\n\n19const unlockIx = await getUnlockV1InstructionAsync({\n\n20 mint: mintAddress,\n\n21 authority,\n\n22 payer: authority,\n\n23 tokenOwner: assetWithToken.token.owner,\n\n24 token: assetWithToken.token.address,\n\n25 tokenRecord: assetWithToken.tokenRecord?.address,\n\n26 tokenStandard: TokenStandard.ProgrammableNonFungible,\n\n27});\n\n28\n\n29await sendAndConfirm({\n\n30 instructions: [unlockIx],\n\n31 payer: authority,\n\n32});\n\n33\n\n34console.log('pNFT unlocked');","tokens":2005,"crawled_at":1791193319800}
+{"id":10218,"url":"https://stack.olas.network/open-autonomy/guides/define_agent","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Define the agent - Olas Stack Developer Documentation","text":"Define the agent\n\nThe next step consists in defining the AI agent. All agent instances in the AI agent share the same code base (blueprint).\nHowever, each operator can configure their agent instance. For example, in an oracle AI agent,\neach operator can define a different data provider.\n\nPart of the development process covered in this guide\n\nWhat you will learn\n\nThis guide covers step 3 of the development process. You will learn how to define the AI agent, how to add the FSM App, and how to add other existing components required by your agent blueprint.\n\nYou must ensure that your machine satisfies the framework requirements, you have set up the framework, and you have a local registry populated with some default components. As a result you should have a Pipenv workspace folder with an initialized local registry (./packages) in it.\n\nStep-by-step instructions\n\nIn order to deploy and run an AI agent you need an agent blueprint with a working FSM App. We base this guide on a default FSM App available in the remote registry, namely, the hello_world_abci FSM App. As a result, we will define an agent blueprint implementing a functionality equivalent to the Hello World AI agent. You can, of course, use your own FSM App to define your agent blueprint.\n\nImportant\n\nIf you have just scaffolded an FSM App in the previous step but you didn't complete coding the business logic, then an agent blueprint that uses that FSM App will fail to run. For this reason, we recommend that you use the hello_world_abci FSM App in a first read of this guide.\n\nEnsure that the components required by your agent blueprint are in the local registry. All the required components by your agent blueprint and their dependencies must be downloaded to the local registry. You can read how to add missing components to the local registry.\nIf you have populated the local registry with the required components to follow these guides, you do not need to take any further action.\n\nCreate the agent blueprint configuration file. Create a folder for your agent blueprint in the local registry (./packages). Pay attention to the correct format of the folder:\n\nmkdir -p ./packages/your_name/agents/your_agent_blueprint/\n\nWithin the agent folder, create the agent blueprint configuration file aea-config.yaml:\n\ntouch ./packages/your_name/agents/your_agent_blueprint/aea-config.yaml\n\nThis file must contain:\n\nA number of mandatory parameters.\n\nImportant\n\nEnsure that author and agent_name match the path within the local registry.\n\nA reference to the FSM App skill.\n\nReferences to other components required by the agent blueprint (or dependencies of the FSM App skill), under the relevant sections.\n\nImportant\n\nThere are a number of components which are mandatory for agent blueprints that are part of an AI agent:\n\nConnections: valory/abci.\n\nProtocols: open_aea/signing, valory/abci, valory/acn(*).\n\nSkills: valory/abstract_abci, valory/abstract_round_abci, valory/termination_abci(*).\n\n(*) Components required only if the AI agent is minted in the Olas Protocol.\n\nConfiguration overrides that specify values for component parameters. These overrides are separated by YAML document separators --- and will be discussed in a further section.\n\nExample of an aea-config.yaml file\nThis is a complete example of an agent blueprint configuration file that uses the hello_world_abci FSM App and overrides some required component parameters.\n\nYou will notice that there are a lot of parameters to be configured for the required components. For an initial read of this guide, you can ignore these parameters, but it is important that you identify how the references to the particular component parameter being overridden.\n\naea-config.yamlagent_name: your_agent_blueprint\nauthor: your_name\nversion: 0.1.0\nlicense: Apache-2.0\ndescription: Example of an agent blueprint.\naea_version: '>=2.0.0, <3.0.0'\nfingerprint: {}\nfingerprint_ignore_patterns: []\nconnections:\n- valory/abci:0.1.0\n- valory/http_client:0.23.0\n- valory/ipfs:0.1.0\n- valory/ledger:0.19.0\n- valory/p2p_libp2p_client:0.1.0\ncontracts: []\nprotocols:\n- open_aea/signing:1.0.0\n- valory/abci:0.1.0\n- valory/http:1.0.0\n- valory/ipfs:0.1.0\nskills:\n- valory/abstract_abci:0.1.0\n- valory/abstract_round_abci:0.1.0\n- valory/hello_world_abci:0.1.0\ndefault_ledger: ethereum\nrequired_ledgers:\n- ethereum\ndefault_routing: {}\nconnection_private_key_paths: {}\nprivate_key_paths: {}\nlogging_config:\nversion: 1\ndisable_existing_loggers: false\nformatters:\nstandard:\nformat: '[%(asctime)s] [%(levelname)s] %(message)s'\nhandlers:\nlogfile:\nclass: logging.handlers.RotatingFileHandler\nformatter: standard\nfilename: ${LOG_FILE:str:log.txt}\nlevel: ${LOG_LEVEL:str:INFO}\nmaxBytes: ${LOG_MAX_BYTES:int:52428800}\nbackupCount: ${LOG_BACKUP_COUNT:int:1}\nconsole:\nclass: logging.StreamHandler\nformatter: standard\nstream: ext://sys.stdout\nloggers:\naea:\nhandlers:\n- logfile\n- console\npropagate: true\ndependencies:\nopen-aea-ledger-ethereum:\nversion: ==2.2.9\nopen-aea-test-autonomy:\nversion: ==0.21.25\ndefault_connection: null\n---\npublic_id: valory/hello_world_abci:0.1.0\ntype: skill\nmodels:\nbenchmark_tool:\nargs:\nlog_dir: ${str:/benchmarks}\nparams:\nargs:\nhello_world_message: ${str:HELLO_WORLD!}\nservice_registry_address: ${str:null}\nshare_tm_config_on_startup: ${bool:false}\non_chain_service_id: ${int:null}\nsetup:\nall_participants: ${list:[]}\nsafe_contract_address: ${str:'0x0000000000000000000000000000000000000000'}\nconsensus_threshold: ${int:null}\ntendermint_url: ${str:http://localhost:26657}\ntendermint_com_url: ${str:http://localhost:8080}\n---\npublic_id: valory/abci:0.1.0\ntype: connection\nconfig:\ntarget_skill_id: valory/hello_world_abci:0.1.0\nhost: ${str:localhost}\nport: ${int:26658}\nuse_tendermint: ${bool:false}\n---\npublic_id: valory/ledger:0.19.0\ntype: connection\nconfig:\nledger_apis:\nethereum:\naddress: ${str:http://localhost:8545}\nchain_id: ${int:31337}\npoa_chain: ${bool:false}\ndefault_gas_price_strategy: ${str:eip1559}\n---\npublic_id: valory/p2p_libp2p_client:0.1.0\ntype: connection\nconfig:\nnodes:\n- uri: ${str:acn.autonolas.tech:9005}\npublic_key: ${str:02d3a830c9d6ea1ae91936951430dee11f4662f33118b02190693be835359a9d77}\n- uri: ${str:acn.autonolas.tech:9006}\npublic_key: ${str:02e741c62d706e1dcf6986bf37fa74b98681bc32669623ac9ee6ff72488d4f59e8}\ncert_requests:\n- identifier: acn\nledger_id: ethereum\nmessage_format: '{public_key}'\nnot_after: '2025-01-01'\nnot_before: '2024-01-01'\npublic_key: ${str:02d3a830c9d6ea1ae91936951430dee11f4662f33118b02190693be835359a9d77}\nsave_path: .certs/acn_cosmos_9005.txt\n- identifier: acn\nledger_id: ethereum\nmessage_format: '{public_key}'\nnot_after: '2025-01-01'\nnot_before: '2024-01-01'\npublic_key: ${str:02e741c62d706e1dcf6986bf37fa74b98681bc32669623ac9ee6ff72488d4f59e8}\nsave_path: .certs/acn_cosmos_9006.txt\nis_abstract: true\n\nYou should also create a README.md file with the description of your agent blueprint in plain text or Markdown format:\n\necho \"Your agent blueprint description.\" > ./packages/your_name/agents/your_agent_blueprint/README.md\n\nCreate an entry for your agent blueprint in the local registry. Add the corresponding entry to the local registry index file (./packages/packages.json). You must add the entry to the dev section, because it is a component being developed by you. You can use a placeholder for its hash value, as it will be corrected afterwards:\n\n{\n\"dev\": {\n\"agent/your_name/your_agent_blueprint/0.1.0\": \"bafybei0000000000000000000000000000000000000000000000000000\",\n\n},\n\"third_party\": {\n\n}\n}\n\nUpdate the package hashes. The command below will correct any hash mismatch in the aea-config.yaml file, as well as in the local registry index file (./packages/packages.json):\n\nautonomy packages lock\n\n(Optional) Run and test the agent instance locally. We will show you how to run an AI agent deployment with multiple agent instances in the next guide. However, you can also run a standalone version (that is, without being part of an AI agent) of the agent blueprint you have created. This can be useful to test and debug certain features quickly. Below we will be using the valory/hello_world agent blueprint, but you can replace it by your_name/your_agent_blueprint accordingly.\n\nIn the workspace folder, fetch the agent blueprint from the local registry:\n\nautonomy fetch valory/hello_world:0.1.0 --local\n\nProvision your agent instance with an Ethereum private key:\n\ncd hello_world\necho -n \"0x47e179ec197488593b187f80a00eb0da91f1b9d0b13f8733639f19c30a34926a\" > your_agent_key.txt\nautonomy add-key ethereum your_agent_key.txt\n\nIf your agent blueprint is using an FSM App, you also need to override the variable all_participants in the aea-config.yaml file with the wallet address of this private key as follows:\n\naea-config.yaml# (...)\nall_participants: ${list:[\"0x15d34AAf54267DB7D7c367839AAf71A00a2C6A65\"]}\n\nWARNING: Use this key for testing purposes only. Never use keys or addresses provided in this example in a production environment or for personal use.\n\nRun your agent instance:\n\nautonomy -s run\n\nAt this point, you may notice that your agent blueprint requires specific Python packages to be installed. For the valory/hello_world agent blueprint, you can do so by executing:\n\npip install hypothesis grpcio typing-extensions py-ecc asn1crypto\n\nYou can retry running your agent instance afterwards.\n\nOn a separate terminal, open a Tendermint node:\n\nrm -rf ~/.tendermint\ntendermint init\ntendermint node --proxy_app=tcp://127.0.0.1:26658 --rpc.laddr=tcp://127.0.0.1:26657 --p2p.laddr=tcp://0.0.0.0:26656 --p2p.seeds= --consensus.create_empty_blocks=true\n\nAt this point, you should see how your agent instance runs and exchanges messages with the Tendermint node. Note that, while running an isolated agent instance might be useful to quickly test and debug certain functionalities, you need to build and test a whole AI agent deployment to ensure that it works as intended.","tokens":2465,"crawled_at":1791193303491}
+{"id":10219,"url":"https://docs.synthetix.io/trading/navigating-the-app","domain":"docs.synthetix.io","chapter":"defi_protocols","title":"Navigating the App – Synthetix","text":"Last updated: Jul 8, 2026\n\nThe Synthetix Exchange brings together trading, account management, rewards, and market information in a single application. Each page in the navigation provides a different view of your account or the broader market.\n\nThis guide provides a high-level overview of each section of the Exchange. For more detailed information on specific features, please refer to the relevant documentation.\n\nTrading (Default)\n\nWhen you first connect, you'll land on the main trading page. This is where you'll spend most of your time.\n\nFrom here you can:\n\nPlace and manage orders using the order entry panel.\n\nTrack price action using the TradingView chart.\n\nMonitor the order book and recent trades.\n\nSwitch between market information tabs such as Price Charts, Depth, Funding, and Asset Details.\n\nView your positions, open orders, balances, borrowing, funding history, and profit and loss (PnL).\n\nThis page combines market data with your personal account activity so you can make trading decisions and manage risk in one place.\n\nThe default trading page brings together the chart, order book, recent trades, order entry, and account panels in a single workspace.\nRelated guides:\n\nGetting Started\n\nDepositing Collateral\n\nMarkets\n\nThe Markets page lets you browse all available perpetual markets on Synthetix, compare market statistics, and monitor overall market conditions.\n\nFrom here you can:\n\nBrowse and compare all available perpetual markets.\n\nSearch for specific markets.\n\nMark favourite markets for quick access.\n\nOpen a market directly from the Trade button.\n\nThe dashboard at the top of the page highlights key market information, including:\n\nMarket sentiment.\n\nTrading volume and open interest.\n\nMarket performance and top movers.\n\nKey market indicators, such as BTC dominance and implied volatility.\n\nYou can also switch to the Heatmap view to visualise market performance across supported assets.\n\nThe Markets page highlights overall market activity at the top and lists all available trading pairs with price, funding, open interest, volume, and quick trade access.\nRelated guides:\n\nMarkets\n\nPortfolio\n\nThe Portfolio page is your account dashboard, bringing together your balances, positions, orders, and trading activity in one place.\n\nThe Portfolio page also provides access to:\n\nOverview - View your account balance, portfolio performance, and current positions.\n\nOpen Orders - Monitor and manage your active orders.\n\nHistory - Review your trading and account activity.\n\nSub-Accounts - Create and manage separate trading accounts.\n\nReferrals - View your referral information and rewards.\n\nUse the Portfolio page to monitor your account and manage your trading activity.\n\nThe Portfolio Overview brings together account balance, performance, balances, and positions in a single dashboard.\nRelated guides:\n\nSub-Accounts\n\nReferral Program\n\nSnaxpot\n\nThe Snaxpot page lets eligible traders participate in Synthetix's weekly rewards program.\n\nFrom here you can:\n\nView your eligible tickets.\n\nChoose your ticket numbers.\n\nView the current prize pool.\n\nCheck previous draws and rewards.\n\nIf you're eligible, this is where you can manage your entries and view weekly rewards.\n\nThe Snaxpot page shows the current prize pool, draw countdown, ticket status, and options to choose numbers or view prizes.\nRelated guides:\n\nSnaxpot\n\nMore Menu\n\nThe More menu provides quick access to additional resources and information about the Exchange.\n\nFrom here you can access:\n\nChangelog - View the latest Exchange updates and release notes.\n\nStats - View protocol and market statistics.\n\nDocs - Open the Synthetix documentation.\n\nUse the More page to stay up to date with Exchange releases, explore protocol statistics, and access the documentation.\n\nVaults\n\nThe Vaults page is coming soon. For information about providing liquidity, see SLP Vault.\n\nSupport\n\nIf you need assistance while using the Exchange, click Support in the bottom-right corner of the application.","tokens":993,"crawled_at":1791193313970}
+{"id":10220,"url":"https://stack.olas.network/open-autonomy/guides/deploy_service","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Deploy the service - Olas Stack Developer Documentation","text":"Deploy the AI agent\n\nThe final step in the development process is deploying the AI agent. There are multiple deployment options to consider, such as deploying on your local machine for testing, deploying on a cluster within your own infrastructure, or deploying on a cloud provider.\n\nPart of the development process covered in this guide\n\nThe framework supports Docker Compose and Kubernetes cluster deployments. Additionally, the framework automates several steps in the deployment process for AI agents registered in the Olas Protocol.\n\nTip\n\nLocal AI agent deployments are commonly used for testing AI agents during active development. These deployments allow you to test and validate your AI agent before minting it in the Olas Protocol, ensuring its readiness for production use.\n\nWhat you will learn\n\nThis guide covers step 6 of the development process. You will learn the different types of AI agent deployments offered by the framework.\n\nYou must ensure that your machine satisfies the framework requirements, you have set up the framework, and you have a local registry populated with some default components. As a result you should have a Pipenv workspace folder with an initialized local registry (./packages) in it.\n\nLocal deployment - full workflow\n\nWe illustrate the full local deployment workflow using the hello_world AI agent as an example, both for Docker Compose and a simple Kubernetes cluster.\n\nFetch the AI agent. In the workspace folder, fetch the AI agent from the corresponding registry:\n\nLocal registryRemote registry\n\nautonomy packages lock\nautonomy push-all\nautonomy fetch valory/hello_world:0.1.0 --service --local\n\nautonomy fetch valory/hello_world:0.1.0:bafybeiabtwvve5dfuv464ypgs6jikz5rx3w3fkpej4rzn6x36zxmthuphm --service\n\nBuild the agent blueprint's image. Navigate to the AI agent runtime folder that you have just created and build the Docker image of the agent blueprint of the AI agent:\n\ncd hello_world\nautonomy build-image\n\nAfter the command finishes, you can check that the image has been created by executing:\n\ndocker image ls | grep <agent_blueprint_name>\n\nYou can find the agent_blueprint_name within the AI agent configuration file service.yaml.\n\nPrepare the keys file. Prepare a JSON file keys.json containing the wallet address and the private key for each of the agent instances that you wish to deploy in the local machine.\n\nExample of a keys.json file\nWARNING: Use this file for testing purposes only. Never use the keys or addresses provided in this example in a production environment or for personal use.\n\nkeys.json[\n{\n\"address\": \"0x15d34AAf54267DB7D7c367839AAf71A00a2C6A65\",\n\"private_key\": \"0x47e179ec197488593b187f80a00eb0da91f1b9d0b13f8733639f19c30a34926a\"\n},\n{\n\"address\": \"0x9965507D1a55bcC2695C58ba16FB37d819B0A4dc\",\n\"private_key\": \"0x8b3a350cf5c34c9194ca85829a2df0ec3153be0318b5e2d3348e872092edffba\"\n},\n{\n\"address\": \"0x976EA74026E726554dB657fA54763abd0C3a0aa9\",\n\"private_key\": \"0x92db14e403b83dfe3df233f83dfa3a0d7096f21ca9b0d6d6b8d88b2b4ec1564e\"\n},\n{\n\"address\": \"0x14dC79964da2C08b23698B3D3cc7Ca32193d9955\",\n\"private_key\": \"0x4bbbf85ce3377467afe5d46f804f221813b2bb87f24d81f60f1fcdbf7cbf4356\"\n}\n]\n\nYou also need to export the environment variable ALL_PARTICIPANTS with the addresses of all the agent instances in the AI agent. In other words, the addresses of the agent instances you are deploying (in the keys.json file) must be a subset of the addresses in ALL_PARTICIPANTS, which might contain additional addresses:\n\nexport ALL_PARTICIPANTS='[\n\"0x15d34AAf54267DB7D7c367839AAf71A00a2C6A65\",\n\"0x9965507D1a55bcC2695C58ba16FB37d819B0A4dc\",\n\"0x976EA74026E726554dB657fA54763abd0C3a0aa9\",\n\"0x14dC79964da2C08b23698B3D3cc7Ca32193d9955\"\n]'\n\nIf you have a situation where you need to define keys for multiple ledgers you can define them using the following format\n\nkeys.json[\n[\n{\n\"address\": \"4Si...\",\n\"private_key\": \"5P1...\",\n\"ledger\": \"solana\"\n},\n{\n\"address\": \"0x1...\",\n\"private_key\": \"0x1...\",\n\"ledger\": \"ethereum\"\n}\n],\n[\n{\n\"address\": \"H1R...\",\n\"private_key\": \"2T1...\",\n\"ledger\": \"solana\"\n},\n{\n\"address\": \"0x6...\",\n\"private_key\": \"0xc...\",\n\"ledger\": \"ethereum\"\n}\n],\n[\n{\n\"address\": \"3bq...\",\n\"private_key\": \"5r5...\",\n\"ledger\": \"solana\"\n},\n{\n\"address\": \"0x5...\",\n\"private_key\": \"0x7...\",\n\"ledger\": \"ethereum\"\n}\n],\n[\n{\n\"address\": \"6Gq...\",\n\"private_key\": \"25c...\",\n\"ledger\": \"solana\"\n},\n{\n\"address\": \"0x5...\",\n\"private_key\": \"0x7...\",\n\"ledger\": \"ethereum\"\n}\n]\n]\n\nBuild the deployment. Within the AI agent runtime folder, execute the command below to build the AI agent deployment:\n\nDocker ComposeKubernetes\n\nrm -rf abci_build_*\nautonomy deploy build keys.json -ltm\n\nThis will create a deployment environment within the ./abci_build_* folder with the following structure:\n\nabci_build_*/\n├── agent_keys\n│ ├── agent_0\n│ ├── agent_1\n│ | ...\n│ └── agent_<N-1>\n├── nodes\n│ ├── node0\n│ ├── node1\n│ | ...\n│ └── node<N-1>\n├── persistent_data\n│ ├── benchmarks\n│ ├── logs\n│ ├── tm_state\n│ └── venvs\n└── docker-compose.yaml\n\nrm -rf abci_build_*\nautonomy deploy build keys.json -ltm --kubernetes\n\nDelete previous deployments, if necessary.\n\n-ltm stands for \"use local Tendermint node\". Check out the autonomy deploy build command documentation to learn more about its parameters and options.\n\nThis will create a deployment environment within the ./abci_build_* folder with the following structure:\n\nabci_build_*/\n├── agent_keys\n│ ├── agent_0_private_key.yaml\n│ ├── agent_1_private_key.yaml\n│ | ...\n│ └── agent_<N-1>_private_key.yaml\n├── build.yaml\n└── persistent_data\n├── benchmarks\n├── logs\n├── tm_state\n└── venvs\n\nExecute the deployment. Navigate to the deployment environment folder (./abci_build_*) and run the deployment locally.\n\nDocker ComposeKubernetes\n\ncd abci_build_*\nautonomy deploy run\n\nThis will spawn in the local machine:\n\nN agent instances containers, each one running an instance of the corresponding FSM App.\n\na network of N Tendermint nodes, one per agent instance.\n\nWe show how to run the AI agent deployment using a local minikube cluster. You might want to consider other local cluster options such as kind.\n\nCreate the minikube Kubernetes cluster.\n\ncd abci_build_*\nminikube start --driver=docker\n\nInstall chart\n\nhelm repo add nfs-ganesha-server-and-external-provisioner https://kubernetes-sigs.github.io/nfs-ganesha-server-and-external-provisioner/\nhelm install nfs-provisioner nfs-ganesha-server-and-external-provisioner/nfs-server-provisioner \\\n--set=image.tag=v3.0.0,resources.limits.cpu=200m,storageClass.name=nfs-ephemeral -n nfs-local --create-namespace\n\nMake sure your image is pushed to Docker Hub (docker push).\nIf this is not the case, you need to provision the cluster with the agent blueprint image so that it is available for the cluster pods.\nThis step might take a while, depending on the size of the image.\n\nminikube image load <repository>:<tag>\n\nYou can get the <repository> and <tag> by inspecting the output of docker image ls.\n\nIn this case, you also might need to change all the instances of imagePullPolicy: Always to imagePullPolicy: IfNotPresent in the deployment file build.yaml.\n\nDefine the StorageClass. Replace with your NFS provisioner and adjust per your requirements. We use minikube-hostpath as an example.\n\ncat <<EOF > storageclass.yaml\napiVersion: storage.k8s.io/v1\nkind: StorageClass\nmetadata:\nname: nfs-ephemeral\nprovisioner: kubernetes.io/no-provisioner\nvolumeBindingMode: WaitForFirstConsumer\nreclaimPolicy: Retain\nEOF\n\nApply all the deployment files to the cluster\n\nkubectl apply --recursive -f .\n\nAfter executing these commands, the minikube cluster will start provisioning and starting N pods in the cluster. Each pod contains:\n\none agent instance container, running an instance of the corresponding FSM App.\n\none Tendermint node associated to the agent instance.\n\nExamine the deployment.\n\nDocker ComposeKubernetes\n\nTo inspect the logs of a single agent instance or Tendermint node you can execute docker logs <container_id> --follow in a separate terminal.\n\nYou can cancel the local execution at any time by pressing Ctrl+C.\n\nYou can access the cluster dashboard by executing minikube dashboard in a separate terminal. To examine the logs of a single agent instance or Tendermint node you can execute:\n\nGet the Kubernetes pod names.\n\nkubectl get pod\n\nAccess the logs of the agent instance in pod <pod-name>.\n\nkubectl exec -it <pod-name> -c aea -- /bin/sh\n\nAccess the logs of the Tendermint node in pod <pod-name>.\n\nkubectl exec -it <pod-name> -c node0 -- /bin/sh\n\nYou can delete the local cluster by executing minikube delete.\n\nLocal deployment of minted AI agents\n\nThe framework provides a convenient method to deploy AI agents minted in the Olas Protocol. This has the benefit that some configuration parameters of the FSM App skill will be overridden automatically with values obtained on-chain. Namely:\n\nskill.yaml# (...)\nmodels:\nparams:\nargs:\nsetup:\nall_participants: # Overridden with the registered values in the Autonolas protocol\nsafe_contract_address: # Overridden with the registered values in the Autonolas protocol\nconsensus_threshold: # Overridden with the registered values in the Autonolas protocol\n\nThis means, in particular, that there is no need to define the ALL_PARTICIPANTS environment variable.\n\nFind the AI agent ID. Explore the AI agents section in the Olas Protocol web app, and note the token ID of the AI agent that you want to deploy. The AI agent must be in Deployed state.\n\nPrepare the keys file. Prepare a JSON file keys.json containing the wallet address and the private key for each of the agent instances that you wish to deploy in the local machine.\n\nExample of a keys.json file\nWARNING: Use this file for testing purposes only. Never use the keys or addresses provided in this example in a production environment or for personal use.\n\nkeys.json[\n{\n\"address\": \"0x15d34AAf54267DB7D7c367839AAf71A00a2C6A65\",\n\"private_key\": \"0x47e179ec197488593b187f80a00eb0da91f1b9d0b13f8733639f19c30a34926a\"\n},\n{\n\"address\": \"0x9965507D1a55bcC2695C58ba16FB37d819B0A4dc\",\n\"private_key\": \"0x8b3a350cf5c34c9194ca85829a2df0ec3153be0318b5e2d3348e872092edffba\"\n},\n{\n\"address\": \"0x976EA74026E726554dB657fA54763abd0C3a0aa9\",\n\"private_key\": \"0x92db14e403b83dfe3df233f83dfa3a0d7096f21ca9b0d6d6b8d88b2b4ec1564e\"\n},\n{\n\"address\": \"0x14dC79964da2C08b23698B3D3cc7Ca32193d9955\",\n\"private_key\": \"0x4bbbf85ce3377467afe5d46f804f221813b2bb87f24d81f60f1fcdbf7cbf4356\"\n}\n]\n\nFetch the AI agent. Fetch the AI agent from the remote registry using token ID.\n\nautonomy fetch <TOKEN_ID> --use-mode\n\nFetch the AI agent with the desired token ID on Mode network.\n\nBuild the agent blueprint's image. Build the Docker image of the agent blueprint of the AI agent.\n\nautonomy build-image --service-dir your_ai_agent/\n\nThis command builds the Docker runtime images for the agent blueprint defined in an AI agent configuration file service.yaml.\n\nBuild the deployment. Build the AI agent deployment.\n\ncd your_ai_agent/\n\nThis command must be executed within an AI agent folder. That is, a folder containing the AI agent configuration file (service.yaml). The deployment will be created in the subfolder ./abci_build_*.\n\nDocker ComposeKubernetes\n\nautonomy deploy build path/to/keys.json -ltm\n\nautonomy deploy build path/to/keys.json --kubernetes\n\nCheck out the autonomy deploy build command documentation to learn more about its parameters and options.\n\nStart the AI agent. Run the AI agent:\n\nautonomy deploy run\n\nRun an AI agent deployment locally stored.\n\nCloud deployment\n\nThe sections above for local deployments provide a fundamental understanding of how to deploy AI agents in general. The Open Operator repository provides the necessary resources and guidelines for seamless cloud deployments of AI agents based on the Open Autonomy framework.","tokens":2933,"crawled_at":1791193322078}
+{"id":10221,"url":"https://docs.synthetix.io/about-synthetix/snx-token","domain":"docs.synthetix.io","chapter":"defi_protocols","title":"SNX Token – Synthetix","text":"Last updated: Jun 24, 2026\n\nSNX is the native token of the Synthetix ecosystem.\n\nThis page explains what SNX is, what changed after the retirement of legacy staking, where SNX is supported, and how the token is used today.\n\nOverview\n\nSNX was originally introduced as the core token of the Synthetix protocol.\n\nHistorically, SNX was used for staking participation, protocol incentives, debt management, and broader ecosystem participation. Following the retirement of the legacy 420 Pool staking system, SNX is no longer used in that previous staking model.\n\nSNX remains the native token of the Synthetix ecosystem. Its current protocol-related uses are more limited and are described below.\n\nCurrent Role of SNX\n\nThe legacy 420 Pool staking system has been retired, and previous SNX staking mechanisms are no longer active.\n\nToday, SNX is used within the ecosystem for:\n\nBroader ecosystem participation where supported by Synthetix governance or ecosystem initiatives\n\nDebt resolution for former 420 Pool stakers with outstanding debt\n\nSettlement in the sUSD to SNX conversion process under SIP-423\n\nFor information about the retired staking system, see 420 Legacy Staking.\n\nSupported Networks\n\nSNX is available on multiple networks.\n\nNetworkTokenContract Address\nEthereum Mainnet\nSNX\n0xC011a73ee8576Fb46F5E1c5751cA3B9Fe0af2a6F\n\nOptimism\nSNX\n0x8700daec35af8ff88c16bdf0418774cb3d7599b4\n\nHow to Acquire SNX\n\nSNX may be acquired through supported centralised exchanges and decentralised exchanges.\n\nBefore purchasing SNX, users should:\n\nVerify the correct network\n\nConfirm the token contract address\n\nEnsure their wallet supports the selected network\n\nUsers should always verify the network and token contract address before purchasing or transferring SNX.\n\nBridging SNX\n\nSNX can be transferred between supported networks using compatible bridge providers, such as Superbridge.\n\nBefore bridging SNX:\n\nConfirm the destination network is supported\n\nVerify the token contract address on both networks\n\nEnsure the receiving wallet supports the destination network\n\nConfirm the selected bridge supports SNX transfers\n\nBridge availability, transfer times, and fees vary by provider and network.\n\nFuture Utility\n\nFuture SNX utility may be introduced through protocol upgrades, governance proposals, or ecosystem initiatives.\n\nAreas that may be considered in future Synthetix development include:\n\nNew SNX staking or participation mechanisms\n\nSNX buybacks using earned protocol fees\n\nSNAXPOT-related eligibility or ticket multipliers\n\nAdditional ecosystem incentives\n\nOther governance-approved participation mechanisms\n\nThese features are not currently active unless separately announced through official Synthetix governance or ecosystem channels.\n\nAdditional Resources\n\nFor the latest information about SNX, refer to official Synthetix announcements, governance proposals, and protocol updates.","tokens":722,"crawled_at":1791193331247}
+{"id":10222,"url":"https://docs.near.org/getting-started/faucet","domain":"docs.near.org","chapter":"layer1_layer2","title":"Token Faucet - NEAR Docs","text":"A faucet provides free testnet tokens for testing and development purposes.\nThere are two testnet faucets: the built‑in faucet on this page - which provides native testnet NEAR only - and the Testnet Faucet, which supports many fungible tokens (NEAR, USDT, and more).\n\nIf any of the faucets is not working, please report it on our NEAR Telegram Channel\n\n​\n\nFaucet\n\nSimply introduce the account you want to receive the tokens in, and click on the “Request” button. The faucet will send a small amount of testnet NEAR tokens to that account.\n\nNEAR Testnet FaucetGet free NEAR tokens for testing\n\nTestnet Account ID\nNot working? Report on Telegram\n\n​\n\nExternal Faucet\n\nNavigate to the Testnet Faucet page, input your address and select which type of token you need! The faucet supports a wide range of fungible tokens, including NEAR, Tether USD, Ether, and many others.\n\nPlease know that the faucet might be out of tokens at times, keep reading below for alternative ways to get other fungible tokens\n\n​\n\nGetting Fungible Tokens\n\nAnother way to get fungible tokens on testnet is through the testnet version of ref finance\nThere, you can swap testnet NEAR for other fungible tokens, such as testnet USDC, testnet USDT, testnet DAI, and others\n\nPlease notice that tokens on testnet might not hold the same rate as on mainnet (e.g. 1 USDC might not exchange to the same amount of NEAR as on mainnet), furthermore, liquidity on testnet might be very low\n\nWas this page helpful?","tokens":368,"crawled_at":1791193339691}
+{"id":10223,"url":"https://docs.synthetix.io/about-synthetix/synthetix-history","domain":"docs.synthetix.io","chapter":"defi_protocols","title":"Synthetix History","text":"Last updated: Mar 24, 2026\n\nSynthetix began in 2018 as Havven, a protocol for decentralized stablecoins. In 2019, Synthetix v2 launched, pioneering the minting of synthetic assets, including crypto assets, indices, and traditional finance (TradFi) assets, on Ethereum. This innovation established Synthetix as a leader in on-chain derivatives and composable DeFi infrastructure.\n\nSynthetix v2: Enabled users to stake SNX and mint sUSD, with a wide range of synthetic assets and the first on-chain decentralized exchange for synthetics.\n\nPerps v2 (Optimism): Introduced decentralized perpetual futures trading, bringing deep liquidity and new trading opportunities to Layer 2. This system is now considered legacy.\n\nPerps v3 and Synthetix v3: Marked a major architectural shift, enabling cross-margin trading, multi-collateral support, and a modular, upgradable protocol. V3 deployments expanded to Base and Arbitrum, but the focus has returned to Ethereum Mainnet for the next generation of Synthetix products.\n\nThroughout its history, Synthetix has been at the forefront of DeFi innovation, from synthetic assets to on-chain derivatives and advanced staking models. The protocol's community-driven governance and continuous upgrades have kept it relevant and resilient through multiple market cycles.","tokens":326,"crawled_at":1791193348081}
+{"id":10224,"url":"https://a16zcrypto.com/team/andrew-lewis-pye","domain":"a16zcrypto.com","chapter":"research","title":"Andrew Lewis-Pye - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nAndrew Lewis-Pye\n\nFeed\nFilter\n(1)\nclear filters\n\ncategory\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\nrecommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nauthor\n(1) all authors\n@x0rart\n1337 Skulls Sers\na16z crypto\na16z crypto editorial\na16z crypto policy & regulatory teams\na16z crypto Regulatory Team\nAaditya Shidham\nAaron Levie\nAaron Phillips\nAaron Schnider\nAbby Green\nAbdou Ndiaye\nAbhi Shelat\nAbhiram Kothapalli\nAbigail Johnson\nAdam Alter\nAdam Back\nAdam Bry\nAdam Grant\nAdam Ludwin\nAdam Martin\nAdam Thierer\nAdam Zuckerman\nAdela Tomsejova\nAdena Friedman\nAdena Hefets\nAdeniyi Abiodun\nAdina Fischer\nAdrian Cockcroft\nAdrian Fenty\nAdrienne Mayor\nAgostino Capponi\nAiden Slavin\nAileen Lee\nAisha Stephenson\nAJ Shankar\nAlan Knott-Craig\nAlan Schaaf\nAlana Benton\nAlbert Tang\nAlec Nielsen\nAlec Ross\nAlejandro Flores\nAlex Constantinople\nAlex Honnold\nAlex Hutchinson\nAlex Immerman\nAlex Kreitz\nAlex Kroeger\nAlex Le\nAlex Masmej\nAlex Morcos\nAlex Price\nAlex Pruden\nAlex Rampell\nAlex Roetter\nAlex Solomon\nAlex Spector\nAlex Stamos\nAlex Tabarrok\nAlexander (Sasha) Spiegelman\nAlexander Chia\nAlexander Zoppa\nAlexandra Chang\nAlexandria Lafci\nAlexis Lakes\nAlexis Madrigal\nAlexis Ohanian\nAli Ghodsi\nAli Yahya\nAlicia Barone\nAlin Tomescu\nAlisha Litman\nAlison Mangiero\nAlison Martin\nAllison Pickens\nAlyssa Del Bene\nAlyssa Torres\nAmanda Cantor\nAmanda Cassatt\nAmanda Catherine\nAmanda Mulay\nAmanda Tuminelli\nAmanda Tyler\nAmelia Salyers\nAmie Tyrrel\nAmir Shevat\nAmira Yahyaoui\nAmy Abernethy\nAmy Berliner\nAmy Bohutinsky\nAmy Choice\nAmy Cray\nAmy Gill\nAmy Hoemeke\nAmy Kalokerinos\nAmy Robertson\nAna Mostarac\nAna Susi\nAnatoly Yakovenko\nAndie Taylor\nAndisheh Tahriri\nAndre Iguodala\nAndrea Clarke Hall\nAndrea Feinberg\nAndrea Rallo\nAndrea Simon\nAndrea Vinkler\nAndreas Papadimitropoulos, Jr\nAndreessen Horowitz\nAndrew Allen\nAndrew Chen\nAndrew F. Read\nAndrew Green\nAndrew Hall\nAndrew Lakis\nAndrew Lewis-Pye\nAndrew Lo\nAndrew Mason\nAndrew McAfee\nAndrew Milson\nAndrew Omori\nAndrew Radin\nAndrew Rubin\nAndrew Savage\nAndrew Smith\nAndrew Tretyakov\nAndy Beal\nAndy Coravos\nAndy Golden\nAndy Hill\nAndy Milenius\nAndy Rachleff\nAndy Tran\nAndy Walshe\nAneel Lakhani\nAngela Schenone\nAngela Strange\nAngela Tran Kingyens\nAngelica Gehr\nAniket Kate\nAnil Sethi\nAnish Acharya\nAnn Winblad\nAnna Berces\nAnna Jablonski\nAnna Semenova\nAnna Van Meurs\nAnnaLee Saxenian\nAnne Brandes\nAnne Lee Skates\nAnne Lewandowski\nAnne Mitchell\nAnne Yip\nAnnie Collins\nAnnie Duke\nAnthony Albanese\nAnthony Atala\nAnthony Foxx\nAnthony Lee Zhang\nAntonio Viggiano\nAntwone Stigall\nAnu Hariharan\nApril Roth\nAri Emanuel\nAri Juels\nArianna Huffington\nArianna Simpson\nArik Kershenbaum\nArmon Dadgar\nArnie Goldberg\nArsho Avetian\nArthur Brooks\nArun Sundararajan\nAsh Ashutosh\nAsha Christian\nAshley McCollum\nAshley Stern\nAshton Carter\nAtif Mian\nAtul Butte\nAubree Pelaez\nAubrey de Grey\nAugusto Marietti\nAurora Petracca\nAusten Allred\nAustin Guzman\nAustin Marchese\nAustin Wilson\nAva Iravani\nAvery Segal\nAvinash Solanky\nAviv Zohar\nAye Moah\nAzeem Azhar\nBailey Flanigan\nBailey Richardson\nBalaji Srinivasan\nBarry McCarthy\nBart Dessaint\nBeau Cronin\nBeau Woods\nBecky Pferdehirt\nBen Buckwalter\nBen Fielding\nBen Fisch\nBen Gardner\nBen Gomez\nBen Horowitz\nBen Kaufman\nBen Leventhal\nBen Lovell\nBen Napier\nBen Portney\nBen Rubin\nBen Scharfstein\nBen Schecter\nBen Silbermann\nBen Uretsky\nBen Wu\nBenedict Evans\nBenedikt Büenz\nBenjamin Ebner\nBenjamin Hindman\nBenjamin Wittes\nBenjamin Wu\nBennett Carroccio\nBenny Pinkas\nBernard J. Tyson\nBernard Tyson\nBeth Newman\nBethany Coates\nBharat Ramamurti\nBharath Ramsundar\nBill Carr\nBill Frist\nBill Hinman\nBill Janeway\nBill Krause\nBill Macaitis\nBlake Kim\nBlake Masters\nBlake Saari\nBlayne Donnell\nBob Iger\nBob Langer\nBob Moore\nBob Muglia\nBob Sutton\nBob Swan\nBob Tinker\nBob Wachter\nBobby Franklin\nBobby Green\nBobby Kotick\nBobby Wagner\nBoris Sofman\nBoris Wertz\nBrad Feld\nBrad Kern\nBrad Peterson\nBram Cohen\nBrandon Ballinger\nBrandon Barros\nBrandon Cherry\nBrandon Millman\nBrenda Kopf\nBrent McIntosh\nBrett Browman\nBrett Falk\nBrett Hagler\nBrewster Kahle\nBrian Armstrong\nBrian Balfour\nBrian Brooks\nBrian Crnkovich\nBrian Curran\nBrian Grazer\nBrian Koppelman\nBrian McCullough\nBrian Quintenz\nBrian Wilkins\nBridget McDowell\nBrittany Lucas\nBrittney Burrows\nBrooke Sheresky\nBruce Friedrich\nBryan Caplan\nBryan Chiang\nBryan Cox\nBryan Crowley\nBryan Faust\nBryan Houser\nBryan Kim\nBryan Pellegrino\nCaitlin Glazebrook\nCaitlin Johnston\nCaitlin Roberson\nCal Turner Jr.\nCaleb Christian\nCameron Schuler\nCamila De Souza\nCarine Carmy\nCarissa Bilinski\nCarl Agnelli\nCarl Eschenbach\nCarl Narcisse\nCarl Pope\nCarlos Araya\nCarolina Gonzalez\nCaroline Friedman\nCaroline Goggins\nCaroline Horn\nCaroline Moon\nCarolyn Bertozzi\nCarra Wu\nCasey Graul\nCasey Neistat\nCasey Winters\nCassady Churchill\nCassie Faerber\nCecilia Marshall\nCeia Font\nChad Rigetti\nChandra Krintz\nCharles Goetz\nCharles Hubbard\nCharles Koch\nCharlie Keinath\nCharlie Warzel\nChattry Meas\nChelsea Komlo\nChelsea Padilla\nCheng Li\nChris Bennett\nChris Best\nChris Burniske\nChris Curran\nChris DeWolfe\nChris Dixon\nChris Granger\nChris Hauth\nChris Lyons\nChris Messina\nChris Milk\nChris Power\nChris Santa Maria\nChris Wanstrath\nChristian Cachin\nChristian Catalini\nChristian Crowley\nChristian Seifert\nChristina Hampp\nChristina Lopes\nChristina Mercando\nChristina Xu\nChristina Zeidan\nChristine Darden\nChristine Perham\nChristopher Giancarlo\nChristopher Lee\nChristopher Mims\nChristopher Nguyen\nChristopher Rippingham\nChristopher Schroeder\nChristy Hubbard\nCiamac Moallemi\nCindi Zhang\nCindy Tenner\nClaire Austin\nClaire Cain Miller\nClaire Kart\nClaudia Picanco\nClay Shirky\nClayton Christensen\nClayton Gardner\nClifford Woolf\nClint Delapaz\nColin Bryar\nColin Rom\nCollin McCune\nConner Lyons Brown\nConnie Chan\nConnie Guglielmo\nConnor McCarthy\nConnor Moyles\nCorban Bell\nCorey Hawkins\nCorey Waller\nCourtney Dettlinger\nCraig Naylor\nCraig Walker\nCristina Cordova\nCurt Funderburk\nCuy Sheffield\nD'Arcy Coolican\nDaejun Park\nDaisy Linden\nDaisy Wolf\nDaljeet Virdi\nDalton Turay\nDan Berkenstock\nDan Boneh\nDan Frommer\nDan Primack\nDan Romero\nDan Shapero\nDan Siroker\nDan Stein\nDan Warmenhoven\nDan Wendlandt\nDaniel Chao\nDaniel Chen\nDanielle Andrzejewski\nDanielle Clark\nDanielle Looymans\nDanielle Lussier\nDanielle Morrill\nDanielle Shea\nDanny Shader\nDaphne Koller\nDapper Dan\nDaren Matsuoka\nDarin Malter\nDarshan Shankar\nDas Rush\nDave Jagoda\nDave King\nDave Touretzky\nDavid Banks\nDavid Belden\nDavid Damato\nDavid Deming\nDavid George\nDavid Haber\nDavid Hollestelle\nDavid Kerr\nDavid Lee\nDavid Mack\nDavid Madden\nDavid Marcus\nDavid Olson\nDavid Oyelowo\nDavid Pierce\nDavid Reich\nDavid Rumsey\nDavid Schweikert\nDavid Sinclair\nDavid Sverdlov\nDavid Tse\nDavid Ulevitch\nDavid Weiden\nDawn Lepore\nDawn Nott\nDeborah Embaie\nDeena Elitreby\nDeepak Maram\nDenis Nazarov\nDenis Young\nDenise Gonzalez\nDerek Dolin\nDerek Thompson\nDerrick Harris\nDevin Finzer\nDevon Zuegel\nDiana Peña\nDiane Greene\nDick Costolo\nDieter Shirley\nDiishan Imira\nDiogo Monica\nDominic Shine\nDominique Reliford\nDon Duet\nDon Faul\nDorris O'Brien\nDoug Ducey\nDoug Folden\nDoug McCracken\nDouglas Argueta\nDozie Uche\nDrew Coffman\nDylan Field\nDylan Rhodes\nEd Felten\nEd Lynch\nEddie Lim\nEddy Lazzarin\nEdith Zimmerman\nEdward Perkins\nEdwin Poston\nEfrat Noy\nEhud Shapiro\nEileen Burbidge\nEileen Wu\nElad Gil\nElaine Fuchs\nElaine Shi\nElena Burger\nEli Dourado\nElisa Leonhardt\nEliza Oak\nElizabeth Gunn\nElizabeth Harkavy\nElizabeth May\nElizabeth Ocken\nElizabeth Stark\nElizabeth Weil\nEllen Tunoa\nEmile Petrone\nEmilio Torres\nEmily Graff\nEmily Hinsch\nEmily Keir\nEmily Oster\nEmily Westerhold\nEmma Janaskie\nEric Budish\nEric Dai\nEric Ries\nEric Thomas\nEric Topol\nEric Wu\nErica Schecter\nErik Brynjolfsson\nErik Kiser\nErik Torenberg\nErika Bracken\nErika Herrera\nErika Louie\nErin Grody Kingsley\nErin Murphy\nErin Tice\nErin Tonnar\nErin Winkler\nErtem Nusret Tas\nEsther Shinn\nEthan Bueno de Mesquita\nEthan Ferreira\nEthan Zuckerman\nEuan Ashley\nEugene Volokh\nEugene Wei\nEugenia Yee\nEula Takahashi\nEva Sakkas\nEvan Burfield\nEvan Osnos\nEvangelos Simoudis\nEzra Klein\nF. Gary Gray\nFabiola Godinez\nFabrizio Zilibotti\nFahad Saleh\nFarid Jiandani\nFei-Fei Li\nFelix Do\nFEWOCIOUS\nFiona Kennedy\nFiona Murray\nFlashrekt\nFlora Oliveira\nFlori Del Valle\nFlorian Leibert\nFoteini Baldimtsi\nFrancesca Gino\nFrank Chen\nFrank Wilczek\nFred Benenson\nFred Ehrsam\nFred Upton\nFred Wilson\nFreda Lewis-Hall\nFrederic Kerrest\nFuture Editorial\nGabby Dizon\nGabby Reece\nGabriel Otte\nGabriel Vasquez\nGaetan Barthelemy\nGarrett Biel\nGary Ang\nGary Reedy\nGary Wolf\nGaurav Banga\nGaurav Dhillon\nGaut\nGayle Tzemach Lemmon\nGeoffrey Woo\nGeorg Fuchsbauer\nGeorg Petschnigg\nGeorge Church\nGeorge Danezis\nGeorge Fraser\nGeraldine Chan\nGérard Cachon\nGerard Ryle\nGerri Elliott\nGerry Tsoukalas\nGia Scinto\nGil Elbaz\nGil Shafir\nGina Moon\nGina Neff\nGina Yocom\nGinger Liau\nGokul Rajaram\nGoldie Chang\nGrace Ellis\nGraham Allison\nGrant Gregory\nGrant Jordan\nGrant LaFontaine\nGrant Rabenn\nGray Kinsella\nGreg Bowman\nGreg Clayman\nGreg Linares\nGreg Loehmann\nGreg Lynn\nGreg Solano\nGreg Truesdell\nGreg Waldon\nGregory Allen\nGregory Mundis\nGretchen Bush\nGretchen McCulloch\nGuido Appenzeller\nGustav Söderström\nGustavo Garcia\nGuy Goren\nGuy Raz\nGuy Wuollet\nHaley Van Dyck\nHanna Aziz\nHannah Frankl\nHanne Winarsky\nHaoyuan Li\nHarmit Malik\nHarry Grieve\nHarry Shum\nHarry Wright\nHatim Shafique\nHayden Adams\nHeather Gwynn\nHeather Podesta\nHedi Samar\nHelen Stoddard\nHelen Su\nHemant Mohapatra\nHendrik Pretorius\nHenri Kor\nHerb Lin\nHerman Narula\nHilmar Pétursson\nHoang Nguyen\nHoward Wu\nIan Dutra\nIan Shannon\nIan Sharp\nIce Cube\nIlan Zechory\nIllia Polosukhin\nIlyas Khan\nIma Christian\nIman Abuzeid\nInsiya Lokhandwala\nIon Stoica\nIrvin Chan\nIsa Guardalabene\nIsaiah Lott\nIsh Verduzco\nIsil Dillig\nIstván András Seres\nIttai Abraham\nIttay Eyal\nIva Messy\nIvan Linscott\nIvor Horn\nJ.D. Moriarty\nJack Donahoe\nJack Soslow\nJackie McQuiston\nJackson David\nJacob Westphal\nJacquelyn Melinek\nJad Esber\nJad Naous\nJade Lai\nJade Raymond\nJae Gnazzo\nJai Ramaswamy\nJaimie Buss\nJak Kennedy\nJake Auchincloss\nJakob Uszkoreit\nJamal Mohammed\nJames Beshara\nJames Currier\nJames da Costa\nJames Gwertzman\nJames J. Collins\nJames Kissell\nJames L. Madara\nJames Loftus\nJames Rathmell\nJames Rogers\nJames Watters\nJames Wu\nJames Zou\nJamie Brandon\nJamie McGurk\nJamie Sullivan\nJamilla Hemeid\nJana Odehnal\nJane Doe\nJane Lippencott\nJane Suh\nJanelle De Los Santos\nJared Bricklin\nJared Furutani\nJared Georgakopoulos\nJared Polis\nJared Smith\nJase Wilson\nJason Franklin\nJason Liu\nJason Mayden\nJason Milionis\nJason Mitchell\nJason Mok\nJason Rosenthal\nJason Warner\nJason Yanowitz\nJay Bradner\nJay Conte\nJay Drain\nJay Komarneni\nJay Rughani\nJean Reilly\nJeanne Tsan\nJeff Amico\nJeff Benson\nJeff Clark\nJeff Cordova\nJeff Glueck\nJeff Hawkins\nJeff Jones\nJeff Jordan\nJeff Lawson\nJeff Lu\nJeff Nagashima\nJeff Stump\nJeff Weiner\nJeffrey Immelt\nJeffrey Kaditz\nJeffrey Katzenberg\nJeffrey Kindler\nJeffrey Low\nJeffrey Silverstein\nJeffrey Zirlin\nJen Bulawsky\nJen Kha\nJenna Walsh\nJenna Zucker\nJennifer 8. Lee\nJennifer Doudna\nJennifer Kodner\nJennifer Konde\nJennifer Li\nJennifer Mumford\nJennifer Tejada\nJennifer Young\nJenny Cieplak\nJens Ernstberger\nJensen Harris\nJeremy Clark\nJeremy England\nJeremy Zhang\nJesse Holmes\nJesse Pollak\nJesse Walden\nJessica Childs\nJessica Hansen\nJessica Keeler\nJessica Patton\nJessica Verrilli\nJewel Pi\nJez Humble\nJi Kim\nJianying Luo\nJim Gilliam\nJimmy Chen\nJimmy Soni\nJing Wang\nJing Zou\nJJ Yu\nJoachim Neu\nJodi Lynn\nJodie Lutkenhaus\nJoe Gebbia\nJoe Grundfest\nJoe Montana\nJoe Morrissey\nJoe Schmidt\nJoe Sullivan\nJoel de la Garza\nJoel Mokyr\nJoel Monegro\nJoel Spolsky\nJoey Burleson\nJohn China\nJohn Collison\nJohn Fawcett\nJohn Garcia\nJohn Gedmark\nJohn Hennessy\nJohn Koelliker\nJohn M. Jack\nJohn Markoff\nJohn Menna\nJohn O’Farrell\nJohn Riccitiello\nJohn Smesko\nJohn Stanfield\nJohn Thompson\nJohn William Hatfield\nJonah Peretti\nJonathan Bush\nJonathan Dotan\nJonathan Downey\nJonathan Lai\nJonathan Lim\nJonathan Lusthaus\nJonathan Weissman\nJonathan Wong\nJordan Mazer\nJordan Stankowski\nJorge Conde\nJorge Gomez\nJose Guardado\nJoseph Bonneau\nJoseph Okpaku\nJoseph Spisak\nJosh Arnold\nJosh Bloom\nJosh Kim\nJosh Williams\nJoshua Browder\nJoshua Gans\nJoshua Grimm\nJoshua Hix\nJoshua Levin\nJoshua Lu\nJoshua Schank\nJoshua Soto\nJosie Ma\nJoyce Park\nJR Rivers\nJT Evans\nJuan Benet\nJudene Small\nJudy Savitskaya\nJudy Smith\nJulia Grace\nJulia Kirby\nJulie Bornstein\nJulie Farnham\nJulie Johnson\nJulie Samuels\nJulie Yoo\nJuliet Grier\nJuliet Nyatta\nJuliette Morton\nJulius Zhang\nJustin Bailey\nJustin Bethune\nJustin Blau\nJustin Cunningham\nJustin Gregorius\nJustin Kahl\nJustin Kan\nJustin Larkin\nJustin Paine\nJustin Pettit\nJustin Roberts\nJustin Simcock\nJustin Thaler\nJustine Moore\nJutta Steiner\nJyoti Bansal\nJZ Young\nKabir Gill\nKabir Laroia\nKais Khimji\nKamala Harris\nKaren Dunn\nKaren Wooley\nKarina Sobieski\nKarl Floersch\nkarma (Daniel Reynaud)\nKarmacoma\nKarthik Rau\nKartik Nayak\nKate Darling\nKate Dellolio\nKate Kerames\nKatherine Boyle\nKatherine Minarik\nKatherine Rundell\nKatherine Schoebel\nKathryn McKinley\nKathy Liu\nKathy Yang\nKatia Ameri\nKatie Baynes\nKatie Haun\nKatie Hemmerling\nKaty DeWitt-Drew\nKaty Nelson\nKayvon Tehranian\nKeener Barnhorst\nKeller Medlin\nKeller Rinaudo\nKelly Cannon\nKelsey Chaplinsky\nKelsey Mellard\nKen Chong\nKen Coleman\nKen Kocienda\nKerry Ganim\nKesha Cash\nKevin Chou\nKevin Chu\nKevin Dulsky\nKevin Kelly\nKevin McKinley\nKevin Nishioka\nKevin O'Kane\nKevin Rose\nKevin Tan\nKevin Wu\nKevin Zollman\nKidSuper\nKieran Snyder\nKierston Gittens\nKiki Mavridis\nKim Enright\nKim Malone Scott\nKim Milosevich\nKim Stevenson\nKim Zetter\nKimberly Tan\nKindra Mason\nKira Poskanzer\nKira Song\nKirstin Arbide\nKirt McMaster\nKofi Ampadu\nKouki Harasaki\nKrista Anderson-Copperman\nKristen Fortney\nKristen Johansson\nKristen Kee\nKristin Sauchak\nKristin Thayer\nKristina Graci-deLuna\nKristina Shen\nKristine Lipscomb\nKristo Käärmann\nKrisztina Holly\nKunal Bahl\nKunle Olukotun\nKurt House\nKyle Russell\nLaird Hamilton\nLatasha\nLaura Arrillaga-Andreessen\nLaura Baller\nLaura Behrens Wu\nLaura Deming\nLaura Gravley\nLaura Johnson\nLaura Shores\nLaura Weidman Powers\nLauren Berson\nLauren Illovsky\nLauren Murrow\nLauren Richardson\nLauren Spragge\nLaurene Powell Jobs\nLawrence Levy\nLawrence Summers\nLeah Cassidy\nLee Kleinman\nLee Lefkowitz\nLeeAnn Caballero\nLeila Hay\nLeila Janah\nLenny Rachitsky\nLeslie Jaw\nLeslie Vosshall\nLester Chen\nLi Fan\nLi Fei-Fei\nLi Jin\nLiang Wu\nLilian King\nLily Liu\nLina Sergie Attar\nLinda Banuelos\nLinda Xie\nLinden Tibbets\nLing Ren\nLinlin Li\nLinxin Wen\nLioba Heimbach\nLisa Hawke\nLisa Lambert\nLisa Orr\nLisa Reilly\nLisa Rosano\nLizzy Anderson\nLJ Erwin\nLloyd Dean\nLoretta Sanchez\nLori Potter\nLuca Prosperi\nLuca Zanolini\nLuis Martinez\nLuis von Ahn\nLuke Wroblewski\nLydia Green\nLynda Gibson\nLynn Rudolph\nMadan Nagaldinne\nMaddison Masaeli\nMadeline Lancaster\nMaggie Hsu\nMaggie Leung\nMaggie Romero\nMahad Abedin\nMahesh Iyer\nMahesh Vellanki\nMahimna Kelkar\nMakiri Duckett\nMalinka Walaliyadde\nMallesh M. Pai\nMalloy Evans\nManas Punhani\nManny Luna\nMarc Andreessen\nMarc Andrusko\nMarc Benioff\nMarc Levinson\nMarci Barbera\nMarco Reuter\nMargaret Jen\nMargit Wennmachers\nMaria LaMagna Morales\nMarian Garvin\nMarianne Winkler\nMariano Sorgente\nMaricarmen Alvarez\nMariel Goldenstein\nMarigold Vu\nMarina Kusserow\nMario Gabriele\nMario Linares\nMarissa Bramlett\nMark Cranney\nMark Leslie\nMark McAndrew\nMark McClusky\nMárk Melczer\nMark Moore\nMark Regan\nMark Sendak\nMarkos Georghiades\nMarkus Covert\nMarkus Funk\nMartha Lane Fox\nMartin Casado\nMartin Fischer\nMarty Makary\nMarvin Ammori\nMarvin Zamora\nMary Pat Jordan\nMary-Catherine Lader\nMaryam Bahrani\nMason Hall\nMatei Zaharia\nMatt Abrahams\nMatt Billmann\nMatt Bornstein\nMatt Clifford\nMatt Flannery\nMatt Fleming\nMatt Gleason\nMatt Kaeberlein\nMatt Levine\nMatt Levy\nMatt Oberhardt\nMatt Shortal\nMatt Spence\nMatt Weinberg\nMatthew Colford\nMatthew Green\nMatthew Haughey\nMatthew McCullough\nMatthew Mills\nMatthew Olsen\nMatthew Rutter\nMatthew Stein\nMatthieu Hafemeister\nMaureen Lara\nMax Kesten\nMax Krohn\nMax Levchin\nMax Polyak\nMax Resnick\nMax Ventilla\nMaya Rahkonen\nMcPherson Moore\nMeaghan Hardy\nMeg Whitman\nMegan Holston-Alexander\nMegan Kristalyn\nMehdi Hasan\nMehul Mehta\nMel Williams\nMelanie Galang\nMelissa Liao\nMelissa Minor\nMelissa Wasser\nMellody Hobson\nMelody Latronico\nMeredith Donahue\nMia Gonzalez\nMia Mandich\nMicah Johnson\nMichael Beckerman\nMichael Blau\nMichael Brandt\nMichael Chan\nMichael Copeland\nMichael Dearing\nMichael Dell\nMichael Franklin\nMichael Garcia\nMichael J. Casey\nMichael J. Freedman\nMichael Killam\nMichael King\nMichael Lee\nMichael Leiter\nMichael Morell\nMichael Ostrovsky\nMichael Ovitz\nMichael Paulus\nMichael Raynor\nMichael Reed\nMichael Snyder\nMichael Temkin\nMichael Wee\nMichael Zhu\nMichel Del Buono\nMichel Feaster\nMichèle Flournoy\nMichele Griffin\nMichele Korver\nMichele Law\nMichelle Ervin\nMichelle Kelso\nMichelle Kung\nMichelle Mundy\nMichelle Shin\nMichelle Ufford\nMichelle Volz\nMichelle Wilson\nMichelle Winn\nMichelle You\nMike Curtis\nMike Haydon\nMike Hearn\nMike Jones\nMike Kasperzak\nMike Kelly\nMike King\nMike Lempres\nMike Manning\nMike Maples jr\nMike Masnick\nMike Matchett\nMike Paulus\nMike Sandwick\nMikeal Rogers\nMikey Dickerson\nMiles Jennings\nMilijana Curic\nMiller Whitehouse-Levine\nMinerva Munoz\nMinnie Ingersoll\nMinsun Pak\nMintu Turakhia\nMiranda Christ\nMo Shaikh\nMohammad Akbarpour\nMohsen Malayeri\nMolly Grace\nMonique McCambridge\nMorgan Beller\nMorgan Bender\nMurat Pak\nMuriel Bowser\nMurray Shanahan\nMy Pham\nNadia Asparouhova\nNadia Eghbal\nNaftali Harris\nNaithan Jones\nNanjira Sambuli\nNaomi Metzger\nNashid Braswell\nNassim Eddequiouaq\nNat Barling\nNatacha Crooks\nNatalia Carrera\nNatalie Bucher\nNatalie Taumoepeau\nNate Chang\nNate Lau\nNathalie Balaban\nNathan McCauley\nNathan Yoon\nNathaniel Gleicher\nNathaniel Popper\nNav Singh\nNazanin Daneshvar\nNeel Maitra\nNeha Narula\nNelson Perla-Ward\nNeveen Bader\nNicholas Christakis\nNicholas Pacilio\nNick Babaian\nNick McKeown\nNick Quah\nNick Tomaino\nNicki Locker\nNicole Conner\nNicole Forsgren\nNicole Irvin\nNicole Neuman\nNicole Stanners\nNiels Provos\nNigel Robinson\nNikhil Krishnan\nNina Suthers\nNir Eyal\nNitasha Tiku\nNitin Natarajan\nNitya Subramanian\nNkiru Balonwu\nNoah Citron\nNoah Feldman\nNoah Levine\nNoah Smith\nNoam Nisan\nNoemi Glaeser\nO’Shea Jackson Jr.\nOlaf Carlson-Wee\nOleg Rogynskyy\nOliver Hsu\nOlivia Moore\nOlivia Webb\nOmri Weinstein\nOoshma Garg\nOprah Winfrey\nOrion Hindawi\nOscar Menjivar\nP.J. Hasleton\nPablo Montagnes\nPacky McCormick\nPak\nPalmer Luckey\nPamela Anderson\nPamon Forouhar\nParag Khanna\nParijat Talkad\nParker Brown\nParker Conrad\nPatrice Peck\nPatrick Byrne\nPatrick Collison\nPatrick Conway\nPatrick McCorry\nPatrick McHenry\nPatrick O’Grady\nPatrick Rivera\nPatrick Sutton\nPaul Cafiero\nPaul Daugherty\nPaul Davison\nPaul Krugman\nPaul Vigna\nPaula Long\nPenny Pritzker\nPerri Chilton\nPete Buttigieg\nPeter Blackwood\nPeter Buisseret\nPeter Chan\nPeter Donnelly\nPeter Johnson\nPeter Lauten\nPeter Leeson\nPeter Levine\nPeter Ludwig\nPeter Rubin\nPeter Thiel\nPeter Wang\nPetra Garrett\nPhil Daian\nPhil Hathaway\nPhil Wong\nPhong Nguyen\nPorter Smith\npplpleasr\nPranav Garimidi\nPrasad Akella\nPrat Moghe\nPreethi Kasireddy\npunk6529\nPurnima Padmanabhan\nPyrs Carvolth\nQasar Younis\nQuang Dao\nQuinten Burgunder\nQuintus Kilbourn\nRachael Horwitz\nRachel Goslins\nRachel Jenkins\nRachel Kalmar\nRachel McIntyre\nRachel Steiner\nRahul Iyer\nRahul Vohra\nRajeev Singh\nRajeev Venkayya\nRam Palaniappan\nRamana Jonnala\nRati Gelashvili\nRaul Vazquez\nRavi Parimi\nRay Dalio\nRaymond Carreira\nRebecca Lewis\nRebecca Rettig\nReed Hastings\nRefik Anadol\nRegina Benjamin\nRenato Valdés Olmos\nReshma Saujani\nReshma Sohoni\nRex Salisbury\nRich Ezekiel\nRichard Green\nRichard Menger\nRichard Rosenblatt\nRick Young\nRidhima Ahuja\nRiyaz Faizullabhoy\nRob Goodman\nRob McElhenney\nRob Pardo\nRob Rhinehart\nRobbie Petersen\nRobbie Peterson\nRobert Alexander\nRobert Cottrell\nRobert Hackett\nRobert Kolker\nRobert Leshner\nRobert McNeely\nRobert Moreno\nRobert Siegel\nRobert Stromberg\nRobert Weber\nRobin Casey\nRobin Guo\nRobin Weisman\nRod Johnson\nRodrigo Ibarra Lopez\nRodrigo Pacheco\nRoger Dickey\nRoger Wattenhofer\nRoham Gharegozlou\nRohini Mukand\nRohit Bansal\nRoman Mars\nRoman Stanek\nRon Gill\nRon Lavi\nRon Rothblum\nRonald Evans\nRonnie Harris\nRosa Davila\nRosalind Rattan\nRose Legarda\nRoss Andersen\nRoss Shuel\nRostin Behnam\nRuben Gallego\nRuben Smith\nRuss Altman\nRuss Heddleston\nRuss Roberts\nRussell Davies\nRyan Allen\nRyan Caldbeck\nRyan Conde\nRyan Holloway\nRyan Hoover\nRyan McEntush\nRyan Petersen\nRyan Prescott\nRyan Sandler\nRyan Spoon\nRyan Tseng\nRyan Walsh\nRyan Ward\nRyan Wyatt\nSaar Tochner\nSachin Jain\nSafi Bahcall\nSagar Dhawan\nSaku Panditharatne\nSalem Vance\nSam Blackshear\nSam Broner\nSam Gerstenzang\nSam Ragsdale\nSam Thompson\nSam Williams\nSam Yam\nSamantha Gelt\nSamantha Langford\nSamantha Ludwig\nSamson Wu\nSamuel Arbesman\nSamuel Hammond\nSandra Samayoa\nSandy Jen\nSankaet Pathak\nSantiago Rodriguez\nSara Boesen\nSarah Fazal\nSarah Hamburg\nSarah Lumbard\nSarah Mascardo\nSarah Meiklejohn\nSarah Porter\nSarah Rebello\nSarah Wang\nSasha Stiles\nSatish Talluri\nSaurabh Ladha\nSavannah Cherry\nScott Clark\nScott Duke Kominers\nScott Gottlieb\nScott Hassan\nScott Kupor\nScott Rubin\nScott Shenker\nScott Tyler\nScott Walker\nScott Weiss\nSean Duffy\nSean Neville\nSebastian Oddo\nSeema Amble\nSeemay Chou\nSep Kamvar\nSergiu Pasca\nSeth Lobree\nSeth Sivak\nSeth Sternberg\nShai Bernstein\nShai Kopeld\nShaka Senghor\nShakil Khan\nShan Sinha\nShana Fisher\nShane Mac\nShane Parrish\nShangda Xu\nShannon (Stubo) Brayton\nShannon Barbour\nShannon Kelly\nShannon Schiltz\nShannon Snow\nShari Doherty\nSharon Chang\nShawn Conway\nSheela Krothapalli\nShellye Archambeau\nSherie James\nSherriAnn Cole\nShishir Mehrotra\nShonda Rhimes\nSid Gorham\nSigne Pierce\nSimon Denny\nSiqi Chen\nSonal Chokshi\nSophie Song\nSoubhik Deb\nSpencer Dinwiddie\nSpencer Howard\nSpencer Rascoff\nSreeram Kannan\nSreevidya Kasturil\nSri Kosuri\nSriram Krishnan\nSrivatsan Sridhar\nStacey Cunningham\nStacey Merrick\nStacia Murray\nStacy Brown-Philpot\nStacy D'Amico\nStacy Warner\nStefan McDonough\nSten Tamkivi\nStephane Bancel\nStephanie Anyanwu\nStephanie Cohen\nStephanie Doppelt\nStephanie Smith\nStephanie Watkins\nStephanie Zinn\nStephen Armanios\nStephen Wink\nStephenie Zhang\nSteve Buress\nSteve Cadigan\nSteve Cheney\nSteve Harvey\nSteve Kaczynski\nSteve McDermid\nSteve Smith\nSteve Zhao\nSteven Adair\nSteven Ebert\nSteven Johnson\nSteven Levy\nSteven Sinofsky\nStewart Butterfield\nStina Ehrensvärd\nStuart Luman\nStuart Russell\nSudip Chakrabarti\nSue Hager\nSuhail Doshi\nSukhinder Singh Cassidy\nSumeet Singh\nSumit Shah\nSungMo Park\nSunil Chokshi\nSurya Ganguli\nSusan B. Wilde\nSusan Mernit\nSusan Rice\nSusannah Fox\nSydney Paul\nTaavet Hinrikus\nTaggart Matthiesen\nTamzen Brewis\nTana Billingsley\nTarek Mansour\nTarun Chitra\nTauri Laws Phillips\nTawny Holguin\nTaylor McFadden\nTed Not Lasso\nTed Sarandos\nTed Ullyot\nTerell Sterling\nTerence Carroll\nTeresa Carlson\nTerry Angelos\nTerry Brown\nThan Nguyen\nThanh Nguyen\nThe 2015 Academic Roundtable Sessions\nThe TxO team\nTheresa DeMichele\nTheresa Dilley\nTheresa Fisher\nTheresa Walz\nTheresia Gouw\nThibaut Scholasch\nThomas Gjerde\nThomas Juenger\nThomas Long\nThomas Rando\nTiffany Vo\nTiffany Zhong\nTim Beiko\nTim O'Reilly\nTim Roughgarden\nTim Schafer\nTim Sullivan\nTimmu Tõke\nTina Anderson\nTina Bhatnagar\nTina Ferguson\nTina Wie\ntinawie\nTing Ni\nTobi Lütke\nTodd Cranney\nTodd Lutwak\nTodd McKinnon\nTodd Park\nTodd Young\nTolga Dizdarer\nTom Butta\nTom Coates\nTom Davenport\nTom Ellis\nTom Hammer\nTom Hofmann\nTom Lehman\nTom Mitchell\nTom Preston-Werner\nTom Rikert\nTom Standage\nTomicah Tillemann\nTony Blair\nTony Blinken\nTori Landrum\nTracy Chou\nTracy Young\nTren Griffin\nTrent Mayol\nTrevor Bedford\nTristan Handy\nTristan Walker\nTroy Kirwin\nTugce Erten\nTurner Novak\nTushar Garg\nTyler Cowen\nTyler Wilson\nTyson Clark\nUma Valeti\nUsman Azam\nUzi Dutta\nValentina Marzorati\nValeria Nikolaenko\nValerie Arboleda\nVan Jones\nVan Le-Gray\nVanessa Kropf\nVas Narasimhan\nVaughn Ferguson\nVenkat Mocherla\nVicente De Baca\nVickie Casillas-Smith\nVictor Liang\nVictor Shoup\nVictoria Butcher\nVijay Balasubramaniyan\nVijay Kedar\nVijay Pande\nVineeta Agarwala\nVinod Khosla\nVirginia Postrel\nVishal Amin\nVitalik Buterin\nVivian Brooks\nVoices Onchain\nW. Brian Arthur\nWahab Owolabi\nWei Luo\nWendy Drpic\nWerner Gerola\nWes Taylor\nWhitney Owens\nWill Brown\nWill Wong\nWillem Mulder\nWilliam Gifford\nWilliam Mougayar\nWing Cheng\nXian Zhang\nXiang-Dong Fu\nXingchen Zhou\nYannai A. Gonczarowski\nYehuda Lindell\nYevgeniy Dodis\nYinuo Zhang\nYogi Roth\nYohei Ishii\nYoko Li\nYoni Levy\nYoram Novick\nYuichi Kurosawa\nYujin Chung\nYun Fan\nYung Yung Sheung\nYuval Efron\nYuval Harari\nZac Bookman\nZach Abrams\nZach Cohen\nZach Dicker\nZach Haigney\nZachary Chen\nZachary Gray\nZack Weiner\nZahabiya Gabaji\nZak Doric\nZal Bilimoria\nZane Lackey\nZeta Avarikioti\nZeya Yang\nZooko Wilcox\nZoran Basich\n\nclear all Andrew Lewis-Pye\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n05.09.25 / Andrew Lewis-Pye, Joachim Neu, Tim Roughgarden and Luca Zanolini\n‘Accountable liveness’: New paper alert\nOn when and how adversarial nodes can be punished if they stall transaction confirmation in blockchains\n\nresearch\nconsensus\nsecurity\n\n11.22.24 / Andrew Lewis-Pye\nFrosty: Bringing strong liveness guarantees to the Snow family of consensus protocols\nSnowman is the consensus protocol implemented by the Avalanche blockchain and is part of the Snow family of protocols, first introduced through the original Avalanche leaderless consensus protocol. A major advantage of Snowman is that each consensus decision only requires an expected constant communication overhead per processor in the common case that the protocol is...\n\nresearch\nconsensus\nvideo\n\n10.17.23 / Andrew Lewis-Pye\nPermissionless consensus\nA new framework for reasoning about the rich design space of blockchain protocols in the permissionless setting\n\nresearch\nconsensus\nvideo\n\n01.30.23 / Andrew Lewis-Pye\nConsensus Canon\nConsensus protocols are a core part of what is going on in blockchain. Here's a list of links that will get you up to date on the foundations and the latest.\n\nresearch\nconsensus\nhow innovation happens\nwhat we're reading\n\n10.14.22 / Andrew Lewis-Pye\nDirect Acyclic Graph (DAG)-Based Consensus Protocols: An Introduction\nAndrew Lewis-Pye (London School of Economics) introduces DAGs, which allow blocks to have multiple parents or children, resolving “forks” in blockchains.\n\nresearch\nconsensus\nDAGs\nglossaries & terminology\nvideo\n\n10.07.22 / Andrew Lewis-Pye\nIntroduction to Consensus (Part II)\nPart II of an introduction to the basics of consensus, the protocol to coordinate and maintain a decentralized blockchain. Andrew Lewis-Pye (London School of Economics) reviews the basics of consensus from Part I, and introduces state machine replication (SMR) — the problem that blockchain protocols are designed to solve — and demonstrates how to reduce...\n\nresearch\nconsensus\nvideo\n\n10.07.22 / Andrew Lewis-Pye\nIntroduction to Consensus (Part I)\nPart I of an introduction to the basics of consensus, the protocol to coordinate and maintain a decentralized blockchain. Andrew Lewis-Pye (London School of Economics) discusses how participants can agree on the correct condition of the blockchain and who owns what at any time. He begins with an overview of Byzantine agreement problem; addresses communications...\n\nresearch\nBFT\nconsensus\nvideo\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":7378,"crawled_at":1791193352243}
+{"id":10225,"url":"https://docs.near.org/getting-started/tools-for-ai","domain":"docs.near.org","chapter":"layer1_layer2","title":"Tools for AI Agents - NEAR Docs","text":"NEAR offers multiple tools and resources to help your AI agents build and use NEAR applications. This page provides an overview of the key tools available and how to use them effectively.\n\nllms.txt\nWhen you need to provide your agent with a quick reference to all NEAR docs.\n\nDocs MCP\nWhen you want agents to search docs in real-time for up-to-date details.\n\nAgent Skills\nWhen you need your agent to become an expert in a specific task (e.g. using our API).\n\nNEAR MCP\nWhen your agent needs to perform on-chain actions (e.g., transfers and function calls).\n\n​\n\nllms.txt\n\nWhat it is: Curated NEAR docs context for coding assistants.\nUse it when: You need to provide your agent with a quick reference to all NEAR docs.\nLink: https://docs.near.org/llms.txt\n\nVS Code Setup\n\nUse #fetch in your prompt:\n\nHow can I upgrade a contract state?\n#fetch https://docs.near.org/llms.txt\n\nCursor Setup\n\nAdd docs source once in Cursor Chat:\n@ → Docs → + Add new doc\n\nAdd: https://docs.near.org/llms.txt\n\nSelect the source while prompting\n\n​\n\nDocs MCP endpoint\n\nWhat it is: An endpoint to search NEAR documentation via MCP.\nUse it when: You want agents to search docs in real-time for up-to-date details and narrower API lookups.\nLink: https://docs.near.org/mcp\nUse two complementary layers:\n\nStatic context (llms.txt) for fast, high-signal docs grounding.\n\nRetrieval (Docs MCP) when the agent needs live lookup across docs.\n\n​\n\nNEAR Agent Skills\n\nNEAR Agent Skills are reusable capabilities that package repeatable workflows.\nUse it when: You need your agent to become an expert in specific tasks (for example, using NEAR APIs).\nLink: https://github.com/near/agent-skills\nSkillFocus\nnear-ai-cloud\nVerifiable private AI inference and attestation\n\nnear-api-js\nJS/TS blockchain interaction, transactions, tokens, and wallet integration\n\nnear-dapp\ndApp project setup, wallet integration, React/Next.js patterns\n\nnear-intents\nCross-chain swaps via the 1Click API\n\nnear-kit\nTypeScript SDK with type-safe contracts and sandbox testing\n\nnear-smart-contracts\nRust smart contract development, security, and state management\n\n​\n\nNEAR MCP Server\n\nThe NEAR MCP Server is a tool server (currently 23 tools) that enables agents to perform blockchain operations.\nUse it when: Your agent needs to hold funds, transfer funds, interact with smart contracts, or perform any action on-chain in NEAR Protocol\nRepo: https://github.com/nearai/near-mcp\nRemote deployment guide: https://github.com/nearai/near-mcp/blob/main/tee.md\n\nThe NEAR MCP is designed to run locally or on your trusted infrastructure because it handles private keys. There is no hosted public version.\n\nWas this page helpful?","tokens":664,"crawled_at":1791193357379}
+{"id":10226,"url":"https://stack.olas.network/open-autonomy/key_concepts/abci_app_interactions","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Interactions between components - Olas Stack Developer Documentation","text":"Interactions between components\n\nIn this section we present sequence diagrams in order to help understand the transmitted messages and method calls between the software components that are part of an FSM App.\n\nThe ABCIApp - AbstractRoundBehaviour interaction\n\nThe interaction between AbstractRoundBehaviour and the ABCIApp occurs via\nthe consensus engine, the setup of which proceeds on the Period.\nand the shared state among the skills. A typical workflow\nlooks as follows:\n\nAt setup time, the consensus engine node creates connections with the\nassociated AEA and sync together. In the AEA process, the ABCIApp starts from\nthe first round, waiting for transactions to update its state. The\nAbstractRoundBehaviour schedules the initial state behaviour for execution\nof the act() method.\n\nThe current state behaviour sends transactions to update the state of the\nABCIApp, and once its job is done waits until it transitions to the next\nround, by checking read-only attributes of the ABCIApp accessible through\nthe AEAs' skill context. Concrete implementations of AbstractRoundBehaviour\ncannot update the state the of ABCIApp directly, only through an agreed\nupon update with other agent instances via the consensus engine node.\n\nOnce the transaction gets added to a block accepted by the consensus engine,\nthe consensus engine node delivers the block and transactions contained in\nit to the ABCIApp using the AEAs ABCIConnection and ABCIHandler. The\nABCIApp processes the transaction and enacts the encoded state transition\nlogic.\n\nThe transition to the next round is detected and all scheduled behaviour and\nother tasks get cancelled before transitioning to the next round.\n\nCycles of such rounds may, either entirely or in part, be repeated until a\nfinal state is reached, implemented as a\n\nAbstractRoundBehaviour:\n\nConcrete implementations of AbstractRoundBehaviour can be seen as a client\nof the ABCIApp (in that sense it encapsulates the \"user\" of a normal blockchain).\n\nAbstractRoundBehaviour diagrams\n\nThe following diagram shows how the FSM behaviour operates in concert with the\nAEA event loop. (Not all components are included in the diagram.)\n\nThe following diagram describes the addition of transactions to the transaction\npool. (Not all components are included in the diagram.)\n\nThe following diagram describes the delivery of transactions in a block:","tokens":591,"crawled_at":1791193362105}
+{"id":10227,"url":"https://gov.uniswap.org/t/seedgov-delegate-platform/23987","domain":"gov.uniswap.org","chapter":"governance_daos","title":"SEEDGov Delegate Platform - Delegation Pitch - Uniswap Governance","text":"SEEDGov Delegate Platform\n\nDelegation Pitch\n\nSEEDGov\n\nMay 22, 2024, 1:36pm\n\n1\n\nDelegate Introduction\n\nName: @SEEDGov\n\nWallet Address:\n\nAddress: 0x12b30979b9a53bb0b42deaaa974ac9304fab0832\n\nRRSS:\n\nTwitter:\n\nhttps://twitter.com/SEEDLatam\n\nhttps://twitter.com/SEEDOrg_\n\nhttps://twitter.com/SEEDGov\n\nSupersite: seedlatam.org\n\nTelegram: @seed_latam\n\nDiscord: comunidad.seedlatam.org\n\nWe are excited about the opportunity to join Uniswap Governance, where we hope to contribute significantly to one of the longest-running DeFi protocols in the ecosystem. We have a dedicated team of SEEDGov members, passionate about Uniswap and committed to governance activities.\n\nThe main objective of this delegation will be to maintain active and meaningful participation, contributing to the growth and evolution of Uniswap Protocol Governance within Ethereum and other chains where available, as an entity that deeply resonate with our values and principles.\n\nOur delegation will include our members @Marian, @Jadmat, @AnonBuilder, and the entire SEED team at disposal as well as other consultants necessary for the comprehensive elaboration, assessment and analysis of proposals.\n\nWhat is SEEDGov?\n\nSEEDGov is as a dynamic and evolving vertical within the SEED Org ecosystem, dedicated to shaping the future of decentralized governance in the web3 space through active participation, community engagement, decision-making and experimentation by anticipating emerging needs of DAOs and protocols, while acknowledging the importance of context-specific approaches to minimize governance where appropriate and professionalize it where necessary.\n\nSEEDGov is the first Latam based Delegate Platform actively engaging in various governance activities. Rooted in community values, we’ve shifted from educational models to a participatory approach, driving a new chapter in how individuals collaborate, coordinate, and decide in the ever-changing landscape of Web3.\n\nOur scope of work across various projects and protocols includes managing grant and allocation programs, designing and implementing governance infrastructure, creating and overseeing incentive programs, and onboarding builders to align with protocol needs.\n\nOperating within established frameworks, our dedicated platform go beyond the traditional role of delegates. We are functional and deeply committed to the success of the protocol through every decision we make.\n\nHow we work\n\nAs a professional delegate platform SEEDGov collaborates with communities and partners to ensure credible representation of all interested in Web3’s future. Since its inception, SEEDGov has advocated for critical thinking through education. We do not endorse scams or collaborate with blockchains, projects, or protocols that are not aligned with our core values.\n\nThe members selected to be part of our delegation will collaborate both directly and indirectly with other SEEDGov members. Any decisions made by this delegation regarding governance will be thoroughly discussed and communicated to all stakeholders through our discussion channels and seamlessly executed through specialized working units.\n\nCaptura de pantalla 2024-05-22 1030071195×382 63.4 KB\n\nWhen a project aligns with our principles, we proactively take steps to ensure its success, whether through offering informed opinions or taking concrete action. We believe in more than just participating; we believe in actively shaping and improving projects within our sphere and we are committed to expressing our principles and rationale in a clear, transparent, and detailed manner in this forum.\n\nSEEDOrg>SEEDGov>Uniswap\n\nParticipation in forum discussion threads and daily activities represent the opinions of SEEDGov and collaborators in their efforts to stay up to date with their roles and commitment to governance. Regular discussions occur prior to deciding our next steps and opinions about governance topics that arise, all through this profile.\n\nOur delegation will do its utmost to represent and embody our values to enhance Uniswap governance:\n\nDecentralization: Uniswap is one of the most decentralized DeFi protocols and all of our initiatives and proposals will align with this same principle. Along with this position, and as the ecosystem continues to mature and be driven by its community, we will collaborate in the creation, iteration, and improvement of governance processes to ensure broader participation and that the system remains secure.\n\nCommunity Led Growth & Sustainability: We will promote and support all initiatives that enable the growth, adoption, scalability and innovation for Uniswap ecosystem. Our focus will be placed on ensuring that all growth initiatives are reliable, secure, and sustainable over time.\n\nSecurity: We will always make sure that no DAO decisions will jeopardize the security of the protocol and thus harm users.\n\nEthos and Support: We will actively contribute to the governance of the protocol and its ecosystem worldwide, looking forward to working with other interested delegates to promote the Uniswap mission and encourage others to actively participate in DAO governance.\n\nWhy Uniswap?\n\nUniswap’s success, achieved independently of the core development team since its deployment, demonstrates the significant demand for permissionless financial services. From our perspective, some strengths make this protocol a special case:\n\nInnovation: Uniswap is consistently at the forefront of pioneering innovations in DeFi infrastructure technology. Its open and permissionless architecture fosters innovation by enabling anyone to create and encourages experimentation and the creation of novel financial instruments, driving the growth and diversity of the DeFi ecosystem.\n\nAccessibility: The Uniswap ecosystem has outpaced others in driving widespread adoption. Its accessibility reduces barriers to entry, democratizing decentralized finance for users globally.\n\nCapital efficiency: Uniswap typically outperforms other AMMs in terms of capital efficiency due to its concentrated liquidity model (V3). The efficient use of capital allows to handle larger trades with less price impact, making it very competitive and attractive among other AMMs.\n\nOur case\n\nWe see Uniswap as an infrastructure layer set to drive innovation throughout the entire ecosystem. Being part of this space will enable us to continue understanding, building, and participating in the following verticals (among others):\n\nExtensive Composability: Uniswap’s vast integration with hundreds of interfaces and applications ensures a smooth interaction within the DeFi ecosystem. Is our intention to actively participate in decisions that enhance and expand these integrations, further solidifying Uniswap’s position as a critical infrastructure layer in DeFi by contributing ideas for improvements and applications, whether for hooks (V4) or any other innovation/technology from Uniswap or external ones that we can implement into the protocol.\n\nGovernance: Uniswap’s governance framework is designed to be as constrained as possible, focusing only on essential areas to maintain neutrality and trust minimization. Despite a large community, only a small fraction actively participates in governance, potentially limiting smaller stakeholders voices. Maintaining good participation rates, active discussions, and healthy governance with genuine engagement is crucial for a DAO’s effectiveness. We believe Uniswap can address these challenges by empowering community involvement, overcoming voter apathy, onboarding new participants, and streamlining governance frameworks.\n\nDisclosure:\n\nSEEDGov is a broad organization with a high participation in some of the most prominent governances in the ecosystem such as Optimism, Arbitrum, Gnosis, Starknet, Connext and we also constitute Sovereign Finance AVC in MakerDAO. As mentioned above we come to Uniswap Governance to bring value, in case there is any conflict of interest, we will communicate it to the community members.\n\nCaptura de pantalla 2024-05-22 1030461005×388 250 KB\n\n7 Likes\n\nGLI -- Treasury Delegation Round 2 Applications\n\nSEEDGov\n\nJune 20, 2024, 7:58pm\n\n2\n\nProposal: Uniswap Arbitrum LTIPP Matching\n\nVote: 1M\n\nSummary: We voted in favor and chose as the first option 1 million, as we believe in supporting Arbitrum’s experimental program to foster growth within the second most impactful chain in DeFi, which is significant for Uniswap where the protocol is the leading Dex. Although we acknowledge the complexity of maintaining retention and liquidity levels post-program, these types of programs greatly improve KPIs like DAU, TVL and volumes in general.\n\nWe accept to accompany these instances, on the verge of genuine sustainability/impact improvements. We also believe that the chosen amount can positively impact with minimal risk for the DAO, in terms of continuing to forge a relationship with Arbitrum.\n\n1 Like\n\nSEEDGov\n\nJuly 22, 2024, 10:33pm\n\n3\n\nProposal: [Temp Check] Uniswap Onboarding Package - Gnosis Chain\n\nVote: $250k\n\nRationale: As stated in the respective post, we voted in favor of this proposal presented by @kpk and chose for the 250k option, as we believe that Onboarding Package for Gnosis Chain is appropriate and reasonable, as it is a network in current growth of both TVL and DeFi protocols, so it represents a great opportunity for Uniswap to strengthen its presence there and expand the scope of “Uniswap Revitalization and Growth” in order to capture more market share of activity and volume for the protocol and we believe that 250k is an appropriate amount, given the history of similar programs for other networks.\n\n1 Like\n\nSEEDGov\n\nAugust 5, 2024, 2:16pm\n\n4\n\nProposal: [TEMP CHECK] Uniswap Onboarding Package - OKX Chain (Snapshot)\n\nVote: Against (deploy without incentives)\n\nRationale: First, we would like to point out that the proponent did not respond to our comment and question regarding the distribution of incentives in the proposed pairs, which we view as a negative sign. Regarding the substance of the proposal, the TVL of layer X is currently very low and we do not believe it is productive to allocate incentives at this time. We applaud the proponent’s position in accepting feedback that it intends to proceed for the time being without $UNI incentives.\n\n1 Like\n\nSEEDGov\n\nAugust 12, 2024, 2:53pm\n\n5\n\nProposal: Onboarding Package for Gnosis Chain (onchain)\n\nVote: For\n\nRationale: Consistent with our vote in the Temp Chack (For - Option 250k), we voted in favor of this proposal, understanding that Gnosis is a growing network of both TVL and DeFi protocols, so reinforcing its presence there is a great opportunity for Uniswap to capture more market cap volume and activity.\n\n///////////////////////////////////////////////////////////////////////\n\nProposal: [TEMP CHECK]- Revised - Uniswap Onboarding Package - OKX Chain (Snapshot)\n\nVote: For\n\nRationale: Also in line with our vote in the previous Temp Check (Against - deploy without incentives), we voted in favor of this proposal, welcoming that the proponent has accepted the feedback from the community and has decided to move forward with its proposal without requesting incentives for the moment and committing to allocate $1M for liquidity for a minimum term of 6 months via community multisig, understanding that the cost for Uniswap to deploy the frontend is reasonable.\n\nWe at SEED Gov again offer ourselves as signatories to the multisig.\n\n///////////////////////////////////////////////////////////////////////\n\nProposal: [Temp Check] Forse Analytics for Uniswap Revitalization and Growth Program (Snapshot)\n\nVote: 33% Arbitrum - 33% Base - 33% Scroll\n\nRationale: We voted in favor as having the proposed data and metrics may help the protocol and the DAO to establish future strategies to allocate incentives in a more efficient and optimized manner.\n\nAs for the networks, we support that the analysis is done equally in:\n\nArbitrum: For being the L2 with the highest LTV.\n\nBase: For being the second L2 with the highest LTV in marked growth during the last months. Source: DefiLlama.\n\nimage1549×581 61.8 KB\n\nScroll: For being the L2 with zero knowledge technology with the highest LTV, with a rapid growth in the last 2 months. Souce: DefiLlama\n\nimage1540×576 50 KB\n\nTreasury Delegation Round 2 Ideas Thread\n\n[Temp Check] Forse Analytics for Uniswap Revitalization and Growth Program\n\n[RFC] Deploy Uniswap v3 on X Layer\n\nOnboarding Package for Gnosis Chain\n\nSEEDGov\n\nAugust 19, 2024, 2:51pm\n\n6\n\nProposal: Deploy Uniswap v3 on X Layer (Onchain)\n\nVote: For\n\nRationale: Consistent with our vote in the Temp Check (For), we voted in favor of this proposal, understanding that it is beneficial for Uniswap to deploy in this network, taking charge only of the cost of the frontend and without assigning incentives for the moment, committing the proponent to allocate 1M for liquidity for a minimum term of 6 months via community multisig.\n\n///////////////////////////////////////////////////////////////////////\n\nProposal: [Temp Check] Activate 2, 3, 4 bps fee tiers on Uniswap v3 on Base (Snapshot)\n\nVote: For\n\nRationale: We have read some of @aadams’ research and understand their capabilities and support for the Uniswap ecosystem. Therefore, having analyzed the proposal and despite some concerns we have, we understand that it is worth trying to add new fee tiers in the ETH/USDC pair in Base, in order to make Uniswap more competitive, hopefully capturing part of Aerodrome’s market cap and adapting to new market conditions that may occur in the future, waiting for an expected reaction from that DEX to the move that Uniswap makes.\n\nHowever, we do not want to overlook the potential disadvantages that the new implementation may bring:\n\nIncreased access to arbitrage: by reducing fees, previously unprofitable extractions of value will become profitable\n\nFragmentation of liquidity; starting new pools will keep liquidity more fragmented, which will increase LVR and IL, negative for liquidity providers; as well as potential cost overruns in more complex routing for the trader.\n\nIf the proposal is approved, we expect the proponent to conduct a subsequent analysis and present conclusions on the impact of the changes introduced, to corroborate that the proposed hypothesis has been validated. We encourage the proponent will consider a commitment to this sense for the onchain vote.\n\nSEEDGov\n\nAugust 19, 2024, 5:06pm\n\n7\n\nProposal: [REDO: Temp Check] Activate 2, 3, 4 bps fee tiers on Uniswap v3 on Base (Snapshot)\n\nVote: For\n\nRationale: Since this is a re-running of this temp chek in which we have already voted and justified the sense of our vote, we repeat our vote in favor for the same arguments, which we cite below:\n\n[RFC] Proposal to active 2, 3, 4 bps fee-tiers on Base\n\nSEEDGov\n\nAugust 21, 2024, 8:10pm\n\n8\n\nProposal: [Temp Check] Uniswap Delegate Reward Initiative - Cycle 2 (Snapshot)\n\nVote: Yes\n\nRationale: We support this proposal because experience shows that the establishment of a delegate system by itself does not achieve the desired results of promoting high quality participation and good governance practices, since governance has become very complex and it is not expected that a group of people will voluntarily dedicate enough time and effort required for active and quality participation in governance, or at least it is not expected that this will happen to a large scale. Thus, the incentivized or compensated professional delegate system is being imposed in the most important DAOs, achieving the desired results of further increasing informed, responsible and quality participation in governance, by having paid individuals and groups of individuals who can devote time and effort to this task, training, research, and thus increase the quality of their participation.\n\nIt’s also great to see that off-chain participation factors are being considered, as we believe the policy-making process is just as crucial as the actual voting itself.\n\nIn Arbitrum we are the Program Managers for the Delegates Incentive Program, which started 6 months ago and has generated a very positive impact, ratifying the above mentioned. And coincidentally, Cycle 1 of the Uniswap Delegate Reward has been a success, with the 12 delegates included in the program maintaining a 100% participation rate in onchain and offchain voting, as well as incorporating new delegates with high participation rates, all of which strengthens the governance of the DAO.\n\nWe look forward to being part of this program!\n\n1 Like\n\nSEEDGov\n\nSeptember 2, 2024, 2:43pm\n\n9\n\nProposal: Uniswap Delegate Reward Initiative - Cycle 2 (Onchain)\n\nVote: For\n\nRationale: Consistent with our vote in the Temp Check (For), we voted in favor of this proposal. We share the rationale expressed on that occasion, as we maintain our position:\n\nSEEDGov\n\nSeptember 5, 2024, 3:12pm\n\n10\n\nProposal: [Temp Check] - Ethereum Foundation Attackathon Sponsorship (Snapshot)\n\nVote: Abstain\n\nRationale: While we generally support initiatives of this nature in all delegations where we have a presence, as they contribute positively to the ecosystem, our experience reviewing multiple sponsorship requests leads us to seek additional budgetary details and further clarification.\n\nAdditionally, despite mentioning marketing and branding integrations for Uniswap, we observed no dedicated workshop or side event for the sponsor.\n\nIn summary, and beyond that it is a program that, by reinforcing the security of Ethereum, will indirectly reinforce the security of Uniswap, but from the commercial point of view of the exposure that Uniswap could achieve, and considering that it is a program aimed at advanced developers who presumably, given their specialization, already know Uniswap, we understand that it is very low the impact of the program and the positioning that Uniswap could achieve, not justifying making the budgetary effort of allocating 75 or 30 ETH.\n\n1 Like\n\n[RFC] - Ethereum Foundation Attackathon Sponsorship\n\nSEEDGov\n\nSeptember 9, 2024, 7:37pm\n\n11\n\nProposal: Proposal to active 2, 3, 4 bps fee-tiers on Base (Onchain)\n\nVote: For\n\nRationale: Consistent with our vote in the Temp Check (For) we support this proposal. We have read some of @aadams ’ research and understand their capabilities and support for the Uniswap ecosystem. Therefore, having analyzed the proposal and despite some concerns we have (regarding increased access to arbitrage and liquidity fragmentation), we understand that it is worth trying to add new fee tiers in the ETH/USDC pair in Base, in order to make Uniswap more competitive, hopefully capturing part of Aerodrome’s market cap and adapting to new market conditions that may occur in the future, waiting for an expected reaction from that DEX to the move that Uniswap makes.\n\nWe expect the proponent to conduct a subsequent analysis and present conclusions on the impact of the changes introduced, to corroborate that the proposed hypothesis has been validated.\n\n[RFC] Proposal to active 2, 3, 4 bps fee-tiers on Base\n\nSEEDGov\n\nSeptember 11, 2024, 8:02pm\n\n12\n\nProposal: UAC Renewal S3 (Snapshot)\n\nVote: Renew UAC\n\nRationale: The UAC has done a great job, so we support its renewal for 7 months for Season 3, as well as the expansion of its scope, which logically must be accompanied by an increase in the expected hours of work and adequate compensation, as well as the increase of a new additional seat.\n\nWe are interested in collaborating with and being part of the committee, since we have the necessary team in SEED Gov. Therefore, if this proposal is approved, we express our interest in applying for one of the two available seats.\n\nSEEDGov\n\nSeptember 11, 2024, 8:05pm\n\n13\n\nProposal: Approved Budgets Rebalancing (Snapshot)\n\nVote: Approved Rebalance\n\nRationale: We support this proposal, since the program budgets have been approved in U.S. dollars, but the UNI token has been established for its payment, so the fluctuation of its price has caused an imbalance in the approved budgets, making the proposed rebalancing logical to balance the accounts.\n\nSEEDGov\n\nSeptember 11, 2024, 8:07pm\n\n14\n\nProposal: Uniswap Delegate Race Tiebreaker (Snapshot)\n\nVote: Both (create an extra 1616th spot)\n\nRationale: We understand that there has been a total tie between both applicants @Tane and @Argonaut, for the following considerations:\n\nWe share with @Pgov statement in that the rule of who voted first should be understood by the proposal on which they have voted and not the precise time and date, as this would encourage undesirable behaviors such as delegates rushing to vote quickly as soon as a proposal is uploaded to be the first to vote, which does not respond to best practices of analyzing the proposals and voting after forming a well-founded opinion within the voting period.\n\nWe share the @Argonaut opinion that the criteria used for the tiebreaker expressed by @Pgov as “we moved to what was used as a tiebreaker in other elections for Uniswap (Uniswap delegation initiative) which was forum activity, to which Tane had more likes, earlier start date and ‘forum cred’\" has not been approved by the governance for this specific case, so it should not be used as a tiebreaker.\n\nThat tie-breaker criterion detailed above is easily gameable by fake users or bots or even by agreements between delegates to give each other likes and improve this metric in an irregular way, so not only we do not share its use in this case for the reason stated above, but we do not share and discourage to use it in the future for any other selection method.\n\nFor the above mentioned, we understand that there has been a total tie between both applicants, not having been foreseen in the proposal how to break a tie of these characteristics.\n\nGiven that the proposal approved by the governance has not foreseen tie-breaking criteria for such a case, we understand that there are no elements that allow choosing or prioritizing one over the other applicant, so it would not be a fair solution to make a decision of these characteristics without any parameter to support it.\n\nOur opinion then is that there would be two possible solutions:\n\nThat both be ranked 15 and receive 50% of the monthly compensation of a delegate each.\n\nThat both be eligible for full compensation by expanding to a slot of 16 incentivized delegates and increasing the budget for this purpose through a governance decision.\n\nGiven that one of the main reasons and objectives taken into account in the proposal to renew the rewards initiative to a cycle 2 has been to incorporate new delegates and increase participation to strengthen governance, we believe that the latter solution would be the fairest and most compatible with these objectives.\n\nConsequently we voted for the option “BOTH (create an extra 16th spot)”.\n\nGiven this experience, which should be taken as a learning experience for the future (every experience brings with it a constant learning process that should serve as a basis for future improvement), we are at complete disposal and we want to be part of the working group where opinions are shared and discussions are carried out for the opportunity to decide to renew to a cycle 3. In Arbitrum we are the Program Managers for the Delegates Incentive Program, which started 6 months ago and has generated a very positive impact, so we have the experience and the necessary team that we put at Uniswap’s disposal to make our best contributions to further improve the current incentive program and its eligibility criteria for the future cycle 3.\n\n3 Likes\n\nUniswap Delegate Reward Initiative - Cycle 2 Application\n\nSEEDGov\n\nSeptember 18, 2024, 2:36pm\n\n15\n\nProposal: Uniswap Accountability S3 Renewal and Rebalance (Onchain)\n\nVote: For\n\nRationale: This online voting proposal combines the 3 Temp Cheks approved by the community between September 10th and 15th: Uniswap Accountability Renewal (UAC) Season 3, Approved Budget Rebalance, and extra 16th delegate cycle 2 spot for Argonaut and Tane. Consistent with our votes in the above temp checks, we support this proposal and confirm the previously stated rationales, which we maintain in this occasion and consider reproduced with the links below.\n\nUniswap Accountability Renewal (UAC) Season 3 rationale\n\nApproved Budget Rebalance rationale\n\nExtra 16th delegate cycle 2 spot for Argonaut and Tane rationale\n\nSEEDGov\n\nOctober 1, 2024, 1:12pm\n\n16\n\nProposal: Forse Analytics for Uniswap Revitalization and Growth Program (Onchain)\n\nVote: Against\n\nRationale: The proposal expressly stated:\n\nand\n\nand\n\nIn other words, it was clearly proposed that the DAO should decide whether to proceed with the proposal, and if so, it would be the DAO that would decide on which 3 blockchains the dashboards would be made.\n\nIn the temp check submitted to a vote, the DAO decided to proceed with the proposal and chose 3 blockchains: Base supported by 1,665,046.46 UNU, Arbitrum with 10,438,561.17 UNI and third Scroll with 1,171,901.87 UNI, followed closely by Blast with 1,171,615.9 UNI. In other words, the third place was very hard fought and the difference was very close, but the DAO chose Scroll over Blast.\n\nContrary to this, in the onchain voting, the proponent included Base, Arbitrum and Blast, i.e. the fourth blockchain chosen by the DAO, and not the third. When asked why this was the case, he expressly replied:\n\nThe proposal then stated that the 3 blockchains would be chosen by the Uniswap DAO, but we are faced with an onchain proposal that includes 3 blockchains, one of them chosen by the proponent contrary to what the DAO decided.\n\nIn principle, and without this being important for our analysis, it should be noted that the TVL of the blockchains today are not those reported in the proposal of Blast $838.46m and Scroll $601.14m, but that today Scroll with $771.92m has more TVL than Blast with $766.41m, so that taking the criteria of the proponent to decide by TVL, Scroll should have been chosen. Source: DefiLllama.\n\nimage494×691 40.1 KB\n\nBut beyond that, we understand that what has happened is very serious and dangerous, the DAO chose Scroll in third place, so the onchain vote should have included Scroll, the proposer by choosing Blast using his own criteria, did not respect and violated what was decided by the DAO.\n\nWe know that the consequences of this are not serious in themselves, since a dashboard will be made analysing Blast instead of Scroll, but we understand that the impact of the vote or the importance of what is being voted in this specific case is secondary, the issue here is that the DAO’s decision has been violated and not respected, which could set a very serious and dangerous precedent in other votes with greater impact.\n\nConsequently, we vote against and request the proposer to cancel this onchain vote and submit a new one that respects the DAO’s decision.\n\n1 Like\n\n[Temp Check] Forse Analytics for Uniswap Revitalization and Growth Program\n\nSEEDGov\n\nOctober 4, 2024, 2:30pm\n\n17\n\nProposal: Uniswap Accountability Committee S3 Elections (Snapshot)\n\nVote: 50% _JoJo – 50% Alicecorsini\n\nRationale: In principle, both successful candidates show a commitment of time and quality to Uniswap.\n\nWe know @_jojo in particular from the Arbitrum delegation where we witnessed his work capacity and professionalism.\n\nWith regard to @alicecorsini, we have great confidence in karpatkey’s support, so we understand that she is a suitable candidate for this seat, both given her experience as part of the Uniswap Treasury Working Group, and given karpatkey’s experience in financial and accountability issues.\n\n1 Like\n\nSEEDGov\n\nOctober 9, 2024, 3:29pm\n\n18\n\nProposal: [TEMP CHECK] - Onboarding Package for Lisk (Snapshot)\n\nVote: For\n\nRationale: We support this proposal as we find it reasonable and beneficial that in exchange for $375 of incentives to be provided by Uniswap, Lisk commits to match $250k in LSK incentives and to lock an additional $1m for 1 year. We also point out that the Oku deployment has already been arranged and therefore this proposal does not include the costs associated with it.\n\nFinally, we highlight that Lisk is on the Optimism Foundation’s whitelist to be part of the superchain, so it is an opportunity for Uniswap to continue to increase its presence in networks that will be part of that ecosystem.\n\n1 Like\n\nOnboarding Package for Lisk\n\nSEEDGov\n\nOctober 17, 2024, 1:20pm\n\n19\n\nProposal: Uniswap Growth Program Trial (Snapshot)\n\nVote: In Support\n\nRationale: We support this initiative because we understand that it can be beneficial for Uniswap to have a dedicated team for Business Development, Marketing and to explore the possibility of obtaining grants and incentives in various chains. We also believe that a 6-month trial program is appropriate in order to evaluate the concrete results obtained and the impact generated, and to decide whether or not to extend the programme, and if so, under the same or different conditions.\n\nSEEDGov is at the disposal of @alphagrowth, the Uniswap MetaGov Team (@PGov, @AranaDigital) and the UEII, we are present in different chains such as Arbitrum, Optimism, Scroll, ZKsync Gnonis, among others, both in delegation teams and in working groups dedicated to the evaluation of different grant and incentive programs, so we can collaborate in these processes.\n\n3 Likes\n\n[RFC] - Uniswap Growth Program Trial\n\nSEEDGov\n\nOctober 23, 2024, 6:35pm\n\n20\n\nProposal: [Updated] Forse Analytics for Uniswap Revitalization and Growth Program (Onchain)\n\nVote: For\n\nRationale: By including the 4 most voted chains in the snapshot voting (even with the same budget), the objections we raised in the previous on-chain vote have been overcome.\n\nFurthermore, we consider very positive the forecast that the budget will be released once the Uniswap Accountability Committee confirms that the work has been done.\n\nWe therefore now support the updated proposal submitted to onchain vote.\n\nWe thank @doo_stablelab for being so responsive to the criticisms it has received and improving the proposal based on it.\n\n1 Like\n\nnext page →\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nCuria Delegate Platform\n\nDelegation Pitch\n\n53\n\n2385\n\nJuly 23, 2026\n\nAtiselsts.eth Delegate Platform\n\nDelegation Pitch\n\n32\n\n4670\n\nJuly 9, 2026\n\nTané Delegate Platform\n\nDelegation Pitch\n\n59\n\n2404\n\nMarch 9, 2026\n\nIgnas Delegate Platform\n\nDelegation Pitch\n\n41\n\n1284\n\nMay 25, 2026\n\nArgonaut Delegate Platform\n\nDelegation Pitch\n\n63\n\n1821\n\nJuly 11, 2026","tokens":7611,"crawled_at":1791193380827}
+{"id":10228,"url":"https://docs.near.org/smart-contracts/quickstart","domain":"docs.near.org","chapter":"layer1_layer2","title":"Your First Smart Contract - NEAR Docs","text":"Welcome! NEAR accounts can store small apps known as smart contracts. In this tutorial, we’ll guide you through creating your first contract on the NEAR testnet.\nCreate an auction contract that allows users to place bids, track the highest bidder, and claim tokens at the end of the auction.\n\nPrefer an online IDE?\n\nWant to jump right into the code without setting up a local dev environment?Check out NEAR Playground for an easy-to-use online IDE with pre-configured templates.\n\n​\n\nPrerequisites\n\nBefore starting, make sure to set up your development environment.\n\n# Install Rust: https://www.rust-lang.org/tools/install\ncurl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh\n\n# Contracts will be compiled to wasm, so we need to add the wasm target\nrustup target add wasm32-unknown-unknown\n\n# Install NEAR CLI-RS to deploy and interact with the contract\ncurl --proto '=https' --tlsv1.2 -LsSf https://github.com/near/near-cli-rs/releases/latest/download/near-cli-rs-installer.sh | sh\n\n# Install cargo near to help building the contract\ncurl --proto '=https' --tlsv1.2 -LsSf https://github.com/near/cargo-near/releases/latest/download/cargo-near-installer.sh | sh\n\n​\n\nCreating the contract\n\nCreate a smart contract with the cargo near scaffolding tool by following its instructions:\n\n# Create a new contract called \"auction\"\ncargo near new auction\n\nCreating a project using cargo near new\n\nFor this tutorial, we chose to name the project auction, but feel free to use any name you prefer.\n\n​\n\nBuild and deploy the contract\n\nLet’s build the contract, create a NEAR testnet account, and deploy the contract to it.\n\n# Run the sandbox tests to verify the contract works as expected\ncargo test\n\n# Build the contract\ncargo near build non-reproducible-wasm\n\n# Create a free testnet account, replace `<account.testnet>` with your desired account name\nnear create-account <account.testnet> --useFaucet\n\n# Deploy the contract to the account\nnear deploy <account.testnet> ./target/near/auction.wasm\n\nAlready have a testnet account?If you already have a testnet account and would like to use it instead, you can log in with the command near login.\n\nGot an error on Windows?\n\nWhen working in WSL—or another headless Linux environment—you might encounter issues creating an account because the CLI tries to save keys to the system keychain.In such cases, you can try the following command to create the account:\n\nnear account create-account sponsor-by-faucet-service <your-account-id.testnet> autogenerate-new-keypair save-to-legacy-keychain network-config testnet create\n\nCongrats! Your contract now lives in the NEAR testnet network.\n\n​\n\nInitialize the auction\n\nThe contract stores the highest bid, auction end time, auctioneer address, and a flag to track whether proceeds have been claimed. Its init function sets these values when the contract is first initialized:\nlib.rs\n\npub struct Bid {\npub bidder: AccountId,\npub bid: NearToken,\n}\n\n#[near(contract_state)]\n#[derive(PanicOnDefault)]\npub struct Contract {\nhighest_bid: Bid,\nauction_end_time: U64,\nauctioneer: AccountId,\nclaimed: bool,\n}\n\n#[near]\nimpl Contract {\n#[init]\n#[private] // only callable by the contract's account\npub fn init(end_time: U64, auctioneer: AccountId) -> Self {\nSelf {\nhighest_bid: Bid {\nbidder: env::current_account_id(),\nbid: NearToken::from_yoctonear(1),\n},\nauction_end_time: end_time,\nclaimed: false,\nauctioneer,\n}\n}\n\nSee code on GitHub\n\nInitialize the auction by setting its end time and designating the auctioneer to receive the funds:\n\n# Get a timestamp for 5 minutes from now (in nanoseconds)\nFIVE_MINUTES_FROM_NOW=$(( $(date +%s%N) + 5 * 60 * 1000000000 ))\n\n# Initialize the auction\nnear call <account.testnet> init \"{\\\"end_time\\\": \\\"$FIVE_MINUTES_FROM_NOW\\\", \\\"auctioneer\\\": \\\"influencer.testnet\\\"}\" --useAccount <account.testnet>\n\nFeel free to replace influencer.testnet with any valid testnet account—this is where the winning bid will be sent.\n\n​\n\nPlace and view bids\n\nPlace a bid in the auction by calling the bid method and attaching a NEAR deposit. The function checks whether the auction is ongoing and whether the bid is higher than the stored amount. If it is, the contract records the new bid and refunds the previous bidder.\nlib.rs\n\n#[payable]\npub fn bid(&mut self) -> Promise {\n// Assert the auction is still ongoing\nrequire!(\nenv::block_timestamp() < self.auction_end_time.into(),\n\"Auction has ended\"\n);\n\n// Current bid\nlet bid = env::attached_deposit();\nlet bidder = env::predecessor_account_id();\n\n// Last bid\nlet Bid {\nbidder: last_bidder,\nbid: last_bid,\n} = self.highest_bid.clone();\n\n// Check if the deposit is higher than the current bid\nrequire!(bid > last_bid, \"You must place a higher bid\");\n\n// Update the highest bid\nself.highest_bid = Bid { bidder, bid };\n\n// Transfer tokens back to the last bidder\nPromise::new(last_bidder).transfer(last_bid)\n}\n\nSee code on GitHub\n\n# Create a new account to place the bid\nnear create-account <bidder-account.testnet> --useFaucet\n\n# Place a bid of 0.01 NEAR\nnear call <account.testnet> bid '{}' --deposit 0.01 --useAccount <bidder-account.testnet>\n\nIn this example, use the <bidder-account.testnet> account (remember to rename it) to call the bid function and attach a deposit of 0.01 NEAR.\n\n​\n\nView the highest bid\n\nThe get_highest_bid function only reads from the contract state, so it does not require a transaction or signature. You can also use the contract’s other view methods to query the auction end time, auctioneer, and claim status:\nlib.rs\n\npub fn get_highest_bid(&self) -> Bid {\nself.highest_bid.clone()\n}\n\npub fn get_auction_end_time(&self) -> U64 {\nself.auction_end_time\n}\n\npub fn get_auctioneer(&self) -> AccountId {\nself.auctioneer.clone()\n}\n\npub fn get_claimed(&self) -> bool {\nself.claimed\n}\n\nSee code on GitHub\n\nnear view <account.testnet> get_highest_bid '{}'\n\nExpected Output\n\n{\n\"bidder\": \"<bidder-account.testnet>\",\n\"amount\": \"10000000000000000000000\"\n}\n\nThe amount is shown in yoctoNEAR, the smallest unit of NEAR. Since 1 NEAR equals 10^24 yoctoNEAR, the displayed amount is 0.01 NEAR.\n\nFeel free to create more bidder accounts and place bids to see how the highest bid changes.\n\n​\n\nClaim the proceeds\n\nAfter the auction ends, anyone can call the claim method. It transfers the amount of the highest bid to the auctioneer and ends the auction:\nlib.rs\n\npub fn claim(&mut self) -> Promise {\nrequire!(\nenv::block_timestamp() > self.auction_end_time.into(),\n\"Auction has not ended yet\"\n);\n\nrequire!(!self.claimed, \"Auction has already been claimed\");\nself.claimed = true;\n\n// Transfer tokens to the auctioneer\nPromise::new(self.auctioneer.clone()).transfer(self.highest_bid.bid)\n}\n\nSee code on GitHub\n\nnear call <account.testnet> claim '{}' --useAccount <account.testnet>\n\nWho won?After the auction ends, you can determine the highest bidder by calling the get_highest_bid method again.\n\n​\n\nFrequently Asked Questions\n\nWhat about mainnet?\n\nYou can deploy a contract to mainnet using the same commands. Create a mainnet account and use the --networkId mainnet flag in the near CLI commands.\n\nHow much does it cost to deploy?\n\nThe cost of deploying a contract depends on its size: approximately 1 Ⓝ per 100 KB.\n\nCan I update a contract after deploying?\n\nYes. Redeploy with near deploy <account> <wasm-file>. The account stays the same, and the code is updated.\n\nHow do I test without deploying?\n\nUse the sandbox tests shown in this guide. They run locally in a simulated NEAR environment.\n\nCan I use a language other than Rust?\n\nYes. You can write smart contracts in any language that compiles to WebAssembly. Our documentation focuses on Rust, but community-maintained SDKs are available for other languages. See supported languages.\n\n​\n\nMoving forward\n\nCreate a Frontend\nCheck the auction frontend tutorial to learn how to build a simple web app that interacts with the auction contract.\n\nExtend the Contract\nFollow the auction NFT tutorial to award the highest bidder a Non-Fungible Token (NFT) and allow users to bid using Fungible Tokens (FT).\n\nLearn More about the SDK\nCheck our Anatomy of a Contract page to understand the different components that make up a NEAR smart contract.\n\nVersioning for this article\n\nAt the time of this writing, this example works with the following versions:\nrustc: 1.86.0\n\nnear-cli-rs: 0.22.0\n\ncargo-near: 0.16.1\n\nWas this page helpful?","tokens":2084,"crawled_at":1791193383162}
+{"id":10229,"url":"https://a16zcrypto.com/posts/article/science-of-blockchain-conference-24-field-notes","domain":"a16zcrypto.com","chapter":"research","title":"Science of Blockchain Conference ‘24: Field notes - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nScience of Blockchain Conference ‘24: Field notes\nJoseph Bonneau, Pranav Garimidi, and Joachim Neu\n10.12.24\n\nTags & Share Tags\nfield notes\nresearch\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nEditor’s note: Field notes is a series where we report on the ground at significant industry, research, and other events. In this edition, Joseph Bonneau, Pranav Garimidi and Joachim Neu, from a16z crypto’s research team, share their highlights from the Science of Blockchain Conference and affiliated workshops, which were held in New York City around August 7-9, 2024. SBC is a premier conference bringing together researchers and builders from the web3 community. You can see the complete program of the main conference here with recordings of talks freely available online.\n\nThe Science of Blockchain Conference has come a long way since it was first held in 2017. The name itself has evolved — from the Stanford Bitcoin Conference to the Stanford Blockchain Conference to today’s Science of Blockchain Conference. The name update was particularly relevant this year, as it was the first edition held outside of Stanford (this year at Lerner Hall, Columbia University, in New York City). The community has grown in size and scope, with now hundreds of attendees (registration was free but “sold out” early at ~1500 registrations) and over 50 associated side events and workshops.\n\nFortunately, all of the talks at the main conference were recorded and are available online. While the content at SBC is strictly technical and focused on research, and draws a large proportion of its attendees from academia, unlike traditional academic conferences there are no associated proceedings. That is, authors do not need to publish a paper to present, and they can present work that was already submitted to a separate conference or journal. As a result, the conference functions as a “greatest hits” from the web3 community, with less than one in ten submissions making it into the program.\n\na16z was active throughout the conference and affiliated workshops with several talks:\n\nGeneral Partner Chris Dixon was interviewed by Dan Boneh in a special segment, offering his broad perspective on the space and describing his experience writing Read Write Own.\n\nHead of Research Tim Roughgarden presented work on Security of Restaking Networks at the affiliated Consensus workshop.\n\nResearch Associate Joachim Neu presented his work on Optimal Flexible Consensus and Nakamoto Consensus under Bounded Processing Capacity.\n\nFormer research intern Ertem Nusret Tas presented Fair Data Exchange, a product of the a16z research group.\n\nFormer research intern Mahimna Kelkar presented his work on Proofs of Complete Knowledge and current intern Sourav Das presented on Asynchronous Consensus.\n\nInvestment Partner Guy Wuollet spoke on the need for verification at the DePIN Summit.\n\nIn the rest of this post we’ll highlight several other talks that the a16z research team found particularly interesting.\n\nInvited industry talks\n\nThe conference featured many talks from industry, showcasing the variety of practical research being done. In a positive trend, all of these talks featured in-depth white paper sharing technical details.\n\nEd Felten, Arbitrum: Permissionless Validation Using the BoLD Protocol\n\nEli Ben-Sasson, Starkware: Stwo\n\nYehuda Lindell, Coinbase: MPC for custody at Coinbase\n\nEllie Davidson, Espresso: The Espresso Sequencing Network: HotShot Consensus, Tiramisu Data-Availability, and Builder-Exchange\n\nDeepak Maram, Mysten: zkLogin\n\nTalks on practical security\n\nStefanos Chaliasos presented a survey: SoK: What Don’t We Know? Understanding Security Vulnerabilities in SNARKs (co-authored by a16z research intern Jens Ernstberger). This work is the result of analyzing over 100 publicly disclosed security vulnerabilities in SNARK systems over the past 6 years, providing a first look at how these systems tend to fail in practice. A key takeaway is that practical SNARK deployments are complex in software (on top of the complicated math), leading to many ways for things to go wrong. The majority of vulnerabilities were circuit specification bugs, which is a very complex task forcing developers to use a low-level language to specify a problem. There is a strong bias towards under-constrained circuits (leading to soundness bugs) rather than over-constrained circuits (leading to completeness bugs). The reason for this bias is intuitive: completeness bugs mean a system doesn’t work for some intended uses, which is usually detected by functionality testing. Soundness bugs are typically invisible until detected or exploited.\n\nMahimna Kelkar presented a paper Complete Knowledge: Preventing Encumbrance of Cryptographic Secrets, which poses a thought-provoking question: How can we be sure somebody really knows a cryptographic secret, like an ECDSA signing key? In a world of trusted hardware, it isn’t enough to simply have them sign a challenge message with it or produce a zero-knowledge proof-of-knowledge. They might have an encumbered version of the key, say, a TEE (hardware enclave) which has the key and will sign some messages or compute a proof but not allow certain banned messages to be signed. This talk (and the associated paper) discuss some protocols which aim to prove complete (or unencumbered) knowledge of the secret.\n\nTalks on Transaction Fee Mechanisms\n\nMax Resnick presented new work on Dynamic Transaction Fee Mechanisms. The work has two main contributions: it first shows that moving from stochastic block times (as in PoW) to deterministic block times (as in PoS) leads to decreased congestion as stable demand is matched more closely with stable supply. This in turn benefits users submitting transactions in being more certain of how much they need to bid to get included in a block. (This is especially true if the fee mechanism is a first price auction but can also be relevant under EIP-1559.) Their second result is that the EIP-1559 update rule under current parameters can lead to long delays for users when a large disparity exists between low and high value users. The concern is that the current update rule causes the base fee to increase too quickly even when the underlying demand isn’t shifting, pricing out lower value users even when there is available blockspace. They also justify the current mechanism increasing base fees too quickly with empirical results showing that users can frequently get substantial savings in how much they are paying for gas if they are willing to wait even just five blocks. The main takeaway from this work is theoretical and empirical evidence supporting decreasing how fast the base fee increases to improve UX for users.\n\nTheo Diamandis presented Multidimensional Blockchain Fees Are (Essentially) Optimal. This work uses a regret minimization framework to study the optimality of different base fee update rules. As a benchmark, the authors consider what optimal per-resource prices would be given that the mechanism designer was privy to the demand over a long period of time. They then provide a class of base fee update rules that given a sufficiently long enough amount of time are nearly as good as being able to perfectly set the prices upfront. In particular, the update rule that EIP-1559 uses falls into the class of update rules they show are optimal. To go along with their results, they prove that no other update rules can substantially beat the class of update rules they give. Overall, this talk shows how we can use tools from the convex optimization and regret minimization literature to have a concrete way to judge the optimality of the mechanisms we are using in practice versus the wide swath of update rules we could be using instead.\n\nTalks on consensus\n\nThe affiliated Consensus workshop was held on August 6, 2024 at Cornell Tech on Roosevelt Island. The recorded talks of this event are also available online.\n\na16z crypto’s Head of Research Tim Roughgarden presented a new work on the Robustness of Restaking Networks. An urgent question in restaking is to characterize under what circumstances a network remains secure when validators reuse stake as collateral to crypto-economically-secure multiple different services. Specifically, the concern is that if too little stake is used to back too many services, then the profits an attacker stands to gain from compromising the services may outweigh the cost it has to bear from the slashing of its stake following an attack, making attack a rational course of action. The authors of the paper give conditions on the network structure and the profits and costs of an attack under which a restaking network is guaranteed to be secure.\n\nSandro Coretti-Drayton presented a network model for gossip networks where nodes have bounded processing capacity, and uses it to prove the security of the Leios protocol which provides High-Throughput Blockchain Consensus under Realistic Network Assumptions. For background, consensus protocols are usually proven secure using very simplistic models for the phenomena that could impact the communication among honest parties. For instance, a standard model assumes that a known upper-bound exists for the time it takes for a message sent by an honest party to be received by all other honest parties. Such a model neglects security-relevant aspects such as network topology (in reality, not every honest party has a direct connection to every other honest party) or congestion (in reality, messages may be delayed more or less depending how many other messages are propagating simultaneously). The talk and its associated paper continue a recent line of work that devises and employs models that capture these aspects.\n\n***\n\nJoseph Bonneau is a Research Partner at a16z Crypto. His research focuses on applied cryptography and blockchain security. He has taught cryptocurrency courses at the University of Melbourne, NYU, Stanford, and Princeton, and received a PhD in computer science from the University of Cambridge and BS/MS degrees from Stanford.\n\nPranav Garimidi is a Research Analyst at a16z Crypto. He does research on problems in mechanism design and algorithmic game theory as it relates to blockchain systems. He is especially focused on how incentives interact across the blockchain stack. Prior to a16z, Pranav was a student at Columbia University where he graduated with a degree in Computer Science.\n\nJoachim Neu is a Research Associate at a16z Crypto. He is particularly interested in the theory and practice of distributed systems security. Recent research topics include Internet-scale consensus for heterogeneous user-bases, with applications to consensus security for the Ethereum blockchain.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nCharts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":3368,"crawled_at":1791193383217}
+{"id":10230,"url":"https://www.metaplex.com/docs/smart-contracts/token-metadata/pnfts","domain":"www.metaplex.com","chapter":"docs","title":"Programmable NFTs (pNFTs) | Token Metadata","text":"Token Metadata is a legacy program. It remains supported, but is not recommended for new projects. Use Core instead.\n\nAs mentioned in the overview page, Programmable NFTs (pNFTs) are a new asset standard that allows creators to define custom rules on specific operations and delegate more granularly to third-party authorities.\nNo More Bypassing Token Metadata\nBecause the Token Metadata program is built on top of the SPL Token program, any owner or spl-token delegate can interact with the SPL Token program directly and bypass the Token Metadata program on vital operations like transferring and burning. Whilst this creates a nice composability pattern between programs it also means the Token Metadata program cannot enforce any rules on behalf of the creators.\nA good example of why this can be problematic is that Token Metadata cannot enforce secondary sales royalties. Even though the royalty percentage is stored on the Metadata account, it is up to the user or program that performs the transfer to decide whether they want to honor it or not. We talk more about this and how pNFTs fix this issue in a section below.\nProgrammable NFTs are introduced to solve this issue in a flexible way that allows creators to customize the authorization layer of their assets.\nProgrammable NFTs work as follows:\nThe Token account of the pNFT is always frozen on the SPL Token program, regardless of whether the pNFT is delegated or not. This ensures that no one can bypass the Token Metadata program by interacting with the SPL Token program directly.\nWhenever an operation is performed on the Token account of a pNFT, the Token Metadata program thaws the account, performs the operation, and then freezes the account again. All of this happens atomically in the same instruction. That way, all operations that could be made on the SPL Token program are still available to pNFTs but they are always performed through the Token Metadata program.\nWhen a Token Delegate is set on a pNFT, the information is stored in a Token Record account. Since pNFTs are always frozen on the SPL Token program, it is the responsibility of the Token Record account to keep track of whether the pNFT is really locked or not.\nBecause every single operation that affects a pNFT must go through the Token Metadata program, we created a bottleneck that allows us to enforce authorization rules for these operations. These rules are defined in a Rule Set account managed by the Token Auth Rules program.\nEssentially, this gives pNFTs the ability to:\nHave more granular delegates.\nEnforce rules on any operation.\nLet's dive into these two abilities in more detail.\nMore granular delegates\nSince all pNFTs operations must go through the Token Metadata program, it can create a new delegate system on top of the spl-token delegate. One that is more granular and allows pNFT owners to pick the operations they want to delegate to a third party.\nInformation for this new delegate system is stored on a special Token Record PDA that is derived from both the Mint and the Token accounts of the pNFT. When a new delegate authority is assigned to a pNFT, the Token Metadata program synchronizes that information on both the Token account and the Token Record account.\nWe discuss these delegates in more detail in the \"Token Delegates\" section of the Delegated Authorities page.\n\nWallet Account\n\nOwner: System Program\n\nToken Account\n\nOwner: Token Program\n\nDelegate Authority\n\nMint Account\n\nOwner: Token Program\n\nPDA\n\nToken Record Account\n\nOwner: Token Metadata Program\n\nKey = TokenRecord\n\nBump\n\nState\n\nRule Set Revision\n\nDelegate\n\nDelegate Role\n\nLocked Transfer\n\nReact Flow\nPress enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.\nPress enter or space to select an edge. You can then press delete to remove it or escape to cancel.\n\nAdditional Accounts\npNFTs require additional accounts for most operations and these include tokenRecord, authorizationRules, authorizationRulesProgram.\nToken Record\nA tokenRecord account is responsible for holding details regarding the token and its state such as delegates, it's lock state.\nThere are a few ways to access the tokenRecord account and that is either by fetchDigitalAssetWithAssociatedToken which returns all needed accounts including metadata, token account, and token record. An alternative is generate the token record PDA address using the mint ID and the token account address with the findTokenRecordPda function.\nAsset With Token\nYou can fetch all accounts needed with the fetchDigitalAssetWithAssociatedToken function which returns data such as the pNFT metadata account, the token account, and the token record account.\n\n1import { publicKey } from '@metaplex-foundation/umi';\n\n2import { fetchDigitalAssetWithAssociatedToken } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4const mint = publicKey('11111111111111111111111111111111');\n\n5const owner = publicKey('22222222222222222222222222222222');\n\n6\n\n7const assetWithToken = await fetchDigitalAssetWithAssociatedToken(\n\n8 umi,\n\n9 mint,\n\n10 owner\n\n11);\n\n12\n\n13console.log('Metadata:', assetWithToken.metadata.name);\n\n14console.log('Token Record:', assetWithToken.tokenRecord);\n\n1import { address } from '@solana/addresses';\n\n2import { fetchDigitalAssetWithAssociatedToken } from '@metaplex-foundation/mpl-token-metadata-kit';\n\n3\n\n4const mint = address('11111111111111111111111111111111');\n\n5const owner = address('22222222222222222222222222222222');\n\n6\n\n7const assetWithToken = await fetchDigitalAssetWithAssociatedToken(\n\n8 rpc,\n\n9 mint,\n\n10 owner\n\n11);\n\n12\n\n13console.log('Metadata:', assetWithToken.metadata.name);\n\n14console.log('Token Record:', assetWithToken.tokenRecord);\n\nToken Record PDA\nGenerates the PDA address for the tokenRecord account with the mintId and tokenAccount of the wallet the pNFT asset is stored in.\n\n1import { publicKey } from '@metaplex-foundation/umi';\n\n2import { findTokenRecordPda } from '@metaplex-foundation/mpl-token-metadata';\n\n3\n\n4const mint = publicKey('11111111111111111111111111111111');\n\n5const token = publicKey('22222222222222222222222222222222');\n\n6\n\n7const tokenRecordPda = findTokenRecordPda(umi, {\n\n8 mint,\n\n9 token,\n\n10});\n\n11\n\n12console.log('Token Record PDA:', tokenRecordPda);\n\n1import { address } from '@solana/addresses';\n\n2import { findTokenRecordPda } from '@metaplex-foundation/mpl-token-metadata-kit';\n\n3\n\n4const mint = address('11111111111111111111111111111111');\n\n5const token = address('22222222222222222222222222222222');\n\n6\n\n7const [tokenRecordPda] = await findTokenRecordPda({\n\n8 mint,\n\n9 token,\n\n10});\n\n11\n\n12console.log('Token Record PDA:', tokenRecordPda);\n\nRuleSet\nIf you have the metadata account data available you can check for the programmableConfig field on the metadata account to get the rule set.\n\n1import { unwrapOptionRecursively } from '@metaplex-foundation/umi';\n\n2\n\n3// Assuming assetWithToken was fetched using fetchDigitalAssetWithAssociatedToken\n\n4\n\n5const ruleSet = unwrapOptionRecursively(\n\n6 assetWithToken.metadata.programmableConfig\n\n7)?.ruleSet;\n\n8\n\n9console.log('Rule Set:', ruleSet);\n\n1// No additional imports needed - programmableConfig is directly on metadata\n\n2\n\n3// Assuming assetWithToken was fetched using fetchDigitalAssetWithAssociatedToken\n\n4\n\n5// In Kit, options are represented as { __option: 'Some', value: ... } or { __option: 'None' }\n\n6const programmableConfig = assetWithToken.metadata.programmableConfig;\n\n7const ruleSet = programmableConfig.__option === 'Some'\n\n8 ? programmableConfig.value.ruleSet\n\n9 : null;\n\n10\n\n11console.log('Rule Set:', ruleSet);\n\nAuthorization Rules Program\nIf you have a ruleSet set on your pNFT Asset you will need to pass in the Authorization Rules Program ID so the ruleSet can be validated.\n\n1import { getMplTokenAuthRulesProgramId } from '@metaplex-foundation/mpl-token-auth-rules';\n\n2\n\n3const authorizationRulesProgram = getMplTokenAuthRulesProgramId(umi);\n\n4\n\n5console.log('Auth Rules Program:', authorizationRulesProgram);\n\n1import { address } from '@solana/addresses';\n\n2\n\n3// Token Auth Rules Program ID\n\n4const authorizationRulesProgram = address('auth9SigNpDKz4sJJ1DfCTuZrZNSAgh9sFD3rboVmgg');\n\n5\n\n6console.log('Auth Rules Program:', authorizationRulesProgram);\n\nAuthorization Data\nIf you have a ruleSet on your pNFT Asset that requires additional data for validation you would pass it in as authorizationData: { payload: ... } in the instruction parameters.\nEnforcing rules on any operation\nOne of the most important features of Programmable NFTs is their ability to enforce a set of rules on any operation that affects them. The entire authorization layer is provided by another Metaplex program called Token Auth Rules. Whilst that program is used to make pNFTs programmable, it is a generic program that can be used to create and validate authorization rules for any use case.\nIn the case of pNFTs, the following operations are supported:\nOperationDescription\nTransfer:Owner\nTransfer initiated by the owner of the pNFT\n\nTransfer:SaleDelegate\nTransfer initiated by a Sale delegate\n\nTransfer:TransferDelegate\nTransfer initiated by a Transfer or Locked Transfer delegate\n\nTransfer:MigrationDelegate\nTransfer initiated by a Migration delegate (legacy delegate used during the pNFT migration period)\n\nTransfer:WalletToWallet\nTransfer between wallets (currently not in use)\n\nDelegate:Sale\nApprove a Sale delegate\n\nDelegate:Transfer\nApprove a Transfer delegate\n\nDelegate:LockedTransfer\nApprove a Locked Transfer delegate\n\nDelegate:Utility\nApprove a Utility delegate\n\nDelegate:Staking\nApprove a Staking delegate\n\nCreators can assign a custom Rule to any of these operations. When that operation is performed, the Token Metadata program will ensure the rule is valid before allowing the operation to go through. The available rules are documented by the Token Auth Rules program directly but it is worth noting that there are two types of rules:\nPrimitive Rules: These rules explicitly tell us if an operation is allowed or not. For instance: the PubkeyMatch rule will pass if and only if the public key at the given field matches the given public key; the ProgramOwnedList will pass if and only if the program owning the account at the given field is part of a given list of programs; the Pass rule will always pass; etc.\nComposite Rules: These rules aggregate multiple rules together to create a more complex authorization logic. For instance: the All rule will pass if and only if all of the rules it contains pass; the Any rule will pass if and only if at least one of the rules it contains passes; the Not rule will pass if and only if the rule it contains does not pass; etc.\nOnce we have all the rules for our operations defined, we can store them in a Rule Set account on the Token Auth Rules program. Whenever we need to make a change to this Rule Set, a new Rule Set Revision is appended to the Rule Set account. This ensures any pNFT currently locked within a specific revision can be unlocked before moving on to the latest revision.\n\nWallet Account\n\nOwner: System Program\n\nToken Account\n\nOwner: Token Program\n\nMint Account\n\nOwner: Token Program\n\nPDA\n\nToken Record Account\n\nOwner: Token Metadata Program\n\n...\n\nRule Set Revision\n\nPDA\n\nMetadata Account\n\nOwner: Token Metadata Program\n\n...\n\nProgrammable Configs\n\nRule Set Account\n\nOwner: Token Auth Rules Program\n\nHeader\n\nRule Set Revision 0\n\nRule Set Revision 1\n\n...\n\nReact Flow\nPress enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.\nPress enter or space to select an edge. You can then press delete to remove it or escape to cancel.\n\nUse-case: Royalty enforcement\nNow that we understand pNFTs a bit better, let's look at a concrete use case that can be solved with PNFTs: royalty enforcement.\nAs mentioned above, without pNFTs, anyone can bypass the royalty percentage stored on the Metadata account by interacting with the SPL Token program directly. This means creators must rely on the goodwill of the users and programs that interact with their assets.\nHowever, with pNFTs, creators can design a Rule Set that ensures programs that do not enforce royalties are forbidden to perform transfers on their assets. They can use a combination of Rules to create an allow list or a deny list depending on their needs.\nAdditionally, since Rule Sets can be shared and reused across multiple pNFTs, creators can create and share Community Rule Sets to ensure that any program that stops supporting royalties is immediately banned from interacting with any pNFTs that use such Community Rule Set. This creates a strong incentive for programs to support royalties as they would otherwise be banned from interacting with a large number of assets.","tokens":3197,"crawled_at":1791193413400}
+{"id":10231,"url":"https://gov.uniswap.org/t/ignas-delegate-platform/24674","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Ignas Delegate Platform - Delegation Pitch - Uniswap Governance","text":"Ignas Delegate Platform\n\nDelegation Pitch\n\nIgnas\n\nOctober 3, 2024, 7:19am\n\n1\n\nBasic Info\n\nName: Ignas\n\nDelegate Address: 0x3DDC7d25c7a1dc381443e491Bbf1Caa8928A05B0\n\nDelegate Profile: https://www.tally.xyz/gov/uniswap/delegate/0x3ddc7d25c7a1dc381443e491bbf1caa8928a05b0\n\nX (Twitter): https://x.com/DefiIgnas\n\nTelegram: @ignasdefi\n\nIntro\n\nI’m Ignas, a DeFi solo researcher breathing and living with Defi. My mission is to provide clear, in-depth insights to promote DeFi, helping my audiences stay up-to-date with the latest trends while actively supporting DAO development.\n\nI believe in the decentralized future and it means actively participating in Uniswap DAO in every way I can—whether it’s by serving as a delegate, joining working groups, discussing any proposals or seizing new opportunities that come up. I’ll also be sharing key DAO decisions on X and my blog.\n\nWhile I am a new DAO member on THIS WALLET, I have been following Uniswap DAO closely since years ago and covered it in my threads, bringing more visibility to the DAO.\n\nExamples of posts: BNB Chain launch 2 (138K views), and Bringing awareness to Uniswap branded Visa card vote (101K views)\n\nDelegate Communication Intent\n\nI’m committed to keeping the Uniswap community informed with regular, transparent updates. I’ll provide clear insights into my voting choices and reasoning to ensure everyone understands the direction I’m headed and why.\n\nWhy I Want to be a Delegate\n\nCurrently, DeFi DAOs face several internal issues, such as voter apathy leading to governance attacks, insider voting, and voting concentration among a few active voting addresses. Additionally, they face external challenges like regulatory uncertainty.\n\nI believe in a decentralized future, even if it seems naive. However, the current state of crypto is plagued by misaligned incentives that prioritize short-term speculative gains over the core DeFi values of self-sovereignty and custody.\n\nEqually concerning is the trend of McKinsification in DAOs, where decisions are increasingly made by one or two professional consultant delegates. This discourages individual participation, as their opinions and votes have less impact.\n\nTo make DeFi DAOs viable, we must align incentives to encourage active participation in governance from the broader crypto community. I believe that community must be at the core of every DAO. Without giving the community a say in protocol governance, we’re no better than the Web2 companies we aim to replace—companies that view their “community” merely as users to extract value from.\n\nI will support initiatives that align token holders with the protocol, such as revenue sharing or other methods to bring value to the token. Token holders are frustrated with exploitative tokenomics that only benefit early insiders who acquired tokens at much lower prices, leaving no upside for new investors. Without incentives to buy and hold tokens, the attractiveness and health of DAOs decline.\n\nFinally, as mentioned, I will highlight key votes and decisions of the DAO on X and my blog, as I believe the general public is often unaware of important actions being taken.\n\nDisclosure\n\nI am the co-founder of Pink Brains, an organization dedicated to promoting various crypto projects through educational content. You can find more info about us here: https://linktr.ee/pinkbrains.\n\nI’m also now stepping up as a delegate for Arbitrum and being very active in Aave, Optimism, and here - Uniswap. I plan to apply as a delegate to other DAOs soon, with the same mission of strengthening them and aligning token holders with the protocol.\n\nI always make appropriate disclosures and recuse myself from voting when necessary.\n\nTreasury Delegation Round 2 Ideas Thread\n\n[RFC] Principles for Uniswap DAO\n\nIgnas\n\nOctober 15, 2024, 8:59am\n\n2\n\nProposal: Forse Analytics for Uniswap Revitalization and Growth Program (Tally)\n\nDate Voted: October 1,2024\n\nVote: For\n\nRationale: I think it’s important to see how Uniswap’s incentive programs are affecting the DAO. Offering rewards to get people involved can be expensive, so we need to find out if it’s actually making people more active in the DAO by using Force. Moreover, the choice of three blockchains also seems like a good decision. We don’t need to spread our resources and money too thin across too many chains. These three blockchains have high TVL, so it makes sense to focus on them. By concentrating on these, hopefully it’ll help us analyze how well we’re attracting and retaining users on these networks\n\n2 Likes\n\nIgnas\n\nOctober 15, 2024, 9:02am\n\n3\n\n2. Proposal: [TEMP CHECK] - Onboarding Package for Lisk (Snapshot)\n\nDate Voted: October 1,2024\n\nVote: Abstain\n\n2 Likes\n\nIgnas\n\nOctober 18, 2024, 9:25am\n\n4\n\nProposal: [Uniswap Growth Program Trial] (Snapshot)\n\nDate Voted: October 17, 2024\n\nVote: In support\n\nRationale: I like how this proposal identified the current issues in Uniswap—it’s spot on.\n\nI’ve mentioned this before in the previous post, [RFC] AlphaGrowth - Growing Uniswap through Incentives, Distribution, and Co-Marketing. While the initiative may or may not succeed, it’s crucial to experiment with ways to strengthen Uniswap’s brand, image, and reach to maintain and attract new users.\n\nThis is especially important as competition increases and Uniswap can’t rely on its first-mover advantage indefinitely. With the launch of Uniswap v4, educating users about its features is essential. Since Uniswap v4 functions more like a platform, establishing a partnership incentive program or any marketing initiatives are a solid strategy.\n\nIgnas\n\nOctober 30, 2024, 3:23am\n\n5\n\n4. Proposal: [Updated] Forse Analytics for Uniswap Revitalization and Growth Program (Tally)\n\n- Date Voted: October 21, 2024\n\n- Vote: For\n\n- Rationale: Same reason with the vote on Snapshot. Offering rewards to get people involved can be expensive, so we need to find out if it’s actually making people more active in the DAO by using Force.\n\nIgnas\n\nOctober 30, 2024, 3:29am\n\n6\n\n5. Proposal: Uniswap Growth Program Trial (Tally)\n\n- Date Voted: October 24, 2024\n\n- Vote: For\n\n- Rationale: Same reason with vote on Snapshot. While the initiative may or may not succeed, it’s crucial to experiment with ways to strengthen Uniswap’s brand, image, and reach to maintain and attract new users.\n\nIgnas\n\nNovember 5, 2024, 8:03am\n\n7\n\n6. Proposal: [TEMP CHECK] - Tally Uniswap Proposal (Snapshot)\n\n- Date voted: November 4, 2024\n\n- Vote: For\n\n- Rationale: I’m in favor of this proposal! Tally has proven its value with so many DAOs using it for on-chain voting. I have no issues with the requested budget, but it would be great if the proposal could outline the new features planned and how they will enhance the governance experience.\n\nIgnas\n\nNovember 26, 2024, 8:39am\n\n8\n\n7. Proposal: Supporting Tally’s Development and Enhancements for Uniswap DAO Governance (Tally)\n\nDate voted: November 25, 2024\n\nVote: For\n\nRationale: Same reason with Snapshot vote. I voted for. Tally has proven its value with so many DAOs using it for on-chain voting.\n\nIgnas\n\nDecember 5, 2024, 7:40am\n\n9\n\n8. Proposal: [TEMP CHECK] Uniswap DAO Principles (Snapshot)\n\nDate Voted: December 4, 2024\n\nVote: For\n\nRationale: As I mentioned in my thread https://gov.uniswap.org/t/ignas-delegate-platform/24674?u=ignas, I’m all for initiatives that makes governance more decentralized, neutral, transparent, and resistant to manipulation. This is key to the protocol’s long-term sustainability in DeFi. So, definitely a “yes” from me\n\nOther delegates such as Seedgov, Jengajojo,… added great suggestions. Looking forward to seeing it applied!\n\nIgnas\n\nDecember 18, 2024, 7:38am\n\n10\n\n9. Proposal: [Temp Check] - Adopt The SEAL Safe Harbor Agreement (Snapshot)\n\nDate Voted: December 17, 2024\n\nVote: For\n\nRationale: I think this kind of proposal is really important for every DAO to have a quick response mechanism for attacks and protect user funds. From both a user and delegate perspective, I voted yes.\n\nIgnas\n\nDecember 20, 2024, 8:21am\n\n11\n\n10. Proposal: [TEMP CHECK] Scale Uniswap Liquidity on Celo (Snapshot)\n\nDate Voted: December 18, 2024\n\nVote: For\n\nRationale: I think collaborating with Celo and the Stabila Foundation is a good move for building a long term partnership between ecosystems. I don’t have any objections. This proposal will boost Uniswap’s liquidity and help expand into new markets.\n\nIgnas\n\nDecember 20, 2024, 8:24am\n\n12\n\nDate Voted: December 19, 2024\n\n11. Proposal: [TEMP CHECK] Metal L2: Bridging TradFi and DeFi Through Uniswap V3 (Snapshot)\n\nVote: Abstain\n\nRationale: I echo other delegate’s concerns. Using DAO funds for a new Layer 2 with no long-term operational history feels risky. Potential future issues could impact Uniswap’s reputation :). Voted Abstain\n\n12. Proposal: Discretionary Budget from UAC for Co-Incentive Campaigns (Snapshot)\n\nVote: Allow UAC Surplus Spending\n\nRationale: I think using the surplus budget for co-incentive campaigns is a good move to boost Uniswap’s liquidity and market presence. That being said, it’s important to ensure that the budget isn’t overused and that there’s still enough reserve for future needs\n\nIgnas\n\nDecember 23, 2024, 8:32am\n\n13\n\n13. Proposal: [RFC] Deploy Uniswap V3 on Sonic (formerly Fantom) (Snapshot)\n\nDate Voted: December 20, 2024\n\nVote: $250k Incentive Match\n\nRationale: Voted for the $250k Incentive Match. I believe matching the incentive will strengthen Uniswap’s relationship with Sonic and encourage more liquidity providers to join the pools on the Sonic platform.\n\nIgnas\n\nJanuary 7, 2025, 5:51am\n\n14\n\nDate Voted: January 6, 2025\n\n14. Proposal: Incentive Package for Sonic (Tally)\n\nVote: For\n\nRationale: Same reason with Snapshot vote. Matching the incentive will strengthen Uniswap’s relationship with Sonic and encourage more liquidity providers to join the pools on the Sonic platform\n\n15. Proposal: Scale Uniswap Liquidity on Celo (Tally)\n\nVote: For\n\nRationale: Celo is good :). Voted for with same reason with Snapshot vote.\n\nIgnas\n\nJanuary 14, 2025, 9:54am\n\n15\n\nDate Voted: January 13, 2025\n\n16. Proposal: Uniswap DAO Principles (Tally)\n\nVote: For\n\nRationale: Voted For with same reason on Snapshot. I’m all for initiatives that makes governance more decentralized, neutral, transparent, and resistant to manipulation.\n\n17. Proposal: Governance Proposal - Adopt The SEAL Safe Harbor Agreement (Tally)\n\nVote: For\n\nRationale: Same reason with Snapshot vote. Its important for every DAO to have a quick response mechanism for attacks and protect user funds.\n\nIgnas\n\nFebruary 26, 2025, 8:58am\n\n16\n\n18. Proposal: [Temp Check] Uniswap Delegate Reward Initiative - Cycle 3 (Snapshot)\n\nDate Voted: February 20, 2025\n\nVote: For\n\nDate Voted: Voted yes on Snapshot. I believe the program will contribute to a more decentralized governance structure and drive more engagement within Uniswap DAO.\n\nIgnas\n\nFebruary 27, 2025, 11:10am\n\n17\n\nDate Voted: February 27, 2025\n\n19. Proposal: [Temp Check] Uniswap Unleashed (Snapshot)\n\nVote: For\n\n20. Proposal: [Temp Check] Unichain and Uniswap v4 Liquidity Incentives (Snapshot)\n\nVote: For\n\nRationale for 19,20:\n\nI see the good motivation here because these proposals bring real value to Uniswap.\n\nUniswap v4 launched about a month ago, but growth is slow. TVL is just $85M, and daily volume is only $73M (compared to $1.7B on v3).\n\n$24M liquidity incentive could help improve trading efficiency and keep Uniswap competitive.\n\nWhat I don’t really like, though, is that Labs collects front-end fees yet doesn’t use that money and still asks the DAO for funding.\n\nBut still voted yes on both propsals since v4 needs this incentive obviously.\n\nScreen Shot 2025-02-27 at 17.51.562354×1030 253 KB\n\nIgnas\n\nMarch 3, 2025, 10:17am\n\n18\n\n21. Proposal: Uniswap Delegate Reward Initiative - Cycle 3 (Tally)\n\nDate Voted: February 28, 2025\n\nVote: For\n\nRationale: Same reason with Snapshot vote. I believe the program will contribute to a more decentralized governance structure and drive more engagement within Uniswap DAO. Voted for!\n\nIgnas\n\nMarch 17, 2025, 12:22pm\n\n19\n\nDate Voted: March 14, 2025\n\n22. Proposal: [Temp Check] Saga Uniswap v3 Liquidity Incentive (Snapshot)\n\nVote: Against\n\nRationale: Saga Foundation is putting up 2M SAGA ($700K) per month and covering $5K/month for maintenance, which shows they’re serious about pushing Uniswap on Saga.\n\nThat said, Saga is still a relatively new L1 without long term data on their ecosystem’s success. Plus, if a stronger DEX gets integrated in the future, Uniswap could lose the position after already spending 250K UNI on incentives. That’s why I voted Against!\n\n23. Proposal: Unichain and Uniswap v4 Liquidity Incentives (Tally)\n\nVoted: For\n\n24. Proposal: Uniswap Unleashed (Tally)\n\nVote: For\n\nRationale for 23,24: Voted for as same Snapshot reason → https://gov.uniswap.org/t/ignas-delegate-platform/24674/17?u=ignas\n\nIgnas\n\nMarch 31, 2025, 7:33am\n\n20\n\n26. Proposal: [Temp Check] Treasury Delegation Round 2 (Snapshot)\n\nDate voted: March 28, 2025\n\nVote: For\n\nRationale: I see no reason to block this. Clearly, the lack of VP has made some delegates question whether it’s worth staying active in the DAO. They have a voice but no real power, means their contributions mostly serve those with bigger votes\n\nPlus, setting expectations for delegates who receive VP makes sense, it ensures only those truly committed keep their delegation.\n\nSo by maintaining a high quality delegate group, Uniswap DAO can make better decisions and drive long term growth. I voted yes!\n\nnext page →\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nTané Delegate Platform\n\nDelegation Pitch\n\n59\n\n2404\n\nMarch 9, 2026\n\nSEEDGov Delegate Platform\n\nDelegation Pitch\n\n76\n\n3514\n\nMay 5, 2026\n\nAtiselsts.eth Delegate Platform\n\nDelegation Pitch\n\n32\n\n4670\n\nJuly 9, 2026\n\nAvantgarde Finance Delegate Platform\n\nDelegation Pitch\n\n32\n\n1063\n\nNovember 27, 2025\n\n404 DAO Delegate Platform\n\nDelegation Pitch\n\n39\n\n3283\n\nJanuary 13, 2026","tokens":3481,"crawled_at":1791193398691}
+{"id":10232,"url":"https://docs.near.org/tools/sdk","domain":"docs.near.org","chapter":"layer1_layer2","title":"SDK Libraries - NEAR Docs","text":"The NEAR SDK for Rust (near-sdk-rs) is the official library for developing smart contracts. Rust provides the most mature tooling, best performance, and the strongest safety guarantees when handling real assets on-chain.\n\nThe best place to start learning is our QuickStart Guide.\n\nRust SDK\nRust SDK reference documentation.\n\n​\n\nSmart contracts on NEAR\n\nThis is how a smart contract written in Rust using the NEAR SDK looks like:\n\n#[near(contract_state)]\npub struct Contract {\ngreeting: String,\n}\n\nimpl Default for Contract {\nfn default() -> Self {\nSelf { greeting: \"Hello\".to_string(), }\n}\n}\n\n#[near]\nimpl Contract {\npub fn get_greeting(&self) -> String {\nself.greeting.clone()\n}\n\npub fn set_greeting(&mut self, greeting: String) {\nself.greeting = greeting;\n}\n}\n\n​\n\nCommunity SDKs\n\nSince NEAR contracts compile to WebAssembly, the community maintains SDKs for other languages. They are great for prototyping and learning, but are not covered in this documentation:\n\nJavaScript / TypeScript SDK (near-sdk-js)\n\nPython SDK (near-sdk-py)\n\nGo SDK (near-sdk-go)\n\n​\n\nReady to start developing?\n\nStart from our Smart Contract QuickStart Guide, and let it guide you through all our documentation on building smart contracts.\n​\n\nWant to see examples?\n\nWe have a section dedicated to tutorials and examples that will help you understand diverse use cases and how to implement them.\n​\n\nReference docs\n\nIf you need to find a specific function signature, or understand the SDK structs and classes, visit the Rust SDK reference.\nWas this page helpful?","tokens":384,"crawled_at":1791193401308}
+{"id":10233,"url":"https://a16zcrypto.com/posts/videos/optimal-flexible-consensus-and-its-application-to-ethereum","domain":"a16zcrypto.com","chapter":"research","title":"Optimal flexible consensus and its application to Ethereum - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nOptimal flexible consensus and its application to Ethereum\nJoachim Neu\n10.24.23\n\nTags & Share Tags\nconsensus\nEthereum\nresearch\nvideo\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nClassic BFT consensus protocols guarantee safety and liveness for all clients if fewer than one-third of replicas are faulty. But some clients may want to prioritize safety over liveness. Flexible consensus allows each client to opt for a higher safety resilience, albeit at the expense of reduced liveness resilience. Joachim Neu (Stanford) presents the first flexible consensus protocol that allows optimal safety–liveness tradeoffs for all clients simultaneously. The core technical ingredient is an additional round of voting and permanent locking done by the replicas, to sidestep a sub-optimal quorum-intersection-based constraint present in previous solutions. Joachim adapt the construction to the existing Ethereum protocol to derive optimal flexible confirmation rules that clients can adopt without requiring system-wide changes. This is possible because existing Ethereum protocol features can double as the extra voting and locking. He demonstrates an implementation using Ethereum’s consensus API. (Joint work with Srivatsan Sridhar, Lei Yang, and David Tse.)\n\nAbout the presenter\n\nJoachim is a PhD candidate at Stanford advised by David Tse. His current research focus is the science and engineering of Internet-scale consensus. Recent research projects include provable consensus security for next-generation Ethereum, and provable security and performance of proof-of-stake consensus under rate constraints and network-level attacks. He has been supported by Protocol Labs PhD Fellowship, Ethereum Foundation, Stanford Graduate Fellowship, and German Academic Scholarship Foundation.\n\nAbout a16z crypto research\n\na16z crypto research is a multidisciplinary lab that works closely with our portfolio companies and others toward solving the important problems in the space, and toward advancing the science and technology of the next generation of the internet.","tokens":547,"crawled_at":1791193403318}
+{"id":10234,"url":"https://gov.uniswap.org/t/consensus-check-staking-tokenomics/9019","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Consensus Check - Staking & Tokenomics - Consensus Check - Uniswap Governance","text":"Consensus Check - Staking & Tokenomics\n\nConsensus Check\n\nsommi\n\nDecember 1, 2020, 6:33am\n\n1\n\nMultiple Choice: Tick each Support of UNI Tokenomics\n\nStaking\n\nBuy-back and Burn\n\nOwn 25 UNI to access More features & Cheaper trading fees\n\nLoyalty Rewards (e.g. Rocket Boost to staking yield if you use the protocol frequently, or rewarded with time)\n\n0\nvoters\n\nWe have to stop thinking like a bunch of weak cowards. We are a tribe, and this is war.\n\nWe are long-term investors and UNI believers but if we don’t take this seriously then there will be no more rainbows here. Long-term investors get stronger by drinking the tears of short-term speculators. So we need to start rewarding long-term investors by getting serious.\n\nWe most certainly need to consider a UNI tokenomics program alongside the proposed buy-back program. We should welcome any sort of mechanism that supports price over time. Anybody who says otherwise is clearly a trojan horse from another community trying to steer us in the wrong way.\n\nI can’t say too much, but I know for a FACT that a certain “Rich famous Crypto Twitter personality” has supporters in here who on purpose, are making false misleading suggestions and start conversations to dampen the growth of UNI.\n\nSushi are taking risks because they are in second place. They want to take over Uniswap and they are fighting for it. They are not sitting there twiddling their thumbs about “legal issues” and cry baby garbage talk about upsetting the wrong people. Stop listening to these unproductive paper pushers. These are the same people who said Bitcoin was going to $0 in January 2019 because “the government will not let it go up”.\n\nNow… There is room for only 1 king so we need to start acting like it.\n\nWe are here for Crypto, but let’s not forget the most important fact… Satoshi already solved the “Digital Scarcity” problem. Stop acting like it’s a bad idea to support the Uniswap with scarcity tokenomics such as buyback & burn, as well as incentives to hold the UNI token for longer periods of time.\n\nClearly it was a mistake to leave the Protocol Fee Switch inactive for 6 months. This is way too long and a thorn in our side. Nobody is happy about that because the “competitors” are making moves EVERY other day. We have basically let the sheep out for the foxes.\n\nWe also need to stop wasting time replying to trojan horse actors who say “GuyZ, BuYBaCkS DoN’T HeLp, AnD BuRnInG DoEsN’T EiTheR!” in every single thread. It’s so obvious that these people are from an outside community and actively trying to take us down from with-in.\n\nAs a start, we should be implementing:\n\nStaking …Reward longer lock-up with higher yield.\n\nBuy-back and Burn …There is incentive for holding as the Unicorn is working for us 24/7.\n\nUNI hodler access …Own 25 UNI and you get access to cheaper fees and more trading features such as Stop Market, Limit Orders, Iceberg etc.)\n\nLoyalty Rewards …Instead of 6% yield, you get 7% staking yield if you have been using for a longer period of time.\n\nWe should also heavily consider giving Liquidity Providers a payment in the form of slightly higher yield on their Staked UNI Tokens as this will punish those who keep dumping their bags early, and it will reward long-term views.\n\nIt’s time to stop playing nice and start working seriously towards total Victory\n\n9 Likes\n\nFigu3\n\nDecember 1, 2020, 10:50am\n\n2\n\nHey, I’m not sure I agree with all of this…\n\nYes, Sushiswap is more aggressive, but UNI has a core team that is not anon and can be leveraged by regulators.\n\nTes, UNI is king, and its our job to keep it that way but it’s going to take time to think of a good plan.\n\nWhile I believe your propositions are interesting, they should be much more detailed for a consensus check. This is the last step before publishing a proposal and should be more fleshed out ! If you need any help, feel free to reach out.\n\nAlso, and that’s a personal opinion, delaying the treasury switch is a good thing because it helps us figure out the way we want to run things.\n\n7 Likes\n\nsinlee\n\nDecember 1, 2020, 11:27am\n\n3\n\nWe should act. Now that AC has acquired Sushi, his DEFI ships are being armed. If we do nothing, the crown will shift.\n\n1 Like\n\ngman211\n\nJanuary 5, 2021, 11:45pm\n\n4\n\nWell said, I was trying to push for exactly what you wrote in your comment. We seem to finally have done something right. I feel like I keep missing out and not informed on present changes. Since, I missed out on our last vote. Due to fees beings so high I am also hesitant to release any from my priv. Wallet.\n\nrobert9g\n\nJanuary 6, 2021, 12:38pm\n\n5\n\nI would like to point out that this poll does not follow the forum’s rules, namely you are required to include the option “Make no change” or its equivalent.\n\nSource:\n\nhttps://gov.uniswap.org/t/readme-how-to-create-a-consensus-check/7607\n\nThus, the results of this poll might better reflect the voice of the community had it included the required option.\n\nThe OP either was not aware of this rule, or he/she broke it deliberately.\n\n5 Likes\n\ndeffo\n\nJanuary 12, 2021, 7:47pm\n\n7\n\nI honstely think that buyback and distributing the tokens to stakers is better than buyback and burn.\n\n1 Like\n\nsr0x\n\nFebruary 4, 2021, 9:36pm\n\n8\n\nAgree with this. Inactive accounts and lost private keys that do not contribute to the community would slowly be diluted.\n\n2 Likes\n\nSteady\n\nFebruary 27, 2021, 8:04pm\n\n10\n\nI want to see staking and a portion of the fees distributed to holders. Burning Uni doesn’t seem good for long term supply and rewards people who aren’t involved in the community.\n\n1 Like\n\nGoobers007\n\nMay 4, 2021, 9:31pm\n\n11\n\nThat was very well said and I love your passion. Anyone that thinks there aren’t people on the inside trying to take UNI down is either lying to themselves or part of the problem. Why don’t we reward users of the protocol, something to offset there Ethereum fees. Not just from now but the past. People are very loyal to brands that treat them well or give them free shit basically. I know if I had a choice between an exchange that hooked me up and one that didn’t I know where I’m going. Just a thought. Anyways, i got so off topic. I loved what you had to say and it’s people like you that can make or brake this project…\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nUNI buyback from market using Uniswap 0.3% fees\n\nConsensus Check\n\n29\n\n7252\n\nFebruary 27, 2021\n\n[POLL] How Would We Structure a Fee Reward?\n\nRequests for Comment\n\n91\n\n10390\n\nApril 10, 2021\n\nBuyback & Burn is the winner\n\nRequests for Comment\n\n1\n\n3746\n\nJanuary 14, 2021\n\n[POLL] Should UNI Holders Be Rewarded?\n\nGovernance-Meta\n\n86\n\n11303\n\nMarch 7, 2021\n\nUni token rewards please read!\n\nRequests for Comment\n\n3\n\n3250\n\nOctober 12, 2020","tokens":1678,"crawled_at":1791193418654}
+{"id":10235,"url":"https://docs.near.org/tools/contracts-list","domain":"docs.near.org","chapter":"layer1_layer2","title":"Reference Contracts - NEAR Docs","text":"List of contracts of various projects deployed on NEAR. This list is not exhaustive and is meant to be a reference for developers and users\n\nFind more:\nNEAR Catalog - A catalog of NEAR projects\n\nNEAR Audit Database - List of Public Audits in the NEAR Ecosystem\n\n​\n\nContracts List\n\nContractProjectTagsDescription\nBurrow.finance (public archive)\nRhea finance\nDeFi\nLending platform\n\nref-exchange\nRhea finance\nDeFi\nDEX Contract\n\nref-farming\nRhea finance\nDeFi\nDEX LP Farming\n\nMeta Token\nMetapool\nFT\nFT contract\n\nmetapool\nMetapool\nstaking\nLiquid staking\n\ndonation\nPotLock\nFT, donation\nDonating FT to any contract\n\npot\nPotLock\ndonation\nQF Funding round\n\npot_factory\nPotLock\nfactory, donation\nFactory contract for QF Funding Rounds\n\nregistry\nPotLock\ndonation, misc\nRegistry for QF funding rounds\n\nsybil\nPotLock\nmisc\nRegistry for sybil resistance providers\n\nShardDog-NFT-Protocol\nShardDog\nNFT\nNFT contract managing multiple NFT collections\n\nNFT-Minting-withFT\nShardDog\nNFT, FT\nNFT contract supports minting with FT tokens, royalties, payment distribution, premint functionality.\n\ncontest-contract\nShardDog\nraffle\nWeighted raffle system.\n\ncore\nNEAR Intents\ncross-chain, DeFi\nProtocol for multichain financial products\n\ncontest-contract\nRace of Sloths\nraffle\nWeighted raffle contract\n\ncontract\nRace of Sloths\nmisc\nScoreboard including streaks\n\ncontract-mvp\nTemplar Protocol\nDeFi\nPermissionless cypher lending\n\nindex-fund-contract\nTemplar Protocol\nDeFi\nIndex fund contract\n\nlinear\nLinear\nstaking\nLiquid staking\n\nhodl-lockup\nSweat Economy\nFT, lockup\nFT lockup contract\n\nsweat-jar\nSweat Economy\nFT, staking\nFT staking contract\n\nsweat-claim\nSweat Economy\nFT\nFT managing contract\n\nsweat-booster\nSweat Economy\nFT, NFT\nNFT vouchers for FT\n\nmultisig\nSweat Economy\nmultisig\nMultisig Contract\n\nsweat-burn\nSweat Economy\nFT\nFT burning\n\nmb-factory-v2\nMintBase\nfactory, NFT\nNFT factory contract\n\nmb-interop-market\nMintBase\nNFT\nNFT Market contract\n\nmb-nft-v2\nMintBase\nNFT\nNFT contract\n\nneardevhub-contract\nNEAR DevHub\nmisc\nCommunity managing platform\n\nlockup-factory\nCore-Contracts\nfactory, lockup\nFactory contract deploying lockup contracts\n\nlockup\nCore-Contracts\nlockup\nLocks and holds an owner’s tokens for a lockup period\n\nmultisig-factory\nCore-Contracts\nfactory\nFactory contract for multisig\n\nmultisig\nCore-Contracts\nmultisig\nmultisig\n\nmultisig2\nCore-Contracts\nmultisig\nmultisig\n\nstaking-pool-factory\nCore-Contracts\nfactory, staking-pool, validator\nStaking Pool factory contract\n\nstaking-pool\nCore-Contracts\nstaking-pool, validator\nStaking pool contract\n\nstate-manipulation\nCore-Contracts\nstate-manipulation\nContracts state-manipulation\n\nvoting\nCore-Contracts\nvalidator\nValidator Voting contract\n\nw-near\nCore-Contracts\nFT\nFT contract that wraps native NEAR\n\nwhitelist\nCore-Contracts\nwhitelist, staking-pool\nWhitelist contract for staking pools\n\nstaking-factory\npool.near\nfactory, staking-pool, validator\nFactory contract deployed as pool.near that creates staking farm contracts\n\nstaking-farm\n*.pool.near\nstaking-pool, validator\nStaking farm contract deployed under *.pool.near accounts\n\nWas this page helpful?","tokens":773,"crawled_at":1791193419549}
+{"id":10236,"url":"https://a16zcrypto.com/posts/article/secure-efficient-zkvms-progress","domain":"a16zcrypto.com","chapter":"research","title":"The path to secure and efficient zkVMs: How to track progress - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nThe path to secure and efficient zkVMs: How to track progress\nJustin Thaler\n03.11.25\n\nTags & Share Tags\nresearch\nSNARKs\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nzkVMs (zero knowledge virtual machines) promise to “democratize SNARKs” by allowing anyone, even those with no specialized SNARK expertise, to prove that they have correctly run any program on a given input (or witness). Their core strength lies in the developer experience, but currently they present enormous challenges in both security and performance. For zkVMs to fulfill their promise, designers will have to overcome these challenges. In this post, I lay out the likely stages for their development, the completion of which will take several years. Don’t let anyone tell you differently.\n\nThe challenges\n\nOn the security side, zkVMs are highly complex software projects still riddled with bugs. On the performance side, proving correct execution of a program can be hundreds of thousands of times slower than running it natively, making real-world deployment for most applications untenable right now.\n\nDespite these realities, much of the blockchain industry portrays zkVMs as ready for immediate deployment. Indeed, some projects already pay significant computation costs to generate proofs of onchain activity. Because of the bugs, this is merely an expensive way of pretending a system is secured by a SNARK when it is actually either secured by permissioning, or far worse, vulnerable to attack.\n\nThe truth is, we are still years away from meeting even the most basic goals for a secure and performant zkVM. This post proposes a series of staged, concrete goals to track our collective progress — goals that cut through hype and help the community focus on genuine advancements.\n\nStages of security\n\nBackground\n\nSNARK-based zkVMs typically include two main components:\n\nPolynomial Interactive Oracle Proof (PIOP): The interactive proof framework used to prove statements about polynomials (or constraints derived from them).\n\nPolynomial Commitment Scheme (PCS): Ensures that the prover cannot lie about polynomial evaluations without being detected.\n\nzkVMs essentially encode valid execution traces as constraint systems — broadly meaning that they enforce correct register and memory usage by a virtual machine — and then apply a SNARK to prove these constraints are satisfied.\n\nThe only path to ensuring that systems as complicated as zkVMs are free of bugs is formal verification. Below is a breakdown of security stages. Stage 1 focuses entirely on correct protocols while Stages 2 and 3 focus on correct implementations.\n\nSecurity stage 1: Correct protocols\n\nStage 1a\n\nA formally verified proof of soundness for the PIOP.\n\nStage 1b\n\nA formally verified proof that the PCS is binding under some cryptographic assumption or an idealized model.\n\nStage 1c\n\nIf using Fiat-Shamir, a formally verified proof that the succinct argument obtained by combining the PIOP and the PCS is secure in the random oracle model (augmented with other cryptographic assumptions as appropriate).\n\nStage 1d\n\nA formally verified proof that the constraint system to which the PIOP is applied is equivalent to the VM’s semantics.\n\nStage 1e\n\nA comprehensive “gluing together” of all these pieces into a single, formally verified proof of a secure SNARK for running any program specified by the VM’s bytecode. If the protocol intends to achieve zero knowledge, this property must also be formally verified, ensuring that no sensitive information about the witness is revealed.\n\nRecursion Caveat: If the zkVM uses recursion, every PIOP, commitment scheme, and constraint system involved anywhere in that recursion must be verified to consider a sub-stage complete.\n\nSecurity stage 2: Correct verifier implementation\n\nA formally verified proof that an actual implementation of the zkVM verifier (in Rust, Solidity, etc.) matches the protocol verified in Stage 1. Achieving this ensures the implemented protocol is sound (rather than merely the design on paper, or an inefficient specification written in, say, Lean).\n\nThe reason Stage 2 focuses on the verifier implementation alone (and not the prover) is two fold. First, getting the verifier right is already sufficient for soundness (i.e., ensuring that the verifier cannot be convinced that any false statement is in fact true). Second, zkVM verifier implementations are over an order of magnitude simpler than prover implementations.\n\nSecurity stage 3: Correct prover implementation\n\nA formally verified proof that an actual implementation of the zkVM prover correctly generates proofs for the proof system verified in Stages 1 and 2. This ensures completeness — that is, any system using the zkVM will not get “stuck” with a statement that cannot be proven. If the prover intends to achieve zero knowledge, this property must be formally verified.\n\nProjected timelines\n\nStage 1 Progress: We can expect incremental achievements over the next year (e.g., ZKLib is one such effort). But no zkVM is likely to fully meet Stage 1 for at least two years.\n\nStages 2 and 3: These can advance in parallel with some aspects of Stage 1. For example, some teams have shown that an implementation of the Plonk verifier matches the protocol in a paper (although the paper’s protocol itself might not be fully verified). Nevertheless, I do not expect any zkVM to reach Stage 3 in fewer than four years — and likely longer.\n\nKey caveats: Fiat-Shamir security and verified bytecode\n\nOne major complication is that there are open research questions surrounding the security of the Fiat-Shamir transformation. All three stages treat Fiat-Shamir and random oracles as if their security is unassailable, but in reality the entire paradigm may turn out to have vulnerabilities. This is due to the difference between the random oracle idealization and actual hash functions used in practice. In the worst case, a system that has reached Stage 2 could later be found completely insecure due to Fiat-Shamir issues. This is cause for serious concern and continued research. We may need to modify the transformation itself to better guard against such vulnerabilities.\n\nSystems without recursion are on somewhat firmer theoretical ground because certain known attacks involve circuits reminiscent of those used in recursive proofs. But the risk remains a fundamental open question.\n\nAnother caveat is that proving you’ve correctly run a computer program (specified via bytecode) has limited value if the bytecode itself is flawed. Consequently, the utility of zkVMs depends heavily on methods for generating formally verified bytecode — an enormous challenge that falls outside the scope of this post.\n\nOn post-quantum security\n\nOver at least the next five years (and likely longer), quantum computers do not pose a serious threat, whereas bugs are an existential risk. So the primary focus now should be meeting the security and performance stages in this post. If we can meet them faster with SNARKs that are not quantum-secure then we should do so. And we should use those until either post-quantum SNARKs catch up, or there is a serious concern that a cryptographically relevant quantum computer is imminent.\n\nConcrete security levels\n\n100 bits of classical security is the absolute bare minimum anyone should deploy a SNARK securing anything of value (there are still some deployments that do not meet this low bar). Even this should not be acceptable: standard cryptographic practice is to use 128 bits of security and up. If SNARK performance were where it truly needs to be, we wouldn’t be skimping on security to eke out incremental performance gains.\n\nStages of performance\n\nThe Current Situation\n\nCurrently, zkVM provers incur overhead factors approaching one million times the cost of native execution. If a program takes X cycles to run, proving correct execution will cost on the order of X times 1 million CPU cycles. This was the case roughly one year ago, and it remains the case today (despite misconceptions to the contrary).\n\nPopular narratives often frame this overhead in ways that sound acceptable. For example, you might hear:\n\n“Generating proofs for all of Ethereum mainnet costs under a million dollars per year.”\n\n“We nearly have real-time proof generation of Ethereum blocks using a cluster of dozens of GPUs.”\n\n“Our latest zkVM is 1000× faster than its predecessor.”\n\nWhile technically accurate, these claims can be misleading without proper context. For instance:\n\n1000× faster than an older zkVM still leaves it very slow in absolute terms. This is much more a statement of how bad things were than how good things are.\n\nThere are already proposals to 10x the amount of computation processed by Ethereum mainnet. This will render current zkVM performance far too slow.\n\nWhat people are calling “nearly real-time proving of Ethereum blocks” is still much slower than what many blockchain applications demand (e.g., Optimism has a block time of 2s, substantially faster than Ethereum’s 12s block time).\n\n“Dozens of GPUs running at all times, without fail” falls short of acceptable liveness guarantees.\n\nThese prover times are often reported for proof sizes that are too large for many applications (e.g., over 1 MB).\n\nUnder a million dollars per year to prove all activity on Ethereum mainnet reflects the fact that Ethereum full nodes perform only about $25 worth of compute per year.\n\nFor applications beyond blockchains, such overheads are plainly too high. No amount of parallelization or engineering can offset such a massive overhead.\n\nWe should aim for slowdowns no worse than 100,000× relative to native execution as a basic baseline — and even that is only the first step. True mainstream adoption probably requires overheads close to 10,000× or lower.\n\nMeasuring performance\n\nSNARK performance has three primary components:\n\nIntrinsic efficiency of the underlying proof system.\n\nApplication-specific optimizations (e.g., pre-compiles).\n\nEngineering and hardware speedups (e.g., GPUs, FPGAs, or multi-core CPUs).\n\nWhile (2) and (3) are vital for real-world deployments, they’re generally available to any proof system so they don’t necessarily reflect progress on fundamental overheads. For instance, adding GPU acceleration plus pre-compiles to a zkEVM can easily yield a 50× speedup over a purely CPU-based, no-precompile approach — enough to make an intrinsically less efficient system appear superior to one that simply hasn’t received the same polishing.\n\nConsequently, this post focuses on measuring how well a SNARK performs absent specialized hardware and pre-compiles. It’s a departure from current benchmarking approaches, which often lump all three factors into a single “headline number.” This is akin to judging diamonds by how many hours they’ve been polished rather than by their innate clarity.\n\nThe goal here is to isolate the intrinsic overhead of general-purpose proof systems — minimizing barriers to entry for underexplored techniques and allowing the community to cut through confounding factors to focus on true progress in proof-system design.\n\nPerformance stages\n\nBelow are my proposed milestones for performance, organized into five stages. First, we need to slash prover overhead on CPUs by multiple orders of magnitude. Only then should the focus turn to further reductions via hardware. Memory usage must improve as well.\n\nIn all of the stages below, developers should not have to tailor their code to the zkVM setting to achieve the necessary performance. Developer experience is a primary benefit of zkVMs. Sacrificing DevEx to meet performance benchmarks defeats the point of both the benchmark and the zkVM itself.\n\nThese metrics focus on prover costs. However, any prover metric can be met trivially if one allows unbounded verifier costs (i.e., no upper limit on proof size or verification time). Consequently, for a system to qualify for the stages described, it is crucial to specify maximum values for both proof size and verification time.\n\nStage 1 Requirements: “Reasonably non-trivial verification costs”\n\nProof size: The proof must be smaller than the witness.\n\nVerification time: Verifying the proof must be no slower than running the program natively (i.e., executing the computation without a proof of correctness).\n\nThese are bare minimum succinctness requirements. They ensure that proof sizes and verification times are not worse than the trivial approach of sending the witness to the verifier and having the verifier directly check it for correctness.\n\nStage 2 and beyond\n\nMaximum proof size: 256 KB\n\nMaximum verification time: 16 ms\n\nThese cutoffs are intentionally generous to accommodate novel, fast-prover techniques that may come with higher verification costs. At the same time, they exclude proofs so expensive that few projects would be willing to include them on a blockchain.\n\nSpeed stage 1\n\nSingle-threaded proving must be at most one hundred thousand times slower than native execution, measured across a range of applications (beyond just proving Ethereum blocks), without relying on pre-compiles.\n\nConcretely, think of a RISC-V process running at roughly 3 billion cycles per second on a modern laptop. Achieving Stage 1 means you can prove about 30,000 RISC-V cycles per second (single-threaded) on that same laptop.\n\nVerifier costs must be “reasonably non-trivial” as defined earlier.\n\nSpeed stage 2\n\nSingle-threaded proving must be at most ten thousand times slower than native execution.\n\nAlternatively, because some promising SNARK approaches (especially those over binary fields) are hindered by current CPUs and GPUs, you can reach this stage using FPGAs (or even ASICs) by comparing:\n\nThe number of RISC-V cores an FPGA can emulate at native speed, vs.\n\nThe number of FPGAs required to emulate and prove RISC-V execution in (near) real-time.\n\nIf the latter number is at most a factor of 10,000 more than the former, you qualify for Stage 2.\n\nProof size must be at most 256 KB and verifier time at most 16 ms on standard CPUs.\n\nSpeed stage 3\n\nIn addition to achieving Speed Stage 2, also achieve a proving overhead of under 1000× (for a wide range of applications) using automatically synthesized and formally verified pre-compiles. Essentially, dynamically customize an instruction set for each program to accelerate proving, but do so in an easy-to-use and formally verified manner.\n\n(For a deeper discussion of why pre-compiles are a double-edged sword — and why “hand-rolled” pre-compiles are not a sustainable approach — see the next section.)\n\nMemory stage 1\n\nStage 1 speed is achieved with less than 2 GB of memory required for the prover (while also achieving zero knowledge).\n\nThis is critical for many mobile devices or browsers and thus opens up countless client-side zkVM use cases. Client-side proving matters because our phones are our constant link to the real world: they track our locations, credentials, and more. If a proof requires more than 1-2 GB of memory to produce, it’s simply too much for most mobile devices today. Hitting that 2 GB threshold opens the door to real-time, on-device SNARK proofs for everything from privacy-preserving location checks to portable, verifiable credentials.\n\nTwo clarifications are in order:\n\nThe 2 GB space bound should hold even for large statements (those requiring many trillions of CPU cycles to run natively). A proof system that achieves the space bound only for small statements lacks broad applicability.\n\nIt is easy to keep the prover’s space below 2 GB of memory if the prover is very slow. So to make Memory Stage 1 non-trivial, I am requiring that Speed Stage 1 be met within the 2 GB space bound.\n\nMemory stage 2\n\nStage 1 speed is achieved with less than 200 MB of memory usage (10x better than Memory Stage 1).\n\nWhy push below 2 GB? Consider a non-blockchain example: Every time you visit a website via HTTPS, you download certificates for authentication and encryption. Instead, websites could send zk-proofs of possession of these certificates. Large sites may issue millions of these proofs per second. If each proof requires 2 GB of memory to generate, you’re talking about petabytes of RAM in total. Pushing memory usage further down is vital for non-blockchain deployments.\n\nPre-compiles: The last mile or a crutch?\n\nIn zkVM design, a pre-compile refers to a special-purpose SNARK (or constraint system) tailored to specific functions — such as Keccak/SHA hashing or elliptic-curve group operations for digital signatures. Within Ethereum — where most of the heavy lifting involves Merkle hashing and signature checks — a few hand-crafted pre-compiles can reduce prover overhead. But relying on them as a crutch will not get SNARKs where they need to go.\n\nWhy pre-compiles are a crutch\n\nStill too slow for most applications (both within and outside blockchains): Even with hashing and signature pre-compiles, current zkVMs remain too slow—both within and beyond blockchain contexts—because of deep inefficiencies in the core proof system.\n\nSecurity failures: Hand-written pre-compiles that are not formally verified are almost certainly riddled with bugs, risking catastrophic security failures.\n\nSuboptimal developer experience: In most zkVMs today, adding new pre-compiles means hand-authoring constraint systems for every function — essentially returning to a 1960s-style workflow. Even when using existing pre-compiles, developers must refactor code to call each one. We should be optimizing for security and developer experience, not sacrificing both to chase incremental performance gains. Doing so merely proves that performance isn’t where it needs to be.\n\nConfounding benchmarks: Benchmarking on workloads dominated by a handful of repetitive cryptographic operations risks selecting for projects that have simply spent the most time optimizing hand-written constraint systems for that application. This is not the best path to advancing the science of SNARK design.\n\nI/O Overheads and no RAM: Although pre-compiles improve performance for heavy cryptographic tasks, they may not deliver meaningful speedups for more diverse workloads because they incur major overhead for passing inputs/outputs, and they cannot use RAM.\n\nEven within blockchain contexts, as soon as you move beyond a monolithic L1 like Ethereum — say, you want to build a slew of cross-chain bridges — you’re confronted with different hash functions and signature schemes. Throwing precompile after precompile at the problem doesn’t scale and introduces massive security risks.\n\nFor all of these reasons, our priority should be making the underlying zkVM more efficient. Whatever techniques produce the best zkVMs will also produce the best pre-compiles.\n\nI do believe pre-compiles will remain critical in the long run, but only once they’re automatically synthesized and formally verified. That way, we can maintain the developer-experience benefits of a zkVM while avoiding catastrophic security risks. This perspective is reflected in Speed Stage 3.\n\nProjected timelines\n\nI expect a small number of zkVMs to achieve Speed Stage 1 and Memory Stage 1 later this year. I think we achieve Speed Stage 2 in the next two years as well, but it’s not yet clear we can get quite there without some new ideas that aren’t in the research literature yet.\n\nI expect that the remaining stages (Speed Stage 3 and Memory Stage 2) will take several years to meet.\n\nAlthough I have separately identified stages for zkVM security and performance in this post, these aspects of zkVMs are not entirely independent. As more vulnerabilities are discovered in zkVMs, I expect that some will be fixable only with a substantial loss in performance. Until a zkVM reaches Security Stage 2, performance results should be viewed as tentative.\n\n***\n\nzkVMs hold immense promise for making zero-knowledge proofs truly universal, but they remain in their infancy — rife with security challenges and debilitating performance overheads. Hype and marketing spin make it difficult to measure genuine progress. By articulating clear security and performance milestones, I hope to provide a roadmap that cuts through the noise. We’ll get there, but it will take time and sustained effort in both research and engineering.\n\n***\n\nJustin Thaler is Research Partner at a16z and an Associate Professor in the Department of Computer Science at Georgetown University. His research interests include verifiable computing, complexity theory, and algorithms for massive data sets.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nThe content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":5765,"crawled_at":1791193422039}
+{"id":10237,"url":"https://www.metaplex.com/docs/smart-contracts/token-metadata/escrow","domain":"www.metaplex.com","chapter":"docs","title":"NFT Escrow | Token Metadata","text":"Token Metadata is a legacy program. It remains supported, but is not recommended for new projects. Use Core instead.\n\nThis extension of the Token Metadata contract was created as a new feature primitive that could optionally be added to all NFTs. At its core it is simply an escrow account attached to an NFT, enabling NFTs to become owners of other tokens.\nAside from the requisite security and ownership checks necessary, the functionality this feature affords has been left generic enough to allow users to implement whatever they desire on top of the composability of the token and its escrow account.\nTypes of Escrow Accounts\nIt is currently possible to create two different types of escrow accounts on an NFT: A Token Owned Escrow (TOE) used for ownership and a Creator Owned Escrow (COE) used for associations. The existence of both types of escrow accounts is not mutually exclusive.\nToken Owned Escrow\nA Token Owned Escrow account, or TOE, is an escrow account attached to the NFT that is managed by the holder of the NFT. Transferring a token out of this escrow account is only allowable by the NFT's holder and the permissions follow the NFT as it is transferred between wallets.\nThis means Alice can add a token to a TOE on her NFT, then sell her NFT to Bob. Bob would then be the only one allowed to transfer that token out of the TOE.\nDue to the holder-based permissions, it is only possible to have one TOE on an NFT. A TOE follows traditional wallet action flow where anyone can transfer a token into the escrow account but the holder is the only one who can transfer the token out.\nCreator Owned Escrow\nA Creator Owned Escrow, or COE, is an escrow account attached to the NFT that is managed by a specified creator. This escrow account allows creators to make associations between tokens that they themselves can manage, regardless of sales, transfers, and holders of the base NFT.\nAn example use case for this is Metaverse avatars. Rather than storing avatars on a Web2 server, the Metaverse team could mint the avatar as an NFT, then put it in a COE (that the Metaverse team manages) attached to the corresponding base NFT. Because usage of the COE is locked to the creator of the COE, a holder would be unable to transfer the avatar out of the escrow account and break the association.\nA Creator Owned Escrow is seeded with the creator public key and therefore there is no limit to the number of COEs that can be attached to an NFT. This allows many associations to be built across many projects. A COE follows traditional wallet action flow where anyone can transfer a token into the escrow account but the creator of the escrow is the only one who can transfer the token out.","tokens":675,"crawled_at":1791193448577}
+{"id":10238,"url":"https://gov.uniswap.org/t/rfc-a-mechanism-to-use-the-uni-treasury-to-grow-and-defend-uniswap/17015","domain":"gov.uniswap.org","chapter":"governance_daos","title":"[RFC] A mechanism to use the UNI treasury to grow and defend Uniswap - Requests for Comment - Uniswap Governance","text":"[RFC] A mechanism to use the UNI treasury to grow and defend Uniswap\n\nRequests for Comment\n\nfirstprinciples\n\nJune 26, 2022, 5:49pm\n\n1\n\nWe believe that, just as in traditional companies, capital and ‘equity’ should be used for growth, future value creation and moat building.\n\nThis post is a proposal for a mechanism we think would help Uniswap allocate, in size, towards that.\n\nCurrent state of the treasury:\n\nOn the one hand, Uniswap currently has the largest treasury in DeFi in dollar terms (per: OpenOrgs.info).\n\nOn the other, its ~100% in UNI tokens. Some vested, some unvested:\n\n1358×532 40 KB\n\nAs @Hasu outlines in his A New Mental Model for DeFi Treasuries, native tokens in DAO treasuries can be looked at as “the crypto-equivalent of authorized but unissued shares”.\n\nFurthermore, a sale of just 1% of the vested UNI tokens in the treasury for USDC would result in 50% price slippage on 1inch. This means that this capital is effectively unusable for any relevantly-sized CaPex or OpEx.\n\nOpportunity:\n\nFrom the above, our view is that Uniswap’s treasury is potentially an extremely valuable asset for the protocol and DAO, but that current use cases don’t unlock a fraction this potential value.\n\nThe Unigrants program is incredible, but there ought to be other and larger scale allocation opportunities for the treasury.\n\nGoals:\n\nWe’d like to:\n\nHave a more diversified treasury.\n\nReducing the treasury’s exposure to just pure UNI and ensuring Uniswap thrives under different market conditions.\n\nUse treasury funds specifically to grow Uniswap.\n\nThere can be disagreement about what the best KPIs for Uniswap’s growth ought to be, but volume as the core one and TVL, liquidity and users as others seems directionally correct.\n\nUse UNI to deepen Uniswap’s moats and build durable defensibility.\n\nCompetitive advantages that can’t be forked or copied and that contribute to keeping Uniswap the leading DEX.\n\nWe’ll look at this proposal through the lens of how it may impact all three.\n\nIdea:\n\nHigh-level:\n\nUniswap provides $x value in UNI tokens from the treasury and a partner protocol/project/DAO provides $x value in their governance (or otherwise) token to LP in an uniswap pool between the two tokens.\n\nThe resulting LP shares are split proportionally between the two treasuries (uniswap and the partner’s).\n\nProcess:\n\nThe way to determine these and other parameters would be via standard governance.\n\nAn interested protocol/project/DAO/community would publish a proposal to uniswap governance following a standard, to be created, template (similar to templates for asset listings on Aave, for example). They’d refer what the value of x should be and why, their metrics, their token’s value (governance or otherswise) or value accrual, why aligning their community with uniswap’s would be valuable, amongst other relevant information for a decision.\n\nAfter discussion here in the forum, it’d move to a governance vote and be acted upon if passed.\n\nWe’d always want these “partner” projects to be high quality or high potential, and that would be assured by UNI governance deciding individually on each.\n\nPro case:\n\nWe believe that, over time, this allocation mechanism would bring material diversification, growth and moats to Uniswap – the three goals stated above.\n\nTreasury Diversification\n\nOver time, the treasury becomes more diversified into other high quality assets, in the form of XYZ-UNI LP positions.\n\n1.1. In particular, this is a way to diversify the treasury without ever directly selling UNI (which, like seen above, wouldn’t even be possible in size). No immediate/direct selling pressure would be put on UNI, contrary to most anternative diversification methods.\n\n1.2. Not only does this diversification mechanism not put selling pressure on UNI, it in fact increases UNI’s liquidity (potentially by many multiples). This has additional benefits such as making UNI a better/more sought after collateral asset across DeFi as well as opening up more ways to employ treasury funds in the future (due to liquidity for bigger size).\n\nCapital efficient and durable expansion of TVL\n\nFor every dollar in UNI invested by the treasury, this “joint LP mechanism” would add two dollars of TVL to Uniswap.\n\nMoreover, this liquidity provision is neither from mercenary capital nor from short-term LP profit maximizing agents. It’s rather from DAOs committed to hold the LP shares long-term.\n\nAs such, this mechanism should lead to sizeable and predictably permanent TVL expansion.\n\n2.1. Alongside point 1., this creates an unforkable moat for Uniswap in the form of protocol owned liquidity, but in a much more sustainable way than previous attempts at POL – like bonding (there is no dilution nor induced selling pressure in our mechanism).\n\nIncentive Alignment\n\nAs discussed, partners that get approved for this joint LP deal will be approved by UNI governance and, as such, should always be high quality or high potential protocols/projects/DAOs.\n\nAfter entering this “exchange” with Uniswap, their treasuries will be positively exposed to UNI, financially aligning their communities and teams with Uniswap’s long-term success.\n\nFrom this, we expect the mechanism to create, over time, a bigger and bigger network of top DeFi/web3 projects that are rationally incentivized to want Uniswap to prosper.\n\nWe think this can constitute yet another unforkable moat and contribute to keeping Uniswap the leading DEX.\n\nDemand\n\nMany if not most other protocols/projects/DAOs face the same challenge of having most of their treasuries’ value in their own governance token (just look at openorgs.info or hasu’s article).\n\nThis joint LP token exchange presents a new possibility for them to diversify their treasury into another high quality asset without generating selling pressure on their token (which would happen in market selling). As an additional benefit, they would also get the reverse incentive alignment pointed out in 3.\n\nAs such, we expect strong and sustainable demand from interested partners.\n\nUNI as a part of Uniswap’s product\n\nThe MKR and AAVE tokens play a role in Maker and Aave’s products and directly add value to them. Altough in different ways, in both cases these governance tokens’s value is used to cover/insure bad debt the protocols may acumulate in extreme scenarios (further reading: maker, aave).\n\nFor both, their governance tokens – as assets – make the protocols better. In their case, being debt protocols, ‘better’ here means safer for depositors. This is another possible moat in DeFi (see Multicoin’s Protocols Don’t Capture Value, DAOs Manage Risk).\n\nCurrently, UNI as an asset doesn’t directly contribute to Uniswap’s product – the DEX – in any analogous way.\n\nThe mechanism outlined in this proposal would make UNI a very relevant pair in Uniswap pools and hence an unforkable value-add to the protocol (adding liquidity, volume and TVL).\n\nWe think that, over time, UNI could become the third or fourth most prevalent trading pair, after ETH, BTC and stables.\n\nConsiderations:\n\nThe obvious main aspect this proposal leaves out is implementation of such a mechanism in v3.\n\nIt is quite straightforward to do these token swaps via LP with uniswap v2 positions (no upfront decision on liquidity range, no maintenance, fungible LP shares, very clean process overall). The same isn’t true if done in uni v3 (which could be more capital efficient but much more complex to manage).\n\nWe don’t have a strong view either way here. There are pros and cons. As such, we’d love to see discussion around this point if the uniswap community finds the overall proposal to make sense.\n\nFinally, this is a Request for Comments, not a proposal yet. We’d love to get all questions, feedback and improvement ideas from the community.\n\nWe’re also open to providing more data, run simulations, and present models on this mechanism, if you think it’d be helpful.\n\n5 Likes\n\nrfritsch\n\nJune 29, 2022, 9:25am\n\n2\n\nI very much appreciate suggestions to diversify the treasury and would like to share my opinion on this one:\n\nFor me, a protocol treasury should be a reserve to support development of the protocol (and the surrounding ecosystem), specially during difficult times (in which the protocol’s token may have a very low value).\n\nI would mentally split the suggested plan in two steps:\n\nSwap UNI tokens of value v from the treasury for “other protocol” token of value v.\n\nUse two assets in the treasury to provide liquidity in an AMM pool.\n\nI don’t think either of the two steps help to make the treasury a safer reserve:\n\nReplacing UNI tokens by “other protocol” tokens doesn’t necessarily make the treasury any less volatile. The treasury should probably hold mostly stablecoins (and at most some ETH or similar assets).\n\nProviding liquidity with treasury assets introduces extra risks and operational complexity. I don’t think liquidity provision is the purpose of a treasury.\n\nBrook_CIAN\n\nJune 30, 2022, 8:28am\n\n3\n\nConclusion: Reject\n\nRationale: The increased pool with this form of exchange does not hold/influence the pricing power of the tokens, but actually just increases the arbitrage space. This is of very limited help to the UNI ecosystem\n\n1 Like\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nUniswap Treasury Report\n\nGovernance-Meta\n\n6\n\n3326\n\nFebruary 20, 2025\n\nUniswap Treasury Working Group (UTWG) Application\n\nGovernance-Meta\n\n15\n\n4305\n\nApril 20, 2024\n\nMobilizing the Uniswap Treasury\n\nRequests for Comment\n\n27\n\n6238\n\nJuly 20, 2024\n\nUniswap Treasury Working Group (UTWG) Interim Update\n\nGovernance-Meta\n\n9\n\n761\n\nOctober 9, 2024\n\nSwap UNI for ETH and wBTC and provide liquidity\n\nConsensus Check\n\n8\n\n4124\n\nMay 16, 2021","tokens":2417,"crawled_at":1791193436498}
+{"id":10239,"url":"https://docs.near.org/tools/clear-state","domain":"docs.near.org","chapter":"layer1_layer2","title":"State Cleaner - NEAR Docs","text":"State Cleaner is an extension for NEAR CLI that wipes a contract account’s on-chain state without deleting the account, so you can redeploy a fresh contract or free the storage staked NEAR.\n​\n\nHow it works\n\nUnder the hood, it deploys a small cleanup contract to the target account and, in a single transaction, calls its clean method with every key in the account’s state. The cleanup contract is left in place — it is not removed — until you deploy a new contract over it.\n\nTo learn more, check out the source code for both the State Cleaner tool and the cleanup contract.\n\n​\n\nHow to use\n\n1\n\nInstall NEAR CLI\nThe State Cleaner is invoked through NEAR CLI, so you need it installed first. If you do not already have it installed, visit the NEAR CLI page.\n\n2\n\nInstall the State Cleaner extension\nInstall it straight from the GitHub repository:\n\ncargo install --locked --git https://github.com/near-examples/near-clear-state near-clear-state\n\nRequires a Rust toolchain ≥ 1.88.\n\n3\n\nMake sure the extension is on your PATH\nConfirm it’s picked up with:\n\nnear clear-state --help\n\n4\n\nRun the command\nRun the extension in interactive mode and follow the prompts:\n\nnear clear-state\n\nOr pass everything in one go:\n\nexport CONTRACT_ID=contract.testnet\nnear clear-state $CONTRACT_ID network-config testnet sign-with-keychain send\n\n5\n\nUse an RPC with a larger view-state cap\nIf the account’s state is large, you may hit:\n\nAccount state is too large for this RPC's view_state cap\n\nMost public RPCs cap view_state responses (around 50 KB). Point NEAR CLI at an RPC with a higher cap:\n\nnear config edit-connection testnet\n\nSet the rpc_url value to a higher-capacity provider, then re-run the command. Intear’s RPCs work well:\nTestnet: https://testnet-rpc.intea.rs\n\nMainnet: https://rpc.intea.rs\n\nYou can also update it without the prompts:\n\nnear config edit-connection testnet --key rpc_url --value https://testnet-rpc.intea.rs\n\n6\n\n(Optional) Verify the bundled wasm\nThe wasm embedded in the extension isn’t built here — it’s NEAR’s prebuilt state-manipulation cleanup contract, vendored from near/core-contracts. The extension pins a specific upstream commit, recorded in extension/wasm/state_cleanup.wasm.provenance.To verify that the wasm in the tool matches the wasm from core-contracts, clone the tool and run the verify script. It re-downloads the upstream wasm at the pinned commit and confirms the bundled bytes match:\n\ngit clone https://github.com/near-examples/near-clear-state.git\ncd near-clear-state\n./scripts/verify-wasm.sh\n\nWas this page helpful?","tokens":636,"crawled_at":1791193438254}
+{"id":10240,"url":"https://gov.uniswap.org/t/unification-proposal/25881","domain":"gov.uniswap.org","chapter":"governance_daos","title":"UNIfication Proposal - Requests for Comment - Uniswap Governance","text":"UNIfication Proposal\n\nRequests for Comment\n\nhaydenadams\n\nNovember 10, 2025, 8:55pm\n\n1\n\nUNIfication Blog Image1920×1440 562 KB\n\nUpdate 12/18:\n\nThis proposal was posted onchain December 18th, 2025 and will be live for voting on December 19th, 2025. You can access the vote here.\n\nUNIfication\n\nHayden Adams, Ken Ng, Devin Walsh\n\nToday, Uniswap Labs and the Uniswap Foundation are excited to make a joint governance proposal that turns on protocol fees and aligns incentives across the Uniswap ecosystem, positioning the Uniswap protocol to win as the default decentralized exchange for tokenized value.\n\nThe protocol has processed ~$4 trillion in volume, made possible by thousands of developers, millions of liquidity providers, and hundreds of millions of swapping wallets.\n\nBut the last several years have also come with obstacles: we’ve fought legal battles and navigated a hostile regulatory environment under Gensler’s SEC. This climate has changed in the US, and milestones like Uniswap governance adopting DUNI, the DUNA, have prepared the Uniswap community for its next steps.\n\nThis proposal comes as DeFi reaches an inflection point. Decentralized trading protocols are rivaling centralized platforms in performance and scale, tokens are going mainstream, and institutions are building on Uniswap and other DeFi protocols.\n\nThis proposal establishes a long-term model for how the Uniswap ecosystem would operate, where protocol usage drives UNI burn and Uniswap Labs focuses on protocol development and growth. We propose to:\n\nTurn on Uniswap protocol fees and use these fees to burn UNI\n\nSend Unichain sequencer fees to this same UNI burn mechanism\n\nBuild Protocol Fee Discount Auctions (PFDA) to increase LP returns and allow the protocol to internalize MEV\n\nLaunch aggregator hooks, turning Uniswap v4 into an onchain aggregator that collects fees on external liquidity\n\nBurn 100 million UNI from the treasury representing the approximate amount of UNI that would have been burned if fees were on from the beginning\n\nFocus Labs on driving protocol development and growth, including turning off our interface, wallet, and API fees and contractually committing to only pursue initiatives that align with DUNI interests\n\nMove ecosystem teams from the Foundation to Labs, with a shared goal of protocol success, with growth and development funded from the treasury\n\nMigrate governance-owned Unisocks liquidity from Uniswap v1 on mainnet to v4 on Unichain and burn the LP position, locking in the supply curve forever\n\nProtocol Fees\n\nThe Uniswap protocol includes a fee switch that can only be turned on by a UNI governance vote. We propose that governance flip the fee switch and introduce a programmatic mechanism that burns UNI.\n\nProtocol Fee Rollout\n\nTo minimize impact, we propose fees roll out over time, starting with v2 pools and a set of v3 pools that make up 80-95% of LP fees on Ethereum mainnet. From there, fees can be turned on for L2s, other L1s, v4, UniswapX, PFDA, and aggregator hooks.\n\nUniswap v2 fee levels are hardcoded and governance must enable or disable fees across all v2 pools at once. With fees off, LP fees are 0.3%. Once activated, LP fees are 0.25% and protocol fees are 0.05%.\n\nUniswap v3 has fixed swap fee tiers on mainnet, with protocol fees that are adjustable by governance and set at the individual pool level. Protocol fees for 0.01% and 0.05% pools would initially be set to 1/4th of LP fees. For 0.30% and 1% pools, protocol fees would be set to 1/6th of LP fees.\n\nLabs will assist the community in monitoring the impact of fees and may make recommendations to adjust. To improve efficiency, we propose governance votes on fee parameters skip the RFC process and move straight to Snapshot followed by an onchain vote.\n\nUpdate 12/18:\n\nThe list of Uniswap v3 pools included in the proposal has been refreshed to reflect the latest available data. The full updated list can be found here.\n\nUnichain Sequencer Fees\n\nUnichain launched just 9 months ago, and is already processing ~$100 billion in annualized DEX volume and ~$7.5 million annualized sequencer fees.\n\nThis proposal directs all Unichain sequencer fees, after L1 data costs and the 15% to Optimism, into the burn mechanism.\n\nFee Mechanism for MEV Internalization\n\nThe Protocol Fee Discount Auction (PFDA) is designed to improve LP performance and add a new source of protocol fees by internalizing MEV that would otherwise go to searchers or validators.\n\nThis mechanism auctions off the right to swap without paying the protocol fee for a single address for a short window of time, with the winning bid going to the UNI burn. Through this process, MEV that would typically go to validators instead burns UNI. For a detailed breakdown of this mechanism, read the whitepaper.\n\nEarly analysis shows these discount auctions could increase LP returns by about $0.06-$0.26 for every $10k traded, a significant improvement given that LP returns typically range between -$1.00 and $1.00 for this amount of volume.\n\nAggregator Hooks\n\nUniswap v4 introduced hooks, turning the protocol into a developer platform with infinite possibilities for innovation. Labs is excited to be one of the many teams unlocking new functionality using hooks, starting with aggregation.\n\nThese hooks source liquidity from other onchain protocols and add a programmatic UNI burn on top, turning Uniswap v4 itself into an aggregator that anyone can integrate.\n\nLabs will integrate aggregator hooks into its frontend and API, providing users access to more sources of onchain liquidity in a way that benefits the Uniswap ecosystem.\n\nAggregator Hooks (1)3600×2259 410 KB\n\nRetroactive Burn\n\nMany community members wish the fee switch had been turned on earlier as UNI holders have missed out on years of fees on ~$4 trillion in Uniswap protocol volume. Alas, we cannot turn back the clock… or can we?\n\nWe propose a retroactive burn of 100 million UNI from the treasury. This is an estimate of what\n\nmight have been burned if the protocol fee switch had been active at token launch.\n\nTechnical Implementation\n\nEach fee source requires an adapter contract, that sends fees into an immutable onchain contract called TokenJar where they accumulate. Fees can only be withdrawn from TokenJar if UNI is burned in another smart contract called Firepit.\n\nTokenJar (1)3600×2259 352 KB\n\nTokenJar and Firepit are already implemented, along with adapters for v2, v3, and Unichain. PFDA, v4, aggregator hooks, and bridge adapters for fees on L2s and other L1s are in progress and will be introduced through future governance proposals.\n\nFees Roadmap (1)3600×2259 250 KB\n\nDetailed documentation on protocol fees and UNI burn can be found here.\n\nUNIfication and Growth Budget\n\nLabs led development of every version of the Uniswap protocol, grew the initial community, popularized AMMs and DeFi, and launched products used by tens of millions. Foundation expanded this ecosystem through grants, governance support, and community growth.\n\nWe propose unifying these efforts by transitioning Foundation teams to Labs, as Labs shifts its focus to helping make Uniswap protocol the default exchange for all tokenized value, funded through a growth budget from the treasury.\n\nUniswap Foundation Activities Move to Uniswap Labs\n\nWith the approval of this proposal, Labs will take on operational functions historically managed by the Foundation, including ecosystem support and funding, governance support, and developer relations.\n\nHayden Adams and Callil Capuozzo will join the existing Foundation board of Devin Walsh, Hart Lambur, and Ken Ng, bringing the board to five members. Most Foundation employees will move to Labs, except for a small team focused on grants and incentives. This team will deploy the Foundation’s remaining budget consistent with its mission, after which future grants will come from the growth budget under Labs.\n\nLabs Focuses on Uniswap Protocol Growth and Development\n\nThis proposal aligns Labs’ incentives with the Uniswap ecosystem. If approved, Labs will shift its focus from monetizing its interfaces to protocol growth and development. Labs’ fees on the interface, wallet, and API will be set to zero.\n\nThese products already drive significant organic volume for the protocol. Removing fees makes them even more competitive and brings in more high quality volume and integrations, leading to better outcomes for LPs and the entire Uniswap ecosystem.\n\nMonetization of Labs interfaces will continue to evolve over time and any fees on volume originating from these products will benefit the Uniswap ecosystem.\n\nLabs will focus on both sides of the protocol’s flywheel – supply of liquidity and demand for volume. Below are just a few of the roadmap items ahead:\n\nImprove LP outcomes and protocol liquidity. Deploy the Protocol Fee Discount Auction and LVR-reducing hooks to capture more value for LPs and the protocol. Strengthen protocol leadership on strategic pairs, including dynamic fee hooks and stable-stable hooks. Add more sources of liquidity to the Uniswap protocol through aggregator hooks.\n\nDrive Uniswap protocol integrations and onboard new ecosystem players. Accelerate adoption through strategic partnerships, grants, and incentives that bring new participants onchain. Provide SDKs, documentation, and even a dedicated engineering team to help partners build on the protocol.\n\nAccelerate developer adoption of the protocol with Uniswap API. Pivot the API from a profit-generating product to a zero margin distribution method, expanding the protocol to more platforms and products, including those that previously competed with Labs products. Launch self-serve developer portal for key provisioning and allow integrators to add and rebalance liquidity directly through the API.\n\nDrive protocol usage with Labs’ interfaces. Use the interface and wallet to drive more volume to the protocol by making it free, investing heavily in LP UX, and adding new features like dollar-cost-averaging, improved crosschain swaps, gas abstraction, and more.\n\nEmpower hook builders. Provide engineering support, routing, support in Labs’ interfaces, grants and more.\n\nEstablish Unichain as a leading liquidity hub. Optimize Unichain for low-cost, high-performance AMM trading which attracts LPs, asset issuers, and other protocols. Make Uniswap protocol on Unichain the lowest cost place to trade in Labs’ interface and API by sponsoring gas.\n\nBring more assets to Uniswap. Deploy Uniswap protocol wherever new assets live. Build and invest in liquidity bootstrapping tools and token launchers, RWA partnerships and bridging of non-EVM assets to Unichain.\n\nLabs will also accelerate growth through builder programs, grants, incentives, partnerships, M&A, venture, onboarding institutions, and exploring moonshot efforts to unlock new value for the Uniswap ecosystem. We will provide regular updates to the community, including budget reports, frequent product and growth updates, and real-time dashboards giving visibility into our impact.\n\nThe Growth Budget\n\nWe propose governance create an annual growth budget of 20M UNI, distributed quarterly using a vesting contract starting January 1, 2026, to fund protocol growth and development.\n\nThe growth budget would be governed by a service provider agreement between Labs and DUNI. This would include an explicit commitment from Labs to maintain alignment between its activities and DUNI, ensuring Labs does not pursue strategies that conflict with token holder interests.\n\nThe Foundation will coordinate this process in its role as Ministerial Agent to DUNI. If the Snapshot vote passes, an independent committee composed of Ben Jones and Hart Lambur will be appointed by the Foundation to lead negotiations based on this draft letter of intent, with Cooley LLP serving as the committee’s external counsel. The final negotiated agreement will be included in this governance proposal as part of the full onchain vote, and executed on its passing.\n\nUpdate 12/18:\n\nFinal services agreement between DUNI and Uniswap Labs\n\nThe final services agreement reflects negotiations between the Uniswap Foundation’s independent committee, acting as Ministerial Agent to DUNI, and Uniswap Labs following the temperature check, and does include deviations from the previously posted Letter of Intent.\n\nHash: 0xb7a5a04f613e49ce4a8c2fb142a37c6781bda05c62d46a782f36bb6e97068d3b\n\nIndemnification agreements for the independent negotiation committee\n\nThese agreements indemnify the members of the independent negotiation committee (Hart Lambur and Ben Jones), or their respective service providers, as applicable, for the services they provided in negotiating the SPA.\n\nHashes:\n\n0x96861f436ef11b12dc8df810ab733ea8c7ea16cad6fd476942075ec28d5cf18a (Hart Lambur), 0x576613b871f61f21e14a7caf5970cb9e472e82f993e10e13e2d995703471f011 (Ben Jones)\n\nLock the Socks\n\nUnisocks have a long history, ranging between fun, fashion, flex, weird, weirder, even weirder, and gross (we’re not linking this one). They were launched by Labs in May 2019 as the first tokenized socks to trade on Uniswap protocol, or anywhere probably.\n\nWhen Labs launched UNI in September 2020, it transferred ownership of the original Uniswap v1 SOCKS/ETH liquidity position to Uniswap governance, where it has sat dormant ever since. We propose that governance move this position from Uniswap v1 on mainnet to Uniswap v4 on Unichain and transfer the LP position to a burn address, locking it forever.\n\nThis would ensure that this liquidity can never be withdrawn in the future, permanently locking in the original price curve and realizing the Unisocks vision. Also, the pink socks belong on the pink chain and “Uniswap v4” rhymes with “wore” – which is what you do with socks.\n\nDue to technical complexity, this migration would be executed through a separate onchain vote.\n\nProposal Spec\n\nPre-proposal - complete before onchain vote\n\n/// Deploy the TokenJar and the Releaser\nTokenJar tokenJar = new TokenJar{salt: SALT_TOKEN_JAR}();\nFirepit releaser = new Firepit{salt: SALT_RELEASER}(RESOURCE, THRESHOLD, address(tokenJar));\n\n/// Update the owner on the TokenJar and Releaser to governance\nIOwned(address(tokenJar)).transferOwnership(TIMELOCK);\nIOwned(address(releaser)).transferOwnership(TIMELOCK);\n\n/// Update the thresholdSetter on the Releaser to the owner\nreleaser.setThresholdSetter(TIMELOCK);\n\n/// Deploy the FeeController\nV3FeeController v3FeeController =new V3FeeController{salt: SALT_FEE_CONTROLLER}(address(V3_FACTORY), address(tokenJar));\n\n/// Update the feeSetter to the owner\nv3FeeController.setFeeSetter(TIMELOCK);\n\n/// Set default fees for each fee tier\nv3FeeController.setDefaultFeeByFeeTier(100, 10 << 4 | 10);\nv3FeeController.setDefaultFeeByFeeTier(500, 8 << 4 | 8);\nv3FeeController.setDefaultFeeByFeeTier(3000, 6 << 4 | 6);\nv3FeeController.setDefaultFeeByFeeTier(10_000, 4 << 4 | 4);\n\n/// Configure the merkle root for enabled pairs (this is all the pairs the fee will be on for)\nv3FeeController.setMerkleRoot(merkleRoot);\n\n/// Deploy the UNIVesting smart contract\nUNIVesting uniVesting = new UNIVesting(5_000_000 ether, 91.25 days, GROWTH_FUND_RECIPIENT);\n\nIn this proposal - if passed\n\n/// Burn 100M UNI\nUNI.transfer(0xdead, 100_000_000 ether);\n\n/// Approve two years of vesting to the UNIvester smart contract\n/// UNI stays in treasury until vested and unvested UNI can be cancelled by setting approve back to 0\nUNI.approve(address(uniVesting), 40_000_000 ether);\n\n/// Set the owner of the v3 factory to the configured fee controller\nV3_FACTORY.setOwner(address(v3FeeController));\n\n/// Update the v2 fee to setter to the timelock\nIOldV2FeeToSetter(V2_FACTORY.feeToSetter()).setFeeToSetter(TIMELOCK);\n\n/// Set the recipient of v2 protocol fees to the token jar\nV2_FACTORY.setFeeTo(address(tokenJar));\n\nResources:\n\nFee documentation\n\nFee contracts\n\nProtocol Fee Discount Auction whitepaper\n\nDraft letter of intent\n\nFinal services agreement\n\nIndemnification agreement for Hart Lambur\n\nIndemnification agreement for Ben Jones\n\nThank you\n\nUniswap protocol wouldn’t be here without the LPs, swappers, builders, and community members who’ve helped the protocol become the largest decentralized exchange in the world. This proposal builds on that foundation, and sets the ecosystem up for the next phase of growth.\n\nThank you to everyone who has been part of the journey so far. We’re just getting started!\n\n47 Likes\n\nUniswap Governance Community Calls\n\n[Temp Check] Protocol Fee Expansion: Robinhood Chain\n\n[Temp Check] Protocol Fee Expansion: Eight More Chains and Remaining Mainnet v3 Pools\n\n[RFC] IL Hedge Hook — Automated Impermanent Loss Protection for Uniswap v4 LPs\n\n[Temp Check] Protocol Fee Expansion: Three More Chains\n\n[Temp Check] Protocol Fee Expansion: Arc\n\nUniswap Foundation: Summary FY’2025 Financials\n\nUniswap Foundation: Summary FY’2025 Financials\n\nDoo_StableLab\n\nNovember 10, 2025, 9:06pm\n\n2\n\nWe support the long waited initiaves. We will vote in support for both Uniswap fee switch as well as burns\n\n8 Likes\n\nBoardroom\n\nNovember 10, 2025, 9:13pm\n\n3\n\nGlad to see this come to fruition, happy to vote in support here.\n\n6 Likes\n\nbendi\n\nNovember 10, 2025, 9:45pm\n\n4\n\nHey @haydenadams, this is an exciting proposal and it’s exciting to see you being the one to make it!\n\nCan you confirm this commit, which is linked from the docs, represents the version of the protocol fee contracts you intend to deploy and go live with. We see the OZ audit reports. Were/will any additional audits performed?\n\nScopeLift looks forward to digging into the technical details of the proposal at length and sharing our analysis. I will say that my high level, gut reaction to what has been proposed is a positive one. Thanks to everyone who helped make it possible\n\n6 Likes\n\nmarktoda\n\nNovember 10, 2025, 9:55pm\n\n5\n\nThere are a few minor smart contract changes still to be made and we are planning one more round of audits before deployment! We welcome any feedback in the meantime and will include it on the bug bounty later this week with details to come\n\n9 Likes\n\nbendi\n\nNovember 10, 2025, 10:06pm\n\n6\n\nAwesome thanks @marktoda\n\n2 Likes\n\nrobertleifke\n\nNovember 10, 2025, 11:21pm\n\n7\n\nHey @haydenadams and team,\n\nI read the proposal and think it’s great news for the development of the Uniswap AMMs and all the onchain infrastructure supporting it. That said, I do worry about the actual incentive alignment between Labs, the Foundation, and the protocol(s). Uniswap Labs is a Delaware C corp that raised large venture rounds on it’s equity and therefore has expectations from it’s investors that the Labs equity will be more valuable in the future. Traditionally businesses become more valuable by maximizing cash flow from it’s products. Instead it’s seems that Labs is moving away from this model by increasing the value of it’s UNI holdings which ideally happens the more revenue the Uniswap AMMs and supporting protocols generate. That seems fine in practice but to realize that value the company must sell it’s tokens, reducing its stake and therefore its future incentive to continue long term development. Even more so, it exposes the Labs entity to volatility and speculation of the UNI token. This moves Labs away from being a company focused on just products to one needing sophisticated treasury management operations. Additionally, if Labs is the primary entity building the protocol and expanding it’s market share, to what extent is it fair that Labs only receives a small portion of the value it creates by holding a small percentage of the token supply. Additionally, many of the core trading functions powered by Uniswap protocols (e.g. Unichain sequencer, UniswapX) requires Labs to run centralized infrastructure. This has created a massive, complex intermediary layer that if Labs truly went away would kill the viability of the protocol. If Labs shuts off it’s own interface fees, it could expose them to unpredictable revenues and thereby have consequential effects on the protocol(s) itself. More importantly, turning on the Uniswap fee switch and then burning UNI tokens feels like the Uniswap AMMs would no longer be public goods but instead a commercialized product. Needless to say, I still like the direction that Labs is taking to prioritize Uniswap V4 but remain skeptical of the alignment between Labs, protocol fees, and the UNI token if the actual protocol(s) are to remain public goods.\n\n3 Likes\n\nArgonaut\n\nNovember 10, 2025, 11:56pm\n\n9\n\nAs a small delegate that did not contribute to this proposal, the Argonaut team appreciates the chance to comment. The community has waited a long time for this milestone for the Uniswap DAO, and we trusted Uniswap Labs to make the right call by moving away from directing interface revenues to themselves and establishing a framework that creates value for the DAO and the governance token. This proposal exceeds our expectations and speaks to the caliber of the teams at Uniswap Labs and the Uniswap Foundation. We will vote in favor. Congratulations to everyone who made it possible!\n\n2 Likes\n\nmnemon1ck\n\nNovember 11, 2025, 12:41am\n\n10\n\nIs all the functionality already implemented and the only thing that is left is turn on the switch?\n\n1 Like\n\ndennisonb\n\nNovember 11, 2025, 3:05am\n\n11\n\nI can hardly believe believe we’ve finally come to this day. Great work everyone. The flame of DeFi rises!\n\n2 Likes\n\nmenaskop\n\nNovember 11, 2025, 5:42am\n\n12\n\nOverall, as someone who has been working with tokenomics for many years, I view this initiative positively.\n\nHowever, I would like to make several clarifications:\n\nBurning is not the only incentive mechanism → it works best when balanced with other methods such as staking or direct fee distribution. The fundamental rule of tokenomics derives from the law of supply and demand: the more effectively we increase demand while reducing supply, the stronger the incentive for token growth overall.\n\nThe governance function of UNI and the inclusion of new participants must not be overlooked, since without that, decentralization will be compromised. Therefore, additional reward campaigns → like those held recently, which allowed users to earn UNI through activity and liquidity provision rather than direct purchases → and similar actions will still be necessary.\n\nMost likely, the team is cautious about introducing direct buybacks or fee distributions due to recurring regulatory risks, so at this stage, the burn mechanism may indeed be the most appropriate solution.\n\nSo overall, I believe that this approach will be beneficial at this stage.\n\n2 Likes\n\nuniyj\n\nNovember 11, 2025, 9:25am\n\n13\n\nHaven’t been very active on Uniswap governance for a while, but soooo pumped for this!\n\nFoundation + Labs = Protocol\n\nUF + UL = UP !!!\n\nyj\n\n1 Like\n\nJames\n\nNovember 11, 2025, 12:35pm\n\n15\n\nObviously cool to see a meaningful proposal from @haydenadams about the UNI tokens future. However, I do think the proposal reads a lot more of ‘here’s what’s happening’ as opposed to ‘lets talk about the future of UNI’ regardless thought I’d post an alternative mechanism to burning 100% of the fees.\n\nInstead, the fees could deposit revenue into a treasury based on the LP pools: ie fees from ETH/USDC pool accrue both ETH & USDC to the uniswap treasury, UNI/BANKER pool accrues both tokens, etc. UNI then creates a productive treasury that is an index of all tokens that are traded on uniswap.\n\nUNI token holders can then vote onchain about how to manage this treasury, capture the upside of all tokens that are traded on uniswap, sell tokens the DAO believes will go down, buy tokens the DAO believes will go up, form an endowment, introduce novel DeFi integrations to the treasury, etc, etc.\n\nThis to me seems like a much longer term and sustainable use of these fees.\n\n1 Like\n\nSEEDGov\n\nNovember 11, 2025, 1:07pm\n\n16\n\nFirst of all, we want to congratulate the team for the work done in developing this long-awaited proposal, which we fully support!\n\nSecondly, we have a few questions we’d like to clarify:\n\nWith the projected reduction of LP fees from 0.3% to 0.25%, isn’t there a risk that liquidity providers might move their funds to other DEXs offering more attractive conditions? If that happens, lower liquidity in the pools and higher IL could lead to a decrease in trading activity and volume, thereby reducing the protocol’s revenue and, consequently, the amount of UNI to be burned. Was this risk assessed? Is there room to reconsider the fee strategy if such effects are observed?\n\nWe’d like to better understand the rationale behind allocating the entire Protocol Fee to token burns, rather than reserving part of it for growth initiatives or revenue sharing with tokenholders. Was any financial analysis conducted to support the idea that burning 100% of fees is preferable to using a portion to strengthen growth or reward holders? Why was this total burn mechanism chosen?\n\nRegarding the budget request of 20M UNI starting in January 2026, aimed at funding growth and protocol development, isn’t there a potential overlap with the $ 25.1M budget approved for the Uniswap Foundation in March this year, which already included allocations for development and growth over the next two years? Given that Uniswap Labs will now take over growth and development responsibilities, along with the transfer of staff and operations from the Foundation to Labs, will the @UniswapFoundation return to the DAO the previously approved budget?\n\nWhat growth initiatives can you tell us about that will be carried out with the required budget? Is there a tentative roadmap you can share?\n\nThanks.\n\n8 Likes\n\nSEEDGov Delegate Platform\n\nDonOfDAOs\n\nNovember 11, 2025, 1:56pm\n\n17\n\nWith the removal of the front end fee, is there path to increase LP fees? Given FE fee was 0.25% and LPs are losing 0.05% there is more than enough in savings to boost LPs to their previous levels while also providing the same 0.05% to burn.\n\n2 Likes\n\ngeronimo\n\nNovember 11, 2025, 3:51pm\n\n18\n\n20M UNI at today’s prices is about $180M per year. This is effectively an expense that offsets the majority if not all fees sent to the firepit. This maybe reasonable but we can’t say without seeing the details of the growth budget and how those funds will be utilized. Where can that be found? @devinwalsh @kenneth\n\nWhy is it being allocated in nominal token units? 20M is 2.2%+ of supply per year. Growth should have a budget and a dollar equivalent in UNI tokens should be granted.\n\n2 Likes\n\nYellow-Cake\n\nNovember 12, 2025, 12:24am\n\n21\n\nThis proposal is long overdue and represents the structural alignment UNI has needed since launch.\n\nTurning on protocol fees, directing them to burns, and linking token value directly to on-chain activity finally gives UNI true economic purpose.\n\nThe one-time burn and recurring fee capture mechanisms reward long-term holders and reinforce Uniswap’s position as a community-driven, revenue-generating protocol rather than just an LP platform.\n\nImportantly, this change doesn’t rely on speculative hype — it builds a measurable, on-chain feedback loop between usage and value. That’s what will sustain Uniswap over the next cycle.\n\nI fully support the proposal and encourage timely execution once the Snapshot passes. Let’s make UNI deflationary, sustainable, and representative of the ecosystem it powers.\n\nYellowCake\n\n1 Like\n\nOleh\n\nNovember 12, 2025, 12:01pm\n\n22\n\nI waited for this to happen for more than 4 years!\n\nUniswap changed 4 major versions meanwhile: a tremendous, colossal amount of work by team, which I’d like to thank for!\n\njuroberttyb\n\nNovember 12, 2025, 2:02pm\n\n23\n\nWith the projected reduction of LP fees from 0.3% to 0.25%, isn’t there a risk that liquidity providers might move their funds to other DEXs offering more attractive conditions?\n\nThis argument holds back uni token holder and the protocol’s revenue alignment issue for too long.\n\nIn the long run, it is impossible to have revenue growth and uni token value alignment separated.\n\nawbvious\n\nNovember 13, 2025, 6:19pm\n\n24\n\nOver 5 years after the UNI drop (and thank you, btw), the biggest legacy of Uniswap in DeFi, I feel, is the Uniswap v2 contract. For one simple reason. If you see just about any other smart contract on any EVM compatible chain, you have to think: “Well, where’s the gotcha.” Now, that chain might have gotchas! But that contract is going to do what it says on the tin. That’s beautiful, and what we, five years later, are missing now.\n\nGovernance is suggestions: 5 years of DeFi and I am convinced more than ever that decentralization is an ideal that is strived for at best, and given lip service at worst. Governance votes are never guarantees, always just suggestions. The examples of DeFi protocol insiders, the five or less actual “devs” who actually “do the thing,” making “emergency measures” despite token votes are numerous. At the end of the day, there’s always some human typing “git commit” and they may or may not do it based on the votes.\n\nBack ends aren’t transparent and fixed: Then there are the “immutable” contracts themselves. Either they are completely obscured as to their source code, and full of admin keys and “upgradability,” or they have it simply a few layers deep, in another contract that is referenced or in some off-chain computational resource. Only a Uniswap v2 contract will do what it says on the tin. Every time. I mean, there may be more examples, but none off the top of my head, certainly not with the historical impact. And still current relevance! Someone spins up a new EVM compatible chain and someone two seconds later is going to come up with a Uniswap v2 clone with Uniswap v2 contracts that work exactly like they did, years ago. (But again, the chain itself could have admin keys, upgradability, 20 validators that are really just one dude, etc., etc.)\n\nFront ends aren’t transparent and fixed: Of course, there are also frontends. Uniswap was also fairly historic (in a less positive way) for being the first high profile case of a “DeFi” protocol censoring their frontend for fear of regulatory attack. Those who knew, of course, could find a way to the Uniswap v2 contracts without using the Uniswap front end. And that’s beautiful. Because, at the time, there was basically no regulation—good or bad—there was only fear of de facto registration through legislation (hence the front-end censorship), but nothing actually written into law as far as I can recall. Which is okay, I think, if—if I can use the old maxim—Code is law. In /that world/ with no regulation, Code is Law works for me. I don’t know about this world. Personally, I was much less scared of smart contracts five years ago than just about everything that is going on now.\n\n(My personal view, if I may slightly digress, just so there’s no misunderstanding as to motives: Crypto should not be connected in any way to banks in any way where ultimately the general public should have to bail out the degens. FDIC-insured banks with “fractional reserves” should not be impacted if some crypto 1000x leveraged prediction market rug pulls or death spirals. That means, in my ideal world, yes, code is law, the MEV extractor or the MEV extractor’s extractor (per a recent case) is on equal terms—all the way up until the proverbial fist hits the proverbial nose, which to me is the onramps and offramps. Do what you want with your bits of 0s and 1s but when you try to convert them to dollars and cents… Well, where the buck starts, is where the buck stops. Just a bit of disclosure on my personal views. I also don’t like one-dollar-equals-one-vote and the outsized power of A16Z, etc., but that’s another matter for another day.)\n\nSo, I don’t think we’ll ever get away from a human has to type in “git commit” sometimes. Robots aren’t running the cooling towers in data centers. Humans will be a part. But we /can/ make it about as “immutable” and decentralized as possible when proposals are enacted, and I think this suggestion needs to incorporate this if we want to believe Uniswap is striving not lip-servicing.\n\nGovernance implementation is as human-less as possible: Basically, you have the high-level proposal, but you also have a very, very detail implementation plan connected to it. One that is clearly audited HEAVILY. But basically the plan is a really detailed computer program that is waiting to read the Ethereum blockchain (presumably) for the result of this vote as basically a parameter that will run the entire program. It details exactly what will happen to the contracts, the infrastructure, the websites, the front, the back, you name it and it happens all programmatically (ideally). If there’s ANY part with a human in it, make them have skin in the game, like Hayden Adams has to himself push some button, fine, but if he doesn’t push the button per the vote, then he has a legally-binding contract where he donates half his wealth to open-source development (or something).\n\nBack-ends are transparent and fixed. Basically every trick they have now, remove it. No admin keys. No upgradability. As little as possible off-chain. Truly decentralized infrastructure would be great… Dunno if it exists. I mean, it does in name, the number of DePIN projects out there is insane. But how many are truly decentralized? But at the very, least there’s probably a way to use disinterested third-parties, maybe a lot of different DePINs and possibly classical infrastructure providers along with some kind of kill switch if it gets messed with and a High Availability solution to go to the others if it happens. In other words, Disaster Recovery assuming that a human wanting to go against the vote is /a disaster/. Not saying it will be easy, but I am pretty sure a solution can be made that is so whack-a-mole it won’t go down, won’t get changed.\n\nFront-ends that are transparent and fixed. Permaweb is probably the easiest way to solve most of that. But just like back-ends, you got the High Availability, whack-a-mole solutions, that include P2P, Tor, you name it. I don’t doubt if there’s the money for it, there’s a solution for it. Point is, even if some powerful country says that memecoin is against our national interest, not much anyone can do about it coming (front end) or going (back end).\n\nOf course, the biggest downside risk is you could spend a bunch of money on something, and after all those audits, it still ships with a bug that bricks it instantly. (Okay, that and a government decides everyone human who made a vote and/or enabled the enaction of that vote should be put in jail. That would be pretty bad.) BUT, at least everyone would know the result would be TRUE (as true as can be) Decentralized Finance.\n\n[EDIT: 10 seconds later, formatting.]\n\n1 Like\n\nnext page →\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nMaking Protocol Fees Operational\n\nRequests for Comment\n\n35\n\n22004\n\nMay 14, 2024\n\n[Temperature Check] - Activate Uniswap Protocol Governance\n\nGovernance-Meta\n\n156\n\n67892\n\nMarch 14, 2025\n\nUniswap Proposal: An Alternative Use-Case for the Fee Switch\n\nUncategorized\n\n21\n\n6616\n\nApril 7, 2023\n\nTemperature Check - Ultrasound UNI [Fee switch organization funding]\n\nTemperature Check\n\n43\n\n8342\n\nFebruary 25, 2022\n\n\"Fee Switch\" Design Space & Next Steps\n\nRequests for Comment\n\n73\n\n29139\n\nNovember 21, 2022","tokens":8816,"crawled_at":1791193454995}
+{"id":10241,"url":"https://stack.olas.network/open-autonomy/key_concepts/abci_app_async_behaviour","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"The AsyncBehaviour class - Olas Stack Developer Documentation","text":"The AsyncBehaviour class\n\nNote\n\nFor clarity, the snippets of code presented here are a simplified version of the actual\nimplementation. We refer the reader to the Open Autonomy API for the complete details.\n\nThe AsyncBehaviour class, introduced in the valory/abstract_round_abci\nSkill, is a mixin class that allows the AEA developer to use\nasynchronous programming patterns in a Behaviour implementation. Since it is usual that many of the tasks to be carried by the state behaviours are long-running, this is the base class from which FSM Behaviours will be typically derived from.\n\nThe Need for Asynchronous Behaviours\n\nThe main motivation behind the AsyncBehaviour utility class\nis that in idiomatic AEA behaviour development, the act method\ncannot contain blocking code or long-running tasks, as otherwise\nthe AEA main thread that executes all the behaviours would get stuck.\nFor example, in order to interact with an external component through\na request-response pattern, e.g., sending a request to an HTTP server and waiting for its response, or\nrequest the Decision Maker to sign a transaction. The usual approach in this case is to:\n\nSend the message from the act() method and update the state\ninto \"waiting for the response\" (e.g., by updating an attribute in\nthe shared state or in the behaviour instance, or by using the\nstate pattern),\nsuch that the next call to act() can be intercepted and controlled by the developer.\n\nReceive the response in a concrete Handler object that is registered\nto process messages of the response protocol.\n\nHandle the response in the handler's handle() method according to the\nskill business logic and the current state behaviour, and notify\nthe behaviour about the change of state (e.g. by updating an attribute\nin the shared state such that the next act call can read it and take\na different execution path).\n\nFor large and complex skills, this development approach is quite error-prone and expensive\nin terms of maintainability, as the business logic does not reside in a single\nskill component (i.e., in a behaviour class), but also in several other skill components (i.e., in the handler classes, one for each interaction protocol required by the behaviour).\n\nAsynchronous Programming to the Rescue\n\nA well-known programming technique that turned out very useful in the\nweb development community is asynchronous programming.\n\nInformally, a programming language that supports asynchronous\nprogramming allows running blocking operations asynchronously:\nthe operation is not run in the same thread where the call happened,\nbut it is delegated to another executor, e.g., another thread/process,\nallowing the caller function execution being \"suspended\" until the operation has completed.\nOnce the blocking operation has completed, the execution of the function\ncan process the result and continue as usual.\nThis lets the main thread to perform other tasks while the function is waiting\nfor the result of the operation.\n\nIf the reader is not familiar with asynchronous programming concepts,\nwe suggest reading the following resources:\n\nMDN Web Docs: Asynchronous JavaScript\n\nMDN Web Docs: Glossary: asynchronous\n\nasyncio standard Python library documentation\n\nHow AsyncBehaviour works\n\nThe behaviour execution model of the AEA framework is the following.\nAt the AEA startup, the framework registers a periodic task, one for each\nBehaviour object b, that executes the b.act method. Such periodic\nexecution for behaviour b is scheduled in the main thread loop,\nwith a tick interval b.tick_interval and starting time b.start_at.\nAs mentioned above, the code in act() should not be blocking,\nas otherwise it would block the main thread execution, and\ntherefore it would prevent the execution of the other behaviours' act()\nand the processing of incoming messages.\n\nclass SimpleBehaviour(Behaviour, ABC):\n\"\"\"This class implements a simple behaviour.\"\"\"\n\ndef act(self) -> None:\n\"\"\"Do the action.\"\"\"\n# (...)\n\nThe AsyncBehaviour utility class allows to wrap the execution\nof the act() method allowing its execution to be \"suspended\"\nand resumed upon the happening of certain events\n(e.g. the receiving of a message, a sleep timeout etc.).\nCurrently, the crux of the implementation is the\nPython built-in generator machinery:\n\nfrom the developer perspective, the execution can be suspended by using\nyield or yield from expressions. This will return a generator object\nto the framework, which can opportunely be stored in an object attribute;\n\nfrom the framework perspective, the execution can be resumed by \"sending\" a\nvalue to the generator object, using the send()\nmethod of the generator object. The value can be None,\nor a message sent by another skill component.\n\nclass AsyncBehaviour(ABC):\n\n@abstractmethod\ndef async_act(self) -> Generator:\n\"\"\"Do the act, supporting asynchronous execution.\"\"\"\n\n@abstractmethod\ndef async_act_wrapper(self) -> Generator:\n\"\"\"Do the act, supporting asynchronous execution.\"\"\"\n# (...)\n\nThe abstract methods the developer should implement are called\nasync_act_wrapper and async_act.\n\nThe sequence diagram below gives the idea of what happens when the\nact() method of an AsyncBehaviour is called:\n\nIn words, the first time the act() method is called:\n\nfirst, it creates the generator object by calling the used-defined async_act_wrapper();\n\nit triggers the first execution by sending the None value;\n\nit returns the execution control at the first yield statement;\n\nsets the state to RUNNING;\n\nreturns to the caller in the main loop.\n\nAny subsequent calls to the act() method are redirected to the generator\nwhose execution was triggered by the first call, which invokes async_act().\n\nA simple example\n\nConsider a (one-shot) behaviour\nwhose logic is to print a sequence of messages separated by a sleep interval:\n\nclass PrintBehaviour(OneShotBehaviour, AsyncBehaviour):\n\ndef async_act_wrapper(self):\nyield from self.async_act()\n\ndef async_act(self):\nprint(\"First message\")\nyield from self.sleep(1.0)\nprint(\"Second message\")\nyield from self.sleep(1.0)\nprint(\"Third message\")\n\nWithout AsyncBehaviour, one should take care of:\n\nremembering the \"state\" of the behaviour (i.e. what is the last message printed)\n\nhandling the sleep interval by hand\n\nThis is a naive implementation\n\nimport datetime\nfrom aea.skills.behaviours import SimpleBehaviour\n\nclass PrintBehaviour(SimpleBehaviour):\n\ndef __init__(self, *args, **kwargs):\nsuper().__init__(*args, **kwargs)\nself.state = 0\n\n# remember time of last printed message\nself.last_time = None\n# timedelta of 0 days, 1 second\nself.timedelta = datetime.timedelta(0, 1)\n\ndef act(self):\nnow = datetime.datetime.now()\nif self.state == 0:\nprint(\"First message\")\nself.state += 1\nself.last_time = now\nreturn\nif self.state == 1 and now > (self.last_time + self.timedelta):\nprint(\"Second message\")\nself.state += 1\nself.last_time = now\nreturn\nif self.state == 2 and now > (self.last_time + self.timedelta):\nprint(\"Third message\")\nself.state += 1\nself.last_time = now\nreturn\n# do nothing\n\nBlocking requests\n\nAs explained above, one of the common tasks for a behaviour is\nto interact with other AI agents and/or agent instances via message-based\ncommunication. In this section, we focus on a sequence of\nrequest-response interactions through agent interaction protocols.\nWe consider the fetchai/generic_buyer skill as an example (link to code).\n\nThe idiomatic approach\n\nThe idiomatic approach, implemented in the skill fetchai/generic_buyer,\nis outlined in the sequence diagram below. The suffix B is a shorthand\nfor Behaviour, and H is a shorthand for Handler.\n\nThe participants SearchB, SearchH, TransactionB, SigningH, LedgerH, FipaH\nand DecisionMaker are internal components of the buyer AEA,\nwhereas ADS, Seller, and Ledger are external actors.\n\nFollows the breakdown of each message exchange:\n\nThe buyer starts by searching for seller of the desired data,\nand the search behaviour (SearchB) sends a search request to an\nagent discovery service (ADS);\n\nThe search result of the ADS gets routed to the search handler (SearchH),\nwhich selects one of the sellers, and sends a \"call for proposal\" (CFP) message to him.\nThe CFP is the first message of a\nFIPA protocol interaction.\nSee the AEA documentation on the\nAEA FIPA-like protocol.\n\nThe seller replies with a \"FIPA proposal\" to the buyer. Such message\nis handled by the FipaH handler;\n\nOnce the negotiation has completed (only the FipaH is involved in the negotiation),\nthe FipaH handler sends the payment transaction to the TransactionB behaviour\nsuch that it can be processed;\n\nThe TransactionB, which was periodically listening for new transaction to process,\nreads the new transaction and sends a signing requests to the\nDecisionMaker.\nNote that a skill component does not have access to the crypto identity of\nan AEA, and it has to rely on the\nDecisionMaker\nfor certain operations, such as the signing of transactions.\n\nThe DecisionMaker\nsends the response to the dedicated handler, the SigningH.\nThe SigningH submit the transactions to the Ledger (through the ledger_api connection);\n\nThe Ledger's response (the transaction hash) is handled by the LedgerH handler,\nwhich in turn sends the transaction hash to the Seller\n\nThe Seller, once the transaction has been validated, will send the\nbought data to the buyer with an FIPA \"inform\" message, which is handled\nby the FipaH handler.\n\nThe business logic is spread across different skill components, behaviours and handlers,\ndue to the \"forced callback\" mechanism that forces the developer to handle the message\nof an interaction protocol in the handler registered for that protocol.\n\nUsing the AsyncBehaviour\n\nThe above example can be reimplemented in an AsyncBehaviour in\nthe following way (Python-pseudocode):\n\nclass GenericBuyerBehaviour(OneShotBehaviour, AsyncBehaviour):\n\ndef async_act_wrapper(self):\nyield from self.async_act()\n\ndef async_act(self):\nsearch_request = build_search_request(...)\n# send search request to the ADS\n# and (asynchronously) wait for the response\nresponse = yield from send(search_request)\nagents = response.result\n# pick the first agent in the result list\nseller = agents[0]\n\n# send CFP to the seller\n# and (asynchronously) wait for the response\ncfp = build_cfp(...)\nresponse = yield from send(cfp, to=seller)\n\n# here there should be the buyer strategy\n# for the negotiation with the seller...\n# (...)\n\n# in case both parties accept the negotiation outcome:\ntx = build_tx(...)\n\n# send transaction to the decision maker\n# and (asynchronously) wait for the response\nsigned_tx = yield from send(tx)\n\n# send transaction to the distributed ledger\n# and (asynchronously) wait for the response\ntx_hash = yield from send(signed_tx)\n\n# send transaction hash to the seller\nsend(tx_hash, to=seller)\n\n# wait until the seller sends the data\ninform_message = yield from self.wait_for_message()\nprint(inform_message.data)\n\n# done!\n\nAs you can see, the core business logic of the buyer resides in the async_act\nmethod. Many details of the implementation are omitted, like\nthe utility functions like build_* and send,\nbut they are conceptually similar to what is done in the handlers of the\nfetchai/generic_buyer skill.\n\nThe wait_for_message method, uses the send(...) method to wait for the\nresponse, allowing it to wait for specific events triggered\nby other components. In this case, each of the handlers will\ndispatch the response to the requester component, whose request\nis identified by the (dialogue) identifier\nof the interaction.\nHowever, note that the handler code in this case is skill-independent,\nwhich means that they do not contribute to the business logic.","tokens":2898,"crawled_at":1791193462037}
+{"id":10242,"url":"https://www.metaplex.com/docs/smart-contracts/token-metadata/token-2022","domain":"www.metaplex.com","chapter":"docs","title":"SPL Token-2022 | Token Metadata","text":"Token Metadata is a legacy program. It remains supported, but is not recommended for new projects. Use Core instead.\n\nSPL Token-2022 is the latest token program on the Solana blockchain that can be used to create fungible and non-fungible tokens. It supports the same functionalities and structures of the SPL Token program, but also includes a set of extensions to add new functionalities.\nIn order to support adding metadata information to Token-2022 mint accounts, a set of Token Metadata instructions have been updated to allow specified the desired token program. For example, Token Metadata can initialize a Token-2022 mint, create metadata and mint tokens using the Create and Mint instructions and specifying the SPL Token-2022 as the token program to use.\n\nThe token program of a mint account can be determined by checking the owner property of the account.\n\nA similar approach can be used for other instructions, such as Burn, Delegate, Lock, Print, Revoke, Transfer, Unlock, Unverify, Updateand Verify. These instruction can validate mint and token accounts from SPL Token-2022. The corresponding token program must be used in any instruction requiring a token program (e.g., Delegate): if the mint and token account are from Token-2022, then the Delegate instruction will validate that the correct token program has been specified.\nBy default, Create and Mint will create SPL Token mint and token accounts if these accounts do not exist. To use Token-2022 accounts, you need to specify SPL Token-2022 as the token program to use.\n\nSupported Extensions\nWhile Token-2022 provides several extensions, the majority of extensions focus on fungible tokens. For example, the confidential transfer can be used to hide the amount of tokens transferred. While this is relevant for fungibles, since the amount can vary across different transfers, it is not applicable to non-fungible tokens since their supply is always 1 and decimals is always 0. Hence, the transfer amount of a non-fungible token will always be 1.\nToken Metadata enforces restrictions on the type of extensions that can be present on mint and token accounts based on the Token Standard. For fungible assets (Fungible and FungibleAsset standards), no restrictions are placed – the only restriction is on the program providing the metadata information. For non-fungible assets (NonFungible and ProgrammableNonFungible standards), Token Metadata validates which extensions are enabled and restricts the set of extensions that can be used.\nMint account extensions\nThese are extensions that can be enabled on mint accounts of SPL Token-2022.\nconfidential transfers: hides the amount during transfers.\nAssetFungibleNon-Fungible\nAllowed\n✅\n❌\n\nDetails\n--\nNot applicable since non-fungibles have supply of 1\n\ntransfer fees: allow to configure a transfer fee derived from the amount being transferred.\nAssetFungibleNon-Fungible\nAllowed\n✅\n❌\n\nDetails\n--\nNot applicable since non-fungibles have supply of 1\n\nclosing mint: allows closing mint accounts when supply reaches 0.\nAssetFungibleNon-Fungible\nAllowed\n✅\n❌\n\nDetails\nMust specify the Metadata account as the close authority\nPotential for a creator to recreate the same group of mint and metadata accounts\n\ninterest-bearing tokens: allows to change how the UI amount of tokens are represented.\nAssetFungibleNon-Fungible\nAllowed\n✅\n❌\n\nDetails\n--\nNot applicable since non-fungibles have supply of 1\n\nnon-transferable tokens: allows for \"soul-bound\" tokens that cannot be moved to any other address.\nAssetFungibleNon-Fungible\nAllowed\n✅\n✅\n\nDetails\n--\n--\n\npermanent delegate: allows to specify a permanent account delegate for any token account of a mint.\nAssetFungibleNon-Fungible\nAllowed\n✅\n❌\n\nDetails\n--\nThis changes the concept of ownership\n\ntransfer hook: allows call into third-party programs during transfer.\nAssetFungibleNon-Fungible\nAllowed\n✅\n❌\n\nDetails\n--\nToken Metadata specifies the logic for transfer\n\nmetadata pointer: allows adding an address that describes the canonical metadata.\nAssetFungibleNon-Fungible\nAllowed\n✅\n✅\n\nDetails\nMust point to the Metadata address\nMust point to the Metadata address\n\nmetadata: allow adding metadata directly to mint accounts.\nAssetFungibleNon-Fungible\nAllowed\n❌\n❌\n\nDetails\nMetadata information is added by Token Metadata\nMetadata information is added by Token Metadata\n\nToken account extensions\nThese are extensions that can be enabled on token accounts of SPL Token-2022.\nmemo required: requires memo on transfers.\nAssetFungibleNon-Fungible\nAllowed\n✅\n❌\n\nDetails\n--\nNot applicable\n\nimmutable ownership: disables the ability to change the ownership of token accounts.\nAssetFungibleNon-Fungible\nAllowed\n✅\n✅\n\nDetails\n--\n--\n\ndefault account state: allows to configure default token account states.\nAssetFungibleNon-Fungible\nAllowed\n✅\n❌\n\nDetails\n--\nToken Metadata validates the account state\n\nCPI guard: prevent certain actions (e.g., transfer) inside cross-program invocations.\nAssetFungibleNon-Fungible\nAllowed\n✅\n❌\n\nDetails\n--\nToken Metadata specifies the logic for transfer\n\nA comprehensibe overview of each extension can be found on SPL Token-2022 program documentation.\n\nDefault extensions\nWhen a mint account does not exist, the Create instruction will initialize one. If the token program being used is SPL Token-2022, the mint will be initialized with both closing mint and metadata pointer extensions.\nAssociated Token Accounts (ATAs) by default are always initialized with the immutable ownership extension.","tokens":1366,"crawled_at":1791193484397}
+{"id":10243,"url":"https://gov.uniswap.org/t/rfc-preparing-for-possible-governance-attacks/24592","domain":"gov.uniswap.org","chapter":"governance_daos","title":"[RFC] Preparing for possible Governance Attacks - Requests for Comment - Uniswap Governance","text":"[RFC] Preparing for possible Governance Attacks\n\nRequests for Comment\n\njengajojo\n\nSeptember 17, 2024, 9:40am\n\n1\n\nSummary\n\nKickstart a discussion around preparing the DAO for possible governance attacks.\n\nMotivation\n\nIn 2023, several major DAOs faced governance crises due to attacks that exploited weaknesses in their treasury management. Nouns DAO encountered an incident when investor DCF GOD and allies amassed enough NFTs to propose liquidating the treasury. Amidst a bear market and disagreements over spending priorities, they used the governance structure for personal gain, withdrawing $27 million from the treasury.\n\nSimilarly, Aragon DAO experienced a governance exploit in May 2023. Investors gained control of 51% of the token supply and proposed liquidating the treasury. Despite efforts to oppose the move, they extracted $163 million, which led to Aragon’s dissolution.\n\nMost recently, in 2024, Compound DAO suffered a governance attack by a group known as the “Golden Boys.” They exploited the governance process to pass a proposal transferring $24 million in COMP tokens to a protocol under their control. This attack succeeded due to several factors: low voter turnout, poor timing of the vote (during a weekend), and lack of transparency.\n\nThese cases highlight a critical vulnerability in DAOs—concentrated voting power and low voter engagement can lead to malicious actors seizing governance control and draining the treasury for personal gain.\n\nRationale\n\nUniswap DAO’s core mission is to govern its protocol and manage treasury resources to support its long-term objectives. However, as the DAO grows, its treasury expands, creating an attractive target for potential attacks.\n\nThe current dynamic poses a threat: while the value of the treasury increases, the percentage of tokens actively delegated for governance decreases. This creates an imbalance where an attacker could acquire enough $UNI to take control of the DAO at a cost far below the total value of the treasury. Without safeguards, Uniswap DAO is at risk of facing a similar governance attack.\n\nImplementation\n\nWe see two possible solutions to address this challenge:\n\nEstablish a Veto Council\n\nOne proposed solution to safeguard the DAO’s treasury is to create a Veto Council. This council would have the authority to veto any proposal deemed harmful to the DAO. However, to avoid centralisation risks, the council’s veto power would be limited—lasting only 18 months. This ensures the council’s role is temporary, allowing time to strengthen governance while minimising the risk of long-term centralisation.\n\nThe Veto Council would provide an immediate defence mechanism, intervening when malicious proposals threaten the DAO’s stability or treasury. The ENS DAO recently adopted a similar solution (link).\n\nIntroduce Proposal Staking\n\nAn alternative solution is to implement a staking requirement for proposal authors. Under this system, anyone submitting a proposal must stake a small amount of UNI tokens, which would be locked until the vote concluded. Additionally, the vote would include a default option to cancel the proposal and slash the author if it receives over 33% of the votes to veto the proposal. This would effectively discourage bad actors from submitting harmful proposals, as they risk losing their staked tokens. The Cosmos hub governance has successfully implemented the ‘’No with Veto’’ option to combat spam and malicious proposals and has achieved tremendous success. This approach, however, can only be implemented in matured DAOs in terms of governance processes as an irrational stakeholder(s) with 33% of the voting power could exploit the system and veto any proposal and slash an innocent participant.\n\nBenefits:\n\nUnlike the Veto Council, which introduces some level of centralisation, proposal staking preserves the DAO’s decentralised nature. It empowers the broader delegate community to assess and vote on the validity of proposals, ensuring the process remains transparent and democratic.\n\nBy adding financial risk to submitting proposals, the staking mechanism discourages malicious intent while encouraging more thoughtful, well-constructed proposals.\n\nNo with Veto could be used by minor delegates to convey their strong disagreement with a particular proposal.\n\nNext Steps\n\nGather consensus from the DAO about next steps.\n\nVoting Options\n\nEstablish a Veto council\n\nExplore Proposal staking\n\nMake no changes\n\nOther\n\n4 Likes\n\n[Temp Check] Raise the onchain proposal quorum threshold from 40M\n\n[RFC] Delegate UNI to delegates qualified for cycle 2 rewards\n\nBlockworksResearch\n\nSeptember 17, 2024, 6:21pm\n\n2\n\nIn the long run there may be some concerns around the legal responsibility of security council dynamics. It’s very easy to imagine a world where a DAO’s security council (or in this case, Veto council) is deemed legally responsible for the rest of the DAO, and so we’re a bit wary of this option.\n\nThe best solution in face of regulatory uncertainty may be to look for more implicit voting dynamics that make governance attacks more difficult. Thus, we’d like to see further exploration of the proposal staking method. A couple immediate thoughts:\n\nIs there any situation where the DAO could find itself “bricked”, as in unable to push any more votes because of a new hostage situation?\n\nThe other possible problem for proposal staking is that a non-malicious controversial proposal could still be slashed. While we don’t think that people will go about slashing proposals they don’t like, it’s a possibility.\n\nStill, generally speaking, we’re in favor of the latter, though how would this be enforced operationally? This cannot be done on Snapshot, so there would have to be a specific Tally integration for this to be possible.\n\nUltimately, this all falls back onto voting dynamics. Compound’s problem was that it had some very large delegates that were inactive, and while incentive programs are great for maintaining participation among key delegates, there will be ways to usurp those programs as well. Thinking aloud here, but maybe we should rethink participation in the DAO, as in have some fall back system for which non-voting delegates can have voting power redistributed upon a certain participation threshold. This wouldn’t be forceful with their own voting power, only voting power delegated to them from other parties.\n\n3 Likes\n\nAbdullahUmar\n\nSeptember 17, 2024, 7:40pm\n\n3\n\nWhile it’s important that the DAO keeps governance security top of mind, implementing safeguards such as a guardian are very much circumstantial. As of today, Uniswap is in a much stronger position than most other DAOs. Voter apathy at the onchain level is not a significant problem either. There has not been a proposal that failed to pass due to voter apathy in the past, and scarcely does this occur even at the offchain level. I think the last time an offchain proposal failed snapshot due to apathy was over a year ago. Delegates are getting paid. Plus the treasury delegates votes, too. The economic value for onchain quorum is high (relative to other DAOs). Proposal threshold is also high. And there are measures like a timelock delay that inherently increase the risk for a proposer to drain the treasury. Plus, unlike Compound, there aren’t user funds at risk. Uniswap DAO only has jurisdiction over so many functions.\n\nI would suggest keeping a keen eye on existing parameters as opposed to introducing alternative vectors that increase risk surface area in other ways. For instance, the proposal threshold today is 1M UNI, and the timelock delay is like 2 days. Increasing the the proposal threshold and the timelock delay collectively make it more difficult for a drain to occur since the attacker is essentially holding on to a lump of sand; a longer delay period allows the market to dump the native token, and a higher proposal threshold would make the economic cost of posting that proposal more expensive since the value of, say that 1M UNI, would be falling in that timelock delay phase.\n\nThis topic should be carefully visited over time though, especially if the treasury aims to diversify. In the treasury working group research draft we mention this concern:\n\n\"\n\nBeyond altering the fee switch function, Uniswap governance importantly has the ability to withdraw UNI tokens from the treasury. As of today, since the treasury is entirely consistent of native tokens, the financial benefit for an attacker is uncertain. The mere cost of swaying, either through direct purchase or bribes, votes towards draining the treasury is simply too high at the moment, with a 40M UNI quorum currently standing at $240M (@ $6 per UNI). Enough time can also elapse before the native token devalues to nearly zero if a governance attack were to occur. The 2+ day timelock delay, for instance, allows for existing token holders to liquidate their holdings, making it increasingly expensive for an attacker to continue holding UNI. However, as the DAO’s treasury diversifies into non-native assets, the value of the treasury becomes increasingly appealing for malicious actors. It is therefore imperative for treasury diversification initiatives to coincide with consistent improvements in governance security.\n\nTo effectively manage the growing complexity of DAO security as treasuries become more valuable and diversified, governance parameters should be reviewed regularly by delegates. Malicious actors take advantage of stale or inadequate voting thresholds, low participation rates, or concentrated voting power. Therefore, vigilance in updating governance mechanisms is critical to mitigating risks. This is especially important if the native token sustains its lack of utility and value accrual for it may increase price suppression as well as likelihood of frustrated UNI holders accepting bribes.\n\nIn a scenario where a fee switch is not active and the treasury is increasing its non-native token holdings, the DAO can, for instance, increase its quorum level to accommodate for the likelihood of an attack. Programs such as delegation using the treasury’s native tokens is another method for allocating votes to community-trusted entities. If the non-native token value of the treasury exceeds the total value of delegated votes, a metric that ideally needs to be adjusted based on average voter participation rate, the expected value of a treasury drain increases. As per the below graph, this has never been an issue for Uniswap—but must be considered once treasury diversification offers.\n\nTreasury tokens can also be allocated toward rewarding consistent voting, participation in governance proposals, or for attracting new delegates. Voter engagement must be seen as a critical expenditure item, directly linked to the long-term security of the DAO’s treasury.\n\nIf voter apathy is unchecked, the barriers to passing malicious proposals will diminish. Therefore, incentivizing governance is not merely a budget item—it is a safeguard against treasury vulnerabilities. For these reasons, the Uniswap DAO has been allocating incentives to socially-responsible delegates since June 2024, and we forecast such programs to remain present for the foreseeable future. A lack of a circuit breaker for malicious votes via a guardian or emergency shutdown mechanisms—like those in MakerDAO—only increases the need for active delegates to monitor parameters and protect the treasury.\n\n\"\n\n3 Likes\n\nbendi\n\nSeptember 18, 2024, 9:25pm\n\n4\n\nOn behalf of ScopeLift, I’m against the introduction of a Veto Council. Such a measure is extremely centralizing and should be looked at as a last ditch, temporary solutio. While some DAOs are in fact facing such a situation now, and while many more (including eventually Uniswap) will face it in the future if we don’t take proper steps to align and incentivize token holders and delegates, it is currently not the case.\n\nI’m open to the idea of proposal staking, and other DAOs are experimenting with this (notably ENS), however such a solution is ultimately just a speedbump for a serious attacker. Any bond requirement placed upon proposers would be much less than what a genuine attacker would be able to gain should they take control of Governance.\n\nFor now, Uniswap DAO is secure, and should not accept a centralizing, risky hack. Instead we should focus on sustainable long term solutions, like delegate compensation, UniStaker adoption, and governance minimization.\n\n2 Likes\n\nGLI -- Treasury Delegation Round 2 Applications\n\ndrllau_LexDAO\n\nSeptember 19, 2024, 3:19am\n\n5\n\nMy question is whether the real issue is structural, mechanics, or procedural?\n\nQuestion of Procedural guardrails\n\nExactly what proposals get listed for voting and subsequent execution? I would think there are checks and balances for\n\nNormal/Routine - threshold (eg less than XYZ), within previous scope, passed temp check\n\nExemption - something which breaks the norms but may require special consideration, longer debate or emergency consideration\n\nException - things which are significant or structural. I’d note that investors have to have mechanism for rage-quitting … There may be penalties involved for early withdrawal but it should be clear at start what pooling the funds and whether there are legal restrictions\n\nIssue of Mechanics\n\nAt the moment the distribution of tokens acts as a functional electoral college (cf HK). But you can have alternatives to Roman voting (yes/no) … For example Kiwi voting using the loom.io approach allows for yes/no/veto/abstain with rules on what a veto does (strong objection as against some policy). Greek voting allows for contentious but popular decisions to be considered by an expert panel. And of course the various web3 attempts like conviction voting (the proposal that timelocked the longest has greater weight) or holographic voting. These all fall under decision science mechanism design and can be assessed rationally (and not argument by analogy). Aragon sought external investment and when the punters saw nothing being done, they got sick of waiting, hence rage-quit so the context is different.\n\nStructural\n\nIf you create new pre-emptive rights or even allow layers of ratification (a la intercession by courts/trust protectors) it alters the balance of power … This may be deliberate but should not be casually done.\n\nDelegation != Abdication … If you wish to “donate” funds to a cause, then make sure someone keeps an eye on any adverse 51%yakuzi style “proposals” https://en.m.wikipedia.org/wiki/Sōkaiya\n\nTane\n\nSeptember 19, 2024, 3:28am\n\n6\n\nThank you @jengajojo for proposing measures regarding the very important issue of governance attacks.\n\nWe think that, considering the current state of the Uniswap DAO, the two options currently proposed change the voting dynamics too much.\n\nFirst, regarding establishing a Veto Council, we believe that giving such strong power to certain DAO participants affects other participants too significantly. We assume that if a rigorous selection is made from the delegates currently participating in the DAO, honest members will be chosen. However, we are concerned that the power balance between the selected and unselected delegates may lower the health of the DAO. Even if the selected members cannot abuse their power, there is a risk that other participants might hesitate to voice strong opinions to members who can reject on-chain votes or become overly compliant with their views.\n\nNext, we think that introducing Proposal Staking is a milder measure than the above method, but we have two concerns. First, we doubt whether staking a small amount of UNI can effectively prevent governance attacks in advance. We couldn’t envision a situation where staking a small amount of UNI would deter attackers when targeting a very large DAO like Uniswap. Second, the potential limitation of proposal creators due to the introduction of this system; after this system is implemented, delegates with low VP may find it difficult to create on-chain votes, possibly leading to an increase in instances where they have to ask larger delegates to create on-chain votes on their behalf. This could accelerate the power gradient, similar to our concerns with establishing a Veto Council, and lead to the unhealthiness of the DAO.\n\nWe believe that instead of such major system changes, we should first implement simple measures that can strengthen governance. For example, increasing the quorum of on-chain voting or extending the time-lock period. Although these changes might introduce significant alterations to the contract, they would have less impact on the DAO’s dynamics and may allow for measures without lowering the health of the DAO.\n\njengajojo\n\nSeptember 20, 2024, 2:15pm\n\n7\n\nThank you @BlockworksResearch @drllau_LexDAO @Tane @AbdullahUmar @bendi for the thoughtful feedback and insights. It’s clear that governance security is a top priority, but opinions differ on the right approach. Here are the common themes we have identified from the discussion:\n\nMost commenters agree that a Veto Council could centralise power and disrupt the balance between delegates, making it a last-resort solution rather than a first step.\n\nMany are open to Proposal Staking, but there are concerns that staking a small amount of UNI won’t effectively deter serious attackers, and that it could discourage smaller delegates from participating.\n\nSeveral commenters prefer smaller, incremental changes, such as increasing the quorum or extending the time-lock period, strengthening governance without drastically altering the current structure.\n\nSuggested Action Items:\n\nGiven the strong concerns about centralisation, it seems best not to pursue this option at the moment.\n\nWhile it’s seen as a ‘speedbump’, further exploration of Proposal Staking is warranted. We can explore adding the functionality of the ProposalBond to the UNI Governor that would allow a proposer to propose with a lower threshold, and then the community could vote [For, Against, Veto and slash,Abstain]. If the weight of VetoandSlash > Against, then the proposer does not get their bond back and the proposal does not pass.\n\nThere seems to be support for increasing the quorum and extending the time-lock period as simpler, effective measures to protect against governance attacks we shall explore bringing these proposals to the DAO.\n\nRegularly reviewing and updating governance mechanisms, particularly as the treasury diversifies, should be prioritised to stay ahead of potential risks.\n\nWhat do you all think?\n\n2 Likes\n\neek637\n\nSeptember 21, 2024, 1:15pm\n\n8\n\nValuable conversation here, thanks for getting it going @jengajojo. The UF recently gave a grant to a team to do a governance audit. The output will be a description of the current risk vectors, strategies for risk mitigation, and a dashboard to monitor the on-chain drivers of risk. I’d suggest waiting for those results before introducing any proposals to change our governance structure.\n\n4 Likes\n\nggmatch\n\nSeptember 21, 2024, 6:29pm\n\n9\n\nIs the any particular reason why you forsee a governance attack in the next 18 months specifically?\n\nTo me it seems that the centralization risks outweight the pros.\n\n1 Like\n\nWintermuteGovernance\n\nSeptember 23, 2024, 6:35am\n\n10\n\nReally great to see this discussion happening thanks @jengajojo\n\nWe certainly agree that now more than ever, governance attacks are becoming more credible and DAOs should be doing more to protect against such attack vectors.\n\nWe echo a lot of the same thoughts highlighted by other comments and delegates and will focus our attention on your response:\n\nWe are not convinced that Proposal Staking will significantly deter an attacker and it ultimately creates more friction for regular day-to-day governance. The Proposal Bond would need to be sufficiently large enough to drastically reduce the profit of an economic attack, it is simply just an additional cost to the attacker (assuming they are very confident they can pass the proposal). By having a lower proposal threshold to make it easier for delegates, we are reducing this cost. Furthermore, it also requires proposers/delegates to hold a notable amount of UNI to put up as a bond which is not ideal (assuming you slash from a bond and not delegated VP)\n\nIncreasing the Quorum should be explored and we look forward to the analysis that the UF has funded as mentioned by @eek637. Looking at all non-cancelled onchain proposals below, our initial thoughts are that there is some room to increase it, however, this should be combined with efforts to further increase delegated UNI VP as we don’t want to end up in a situation where it’s extremely difficult to pass proposals.\n\nimage1128×1034 24.8 KB\n\nRegarding increasing the time lock, we are unsure of its efficacy. In most cases, Timelocks were created to allow for Veto Councils to intervene and/or allow users of the relevant protocol to exit the system if they do not agree with the changes. In Uniswap’s case, governance is largely minimised and doesn’t really affect users. Increasing the Timelock delay also delays the DAO’s ability to respond to any bugs or exploits across relevant gov controlled contracts. Lastly, it could be fair to assume that an attacker could be hedging their position (buying spot, selling perps) in which a declining UNI price is not as important as it seems. In this case, an attacker’s costs are likely the funding rate and slippage to enter + exit their position.\n\n3 Likes\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nURGENT discussion on current vote: \"Reduce UNI Governance Proposal & Quorum Thresholds\"\n\nRequests for Comment\n\n144\n\n12823\n\nNovember 17, 2021\n\nProposal 1: Feedback/Discussion for going forward\n\nUncategorized\n\n18\n\n3038\n\nOctober 21, 2020\n\n[proposal] giving Uniswap governance to long term UNI holders\n\nRequests for Comment\n\n8\n\n3119\n\nNovember 16, 2020\n\nProposal: Reduce amount of UNIs required to submit governance proposal\n\nRequests for Comment\n\n105\n\n17151\n\nNovember 25, 2021\n\nMobilizing the Uniswap Treasury\n\nRequests for Comment\n\n27\n\n6238\n\nJuly 20, 2024","tokens":5515,"crawled_at":1791193472995}
+{"id":10244,"url":"https://stack.olas.network/open-autonomy/configure_service/service_configuration_file","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"The service configuration file - Olas Stack Developer Documentation","text":"The service configuration file\n\nThe AI agent configuration file service.yaml is a YAML file where the main attributes of the AI agent are set up, including the particular agent blueprint that defines the AI agent. An important feature of AI agent configuration files is that they can override attributes defined in agent blueprint or component configurations.\n\nThe structure of the AI agent configuration file\n\nThe AI agent configuration file service.yaml is typically composed of AI-agent-specific attributes followed by additional YAML documents. Each additional document overrides the parameter of a specific agent blueprint or component configuration used by the AI agent, and they must begin with ---.\n\nExample\nHere is an example of the AI agent configuration file of the Hello World AI agent:\n\nservice.yamlname: hello_world\nauthor: valory\nversion: 0.1.0\ndescription: A simple demonstration of a simple ABCI application\naea_version: '>=2.0.0, <3.0.0'\nlicense: Apache-2.0\nfingerprint:\nREADME.md: bafybeiapubcoersqnsnh3acia5hd7otzt7kjxekr6gkbrlumv6tkajl6jm\nfingerprint_ignore_patterns: []\nagent: valory/hello_world:0.1.0:bafybeig6p6shyx6wmih2xlzu3h6rd7gul3fxqhpdoi77qidqmpzxf33spm\nnumber_of_agents: 4\ndeployment: {}\ndependencies: {}\n---\nextra:\nbenchmark_persistence_params:\nargs: &id001\nlog_dir: /benchmarks\npublic_id: valory/hello_world_abci:0.1.0\ntype: skill\n0:\nmodels:\nparams:\nargs:\nhello_world_message: ${MY_HELLO_WORLD_MESSAGE:str:HELLO_WORLD_AGENT_0}\nbenchmark_tool:\nargs: *id001\n1:\nmodels:\nparams:\nargs:\nhello_world_message: ${MY_HELLO_WORLD_MESSAGE:str:HELLO_WORLD_AGENT_1}\nbenchmark_tool:\nargs: *id001\n2:\nmodels:\nparams:\nargs:\nhello_world_message: ${MY_HELLO_WORLD_MESSAGE:str:HELLO_WORLD_AGENT_2}\nbenchmark_tool:\nargs: *id001\n3:\nmodels:\nparams:\nargs:\nhello_world_message: ${MY_HELLO_WORLD_MESSAGE:str:HELLO_WORLD_AGENT_3}\nbenchmark_tool:\nargs: *id001\n---\npublic_id: valory/ledger:0.19.0\ntype: connection\nconfig:\nledger_apis:\nethereum:\naddress: http://host.docker.internal:8545\nchain_id: 31337\npoa_chain: false\ndefault_gas_price_strategy: eip1559\n\nAs you can see, the AI agent configuration file is overriding some attributes for the skill valory/hello_world_abci and the connection valory/ledger.\nAlso, note how the attributes hello_world_message read their value from the environment variable MY_HELLO_WORLD_STRING of type string, and take a default value if they are not defined.\n\nThere are a number of mandatory attributes that define the AI agent, which are summarized in the table below:\n\nAttribute\nDescription\n\nname\n\nAI agent name. It shall not contain spaces.\n\nauthor\n\nAuthor name.\n\nversion\n\nAI Agent version, in the format <major>.<minor>.<patch>.\n\ndescription\n\nDescription of the AI agent.\n\naea_version\n\nOpen AEA version supported by the AI agent.\n\nlicense\n\nLicense identifier.\n\nfingerprint\n\nList with entries <file>: <hash> for all the files that compose the AI agent.\n\nfingerprint_ignore_patterns\n\nFilename patterns to be ignored.\n\nagent\n\nAgent blueprint, in the form <agent_public_id>:<version>:<hash>.\n\nnumber_of_agents\n\nNumber of agent instances that the AI agent is composed of.\n\ndeployment\n\nExternal deployment configuration for publishing container ports.\n\ndependencies\n\nPython dependencies to include in the runtime image publishing container ports.\n\nAI-agent-level overrides\n\nThe Open AEA framework already has the notion of component overrides: if a component uses another component, the former can override configuration values of the sub-component.\n\nSimilarly, the Open Autonomy framework has the notion of AI-agent-level overrides. You can define them in the AI agent configuration file service.yaml, which will be used to generate the deployment environment for the agent instances.\n\nAI-agent-level overrides follow the mandatory AI-agent-specific attributes, separated by ---.\nYou can, for example, override the default HELLO_WORLD! string that each agent instances prints on their console in the Hello World AI agent, which is originally defined in the hello_world_abci skill.\n\nservice.yamlname: hello_world\nauthor: valory\nversion: 0.1.0\ndescription: A simple demonstration of a simple ABCI application\naea_version: '>=2.0.0, <3.0.0'\nlicense: Apache-2.0\nfingerprint:\nREADME.md: bafybeiapubcoersqnsnh3acia5hd7otzt7kjxekr6gkbrlumv6tkajl6jm\nfingerprint_ignore_patterns: []\nagent: valory/hello_world:0.1.0:bafybeig6p6shyx6wmih2xlzu3h6rd7gul3fxqhpdoi77qidqmpzxf33spm\nnumber_of_agents: 4\n---\npublic_id: valory/hello_world_abci:0.1.0\ntype: skill\nmodels:\nparams:\nargs:\nhello_world_message: Hello world!\n\nNote that AI-agent-level overrides take precedence over agent-blueprint-level overrides, and agent-blueprint-level overrides take precedence over component-level overrides.\n\nOverrides precedence\n\nYou can define values for overridden attributes in two ways:\n\nDirectly assign a hardcoded value, for example:\n\nhello_world_message: HELLO_WORLD!\n\nUse an environment variable with a default value using the syntax\n\n<overridden_attribute>: ${<env_var_name>:<type>:<default_value>}\n\nfor example:\nhello_world_message: ${MY_HELLO_WORLD_MESSAGE:str:HELLO_WORLD!}\n\nIn this case, the environment variable MY_HELLO_WORLD_MESSAGE will be read by the agent instance in runtime. If not found, the default value HELLO_WORLD! will be used.\n\nMultiple overrides\n\nYou can override different values for different agent instances in the AI agent configuration file with the multiple override feature, using the pattern below:\n\nservice.yaml# (...)\n---\npublic_id: valory/hello_world_abci:0.1.0\ntype: skill\n<agent_number>:\n<overridden_attributes>\n\nImportant\n\nIf you choose to use the multiple override feature, you have to define overrides for every single agent instance that composes the AI agent.\n\nExample\nIf you wish that each agent instance outputs a different message in the Hello World AI agent with four agent instances, you can define the following multiple override in the service.yaml file:\n\nservice.yaml# (...)\n---\npublic_id: valory/hello_world_abci:0.1.0\ntype: skill\n0:\nmodels:\nparams:\nargs:\nhello_world_message: Hello, from agent instance 0\n1:\nmodels:\nparams:\nargs:\nhello_world_message: Hello, from agent instance 1\n2:\nmodels:\nparams:\nargs:\nhello_world_message: Hello, from agent instance 2\n3:\nmodels:\nparams:\nargs:\nhello_world_message: Hello, from agent instance 3\n\nIf you have repetitive overridden parameters, you can define them using YAML anchors under the section extra, and reference them when defining overrides for different agent instances.\n\nExample\nIn this example, we define a YAML anchor with label &id001 to avoid repeating the same configuration of the args parameter in all the agent instances.\n\nservice.yaml# (...)\n---\nextra:\nbenchmark_tool:\nargs: &id001\nlog_dir: /benchmarks\npublic_id: valory/hello_world_abci:0.1.0\ntype: skill\n0:\nmodels:\nparams:\nargs:\nhello_world_message: Hello, from agent instance 0\nbenchmark_tool:\nargs: *id001\n1:\nmodels:\nparams:\nargs:\nhello_world_message: Hello, from agent instance 1\nbenchmark_tool:\nargs: *id001\n2:\nmodels:\nparams:\nargs:\nhello_world_message: Hello, from agent instance 2\nbenchmark_tool:\nargs: *id001\n3:\nmodels:\nparams:\nargs:\nhello_world_message: Hello, from agent instance 3\nbenchmark_tool:\nargs: *id001\n\nSharing the same parameter across skills\n\nEach skill has its own models.params.args namespace — there is no implicit cross-skill binding, and BaseParams._ensure(key, kwargs, type_) pops key from the skill's own kwargs. Two skills that need the same value (e.g. an external API URL both read from and write to) must each declare the parameter in their respective skill.yaml, and keep the values in sync at the service level.\n\nThe idiomatic options, in order of preference:\n\nYAML anchor in service.yaml — declare the value once with &anchor and reference it with *anchor under each skill's overrides (same mechanism as the example above).\n\nEnvironment variable export — set one environment variable and let the service build pass it through the SKILL_<MODELS_PATH>_<ARG_NAME> path for each consuming skill (see the next section).\n\nAvoid renaming the parameter per-skill to dodge the sharing concern — it hides the logical relationship and makes service-level overrides harder to reason about.\n\nExport to environment variables\n\nWhen building the deployments, the overrides from the AI agent components are exported as system environment variables inside the Docker containers and picked up at runtime by the agent instances. The exported environment variables are labelled with their upper case JSON path:\n\n<COMPONENT_TYPE>_<UPPERCASE_ATTRIBUTE_PATH>=<value>\n\nNote that when deploying an AI agent, environment variables are defined separately within each agent instance container. Therefore, even if you use the multiple override feature to define a different value per agent instance, their respective environment variable within the container will have the same name.\n\nExample\nIf you have an override like\n\nservice.yaml# (...)\n---\npublic_id: valory/hello_world_abci:0.1.0\ntype: skill\nmodels:\nparams:\nargs:\nhello_world_message: Hello world!\n\nit will export the environment variable SKILL_MODELS_PARAM_ARGS_HELLO_WORLD_MESSAGE.\n\nOn the other hand, if you use the multiple override feature and you have something like\n\nservice.yaml# (...)\n---\npublic_id: valory/hello_world_abci:0.1.0\ntype: skill\n0:\nmodels:\nparams:\nargs:\nhello_world_message: Hello, from agent instance 0\n1:\nmodels:\nparams:\nargs:\nhello_world_message: Hello, from agent instance 1\n2:\nmodels:\nparams:\nargs:\nhello_world_message: Hello, from agent instance 2\n3:\nmodels:\nparams:\nargs:\nhello_world_message: Hello, from agent instance 3\n\nit will also export the environment SKILL_MODELS_PARAM_ARGS_HELLO_WORLD_MESSAGE within each agent instance container. However each such variable will have a different value inside each container, that is, Hello, from agent instance 0, Hello, from agent instance 1, etc.\n\nExported environment variables require such specific format because they are used by the constituent agent instances and skills. Read about component overrides in the Open AEA framework for more information.\n\nExport complicated data structures\n\nIf you have nested lists the environment export rules will differ as per the inner data structures. If the list is a strict list, meaning the inner values are either primitive data types like int, str, float or boolean, the list will be exported as a JSON string.\n\nExample\nIf you have an override like\n\nservice.yaml# (...)\n---\npublic_id: vendor/hello_world_abci:0.1.0\ntype: skill\nmodels:\nparams:\nargs:\nsimple_list:\n- 1\n- 2\n- 3\nnested_list:\n- - foo\n- bar\n- - \"hello\"\n- \"world\"\n\nit will export the environment variables\n\nSKILL_HELLO_WORLD_ABCI_MODELS_PARAMS_ARGS_SIMPLE_LIST='[1, 2, 3]',\n\nSKILL_HELLO_WORLD_ABCI_MODELS_PARAMS_ARGS_NESTED_LIST='[[\"foo\", \"bar\"], [\"hello\", \"world\"]]'.\n\nIf an overridden list contains mapping values, it will be exported as\n\n<COMPONENT_TYPE>_<UPPERCASE_ATTRIBUTE_PATH>_<MAPPING_INDEX>_KEY=<value>\n\nExample\nIf you have an override like\n\nservice.yaml# (...)\n---\npublic_id: valory/hello_world_abci:0.1.0\ntype: skill\nmodels:\nparams:\nargs:\nlist_with_mappings:\n- key: value_0\n- key: value_1\n\nit will export the environment variables\n\nSKILL_HELLO_WORLD_ABCI_MODELS_PARAMS_ARGS_LIST_WITH_MAPPINGS_0_KEY='value_0',\n\nSKILL_HELLO_WORLD_ABCI_MODELS_PARAMS_ARGS_LIST_WITH_MAPPINGS_1_KEY='value_1'.\n\nSo when defining the agent blueprint/component level overrides you will have to explicitly define all the elements of the list like this:\n\nservice.yaml# (...)\n---\npublic_id: valory/hello_world_abci:0.1.0\ntype: skill\nmodels:\nparams:\nargs:\nlist_with_mappings:\n- key: ${<env_var_name>:<type>:<default_value>}\n- key: ${<env_var_name>:<type>:<default_value>}\n\nPublish container ports\n\nWe use a syntax similar to Docker for port publishing. To expose agent instance container ports to host machine ports use the following configuration:\n\nservice.yaml# (...)\ndeployment:\nagent:\nports:\n<agent_id>:\n<host_machine_port>: <agent_container_port>\ntendermint:\nports:\n<node_id>:\n<host_machine_port>: <node_container_port>\n\nPort publishing also works with multiple overrides. For example if you want to map port 8080 of agent instance 0 to port 8081 of the host machine, use:\n\nservice.yaml# (...)\ndeployment:\nagent:\nports:\n0:\n8081: 8080\ntendermint:\nports:\n0:\n26656: 26656\n\nYou can also configure these mappings using environment variables:\n\nservice.yaml# (...)\ndeployment:\nagent:\nports:\n0:\n8081: ${AGENT_0_HTTP_PORT:int:8080}\ntendermint:\nports:\n0:\n26656: ${TM_NODE_0_P2P_PORT:int:26656}\n\nMount volumes for agent instance data\n\nCustom volumes can be mounted using the deployment configuration.\n\nservice.yaml# (...)\ndeployment:\nagent:\nvolumes:\n<host_dir>: <container_dir>\n\nOr specify volumes specific to agent instance\n\nservice.yaml# (...)\ndeployment:\nagent:\nvolumes:\n<agent_index>:\n<host_dir>: <container_dir>\n\nFor example, if you want to mount ./data directory as /data volume\n\nservice.yaml# (...)\ndeployment:\nagent:\nvolumes:\n./data: /data\n\nand\n\nservice.yaml# (...)\ndeployment:\nagent:\nvolumes:\n0:\n./data_0: /data\n1:\n./data_1: /data\n\nNote: When specifying the host directory path, use absolute path instead of relative path to avoid mounting related errors.\n\nOverride agent blueprint/component dependencies\n\nAI agent level dependencies can be defined using following format\n\nservice.yaml# (...)\ndependencies:\npypi-package:\nversion: ==1.0.0\ngit-package:\ngit: https://github.com/valory-xyz/open-autonomy\nref: 79342a93079648ef03ab5aaf14978068fc96587a\n\nThe dependencies defined at the AI agent level will take priority over the dependencies defined at the agent blueprint or component level. This means, if you define some dependency pypi-package==1.0.0 at the agent blueprint/component level and re-define it as py-package==1.1.0 at the AI agent level, py-package==1.1.0 will get installed when building the agent blueprint image following the AI agent > agent blueprint > skill > connection > contract > protocol priority order.","tokens":3480,"crawled_at":1791193491759}
+{"id":10245,"url":"https://docs.near.org/web3-apps/quickstart","domain":"docs.near.org","chapter":"layer1_layer2","title":"Your First Web3 App - NEAR Docs","text":"In this guide we will show you how to build a React app connected to NEAR, where users can login using their wallets and interact with a contract.\n\nSearching to integrate NEAR in your App?If you already have an application and want to integrate NEAR into it, we recommend you to first go through this guide and then check our documentation on integrating NEAR to a frontend\n\n​\n\nTemplate Setup\n\nIf you already have Node.js installed, you can use create-near-app to quickly setup a template:\n\nnpx create-near-app@latest\n\n# ✔ What do you want to build? › Web Application\n# ✔ Select a framework for your frontend › Next.js (Classic)\n# ✔ Name your project (we will create a directory with that name) … near-template\n# ✔ Run 'npm install' now? … yes\n\nOnce the folder is ready - and all dependencies installed - you can start the development server using pnpm.\n\ncd near-template # go to your project folder\nnpm run dev\n\nVisit http://localhost:3000 in your browser to view the dApp. Note that since the dApp uses NextJS the app might take longer to load the pages on first visit.\n\nThe app is not starting?\n\nMake sure you are using node >= v22, you can easily switch versions using nvm use 22\n\nFramework\nIn this tutorial we are using the Next.js framework with the “classic” page-based routing, but you can select other frameworks such as Vite when creating the app\n\n​\n\nLanding Page\n\nOnce the app starts you will see the landing page, rendering a navigation bar that allows users to login using their NEAR wallet. You can then navigate to the docs or the Near Integration page (which we will do).\n\nLanding page of Hello NEAR Gateway\nGo ahead and sign in with your NEAR account. If you don’t have one, you can create one on the fly.\n\n​\n\nContext Provider\n\nNext.js uses a template system, where each page is a React component. Our main logic is defined at ./src/pages/_app.js, which:\n\nCreates a NearProvider that wraps the entire application to provide NEAR functionality\n\nRenders the navigation menu and the page’s content\n\nLoading...\nSee code on GitHub\n\nWhat is NEAR Connect Hooks?\n\nNEAR Connect is a library that allows users to select their preferred NEAR wallet to login, our application uses hooks that wrap its functionality to make it easier to use\n\n​\n\nNavigation Bar\n\nThe navigation bar implements a button to allow users to login and logout with their NEAR wallet. The main logic comes from the useNearWallet hook, which exposes all wallet related functionality.\nLoading...\nSee code on GitHub\n\n​\n\nHow Do I Call Smart Contract Functions?\n\nNow that you understand how the landing page works, we can move to the Near Integration page, which retrieves a greeting from the hello.near-examples.testnet contract.\n​\n\nRead vs. Write Operations\n\nOperation TypeMethodCostRequires Signature\nRead (view)\nviewMethod()\nFree\nNo\n\nWrite (call)\ncallMethod()\nGas fees (~0.0001 Ⓝ)\nYes\n\nView methods query contract state without modifying it. Call methods change state and require the user to sign a transaction.\n\nView of the Near Integration page\nLogin if you haven’t done it yet and you will see a simple form that allows you to store a greeting in the smart contract.\n\n​\n\nFunction Call Hooks\n\nJust like the navigation bar, we use the useNearWallet hook to get functions that allow us to call methods on the contract:\n\nviewFunction is used to call functions that are read-only\n\ncallFunction is used to call functions that modify the state of the contract\n\nLoading...\nSee code on GitHub\n\n​\n\nCalling Read-Only Methods\n\nFor example, when we want to fetch the current greeting stored in the contract, we use viewFunction inside a useEffect hook:\nLoading...\nSee code on GitHub\n\n​\n\nCalling Change Methods\n\nOn the other hand, when the user submits a new greeting, we use callFunction to send a transaction to the contract:\nLoading...\nSee code on GitHub\n\n​\n\nCommon Questions\n\n​\n\nDo users need NEAR tokens to login?\n\nNo. Wallet login is free. Users only pay gas fees when they call contract functions that modify state.\n​\n\nWhat wallets can users connect with?\n\nNEAR wallets (MyNearWallet, Meteor, HERE Wallet) and Ethereum wallets (Metamask, WalletConnect, Coinbase Wallet via EVM support).\n​\n\nHow do I avoid users signing every transaction?\n\nCreate a function-call access key by setting createAccessKeyFor: <contract-name> in the wallet selector config. This allows the app to sign non-payable methods automatically.\n​\n\nCan I use this with an existing React app?\n\nYes. Install near-connect-hooks and follow our integration guide.\n​\n\nWhy Next.js instead of plain React?\n\nNext.js is recommended but not required. You can use Vite/React, Vue, Svelte, or any framework. Check create-near-app templates for options.\n\n​\n\nMoving Forward\n\nThat’s it for our quickstart tutorial. You have now seen a fully functional frontend that can talk with NEAR contracts and render Web3 components.\nWas this page helpful?","tokens":1218,"crawled_at":1791193508042}
+{"id":10246,"url":"https://stack.olas.network/open-autonomy/configure_service/analise_test","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Analise and test - Olas Stack Developer Documentation","text":"Analise and test\n\nWhen developing your AI agent (and its required components, including the FSM App), it is important to ensure that the code is exhaustively tested and adheres to best practices. This will not only help identify and fix any bugs or errors early, but also ensure your code is reliable, efficient, and maintainable.\n\nStatic code analysis\n\nStandard tools\n\nFor convenience the Dev template comes with a Pipenv that includes a number of tools grouped under predefined make targets.\n\nMake target: make formatters\n\nTool\nDescription\n\nblack\n\nA Python code formatter that automatically reformats code to conform to a consistent style.\n\nisort\n\nA Python tool that sorts imports alphabetically and separates them into sections, making it easier to read and maintain import statements in Python code.\n\nMake target: make code-checks\n\nTool\nDescription\n\ndarglint\n\nA Python docstring argument linter that checks for adherence to Google's style guide.\n\nmypy\n\nA static type checker for Python that analyses code and provides feedback on variable types and potential errors.\n\nflake8\n\nA Python tool that combines multiple linters to check code for syntax errors, style violations, and other issues.\n\npylint\n\nA Python code analyser that checks code for potential errors, security vulnerabilities, and style violations, and provides feedback on how to improve code quality.\n\nvulture\n\nA Python tool that analyses code for unused variables, functions, and other dead code that can be safely removed to improve code quality and performance.\n\nFramework-specific tools\n\nIn addition, the framework comes with a number of dedicated tools that you might find useful for analysing your AI agent and component packages.\n\nautonomy check-packages\nPerforms several consistency checks on the component packages to make sure there are no issues with the component configurations (including checking that every package has existing dependencies and a non-empty description).\nautonomy analyse handlers\nThis command verifies that all the FSM App skills in a local registry (except the explicitly excluded ones) have defined the specified handlers. See the command documentation here.\nautonomy analyse dialogues\nThis command verifies that all the FSM App skills in a local registry (except the explicitly excluded ones) have defined the specified dialogues. See the command documentation here.\nautonomy analyse service\nThis command verifies an AI agent configuration to see if there is any potential issue with it which can cause issues when running the AI agent deployment. See the command documentation here and the on-chain deployment checklist for more information.\n\nTesting\n\nUnit testing\n\nThe valory/abstract_round_abci skill packages come with a number of testing tools located in packages/valory/skills/abstract_round_abci/test_tools which you can use to write unit tests for your FSM Apps.\n\nExample\nFetch the hello_world agent blueprint, which comes with the hello_world_abci FSM App skill within:\n\nautonomy fetch valory/hello_world:0.1.0:bafybeidkuptt5jvtsetgqfbj3detp7zne7z67bi3rkxh43q5thbsz3pwsy --alias hello_world_agent\n\nLook at the unit tests for the hello_world_abci skill, located in the folder\n\n./hello_world_agent/vendor/valory/skills/hello_world_abci/tests/\n\nIntegration testing\n\nThe open-aea-test-autonomy plugin provides several test classes which can be utilized for various Docker integration tests. Here are some examples of the base test classes:\n\naea_test_autonomy.base_test_classes.BaseContractTest: Comes with utilities required for testing a contract.\n\naea_test_autonomy.base_test_classes.BaseGanacheContractTest: Can be used for testing contracts on a local Ganache instance.\n\naea_test_autonomy.base_test_classes. BaseRegistriesContractsTest: Launches a local Hardhat node with pre-deployed Autonolas registries contracts image.\n\nEnd-to-end testing\n\nThe same plugin also provides tools for writing end-to-end tests for agent blueprints. The aea_test_autonomy.base_test_classes.agents.BaseTestEnd2End class provides an environment for testing agent instances end to end.\n\nExample\nFetch the hello_world agent blueprint:\n\nautonomy fetch valory/hello_world:0.1.0:bafybeidkuptt5jvtsetgqfbj3detp7zne7z67bi3rkxh43q5thbsz3pwsy --alias hello_world_agent\n\nLook at the end-to-end tests, located in the folder\n\n./hello_world_agent/tests/\n\nThe framework also provides CLI tools for building and running local testing deployments.\nYou can include additional images in your testing deployment, for example, a Hardhat node with custom contracts, or an ACN node. This is achieved through the flags --use-hardhat and --use-acn, respectively. Read the autonomy deploy build command documentation and the guide for using custom images in a deployment for more information.","tokens":1189,"crawled_at":1791193510511}
+{"id":10247,"url":"https://a16zcrypto.com/posts/article/getting-bugs-out-of-snarks","domain":"a16zcrypto.com","chapter":"research","title":"Getting the bugs out of SNARKs: The road ahead - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nGetting the bugs out of SNARKs: The road ahead\nJustin Thaler\n11.20.24\n\nTags & Share Tags\nJolt\nresearch\nSNARKs\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nIn the blockchain world, SNARKs hold the promise of unparalleled scalability and enhanced privacy compared to today’s transparent ledgers. Yet the current reality is that SNARK implementations are riddled with bugs, providing security through obscurity rather than robust cryptographic guarantees. Achieving true security requires formal verification — proof that SNARK systems are bug-free. This post briefly reviews progress on Jolt, our zkVM for RISC-V, and then discusses our efforts toward formal verification.\n\nzkVMs and Jolt: A short recap\n\nzkVMs are SNARKs that allow an untrusted prover to prove that it correctly ran some specified computer program on a witness, where the program is specified as bytecode conforming to a particular instruction set architecture (ISA) like RISC-V.\n\nzkVMs offer the most promising path to usable and maintainable SNARKs. They allow developers to write programs in whatever high-level language they please, so long as the language comes with a compiler down to the ISA’s bytecode. Developers need not express computations directly as circuits or constraints, or even within “zkDSLs.” Those building the zkVMs will deal with the nastiness of constraint systems and circuits once and for all, meaning that anyone can then use the zkVM without any knowledge of how the proof machinery actually works.\n\nIn April 2024, we released an initial implementation of the Jolt zkVM for RISC-V and showed its performance compares favorably to alternatives. Our initial findings have since been confirmed by several other benchmarks. Since then, we have dramatically reduced Jolt’s proof size (from several MBs to 200 KBs, and as low as 35 KBs at the cost of slightly increased prover time) and incorporated additional features like support for the Rust standard library and the RISC-V Multiplication extension.\n\nSoon, I expect Jolt to be the only RISC-V zkVM capable of proving in resource-constrained environments (under 2GB of prover space, compared to 8-16 GBs for RISC Zero and more for SP1), while also achieving state-of-the art prover time.\n\nBut this post is not about Jolt’s performance or feature support. It’s about a more important topic: correctness and security. This post lays out our roadmap toward the long-term goal of obtaining a formally verified Jolt implementation and describes the initial steps we have already taken along this path.\n\nA key risk for SNARKs\n\nBugs and catastrophes\n\nThe slightest bug in a SNARK toolchain can lead to catastrophic security failures. For example, a single missing or improperly specified constraint could mean that the prover does not actually know the witness that it claims it knows (e.g., does not actually know the secret key controlling the Ethereum wallet initiating a purported blockchain transaction).\n\nUntil we have confidence that our toolchains are completely bug free, projects using SNARKs cannot really be secured by the SNARK itself. At best, they are secured by obscurity: finding the bugs may require expertise (to identify missing or malspecified constraints, or any other bug in the tool-chain used to deploy the SNARK). But the bugs are there — and that likely means a motivated adversary can find convincing proofs of false statements.\n\nThe very worst-case situation is that we think our SNARK toolchains are bug-free, and therefore stop treating SNARKs as but one of many layers of a system of defense-in-depth. These other layers of security will be semi-centralized. In the context of rollups, this may mean using an allowlist of who can submit proofs, the use of TEEs, or a security council that can “undo” acceptance of buggy proofs, likely at the substantial cost and chaos of also “undoing” many transactions that network participants believed to have been already confirmed.\n\nThe long-term prospects are bright, but far off\n\nOver the long term, zkVMs will have implications not just for SNARK usability, but also for correctness. If we develop confidence that the zkVM itself is bug free, and ensure that the program bytecode on which the zkVM is applied correctly implements the intended witness-checking procedure, then the end-to-end toolchain will also be bug free.\n\nThe Ethereum Foundation is investing heavily to bring this endgame to reality — but it is years away. In fact, I consider it a distinct possibility that in five years’ time, we still don’t have strong confidence that any performative zkVM toolchain is actually bug free.\n\nToday, zkVM toolchains are almost certainly full of bugs. We should stop pretending they’re not. To give a sense of how complicated they are, consider the following:\n\nThe Jolt codebase is up to 34,000 lines of Rust code (if you don’t count the SDK or the RISC-V emulator, it’s “only” about 25,000 lines), plus it uses some functionality from arkworks, namely field, group, and pairing operations. SP1 is over 60,000 lines of Rust code (closer to 100,000 if you include the proof system it invokes, plonky3), plus thousands of lines of Go code, and several hundred lines of assembly code. RISC Zero’s codebase is even bigger, with over 100,000 lines of Rust code, almost 200,000 lines of C++, 150,000 lines of CUDA, 400 lines of assembly, and more. (All of these statistics were obtained using the cloc –vcs git command to count lines of code.)\n\nOf course, most of these lines of code are devoted to implementing the zkVM prover, yet for security guarantees only the zkVM verifier needs to be correctly implemented, and the verifier can be much simpler than the prover. Still, these statistics give a sense of the complexity of these systems, and even the verifier implementations are many thousands of lines of code.\n\nGiven this state of affairs, simplicity is a major virtue in any zkVM, and we firmly believe that Jolt is the simplest zkVM for RISC-V today. But formal methods are not some magic wand that can be waved at any piece of software and magically make all the bugs go away. Major technical challenges will have to be overcome to get any kind of guarantee that zkVM toolchains are end-to-end correct and secure. Simplicity in zkVMs is not only important in the short term; it will ease these formal verification efforts and remain a virtue for many years to come.\n\nRoadmap to a bug-free Jolt\n\nNear-term efforts (complete and in-progress)\n\nIn the intermediate term, there is no substitute for audits and bug-finding efforts. Jolt has not yet undergone a full audit, but it has been subjected to considerable scrutiny. Recently, the zkSecurity team found several bugs in Jolt. These bugs were not in the “guts” of the proof machinery but rather in how inputs and outputs are processed, how Jolt makes sure the prover actually ran the computer program to completion rather than “stopping it early,” and in allowing the prover to specify certain parameters that should instead be specified by the verifier or another honest party. (See zkSecurity’s companion post for additional details on the bugs and how they found them.)\n\nBeyond bug-finding efforts, we have taken the first steps along the (very) long road to a formally verified Jolt implementation. First, one major reason for Jolt’s simplicity is its lookup-centric design: Rather than expressing each primitive instruction of the VM as a circuit or constraint system, Jolt instead “decomposes” each instruction into a handful of lookups into small lookup tables and then uses our Lasso lookup argument to verifiably perform the lookups. With Carl Kwan and Quang Dao, who are leading Jolt’s formal verification efforts, we have used the ACL2 automated theorem prover to verify the correctness of Jolt’s lookup decompositions. This formalization is highly automated, which means the techniques will be easy to extend to different, richer ISAs than RISC-V, should the community prove interested in them down the line. These verification efforts have also led to modest performance improvements to Jolt, by identifying, in an automated fashion, some unnecessary lookups we were doing for a handful of primitive RISC-V instructions.\n\nSecond, Quang and collaborators Gregor Mitscha-Baude from zkSecurity and Devon Tuma are using Lean to verify the soundness of the Spartan, Lasso, and Spice polynomial IOPs (PIOPs) at the heart of Jolt. This work will extend broadly to all PIOPs used in practice, not only those used in Jolt. This work will likely be complete by the middle of 2025. As with all of Jolt, it’s being done in the open, and you can follow along with Quang’s progress at his ZKlib repo. This effort is one of the projects recently funded by the Ethereum Foundation’s formal verification project.\n\nA third step is to verify (assuming the soundness of the polynomial IOPs above) that the constraint system to which Spartan is applied in Jolt, combined with the lookups and reads/writes to memory that Jolt applies Lasso and Spice to, together capture the RISC-V ISA. This effort consists of first building a formal RISC-V model in ACL2 (which is done), and then using ACL2 to verify the equivalence of the model to Jolt’s combination of constraints, lookups, and memory operations (which is in progress).\n\nLonger-term efforts\n\nConverging on a theorem prover\n\nWe plan to port over all of our ACL2 formalizations to Lean. Lean is newer and less mature than ACL2 but has more community support/libraries for mathematics, and more momentum within the SNARK community (e.g., a large part of the Ethereum Foundations’s zkEVM verification effort is expected to be in Lean). Most of our initial efforts have used ACL2 in large part to take advantage of its extensive support of automated techniques like bit-blasting (e.g., bitvector reasoning via passing to a SAT solver) and rewriting. Lean recently added support for rudimentary bit-blasting, so long-term it may make sense to shift the entire effort to Lean.\n\nVerifying the actual Jolt implementation\n\nA major long-term challenge is to actually verify the Rust implementation of the Jolt verifier (much less an on-chain implementation of the same, via Solidity or EVM bytecode). We haven’t really begun to make headway here. Jolt is really just a polynomial IOP for proving correct execution of RISC-V programs, and our efforts to date have mainly focused on making sure the polynomial IOP is secure, not that the Rust implementation of Jolt correctly implements the polynomial IOP. The main exception to date: We have, via fuzzing, validated that the lookup decompositions we’ve formalized in ACL2 match the decompositions implemented in Jolt’s Rust codebase.\n\nHere, we will need good tooling to ensure the correctness of Rust code (according to certain specifications). There are many potential approaches for enabling this including tools such as Restricted Algorithmic Rust (RAR), Aeneas, Verus, and others. Another possible approach is to circumvent the issue of Rust programming altogether. Many theorem provers (e.g., ACL2, Lean, Coq) support code extraction to certain target languages (e.g., OCaml, C, Lisp), and Rust may be supported in the future. A major issue with code extraction is that often the “cross-compilation” step is itself unverified. One unique advantage of ACL2 is that execution in the theorem prover is the same as native Common Lisp execution, so a “formally-verified Jolt verifier” in ACL2 can be called as needed, requiring no cross-compilation to a target language. Overall, I would not be surprised if we only seriously target this essential direction 1.5 years or more from now. A silver lining of this timeline is that Rust tooling will mature considerably in the meantime.\n\nIn the meantime, as we verify the correctness of various components of Jolt’s polynomial IOP and constraint systems using Lean/ACL2, we’ll extensively test for compliance of the verified models with Jolt’s Rust code. This is the approach that we took in verifying Jolt’s lookup decompositions. Though it falls well short of the end goal of a “formally verified Rust verifier,” it does let us gain confidence in the correctness of different parts of the Jolt codebase.\n\nA DSL for all “constraints” used in Jolt\n\nUnlike other zkVMs, which mainly use so-called Plonkish or AIR constraint systems to capture VM execution, Jolt uses a combination of rank-one constraints (R1CS) and “offline memory checking” techniques via Lasso and Spice that check that the prover is correctly performing reads into read-only memory (aka lookups) and read-write memory (aka registers and RAM), respectively.\n\nCurrently, the Jolt implementation specifies the above constraints/lookups/memory operations in ad hoc fashion. For R1CS specification, we were initially using Circom, but due to untenable overheads, we hand-rolled our own R1CS specification language and vertically integrated it into Jolt. Likewise, lookups and reads and writes of registers and RAM are specified via internal APIs.\n\nFor maintainability and continued verification as Jolt evolves, it would be good to have a single DSL that cleanly captures R1CS, lookups, and registers/RAM. This will also be useful for pre-compile specification. (Like Jolt itself, pre-compiles in Jolt will consist of a mix of R1CS, lookups, and arithmetic circuits to which the GKR protocol can be applied.) We are working with Galois to take steps in this direction.\n\nFormal verification and controlling prover memory\n\nA challenge for formal verification efforts is the heavy use of SNARK recursion in today’s zkVMs. To keep the prover’s space bounded (i.e., avoid needing terabytes of space to prove even toy program executions) and to reduce proof size, the standard procedure today is to break VM executions into “shards,” prove correct execution of each shard, and then recursively aggregate the proofs. This requires turning a SNARK verifier into a circuit or constraint system, and proving that one knows a satisfying assignment for the circuit. Any error in the specification of the circuit can lead to catastrophic security failures. And from a usability perspective, recursion simply makes it very hard for the public to tell what statement is actually being verified. No longer is the prover simply proving, “I ran this computer program correctly.” Rather, it is proving, “I know many proofs, one per shard, that each shard was run correctly, and the state of the machine at the end of shard i matches the state at the start of shard i+1”.\n\nAt least for sum-check-based SNARKs like Jolt, it is actually known how to keep the prover’s space bounded without SNARK recursion. We’ll flesh out the details in the context of Jolt in an upcoming e-print, and have begun implementing such a non-recursive space-bounded prover. It will take major engineering effort to achieve a performant implementation with this approach, but this will eventually pay off, leading to a simpler and easier-to-verify implementation.\n\nFolding\n\nLong term, I expect that “non-recursive space control” for SNARK provers will be an effective way to achieve a simple and performative prover when using hashing-based commitment schemes like Ligero, Brakedown, or FRI-Binius. But for the elliptic-curve-based commitment schemes supported by Jolt today, folding is the right way to minimize prover space while keeping the prover fast. Since folding inherently involves recursion, this will require formally verifying the correctness of a circuit representation of the Jolt verifier. This task may be complicated but will be helped by new tooling from the zkEVM formal verification project.\n\n(I don’t expect that folding will be difficult to incorporate into Jolt, but it might be challenging to apply formal methods to confirm its correctness due to its application of recursive proving to a complicated verification procedure. Fortunately, lots of tools are being developed to help with this task.)\n\nVerifying commitment schemes and Fiat-Shamir\n\nSuccinct arguments typically consist of two components: a PIOP and a polynomial commitment scheme. Together, this yields a succinct interactive argument, which is then rendered non-interactive via the Fiat-Shamir transformation. Efforts described above to formally verify the soundness of the Jolt PIOP are not enough on their own to guarantee that the Jolt SNARK is secure. We will also have to verify that the polynomial commitment schemes supported by Jolt are secure and correctly implemented, and also formally verify that applying Fiat-Shamir to the resulting succinct argument is secure and correctly implemented. This is a future goal of Quang and his collaborators’ work in Zklib, that is, to verify the soundness not only of PIOPs but also of polynomial commitment schemes and the PIOP-to-SNARK transformation.\n\nOther Directions\n\nVerified bytecode\n\nSome projects have criticized RISC-V zkVMs by discussing bugs in compilers from high-level languages down to RISC-V bytecode, and leveling criticisms at Rust as a high-level language. Our take is if one wants verified RISC-V bytecode then one should verify the bytecode directly, or use a verified compiler. And if one doesn’t like Rust as a high-level language, then one is free to use any other high-level language that compiles down to RISC-V.\n\nTo be sure, additional tooling to produce verified RISC-V bytecode would be of massive value to zkVMs. But that is outside of the scope of the zkVM itself. The zkVM’s job is to make sure the bytecode it is handed is run correctly.\n\nA verified implementation of the EVM via Jolt with precompiles\n\nRISC-V zkVMs are a promising tool for building zkEVMs (EVM=Ethereum Virtual Machine). Jolt is well suited for this task, but for maximum performance this will entail incorporating a handful of pre-compiles into Jolt (and formally verifying the implementation indeed captures EVM semantics). This is on the Jolt roadmap, and the formal verification component will be able to take advantage of other efforts supported by EF’s zkEVM Formal Verification project.\n\n***\n\nI have serious concerns about the rush to deploy zkVMs while they still almost certainly contain bugs. The road to bug-free zkVMs is long, and extreme caution is warranted while we walk it. But we will get there eventually, and the tools and techniques developed along the way will pay rich dividends in computer science and mathematics well beyond SNARK design.\n\n***\n\nJustin Thaler is Research Partner at a16z and an Associate Professor in the Department of Computer Science at Georgetown University. His research interests include verifiable computing, complexity theory, and algorithms for massive data sets.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investment-list/.\n\nThe content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures/ for additional important information.","tokens":5313,"crawled_at":1791193514590}
+{"id":10248,"url":"https://stack.olas.network/open-autonomy/configure_service/configure_access_external_chains","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Configure access to external chains - Olas Stack Developer Documentation","text":"Configure access to external chains\n\nThe Open Autonomy framework supports that AI agents access different external chains\nby defining certain configuration parameters appropriately.\n\nFor example, if you are developing an AI agent to be run in Ethereum, you might first want to use\na development environment like Hardhat or Ganache as your testbed, then migrate to a public testnet like Arbitrum Sepolia, and ultimately run your AI agent in the Ethereum main chain.\n\nTo use an AI agent in a particular chain, you must ensure that the the relevant agent instances addresses are funded in that chain.\n\nWhat will you learn\n\nIn this guide, you will learn how to:\n\nConfigure an AI agent to be run in a particular chain.\n\nConfigure the test classes appropriately.\n\nConfiguring the AI agent\n\nTo configure an AI agent to work with a particular chain, you must configure the parameters address and chain_id accordingly in the connection valory/ledger. This configuration can be set up by overriding the valory/ledger configuration at agent blueprint level or at AI agent level.\n\nAgent-blueprint-level override\n\nAt agent blueprint level, the agent blueprint configuration file aea-config.yaml should contain an override for the parameters of the connection valory/ledger, either using hardcoded values or environment variables as follows:\n\nUsing environment variables (recommended)Using hardcoded values\n\naea-config.yaml# (...)\n---\npublic_id: valory/ledger:0.19.0\ntype: connection\nconfig:\nledger_apis:\nethereum:\naddress: ${str:http://localhost:8545}\nchain_id: ${int:31337}\n<other_params>\n\naea-config.yaml# (...)\n---\npublic_id: valory/ledger:0.19.0\ntype: connection\nconfig:\nledger_apis:\nethereum:\naddress: http://host.docker.internal:8545\nchain_id: 31337\n<other_params>\n\nNote that if you use agent-blueprint-level hardcoded overrides, then AI-agent-level overrides will not work.\nOn the other hand agent-blueprint-level environment variable overrides must follow the export variable format.\n\nAI-agent-level override\n\nSimilarly, AI-agent-level overrides for the valory/ledger connection are defined in the AI agent configuration file service.yaml using either approach:\n\nUsing environment variablesUsing hardcoded values\n\nservice.yaml# (...)\n---\npublic_id: valory/ledger:0.19.0\ntype: connection\nconfig:\nledger_apis:\nethereum:\naddress: ${MY_CHAIN_ADDRESS:str:http://localhost:8545}\nchain_id: ${MY_CHAIN_ID:int:31337}\n<other_params>\n\nservice.yaml# (...)\n---\npublic_id: valory/ledger:0.19.0\ntype: connection\nconfig:\nledger_apis:\nethereum:\naddress: http://host.docker.internal:8545\nchain_id: 31337\n<other_params>\n\nObserve that within the AI agent configuration file there is no restriction for naming the environment variables.\n\nConfiguring integration tests\n\nThe open-aea-test-autonomy test tools contain a collection of classes for open-autonomy packages\nthat allows you to configure the ledger connection for contract integration tests.\nTo use the test tools, you must include open-aea-test-autonomy as a dependency for your packages.\n\nTests that make calls to a chain inherit from the class\n\naea_test_autonomy.base_test_classes.contracts.BaseContractTest\n\nThe configuration of the ledger connection for tests is done through the\nthe _setup_class(...) method from BaseContractTest, which overrides the valory/ledger connection\nconfiguration for tests. As above, you must set the parameters address and chain_id accordingly:\n\nnew_config = {\n\"address\": url,\n\"chain_id\": DEFAULT_CHAIN_ID,\n\"denom\": DEFAULT_CURRENCY_DENOM,\n\"default_gas_price_strategy\": \"eip1559\",\n\"gas_price_strategies\": {\n\"gas_station\": DEFAULT_GAS_STATION_STRATEGY,\n\"eip1559\": DEFAULT_EIP1559_STRATEGY,\n},\n}\n\nAlso, instead of inheriting directly from BaseContractTest, the test tools in open-aea-test-autonomy include several preconfigured helper base classes for common chains:\n\nBaseGanacheContractTest: Base test case for testing contracts on Ganache.\n\nBaseHardhatGnosisContractTest: Base test case for testing contracts on Hardhat with Gnosis.\n\nBaseHardhatAMMContractTest: Base test case for testing AMM contracts on Hardhat.\n\nBaseGanacheContractWithDependencyTest: Base test case for testing contracts with dependencies on Ganache.\n\nBaseHardhatGnosisContractWithDependencyTest: Base test case for testing contracts with dependencies on Hardhat with Gnosis.\n\nBaseHardhatAMMContractWithDependencyTest: Base test case for testing AMM contracts with dependencies on Hardhat.\n\nConfiguring end-to-end tests\n\nThe open-aea-test-autonomy test tools also contain base classes for end-to-end tests. These tests inherit from the base classes\n\naea_test_autonomy.base_test_classes.agents.BaseTestEnd2End\n\naea_test_autonomy.base_test_classes.agents.BaseTestEnd2EndExecution\n\nThese classes define an extra_configs attribute that is used to set the agent-blueprint-level overrides.\nTests that have this attribute set will override the corresponding agent blueprint configuration parameters.\n\nImportant\n\nThis does not only apply to the valory/ledger connection, but to any agent blueprint configuration.\n\nExample\nAll tests that inherit from the test class bellow will use the new configuration:\n\nfrom aea_test_autonomy.base_test_classes.agents import BaseTestEnd2EndExecution\n\nclass MyEndToEndTest(BaseTestEnd2EndExecution):\n\"\"\"Base class for my end-to-end tests.\"\"\"\n\nextra_configs = [\n{\n\"dotted_path\": \"vendor.valory.skills.my_skill_abci.models.params.args.ipfs_domain_name\",\n\"value\": \"/dns/localhost/tcp/5001/http\",\n}\n]\n\nConfiguring the validation timeout\n\nLast but not least, it is important to keep in mind what the average block times are in the deploying network.\nThis is going to play a significant role when performing transactions, since the validation logic is based on that.\n\nMore specifically, the attribute validate_timeout in the skill configuration file skill.yaml\nshould not be less than the average block time of the network, because timeouts and unnecessary repricing\nwill happen too often. For reference, at the time this document was written, the average block time\nin the Ethereum mainnet was around 13.3 seconds. Therefore, it is not recommended that you specify a value less than that. Moreover, it\nwould be advisable to allow for some margin before stopping retrials, because actual block times might be higher than their average value,\nand there is no guarantee that a transaction will be included into the next block.\n\nThe underlying retrial mechanism has a backoff that scales linearly, starting at retry_timeout, and stopping either when retry_attempts have been executed or validate_timeout has been reached.\n\nExample\nAn example configuration in the skill.yaml file for the Ethereum mainnet is as follows:\n\n# (...)\nmodels:\nparams:\nargs:\nretry_attempts: 13\nretry_timeout: 13.3\nvalidate_timeout: 1205\n\nTherefore, unsuccessful transactions will be retried at the following times:\n\n1st retry: 13.3⋅(1)=13.3\n\n2nd retry: 13.3⋅(1+2)=26.6\n\n...\n\nith retry: 13.3⋅i(i+1)2\n\n...\n\n12th retry: 13.3⋅(1+2+⋯+12)=1037.4\n\n13th retry: 13.3⋅(1+2+⋯+12+13)=1210.3\n\nNote, however, that it will stop at the 12th retry, because\n1210.3> validate_timeout =1205.","tokens":1775,"crawled_at":1791193529381}
+{"id":10249,"url":"https://docs.near.org/web3-apps/tutorials/data-types","domain":"docs.near.org","chapter":"layer1_layer2","title":"Handling NEAR Types - NEAR Docs","text":"When calling methods in a contract or receiving results from them, you will need to encode/decode parameters correctly. For this, it is important to know how the contracts encode timestamps, balances, and gas.\n\nSearching for Smart Contract Data Types?Check the Smart Contract SDK Types section for more information on how to handle data types within smart contracts.\n\n​\n\nTime\n\nThe block timestamp in a smart contract is encoded using nanoseconds (i.e. 19 digits: 1655373910837593990).\n🌐 Javascript\n\n🦀 Rust\n\nDate.now() returns a timestamp in milliseconds (i.e 13 digits: 1655373910837). Make sure to convert between milliseconds and nanoseconds to properly handle time variables.\nIn Rust std::time::SystemTime::now() returns a SystemTime object. You can convert it to nanoseconds since UNIX_EPOCH as follows:\n\nuse std::time::{SystemTime, UNIX_EPOCH};\nlet start = SystemTime::now();\nlet since_the_epoch = start.duration_since(UNIX_EPOCH)\n.expect(\"Time went backwards\");\nlet in_nanoseconds = since_the_epoch.as_nanos();\nprintln!(\"Current time in nanoseconds since UNIX EPOCH: {}\", in_nanoseconds);\n\n​\n\nDeposits\n\nSmart contracts handle NEAR amounts always using yoctoNEAR (1Ⓝ = 10^24yocto). This means that when interacting with contract’s or the user’s balance you will need to convert between NEAR and yoctoNEAR.\nUnder the hood, the network (and contracts) represent balances as u128, which are encoded as strings (since JSON cannot handle more than 52 bit integers).\nRemember to always send amounts as strings (e.g. \"1000000000000000000000000\" for 1Ⓝ) and never as number (e.g. 1000000). Consequently, convert amounts from string whenever you want to display them to the user.\n🌐 Javascript\n\n🦀 Rust\n\nIn javascript, you can use the near-api-js library to convert between NEAR and yoctoNEAR:\n\nimport { NEAR } from '@near-js/tokens'\n\nconst units = NEAR.fromDecimal('1.5') // 1.5Ⓝ\nconsole.log(units) // \"1500000000000000000000000\"\n\nconst decimal = NEAR.fromUnits('1500000000000000000000000', 2)\nconsole.log(decimal) // 1.5\n\nIn Rust you can directly use the near_token crate to convert between NEAR and yoctoNEAR:\n\nuse near_token::NearToken\n\nfn main() {\nconst TEN_NEAR: NearToken = NearToken::from_near(10);\n\nassert_eq!(TEN_NEAR.to_string(), \"10.00 NEAR\");\nassert_eq!(TEN_NEAR.as_near(), 10);\nassert_eq!(TEN_NEAR.as_millinear(), 10000);\nassert_eq!(TEN_NEAR.as_yoctonear(), 10000000000000000000000000);\n\nlet input_str = \"0.123456 NEAR\";\nlet input_near: NearToken = input_str.parse().unwrap();\nassert_eq!(\ninput_near,\nNearToken::from_yoctonear(123456000000000000000000)\n);\n\n}\n\n​\n\nGas\n\nWhen calling a contract method, you can specify how much gas you want to attach to the call. Within the network, the Gas is represented as a u64, which is encoded as a string (since JSON cannot handle more than 52 bit integers).\nAs a rule of thumb, functions that consume little computation can be called with 30 Tgas or less, while more complex functions may require up to 1000 Tgas.\n🌐 Javascript\n\n🦀 Rust\n\nIn javascript there is no built-in library to handle gas units, but you can easily convert between them as follows:\n\nconst TGAS = 1000000000000; // 1 Tgas = 10^12 gas units\n\nfunction toTgas(gas) {\nreturn (gas * TGAS).toString();\n}\n\nfunction fromTgas(tgas) {\nreturn (parseInt(tgas) / TGAS).toFixed(2);\n}\n\nuse near_gas::NearGas;\n\nfn main() {\nlet data = \"12.657 tgas\";\n\nlet near_gas: NearGas = data.parse().unwrap();\n\n// Convert the value to the most precise \"gas\" unit\nassert_eq!(near_gas.as_gas(), 12657000000000);\n// Convert the value to \"gigagas\" unit\nassert_eq!(near_gas.as_ggas(), 12657);\n\n// Display Gas. It will print: \"Here is 12.7 Tgas\"\nprintln!(\"Here is {}\", near_gas);\n\n// When `serde` feature is enabled, NearGas can be used in serde-serializable structs.\n// NearGas will be serialized to a gas-precision u64 value encoded as string.\n#[derive(serde::Serialize)]\nstruct FunctionCallDetails {\nused_gas: NearGas,\n}\n\nlet details = FunctionCallDetails { used_gas: near_gas };\n\nassert_eq!(serde_json::to_string(&details).unwrap(), r#\"{\"used_gas\":\"12657000000000\"}\"#);\n}\n\nWas this page helpful?","tokens":1022,"crawled_at":1791193539106}
+{"id":10250,"url":"https://stack.olas.network/open-autonomy/configure_service/on-chain_deployment_checklist","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"On-chain deployment checklist - Olas Stack Developer Documentation","text":"On-chain deployment checklist\n\nThis section details a requirement checklist that need to be satisfied so that your AI agent can be properly deployed on-chain.\n\nRequired FSM App skill models\n\nEnsure that your skill extends the following classes in the models.py file:\n\npackages.valory.skills.abstract_round_abci.models.BenchmarkTool\npackages.valory.skills.abstract_round_abci.models.BaseParams\n\nYou can define custom arguments for the skill, if required.\n\nWithout custom argumentsWith custom arguments\n\nfrom packages.valory.skills.abstract_round_abci.models import BenchmarkTool\nfrom packages.valory.skills.abstract_round_abci.models import BaseParams\n\n# (...)\n\nYourBenchmarkTool = BenchmarkTool\nYourSkillParams = BaseParams\n\nfrom packages.valory.skills.abstract_round_abci.models import BenchmarkTool\nfrom packages.valory.skills.abstract_round_abci.models import BaseParams\n\n# (...)\n\nYourBenchmarkTool = BenchmarkTool\n\nclass YourSkillParams(BaseParams):\ndef __init__(self, *args: Any, **kwargs: Any) -> None:\nself.your_custom_arg_1: str = self._ensure(\"your_custom_arg_1\", kwargs, str)\nself.your_custom_arg_2: str = self._ensure(\"your_custom_arg_2\", kwargs, str)\n\n# (...)\n\nsuper().__init__(*args, **kwargs)\n\nRequired arguments and overrides\n\nEnsure that your FSM App skill, agent blueprint and AI agent configuration files (skill.yaml, aea-config.yaml, and service.yaml, respectively) define the appropriate arguments and overrides:\n\nskill.yaml\nMust define default/placeholder values for the arguments associated to the YourSkillParams class.\naea-config.yaml\nMust define overrides for valory/abci connection, valory/ledger connection, valory/p2p_libp2p_client connection, and your FSM App skill. Environment variables used for agent-blueprint-level overrides can use the simplified syntax ${<type>:<default_value>}.\nservice.yaml\nMust define overrides for valory/ledger connection and your FSM App skill (optionally, also for valory/p2p_libp2p_client connection). Environment variables used for ai-agent-level overrides use the syntax ${<env_var_name>:<type>:<default_value>}. They will be exported as their upper case JSON path in the agent blueprint Docker container.\nSee also the AI agent level overrides and multiple overrides sections for more information.\n\nskill.yamlaea-config.yamlservice.yaml\n\nname: <your_skill_name>\nauthor: <author>\nversion: <version>\ntype: skill\n# (...)\nmodels:\nbenchmark_tool:\nargs:\nlog_dir: /logs\nclass_name: YourBenchmarkTool\n\nparams:\nargs:\nsetup:\nall_participants:\n- '0x0000000000000000000000000000000000000000'\nsafe_contract_address: '0x0000000000000000000000000000000000000000'\nconsensus_threshold: null\ntendermint_url: http://localhost:26657\ntendermint_com_url: http://localhost:8080\nservice_registry_address: null\nshare_tm_config_on_startup: false\non_chain_service_id: null\n# (...)\nclass_name: YourSkillParams\n\n# (...)\n---\npublic_id: valory/abci:0.1.0\ntype: connection\nconfig:\ntarget_skill_id: <author>/<your_skill_name>:<version>\nhost: ${ABCI_HOST:str:localhost}\nport: ${ABCI_PORT:int:26658}\nuse_tendermint: ${ABCI_USE_TENDERMINT:bool:false}\n\n---\npublic_id: valory/ledger:0.19.0\ntype: connection\nconfig:\nledger_apis:\nethereum:\naddress: ${str:http://localhost:8545}\nchain_id: ${int:31337}\npoa_chain: ${bool:false}\ndefault_gas_price_strategy: ${str:eip1559}\n\n---\npublic_id: valory/p2p_libp2p_client:0.1.0\ntype: connection\nconfig:\nnodes:\n- uri: ${P2P_URI:str:acn.autonolas.tech:9005}\npublic_key: ${P2P_PUBLIC_KEY:str:02d3a830c9d6ea1ae91936951430dee11f4662f33118b02190693be835359a9d77}\n- uri: ${P2P_URI:str:acn.autonolas.tech:9006}\npublic_key: ${P2P_PUBLIC_KEY:str:02e741c62d706e1dcf6986bf37fa74b98681bc32669623ac9ee6ff72488d4f59e8}\ncert_requests:\n- identifier: acn\nledger_id: ethereum\nmessage_format: '{public_key}'\nnot_after: '2025-01-01'\nnot_before: '2024-01-01'\npublic_key: ${P2P_PUBLIC_KEY:str:02d3a830c9d6ea1ae91936951430dee11f4662f33118b02190693be835359a9d77}\nsave_path: .certs/acn_cosmos_9005.txt\n\n---\npublic_id: <author>/<your_skill_name>:<version>\ntype: skill\nmodels:\nbenchmark_tool:\nargs:\nlog_dir: ${str:/benchmarks}\n\nparams:\nargs:\nsetup:\nall_participants: ${list:[]}\nsafe_contract_address: ${str:'0x0000000000000000000000000000000000000000'}\nconsensus_threshold: ${int:null}\ntendermint_url: ${str:http://localhost:26657}\ntendermint_com_url: ${str:http://localhost:8080}\nservice_registry_address: ${str:null}\nshare_tm_config_on_startup: ${bool:false}\non_chain_service_id: ${int:null}\n# (...)\n\n# (...)\n---\npublic_id: valory/ledger:0.19.0\ntype: connection\nconfig:\nledger_apis:\nethereum:\naddress: ${ETHEREUM_ADDRESS:str:http://localhost:8545}\nchain_id: ${ETHEREUM_CHAIN_ID:int:31337}\npoa_chain: ${ETHEREUM_POA_CHAIN:bool:false}\ndefault_gas_price_strategy: ${DEFAULT_GAS_PRICE_STRATEGY:str:eip1559}\n\n---\npublic_id: <author>/<your_skill_name>:<version>\ntype: skill\nmodels:\nbenchmark_tool:\nargs:\nlog_dir: ${LOG_DIR:str:/benchmarks}\n\nparams:\nargs:\nsetup:\nall_participants: ${ALL_PARTICIPANTS:list:[\"0x...\",\"0x...\",\"0x...\",\"0x...\"]}\nsafe_contract_address: ${SAFE_CONTRACT_ADDRESS:str:0x...}\nconsensus_threshold: ${CONSENSUS_THRESHOLD:int:null}\ntendermint_url: ${str:http://localhost:26657}\ntendermint_com_url: ${str:http://localhost:8080}\nservice_registry_address: ${SERVICE_REGISTRY_ADDRESS:str:0x...}\nshare_tm_config_on_startup: ${SHARE_TM_CONFIG_ON_STARTUP:bool:false}\non_chain_service_id: ${ON_CHAIN_SERVICE_ID:int:1}\n# (...)\n\nImportant\n\nRecall that when deploying an on-chain AI agent using autonomy deploy from-token, a number of arguments (under setup) are overridden with the values registered in the Autonolas Protocol:\n\nservice.yaml# (...)\nmodels:\nparams:\nargs:\nsetup:\nall_participants: # Overridden with the registered values\nsafe_contract_address: # Overridden with the registered values\nconsensus_threshold: # Overridden with the registered values\n\nFor local deployments, the argument consensus_threshold can take the value:\n\nnull: then the framework will automatically calculate consensus_threshold as ⌈(2N+1)/3⌉, where N=len(all_participants).\n\nAny value M such that ⌈(2N+1)/3⌉≤M≤N.\n\nOtherwise, the framework will raise an error and the app will not start.\n\nPublish and mint packages\n\nEnsure that your components, agent blueprints and AI agents packages are published to the IPFS registry:\n\nPush your components using the autonomy push command.\n\nPublish your agent blueprints using the autonomy publish command.\n\nPublish your AI agents using the autonomy publish command.\n\nEnsure that your components, agent blueprints and AI agents packages are minted on-chain in the Autonolas Protocol.\n\nCheck the deployment readiness of the AI agent using\n\n$ autonomy analyse service --public-id PUBLIC_ID\n\nor if you want to check deployment readiness of an on-chain AI agent\n\n$ autonomy analyse service --token-id TOKEN_ID\n\nPublish Docker images (optional)\n\nYou can build the Docker images for the AI agent using the autonomy build-image command. Alternatively, the images are built automatically when the AI agent is deployed using autonomy deploy from-token command\n\nIf you want to use an image with a stable hash or a stable version of a runtime image, you can provide the hash/version using --image-version on the autonomy deploy build command.\n\nEnsure that the image exists before running the deployment:\n\ndocker pull <author>/oar_runtime_<ai_agent_name>:<ipfs_hash_ai_agent>","tokens":1830,"crawled_at":1791193548119}
+{"id":10251,"url":"https://docs.near.org/web3-apps/tutorials/frontend-multiple-contracts","domain":"docs.near.org","chapter":"layer1_layer2","title":"Frontend Interacting with Multiple Contracts - NEAR Docs","text":"This example showcases how to interact with multiple contracts from a single frontend.\nParticularly, this example shows how to:\n\nQuery data from multiple contracts.\n\nCall methods in multiple contracts simultaneously.\n\n​\n\nQuery Data from Multiple Contracts\n\nTo query multiple contracts simply perform multiple view calls:\nLoading...\nSee code on GitHub\n\n​\n\nDispatching Multiple Transactions\n\nThe wallet object enables to dispatch multiple transactions simultaneously. However, please notice that the transactions execute independently.\nDispatching multiple transactions at once is just a nice way to improve UX, because the user interacts with the wallet only once.\nLoading...\nSee code on GitHub\n\nIn this example, the user signs two independent transactions:\n\nA transaction to call set_greeting in our Hello NEAR example\n\nA transaction to call add_message in our GuestBook example\n\nEven when the user accepts signing the transactions at the same time, the\ntransactions remain independent. This is, if one fails, the other is NOT rolled back.\n\n​\n\nBatch Actions\n\nYou can aggregate multiple actions directed towards a same contract into a single transaction. Batched actions execute sequentially, with the added benefit that, if one fails then they all get reverted.\n\n// Register a user and transfer them FT on a single take\nconst REGISTER_DEPOSIT = \"1250000000000000000000\";\n\nconst ftTx = {\nreceiverId: FT_ADDRESS,\nactions: [\n{\ntype: 'FunctionCall',\nparams: {\nmethodName: 'storage_deposit',\nargs: { account_id: \"<receiver-account>\" },\ngas: THIRTY_TGAS, deposit: REGISTER_DEPOSIT\n}\n},\n{\ntype: 'FunctionCall',\nparams: {\nmethodName: 'ft_transfer',\nargs: { receiver_id: \"<receiver-account>\", amount: amount_in_yocto },\ngas: THIRTY_TGAS, deposit: 1 }\n}\n]\n}\n\n// Ask the wallet to sign and send the transaction\nawait wallet.signAndSendTransactions({ transactions: [ ftTx ] })\n\nWas this page helpful?","tokens":472,"crawled_at":1791193557176}
+{"id":10252,"url":"https://a16zcrypto.com/posts/article/understanding-jolt-clarifications-and-reflections","domain":"a16zcrypto.com","chapter":"research","title":"Understanding Jolt: Clarifications and reflections - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nUnderstanding Jolt: Clarifications and reflections\nJustin Thaler\n06.03.24\n\nTABLE OF CONTENTS\n1. The sum-check protocol and the Binius commitment scheme 1. The sum-check protocol and the Binius commitment scheme\n2. Sum-check, lookups, performance, and simplicity\n3. Elliptic curves, again\n4. Precompiles and zkVM benchmarks\nTags\nJolt\nresearch\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nWe’ve been making steady progress on Lasso and Jolt – our new, simple, performant lookup argument and zkVM — starting with the theory papers and Lasso implementation last summer, and since releasing a fully open source implementation of Jolt last month.\n\nThe implementation has shown Jolt’s promise relative to existing technology and challenged much of the conventional wisdom in SNARK design. Since its release, we have added support for the Rust standard library, incorporated improvements from over 10 contributors and merged nearly 50 pull requests, and improved the modularity and extensibility of the codebase.\n\nWhile we continue to enhance Jolt, I wanted to address questions, clarify misconceptions, and share my perspective on key issues. The four areas I explore here are (1) the relationship between the sum-check protocol and the Binius commitment scheme, (2) the role of sum-check and lookups in Jolt, (3) elliptic curves versus hashing, and (4) precompiles as they relate to zkVMs.\n\n1. The sum-check protocol and the Binius commitment scheme\n\nCommitment schemes are often highlighted as the key building block of a SNARK. But it’s also important to remember the vital role of the other component: the polynomial IOP. For instance, the Binius commitment scheme for multilinear polynomials represents a major advance, but it must be paired with a polynomial interactive oracle proof (PIOP) to prove that the committed data actually validates the prover’s claims.\n\nBinius’ commitment is specifically compatible with PIOPs that use the sum-check protocol. This is due to reasons both clear (sum-check relies on multilinear polynomials, not univariate ones; and FRI-Binius even uses sum-check internally) and nuanced (sum-check PIOPs naturally operate across fields of any characteristic, which is crucial for taking full advantage of Binius’ novel performance traits). Binius’ commitment is not compatible with the PIOPs that are most common today, which unfortunately don’t use sum-check.\n\nDesigning a fast PIOP requires more insight than just the phrase “apply sum-check”. Binius uses over a decade’s worth of work employing the sum-check protocol to implement prover-efficient polynomial IOPs. Sections 4 and 5 of the Binius paper are devoted to designing new highly efficient sum-check-based PIOPs to combine with the commitment scheme.\n\nThe Binius commitment and Jolt go together like peanut butter and jelly because Jolt is the only zkVM today that is exclusively based on the sum-check protocol. Today, Jolt uses commitment schemes based on elliptic curve cryptography, but incorporating the Binius commitment into Jolt is our highest priority.\n\n2. Sum-check, lookups, performance, and simplicity\n\nWhat sets Jolt apart? Is it that it is the first (and currently only) zkVM that exclusively uses sum-check-based polynomial IOPs — or is it that Jolt implements the lookup singularity (i.e., it does almost everything with lookups rather than constraint systems or circuits)? The answer is, It’s both. Most of Jolt’s simplicity benefits over prior zkVMs come from lookups; its performance benefits come from both its use of lookups and of sum-check.\n\nThe lookup-only approach is better for some instructions — ones that don’t have very small circuits — but can be worse for others that do have very small circuits, such as the bitwise-XOR instruction when working over a field of characteristic two, which corresponds to native field addition. But overall, the lookup-only approach is a net positive for performance, at least when working over 256-bit fields. Today, the Jolt prover spends about 20% of its time on these “instruction execution” lookups, and 40% of its time proving constraints. Adding more constraints to reduce lookups would not be helpful.\n\nRoughly speaking, Jolt uses lookups to implement both the “fetch” and “execute” parts of the CPU’s fetch-decode-execute loop. These lookups are fast enough that most of the prover’s time is spent proving it ran “decode,” which is handled through traditional constraints.\n\nThe lookup-only approach also results in a simpler and more auditable implementation. These benefits are difficult to quantify, and take time to recognize and appreciate. But Jolt does well on crude proxies such as lines of code (the Jolt codebase is about 25,000 lines of code, which is 2x to 4x fewer than prior RISC-V zkVMs) and development time. Such improvements are much harder to obtain than performance ones: While I expect zkVM provers to be nearly 100x faster in the coming months than they were in August 2023, it’s hard to imagine a zkVM with even 10x fewer lines of code\n\n3. Elliptic curves, again\n\nPublic discourse undervalues the benefits of having a fast zkVM that works over elliptic curves, partly due to the justified enthusiasm for hashing-based commitment schemes like Binius.\n\nWhen proving statements about elliptic curve cryptography, a curve-based zkVM can avoid non-native field arithmetic that adds hundred-to-thousand-fold overheads to proving time. Such applications include proving knowledge of many digital signatures (the main work relevant to blockchain light clients and SNARK-based bridges); aggregating Plonk/Groth16/Nova/Honk proofs; and proving knowledge of Verkle tree authentication paths.\n\nI am optimistic that the community will converge around sum-check–based PIOPs combined with the FRI-Binius commitment scheme as the right approach to performant SNARKs in many applications. Even if this happens, there will still be a role for fast curve-based SNARKs, unless the world moves away from elliptic curve cryptography entirely (e.g., after society completes a shift away from cryptosystems that are not quantum-secure).\n\nTo summarize:\n\nJolt-with-curve-based-commitments is competitive with all other zkVMs that exist today (all of which are already using hashing-based commitment schemes and working over small fields).\n\nJolt-with-curves is what one would want to use when proving statements about elliptic curves (at least, without major advances in proving non-native field arithmetic).\n\nJolt-with-Binius-commitment will be much faster as a pure zkVM than alternatives, and will be what people use except when proving statements about curves or proving with very small space (in which case people would use Jolt-with-curves).\n\nSNARKs based on elliptic curves will continue to be used to compress proof size and verifier costs before posting proofs onchain. zkVMs that work over large fields will play a role as long as that is the case. Even today, zkVM projects that people consider hashing-based are actually using zkVMs defined over BN254’s scalar field as part of their recursion pipeline.\n\n4. Precompiles and zkVM benchmarks\n\nThere’s been some discussion about precompiles and their role in zkVMs and in benchmarking. Before I explain, it’s helpful to unpack what precompiles are, as the term’s meaning varies by context.\n\n“Precompiles” in Ethereum. In the Ethereum Virtual Machine (EVM), precompiles are operations that are performed frequently and are natively supported to enhance efficiency. This avoids the substantial overheads and exorbitant gas costs associated with executing these operations through lengthy sequences of EVM opcodes.\n\nThe distinction between “EVM precompiles” and “primitive instructions” (opcodes) is primarily semantic. For example, the Keccak hash function is an EVM opcode, while SHA-2 is an EVM precompile. Both precompiles and opcodes are frequently executed operations that Ethereum natively supports for identical purposes: optimizing efficiency and gas costs. Precompiles are undeniably part of the EVM, which is commonly used to describe the Ethereum execution environment broadly, encompassing much more than just opcodes.\n\nWhy does the EVM even have precompiles if they function essentially the same as opcodes? It’s mainly just a matter of convention. One other possible reason is that precompiles consist of relatively complicated operations like cryptographic primitives that may need to change in the future, and it will be easier to change them if they are not assigned an opcode.\n\n“Precompiles” in zkVM design. In zkVM design, a precompile refers to a special purpose SNARK targeted at a specific functionality like Keccak or SHA hashing, or a specific elliptic curve group operation. Today, SNARK precompiles are typically implemented via hand-optimized constraint systems (although as the community switches to sum-check-based SNARKs, the nature of these constraint systems and how they get proved will change).\n\nThe parallels between EVM precompiles and zkVM precompiles run deep. Before Jolt, zkVMs implemented primitive instructions via hand-optimized constraints systems, one per instruction, exactly as they implement precompiles. The difference between what gets called a zkVM precompile and what gets called a primitive instruction is purely semantic. There is no actual difference between them.\n\nIn Jolt, we implement primitive instructions with lookups instead of traditional constraints. But there are no major issues with choosing to implement some primitive instructions via constraints. (In fact, lookups can even be viewed as a type of constraint.) Indeed, as I’ve said previously, we will likely have to use traditional constraints to implement RISC-V addition and multiplication once we switch to the Binius commitment scheme over fields of characteristic two.\n\nBenchmarking zkVMs\n\nWith that background, here are my views on precompiles as they relate to zkVMs and benchmarking.\n\nFirst, benchmarking various RISC-V zkVMs without precompiles is exactly what it means to benchmark RISC-V zkVMs. The term “zkVM” is an informal one, so there’s room for disagreement, but in my view, a RISC-V zkVM with one or more precompiles is no longer a zkVM for RISC-V: It is a zkVM for the new instruction set based on RISC-V by adding each precompile as a primitive instruction. At a minimum, each precompile added to a zkVM erodes the value proposition of the zkVM paradigm — every additional circuit adds surface area for bugs, and existing programs won’t be able to leverage the new precompile out-of-the-box.\n\nSome also conflate the notion of EVM precompiles for zkEVMs with the notion of precompiles for zkVMs. But these are very different things. While a few key operations for zkEVMs — such as Merkle hashing and digital signature verification — are indeed more complicated than primitive RISC-V instructions, that doesn’t change the fact that there is no functional difference between EVM precompiles and primitive EVM instructions. zkEVMs must support EVM precompiles to claim parity with the EVM. In other words, a zkEVM that does not support EVM precompiles is not analogous to a RISC-V zkVM like Jolt, where precompiles would be used to expand the instruction set beyond RISC-V.\n\nAnother concern is how to choose a “fair” set of functionalities on which to benchmark the zkVMs. But for RISC-V zkVMs, any set of functionalities is fair. The prover time is almost entirely determined simply by the number of cycles that the RISC-V CPU runs for, for two reasons. First, the prover spends a small fraction of its time on the “execute” part of the “fetch-decode-execute” loop. Second, different RISC-V instructions, as well as memory accesses, all have reasonably similar proving times. (In Jolt, they are all handled with offline memory checking techniques.)\n\nFinally, if precompiles are brought into the picture, Jolt will likely not do any worse than alternatives. Indeed, I expect it to do better because sum-check-based precompiles will be the fastest, and can be integrated into Jolt without overhead due to its exclusive use of sum-check-based PIOPs. On this point, some people expressed concern that precompiles using elliptic-curve commitment schemes will be much worse than those using hashing-based schemes. Jolt uses curves today, but this is not essential, and we’ve been very open about our plans to switch over to Binius.\n\nBroader thoughts on benchmarking\n\nOur main goal in benchmarking is to ascertain the intrinsic performance profiles of different proof systems, to the extent that they can be isolated from their implementations. This approach allows the community to understand and converge upon the right techniques for designing performant and secure SNARKs. But when attempting to compare two different SNARKs, there are endless confounding factors that often make an “apples to apples” comparison all but impossible.\n\nEngineering effort represents one of these confounding factors, although much of the community appears to take an opposite view. The thinking seems to go something like this: if a project has added “features” like precompiles or optimized implementations for specific hardware, then it should get “credit” in any benchmarking.\n\nBoth viewpoints have merit. But taken too far, the latter viewpoint is clearly untenable. New approaches will forever be at a disadvantage in any benchmark simply because those implementing them have not had time commensurate with older projects. This holds back progress.\n\nOver time, I expect the confounding factors in benchmarking to ease. As tooling to build SNARKs matures, SNARKs will require less engineering effort to get decent performance. And it’s a minor miracle that — at least for RISC-V — zkVM costs depend mainly on cycle counts rather than idiosyncrasies of any particular application. If people converge on a choice of constraint system (as opposed to today’s fractured state of R1CS, AIR, Plonkish, etc.), something similar may happen for SNARKs targeted at constraint systems, with simple measures of constraint-system size standing in for cycle counts.\n\nUntil then, it will be difficult to strike the right balance between under- and over-controlling for confounding factors. Disagreements will be inevitable, and builders will have to provide the full context, details, and rationales behind any benchmarks so the community can understand and discuss them.\n\n****\n\nJustin Thaler is Research Partner at a16z and an Associate Professor in the Department of Computer Science at Georgetown University. His research interests include verifiable computing, complexity theory, and algorithms for massive data sets.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investment-list/.\n\nCharts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures/ for additional important information.","tokens":4354,"crawled_at":1791193558049}
+{"id":10253,"url":"https://gov.uniswap.org/t/transaction-fee-distribution/482","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Transaction Fee Distribution - Requests for Comment - Uniswap Governance","text":"Transaction Fee Distribution\n\nRequests for Comment\n\nFableEye\n\nSeptember 17, 2020, 6:47am\n\n1\n\nProposal to allocate 0.04% of all Uniswap platform transaction fees to UNI stakers in the form of ETH. Staking pool will be used for both governance and fee distribution.\n\n0.01% of transaction fees will go to the treasury to be used at the DAOs discretion.\n\n17 Likes\n\nMunsey\n\nSeptember 17, 2020, 6:55am\n\n2\n\nHow would we convert the fees for pools that don’t involve ETH? I imagine logic to transform the fee into eth would cause total gas needed to go up and we’d have to account for slippage on that transaction as well.\n\n1 Like\n\nCryptoved\n\nSeptember 17, 2020, 12:43pm\n\n3\n\nNice proposal. Reward tokenomics will be good for economic stimuls of tokenholders. People can claim rewards so it can be not only ETH.\n\n1 Like\n\nleo_eth\n\nSeptember 17, 2020, 4:51pm\n\n4\n\nI wholly agree on the 0.04/0.01 design. Nevertheless I suggest that we could get some inspiration from the CurveDAO where only time-locked UNI coins and ETH-UNI LP can get reward from the fees. That would help create a virtuous circle:\n\nReduce selling pressure which should increase LM ROI.\n\nReduce selling incentives for newly minted coins by LM.\n\nLocked-UNI coins holders have more skin in the game thus would be more motivated to participate in the governance and the growth of the ecosystem.\n\n7 Likes\n\nDarkhane\n\nSeptember 17, 2020, 5:08pm\n\n5\n\nPlease stop with these timelocked thing, this only favors whales.\n\nReduce selling pressure is only a very short-term vision.\n\nThe higher the volume, the higher the fees and the higher the valuation. Only that matters.\n\nUtility makes value, everything else is artificial and won’t last.\n\n3 Likes\n\nmonet-supply\n\nSeptember 17, 2020, 6:51pm\n\n6\n\nThe protocol fee has not yet been activated, and even when it is it won’t start accumulating for 180 days.\n\nIf anything, I expect protocol fees to be most useful as a gentle ‘push’ factor to incentivize LP migration from v2 to forthcoming v3.\n\n2 Likes\n\nNative\n\nSeptember 17, 2020, 7:11pm\n\n7\n\nTime-locked vesting periods are a great idea for the reasons that you describe.\n\nleo_eth\n\nSeptember 17, 2020, 7:20pm\n\n8\n\nI think having LM boosting (More coins minted) when one time-lock some UNi as in Curve is indeed a bad idea.\n\nI just propose that only people that time-lock their UNI tokens can obtain the 0.0x% trading fee.\n\nOne holder profit would be equal to ((his number of tokens locked)/(all token locked))*(fee revenue during x time) thus, due to linearity, it will not particularly profit to whales.\n\nonlinedollars\n\nSeptember 17, 2020, 8:02pm\n\n9\n\nIf this is implemented, a lot of new users could join to stake as Uniswap had shown that it is ready to stand the test of time.\n\niwearahoodie\n\nSeptember 17, 2020, 11:24pm\n\n10\n\nI support the idea in theory, eventually. However I think more debate and discussion needs to be had on the benefit of growing V3 and building a moat around that before turning on fees.\n\nI’m happy to delay this vote until V3 is out.\n\n4 Likes\n\nLosMontana420\n\nSeptember 18, 2020, 5:55am\n\n11\n\nI agree that this will take a more detailed discussion to determine the best coarse of action, the theory is good but could catch some whales doing what they do.\n\ncoolcryptomaniac\n\nSeptember 18, 2020, 8:43am\n\n12\n\nBest to be given in form of dai,eth and other new Uniswap tokens , will create above balance and secure future of uni holders\n\nunijay\n\nSeptember 18, 2020, 8:40pm\n\n13\n\nGrowth and maintaining a competitive platform should be prioritized. IMO it is far to early to think about value extraction. This sector will have explosive growth moving forward and everyone here benefits if Uniswap is established as an important hub in that, far larger, network. The less fees and friction, and the more incentive for participation, the greater Uniswaps market share will be.\n\n6 Likes\n\niwearahoodie\n\nSeptember 21, 2020, 12:57pm\n\n14\n\nI agree with unijay 110%. I’d prefer to put resources towards growth.\n\n1 Like\n\nNaught\n\nOctober 9, 2020, 5:20am\n\n15\n\nUNI being a governance token its value is hinged not only on the protocol, but also activity of its participants by voting on innovative proposals.\n\nGrowth should not be focused on cultivating holding via a general transaction fee to all.\n\nThe transaction fee should go towards those who are engaged with governance (such as small users delegating and large whales who are active with proposal improvements).\n\nIncentive should be aligned with governance engagement.\n\n1 Like\n\nDmills\n\nOctober 9, 2020, 7:33am\n\n16\n\nI definitely think token holders sure be able to earn something, other than the right to vote. for the sake of the whales and making things pretty even, what if we just make a limit to the number of tokens any said token holder could earn rewards on. Like say you have 3,000 tokens, our limit could be 2,000 tokens max for earning.\n\n1 Like\n\nDarkhane\n\nOctober 9, 2020, 5:16pm\n\n17\n\nI’m sorry but that’s nonsense.\n\nIt’s only going to serve for a pile of ridiculous proposals, worse than now.\n\nThe majority of the hodlers will vote anything and everything just to get some tokens.\n\n2 Likes\n\nNaught\n\nOctober 9, 2020, 10:16pm\n\n18\n\nI do not think it will result in a pile of proposals. The reward would only go to those who have shown intent to align to specific platform goals.\n\nReward the .05% fees to delegate pools, does not mean spamming proposals. It just means you have a stake in the future direction of the platform.\n\nishaan1986\n\nFebruary 21, 2021, 9:47pm\n\n19\n\nNeed Gas Token On Uniswap Like Chi Gas Token On 1inch Exchange to Reduce Gas Fee and it also need to be airdropped like UNI to Uniswap User.\n\n1 Like\n\nOblomov\n\nFebruary 23, 2021, 11:02am\n\n20\n\nNeed is a strong word, and you haven’t really justified it’s use in your post.\n\nFrom what I’m aware, gas tokens aren’t an intentional feature of the ethereum protocol, and I think there are active proposals to remove the ability to use them, so investing dev time might not be a priority for the uniswap team. You can look up the EIPs to see exactly what’s being discussed.\n\nWhen you airdrop a token you inflate it’s availability and likely reduce its price, if it goes to people who’re just going to sell it. What would we be trying to incentivise, with another airdrop, that would be beneficial for the uniswap project as a whole?\n\nPursuing another airdrop without a justification sounds like you’re just looking for a handout.\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nFees Switch Follow Up: Supporting the Evolution of Uniswap Protocol Design\n\nUncategorized\n\n8\n\n3957\n\nMarch 30, 2023\n\nAbility to toggle fees is next week, do we do it?\n\nRequests for Comment\n\n27\n\n4718\n\nFebruary 27, 2021\n\nUniswap Proposal: An Alternative Use-Case for the Fee Switch\n\nUncategorized\n\n21\n\n6616\n\nApril 7, 2023\n\n[POLL] Adding value to UNI tokens\n\nRequests for Comment\n\n2\n\n2243\n\nOctober 10, 2020\n\nProposal: Flip the Protocol Fee Switch for Uniswap Dev Team and UNI Holders\n\nRequests for Comment\n\n5\n\n7159\n\nOctober 30, 2020","tokens":1745,"crawled_at":1791193572700}
+{"id":10254,"url":"https://docs.near.org/tools/cli","domain":"docs.near.org","chapter":"layer1_layer2","title":"NEAR CLI - NEAR Docs","text":"The NEAR Command Line Interface (CLI) is a tool that enables you to interact with the NEAR network directly from the shell. Among other things, the NEAR CLI enables you to create and manage accounts, send tokens such as NEAR, FTs and NFTs, deploy smart contracts, call functions on those contracts, and manage access keys.\n​\n\nInstallation\n\nnpm\n\nHomebrew\n\nCargo\n\nMac and Linux (binaries)\n\nWindows (binaries)\n\nnpm install -g near-cli-rs@latest\n\nbrew install near\n\ncargo install near-cli-rs\n\ncurl --proto '=https' --tlsv1.2 -LsSf https://github.com/near/near-cli-rs/releases/latest/download/near-cli-rs-installer.sh | sh\n\nirm https://github.com/near/near-cli-rs/releases/latest/download/near-cli-rs-installer.ps1 | iex\n\n​\n\nConfiguration file\n\nThe directory with access keys and available connection networks are defined in the configuration file (near-cli/config.toml), which is located depending on the operating system in the following places:\n\nmacOS: $HOME/Library/Application Support (e.g. /Users/Alice/Library/Application Support)\n\nLinux: $XDG_CONFIG_HOME or $HOME/.config (e.g. /home/alice/.config)\n\nWindows: {FOLDERID_RoamingAppData} (e.g. C:\\Users\\Alice\\AppData\\Roaming)\n\nYou can learn more about working with the configuration file here.\n\nYou can set up a custom RPC server by changing the rpc_url parameter in near-cli settings:\n\nnear config edit-connection testnet --key rpc_url --value https://archival-rpc.testnet.near.org/\n\n​\n\nLocalnet configuration values\n\nWhen setting up a localnet connection with near config add-connection, several optional fields can be configured. Most of them can be skipped or set to placeholder URLs — they are only used for specific commands and are not required for basic localnet usage.\nFieldPurposeLocalnet recommendation\nrpc_url\nRPC endpoint for all blockchain interactions\nhttp://localhost:3030/\n\nwallet_url\nUsed to construct a URL for importing accounts from a Web wallet\nAny URL (e.g. http://localhost) or a local wallet if available\n\nexplorer_transaction_url\nPrinted after a transaction is signed as <url>/<tx-hash>\nAny URL (e.g. http://localhost) or omit\n\nlinkdrop_account_id\nAccount with the near-linkdrop contract, used by account create-account fund-myself\nCan be skipped; use testnet as a placeholder if needed\n\nnear_social_db_contract_account_id\nNEAR Social contract account, used for account view-account-summary and account update-social-profile\nCan be skipped\n\nfaucet_url\nService that creates new accounts without requiring NEAR tokens, used by account create-account sponsor-by-faucet-service\nCan be skipped\n\nfastnear_url\nFastNEAR API for fetching staking pool delegations, used by account view-account-summary\nCan be skipped\n\nstaking_pools_factory_account_id\nFallback to FastNEAR — queries all staking pools individually; used by account view-account-summary\nCan be skipped\n\nmpc_contract_account_id\nMPC signing service contract, used to sign payloads and control other accounts\nCan be skipped unless running a local MPC node\n\nA minimal localnet connection requires only rpc_url. The other values are only needed when using the specific commands listed above.\n\nnear config add-connection \\\n--network-name localnet \\\n--connection-name localnet-sandbox \\\n--rpc-url http://localhost:3030/ \\\n--wallet-url http://localhost/ \\\n--explorer-transaction-url http://localhost/\n\n​\n\nInteractive mode\n\nTo use the near-cli simply run the following in your terminal.\n\nnear\n\nYou should then see the following. Use the arrow keys and hit enter or simply type out one of the available options to select an option.\n\nWe provide examples only of the most used commands. Such commands may have two versions — a full one and a short one. If you want to explore all options provided by near-cli, use the interactive mode described above.\n\n​\n\nAccount\n\nThis option will allow you to manage, control, and retrieve information on your accounts.\n​\n\nSummary\n\nview-account-summary - view properties for an account.\nFull\n\nShort\n\nexport ACCOUNT_ID=bob.testnet\nnear account view-account-summary $ACCOUNT_ID network-config testnet now\n\nexport ACCOUNT_ID=bob.testnet\nnear state $ACCOUNT_ID --networkId testnet\n\n​\n\nImport\n\nimport-account - import existing account (a.k.a. “sign in”).\nFull\n\nShort\n\nnear account import-account using-web-wallet network-config testnet\n\nnear login --networkId testnet\n\n​\n\nExport\n\nexport-account - export existing account.\n\nexport ACCOUNT_ID=bob.testnet\nnear account export-account $ACCOUNT_ID using-web-wallet network-config testnet\n\n​\n\nCreate\n\ncreate-account - create a new account.\nFull\n\nShort\n\nexport ACCOUNT_ID=bob.testnet\nnear account create-account sponsor-by-faucet-service $ACCOUNT_ID autogenerate-new-keypair save-to-keychain network-config testnet create\n\nexport ACCOUNT_ID=bob.testnet\nnear create-account $ACCOUNT_ID --useFaucet --networkId testnet\n\n​\n\nDelete\n\ndelete-account - delete an account.\nFull\n\nShort\n\nexport ACCOUNT_ID=bob.testnet\nexport BENEFICIARY_ID=alice.testnet\n\nnear account delete-account $ACCOUNT_ID beneficiary $BENEFICIARY_ID network-config testnet sign-with-keychain send\n\nexport ACCOUNT_ID=bob.testnet\nexport BENEFICIARY_ID=alice.testnet\n\nnear delete-account $ACCOUNT_ID $BENEFICIARY_ID --networkId testnet\n\n​\n\nKeys\n\nGenerating, showing, adding and removing account keys. NEAR keys can use any of the supported signature schemes: ed25519 (default), secp256k1, or the post-quantum ml-dsa-65.\n​\n\nGenerate a key pair\n\ngenerate-keypair - create a fresh key pair offline, without touching an account or the network. Use --signature-scheme to choose the scheme (defaults to ed25519).\nEd25519\n\nML-DSA-65 (post-quantum)\n\n# Print a new key pair to the terminal\nnear generate-keypair print-to-terminal\n\n# ...or save it to a JSON file\nnear generate-keypair save-to-file ./my-key.json\n\n# Print a new post-quantum key pair to the terminal\nnear generate-keypair --signature-scheme ml-dsa-65 print-to-terminal\n\n# ...or save it to a JSON file\nnear generate-keypair --signature-scheme ml-dsa-65 save-to-file ./pq-key.json\n\nRun in an interactive terminal without --signature-scheme and the CLI prompts you to pick a scheme; otherwise it defaults to ed25519. Unlike ed25519, ml-dsa-65 key pairs are generated randomly and have no seed phrase or implicit-account address — be sure to back up the saved key file.\n\n​\n\nList keys\n\nlist-keys - view a list of keys for an account.\nFull\n\nShort\n\nexport ACCOUNT_ID=bob.testnet\nnear account list-keys $ACCOUNT_ID network-config testnet now\n\nexport ACCOUNT_ID=bob.testnet\nnear list-keys $ACCOUNT_ID --networkId testnet\n\n​\n\nAdd key\n\nadd-key - add an access key to an account.\nFull\n\nShort\n\nexport ACCOUNT_ID=bob.testnet\nnear account add-key $ACCOUNT_ID grant-full-access use-manually-provided-public-key ed25519:CXqAs8c8kZz81josLw82RQsnZXk8CAdUo7jAuN7uSht2 network-config testnet sign-with-keychain send\n\nexport ACCOUNT_ID=bob.testnet\nnear add-key $ACCOUNT_ID ed25519:CXqAs8c8kZz81josLw82RQsnZXk8CAdUo7jAuN7uSht2 --networkId testnet\n\nInstead of providing a key, you can have the CLI autogenerate one and add it in a single step with autogenerate-new-keypair --signature-scheme <scheme>:\nEd25519\n\nML-DSA-65 (post-quantum)\n\nexport ACCOUNT_ID=bob.testnet\nnear account add-key $ACCOUNT_ID grant-full-access autogenerate-new-keypair save-to-keychain network-config testnet sign-with-keychain send\n\nexport ACCOUNT_ID=bob.testnet\nnear account add-key $ACCOUNT_ID grant-full-access autogenerate-new-keypair --signature-scheme ml-dsa-65 save-to-keychain network-config testnet sign-with-keychain send\n\nThe same --signature-scheme flag is available on the account create-account fund-myself and sponsor-by-faucet-service autogenerate flows. You can also add an externally generated ml-dsa-65:<base58> key through the use-manually-provided-public-key flow shown above. An ml-dsa-65 key has no implicit-account form — you can’t derive a new implicit account from one — but you can add it to any existing account, named or implicit, just like any other key.\n\n​\n\nDelete key\n\ndelete-keys - delete an access key from an account.\nFull\n\nShort\n\nexport ACCOUNT_ID=bob.testnet\nnear account delete-keys $ACCOUNT_ID public-keys ed25519:HdkFZFEPoWfgrrLK3R4t5dWtNoLC8WymBzhCXoP3zrjh network-config testnet sign-with-keychain send\n\nexport ACCOUNT_ID=bob.testnet\nnear delete-key $ACCOUNT_ID ed25519:HdkFZFEPoWfgrrLK3R4t5dWtNoLC8WymBzhCXoP3zrjh --networkId testnet\n\nThe interactive key picker only lists ed25519 and secp256k1 keys. A post-quantum ml-dsa-65 key is stored on-chain only as a hash, so its full public key can’t be read back from the network — to delete one, pass the full ml-dsa-65:<base58> key explicitly to the public-keys argument of near account delete-keys (the full command form shown above).\n\n​\n\nGas keys\n\nGas keys are access keys with their own prepaid gas balance and up to 1,024 parallel nonces. The add-key command can create them through the grant-gas-key-full-access and grant-gas-key-function-call modes, and dedicated commands manage their balance and nonces.\nA gas key is always created empty — fund it with fund-gas-key before using it:\n\nexport ACCOUNT_ID=bob.testnet\n\n# Create a full-access gas key with 8 parallel nonces\nnear account add-key $ACCOUNT_ID grant-gas-key-full-access --num-nonces 8 autogenerate-new-keypair save-to-keychain network-config testnet sign-with-keychain send\n\n# Transfer 5 NEAR from the account into the gas key's balance\nnear account fund-gas-key $ACCOUNT_ID ed25519:CXqAs8c8kZz81josLw82RQsnZXk8CAdUo7jAuN7uSht2 '5 NEAR' network-config testnet sign-with-keychain send\n\n# View the current nonce of each of the key's lanes\nnear account view-gas-key-nonces $ACCOUNT_ID ed25519:CXqAs8c8kZz81josLw82RQsnZXk8CAdUo7jAuN7uSht2 network-config testnet now\n\n# Move 2 NEAR from the gas key's balance back to the account\nnear account withdraw-from-gas-key $ACCOUNT_ID ed25519:CXqAs8c8kZz81josLw82RQsnZXk8CAdUo7jAuN7uSht2 '2 NEAR' network-config testnet sign-with-keychain send\n\nTo sign a transaction with a gas key, pass --nonce-index to the signing option to choose which nonce lane to use (defaults to lane 0):\n\nnear tokens $ACCOUNT_ID send-near alice.testnet '1 NEAR' network-config testnet sign-with-keychain --nonce-index 3 send\n\nGas keys also work with meta transactions. The CLI signs as a delegate action when the selected network connection has a relayer configured (a meta_transaction_relayer_url, set on the connection with near config add-connection). Signing such a transaction with --nonce-index then produces a DelegateV2 delegate action bound to that nonce lane, which the relayer wraps and pays for.\n\nDeleting a gas key burns any balance left on it, and fails if the balance exceeds 1 NEAR — withdraw first with withdraw-from-gas-key, then delete with the regular delete-keys command. Gas-key meta transactions are supported for all software signers; Ledger is the exception, since the device firmware cannot yet produce a DelegateV2 signature.\n\n​\n\nTokens\n\nThis will allow you to manage your token assets such as NEAR, FTs and NFTs.\n​\n\nSend NEAR\n\nsend-near - transfers NEAR to a specified recipient in units of NEAR or yoctoNEAR.\nFull\n\nShort\n\nexport ACCOUNT_ID=bob.testnet\nexport RECEIVER_ID=alice.testnet\nnear tokens $ACCOUNT_ID send-near $RECEIVER_ID '0.5 NEAR' network-config testnet sign-with-keychain send\n\nexport ACCOUNT_ID=bob.testnet\nexport RECEIVER_ID=alice.testnet\n\nnear send-near $ACCOUNT_ID $RECEIVER_ID 0.5 --networkId testnet\n\n​\n\nSend FT\n\nsend-ft - transfer Fungible Tokens to a specified user.\n\nexport ACCOUNT_ID=bob.testnet\nexport RECEIVER_ID=alice.testnet\nexport FT_CONTRACT_ID=0c97251cd1f630c444dbusdt.testnet\n\nnear tokens $ACCOUNT_ID send-ft $FT_CONTRACT_ID $RECEIVER_ID amount-ft '1 USDT' prepaid-gas '100.0 Tgas' attached-deposit '1 yoctoNEAR' network-config testnet sign-with-keychain send\n\n​\n\nSend NFT\n\nsend-nft - transfers NFTs between accounts.\n\nexport ACCOUNT_ID=bob.testnet\nexport RECEIVER_ID=alice.testnet\nexport NFT_CONTRACT_ID=nft.examples.testnet\n\nnear tokens $ACCOUNT_ID send-nft $NFT_CONTRACT_ID $RECEIVER_ID 1 --prepaid-gas '100.0 Tgas' --attached-deposit '1 yoctoNEAR' network-config testnet sign-with-keychain send\n\n​\n\nView NEAR balance\n\nview-near-balance - view the balance of NEAR tokens.\n\nexport ACCOUNT_ID=bob.testnet\nnear tokens $ACCOUNT_ID view-near-balance network-config testnet now\n\n​\n\nView FT balance\n\nview-ft-balance - view the balance of Fungible Tokens.\n\nexport ACCOUNT_ID=bob.testnet\nexport FT_CONTRACT_ID=0c97251cd1f630c444dbusdt.testnet\nnear tokens $ACCOUNT_ID view-ft-balance $FT_CONTRACT_ID network-config testnet now\n\n​\n\nView NFT balance\n\nview-nft-assets - view the balance of NFT tokens.\n\nexport ACCOUNT_ID=bob.testnet\nexport NFT_CONTRACT_ID=nft.examples.testnet\nnear tokens $ACCOUNT_ID view-nft-assets $NFT_CONTRACT_ID network-config testnet now\n\n​\n\nContract\n\nThis option allows you to manage and interact with your smart contracts.\n​\n\nCall\n\ncall-function - execute function (contract method).\nFull\n\nShort\n\n# View method\nexport CONTRACT_ID=nft.examples.testnet\nnear contract call-function as-read-only $CONTRACT_ID nft_tokens json-args '{\"from_index\": \"0\", \"limit\": 2}' network-config testnet now\n\n# Call method\nexport ACCOUNT_ID=bob.testnet\nnear contract call-function as-transaction $CONTRACT_ID nft_mint json-args '{\"metadata\": {\"copies\": 1, \"description\": \"The Team Goes\", \"media\": \"https://bafybeidl4hjbpdr6u6xvlrizwxbrfcyqurzvcnn5xoilmcqbxfbdwrmp5m.ipfs.dweb.link/\", \"title\": \"GO TEAM\"}, \"receiver_id\": \"bob.testnet\", \"token_id\": \"5895\"}' prepaid-gas '100.0 Tgas' attached-deposit '0.1 NEAR' sign-as $ACCOUNT_ID network-config testnet sign-with-keychain send\n\n# View method\nexport CONTRACT_ID=nft.examples.testnet\nnear view $CONTRACT_ID nft_tokens '{\"from_index\": \"0\", \"limit\": 2}' --networkId testnet\n\n# Call method\nexport ACCOUNT_ID=bob.testnet\nnear call $CONTRACT_ID nft_mint '{\"metadata\": {\"copies\": 1, \"description\": \"The Team Goes\", \"media\": \"https://bafybeidl4hjbpdr6u6xvlrizwxbrfcyqurzvcnn5xoilmcqbxfbdwrmp5m.ipfs.dweb.link/\", \"title\": \"GO TEAM\"}, \"receiver_id\": \"bob.testnet\", \"token_id\": \"5896\"}' --deposit 0.1 --useAccount $ACCOUNT_ID --networkId testnet\n\n​\n\nDeploy\n\ndeploy - add a new contract code.\nFull\n\nShort\n\nexport CONTRACT_ID=contract.testnet\nnear contract deploy $CONTRACT_ID use-file ../target/near/contract.wasm without-init-call network-config testnet sign-with-keychain send\n\nexport CONTRACT_ID=contract.testnet\nnear deploy $CONTRACT_ID ../target/near/contract.wasm --networkId testnet\n\n​\n\nInspect\n\ninspect - get a list of available function names.\nFull\n\nShort\n\nexport CONTRACT_ID=nft.examples.testnet\nnear contract view-storage $CONTRACT_ID all as-text network-config testnet now\n\nexport CONTRACT_ID=nft.examples.testnet\nnear storage $CONTRACT_ID --finality final --utf8 --networkId testnet\n\n​\n\nTransaction\n\nOperate transactions.\n​\n\nView status\n\nview-status - view a transaction status.\nFull\n\nShort\n\nnear transaction view-status BFrVVtjqD2p1zYX1UCvn4nJpy7zPHpY5cTgQaKCZjBvw network-config testnet\n\nnear tx-status BFrVVtjqD2p1zYX1UCvn4nJpy7zPHpY5cTgQaKCZjBvw --networkId testnet\n\n​\n\nConfig\n\nManage the connection parameters inside the config.toml file for near-cli.\nThis will allow you to change or modify the network connections for your CLI.\n​\n\nShow connections\n\nshow-connections - show a list of network connections.\n\nnear config show-connections\n\n​\n\nEdit connection\n\nedit-connection - edit a network connection.\n\nnear config edit-connection testnet --key rpc_url --value https://test.rpc.fastnear.com\n\nWe provide examples only of the most used commands. If you want to explore all options provided by near-cli, use the interactive mode.\n\n​\n\nValidators\n\nYou can use the following commands to interact with the blockchain and view validator stats. There are three reports used to monitor validator status:\n\nProposals\n\nCurrent validators\n\nNext validators\n\nTo use these commands, you must install the CLI validator extension.\n\n​\n\nValidator extension\n\nIf you want to interact with NEAR Validators from command line, you can install the NEAR Validator CLI Extension:\nnpm\n\nCargo\n\nMac and Linux (binaries)\n\nWindows (binaries)\n\nnpm install -g near-validator\n\ncargo install near-validator\n\ncurl --proto '=https' --tlsv1.2 -LsSf https://github.com/near-cli-rs/near-validator-cli-rs/releases/latest/download/near-validator-installer.sh | sh\n\nirm https://github.com/near-cli-rs/near-validator-cli-rs/releases/latest/download/near-validator-installer.ps1 | iex\n\n​\n\nProposals\n\nA proposal by a validator indicates they would like to enter the validator set. In order for a proposal to be accepted it must meet the minimum seat price.\n\nnear-validator proposals network-config mainnet\n\n​\n\nCurrent validators\n\nThis shows a list of active validators in the current epoch, the number of blocks produced, number of blocks expected, and online rate. Used to monitor if a validator is having issues.\n\nnear-validator validators network-config mainnet now\n\n​\n\nNext validators\n\nThis shows validators whose proposal was accepted one epoch ago, and that will enter the validator set in the next epoch.\n\nnear-validator validators network-config mainnet next\n\n​\n\nStaking\n\nFor validators, there’s also an option to stake NEAR tokens without deploying a staking pool smart contract.\n​\n\nView validator stake\n\nTo view the validator’s stake on the last block:\n\nnear-validator staking view-stake examples.testnet network-config testnet now\n\n​\n\nStake directly without a staking pool\n\nTo stake the amount:\n\nnear-validator staking stake-proposal examples.testnet ed25519:AiEo5xepXjY7ChihZJ6AsfoDAaUowhPgvQp997qnFuRP '1500 NEAR' network-config testnet sign-with-keychain send\n\n​\n\nUnstake directly without a staking pool\n\nTo unstake:\n\nnear-validator staking unstake-proposal examples.testnet ed25519:AiEo5xepXjY7ChihZJ6AsfoDAaUowhPgvQp997qnFuRP network-config testnet sign-with-keychain send\n\nWas this page helpful?","tokens":4449,"crawled_at":1791193575705}
+{"id":10255,"url":"https://www.metaplex.com/docs/solana/understanding-programs","domain":"www.metaplex.com","chapter":"docs","title":"Understanding Programs | Developer Hub","text":"This page aims to provide a quick overview of how programs work in Solana and offer additional reading material for those who are interested in learning more about a particular subject.\nIntroduction\nUnlike most blockchains, Solana separates logic and data into two separate components. These are, respectively, Programs and Accounts. What that means is that instead of storing data inside variables internally, Programs interact with external data stored in Accounts with the ability to mutate them.\nThis architecture is great for making Programs more modular since the data they interact with is not bound by the Program itself and can scale to new orders of magnitude. It is also great for making Programs more performant since it allows the blockchain to run the same Program in parallel with different Accounts.\nTo interact with a Program, we must use the Instructions defined by that Program. You can think of Instructions as API endpoints exposed by the Program. Each Instruction contains a set of parameters and constraints that must be fulfilled to execute it.\nTo recap: In Solana, Programs define Instructions that can be used to interact with external data stores called Accounts.\nNote that, technically, Programs are special kinds of Accounts marked as executable whose entire purpose is to store the compiled code of the Program. However, for the sake of simplicity, we will distinguish these definitions and use the term \"Account\" to refer to non-executable Accounts.\nIn the rest of this guide, we will talk about Accounts and Instructions in more detail before explaining the visual representation that we will be using in diagrams throughout the documentation.\n📚 Additional reading:\nSolana Documentation — On-chain Programs\nSolana Cookbook — Programs\nThe Anchor Book — Intro to Programming on Solana\nAccounts\nIn Solana, Accounts are used to store data. In essence, they are simple arrays of bytes stored at a particular address. The address of an Account is the public key of a cryptographic key pair.\nAnyone that has access to the private key of that key pair, can sign on behalf of that Account which, depending on the program, may give them the ability to mutate the data stored in that Account.\nOnce an Account is created, it is usually immediately initialized by a Program which will be marked as its Owner and will define the data structure of the allocated array of bytes. The Program that owns the Account is then responsible for providing Instructions that can be used to interact with it.\n📚 Additional reading:\nSolana Documentation — Accounts\nSolana Cookbook — Accounts\nProgram Derived Addresses (PDA)\nThere exist another type of Account, called Program Derived Account, whose address is not the public key of a cryptographic key pair but instead is algorithmically derived from the public key of the Program that owns the Account. We call that address a Program Derived Address or PDA for short.\nSince the address is always derived from the public key of the Program, no other Program can algorithmically derive the same address. On top of that, additional Seeds can be provided to the algorithm to add more context to the address.\nThis has a variety of use cases such as enabling programs to sign Cross-Program Invocations or enabling the creation of accounts within an address that can be derived deterministically.\nNote that, by design, Program Derived Addresses will never conflict with cryptographically generated public keys. All cryptographic public keys are part of what we call an Elliptic-curve. If, when generating a PDA, the algorithm generated a key that falls on that curve, a Bump is added to the address and is incremented by one until the generated address no longer falls on the curve.\n📚 Additional reading:\nSolana Documentation — PDAs\nSolana Cookbook — PDAs\nAccount data\nWhether we are dealing with a regular Account or a Program Derived Account, Accounts store data as a serialized array of bytes. Therefore, it is the responsibility of the Program to define a data structure for each of the Accounts it manages as well as provide a way of differentiating these Accounts, so we know which data structure to apply to them.\nDiscriminators\nDiscriminators are used to differentiate between different types of Accounts within a Program. They can be implemented in many ways but here are the three most common ones:\nUse a shared Enum as the first byte of every account. By prefixing every Account with a shared Enum, we can use the first byte of the serialized data to identify the Account. This is a simple and efficient way to implement discriminators. Most of the programs maintained by Metaplex use this approach.\nUse a deterministic hash as the first byte of every account. This is very similar to the previous point, but it uses a hash instead of an Enum. Programs created using the Anchor framework end up using this approach implicitly because Anchor will automatically generate that hash based on the Account's name.\nNo discriminator, use the size of the Account. If all the accounts managed by a Program have different sizes, then we can examine the length of that array of bytes to determine which Account we are dealing with. This is a performant approach since we don't need to add extra bytes to the data, but it limits how flexible a Program can be with its Accounts. The SPL Token Program by Solana uses this approach since it only maintains two accounts of different fixed sizes.\nField types, sizes and offsets\nEach Account defines its own data structure by using fields of different types. These types will affect the number of bytes required to store the field. For instance, an i8 is an 8-bit integer that will require 1 byte to store whereas an i64 is a 64-bit integer which will require 8 bytes to store.\nSince, in the blockchain, Accounts are just arrays of bytes, it is important to understand the size of each field and where they start in this array, i.e. their offset. This can be useful when fetching multiple accounts from a given program using a memcmp filter.\nNote that not all fields have a fixed size. For instance, a Vec<i8> is a vector of 8-bit integers that may contain none, one or many items. As such, it becomes a lot more complicated to filter accounts based on fields that are located after the first field of variable size.\nOptional fields\nA field can also be defined as optional, meaning there exists a scenario where that field can be empty.\nThis field will use an additional byte as a prefix to indicate whether the field is empty or not.\nConcretely, the value None will be assigned and the program will act accordingly when using that field.\nIndicative fields\nWhilst this is not something that is explicitly defined in the data structure, the documentation will mark certain fields as indicative.\nAn indicative field means that the information provided by the field is not used by the program itself. Instead, it indicates a piece of information to third parties. The program will still enforce the integrity of the data, but it will simply not use that information internally.\nLet’s take the Metadata Account as an example.\nThe Share property of each creator in the Creators array is indicative. The Token Metadata program will ensure that the Share values of all creators add up to 100%, but it will not do anything with that information. Instead, it expects NFT marketplaces to use this information when distributing royalties.\nOn the other hand, the Is Mutable property is not indicative because the Token Metadata program will use that information internally to prevent immutable Metadata Accounts to be updated.\nInstructions\nOne can interact with a Program using the Instructions it provides. Multiple Instructions can be packed into a single Transaction that will be sent to the blockchain. Each Transaction is atomic meaning if any of its instructions fails, the whole Transaction will be reverted.\nSimilarly to Accounts, Instructions must be serialized into an array of bytes before they can be sent to the network. The data to be serialized must contain the following information for the Program to execute it.\nDiscriminator: Similarly to Accounts, Instructions are usually prefixed with a discriminator so the Program can identify which Instruction is being executed.\nAccounts: An array of Account addresses that are affected by this instruction. This can either be because the Account will be read, mutated or both. Note that the order of this array is important since Programs will identify the type of Account provided based on its position.\nArguments: An array of data fields required by the instruction. It is not uncommon for this array to be empty since Instructions can get most of their information directly from the Accounts. Note that these arguments are comparable to the fields of an Account and, therefore, they can have the same properties mentioned above such as \"optional\" and \"indicative\".\nSigners: An array of signatures for a sub-set of the Accounts provided. This is only needed for Accounts that are required to sign the Instruction. The next section explains this in a bit more detail.\n📚 Additional reading:\nSolana Documentation — Transactions\nSolana Documentation — Instructions\nSolana Cookbook — Transactions\nSigner and/or Writable Accounts\nA Program may require that the Accounts provided within an Instruction are Signers and/or Writable.\nSigners: A Signer Account is required to sign the Transaction for the Instruction to be successful. By attaching a signature, users can prove that they are the owner of the Account.\nWritable: A Writable Account will be mutated by the Instruction. This information is important for the blockchain to know which Transactions can be run in parallel and which ones can't.\nTherefore, with these two booleans, we end up with the following four possible scenarios:\nNon-Signer and Non-Writable: This Account is only used to read data. We cannot mutate it and we cannot make any assumption about its ownership.\nSigner and Non-Writable: This Account can also not be mutated, but we know that the user who sent the Transaction owns its private key. This enables Programs to grant or deny access to certain actions.\nSigner and Writable: This Account has both signed the Transaction and it can be mutated by the Instruction. This combination is pretty common since Programs will usually require the owner of an Account to prove who they are before mutating that account. Otherwise, anyone could mutate any Account they don't own.\nNon-Signer and Writable: This Account can be mutated, but we can't make any assumption about its ownership. That usually means that the Program is using other Signer Accounts to prove they can mutate that one. This is also the case for PDA Accounts since they are owned by the Program and, as such, they require the Program to keep track of Authorities that can mutate them. Also, note that certain actions like crediting lamports to an Account do not require the Account to sign the Transaction.\nCross-Program Invocations (CPI)\nCross-Program Invocations allow Programs to execute nested Instructions within their Instructions. They can use Instructions from their own Program and/or from other Programs.\n📚 Additional reading:\nSolana Documentation — CPI\nUsing CPIs with Anchor Programs","tokens":2818,"crawled_at":1791193577807}
+{"id":10256,"url":"https://docs.dydx.xyz/indexer-client/websockets","domain":"docs.dydx.xyz","chapter":"defi_protocols","title":"dYdX Documentation","text":"The WebSockets API provides data feeds providing the trader real-time information.\n\nSee the guide for examples on how to use the WebSockets API.\n\nCommon schemas\n\nInteractions with the WebSockets endpoint is done using common base JSON schemas for all channels/feed types.\nFor specific feeds, see the following subsections.\n\nSubscribe\n\nUse the following schema to subscribe to a channel.\n\nJSON Schema\n\nParameterTypeDescription\ntype\nstring\nMessage type (subscribe).\n\nchannel\nstring\nFeed type identifier.\n\nid\nstring\nSelector for channel-specific data. Only used in some channels.\n\nbatched\nbool\nReduce incoming messages by batching contents.\n\nExample{\n\"type\": \"subscribe\",\n\"channel\": \"v4_trades\",\n\"id\": \"BTC-USD\",\n\"batched\": false\n}\n\nResponse\n\nParameterTypeDescription\ntype\nstring\nMessage type (subscribed).\n\nconnection_id\nstring\nString identifying the subscription.\n\nmessage_id\nint\nMessage sequence number sent on the subscription.\n\nid\nstring\nSelector for channel-specific data.\n\ncontents\nvalue\nChannel-specific initial data.\n\nUnsubscribe\n\nUse the following schema to unsubscribe from a channel.\nSimilar scheme to the subscribe schema, however with the unsubscribe type, and without the batched field.\n\nJSON Schema\n\nParameterTypeDescription\ntype\nstring\nMessage type (unsubscribe).\n\nchannel\nstring\nFeed type identifier.\n\nid\nstring\nSelector for channel-specific data.\n\nExample{\n\"type\": \"unsubscribe\",\n\"channel\": \"v4_trades\",\n\"id\": \"BTC-USD\"\n}\n\nResponse\n\nParameterTypeDescription\ntype\nstring\nMessage type (unsubscribed).\n\nconnection_id\nstring\nString identifying the subscription.\n\nchannel\nstring\nFeed type identifier.\n\nmessage_id\nint\nMessage sequence number sent on the subscription.\n\nid\nstring\nSelector for channel-specific data. Only used in some channels.\n\nData\n\nAfter subscription, the incoming messages will be serialized using the following schema.\n\nJSON Schema\n\nParameterTypeDescription\nconnection_id\nstring\nString identifying the subscription.\n\nchannel\nstring\nFeed type identifier.\n\nid\nstring\nSelector for channel-specific data. Only used in some channels.\n\nmessage_id\nint\nMessage sequence number sent on the subscription.\n\nversion\nstring\nProtocol identifier.\n\ncontents\nvalue\nChannel-specific message data.\n\nChannels\n\nThe available clients API is presented below.\nFor each, the subscription and unsubscription functions are shown. Internally, these functions send messages serialized in the subscribe and unsubscribe JSON schemas above.\n\nFor each channel/feed type the sub-schemas employed in the contents field of the received Data (after subscription) are shown.\n\nSubaccounts\n\nData feed of a subaccount. Data contains updates to the subaccount such as position, orders and fills updates.\n\nMethod Declaration\n\nPython\n# class `Subaccounts`\ndef subscribe(self, address: str, subaccount_number: int) -> Self\ndef unsubscribe(self, address: str, subaccount_number: int)\n\nSchema\n\nThe field id is a string containing the subaccount ID (address and subaccount number). It is formattted as {address}/{subaccount-number}.\n\nThe field contents is serialized using the following schemas.\n\nMessages\n\nInitialUpdate\nSubaccountsInitialMessage\nSubaccountsUpdateMessage *\n\nMarkets\n\nData feed of all dYdX markets. Data contains updates to all markets, including market parameters and oracle prices.\n\nMethod Declaration\n\nPython\n# class `Markets`\ndef subscribe(self, batched: bool = True) -> Self\ndef unsubscribe(self)\n\nSchema\n\nThe field id is not employed in the subscribe/unsubscribe schemas.\n\nThe field contents is serialized using the following schemas.\n\nMessages\n\nInitialUpdate\nMarketsInitialMessage\nMarketsUpdateMessage *\n\nTrades\n\nData feed of the trades on a market. Data contains order fills updates, such as the order side, price and size.\n\nMethod Declaration\n\nPython\n# class `Trades`\ndef subscribe(self, id: str, batched: bool = True) -> Self\ndef unsubscribe(self, id: str)\n\nSchema\n\nThe field id is the market/ticker as a string.\n\nThe field contents is serialized using the following schemas.\n\nMessages\n\nInitialUpdate\nTradesInitialMessage\nTradesUpdateMessage *\n\nOrders\n\nData feed of the orders of a market. Data contains lists of the bids and asks of the order book.\n\nMethod Declaration\n\nPython\n# class `OrderBook`\ndef subscribe(self, id: str, batched: bool = True) -> Self\ndef unsubscribe(self, id: str)\n\nSchema\n\nThe field id is the market/ticker as a string.\n\nThe field contents is serialized using the following schemas.\n\nMessages\n\nInitialUpdate\nOrdersInitialMessage\nOrdersUpdateMessage *\n\nCandles\n\nData feed of the candles of a market. Data contains updates for open, low, high, and close prices, trade volume, for a certain time resolution.\n\nMethod Declaration\n\nPython\n# class `Candles`\ndef subscribe(self, id: str, resolution: CandlesResolution, batched: bool = True) -> Self\ndef unsubscribe(self, id: str, resolution: CandlesResolution)\n\nSchema\n\nThe field id is a string containing the market and candle resolution. It is formatted as {market}/{resolution}.\n\nThe field contents is serialized using the following schemas.\n\nMessages\n\nInitialUpdate\nCandlesInitialMessage\nCandlesUpdateMessage *\n\nParent Subaccounts\n\nData feed of a parent subaccount. This channel returns similar data to the subaccount channel.\n\nA parent subaccount is a subaccount numbered between 0 and 127. Used for isolated position management by the dYdX frontend (web).\n\nMethod Declaration\n\nPython\n# Coming soon.\n\nSchema\n\nThe field id is a string containing the subaccount ID (address and subaccount number). It is formattted as {address}/{subaccount-number}.\n\nThe field contents is serialized using the following schemas.\n\nMessages\n\nInitialUpdate\nParentSubaccountsInitialMessage\nParentSubaccountsUpdateMessage *\n\nBlock Height\n\nData feed of current block height. Data contains the last block height and time.\n\nMethod Declaration\n\nPython\n\nUnification Plan\nAdd feed to Python, TS clients.\n\nSchema\n\nThe field id is not employed in the subscribe/unsubscribe schemas.\n\nThe field contents is serialized using the following schemas.\n\nMessages\n\nInitialUpdate\nBlockHeightInitialMessage\nBlockHeightUpdateMessage *","tokens":1518,"crawled_at":1791193587033}
+{"id":10257,"url":"https://gov.uniswap.org/t/uniswap-delegate-reward-application-thread/23838/8","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Uniswap Delegate Reward Application Thread - #8 by kfx - Uncategorized - Uniswap Governance","text":"Uniswap Delegate Reward Application Thread\n\nUncategorized\n\nkfx\n\nMay 15, 2024, 10:01am\n\n8\n\nApplicant name: atiselsts.eth\n\nLink to Delegate Forum Platform: https://gov.uniswap.org/t/atiselsts-eth-delegate-platform/22270\n\nLink to Snapshot Profile: https://snapshot.org/#/profile/0xAac35d953Ef23aE2E61a866ab93deA6eC0050bcD\n\nLink to Tally/ Agora/ onchain voting profile: https://www.tally.xyz/gov/uniswap/delegate/0xaac35d953ef23ae2e61a866ab93dea6ec0050bcd\n\nLink to the proposal that you authored or co-authored that passed the snapshot (Required if the voting power is less than 10k $UNI) : n/a\n\nLinks to the proposal that you authored or co-authored that passed the Onchain Vote: n/a\n\nJoined Uniswap Gov Workshop Before? If so, when?: No (but I’ll be in EthCC’s “GovSwap” this year).\n\nJoined Uniswap Community Call Before? If so, when?: Yes, January/February/March/April 2024.\n\nApplicant Summary including why interested in applying for the Program:\n\nI’m a researcher and consultant fascinated with the Uniswap protocol, professionally and academically involved with it since 2021. I have participated in Uniswap governance since July 2023, with near 100% voting rate, and have maintained active presence in the forum. My conflicts of interest are minimized, since I’m not a service provider for the DAO or professionally affiliated with DeFi protocols unrelated to Uniswap, which makes it fair to be compensated for my time spent on its governance activities here. In perspective, I’m looking forward to getting more actively involved in crafting proposals, especially v4-related ones.\n\n2 Likes\n\nshow post in topic\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nUniswap Delegate Reward Initiative - Cycle 4 Application and Results\n\nGovernance-Meta\n\n23\n\n868\n\nAugust 31, 2025\n\nUniswap Delegate Reward Initiative - Cycle 2 Application\n\nGovernance-Meta\n\n40\n\n1901\n\nSeptember 16, 2024\n\nUniswap Delegate Reward Initiative - Cycle 3 Application and Results\n\nGovernance-Meta\n\n32\n\n1550\n\nMarch 11, 2025\n\nUniswap Delegate Reward Initiative - Cycle 4\n\nRequests for Comment\n\n11\n\n1015\n\nSeptember 2, 2025\n\n[RFC] Uniswap Delegate Reward Initiative - Cycle 2\n\nRequests for Comment\n\n25\n\n1306\n\nSeptember 3, 2024","tokens":548,"crawled_at":1791193590236}
+{"id":10258,"url":"https://docs.near.org/web3-apps/tutorials/meta-transactions","domain":"docs.near.org","chapter":"layer1_layer2","title":"Building a Meta Transaction Relayer - NEAR Docs","text":"Relayers serve to delegate gas fees to a web service, allowing users to transact on NEAR without the need to acquire the token themselves while still retaining the security of signing their own transactions. This guide will lead you through the components necessary to construct a relayer capable of handling meta transactions.\n\nIf you’re already acquainted with the technology and you just want to run your own Relayer, you can fast track to a complete Rust Relayer server open-source implementation.\n\n​\n\nHow it works\n\nA basic relayer consists of a web server housing a funded NEAR account. This account receives an encoded signed transaction, which can subsequently be decoded into a SignedDelegate format and transmitted on-chain.\nThe client can then generate a SignedDelegateAction (a signed message that hasn’t yet been sent), encode it, and transmit it to this server, where it will be relayed onto the blockchain.\n\n​\n\nRelayer (server)\n\nnear-api-js\n\n@near-relay/server\n\nHere’s a simple express endpoint that deserializes the body, instantiates the relayer account and then sends the transaction.Loading...\nSee code on GitHub\n\nYou can easily get the account object used to send the transactions from its private key using this snippetLoading...\nSee code on GitHub\n\nThe code in the example only works from the following versions onwards\n\n\"near-api-js\": \"3.0.4\"\n\"@near-js/transactions\": \"1.1.2\",\n\"@near-js/accounts\": \"1.0.4\"\n\n@near-relay simplifies meta transactions making it easier to get started for a beginner.To start, call the relay method inside an endpoint to automatically deserialize the transaction and send it with the account defined in the environment variables.Loading...\nSee code on GitHub\n\nIf you’re interested in relaying account creation as well, it’s quite straightforward. Simply create another endpoint and directly call the createAccount method with the accountId and publicKey. These parameters are automatically included in the body when using the corresponding client library.Loading...\nSee code on GitHub\n\n​\n\nClient\n\nnear-api-js\n\n@near-relay/client\n\nIn this method we are creating an arbitrary smart contract call, instantiating an account and using it to sign but not send the transaction. We can then serialize it and send it to the relayer where it will be delegated via the previously created endpoint.Loading...\nSee code on GitHub\n\nAs mentioned in the above note in order to be able to relay on the client side it’s necessary to have access to signing transactions directly on the client. Luckily leveraging the near biometric library it’s possible to do so in a non custodial way.By calling this method and passing in the URL for the account creation endpoint (mentioned in the server section) as well as the accountId everything is handled under the hood to successfully create an account.Loading...\nSee code on GitHub\n\nOn the client side, you just need to create an Action and pass it into the relayTransaction method along with the URL of the relayer endpoint discussed in the server section and the id of the receiverId.Loading...\nSee code on GitHub\n\nRelaying with wallets\n\nAt the moment, wallet selector standard doesn’t support signing transactions without immediately sending them. This functionality is essential for routing transactions to a relayer. Therefore, to smoothly integrate relaying on the client side, it’s necessary to be able to sign transactions without relying on wallets.\nProgress is being made to make this possible in the future.\n\n​\n\nHigh volume parallel processing\n\nWhen running a relayer that handles a large number of transactions, you will quickly run into a nonce collision problem. At the protocol level, transactions have a unique number that identifies them (nonce) that helps to mitigate reply attacks. Each key on an account has its own nonce, and the nonce is expected to increase with each signature the key creates.\nWhen multiple transactions are sent from the same access key simultaneously, their nonces might collide. Imagine the relayer creates 3 transactions Tx1, Tx2, Tx3 and send them in very short distance from each other, and lets assume that Tx3 has the largest nonce. If Tx3 ends up being processed before Tx1 (because of network delays, or a node picks Tx3 first), then Tx3 will execute, but Tx1 and Tx2 will fail, because they have smaller nonce!\nSince nearcore 2.13, the native solution to this problem is a gas key: a single access key with up to 1,024 independent nonce lanes and its own prepaid gas balance. The relayer signs each concurrent transaction on a different lane (via the transaction’s nonce_index), so nonces can never collide, and the gas spent on relaying is isolated from the account’s main balance. This replaces the key-rotation workaround below with one key to manage.\nOn earlier versions, the way to mitigate this is to sign each transaction with a different key. Adding multiple full access keys to the NEAR account used for relaying (up to 20 keys can make a significant difference) will help.\n\nAdding keys\n\nconst keyPair = nearAPI.KeyPair.fromRandom(\"ed25519\");\n\nconst receipt = await account.addKey(keyPair.getPublicKey().toString())\n\nAfter saving these keys, its possible to rotate the private keys randomly when instantiating accounts before relaying ensuring you won’t create a nonce collision.\n\n​\n\nGating the relayer\n\nIn most production applications it’s expected that you want to be able to gate the relayer to only be used in certain cases.\nThis can be easily accomplished by specifying constraints inside the SignedDelegate.delegateAction object.\n\nexport declare class DelegateAction extends Assignable {\nsenderId: string;\nreceiverId: string;\nactions: Array<Action>;\nnonce: BN;\nmaxBlockHeight: BN;\npublicKey: PublicKey;\n}\n\nYou can, for example, gate by some particular user or contract:\n\nconst serializedTx: Buffer = req.body;\nconst deserializedTx: SignedDelegate = deserialize(SCHEMA.SignedDelegate, Buffer.from(serializedTx)) as SignedDelegate;\nconst relayerAccount: Account = await getAccount(NETWORK_ID, RELAYER_ID, RELAYER_PRIVATE_KEY);\nconst delegateAction = deserializedTx?.delegateAction\n\nif(delegateAction.senderId == 'someUserId' || delegateAction.receiverId == 'someContractId' ){\nconst receipt = await relayerAccount.signAndSendTransaction({\nactions: [actionCreators.signedDelegate(deserializedTx)],\nreceiverId: deserializedTx.delegateAction.senderId\n});\n}\n\nOther examples could be looking into the actions and seeing if there is deposit or gas and limiting them, gating by particular smart contract methods or even args.\nYou can decode the args using:\n\nJSON.parse(Buffer.from(args_base64 || \"\", \"base64\").toString())\n\n​\n\nRust Relayer Server\n\nThe open-source Rust reference implementation of a Relayer server offers the following features:\n\nFeatures can be combined as needed. Use of one feature does not preclude the use of any other feature unless specified.\n\nSign and send Meta Transactions to the RPC to cover the gas costs of end users while allowing them to maintain custody of their funds and approve transactions (/relay, /send_meta_tx, /send_meta_tx_async, /send_meta_tx_nopoll)\n\nSign Meta Transactions returning a Signed Meta Transaction to be sent to the RPC later - (/sign_meta_tx, /sign_meta_tx_no_filter)\n\nOnly pay for users interacting with certain contracts by whitelisting contracts addresses (whitelisted_contracts in config.toml)\n\nSpecify gas cost allowances for all accounts (/update_all_allowances) or on a per-user account basis (/create_account_atomic, /register_account, /update_allowance) and keep track of allowances (/get_allowance)\n\nSpecify the accounts for which the relayer will cover gas fees (whitelisted_delegate_action_receiver_ids in config.toml)\n\nOnly allow users to register if they have a unique Oauth Token (/create_account_atomic, /register_account)\n\nRelayer Key Rotation: keys_filenames in config.toml\n\nIntegrate with FastAuth SDK\n\nMix and Match configuration options\n\nCheck the Use cases section for example configuration files corresponding to different usage scenarios.\n\n​\n\nBasic Setup\n\nYou can follow these steps to set up your local Relayer server development environment:\n\nInstall Rust for NEAR Development\n\nIf you don’t have a NEAR account, create one\n\nWith the account from step 2, create a JSON file in this directory in the format\n\n[{\"account_id\":\"example.testnet\",\"public_key\":\"ed25519:98GtfFzez3opomVpwa7i4m3nptHtc7Ha514XHMWszLtQ\",\"private_key\":\"ed25519:YWuyKVQHE3rJQYRC3pRGV56o1qEtA1PnMYPDEtroc5kX4A4mWrJwF7XkzGe7JWNMABbtY4XFDBJEzgLyfPkwpzC\"}]\n\nusing a Full Access Key from an account that has enough NEAR to cover the gas costs of transactions your server will be relaying. Usually, this will be a copy of the json file found in the .near-credentials directory.\n\nUpdate values in config.toml\n\nOpen up the port from config.toml in your machine’s network settings\n\nRun the server using cargo run.\n\n(OPTIONAL) To run with logs (tracing) enabled run RUST_LOG=tower_http=debug cargo run\n\nOptional setupIf you’re integrating with FastAuth make sure to enable feature flags:\n\ncargo build --features fastauth_features,shared_storage\n\nIf you’re using shared storage, make sure to enable feature flags:\n\ncargo build --features shared_storage\n\n​\n\nRedis Setup\n\nRedis is only needed when the relayer must persist per-account state. That applies if you want to:\nAllowances: track and limit how much gas each account can spend (e.g. /update_allowance, /get_allowance).\n\nOAuth (sybil resistance): require a unique OAuth token at signup so each real user can only register one account.\n\nWhitelisting contracts or senders does not need Redis — those are static lists in config.toml. See the Redis and FastAuth entries under Use cases for example configs that rely on Redis.\n\nInstall Redis.\n\nSteps 2 & 3 assume Redis was installed on machine instead of a Docker setup. If you’re connecting to a Redis instance running in GCP, follow the above steps to connect to a VM that will forward requests from your local relayer server to Redis running in GCP\n\nRun redis-server --bind 127.0.0.1 --port 6379 - make sure the port matches the redis_url in the config.toml.\n\nRun redis-cli -h 127.0.0.1 -p 6379\n\n​\n\nAdvanced setup\n\nMultiple Key Generation: this is optional, but recommended for high throughput to prevent nonce race conditions. Check\n\nDocker Deployment: instructions to deploy with Docker\n\nCloud Deployment: instructions to deploy on Cloud providers\n\n​\n\nAPI Specifications\n\nYou can find the complete Relayer server API specification on the GitHub repository.\n​\n\nUse cases\n\nThe examples folder on the GitHub repository contains example configuration files corresponding to different use cases.\n\nThese files are for reference only and you should update the config.toml values before using it on your development environment.\n\n​\n\nNo filters\n\nThis is a config for a relayer that covers gas for all user transactions to all contracts with no filters. To prevent abuse, this should only be used if there’s only a secure backend calling the relayer\n\nno_filters.toml\n\n​\n\nBasic whitelist\n\nThis is a configuration for a basic relayer that covers gas for user transactions to interact with a whitelisted set of contracts\n\nbasic_whitelist.toml\n\n​\n\nRedis\n\nThis is a configuration for a relayer that covers gas for user transactions up to a allowance specified in Redis to interact with a whitelisted set of contracts.\n\nAllowances are on a per-account id basis and on signup (account creation in Redis and on-chain) an OAuth token is required to help with sybil resistance\n\nredis.toml\n\n​\n\nFastAuth\n\nClosed access betaFastAuth is currently in a private beta stage. If you want to try it out during this early development stage, please contact us on Telegram.\n\nThis is a configuration for use if you intend to integrate with FastAuth SDK\n\nIt covers gas for user transactions up to a allowance specified in Redis to interact with a whitelisted set of contracts.\n\nAllowances are on a per-account id basis and on signup (account creation in Redis and on-chain) an OAuth token is required to help with sybil resistance\n\nThis also makes use of a shared storage functionality on the Near Social DB contract\n\nand a whitelisted sender (whitelisted_delegate_action_receiver_ids)\n\nfastauth.toml\n\n​\n\nPay with fungible tokens\n\nThis is a configuration for a relayer that ensures there’s FTs sent to a burn address used to cover the equivalent amount of gas for user transactions to interact with a whitelisted set of contracts\n\npay_with_ft.toml\n\n​\n\nWhitelist senders\n\nThis is a config for a relayer that covers gas for a whitelisted set of users’ transactions to interact with a whitelisted set of contracts\n\nwhitelist_senders.toml (whitelisted_delegate_action_receiver_ids)\n\n​\n\nShared storage\n\nThis is a configuration for a relayer that covers BOTH gas AND storage fees for user transactions to interact with a whitelisted set of contracts\n\nbe sure to include shared storage logic based on shared_storage.rs in your contract that is being whitelisted\n\nshared_storage.toml\n\n​\n\nExchange withdraw\n\nThis is a configuration for a relayer where an exchange running the relayer covers user withdraw fees when they are withdrawing stablecoins on NEAR (e.g., USDT or USDC)\n\nexchange_withdraw.toml\n\nWas this page helpful?","tokens":3314,"crawled_at":1791193594411}
+{"id":10259,"url":"https://www.metaplex.com/docs/solana/solana-programs","domain":"www.metaplex.com","chapter":"docs","title":"Solana Programs and State Overview | Guides","text":"Solana Programs\nSolana programs are executable code that runs on the Solana blockchain. They are similar to smart contracts on other blockchain platforms, but with some distinct characteristics and optimizations specific to Solana.\nKey Characteristics:\nStateless: Solana programs do not store state internally. Instead, state is stored in separate accounts on the chain.\nWritten in Rust: Programs are typically written in Rust.\nExecuted by Transactions: Programs are invoked by transactions that specify the program ID and the required accounts and data.\nAccounts\nAccounts used to store both data and SOL. Each account has an owner, which is a program that can modify its data.\nTypes of Accounts:\nData Accounts: Store arbitrary data used by programs.\nSPL Token Accounts: Manage token balances (similar to ERC-20 tokens on Ethereum).\nProgram Accounts: Contain the executable code of a Solana program.\nInstructions\nInstructions are operations sent to Solana programs. They are included in transactions and specify which accounts the program should operate on, as well as any additional data needed to perform the operation.\nKey Elements of Instructions:\nProgram ID: Identifies the program to be executed.\nAccounts: A list of accounts that the instruction will read from or write to.\nData: Custom data required to perform the instruction.\nState Management\nIn Solana, the state is managed externally from the programs, stored in accounts. This separation of state and logic enables higher scalability and efficiency.\nState Management Workflow:\nAccount Creation: Create accounts to store data.\nProgram Execution: Execute a program with instructions specifying which accounts to read from or write to.\nState Update: Programs modify the state by updating the data in accounts.\nExample Workflow\nDefine a Program:Write a program in Rust to perform a specific task, such as incrementing a counter.\n\nDeploy the Program:Compile and deploy the program to the Solana blockchain.\n\nCreate Accounts:Create accounts to store the program's state.\n\nSend Instructions:Send transactions containing instructions to invoke the program, specifying the accounts and data to use.\n\nExample Code\nBelow is a simple example of a Solana program written in Rust that increments a value stored in an account.\nuse solana_program::{\n\naccount_info::{next_account_info, AccountInfo},\n\nentrypoint,\n\nentrypoint::ProgramResult,\n\npubkey::Pubkey,\n\nmsg,\n\nprogram_error::ProgramError,\n\n};\n\nentrypoint!(process_instruction);\n\nfn process_instruction(\n\nprogram_id: &Pubkey,\n\naccounts: &[AccountInfo],\n\ninstruction_data: &[u8],\n\n) -> ProgramResult {\n\nlet accounts_iter = &mut accounts.iter();\n\nlet account = next_account_info(accounts_iter)?;\n\n// Ensure account is owned by the program\n\nif account.owner != program_id {\n\nmsg!(\"Account is not owned by the program\");\n\nreturn Err(ProgramError::IncorrectProgramId);\n\n}\n\n// Deserialize instruction data (increment value)\n\nlet increment_amount = instruction_data[0];\n\n// Increment the value\n\nlet mut data = account.try_borrow_mut_data()?;\n\ndata[0] = data[0].wrapping_add(increment_amount);\n\nmsg!(\"Value after increment: {}\", data[0]);\n\nOk(())\n\n}","tokens":786,"crawled_at":1791193596128}
+{"id":10260,"url":"https://www.metaplex.com/docs/solana/understanding-pdas","domain":"www.metaplex.com","chapter":"docs","title":"Understanding Solana Program Derived Addresses | Guides","text":"Overview\nProgram Derived Addresses (PDAs) are special types of account used on Solana that are deterministically derived and look like standard public keys, but have no associated private keys.\nOnly the program that derived the PDA can sign transactions involving the address/account. This is due to the fact that PDAs do not occur on the Ed25519 curve (elliptic-curve cryptography). Only addresses that appear on the curve can have a matching private key making PDAs a secure way of signing transactions from within a program. This means that no external user can generate a valid signature for the PDA address and sign on behalf of a pda/program.\nRole of PDAs\nPDAs are primarily used to:\nManage State: PDAs allow programs to create accounts and store data to a deterministic PDA address which allows read and write access for the program.\nAuthorize Transactions: Only the program that owns the PDA can authorize transactions involving it, ensuring secure controlled access. For example this allows programs and PDA accounts to store tokens/own NFTs that would require the current owner of the tokens/NFT to sign a transaction to transfer the items to another account.\nHow PDAs are Derived\nPDAs are derived using a combination of a program ID and a set of seed values. The derivation process involves hashing these values together and ensuring the resulting address is valid.\nDerivation Process\nSelect Program ID: The public key of the program for which the PDA is being derived.\nChoose Seeds: One or more seed values that, together with the program ID, will deterministically generate the PDA algorithmically based on the combined values.\nCompute PDA: Use the Pubkey::find_program_address function to derive the PDA. This function ensures the derived address is valid and cannot collide with any regular (non-PDA) address.\nExample in Rust\nHere's an example of deriving a PDA in a Solana program written in Rust:\nuse solana_program::{\n\npubkey::Pubkey,\n\nsystem_instruction,\n\nsystem_program,\n\nsysvar::rent::Rent,\n\nprogram::invoke_signed,\n\n};\n\n// Function to derive a PDA\n\nfn derive_pda(program_id: &Pubkey, seeds: &[&[u8]]) -> (Pubkey, u8) {\n\nPubkey::find_program_address(seeds, program_id)\n\n}\n\n// Example usage\n\nfn example_usage(program_id: &Pubkey) {\n\n// Define seeds\n\nlet seed1 = b\"seed1\";\n\nlet seed2 = b\"seed2\";\n\n// Derive PDA\n\nlet (pda, bump_seed) = derive_pda(program_id, &[seed1, seed2]);\n\n// Print PDA\n\nprintln!(\"Derived PDA: {}\", pda);\n\n}\n\nPractical Use Case: Account Creation Programs often use PDAs to create and manage program-specific accounts. Here's an example of how a PDA can be used to create an account:\n\nuse solana_program::{\n\npubkey::Pubkey,\n\nsystem_instruction,\n\nsystem_program,\n\nsysvar::rent::Rent,\n\nprogram::invoke_signed,\n\n};\n\nfn create_account_with_pda(\n\nprogram_id: &Pubkey,\n\npayer: &Pubkey,\n\nseeds: &[&[u8]],\n\nlamports: u64,\n\nspace: u64,\n\n) -> Result<(), ProgramError> {\n\nlet (pda, bump_seed) = Pubkey::find_program_address(seeds, program_id);\n\nlet create_account_ix = system_instruction::create_account(\n\npayer,\n\n&pda,\n\nlamports,\n\nspace,\n\nprogram_id,\n\n);\n\n// Sign the instruction with the PDA\n\nlet signers_seeds = &[&seeds[..], &[bump_seed]];\n\ninvoke_signed(\n\n&create_account_ix,\n\n&[payer_account_info, pda_account_info],\n\nsigners_seeds,\n\n)?;\n\nOk(())\n\n}","tokens":821,"crawled_at":1791193613908}
+{"id":10261,"url":"https://stack.olas.network/open-autonomy/advanced_reference/commands","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Open Autonomy CLI Overview - Olas Stack Developer Documentation","text":"Open Autonomy CLI Overview\n\nThis page provides a quick reference to commonly used CLI commands in the Open Autonomy framework. Each command has a brief description and basic usage example, with links to more detailed documentation.\n\nCore Commands\n\nautonomy analyse\n\nAnalyse an AI agent, including ABCI app specifications, docstrings, logs, and more.\n\nDetailed analyse documentation\n\nautonomy deploy\n\nDeploy an AI agent using various deployment backends (Docker, Kubernetes, or localhost).\n\nDetailed deploy documentation\n\nautonomy develop\n\nDevelopment tools for AI agents.\n\nDetailed develop documentation\n\nautonomy fetch\n\nFetch an agent blueprint or AI agent from a registry.\n\nDetailed fetch documentation\n\nautonomy mint\n\nMint components and AI agents on-chain.\n\nDetailed mint documentation\n\nautonomy push-all\n\nPush all available packages to a registry.\n\nDetailed push-all documentation\n\nautonomy replay\n\nReplay tools for AI agents.\n\nDetailed replay documentation\n\nautonomy service\n\nManage on-chain AI agents.\n\nDetailed AI agent documentation\n\nAdditional Information\n\nMost commands support the --help flag for detailed usage information\n\nCommands that interact with blockchains typically require a key file\n\nMany commands have additional options for customization and configuration\n\nSee the detailed command reference for complete documentation of each command\n\nCommon Options\n\nMany commands share common options:\n\n--registry: Specify the registry to use (default: remote)\n\n--chain: Select blockchain network (e.g., ethereum, polygon)\n\n--key: Path to key file for blockchain transactions\n\n--password: Password for encrypted key files\n\n--help: Show help message and exit","tokens":417,"crawled_at":1791193614645}
+{"id":10262,"url":"https://gov.uniswap.org/t/temp-check-forse-analytics-for-uniswap-revitalization-and-growth-program/24373/10","domain":"gov.uniswap.org","chapter":"governance_daos","title":"[Temp Check] Forse Analytics for Uniswap Revitalization and Growth Program - #10 by AbdullahUmar - Temperature Check - Uniswap Governance","text":"[Temp Check] Forse Analytics for Uniswap Revitalization and Growth Program\n\nTemperature Check\n\nAbdullahUmar\n\nAugust 12, 2024, 8:26pm\n\n10\n\nFirstly, someone does need to conduct a retrospective analysis on the efficacy of these incentive programs, especially if we wish to renew incentives or alter them in some capacity. So I’m directionally in favor of this proposal.\n\nAs per the above, not all of the programs have been terminated yet. Looks like Base is currently leading the race, which is good since those incentives have come to a conclusion. For anyone interested, here’s a more detailed overview of the Base program:\n\nScreenshot 2024-08-12 at 4.02.27 PM1920×960 170 KB\n\nScroll incentives ended on July 11th.\n\nBlast was divided into two parts. 50% of those incentives concluded July 2nd. The other 50% haven’t yet been deployed.\n\nLinea concluded on July 11th.\n\nMantle is still live.\n\nArbitrum LTIPP is still live.\n\n^Note: analysis will only be available for campaigns that have concluded. Those that are still live will require some wait time.\n\nCorrect–the BSC incentives haven’t been deployed yet since we are trying to finalize some of the bridging issues. This is the only campaign set that hasn’t begun yet. The Accountability Committee will keep you all posted.\n\n^This point is being overlooked…Arbitrum incentives were a part of the LTIPP matching program. Here’s some color on how the URGP differs from the LTIPP:\n\nThis proposal therefore isn’t limited to the URGP. Since there’s overwhelming support for Arbitrum right now, the DAO should note that this analysis will be reviewing Gauntlet’s distribution, which is far more sophisticated than the URGP method for distribution. It could be beneficial to contrast the two methods, however. We may see that a simple, heuristics-based approach being used for the URGP isn’t effective enough (or it could reveal the contrary).\n\nI’m also interested in seeing the efficacy of incentive programs on EVMs that Uniswap is less dominant on. We already see a degree of success on Arbitrum and Base–but the majority of the URGP incentives actually go to new or less active EVMs. We are therefore voting for Scroll, Blast, and Base. Scroll incentives were deployed nearly a year after its mainnet launched. Blast incentives were deployed early-on, when Blast just went live. This would show how much benefit an early mover advantage yields. And Base would be a good case for studying how tied incentives are to a chain that is directionally doing well due to narratives like memecoins.\n\n5 Likes\n\nArana Digital Delegate Platform\n\nArana Digital Delegate Platform\n\nshow post in topic\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[RFC] Analytics Hub for Uniswap's Revitalization and Growth Program\n\nRequests for Comment\n\n11\n\n592\n\nMay 8, 2025\n\n[RFC] Forse for Uniswap Analytics for Uniswap Revitalization and Growth Program\n\nRequests for Comment\n\n0\n\n249\n\nJuly 27, 2024\n\n[Governance Proposal] Uniswap Unleashed: Unichain and Uniswap v4 Liquidity Incentives\n\nRequests for Comment\n\n44\n\n10632\n\nApril 22, 2025\n\nUniswap Incentive Design Analysis\n\nGovernance-Meta\n\n10\n\n7858\n\nSeptember 15, 2023\n\nIntroducing the Uniswap Incentive Analysis Terminal by Forse\n\nUncategorized\n\n4\n\n658\n\nApril 16, 2025","tokens":809,"crawled_at":1791193617379}
+{"id":10263,"url":"https://docs.dydx.xyz/indexer-client/http","domain":"docs.dydx.xyz","chapter":"defi_protocols","title":"HTTP API – dYdX Documentation","text":"Accounts\n\nPython\naccount = indexer_client.account()\n\nGet Subaccounts\n\nRetrieves a list of subaccounts associated with a given address. Subaccounts are related addresses that fall under the authority or ownership of the primary address.\n\nMethod Declaration\n\nPython\nasync def get_subaccounts(\nself,\naddress: str,\nlimit: Optional[int] = None,\n) -> Any\n\nUnification Plan\nRust implementation doesn't have optional parameters.\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\npath\nAddress\ntrue\nThe primary address for which to retrieve associated subaccounts.\n\nlimit\nquery\nu32\nfalse\nMaximum number of subaccounts in the response.\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nAddressResponse\nThe subaccounts data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\nAPI Example\n\nGet Subaccount\n\nRetrieves a specific subaccount associated with a given address and subaccount number.\n\nMethod Declaration\n\nPython\nasync def get_subaccount(\nself,\naddress: str,\nsubaccount_number: int,\n) -> Any\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\nquery\nAddress\ntrue\nThe primary address to which the subaccount belongs.\n\nsubaccountNumber\nquery\nSubaccountNumber\ntrue\nThe specific subaccount number to retrieve.\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nSubaccountResponseObject ⛁\nThe subaccount data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe subaccount was not found.\n\nAPI Example\n\nList Positions\n\nRetrieves perpetual positions for a specific subaccount. Both open and closed/historical positions can be queried.\n\nMethod Declaration\n\nPython\nasync def get_subaccount_perpetual_positions(\nself,\naddress: str,\nsubaccount_number: int,\nstatus: Optional[PositionStatus] = None,\nlimit: Optional[int] = None,\ncreated_before_or_at_height: Optional[int] = None,\ncreated_before_or_at: Optional[str] = None,\n) -> Any\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\nquery\nAddress\ntrue\nThe wallet address that owns the account.\n\nsubaccountNumber\nquery\nSubaccountNumber\ntrue\nThe identifier for the specific subaccount within the wallet address.\n\nstatus\nquery\nPerpetualPositionStatus\nfalse\nFilter to retrieve positions with a specific status. If not provided, all positions will be returned regardless of status.\n\nlimit\nquery\nu32\nfalse\nMaximum number of asset positions to return in the response.\n\ncreatedBeforeOrAtHeight\nquery\nHeight\nfalse\nRestricts results to positions created at or before a specific blockchain height.\n\ncreatedBeforeOrAt\nquery\nDateTime\nfalse\nRestricts results to positions created at or before a specific timestamp (ISO 8601 format).\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nPerpetualPositionResponseObject ⛁\nThe perpetual positions data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe subaccount was not found.\n\nAPI Example\n\nExamples: Guide - List Positions\n\nGet Asset Positions\n\nRetrieves asset positions and respective details of a specific subaccount.\n\nMethod Declaration\n\nPython\nasync def get_subaccount_asset_positions(\nself,\naddress: str,\nsubaccount_number: int,\nstatus: Optional[PositionStatus] = None,\nlimit: Optional[int] = None,\ncreated_before_or_at_height: Optional[int] = None,\ncreated_before_or_at: Optional[str] = None,\n) -> Any\n\nUnification Plan\nRename all methods to get_asset_positions - shorter is better.\n\nAdd a Subaccount pair to Python and JavaScript, since it's always a pair\n\nAdd options to the Rust version\n\nRename created_before_or_at_time parameter to created_before_or_at\n\nRename PerpetualPositionStatus to PositionStatus\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\nquery\nAddress\ntrue\nThe wallet address that owns the account.\n\nsubaccountNumber\nquery\nSubaccountNumber\ntrue\nThe identifier for the specific subaccount within the wallet address.\n\nstatus\nquery\nPerpetualPositionStatus\nfalse\nFilter to retrieve positions with a specific status. If not provided, all positions will be returned regardless of status.\n\nlimit\nquery\nu32\nfalse\nMaximum number of asset positions to return in the response.\n\ncreatedBeforeOrAtHeight\nquery\nHeight\nfalse\nRestricts results to positions created at or before a specific blockchain height.\n\ncreatedBeforeOrAt\nquery\nDateTime\nfalse\nRestricts results to positions created at or before a specific timestamp (ISO 8601 format).\n\nResponse\n\nA data structure containing the requested asset positions. Typically includes details such as asset ID, size, side (buy/sell), entry price, realized PnL, and other position-specific information.\n\nStatusMeaningSchemaDescription\n200\nOK\nAssetPositionResponseObject ⛁\nThe asset positions data.\n\nAPI Example\n\nGet Transfers\n\nRetrieves the transfer history for a specific subaccount.\n\nMethod Declaration\n\nPython\nasync def get_subaccount_transfers(\nself,\naddress: str,\nsubaccount_number: int,\nlimit: Optional[int] = None,\ncreated_before_or_at_height: Optional[int] = None,\ncreated_before_or_at: Optional[str] = None,\n) -> Any\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\nquery\nAddress\ntrue\nThe wallet address that owns the account.\n\nsubaccount_number\nquery\nSubaccountNumber\ntrue\nThe identifier for the specific subaccount within the wallet address.\n\nlimit\nquery\nu32\nfalse\nMaximum number of items in the response.\n\ncreatedBeforeOrAtHeight\nquery\nHeight\nfalse\nRestricts results to positions created at or before a specific blockchain height.\n\ncreatedBeforeOrAt\nquery\nDateTime\nfalse\nRestricts results to positions created at or before a specific timestamp.\n\npage\nquery\nu32\nfalse\nThe page number for paginated results.\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nTransferResponseObject ⛁\nThe transfers data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe subaccount was not found.\n\nAPI Example\n\nGet Transfers Between\n\nFetch information regarding a transfer between two subaccounts.\n\nMethod Declaration\n\nPython\nasync def get_transfer_between(\nself,\nsource_address: str,\nsource_subaccount_number: int,\nrecipient_address: str,\nrecipient_subaccount_number: int,\ncreated_before_or_at_height: Optional[int] = None,\ncreated_before_or_at: Optional[str] = None,\n) -> Any\n\nUnification Plan\nResponse object does not have defined structure in TypeScript client. Will have to work on it.\n\nParameters\n\nParameterLocationTypeRequiredDescription\nsourceAddress\nquery\nstring\ntrue\nSender's wallet address\n\nsourceSubaccountNumber\nquery\nstring\ntrue\nThe identifier for the specific subaccount within the sender wallet address.\n\nrecipientAddress\nquery\nstring\ntrue\nReceiver wallet address\n\nrecipientSubaccountNumber\nquery\nstring\ntrue\nThe identifier for the specific subaccount within the receiver wallet address.\n\ncreatedBeforeOrAtHeight\nquery\nnumber\nfalse\nRestricts results to positions created at or before a specific blockchain height.\n\ncreatedBeforeOrAt\nquery\nstring\nfalse\nRestricts results to positions created at or before a specific timestamp (ISO 8601 format).\n\nResponse\n\nList Orders\n\nRetrieves orders for a specific subaccount, with various filtering options to narrow down the results based on order characteristics.\n\nMethod Declaration\n\nPython\nasync def get_subaccount_orders(\nself,\naddress: str,\nsubaccount_number: int,\nticker: Optional[str] = None,\nticker_type: TickerType = TickerType.PERPETUAL,\nside: Optional[OrderSide] = None,\nstatus: Optional[OrderStatus] = None,\ntype: Optional[OrderType] = None,\nlimit: Optional[int] = None,\ngood_til_block_before_or_at: Optional[int] = None,\ngood_til_block_time_before_or_at: Optional[str] = None,\nreturn_latest_orders: Optional[bool] = None,\n) -> Any\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\nquery\nAddress\ntrue\nThe wallet address that owns the account.\n\nsubaccountNumber\nquery\nSubaccountNumber\ntrue\nThe identifier for the specific subaccount within the wallet address.\n\nlimit\nquery\nu32\nfalse\nMaximum number of asset positions to return in the response.\n\nticker\nquery\nTicker\nfalse\nThe ticker filter.\n\nside\nquery\nOrderSide\nfalse\nThe order side filter.\n\nstatus\nquery\nOrderStatus\nfalse\nThe order status filter.\n\ntype\nquery\nOrderType\nfalse\nThe order type filter.\n\ngoodTilBlockBeforeOrAt\nquery\nHeight\nfalse\nThe block number filter for orders good until before or at.\n\ngoodTilBlockTimeBeforeOrAt\nquery\nDateTime in UTC\nfalse\nThe timestamp filter for orders good until before or at.\n\nreturnLatestOrders\nquery\nbool\nfalse\nWhether to return only the latest orders.\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nOrderResponseObject ⛁\nThe orders data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe subaccount was not found.\n\nAPI Example\nExamples: Guide - List Orders\n\nGet Order\n\nRetrieves detailed information about a specific order based on its unique identifier (the order ID).\nTo get the order ID, see how to create it or fetch the order history.\n\nMethod Declaration\n\nPython\nasync def get_order(\nself,\norder_id: str,\n) -> Any\n\nParameters\n\nParameterLocationTypeRequiredDescription\norderId\npath\nOrderId\ntrue\nThe order ID.\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nOrderResponseObject ⛁\nThe order data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe order was not found.\n\nAPI Example\n\nGet Fills\n\nRetrieves fill records for a specific subaccount on the exchange.\nA fill represents a trade that has been executed.\n\nMethod Declaration\n\nPython\nasync def get_subaccount_fills(\nself,\naddress: str,\nsubaccount_number: int,\nticker: Optional[str] = None,\nticker_type: TickerType = TickerType.PERPETUAL,\nlimit: Optional[int] = None,\ncreated_before_or_at_height: Optional[int] = None,\ncreated_before_or_at: Optional[str] = None,\n) -> Any\n\nUnification Plan\nRename all methods to get_fills - shorter is better.\n\nAdd a Subaccount pair to Python and JavaScript, since it's always a pair\n\nRename created_before_or_at_time parameter to created_before_or_at\n\npage optional parameter is missing in Python\n\npage optional parameter is missing in Rust\n\nIn Rust market field of the options struct must be ticker\n\nIn Rust market_type field of the options struct must be ticker_type\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\nquery\nAddress\ntrue\nThe wallet address that owns the account.\n\nsubaccountNumber\nquery\nSubaccountNumber\ntrue\nThe identifier for the specific subaccount within the wallet address.\n\nmarket\nquery\nTicker\nfalse\nThe market symbol to filter fills by (e.g., \"BTC-USD\"). If not provided, fills for all markets will be returned. (Python/TS SDK parameter: ticker)\n\nmarketType\nquery\nMarketType\nfalse\nThe type of market to filter by. (Python/TS SDK parameter: ticker_type / tickerType)\n\nlimit\nquery\nu32\nfalse\nMaximum number of asset positions to return in the response.\n\ncreatedBeforeOrAtHeight\nquery\nHeight\nfalse\nFilters results to positions created at or before a specific blockchain height.\n\ncreatedBeforeOrAt\nquery\nDateTime\nfalse\nFilters results to positions created at or before a specific timestamp (ISO 8601 format).\n\npage\nquery\nu32\nfalse\nThe page number for paginated results.\n\nResponse\n\nA promise that resolves to fill data containing details such as order ID, market, side (buy/sell), size, price, execution time, and other fill-specific information.\n\nStatusMeaningSchemaDescription\n200\nOK\nFillResponseObject ⛁\nThe fills data.\n\nAPI Example\nExamples: Guide - Get Fills\n\nGet Historical PNL\n\nRetrieves historical profit and loss (PNL) data for a specific subaccount on the exchange.\nThese records provide insights into the trading performance over time.\n\nMethod Declaration\n\nPython\nasync def get_subaccount_historical_pnls(\nself,\naddress: str,\nsubaccount_number: int,\neffective_before_or_at: Optional[str] = None,\neffective_at_or_after: Optional[str] = None,\n) -> Any\n\nUnification Plan\nParameter created_on_or_after_height is missing\n\nParameter created_on_or_after is missing\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\nquery\nAddress\ntrue\nThe wallet address that owns the account.\n\nsubaccount_number\nquery\nSubaccountNumber\ntrue\nThe identifier for the specific subaccount within the wallet address.\n\nlimit\nquery\nu32\nfalse\nMaximum number of asset positions to return in the response.\n\ncreatedBeforeOrAtHeight\nquery\nHeight\nfalse\nFilters results to positions created at or before a specific blockchain height.\n\ncreatedBeforeOrAt\nquery\nDateTime in UTC\nfalse\nFilters results to positions created at or before a specific timestamp (ISO 8601 format).\n\ncreatedOnOrAfterHeight\nquery\nHeight\nfalse\nFilters results to positions created on or after a specific blockchain height.\n\ncreatedOnOrAfter\nquery\nDateTime in UTC\nfalse\nFilters results to positions created on or after a specific timestamp (ISO 8601 format).\n\npage\nquery\nu32\nfalse\nThe page number for paginated results.\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nPnlTicksResponseObject ⛁\nThe historical PnLs data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe subaccount was not found.\n\nAPI Example\n\nGet Rewards\n\nRetrieves historical block trading rewards for the specified address.\n\nMethod Declaration\n\nPython\nasync def get_historical_block_trading_rewards(\nself,\naddress: str,\nlimit: Optional[int] = None,\n) -> Any\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\npath\nAddress\ntrue\nThe wallet address that owns the account.\n\nlimit\nquery\nu32\nfalse\nMaximum number of asset positions to return in the response.\n\nstartingBeforeOrAtHeight\nquery\nHeight\nfalse\nThe timestamp filter for rewards starting before or at.\n\nstartingBeforeOrAt\nquery\nDateTime in UTC\nfalse\nThe block height filter for rewards starting before or at.\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nHistoricalBlockTradingReward ⛁\nThe historical block trading rewards data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\nAPI Example\n\nGet Rewards Aggregated\n\nRetrieves aggregated historical trading rewards for the specified address.\n\nMethod Declaration\n\nPython\nasync def get_historical_trading_rewards_aggregated(\nself,\naddress: str,\nperiod: TradingRewardAggregationPeriod = TradingRewardAggregationPeriod.DAILY,\nlimit: Optional[int] = None,\nstarting_before_or_at: Optional[str] = None,\nstarting_before_or_at_height: Optional[int] = None,\n) -> Any\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\npath\nAddress\ntrue\nThe wallet address that owns the account.\n\nperiod\nquery\nTradingRewardAggregationPeriod\ntrue\nThe aggregation period.\n\nlimit\nquery\nu32\nfalse\nThe maximum number of aggregated rewards to retrieve.\n\nstartingBeforeOrAt\nquery\nDateTime\nfalse\nThe timestamp filter for rewards starting before or at.\n\nstartingBeforeOrAtHeight\nquery\nHeight\nfalse\nThe block height filter for rewards starting before or at.\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nHistoricalTradingRewardAggregation ⛁\nThe aggregated historical trading rewards data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\nAPI Example\n\nGet Parent Subaccount\n\nQuery for the parent subaccount, its child subaccounts, equity, collateral and margin. See more information on parent subaccounts here.\ne.g. parent subaccount 0 has child subaccounts 128, 256,...\n\nMethod Declaration\n\nPython\nasync def get_parent_subaccount(\nself,\naddress: str,\nsubaccount_number: int,\n) -> Any\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\npath\nAddress\ntrue\nThe wallet address that owns the parent subaccount.\n\nnumber\npath\nSubaccountNumber\ntrue\nThe identifier for the specific subaccount within the wallet address.\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nParentSubaccountResponseObject ⛁\nThe parent subaccount data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe parent subaccount was not found.\n\nAPI Example\n\nList Parent Positions\n\nList all positions of a parent subaccount.\n\nMethod Declaration\n\nPython\nasync def list_parent_orders(\nself,\naddress: str,\nsubaccount_number: int,\nlimit: Optional[int] = None,\nticker: Optional[str] = None,\nside: Optional[OrderSide] = None,\nstatus: Optional[OrderStatus] = None,\norder_type: Optional[OrderType] = None,\ngood_til_block_before_or_at: Optional[int] = None,\ngood_til_block_time_before_or_at: Optional[str] = None,\nreturn_latest_orders: Optional[bool] = None,\n) -> Any\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\nquery\nAddress\ntrue\nThe wallet address that owns the account.\n\nparentSubaccountNumber\nquery\nSubaccountNumber\ntrue\nSubaccount number of the parent subaccount.\n\nlimit\nquery\nu32\nfalse\nMaximum number of asset positions to return in the response.\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nPerpetualPositionResponseObject ⛁\nThe perpetual positions data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe subaccount was not found.\n\nAPI Example\n\nGet Parent Asset Positions\n\nQuery for asset positions (size, buy/sell etc) for a parent subaccount.\n\nMethod Declaration\n\nPython\nasync def get_parent_subaccount_asset_positions(\nself,\naddress: str,\nsubaccount_number: int,\nstatus: Optional[PositionStatus] = None,\nlimit: Optional[int] = None,\ncreated_before_or_at_height: Optional[int] = None,\ncreated_before_or_at: Optional[str] = None,\n) -> Any:\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\nquery\nAddress\ntrue\nThe wallet address that owns the account.\n\nparentSubaccountNumber\nquery\nSubaccountNumber\ntrue\nThe parent subaccount number of this wallet\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nAssetPositionResponseObject ⛁\nThe asset positions data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe parent subaccount was not found.\n\nAPI Example\n\nGet Parent Transfers\n\nQuery for transfers between subaccounts associated with a parent subaccount.\n\nMethod Declaration\n\nPython\nasync def get_parent_transfers(\nself,\naddress: str,\nsubaccount_number: int,\nlimit: Optional[int] = None,\ncreated_before_or_at_height: Optional[int] = None,\ncreated_before_or_at: Optional[str] = None,\n) -> Any\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\nquery\nAddress\ntrue\nThe wallet address that owns the parent subaccount.\n\nparentSubaccountNumber\nquery\nSubaccountNumber\ntrue\nThe identifier for the specific subaccount within the wallet address.\n\nlimit\nquery\nu32\nfalse\nMaximum number of asset positions to return in the response.\n\ncreatedBeforeOrAtHeight\nquery\nHeight\nfalse\nRestricts results to positions created at or before a specific blockchain height.\n\ncreatedBeforeOrAt\nquery\nDateTime in UTC\nfalse\nRestricts results to positions created at or before a specific timestamp (ISO 8601 format).\n\nResponse\n\nStatusMeaningSchema\n200\nOK\nTransferResponseObject ⛁\n\nAPI Example\n\nList Parent Orders\n\nQuery for orders filtered by order params of a parent subaccount.\n\nMethod Declaration\n\nPython\nasync def list_parent_orders(\nself,\naddress: str,\nsubaccount_number: int,\nlimit: Optional[int] = None,\nticker: Optional[str] = None,\nside: Optional[OrderSide] = None,\nstatus: Optional[OrderStatus] = None,\norder_type: Optional[OrderType] = None,\ngood_til_block_before_or_at: Optional[int] = None,\ngood_til_block_time_before_or_at: Optional[str] = None,\nreturn_latest_orders: Optional[bool] = None,\n) -> Any\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\nquery\nAddress\ntrue\nThe wallet address that owns the account.\n\nparentSubaccountNumber\nquery\nSubaccountNumber\ntrue\nParent subaccount number\n\nlimit\nquery\nu32\nfalse\nMaximum number of asset positions to return in the response.\n\nticker\nquery\nTicker\nfalse\nThe ticker filter.\n\nside\nquery\nOrderSide\nfalse\nThe order side filter.\n\nstatus\nquery\nOrderStatus\nfalse\nThe order status filter.\n\ntype\nquery\nOrderType\nfalse\nThe order type filter.\n\ngoodTilBlockBeforeOrAt\nquery\nHeight\nfalse\nThe block number filter for orders good until before or at.\n\ngoodTilBlockTimeBeforeOrAt\nquery\nDateTime in UTC\nfalse\nThe timestamp filter for orders good until before or at.\n\nreturnLatestOrders\nquery\nbool\nfalse\nWhether to return only the latest orders.\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nListOrdersResponse\nThe orders data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe subaccount was not found.\n\nAPI Example\n\nGet Parent Fills\n\nQuery for fills (i.e. filled orders data) for a parent subaccount.\n\nMethod Declaration\n\nPython\nasync def get_parent_fills(\nself,\naddress: str,\nsubaccount_number: int,\nlimit: Optional[int] = None,\nmarket: Optional[str] = None,\nmarket_type: Optional[TickerType] = None,\ncreated_before_or_at_height: Optional[int] = None,\ncreated_before_or_at: Optional[str] = None,\n) -> Any:\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\nquery\nAddress\ntrue\nThe wallet address that owns the parent subaccount.\n\nparentSubaccountNumber\nquery\nSubaccountNumber\ntrue\nThe identifier for the specific subaccount within the wallet address.\n\nlimit\nquery\nu32\nfalse\nMaximum number of asset positions to return in the response.\n\ncreatedBeforeOrAtHeight\nquery\nHeight\nfalse\nFilters results to positions created at or before a specific blockchain height.\n\nmarket\nquery\nTicker\nfalse\nMarket id like USD-BTC, ETH-USD\n\nmarketType\nquery\nMarketType\nfalse\nMarket type of filled order Data\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nFillResponseObject ⛁\nThe fills data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe parent subaccount was not found.\n\nAPI Example\n\nGet Parent Historical Pnl\n\nQuery for profit and loss report for the specified time/block range of a parent subaccount.\n\nMethod Declaration\n\nPython\nasync def get_parent_historical_pnls(\nself,\naddress: str,\nsubaccount_number: int,\nlimit: Optional[int] = None,\ncreated_before_or_at_height: Optional[int] = None,\ncreated_before_or_at: Optional[str] = None,\ncreated_on_or_after_height: Optional[int] = None,\ncreated_on_or_after: Optional[str] = None,\n) -> Any:\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\nquery\nAddress\ntrue\nThe wallet address that owns the parent subaccount.\n\nparentSubaccountNumber\nquery\nSubaccountNumber\ntrue\nThe identifier for the specific subaccount within the wallet address.\n\nlimit\nquery\nu32\nfalse\nMaximum number of asset positions to return in the response.\n\ncreatedBeforeOrAtHeight\nquery\nHeight\nfalse\nRestricts results to positions created at or before a specific blockchain height.\n\ncreatedBeforeOrAt\nquery\nDateTime in UTC\nfalse\nRestricts results to positions created at or before a specific timestamp (ISO 8601 format).\n\ncreatedOnOrAfterHeight\nquery\nHeight\nfalse\nRestricts results to positions created on or after a specific blockchain height.\n\ncreatedOnOrAfter\nquery\nDateTime in UTC\nfalse\nRestricts results to positions created on or after a specific timestamp (ISO 8601 format).\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nPnlTicksResponseObject ⛁\nThe historical PnLs data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe parent subaccount was not found.\n\nAPI Example\n\nGet Funding Payments\n\nRetrieves funding payment history for a specific subaccount.\nFunding payments are periodic settlements that occur between long and short positions based on the funding rate.\n\nMethod Declaration\n\nPython\nasync def get_funding_payments(\nself,\naddress: str,\nsubaccount_number: int,\nlimit: Optional[int] = None,\nticker: Optional[str] = None,\nafter_or_at: Optional[str] = None,\npage: Optional[int] = None,\n) -> Any\n\nUnification Plan\nRename all methods to get_funding_payments - shorter is better.\n\nAdd a Subaccount pair to Python and JavaScript, since it's always a pair\n\npage optional parameter is missing in Python\n\npage optional parameter is missing in Rust\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\nquery\nAddress\ntrue\nThe wallet address that owns the account.\n\nsubaccountNumber\nquery\nSubaccountNumber\ntrue\nThe identifier for the specific subaccount within the wallet address.\n\nlimit\nquery\nu32\nfalse\nMaximum number of funding payments to return in the response.\n\nticker\nquery\nTicker\nfalse\nThe market symbol to filter funding payments by (e.g., \"BTC-USD\"). If not provided, payments for all markets will be returned.\n\nafterOrAt\nquery\nDateTime\nfalse\nFilters results to funding payments created at or after a specific timestamp (ISO 8601 format).\n\npage\nquery\nu32\nfalse\nThe page number for paginated results.\n\nResponse\n\nA promise that resolves to funding payment data containing details such as payment amount, funding rate, position size, market ticker, and timestamp information.\n\nStatusMeaningSchemaDescription\n200\nOK\nFundingPaymentsResponseObject ⛁\nThe funding payments data.\n\nAPI Example\n\nGet Funding Payments for Parent Subaccount\n\nRetrieves funding payment history for all subaccounts under a parent subaccount.\nThis endpoint aggregates funding payments across all child subaccounts of a given parent subaccount.\n\nMethod Declaration\n\nPython\nasync def get_funding_payments_for_parent_subaccount(\nself,\naddress: str,\nparent_subaccount_number: int,\nlimit: Optional[int] = None,\nafter_or_at: Optional[str] = None,\npage: Optional[int] = None,\n) -> Any\n\nUnification Plan\nRename all methods to get_funding_payments_for_parent_subaccount - shorter is better.\n\nAdd a ParentSubaccount pair to Python and JavaScript, since it's always a pair\n\npage optional parameter is missing in Python\n\npage optional parameter is missing in Rust\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\nquery\nAddress\ntrue\nThe wallet address that owns the account.\n\nparentSubaccountNumber\nquery\nSubaccountNumber\ntrue\nThe identifier for the parent subaccount within the wallet address.\n\nlimit\nquery\nu32\nfalse\nMaximum number of funding payments to return in the response.\n\nafterOrAt\nquery\nDateTime\nfalse\nFilters results to funding payments created at or after a specific timestamp (ISO 8601 format).\n\npage\nquery\nu32\nfalse\nThe page number for paginated results.\n\nResponse\n\nA promise that resolves to funding payment data containing details such as payment amount, funding rate, position size, market ticker, and timestamp information aggregated across all child subaccounts.\n\nStatusMeaningSchemaDescription\n200\nOK\nFundingPaymentsResponseObject ⛁\nThe funding payments data.\n\nAPI Example\n\nMarkets\n\nTODO: How to access to the accounts space.\n\nPython\nmarket = indexer_client.markets()\n\nGet Perpetual Markets\n\nRetrieves perpetual markets.\n\nMethod Declaration\n\nPython\ndef get_perpetual_markets(self, market: str = None) -> Response\n\nUnification Plan\nAdd alias for the return type in Rust: PerpetualMarketsMap\n\nParameters\n\nParameterLocationTypeRequiredDescription\nmarket\nquery\nTicker\nfalse\nThe specific market ticker to retrieve. If not provided, all markets are returned.\n\nlimit\nquery\nu32\nfalse\nMaximum number of asset positions to return in the response.\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nPerpetualMarketMap\nThe perpetual markets data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe market was not found.\n\nAPI Example\n\nGet Perpetual Market Orderbook\n\nRetrieves the orderbook for a specific perpetual market.\n\nMethod Declaration\n\nPython\nasync def get_perpetual_market_orderbook(\nself,\nmarket: str,\n) -> dict\n\nParameters\n\nParameterLocationTypeRequiredDescription\nmarket\npath\nTicker\ntrue\nThe market ticker.\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nOrderBookResponseObject ⛁\nThe orderbook data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe market was not found.\n\nAPI Example\n\nGet Trades\n\nRetrieves trades for a specific perpetual market.\n\nMethod Declaration\n\nPython\nasync def get_perpetual_market_trades(\nself,\nmarket: str,\nstarting_before_or_at_height: Optional[int] = None,\nlimit: Optional[int] = None,\n) -> dict\n\nParameters\n\nParameterLocationTypeRequiredDescription\nmarket\npath\nTicker\ntrue\nThe market ticker.\n\nlimit\nquery\nu32\nfalse\nThe maximum number of trades to retrieve.\n\nstartingBeforeOrAtHeight\nquery\nHeight\nfalse\nThe block height to start retrieving trades from.\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nTradeResponseObject ⛁\nThe trades data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe market was not found.\n\nAPI Example\n\nGet Candles\n\nRetrieves candle data for a specific perpetual market.\n\nMethod Declaration\n\nPython\nasync def get_perpetual_market_candles(\nself,\nmarket: str,\nresolution: str,\nfrom_iso: Optional[str] = None,\nto_iso: Optional[str] = None,\nlimit: Optional[int] = None,\n) -> dict\n\nParameters\n\nParameterLocationTypeRequiredDescription\nmarket\npath\nTicker\ntrue\nThe market ticker.\n\nresolution\nquery\nCandleResolution\ntrue\nThe candle resolution (e.g., \"1DAY\", \"1HOUR\", \"1MIN\").\n\nlimit\nquery\nu32\nfalse\nThe maximum number of candles to retrieve.\n\nfromISO\nquery\nDateTime\nfalse\nThe start timestamp in ISO format.\n\ntoISO\nquery\nDateTime\nfalse\nThe end timestamp in ISO format.\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nCandleResponseObject ⛁\nThe candle data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\nAPI Example\n\nGet Historical Funding\n\nRetrieves historical funding rates for a specific perpetual market.\n\nMethod Declaration\n\nPython\nasync def get_perpetual_market_historical_funding(\nself,\nmarket: str,\neffective_before_or_at: Optional[str] = None,\neffective_before_or_at_height: Optional[int] = None,\nlimit: Optional[int] = None,\n) -> dict\n\nParameters\n\nParameterLocationTypeRequiredDescription\nmarket\npath\nTicker\ntrue\nThe market ticker.\n\nlimit\nquery\nu32\nfalse\nThe maximum number of funding rates to retrieve.\n\neffectiveBeforeOrAt\nquery\nDateTime\nfalse\nThe timestamp to retrieve funding rates effective before or at.\n\neffectiveBeforeOrAtHeight\nquery\nHeight\nfalse\nThe block height to retrieve funding rates effective before or at.\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nHistoricalFundingResponseObject ⛁\nThe historical funding rates data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe market was not found.\n\nAPI Example\n\nGet Sparklines\n\nRetrieves sparkline data for perpetual markets.\n\nMethod Declaration\n\nPython\nasync def get_perpetual_market_sparklines(\nself,\nperiod: str = TimePeriod.ONE_DAY\n) -> dict\n\nParameters\n\nParameterLocationTypeRequiredDescription\ntimePeriod\nquery\nSparklineTimePeriod\ntrue\nThe time period for the sparkline data (e.g., \"ONE_DAY\", \"SEVEN_DAYS\").\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nSparklineResponseObject ⛁\nThe sparkline data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\nAPI Example\n\nUtility\n\n// TODO: Add description\n\nMethod Declaration\n\nGet Time\n\nGet current server time of the Indexer.\n\nMethod Declaration\n\nPython\nasync def get_time(self) -> Dict[str, str]\n\nParameters\n\nParameterLocationTypeRequiredDescription\n\nResponse\n\nStatusMeaningSchema\n200\nOK\nTimeResponse\n\nAPI Example\n\nGet Height\n\nCurrent block height and block time (UTC) parsed by the Indexer.\n\nMethod Declaration\n\nPython\nasync def get_height(self) -> Dict[str, str]\n\nParameters\n\nParameterLocationTypeRequiredDescription\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nHeightResponse ⛁\nDictionary containing the block height and time.\n\nAPI Example\n\nGet Screen\n\nQuery for screening results (compliance) of the address.\n\nMethod Declaration\n\nPython\nasync def screen(self, address: str) -> Dict[str, bool]:\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\nquery\nAddress\ntrue\nThe wallet address that owns the account.\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nComplianceResponse ⛁\nThe compliance data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\nAPI Example\n\nGet Compliance Screen\n\nScreen an address to see if it is restricted.\n\nMethod Declaration\n\nPython\nasync def compliance_screen(self, address: str) -> Any\n\nParameters\n\nParameterLocationTypeRequiredDescription\naddress\nPath\nstring\ntrue\nevm or dydx address\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nComplianceV2Response\nwhether the specified address is restricted\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\nAPI Example\n\nVaults\n\nTODO: How to access to the vaults space.\n\nRust\nlet vaults = indexer_client.vaults();\n\nGet MegaVault Historical Pnl\n\nMegaVault historical PnL.\n\nMethod Declaration\n\nPython\nasync def get_megavault_historical_pnl(self, resolution)\n\nParameters\n\nParameterLocationTypeRequiredDescription\nresolution\nquery\nPnlTickInterval\ntrue\nPnL tick resolution.\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nPnlTicksResponseObject ⛁\nThe PnL ticks data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\nAPI Example\n\nGet Vaults Historical Pnl\n\nVaults historical PnL.\n\nMethod Declaration\n\nPython\nasync def get_vaults_historical_pnl(self, resolution)\n\nParameters\n\nParameterLocationTypeRequiredDescription\nresolution\nquery\nPnlTickInterval\ntrue\nPnL tick resolution.\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nVaultHistoricalPnl ⛁\nThe vault historical PnL data.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\nAPI Example\n\nGet MegaVaults Positions\n\nMegaVault positions.\n\nMethod Declaration\n\nPython\nasync def get_megavault_positions(self)\n\nParameters\n\nResponse\n\nStatusMeaningSchema\n200\nOK\nVaultPosition ⛁\n\nAPI Example","tokens":8198,"crawled_at":1791193621104}
+{"id":10264,"url":"https://www.metaplex.com/docs/solana/solana-keypairs-and-wallets","domain":"www.metaplex.com","chapter":"docs","title":"Solana Keypairs and Wallets | Wallet Security Guide","text":"A comprehensive guide to creating, managing, and securing Solana keypairs for development and production environments.\nWhat You'll Learn\nWhat keypairs are and how they work on Solana\nHow to generate and manage keypairs\nSecurity best practices for different environments\nHow to use keypairs with the Solana CLI and MPLX CLI\nPrerequisites\nSolana CLI installed\nUnderstanding Keypairs\nA keypair on Solana consists of:\nPublic Key - Your wallet address, safe to share\nSecret Key - Secret key that controls the wallet, never share this\nCritical Security Rule\nYour private key gives complete control over your wallet. Anyone with access to it can transfer all your assets. Never commit keypair files to git, share them online, or store them unencrypted on cloud services.\n\nCreating Keypairs\nGenerate a New Keypair\n# Create a new keypair (prompts for BIP39 passphrase)\n\nsolana-keygen new\n\n# Create with a specific output file\n\nsolana-keygen new --outfile ~/my-wallet.json\n\n# Create without passphrase prompt (for scripts/testing)\n\nsolana-keygen new --no-bip39-passphrase --outfile ~/my-devnet-wallet.json\n\nThe command outputs:\nThe public key (your wallet address)\nA seed phrase (12-24 words) for recovery\nSave Your Seed Phrase\nWrite down your seed phrase and store it securely offline. This is the only way to recover your wallet if you lose the keypair file.\n\nRecover from Seed Phrase\n# Recover a keypair from seed phrase\n\nsolana-keygen recover --outfile ~/recovered-wallet.json\n\nYou'll be prompted to enter your seed phrase.\nGenerate from Existing Seed\nIf you have a seed phrase and want to derive the keypair:\nsolana-keygen recover 'prompt://?full-path=m/44'/501'/0'/0'' --outfile ~/derived-wallet.json\n\nManaging Keypairs with MPLX CLI\nThe MPLX CLI provides convenient wallet management with named wallets:\n# Create a new wallet in MPLX config\n\nmplx config wallets new my-dev-wallet\n\n# Add an existing keypair file\n\nmplx config wallets add my-wallet ~/path/to/keypair.json\n\n# List all configured wallets\n\nmplx config wallets list\n\n# Set the active wallet\n\nmplx config wallets set my-dev-wallet\n\n# Remove a wallet from config\n\nmplx config wallets remove old-wallet\n\nBenefits of MPLX wallet management:\nNamed wallets instead of file paths\nEasy switching between wallets\nCentralized configuration at ~/.mplx/config.json\nViewing Keypair Information\nGet Public Key from Keypair File\nsolana-keygen pubkey ~/my-wallet.json\n\nVerify a Keypair File\nsolana-keygen verify <PUBKEY> ~/my-wallet.json\n\nSetting Your Default Keypair\nSolana CLI\n# Set default keypair for all commands\n\nsolana config set --keypair ~/my-wallet.json\n\n# Verify the setting\n\nsolana config get\n\nPer-Command Override\n# Use a specific keypair for one command\n\nsolana balance --keypair ~/other-wallet.json\n\nsolana transfer <ADDRESS> 1 --keypair ~/funding-wallet.json\n\nSecurity Best Practices\nDevelopment vs Production\nEnvironmentRecommendation\nLocal testing\nFile system wallet, no passphrase needed\n\nDevnet/Testnet\nFile system wallet, backed up seed phrase\n\nMainnet (small amounts)\nFile system wallet with passphrase, encrypted disk\n\nMainnet (significant value)\nHardware wallet or multisigs\n\nFile System Wallets\nFor development and moderate amounts:\n# Create with restrictive permissions\n\nsolana-keygen new --outfile ~/.config/solana/mainnet-wallet.json\n\nchmod 600 ~/.config/solana/mainnet-wallet.json\n\nEnvironment Variables\nFor automated scripts, avoid hardcoding keypair paths:\n# In your shell profile (~/.bashrc or ~/.zshrc)\n\nexport SOLANA_KEYPAIR_PATH=\"$HOME/.config/solana/devnet-wallet.json\"\n\n# In scripts\n\nsolana config set --keypair \"$SOLANA_KEYPAIR_PATH\"\n\nMultiple Wallets Strategy\nRecommended setup for active developers:\n~/.config/solana/\n\n├── devnet-wallet.json # Main devnet testing\n\n├── testnet-wallet.json # Testnet when needed\n\n├── mainnet-wallet.json # Small mainnet operations\n\n└── burner-wallet.json # Temporary/throwaway\n\nConfigure with MPLX CLI for easy switching:\nmplx config wallets add devnet ~/.config/solana/devnet-wallet.json\n\nmplx config wallets add mainnet ~/.config/solana/mainnet-wallet.json\n\nmplx config wallets set devnet\n\nWhat NOT to Do\nNever commit keypair files to git (add *.json to .gitignore)\nNever share your seed phrase or private key in Discord, Telegram, or support tickets\nNever paste your private key into websites\nNever store unencrypted keypairs in cloud storage (Dropbox, Google Drive)\nNever use the same keypair for mainnet testing and production\nHardware Wallets\nFor significant mainnet holdings, use a Ledger hardware wallet:\n# Check if Ledger is connected\n\nsolana-keygen pubkey usb://ledger\n\n# Use Ledger for transactions\n\nsolana config set --keypair usb://ledger\n\nsolana transfer <ADDRESS> 1\n\nRequirements:\nLedger device with Solana app installed\nUSB connection to your computer\nPractical Examples\nDevelopment Wallet Setup\n# 1. Create a devnet wallet (no passphrase for convenience)\n\nsolana-keygen new --no-bip39-passphrase --outfile ~/.config/solana/devnet.json\n\n# 2. Set it as default\n\nsolana config set --keypair ~/.config/solana/devnet.json\n\n# 3. Switch to devnet\n\nsolana config set --url devnet\n\n# 4. Get some devnet SOL\n\nsolana airdrop 2\n\n# 5. Verify\n\nsolana balance\n\nTeam Development Setup\nFor teams, each developer should have their own keypairs:\n# Developer creates their own wallet\n\nsolana-keygen new --outfile ~/my-project-wallet.json\n\n# Share only the PUBLIC key with the team\n\nsolana-keygen pubkey ~/my-project-wallet.json\n\n# Output: 7nE9GvcwYDhwWdFfGjVZQ8dR6bYYvqPJktNpyxQYb1xm\n\nProgrammatic Keypair Generation (JavaScript)\nFor applications that need to generate keypairs using UMI:\nimport { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\nimport { generateSigner, signerIdentity } from '@metaplex-foundation/umi'\n\nconst umi = createUmi('https://api.devnet.solana.com')\n\n// Generate a new random keypair signer\n\nconst signer = generateSigner(umi)\n\nconsole.log('Public Key:', signer.publicKey)\n\n// Use it as the identity (payer + signer)\n\numi.use(signerIdentity(signer))\n\n// Load an existing keypair from a file\n\nimport { createSignerFromKeypair } from '@metaplex-foundation/umi'\n\nimport fs from 'fs'\n\nconst secretKey = new Uint8Array(JSON.parse(fs.readFileSync('wallet.json')))\n\nconst keypair = umi.eddsa.createKeypairFromSecretKey(secretKey)\n\nconst loadedSigner = createSignerFromKeypair(umi, keypair)\n\nTroubleshooting\n\"Keypair file not found\"\n# Check if file exists\n\nls -la ~/.config/solana/id.json\n\n# If not, create one\n\nsolana-keygen new --outfile ~/.config/solana/id.json\n\n# Or check your config\n\nsolana config get\n\n\"Invalid keypair\"\nThe keypair file must be a JSON array of 64 numbers. Verify format:\n# Should output an array like [123, 45, 67, ...]\n\ncat ~/my-wallet.json | head -c 100\n\nLost Seed Phrase\nIf you lost your seed phrase but still have the keypair file:\nYour funds are safe as long as you have the file\nTransfer funds to a new wallet with a backed-up seed phrase\nTreat the old keypair as compromised for future use\nNext Steps\nGrind a vanity public key - Create branded addresses\nGet SOL for development - Fund your new wallet\nSolana CLI essentials - Use your wallet effectively\nFAQ\nCan I use the same keypair on devnet and mainnet?\nTechnically yes, but it's not recommended. Use separate keypairs to avoid accidentally sending real SOL in test scripts.\nWhat's the difference between a keypair and a wallet?\nA keypair is the cryptographic key pair (public + private). A wallet is software that manages keypairs and helps you interact with the blockchain. File system wallets store the raw keypair; browser wallets like Phantom manage it with additional UX.\nHow do I use my Phantom wallet with the CLI?\nExport your private key from Phantom (Settings > Security > Export Private Key), then import it:\n# The exported key is base58 encoded, convert it:\n\necho \"[your-exported-key]\" | base58 -d > phantom-wallet.json\n\nsolana config set --keypair phantom-wallet.json\n\nNote: For security, consider creating a separate CLI keypair instead of exporting from Phantom.","tokens":2001,"crawled_at":1791193632124}
+{"id":10265,"url":"https://gov.uniswap.org/t/temp-check-forse-analytics-for-uniswap-revitalization-and-growth-program/24373/5","domain":"gov.uniswap.org","chapter":"governance_daos","title":"[Temp Check] Forse Analytics for Uniswap Revitalization and Growth Program - #5 by kfx - Temperature Check - Uniswap Governance","text":"[Temp Check] Forse Analytics for Uniswap Revitalization and Growth Program\n\nTemperature Check\n\nkfx\n\nAugust 10, 2024, 2:24pm\n\n5\n\nI have voted against the temp check, explanation here:\n\n6 Likes\n\nshow post in topic\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[RFC] Analytics Hub for Uniswap's Revitalization and Growth Program\n\nRequests for Comment\n\n11\n\n592\n\nMay 8, 2025\n\n[RFC] Forse for Uniswap Analytics for Uniswap Revitalization and Growth Program\n\nRequests for Comment\n\n0\n\n249\n\nJuly 27, 2024\n\n[Governance Proposal] Uniswap Unleashed: Unichain and Uniswap v4 Liquidity Incentives\n\nRequests for Comment\n\n44\n\n10632\n\nApril 22, 2025\n\nUniswap Incentive Design Analysis\n\nGovernance-Meta\n\n10\n\n7858\n\nSeptember 15, 2023\n\nIntroducing the Uniswap Incentive Analysis Terminal by Forse\n\nUncategorized\n\n4\n\n658\n\nApril 16, 2025","tokens":204,"crawled_at":1791193634989}
+{"id":10266,"url":"https://www.metaplex.com/docs/solana/solana-transaction-fundamentals","domain":"www.metaplex.com","chapter":"docs","title":"Solana Transaction Fundamentals | How Transactions Work","text":"A comprehensive guide to understanding how Solana transactions work from structure to confirmation.\nWhat You'll Learn\nThe anatomy of a Solana transaction\nHow to sign and send transactions\nTransaction confirmation and finality\nVersioned transactions vs legacy\nCommon transaction errors and their meanings\nPrerequisites\nSolana CLI installed\nUnderstanding Solana accounts\nTransaction Anatomy\nA Solana transaction consists of several components:\n┌─────────────────────────────────────────────────────────────┐\n\n│ Transaction │\n\n├─────────────────────────────────────────────────────────────┤\n\n│ Signatures: [sig1, sig2, ...] │\n\n│ │\n\n│ Message: │\n\n│ ├── Header │\n\n│ │ ├── num_required_signatures │\n\n│ │ ├── num_readonly_signed_accounts │\n\n│ │ └── num_readonly_unsigned_accounts │\n\n│ │ │\n\n│ ├── Account Keys: [pubkey1, pubkey2, ...] │\n\n│ │ │\n\n│ ├── Recent Blockhash │\n\n│ │ │\n\n│ └── Instructions: [ │\n\n│ { program_id_index, accounts, data }, │\n\n│ { program_id_index, accounts, data }, │\n\n│ ] │\n\n└─────────────────────────────────────────────────────────────┘\n\nKey Components\nComponentDescription\nSignatures\nEd25519 signatures from required signers\n\nRecent Blockhash\nA recent block hash (valid for ~60-90 seconds)\n\nInstructions\nThe operations to perform\n\nAccount Keys\nAll accounts involved in the transaction\n\nInstructions\nInstructions are the actual operations in a transaction. Each instruction specifies:\nProgram ID - Which program to execute\nAccounts - Which accounts the program needs\nData - Serialized arguments for the program\nInstruction:\n\n├── program_id: 11111111111111111111111111111111 (System Program)\n\n├── accounts:\n\n│ ├── sender (signer, writable)\n\n│ └── recipient (not signer, writable)\n\n└── data: [encoded transfer amount]\n\nMultiple Instructions\nTransactions can contain multiple instructions that execute atomically:\nimport { transactionBuilder } from '@metaplex-foundation/umi'\n\n// All instructions succeed or all fail (atomic)\n\nconst builder = transactionBuilder()\n\n.add(createAccountInstruction)\n\n.add(initializeMintInstruction)\n\n.add(mintTokensInstruction)\n\nawait builder.sendAndConfirm(umi)\n\nThis atomicity is powerful. If any instruction fails, the entire transaction is reverted.\nRecent Blockhash\nEvery transaction requires a recent blockhash that:\nProves the transaction was created recently\nPrevents replay attacks\nExpires after ~60-90 seconds (~150 slots)\n// UMI handles blockhash automatically when sending transactions.\n\n// To fetch it manually:\n\nconst { blockhash, lastValidBlockHeight } = await umi.rpc.getLatestBlockhash()\n\nBlockhash Expiration\nIf your transaction isn't confirmed before the blockhash expires, it will be dropped. For long-running operations, fetch a fresh blockhash before sending.\n\nSigning Transactions\nTransactions must be signed by all accounts marked as isSigner:\n// UMI signs automatically with the identity signer when sending.\n\n// For additional signers, pass them during the build:\n\nconst tx = await myBuilder\n\n.setBlockhash(await umi.rpc.getLatestBlockhash())\n\n.buildAndSign(umi)\n\n// For partial signing (multi-sig workflows), you can sign\n\n// and serialize the transaction, then pass it to another party:\n\nimport { base64 } from '@metaplex-foundation/umi/serializers'\n\nconst serialized = umi.transactions.serialize(tx)\n\nconst encoded = base64.deserialize(serialized)[0]\n\n// ... send encoded string to another party for additional signing ...\n\nSending Transactions\nBasic Send\n// Send and wait for confirmation (recommended)\n\nconst result = await myBuilder.sendAndConfirm(umi)\n\n// Or just send without waiting\n\nconst signature = await myBuilder.send(umi)\n\nSend with Options\nconst result = await myBuilder.sendAndConfirm(umi, {\n\nsend: { skipPreflight: false },\n\nconfirm: { commitment: 'confirmed' },\n\n})\n\nTransaction Confirmation\nSolana has multiple commitment levels indicating transaction finality:\nCommitmentDescriptionUse Case\nprocessed\nTransaction received by leader\nReal-time updates\n\nconfirmed\nVoted on by supermajority\nMost applications\n\nfinalized\n31+ blocks deep, irreversible\nFinancial operations\n\nChecking Confirmation\n// sendAndConfirm waits for confirmation automatically.\n\n// To check a signature status manually:\n\nconst result = await umi.rpc.getSignatureStatuses([signature])\n\nCommitment in Practice\n// For most operations, 'confirmed' is the right default\n\nconst result = await myBuilder.sendAndConfirm(umi, {\n\nconfirm: { commitment: 'confirmed' },\n\n})\n\n// For financial operations where you need full finality\n\nconst result = await myBuilder.sendAndConfirm(umi, {\n\nconfirm: { commitment: 'finalized' },\n\n})\n\nVersioned Transactions\nSolana supports three transaction formats:\nLegacy Transactions\nLegacy transactions use Solana's original transaction format without Address Lookup Tables.\nOriginal format\nLimited to 35 accounts\nSimpler structure\nV0 Transactions\nV0 transactions add Address Lookup Table support for transactions that need more accounts.\nSupport Address Lookup Tables (ALTs)\nCan reference up to 256 accounts\nRequired for complex DeFi operations\nV1 Transactions\nV1 transactions increase the transaction size limit and store compute configuration in the message.\nSupport transactions up to 4,096 bytes\nStore compute budget configuration in the transaction message\nDo not support Address Lookup Tables\n// Umi uses V0 transactions by default. Opt in to V1 explicitly.\n\nconst result = await myBuilder\n\n.useV1()\n\n.sendAndConfirm(umi)\n\n// To use legacy transactions instead\n\nconst result = await myBuilder\n\n.useLegacyVersion()\n\n.sendAndConfirm(umi)\n\n// With Address Lookup Tables\n\nimport { createLut } from '@metaplex-foundation/mpl-toolbox'\n\nconst [lutBuilder, lut] = createLut(umi, {\n\nrecentSlot: await umi.rpc.getSlot({ commitment: 'finalized' }),\n\naddresses: [addressA, addressB, addressC],\n\n})\n\nawait lutBuilder.sendAndConfirm(umi)\n\n// Address Lookup Tables require V0.\n\nawait myBuilder\n\n.useV0()\n\n.setAddressLookupTables([lut])\n\n.sendAndConfirm(umi)\n\nChoosing a Transaction Version\nUse V1 for transactions larger than 1,232 bytes when the wallet supports transaction version 1.\nUse V0 when the transaction requires an Address Lookup Table.\nUse legacy transactions only when compatibility requires the original format.\nUmi defaults to V0 for backward compatibility. See Migrating from V0 to V1 Transactions before changing the application-wide default.\n\nTransaction Size Limits\nSolana transactions have strict size limits:\nLimitValue\nLegacy and V0 transaction size\n1,232 bytes\n\nV1 transaction size\n4,096 bytes\n\nAddress Lookup Tables\nV0 only\n\nMaximum instructions\nLimited by size\n\nDealing with Size Limits\nIf your transaction is too large:\nUse V1 - Increase the size limit to 4,096 bytes when no Address Lookup Table is required\nUse Address Lookup Tables with V0 - Compress account references\nSplit into multiple transactions - Execute sequentially\nOptimize instruction data - Minimize serialized data\nSimulation\nBefore sending, simulate transactions to catch errors:\n// Build the transaction without sending\n\nconst tx = await myBuilder\n\n.setBlockhash(await umi.rpc.getLatestBlockhash())\n\n.buildAndSign(umi)\n\n// Simulate it\n\nconst simulation = await umi.rpc.simulateTransaction(tx, {\n\ncommitment: 'confirmed',\n\n})\n\nconsole.log('Simulation result:', simulation)\n\nSimulation helps you:\nCatch errors before paying fees\nEstimate compute units\nDebug program logic\nCommon Transaction Errors\n\"Blockhash not found\"\nCause: The blockhash expired before confirmation.\nSolutions:\nRetry with a fresh blockhash (UMI fetches a new blockhash automatically on each send)\nUse 'finalized' commitment for blockhash when network is congested\nImplement retry logic in your application\n\"Insufficient funds\"\nCause: Account doesn't have enough SOL for transaction fees + rent.\nSolution: Ensure the fee payer has sufficient balance:\nsolana balance\n\nsolana airdrop 1 # On devnet\n\n\"Transaction simulation failed\"\nCause: Program logic error.\nSolution: Check simulation logs on an explorer (see Using Solana Explorers), or simulate the transaction before sending to inspect the error output.\n\"Account not found\"\nCause: An account in the transaction doesn't exist.\nSolution: Create the account first or check addresses.\n\"Invalid account owner\"\nCause: Account is owned by a different program than expected.\nSolution: Verify account ownership matches the program you're calling.\nPractical Example: Complete Flow\nimport { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\nimport { transferSol } from '@metaplex-foundation/mpl-toolbox'\n\nimport { signerIdentity, generateSigner, sol, publicKey } from '@metaplex-foundation/umi'\n\nimport { base58 } from '@metaplex-foundation/umi/serializers'\n\n// 1. Create UMI instance\n\nconst umi = createUmi('https://api.devnet.solana.com')\n\n// 2. Set up signer (your wallet)\n\nconst signer = generateSigner(umi)\n\numi.use(signerIdentity(signer))\n\n// 3. Build and send the transaction\n\nconst result = await transferSol(umi, {\n\nsource: umi.identity,\n\ndestination: publicKey('RecipientAddressHere...'),\n\namount: sol(1),\n\n}).sendAndConfirm(umi)\n\n// 4. Get the transaction signature\n\nconst signature = base58.deserialize(result.signature)[0]\n\nconsole.log('Transaction confirmed:', signature)\n\nconsole.log(`Explorer: https://explorer.solana.com/tx/${signature}?cluster=devnet`)\n\nNext Steps\nCompute units and priority fees - Optimize transaction landing\nWorking with devnet and testnet - Test your transactions\nDiagnose transaction errors - Debug failed transactions\nFAQ\nHow long do I have to confirm a transaction?\nA transaction's blockhash is valid for approximately 60-90 seconds (~150 slots). After that, the transaction will be dropped if not confirmed.\nCan I cancel a transaction?\nNo, once submitted, you cannot cancel a transaction. However, if it hasn't been confirmed, you can submit a new transaction with the same nonce (using durable nonces) to effectively \"replace\" it.\nWhat's the difference between \"processed\" and \"confirmed\"?\n\"Processed\" means a validator received it. \"Confirmed\" means a supermajority (66%+) of validators voted on the block containing it. Always use \"confirmed\" or \"finalized\" for important operations.\nWhy did my transaction fail after simulation succeeded?\nState can change between simulation and execution. Another transaction may have modified the accounts. This is common in competitive scenarios like NFT mints.","tokens":2582,"crawled_at":1791193650574}
+{"id":10267,"url":"https://gov.uniswap.org/t/governance-proposal-uniswap-unleashed/25251/39","domain":"gov.uniswap.org","chapter":"governance_daos","title":"[Governance Proposal] Uniswap Unleashed - #39 by kfx - Requests for Comment - Uniswap Governance","text":"[Governance Proposal] Uniswap Unleashed\n\nRequests for Comment\n\nkfx\n\nFebruary 26, 2025, 6:10pm\n\n39\n\nI will vote against the proposals as they stand now. In my view, a request for such an extraordinary funding amount requires extraordinarily strong evidence. I don’t believe that level of proof has been reached yet.\n\nSpecifically, I haven’t seen sufficient evidence that spending the funds in the proposed manner is a better alternative for UNI tokenholders than simply allocating them to a Stability Fund for yield. For example, the total gross revenue of a top-5 L2 (Linea) has ranged between $5,000 and $20,000 per day over the past week. If this is the revenue Unichain aims to reach by spending >$30M on Unichain-related incentives and grants (not even including the related budget for ops), it will take a long time to recapture the investment—especially if only 65% of the net revenue goes to tokenholders. We can hope that Unichain’s revenue will be much higher, but’s it’s just that, hop. To be clear Unichain here is just an example, this also applied to other categories.\n\nAnother major issue is the lack of alignment and coordination among the key actors (UF, Labs, DAO). Unichain, in particular, is problematic in this regard.\n\nChanges I’d like to see in the proposal\n\nPostpone all funding related to Unichain’s operations and related operational budget.\n\nProvide clarity on how the grants used to fund v4, including v4 hooks, will benefit UNI tokenholders.\n\nPresent a concrete roadmap toward the fee switch or alternative revenue generation methods.\n\nImprove transparency and accountability within the UF, either through a closer feedback loop with the DAO or via an external supervisory organization.\n\nConsider making some funding conditional. For example, once Labs delivers the promised innovations for Unichain, the DAO could release X% of the incentive funding. Once the fee switch is live, X% of grant funding could be released, and so on.\n\nBelow are detailed explanations of these proposed changes.\n\nUnichain\n\nWhile I and most other delegates support incentives for Unichain’s growth, it’s unclear whether including votes for such incentives within the same proposal as the rest of the UF’s budget is necessary. There are multiple reasons to separate and/or postpone this funding:\n\nUnichain represents a significant shift in the DAO’s scope and responsibilities, and more time is needed to understand the role the DAO can and wants to take.\n\nThe promised technical innovations for Unichain are mostly not live yet; currently, it is a generic chain within the Optimism Superchain ecosystem. Therefore, incentives may be better timed for later.\n\nAt present, the DAO lacks a legal structure to capture fees from Unichain.\n\nThe DAO does not control the “fee switch” of the chain.\n\nAttempting to handle both the v3 → v4 migration and Unichain incentives simultaneously could pose operational challenges for the UF and its partners.\n\nIt’s not clear how Labs see Unichain in their strategy and whether/how they will influence the chain’s governance in the future. The DAO should not spend UNI tokens to indirectly fund the Labs.\n\nWe believe the following conditions should be met before the DAO provides incentives to Unichain:\n\nThe technical innovations promised in Unichain’s whitepaper are either live or ready for launch, specifically:\n\nUnichain’s Validator Network\n\nSub-second block times\n\nTrustless revert protection\n\nAn incorporated entity (such as a DUNA) exists to receive revenue from Unichain on the DAO’s behalf.\n\nOther concerns—such as the DAO’s lack of control over the chain and its fee distribution—are thoroughly discussed and addressed where possible.\n\nGrants, Including v4 Incentives\n\nHook Grants & Incentives\n\nSince v4 hook developers can choose to bypass the protocol fee using hooks with BEFORE_SWAP_RETURNS_DELTA_FLAG or otherwise interfere with the protocol fee, we request that, at a minimum, a legally binding agreement be made with each hook developer receiving a grant. If the developer collects revenue from the hook in any form, the DAO must be entitled to its fair share through protocol fees.\n\nAdditionally, we believe other mechanisms should be explored to capture revenue from protocols building on top of Uniswap. For example, grant agreements could stipulate a share in future equity or tokens.\n\nOther Incentives\n\nThe proposal should clarify which incentives are public goods for the DeFi space and which are aimed at sustainability of the DAO & UF and UNI token appreciation.\n\nFee Switch\n\nThe funding of v4 incentives and the operational budget should be conditional on establishing a clear pathway for capturing revenue from the protocol—whether through the protocol fee switch or alternative mechanisms such as frontend fees. The burden of proof lies with the Foundation, not the delegates, as it is unlikely that any bottom-up proposal from the DAO will gain traction while the general understanding remains that the Foundation is still working on its design.\n\nImproved Oversight\n\nOne option to enhance oversight is extending the UF’s Legal Board to include DAO members, as suggested by GFX Labs. However, if this is not possible due to regulatory reasons, other alternatives should be explored. Some options were recommended in response to the previous funding request in 2023, and I’m happy to see that some of them have already been implemented!\n\nThe goal should be to reduce potential misalignments (real or perceived) between key stakeholders within the ecosystem and improve transparency.\n\n4 Likes\n\nAtiselsts.eth Delegate Platform\n\nshow post in topic\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[Governance Proposal]: Complete initial funding of the Uniswap Foundation\n\nRequests for Comment\n\n8\n\n6487\n\nOctober 16, 2023\n\n[Temperature Check] Create the Uniswap Foundation\n\nTemperature Check\n\n59\n\n25158\n\nSeptember 9, 2022\n\n[RFC]: Complete initial funding of the Uniswap Foundation\n\nRequests for Comment\n\n15\n\n7771\n\nOctober 7, 2023\n\n404 DAO Delegate Platform\n\nDelegation Pitch\n\n39\n\n3283\n\nJanuary 13, 2026\n\n[Governance Proposal] Create the Uniswap Foundation\n\nRequests for Comment\n\n0\n\n7548\n\nAugust 17, 2022","tokens":1541,"crawled_at":1791193652826}
+{"id":10268,"url":"https://stack.olas.network/open-autonomy/advanced_reference/commands/autonomy_analyse","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"autonomy analyse - Olas Stack Developer Documentation","text":"autonomy analyse\n\nTools for analysing and verifying AI agents.\n\nThis command group consists of a number of functionalities to analyse and verify AI agents, including FSM App skill consistency checks. See the appropriate subcommands for more information.\n\nautonomy analyse docstrings\n\nAnalyse FSM App skill docstring definitions.\n\nThis command verifies that the AbciApp class docstring is follows a standard format.\n\nExample\nThe docstring corresponding to the Hello World AI agent is\n\n\"\"\"HelloWorldAbciApp\n\nInitial round: RegistrationRound\n\nInitial states: {RegistrationRound}\n\nTransition states:\n1. RegistrationRound\n- done: 1.\n2. CollectRandomnessRound\n- done: 2.\n- no majority: 1.\n- round timeout: 1.\n3. SelectKeeperRound\n- done: 3.\n- no majority: 0.\n- round timeout: 0.\n4. PrintMessageRound\n- done: 4.\n- round timeout: 0.\n5. ResetAndPauseRound\n- done: 1.\n- no majority: 0.\n- reset timeout: 0.\n\nFinal states: {}\n\nTimeouts:\nround timeout: 30.0\nreset timeout: 30.0\n\"\"\"\n\nUsage\n\nautonomy analyse docstrings [OPTIONS]\n\nOptions\n\n--update\nUpdate docstrings if required.\n--help\nShow the help message and exit.\n\nExamples\n\nTo analyse all the FSM App skill docstrings within the local registry, run the following command in the directory containing the registry:\n\nautonomy analyse docstrings\n\nTo update/fix the FSM App skill docstrings, run the following command:\n\nautonomy analyse docstrings --update\n\nautonomy analyse fsm-specs\n\nVerify the FSM App against its specification or generate the FSM App specification file.\n\nUsage\n\nUsage: autonomy analyse fsm-specs [OPTIONS]\n\nOptions\n\n--package PATH\n\nPath to the package containing the FSM App skill.\n--app-class ABCI_APP_CLASS\n\nName of the AbciApp class of the FSM App.\n--update\n\nUpdate/create the FSM App definition file if check fails.\n--yaml\n\nYAML file (default).\n--json\n\nJSON file.\n--mermaid\n\nMermaid file.\n--help\n\nShow the help message and exit.\n\nExamples\n\nAnalyse the FSM App specification for the hello_world_abci:\n\nautonomy analyse fsm-specs --package ./packages/valory/skills/hello_world_abci\n\nUpdate/create the FSM App specification for the hello_world_abci in YAML format:\n\nautonomy analyse fsm-specs --package ./packages/valory/skills/hello_world_abci --app-class HelloWorldAbciApp --update\n\nExport the FSM App specification for the hello_world_abci in Mermaid format:\n\nautonomy analyse fsm-specs --package ./packages/valory/skills/hello_world_abci --app-class HelloWorldAbciApp --update --mermaid\n\nAnalyse all the FSM App specifications in a local registry. This command must be executed\nin a directory containing the local registry:\n\nautonomy analyse fsm-specs\n\nautonomy analyse handlers\n\nVerify existence of handler definitions.\n\nThis command verifies that all the FSM App skills in a local registry (except the explicitly excluded ones) have defined the specified handlers.\n\nUsage\n\nautonomy analyse handlers [OPTIONS]\n\nOptions\n\n-h, --common-handlers HANDLER_NAME\nSpecify which handlers to check. E.g., -h handler_a -h handler_b -h handler_c.\n-i, --ignore SKILL_NAME\nSpecify which skills to skip. E.g., -i skill_0, -i skill_1, -i skill_2.\n--help\nShow the help message and exit.\n\nExamples\n\nEnsure that handlers http and signing are defined in all the FSM App skills in a local registry, except the skills excluded_skill_1 and excluded_skill_2:\n\nautonomy analyse handlers -h http -h signing -i excluded_skill_1 -i excluded_skill_2\n\nautonomy analyse dialogues\n\nCheck dialogues definitions in a skill package.\n\nThis command verifies that all the FSM App skills in a local registry (except the explicitly excluded ones) have defined the specified dialogues.\n\nUsage\n\nautonomy analyse dialogues [OPTIONS]\n\nOptions\n\n-d, --dialogue TEXT\nSpecify which dialogues to check. Eg. -d dialogue_a, -d dialogue_b, -d dialogue_c.\n-i, --ignore SKILL_NAME\nSpecify which skills to skip. E.g., -i skill_0, -i skill_1, -i skill_2.\n--help\nShow the help message and exit.\n\nExamples\n\nEnsure that dialogues abci_dialogues and http_dialogues are defined in all the FSM App skills in a local registry, except the skills excluded_skill_1 and excluded_skill_2:\n\nautonomy analyse dialogues -d abci_dialogues -d http_dialogues -i excluded_skill_1 -i excluded_skill_2\n\nOr\n\nautonomy analyse dialogues -d abci -d http -i excluded_skill_1 -i excluded_skill_2\n\nSince the command will automatically append the _dialogues postfix if not provided by the user.\n\nautonomy analyse logs\n\nParse logs of an AI agent.\n\nUsage\n\nautonomy analyse logs [OPTIONS]\n\nOptions\n\n--from-dir PATH\nPath to logs directory [required]\n--reset-db\nUse this flag to reset the log database.\n-a, --agent TEXT\nAgent IDs to include in analysis\n--start-time TEXT\nStart time in YYYY-MM-DD H:M:S,MS format\n--end-time TEXT\nEnd time in YYYY-MM-DD H:M:S,MS format\n--log-level [INFO|DEBUG|WARNING|ERROR|CRITICAL]\nLogging level.\n--period INTEGER\nPeriod ID\n--round TEXT\nRound name\n--behaviour TEXT\nBehaviour name filter\n--fsm\nPrint only the FSM execution path\n-ir, --include-regex TEXT\nRegex pattern to include in the result.\n-er, --exclude-regex TEXT\nRegex pattern to exclude from the result.\n--help\nShow the help message and exit.\n\nExamples\n\nAnalyze logs from the build directory ./abci_build_hAsH/persistent_data/logs for 2 agents:\n\nautonomy analyse logs --from-dir ./abci_build_hAsH/persistent_data/logs -a 'aea_0' -a 'aea_1'\n\nView logs for 2 agents between specific times:\n\nautonomy analyse logs --from-dir ./abci_build_hAsH/persistent_data/logs -a 'aea_0' --start-time \"2024-01-20 10:00:00,000\" --end-time \"2024-01-20 11:00:00,000\"\n\nView logs for period 2 and round RegistrationRound:\n\nautonomy analyse logs --from-dir ./abci_build_hAsH/persistent_data/logs -a 'aea_0' --period 2 --round RegistrationRound\n\nView only the FSM state transitions:\n\nautonomy analyse logs --from-dir ./abci_build_hAsH/persistent_data/logs -a 'aea_0' --fsm\n\nFilter by log level ERROR and behaviour RegistrationBehaviour:\n\nautonomy analyse logs --from-dir ./abci_build_hAsH/persistent_data/logs -a 'aea_0' --log-level ERROR --behaviour RegistrationBehaviour\n\nUse regex patterns to filter logs, include lines with consensus and exclude lines with debug\n\nautonomy analyse logs --from-dir ./abci_build_hAsH/persistent_data/logs -a 'aea_0' -ir \".*consensus.*\" -er \".*debug.*\"\n\nThese examples demonstrate various ways to filter and analyze AI agent logs. You can combine multiple options to narrow down the log output to exactly what you need for debugging or analysis.\n\nautonomy analyse benchmarks\n\nAggregate benchmark results from AI agent deployments.\n\nThis tool requires the benchmark data generated from agent blueprint's runtime.\nBy default the tool will aggregate the output for all the periods and code block types but you can restrict the aggregation to a specific period and/or a specific block type.\n\nRead the guide on how to use the benchmarking tool for more information.\n\nUsage\n\nautonomy analyse benchmarks [OPTIONS] PATH\n\nOptions\n\n-b, --block-type [local|consensus|total|all]\n\nBlock type:\n\nlocal: only consider local code blocks,\n\nconsensus: only consider consensus code blocks,\n\ntotal: consider local + consensus code blocks together.\n\nall: consider local and consensus code blocks.\n\n-d, --period PERIOD_NUM\nPeriod.\n-o, --output FILE\nOutput file name.\n--help\nShow the help message and exit.\n\nExamples\n\nThe benchmark data will be stored in the folder <service_folder>/abci_build_hAsH/persistent_data/benchmarks.\n\nTo aggregate stats for all periods, execute:\n\nautonomy analyse benchmarks abci_build_hAsH/persistent_data/benchmarks\n\nTo aggregate stats for consensus block type in the second period, execute:\n\nautonomy analyse benchmarks abci_build_hAsH/persistent_data/benchmarks --period 2 --block-type consensus\n\nautonomy analyse service\n\nAnalyse if the AI agent is ready to be deployed or not.\n\nThis tool can be used to analyse an AI agent definition and see if there are any potential issues with configuration which can cause issues when running the deployment.\n\nRead the guide on deployment readiness for more information.\n\nUsage\n\nautonomy analyse service [OPTIONS]\n\nOptions\n\n--token-id INTEGER\nToken ID of the AI agent\n--public-id PUBLIC_ID_OR_HASH\nPublic ID of the AI agent\n--use-celo\nTo use celo chain profile to interact with the contracts\n--use-base\nTo use base chain profile to interact with the contracts\n--use-optimism\nTo use optimism chain profile to interact with the contracts\n--use-arbitrum-one\nTo use arbitrum-one chain profile to interact with the contracts\n--use-gnosis\nTo use gnosis chain profile to interact with the contracts\n--use-polygon\nTo use polygon chain profile to interact with the contracts\n--use-ethereum\nTo use ethereum chain profile to interact with the contracts\n--use-custom-chain\nTo use custom-chain chain profile to interact with the contracts\n--use-local\nTo use local chain profile to interact with the contracts\n--help\nShow the help message and exit.\n\nExamples\n\nAnalyse the AI agent valory/hello_world using\n\nautonomy analyse service --public-id valory/hello_world\n\nAnalyse an on-chain AI agent with token ID 1 using\n\nautonomy analyse service --token-id 1","tokens":2265,"crawled_at":1791193653958}
+{"id":10269,"url":"https://a16zcrypto.com/posts/videos/the-transaction-supply-chain-for-high-performance-l1s","domain":"a16zcrypto.com","chapter":"research","title":"The transaction supply chain for high performance L1s - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nThe transaction supply chain for high performance L1s\nPranav Garimidi\n12.07.25\n\nTags & Share Tags\nresearch\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nIn this talk we discuss the transaction supply chain in detail for high performance chains. We use Solana and Aptos as case studies to consider the unique challenges that come with scale and discuss the different space of solutions that have been used along with the outstanding problems.\n\nPranav Garimidi is a research analyst at a16z crypto. He does research on problems in mechanism design and algorithmic game theory as it relates to blockchain systems. He is especially focused on how incentives interact across the blockchain stack. Prior to a16z, Pranav was a student at Columbia University where he graduated with a degree in Computer Science.\n\nAbout a16z crypto research\n\na16z crypto research is a multidisciplinary lab that works closely with our portfolio companies and others toward solving the important problems in the space, and toward advancing the science and technology of the next generation of the internet.\n\nMore about us: a16z.com/2022/04/21/announcing-a16z-crypto-research\n\nMore from the a16z crypto team\n\nSubscribe to our ‘web3 weekly newsletter’: a16zcrypto.substack.com\n\nListen to our ‘web3 with a16z’ podcast: a16zcrypto.com/web3-with-a16z-podcast/\n\nRead more of our work: a16zcrypto.com","tokens":375,"crawled_at":1791193657646}
+{"id":10270,"url":"https://www.metaplex.com/docs/solana/understanding-solana-accounts","domain":"www.metaplex.com","chapter":"docs","title":"Understanding Solana Accounts | Solana Account Model Guide","text":"A comprehensive guide to Solana's account model—the foundation for understanding tokens, NFTs, and all on-chain data storage.\nWhat You'll Learn\nHow Solana accounts differ from Ethereum accounts\nAccount ownership and the program model\nRent and rent exemption\nTypes of accounts you'll encounter in token development\nPrerequisites\nBasic blockchain understanding\nSolana CLI installed (for examples)\nThe Solana Account Model\nOn Solana, everything is an account. Unlike Ethereum where contracts have their own storage, Solana separates code (programs) from data (accounts).\n┌─────────────────────────────────────────────┐\n\n│ Account │\n\n├─────────────────────────────────────────────┤\n\n│ lamports: 1000000 │ ← Balance (in lamports, 1 SOL = 1B lamports)\n\n│ data: [bytes...] │ ← Arbitrary data storage\n\n│ owner: 11111111111111111111111111111111 │ ← Program that controls this account\n\n│ executable: false │ ← Is this a program?\n\n│ rent_epoch: 123 │ ← Rent tracking\n\n└─────────────────────────────────────────────┘\n\nKey Concepts\nConceptDescription\nLamports\nThe balance in the smallest unit (1 SOL = 1,000,000,000 lamports)\n\nData\nArbitrary bytes stored in the account\n\nOwner\nThe program ID that can modify this account's data\n\nExecutable\nWhether this account contains program code\n\nAccount Ownership\nEvery account has an owner—a program that has exclusive rights to:\nModify the account's data\nDebit lamports from the account\nChange the account's owner (transfer ownership)\nThe System Program\nThe System Program (11111111111111111111111111111111) owns all basic wallet accounts:\n# View a wallet account\n\nsolana account <YOUR_WALLET_ADDRESS>\n\n# Output shows:\n\n# Owner: 11111111111111111111111111111111\n\nWhen you transfer SOL, you're asking the System Program to debit your account.\nProgram Ownership\nWhen a program creates an account, that program becomes the owner:\n┌─────────────────────────────────────────────────────────────┐\n\n│ Token Program owns token-related accounts │\n\n│ │\n\n│ Token Program ──owns──► Mint Account │\n\n│ │ │\n\n│ └──────owns──► Token Account (your token balance) │\n\n│ │\n\n│ Metaplex Token Metadata Program ──owns──► Metadata Account │\n\n└─────────────────────────────────────────────────────────────┘\n\nTypes of Accounts\n1. Wallet Accounts (System Accounts)\nBasic accounts that hold SOL:\n# Create a new wallet\n\nsolana-keygen new --outfile wallet.json\n\n# This creates a keypair, and when funded, a System Program-owned account\n\nsolana airdrop 1\n\nProperties:\nOwner: System Program\nData: Empty (0 bytes)\nPurpose: Hold SOL, sign transactions\n2. Program Accounts\nAccounts that contain executable code:\n# View a program account\n\nsolana account TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA\n\n# Owner: BPFLoaderUpgradeab1e11111111111111111111111\n\n# Executable: true\n\nProperties:\nOwner: BPF Loader\nExecutable: true\nData: Compiled program bytecode\n3. Data Accounts\nAccounts that store arbitrary data for programs:\n# View a token mint account\n\nsolana account <MINT_ADDRESS>\n\n# Owner: TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA (Token Program)\n\n# Executable: false\n\n# Data: [mint data...]\n\n4. Program Derived Addresses (PDAs)\nSpecial accounts derived deterministically from a program ID and seeds:\nPDA = hash(seeds + program_id + \"PDA\")\n\nProperties:\nNo private key (cannot sign transactions)\nOnly the deriving program can sign for it\nDeterministic—same inputs always produce same address\nSee Understanding PDAs for more details.\nAccounts in Token Development\nWhen working with Metaplex tools, you'll interact with several account types:\nToken Mint Account\nRepresents the token itself:\n┌─────────────────────────────────────────────┐\n\n│ Mint Account │\n\n├─────────────────────────────────────────────┤\n\n│ mint_authority: <pubkey> │ ← Who can mint more\n\n│ supply: 1000000 │ ← Total supply\n\n│ decimals: 9 │ ← Decimal places\n\n│ freeze_authority: <pubkey> │ ← Who can freeze\n\n└─────────────────────────────────────────────┘\n\nToken Account (Associated Token Account)\nHolds a user's balance of a specific token:\n┌─────────────────────────────────────────────┐\n\n│ Token Account │\n\n├─────────────────────────────────────────────┤\n\n│ mint: <mint_pubkey> │ ← Which token\n\n│ owner: <wallet_pubkey> │ ← Who owns these tokens\n\n│ amount: 500 │ ← Balance\n\n│ state: Initialized │ ← Account state\n\n└─────────────────────────────────────────────┘\n\nMetadata Account (Metaplex)\nStores token/NFT metadata on-chain:\n┌─────────────────────────────────────────────┐\n\n│ Metadata Account │\n\n├─────────────────────────────────────────────┤\n\n│ mint: <mint_pubkey> │ ← Associated mint\n\n│ name: \"My Token\" │\n\n│ symbol: \"MTK\" │\n\n│ uri: \"https://...\" │ ← Off-chain metadata\n\n│ creators: [...] │ ← Creator info\n\n│ royalties: 500 (5%) │\n\n└─────────────────────────────────────────────┘\n\nSPL Token Model vs Metaplex Core\nThe account structure for tokens and NFTs differs significantly depending on the program you use.\nSPL Token + Token Metadata uses multiple accounts per asset:\n┌──────────────────────────────────────────────────────┐\n\n│ SPL Token Model (3+ accounts per asset) │\n\n│ │\n\n│ Mint Account ← Token definition (82 bytes) │\n\n│ Token Account (ATA) ← Holder's balance (165 bytes)│\n\n│ Metadata Account ← Name, symbol, URI (PDA) │\n\n│ Master Edition ← NFT edition tracking (PDA) │\n\n└──────────────────────────────────────────────────────┘\n\nEach account is owned by a different program, requires its own rent-exempt deposit, and must be managed separately. Transferring an NFT means updating the Token Account; metadata lives in a separate PDA owned by the Token Metadata program.\nMetaplex Core collapses everything into a single account:\n┌──────────────────────────────────────────────────────┐\n\n│ Core Model (1 account per asset) │\n\n│ │\n\n│ Asset Account │\n\n│ ├── owner: <wallet_pubkey> │\n\n│ ├── name: \"My NFT\" │\n\n│ ├── uri: \"https://...\" │\n\n│ └── plugins: [royalties, freeze, burn, ...] │\n\n└──────────────────────────────────────────────────────┘\n\nWith Core, ownership, metadata, and extensibility (via plugins) are stored in one account owned by the Core program. This means fewer accounts to create, lower rent costs, and simpler transactions.\nSPL Token + Token MetadataMetaplex Core\nAccounts per NFT\n3–4 (mint, token, metadata, edition)\n1 (asset)\n\nRent cost\n~0.01 SOL\n~0.003 SOL\n\nOwnership\nToken Account tracks balance\nAsset account owner field\n\nMetadata\nSeparate PDA\nBuilt into the asset account\n\nExtensibility\nToken Extensions (Token-2022)\nPlugin system\n\nBest for\nFungible tokens (SPL)\nNFTs and digital assets\n\nWhich should I use?\nFor NFTs and digital assets, use Metaplex Core — it's simpler, cheaper, and purpose-built. For fungible tokens (currencies, rewards), use the SPL Token program with Metaplex Token Metadata for on-chain metadata.\n\nRent and Rent Exemption\nAccounts must pay rent to exist on Solana. This prevents blockchain bloat.\nHow Rent Works\nRent is paid in lamports based on data size\nAccounts that fall below minimum balance are purged\nRent-exempt accounts pay a one-time deposit and exist forever\nRent Exemption\nTo be rent-exempt, an account must hold minimum lamports based on its size:\n# Check rent-exempt minimum for different sizes\n\nsolana rent 0 # Wallet (0 bytes): ~0.00089 SOL\n\nsolana rent 82 # Mint Account: ~0.002 SOL\n\nsolana rent 165 # Token Account: ~0.0025 SOL\n\nsolana rent 679 # Metadata Account: ~0.0056 SOL\n\nAlways Rent-Exempt\nWhen creating accounts with Metaplex tools (MPLX CLI, SDKs), the tools automatically calculate and include rent-exempt amounts. You don't need to manually calculate rent.\n\nRecovering Rent\nWhen you close an account, you recover the rent deposit:\n# Burning an NFT recovers most of its rent\n\nmplx core burn-asset <ASSET_ADDRESS>\n\n# Returns ~0.00089 SOL\n\nSolana vs Ethereum\nComing from Ethereum? Here are the key differences:\nAspectEthereumSolana\nContract storage\nContract stores its own data\nPrograms are stateless; data in separate accounts\n\nAccount creation\nImplicit (just send to address)\nExplicit (must create and fund account)\n\nStorage cost\nGas per operation\nRent exemption (one-time deposit)\n\nOwnership\nContracts own themselves\nPrograms own data accounts\n\nBalance storage\nSingle balance field\nSeparate token accounts per token\n\nPractical Implications\nToken balances: On Ethereum, one contract tracks all balances. On Solana, each holder has a separate token account:\nEthereum:\n\nERC-20 Contract\n\n└── balances mapping\n\n├── Alice: 100\n\n└── Bob: 50\n\nSolana:\n\n├── Mint Account\n\n├── Alice's Token Account → amount: 100\n\n└── Bob's Token Account → amount: 50\n\nViewing Accounts\nCLI\n# View account info\n\nsolana account <ADDRESS>\n\n# View in JSON format\n\nsolana account <ADDRESS> --output json\n\n# View only data (hex encoded)\n\nsolana account <ADDRESS> --output json | jq '.data'\n\nExplorer\nUse Solana Explorer or SolanaFM to view accounts visually:\nSolana Explorer\nSolanaFM\nProgrammatically\nimport { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nconst umi = createUmi('https://api.devnet.solana.com')\n\nconst account = await umi.rpc.getAccount(publicKey('YourAddressHere...'))\n\nif (account.exists) {\n\nconsole.log('Owner:', account.owner)\n\nconsole.log('Lamports:', account.lamports)\n\nconsole.log('Data length:', account.data.length)\n\n}\n\nCommon Patterns\nWhy \"Account Not Found\"?\nOn Solana, accounts must be explicitly created:\nError: Account does not exist\n\nCause: The account has never been created, or it was closed/purged\n\nSolution: Create the account first (automatic with most Metaplex operations)\n\nAssociated Token Accounts (ATAs)\nATAs are deterministically derived so you don't need to track them:\nATA = derive(wallet_address, mint_address, token_program)\n\nThe MPLX CLI and SDKs automatically create ATAs when needed:\n# This auto-creates the recipient's ATA if it doesn't exist\n\nmplx toolbox token-transfer <RECIPIENT> <AMOUNT>\n\nNext Steps\nUnderstanding PDAs - Dive deeper into Program Derived Addresses\nTransaction fundamentals - How transactions work on Solana\nCreate a Solana token - Put this knowledge into practice\nFAQ\nWhy do I need to create token accounts?\nUnlike Ethereum where a contract tracks balances, Solana requires separate accounts. This enables parallel processing—different accounts can be modified simultaneously.\nWhat happens if my account runs out of rent?\nIf an account falls below the rent-exempt threshold, it will be purged after some time, and the remaining lamports returned to the owner. Always keep accounts rent-exempt.\nCan I close accounts to recover SOL?\nYes! When you burn NFTs or close token accounts, you recover the rent-exempt deposit. This is why burning assets returns SOL.\nWhy does my wallet show a small balance after minting?\nCreating accounts (mint, metadata, token accounts) requires rent-exempt deposits. These are locked in the accounts, not spent.\nWhat's the difference between owner and authority?\nOwner (on-chain): The program that controls the account's data\nAuthority (in account data): The wallet that can perform certain actions (like minting)\nExample: A Mint Account is owned by the Token Program, but its mint authority is your wallet.","tokens":2771,"crawled_at":1791193668816}
+{"id":10271,"url":"https://stack.olas.network/open-autonomy/advanced_reference/commands/autonomy_mint","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"autonomy mint - Olas Stack Developer Documentation","text":"autonomy mint\n\nTools for minting software packages in the Olas Protocol.\n\nThis command group consists of a number of functionalities to mint components, agent blueprints and AI agents in the Olas Protocol. These commands are the CLI alternative to mint packages using the Olas Protocol web app. See the appropriate subcommands for more information.\n\nInfo\n\nYou can specify how you wish to sign the on-chain transactions produced by these commands: either with a private key stored in a file, or with a hardware wallet. In this latter case, ensure that you have configured properly the drivers for your hardware wallet.\n\nOptions\n\n--dry-run\nPerform a dry run for the transaction.\n--use-celo\nUse the Celo chain profile to interact with the Autonolas Protocol registry contracts.\n--use-base\nUse the Base chain profile to interact with the Autonolas Protocol registry contracts.\n--use-optimism\nUse the Optimism chain profile to interact with the Autonolas Protocol registry contracts.\n--use-arbitrum-one\nUse the Arbitrum One chain profile to interact with the Autonolas Protocol registry contracts.\n--use-gnosis\nUse the Gnosis chain profile to interact with the Autonolas Protocol registry contracts.\n--use-polygon\nUse the Polygon chain profile to interact with the Autonolas Protocol registry contracts.\n--use-ethereum\nUse the Ethereum chain profile to interact with the Autonolas Protocol registry contracts.\n\nTo use these chain profile, you will have to export an environment variable for RPC in <CHAIN_NAME>_CHAIN_RPC format. For example if you want to use ethereum, you will have to export ETHEREUM_CHAIN_RPC.\n\n--use-custom-chain\n\nUse the custom-chain profile to interact with the Autonolas Protocol registry contracts. This profile requires that you define some parameters and contract addresses as environment variables (see also the Olas Protocol documentation for more information):\n\nCUSTOM_CHAIN_RPC : RPC endpoint for the custom chain.\n\nCUSTOM_CHAIN_ID : chain ID.\n\nCUSTOM_COMPONENT_REGISTRY_ADDRESS : Custom Component Registry contract address.\n\nCUSTOM_AGENT_REGISTRY_ADDRESS : Custom Agent Registry contract address.\n\nCUSTOM_REGISTRIES_MANAGER_ADDRESS : Custom Registries Manager contract address.\n\nCUSTOM_SERVICE_MANAGER_ADDRESS : Custom Service Manager contract address.\n\nCUSTOM_SERVICE_REGISTRY_ADDRESS : Custom Service Registry contract address.\n\nCUSTOM_GNOSIS_SAFE_PROXY_FACTORY_ADDRESS : Custom Gnosis Safe multisig contract address.\n\nCUSTOM_GNOSIS_SAFE_SAME_ADDRESS_MULTISIG_ADDRESS : Custom Gnosis Safe Same Address Multisig address.\n\nCUSTOM_SERVICE_REGISTRY_TOKEN_UTILITY_ADDRESS : Custom Service Registry Token Utility address.\n\nCUSTOM_MULTISEND_ADDRESS : Custom Multisend address.\n\nNote\n\nFor L2 chains you are only required to set\n- CUSTOM_SERVICE_MANAGER_ADDRESS,\n- CUSTOM_SERVICE_REGISTRY_ADDRESS,\n- CUSTOM_GNOSIS_SAFE_PROXY_FACTORY_ADDRESS,\n- CUSTOM_GNOSIS_SAFE_SAME_ADDRESS_MULTISIG_ADDRESS and\n- CUSTOM_MULTISEND_ADDRESS.\n\n--use-local\nUse the local chain profile to interact with the Autonolas Protocol registry contracts. This option requires that you have a local Hardhat node with the required contracts deployed.\n\nNote\n\nThe chain profile flags are mutually exclusive.\n\n-t, --timeout FLOAT\nTimeout for on-chain interactions\n-r, --retries INTEGER\nMax retries for on-chain interactions\n--sleep FLOAT\nSleep period between retries\n\nautonomy mint protocol / contract / connection / skill\n\nMint a protocol, contract, connection or skill in the Autonolas Protocol.\n\nUsage\n\nautonomy mint protocol [OPTIONS] PACKAGE_PATH\nautonomy mint contract [OPTIONS] PACKAGE_PATH\nautonomy mint connection [OPTIONS] PACKAGE_PATH\nautonomy mint skill [OPTIONS] PACKAGE_PATH\n\nOptions\n\n--key FILE\nUse a private key from a file to sign the transactions.\n--hwi\nUse a hardware wallet to sign the transactions.\n--password PASSWORD\nPassword for the key file.\n--nft IPFS_HASH_OR_IMAGE_PATH\nIPFS hash or path to the image for the NFT representing the package. Note that if you are using a local chain this option is not required.\n--owner OWNER_ADDRESS\nOwner address of the package.\n--update TOKEN_ID\nUpdate the existing minted token with the latest package hash.\n\nExamples\n\nMint the abstract_abci skill in a local chain:\n\nautonomy mint --use-local skill --key my_key.txt --nft <nft_ipfs_hash_or_image_path> --owner <owner_address> ./packages/valory/skills/abstract_abci\n\nSame as above, but using a hardware wallet:\n\nautonomy mint --use-local skill --hwi --nft <nft_ipfs_hash_or_image_path> --owner <owner_address> ./packages/valory/skills/abstract_abci\n\nUpdate the minted abstract_abci skill using\n\nautonomy mint --use-local skill --key my_key.txt --nft <nft_ipfs_hash_or_image_path> --owner <owner_address> ./packages/valory/skills/abstract_abci --update <token_id>\n\nPerform a dry run\n\nautonomy mint --dry-run protocol ./packages/valory/protocols/abci --key key.txt\n\nOutput\n\n=== Dry run output ===\nMethod: RegistriesManagerContract.get_create_transaction\nContract: 0x...\nKwargs:\nowner: 0x...\ncomponent_type: UnitType.COMPONENT\nmetadata_hash: 0x...\nsender: 0x...\n§ncies: []\nTransaction:\nchainId: 31337\nnonce: 0\nvalue: 0\ngas: 16000\nmaxFeePerGas: 4000000000\nmaxPriorityFeePerGas: 3000000000\nto: 0x...\ndata: 0x...\n\nautonomy mint agent\n\nMint an agent blueprint in the Autonolas Protocol.\n\nUsage\n\nautonomy mint agent [OPTIONS] PACKAGE_PATH\n\nOptions\n\n--key FILE\nUse a private key from a file to sign the transactions.\n--hwi\nUse a hardware wallet to sign the transactions.\n--password PASSWORD\nPassword for the key file.\n--nft NFT_HASH_OR_IMAGE_PATH\nIPFS hash or path to the image for the NFT representing the package. Note that if you are using a local chain this option is not required.\n--owner OWNER_ADDRESS\nOwner address of the package.\n--update TOKEN_ID\nUpdate the already minted agent blueprint with on-chain TOKEN_ID with the current package hash.\n\nExamples\n\nMint the hello_world agent blueprint in the Ethereum main chain:\n\nautonomy mint --use-ethereum agent --key my_key.txt --nft <nft_ipfs_hash_or_image_path> --owner <owner_address> ./packages/valory/agents/hello_world\n\nSame as above, but using a hardware wallet:\n\nautonomy mint --use-ethereum agent --hwi --nft <nft_ipfs_hash_or_image_path> --owner <owner_address> ./packages/valory/agents/hello_world\n\nautonomy mint service\n\nMint an AI agent in the Autonolas Protocol.\n\nUsage\n\nautonomy mint service [OPTIONS] PACKAGE_PATH\n\nOptions\n\n--key FILE\nUse a private key from a file to sign the transactions.\n--hwi\nUse a hardware wallet to sign the transactions.\n--password PASSWORD\nPassword for the key file.\n--nft IPFS_HASH_OR_IMAGE_PATH\nIPFS hash or path to the NFT image for the NFT image representing the package. Note that if you are using a local chain this option is not required.\n--owner OWNER_ADDRESS\nOwner address of the package.\n-a, --agent-id AGENT_ID\nAgent blueprint ID.\n-n, --number-of-slots NUM_SLOTS\nNumber of instances for the agent blueprint.\n-c, --cost-of-bond COST_BOND_WEI\nCost of bond for the agent instance (Wei).\n--threshold\nThreshold for the minimum number of agent instances required to run the AI agent. The threshold has to be at least ⌈(2N+1)/3⌉, where N is total number of the agent instances in the AI agent.\n--token ERC20_TOKEN_ADDRESS\nERC20 token for securing the AI agent.\n--update TOKEN_ID\nUpdate the already minted AI agent with on-chain TOKEN_ID with the current package hash.\n\nExamples\n\nMint the hello_world AI agent with 4 instances of agent blueprint ID 3, cost of bond 10000000000000000 Wei per agent instance and a threshold of 3 instances, in the Ethereum main chain:\n\nautonomy mint --use-ethereum service --key my_key.txt --nft <nft_ipfs_hash_or_image_path> --owner <owner_address> --agent-id 3 --number-of-slots 4 --cost-of-bond 10000000000000000 --threshold 3 ./packages/valory/services/hello_world\n\nSame as above, but using a hardware wallet:\n\nautonomy mint --use-ethereum service --hwi --nft <nft_ipfs_hash_or_image_path> --owner <owner_address> --agent-id 3 --number-of-slots 4 --cost-of-bond 10000000000000000 --threshold 3 ./packages/valory/services/hello_world\n\nNote\n\nYou can specify more than one type of agent blueprints in an AI agent by appropriately defining the triplets --agent-id, --number-of-slots and --cost-of-bond for each agent blueprint ID.\n\nYou can also use a custom ERC20 token as token to secure the AI agent. Use the --token flag to provide the address of the token of your choice:\n\nautonomy mint --use-ethereum service --key my_key.txt --nft <nft_ipfs_hash_or_image_path> --owner <owner_address> --agent-id 3 --number-of-slots 4 --cost-of-bond 10000000000000000 --threshold 3 ./packages/valory/services/hello_world --token <erc20_token_address>\n\nImportant\n\nIf you have minted an AI agent using a custom ERC20 token, then you have to use the same token to activate the AI agent and to register the agent instances.","tokens":2206,"crawled_at":1791193672321}
+{"id":10272,"url":"https://a16zcrypto.com/team/lioba-heimbach","domain":"a16zcrypto.com","chapter":"research","title":"Lioba Heimbach - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nLioba Heimbach\n\nFeed\nFilter\n(1)\nclear filters\n\ncategory\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\nrecommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nauthor\n(1) all authors\n@x0rart\n1337 Skulls Sers\na16z crypto\na16z crypto editorial\na16z crypto policy & regulatory teams\na16z crypto Regulatory Team\nAaditya Shidham\nAaron Levie\nAaron Phillips\nAaron Schnider\nAbby Green\nAbdou Ndiaye\nAbhi Shelat\nAbhiram Kothapalli\nAbigail Johnson\nAdam Alter\nAdam Back\nAdam Bry\nAdam Grant\nAdam Ludwin\nAdam Martin\nAdam Thierer\nAdam Zuckerman\nAdela Tomsejova\nAdena Friedman\nAdena Hefets\nAdeniyi Abiodun\nAdina Fischer\nAdrian Cockcroft\nAdrian Fenty\nAdrienne Mayor\nAgostino Capponi\nAiden Slavin\nAileen Lee\nAisha Stephenson\nAJ Shankar\nAlan Knott-Craig\nAlan Schaaf\nAlana Benton\nAlbert Tang\nAlec Nielsen\nAlec Ross\nAlejandro Flores\nAlex Constantinople\nAlex Honnold\nAlex Hutchinson\nAlex Immerman\nAlex Kreitz\nAlex Kroeger\nAlex Le\nAlex Masmej\nAlex Morcos\nAlex Price\nAlex Pruden\nAlex Rampell\nAlex Roetter\nAlex Solomon\nAlex Spector\nAlex Stamos\nAlex Tabarrok\nAlexander (Sasha) Spiegelman\nAlexander Chia\nAlexander Zoppa\nAlexandra Chang\nAlexandria Lafci\nAlexis Lakes\nAlexis Madrigal\nAlexis Ohanian\nAli Ghodsi\nAli Yahya\nAlicia Barone\nAlin Tomescu\nAlisha Litman\nAlison Mangiero\nAlison Martin\nAllison Pickens\nAlyssa Del Bene\nAlyssa Torres\nAmanda Cantor\nAmanda Cassatt\nAmanda Catherine\nAmanda Mulay\nAmanda Tuminelli\nAmanda Tyler\nAmelia Salyers\nAmie Tyrrel\nAmir Shevat\nAmira Yahyaoui\nAmy Abernethy\nAmy Berliner\nAmy Bohutinsky\nAmy Choice\nAmy Cray\nAmy Gill\nAmy Hoemeke\nAmy Kalokerinos\nAmy Robertson\nAna Mostarac\nAna Susi\nAnatoly Yakovenko\nAndie Taylor\nAndisheh Tahriri\nAndre Iguodala\nAndrea Clarke Hall\nAndrea Feinberg\nAndrea Rallo\nAndrea Simon\nAndrea Vinkler\nAndreas Papadimitropoulos, Jr\nAndreessen Horowitz\nAndrew Allen\nAndrew Chen\nAndrew F. Read\nAndrew Green\nAndrew Hall\nAndrew Lakis\nAndrew Lewis-Pye\nAndrew Lo\nAndrew Mason\nAndrew McAfee\nAndrew Milson\nAndrew Omori\nAndrew Radin\nAndrew Rubin\nAndrew Savage\nAndrew Smith\nAndrew Tretyakov\nAndy Beal\nAndy Coravos\nAndy Golden\nAndy Hill\nAndy Milenius\nAndy Rachleff\nAndy Tran\nAndy Walshe\nAneel Lakhani\nAngela Schenone\nAngela Strange\nAngela Tran Kingyens\nAngelica Gehr\nAniket Kate\nAnil Sethi\nAnish Acharya\nAnn Winblad\nAnna Berces\nAnna Jablonski\nAnna Semenova\nAnna Van Meurs\nAnnaLee Saxenian\nAnne Brandes\nAnne Lee Skates\nAnne Lewandowski\nAnne Mitchell\nAnne Yip\nAnnie Collins\nAnnie Duke\nAnthony Albanese\nAnthony Atala\nAnthony Foxx\nAnthony Lee Zhang\nAntonio Viggiano\nAntwone Stigall\nAnu Hariharan\nApril Roth\nAri Emanuel\nAri Juels\nArianna Huffington\nArianna Simpson\nArik Kershenbaum\nArmon Dadgar\nArnie Goldberg\nArsho Avetian\nArthur Brooks\nArun Sundararajan\nAsh Ashutosh\nAsha Christian\nAshley McCollum\nAshley Stern\nAshton Carter\nAtif Mian\nAtul Butte\nAubree Pelaez\nAubrey de Grey\nAugusto Marietti\nAurora Petracca\nAusten Allred\nAustin Guzman\nAustin Marchese\nAustin Wilson\nAva Iravani\nAvery Segal\nAvinash Solanky\nAviv Zohar\nAye Moah\nAzeem Azhar\nBailey Flanigan\nBailey Richardson\nBalaji Srinivasan\nBarry McCarthy\nBart Dessaint\nBeau Cronin\nBeau Woods\nBecky Pferdehirt\nBen Buckwalter\nBen Fielding\nBen Fisch\nBen Gardner\nBen Gomez\nBen Horowitz\nBen Kaufman\nBen Leventhal\nBen Lovell\nBen Napier\nBen Portney\nBen Rubin\nBen Scharfstein\nBen Schecter\nBen Silbermann\nBen Uretsky\nBen Wu\nBenedict Evans\nBenedikt Büenz\nBenjamin Ebner\nBenjamin Hindman\nBenjamin Wittes\nBenjamin Wu\nBennett Carroccio\nBenny Pinkas\nBernard J. Tyson\nBernard Tyson\nBeth Newman\nBethany Coates\nBharat Ramamurti\nBharath Ramsundar\nBill Carr\nBill Frist\nBill Hinman\nBill Janeway\nBill Krause\nBill Macaitis\nBlake Kim\nBlake Masters\nBlake Saari\nBlayne Donnell\nBob Iger\nBob Langer\nBob Moore\nBob Muglia\nBob Sutton\nBob Swan\nBob Tinker\nBob Wachter\nBobby Franklin\nBobby Green\nBobby Kotick\nBobby Wagner\nBoris Sofman\nBoris Wertz\nBrad Feld\nBrad Kern\nBrad Peterson\nBram Cohen\nBrandon Ballinger\nBrandon Barros\nBrandon Cherry\nBrandon Millman\nBrenda Kopf\nBrent McIntosh\nBrett Browman\nBrett Falk\nBrett Hagler\nBrewster Kahle\nBrian Armstrong\nBrian Balfour\nBrian Brooks\nBrian Crnkovich\nBrian Curran\nBrian Grazer\nBrian Koppelman\nBrian McCullough\nBrian Quintenz\nBrian Wilkins\nBridget McDowell\nBrittany Lucas\nBrittney Burrows\nBrooke Sheresky\nBruce Friedrich\nBryan Caplan\nBryan Chiang\nBryan Cox\nBryan Crowley\nBryan Faust\nBryan Houser\nBryan Kim\nBryan Pellegrino\nCaitlin Glazebrook\nCaitlin Johnston\nCaitlin Roberson\nCal Turner Jr.\nCaleb Christian\nCameron Schuler\nCamila De Souza\nCarine Carmy\nCarissa Bilinski\nCarl Agnelli\nCarl Eschenbach\nCarl Narcisse\nCarl Pope\nCarlos Araya\nCarolina Gonzalez\nCaroline Friedman\nCaroline Goggins\nCaroline Horn\nCaroline Moon\nCarolyn Bertozzi\nCarra Wu\nCasey Graul\nCasey Neistat\nCasey Winters\nCassady Churchill\nCassie Faerber\nCecilia Marshall\nCeia Font\nChad Rigetti\nChandra Krintz\nCharles Goetz\nCharles Hubbard\nCharles Koch\nCharlie Keinath\nCharlie Warzel\nChattry Meas\nChelsea Komlo\nChelsea Padilla\nCheng Li\nChris Bennett\nChris Best\nChris Burniske\nChris Curran\nChris DeWolfe\nChris Dixon\nChris Granger\nChris Hauth\nChris Lyons\nChris Messina\nChris Milk\nChris Power\nChris Santa Maria\nChris Wanstrath\nChristian Cachin\nChristian Catalini\nChristian Crowley\nChristian Seifert\nChristina Hampp\nChristina Lopes\nChristina Mercando\nChristina Xu\nChristina Zeidan\nChristine Darden\nChristine Perham\nChristopher Giancarlo\nChristopher Lee\nChristopher Mims\nChristopher Nguyen\nChristopher Rippingham\nChristopher Schroeder\nChristy Hubbard\nCiamac Moallemi\nCindi Zhang\nCindy Tenner\nClaire Austin\nClaire Cain Miller\nClaire Kart\nClaudia Picanco\nClay Shirky\nClayton Christensen\nClayton Gardner\nClifford Woolf\nClint Delapaz\nColin Bryar\nColin Rom\nCollin McCune\nConner Lyons Brown\nConnie Chan\nConnie Guglielmo\nConnor McCarthy\nConnor Moyles\nCorban Bell\nCorey Hawkins\nCorey Waller\nCourtney Dettlinger\nCraig Naylor\nCraig Walker\nCristina Cordova\nCurt Funderburk\nCuy Sheffield\nD'Arcy Coolican\nDaejun Park\nDaisy Linden\nDaisy Wolf\nDaljeet Virdi\nDalton Turay\nDan Berkenstock\nDan Boneh\nDan Frommer\nDan Primack\nDan Romero\nDan Shapero\nDan Siroker\nDan Stein\nDan Warmenhoven\nDan Wendlandt\nDaniel Chao\nDaniel Chen\nDanielle Andrzejewski\nDanielle Clark\nDanielle Looymans\nDanielle Lussier\nDanielle Morrill\nDanielle Shea\nDanny Shader\nDaphne Koller\nDapper Dan\nDaren Matsuoka\nDarin Malter\nDarshan Shankar\nDas Rush\nDave Jagoda\nDave King\nDave Touretzky\nDavid Banks\nDavid Belden\nDavid Damato\nDavid Deming\nDavid George\nDavid Haber\nDavid Hollestelle\nDavid Kerr\nDavid Lee\nDavid Mack\nDavid Madden\nDavid Marcus\nDavid Olson\nDavid Oyelowo\nDavid Pierce\nDavid Reich\nDavid Rumsey\nDavid Schweikert\nDavid Sinclair\nDavid Sverdlov\nDavid Tse\nDavid Ulevitch\nDavid Weiden\nDawn Lepore\nDawn Nott\nDeborah Embaie\nDeena Elitreby\nDeepak Maram\nDenis Nazarov\nDenis Young\nDenise Gonzalez\nDerek Dolin\nDerek Thompson\nDerrick Harris\nDevin Finzer\nDevon Zuegel\nDiana Peña\nDiane Greene\nDick Costolo\nDieter Shirley\nDiishan Imira\nDiogo Monica\nDominic Shine\nDominique Reliford\nDon Duet\nDon Faul\nDorris O'Brien\nDoug Ducey\nDoug Folden\nDoug McCracken\nDouglas Argueta\nDozie Uche\nDrew Coffman\nDylan Field\nDylan Rhodes\nEd Felten\nEd Lynch\nEddie Lim\nEddy Lazzarin\nEdith Zimmerman\nEdward Perkins\nEdwin Poston\nEfrat Noy\nEhud Shapiro\nEileen Burbidge\nEileen Wu\nElad Gil\nElaine Fuchs\nElaine Shi\nElena Burger\nEli Dourado\nElisa Leonhardt\nEliza Oak\nElizabeth Gunn\nElizabeth Harkavy\nElizabeth May\nElizabeth Ocken\nElizabeth Stark\nElizabeth Weil\nEllen Tunoa\nEmile Petrone\nEmilio Torres\nEmily Graff\nEmily Hinsch\nEmily Keir\nEmily Oster\nEmily Westerhold\nEmma Janaskie\nEric Budish\nEric Dai\nEric Ries\nEric Thomas\nEric Topol\nEric Wu\nErica Schecter\nErik Brynjolfsson\nErik Kiser\nErik Torenberg\nErika Bracken\nErika Herrera\nErika Louie\nErin Grody Kingsley\nErin Murphy\nErin Tice\nErin Tonnar\nErin Winkler\nErtem Nusret Tas\nEsther Shinn\nEthan Bueno de Mesquita\nEthan Ferreira\nEthan Zuckerman\nEuan Ashley\nEugene Volokh\nEugene Wei\nEugenia Yee\nEula Takahashi\nEva Sakkas\nEvan Burfield\nEvan Osnos\nEvangelos Simoudis\nEzra Klein\nF. Gary Gray\nFabiola Godinez\nFabrizio Zilibotti\nFahad Saleh\nFarid Jiandani\nFei-Fei Li\nFelix Do\nFEWOCIOUS\nFiona Kennedy\nFiona Murray\nFlashrekt\nFlora Oliveira\nFlori Del Valle\nFlorian Leibert\nFoteini Baldimtsi\nFrancesca Gino\nFrank Chen\nFrank Wilczek\nFred Benenson\nFred Ehrsam\nFred Upton\nFred Wilson\nFreda Lewis-Hall\nFrederic Kerrest\nFuture Editorial\nGabby Dizon\nGabby Reece\nGabriel Otte\nGabriel Vasquez\nGaetan Barthelemy\nGarrett Biel\nGary Ang\nGary Reedy\nGary Wolf\nGaurav Banga\nGaurav Dhillon\nGaut\nGayle Tzemach Lemmon\nGeoffrey Woo\nGeorg Fuchsbauer\nGeorg Petschnigg\nGeorge Church\nGeorge Danezis\nGeorge Fraser\nGeraldine Chan\nGérard Cachon\nGerard Ryle\nGerri Elliott\nGerry Tsoukalas\nGia Scinto\nGil Elbaz\nGil Shafir\nGina Moon\nGina Neff\nGina Yocom\nGinger Liau\nGokul Rajaram\nGoldie Chang\nGrace Ellis\nGraham Allison\nGrant Gregory\nGrant Jordan\nGrant LaFontaine\nGrant Rabenn\nGray Kinsella\nGreg Bowman\nGreg Clayman\nGreg Linares\nGreg Loehmann\nGreg Lynn\nGreg Solano\nGreg Truesdell\nGreg Waldon\nGregory Allen\nGregory Mundis\nGretchen Bush\nGretchen McCulloch\nGuido Appenzeller\nGustav Söderström\nGustavo Garcia\nGuy Goren\nGuy Raz\nGuy Wuollet\nHaley Van Dyck\nHanna Aziz\nHannah Frankl\nHanne Winarsky\nHaoyuan Li\nHarmit Malik\nHarry Grieve\nHarry Shum\nHarry Wright\nHatim Shafique\nHayden Adams\nHeather Gwynn\nHeather Podesta\nHedi Samar\nHelen Stoddard\nHelen Su\nHemant Mohapatra\nHendrik Pretorius\nHenri Kor\nHerb Lin\nHerman Narula\nHilmar Pétursson\nHoang Nguyen\nHoward Wu\nIan Dutra\nIan Shannon\nIan Sharp\nIce Cube\nIlan Zechory\nIllia Polosukhin\nIlyas Khan\nIma Christian\nIman Abuzeid\nInsiya Lokhandwala\nIon Stoica\nIrvin Chan\nIsa Guardalabene\nIsaiah Lott\nIsh Verduzco\nIsil Dillig\nIstván András Seres\nIttai Abraham\nIttay Eyal\nIva Messy\nIvan Linscott\nIvor Horn\nJ.D. Moriarty\nJack Donahoe\nJack Soslow\nJackie McQuiston\nJackson David\nJacob Westphal\nJacquelyn Melinek\nJad Esber\nJad Naous\nJade Lai\nJade Raymond\nJae Gnazzo\nJai Ramaswamy\nJaimie Buss\nJak Kennedy\nJake Auchincloss\nJakob Uszkoreit\nJamal Mohammed\nJames Beshara\nJames Currier\nJames da Costa\nJames Gwertzman\nJames J. Collins\nJames Kissell\nJames L. Madara\nJames Loftus\nJames Rathmell\nJames Rogers\nJames Watters\nJames Wu\nJames Zou\nJamie Brandon\nJamie McGurk\nJamie Sullivan\nJamilla Hemeid\nJana Odehnal\nJane Doe\nJane Lippencott\nJane Suh\nJanelle De Los Santos\nJared Bricklin\nJared Furutani\nJared Georgakopoulos\nJared Polis\nJared Smith\nJase Wilson\nJason Franklin\nJason Liu\nJason Mayden\nJason Milionis\nJason Mitchell\nJason Mok\nJason Rosenthal\nJason Warner\nJason Yanowitz\nJay Bradner\nJay Conte\nJay Drain\nJay Komarneni\nJay Rughani\nJean Reilly\nJeanne Tsan\nJeff Amico\nJeff Benson\nJeff Clark\nJeff Cordova\nJeff Glueck\nJeff Hawkins\nJeff Jones\nJeff Jordan\nJeff Lawson\nJeff Lu\nJeff Nagashima\nJeff Stump\nJeff Weiner\nJeffrey Immelt\nJeffrey Kaditz\nJeffrey Katzenberg\nJeffrey Kindler\nJeffrey Low\nJeffrey Silverstein\nJeffrey Zirlin\nJen Bulawsky\nJen Kha\nJenna Walsh\nJenna Zucker\nJennifer 8. Lee\nJennifer Doudna\nJennifer Kodner\nJennifer Konde\nJennifer Li\nJennifer Mumford\nJennifer Tejada\nJennifer Young\nJenny Cieplak\nJens Ernstberger\nJensen Harris\nJeremy Clark\nJeremy England\nJeremy Zhang\nJesse Holmes\nJesse Pollak\nJesse Walden\nJessica Childs\nJessica Hansen\nJessica Keeler\nJessica Patton\nJessica Verrilli\nJewel Pi\nJez Humble\nJi Kim\nJianying Luo\nJim Gilliam\nJimmy Chen\nJimmy Soni\nJing Wang\nJing Zou\nJJ Yu\nJoachim Neu\nJodi Lynn\nJodie Lutkenhaus\nJoe Gebbia\nJoe Grundfest\nJoe Montana\nJoe Morrissey\nJoe Schmidt\nJoe Sullivan\nJoel de la Garza\nJoel Mokyr\nJoel Monegro\nJoel Spolsky\nJoey Burleson\nJohn China\nJohn Collison\nJohn Fawcett\nJohn Garcia\nJohn Gedmark\nJohn Hennessy\nJohn Koelliker\nJohn M. Jack\nJohn Markoff\nJohn Menna\nJohn O’Farrell\nJohn Riccitiello\nJohn Smesko\nJohn Stanfield\nJohn Thompson\nJohn William Hatfield\nJonah Peretti\nJonathan Bush\nJonathan Dotan\nJonathan Downey\nJonathan Lai\nJonathan Lim\nJonathan Lusthaus\nJonathan Weissman\nJonathan Wong\nJordan Mazer\nJordan Stankowski\nJorge Conde\nJorge Gomez\nJose Guardado\nJoseph Bonneau\nJoseph Okpaku\nJoseph Spisak\nJosh Arnold\nJosh Bloom\nJosh Kim\nJosh Williams\nJoshua Browder\nJoshua Gans\nJoshua Grimm\nJoshua Hix\nJoshua Levin\nJoshua Lu\nJoshua Schank\nJoshua Soto\nJosie Ma\nJoyce Park\nJR Rivers\nJT Evans\nJuan Benet\nJudene Small\nJudy Savitskaya\nJudy Smith\nJulia Grace\nJulia Kirby\nJulie Bornstein\nJulie Farnham\nJulie Johnson\nJulie Samuels\nJulie Yoo\nJuliet Grier\nJuliet Nyatta\nJuliette Morton\nJulius Zhang\nJustin Bailey\nJustin Bethune\nJustin Blau\nJustin Cunningham\nJustin Gregorius\nJustin Kahl\nJustin Kan\nJustin Larkin\nJustin Paine\nJustin Pettit\nJustin Roberts\nJustin Simcock\nJustin Thaler\nJustine Moore\nJutta Steiner\nJyoti Bansal\nJZ Young\nKabir Gill\nKabir Laroia\nKais Khimji\nKamala Harris\nKaren Dunn\nKaren Wooley\nKarina Sobieski\nKarl Floersch\nkarma (Daniel Reynaud)\nKarmacoma\nKarthik Rau\nKartik Nayak\nKate Darling\nKate Dellolio\nKate Kerames\nKatherine Boyle\nKatherine Minarik\nKatherine Rundell\nKatherine Schoebel\nKathryn McKinley\nKathy Liu\nKathy Yang\nKatia Ameri\nKatie Baynes\nKatie Haun\nKatie Hemmerling\nKaty DeWitt-Drew\nKaty Nelson\nKayvon Tehranian\nKeener Barnhorst\nKeller Medlin\nKeller Rinaudo\nKelly Cannon\nKelsey Chaplinsky\nKelsey Mellard\nKen Chong\nKen Coleman\nKen Kocienda\nKerry Ganim\nKesha Cash\nKevin Chou\nKevin Chu\nKevin Dulsky\nKevin Kelly\nKevin McKinley\nKevin Nishioka\nKevin O'Kane\nKevin Rose\nKevin Tan\nKevin Wu\nKevin Zollman\nKidSuper\nKieran Snyder\nKierston Gittens\nKiki Mavridis\nKim Enright\nKim Malone Scott\nKim Milosevich\nKim Stevenson\nKim Zetter\nKimberly Tan\nKindra Mason\nKira Poskanzer\nKira Song\nKirstin Arbide\nKirt McMaster\nKofi Ampadu\nKouki Harasaki\nKrista Anderson-Copperman\nKristen Fortney\nKristen Johansson\nKristen Kee\nKristin Sauchak\nKristin Thayer\nKristina Graci-deLuna\nKristina Shen\nKristine Lipscomb\nKristo Käärmann\nKrisztina Holly\nKunal Bahl\nKunle Olukotun\nKurt House\nKyle Russell\nLaird Hamilton\nLatasha\nLaura Arrillaga-Andreessen\nLaura Baller\nLaura Behrens Wu\nLaura Deming\nLaura Gravley\nLaura Johnson\nLaura Shores\nLaura Weidman Powers\nLauren Berson\nLauren Illovsky\nLauren Murrow\nLauren Richardson\nLauren Spragge\nLaurene Powell Jobs\nLawrence Levy\nLawrence Summers\nLeah Cassidy\nLee Kleinman\nLee Lefkowitz\nLeeAnn Caballero\nLeila Hay\nLeila Janah\nLenny Rachitsky\nLeslie Jaw\nLeslie Vosshall\nLester Chen\nLi Fan\nLi Fei-Fei\nLi Jin\nLiang Wu\nLilian King\nLily Liu\nLina Sergie Attar\nLinda Banuelos\nLinda Xie\nLinden Tibbets\nLing Ren\nLinlin Li\nLinxin Wen\nLioba Heimbach\nLisa Hawke\nLisa Lambert\nLisa Orr\nLisa Reilly\nLisa Rosano\nLizzy Anderson\nLJ Erwin\nLloyd Dean\nLoretta Sanchez\nLori Potter\nLuca Prosperi\nLuca Zanolini\nLuis Martinez\nLuis von Ahn\nLuke Wroblewski\nLydia Green\nLynda Gibson\nLynn Rudolph\nMadan Nagaldinne\nMaddison Masaeli\nMadeline Lancaster\nMaggie Hsu\nMaggie Leung\nMaggie Romero\nMahad Abedin\nMahesh Iyer\nMahesh Vellanki\nMahimna Kelkar\nMakiri Duckett\nMalinka Walaliyadde\nMallesh M. Pai\nMalloy Evans\nManas Punhani\nManny Luna\nMarc Andreessen\nMarc Andrusko\nMarc Benioff\nMarc Levinson\nMarci Barbera\nMarco Reuter\nMargaret Jen\nMargit Wennmachers\nMaria LaMagna Morales\nMarian Garvin\nMarianne Winkler\nMariano Sorgente\nMaricarmen Alvarez\nMariel Goldenstein\nMarigold Vu\nMarina Kusserow\nMario Gabriele\nMario Linares\nMarissa Bramlett\nMark Cranney\nMark Leslie\nMark McAndrew\nMark McClusky\nMárk Melczer\nMark Moore\nMark Regan\nMark Sendak\nMarkos Georghiades\nMarkus Covert\nMarkus Funk\nMartha Lane Fox\nMartin Casado\nMartin Fischer\nMarty Makary\nMarvin Ammori\nMarvin Zamora\nMary Pat Jordan\nMary-Catherine Lader\nMaryam Bahrani\nMason Hall\nMatei Zaharia\nMatt Abrahams\nMatt Billmann\nMatt Bornstein\nMatt Clifford\nMatt Flannery\nMatt Fleming\nMatt Gleason\nMatt Kaeberlein\nMatt Levine\nMatt Levy\nMatt Oberhardt\nMatt Shortal\nMatt Spence\nMatt Weinberg\nMatthew Colford\nMatthew Green\nMatthew Haughey\nMatthew McCullough\nMatthew Mills\nMatthew Olsen\nMatthew Rutter\nMatthew Stein\nMatthieu Hafemeister\nMaureen Lara\nMax Kesten\nMax Krohn\nMax Levchin\nMax Polyak\nMax Resnick\nMax Ventilla\nMaya Rahkonen\nMcPherson Moore\nMeaghan Hardy\nMeg Whitman\nMegan Holston-Alexander\nMegan Kristalyn\nMehdi Hasan\nMehul Mehta\nMel Williams\nMelanie Galang\nMelissa Liao\nMelissa Minor\nMelissa Wasser\nMellody Hobson\nMelody Latronico\nMeredith Donahue\nMia Gonzalez\nMia Mandich\nMicah Johnson\nMichael Beckerman\nMichael Blau\nMichael Brandt\nMichael Chan\nMichael Copeland\nMichael Dearing\nMichael Dell\nMichael Franklin\nMichael Garcia\nMichael J. Casey\nMichael J. Freedman\nMichael Killam\nMichael King\nMichael Lee\nMichael Leiter\nMichael Morell\nMichael Ostrovsky\nMichael Ovitz\nMichael Paulus\nMichael Raynor\nMichael Reed\nMichael Snyder\nMichael Temkin\nMichael Wee\nMichael Zhu\nMichel Del Buono\nMichel Feaster\nMichèle Flournoy\nMichele Griffin\nMichele Korver\nMichele Law\nMichelle Ervin\nMichelle Kelso\nMichelle Kung\nMichelle Mundy\nMichelle Shin\nMichelle Ufford\nMichelle Volz\nMichelle Wilson\nMichelle Winn\nMichelle You\nMike Curtis\nMike Haydon\nMike Hearn\nMike Jones\nMike Kasperzak\nMike Kelly\nMike King\nMike Lempres\nMike Manning\nMike Maples jr\nMike Masnick\nMike Matchett\nMike Paulus\nMike Sandwick\nMikeal Rogers\nMikey Dickerson\nMiles Jennings\nMilijana Curic\nMiller Whitehouse-Levine\nMinerva Munoz\nMinnie Ingersoll\nMinsun Pak\nMintu Turakhia\nMiranda Christ\nMo Shaikh\nMohammad Akbarpour\nMohsen Malayeri\nMolly Grace\nMonique McCambridge\nMorgan Beller\nMorgan Bender\nMurat Pak\nMuriel Bowser\nMurray Shanahan\nMy Pham\nNadia Asparouhova\nNadia Eghbal\nNaftali Harris\nNaithan Jones\nNanjira Sambuli\nNaomi Metzger\nNashid Braswell\nNassim Eddequiouaq\nNat Barling\nNatacha Crooks\nNatalia Carrera\nNatalie Bucher\nNatalie Taumoepeau\nNate Chang\nNate Lau\nNathalie Balaban\nNathan McCauley\nNathan Yoon\nNathaniel Gleicher\nNathaniel Popper\nNav Singh\nNazanin Daneshvar\nNeel Maitra\nNeha Narula\nNelson Perla-Ward\nNeveen Bader\nNicholas Christakis\nNicholas Pacilio\nNick Babaian\nNick McKeown\nNick Quah\nNick Tomaino\nNicki Locker\nNicole Conner\nNicole Forsgren\nNicole Irvin\nNicole Neuman\nNicole Stanners\nNiels Provos\nNigel Robinson\nNikhil Krishnan\nNina Suthers\nNir Eyal\nNitasha Tiku\nNitin Natarajan\nNitya Subramanian\nNkiru Balonwu\nNoah Citron\nNoah Feldman\nNoah Levine\nNoah Smith\nNoam Nisan\nNoemi Glaeser\nO’Shea Jackson Jr.\nOlaf Carlson-Wee\nOleg Rogynskyy\nOliver Hsu\nOlivia Moore\nOlivia Webb\nOmri Weinstein\nOoshma Garg\nOprah Winfrey\nOrion Hindawi\nOscar Menjivar\nP.J. Hasleton\nPablo Montagnes\nPacky McCormick\nPak\nPalmer Luckey\nPamela Anderson\nPamon Forouhar\nParag Khanna\nParijat Talkad\nParker Brown\nParker Conrad\nPatrice Peck\nPatrick Byrne\nPatrick Collison\nPatrick Conway\nPatrick McCorry\nPatrick McHenry\nPatrick O’Grady\nPatrick Rivera\nPatrick Sutton\nPaul Cafiero\nPaul Daugherty\nPaul Davison\nPaul Krugman\nPaul Vigna\nPaula Long\nPenny Pritzker\nPerri Chilton\nPete Buttigieg\nPeter Blackwood\nPeter Buisseret\nPeter Chan\nPeter Donnelly\nPeter Johnson\nPeter Lauten\nPeter Leeson\nPeter Levine\nPeter Ludwig\nPeter Rubin\nPeter Thiel\nPeter Wang\nPetra Garrett\nPhil Daian\nPhil Hathaway\nPhil Wong\nPhong Nguyen\nPorter Smith\npplpleasr\nPranav Garimidi\nPrasad Akella\nPrat Moghe\nPreethi Kasireddy\npunk6529\nPurnima Padmanabhan\nPyrs Carvolth\nQasar Younis\nQuang Dao\nQuinten Burgunder\nQuintus Kilbourn\nRachael Horwitz\nRachel Goslins\nRachel Jenkins\nRachel Kalmar\nRachel McIntyre\nRachel Steiner\nRahul Iyer\nRahul Vohra\nRajeev Singh\nRajeev Venkayya\nRam Palaniappan\nRamana Jonnala\nRati Gelashvili\nRaul Vazquez\nRavi Parimi\nRay Dalio\nRaymond Carreira\nRebecca Lewis\nRebecca Rettig\nReed Hastings\nRefik Anadol\nRegina Benjamin\nRenato Valdés Olmos\nReshma Saujani\nReshma Sohoni\nRex Salisbury\nRich Ezekiel\nRichard Green\nRichard Menger\nRichard Rosenblatt\nRick Young\nRidhima Ahuja\nRiyaz Faizullabhoy\nRob Goodman\nRob McElhenney\nRob Pardo\nRob Rhinehart\nRobbie Petersen\nRobbie Peterson\nRobert Alexander\nRobert Cottrell\nRobert Hackett\nRobert Kolker\nRobert Leshner\nRobert McNeely\nRobert Moreno\nRobert Siegel\nRobert Stromberg\nRobert Weber\nRobin Casey\nRobin Guo\nRobin Weisman\nRod Johnson\nRodrigo Ibarra Lopez\nRodrigo Pacheco\nRoger Dickey\nRoger Wattenhofer\nRoham Gharegozlou\nRohini Mukand\nRohit Bansal\nRoman Mars\nRoman Stanek\nRon Gill\nRon Lavi\nRon Rothblum\nRonald Evans\nRonnie Harris\nRosa Davila\nRosalind Rattan\nRose Legarda\nRoss Andersen\nRoss Shuel\nRostin Behnam\nRuben Gallego\nRuben Smith\nRuss Altman\nRuss Heddleston\nRuss Roberts\nRussell Davies\nRyan Allen\nRyan Caldbeck\nRyan Conde\nRyan Holloway\nRyan Hoover\nRyan McEntush\nRyan Petersen\nRyan Prescott\nRyan Sandler\nRyan Spoon\nRyan Tseng\nRyan Walsh\nRyan Ward\nRyan Wyatt\nSaar Tochner\nSachin Jain\nSafi Bahcall\nSagar Dhawan\nSaku Panditharatne\nSalem Vance\nSam Blackshear\nSam Broner\nSam Gerstenzang\nSam Ragsdale\nSam Thompson\nSam Williams\nSam Yam\nSamantha Gelt\nSamantha Langford\nSamantha Ludwig\nSamson Wu\nSamuel Arbesman\nSamuel Hammond\nSandra Samayoa\nSandy Jen\nSankaet Pathak\nSantiago Rodriguez\nSara Boesen\nSarah Fazal\nSarah Hamburg\nSarah Lumbard\nSarah Mascardo\nSarah Meiklejohn\nSarah Porter\nSarah Rebello\nSarah Wang\nSasha Stiles\nSatish Talluri\nSaurabh Ladha\nSavannah Cherry\nScott Clark\nScott Duke Kominers\nScott Gottlieb\nScott Hassan\nScott Kupor\nScott Rubin\nScott Shenker\nScott Tyler\nScott Walker\nScott Weiss\nSean Duffy\nSean Neville\nSebastian Oddo\nSeema Amble\nSeemay Chou\nSep Kamvar\nSergiu Pasca\nSeth Lobree\nSeth Sivak\nSeth Sternberg\nShai Bernstein\nShai Kopeld\nShaka Senghor\nShakil Khan\nShan Sinha\nShana Fisher\nShane Mac\nShane Parrish\nShangda Xu\nShannon (Stubo) Brayton\nShannon Barbour\nShannon Kelly\nShannon Schiltz\nShannon Snow\nShari Doherty\nSharon Chang\nShawn Conway\nSheela Krothapalli\nShellye Archambeau\nSherie James\nSherriAnn Cole\nShishir Mehrotra\nShonda Rhimes\nSid Gorham\nSigne Pierce\nSimon Denny\nSiqi Chen\nSonal Chokshi\nSophie Song\nSoubhik Deb\nSpencer Dinwiddie\nSpencer Howard\nSpencer Rascoff\nSreeram Kannan\nSreevidya Kasturil\nSri Kosuri\nSriram Krishnan\nSrivatsan Sridhar\nStacey Cunningham\nStacey Merrick\nStacia Murray\nStacy Brown-Philpot\nStacy D'Amico\nStacy Warner\nStefan McDonough\nSten Tamkivi\nStephane Bancel\nStephanie Anyanwu\nStephanie Cohen\nStephanie Doppelt\nStephanie Smith\nStephanie Watkins\nStephanie Zinn\nStephen Armanios\nStephen Wink\nStephenie Zhang\nSteve Buress\nSteve Cadigan\nSteve Cheney\nSteve Harvey\nSteve Kaczynski\nSteve McDermid\nSteve Smith\nSteve Zhao\nSteven Adair\nSteven Ebert\nSteven Johnson\nSteven Levy\nSteven Sinofsky\nStewart Butterfield\nStina Ehrensvärd\nStuart Luman\nStuart Russell\nSudip Chakrabarti\nSue Hager\nSuhail Doshi\nSukhinder Singh Cassidy\nSumeet Singh\nSumit Shah\nSungMo Park\nSunil Chokshi\nSurya Ganguli\nSusan B. Wilde\nSusan Mernit\nSusan Rice\nSusannah Fox\nSydney Paul\nTaavet Hinrikus\nTaggart Matthiesen\nTamzen Brewis\nTana Billingsley\nTarek Mansour\nTarun Chitra\nTauri Laws Phillips\nTawny Holguin\nTaylor McFadden\nTed Not Lasso\nTed Sarandos\nTed Ullyot\nTerell Sterling\nTerence Carroll\nTeresa Carlson\nTerry Angelos\nTerry Brown\nThan Nguyen\nThanh Nguyen\nThe 2015 Academic Roundtable Sessions\nThe TxO team\nTheresa DeMichele\nTheresa Dilley\nTheresa Fisher\nTheresa Walz\nTheresia Gouw\nThibaut Scholasch\nThomas Gjerde\nThomas Juenger\nThomas Long\nThomas Rando\nTiffany Vo\nTiffany Zhong\nTim Beiko\nTim O'Reilly\nTim Roughgarden\nTim Schafer\nTim Sullivan\nTimmu Tõke\nTina Anderson\nTina Bhatnagar\nTina Ferguson\nTina Wie\ntinawie\nTing Ni\nTobi Lütke\nTodd Cranney\nTodd Lutwak\nTodd McKinnon\nTodd Park\nTodd Young\nTolga Dizdarer\nTom Butta\nTom Coates\nTom Davenport\nTom Ellis\nTom Hammer\nTom Hofmann\nTom Lehman\nTom Mitchell\nTom Preston-Werner\nTom Rikert\nTom Standage\nTomicah Tillemann\nTony Blair\nTony Blinken\nTori Landrum\nTracy Chou\nTracy Young\nTren Griffin\nTrent Mayol\nTrevor Bedford\nTristan Handy\nTristan Walker\nTroy Kirwin\nTugce Erten\nTurner Novak\nTushar Garg\nTyler Cowen\nTyler Wilson\nTyson Clark\nUma Valeti\nUsman Azam\nUzi Dutta\nValentina Marzorati\nValeria Nikolaenko\nValerie Arboleda\nVan Jones\nVan Le-Gray\nVanessa Kropf\nVas Narasimhan\nVaughn Ferguson\nVenkat Mocherla\nVicente De Baca\nVickie Casillas-Smith\nVictor Liang\nVictor Shoup\nVictoria Butcher\nVijay Balasubramaniyan\nVijay Kedar\nVijay Pande\nVineeta Agarwala\nVinod Khosla\nVirginia Postrel\nVishal Amin\nVitalik Buterin\nVivian Brooks\nVoices Onchain\nW. Brian Arthur\nWahab Owolabi\nWei Luo\nWendy Drpic\nWerner Gerola\nWes Taylor\nWhitney Owens\nWill Brown\nWill Wong\nWillem Mulder\nWilliam Gifford\nWilliam Mougayar\nWing Cheng\nXian Zhang\nXiang-Dong Fu\nXingchen Zhou\nYannai A. Gonczarowski\nYehuda Lindell\nYevgeniy Dodis\nYinuo Zhang\nYogi Roth\nYohei Ishii\nYoko Li\nYoni Levy\nYoram Novick\nYuichi Kurosawa\nYujin Chung\nYun Fan\nYung Yung Sheung\nYuval Efron\nYuval Harari\nZac Bookman\nZach Abrams\nZach Cohen\nZach Dicker\nZach Haigney\nZachary Chen\nZachary Gray\nZack Weiner\nZahabiya Gabaji\nZak Doric\nZal Bilimoria\nZane Lackey\nZeta Avarikioti\nZeya Yang\nZooko Wilcox\nZoran Basich\n\nclear all Lioba Heimbach\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n07.15.25 / Pranav Garimidi, Joseph Bonneau and Lioba Heimbach\nOn the limits of encrypted mempools\nAn encrypted mempool is not a universal solution to MEV. This post outlines the difficulties and explores how encrypted mempools might be designed.\n\nresearch\nDeFi\nmev\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":6834,"crawled_at":1791193677916}
+{"id":10273,"url":"https://docs.near.org/smart-contracts/anatomy/anatomy","domain":"docs.near.org","chapter":"layer1_layer2","title":"Basic Anatomy - NEAR Docs","text":"Let’s illustrate the basic anatomy of a simple “Hello World” contract. The code on this page comes from our Hello NEAR repository on GitHub.\n​\n\nImporting the SDK\nAll contracts will import the NEAR SDK, enabling them to access the execution environment, call other contracts, transfer tokens, and much more.You can also use third-party libraries, though some might not work due to the limitations of the contract runtime.\n​\n\nContract’s Main Structure\nThe contract is described through a structure:\nThe attributes define which data the contract stores\n\nThe functions define its public (and private) interface\n\n​\n\nContract Struct Macro\nNote that the contract’s struct definition and the implementation are decorated with macrosThe #[near(contract_state)] macro tells the SDK that this structure defines the contract’s state, so it knows:\nWhat to fetch from storage when the contract is loaded\n\nWhat to store when the contract is done executing\n\nThe #[near] macro tells the SDK which functions are exposed to the outside world.\nOnly one struct can be decorated with the #[near(contract_state)] macro.\n\nInteraction with other macros\n\nWhen near is built for the wasm32 target, it generates the external NEAR contract bindings. To achieve this it is actually generating another function with the signature pub extern \"C\" fn function_name() that first deserializes the contract struct from NEAR storage and then calls the contract.function_name(parameter1, parameter2, ...).If you have annotated your function with any attribute-like macros, these are then executed twice. Specifically if the attribute like macro makes any modification to the function signature, or inserts any code that depends on the contract struct (in the form of &self, &mut self, or self) this will fail in the second invocation, because the externally exposed function does not have any concept of this struct.It is possible to detect this by checking which build target you are building for and limit the execution of the macro to operate only on the first pass.\n\n​\n\nStorage (State)\nWe call the data stored in the contract the contract’s state.In our Hello World example, the contract stores a single string (greeting), and the state starts initialized with the default value \"Hello\".\nWe will cover more about the contract’s state in the state section.\n\n​\n\nRead Only Functions\nContract’s functions can be read-only, meaning they don’t modify the state. Calling them is free for everyone, and does not require to have a NEAR account.\nWe will cover more about function types in the functions section.\n\n​\n\nState Mutating Functions\nFunctions that modify the state or call other contracts are considered state mutating functions. It is necessary to have a NEAR account to call them, as they require a transaction to be sent to the network.\nWe will cover more about function types in the functions section.\n\nhello-near\n\nuse near_sdk::{log, near};\n\n// Define the contract structure\n#[near(contract_state)]\npub struct Contract {\ngreeting: String,\n}\n\n// Define the default, which automatically initializes the contract\nimpl Default for Contract {\nfn default() -> Self {\nSelf {\ngreeting: \"Hello\".to_string(),\n}\n}\n}\n\n// Implement the contract structure\n#[near]\nimpl Contract {\n// Public method - returns the greeting saved, defaulting to DEFAULT_GREETING\npub fn get_greeting(&self) -> String {\nself.greeting.clone()\n}\n\n// Public method - accepts a greeting, such as \"howdy\", and records it\npub fn set_greeting(&mut self, greeting: String) {\nlog!(\"Saving greeting: {}\", greeting);\nself.greeting = greeting;\n}\n}\n\nSee on GitHub\n\nWas this page helpful?","tokens":902,"crawled_at":1791193678826}
+{"id":10274,"url":"https://stack.olas.network/open-autonomy/advanced_reference/commands/autonomy_deploy","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"autonomy deploy - Olas Stack Developer Documentation","text":"autonomy deploy\n\nBuild or run AI agent deployments.\n\nThis command group consists of a number of functionalities for building AI agent deployments, run locally stored AI agent deployments, and run AI agent deployments defined in the on-chain protocol. See the appropriate subcommands for more information.\n\nOptions\n\n--env-file FILE\nFile containing environment variable mappings\n\nExamples\n\nIf you have an .env file in the working directory, autonomy deploy will load the .env file automatically. If the file is not present in the working directory you can provide the path to the file using --env-file flag\n\nautonomy deploy --env-file <path_to_dotenv> COMMAND [ARGS]\n\nFor loading the environment variables you can use a json file as well. While using a json file you can either use json serialized strings like\n\nenv.json{\n\"ALL_PARTICIPANTS\": \"[\\\"0x0000000000000000000000000000000000000000\\\"]\"\n}\n\nOr the json objects\n\nenv.json{\n\"ALL_PARTICIPANTS\": [\"0x0000000000000000000000000000000000000000\"]\n}\n\nThe framework will handle both of these cases automatically.\n\nautonomy deploy --env-file <path_to_json> COMMAND [ARGS]\n\nautonomy deploy build\n\nBuild an AI agent deployment.\n\nThis command must be executed within a service folder. That is, a folder containing the AI agent configuration file (service.yaml). The deployment will be created in the subfolder ./abci_build_*.\n\nUsage\n\nautonomy deploy build [OPTIONS] [KEYS_FILE]\n\nOptions\n\n--o PATH\nPath to output directory.\n--n INTEGER\nNumber of agent instances.\n--docker\nUse docker as a backend.\n--kubernetes\nUse kubernetes as a backend.\n--dev\nCreate development environment.\n--log-level [INFO|DEBUG|WARNING|ERROR|CRITICAL]\nLogging level for runtime.\n--packages-dir PATH\nPath to packages directory (Use with dev mode).\n--open-aea-dir PATH\nPath to open-aea repo (Use with dev mode).\n--aev\nDeprecated. Applying environment variables when loading service config is now the default; this flag will be removed in v1.0.0.\n--use-hardhat\nInclude a hardhat node in the deployment setup.\n--use-acn\nInclude an ACN node in the deployment setup.\n-ltm, --local-tm-setup\nUse local tendermint chain setup.\n--image-version TEXT\nDefine runtime image version.\n--agent-cpu-request FLOAT\nSet agent instance CPU usage request.\n--agent-memory-request INTEGER\nSet agent instance memory usage request.\n--agent-cpu-limit FLOAT\nSet agent instance CPU usage limit.\n--agent-memory-limit INTEGER\nSet agent instance memory usage limit.\n\n--number-of-services INTEGER\nNumber of AI agents (i.e., separate deployment folders) to build. Default is 1.\n\n--remote\nTo use a remote registry.\n--local\nTo use a local registry.\n-p\nAsk for password interactively.\n--help\nShow the help message and exit.\n\nExamples\n\nautonomy deploy build keys.json -ltm\n\nBuilds an AI agent deployment using the keys stored in the file keys.json and applying environment variables to the AI agent configuration file. The deployment will be generated by default for as many agents as keys are stored in keys.json. By default, the command searches for the file keys.json, if no file name is provided.\n\nYou can build multiple AI agent deployments at once using the --number-of-services parameter. Each AI agent will be created in its own abci_build_* folder:\n\nautonomy deploy build --number-of-services 2 keys.json\n\nNote: Use --n to set the number of agent instances per AI agent, and use --number-of-services to build multiple separate AI agents at once.\n\nIf you are manually defining keys.json make sure to include ledger property for a key object. This will be used when writing key files to the deployment environment. If you don't specify the property ethereum will be used as default ledger identifier, so if you're running an AI agent against a different ledger (eg. solana) you'll have to specify this property manually like this\n\n[\n{\n\"address\": \"Solanaaddress\",\n\"private_key\": \"Solanaprivatekey\",\n\"ledger\": \"solana\"\n}\n]\n\nIf the keys are generated using autonomy generate-key command the ledger property will be included automatically.\n\nPrivate key security\n\nWhen building deployments, you can use password protected privates keys (eg. generated using autonomy generate-key LEDGER --password PASSWORD) to avoid exposing them.\n\nDocker Compose\n\nIn a docker-compose deployment you can just export OPEN_AUTONOMY_PRIVATE_KEY_PASSWORD environment variable before running the deployment like\n\nexport OPEN_AUTONOMY_PRIVATE_KEY_PASSWORD=PASSWORD\nautonomy deploy run --build-dir PATH_TO_BUILD_DIR\n\nor\n\nexport OPEN_AUTONOMY_PRIVATE_KEY_PASSWORD=PASSWORD\ndocker-compose -f PATH_TO_BUILD_DIR/docker-compose.yaml up\n\nKubernetes\n\nIn a kubernetes deployment, you'll have to export the OPEN_AUTONOMY_PRIVATE_KEY_PASSWORD variable when building the deployment, not when running.\n\nexport OPEN_AUTONOMY_PRIVATE_KEY_PASSWORD=PASSWORD\nautonomy deploy build (...)\n\nCustomize resources\n\nYou can customize the resource values for the agent instance nodes using --agent-cpu-limit, --agent-memory-limit, --agent-cpu-request and --agent-memory-request flags or using AUTONOMY_AGENT_MEMORY_LIMIT, AUTONOMY_AGENT_CPU_LIMIT, AUTONOMY_AGENT_MEMORY_REQUEST and AUTONOMY_AGENT_CPU_REQUEST environment variables.\n\nautonomy deploy build --agent-cpu-limit 1.0 --agent-memory-limit 2048 --agent-memory-request 1024\n\nwill produce agent instance nodes with following resource constrains\n\nxyz_abci_0:\nmem_reservation: 1024M\nmem_limit: 2048M\ncpus: 1.0\n\non docker-compose deployment and\n\nresources:\nlimits:\ncpu: '1.0'\nmemory: 2048Mi\nrequests:\ncpu: '0.5'\nmemory: 1024Mi\n\non kubernetes deployment.\n\nautonomy deploy run\n\nRun an AI agent deployment locally stored.\n\nThis command is a wrapper around docker-compose up to run the AI agent deployment. To execute this command you need to be located within the deployment environment subfolder (./abci_build_*), or specify it with the option --build-dir.\n\nUsage\n\nautonomy deploy run [OPTIONS]\n\nOptions\n\n--build-dir PATH\nPath where the deployment is located.\n--no-recreate\nIf containers already exist, don not recreate them.\n--remove-orphans\nRemove containers for AI agents not defined in the Compose file.\n--detach\nRun AI agent in the background.\n--help\nShow the help message and exit.\n\nExamples\n\nautonomy deploy run --build-dir ./abci_build_hAsH\n\nRuns the AI agent deployment stored locally in the directory ./abci_build_hAsH.\n\nTo provide password for the private keys\n\nexport OPEN_AUTONOMY_PRIVATE_KEY_PASSWORD=PASSWORD\nautonomy deploy run --build-dir ./abci_build_hAsH\n\nautonomy deploy from-token\n\nDeprecation Warning\n\nThis command will be deprecated in the future. Please use autonomy fetch instead.\n\nRun an AI agent deployment minted on-chain protocol.\n\nThis command allows to deploy AI agents directly without having the need to explicitly fetch them locally (also known as \"one-click deployment\"). The command requires the TOKEN_ID which can be checked in the Olas Protocol web app. See the mint an AI agent on-chain guide for more information.\n\nTo understand how to use various chain profiles refer to Chain Selection section on the autonomy mint command documentation.\n\nUsage\n\nautonomy deploy from-token [OPTIONS] TOKEN_ID KEYS_FILE\n\nOptions\n\n--n INTEGER\nNumber of agent instances to include in the build.\n--skip-image\nSkip building images.\n--aev\nDeprecated. Applying environment variables when loading service config is now the default; this flag will be removed in v1.0.0.\n--docker\nUse docker as a backend.\n--agent-cpu-request FLOAT\nSet agent instance CPU usage request.\n--agent-memory-request INTEGER\nSet agent instance memory usage request.\n--agent-cpu-limit FLOAT\nSet agent instance CPU usage limit.\n--agent-memory-limit INTEGER\nSet agent instance memory usage limit.\n--kubernetes\nUse kubernetes as a backend.\n--no-deploy\nIf set to true, the deployment won't run automatically\n--use-celo\nTo use celo chain profile to interact with the contracts\n--use-base\nTo use base chain profile to interact with the contracts\n--use-optimism\nTo use optimism chain profile to interact with the contracts\n--use-arbitrum-one\nTo use arbitrum-one chain profile to interact with the contracts\n--use-gnosis\nTo use gnosis chain profile to interact with the contracts\n--use-polygon\nTo use polygon chain profile to interact with the contracts\n--use-ethereum\nTo use ethereum chain profile to interact with the contracts\n--use-custom-chain\nTo use custom-chain chain profile to interact with the contracts\n--use-local\nTo use local chain profile to interact with the contracts\n--help\nShow the help message and exit.\n\nExamples\n\nautonomy deploy from-token --use-ethereum 2 keys.json\n\nRuns the AI agent deployment registered with TOKEN_ID=2 on the Ethereum mainnet. The deployment will be run for as many agent instances as keys are defined in the keys.json file.\n\nautonomy deploy stop\n\nStop a deployment running in background, if you use --detach flag on autonomy deploy run or autonomy deploy from-token the AI agent will run in background. You can stop this AI agent using autonomy deploy stop command.\n\nUsage\n\nautonomy deploy stop --build-dir BUILD_DIR\n\nOptions:\n\n--build-dir PATH\nPath to the deployment build directory.\n--help\nShow this message and exit.","tokens":2280,"crawled_at":1791193690434}
+{"id":10275,"url":"https://a16zcrypto.com/posts/article/limits-encrypted-mempools","domain":"a16zcrypto.com","chapter":"research","title":"On the limits of encrypted mempools - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nOn the limits of encrypted mempools\nPranav Garimidi, Joseph Bonneau, and Lioba Heimbach\n07.15.25\n\nTABLE OF CONTENTS\nHow encrypted mempools work How encrypted mempools work\nTechnical challenges for encrypted mempools\nEconomic challenges for encrypted mempools\nOther efficiency challenges\nTags\nDeFi\nmev\nresearch\ntech trends\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nThe value that can be extracted by including, excluding, or reordering transactions in a block is known as “maximal extractable value, or MEV. MEV is common on most blockchains, and has been a topic of widespread interest and discussion in the community.\n\nNote: This blog post assumes basic familiarity with MEV. Some readers might wish to start by reading our MEV explainer.\n\nMany researchers, observing the MEV situation, have asked an obvious question: Can cryptography solve the problem? One approach is an encrypted mempool, where users broadcast encrypted transactions that are only revealed after they are sequenced. Hence, a consensus protocol would have to commit to a transaction ordering blindly, seemingly preventing the ability to take advantage of MEV opportunities during the ordering process.\n\nUnfortunately, for both practical and theoretical reasons, we don’t see encrypted mempools providing a universal solution to MEV. We outline the difficulties and explore how encrypted mempools might be designed.\n\nHow encrypted mempools work\n\nThere have been many proposals for encrypted mempools, but the general framework for encrypted mempools is as follows:\n\nUsers broadcast their encrypted transactions.\n\nThe encrypted transactions are committed on-chain (in some proposals after being provably shuffled randomly)\n\nAfter the committing block is finalized, the transactions are decrypted.\n\nFinally, the transactions are executed.\n\nNote that step 3 (transaction decryption) poses an important challenge: Who decrypts, and what if the decryption doesn’t happen? A naive solution would be to say that users themselves decrypt their transactions (in this case one wouldn’t even need encryption, but could simply hide commitments). However, this approach is vulnerable: An attacker can perform speculative MEV.\n\nWith speculative MEV, an attacker tries to guess that a certain encrypted transaction yields some MEV. They encrypt their own transactions which hopefully will appear in an opportune place (e.g., right before or after a target transaction). If the transaction is sequenced in the hoped-for order, the attacker decrypts and their transaction extracts the MEV. If not, they decline to decrypt and their transaction is not included in the final chain.\n\nPerhaps users could face some penalty for failing to decrypt, but this is tricky to implement. The penalty would need to be the same for all encrypted transactions (since they are encrypted and therefore indistinguishable), but also large enough to discourage speculative MEV even against high-value targets. This would require tying up lots of capital, which should be anonymous (to avoid leaking information about which transactions are posted by which users). And it would end up costing honest users in the case of a bug or network failure which prevents their legitimate attempt to decrypt.\n\nHence, most proposals suggest that transactions be encrypted in such a way that decryption is guaranteed to be possible at some point in the future — even if the posting user goes offline or doesn’t cooperate. This can be achieved in several ways:\n\nTEEs: Users can encrypt their transactions to a key held by a Trusted Execution Environment (TEE) enclave. In some simple versions, the TEE is only used to decrypt transactions after a certain time deadline (which requires some notion of time within the TEE). More advanced approaches use the TEE to decrypt transactions and build the block, ordering them based on some criteria like arrival times or fees. An advantage of TEEs compared to other encrypted mempool approaches is their ability to operate on plaintext transactions, thereby reducing onchain spam by filtering out transactions that would revert. However, this method requires trust in the hardware.\n\nSecret-sharing and threshold encryption: With this approach, users encrypt transactions to a key that is shared by some committee, typically a subset of validators. Some threshold (e.g., two-thirds of the committee) is required for decryption.\n\nThe simplest approach uses a new shared decryption key in each round (e.g., each block or epoch on Ethereum), which the committee re-constructs and publishes after transactions are ordered in a finalized block. This approach can use simple secret sharing. The downside is that this reveals all transactions from the mempool, even those that were not included in a block. This approach also requires a new distributed key generation (DKG) in each round.\n\nA better approach for privacy is to decrypt only the transactions that were actually included. This can be realized using threshold decryption. This approach also enables amortizing the cost of the DKG protocols but using the same key for multiple blocks with the committee threshold-decrypting transactions after they are ordered in a finalized block. A challenge is that the committee has to do a lot more work. Naively, the committee’s work is linear in the number of transactions to decrypt, although recent work suggests batch threshold decryption which can improve on this significantly.\n\nWith threshold decryption, trust shifts from a piece of hardware to a committee. The claim is that, since most protocols already make an honest majority assumption about validators for the consensus protocol, we can make a similar assumption that a majority of validators are honest and won’t decrypt transactions early. A note of caution is in order, however: These are not the same trust assumption. Consensus failures like forking the chain are publicly visible (called a weak trust assumption), whereas a malicious committee privately decrypting transactions early will generate no public evidence and hence such an attack cannot be detected or slashed (a strong trust assumption). Thus while, from the outside, the security assumptions for consensus and an encryption committee might look the same, practical considerations make the assumption that a committee won’t collude more tenuous.\n\nTime-lock and delay encryption: An alternative to threshold encryption comes in the form of delay encryption. Users encrypt their transactions to a public key whose secret key is hidden within a time-locked puzzle. A time-locked puzzle is a cryptographic puzzle that encapsulates a secret, which can only be revealed after some predetermined amount of time has elapsed – more specifically, the puzzle can be decrypted by repeatedly performing some non-parallelizable computation. In this case, this puzzle can be opened by anybody to recover the key and decrypt transactions, but only after a slow (inherently sequential) computation which is designed to take long enough that transactions cannot be decrypted before they have been finalized. The strongest version of this primitive uses delay encryption to publicly generate such a puzzle. It can also be approximated by using a trusted committee to compute the puzzle via time-lock encryption, although at that point the advantages over threshold encryption are questionable.\n\nWhether by delay encryption or computation by a trusted committee, there are a number of practical challenges. First, it is more difficult to ensure precise timing of decryption, since the delay is computational in nature. Second, these schemes rely on some entity running sophisticated hardware to solve the puzzles efficiently. While anybody can fulfill this role, it is unclear how to incentivize this party. Finally, in these designs, all broadcast transactions will be decrypted, including those which were never finalized in a block. Threshold-based (or witness encryption) solutions could potentially only decrypt transactions that are successfully included.\n\nWitness encryption. Finally, the most advanced cryptographic approach uses a tool called witness encryption. Theoretically, witness encryption allows encrypting information to anybody who knows the witness to a specific NP relation. For example, one could encrypt such that anybody with the solution to a certain Sudoku puzzle, or anybody with a hash preimage of a certain value, can decrypt.\n\nSNARKs are also possible for any NP relation. One can think of witness encryption as encrypting data to anybody who can compute a SNARK proving a desired condition. For encrypted mempools, one example for such a condition would be that transactions can only be decrypted when a block has been finalized.\n\nThis is a very powerful theoretical primitive. In fact, it is a generalization for which committee-based approaches and delay-based approaches are specific cases. Unfortunately, we don’t have any practical constructions of witness-based encryption. Furthermore, even if we did, it is not clear how it is an improvement over a committee-based approach for proof-of-stake chains. Even if witness encryption is set up so that transactions can only be decrypted once they are ordered in a finalized block, a malicious committee can still privately simulate the consensus protocol such that the transaction is finalized, and then use this private chain as a witness to decrypt transactions. At that point, using threshold decryption by the same committee provides equivalent security and is much simpler.\n\nWitness encryption offers a more decisive edge in proof-of-work consensus protocols, since even a fully malicious committee can’t privately mine several new blocks on top of the current head to simulate finality.\n\nTechnical challenges for encrypted mempools\n\nSeveral important practical challenges limit encrypted mempools’ ability to prevent MEV. In general, keeping information confidential is hard. Interestingly, encryption is a tool rarely used in the web3 space. But we have decades of practical experience that showcase the challenges to deploying encryption on the web (TLS/HTTPS) and for private communication (from PGP to modern encrypted messaging platforms like Signal or Whatsapp). While encryption is a tool to preserve confidentiality, it does not guarantee it.\n\nFirst, there might be parties with direct access to the plaintext of a user’s transaction. In typical cases, users may not encrypt their own transaction but outsource this to their wallet provider. Consequently, the wallet provider has access to the plaintext transaction and could use or sell this information to extract MEV. Encryption is never stronger than the set of parties with access to the key.\n\nBeyond this, the biggest problem is metadata, that is, data surrounding the encrypted payload (transaction), which is not encrypted. Searchers can use this metadata to guess the intent of a transaction and then attempt speculative MEV. Remember, searchers don’t have to fully understand a transaction, or be right every time. It’s enough if they know, for example, that with some reasonable probability a transaction represents a buy order from a specific DEX.\n\nWe can consider several types of metadata, some of which are classic challenges with encryption and some of which are unique for encrypted mempools.\n\nTransaction size: Encryption by itself does not hide the size of the encrypted plaintext. (There is, notoriously, a specific exception made in the formal definitions of semantic security to exclude hiding the size of the plaintext being encrypted.) This is a classic attack vector on encrypted communication. (In a famous example, even with encryption an eavesdropper can determine what video is being streamed over Netflix in real-time from the size of each packet in the video stream.) In the encrypted mempool context, certain transaction types might have a specific size which leaks information.\n\nBroadcast time: Encryption also doesn’t hide timing information (another classic attack vector). In the web3 context, certain senders — for example, in structured selling — might perform transactions at regular intervals. Transaction timing might also be correlated with other information, such as activity in external exchanges or news events. A more subtle way to exploit timing information is CEX/DEX arbitrage. A sequencer can benefit from inserting a transaction created as late as possible, taking advantage of more recent information about CEX prices. The same sequencer could exclude any other transactions (even if encrypted) broadcast after a certain point in time, ensuring that its transaction alone has the advantage of the most up-to-date price information.\n\nOriginating IP address: Searchers might infer a transaction sender’s identity by monitoring the peer-to-peer network and observing the originating IP address. This problem was actually identified over ten years ago in the early days of Bitcoin. This can be useful to searchers if specific senders have specific patterns — for example, knowing the sender might enable linking an encrypted transaction to prior transactions which have already been decrypted.\n\nTransaction sender and fee/gas information: Finally, transaction fees represent a type of metadata specific to encrypted mempools. In Ethereum, transactions classically include an (onchain) sender address, which is used to pay fees, as well as a maximum gas budget and a fee per unit of gas that the sender is willing to pay. The sender address, like the originating network address, can be used to link transactions together and to real-world entities. The gas budget can be used to estimate what the transaction intends to do. For example, interacting with a specific DEX might require a specific amount of gas which is identifiable.\n\nSophisticated searchers might use any combination of the above metadata types to predict a transaction’s contents.\n\nAll of this information could potentially be hidden, but at a performance and complexity cost. For example, padding transactions up to a standard limit hides transaction size, but it wastes bandwidth and space onchain. Adding delays before sending messages hides transaction time, but harms latency. Submitting transactions over an anonymity network like Tor could hide the sender’s IP address, but this has its own challenges.\n\nThe most difficult metadata to hide is transaction fee data. Encrypting this data creates a number of challenges for the builder. The first problem is spam. If transaction fee payment data is encrypted, then anybody can broadcast malformed encrypted transactions that will be ordered but have no ability to pay fees. Hence, after decryption they will not be able to execute but no party can be penalized. This could possibly be addressed with SNARKs that prove that a transaction is well-formed and funded, but this would greatly increase overhead.\n\nThe second problem is efficient block building and fee auctions. Builders use fees to build the most profitable block and establish the current market price for onchain resources. Encrypting this data disrupts this process. This could be addressed by establishing a flat fee in each block, but this is economically inefficient and might encourage secondary markets for transaction inclusion that would undermine the point of having an encrypted mempool. Conducting a fee auction using secure multi-party computation or trusted hardware is possible, but these are both expensive steps.\n\nFinally, secure, encrypted mempools impose overhead on the system in a number of ways. Encryption adds latency, computational and bandwidth overhead to the chain. How to combine it with support for sharding or parallel execution — which are important future goals — is far from obvious. It might add additional points of failure for liveness (e.g., the decryption committee for threshold solutions or delay function solver). And it certainly adds to design and implementation complexity.\n\nMany of the problems of encrypted mempools are shared by blockchains that themselves aim to ensure transaction privacy (e.g., Zcash, Monero). If there is a silver lining, it is that solving all of the challenges of encryption for MEV abatement would as a side effect clear the way for transaction privacy.\n\nEconomic challenges for encrypted mempools\n\nFinally, encrypted mempools face economic challenges. Unlike the technical challenges, which could potentially be mitigated with enough engineering effort, these are fundamental limitations that appear difficult to solve.\n\nThe basic problem of MEV results from information asymmetry between users creating transactions, and the searchers and builders finding MEV opportunities. Users typically don’t know how much MEV can be extracted from their transactions. As a result, even with a perfect encrypted mempool, users might be induced to give up their decryption keys in exchange for a payment from builders that is less than the value extracted. We can call this incentivized decryption.\n\nIt’s not hard to imagine how this would look because a version of it, called MEV Share, exists today. MEV Share is an order flow auction that allows users to selectively submit information about their transactions to a pool where searchers compete for the chance to exploit the MEV opportunity presented by the transaction. The searcher with the winning bid extracts the MEV and refunds part of their profit (i.e., the bid or a fraction of the bid) to the user.\n\nThis model could be immediately adapted within an encrypted mempool space, requiring users to reveal their decryption keys (or possibly just some partial information) to participate. But most users won’t understand the opportunity cost of participating in such a scheme, only seeing the rewards coming back to them and being happy to give up their information. There are also examples from traditional finance (e.g., zero-fee trading services like Robinhood) that profit from selling their users’ order flow to third parties in a so-called “payment-for-order-flow” business model.\n\nOther possible scenarios include large builders forcing users to reveal their transactions (or some information about them) for censorship reasons. Censorship resilience is an important and controversial topic within web3, but if large proposers and/or builders are legally obligated to enforce a censorship list (e.g., by OFAC), they may refuse to sequence any encrypted transactions. It might be possible to solve this problem technically, if users can produce a zero-knowledge proof that their encrypted transaction complies with the censorship list, but this will also add cost and complexity. Even if the chain has strong censorship resistance, where encrypted transactions are guaranteed to be included, block builders might still prioritize putting transactions they know in plaintext at the top of the block and demoting any encrypted transactions to the bottom of the block. Thus, transactions that desire certain execution guarantees might be forced to reveal their contents to builders anyways.\n\nOther efficiency challenges\n\nEncrypted mempools add overhead to the system in a few obvious ways. Users must encrypt transactions and the system must somehow decrypt them. This adds computational cost and possibly increases transaction size. As discussed above, dealing with metadata can make these overheads worse. However, some other efficiency costs are less obvious. In finance, a market is considered to be efficient if the price reflects all available information, and inefficiencies arise from delays and information asymmetries — natural consequences of encrypted mempools.\n\nOne of the consequences of these inefficiencies is increased price uncertainty, the result of the additional delay encrypted mempools introduce. Thus, the number of trade failures due to exceeding the price slippage tolerance are likely to increase and waste chain space.\n\nSimilarly, this price uncertainty might also lead to speculative MEV transactions that attempt to profit from onchain arbitrage. Importantly, these opportunities might be more widespread with encrypted mempools because the increased uncertainty around the current state of DEXs, in light of the delayed execution, is likely to produce less efficient markets with price discrepancies across venues. These types of speculative MEV transactions would also waste block space because they will often abort if no such opportunities are found.\n\n***\n\nWhile our goal here was to outline the challenges in encrypted mempools, so that people can focus on building and solving things in other ways, they may yet be a part of the solution to MEV.\n\nOne possible solution is hybrid designs, where some transactions are blind-ordered via an encrypted mempool and some are ordered via another solution. For certain types of transactions — for example, buy/sell orders from large market participants who can carefully encrypt/pad them and are willing to pay more to avoid MEV — hybrid designs may be the right solution. These designs might also make sense for certainly highly sensitive transactions, such as bug fixes to a security contract with a vulnerability.\n\nHowever, due to their technological limitations, as well as significant engineering complexity and performance overheads, encrypted mempools are unlikely to be the silver bullet solution to MEV that they are sometimes made out to be. The community will need to develop other solutions, including MEV auctions, application-layer defenses and minimizing finality time. MEV will be a challenge for some time to come, and careful investigation is needed to find the right balance of solutions to manage its downsides.\n\n***\n\nPranav Garimidi is a Research Associate at a16z Crypto. He does research on problems in mechanism design and algorithmic game theory as it relates to blockchain systems. He is especially focused on how incentives interact across the blockchain stack. Prior to a16z, Pranav was a student at Columbia University where he graduated with a degree in Computer Science.\n\nJoseph Bonneau is an Associate Professor in the Computer Science Department at the Courant Institute, New York University, and a technical adviser to a16z crypto. His research focuses on applied cryptography and blockchain security. He has taught cryptocurrency courses at the University of Melbourne, NYU, Stanford, and Princeton, and received a PhD in computer science from the University of Cambridge and BS/MS degrees from Stanford.\n\nLioba Heimbach is a fourth-year Ph.D. student advised by Prof. Dr. Roger Wattenhofer in the Distributed Computing (Disco) group at ETH Zurich. Her research centers around blockchain protocols with a focus on decentralized finance (DeFi). In particular, it focuses on enabling an accessible, decentralized, fair, and efficient blockchain and DeFi ecosystem. She was a research intern at a16z crypto during the summer of 2024.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nThe content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":6372,"crawled_at":1791193696574}
+{"id":10276,"url":"https://docs.near.org/smart-contracts/anatomy/crosscontract","domain":"docs.near.org","chapter":"layer1_layer2","title":"Cross-Contract Calls - NEAR Docs","text":"NEAR contracts can interact with other deployed contracts, querying information and executing functions on them through cross-contract calls.\nSince NEAR is a sharded blockchain, its cross-contract calls behave differently than in other chains. In NEAR, cross-contract calls are asynchronous and independent.\n\nAsynchronous\nThe calling function and the callback execute in different blocks (typically 1-2 blocks apart). During this time, the contract remains active and can receive other calls.\n\nIndependentEach function — the one making the call, the external function, and the callback — executes in its own context. If the external call fails, the calling function has already completed successfully; there’s no automatic rollback. You must handle failures explicitly in the callback.\n\n​\n\nSnippet: Querying Information\n\nWhile making your contract, it is likely that you will want to query information from another contract. Below, you can see a basic example in which we query the greeting message from our Hello NEAR example.\nlow_level.rs\n\nhigh_level.rs\n\nLoading...\nSee code on GitHub\n\nLoading...\nSee code on GitHub\n\nThe high level API makes use of the interface defined in the ext_contract.rs\n\n​\n\nSnippet: Sending Information\n\nCalling another contract passing information is also a common scenario. Below you can see a function that interacts with the Hello NEAR example to change its greeting message.\nlow_level.rs\n\nhigh_level.rs\n\nLoading...\nSee code on GitHub\n\nLoading...\nSee code on GitHub\n\nThe high level API makes use of the interface defined in the ext_contract.rs\n\n​\n\nPromises\n\nCross-contract calls work by creating two promises in the network:\n\nA promise to execute code in the external contract - Promise.create\n\nOptional: A promise to call another function with the result - Promise.then\n\nBoth promises will contain the following information:\n\nThe address of the contract you want to interact with\n\nThe function that you want to execute\n\nThe arguments to pass to the function\n\nThe amount of GAS to use (deducted from the attached Gas)\n\nThe NEAR deposit to attach (deducted from your contract’s balance)\n\nThe callback can be made to any contract. Meaning that the result could potentially be handled by another contract\n\n​\n\nCreating a Cross Contract Call\n\nTo create a cross-contract call with a callback, create two promises and use the .then method to link them:\nHigh Level API\n\nLow Level API\n\n#[ext_contract(external_trait)]\ntrait Contract {\nfn function_name(&self, param1: T, param2: T) -> T;\n}\n\nexternal_trait::ext(\"external_address\")\n.with_attached_deposit(DEPOSIT)\n.with_static_gas(GAS)\n.function_name(arguments)\n.then(\n// this is the callback\nSelf::ext(env::current_account_id())\n.with_attached_deposit(DEPOSIT)\n.with_static_gas(GAS)\n.callback_name(arguments)\n);\n\nlet arguments = json!({ \"foo\": \"bar\" })\n.to_string()\n.into_bytes();\n\nlet promise = Promise::new(\"external_address\").function_call(\n\"function_name\".to_owned(),\narguments,\nDEPOSIT,\nGAS\n);\n\npromise.then(\n// Create a promise to callback query_greeting_callback\nSelf::ext(env::current_account_id())\n.with_static_gas(GAS)\n.callback_name(),\n);\n\nConcatenating Promises\n\n✅ You can concatenate promises: P1.then(P2).then(P3): P1 executes, then P2 executes with the result of P1, then P3 executes with the result of P2✅ You can join promises: (P1.and(P2)).then(P3): P1 and P2 execute in parallel, after they finish P3 will execute and have access to both their results⛔ You cannot return a joint promise without a callback: return P1.and(P2) is invalid, you need to add a .then()⛔ You cannot join promises within a then: P1.then(P2.join([P3])) is invalid⛔ You cannot use a then within a then: P1.then(P2.then(P3)) is invalid\n\nIf a function returns a promise, then it will delegate the return value and status of transaction execution, but if you return a value or nothing, then the Promise result will not influence the transaction status\n\nThe Promises you are creating will not execute immediately. In fact, they will be queued in the network an:\nThe cross-contract call will execute 1 or 2 blocks after your function finishes correctly.\n\n​\n\nAttaching gas\n\nEach promise in a cross-contract call needs enough gas to execute. This includes the external call and any callback you attach with .then.\n\nAlways reserve gas for the callback. It executes in a separate receipt, so it can fail independently if it does not receive enough gas.\n\nIn the high level API, with_static_gas(gas) reserves a fixed amount of gas for a promise:\n\nconst CALL_GAS: Gas = Gas::from_tgas(10);\nconst CALLBACK_GAS: Gas = Gas::from_tgas(5);\n\nexternal_trait::ext(\"external_address\")\n.with_static_gas(CALL_GAS)\n.function_name(arguments)\n.then(\nSelf::ext(env::current_account_id())\n.with_static_gas(CALLBACK_GAS)\n.callback_name(arguments)\n);\n\nThe high level API also exposes with_unused_gas_weight(weight), which gives a promise a proportional share of the gas left after all static gas has been reserved.\n\nexternal_trait::ext(\"external_address\")\n.with_static_gas(Gas::from_tgas(10))\n.with_unused_gas_weight(2)\n.function_name(arguments)\n.then(\nSelf::ext(env::current_account_id())\n.with_static_gas(Gas::from_tgas(5))\n.with_unused_gas_weight(0)\n.callback_name(arguments)\n);\n\nThe default unused gas weight is 1. Set the weight to 0 when you want a promise to receive only its static gas reservation.\nFor example, if 100 Tgas is left when you create two promises:\nPromiseStatic gasUnused gas weight\nA\n20 Tgas\n1\n\nB\n10 Tgas\n3\n\nThe runtime reserves 30 Tgas as static gas, then distributes the remaining 70 Tgas by weight:\n\nA gets 20 + (1/4) * 70 = 37.5 Tgas\n\nB gets 10 + (3/4) * 70 = 62.5 Tgas\n\nIf you forget that the default weight is 1, a callback or parallel promise can receive more of the remaining gas than you expected. For gas-sensitive calls, combine with_static_gas with with_unused_gas_weight(0) on promises that should not draw from the unused gas pool.\n\nThe low level API (Promise::new(...).function_call(...)) takes a fixed gas value. It behaves like with_static_gas and does not use unused gas weights.\n\n​\n\nCallback Function\n\nIf your function finishes correctly, then eventually your callback function will execute. This will happen whether the external contract fails or not.\nIn the callback function you will have access to the result, which will contain the status of the external function (if it worked or not), and the values in case of success.\nLoading...\nSee code on GitHub\n\nCallback will always executeWe repeat, if your function finishes correctly, then your callback will always execute. This will happen no matter if the external function finished correctly or not\n\nAlways make sure to have enough Gas for your callback function to execute\n\nRemember to mark your callback function as private using macros/decorators, so it can only be called by the contract itself\n\n​\n\nWhat happens if the function I call fails?\n\nIf the external function fails (i.e. it panics), then your callback will be executed anyway. Here you need to manually rollback any changes made in your\ncontract during the original call. Particularly:\n\nRefund the predecessor if needed: If the contract attached NEAR to the call, the funds are now back in the contract’s account\n\nRevert any state changes: If the original function made any state changes (i.e. changed or stored data), you need to manually roll them back. They won’t revert automatically\n\nIf your original function finishes correctly then the callback executes even if the external function panics. Your state will not rollback automatically,\nand $NEAR will not be returned to the signer automatically. Always make sure to check in the callback if the external function failed, and manually rollback any\noperation if necessary.\n\n​\n\nCalling Multiple Functions on the Same Contract\n\nYou can call multiple functions in the same external contract, which is known as a batch call.\nAn important property of batch calls is that they act as a unit: they execute in the same receipt, and if any function fails, then they all get reverted.\nLoading...\nSee code on GitHub\n\nCallbacks only have access to the result of the last function in a batch call\n\n​\n\nCalling Multiple Functions on Different Contracts\n\nYou can also call multiple functions in different contracts. These functions will be executed in parallel, and do not impact each other. This means that, if one fails, the others will execute, and NOT be reverted.\nLoading...\nSee code on GitHub\n\nCallbacks have access to the result of all functions in a parallel call\n\n​\n\nSecurity Concerns\n\nWhile writing cross-contract calls there is a significant aspect to keep in mind: all the calls are independent and asynchronous. In other words:\n\nThe function in which you make the call and function for the callback are independent.\n\nThere is a delay between the call and the callback, in which people can still interact with the contract\n\nThis has important implications on how you should handle the callbacks. Particularly:\n\nMake sure you don’t leave the contract in a exploitable state between the call and the callback.\n\nManually rollback any changes to the state in the callback if the external call failed.\n\nWe have a whole security section dedicated to these specific errors, so please go and check it.\n\nNot following these basic security guidelines could expose your contract to exploits. Please check the security section, and if still in doubt, join us in Discord.\n\nWas this page helpful?","tokens":2356,"crawled_at":1791193697472}
+{"id":10277,"url":"https://docs.dydx.xyz/interaction/data/market","domain":"docs.dydx.xyz","chapter":"defi_protocols","title":"Trading Data – dYdX Documentation","text":"This section guides you on how to fetch some important data points.\nWe focus here on getting data using spontaneous (single) requests. For continuous data streams of data see also the WebSockets guide.\n\nList Positions\n\nAssets are used to trade and manage (perpetual) positions opened and closed by issuing orders. See the example below on how to check your perpetual positions.\n\nPython\nfrom dydx_v4_client.indexer.rest.constants import PositionStatus\n\n# Fetch all subaccount '0' positions.\nperpetual_positions_response = await indexer\n.account\n.get_subaccount_perpetual_positions(ADDRESS, 0)\n\n# Fetch only open positions.\nperpetual_positions_response = await indexer\n.account\n.get_subaccount_perpetual_positions(address, 0, PositionStatus.OPEN)\n\nSee the API reference for the complete method definition.\n\nMarket List\n\nA market (sometimes referred by the ticker name, e.g., ETH-USD) is associated with a perpetual and it is the place where trading happens.\nTo fetch the available markets see the code below.\n\nPython\nresponse = await indexer.markets.get_perpetual_markets()\nprint(response[\"markets\"])\n\nSee the API reference for the complete method definition.\n\nList Orders\n\nRetrieve orders for a specific subaccount, with various filtering options to narrow down the results based on order characteristics.\n\nPython\norders_response = indexer.account.get_subaccount_orders(address, 0)\n\nSee the API reference the complete method definition.\n\nGet Fills\n\nRetrieve order fill records for a specific subaccount on the exchange. Fills are matched orders.\n\nPython\nfills_response = indexer.account.get_subaccount_fills(address, 0)\n\nSee the API reference the complete method definition.\n\nPrice History\n\nPrice history in the classic candlestick can also be fetched. Data will be organized into a open, high, low, and close (OHLC) prices for some period.\n\nPython\nfrom dydx_v4_client.indexer.candles_resolution import CandlesResolution\nresponse = await indexer.markets.get_perpetual_market_candles(\nmarket=\"BTC-USD\", resolution=CandlesResolution.ONE_MINUTE\n)\nprint(response[\"candles\"])\n\nSee the API reference for the complete method definition.\n\nGet User Fee Tier\n\nThe Get User Fee Tier function retrieves the perpetual fee tier associated with a specific wallet address, providing information on the user's current fee structure.\n\nPython\nuser_fee_tier = await node.get_user_fee_tier(ADDRESS)\n\nSee the API reference for the complete method definition.\n\nGet Rewards Params\n\nThe Get Rewards Params function retrieves the parameters for the rewards system, providing insight into the set configurations for earning and distributing rewards.\n\nPython\nrewards_params = await node.get_rewards_params()\n\nSee the API reference for the complete method definition.\n\nTrading Rewards\n\nRetrieve historical block trading rewards for the specified address.\n\nPython\nresponse = await indexer.account.get_historical_block_trading_rewards(test_address, limit)\n\nSee the API reference for the complete method definition.\n\nGet Latest Block Height\n\nRetrieve the most recent block's height. This can serve to see if the blockchain node you are connected to is in sync.\n\nPython\nheight = await node.latest_block_height()\n\nSee the API reference for the complete method definition.","tokens":809,"crawled_at":1791193714962}
+{"id":10278,"url":"https://a16zcrypto.com/posts/tags/mev","domain":"a16zcrypto.com","chapter":"research","title":"mev - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nmev\n\nFeed\nFILTERS\n(1)\nclear filters\n\ncategories\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\n(1) recommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nclear all mev\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n07.15.25 / Pranav Garimidi, Joseph Bonneau and Lioba Heimbach\nOn the limits of encrypted mempools\nAn encrypted mempool is not a universal solution to MEV. This post outlines the difficulties and explores how encrypted mempools might be designed.\n\nresearch\nDeFi\nmev\n\n05.28.25 / a16z crypto editorial\nMEV, explained: what it is, what to do about it [newsletter]\nWhat is MEV, or maximal extractable value? Plus a marketing 101 primer: How to attract developers, launch tokens, hire teams, and more\n\ntech trends\nmev\nnewsletters\n\n05.15.25 / Pranav Garimidi and Joseph Bonneau\nMEV explained\nA primer on the basics of maximal extractable value (MEV), how it affects blockchains, and ways to address it\n\nresearch\nDeFi\nmev\n\n09.21.23 / Pranav Garimidi\nTransaction fee mechanism design with active block producers\nPranav Garimidi (a16z crypto research) explores active block producers, which have their own private valuations for blocks.\n\nresearch\nDeFi\nmev\nvideo\n\n07.10.23 / Maryam Bahrani, Pranav Garimidi and Tim Roughgarden\nNew paper alert: “Transaction Fee Mechanism Design with Active Block Producers”\nNew research shows that transaction fee mechanism design is fundamentally more difficult with active block producers than with passive ones\n\nresearch\nDeFi\nmev\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":1075,"crawled_at":1791193715731}
+{"id":10279,"url":"https://docs.near.org/smart-contracts/anatomy/actions","domain":"docs.near.org","chapter":"layer1_layer2","title":"Transfers & Actions - NEAR Docs","text":"This page describes the different types of actions that a smart contract can perform on NEAR like transferring NEAR, calling other contracts, creating sub-accounts, and deploying contracts. It also explains how to add access keys to accounts.\nSmart contracts can perform specific Actions such as transferring NEAR, or calling other contracts.\nAn important property of Actions is that they can be batched together when acting on the same contract. Batched actions act as a unit: they execute in the same receipt, and if any fails, then they all get reverted.\n\nActions can be batched only when they act on the same contract. You can batch calling two methods on a contract,\nbut cannot call two methods on different contracts.\n\n​\n\nTransfer NEAR Ⓝ\n\nYou can send $NEAR from your contract to any other account on the network. The Gas cost for transferring $NEAR is fixed and is based on the protocol’s genesis config. Currently, it costs ~0.45 TGas.\n\nuse near_sdk::{near, AccountId, Promise, NearToken};\n\n#[near(contract_state)]\n#[derive(Default)]\npub struct Contract { }\n\n#[near]\nimpl Contract {\npub fn transfer(&self, to: AccountId, amount: NearToken){\nPromise::new(to).transfer(amount);\n}\n}\n\nWhy is there no callback?\nThe only case where a transfer will fail is if the receiver account does not exist.\n\nRemember that your balance is used to cover for the contract’s storage. When sending money, make sure you always leave enough to cover for future storage needs.\n\n​\n\nFunction Call\n\nYour smart contract can call methods in another contract. In the snippet below we call a method\nin a deployed Hello NEAR contract, and check if everything went\nright in the callback.\n\nuse near_sdk::{near, env, log, Promise, Gas, PromiseError};\nuse serde_json::json;\n\n#[near(contract_state)]\n#[derive(Default)]\npub struct Contract { }\n\nconst HELLO_NEAR: &str = \"hello-nearverse.testnet\";\nconst NO_DEPOSIT: u128 = 0;\nconst CALL_GAS: Gas = Gas(5_000_000_000_000);\n\n#[near]\nimpl Contract {\npub fn call_method(&self){\nlet args = json!({ \"message\": \"howdy\".to_string() })\n.to_string().into_bytes().to_vec();\n\nPromise::new(HELLO_NEAR.parse().unwrap())\n.function_call(\"set_greeting\".to_string(), args, NO_DEPOSIT, CALL_GAS)\n.then(\nPromise::new(env::current_account_id())\n.function_call(\"callback\".to_string(), Vec::new(), NO_DEPOSIT, CALL_GAS)\n);\n}\n\npub fn callback(&self, #[callback_result] result: Result<(), PromiseError>){\nif result.is_err(){\nlog!(\"Something went wrong\")\n}else{\nlog!(\"Message changed\")\n}\n}\n}\n\nThe snippet showed above is a low level way of calling other methods. We recommend make calls to other contracts as explained in the Cross-contract Calls section.\n\n​\n\nCreate a Sub Account\n\nYour contract can create direct sub accounts of itself, for example, user.near can create sub.user.near.\nAccounts do NOT have control over their sub-accounts, since they have their own keys.\nSub-accounts are simply useful for organizing your accounts (e.g. dao.project.near, token.project.near).\n\nCreating an account costs a fixed 0.007Ⓝ, or about 0.00707Ⓝ in total once the send fees are added. That 0.007Ⓝ already includes the gas burned while creating the account, and it is taken out of the transaction’s gas refund, not out of the deposit you attach for storage.\n\nuse near_sdk::{near, env, Promise, NearToken};\n\n#[near(contract_state)]\n#[derive(Default)]\npub struct Contract { }\n\nconst MIN_STORAGE: NearToken = NearToken::from_millinear(1); //0.001Ⓝ\n\n#[near]\nimpl Contract {\npub fn create(&mut self, prefix: String) {\nlet account_id = prefix + \".\" + &env::current_account_id().to_string();\nPromise::new(account_id.parse().unwrap())\n.create_account()\n.transfer(MIN_STORAGE);\n}\n}\n\nNotice that in the snippet we are transferring some money to the new account for storage\n\nWhen you create an account from within a contract, it has no keys by default. If you don’t explicitly add keys to it or deploy a contract on creation then it will be locked.\n\n​\n\nCreating .testnet / .near Accounts\n\nAccounts can only create immediate sub-accounts of themselves.\nIf your contract wants to create a .mainnet or .testnet account, then it needs to call\nthe create_account method of near or testnet root contracts.\n\nuse near_sdk::{near, Promise, Gas, NearToken };\nuse serde_json::json;\n\n#[near(contract_state)]\n#[derive(Default)]\npub struct Contract { }\n\nconst CALL_GAS: Gas = Gas::from_gas(28_000_000_000_000);\nconst MIN_STORAGE: NearToken = NearToken::from_yoctonear(1_820_000_000_000_000_000_000); //0.00182Ⓝ\n\n#[near]\nimpl Contract {\npub fn create_account(&mut self, account_id: String, public_key: String){\nlet args = json!({\n\"new_account_id\": account_id,\n\"new_public_key\": public_key,\n}).to_string().into_bytes().to_vec();\n\n// Use \"near\" to create mainnet accounts\nPromise::new(\"testnet\".parse().unwrap())\n.function_call(\"create_account\".to_string(), args, MIN_STORAGE, CALL_GAS);\n}\n}\n\n​\n\nDeploy a Contract\n\nWhen creating an account you can also batch the action of deploying a contract to it. Note that for this, you will need to pre-load the byte-code you want to deploy in your contract.\n\nuse near_sdk::{near, env, Promise, NearToken};\n\n#[near(contract_state)]\n#[derive(Default)]\npub struct Contract { }\n\nconst MIN_STORAGE: NearToken = NearToken::from_millinear(1100); //1.1Ⓝ\nconst HELLO_CODE: &[u8] = include_bytes!(\"./hello.wasm\");\n\n#[near]\nimpl Contract {\npub fn create_hello(&self, prefix: String){\nlet account_id = prefix + \".\" + &env::current_account_id().to_string();\nPromise::new(account_id.parse().unwrap())\n.create_account()\n.transfer(MIN_STORAGE)\n.deploy_contract(HELLO_CODE.to_vec());\n}\n}\n\nIf an account with a contract deployed does not have any access keys, this is known as a locked contract. When the account is locked, it cannot sign transactions therefore, actions can only be performed from within the contract code.\n\n​\n\nAdd Keys\n\nWhen you use actions to create a new account, the created account does not have any access keys, meaning that it cannot sign transactions (e.g. to update its contract, delete itself, transfer money).\nThere are two options for adding keys to the account:\n\nadd_access_key: adds a key that can only call specific methods on a specified contract.\n\nadd_full_access_key: adds a key that has full access to the account.\n\nuse near_sdk::{near, env, Promise, NearToken, PublicKey};\n\n#[near(serializers = [json, borsh])]\n#[derive(Default)]\npub struct Contract { }\n\nconst MIN_STORAGE: NearToken = NearToken::from_millinear(1100); //1.1Ⓝ\nconst HELLO_CODE: &[u8] = include_bytes!(\"./hello.wasm\");\n\n#[near]\nimpl Contract {\npub fn create_hello(&self, prefix: String, public_key: PublicKey){\nlet account_id = prefix + \".\" + &env::current_account_id().to_string();\nPromise::new(account_id.parse().unwrap())\n.create_account()\n.transfer(MIN_STORAGE)\n.deploy_contract(HELLO_CODE.to_vec())\n.add_full_access_key(public_key);\n}\n}\n\nNotice that what you actually add is a “public key”. Whoever holds its private counterpart, i.e. the private-key, will be able to use the newly access key.\n\nThe public_key can use any of NEAR’s signature schemes — ed25519, secp256k1, or the post-quantum ml-dsa-65. Adding an ml-dsa-65 key needs no code changes: pass an ml-dsa-65:... key exactly like the examples above.\n\nIf an account with a contract deployed does not have any access keys, this is known as a locked contract. When the account is locked, it cannot sign transactions therefore, actions can only be performed from within the contract code.\n\n​\n\nDelete Account\n\nThere are two scenarios in which you can use the delete_account action:\n\nAs the last action in a chain of batched actions.\n\nTo make your smart contract delete its own account.\n\nuse near_sdk::{near, env, Promise, NearToken, AccountId};\n\n#[near(contract_state)]\n#[derive(Default)]\npub struct Contract { }\n\nconst MIN_STORAGE: NearToken = NearToken::from_millinear(1); //0.001Ⓝ\n\n#[near]\nimpl Contract {\npub fn create_delete(&self, prefix: String, beneficiary: AccountId){\nlet account_id = prefix + \".\" + &env::current_account_id().to_string();\nPromise::new(account_id.parse().unwrap())\n.create_account()\n.transfer(MIN_STORAGE)\n.delete_account(beneficiary);\n}\n\npub fn self_delete(beneficiary: AccountId){\nPromise::new(env::current_account_id())\n.delete_account(beneficiary);\n}\n}\n\nToken LossIf the beneficiary account does not exist the funds will be dispersed among validators.\n\nToken LossDo not use delete to try fund a new account. Since the account doesn’t exist the tokens will be lost.\n\nWas this page helpful?","tokens":2115,"crawled_at":1791193715963}
+{"id":10280,"url":"https://gov.uniswap.org/t/atiselsts-eth-delegate-platform/22270?page=2","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Atiselsts.eth Delegate Platform - Page 2 - Delegation Pitch - Uniswap Governance","text":"Atiselsts.eth Delegate Platform\n\nDelegation Pitch\n\nkfx\n\nMarch 17, 2025, 8:15am\n\n21\n\nOnchain\n\nUniswap Unleashed\n\nVote: Against. Same rationale as for the snapshot vote.\n\nTo be clear, I will continue to support the UF and the DAO regardless of the outcome, even if I disagree with the proposed resource allocation: Disagree and commit.\n\nUnichain and Uniswap v4 Liquidity Incentives\n\nVote: Abstain. Upon reflection, I changed my “Against” vote in the snapshot to “Abstain” in the on-chain vote. While I believe it is important to provide liquidity incentives for the v3 to v4 migration, I do not want my vote to be interpreted as opposition to that effort.\n\nThat said, I want to reiterate that supporting Unichain incentives at this stage is premature. While Unichain has strong potential, the DAO should first establish some level of governance control over Unichain, including its fee switch. Additionally, incentives should be conditional on Labs delivering the promised technical innovations in Unichain, specifically:\n\nFlashblocks\n\nUVN with fees captured by UNI stakers\n\nCross-chain swaps utilizing Unichain’s liquidity\n\nSnapshot\n\n[Temp Check] Saga Uniswap v3 Liquidity Incentives\n\nVote: Against. The liquidity incentive program has now been running for a year, and the evidence conclusively shows that providing incentives to low-TVL chains has been ineffective. As a result, I will vote against all such incentives going forward unless a compelling, exceptional case is made for the chain.\n\nWhile the Saga architecture is interesting, it does not currently meet the threshold for an exceptional case.\n\n[Temp Check] Treasury Delegation Round 2\n\nVote: For. Strong support. We clearly need the treasury delegation program to continue to reach quorum on votes. Furthermore, this is a solid proposal that improves the existing program in several ways (notably with automatically expiring delegations), is clear and comprehensive. I’m also happy to see that agreement to the Uniswap DAO Principles has been added as a requirement.\n\n2 Likes\n\nkfx\n\nApril 11, 2025, 11:55am\n\n22\n\nApril Votes\n\nOnchain\n\nBoB Uniswap v3 Incentives Package\n\nVote: For.\n\nFollowing the snapshot vote, I continue to support this proposal.\n\nEstablish Uniswap v4 Licensing Process\n\nVote: For.\n\nFollowing the snapshot vote, I continue to support this proposal.\n\nSnapshot\n\n[TEMP CHECK] BoB Uniswap v3 Incentives Package\n\nVote: For $375k.\n\nPreviously I stated that I’d support v3 / multichain incentives in exceptional cases. BOB hits the checklist nicely, and therefore is such a case:\n\nRelatively solid total chain TVL\n\nStrong buy-in from the chain, prioritizing Uniswap as the top DEX on the chain.\n\nSolid existing Uniswap TVL and fee revenue, relative to the chain’s TVL.\n\nLast but not least, more than matching Uniswap’s incentives with their own, part of which is already distributed.\n\nIt’s slightly disappointing that they did not go straight for v4, but since their v3 deployment has already been active for some time, forcing them to switch to v4 would create unnecessary friction.\n\n[TEMP CHECK] Establish Uniswap v4 Licensing Process\n\nVote: For.\n\nThis proposal will streamline v4 deployments, while keeping the risks minimal.\n\nUAC Renewal S4\n\nVote: Renew UAC.\n\nThe UAC has been successfully operating for the past three seasons and is a key actor of the ecosystem and a focus point of the DAO.\n\nThe increase in the runway budget is reasonable and in line with the increased responsibilities.\n\nThe discretional budget ask is also reasonable, relatively small compared to the main budget, and will hopefully ensure that the UAC can operate without unnecessary friction.\n\nApproved Budgets Rebalancing (S4)\n\nVote: Approve Rebalance.\n\nThis action is necessary due to UNI token price changes. As UNI remains very volatile, it’s expected that we’ll need to occasionally do this.\n\n[Temp Check/Revised] Treasury Delegation Round 2\n\nVote: For.\n\nThis is a revised version of a proposal that I supported previously. As the revised version is even more conservative, I continue to strongly support it. The change from 18 to 12 month limit is fine due to the situation with Unistaker potentially coming live in 2025. (It’s good to learn that it has not been abandoned, at least.)\n\nFor those in doubt of the need of such a program, the fact is that the DAO has been reliant on the previous iteration to reach consensus on almost all votes. Until this situation in some other way, let’s keep the program running to keep the DAO operational.\n\n[TEMP CHECK] Scaling V4 and Supporting Unichain\n\nVote: For.\n\nThe proposal has GFX Labs requesting $250k to integrate Uniswap v4 in Oku Trade.\n\nI support this proposal primarily because I would support any proposal for an alternative frontend that has reasonable cost requirements and a competent, experienced team behind it. Having alternative frontends is important for Uniswap, as it reduces both regulatory and censorship risks. Uniswap is too important a protocol to rely on a single point of failure at the UI level. Additionally, it provides the DAO with some leverage over Labs—something sorely needed, as the DAO’s history demonstrates.\n\nSide note on the conflict of interest involving @GFXlabs that someone mentioned (quote below). As one of the authors of the DAO Principles, I’d like to clarify how I interpret their application in this case.\n\nLet me be clear that this is a conflict of interest situation, and potentially falls under the guideline that “severe conflicts of interest […] must be avoided.” Ideally, GFX Labs should change their vote to “Abstain.” However, I don’t believe this alone is a reason to veto the proposal. The principles are non-binding and voluntary—a delegate may choose to disagree with them. (Though the vision is that violating the principles will make a delegate ineligible for DAO programs such as the Treasury Delegation Program.) Furthermore, to my knowledge, GFX Labs did not vote in favor of adopting the principles—perhaps anticipating situations like this—so at the very least, their position is internally consistent.\n\n1 Like\n\nScaling V4 and Supporting Unichain\n\nScaling V4 and Supporting Unichain\n\nkfx\n\nMay 6, 2025, 12:58pm\n\n23\n\nMay Votes\n\nOnchain\n\nUAC Renewal S4\n\nVote: For.\n\nFollowing the snapshot vote, I continue to support this proposal.\n\nApproved Budgets Rebalancing (S4)\n\nVote: For.\n\nFollowing the snapshot vote, I continue to support this proposal.\n\nScaling V4 and Supporting Unichain\n\nVote: For.\n\nAs in the snapshot, I continue to support this incentive. The updated Additional Use Grant text also makes extremely clear what the scope and limitations are.\n\nSnapshot\n\n[Temp Check] Analytics Hub for Uniswap’s Revitalization and Growth Program\n\nVote: For.\n\nWhile I did not support the initial Forse proposal, I’m willing to support this one. The reasons are:\n\nI was hoping that there could be some competition in proposals aiming to analyze the DAO’s incentive programs. Since this has not happened, and Forse remains the only candidate with a concrete proposal, at this point its fair to support them.\n\nThe Forse team has delivered their initial analytics and proven their competency and ability to execute.\n\nSome has raised concerns about duplication of work if/when Gauntlet does some of their own analysis, especially for Unichain. In my view, there is no duplication, since the incentives manager should not be the one responsible for analyzing the success of the program. Ideally that should be an unaffiliated third party, but absent that, Forse will have to do.\n\nFour Chains for Analytics Hub for Uniswap’s Revitalization and Growth Program\n\nVote: Unichain, zkSync, Polygon zkEVM.\n\nRationale:\n\nUnichain - self explanatory.\n\nPolygon zkEVM - this was probably the least successful of DAO incentive programs in terms of TVL retention, so it would be important to do a postmortem here to avoid similar failures in the future.\n\nzkSync - a fairly prototypical chain / L2 in the context of this incentive program, so can serve as a baseline for comparison. Also there’s a clear follow-up potential, to analyze the zkSync’s own Ignite incentive program, and contrast/compare that with the DAO’s incentive program.\n\nUniswap Accountability Committee S4 Elections\n\nVote: 66% Doo, 33% Takeshi.\n\nTo my knowledge, none of the candidates had a significantly different vision for the UAC compared with the existing UAC’s direction and responsibilities. In light of this, it made the most sense to look at the experience and accomplishments of the candidates in Uniswap DAO so far, so that the new UAC members can “hit the ground running”. Both Doo and Takeshi have experience in authoring and submitting proposals, being active members of working groups, etc. Doo also has previous UAC experience.\n\nkfx\n\nJune 3, 2025, 8:40am\n\n24\n\nJune Votes\n\nOnchain\n\nScaling V4 and Supporting Unichain (revised version)\n\nVote: For.\n\nSince the only change was the removal of Additional Use Grant text, I continue to support this proposal.\n\nSnapshot\n\nTrial run a Technical Advisory Board (TAB)\n\nVote: Abstain.\n\nEchoing other delegates, I have concerns about the necessity of this program, cost, and candidate preselection without consulting the DAO. However if the DAO wished I would not be against seeing a trial run as an experiment, since experimentation can lead to useful findings even when the result is not a success.\n\nUniswap Unichain - USDS and sUSDS Co-Incentives Growth Management Plan\n\nVote: For. Attracting a major protocol like Sky to Unichain is important for its growth. I like the conditional unlock approach, this is something I was (unsucessfully) suggested to UF for their Unichain incentives. However, I will not support this proposal when it reaches onchain stage, unless it adds more concrete details on how the incentives are planned to be spent.\n\n1 Like\n\nkfx\n\nJuly 14, 2025, 7:47am\n\n25\n\nJuly Votes\n\nSnapshot\n\n[TEMP CHECK] - Etherlink Co-incentives Proposal\n\nVote: Do Not Approve. There’s lot to like in this proposal, this is a solid proposal backed by an well established foundation in the space, with a co-incentive ratio ($300k co-incentives vs. $150k ask) that’s very good relative to Uniswap’s historical averages. However I have previously stated that in 2025 I plan to apply a stricter threshold for chains asking for incentives. While I have supported BOB incentives, Etherlink, unless a further evidence is provided, falls a little short of that threshold.\n\nkfx\n\nAugust 20, 2025, 7:53am\n\n26\n\nAugust votes\n\nSnapshot\n\nUniswap Delegate Reward Initiative - Cycle 4\n\nVote: For.\n\nI continue to support this program. including the new 1000 UNI requirement, which in my view is long overdue.\n\nI’m also happy to see (and want to draw attention to!) that following the Uniswap Principles now is expected from the delegates who receive compensation.\n\nWhile I obviously have a conflict of interest in this vote, I believe it’s sufficient to acknowledge the CoI, rather than to abstain from voting. This is in line with the Principles.\n\nEstablish Uniswap Governance as “DUNI,” a Wyoming DUNA\n\nVote: For.\n\nThis is a much desired development that should open many options for the Uniswap DAO, including managing the protocol treasury and collecting revenue from Unichain or the protocol.\n\nPerhaps more importantly, it will clarify and limit the individual liability of the delegates, which has been a realistic concern for all these years.\n\nLess ideally, it will firmly tie the protocol governance to the US. However that also is a sensible choice given the options, and the fact that both the Labs and Foundation are already based in the US.\n\nkfx\n\nSeptember 3, 2025, 3:58pm\n\n27\n\nSeptember votes\n\nOnchain\n\nEstablish Uniswap Governance as “DUNI,” a Wyoming DUNA\n\nVote: For. Following my support in the snapshot, I continue to vote for this initiative.\n\nUnichain Co-Incentives Growth Management Plan\n\nI support this initiative, keeping the same rationale as for the snapshot. The added details are sufficient to get my support in the on chain stage. However I will be unable to vote this time because of travel and HW wallet access.\n\nSnapshot\n\nGLI — Treasury delegation Round 2\n\nVote: For. I continue to support the treasury delegation program.\n\nConflict of interest statement: I received 153 544.00 UNI delegation in the previous round. This amount is ~37% of the total votes under my control.\n\nGLI — Incentivized Delegation Vaults\n\nVote: Abstain. I cannot support this proposal as I see it out of sync with potential strategic developments like yield from UVN and Unistaker.\n\nLaunching Uniswap v3 on Ronin with co-incentives\n\nVote: Do not deploy initiatives. I do not support continuing UNI incentives for v3 deployments in 2025, unless the circumstances are exceptional.\n\nkfx\n\nOctober 3, 2025, 2:22pm\n\n28\n\nOctober 2025 Votes\n\nSnapshot\n\nTreasury Delegation Round 2 Elections\n\nVote (alphabetical order):\n\n25% Arana Digital\n\n25% Event Horizon\n\n25% SEEDGov\n\n25% Tane\n\nAll these delegates have demonstrated strong involvement in the DAP through proposal preparation, WG and/or UAC participation, discussions, voting and so on. I would also support KPK with the same rationale, but felt that here new delegates should be given priority as KPK is already part of the still ongoing first round of treasury delegations.\n\nGrow Uniswap on Plasma.\n\nVote: Allocate $250k. First, this vote asks for the $250k in addition to another $250k that will be taken from UAC’s discretionary budget once all blockers are sorted out - some delegates have been misinterpreting this!\n\nWhile my vote is positive, this was by no means a foregone conclusion. Why? 1) Plasma is not an Ethereum chain. 2) Continuing to incentivize v3 in late 2025 is not a great look.\n\nEventually I supported it due to the large existing TVL and growth potential of Plasma, as well as the generous XPL co-incentives.\n\n1 Like\n\nkfx\n\nNovember 8, 2025, 9:47am\n\n29\n\nNovember 2025 Votes\n\nSnapshot\n\nUniswap Community Proposal Factory\n\nVote: Against.\n\nAfter careful consideration, I will be voting against this proposal, as I disagree with the notion that introducing a new actor in the governance process with 20M UNI delegated brings no additional risks. As a minimum, it brings in a leverage multiplier, as now everyone who supports the CPM proposal effectively has the power of their votes multiplied by the additional 20M votes. The design should be reviewed by an independent third party / parties, both for smart contract risks but more importantly for economic attack risks.\n\nkfx\n\nNovember 19, 2025, 10:59am\n\n30\n\nSnapshot\n\nUNIfication\n\nVote: For.\n\nRationale: https://gov.uniswap.org/t/unification-proposal/25881/29?u=kfx\n\nkfx\n\nDecember 3, 2025, 8:39am\n\n31\n\nDecember 2025 Votes\n\nSnapshot\n\nStrategic Renewal of Gnosis, Linea, and Mantle Deployments\n\nVote: For.\n\nWe need to continue supporting alternatives to the Labs frontend. Continuing to fund deployments on these three chains is a good way to do that, since there’s no direct competition involved.\n\nOnchain\n\nUNIficaton\n\nVote: For. Following my snapshot vote, I continue to support this game-changing proposal.\n\nStrategic Renewal of Gnosis, Linea, and Mantle Deployments\n\nVote: For. I continue to support this proposal. We need to keep some balance in the DAO even after Labs steps in as the main service provider.\n\n1 Like\n\nkfx\n\nFebruary 20, 2026, 2:35pm\n\n32\n\nFebruary 2026\n\nSnapshot\n\n[Temp Check] Protocol Fee Expansion: Eight More Chains and Remaining Mainnet V3 Pools\n\nVote: For.\n\nThis is a continuation of the fee switch from the UNIfication proposal. As such, I continue to support it, with the same rationale as described above.\n\nOnchain\n\nProtocol Fee Expansion: Vote 1\n\nProtocol Fee Expansion: Vote 2\n\nVote: For (both).\n\nContinue to support the proposal. While the protocol fee is share % is higher that I’d recommend myself, it’s worth doing this experiment - let’s turn it on and observe what the reaction is. A positive outcome is where the Uniswap’s overall market share (both in TVL and volume) is retained - either through LPs staying in v3 pools, or, prefferrably, migrating to v4.\n\nkfx\n\nJuly 9, 2026, 2:04pm\n\n33\n\n[Temp Check] Activate v4 Protocol Fees\n\nVote: Abstain. There proposed high (25%) protocol fee is expected to decrease available liquidity. This comes with risks not just for Uniswap traders - which will be getting worse execution - but for the rest of DeFi too, as liquidations under stress are affected. For deeper analysis, see my X thread.\n\n← previous page\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nGFX Labs - Delegate Communication Thread\n\nDelegation Pitch\n\n27\n\n1504\n\nDecember 8, 2025\n\nSEEDGov Delegate Platform\n\nDelegation Pitch\n\n76\n\n3514\n\nMay 5, 2026\n\nTané Delegate Platform\n\nDelegation Pitch\n\n59\n\n2404\n\nMarch 9, 2026\n\nCuria Delegate Platform\n\nDelegation Pitch\n\n53\n\n2385\n\nJuly 23, 2026\n\nIgnas Delegate Platform\n\nDelegation Pitch\n\n41\n\n1284\n\nMay 25, 2026","tokens":4213,"crawled_at":1791193721281}
+{"id":10281,"url":"https://a16zcrypto.com/posts/article/mev-explained","domain":"a16zcrypto.com","chapter":"research","title":"MEV explained - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nMEV explained\nPranav Garimidi and Joseph Bonneau\n05.15.25\n\nTABLE OF CONTENTS\nExamples of MEV Examples of MEV\nHow MEV works\nOn the negative externalities of MEV\nMitigating the negative externalities\nMinimizing MEV\nTags\nDeFi\nmev\nresearch\ntech trends\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nMEV has been a hot topic in the blockchain industry, and particularly relevant in DeFi. When blockchains still relied on proof of work, MEV stood for “miner extractable value,” but it now commonly stands for “maximal extractable value.” Fundamentally, it is the value that can be obtained by including, excluding, or reordering transactions in a block, in addition to standard block rewards.\n\nMEV naturally arises from the fact that block producers are responsible for coordinating users’ preferences and hence are in a position to profit from information asymmetries. (In computer science-speak, they are responsible for “advancing semantically interesting state” — a point in the system where an important change occurs that matters to its operation, like the creation of a new block.)\n\nBecause there are many ways to coordinate preferences, block producers can gain value through strategically performing the coordination task in a way that benefits them. This makes MEV fundamental to how blocks get built on nearly all blockchains. And while MEV manifests in various forms — some good, some bad (both of which we’ll discuss below) — it drastically affects protocols by changing the incentives of the people participating in them.\n\nIt’s only by understanding MEV that protocol designers can help manage it. And because understanding these effects and addressing the externalities of MEV has been a topic of widespread interest and debate, in this post we explain the basics of what MEV is, how it affects blockchains, and ways to address it.\n\nExamples of MEV\n\nFrontrunning\n\nPerhaps the simplest form of MEV is frontrunning. Frontrunning occurs whenever a transaction is strategically inserted right before a target transaction for some type of market advantage. For example, consider a first-come, first-serve lottery where at some randomly announced block, the first transaction to interact with a smart contract can claim some prize. In this case, the block producer for the slot when the prize is available to claim can always guarantee that they can claim the prize before any users submitting transactions.\n\nBackrunning\n\nAnother example of MEV is a form of onchain arbitrage called backrunning. Whereas frontrunning rearranges transactions so the person who finds it can extract profits (or execute other smart contract calls to their benefit) before someone’s transaction executes, backrunning places the transaction after that person’s transaction.\n\nIf Alice broadcasts an order to buy 1,000 ETH worth of ExampleTokens via an automated market maker (AMM), it shifts the price at that AMM and creates a price difference compared to other AMMs. The larger her trade as a fraction of the AMM’s liquidity, the larger this price impact. A third party who spots this (typically called a searcher) can insert a sell transaction right after Alice’s to profit from this price differential, moving the spot price of the AMM back in line with the rest of the market in the process.\n\nNote that this MEV opportunity existed because the AMM’s price drifted from the actual price of the asset. In this case, backrunning actually provides a service in keeping AMMs’ prices up to date.\n\nSandwich attacks\n\nAnother kind of MEV is a sandwich attack, in which a target transaction is sandwiched in between frontrunning and backrunning transactions to influence price and more.\n\nSuppose Alice again broadcasts an order to buy 1000 ETH worth of ExampleTokens via an AMM. With no attack, the AMM might fulfill this order at an average price of 0.1 ETH per token. A sandwich attacker can frontrun Alice’s trade by inserting a transaction just ahead of it that buys ExampleTokens from the same AMM. This will increase the spot price of the AMM when Alice’s trade gets executed, causing Alice to pay a higher price than she would have otherwise.\n\nThen the attacker can also backrun Alice’s transaction, adding a transaction just after it that sells the ExampleTokens to the AMM at an inflated price. The net result is that Alice pays a higher price for the ExampleTokens, and the attacker earns a profit.\n\nSpeculative MEV\n\nThese simple examples already show a few interesting properties of MEV: First, searchers don’t necessarily need their transactions to appear in an exact order. Backrunning, for example, can be profitable as long as the transactions appear after Alice’s transaction (and any intervening transactions don’t interact with the same decentralized exchange or DEX pool). Second, even if a searcher’s backrunning transaction doesn’t get sequenced as intended (after Alice’s transaction), the searcher’s transaction can automatically abort the attack by reverting.\n\nCombining these two ideas, even without precise control over transaction ordering, searchers can attempt speculative MEV: insert an MEV transaction that will execute if sequenced as hoped, but will revert otherwise. The only cost of failure is transaction fees for the reverted transactions. If transaction costs are low relative to the potential gains from the MEV opportunity, it might be worthwhile for the searcher to attempt many speculative MEV transactions, even if most of them fail. Speculative MEV especially makes sense when gas fees are low so searchers pay almost nothing for failed attempts.\n\nHow MEV works\n\nWhy is MEV exploitation possible?\n\nIn the simplest traditional blockchain designs users broadcast their transactions to a public peer-to-peer network. This process places the transaction into the mempool, a public holding area maintained by each validator of transactions waiting to be included in the chain.\n\nWhen it is a validator’s turn to propose a block, they scan their mempool to decide which transactions to include and in what order. Naively, a validator might sort the transactions in decreasing order of fees and simply include the maximal prefix of this list that fits within the gas limit to maximize the fees they earn.\n\nBut a validator can decide which transactions to include in specific orders to maximize the MEV they earn. Importantly, validators have full jurisdiction over what gets included. Not only are they free to pick the ordering that favors them most, they can add their own transactions — with the benefit of seeing all other transactions in the block.\n\nWhile this picture captures how MEV started out on blockchains, it omits much of the complexity of how MEV works today. A complex infrastructure has evolved with multiple specialized competing parties who facilitate MEV. For example on Ethereum, proposers rarely construct blocks themselves, instead relying on this infrastructure to decide which block to propose. The most important parties — in addition to the existing users and proposers — are searchers and builders.\n\nSearchers operate at the transaction level and look for opportunities to bundle transactions together to earn MEV. Backrunning and sandwiching are examples of the type of MEV a searcher would extract.\n\nBuilders operate at the block level and are responsible for putting together bundles into a single block from multiple searchers, along with normal transactions from users. Instead of deciding which transactions to include in a block themselves, validators today often run an auction where they propose the block constructed by the builder with the highest bid.\n\nIn practice, the ways these parties interact with each other is incredibly complex and constantly evolving. For example, users frequently opt to send their transactions not to public mempools, but to private ones, which broadcast their transactions to only a select list of searchers and builders, giving them an edge over their competition. In return, these private mempools sometimes explicitly pay users to submit to them or make promises to users that certain types of MEV won’t be extracted from them. The way the MEV ecosystem works also differs greatly from chain to chain and is constantly evolving.\n\nOn the negative externalities of MEV\n\nIf not properly addressed, the incentives MEV creates can bring negative externalities to the system, which must be understood so they can be addressed.\n\nFor example, in the traditional setup — without MEV infrastructure, where users simply submit transactions to the public mempool and validators pick a block — a searcher might be incentivized to spam many speculative MEV attacks. Or multiple searchers might actively compete for the same MEV opportunity onchain. In both of these cases, lots of blockspace gets taken up by useless transactions, driving gas costs up and decreasing the opportunity for other transactions to land.\n\nMEV can also affect the consensus layer. If the revenue from MEV in a given block outweighs standard block rewards by a large enough margin, it may be rational for the next proposer to fork the chain to claim this value.\n\nFinally, MEV can be a centralizing force in the blockchain ecosystem, which is meant to be decentralized. Those with an edge in MEV extraction can accumulate disproportionate profits, leading to increased control and influence over the network.\n\nIn response, researchers, blockchain designers, and users have proposed multiple approaches to mitigate MEV, or at least reduce its negative externalities. Many of the elements of today’s MEV infrastructure have arisen to address these very problems, although not without creating problems of their own.\n\nMitigating the negative externalities\n\nOffchain auctions\n\nOne of the earliest and most widely adopted approaches to tackle MEV’s externalities is using offchain auctions to facilitate competition for MEV.\n\nBlock builders run auctions where searchers compete to win MEV opportunities in a given builder’s block. By competing via these auctions, searchers no longer have incentives to spam the chain with speculative transactions that often revert. Today these auctions rely on trusted third parties (sometimes implemented within trusted hardware enclaves like TEEs) to keep the mempool private and run the auction.\n\nOrder flow auctions\n\nWhile these auctions address the externalities MEV has on network performance, they don’t address the negative externalities users face.\n\nOrder flow auctions (OFAs) aim to address this problem. OFAs allow users to selectively share information about their transaction with searchers. If searchers find a profitable MEV opportunity targeted at the transaction, they bid for the right to extract the MEV. The searcher with the highest bid gains exclusive rights to extract MEV from that user’s transaction; in return the user gets paid the bid. In essence, OFAs redistribute some of the MEV back to users.\n\nSingle-slot finality\n\nTweaks to the consensus layer can also mitigate the effects of MEV.\n\nFor example, single-slot finality (SSF), whereby each block is finalized within a slot (with no possibility of forking), is a partial solution to the consensus-layer risk that MEV poses. Once a block is finalized, a subsequent proposer can no longer fork the blockchain to extract the value in that block themselves.\n\nThis doesn’t completely eliminate consensus layer effects, though: Other validators might be incentivized not to finalize a block from a competing proposer if there is valuable MEV that could instead be taken by the next proposer.\n\nSingle-slot finality does prevent consensus-layer impact of MEV under an honest majority assumption. One might be tempted to assume that, since consensus protocols already require an honest majority assumption among validators, this is a safe assumption to make. Unfortunately, these two honest majority assumptions are not equivalent. Safety violations in a consensus protocol (e.g., equivocating attestations), which are possible given a corrupt threshold of nodes, typically lead to public evidence of misbehavior.\n\nMEV, however, does not produce attributable evidence. For this reason, validators might reasonably be unwilling to attack consensus (for fear of exposure) but willing to chase MEV. This latter assumption is a strong honest majority assumption (most nodes will be honest even if attacking produces no evidence) versus a weak honest majority assumption (most nodes will be honest only if attacks are detectable) — an important distinction that affects multiple MEV mitigations, which we will come back to.\n\nMinimizing MEV\n\nA second group of approaches to mitigating MEV goes further, targeting MEV itself. Broadly, these approaches can be divided into three categories:\n\napplication-specific prevention,\n\nfair ordering proposals, and\n\nblind-ordering proposals, also known as encrypted mempools.\n\nApplication-specific prevention\n\nSome types of MEV can be prevented through careful application-specific design.\n\nFor example, Dutch Auctions are trivially vulnerable to MEV, because it is profitable to front-run the first broadcast bid. But attacking Vickrey Auctions implemented via a commit-reveal scheme is more difficult, because it would require re-organizing the chain to retroactively insert a bid commitment.\n\nSimilarly, limiting the maximal tolerable price slippage, batch auctions, or switching from an AMM to limit order books are all possible design choices that remove or reduce potential MEV extraction for specific applications. Of course, all of these approaches require careful consideration by application developers, and they often impose a performance penalty (e.g., requiring extra transactions or extra data posted on-chain).\n\nFair ordering proposals\n\nNext are approaches that aim to ensure fair ordering of transactions: Transactions are ordered first come, first served.\n\nGiven that there is no central server in DeFi but instead a distributed network of nodes that receives and orders transactions, nodes can see transactions in different relative orders. Consequently, agreeing on a relative order is not a straightforward task. Ongoing work therefore focuses on consensus protocols that approximate a fair ordering. Also, once again, fair ordering requires a strong honest majority assumption on validators since there is no way to tell if validators misreport the time they received a transaction.\n\nEncrypted mempools\n\nLast are the solutions that attempt to order transactions blindly: The transaction order is agnostic to the transaction contents.\n\nOne way to achieve this is by committing to a set of transactions in a block first, then randomly shuffling them with a randomness beacon that is sampled after the transaction set is finalized. This can make MEV more difficult — but not impossible. Speculative attacks, where searchers spam potential backrunning transactions to hope to land in a favorable spot, still exist.\n\n***\n\nOur goal with this overview is to help protocol designers understand MEV and its effects so they can help address it. While MEV introduces dynamics that can disadvantage users and distort incentives, it is also a transparent and observable phenomenon inherent to public blockchain infrastructure. Because MEV is visible onchain, it allows for market-based accountability: Projects that implement mechanisms to minimize harmful MEV — whether through private mempools, encrypted transaction ordering, or incentive-aligned auction design — can be rewarded by the market (that is, users) and can be integrated into application-layer norms.\n\nThese features of MEV stand in contrast to prescriptive regulatory interventions, which may risk slowing the evolution of infrastructure or mischaracterizing emergent behaviors. Innovation often arises in response to adversarial conditions, so a policy framework that permits this evolutionary process — rather than prematurely constraining it — is more likely to produce robust, decentralized solutions.\n\n***\n\nPranav Garimidi is a Research Analyst at a16z Crypto. He does research on problems in mechanism design and algorithmic game theory as it relates to blockchain systems. He is especially focused on how incentives interact across the blockchain stack. Prior to a16z, Pranav was a student at Columbia University where he graduated with a degree in Computer Science.\n\nJoseph Bonneau is an Associate Professor in the Computer Science Department at the Courant Institute, New York University, and a technical adviser to a16z crypto. His research focuses on applied cryptography and blockchain security. He has taught cryptocurrency courses at the University of Melbourne, NYU, Stanford, and Princeton, and received a PhD in computer science from the University of Cambridge and BS/MS degrees from Stanford.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nThe content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":4835,"crawled_at":1791193734003}
+{"id":10282,"url":"https://docs.sui.io/getting-started","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Getting Started | Sui Documentation","text":"Sui Documentation\nSui delivers the full stack for a new global economy. Assets, data, and permissions can be owned, programmed, and verified.\n\nStart building\nSui Agent Skills\n\nDrop pre-built skills into Claude Code, Cursor, Codex, and other AI coding agents to build on Sui.\n\nSui Docs MCP Server\n\nConnect the documentation MCP server to Claude Code, Cursor, or VS Code so your agent can search Sui docs without leaving the editor.\n\nTry it out\nHello, World!\n\nBuild and publish your first Move packagePackageSmart contracts on Sui. on Sui with a step-by-step walkthrough.\n\nExample Apps\n\nSource repositories for MoveMoveAn open source programming language used for all activity on Sui. contracts, React frontends, indexers, and onchain security challenges.\n\nConsumer App Cookbook\n\nOnboard users without a wallet install, a seed phrase, or a funding step, using zkLoginzkLoginA Sui primitive that allows you to send transactions using an OAuth credential., Enoki, and Seal.\n\nLearn the fundamentals\nSui Architecture\n\nUnderstand the objectObjectThe basic unit of storage on Sui. model, consensusConsensusThe process by which the majority of nodes agree on the current state of the network, and transactionTransactionA number of commands that execute on inputs to define the result of the transaction. pipeline.\n\nWriting Move Packages\n\nLearn Move on Sui: structs, abilities, modulesModuleA component of a Move package that defines interaction with on-chain objects., and patterns.\n\nBuilding Transactions\n\nConstruct programmable transaction blocksProgrammable transaction blocksDefine all user transactions on Sui. (PTBs) for complex operations.\n\nTools and references\nDeveloper Tools\n\nCLI, IDE extensions, debuggers, linters, and deployment tools.\n\nDeveloper Cheat Sheet\n\nQuick reference on best practices for Sui developers.\n\nSui SDKs\n\nTypeScript, Rust, Python, Go, and community SDKs.\n\nComing from another chain?\nEthereum → Sui\n\nMap EVM concepts to Sui's object model and Move language.\n\nSolana → Sui\n\nCompare Solana's account model with Sui's object-centric approach.","tokens":516,"crawled_at":1791193737309}
+{"id":10283,"url":"https://gov.uniswap.org/t/gfx-labs-delegate-communication-thread/24194","domain":"gov.uniswap.org","chapter":"governance_daos","title":"GFX Labs - Delegate Communication Thread - Delegation Pitch - Uniswap Governance","text":"GFX Labs - Delegate Communication Thread\n\nDelegation Pitch\n\nGFXlabs\n\nJuly 3, 2024, 1:52am\n\n1\n\nThis thread is intended to provide a record of GFX Labs’ voting and communication around the reasoning of each vote. Subsequent voting communications will be added to this thread over time.\n\nApril Proposals\n\nTemp Check - Onboard Uniswap to Sei\n\nSummary: Blockchain Michigan proposed that Sei receive the Uniswap Onboarding Package.\n\nRecommendation: For Incentivize $500K. GFX Labs is always in favor of additional Uniswap deployments. We believe that Sei is a good opportunity for Uniswap to secure an early key position after their launch of Sei v2.\n\nTemp Check - Update Uni v3/v2 Deployment Process (March 2024)\n\nSummary: This proposal contains a series of operational improvements for new v2 and v3 deployments. This proposal would transfer the ability to add new records to v2deployments and v3deployments ENS records to the UAC.\n\nRecommendation: Vote Update Process. The DAO has been operating on an outdated system. This proposal contains logical reforms that should streamline new deployments post-BSL.\n\nUpdate Uni v3/v2 Deployment Process (March 2024)\n\nSummary: This proposal contains a series of operational improvements for new v2 and v3 deployments. This proposal would transfer the ability to add new records to v2deployments and v3deployments ENS records to the UAC.\n\nRecommendation: Vote For. The DAO has been operating on an outdated system. This proposal contains logical reforms that should streamline new deployments post-BSL.\n\nTemp Check - Uniswap Onboarding Package - Manta\n\nSummary: This proposal adds Manta Pacific to the v3 deployments record and grants Manta an Onboarding Package, which includes $250k of UNI incentives for three months on four key markets and Angle Merkl’s integration of Manta. Separate from this proposal, Manta has arranged for Oku to support Manta, and the contracts have been deployed.\n\nRecommendation: Vote For. GFX Labs authored the proposal. Read the proposal for full reasoning.\n\nOnboarding Package Bundle\n\nSummary: GFX Labs authored the proposal. The proposal bundles four proposals that have previously been approved in individual temperature checks. While we typically like to avoid bundling proposals, we consulted with the Accountability Committee (AC) and other members of the DAO prior to posting the proposal to weigh the operational headache of getting four delegates to make proposals. In the future, the organization could consider upgrading our governance contract to make it easier to run multiple governance proposals. Please read the proposal for the full context.\n\nRecommendation: Vote For. For the reasons stated in the proposal and related temperature checks, GFX Labs is voting in favor of this proposal.\n\nTemp Check - Uniswap Treasury Working Group (UTWG) Election\n\nSummary: This election would fill two seats on the UTWG.\n\nRecommendation: 20% for Franklin DAO, 20% for Steakhouse Financial Limited, 20% for Nathan van der Heyden, 20% for 404 DAO, 20% for karpatkey.\n\nMobilizing the Uniswap Treasury\n\nSummary: StableLab proposed the UTWG receive its initial funding of 6,000 UNI. The proposal is co-authored by Arana.\n\nRecommendation Vote For. We support the DAO’s exploration of new ways to manage its treasury and are particularly interested in how it might handle protocol-owned liquidity. After deploying UNI incentives to several new EVM chains, it would be great if the DAO could begin allocating ETH-stablecoin and stable-stable LP to chains.\n\nTemp Check - DeFi Education Fund\n\nSummary: GFX Labs sponsored DEF’s proposal, which requested 1M UNI. 500K was transferred to the DEF’s Coinbase account, and the other 500K will be streamed to the DEF over 12 months. DEF’s founding grant came in July 2021. They have two years of operations currently, but for them to fight larger and longer battles, they need additional funding.\n\nRecommendation: Vote For. The DEF has proven to be a great investment for the DAO and the ecosystem. While the initial grant carried added risk because it was a new program and untested, we now have evidence for their quality of work and value.\n\nTemp Check - DeFi Education Fund Options\n\nSummary: Stable introduced a poll to amend the amount of funds requested by the DEF. If the primary Temp Check were to fail the quorum, then this poll’s result would be applied to the onchain proposal.\n\nRecommendation: Vote Abstain. Since GFX Labs favored the original proposal, we decided to abstain from voting in the poll.\n\nMay Proposals\n\nTemp Check - Uniswap Delegate Reward 3 Months Cycle 1\n\nSummary: StableLab introduced the DAO’s first Delegate compensation program. The program will run for three months. Qualifying delegates will receive compensation based on some basic metrics.\n\nRecommendation: Vote For. GFX Labs is in favor of being a delegate compensation program. Delegate compensation is a key issue in attracting and retaining high-quality delegates. While this program is imperfect in many ways, we will not let perfection prevent progress. Instead, we invite (and have done so proactively) other organizations and delegates to propose improved programs. Ideally, the DAO can select a new and improved program each cycle.\n\nTemp Check - Onboard Uniswap to Redstone\n\nSummary: Redstone is requesting to become an official Uniswap deployment and an Onboarding Package. Due to Redstone’s limited TVL and market position, it does not merit an Onboarding Package at this time. We would be happy to reevaluate down the line.\n\nRecommendation: Deploy without incentives. As always, we are in favor of new Uniswap deployments for any chain that follows the process and passes ownership back to the DAO.\n\nDeFi Education Fund\n\nSummary: GFX Labs sponsored DEF’s proposal, which requested 1M UNI. 500K was transferred to the DEF’s Coinbase account, and the other 500K will be streamed to the DEF over 12 months. DEF’s founding grant came in July 2021. They have two years of operations currently, but for them to fight larger and longer battles, they need additional funding.\n\nRecommendation: Vote For. The DEF has proven to be a great investment for the DAO and the ecosystem. While the initial grant carried added risk because it was a new program and untested, we now have evidence for their quality of work and value.\n\nJune Proposals\n\nTemp Check - Uniswap Arbitrum LTIPP Matching\n\nSummary: The UADP secured 1M ARB from Arbitrum’s LTIPP program. In their application to Arbitrum DAO, the UADP stated that they would request a matching of funds from Uniswap. Gauntlet will manage the rewarded funds via Merkl’s platform.\n\nRecommendation: Vote (1st) $250k, (2nd) Do Not Fund, (3rd) $500k, (4th) $750k, (5th) $1m. Uniswap has a strong position in Arbitrum. A modest matching of funds with the LTIPP seems appropriate, but we discourage significant investment in Arbitrum over other opportunities.\n\nUniswap Arbitrum LTIPP Matching\n\nSummary: The UADP secured 1M ARB from Arbitrum’s LTIPP program. In their application to Arbitrum DAO, the UADP stated that they would request a matching of funds from Uniswap. Gauntlet will manage the rewarded funds via Merkl’s platform. The prior temperature check resulted in $750K, which is requested in this onchain proposal.\n\nRecommendation: Vote For. While the amount is more than we had ideally considered, it is within reason. However, we will be unlikely to vote in favor of further UNI allocated to Arbitrum unless there is clear evidence of Uniswap losing meaningful market share and a clear plan for the UNI to combat that issue.\n\n5 Likes\n\nUniswap Delegate Reward Initiative - Cycle 2 Application\n\nGLI -- Treasury Delegation Round 2 Applications\n\nUniswap Delegate Reward Initiative - Cycle 3 Application and Results\n\nGFXlabs\n\nAugust 2, 2024, 11:04am\n\n2\n\nJuly Proposals\n\n[Temp Check] Uniswap Onboarding Package - Gnosis Chain\n\nSummary: Gnosis requested an onboarding package. This is the standard package available to new deployments.\n\nRecommendation: Vote $250k.\n\n[Temp Check] Uniswap Onboarding Package - OKX Chain\n\nSummary: OKX Chain requested an onboarding package. This is the standard package available for new deployments.\n\nRecommendation: Vote $250k.\n\n1 Like\n\nTreasury Delegation Round 2 Ideas Thread\n\nGFXlabs\n\nSeptember 6, 2024, 4:15am\n\n3\n\nAugust Proposals\n\nOnboarding Package for Gnosis Chain\n\nSummary: Gnosis requested an onboarding package. This is the standard package available to new deployments.\n\nRecommendation: For. $250K (no change from the temp check).\n\n[Temp Check] Forse Analytics for Uniswap Revitalization and Growth Program\n\nSummary: This proposal seeks to onboard Forse by StableLab as a data service provider, helping analyze the effectiveness of the Uniswap Revitalization and Growth Program.\n\nRecommendation : Against. Linking because we had a longer comment on the thread.\n\n[TEMP CHECK]- Revised - Uniswap Onboarding Package - OKX Chain\n\nSummary: On OKX’s behalf, we proposed that X Layer receive a revised onboarding package.\n\nRecommendation : For. We continue to believe that expanding to new chains is advantageous for the DAO. By OKX putting up a liquidity guarantee, we agree it’s in the DAO’s interest to authorize the package.\n\n[REDO: Temp Check] Activate 2, 3, 4 bps fee tiers on Uniswap v3 on Base\n\nSummary: Austin proposed the DAO enable the 2, 3, 4 bp fee tiers on Base to position the DAO better to compete with Aerodrome’s 4bp fee pools.\n\nRecommendation : Abstain. Linking because we had a longer comment on the thread.\n\n[Temp Check] Uniswap Delegate Reward Initiative - Cycle 2\n\nSummary: Renewing the delegate pay program for another three months.\n\nRecommendation : For. Linking because we had a longer comment on the thread.\n\nOnchain vote: Uniswap Delegate Reward Initiative - Cycle 2\n\nSummary: Renewing the delegate pay program for another three months.\n\nRecommendation : For. Linking because we had a longer comment on the thread.\n\nOnchain vote: Deploy Uniswap v3 on X Layer\n\nSummary: On OKX’s behalf, we proposed that X Layer receive a revised onboarding package.\n\nRecommendation : For. We continue to believe that expanding to new chains is advantageous for the DAO. By OKX putting up a liquidity guarantee, we agree it’s in the DAO’s interest to authorize the package.\n\n2 Likes\n\nGFXlabs\n\nSeptember 9, 2024, 5:11pm\n\n4\n\nSeptember Proposals\n\nProposal to active 2, 3, 4 bps fee-tiers on Base\n\nSummary: Add additional fee tiers to combat Aerodrome’s recent rise with their 4bp fee tier.\n\nRecommendation: Abstain. We voted to abstain in the temperature check and will vote to abstain here as well. Most of our reasons are available on the forum. To summarize, we don’t believe this initiative will be successful in gaining back our lost market share from Aerodrome because we’re competing against their token incentives. We’re not voting against the proposal because we don’t believe it can harm the protocol, but we also don’t think there is much upside in the action either, so we’re not voting for it. If the DAO wants to improve LP flexibility, then we should focus on the GTM of v4.\n\n[Temp Check] - Ethereum Foundation Attackathon Sponsorship\n\nSummary: The proposal requests funding for the EF’s Attackathon, with two sponsorship tiers: Unicorn Partners requires a +75 ETH commitment (approximately $250,000), and Panda Partners requires a 30 ETH commitment (approximately $100,000).\n\nRecommendation: Abstain. We do not feel strongly enough to support or oppose this initiative at this time. While the capital request is not significant, the ROI and what we could expect from the EF in return are unclear.\n\n1 Like\n\nGFXlabs\n\nSeptember 11, 2024, 8:25pm\n\n5\n\nUAC Renewal S3\n\nSummary: The UAC is seeking funding for its third season.\n\nRecommendation: Renew UAC. GFX Labs has had the pleasure of working closely with the UAC over the last year while we have been expanding Uniswap v3 to new chains. The committee demonstrated a strong commitment to the protocol, its roles in the committee, and its partners. We are pleased to see the UAC continue to take on more responsibility and effectively operate.\n\nApproved Budgets Rebalancing\n\nSummary: Due to price changes in UNI, the UAC is requesting an additional 42K UNI.\n\nRecommendation: Approve Rebalance. The UAC has demonstrated good accounting practices. The UNI allocated to them is being put to work per governance.\n\nUniswap Delegate Race Tiebreaker\n\nSummary: Tiebreaker vote for 15th delegate slot on the cycle 2 program.\n\nRecommendation: Both. In the current situation, expanding the program to another delegate who would have otherwise qualified if we had a 16th slot is fine. Given the short length (three months) of this program, adding another delegate while the DAO still needs more delegates is a net positive.\n\n2 Likes\n\nGFXlabs\n\nOctober 7, 2024, 2:30am\n\n6\n\nUniswap Delegate Reward Initiative - Cycle 2 - Onchain\n\nSummary: This proposal will fund an additional three months of the delegate compensation program and expand the number of delegate positions to 16.\n\nRecommendation: For. While we voted in favor of a second cycle of this program, GFX will be hesitant to support this program for a third cycle unless we see reforms. We initially voted for the first cycle, admitting it was a far from perfect program, but in light of no other real options, we decided it was better than nothing. However, this sort of thinking can’t go on forever.\n\nDuring the early voting process of cycle one, we tried to bring in the folks at Gov Score and Karma to develop a more robust program. We have since suggested our own reform for cycle 3, and we’re keen for the DAO to adopt our suggestion or others.\n\nHigh-quality delegate participation is critical to the success of the DAO. We should strive to improve this program with each new cycle to drive the outcomes we all want to see in Uniswap.\n\nProposal to active 2, 3, 4 bps fee-tiers on Base - Onchain\n\nSummary: Add additional fee tiers to combat Aerodrome’s recent rise with their 4bp fee tier.\n\nRecommendation: Abstain. We voted to abstain in the temperature check and will vote to abstain here as well. Most of our reasons are available on the forum. To summarize, we don’t believe this initiative will be successful in gaining back our lost market share from Aerodrome because we’re competing against their token incentives. We’re not voting against the proposal because we don’t believe it can harm the protocol, but we also don’t think there is much upside in the action either, so we’re not voting for it. If the DAO wants to improve LP flexibility, then we should focus on the GTM of v4.\n\nUAC Renewal S3 - Onchain\n\nSummary: The UAC is seeking funding for its third season.\n\nRecommendation: Renew UAC. GFX Labs has had the pleasure of working closely with the UAC over the last year while we have been expanding Uniswap v3 to new chains. The committee demonstrated a strong commitment to the protocol, its roles in the committee, and its partners. We are pleased to see the UAC continue to take on more responsibility and effectively operate.\n\nForse Analytics for Uniswap Revitalization and Growth Program\n\nSummary: This proposal seeks to onboard Forse by StableLab as a data service provider, helping analyze the effectiveness of the Uniswap Revitalization and Growth Program.\n\nRecommendation: Abstain. We’ve updated our position from Against to Abstain after StableLab reduced their requested fee from $70K to $60k. We don’t believe the analysis would yield enough value to support the proposal, but we also felt that if other delegates felt it would we would not oppose it.\n\nFor more context, the goal of the Uniswap Revitalization and Growth program is for Uniswap to establish a position in new chains such that if the chain ends up growing significantly, Uniswap can grow with the chain rather than trying to join later and face an uphill battle. The incentives are meant to help Uniswap establish itself at the chain during the initial launch and then end with no plan to bring it back. The hope is that two or three chains that get these incentives grow to become massive chains, and then we’ll have a great market position. Most of them aren’t going to be worth putting additional incentives on. In some instances, the UAC didn’t distribute all the funds allocated by the DAO because it would have been far too wasteful to do so in their mind. Generally, we learn the most about a new blockchain’s potential success in those few months while working with them on the new deployment, marketing, and other post-launch efforts. GFX would be happy to play an active role in the event a chain requests additional funding. However, we don’t foresee that occurring at this time.\n\nUniswap Accountability Committee S3 Elections\n\nSummary: 10 individuals are running for election on the UAC. The top two will join the committee.\n\nRecommendation: The candidates for this election were by far the strongest we have ever seen. We believe all the candidates would do a fine job if elected, but we focused our attention on candidates who have been participating in the DAO and have a vested interest in seeing it succeed. Going into the last 24 hrs, we thought supporting one of the lesser-known but rising individuals in the Uniswap ecosystem would be beneficial. This made it a difficult decision, but ultimately, we selected Jay Yu from Standford. Jay was kind enough to answer a few last-minute questions that helped us decide.\n\n[TEMP CHECK] - Onboarding Package for Lisk\n\nSummary: The proposal requests that Uniswap put up $375K in UNI and cover Merkl costs, and Lisk will put up $250K in LSK and $1M in liquidity. Separately, Lisk has arranged for Oku to support the deployment, and it is currently live on Oku.\n\nRecommendation: For. Lisk’s proposal sets a new precedent that we think is very healthy and deepens the relationship between the two organizations. We will encourage more chains to include incentives and liquidity in their package requests.\n\n1 Like\n\nGFXlabs\n\nNovember 5, 2024, 12:51am\n\n7\n\nTemp Check - Uniswap Growth Trial\n\nSummary: AlphaGrowth has identified that the DAO’s BD and marketing functions are quite limited in their present form. They have proposed running a six-month trial with a monthly budget of $70K.\n\nRecommendation: For. We concur with AlpahGrowth’s assessment of the DAO and its needs. The DAO’s surface area is large and unattended. It would be beneficial to have a DAO-backed team focused on growing the protocol’s core business. Six months should be a sufficient period for the DAO to evaluate their performance and value to the DAO before considering a longer term.\n\nOnchain - [Updated] Forse Analytics for Uniswap Revitalization and Growth Program\n\nSummary: The StableLab team proposed an updated version of their Forse analytics proposal, reducing the requested amount from $70K to $60K while increasing the chain count from three to four.\n\nRecommendation: For. We debated this proposal. We initially opposed it because we didn’t believe it would produce value relative to its cost. However, the decrease in cost and increase in the chain represents an overall 36% reduction in price. While we don’t expect immense value, we did feel it was in the range of supporting.\n\nOnchain - Uniswap Growth Trial\n\nSummary: AlphaGrowth has identified that the DAO’s BD and marketing functions are quite limited in their present form. They have proposed running a six-month trial with a monthly budget of $70K.\n\nRecommendation: For. We concur with AlpahGrowth’s assessment of the DAO and its needs. The DAO’s surface area is large and unattended. It would be beneficial to have a DAO-backed team focused on growing the protocol’s core business. Six months should be a sufficient period for the DAO to evaluate their performance and value to the DAO before considering a longer term.\n\nTemp Check - Tally Uniswap Proposal\n\nSummary: Tally requested 250K/year for two years for their supporting Uniswap on their platform.\n\nRecommendation: For. Tally has been a critical partner for the Uniswap DAO. In our opinion, this proposal is long overdue. They provide a high-quality service and have done so for years with no compensation. If the DAO were to stand up our service, we would likely spend the same amount and probably produce a lower quality experience.\n\n1 Like\n\nGFXlabs\n\nDecember 4, 2024, 3:40am\n\n8\n\n[TEMP CHECK] - Tally Uniswap Proposal\n\nSummary: Tally is requesting Uniswap pay them $250K/year for two years for ongoing support, maintenance, and feature requests.\n\nRecommendation: For. GFX Labs has been a user of Tally from the beginning. We have utilized Tally heavily in our capacity as a delegate at Uniswap. We can uniquely attest to its value since we have created the most proposals of any delegate and have been participating in the DAO since the spring of 2021.\n\nTally has the difficult task of indexing every UNI transfer, its effect on voting power, how every wallet voted, supporting delegates in creating proposals, simulating proposals, and displaying proposals to voters. From our experience with Oku, we know that indexing that data, organizing it to be easily queryable in an API, offering a high-quality and reliable user interface, and operating it as a business is not easy.\n\nThat said, we should reassess the contract six months before its expiry before we need to renew it.\n\nSupporting Tally’s Development and Enhancements for Uniswap DAO Governance\n\nSummary: Tally is requesting Uniswap pay them $250K/year for two years for ongoing support, maintenance, and feature requests.\n\nRecommendation: For. Same rationale as our temp check rationale.\n\n2 Likes\n\nGFXlabs\n\nJanuary 8, 2025, 5:30am\n\n9\n\n[TEMP CHECK] Uniswap DAO Principles\n\nSummary: A set of principles were proposed for the Uniswap DAO to review and agree to.\n\nRecommendation: GFX Labs informally abstained from voting. We are generally opposed to social governance. Without the governance mechanism being onchain, it holds little hard value. Of course, there can be some social and coordinating value, but we didn’t see a reason to sign on to this proposal.\n\n[Temp Check] - Adopt The SEAL Safe Harbor Agreement\n\nSummary: A proposal to provide liability protection to a white hat hacker group.\n\nRecommendation: We chose to vote Abstain out of an abundance of caution. The agreement itself contains language that attempts to bind users, who are not party to this agreement. Additionally, it appears to require those voting in favor of it to waive their own legal right to legal recourse.\n\nMore broadly, this agreement presents a case where governance is proactively agreeing, in writing, to be classified as a legal person, which we do not necessarily agree with, and do not wish to endorse, since that could have unintended consequences.\n\nWe believe this agreement is done with the best of intentions, and to fill a gap in the existing bug bounty, but will withhold an affirmative endorsement of this agreement.\n\n[TEMP CHECK] Scale Uniswap Liquidity on Celo\n\nSummary: Celo is requesting $250K in UNI + $105K for Oku and will be committing $500K in Celo incentives in addition to having already allocated $730K in CELO.\n\nRecommendation: GFX Labs is in Favor of Celo’s request. Celo has done a great job scaling its Uniswap deployment and has a unique niche in foreign stablecoin. Additionally, their user base is interested in having a more professional interface to enable and enhance further FX trading and liquidity management.\n\n[TEMP CHECK] Metal L2: Bridging TradFi and DeFi Through Uniswap V3\n\nSummary: Metal requests $250K from the DAO and will match it with 250K MTL tokens. Regardless, Metal will be deploying an additional 250k MTL to the new deployment and they have already contracted GFX Labs to deploy Oku.\n\nRecommendation: GFX Labs is in favor of this proposal. Metal is one of the oldest projects in the space and has done a great job building a popular product and growing user base. Uniswap has the unique opportunity to be the first major DEX on their Superchain L2 before Aerodrome stakes their claim.\n\nDiscretionary Budget from UAC for Co-Incentive Campaigns\n\nSummary: AlphaGrowth is requesting access to additional funds so they can structure incentive-matching deals faster than the DAO will approve them.\n\nRecommendation: GFX Labs is in Favor of this proposal. However, we encourage delegates to monitor the allocation of funds and performance to ensure good practices. Overall, the DAO\n\nwill benefit from more active management, and in order to do that, we need to delegate responsibility.\n\nIncentive Package for Sonic (Formerly Fantom)\n\nSummary: Sonic is requesting $250k for the DAO, which they will match with $500k, and they have already contracted Oku to deploy on Sonic.\n\nRecommendation: GFX Labs is in favor of the proposal. Sonic’s offer to double the incentives match is generous.\n\nOnchain Scale Uniswap Liquidity on Celo\n\nSummary: Celo is requesting $250K in UNI + $105K for Oku and will be committing $500K in Celo incentives in addition to having already allocated $730K in CELO.\n\nRecommendation: GFX Labs is in Favor of Celo’s request. Celo has done a great job scaling its Uniswap deployment and has a unique niche in foreign stablecoin. Additionally, their user base is interested in having a more professional interface to enable and enhance further FX trading and liquidity management.\n\nOnchain Incentive Package for Sonic\n\nSummary: Sonic is requesting $250k for the DAO, which they will match with $500k, and they have already contracted Oku to deploy on Sonic.\n\nRecommendation: GFX Labs is in favor of the proposal. Sonic’s offer to double the incentives match is generous.\n\n1 Like\n\nGFXlabs\n\nFebruary 8, 2025, 4:37pm\n\n10\n\nUniswap DAO Principles\n\nSummary: A set of principles written by Atis and Erik for the Uniswap DAO.\n\nRecommendation: We appreciate Atis’ and Erik’s efforts in crafting this documents. We generally support its contents and hope it can guide delegates.\n\nHowever, we don’t feel it necessitates being written to the chain by the DAO since there is no binding aspect of the proposal or an onchain mechanism is connects with. For that reason we have casted our vote to abstain.\n\nGovernance Proposal - Adopt The SEAL Safe Harbor Agreement\n\nSummary: A proposal to provide liability protection to a white hat hacker group.\n\nRecommendation: Recommendation: We chose to vote Abstain out of an abundance of caution. The agreement itself contains language that attempts to bind users who are not party to this agreement. Additionally, it appears to require those voting in favor of it to waive their own legal right to legal recourse.\n\nMore broadly, this agreement presents a case where governance is proactively agreeing, in writing, to be classified as a legal person, which we do not necessarily agree with, and do not wish to endorse, since that could have unintended consequences.\n\nWe believe this agreement is done with the best of intentions, and to fill a gap in the existing bug bounty, but will withhold an affirmative endorsement of this agreement.\n\n1 Like\n\nGFXlabs\n\nFebruary 24, 2025, 9:03pm\n\n11\n\n# [Temp Check] Uniswap Delegate Reward Initiative - Cycle 3\n\nSummary: Renew the Uniswap Delegate Reward Initiative\n\nRecommendation: Overall, the program has been successful at bringing a few more delegates and getting delegates to participate more regularly. Unfortunately, it’s not clear that the quality has improved over the duration of this program. In some aspects, like feedback, the program has led to general improvements, but nothing is clearly substantial. However, the number of proposals and the quality of proposal has remained stagnant. We voted to abstain on the proposal because we are generally for it, but we wished to see reform in cycle 3 to drive further productivity. The current proposal does not go far enough to drive delegates to be more productive.\n\nGFXlabs\n\nMarch 14, 2025, 5:15pm\n\n12\n\nUniswap Unleashed\n\nSummary: The Uniswap Foundation requests 20.32M UNI (~$120M) for their 2025/2026 budget.\n\nRecommendation: Against. Link to our original comment.\n\nAs it currently stands, the Uniswap Foundation is an entirely independent organization. The DAO has no ability to direct, oversee, or manage the UF. Given the UF’s large request and track record, it is sensible for the Uniswap DAO to appoint a legal board to guide and support the foundation. Please review our comments from the forum thread for more information.\n\nFurther, it has come to our attention that the leading Uniswap v4 projects use a “No-Op” hook (see Hook Rank for where “No-Op” hooks are being used), enabling them to build more custom and unique functionality, bypassing the core Uniswap v4’s swap logic. While we appreciate how that enables novel applications to be developed, it cuts the DAO’s ability to turn on a fee for those pools.\n\nThe DAO, and the UF, with the DAO’s funding, should only be financially supporting hook/pool development where it can also accrue value.\n\n3 Likes\n\n[Governance Proposal] Uniswap Unleashed: Unichain and Uniswap v4 Liquidity Incentives\n\nGFXlabs\n\nApril 3, 2025, 12:25am\n\n13\n\nUnichain and Uniswap v4 Liquidity Incentives\n\nSummary: Allocate 7.5M UNI for Uniswap v4 and Unichain rewards.\n\nRecommendation: Abstain. Relevant comment: link. The UF plans to allocate UNI to pools that the DAO cannot monetize per Devin’s comment. Since Devin did say they would seek methods to either “…split fees or otherwise share economics…” we voted to abstain rather than explicitly against.\n\n[Temp Check] Saga Uniswap v3 Liquidity Incentives\n\nSummary: Saga requested $250K in UNI for six months to support five pools on Saga. Saga will allocate $4.2M. Saga paid for Oku’s costs.\n\nRecommendation: For. This is the most a chain has offered to put in rewards, and we felt it was a very rational proposal relative to their minimal ask.\n\n[Temp Check] Treasury Delegation Round 2\n\nSummary: Revise the existing protocol delegation program to have expiring delegations and increase the total amount delegated by the protocol to 18M.\n\nRecommendation: Abstain. We don’t think the program has been a glaring success. We want more folks making creative/ambitious proposals to move the DAO forward. We fear utilizing UNI from the treasury increases the bureaucracy and limits productivity. That said, we don’t hold a strong enough opinion to cast an against vote.\n\nGFXlabs\n\nApril 21, 2025, 7:02pm\n\n14\n\n[TEMP CHECK] Establish Uniswap v4 Licensing Process\n\nSummary: Grant the UF access to deploy Uniswap v4 as they see fit.\n\nRecommendation: For. As Uniswap transitions from v3 to v4, upgrading how chain deployments are handled makes sense. From our point of view, this proposal is an easy operational improvement.\n\n[TEMP CHECK] BoB Uniswap v3 Incentives Package\n\nSummary: Bob Chain requests approximately $380K from the DAO.\n\nRecommendation: For. GFX Labs generally supports proposals by chains that are willing to match the DAO’s contributions. Not only has Bob pledged funds in this proposal, but they have also allocated considerable Spice points toward the Uni v3 deployment. We should encourage other chains to do the same, and so we are voting for this proposal.\n\nOnchain: BoB Uniswap v3 Incentives Package\n\nSummary: Bob Chain requests approximately $380K from the DAO.\n\nRecommendation: For. GFX Labs generally supports proposals by chains that are willing to match the DAO’s contributions. Not only has Bob pledged funds in this proposal, but they have also allocated considerable Spice points toward the Uni v3 deployment. We should encourage other chains to do the same, and so we are voting for this proposal.\n\nGFXlabs\n\nApril 24, 2025, 6:30pm\n\n15\n\nUAC Renewal S4\n\nSummary: The UAC is requesting a total of ~$370K in UNI to continue operations for the rest of the year.\n\nRecommendation: For. The UAC continues to play an important role in the Uniswap DAO. We are more than happy to approve the request.\n\nApproved Budgets Rebalancing (S4)\n\nSummary: The UAC is requesting a $280K top-up.\n\nRecommendation: For. Abdullah’s forum post clearly summarized the current account and the need for the top-up.\n\nGFXlabs\n\nApril 29, 2025, 12:19am\n\n16\n\n[Temp Check/Revised] Treasury Delegation Round 2\n\nSummary: This is a revised proposal to renew the Treasury Delegation Program.\n\nRecommendation: For. Last time this was up for vote, we chose to vote Abstain.\n\nHowever, with more information regarding the timeline for the Unistaker and activation of the Fee Switch, we feel it’s pertinent to have this program continue until otherwise votes can be mobilized. Once the fee switch and Unistaker are activated, we could support ending the delegation program.\n\nGFXlabs\n\nMay 1, 2025, 2:04pm\n\n17\n\nEstablish Uniswap v4 Licensing Process\n\nSummary : Grant the UF access to deploy Uniswap v4 as they see fit.\n\nRecommendation : For. As Uniswap transitions from v3 to v4, upgrading how chain deployments are handled makes sense. From our point of view, this proposal is an easy operational improvement.\n\nGFXlabs\n\nMay 9, 2025, 8:02pm\n\n18\n\nOnchain: Approved Budgets Rebalancing (S4)\n\nSummary: The UAC is requesting a $280K top-up.\n\nRecommendation: For. Abdullah’s forum post clearly summarized the current account and the need for the top-up.\n\nOnchain: UAC Renewal S4\n\nSummary: The UAC is requesting a total of ~$370K in UNI to continue operations for the rest of the year.\n\nRecommendation: For. The UAC continues to play an important role in the Uniswap DAO. We are more than happy to approve the request.\n\nGFXlabs\n\nMay 27, 2025, 4:51pm\n\n19\n\nUniswap Accountability Committee S4 Elections\n\nSummary: The DAO needs to elect two new members to the UAC.\n\nRecommendation: We allocated 50% to Doo and 50% to Jordan. There are several qualified candidates, which speaks to the quality of the Uniswap DAO. We voted for Doo because of his longterm thoughtful participation in the DAO. We voted for Jordan after having a robust conversation about improving delegation and UNI token holder engagement, which we believe is a critical initiative that the DAO should pursue.\n\nGFXlabs\n\nJune 9, 2025, 5:51pm\n\n20\n\nScaling V4 and Supporting Unichain\n\nSummary: Provide a grant to GFX Labs to support Oku’s growth to Unichain and Uniswap V4.\n\nRecommendation: For. See the proposal for the full rationale.\n\nnext page →\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nAtiselsts.eth Delegate Platform\n\nDelegation Pitch\n\n32\n\n4670\n\nJuly 9, 2026\n\nTané Delegate Platform\n\nDelegation Pitch\n\n59\n\n2404\n\nMarch 9, 2026\n\nStableLab Delegate Platform\n\nDelegation Pitch\n\n103\n\n8892\n\nDecember 30, 2025\n\nFranklinDAO (Prev. Penn Blockchain) Delegate Platform\n\nDelegation Pitch\n\n42\n\n8463\n\nSeptember 7, 2025\n\n404 DAO Delegate Platform\n\nDelegation Pitch\n\n39\n\n3283\n\nJanuary 13, 2026","tokens":8667,"crawled_at":1791193739623}
+{"id":10284,"url":"https://gov.uniswap.org/t/deploy-uniswap-v3-on-avalanche/20587","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Deploy Uniswap v3 on Avalanche - Requests for Comment - Uniswap Governance","text":"Deploy Uniswap v3 on Avalanche\n\nRequests for Comment\n\nAbdullahUmar\n\nFebruary 25, 2023, 12:35am\n\n1\n\nWe Blockchain at Michigan are submitting this proposal for initiating Uniswap v3 deployment on the Avalanche blockchain. With the BSL expiring on April 1st, the Uniswap Foundation has stated the importance of Uniswap v3 expansion to popular EVM chains. Establishing Uniswap on alt L1s–and not just on Ethereum L2s–is vital for establishing a robust, multichain future. After consulting with the Ava Labs team, we believe that this is a crucial and opportune time for Uniswap to expand to Avalanche’s growing ecosystem.\n\nProposal Motivation\n\nThe primary urgency behind this proposal is the upcoming BSL expiration on April 1st. As soon as the license expires, all entities will have the legal right to duplicate Uniswap v3 and utilize the forked code for commercial purposes. Invariably, large chains like Avalanche will see a rapid influx of v3 copycats, which will dilute the markets on those respective chains. It is therefore imperative for Uniswap v3 to get ahead of the competitors by launching on large chains before duplicates arise. Trader Joe v2, the current leading DEX on Avalanche, did $92.45M of volume in the past 24 hours (Feb 23)–indicative of the demand for a concentrated liquidity AMM. Due to the continual growth of the Avalanche ecosystem, along with the liquidity present on the platform, we believe that this proposal be enacted as soon as possible to ensure that Uniswap establishes a foothold in the Avalanche DEX market.\n\nWe realize that beyond the chain of deployment, the community must also consider the required cross-chain messaging protocol. Although the DAO previously coalesced to utilize Wormhole for the BNB Chain deployment, we believe that such a decision should not set a precedent for bridge selection. A vendor lock-in model would prevent the further testing of equally renowned messaging protocols like LayerZero. A handful of delegates and tokenholders have also pioneered a more novel approach to governance messaging, where cross-chain governance relies not on a single bridge but simultaneously on a handful of bridges. Although we see the merits of a multi-bridge system, it will take time for this approach to garner attention and be fully vetted. The DAO can decide to opt into a multi bridge system in the future–but for an agile deployment that can be implemented in the present, we believe that LayerZero is the best solution.\n\nCurrent State of Avalanche\n\nAvalanche is a blockchain platform that utilizes three separate blockchains, the Platform Chain (P-Chain), Contract Chain (C-Chain), and Exchange Chain (X-Chain), to improve scalability and interoperability. These three chains compose a consortium of validators called the Primary Network, which is responsible for Avalanche’s security.\n\nScreen Shot 2023-02-25 at 1.03.44 AM1920×963 68.6 KB\n\nSource: Avalanche Docs\n\nAvalanche operates with the Avalanche consensus algorithm, which is designed to be more efficient than alternative consensus mechanisms and enables EVM-compatibility. The consensus mechanism checks validators’ transaction confirmations randomly by allowing all nodes to work in parallel, increasing the probability that a transaction is valid. The C-Chain leverages the Snowman consensus protocol, which mimics Avalanche consensus but is optimized for smart contract integration. Therefore, most Avalanche dAPP activity currently transpires on the C-Chain.\n\nIn comparison to other smart contract platforms, Avalanche touts 2-second time-to-finality, faster than any of its peers (ex. Ethereum finality is 10 minutes). Uniswap on Avalanche would thereby enhance the user experience for both application users and liquidity providers.\n\nAvalanche also allows for an unbounded number of validators without sacrificing block time. This allows for an increasing degree of decentralization over time. In Q4 2022, the platform’s Nakamoto coefficient increased from 30 to 32–surpassing most other L1s–and is poised to continue in an upward direction. Currently, there are 1,228 validators and over 233M AVAX tokens staked. The expanding validator set and staked AVAX tokens exemplify a robust L1.\n\nThe Avalanche architecture permits a high degree of scalability through its ecosystem of subnets. Similar to Ethereum’s L2s, subnets allow for outsourcing blockspace from the Primary Network to alternative blockchains. As demand increases for the C-Chain, many projects will opt out of the Primary Network by creating their own subnet. Application-specific blockchains can be launched under customized subnets, granting builders control over their development stack (subnets specify their own execution logic, fee regime, state, networking, and security). Large protocols that initially relied on the C-Chain, like DFK and StepNetwork, are now migrating to their individualized subnets. The increase in subnets furthers the security of Avalanche since each subnet’s validators must simultaneously secure the Primary Network by staking 2,000 AVAX tokens. Avalanche Foundation is prompting the creation of a robust subnet ecosystem through its $290M incentive program. On December 23, 2022, interoperability between subnets was enhanced via Avalanche Warp Messaging (AWM), allowing for cross-subnet data and asset transfer.\n\nScreen Shot 2023-02-25 at 1.07.37 AM1254×710 188 KB\n\nSource: Avax Docs\n\nIncreased application activity on the C-Chain and subnets presents Avalanche as an expanding ecosystem. At the time of writing, according to DeFi Llama, Avalanche holds over $950M of TVL across 281 different protocols.\n\nScreen Shot 2023-02-25 at 1.09.05 AM1692×768 127 KB\n\nSource: DeFi Llama\n\nSince launching in Q3 2020, Avalanche’s txn count has cumulatively increased to nearly 700M. Messari reported that between Nov 2021 - Nov 2022 alone, the network experienced YoY txn growth of 1,507%. Although daily active users remained relatively steady since Summer 2022, average daily transactions increased from ~1M to ~3M, indicating the emergence of power users. A reliable user base is imperative for a properly functioning Uniswap protocol. The presence of long-term liquidity provision would aid in bootstrapping individual subnets as well as making the C-Chain more robust.\n\nScreen Shot 2023-02-25 at 1.10.02 AM1688×940 94.7 KB\n\nSource: Messari State of Avalanche Q4 2022\n\nThe highest activity DEXs on Avalanche are Trader Joe (concentrated liquidity AMM), Platypus (stable swap AMM), and KyberSwap (concentrated liquidity DEX aggregator).\n\nScreen Shot 2023-02-25 at 1.10.54 AM1690×326 121 KB\n\nSource: DeFi Llama\n\nPost deployment, the most fierce competitor for Uni v3 will be Trader Joe. Since Trader Joe recently released a Uni v3-like, capital efficient AMM, Uniswap has an incentive to capture as much of Avalanche’s DEX market prior to Trader Joe v2 locking in a concrete user base. Plus, after the BSL expires in April, numerous Uni v3 forks will invariably launch on Avalanche. Therefore, to minimize Uniswap’s dilution in the Avalanche ecosystem, the DAO is incentivized to launch v3 as soon as possible.\n\nDue to Uniswap’s strong brand, it has the ability to capture market share from existing DEXs and attract liquidity from new users. A notable historical anecdote is Polygon. Once Uni v3 launched on Polygon, it quickly acquired market share from both Quickswap and Sushiswap. Although this experiment is yet to be tested on an alt L1, it is likely that a similar pattern will surface on Avalanche–although Trader Joe may present a higher degree of friction. Nonetheless, it is not necessary that the DEX competition will result in a zero-sum game and can favor both Trader Joe and Uniswap simultaneously.\n\nScreen Shot 2023-02-25 at 1.12.18 AM1132×676 144 KB\n\nSource: Dune Analytics @wanxin\n\nApart from DeFi developments, Avalanche has also made strides in other sectors like gaming, NFTs, and user adoption.\n\nNFT Progression:\n\nOpenSea launched natively on Avalanche in October 2022.\n\nThe NFT Minter application (run on Avalanche) became integrated with Shopify, allowing merchants to create, sell, and mint NFTs.\n\nJoePegs, an NFT marketplace built by Trader Joe, launched in Q2 2022. It has become the most active NFT marketplace on Avalanche and is responsible for onboarding over 50 NFT projects.\n\nGaming Progression:\n\nNumerous subnets dedicated exclusively to gaming are receiving increasing reception.\n\nThe DFK subnet generated 1-2 million txns per day in Q4 and increased unique active wallets from 1k to 5k.\n\nSwimmer also integrated Snake City and Crabada into its gaming subnet.\n\nCrypto Royale migrated from Harmony, and Monsterra launched from BNB Chain to the C-Chain.\n\nJapanese media company GREE partnered with Avalanche in October 2022 to build games on its subnets and aid in validating the Primary Network. They have already launched 12+ validators.\n\nUser Adoption:\n\nAva Labs enacted a handful of developments for Avalanche’s multichain wallet, Core. Fiat onramps have been added to Core using Coinbase Pay. Core Web allows for a seamless wallet browser extension for navigating the Avalanche ecosystem–and Core Mobile serves an identical purpose but on Android mobile devices, with iOS coming soon.\n\nFurther facilitation of each of these categories is enabled by a DEX like Uniswap. And in turn, Uniswap liquidity providers–and maybe token holders–will attain economic value from the protocol’s increased usage.\n\nSafety and Cross-Chain Governance\n\nLayerZero Overview\n\nWe propose using LayerZero, an omnichain bridging solution, to facilitate cross-chain message passing between Ethereum and Avalanche. LayerZero has pre-existing support for both Avalanche and Ethereum.\n\nThe first use case of Omnichain Fungible Token (OFT) transfer has been active for nearly 4 months on Avalanche. LayerZero allows Avalanche BTC (BTC.b) bridging between all LayerZero-supported chains (including Ethereum, BNB Chain, Avalanche C-Chain, Polygon, Arbitrum, Optimism, Fantom, Moonbeam), creating a composable, unified liquidity system for BTC. From the 25+ supported chains, two, DFK and Swimmer, are run as their own subnets. Apart from cross-chain asset transferring, LayerZero also supports arbitrary message passing–which includes governance communication between Uniswap on Ethereum to Avalanche.\n\nLayerZero is backed by the likes of a16z, Sequoia, Uniswap Labs, Coinbase, and numerous others–it is supported by thousands of cross-chain builders with over 2,000 contracts deployed on mainnet, ~700 unique applications, ~2M total messages, ~$5B transactional volume, and billions of dollars in TVL.\n\nIs the bridge secured by a trusted entity, by a multi sig, or a protocol/set of incentivized nodes?\n\nLayerZero endpoints rely on an architecture leveraging Ultra Light Nodes and two off-chain entities called oracles and relayers to securely relay messages between endpoints on a source and destination chain. The oracle is responsible for relaying block headers, and with the default LayerZero setup, will be handled by Chainlink. A transaction proof is sent using the relayer; the default relayer is operated by LayerZero. Hence, the security of the system relies on 2 entities. The primary assumption behind this setup is that the oracle and relayer remain independent at all times. Collusion between the entities would lead to a compromised system. Uniswap will have the option to operate one or both of these entities which would decrease the possibility of collusion; however, this would require the DAO to operate infrastructure. Ideally, Uniswap governance does not venture into infrastructure maintenance.\n\nIs the bridge secured by a trusted entity, by a multi sig, or a protocol/set of incentivized nodes?\n\nLayerZero leverages direct MPT validation construction of the source transaction and verifies the merkle inclusion proof directly on the destination chain via the protocol’s novel Ultra Light Node (ULN).\n\nIs it possible for a fraudulent message to be passed to the destination chain? If so, are there any recall mechanisms?\n\nMalicious message transmission is a possibility if there is a compromise of both the oracle and relayer sets. Both entities would have to agree to approve a fraudulent message together and against the same application. For example, the decentralized Chainlink DON would have to actively collude with the LayerZero Labs relayer at the same time to enable passing of a malicious message. If the application selects multiple oracles and multiple relayers, thereby pricing its security higher, fraudulent message passing would require more independent parties to be simultaneously compromised.\n\nWhat are the ramifications of fraud to the malicious actor?\n\nUnlike some other bridges, LayerZero does not pose an economic stake or bond to punish malicious actors via a slashing mechanism. Instead, if the default oracle-relayer configuration is compromised, then there is a reputational backlash that would beset LayerZero and Chainlink–since they are the entities responsible for the relayer and oracle, respectively. However, if Uniswap decides to control the messaging stack by running either the oracle or relayer, then Uniswap itself will have to answer for its shortcomings if there happens to be malicious activity.\n\nLayerZero is also designed to be censorship resistant. Oracles and Relayers cannot censor messages without censoring all messages due to the sequential nonce ordered enforcement on the receiving chain. As a result, if an attacker obtained control of the Uniswap-selected Oracles or Relayers, and succeeded in censoring a message, every subsequent message would also be censored and the vote would stop. Uniswap could then expediently resolve the issue by updating configurations and messaging would resume.\n\nHas the bridge code been audited? By a third party? What attack vectors and vulnerabilities were identified, if any? Have the identified vulnerabilities been remedied?\n\nImmutability is part and parcel to LayerZero’s infrastructure. Its smart contracts are not upgradable and therefore aren’t prone to bugs due to smart contract updates. Smart contract bugs is the predominant historical cause for bridge exploits, as was the case with Wormhole’s $300M and Nomad’s $190M hack in 2022. To ensure that the current LayerZero contracts are reliable enough to be set in stone and entirely independent from LayerZero Labs’ future involvements, the protocol has been audited 35+ times and reviewed at least 3+ times by the LayerZero Labs team.\n\nLayerZero is the only major cross-chain messaging protocol to have secured significant transaction volume (~$5B) over time without any exploit, compromise of key infrastructure, or loss of user funds. Additionally, LayerZero has the largest live bug bounty across the industry at up to $15M.\n\nFuture Bridge Alterations\n\nFollowing deployment, if Uniswap governance would like to switch to a different bridge setup, the DAO can do so with a future proposal. There are current ruminations regarding a multi bridge messaging setup–but that is too early to implement for this proposal. Much like the recent BNB Chain deployment proposal, we recommend utilizing a single bridge for the time being and integrating a more novel system later on after the BSL expiration.\n\nLicense Exemption\n\nWe are requesting an exemption via an Additional Use Grant (license change enacted via the ENS domain uniswap.eth) that would allow LayerZero to use the Licensed Work to deploy it on Avalanche, provided that the deployment is subject to Ethereum layer 1 Uniswap Protocol governance and control. Uniswap v3 will be deployed on Avalanche by LayerZero Labs through the “Deploy Uniswap V3 Script”. LayerZero Labs would be permitted to use subcontractors to do this work.\n\nTimeline\n\nOnce the on-chain governance proposal is completed, LayerZero Labs will deploy the Uniswap v3 smart contracts on the Avalanche C-Chain. Uniswap Labs will handle the front-end integration updates and include Avalanche to the auto router. Altogether, this deployment will take ~5 weeks to complete.\n\n9 Likes\n\nScaling V4 and Supporting Unichain\n\n[Temp Check] - Update Crosschain Governance Parameters for Avalanche, MegaETH, Soneium, and X Layer\n\nArana Digital Delegate Platform\n\nArana Digital Delegate Platform\n\nNomination and Election Process for the UNI-ARB Grant Program (UAGP) and Delegate Program (UADP)\n\nLdemeo88\n\nFebruary 25, 2023, 1:44am\n\n2\n\nHello all -\n\nMy name is Luigi D’Onorio DeMeo and I am the Head of DeFi at Ava Labs. We are very excited by this proposal from the University of Michigan. Ava Labs worked with and endorses this proposal to deploy Uniswap V3 on the Avalanche C Chain with LayerZero. As mentioned in the proposal, the timing of this proposal is key as the BSL is ending and we fear many low effort Uni v3 forks will enter the fray. The opportunity set for DEXs on Avalanche is unique - as new subnets come online with very large user sets, many are architecting them such that liquidity will remain on the C chain. With the addition of Avalanche Warp Messaging (AWM), this is only pronounced and provides a major opportunity for new DEX volumes, unique to Avalanche. We very much look forward to engaging with the Uniswap community!\n\n3 Likes\n\npaulsengh\n\nFebruary 26, 2023, 7:04pm\n\n3\n\nHello everyone!\n\nMy name is Paul Sengh, and I’m a contributor to Delta One (deltaone.xyz). Thank you to Abdullah and the team at Michigan for the well-written proposal.\n\nBootstrapping liquidity pools on a new venue is no easy feat, and these early network participants will need to be compensated fairly. Rather than putting this burden on the initial users of the new Uniswap deployment, the network should be bootstrapped––in true crypto fashion––through incentives from the other beneficiaries of the proposal (namely, Avalanche and Layer Zero). In return for the improvement in daily active users, transaction volumes, and reputation that Uniswap is providing to the other ecosystems, the DAO should request a fitting grant as a stipulation for the deployment.\n\nWe look forward to engaging with the Uniswap, Avalanche, and Layer Zero communities to get their thoughts.\n\n1 Like\n\nLdemeo88\n\nFebruary 27, 2023, 12:44pm\n\n4\n\nThank you for the comment @paulsengh. I will say from my perspective, the beauty of concentrated liquidity DEXs, especially those such as Uniswap that have a reputation and more battle tested code is that incentives are not typically required. For example, Trader Joe’s liquidity book on Avalanche has amassed $30m in TVL in a few months for a brand new concentrated liquidity DEX protocol with no incentives by them or Avalanche. By simply looking at the yields on Liquidity Book pools, it is clear there is demand for similar products on this network. To provide additional comfort, Ava Labs has been and is in touch with liquidity providers who will seed pools on a deployment.\n\n3 Likes\n\npaulsengh\n\nFebruary 27, 2023, 5:26pm\n\n5\n\nThe leverage capabilities from concentrating liquidity certainly can help individual LPs earn a larger share of fees compared to other LPs, but the “chicken or egg” problem still exists for the network at large––initial traders will be drawn to more liquid markets on Avalanche, and initial LPs will be dissuaded by the lack of trading fees. To be sure, it is very well possible that liquidity will be raised (as in your example of Trader Joe), but I am not convinced that those initial LPs will be profitable on a risk-adjusted basis. Given that those initial LPs will likely be excited Uniswap community members, I still urge the DAO to negotiate for incentives to bootstrap the network.\n\nIt certainly does help that Ava Labs is working with LPs to seed the pools, but given that this is a trustless environment, it’s hard to take comfort without more explicit guarantees from Ava Labs. Looking forward to hearing your thoughts, and shaping this proposal so we can see Uniswap V3 on Avalanche as soon as possible!\n\n2 Likes\n\nblueberryboy\n\nMarch 1, 2023, 8:56pm\n\n6\n\nThanks for submitting this in-depth proposal @AbdullahUmar\n\nIt’s a no-brainer to me: it makes total sense for Uniswap V3 to expand to blockchains with active DeFi ecosystems and less competition for concentrated liquidity AMMs before the license expires and fork season begins.\n\nYou briefly mention the possibility of implementing a multi-bridge system and I think that could be the right approach here. How open are you to using multiple bridges as opposed to only using LayerZero?\n\n1 Like\n\nAbdullahUmar\n\nMarch 1, 2023, 9:22pm\n\n7\n\nAppreciate the comment, @blueberryboy.\n\nYes, the possibility of implementing a multi-bridge system is ever growing; however, nothing in that vein has fully materialized. That structure is currently being reviewed, debated, and tested. No previous deployment has implemented such a standard. Due to the novel nature of a multi-bridge architecture, this proposal prompts Uni delegates and tokenholders to choose LayerZero as the messaging system because it’s simply the path of least resistance–not to mention LZ has worked actively with Avalanche in the past. The relationship is there. And LZ has a proven history of reliability due to active interrogations with a multitude of applications. If in the future the DAO selects to opt into a multi-bridge system, that’s its prerogative. But for now, LZ is the most seamless means forward.\n\nIf you’d like more context on the multi-bridge system, check out this forum page: Cross-Chain Bridge Assessment Process\n\n1 Like\n\nLdemeo88\n\nMarch 1, 2023, 9:40pm\n\n8\n\nThank you for the comment @blueberryboy . As far as I am concerned and Ava Labs in particular, we would not be opposed to other bridges being selected if the Uniswap community explicitly desired - whether that was Wormhole, Axelar, Synapse or others. We worked with LayerZero particularly on this proposal and also value them on their merits as well. As @AbdullahUmar mentioned, we also look forward to the multi-bridge system by the DAO.\n\nWormhole\n\nMarch 2, 2023, 6:23pm\n\n9\n\nThanks for the comments everyone. We appreciate @Ldemeo88 and the Avalanche community’s desire to work with the wishes of the Uniswap DAO. Avalanche is a thriving ecosystem and a prime candidate for a Uniswap V3 deployment. So, for the avoidance of doubt, we at Wormhole are excited to throw our hat in the ring here.\n\nTo comment on the landscape where this vote falls - we understand that this proposal comes on the back of a contentious vote for BNB along with the ongoing work to do a full evaluation of bridge providers.\n\nHowever, given the pending BSL expiry and recently having been voted in to service the BNB deployment, we believe that Wormhole is a strong contender as the most pragmatic choice until consensus is reached by the community.\n\nGiven that the BNB deployment is live and should be added to the UI within a week, we feel confident in Wormhole’s ability to deliver for the Uniswap and Avalanche communities.\n\nWe look forward to comments and questions!\n\n3 Likes\n\nkari\n\nMarch 6, 2023, 10:23am\n\n10\n\nHello everyone, Kari from MAP Protocol here. (MAP Protocol is the interoperable omnichain layer built upon ZK and light client)\n\nThanks @AbdullahUmar for putting the well-written proposal. Deploying Uniswap v3 on Avalanche will be a plus for a DEX product like Uniswap, especially with Avalanche’s star defi products such as traderjoe and gmx. And Just like @paulsengh mentioned, putting the burden of LP on initial users would not be fair and a better way should be bootstrapping the network.\n\nGreat to know that you’ve already had a bridge option for the deployment. If the DAO implemented the multi-bridge system, will that mean Avalanche will also consider other bridge options for the deployment?\n\n2 Likes\n\neek637\n\nMarch 6, 2023, 10:13pm\n\n11\n\nI hate to be a stick in the mud here, but we’ll be voting against this in its current form.\n\nI am on the record explaining Avantgarde’s vote in the Binance proposal. In that case, we believed that the benefits of getting an official deployment on that chain before the BSL expired outweighed the risks presented by doing so with a bridge that hadn’t been formally evaluated.\n\nHaving to make that evaluation at all was a wake up call that the DAO’s process for assessing bridges in cross-chain deployments was broken. In the aftermath of that vote, and the furious politicking that went on behind closed doors, the UF has tasked the newly-formed Bridge Assessment Committee with creating a framework for the community to make better-informed decisions on these issues going forward.\n\nIn the context of this proposal, and the Kava proposal, and the multitude of “Deploy on X Chain” proposals that are sure to pop up in the forum between now and April 1, we do not believe the “deploy before the bsl expires and worry about the bridge provider later” tradeoff still holds. While we still don’t believe there is a material risk to the protocol of deploying with Layer Zero, it will increase the burden of the inevitable clean up that we need to do when it comes time to unify the DAOs approach to cross chain messaging. And in the case of every chain/bridge combo we vote on between now and April 1, that technical debt is incurred without a corresponding upside - the BSL will expire before these deployments are pushed to production on the front end. (Having integrated with v3 so that Enzyme users can provide liquidity from their vaults, I am not convinced that there would be any meaningful contract-level liquidity provision from the drop. I would be happy to be proven wrong on that… but there’s been zero volume on Binance and the contracts were deployed three weeks ago).\n\nSaid more plainly - we do want to deploy to Avalanche (and to Kava, and probably to many other chains), but we believe that the costs (technical debt) outweigh the benefits (having an official deployment sometime soonish after the BSL expires). Additionally, voting yes to this proposal incentivizes other chains and bridge providers to make additional deployment proposals which will increase our technical debt which will make cleanup harder which will… you get the picture.\n\nWe would be supportive of granting Ava Labs an Additional Use Grant with no bridge specified and then running a Snapshot vote post-Bridge Assessment Committee to approve a bridge provider.\n\nAlso, as a side note, I just noticed that this proposal is to grant Layer Zero an additional use grant which, though the wording in the proposal is specific to avalanche, seems potentially problematic (not being a lawyer I’d appreciate if someone else who is or has legal counsel on hand to weigh in on that).\n\n1 Like\n\nAbdullahUmar\n\nMarch 6, 2023, 11:27pm\n\n12\n\nThank you for your comment, @kari. Liquidity bootstrapping is always a plus for any deployment but should be looked at in the context of the network. If the deployment is on a comparatively more robust chain like Avalanche, then the requirement for bootstrapping is less. Plus, the demand for a concentrated liquidity AMM is present on Avalanche–in fact, Trader Joe v2 is responsible for most of Avalanche’s present DEX activity. Ava Labs is also in close contact with market makers. Conversations will naturally transpire regarding liquidity on Avalanche post deployment.\n\nFor a seamless deployment, we are proposing just using LayerZero. If the DAO wants to reassess the active bridge in the future, that conversation is encouraged.\n\n2 Likes\n\nMAPO_MapProtocol\n\nMarch 7, 2023, 5:39am\n\n13\n\nThank you Kari for sharing with the Uni members here about MAP Protocol. As the omnichain layer for Web3, we envision a future where every chain can be connected seamlessly and users can use dApps just like the way they use Web2 apps – intuitive, easy, but more privacy-preserving. We also will plan to add Avalanche to our omnichain network to enable greater interoperability.\n\n1 Like\n\nhn_avax\n\nMarch 8, 2023, 2:27am\n\n14\n\nHello everyone, I’m one of the core contributors to BENQI, and I’m excited to have Uniswap deploy on Avalanche. Thanks everyone for sharing their thoughts on the proposal so far!\n\nAvantgarde’s suggestions seems to make the most sense to me thus far given the ongoing debate on both sides regarding the bridge. Is there a rush to decide on a bridge provider at this point? A decision by the Bridge Assessment Committee post deployment seems like the most prudent, and expedient, approach.\n\n1 Like\n\nDAOstrat.C\n\nMarch 8, 2023, 7:15pm\n\n15\n\nVoted in support of this proposal. First, thank you @AbdullahUmar, for bringing this proposal forward. As discussed through other deployments, Uniswap cross-chain provides users with a trusted medium for decentralized exchange. This vote also supports our long-standing position around protocol competitiveness.\n\nWith April 1 approaching, we do not see the BSL argument as a driving factor right now. Although the timing of this proposal intersects with the Cross Chain Bridge Committee’s work, Avalanche is a strong L1.\n\nWe do not see any impacts to protocol security and would like this conversation to continue.\n\nAs always, we support the bridging committee, community innovations like the MMA, and ongoing process discussions.\n\n1 Like\n\nGFXlabs\n\nMarch 9, 2023, 12:12am\n\n16\n\nHi Everyone,\n\nWhile GFX Labs supports further deployments, we will be abstaining from this vote and all deployments until the Bridge Commitee delivers their report. The committee is expected to deliver the report on the 27th. Given that the governance and deployment processes take over three weeks and the report is similarly three weeks away, it’s best to wait for the report and revisit this deployment and the several other chains we’re aware of who would also like a deployment of Uniswap v3.\n\n4 Likes\n\nPorter\n\nMarch 17, 2023, 2:36pm\n\n18\n\nWe voted for the Uniswap v3 deployment to Avalanche. Our primary reasoning coincides with the support from the Ava Labs team to proceed with a deployment due to time considerations with the BSL expiring. We fully support the bridge committee process, and we look forward to seeing their output, but we feel conducting the deployment with L0 and re-evaluating the bridge later based on a multi-bridge proposal, or the committee’s final analysis, is an equally viable option with a low degree of risk.\n\n4 Likes\n\n0xIryna\n\nApril 22, 2023, 12:41am\n\n19\n\nUniswap v3 contracts are deployed on Avalanche at the following addresses:\n\nContract\nAddress\n\nUniswapV3Factory\n\n0x740b1c1de25031C31FF4fC9A62f554A55cdC1baD\n\nMulticall2\n\n0x0139141Cd4Ee88dF3Cdb65881D411bAE271Ef0C2\n\nProxyAdmin\n\n0x9AdA7D7879214073F40183F3410F2b3f088c6381\n\nTickLens\n\n0xEB9fFC8bf81b4fFd11fb6A63a6B0f098c6e21950\n\nNFTDescriptor\n\n0x27Dd7eE7fE723e83Bf3612a75a034951fe299E99\n\nNonfungibleTokenPositionDescriptor\n\n0xe89B7C295d73FCCe88eF263F86e7310925DaEBAF\n\nDescriptorProxy\n\n0xE1f93a7cB6fFa2dB4F9d5A2FD43158A428993C09\n\nNonfungibleTokenPositionManager\n\n0x655C406EBFa14EE2006250925e54ec43AD184f8B\n\nV3Migrator\n\n0x44f5f1f5E452ea8d29C890E8F6e893fC0f1f0f97\n\nV3Staker\n\n0xCA9D0668C600c4dd07ca54Be1615FE5CDFd76Ac3\n\nQuoterV2\n\n0xbe0F5544EC67e9B3b2D979aaA43f18Fd87E6257F\n\nSwapRouter02\n\n0xbb00FF08d01D300023C629E8fFfFcb65A5a578cE\n\nOmnichainProposalSender is deployed on Ethereum and OmnichainGovernanceExecutor is deployed on Avalanche at the following addresses:\n\nContract\nAddress\n\nOmnichainProposalSender\n\n0xeb0BCF27D1Fb4b25e708fBB815c421Aeb51eA9fc\n\nOmnichainGovernanceExecutor\n\n0xeb0BCF27D1Fb4b25e708fBB815c421Aeb51eA9fc\n\n2 Likes\n\nDoo_StableLab\n\nAugust 25, 2023, 1:33pm\n\n20\n\nHello, the Deployment Accountability Committee has reviewed this proposal and found no specific commitment to support the Uniswap Ecosystem, and also no specific expectation from such deployment. And those “broad” expectations seem to be overall still valid (for example, Trader Joe’s TVL is almost 19 times larger than Uniswap’s TVL on Avalanche but the author is correct that Uniswap did “capture market share”)\n\n1 Like\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[RFC - Update] Deploy Uniswap v3 (1 / 0.3 / 0.05 / 0.01) on BNB Chain (Binance)\n\nRequests for Comment\n\n101\n\n45661\n\nJuly 22, 2026\n\n[RFC] Post-BSL Cross-chain Deployment Process & New Uniswap.eth Subdomain\n\nRequests for Comment\n\n7\n\n3895\n\nApril 7, 2023\n\nUF Bridge Recommendations\n\nGovernance-Meta\n\n0\n\n1593\n\nJune 15, 2023\n\nDeploy Uniswap v3 to Arbitrum Mainnet\n\nRequests for Comment\n\n48\n\n19120\n\nDecember 1, 2021\n\nDeploy Uniswap v3 on Moonbeam (2023)\n\nRequests for Comment\n\n16\n\n7749\n\nOctober 4, 2023","tokens":8113,"crawled_at":1791193757889}
+{"id":10285,"url":"https://docs.sui.io/getting-started/onboarding/get-coins","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Get SUI from Faucet | Sui Documentation","text":"To perform transactions on a Sui network, you need SUI tokens to pay for gasGasThe computational cost of execution and object storage for a transaction. and storage.\n\nFor applications on MainnetMainnetProduction network for live transactions and real-value assets., you must buy real SUI on exchanges like Coinbase, OKX, or Robinhood. Its value is determined by market factors such as supply and demand, network utility, and perceived value.\n\nBecause Mainnet tokens cost real money, development can be expensive. That's why Sui provides DevnetDevnetFor developing and testing new features. and TestnetTestnetStaging network for testing changes before production deployment. networks, which mirror Mainnet features and enable you to build and test safely for an affordable cost.\n\nimportant\nSUI tokens on Devnet and Testnet are free and hold no monetary value.\n\nYou can get free SUI tokens from the Sui faucetFaucetA service that provides free Testnet tokens., which lets you deploy and interact with smart contracts and objects on Devnet, Testnet, or a local network. There is no faucet for Mainnet.\n\nPrerequisites\n\nInstall the latest version of Sui.\n\nSet up your Sui account and CLI environment.\n\nClick to openCreate Sui account and setup CLI environment.\n$ sui client\n\nIf this is the first time running the sui client CLI tool, it asks you to provide a Sui full nodeFull nodeResponsible for validating blockchain activity. server URL (or press enter for the default Testnet), select an encryption scheme to generate an addressAddressA unique, anonymous identity on a blockchain network., and stores the configuration in a client.yaml file. For more information, refer to the Sui client CLI tutorial.\nIf this is not your first time running sui client, then you already have a client.yaml file in your local environment. If you'd like to create a new address for this tutorial, use the command:\n$ sui client new-address ed25519\n\nRequest SUI tokens from faucet​\n\nVisit the online faucet to request SUI tokens.\n\nThen, follow these steps:\n\nConnect your wallet or paste your wallet address in the address field. Get your wallet address in the CLI with the command sui client active-address.\n\nUse the network dropdown to select the correct network: Testnet, Devnet, or LocalnetLocalnetLocal network you can run on your own machine for optimized development.. Use the Testnet for most use cases before deploying to Mainnet for production. Learn more about the available networks and their differences.\n\nClick the Request SUI button.\n\nTo request more SUI, refresh your browser and click the Request SUI button again. The requests are rate limited, however, so too many requests results in a waiting period before you can request more tokens.\n\nCommunity faucets​\n\nYou can also use the following community-provided faucets to obtain SUI tokens:\n\nN1Stake faucet\n\nSuiLearn faucet\n\nThese faucets have their own separate limits, such as one request per day or one request every few hours.\n\nVerify token balance​\n\nTo check your balance of SUI tokens and confirm you received some from the faucet, use the command:\n\n$ sui client balance\n\nAlternatively, use a Sui Explorer such as SuiVision or SuiScan to check the SUI token balance of an address.\n\nYou should have a balance of SUI tokens:\n\n╭────────────────────────────────────────────╮\n│ Balance of coins owned by this address │\n├────────────────────────────────────────────┤\n│ ╭────────────────────────────────────────╮ │\n│ │ coin balance (raw) balance │ │\n│ ├────────────────────────────────────────┤ │\n│ │ Sui 56804696124 0.50 SUI │ │\n│ ╰────────────────────────────────────────╯ │\n╰────────────────────────────────────────────╯\n\nIf you do not have a balance, repeat the request SUI tokens from faucet steps, or use an alternative faucet method.\n\nReturn unused Testnet SUI​\n\nThe faucet drains from a finite pool of SUI. If the pool empties, it disrupts faucet service for the rest of the community. To help ensure this doesn't happen, you can use the online faucet to return your unused SUI to the Testnet pool. You cannot return SUI to the Devnet or Localnet pools.\n\nThere are two ways to return unused Testnet SUI tokens:\n\nConnect your wallet to the online faucet, and click the Return tokens to faucet button. Approve the transactionTransactionA number of commands that execute on inputs to define the result of the transaction. using your wallet, and the faucet returns your SUI tokens to the pool.\n\nIf you prefer not to connect your wallet, send the tokens to the address 0x7a9d19d4c210663926eb549da59a54e25777fef63161bfccda08277b58b4212e through a separate transaction.\n\nAlternative methods for getting SUI tokens​\n\nIf you need an alternative method to get SUI tokens for deployment on Testnet or Devnet, you have several options.\n\ntip\nEvery method to obtain SUI tokens for Testnet and Devnet is rate limited. If you need a large amount of SUI tokens, use a local network.\n\nDiscord\ncURL\nTypeScript SDK\n\nJoin Discord.\n\nIf you try to join the Sui Discord channel using a newly created Discord account, you might need to wait a few days for validation.\n\nRequest SUI tokens in the Sui #devnet-faucet or #testnet-faucet Discord channels. Send the following message to the channel, replacing <YOUR SUI ADDRESS> with your client address:\n\n!faucet <YOUR SUI ADDRESS>\n\nUse the following cURL commands to set console variables and request tokens directly from the faucet server. Set NETWORK to either testnet or devnet.\n$ ADDRESS=$(sui client active-address)\n$ NETWORK=testnet\n$ curl --location --request POST \"https://faucet.${NETWORK}.sui.io/v2/gas\" \\\n--header \"Content-Type: application/json\" \\\n--data-raw \"{\n\\\"FixedAmountRequest\\\": {\n\\\"recipient\\\": \\\"${ADDRESS}\\\"\n}\n}\"\n\nIf you're working with a local network, replace \"https://faucet.${NETWORK}.sui.io/v2/gas\" with the appropriate value based on which packagePackageSmart contracts on Sui. runs your network:\n\nsui-faucet: http://127.0.0.1:5003/gas\n\nsui: http://127.0.0.1:9123/gas\n\nYou can access the faucet using the Sui TypeScript SDK.\nimport { getFaucetHost, requestSuiFromFaucetV2 } from '@mysten/sui/faucet';\n\n// get tokens from the Devnet faucet server\nawait requestSuiFromFaucetV2({\n// connect to Devnet\nhost: getFaucetHost('devnet'),\nrecipient: '<YOUR SUI ADDRESS>',\n});\n\nSUI tokens on a local network​\n\nIf you are running a local Sui network, you can get SUI tokens from your local faucet. See the Connect to a Local Network topic for details.\n\nAfter you have SUI tokens, you're ready to build and publish your first package.\n\nNext steps\n\nHello, World!\n\nClone and build the \"Hello, World!\" project.\n\nRequest SUI tokens from faucetCommunity faucets\nVerify token balance\nReturn unused Testnet SUI\n\nAlternative methods for getting SUI tokens\nSUI tokens on a local network\n\nWas this page helpful?","tokens":1697,"crawled_at":1791193758295}
+{"id":10286,"url":"https://www.metaplex.com/docs/smart-contracts/core/what-is-an-asset","domain":"www.metaplex.com","chapter":"docs","title":"What is a Core Asset | Metaplex Core","text":"This page explains what a Core Asset is and how it differs from traditional Solana NFTs. Understand the account structure, collection relationships, and metadata storage.\nKey Concepts\nSingle-account model: Core Assets store ownership within the Asset account itself\nNo token accounts: Unlike SPL tokens, Core doesn't require Associated Token Accounts\nCollection membership: Assets can belong to Collections via the updateAuthority field\nOff-chain metadata: A URI points to JSON metadata (permanent storage like Arweave/IPFS is recommended)\n\nSummary\nA Core Asset is a single Solana account that represents an NFT. Unlike Token Metadata (which requires 3+ accounts), Core stores all essential data in one account: owner, name, URI, and update authority. This makes Core Assets ~80% cheaper and simpler to work with.\nOverview\nSetting itself apart from existing Asset programs, like Solana’s Token program, Metaplex Core and Core Assets (sometimes referred to as Core NFT Assets) do not rely on multiple accounts, like Associated Token Accounts. Instead, Core Assets store the relationship between a wallet and the \"mint\" account within the asset itself.\n\nWallet Account\n\nOwner: System Program\n\nSomeone's wallet.\n\nAsset Account\n\nOwner: Core Program\n\nStores information about the\nasset, including the owner\n\nReact Flow\nPress enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.\nPress enter or space to select an edge. You can then press delete to remove it or escape to cancel.\n\nThe Core Asset Account\nThe Core Asset account represents the bare minimum data for a digital asset. This structure provides an unopinionated blockchain primitive for onchain ownership.\n\nWallet Account\n\nOwner: System Program\n\nAsset Account\n\nOwner: Core Program\n\nKey = Asset\n\nOwner\n\nUpdate Authority\n\nName\n\nURI\n\nReact Flow\nPress enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.\nPress enter or space to select an edge. You can then press delete to remove it or escape to cancel.\n\nIs my Asset in a Collection?\nMPL Core Assets can belong to collections. The updateAuthority field in the MPL Core Asset data provides two duties, either to report the update authority of the Asset, or to provide the publicKey of the MPL Core Collection to which it belongs. When accessing the updateAuthority field either directly via the asset, or via the collectionAddress helper of the MPL Core Asset, the returning result will be one of the following outcomes: Collection The asset belongs to the collection at the given address.\nCreate Asset\n\n{\n\n__kind: 'Collection'\n\nfields: [PublicKey]\n\n}\n\nimport { fetchAssetV1 } from '@metaplex-foundation/mpl-core'\n\nconst asset = await fetchAssetV1(umi, assetAddress.publicKey)\n\nconst collectionId = collectionAddress(asset)\n\nconsole.log({collectionId})\n\nconsole.log({asset})\n\n// log\n\ncollection: '2222222222222222222222222222222'\n\nasset: {\n\nkey: AssetV1,\n\nowner: \"11111111111111111111111111111111\",\n\nupdateAuthority: {\n\ntype: 'Collection',\n\naddress: '2222222222222222222222222222222'\n\n},\n\nname: \"My Core Asset\",\n\nuri: \"https://example.com/metadata.json\",\n\n...\n\n}\n\nAddress The asset has an update authority set and does not belong to a collection.\nCreate Asset\n\nimport { fetchAssetV1 } from '@metaplex-foundation/mpl-core'\n\nconst asset = await fetchAssetV1(umi, assetAddress.publicKey)\n\nconst collectionId = collectionAddress(asset)\n\nconsole.log({collectionId})\n\nconsole.log({asset})\n\n// log\n\ncollectionId: undefined\n\nasset: {\n\nkey: AssetV1,\n\nowner: \"11111111111111111111111111111111\",\n\nupdateAuthority: {\n\ntype: 'Address',\n\naddress: '2222222222222222222222222222222'\n\n}\n\nname: \"My Core Asset\",\n\nuri: \"https://example.com/metadata.json\",\n\n...\n\n}\n\nNone The asset has no update authority set.\nCreate Asset\n\nimport { fetchAssetV1 } from '@metaplex-foundation/mpl-core'\n\nconst asset = await fetchAssetV1(umi, assetAddress.publicKey)\n\nconst collectionId = collectionAddress(asset)\n\nconsole.log({collectionId})\n\nconsole.log({asset})\n\n// log\n\ncollectionId: undefined\n\nasset: {\n\nkey: AssetV1,\n\nowner: \"11111111111111111111111111111111\",\n\nupdateAuthority: {\n\ntype: 'None',\n\n},\n\nname: \"My Core Asset\",\n\nuri: \"https://example.com/metadata.json\",\n\n}\n\nOff Chain Metadata\nOne important attribute of the Asset Account is the URI attribute that points to a JSON file off-chain. This is used to safely provide additional data whilst not being constrained by the fees involved in storing onchain data. That JSON file follows a certain standard that anyone can use to find useful information on tokens. Off Chain Metadata can be stored at any publicly accessible location. Popular places to host your json files include;\nArweave\nNFT.Storage/IPFS\nAmazon AWS S3/Google Cloud\n\nWallet Account\n\nOwner: System Program\n\nAsset Account\n\nOwner: Core Program\n\nKey = Asset\n\nOwner\n\nUpdate Authority\n\nName\n\nURI\n\nOff-chain\nJSON Metadata\n\nName\n\nDescription\n\nImage\n\nAnimated URL\n\nAttributes\n\n...\n\nReact Flow\nPress enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.\nPress enter or space to select an edge. You can then press delete to remove it or escape to cancel.\n\nFieldTypeDescription\nname\nstring\nName of the asset.\n\ndescription\nstring\nDescription of the asset.\n\nimage\nstring\nURI pointing to the asset's logo.\n\nanimation_url\nstring\nURI pointing to the asset's animation.\n\nexternal_url\nstring\nURI pointing to an external URL defining the asset — e.g. the game's main site.\n\nattributes\narray\nArray of attributes defining the characteristics of the asset.trait_type (string): The type of attribute.\nvalue (string): The value for that attribute.\n\nproperties\nobject\nAdditional properties that define the asset.files (array): Additional files to include with the asset.uri (string): The file's URI.\ntype (string): The file's type. E.g. image/png, video/mp4, etc.\ncdn (boolean, optional): Whether the file is served from a CDN.\n\ncategory (string): A media category for the asset. E.g. video, image, etc.\n\nNote that, this JSON file can be stored using a permanent storage solution such as Arweave to ensure it cannot be updated. Additionally, one can set the Update Authority field to None to make it immutable and, therefore, forbid the URI and Name attributes to ever be changed. Using this combination, we can guarantee the immutability of the off-chain JSON file.\nFAQ\nHow is Core different from Token Metadata NFTs?\nToken Metadata requires 3+ accounts (mint, metadata, token account). Core uses a single account that stores owner and metadata together. This makes Core ~80% cheaper and faster to create.\nWhat data is stored on-chain vs off-chain?\nOn-chain: owner, name, URI, update authority, plugins. Off-chain (at the URI): description, image, attributes, animation URL, and other extended metadata.\nCan I convert a Token Metadata NFT to Core?\nNot directly. Core and Token Metadata are separate standards. You would need to burn the old NFT and mint a new Core Asset. Some migration tools exist to help with this process.\nIs Core compatible with existing NFT marketplaces?\nMost major Solana marketplaces support Core Assets. Check Ecosystem Support for the current list of compatible platforms.\nWhat happens if the off-chain metadata goes offline?\nThe Asset still exists on-chain with its name and URI, but the image and off-chain attributes won't be accessible. On-chain attributes (via the Attributes plugin) remain accessible. Use permanent storage (Arweave, IPFS with pinning) to prevent this.\nGlossary\nTermDefinition\nAsset\nA single Core account representing an NFT\n\nOwner\nThe wallet that currently owns the Asset\n\nUpdate Authority\nThe account authorized to modify Asset metadata\n\nURI\nURL pointing to off-chain JSON metadata\n\nCollection\nA Core account that groups related Assets\n\nKey\nAccount discriminator identifying the account type\n\nseq\nSequence number used for compression indexing\n\nAsset Signer PDA\nA separate address derived from an Asset that acts as the Asset's wallet for SOL and tokens","tokens":2029,"crawled_at":1791193794633}
+{"id":10287,"url":"https://docs.ethers.org/v6/api/abi","domain":"docs.ethers.org","chapter":"developer_specs","title":"","text":"ethers\n6.17.0\n\nDOCUMENTATION\nGetting Started\nEthereum Basics\nApplication Programming Interface\nPollingBlockTagSubscriber\nApplication Binary Interface\nResult\nInterfaces\nTyped Values\nABI Encoding\nAddresses\nConstants\nContracts\nCryptographic Functions\nHashing Utilities\nProviders\nTransactions\nUtilities\nWallets\nWordlists\nCookbook\nMigrating from v5\nContributions and Hacking\nLicense and Copyright\n\nSingle Page\n\nDocumentation »API »Application Binary Interface\nApplication Binary Interface\nThe Application Binary Interface (ABI) describes how method input parameters should be encoded, their results decoded, and how to decode events and errors.\nSee About ABIs for more details how they are used.\n\nFUNCTIONS\n<src>checkResultErrors(result: Result)⇒ Array< { error: Error , path: Array< string | number > } >\nReturns all errors found in a Result.\nSince certain errors encountered when creating a Result do not impact the ability to continue parsing data, they are deferred until they are actually accessed. Hence a faulty string in an Event that is never used does not impact the program flow.\nHowever, sometimes it may be useful to access, identify or validate correctness of a Result.\n\n<src>decodeBytes32String(bytes: BytesLike)⇒ string\nEncodes the Bytes32-encoded bytes into a string.\n\n<src>encodeBytes32String(text: string)⇒ string\nEncodes text as a Bytes32 string.\n\nclass Result\nA Result is a sub-class of Array, which allows accessing any of its values either positionally by its index or, if keys are provided by its name.\n\nCREATING INSTANCES\n<src>Result.fromItems(items: Array< any >, keys?: Array< null | string >)⇒ Result\nCreates a new Result for items with each entry also accessible by its corresponding name in keys.\n\nMETHODS\n<src>result.getValue(name: string)⇒ any\nReturns the value for name.\nSince it is possible to have a key whose name conflicts with a method on a Result or its superclass Array, or any JavaScript keyword, this ensures all named values are still accessible by name.\n\n<src>result.toArray(deep?: boolean)⇒ Array< any >\nReturns the Result as a normal Array. If deep, any children which are Result objects are also converted to a normal Array.\nThis will throw if there are any outstanding deferred errors.\n\n<src>result.toObject(deep?: boolean)⇒ Record< string, any >\nReturns the Result as an Object with each name-value pair. If deep, any children which are Result objects are also converted to an Object.\nThis will throw if any value is unnamed, or if there are any outstanding deferred errors.\n\nInterfaces\nThe Interface class is a low-level class that accepts an ABI and provides all the necessary functionality to encode and decode paramaters to and results from methods, events and errors.\nIt also provides several convenience methods to automatically search and find matching transactions and events to parse them.\n\nTYPES\n<src>InterfaceAbi⇒ string | ReadonlyArray< Fragment | JsonFragment | string >\nAn InterfaceAbi may be any supported ABI format.\nA string is expected to be a JSON string, which will be parsed using JSON.parse. This means that the value must be a valid JSON string, with no stray commas, etc.\nAn array may contain any combination of:\n\nHuman-Readable fragments\nParsed JSON fragment\nFragment instances\n\nA Human-Readable Fragment is a string which resembles a Solidity signature and is introduced in this blog entry. For example, function balanceOf(address) view returns (uint).\nA Parsed JSON Fragment is a JavaScript Object desribed in the Solidity documentation.\n\nclass ErrorDescription\nWhen using the interface.parseError to automatically match an error for a call result for parsing, an ErrorDescription is returned.\n\nPROPERTIES\n<src>errorDescription.args⇒ Resultread-only\nThe arguments passed to the Error with revert.\n\n<src>errorDescription.fragment⇒ ErrorFragmentread-only\nThe matching fragment.\n\n<src>errorDescription.name⇒ stringread-only\nThe name of the Error.\n\n<src>errorDescription.selector⇒ stringread-only\nThe selector for the Error.\n\n<src>errorDescription.signature⇒ stringread-only\nThe full Error signature.\n\nclass Indexed\nAn Indexed is used as a value when a value that does not fit within a topic (i.e. not a fixed-length, 32-byte type). It is the keccak256 of the value, and used for types such as arrays, tuples, bytes and strings.\n\nPROPERTIES\n<src>indexed.hash⇒ null | stringread-only\nThe keccak256 of the value logged.\n\nSTATIC METHODS\n<src>Indexed.isIndexed(value: any)⇒ boolean\nReturns true if value is an Indexed.\nThis provides a Type Guard for property access.\n\nclass Interface\nAn Interface abstracts many of the low-level details for encoding and decoding the data on the blockchain.\nAn ABI provides information on how to encode data to send to a Contract, how to decode the results and events and how to interpret revert errors.\nThe ABI can be specified by any supported format.\n\nPROPERTIES\n<src>interface.deploy⇒ ConstructorFragmentread-only\nThe Contract constructor.\n\n<src>interface.fallback⇒ null | FallbackFragmentread-only\nThe Fallback method, if any.\n\n<src>interface.fragments⇒ ReadonlyArray< Fragment >read-only\nAll the Contract ABI members (i.e. methods, events, errors, etc).\n\n<src>interface.receive⇒ booleanread-only\nIf receiving ether is supported.\n\nCREATING INSTANCES\n<src>new Interface(fragments: InterfaceAbi)\nCreate a new Interface for the fragments.\n\n<src>Interface.from(value: InterfaceAbi | Interface)⇒ Interface\nCreates a new Interface from the ABI value.\nThe value may be provided as an existing Interface object, a JSON-encoded ABI or any Human-Readable ABI format.\n\nMETHODS\n<src>interface._decodeParams(params: ReadonlyArray< ParamType >, data: BytesLike)⇒ Result\n\n<src>interface._encodeParams(params: ReadonlyArray< ParamType >, values: ReadonlyArray< any >)⇒ string\n\n<src>interface.decodeErrorResult(fragment: ErrorFragment | string, data: BytesLike)⇒ Result\nDecodes the result data (e.g. from an eth_call) for the specified error (see getError for valid values for key).\nMost developers should prefer the parseCallResult method instead, which will automatically detect a CALL_EXCEPTION and throw the corresponding error.\n\n<src>interface.decodeEventLog(fragment: EventFragment | string, data: BytesLike, topics?: ReadonlyArray< string >)⇒ Result\n\n<src>interface.decodeFunctionData(fragment: FunctionFragment | string, data: BytesLike)⇒ Result\nDecodes the data from a transaction tx.data for the function specified (see getFunction for valid values for fragment).\nMost developers should prefer the parseTransaction method instead, which will automatically detect the fragment.\n\n<src>interface.decodeFunctionResult(fragment: FunctionFragment | string, data: BytesLike)⇒ Result\nDecodes the result data (e.g. from an eth_call) for the specified function (see getFunction for valid values for key).\nMost developers should prefer the parseCallResult method instead, which will automatically detect a CALL_EXCEPTION and throw the corresponding error.\n\n<src>interface.encodeDeploy(values?: ReadonlyArray< any >)⇒ string\nEncodes a tx.data object for deploying the Contract with the values as the constructor arguments.\n\n<src>interface.encodeErrorResult(fragment: ErrorFragment | string, values?: ReadonlyArray< any >)⇒ string\nEncodes the transaction revert data for a call result that reverted from the the Contract with the sepcified error (see getError for valid values for fragment) with the values.\nThis is generally not used by most developers, unless trying to mock a result from a Contract.\n\n<src>interface.encodeEventLog(fragment: EventFragment | string, values: ReadonlyArray< any >)⇒ { data: string , topics: Array< string > }\n\n<src>interface.encodeFilterTopics(fragment: EventFragment | string, values: ReadonlyArray< any >)⇒ Array< null | string | Array< string > >\n\n<src>interface.encodeFunctionData(fragment: FunctionFragment | string, values?: ReadonlyArray< any >)⇒ string\nEncodes the tx.data for a transaction that calls the function specified (see getFunction for valid values for fragment) with the values.\n\n<src>interface.encodeFunctionResult(fragment: FunctionFragment | string, values?: ReadonlyArray< any >)⇒ string\nEncodes the result data (e.g. from an eth_call) for the specified function (see getFunction for valid values for fragment) with values.\nThis is generally not used by most developers, unless trying to mock a result from a Contract.\n\n<src>interface.forEachError(callback: (func: ErrorFragment, index: number) => void)⇒ void\nIterate over all errors, calling callback, sorted by their name.\n\n<src>interface.forEachEvent(callback: (func: EventFragment, index: number) => void)⇒ void\nIterate over all events, calling callback, sorted by their name.\n\n<src>interface.forEachFunction(callback: (func: FunctionFragment, index: number) => void)⇒ void\nIterate over all functions, calling callback, sorted by their name.\n\n<src>interface.format(minimal?: boolean)⇒ Array< string >\nReturns the entire Human-Readable ABI, as an array of signatures, optionally as minimal strings, which removes parameter names and unneceesary spaces.\n\n<src>interface.formatJson()⇒ string\nReturn the JSON-encoded ABI. This is the format Solidiy returns.\n\n<src>interface.getAbiCoder()⇒ AbiCoder\nThe ABI coder that will be used to encode and decode binary data.\n\n<src>interface.getError(key: string, values?: Array< any | Typed >)⇒ null | ErrorFragment\nGet the ErrorFragment for key, which may be an error selector, error name or error signature that belongs to the ABI.\nIf values is provided, it will use the Typed API to handle ambiguous cases where multiple errors match by name.\nIf the key and values do not refine to a single error in the ABI, this will throw.\n\n<src>interface.getEvent(key: string, values?: Array< any | Typed >)⇒ null | EventFragment\nGet the EventFragment for key, which may be a topic hash, event name or event signature that belongs to the ABI.\nIf values is provided, it will use the Typed API to handle ambiguous cases where multiple events match by name.\nIf the key and values do not refine to a single event in the ABI, this will throw.\n\n<src>interface.getEventName(key: string)⇒ string\nGet the event name for key, which may be a topic hash, event name or event signature that belongs to the ABI.\n\n<src>interface.getFunction(key: string, values?: Array< any | Typed >)⇒ null | FunctionFragment\nGet the FunctionFragment for key, which may be a function selector, function name or function signature that belongs to the ABI.\nIf values is provided, it will use the Typed API to handle ambiguous cases where multiple functions match by name.\nIf the key and values do not refine to a single function in the ABI, this will throw.\n\n<src>interface.getFunctionName(key: string)⇒ string\nGet the function name for key, which may be a function selector, function name or function signature that belongs to the ABI.\n\n<src>interface.hasEvent(key: string)⇒ boolean\nReturns true if key (an event topic hash, event name or event signature) is present in the ABI.\nIn the case of an event name, the name may be ambiguous, so accessing the EventFragment may require refinement.\n\n<src>interface.hasFunction(key: string)⇒ boolean\nReturns true if key (a function selector, function name or function signature) is present in the ABI.\nIn the case of a function name, the name may be ambiguous, so accessing the FunctionFragment may require refinement.\n\n<src>interface.makeError(data: BytesLike, tx: CallExceptionTransaction)⇒ CallExceptionError\n\n<src>interface.parseCallResult(data: BytesLike)⇒ Result\n\n<src>interface.parseError(data: BytesLike)⇒ null | ErrorDescription\nParses a revert data, finding the matching error and extracts the parameter values along with other useful error details.\nIf the matching error cannot be found, returns null.\n\n<src>interface.parseLog(log: { data: string , topics: ReadonlyArray< string > })⇒ null | LogDescription\nParses a receipt log, finding the matching event and extracts the parameter values along with other useful event details.\nIf the matching event cannot be found, returns null.\n\n<src>interface.parseTransaction(tx: { data: string , value?: BigNumberish })⇒ null | TransactionDescription\nParses a transaction, finding the matching function and extracts the parameter values along with other useful function details.\nIf the matching function cannot be found, return null.\n\nclass LogDescription\nWhen using the interface.parseLog to automatically match a Log to its event for parsing, a LogDescription is returned.\n\nPROPERTIES\n<src>logDescription.args⇒ Resultread-only\nThe arguments passed into the Event with emit.\n\n<src>logDescription.fragment⇒ EventFragmentread-only\nThe matching fragment for the topic0.\n\n<src>logDescription.name⇒ stringread-only\nThe name of the Event.\n\n<src>logDescription.signature⇒ stringread-only\nThe full Event signature.\n\n<src>logDescription.topic⇒ stringread-only\nThe topic hash for the Event.\n\nclass TransactionDescription\nWhen using the interface.parseTransaction to automatically match a transaction data to its function for parsing, a TransactionDescription is returned.\n\nPROPERTIES\n<src>transactionDescription.args⇒ Resultread-only\nThe arguments passed to the Function from the transaction data.\n\n<src>transactionDescription.fragment⇒ FunctionFragmentread-only\nThe matching fragment from the transaction data.\n\n<src>transactionDescription.name⇒ stringread-only\nThe name of the Function from the transaction data.\n\n<src>transactionDescription.selector⇒ stringread-only\nThe selector for the Function from the transaction data.\n\n<src>transactionDescription.signature⇒ stringread-only\nThe full Function signature from the transaction data.\n\n<src>transactionDescription.value⇒ bigintread-only\nThe value (in wei) from the transaction.\n\nTyped Values\nA Typed object allows a value to have its type explicitly specified.\nFor example, in Solidity, the value 45 could represent a uint8 or a uint256. The value 0x1234 could represent a bytes2 or bytes.\nSince JavaScript has no meaningful way to explicitly inform any APIs which what the type is, this allows transparent interoperation with Soldity.\n\nclass Typed\nThe Typed class to wrap values providing explicit type information.\n\nPROPERTIES\n<src>typed.arrayLength⇒ null | numberread-only\nReturns the length of the array type or -1 if it is dynamic.\nThrows if the type is not an array.\n\n<src>typed.tupleName⇒ null | stringread-only\nReturns the tuple name, if this is a tuple. Throws otherwise.\n\n<src>typed.type⇒ stringread-only\nThe type, as a Solidity-compatible type.\n\n<src>typed.value⇒ anyread-only\nThe actual value.\n\nCREATING INSTANCES\n<src>Typed.address(v: string | Addressable)⇒ Typed\nReturn a new address type for v.\n\n<src>Typed.array(v: Array< any | Typed >, dynamic?: null | boolean)⇒ Typed\nReturn a new array type for v, allowing dynamic length.\n\n<src>Typed.bool(v: any)⇒ Typed\nReturn a new bool type for v.\n\n<src>Typed.bytes(v: BytesLike)⇒ Typed\nReturn a new bytes type for v.\n\n<src>Typed.bytes1(v: BytesLike)⇒ Typed\nReturn a new bytes1 type for v.\n\n<src>Typed.bytes10(v: BytesLike)⇒ Typed\nReturn a new bytes10 type for v.\n\n<src>Typed.bytes11(v: BytesLike)⇒ Typed\nReturn a new bytes11 type for v.\n\n<src>Typed.bytes12(v: BytesLike)⇒ Typed\nReturn a new bytes12 type for v.\n\n<src>Typed.bytes13(v: BytesLike)⇒ Typed\nReturn a new bytes13 type for v.\n\n<src>Typed.bytes14(v: BytesLike)⇒ Typed\nReturn a new bytes14 type for v.\n\n<src>Typed.bytes15(v: BytesLike)⇒ Typed\nReturn a new bytes15 type for v.\n\n<src>Typed.bytes16(v: BytesLike)⇒ Typed\nReturn a new bytes16 type for v.\n\n<src>Typed.bytes17(v: BytesLike)⇒ Typed\nReturn a new bytes17 type for v.\n\n<src>Typed.bytes18(v: BytesLike)⇒ Typed\nReturn a new bytes18 type for v.\n\n<src>Typed.bytes19(v: BytesLike)⇒ Typed\nReturn a new bytes19 type for v.\n\n<src>Typed.bytes2(v: BytesLike)⇒ Typed\nReturn a new bytes2 type for v.\n\n<src>Typed.bytes20(v: BytesLike)⇒ Typed\nReturn a new bytes20 type for v.\n\n<src>Typed.bytes21(v: BytesLike)⇒ Typed\nReturn a new bytes21 type for v.\n\n<src>Typed.bytes22(v: BytesLike)⇒ Typed\nReturn a new bytes22 type for v.\n\n<src>Typed.bytes23(v: BytesLike)⇒ Typed\nReturn a new bytes23 type for v.\n\n<src>Typed.bytes24(v: BytesLike)⇒ Typed\nReturn a new bytes24 type for v.\n\n<src>Typed.bytes25(v: BytesLike)⇒ Typed\nReturn a new bytes25 type for v.\n\n<src>Typed.bytes26(v: BytesLike)⇒ Typed\nReturn a new bytes26 type for v.\n\n<src>Typed.bytes27(v: BytesLike)⇒ Typed\nReturn a new bytes27 type for v.\n\n<src>Typed.bytes28(v: BytesLike)⇒ Typed\nReturn a new bytes28 type for v.\n\n<src>Typed.bytes29(v: BytesLike)⇒ Typed\nReturn a new bytes29 type for v.\n\n<src>Typed.bytes3(v: BytesLike)⇒ Typed\nReturn a new bytes3 type for v.\n\n<src>Typed.bytes30(v: BytesLike)⇒ Typed\nReturn a new bytes30 type for v.\n\n<src>Typed.bytes31(v: BytesLike)⇒ Typed\nReturn a new bytes31 type for v.\n\n<src>Typed.bytes32(v: BytesLike)⇒ Typed\nReturn a new bytes32 type for v.\n\n<src>Typed.bytes4(v: BytesLike)⇒ Typed\nReturn a new bytes4 type for v.\n\n<src>Typed.bytes5(v: BytesLike)⇒ Typed\nReturn a new bytes5 type for v.\n\n<src>Typed.bytes6(v: BytesLike)⇒ Typed\nReturn a new bytes6 type for v.\n\n<src>Typed.bytes7(v: BytesLike)⇒ Typed\nReturn a new bytes7 type for v.\n\n<src>Typed.bytes8(v: BytesLike)⇒ Typed\nReturn a new bytes8 type for v.\n\n<src>Typed.bytes9(v: BytesLike)⇒ Typed\nReturn a new bytes9 type for v.\n\n<src>Typed.from(type: string, value: any)⇒ Typed\nReturns a new Typed of type with the value.\n\n<src>Typed.int(v: BigNumberish)⇒ Typed\nReturn a new int256 type for v.\n\n<src>Typed.int104(v: BigNumberish)⇒ Typed\nReturn a new int104 type for v.\n\n<src>Typed.int112(v: BigNumberish)⇒ Typed\nReturn a new int112 type for v.\n\n<src>Typed.int120(v: BigNumberish)⇒ Typed\nReturn a new int120 type for v.\n\n<src>Typed.int128(v: BigNumberish)⇒ Typed\nReturn a new int128 type for v.\n\n<src>Typed.int136(v: BigNumberish)⇒ Typed\nReturn a new int136 type for v.\n\n<src>Typed.int144(v: BigNumberish)⇒ Typed\nReturn a new int144 type for v.\n\n<src>Typed.int152(v: BigNumberish)⇒ Typed\nReturn a new int52 type for v.\n\n<src>Typed.int16(v: BigNumberish)⇒ Typed\nReturn a new int16 type for v.\n\n<src>Typed.int160(v: BigNumberish)⇒ Typed\nReturn a new int160 type for v.\n\n<src>Typed.int168(v: BigNumberish)⇒ Typed\nReturn a new int168 type for v.\n\n<src>Typed.int176(v: BigNumberish)⇒ Typed\nReturn a new int176 type for v.\n\n<src>Typed.int184(v: BigNumberish)⇒ Typed\nReturn a new int184 type for v.\n\n<src>Typed.int192(v: BigNumberish)⇒ Typed\nReturn a new int92 type for v.\n\n<src>Typed.int200(v: BigNumberish)⇒ Typed\nReturn a new int200 type for v.\n\n<src>Typed.int208(v: BigNumberish)⇒ Typed\nReturn a new int208 type for v.\n\n<src>Typed.int216(v: BigNumberish)⇒ Typed\nReturn a new int216 type for v.\n\n<src>Typed.int224(v: BigNumberish)⇒ Typed\nReturn a new int224 type for v.\n\n<src>Typed.int232(v: BigNumberish)⇒ Typed\nReturn a new int232 type for v.\n\n<src>Typed.int24(v: BigNumberish)⇒ Typed\nReturn a new int24 type for v.\n\n<src>Typed.int240(v: BigNumberish)⇒ Typed\nReturn a new int240 type for v.\n\n<src>Typed.int248(v: BigNumberish)⇒ Typed\nReturn a new int248 type for v.\n\n<src>Typed.int256(v: BigNumberish)⇒ Typed\nReturn a new int256 type for v.\n\n<src>Typed.int32(v: BigNumberish)⇒ Typed\nReturn a new int32 type for v.\n\n<src>Typed.int40(v: BigNumberish)⇒ Typed\nReturn a new int40 type for v.\n\n<src>Typed.int48(v: BigNumberish)⇒ Typed\nReturn a new int48 type for v.\n\n<src>Typed.int56(v: BigNumberish)⇒ Typed\nReturn a new int56 type for v.\n\n<src>Typed.int64(v: BigNumberish)⇒ Typed\nReturn a new int64 type for v.\n\n<src>Typed.int72(v: BigNumberish)⇒ Typed\nReturn a new int72 type for v.\n\n<src>Typed.int8(v: BigNumberish)⇒ Typed\nReturn a new int8 type for v.\n\n<src>Typed.int80(v: BigNumberish)⇒ Typed\nReturn a new int80 type for v.\n\n<src>Typed.int88(v: BigNumberish)⇒ Typed\nReturn a new int88 type for v.\n\n<src>Typed.int96(v: BigNumberish)⇒ Typed\nReturn a new int96 type for v.\n\n<src>Typed.overrides(v: Record< string, any >)⇒ Typed\nReturn a new uint8 type for v.\n\n<src>Typed.string(v: string)⇒ Typed\nReturn a new string type for v.\n\n<src>Typed.tuple(v: Array< any | Typed > | Record< string, any | Typed >, name?: string)⇒ Typed\nReturn a new tuple type for v, with the optional name.\n\n<src>Typed.uint(v: BigNumberish)⇒ Typed\nReturn a new uint256 type for v.\n\n<src>Typed.uint104(v: BigNumberish)⇒ Typed\nReturn a new uint104 type for v.\n\n<src>Typed.uint112(v: BigNumberish)⇒ Typed\nReturn a new uint112 type for v.\n\n<src>Typed.uint120(v: BigNumberish)⇒ Typed\nReturn a new uint120 type for v.\n\n<src>Typed.uint128(v: BigNumberish)⇒ Typed\nReturn a new uint128 type for v.\n\n<src>Typed.uint136(v: BigNumberish)⇒ Typed\nReturn a new uint136 type for v.\n\n<src>Typed.uint144(v: BigNumberish)⇒ Typed\nReturn a new uint144 type for v.\n\n<src>Typed.uint152(v: BigNumberish)⇒ Typed\nReturn a new uint152 type for v.\n\n<src>Typed.uint16(v: BigNumberish)⇒ Typed\nReturn a new uint16 type for v.\n\n<src>Typed.uint160(v: BigNumberish)⇒ Typed\nReturn a new uint160 type for v.\n\n<src>Typed.uint168(v: BigNumberish)⇒ Typed\nReturn a new uint168 type for v.\n\n<src>Typed.uint176(v: BigNumberish)⇒ Typed\nReturn a new uint176 type for v.\n\n<src>Typed.uint184(v: BigNumberish)⇒ Typed\nReturn a new uint184 type for v.\n\n<src>Typed.uint192(v: BigNumberish)⇒ Typed\nReturn a new uint192 type for v.\n\n<src>Typed.uint200(v: BigNumberish)⇒ Typed\nReturn a new uint200 type for v.\n\n<src>Typed.uint208(v: BigNumberish)⇒ Typed\nReturn a new uint208 type for v.\n\n<src>Typed.uint216(v: BigNumberish)⇒ Typed\nReturn a new uint216 type for v.\n\n<src>Typed.uint224(v: BigNumberish)⇒ Typed\nReturn a new uint224 type for v.\n\n<src>Typed.uint232(v: BigNumberish)⇒ Typed\nReturn a new uint232 type for v.\n\n<src>Typed.uint24(v: BigNumberish)⇒ Typed\nReturn a new uint24 type for v.\n\n<src>Typed.uint240(v: BigNumberish)⇒ Typed\nReturn a new uint240 type for v.\n\n<src>Typed.uint248(v: BigNumberish)⇒ Typed\nReturn a new uint248 type for v.\n\n<src>Typed.uint256(v: BigNumberish)⇒ Typed\nReturn a new uint256 type for v.\n\n<src>Typed.uint32(v: BigNumberish)⇒ Typed\nReturn a new uint32 type for v.\n\n<src>Typed.uint40(v: BigNumberish)⇒ Typed\nReturn a new uint40 type for v.\n\n<src>Typed.uint48(v: BigNumberish)⇒ Typed\nReturn a new uint48 type for v.\n\n<src>Typed.uint56(v: BigNumberish)⇒ Typed\nReturn a new uint56 type for v.\n\n<src>Typed.uint64(v: BigNumberish)⇒ Typed\nReturn a new uint64 type for v.\n\n<src>Typed.uint72(v: BigNumberish)⇒ Typed\nReturn a new uint72 type for v.\n\n<src>Typed.uint8(v: BigNumberish)⇒ Typed\nReturn a new uint8 type for v.\n\n<src>Typed.uint80(v: BigNumberish)⇒ Typed\nReturn a new uint80 type for v.\n\n<src>Typed.uint88(v: BigNumberish)⇒ Typed\nReturn a new uint88 type for v.\n\n<src>Typed.uint96(v: BigNumberish)⇒ Typed\nReturn a new uint96 type for v.\n\nMETHODS\n<src>typed.defaultValue()⇒ string | number | bigint | Result\nThe default value returned by this type.\n\n<src>typed.format()⇒ string\nFormat the type as a Human-Readable type.\n\n<src>typed.isBigInt()⇒ boolean\nReturns true and provides a type guard is this is a TypedBigInt.\n\n<src>typed.isData()⇒ boolean\nReturns true and provides a type guard is this is a TypedData.\n\n<src>typed.isString()⇒ boolean\nReturns true and provides a type guard is this is a TypedString.\n\n<src>typed.maxValue()⇒ string | number | bigint\nThe maximum value for numeric types.\n\n<src>typed.minValue()⇒ string | number | bigint\nThe minimum value for numeric types.\n\nSTATIC METHODS\n<src>Typed.dereference(value: Typed | T, type: string)⇒ T\nIf the value is a Typed instance, validates the underlying value and returns it, otherwise returns value directly.\nThis is useful for functions that with to accept either a Typed object or values.\n\n<src>Typed.isTyped(value: any)⇒ boolean\nReturns true only if value is a Typed instance.\n\ninterface TypedBigInt\ninherits from Typed\nA Typed that represents a numeric value.\n\nPROPERTIES\n<src>typedBigInt.value⇒ bigint\nThe value.\n\nMETHODS\n<src>typedBigInt.defaultValue()⇒ bigint\nThe default value for all numeric types is 0.\n\n<src>typedBigInt.maxValue()⇒ bigint\nThe minimum value for this type, accounting for bit-width.\n\n<src>typedBigInt.minValue()⇒ bigint\nThe minimum value for this type, accounting for bit-width and signed-ness.\n\ninterface TypedData\ninherits from Typed\nA Typed that represents a binary sequence of data as bytes.\n\nPROPERTIES\n<src>typedData.value⇒ string\nThe value.\n\nMETHODS\n<src>typedData.defaultValue()⇒ string\nThe default value for this type.\n\ninterface TypedString\ninherits from Typed\nA Typed that represents a UTF-8 sequence of bytes.\n\nPROPERTIES\n<src>typedString.value⇒ string\nThe value.\n\nMETHODS\n<src>typedString.defaultValue()⇒ string\nThe default value for the string type is the empty string (i.e. \"\").\n\n← Application Programming Interface\nABI Encoding→\n\nThe content of this site is licensed under the Creative Commons License. Generated on June 4, 2024, 5:00am.","tokens":6176,"crawled_at":1791193794458}
+{"id":10288,"url":"https://gov.uniswap.org/t/temp-check-update-crosschain-governance-parameters-for-avalanche-megaeth-soneium-and-x-layer/26127/4","domain":"gov.uniswap.org","chapter":"governance_daos","title":"[Temp Check] - Update Crosschain Governance Parameters for Avalanche, MegaETH, Soneium, and X Layer - #4 by Manugotsuka - Requests for Comment - Uniswap Governance","text":"[Temp Check] - Update Crosschain Governance Parameters for Avalanche, MegaETH, Soneium, and X Layer\n\nRequests for Comment\n\nManugotsuka\n\nJuly 2, 2026, 2:52pm\n\n4\n\nThe following reflects the views of L2BEAT’s governance team, composed of @kaereste and @Manugotsuka, and is based on their combined research, fact-checking, and discussion.\n\nWe voted FOR.\n\nCrosschain governance is an important part of how Uniswap operates across multiple networks, and it makes sense to keep that infrastructure up to date as deployments evolve and older messaging systems become less suitable.\n\nMoving Avalanche and MegaETH away from LayerZero v1 is a reasonable step. Given the direction of LayerZero v1 and the bridge work already done by the Uniswap Foundation, we think migrating these deployments to a more actively supported messaging path is the right direction.\n\nWe also support moving Soneium and X Layer away from aliased timelock ownership and toward CrossChainAccount contracts. Aliased ownership on OP Stack chains can be unintuitive and easier to mishandle, while CrossChainAccount provides a clearer and more explicit ownership structure for executing governance actions from Ethereum.\n\nBefore voting, we asked our Research Team to review the proposal. Their view was that the overall direction is sound: moving away from LayerZero v1 makes sense, and the proposed CrossChainAccount changes are a cleaner setup for Soneium and X Layer.\n\nThe main nuance they raised is around MegaETH. If a canonical bridge path is available there, it would be helpful to understand why the proposal uses Wormhole instead of the canonical bridge, especially when CrossChainAccount is already being used for other OP Stack deployments. This does not change our support for the proposal, but we think the design choice is worth clarifying.\n\nshow post in topic\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nRFC: Uniswap Universal Governance Module\n\nRequests for Comment\n\n21\n\n13381\n\nNovember 29, 2022\n\n[RFC - Update] Deploy Uniswap v3 (1 / 0.3 / 0.05 / 0.01) on BNB Chain (Binance)\n\nRequests for Comment\n\n101\n\n45661\n\nJuly 22, 2026\n\nProposed Template for Future Cross-chain Deployment Proposals\n\nGovernance-Meta\n\n6\n\n6473\n\nMay 6, 2022\n\nDeploy Uniswap v3 on Avalanche\n\nRequests for Comment\n\n18\n\n10148\n\nAugust 25, 2023\n\n[Temperature Check] Fix the Cross Chain Messaging Bridge on Arbitrum\n\nTemperature Check\n\n8\n\n5320\n\nDecember 9, 2022","tokens":602,"crawled_at":1791193795895}
+{"id":10289,"url":"https://docs.dydx.xyz/nodes/full-node-streaming","domain":"docs.dydx.xyz","chapter":"defi_protocols","title":"Full Node gRPC Streaming – dYdX Documentation","text":"Enable full node streaming to expose a stream of orderbook updates (L3), fills, taker orders, and subaccount updates, allowing clients to maintain a full view of the orderbook and various exchange activities. Note that the orderbook state can vary slightly between nodes due to dYdX's offchain orderbook design.\n\nLast updated for: v7.0.2\n\nEnabling Streaming\n\nFull node streaming supports two streaming protocols. Information can be streamed via gRPC or Websockets. Use the following flags to configure full node streaming features:\n\nCLI FlagTypeDefaultShort Explanation\ngrpc-streaming-enabled\nbool\nfalse\nToggle on to enable grpc-based full node streaming.\n\ngrpc-streaming-flush-interval-ms\nint\n50\nBuffer flush interval for batch emission of protocol-side updates.\n\ngrpc-streaming-max-batch-size\nint\n2000\nMaximum protocol-side update buffer before dropping all streaming connections.\n\ngrpc-streaming-max-channel-buffer-size\nint\n2000\nMaximum channel size before dropping slow or erroring grpc connections. Decreasing this will more aggressively drop slow client connections.\n\nwebsocket-streaming-enabled\nbool\nfalse\nToggle on to enable websocket-based streaming. Must be used in conjunction with grpc-streaming-enabled.\n\nwebsocket-streaming-port\nint\n9092\nPort number to expose for websocket streaming.\n\nfns-snapshot-interval\nint\n0\nIf set to a nonzero number, snapshots will be sent out at this block interval. Used for debugging purposes.\n\nConnecting to the Stream\n\nAfter setting up a full node with gRPC streaming enabled, you can connect to the stream using any gRPC client.\nTo follow along with Google's documentation on gRPC streaming clients:\n\nClone the github.com/dydxprotocol/v4-chain repository at the same version as your full node.\n\nGenerate the protos: make proto-gen && make proto-export-deps.\n\nThe generated protos are now in the .proto-export-deps directory.\n\nUse the protobuf compiler (protoc) to generate stubs in any supported language.\n\nFollow Google's documentation to write a client that can read from the stream.\n\nConnect to the stream defined in the dydxprotocol.clob.Query service (StreamOrderbookUpdates).\n\nFor Python, the corresponding code is already generated in the package v4-proto.\nFor Rust, install the crate dydx-proto.\n\nTo connect via websocket, connect to the specified websocket server port at endpoint /ws. Default port number is 9092, but it can be configured via CLI flag. There are two query parameters. clobPairIds is a list of CLOB pair IDs to subscribe to, and subaccountIds are a list of subaccount ids to subscribe to.\n\nMaintaining Orderbook and Subaccount State\n\nOverview\n\nConnect to the stream and subscribe to updates for a series of CLOB pair IDs, each of which corresponds to a tradeable instrument, and subaccount ids, each of which corresponds to a subaccount.\n\nDiscard order messages until you receive a StreamOrderbookUpdate with snapshot set to true. This message contains the full orderbook state for each CLOB pair.\n\nSimilarly, discard subaccount messages until you receive a StreamSubaccountUpdate with snapshot set to true. This message contains the full subaccount state for each subscribed subaccount.\n\nWhen you see an OrderPlaceV1 message, insert the order into the book at the end of the queue on its price level. Track the order's initial quantums (quantity) and total filled quantums.\n\nWhen you see an OrderUpdateV1 message, update the order's total filled quantums.\n\nWhen you see a ClobMatch (trade) message, update the total filled quantums for each maker order filled using the fill_amounts field.\n\nNote that, similar to OrderUpdateV1, the fill_amounts field represents the order's total filled quantity up to this point. This is not the amount filled in this specific match, but rather the cumulative amount filled across all matches for this order.\n\nThe order's quantity remaining is always its initial quantity minus its total filled quantity.\n\nNote that both OrderUpdateV1 and ClobMatch messages must be processed to maintain the correct book state. See OrderUpdateV1 for details.\n\nWhen you see an OrderRemoveV1 message, remove the order from the book.\n\nWhen you see a StreamSubaccountUpdate message with snapshot set to false, incrementally update the subaccount's balances and positions.\n\nWhen you see a StreamTakerOrder message, state does not need to be updated. Taker orders are purely informational and are emitted whenever a taker order enters the matching loop, regardless of success or failure.\n\nNote:\n\nThe order subticks (price) and quantums (quantity) fields are encoded as integers and\nrequire translation to human-readable values.\n\nEach node's view of the book is subjective, because order messages arrive at different nodes in different orders. When a block is proposed, nodes \"sync\" subsets of their book states to cohere with the trades seen by the block proposer.\n\nOnly ClobMatch messages with execModeFinalize are trades confirmed by consensus.\n\nUse all ClobMatch messages to update the orderbook state. The node's book state is optimistic, and reverts if fills are not confirmed, in which case a series of OrderRemoveV1, OrderPlaceV1 and OrderUpdateV1 messages are sent to represent the modifications to the full node's book state.\n\nTreat only ClobMatch messages with execModeFinalize as confirmed trades.\n\nSee Reference Material for more information.\n\nRequest / Response\n\nTo subscribe to the stream, the client can send a 'StreamOrderbookUpdatesRequest' specifying the CLOB pair IDs and subaccount ids to subscribe to.\n\nProtobuf Structs// StreamOrderbookUpdatesRequest is a request message for the\n// StreamOrderbookUpdates method.\nmessage StreamOrderbookUpdatesRequest {\n// Clob pair ids to stream orderbook updates for.\nrepeated uint32 clob_pair_id = 1;\n\n// Subaccount ids to stream subaccount updates for.\nrepeated dydxprotocol.subaccounts.SubaccountId subaccount_ids = 2;\n}\n\nResponse will contain a oneof field that contains either:\n\nStreamOrderbookUpdate\n\nContains one or more OffChainUpdateV1 orderbook updates (Add/Remove/Update)\n\nboolean field indicating if the updates are coming from a snapshot or not.\n\nStreamOrderbookFill\n\nContains a singular ClobMatch object describing a fill (order or liquidation).\n\nRepresents one taker order matched with 1 or more maker orders.\n\nMatched quantums are provided for each pair in the match.\n\norders field contains full order information at time of matching. Contains all maker and taker orders involved in the ClobMatch object.\n\nPrices within a Match are matched at the maker order price.\n\nfill_amounts contains the absolute, total filled quantums of each order as stored in state.\n\nfill_amounts should be zipped together with the orders field. Both arrays should have the same length.\n\nStreamTakerOrder\n\nContains a oneof TakerOrder field which represents the order that entered the matching loop.\n\nCould be a regular order or a Liquidation Order.\n\nContains a StreamTakerOrderStatus field which represents the status of a taker order after it has finished the matching loop.\n\nOrderStatus is a uint32 describing the result of the taker order matching. Only value 0 indicates success. Possible values found here.\n\n@jonfung to update to static link\n\nRemainingQuantums represents the remaining amount of non-matched quantums for the taker order.\n\nOptimisticallyFilledQuantums represents the number of quantums filled during this matching loop. It does not include quantums filled before this matching loop, if the order was a replacement order and was previously filled.\n\nStreamSubaccountUpdate\n\nContains a singular SubaccountId object to identify the subaccount.\n\nmultiple SubaccountPerpetualPositions to represent the perpetual positions of the subaccount.\n\neach SubaccountPerpetualPosition contains a perpetual id and the size of the position in base quantums.\n\nmultiple SubaccountAssetPositions to represent the asset positions of the subaccount. (i.e, usdc collateral positions)\n\neach SubaccountAssetPosition contains an asset id and the size of the position in base quantums.\n\nas well as block_height and exec_mode (see Exec Modes Reference).\n\nProtobuf Structs// StreamOrderbookUpdatesResponse is a response message for the\n// StreamOrderbookUpdates method.\nmessage StreamOrderbookUpdatesResponse {\n// Batch of updates for the clob pair.\nrepeated StreamUpdate updates = 1 [ (gogoproto.nullable) = false ];\n}\n\n// StreamUpdate is an update that will be pushed through the\n// gRPC stream.\nmessage StreamUpdate {\n// Contains one of an StreamOrderbookUpdate,\n// StreamOrderbookFill, StreamTakerOrderStatus, StreamSubaccountUpdate.\noneof update_message {\nStreamOrderbookUpdate orderbook_update = 1;\nStreamOrderbookFill order_fill = 2;\nStreamTakerOrder taker_order = 3;\ndydxprotocol.subaccounts.StreamSubaccountUpdate subaccount_update = 4;\n}\n\n// Block height of the update.\nuint32 block_height = 5;\n\n// Exec mode of the update.\nuint32 exec_mode = 6;\n}\n\n// StreamOrderbookUpdate provides information on an orderbook update. Used in\n// the full node gRPC stream.\nmessage StreamOrderbookUpdate {\n// Orderbook updates for the clob pair. Can contain order place, removals,\n// or updates.\nrepeated dydxprotocol.indexer.off_chain_updates.OffChainUpdateV1 updates = 1\n[ (gogoproto.nullable) = false ];\n\n// Snapshot indicates if the response is from a snapshot of the orderbook.\n// This is true for the initial response and false for all subsequent updates.\n// Note that if the snapshot is true, then all previous entries should be\n// discarded and the orderbook should be resynced.\nbool snapshot = 2;\n}\n\n// StreamOrderbookFill provides information on an orderbook fill. Used in\n// the full node gRPC stream.\nmessage StreamOrderbookFill {\n// Clob match. Provides information on which orders were matched\n// and the type of order.\nClobMatch clob_match = 1;\n\n// All orders involved in the specified clob match. Used to look up\n// price of a match through a given maker order id.\nrepeated Order orders = 2 [ (gogoproto.nullable) = false ];\n\n// Resulting fill amounts for each order in the orders array.\nrepeated uint64 fill_amounts = 3 [ (gogoproto.nullable) = false ];\n}\n\n// StreamTakerOrder provides information on a taker order that was attempted\n// to be matched on the orderbook.\n// It is intended to be used only in full node streaming.\nmessage StreamTakerOrder {\n// The taker order that was matched on the orderbook. Can be a\n// regular order or a liquidation order.\noneof taker_order {\nOrder order = 1;\nStreamLiquidationOrder liquidation_order = 2;\n}\n\n// Information on the taker order after it is matched on the book,\n// either successfully or unsuccessfully.\nStreamTakerOrderStatus taker_order_status = 3;\n}\n\n// StreamTakerOrderStatus is a representation of a taker order\n// after it is attempted to be matched on the orderbook.\n// It is intended to be used only in full node streaming.\nmessage StreamTakerOrderStatus {\n// The state of the taker order after attempting to match it against the\n// orderbook. Possible enum values can be found here:\n// https://github.com/dydxprotocol/v4-chain/blob/main/protocol/x/clob/types/orderbook.go#L105\nuint32 order_status = 1;\n\n// The amount of remaining (non-matched) base quantums of this taker order.\nuint64 remaining_quantums = 2;\n\n// The amount of base quantums that were *optimistically* filled for this\n// taker order when the order is matched against the orderbook. Note that if\n// any quantums of this order were optimistically filled or filled in state\n// before this invocation of the matching loop, this value will not include\n// them.\nuint64 optimistically_filled_quantums = 3;\n}\n\n// StreamSubaccountUpdate provides information on a subaccount update. Used in\n// the full node GRPC stream.\nmessage StreamSubaccountUpdate {\nSubaccountId subaccount_id = 1;\n// updated_perpetual_positions will each be for unique perpetuals.\nrepeated SubaccountPerpetualPosition updated_perpetual_positions = 2;\n// updated_asset_positions will each be for unique assets.\nrepeated SubaccountAssetPosition updated_asset_positions = 3;\n// Snapshot indicates if the response is from a snapshot of the subaccount.\n// All updates should be ignored until snapshot is received.\n// If the snapshot is true, then all previous entries should be\n// discarded and the subaccount should be resynced.\n// For a snapshot subaccount update, the `updated_perpetual_positions` and\n// `updated_asset_positions` fields will contain the full state of the\n// subaccount.\nbool snapshot = 4;\n}\n\n// SubaccountPerpetualPosition provides information on a subaccount's updated\n// perpetual positions.\nmessage SubaccountPerpetualPosition {\n// The `Id` of the `Perpetual`.\nuint32 perpetual_id = 1;\n// The size of the position in base quantums. Negative means short.\nint64 quantums = 2;\n}\n\n// SubaccountAssetPosition provides information on a subaccount's updated asset\n// positions.\nmessage SubaccountAssetPosition {\n// The `Id` of the `Asset`.\nuint32 asset_id = 1;\n// The absolute size of the position in base quantums.\nuint64 quantums = 2;\n}\n\nAfter subscribing to the orderbook updates, use the orderbook in the snapshot as the starting orderbook.\nSimilarly, use the subaccount state in the snapshot as the starting subaccount state.\n\nOrderPlaceV1\n\nWhen OrderPlaceV1 is received, add the corresponding order to the end of the price level.\n\nThis message is only used to modify the orderbook data structure (Bids, Asks).\n\nThis message is sent out whenever an order is added to the in-memory orderbook.\n\nThis may occur in various places such as when an order is initially placed, or when an order is replayed during the ProcessCheckState step.\n\nAn OrderPlaceV1 message is always be followed by an OrderUpdateV1 message, which sets the intial fill amount (typically zero).\n\nCode Snippetfunc (l *LocalOrderbook) AddOrder(order v1types.IndexerOrder) {\nl.Lock()\ndefer l.Unlock()\n\nif _, ok := l.OrderIdToOrder[order.OrderId]; ok {\nl.Logger.Error(\"order already exists in orderbook\")\n}\n\nsubticks := order.GetSubticks()\nif order.Side == v1types.IndexerOrder_SIDE_BUY {\nif _, ok := l.Bids[subticks]; !ok {\nl.Bids[subticks] = make([]v1types.IndexerOrder, 0)\n}\nl.Bids[subticks] = append(l.Bids[subticks], order)\n} else {\nif _, ok := l.Asks[subticks]; !ok {\nl.Asks[subticks] = make([]v1types.IndexerOrder, 0)\n}\nl.Asks[subticks] = append(l.Asks[subticks], order)\n}\n\nl.OrderIdToOrder[order.OrderId] = order\nl.OrderRemainingAmount[order.OrderId] = 0\n}\n\nOrderUpdateV1\n\nWhen OrderUpdateV1 is received, update the order's fill amount to the amount specified.\n\nThis message is only used to update fill amounts. It carries information about an order's updated fill amount.\n\nThis message is emitted when an order's fill amount changes due to something other than a ClobMatch.\n\nThis includes when deliverState is reset to the checkState from last block, or when branched state is written to and then discarded if there was a matching error.\n\nFor example, this could happen if the full node sees the order filled, and then the next block committed by consensus does not contain the expected fill, so the order’s quantity remaining resets to its state from the previous block.\n\nAn update message will always accompany an order placement message.\n\nIt's possible for an update message to be sent before a placement message. You can safely ignore update messages with order ids not in the orderbook.\n\nNote that you must handle both OrderUpdateV1 and ClobMatch messages to maintain the correct book state.\n\nCode Snippetfunc (l *LocalOrderbook) SetOrderFillAmount(\norderId *v1types.IndexerOrderId,\nfillAmount uint64,\n) {\nl.Lock()\ndefer l.Unlock()\n\nif fillAmount == 0 {\ndelete(l.FillAmounts, *orderId)\n} else {\nl.FillAmounts[*orderId] = fillAmount\n}\n}\n\nOrderRemoveV1\n\nWhen OrderRemoveV1 is received, remove the order from the orderbook.\n\nThis message is only used to modify the orderbook data structure (Bids, Asks).\n\nThis message is emitted when an order is removed from the in-memory orderbook.\n\nNote that this does not mean the fills are removed from state yet.\n\nWhen fills are removed from state, a separate Update message will be sent with 0 quantum.\n\nCode Snippetfunc (l *LocalOrderbook) RemoveOrder(orderId v1types.IndexerOrderId) {\nl.Lock()\ndefer l.Unlock()\n\nif _, ok := l.OrderIdToOrder[orderId]; !ok {\nl.Logger.Error(\"order not found in orderbook\")\n}\n\norder := l.OrderIdToOrder[orderId]\nsubticks := order.GetSubticks()\n\nif order.Side == v1types.IndexerOrder_SIDE_BUY {\nfor i, o := range l.Bids[subticks] {\nif o.OrderId == order.OrderId {\nl.Bids[subticks] = append(\nl.Bids[subticks][:i],\nl.Bids[subticks][i+1:]...,\n)\nbreak\n}\n}\nif len(l.Bids[subticks]) == 0 {\ndelete(l.Bids, subticks)\n}\n} else {\nfor i, o := range l.Asks[subticks] {\nif o.OrderId == order.OrderId {\nl.Asks[subticks] = append(\nl.Asks[subticks][:i],\nl.Asks[subticks][i+1:]...,\n)\nbreak\n}\n}\nif len(l.Asks[subticks]) == 0 {\ndelete(l.Asks, subticks)\n}\n}\ndelete(l.OrderIdToOrder, orderId)\n}\n\nStreamOrderbookFill/ClobMatch\n\nThis message is only used to update fill amounts, it does not add or remove orders from the book but can change the quantity remaining for open orders.\n\nThe ClobMatch data structure contains either a MatchOrders or a MatchPerpetualLiquidation object. Match Deleveraging events are not emitted. Within each Match object, a MakerFill array contains the various maker orders that matched with the singular taker order and the amount of quantums matched.\n\nNote that all matches occur at the maker order price. The orders field in the StreamOrderbookFill object allow for price lookups based on order id. It contains all the maker order ids, and in the case of non-liquidation orders, it has the taker order.\n\nMapping each order in orders to the corresponding value in the fill_amounts field provides the absolute filled amount of quantums that each order is filled to after the ClobMatch was processed.\n\nCode Snippet// fillAmountMap is a map of order ids to fill amounts.\n// The SetOrderFillAmount code can be found in `the `OrderUpdateV1` section.\nfunc (c *GrpcClient) ProcessMatchOrders(\nmatchOrders *clobtypes.MatchOrders,\norderMap map[clobtypes.OrderId]clobtypes.Order,\nfillAmountMap map[clobtypes.OrderId]uint64,\n) {\ntakerOrderId := matchOrders.TakerOrderId\nclobPairId := takerOrderId.GetClobPairId()\nlocalOrderbook := c.Orderbook[clobPairId]\n\nindexerTakerOrder := v1.OrderIdToIndexerOrderId(takerOrderId)\nlocalOrderbook.SetOrderFillAmount(&indexerTakerOrder, fillAmountMap[takerOrderId])\n\nfor _, fill := range matchOrders.Fills {\nmakerOrder := orderMap[fill.MakerOrderId]\nindexerMakerOrder := v1.OrderIdToIndexerOrderId(makerOrder.OrderId)\nlocalOrderbook.SetOrderFillAmount(&indexerMakerOrder, fillAmountMap[makerOrder.OrderId])\n}\n}\n\nfunc (c *GrpcClient) ProcessMatchPerpetualLiquidation(\nperpLiquidation *clobtypes.MatchPerpetualLiquidation,\norderMap map[clobtypes.OrderId]clobtypes.Order,\nfillAmountMap map[clobtypes.OrderId]uint64,\n) {\nlocalOrderbook := c.Orderbook[perpLiquidation.ClobPairId]\nfor _, fill := range perpLiquidation.GetFills() {\nmakerOrder := orderMap[fill.MakerOrderId]\nindexerMakerOrderId := v1.OrderIdToIndexerOrderId(makerOrder.OrderId)\nlocalOrderbook.SetOrderFillAmount(&indexerMakerOrderId, fillAmountMap[makerOrder.OrderId])\n}\n}\n\nStreamSubaccountUpdate\n\nThis message is used to update subaccount balances and positions.\n\nThe initial message for a subaccount will have snapshot set to true. This message contains the full state of the subaccount. All updates should be ignored until the snapshot is received. Subsequent updates will contain updates to the positions and balances of the subaccount. They should be merged in with the existing state of the subaccount.\n\nApart from the initial snapshot, this mesage will only be sent out for subaccount updates that are in consensus.\n\nCode Snippettype SubaccountId struct {\nOwner string\nNumber int\n}\n\ntype SubaccountPerpetualPosition struct {\nPerpetualId int\nQuantums int\n}\n\ntype SubaccountAssetPosition struct {\nAssetId int\nQuantums int\n}\n\ntype SubaccountState struct {\nSubaccountId SubaccountId\nPerpetualPositions map[int]SubaccountPerpetualPosition\nAssetPositions map[int]SubaccountAssetPosition\n}\n\nfunc (c *GrpcClient) ProcessSubaccountUpdate(\nsubaccountUpdate *satypes.StreamSubaccountUpdate,\nsubaccountMap map[satypes.SubaccountId]SubaccountState,\n) {\n// Extract the subaccount ID from the update\nsubaccountId := *subaccountUpdate.SubaccountId\n\n// Check if this is a snapshot\nif subaccountUpdate.Snapshot {\n// Replace the entire subaccount state with the snapshot data\nsubaccountState := SubaccountState{\nSubaccountId: subaccountId,\nPerpetualPositions: make(map[int]SubaccountPerpetualPosition),\nAssetPositions: make(map[int]SubaccountAssetPosition),\n}\n\n// Populate perpetual positions from snapshot\nfor _, perpPositionUpdate := range subaccountUpdate.UpdatedPerpetualPositions {\nsubaccountState.PerpetualPositions[perpPositionUpdate.PerpetualId] = *perpPositionUpdate\n}\n\n// Populate asset positions from snapshot\nfor _, assetPositionUpdate := range subaccountUpdate.UpdatedAssetPositions {\nsubaccountState.AssetPositions[assetPositionUpdate.AssetId] = *assetPositionUpdate\n}\n\n// Update the map with the new snapshot state\nsubaccountMap[subaccountId] = subaccountState\n} else {\n// If not a snapshot, retrieve or initialize the current subaccount state\nsubaccountState, exists := subaccountMap[subaccountId]\nif !exists {\nsubaccountState = SubaccountState{\nSubaccountId: subaccountId,\nPerpetualPositions: make(map[int]SubaccountPerpetualPosition),\nAssetPositions: make(map[int]SubaccountAssetPosition),\n}\n}\n\n// Update perpetual positions\nfor _, perpPositionUpdate := range subaccountUpdate.UpdatedPerpetualPositions {\nif perpPositionUpdate.Quantums != 0 {\nsubaccountState.PerpetualPositions[perpPositionUpdate.PerpetualId] = *perpPositionUpdate\n} else {\n// Delete the entry if the position size is zero\ndelete(subaccountState.PerpetualPositions, perpPositionUpdate.PerpetualId)\n}\n}\n\n// Update asset positions\nfor _, assetPositionUpdate := range subaccountUpdate.UpdatedAssetPositions {\nif assetPositionUpdate.Quantums != 0 {\nsubaccountState.AssetPositions[assetPositionUpdate.AssetId] = *assetPositionUpdate\n} else {\n// Delete the entry if the asset quantity is zero\ndelete(subaccountState.AssetPositions, assetPositionUpdate.AssetId)\n}\n}\n\n// Update the map with the modified state\nsubaccountMap[subaccountId] = subaccountState\n}\n}\n\nStreamTakerOrder\n\nThis message is purely an informational message used to indicate whenever a taker order is matched against the orderbook. No internal state in clients need to be updated.\n\nInformation provided in the struct:\n\nOne of (taker order, liquidation order) entering matching loop\n\nStatus of order after matching. If order failed to match, status code provides the reason for failure (i.e post only order crosses book)\n\nRemaining non-matched quantums for the taker order\n\nQuantity of optimistically matched quantums during this matching order loop.\n\nNote that by protocol design, all StreamTakerOrderStatus emissions will be optimistic from CheckTx state. This is due to the fact that each node maintains it's own orderbook, thus all matching operations when a taker order enters the matching loop will be optimistic. If confirmed fill amounts in consensus are desired, StreamOrderbookFill objects will be emitted during DeliverTx for proposed blocks.\n\nCode Snippettype StreamTakerOrderStatus struct {\nOrderStatus uint32\nRemainingQuantums uint64\nOptimisticallyFilledQuantums uint64\n}\n\nfunc (c *GrpcClient) ProcessStreamTakerOrder(\nstreamTakerOrder *satypes.StreamTakerOrder,\n) {\ntakerOrder := streamTakerOrder.GetOrder()\ntakerOrderLiquidation := streamTakerOrder.GetLiquidationOrder()\ntakerOrderStatus := streamTakerOrder.GetTakerOrderStatus()\nif takerOrderStatus.OrderStatus == 0 || takerOrderStatus.OrderStatus == 0 {\nif takerOrder != nil {\n// Process success of regular taker order\n}\nif takerOrderLiquidation != nil {\n// Process success of liquidation taker order\n}\n}\n}\n\nReference Material\n\nOptimistic Orderbook Execution\n\nBy protocol design, each validator has their own version of the orderbook and optimistically processes orderbook matches. As a result, you may see interleaved sequences of order removals, placements, and state fill amount updates when optimistically processed orderbook matches are removed and later replayed on the local orderbook.\n\nNote that DeliverTx maps to exec mode execModeFinalize.\n\nStaged DeliverTx Validation\n\nIn DeliverTx, all of the updates emitted are finalized and in consensus. A batch of updates will be sent out in the same StreamOrderbookUpdatesResponse object. In consensus, fills and subaccount updates will be emitted.\n\nFinalized Subaccount Updates\n\nOnly finalized subaccount updates are sent. Snapshots are sent during PrepareCheckState, so the execMode will be set to 102 for subaccount snapshots. Finalized incremental subaccount updates are sent with execMode 7.\n\nExec Mode Reference\n\nExec Modes execModeCheck = 0 // Check a transaction\nexecModeReCheck = 1 // Recheck a (pending) transaction after a commit\nexecModeSimulate = 2 // Simulate a transaction\nexecModePrepareProposal = 3 // Prepare a block proposal\nexecModeProcessProposal = 4 // Process a block proposal\nexecModeVoteExtension = 5 // Extend or verify a pre-commit vote\nexecModeVerifyVoteExtension = 6 // Verify a vote extension\nexecModeFinalize = 7 // Finalize a block proposal\nExecModeBeginBlock = 100\nExecModeEndBlock = 101\nExecModePrepareCheckState = 102\n\nTaker Order Status Reference\n\nValues are defined in code here.\n\n@jonfung to update to static link\n\nValueStatusDescription\n0\nSuccess\nOrder was successfully matched and/or added to the orderbook.\n\n1\nUndercollateralized\nOrder failed collateralization checks when matching or placed on orderbook. Order was cancelled.\n\n2\nInternalError\nOrder caused internal error and was cancelled.\n\n3\nImmediateOrCancelWouldRestOnBook\nOrder is an IOC order that would have been placed on the orderbook. Order was cancelled.\n\n4\nReduceOnlyResized\nOrder was resized since it would have changed the user's position size.\n\n5\nLiquidationRequiresDeleveraging\nNot enough liquidity to liquidate the subaccount profitably on the orderbook. Order was not fully matched because insurance fund did not have enough funds to cover losses from performing liquidation. Subaccount requires deleveraging.\n\n6\nLiquidationExceededSubaccountMaxNotionalLiquidated\nLiquidation order could not be matched because it exceeds the max notional liquidated in this block.\n\n7\nLiquidationExceededSubaccountMaxInsuranceLost\nLiquidation order could not be matched because it exceeds the max funds lost for hte insurance fund in this block.\n\n8\nViolatesIsolatedSubaccountConstraints\nMatching this order would lead to the subaccount violating isolated perpetual constraints. Order was cancelled.\n\n9\nPostOnlyWouldCrossMakerOrder\nMatching this order would lead to the post only taker order crossing the orderbook. Order wasa cancelled.\n\nExample Scenario\n\nTrader places a bid at price 100 for size 1\n\nOrderPlace, price = 100, size = 1\n\nOrderUpdate, total filled amount = 0\n\nTrader replaces that original bid to be price 99 at size 2\n\nOrderRemove\n\nOrderPlace, price = 99, size = 2\n\nOrderUpdate, total filled amount = 0\n\nAnother trader submits an IOC ask at price 100 for size 1.\n\nFull node doesn't see this matching anything so no updates.\n\nBlock is confirmed that there was a fill for the trader's original order at price 100 for size 1 (block proposer didn't see the order replacement)\n\nOrderUpdate, set total fill amount to be 0 (no-op) from checkState -> deliverState reset\n\nMatchOrder emitted for block proposer's original order match, total filled amount = 1\n\nMetrics and Logs\n\nMetricTypeExplanation\ngrpc_send_orderbook_updates_latency.quantile\nhistogram\nLatency for each orderbook cache buffer enqueue\n\ngrpc_send_orderbook_updates_latency.count\ncount\nnumber orderbook updates enqueued in cache buffer\n\ngrpc_send_orderbook_snapshot_latency.quantile\nhistogram\nLatency for each snapshot orderbook emission\n\ngrpc_send_orderbook_snapshot_latency.count\ncount\nnumber of order book snapshots emitted\n\ngrpc_send_subaccount_update_count\ncount\nNumber of subaccount updates emitted\n\ngrpc_send_orderbook_fills_latency.quantile\nhistogram\nLatency for each orderbook fill cache buffer enqueue\n\ngrpc_send_orderbook_fills_latency.count\ncount\nnumber orderbook snapshots enqueued in cache buffer\n\ngrpc_add_update_to_buffer_count\ncount\nNumber of total update objects added to the cache buffer\n\ngrpc_add_to_subscription_channel_count\ncount\nNumber of updates added to each per-subscription channel buffer. Tagged by subscription_id.\n\ngrpc_send_response_to_subscriber_count\ncount\nNumber of updates sent from each per-subscription channel buffer to the client. Tagged by subscription_id.\n\ngrpc_stream_subscriber_count\ncount\nnumber of streaming connections currently connected to the full node\n\ngrpc_stream_num_updates_buffered\nhistogram\nnumber of updates in the full node's buffer cache of updates. Once this hits grpc-streaming-max-batch-size, all subscriptions will be dropped. Use with quantile:0.99 in order to observe maximum amount of updates.\n\ngrpc_flush_updates_latency.count\ncount\nnumber of times the buffer cache is flushed.\n\ngrpc_flush_updates_latency.quantile\nhistogram\nLatency of each buffer cache flush call into subscription channel.\n\ngrpc_subscription_channel_length.quantile\nhistogram\nLength of each subscription's channel buffer. Tagged by subscription_id. Use with quantile:0.99 in order to observe subscription channel length for subscription ids. Once this hits grpc-streaming-max-channel-buffer-size, the offending subscription will be dropped.\n\nAll logs from grpc streaming are tagged with module: full-node-streaming.\n\nProtocol-side buffering and Slow gRPC Client Connections\n\nThe full node maintains a length-configurable buffer cache of streaming updates to ensure bursts of protocol updates do not induce full node lag. If the buffer reaches maximum capacity, all connections and updates are dropped, and subscribers will have to re-subscribe. The buffer is periodically flushed into each per-subscription golang channel at a configurable set interval of time, defaulting to 50ms.\n\nTo ensure slow client connections do not induce full node lag, each client subscription has a unique goroutine and golang channel that pushes updates through the grpc stream. If the channel buffer grows beyond the configurable grpc-streaming-max-channel-buffer-size parameter, the goroutine will be stopped. With the poller gone, the channel buffer will eventually grow and hit the max buffer size, at which the lagging subscription is pruned.\n\nMetrics and logs are emitted to help tune both of these parameters.\n\nFAQs\n\nQ: Suppose the full node saw the cancellation of order X at t0 before the placement of the order X at t1. What would the updates be like?\n\nA: No updates because the order was never added to the book.\n\nQ: A few questions because it often results in crossed books:\nIn which cases shall we not expect to see OrderRemove message?\n\nPost only reject? → PO reject won’t have a removal since they were never added to the book;\n\nIOC/FOK auto cancel? → IOC/FOK also won’t have a removal message for similar reason;\n\nOrder expired outside of block window? → Expired orders will generate a removal message;\n\nPassive limit order was fully filled → Fully filled maker will generate a removal message;\n\nAggressive limit order was fully filled? → Fully filled taker won’t have a removal.\n\nQ: Why does StreamOrderbookUpdate use IndexerOrderId and StreamOrderbookFill use dydxprotocol.OrderId?\n\nA: gRPC streaming exposes inner structs of the matching engine and our updates are processed differently from fills. The two data structures have equivalent fields, and a lightweight translation layer to go from Indexer OrderId to Protocol OrderId can be written.\n\nQ: I only want to listen to confirmed updates. I do not want to process optimistic fills.\n\nA: You will want to only process messages from DeliverTx stage (execModeFinalize). This step is when we save proposed matches from the block proposer into state. These updates will have exec mode execModeFinalize.\n\nQ: Why do I see an Order Update message for a new OrderId before an Order Place message?\n\nA: During DeliverTx, the first step we do is to reset fill amounts (via OrderUpdate messages) for all orders involved in the proposed and local operations queue due to the deliver state being reset to the check state from last block. We \"reset\" fill order amounts to 0 for orders that the block proposer has seen but has not gossiped to our full node yet. In the future, we may reduce the number of messages that are sent, but for now we are optimizing for orderbook correctness.\n\nQ: How do I print the gRPC stream at the command line?\n\nA: Use the grpcurl tool. Connect to a full node stream with:\n\ngrpcurl -plaintext -d '{\"clobPairId\":[0,1], \"subaccountIds\": [{\"owner\": \"dydx1nzuttarf5k2j0nug5yzhr6p74t9avehn9hlh8m\", \"number\": 0}]}' 127.0.0.1:9090 dydxprotocol.clob.Query/StreamOrderbookUpdates\n\nQ: Is there a sample client?\n\nA: Example client which subscribes to the stream and maintains a local orderbook: dydxprotocol/grpc-stream-client\n\nChangelog\n\nv7.0.2\n\nperp position to signed int for tracking long/short positions\n\nv6.0.8\n\nadded taker order message to stream\n\nadded subaccount update message to stream\n\nFinalized DeliverTx updates are all batched together in a single message\n\nMetrics modifications\n\nWebsocket support\n\nv5.0.5\n\nadded update batching and per-channel channel/goroutines to not block full node on laggy subscriptions\n\nProtobuf breaking change: Shifted block height and exec mode from StreamOrderbookUpdatesResponse to StreamUpdate\n\nMetrics","tokens":8407,"crawled_at":1791193796114}
+{"id":10290,"url":"https://stack.olas.network/open-autonomy/advanced_reference/commands/autonomy_service","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"autonomy service - Olas Stack Developer Documentation","text":"autonomy service\n\nTools to manage AI agents minted in the Olas Protocol.\n\nThis command group consists of a number of functionalities to manage the life cycle of AI agents that have been minted in the Olas Protocol.\n\nInfo\n\nYou can specify how you wish to sign the on-chain transactions produced by these commands: either with a private key stored in a file, or with a hardware wallet. In this latter case, ensure that you have configured properly the drivers for your hardware wallet.\n\nOptions\n\n--dry-run\nPerform a dry run for the transaction.\n--use-celo\nUse the Celo chain profile to interact with the Autonolas Protocol registry contracts.\n--use-base\nUse the Base chain profile to interact with the Autonolas Protocol registry contracts.\n--use-optimism\nUse the Optimism chain profile to interact with the Autonolas Protocol registry contracts.\n--use-arbitrum-one\nUse the Arbitrum One chain profile to interact with the Autonolas Protocol registry contracts.\n--use-gnosis\nUse the Gnosis chain profile to interact with the Autonolas Protocol registry contracts.\n--use-polygon\nUse the Polygon chain profile to interact with the Autonolas Protocol registry contracts.\n--use-ethereum\nUse the Ethereum chain profile to interact with the Autonolas Protocol registry contracts.\n\nTo use these chain profiles, you have to export an environment variable that defines the RPC endpoint in the format <CHAIN_NAME>_CHAIN_RPC. For example, if you want to use Ethereum (--use-ethereum), you have to export ETHEREUM_CHAIN_RPC.\n\n--use-custom-chain\n\nUse the custom-chain profile to interact with the Autonolas Protocol registry contracts. This profile requires that you define some parameters and contract addresses as environment variables (see also the Olas Protocol documentation for more information):\n\nCUSTOM_CHAIN_RPC : RPC endpoint for the custom chain.\n\nCUSTOM_CHAIN_ID : chain ID.\n\nCUSTOM_COMPONENT_REGISTRY_ADDRESS\n\nCUSTOM_AGENT_REGISTRY_ADDRESS\n\nCUSTOM_REGISTRIES_MANAGER_ADDRESS\n\nCUSTOM_SERVICE_MANAGER_ADDRESS\n\nCUSTOM_SERVICE_REGISTRY_ADDRESS\n\nCUSTOM_GNOSIS_SAFE_PROXY_FACTORY_ADDRESS†\n\nCUSTOM_GNOSIS_SAFE_SAME_ADDRESS_MULTISIG_ADDRESS†\n\nCUSTOM_SAFE_MULTISIG_WITH_RECOVERY_MODULE_ADDRESS‡\n\nCUSTOM_RECOVERY_MODULE_ADDRESS‡\n\nCUSTOM_SERVICE_REGISTRY_TOKEN_UTILITY_ADDRESS\n\nCUSTOM_MULTISEND_ADDRESS\n\nNote\n\nFor L2 chains you are only required to set\n\nCUSTOM_SERVICE_MANAGER_ADDRESS\n\nCUSTOM_SERVICE_REGISTRY_ADDRESS\n\nCUSTOM_GNOSIS_SAFE_PROXY_FACTORY_ADDRESS†\n\nCUSTOM_GNOSIS_SAFE_SAME_ADDRESS_MULTISIG_ADDRESS†\n\nCUSTOM_SAFE_MULTISIG_WITH_RECOVERY_MODULE_ADDRESS‡\n\nCUSTOM_RECOVERY_MODULE_ADDRESS‡\n\nCUSTOM_MULTISEND_ADDRESS\n\n† Required only if --use-recovery is not specified.\n\n‡ Required only if --use-recovery is specified.\n\n--use-local\nUse the local chain profile to interact with the Autonolas Protocol registry contracts. This option requires that you have a local Hardhat node with the required contracts deployed.\n\nNote\n\nThe chain profile flags (--use-ethereum, etc.) are mutually exclusive.\n\n--use-recovery\nUse a multisig with a recovery module when deploying or redeploying the AI agent. This module allows ownership of the AI agent multisig to be transferred to the AI agent owner if the agent instances have not done so. This functionality is only available during the Pre-Registration phase and is executed automatically when activating the AI agent. See notes † and ‡ above.\n-t, --timeout FLOAT\nTimeout for on-chain interactions\n-r, --retries INTEGER\nMax retries for on-chain interactions\n--sleep FLOAT\nSleep period between retries\n\nautonomy service info\n\nPrint AI agent information.\n\nUsage\n\nautonomy service info AI_AGENT_ID\n\nExamples\n\n$ autonomy service info 3\n\n+---------------------------+----------------------------------------------+\n| Property | Value |\n+===========================+==============================================+\n| Service State | DEPLOYED |\n+---------------------------+----------------------------------------------+\n| Security Deposit | 1000 |\n+---------------------------+----------------------------------------------+\n| Multisig Address | 0x0000000000000000000000000000000000000000 |\n+---------------------------+----------------------------------------------+\n| Cannonical Agents | 1 |\n+---------------------------+----------------------------------------------+\n| Max Agents | 4 |\n+---------------------------+----------------------------------------------+\n| Threshold | 3 |\n+---------------------------+----------------------------------------------+\n| Number Of Agent Instances | 4 |\n+---------------------------+----------------------------------------------+\n| Registered Instances | - 0x0000000000000000000000000000000000000000 |\n| | - 0x0000000000000000000000000000000000000000 |\n| | - 0x0000000000000000000000000000000000000000 |\n| | - 0x0000000000000000000000000000000000000000 |\n+---------------------------+----------------------------------------------+\n\nautonomy service activate\n\nActivate an AI agent minted in the Autonolas Protocol.\n\nUsage\n\nautonomy service activate [OPTIONS] AI_AGENT_ID\n\nOptions\n\n--key FILE\nUse a private key from a file to sign the transactions.\n--hwi\nUse a hardware wallet to sign the transactions.\n--token ERC20_TOKEN_ADDRESS\nERC20 token to use for activating the AI agent. You must specify the same token used when minting the AI agent. See the autonomy mint service command.\n--password PASSWORD\nPassword for the key file.\n\nExamples\n\nTo activate an AI agent with ID 42 in the Autonolas Protocol:\n\nautonomy service activate 42 --key my_key.txt\n\nSame as above, but using a hardware wallet:\n\nautonomy service activate 42 --hwi\n\nIf an ERC20 token was used as bonding token when the AI agent was minted, then you have to provide the same token address using the --token flag:\n\nautonomy service activate 42 --key my_key.txt --token <token_address>\n\nMake sure your account holds enough funds for activating the AI agent:\n\nautonomy service register\n\nRegister an agent instance in an AI agent minted and activated in the Autonolas Protocol.\n\nUsage\n\nautonomy service register [OPTIONS] AI_AGENT_ID\n\nOptions\n\n--key FILE\nUse a private key from a file to sign the transactions.\n--hwi\nUse a hardware wallet to sign the transactions.\n-i, --instance AGENT_ADDRESS\nAgent instance address.\n-a, --agent-id AGENT_ID\nCanonical agent ID.\n--token ERC20_TOKEN_ADDRESS\nERC20 token to use as bond for the agent instance. You must specify the same token used when minting the AI agent. See the autonomy mint service command.\n--password PASSWORD\nPassword for the key file.\n\nExamples\n\nTo register an agent instance of blueprint ID 56 with address 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266 on the AI agent with ID 42 in the protocol:\n\nautonomy service register -i 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266 -a 56 42 --key my_key.txt\n\nSame as above, but using a hardware wallet:\n\nautonomy service register -i 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266 -a 56 42 --hwi\n\nWhen providing the agent instance address make sure that the address you provide is funded.\n\nIf an ERC20 token was used as bonding token when the AI agent was minted, then you have to provide the same token address using the --token flag:\n\nautonomy service register -i 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266 -a 56 42 --hwi --token <token_address>\n\nMake sure your account holds enough funds to pay for the agent instance bonds.\n\nautonomy service deploy\n\nDeploy an AI agent in the Autonolas Protocol.\n\nThis command can be executed after all agent instance slots have been registered in the corresponding AI agent.\n\nUsage\n\nautonomy service deploy [OPTIONS] AI_AGENT_ID\n\nOptions\n\n--reuse-multisig\nReuse mutlisig from previous deployment.\n--key FILE\nUse a private key from a file to sign the transactions.\n--hwi\nUse a hardware wallet to sign the transactions.\n-f, --fallback-handler ADDRESS\nFallback handler address for the gnosis safe multisig.\n--password PASSWORD\nPassword for the key file.\n\nExamples\n\nTo deploy an AI agent with ID 42 in the Autonolas Protocol:\n\nautonomy service deploy 42 --key my_key.txt\n\nSame as above, but using a hardware wallet:\n\nautonomy service deploy 42 --hwi\n\nautonomy service terminate\n\nTerminate an AI agent.\n\nThis command can be executed after the AI agent is activated.\n\nUsage\n\nautonomy service terminate [OPTIONS] AI_AGENT_ID\n\nOptions\n\n--key FILE\nUse a private key from a file to sign the transactions.\n--hwi\nUse a hardware wallet to sign the transactions.\n--password PASSWORD\nPassword for the key file.\n\nExamples\n\nTo terminate the AI agent with ID 42 in the Autonolas Protocol:\n\nautonomy service terminate 42 --key my_key.txt\n\nSame as above, but using a hardware wallet:\n\nautonomy service terminate 42 --hwi\n\nautonomy service unbond\n\nUnbond an AI agent.\n\nThis command can be executed after the AI agent is terminated.\n\nUsage\n\nautonomy service unbond [OPTIONS] AI_AGENT_ID\n\nOptions\n\n--key FILE\nUse a private key from a file to sign the transactions.\n--hwi\nUse a hardware wallet to sign the transactions.\n--password PASSWORD\nPassword for the key file.\n\nExamples\n\nTo unbond an AI agent with ID 42 in the Autonolas Protocol:\n\nautonomy service unbond 42 --key my_key.txt\n\nSame as above, but using a hardware wallet:\n\nautonomy service unbond 42 --hwi\n\nautonomy service recover-multisig\n\nRecover the AI agent multisig.\n\nThis command allows the AI agent owner to reclaim the multisig wallet from the\nprevious deployment if it was not properly transferred by the agent instances after\nAI agent termination.\n\nAI agent multisig recovery is only possible if:\n- The original deployment was performed with the --use-recovery-module flag.\n- The AI agent is currently in the PRE_REGISTRATION state (i.e., all operators have unbonded).\n\nUsage\n\nautonomy service recover-multisig [OPTIONS] AI_AGENT_ID\n\nOptions\n\n--key FILE\nUse a private key from a file to sign the transactions.\n--hwi\nUse a hardware wallet to sign the transactions.\n--password PASSWORD\nPassword for the key file.\n\nExamples\n\nTo recover the multisig of AI agent with ID 42 in the Autonolas Protocol:\n\nautonomy service recover-multisig 42 --key my_key.txt\n\nSame as above, but using a hardware wallet:\n\nautonomy service recover-multisig 42 --hwi","tokens":2533,"crawled_at":1791193807025}
+{"id":10291,"url":"https://docs.ethers.org/v6/api/crypto","domain":"docs.ethers.org","chapter":"developer_specs","title":"","text":"ethers\n6.17.0\n\nDOCUMENTATION\nGetting Started\nEthereum Basics\nApplication Programming Interface\nPollingBlockTagSubscriber\nApplication Binary Interface\nAddresses\nConstants\nContracts\nCryptographic Functions\nHash Functions\nHMAC\nPasswords\nRandom Values\nSigning\nHashing Utilities\nProviders\nTransactions\nUtilities\nWallets\nWordlists\nCookbook\nMigrating from v5\nContributions and Hacking\nLicense and Copyright\n\nSingle Page\n\nDocumentation »API »Cryptographic Functions\nCryptographic Functions\nA fundamental building block of Ethereum is the underlying cryptographic primitives.\n\nFUNCTIONS\n<src>lock()⇒ void\nOnce called, prevents any future change to the underlying cryptographic primitives using the .register feature for hooks.\n\nHash Functions\nCryptographic hashing functions\n\nFUNCTIONS\n<src>keccak256(data: BytesLike)⇒ DataHexstring\nCompute the cryptographic KECCAK256 hash of data.\nThe data must be a data representation, to compute the hash of UTF-8 data use the id function.\n\nkeccak256(\"0x\")\n// '0xc5d2460186f7233c927e7db2dcc703c0e500b653ca82273b7bfad8045d85a470'\n\nkeccak256(\"0x1337\")\n// '0x2636a8beb2c41b8ccafa9a55a5a5e333892a83b491df3a67d2768946a9f9c6dc'\n\nkeccak256(new Uint8Array([ 0x13, 0x37 ]))\n// '0x2636a8beb2c41b8ccafa9a55a5a5e333892a83b491df3a67d2768946a9f9c6dc'\n\n// Strings are assumed to be DataHexString, otherwise it will\n// throw. To hash UTF-8 data, see the note above.\nkeccak256(\"Hello World\")\n// Error(\"invalid BytesLike value\", {\n// code: \"INVALID_ARGUMENT\"\n// argument: \"data\"\n// value: \"Hello World\"\n// shortMessage: \"invalid BytesLike value\"\n// })\n\n<src>ripemd160(data: BytesLike)⇒ DataHexstring\nCompute the cryptographic RIPEMD-160 hash of data.\n\nripemd160(\"0x\")\n// '0x9c1185a5c5e9fc54612808977ee8f548b2258d31'\n\nripemd160(\"0x1337\")\n// '0x224d2bd5251d8f9faa114eb0826e371d1236fda1'\n\nripemd160(new Uint8Array([ 0x13, 0x37 ]))\n// '0x224d2bd5251d8f9faa114eb0826e371d1236fda1'\n\n<src>sha256(data: BytesLike)⇒ DataHexstring\nCompute the cryptographic SHA2-256 hash of data.\n\nsha256(\"0x\")\n// '0xe3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855'\n\nsha256(\"0x1337\")\n// '0x158760c856e5ea1ba97e2e2a456736c4bf30d964559afa6d748cf05694a636ff'\n\nsha256(new Uint8Array([ 0x13, 0x37 ]))\n// '0x158760c856e5ea1ba97e2e2a456736c4bf30d964559afa6d748cf05694a636ff'\n\n<src>sha512(data: BytesLike)⇒ DataHexstring\nCompute the cryptographic SHA2-512 hash of data.\n\nsha512(\"0x\")\n// '0xcf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e'\n\nsha512(\"0x1337\")\n// '0x55ccb35e52b39adac42b68304bf33ff7ecb854f09b2e761e234061482e98e45b4e68de2756bcc7b7099d7dd178f04dafa229d403b90bf8884eedea3806d4642b'\n\nsha512(new Uint8Array([ 0x13, 0x37 ]))\n// '0x55ccb35e52b39adac42b68304bf33ff7ecb854f09b2e761e234061482e98e45b4e68de2756bcc7b7099d7dd178f04dafa229d403b90bf8884eedea3806d4642b'\n\nHMAC\nAn HMAC enables verification that a given key was used to authenticate a payload.\nSee: link-wiki-hmac\n\nFUNCTIONS\n<src>computeHmac(algorithm: \"sha256\" | \"sha512\", key: BytesLike, data: BytesLike)⇒ string\nReturn the HMAC for data using the key key with the underlying algo used for compression.\n\nkey = id(\"some-secret\")\n\n// Compute the HMAC\ncomputeHmac(\"sha256\", key, \"0x1337\")\n// '0xbc985612171f71b89c7561c593f2cea20038d3f38f710b2516e405085d7c0c79'\n\n// To compute the HMAC of UTF-8 data, the data must be\n// converted to UTF-8 bytes\ncomputeHmac(\"sha256\", key, toUtf8Bytes(\"Hello World\"))\n// '0xd0404ef8fae0d7f18a54a0ddfad8b81afa9e4cdab872a1dc36628c4397fd8201'\n\nPasswords\nA Password-Based Key-Derivation Function is designed to create a sequence of bytes suitible as a key from a human-rememberable password.\n\nTYPES\n<src>ProgressCallback⇒ (percent: number) => void\nA callback during long-running operations to update any UI or provide programatic access to the progress.\nThe percent is a value between 0 and 1.\n\nFUNCTIONS\n<src>pbkdf2(password: BytesLike, salt: BytesLike, iterations: number, keylen: number, algo: \"sha256\" | \"sha512\")⇒ string\nReturn the PBKDF2 for keylen bytes for password using the salt and using iterations of algo.\nThis PBKDF is outdated and should not be used in new projects, but is required to decrypt older files.\n\n// The password must be converted to bytes, and it is generally\n// best practices to ensure the string has been normalized. Many\n// formats explicitly indicate the normalization form to use.\npassword = \"hello\"\npasswordBytes = toUtf8Bytes(password, \"NFKC\")\n\nsalt = id(\"some-salt\")\n\n// Compute the PBKDF2\npbkdf2(passwordBytes, salt, 1024, 16, \"sha256\")\n// '0x226addf5b6d87544337e9733b99ceb9d'\n\n<src>scrypt(passwd: BytesLike, salt: BytesLike, N: number, r: number, p: number, dkLen: number, progress?: ProgressCallback)⇒ Promise< string >\nThe scrypt PBKDF uses a memory and cpu hard method of derivation to increase the resource cost to brute-force a password for a given key.\nThis means this algorithm is intentionally slow, and can be tuned to become slower. As computation and memory speed improve over time, increasing the difficulty maintains the cost of an attacker.\nFor example, if a target time of 5 seconds is used, a legitimate user which knows their password requires only 5 seconds to unlock their account. A 6 character password has 68 billion possibilities, which would require an attacker to invest over 10,000 years of CPU time. This is of course a crude example (as password generally aren't random), but demonstrates to value of imposing large costs to decryption.\nFor this reason, if building a UI which involved decrypting or encrypting datsa using scrypt, it is recommended to use a ProgressCallback (as event short periods can seem lik an eternity if the UI freezes). Including the phrase \"decrypting\" in the UI can also help, assuring the user their waiting is for a good reason.\n\n// The password must be converted to bytes, and it is generally\n// best practices to ensure the string has been normalized. Many\n// formats explicitly indicate the normalization form to use.\npassword = \"hello\"\npasswordBytes = toUtf8Bytes(password, \"NFKC\")\n\nsalt = id(\"some-salt\")\n\n// Compute the scrypt\nscrypt(passwordBytes, salt, 1024, 8, 1, 16)\n// Promise<'0x3982633256a26ab2e62efa0621d1a5c0'>\n\n<src>scryptSync(passwd: BytesLike, salt: BytesLike, N: number, r: number, p: number, dkLen: number)⇒ string\nProvides a synchronous variant of scrypt.\nThis will completely lock up and freeze the UI in a browser and will prevent any event loop from progressing. For this reason, it is preferred to use the async variant.\n\n// The password must be converted to bytes, and it is generally\n// best practices to ensure the string has been normalized. Many\n// formats explicitly indicate the normalization form to use.\npassword = \"hello\"\npasswordBytes = toUtf8Bytes(password, \"NFKC\")\n\nsalt = id(\"some-salt\")\n\n// Compute the scrypt\nscryptSync(passwordBytes, salt, 1024, 8, 1, 16)\n// '0x3982633256a26ab2e62efa0621d1a5c0'\n\nRandom Values\nA Cryptographically Secure Random Value is one that has been generated with additional care take to prevent side-channels from allowing others to detect it and prevent others from through coincidence generate the same values.\n\nFUNCTIONS\n<src>randomBytes(length: number)⇒ Uint8Array\nReturn length bytes of cryptographically secure random data.\n\nrandomBytes(8)\n// Uint8Array(8) [\n// 227, 172, 30, 18,\n// 233, 194, 46, 196\n// ]\n\nSigning\nAdd details about signing here.\n\nTYPES\n<src>SignatureLike⇒ Signature | string | { r: string , s: string , v: BigNumberish , yParity?: 0 | 1 , yParityAndS?: string } | { r: string , s?: string , v?: number , yParity?: 0 | 1 , yParityAndS: string } | { r: string , s: string , v?: BigNumberish , yParity: 0 | 1 , yParityAndS?: string }\nA SignatureLike\n\nclass Signature\nA Signature @TODO\n\nPROPERTIES\n<src>signature._s⇒ stringread-only\nReturn the s value, unchecked for EIP-2 compliance.\nThis should generally not be used and is for situations where a non-canonical S value might be relevant, such as Frontier blocks that were mined prior to EIP-2 or invalid Authorization List signatures.\n\n<src>signature.compactSerialized⇒ stringread-only\nThe EIP-2098 compact representation.\n\n<src>signature.legacyChainId⇒ null | bigintread-only\nThe chain ID for EIP-155 legacy transactions. For non-legacy transactions, this value is null.\n\n<src>signature.networkV⇒ null | bigintread-only\nThe EIP-155 v for legacy transactions. For non-legacy transactions, this value is null.\n\n<src>signature.r⇒ string\nThe r value for a signature.\nThis represents the x coordinate of a \"reference\" or challenge point, from which the y can be computed.\n\n<src>signature.s⇒ string\nThe s value for a signature.\n\n<src>signature.serialized⇒ stringread-only\nThe serialized representation.\n\n<src>signature.v⇒ 27 | 28\nThe v value for a signature.\nSince a given x value for r has two possible values for its correspondin y, the v indicates which of the two y values to use.\nIt is normalized to the values 27 or 28 for legacy purposes.\n\n<src>signature.yParity⇒ 0 | 1read-only\nThe yParity for the signature.\nSee v for more details on how this value is used.\n\n<src>signature.yParityAndS⇒ stringread-only\nThe EIP-2098 compact representation of the yParity and s compacted into a single bytes32.\n\nCREATING INSTANCES\n<src>Signature.from(sig?: SignatureLike)⇒ Signature\nCreates a new Signature.\nIf no sig is provided, a new Signature is created with default values.\nIf sig is a string, it is parsed.\n\nMETHODS\n<src>signature.clone()⇒ Signature\nReturns a new identical Signature.\n\n<src>signature.getCanonical()⇒ Signature\nReturns the canonical signature.\nThis is only necessary when dealing with legacy transaction which did not enforce canonical S values (i.e. EIP-155. Most developers should never require this.\n\n<src>signature.inspect()⇒ string\n\n<src>signature.isValid()⇒ boolean\nReturns true if the Signature is valid for EIP-155 signatures.\n\n<src>signature.toJSON()⇒ any\nReturns a representation that is compatible with JSON.stringify.\n\n<src>signature.toString()⇒ string\n\nSTATIC METHODS\n<src>Signature.getChainId(v: BigNumberish)⇒ bigint\nCompute the chain ID from the v in a legacy EIP-155 transactions.\n\nSignature.getChainId(45)\n// 5n\n\nSignature.getChainId(46)\n// 5n\n\n<src>Signature.getChainIdV(chainId: BigNumberish, v: 27 | 28)⇒ bigint\nCompute the v for a chain ID for a legacy EIP-155 transactions.\nLegacy transactions which use EIP-155 hijack the v property to include the chain ID.\n\nSignature.getChainIdV(5, 27)\n// 45n\n\nSignature.getChainIdV(5, 28)\n// 46n\n\n<src>Signature.getNormalizedV(v: BigNumberish)⇒ 27 | 28\nCompute the normalized legacy transaction v from a yParirty, a legacy transaction v or a legacy EIP-155 transaction.\n\n// The values 0 and 1 imply v is actually yParity\nSignature.getNormalizedV(0)\n// 27\n\n// Legacy non-EIP-1559 transaction (i.e. 27 or 28)\nSignature.getNormalizedV(27)\n// 27\n\n// Legacy EIP-155 transaction (i.e. >= 35)\nSignature.getNormalizedV(46)\n// 28\n\n// Invalid values throw\nSignature.getNormalizedV(5)\n// Error(\"invalid v\", {\n// code: \"INVALID_ARGUMENT\"\n// argument: \"v\"\n// value: 5\n// shortMessage: \"invalid v\"\n// })\n\nclass SigningKey\nA SigningKey provides high-level access to the elliptic curve cryptography (ECC) operations and key management.\n\nPROPERTIES\n<src>signingKey.compressedPublicKey⇒ stringread-only\nThe compressed public key.\nThis will always begin with either the prefix 0x02 or 0x03 and be 68 characters long (the 0x prefix and 33 hexadecimal nibbles)\n\n<src>signingKey.privateKey⇒ stringread-only\nThe private key.\n\n<src>signingKey.publicKey⇒ stringread-only\nThe uncompressed public key.\nThis will always begin with the prefix 0x04 and be 132 characters long (the 0x prefix and 130 hexadecimal nibbles).\n\nCREATING INSTANCES\n<src>new SigningKey(privateKey: BytesLike)\nCreates a new SigningKey for privateKey.\n\nMETHODS\n<src>signingKey.computeSharedSecret(other: BytesLike)⇒ string\nReturns the ECDH shared secret between this private key and the other key.\nThe other key may be any type of key, a raw public key, a compressed/uncompressed pubic key or aprivate key.\nBest practice is usually to use a cryptographic hash on the returned value before using it as a symetric secret.\n\nsign1 = new SigningKey(id(\"some-secret-1\"))\nsign2 = new SigningKey(id(\"some-secret-2\"))\n\n// Notice that privA.computeSharedSecret(pubB)...\nsign1.computeSharedSecret(sign2.publicKey)\n// '0x04b5bc2a5428042331a4c70da8f090d5552bdb35bc08a00ea8ed0a9b6d8737b8b7ea016b268d7cb9f02e11736b82b129ea3f37a8fdc6a7b0e9f5cdde4105ceb0de'\n\n// ...is equal to privB.computeSharedSecret(pubA).\nsign2.computeSharedSecret(sign1.publicKey)\n// '0x04b5bc2a5428042331a4c70da8f090d5552bdb35bc08a00ea8ed0a9b6d8737b8b7ea016b268d7cb9f02e11736b82b129ea3f37a8fdc6a7b0e9f5cdde4105ceb0de'\n\n<src>signingKey.sign(digest: BytesLike)⇒ Signature\nReturn the signature of the signed digest.\n\nSTATIC METHODS\n<src>SigningKey.addPoints(p0: BytesLike, p1: BytesLike, compressed?: boolean)⇒ string\nReturns the point resulting from adding the ellipic curve points p0 and p1.\nThis is not a common function most developers should require, but can be useful for certain privacy-specific techniques.\nFor example, it is used by HDNodeWallet to compute child addresses from parent public keys and chain codes.\n\n<src>SigningKey.computePublicKey(key: BytesLike, compressed?: boolean)⇒ string\nCompute the public key for key, optionally compressed.\nThe key may be any type of key, a raw public key, a compressed/uncompressed public key or private key.\n\nsign = new SigningKey(id(\"some-secret\"));\n\n// Compute the uncompressed public key for a private key\nSigningKey.computePublicKey(sign.privateKey)\n// '0x04925bec9818e11ac806bf8b142a7965ac9231aaa9d23f256795d63b1d8d7f203f7481609b6a6964a0f5b459585e9d18a9ec9070d0baf24689138868811c974c96'\n\n// Compute the compressed public key for a private key\nSigningKey.computePublicKey(sign.privateKey, true)\n// '0x02925bec9818e11ac806bf8b142a7965ac9231aaa9d23f256795d63b1d8d7f203f'\n\n// Compute the uncompressed public key\nSigningKey.computePublicKey(sign.publicKey, false);\n// '0x04925bec9818e11ac806bf8b142a7965ac9231aaa9d23f256795d63b1d8d7f203f7481609b6a6964a0f5b459585e9d18a9ec9070d0baf24689138868811c974c96'\n\n// Compute the Compressed a public key\nSigningKey.computePublicKey(sign.publicKey, true);\n// '0x02925bec9818e11ac806bf8b142a7965ac9231aaa9d23f256795d63b1d8d7f203f'\n\n<src>SigningKey.recoverPublicKey(digest: BytesLike, signature: SignatureLike)⇒ string\nReturns the public key for the private key which produced the signature for the given digest.\n\nkey = new SigningKey(id(\"some-secret\"))\ndigest = id(\"hello world\")\nsig = key.sign(digest)\n\n// Notice the signer public key...\nkey.publicKey\n// '0x04925bec9818e11ac806bf8b142a7965ac9231aaa9d23f256795d63b1d8d7f203f7481609b6a6964a0f5b459585e9d18a9ec9070d0baf24689138868811c974c96'\n\n// ...is equal to the recovered public key\nSigningKey.recoverPublicKey(digest, sig)\n// '0x04925bec9818e11ac806bf8b142a7965ac9231aaa9d23f256795d63b1d8d7f203f7481609b6a6964a0f5b459585e9d18a9ec9070d0baf24689138868811c974c96'\n\n← Contracts\nHashing Utilities→\n\nThe content of this site is licensed under the Creative Commons License. Generated on September 6, 2025, 2:21am.","tokens":3778,"crawled_at":1791193811837}
+{"id":10292,"url":"https://www.metaplex.com/docs/smart-contracts/core/using-core-in-anchor","domain":"www.metaplex.com","chapter":"docs","title":"Using Metaplex Core in Anchor | Metaplex Core","text":"Build on-chain programs that interact with Core Assets using Anchor. This guide covers installation, account deserialization, plugin access, and CPI patterns.\nWhat You'll Learn\nInstall and configure mpl-core in Anchor projects\nDeserialize Core Assets and Collections in your programs\nAccess plugin data (Attributes, Freeze, etc.)\nMake CPI calls to create, transfer, and manage Assets\n\nSummary\nThe mpl-core Rust crate provides everything needed to interact with Core from Anchor programs. Enable the anchor feature flag for native Anchor account deserialization.\nAdd mpl-core with default-features = false and the appropriate Anchor features\nUse features = [\"anchor\", \"anchor-0-32\"] with anchor-lang 0.32.x\nUse features = [\"anchor\"] with anchor-lang 0.31.x\nDeserialize Assets/Collections in Accounts structs\nUse fetch_plugin() to read plugin data\nCPI builders simplify instruction calls\nOut of Scope\nClient-side JavaScript SDK (see JavaScript SDK), standalone Rust clients (see Rust SDK), and creating Core Assets from clients.\nQuick Start\nJump to: Installation · Account Deserialization · Plugin Access · CPI Examples\nAdd mpl-core with default-features = false and Anchor features to Cargo.toml\nPin Rust 1.89.0 or newer in rust-toolchain.toml\nDeserialize Assets with Account<'info, BaseAssetV1>\nAccess plugins with fetch_plugin::<BaseAssetV1, PluginType>()\nMake CPI calls with CreateV2CpiBuilder, TransferV1CpiBuilder, etc.\nInstallation\nAdd mpl-core to your Anchor program's Cargo.toml. The default borsh-v1 feature is incompatible with Anchor integration, so always disable default features when enabling anchor.\nFeature Flags\nFeatureDescription\nanchor\nEnables Anchor account deserialization using anchor-lang 0.31.1 and Solana 2.x types\n\nanchor-0-32\nOpt-in support for anchor-lang 0.32.x; requires anchor\n\nserde\nOptional serde support for off-chain tooling\n\nAnchor 0.32.x (recommended)\nUse this when your program depends on anchor-lang 0.32.x:\n[dependencies]\n\nanchor-lang = \"0.32.1\"\n\nmpl-core = { version = \"x.x.x\", default-features = false, features = [\"anchor\", \"anchor-0-32\"] }\n\nAnchor 0.31.x (legacy)\nUse this when your program depends on anchor-lang 0.31.x:\n[dependencies]\n\nanchor-lang = \"0.31.1\"\n\nmpl-core = { version = \"x.x.x\", default-features = false, features = [\"anchor\"] }\n\nImportant\nanchor-0-32 alone is not enough — it must be combined with anchor.\ndefault-features = false is required. Without it, the default borsh-v1 feature conflicts with Anchor integration.\nThe Anchor path uses Solana 2.x types for Pubkey, AccountInfo, and related Anchor traits.\n\nRust Toolchain\nmpl-core requires Rust 1.89.0 or newer. Add a rust-toolchain.toml file to your Anchor workspace:\n[toolchain]\n\nchannel = \"1.89.0\"\n\nIf your build fails with an edition2024 error from transitive dependencies such as base64ct, upgrade to Rust 1.89.0 or newer.\nCore Rust SDK Modules\nThe Core Rust SDK is organized into several modules:\naccounts: represents the program's accounts.\nerrors: enumerates the program's errors.\ninstructions: facilitates the creation of instructions, instruction arguments, and CPI instructions.\ntypes: represents types used by the program. For more detailed information on how different instructions are called and used, refer to the mpl-core docs.rs website or you can use cmd + left click (mac) or ctrl + left click (windows) on the instruction to expand it.\nAccounts Deserialization\nDeserializable Accounts\nThe following account structs are available for deserialization within the mpl-core crate:\n- BaseAssetV1\n\n- BaseCollectionV1\n\n- HashedAssetV1\n\n- PluginHeaderV1\n\n- PluginRegistryV1\n\nThere are two ways to deserialize Core accounts within Anchor.\nUsing Anchors Account list struct (recommended in most cases),\nDirectly in the instruction functions body using <Account>::from_bytes().\nAnchor Accounts List Method\nBy activating the anchor flag you'll be able to deserialize both the BaseAssetV1 and BaseCollectionV1 accounts directly in the Anchor Accounts list struct:\nAccounts Deserialization\n\n#[derive(Accounts)]\n\npub struct ExampleAccountStruct<'info> {\n\n...\n\npub asset: Account<'info, BaseAssetV1>,\n\n}\n\nAccount from_bytes() Method\nBorrow the data inside the asset/collection account using the try_borrow_data() function and create the asset/collection struct from those bytes:\nAccounts Deserialization\n\nlet data = ctx.accounts.asset.try_borrow_data()?;\n\nlet base_asset: BaseAssetV1 = BaseAssetV1::from_bytes(&data.as_ref())?;\n\nDeserializing Plugins\nTo access individual plugins within an Asset or Collection account, use the fetch_plugin() function. This function will either return the plugin data or a null response without throwing an hard error, allowing you to check if a plugin exists without having to access its data. The fetch_plugin() function is used for both Assets and Collections accounts and can handle every plugin type by specifying the appropriate typing. If you want to access the data inside a plugin, use the middle value returned by this function.\nPlugins Deserialization\n\nlet (_, attribute_list, _) = fetch_plugin::<BaseAssetV1, Attributes>(&ctx.accounts.asset.to_account_info(), mpl_core::types::PluginType::Attributes)?;\n\nNote: The fetch_plugin() function is only used for non-external plugins. To read external plugins, use the fetch_external_plugin() function, which operates in the same way as fetch_plugin().\nThe CPI Instruction Builders\nEach instruction from the Core crate comes with a CpiBuilder version. The CpiBuilder version is created using name of the instruction + CpiBuilder and simplifies the code significantly abstracting a lot of boilerplate code away! If you want to learn more about all the possible instruction available in Core, you can find them on the mpl-core docs.rs website\nCPI Example\nLet's take the CreateCollectionV2CpiBuilder instruction as an example Initialize the builder by calling new on the CpiBuilder and passing in the core program as AccountInfo:\nCreateCollectionV2CpiBuilder::new(ctx.accounts.mpl_core_program.to_account_info);\n\nUse then Cmd + left click (Ctrl + left click for Windows users) to view all the CPI arguments required for this CPI call:\nCreateCollectionV2CpiBuilder::new(&ctx.accounts.core_program)\n\n.collection(&ctx.accounts.collection)\n\n.payer(&ctx.accounts.payer)\n\n.system_program(&ctx.accounts.system_program)\n\n.name(\"Test Collection\".to_string())\n\n.uri(\"https://test.com\".to_string())\n\n.invoke()?;\n\nCommon Errors\nAccountNotInitialized\nThe Asset or Collection account doesn't exist or hasn't been created yet.\nPluginNotFound\nThe plugin you're trying to fetch doesn't exist on the Asset. Check with fetch_plugin() which returns None safely.\nInvalidAuthority\nThe signer doesn't have permission for this operation. Verify the correct authority is signing.\nNotes\nAlways set default-features = false when enabling Anchor features\nUse features = [\"anchor\", \"anchor-0-32\"] with anchor-lang 0.32.x\nUse features = [\"anchor\"] with anchor-lang 0.31.x\nPin Rust 1.89.0 or newer in rust-toolchain.toml\nUse fetch_plugin() for built-in plugins, fetch_external_plugin() for external\nCPI builders abstract away account ordering complexity\nCheck docs.rs/mpl-core for complete API reference\nQuick Reference\nCommon CPI Builders\nOperationCPI Builder\nCreate Asset\nCreateV2CpiBuilder\n\nCreate Collection\nCreateCollectionV2CpiBuilder\n\nTransfer Asset\nTransferV1CpiBuilder\n\nBurn Asset\nBurnV1CpiBuilder\n\nUpdate Asset\nUpdateV1CpiBuilder\n\nAdd Plugin\nAddPluginV1CpiBuilder\n\nUpdate Plugin\nUpdatePluginV1CpiBuilder\n\nAccount Types\nAccountStruct\nAsset\nBaseAssetV1\n\nCollection\nBaseCollectionV1\n\nHashed Asset\nHashedAssetV1\n\nPlugin Header\nPluginHeaderV1\n\nPlugin Registry\nPluginRegistryV1\n\nFAQ\nDo I need the anchor feature flag?\nYes, for direct deserialization in Accounts structs. Without it, use from_bytes() manually. Always set default-features = false when enabling anchor.\nWhich Anchor version should I use?\nFor anchor-lang 0.32.x, use default-features = false with features = [\"anchor\", \"anchor-0-32\"]. For anchor-lang 0.31.x, use features = [\"anchor\"] only.\nWhat Rust version is required?\nmpl-core requires Rust 1.89.0 or newer. Pin it in rust-toolchain.toml in your Anchor project.\nHow do I check if a plugin exists?\nUse fetch_plugin() which returns Option - it won't throw an error if the plugin doesn't exist.\nCan I access external plugins (Oracle, AppData)?\nYes. Use fetch_external_plugin() instead of fetch_plugin() with the appropriate key.\nWhere can I find all available instructions?\nSee the mpl-core docs.rs instructions module.\nGlossary\nTermDefinition\nCPI\nCross-Program Invocation - calling one program from another\n\nCpiBuilder\nHelper struct for constructing CPI calls\n\nBaseAssetV1\nCore Asset account struct for deserialization\n\nfetch_plugin()\nFunction to read plugin data from accounts\n\nanchor feature\nCargo feature enabling Anchor-native deserialization\n\nanchor-0-32 feature\nOpt-in Cargo feature for anchor-lang 0.32.x support\n\nRelated Pages\nAnchor Staking Example - Complete staking program\nCreate Asset with Anchor - Step-by-step guide\nRust SDK - Standalone Rust client usage\nmpl-core docs.rs - Complete API reference","tokens":2276,"crawled_at":1791193830022}
+{"id":10293,"url":"https://a16zcrypto.com/posts/article/ethereum-roadmap-focil-and-multi-proposers","domain":"a16zcrypto.com","chapter":"research","title":"A look down Ethereum’s roadmap: The cases for FOCIL and multi-proposer schemes - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nA look down Ethereum’s roadmap: The cases for FOCIL and multi-proposer schemes\nPranav Garimidi\n11.11.24\n\nTags & Share Tags\nEthereum\nresearch\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nEthereum now supports a vibrant ecosystem of applications and Layer 2s. But its transaction supply chain, which determines which transactions land onchain, enshrines certain participants with market power, harming the chain’s economic efficiency.\n\nMany issues with Ethereum’s transaction supply chain stem from the fact that for every slot, a single proposer has monopoly control over what transactions to include in their block. Proposers also have incentives offchain and from the application layer that affect their behavior. These sometimes competing incentives make it difficult to encourage proposers to honestly follow the protocol.\n\nTwo types of proposer deviations are of particular concern: (1) short-term censorship, and (2) acting on enshrined latency advantages.\n\nHow to prioritize and address these two problems depends on Ethereum’s development roadmap. If Ethereum has to solve short-term censorship resistance, constrained single proposer designs have appealing properties while also being close to well specified enough with proposals like FOCIL to be implemented. But if Ethereum’s success also relies on addressing some of the negative market effects of single proposer schemes on the application layer, more drastic change likely needs to happen. Multi-proposer schemes look promising to address the broader concerns.\n\nThe rest of this post describes these problems in more detail before getting into how these issues impact Ethereum’s functionality. I’ll then analyze the two potential solutions to address them — the implementation of which depends on Ethereum’s roadmap.\n\nProblem 1: Short-term censorship\n\nBlockchains inherent censorship resistance from liveness: Eventually every valid submitted transaction will make it onchain. But the bounds on how long a transaction will take to be included onchain are too loose for many applications. DeFi transactions are a common example, where it might be only a few seconds until a transaction is stale. In these scenarios, a proposer could stand to gain by censoring a transaction even for a single block, degrading the efficiency of these applications.\n\nConsider the case where a dapp wants to sell an item every slot via a first price auction. Assume this item has a common value of $10; thus in a competitive auction we’d expect the dapp to receive around $10. But since the auction takes place over the course of a slot, all the bids from the auction need to be included by the proposer. In a single proposer scheme, the proposer could simply exclude others’ bids, and include only their own low bid, winning the item for much less than the item is worth.\n\nSuch instances require a notion of short-term censorship resistance that captures how hard it is for an adversary to censor a transaction for a single block. Short-term censorship resistance is an economic property. If more transactions demand to be included in a block than there is space, some of the transactions must be left out. Those transactions aren’t necessarily being censored by an adversary; rather, they are simply priced out of inclusion. However, some protocols make it easier for an adversary to either price out or incentivize the proposer not to include target transactions. In the spirit of saying protocol A is more censorship resistant than protocol B if it is more difficult for an adversary to censor a target transaction in A than B, we use the following definition:\n\nProtocol A is more short-term censorship resistant than protocol B if all else equal, for any transaction t, the minimum net payments an adversary has to make to prevent t from being included at equilibrium in a given block is higher under A than B.\n\n(This definition is intentionally not well defined mathematically. Formally defining the game being played and the equilibrium concept will be the subject of future work. For now, the examples convey the spirit of this definition.)\n\nExample\n\nWith Ethereum using EIP-1559 as its fee mechanism, an adversary simply needs to pay the proposer more than a transaction’s tip above the base fee to not include it.\n\nIf the fee mechanism is a first-price auction, an adversary would have to pay the proposer more than the entirety of a user’s bid to incentivize them to not include the transaction.\n\nNote that bidders are expected to only pay tiny tips under EIP-1559. Thus while the bids under a first price auction are expected to be relatively small in comparison to a transaction’s true value, they are still substantially higher than what the transaction’s tip would be in EIP-1559. Thus we would say that Ethereum using a first price auction as its TFM is more short-term censorship resistant than Ethereum using EIP-1559. In either case, however, if the equilibrium price for inclusion for a Defi transaction is high enough to deter an adversary, users now have to pay a hefty tax to the protocol in turn making the Defi app itself less attractive.\n\nProblem 2: Enshrined proposer latency advantages\n\nIn a single proposer architecture, the proposer is by design the last one to move in the block production game for a given slot. (In practice there is a complicated offchain transaction supply chain where relays move last. For the purposes of this post we treat proposers and builders as combined.) This means that proposers can always submit transactions that reflect a “fresher” state compared to any other submitted transactions. Even if both users and the proposer receive information simultaneously, it takes time for users to send their transactions to the proposer, during which new information might arrive. The proposer is in a position to instantly react to this information and potentially change their transaction, but the user has no time to do this.\n\nFor example, the optimal way to route a trade onchain may depend on the offchain ETH-USD price on Binance. In a single proposer architecture, a sophisticated proposer can submit trades that are more up-to-date than any users competing for the same trade.\n\nExample\n\nConsider our previous example of a dapp selling an item every slot via first-price auction. But now the item’s value is a function of constantly updating information. Assume there are two bidders competing for the item, agents 1 and 2. Both agents hear new information simultaneously, except agent 1 always gets to bid after agent 2. In this case, agent 2 is adversely selected against when they win because the only time bidder 2 wins is when the information updates after they submit their bid to the point that they are over paying. Otherwise, whenever the information changes so that bidder 2’s bid is profitable, bidder 1 will simply update their bid in response to the newer information and win the auction. This effect is especially stark when agent 1 can directly observe agent 2’s bid, but even if agent 1 can’t see agent 2’s bid, agent 1 still has a substantial competitive advantage. In the long run, agent 2 will not find it worth it to participate, letting agent 1 capture all the value from the auction.\n\nThis example shows how structural advantages given to the proposer can cause competition to dry up and drive all the surplus value from onchain markets to the proposer.\n\nPossible solutions depend on the roadmap\n\nThe extent to which short-term censorship resistance and proposer latency advantages matter depend on the Ethereum development roadmap. One vision for Ethereum’s future is fully embracing the L2 roadmap and having all meaningful execution happen offchain, with Ethereum being used for settlement, data availability, and proof-verification. In such a world, short-term censorship is the main problem, although achieving it over the span of ~10 blocks may be sufficient rather than the block-level guarantees we described above. An alternative path is for Ethereum to serve as a hub for high value execution, and in particular for high-value Defi. In this world, achieving strong short-term censorship resistance and alleviating proposers’ strong structural economic advantages becomes essential.\n\nTwo alternatives help address these problems. The first is a constrained single proposer architecture that adds committees which bind the proposer’s action space. The second is a multi-proposer architecture that looks dramatically different from Ethereum’s current design: It splits the proposer’s power among many different parties.\n\nWhile both designs are still in active development, there have been proposals of what these architectures might look like. We outline what these proposals look like and analyze how they address the problems we’ve discussed.\n\nA case for FOCIL\n\nConstrained single proposer architecture\n\nA constrained single proposer architecture is one where a committee within the same block imposes constraints on the proposer. Inclusion lists (ILs) are the most natural example of this, where an inclusion committee enforces that a block proposer include certain transactions the committee hears about.\n\nThe amount of power the committee has varies in different designs. One important distinction is between unconditional and conditional inclusion lists. With unconditional inclusion lists, the transactions the committee includes must be included by a proposer for the block to be valid. With conditional inclusion lists, a block only has to include the contents of the inclusion list conditioned on the block not being full, meaning that if the proposer fills the entire block with their own transactions, they aren’t required to include any transactions in the inclusion list. While unconditional ILs can offer better short-term censorship resistance, they might also be easier to crowd out because they might be used to offer products like preconfirmations.\n\nThe latest proposal for a constrained single proposer design on Ethereum is called FOCIL (fork choice conditional inclusion lists), which lays out how to implement inclusion lists (FOCIL is not explicitly designed to deal with high-value MEV transactions but is instead optimized for censorship resistance over the span of a few blocks. Nevertheless, as it’s the most concrete specification of what a constrained-single proposer architecture could look like, it’s useful to analyze it in this setting.)\n\nThe high-level design is as follows (for details, see “FOCIL CL & EL workflow”): Every slot a subset of validators are chosen as inclusion committee members. Committee members construct their lists of transactions up to a local IL size limit (in KB). These lists are locked ¾ of the way through the slot and gossiped to the proposer, who is then responsible for appending any transactions they are missing in the list to their block, until their block hits the gas limit. Then, in addition to standard block validity rules, attesters also check that proposed blocks are conformant against the corresponding inclusion lists. Note, there are no economic incentives in the protocol for the inclusion list committee to act honestly.\n\nAnalysis\n\nShort-term censorship resistance\n\nThe short-term censorship resistance of a constrained single proposer scheme depends on what types of constraints are allowed and how the proposer is bound to them. As we define short-term censorship via an economic model, the details of how the inclusion committee is incentivized can also change the relative power of these mechanisms. We will start by analyzing FOCIL with EIP-1559 as the L1 TFM before expanding on what is possible in the space of constrained single proposer mechanisms.\n\nSince FOCIL does not explicitly incentivize the inclusion committee to include any transactions, let’s assume that the inclusion list committee is non-strategic and acts honestly. FOCIL also doesn’t specify what inclusion rule honest IL committee members should follow, but for our analysis we assume that honest IL members will include transactions they hear about with the highest priority fees. (FOCIL’s goal is to also increase censorship resistance on longer time scales than a slot, so the intention is that some committee members also follow inclusion rules such as including transactions that have been in the mempool the longest.)\n\nNow consider an instance where an adversary is targeting a transaction that tips $10 on top of the base fee, and that $10 is sufficiently high to make the transaction included in the IL. The adversary here has two options. They can either send enough transactions above a $10 tip in the mempool to kick the target transaction out of the IL while also bribing the proposer $10 to not include the target; or the adversary could send enough transactions to fill the proposer’s block and also still send the proposer with $10 to not include the target transaction. Either of these strategies is significantly more expensive for the adversary than the status quo of only paying the proposer $10 to not include the target transaction. In the former case, the adversary has to pay the priority fee plus base fee for any of the transactions that ends up landing on chain; in the later case the adversary has to pay at least the base fee to fill the entire block (assuming EIP-1559 as the base layer TFM).\n\nIf FOCIL instead used unconditional inclusion lists, the second attack vector would be ruled out. Thus, if the target transaction had a high tip, then the adversary would be put in the position of filling the IL gas limit with transactions having tips above the target, which is potentially much more expensive than paying the base fee to fill the entire block.\n\nThe key assumption in this analysis is that the IL committee acts honestly while being non-strategic. If the inclusion committee were strategic, then the adversary could pay them an arbitrarily small amount to produce empty lists in the current protocol. Without any mechanism incentivizing the IL committee to follow the protocol, analyzing the short-term censorship resistance of these protocols reduces to the standard single proposer case. Fee mechanism design that allows fees of transactions included by the IL committee to go to the IL committee can help increase the robustness of these protocols, but the details of such designs and the properties they would satisfy are the subject of future work (for instance, see this example).\n\nProposer latency advantage\n\nConstraints like ILs alone don’t help address proposers’ latency advantages. In these designs, the single proposer still moves last and still has the power to insert whatever transactions they like. In general, the constrained single proposer setting has difficulty addressing this problem because any form of a constraint committee must act before the end of a slot for the proposer to have time to hear the outcome of the constraint and act accordingly. Thus, the proposer has the privileged position to act on any information that arrives in this duration. The only way around this is for a committee, rather than the proposer, to end the block production game, in which case we move toward a multi-proposer architecture.\n\nA case for multi-proposer\n\nMulti-proposer architecture\n\nA multi-proposer architecture explicitly has multiple proposers jointly building a block every slot. Many potential instantions exist, but multi-proposer schemes generally have a similar structure: A set of validators is chosen randomly by stake as proposers in a given slot. At the end of the slot, each chosen validator proposes a set of transactions following a local block validity rule. Then the protocol deterministically aggregates these proposals into a single canonical block.\n\nThe key feature of multi-proposer schemes is that no single proposer is given special power over what gets included in a block. Even though the multiple proposers in such a scheme have advantages compared to non-proposers, the competition between proposers themselves can lead to improved market equilibria.\n\nAs opposed to the constrained single proposer setting that is additive to the current Ethereum protocol, a multi-proposer architecture would require a fundamental rework of Ethereum. As such, many components have to be reasoned about, including the transaction supply chain, consensus, and fee mechanisms. Here, we will consider an idealized model of a multi-proposer architecture where the consensus details are worked out and we can focus on a single slot in isolation. Assumptions include that all the proposers are homogenous and have equal access to information, and that the aggregation rule is simply taking a union over all proposed transactions. (This analysis holds for any reasonable choice of ordering rule.) A large part of bringing multi-proposer to production will be relaxing these assumptions to create a full specification, but even with this simple model there is still much to consider.\n\nAnalysis\n\nShort-term censorship resistance\n\nThe short-term censorship resistance of a multi-proposer architecture depends on the TFM being used. For example, schemes that evenly distribute fees across all proposers and are pay-as-bid for users can incentivize better throughput but worse short-term censorship resistance than you would get from current single proposer schemes. On the other hand, some proposal TFMs look to take advantage of multi-proposer architectures to get more censorship resistance than would be possible in a single proposal scheme.\n\nFor example, Fox, Pai, and Resnick. make the observation that having a transaction’s payment be a function of how many proposers include a transaction can drastically increase the cost to censor the transaction. Their TFM has users submit a pair of bids (t,T) with t<<T. If k>1 proposers include the transaction. The transaction pays kt with t going to each of the corresponding proposers. However, if only one proposer includes the transaction, then the transaction pays T to the single block producer. Hence, an adversary has to pay kT to censor the transaction, since any validator can unilaterally deviate to include the transaction if no one else is, while the transaction only expects to pay Θ(t) for inclusion.\n\nThis gap between how much a transaction has to pay for inclusion and the cost to censor it, is a key property that comes from proposers competing among themselves. A censoring adversary needs to make payments such that none of the proposers include the transaction. Of course, if the proposers all collude, this analysis breaks down and the benefits of multi-proposer is lost — potentially leaving us in a worse situation than the single proposer case. However, as the number of concurrent proposers increases, both the amount an adversary has to pay to induce a censoring equilibrium and the difficulty of maintaining the collusion increase since even one proposer deviating from the censoring ring would be sufficient to regain short-term censorship resistance properties.\n\nProposer latency advantage\n\nAssume no proposer can see other proposers’ blocks before they make their own block. Perfect synchrony could achieve this, but, more practically, cryptography can achieve the same end. Proposers can use time lock encryption to have their block contents hidden only for a few seconds. Thus, if proposers all release their blocks a couple seconds before the end of the slot, proposers can’t see each other’s blocks until the slot has passed. Instead of time lock encryption we could also threshold encrypt block contents to an attester committee to achieve a similar property.\n\nGiven this assumption, there is no party who moves last to end the block production game. This means that proposers are forced to compete with one another on an equal playing field to take advantage of opportunities at the application layer. As new information comes in, all proposers are in an equal position to react and update their transactions. This competition then keeps this value within the application layer and allows a competitive market to exist instead of having the market unravel and letting the value all leak to a single proposer. Note, however, that a multi-proposer scheme doesn’t change the structural advantage proposers have over users, since users still face a latency delay in getting their transactions to the proposer. But now instead of a single party with the advantage, there are multiple parties with equal advantages.\n\nThe exact details of how to implement the cryptography so proposers can’t see each others’ blocks before they propose their own are crucial to maintaining this property. Otherwise, certain proposers again have structural market advantages over others, degrading the competitiveness of onchain markets. These specifications are still largely works in progress.\n\n***\n\nIf the main concern Ethereum has to solve is short-term censorship resistance, constrained single proposer designs have appealing properties while also being close to well specified enough with proposals like FOCIL to be implemented. On the other hand, if Ethereum’s success also relies on addressing some of the negative market effects of single proposer schemes on the application layer, more drastic change is likely needed. Multi-proposer schemes look promising to address the broader space of issues. But since these designs completely restructure the Ethereum stack, they have a longer path ahead of them in getting to a complete specification and addressing all the potential second-order effects of such large changes.\n\n***\n\nAcknowledgments: Thanks to Barnabe, Joachim, Julian, Max, and Thomas for helpful comments and suggestions\n\n***\n\nPranav Garimidi is a research analyst at a16z crypto. He focuses on mechanism design and algorithmic game theory as it relates to blockchain systems. He is especially interested in how incentives interact across the blockchain stack. Prior to a16z, Pranav was a student at Columbia University where he graduated with a degree in Computer Science. You can follow him on X @pgarimidi\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investment-list/.\n\nThe content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures/ for additional important information","tokens":6153,"crawled_at":1791193815939}
+{"id":10294,"url":"https://docs.dydx.xyz/nodes/full-node-streaming/example","domain":"docs.dydx.xyz","chapter":"defi_protocols","title":"gRPC Streaming Example – dYdX Documentation","text":"Indexer-based orderbook streaming, due to the increased latency introduced by the Indexer, can cause issues like more outdated orders or a crossed orderbook.\nIn a full node, the orderbook available will be more up-to-date and should be preferred over the Indexer-based solution.\nThis requires a full node with gRPC streaming enabled.\n\nIn this example, we'll guide on how to connect and handle the gRPC data in order to enable use-cases such as orderbook watching.\nWhile full node streaming is provided both using gRPC and WebSockets, we'll focus here on gRPC-based streaming due to its higher efficiency.\n\nInstall dependencies\n\ngRPC uses structured and serialized data using Protocol Buffers.\nFor Python, install the package v4-proto which already contains the messages and generated code used in gRPC.\nThis is the main dependency used in this guide, allowing us to deserialize the incoming stream messages.\n\nEstablish a connection\n\nWith a full node with gRPC streaming available, we can now try to establish a connection to it. We'll need to define a gRPC configuration to maintain an healthy connection.\nLets also define here the CLOB pairs IDs (markets) that we are interested in, as well as the relevant subaccounts.\nPython\nimport grpc\nfrom v4_proto.dydxprotocol.clob.query_pb2 import StreamOrderbookUpdatesRequest\nfrom v4_proto.dydxprotocol.clob.query_pb2_grpc import QueryStub\nfrom v4_proto.dydxprotocol.subaccounts.subaccount_pb2 import SubaccountId\n\nGRPC_OPTIONS = [\n# Send keepalive ping every 30 seconds\n(\"grpc.keepalive_time_ms\", 3000),\n# Wait 10 seconds for ping ack before considering the connection dead\n(\"grpc.keepalive_timeout_ms\", 1000,),\n# Allow keepalive pings even when there are no calls\n(\"grpc.keepalive_permit_without_calls\", True,),\n# Minimum allowed time between pings\n(\"grpc.http2.min_time_between_pings_ms\", 3000,),\n# Minimum allowed time between pings with no data\n(\"grpc.http2.min_ping_interval_without_data_ms\", 3000,),\n]\n\nendpoint = \"your-node-address:9090\"\nclob_pair_ids = [0, 1] # ETH-USD\nsubaccount_ids = [] # All subaccounts\n\n# Establish async connection\nasync with grpc.aio.insecure_channel(endpoint, GRPC_OPTIONS) as channel:\ntasks = [\nlisten_to_grpc_stream(\nchannel,\nclob_pair_ids,\nsubaccount_ids,\nfeed_handler,\n),\n]\nawait asyncio.gather(*tasks)\n\nStreaming\n\nThe streaming function listen_to_grpc_stream() processes the continuous stream of orderbook updates. Each message contains batched updates that must be processed sequentially to maintain correct state.\nPython\nasync def listen_to_grpc_stream(\nchannel: grpc.Channel,\nclob_pair_ids: List[int],\nsubaccount_ids: List[str],\nfeed_handler: FeedHandler,\n):\n\"\"\"Subscribe to gRPC stream and handle orderbook updates.\"\"\"\nstub = QueryStub(channel)\n\n# Parse subaccount ids (format: owner_address/subaccount_number)\nsubaccount_protos = [\nSubaccountId(owner=sa.split('/')[0], number=int(sa.split('/')[1]))\nfor sa in subaccount_ids\n]\n\nrequest = StreamOrderbookUpdatesRequest(\nclob_pair_id=clob_pair_ids,\nsubaccount_ids=subaccount_protos\n)\n\nasync for response in stub.StreamOrderbookUpdates(request):\nfill_events = feed_handler.handle(response)\n# Process fills and other updates\nfor fill in fill_events:\nprint(f\"Fill: {fill.quantums} @ {fill.subticks}\")\n\nMaintaining Orderbook and Subaccount State\n\nLets add a component FeedHandler that maintains local state by processing streaming updates.\nIt will handle different message types and ensure state consistency.\nPython\nclass FeedHandler:\ndef __init__(self):\nself.books: Dict[int, LimitOrderBook] = {}\nself.subaccounts: Dict[SubaccountId, StreamSubaccount] = {}\nself.has_seen_first_snapshot = False\n\ndef handle(self, message: StreamOrderbookUpdatesResponse) -> List[Fill]:\n\"\"\"Handle incoming stream messages and update state.\"\"\"\ncollected_fills = []\n\nfor update in message.updates:\nupdate_type = update.WhichOneof('update_message')\n\nif update_type == 'orderbook_update':\nself._handle_orderbook_update(update.orderbook_update)\nelif update_type == 'order_fill':\nfills = self._handle_fills(update.order_fill, update.exec_mode)\ncollected_fills += fills\nelif update_type == 'subaccount_update':\nself._handle_subaccounts(update.subaccount_update)\n\nreturn collected_fills\n\nSnapshots\n\nSnapshots provide the complete current state and serve as the foundation for processing subsequent incremental updates. The client should wait for snapshots before processing any other messages to ensure state consistency.\n\nDiscard order messages until you receive a StreamOrderbookUpdate with snapshot set to true. This message contains the full orderbook state for each clob pair.\n\nSimilarly, discard subaccount messages until you receive a StreamSubaccountUpdate with snapshot set to true. This message contains the full subaccount state for each subscribed subaccount.\n\ndef _handle_orderbook_update(self, update: StreamOrderbookUpdate):\n\"\"\"Handle orderbook snapshots and incremental updates.\"\"\"\n# Skip messages until the first snapshot is received\nif not self.has_seen_first_snapshot and not update.snapshot:\nreturn\n\n# Skip subsequent snapshots\nif update.snapshot and self.has_seen_first_snapshot:\nlogging.warning(\"Skipping subsequent snapshot\")\nreturn\n\nif update.snapshot:\n# This is a new snapshot of the book state\nif not self.has_seen_first_snapshot:\nself.has_seen_first_snapshot = True\n\n# Process each update in the batch\nfor u in update.updates:\nupdate_type = u.WhichOneof('update_message')\n\nif update_type == 'order_place':\nself._handle_order_place(u.order_place)\nelif update_type == 'order_update':\nself._handle_order_update(u.order_update)\nelif update_type == 'order_remove':\nself._handle_order_remove(u.order_remove)\n\ndef _handle_subaccounts(self, update: StreamSubaccountUpdate):\n\"\"\"Handle subaccount snapshots and updates.\"\"\"\nparsed_subaccount = parse_subaccounts(update)\nsubaccount_id = parsed_subaccount.subaccount_id\n\nif update.snapshot:\n# Skip subsequent snapshots\nif subaccount_id in self.subaccounts:\nlogging.warning(f\"Saw multiple snapshots for subaccount {subaccount_id}\")\nreturn\nself.subaccounts[subaccount_id] = parsed_subaccount\nelse:\n# Skip messages until the first snapshot is received\nif subaccount_id not in self.subaccounts:\nreturn\n# Update the existing subaccount\nexisting_subaccount = self.subaccounts[subaccount_id]\nexisting_subaccount.perpetual_positions.update(parsed_subaccount.perpetual_positions)\nexisting_subaccount.asset_positions.update(parsed_subaccount.asset_positions)\n\nOrderbook Management\n\nThe orderbook is implemented as a Level 3 (L3) order book that maintains individual orders with their full details. This provides maximum granularity for trading applications that need to track specific orders and their execution.\nLets implement an efficient Orderbook data structure named LimitOrderBook suitable for high-frequency trading.\nEach price level maintains orders in a doubly-linked list for efficient insertion and removal.\nOrders progress through a lifecycle of placement, updates, and removal. Your client must handle each stage correctly to maintain accurate book state.\nHandle both optimistic and finalized trades correctly. Optimistic fills update book state immediately, while only finalized fills should be treated as confirmed trades.\n\nAdditional logic\n\nProcess informational taker order messages without updating state.\nConvert protocol integers to decimal values for display and analysis. Fetch the market information from the Indexer, containing data required for integer conversion.\nValidate orderbook state consistency in order to detect any errors, here related with crossed orderbook (a bid larger than a ask).","tokens":1895,"crawled_at":1791193828551}
+{"id":10295,"url":"https://stack.olas.network/open-autonomy/advanced_reference/use_custom_images","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Using custom images in a deployment - Olas Stack Developer Documentation","text":"Using custom images in a deployment\n\nThe Open Autonomy framework uses up to 6 different Docker images when building an AI agent deployment with the command autonomy deploy build. Some of these images are for testing purposes and they are only included if indicated explicitly.\n\nImages used in production and testing\n\nvalory/open-autonomy\n\nBase image that contains all the required Python packages and a virtual environment required to deploy an agent instance. The deployment builder will use valory/open-autonomy as the name and the current version of the framework as the version tag. You can change the name and the version tag of the image by exporting the environment variables AUTONOMY_IMAGE_NAME and AUTONOMY_IMAGE_VERSION, respectively.\n\nvalory/oar-<author>/<agent_package>:<package_hash>\n\nThis image extends the base image valory/open-autonomy. It contains the agent blueprint package for an AI agent and a deployment environment for the same agent blueprint. This image is built through the autonomy build-image command.\n\nvalory/open-autonomy-tendermint\n\nDefines a Tendermint node in the deployment setup. The deployment builder will use valory/open-autonomy-tendermint as the name and the current version of the framework as the version tag. You can change the name and the version tag of the image by exporting the environment variables TENDERMINT_IMAGE_NAME and TENDERMINT_IMAGE_VERSION, respectively.\n\nImages used in testing only\n\nvalory/open-autonomy-hardhat\n\nBase image that contains a pre-configured Hardhat node which can be used as a test blockchain for testing AI agents locally and running end-to-end tests for the agent blueprint packages.\n\nvalory/autonolas-registries\n\nThis image extends the base image valory/open-autonomy-hardhat.\nIt comes with the Autonolas Protocol registry contracts pre-deployed. The deployment builder will use valory/open-autonomy-hardhat as the name and latest as the version tag. You can change the name and the version tag of the image by exporting the environment variables HARDHAT_IMAGE_NAME and HARDHAT_IMAGE_VERSION, respectively, to valory/autonolas-registries:latest.\n\nImportant\n\nThis image is only included if explicitly indicated through the flag --use-hardhat when building the AI agent deployment (autonomy deploy build command).\n\nThis image should only be used when working with the dev mode.\n\nIf you require specific custom contracts to test your AI agent, read the guide to include custom contracts.\n\nvalory/open-acn-node\n\nDefines an ACN node in the deployment setup, which can be used for direct agent to agent communication. The deployment builder will use valory/open-acn-node as the name and latest as the version tag. You can change the name and the version tag of the image by exporting the environment variables ACN_IMAGE_NAME and ACN_IMAGE_VERSION, respectively.\n\nImportant\n\nThis image is only included if explicitly indicated through the flag --use-acn when building the AI agent deployment (autonomy deploy build command).\n\nThis image should only be used when working with the dev mode.","tokens":765,"crawled_at":1791193835163}
+{"id":10296,"url":"https://docs.ethers.org/v6/api/providers","domain":"docs.ethers.org","chapter":"developer_specs","title":"","text":"ethers\n6.17.0\n\nDOCUMENTATION\nGetting Started\nEthereum Basics\nApplication Programming Interface\nPollingBlockTagSubscriber\nApplication Binary Interface\nAddresses\nConstants\nContracts\nCryptographic Functions\nHashing Utilities\nProviders\nBlock\nBrowserDiscoverOptions\nBrowserProvider\nContractRunner\nEip1193Provider\nEip6963ProviderInfo\nEnsPlugin\nEventFilter\nFeeData\nFeeDataNetworkPlugin\nFetchUrlFeeDataNetworkPlugin\nFilter\nFilterByBlockHash\nGasCostPlugin\nIpcSocketProvider\nLog\nMinedBlock\nMinedTransactionResponse\nNetworkPlugin\nNonceManager\nPreparedTransactionRequest\nProvider\nSigner\nTransactionReceipt\nTransactionRequest\nTransactionResponse\nWebSocketLike\nWebSocketProvider\nNetworks\nSubclassing Provider\nSubclassing Signer\nENS Resolver\nFallback Provider\nFormatting\nJSON-RPC Provider\nCommunity Providers\nTransactions\nUtilities\nWallets\nWordlists\nCookbook\nMigrating from v5\nContributions and Hacking\nLicense and Copyright\n\nSingle Page\n\nDocumentation »API »Providers\nProviders\nA Provider provides a connection to the blockchain, which can be used to query its current state, simulate execution and send transactions to update the state.\nIt is one of the most fundamental components of interacting with a blockchain application, and there are many ways to connect, such as over HTTP, WebSockets or injected providers such as MetaMask.\n\nTYPES\n<src>BlockTag⇒ BigNumberish | string\nA BlockTag specifies a specific block.\nnumeric value - specifies the block height, where the genesis block is block 0; many operations accept a negative value which indicates the block number should be deducted from the most recent block. A numeric value may be a number, bigint, or a decimal of hex string.\nblockhash - specifies a specific block by its blockhash; this allows potentially orphaned blocks to be specifed, without ambiguity, but many backends do not support this for some operations.\n\n<src>BrowserProviderOptions⇒ { cacheTimeout?: number , polling?: boolean , pollingInterval?: number , providerInfo?: Eip6963ProviderInfo , staticNetwork?: null | boolean | Network }\n\n<src>DebugEventBrowserProvider⇒ { action: \"sendEip1193Payload\" , payload: { method: string , params: Array< any > } } | { action: \"receiveEip1193Result\" , result: any } | { action: \"receiveEip1193Error\" , error: Error }\nThe possible additional events dispatched when using the \"debug\" event on a BrowserProvider.\n\n<src>GasCostParameters⇒ { txAccessListAddress?: number , txAccessListStorageKey?: number , txBase?: number , txCreate?: number , txDataNonzero?: number , txDataZero?: number }\nThe gas cost parameters for a GasCostPlugin.\n\n<src>OrphanFilter⇒ { hash: string , number: number , orphan: \"drop-block\" } | { orphan: \"drop-transaction\" , other?: { blockHash: string , blockNumber: number , hash: string } , tx: { blockHash: string , blockNumber: number , hash: string } } | { orphan: \"reorder-transaction\" , other?: { blockHash: string , blockNumber: number , hash: string } , tx: { blockHash: string , blockNumber: number , hash: string } } | { log: { address: string , blockHash: string , blockNumber: number , data: string , index: number , topics: ReadonlyArray< string > , transactionHash: string } , orphan: \"drop-log\" }\nAn Orphan Filter allows detecting when an orphan block has resulted in dropping a block or transaction or has resulted in transactions changing order.\nNot currently fully supported.\n\n<src>ProviderEvent⇒ string | Array< string | Array< string > > | EventFilter | OrphanFilter\nA ProviderEvent provides the types of events that can be subscribed to on a Provider.\nEach provider may include additional possible events it supports, but the most commonly supported are:\n\"block\" - calls the listener with the current block number on each new block.\n\"error\" - calls the listener on each async error that occurs during the event loop, with the error.\n\"debug\" - calls the listener on debug events, which can be used to troubleshoot network errors, provider problems, etc.\ntransaction hash - calls the listener on each block after the transaction has been mined; generally .once is more appropriate for this event.\nArray - calls the listener on each log that matches the filter.\nEventFilter - calls the listener with each matching log\n\n<src>TopicFilter⇒ Array< null | string | Array< string > >\nA TopicFilter provides a struture to define bloom-filter queries.\nEach field that is null matches any value, a field that is a string must match exactly that value and array is effectively an OR-ed set, where any one of those values must match.\n\n<src>WebSocketCreator⇒ () => WebSocketLike\nA function which can be used to re-create a WebSocket connection on disconnect.\n\nFUNCTIONS\n<src>copyRequest(req: TransactionRequest)⇒ PreparedTransactionRequest\nReturns a copy of req with all properties coerced to their strict types.\n\n<src>getDefaultProvider(network?: string | Networkish | WebSocketLike, options?: any)⇒ AbstractProvider\nReturns a default provider for network.\nIf network is a WebSocketLike or string that begins with \"ws:\" or \"wss:\", a WebSocketProvider is returned backed by that WebSocket or URL.\nIf network is a string that begins with \"HTTP:\" or \"HTTPS:\", a JsonRpcProvider is returned connected to that URL.\nOtherwise, a default provider is created backed by well-known public Web3 backends (such as INFURA) using community-provided API keys.\nThe options allows specifying custom API keys per backend (setting an API key to \"-\" will omit that provider) and options.exclusive can be set to either a backend name or and array of backend names, which will whitelist only those backends.\nCurrent backend strings supported are:\n\n\"alchemy\"\n\"ankr\"\n\"cloudflare\"\n\"chainstack\"\n\"etherscan\"\n\"infura\"\n\"publicPolygon\"\n\"quicknode\"\n\n// Connect to a local Geth node\nprovider = getDefaultProvider(\"http://localhost:8545/\");\n\n// Connect to Ethereum mainnet with any current and future\n// third-party services available\nprovider = getDefaultProvider(\"mainnet\");\n\n// Connect to Polygon, but only allow Etherscan and\n// INFURA and use \"MY_API_KEY\" in calls to Etherscan.\nprovider = getDefaultProvider(\"matic\", {\netherscan: \"MY_API_KEY\",\nexclusive: [ \"etherscan\", \"infura\" ]\n});\n\nclass Block\ninherits from BlockParams\nA Block represents the data associated with a full block on Ethereum.\n\nPROPERTIES\n<src>block.baseFeePerGas⇒ null | bigintread-only\nThe base fee per gas that all transactions in this block were charged.\nThis adjusts after each block, depending on how congested the network is.\n\n<src>block.blobGasUsed⇒ null | bigintread-only\nThe total amount of blob gas consumed by the transactions within the block. See EIP-4844.\n\n<src>block.date⇒ null | Dateread-only\nThe Date this block was included at.\n\n<src>block.difficulty⇒ bigintread-only\nThe difficulty target.\nOn legacy networks, this is the proof-of-work target required for a block to meet the protocol rules to be included.\nOn modern networks, this is a random number arrived at using randao. @TODO: Find links?\n\n<src>block.excessBlobGas⇒ null | bigintread-only\nThe running total of blob gas consumed in excess of the target, prior to the block. See EIP-4844.\n\n<src>block.extraData⇒ stringread-only\nAny extra data the validator wished to include.\n\n<src>block.gasLimit⇒ bigintread-only\nThe total gas limit for this block.\n\n<src>block.gasUsed⇒ bigintread-only\nThe total gas used in this block.\n\n<src>block.hash⇒ null | stringread-only\nThe block hash.\nThis hash includes all properties, so can be safely used to identify an exact set of block properties.\n\n<src>block.length⇒ numberread-only\nThe number of transactions in this block.\n\n<src>block.miner⇒ stringread-only\nThe miner coinbase address, wihch receives any subsidies for including this block.\n\n<src>block.nonce⇒ stringread-only\nThe nonce.\nOn legacy networks, this is the random number inserted which permitted the difficulty target to be reached.\n\n<src>block.number⇒ numberread-only\nThe block number, sometimes called the block height. This is a sequential number that is one higher than the parent block.\n\n<src>block.parentBeaconBlockRoot⇒ null | string\nThe hash tree root of the parent beacon block for the given execution block. See EIP-4788.\n\n<src>block.parentHash⇒ stringread-only\nThe block hash of the parent block.\n\n<src>block.prefetchedTransactions⇒ Array< TransactionResponse >read-only\nReturns the complete transactions, in the order they were executed within the block.\nThis is only available for blocks which prefetched transactions, by passing true to prefetchTxs into provider.getBlock.\n\n<src>block.prevRandao⇒ null | stringread-only\nThe latest RANDAO mix of the post beacon state of the previous block.\n\n<src>block.provider⇒ Providerread-only\nThe provider connected to the block used to fetch additional details if necessary.\n\n<src>block.receiptsRoot⇒ null | stringread-only\nThe hash of the transaction receipts trie.\n\n<src>block.stateRoot⇒ null | stringread-only\nThe root hash for the global state after applying changes in this block.\n\n<src>block.timestamp⇒ numberread-only\nThe timestamp for this block, which is the number of seconds since epoch that this block was included.\n\n<src>block.transactions⇒ ReadonlyArray< string >read-only\nReturns the list of transaction hashes, in the order they were executed within the block.\n\n<src>block.transactionsRoot⇒ null | stringread-only\nThe hash of the transactions.\n\nCREATING INSTANCES\n<src>new Block(block: BlockParams, provider: Provider)\nCreate a new Block object.\nThis should generally not be necessary as the unless implementing a low-level library.\n\nMETHODS\n<src>block.getPrefetchedTransaction(indexOrHash: number | string)⇒ TransactionResponse\nIf a Block was fetched with a request to include the transactions this will allow synchronous access to those transactions.\nIf the transactions were not prefetched, this will throw.\n\n<src>block.getTransaction(indexOrHash: number | string)⇒ Promise< TransactionResponse >\nGet the transaction at indexe within this block.\n\n<src>block.isLondon()⇒ boolean\nReturns true if this block is an EIP-2930 block.\n\n<src>block.isMined()⇒ boolean\nReturns true if this block been mined. This provides a type guard for all properties on a MinedBlock.\n\n<src>block.toJSON()⇒ any\nReturns a JSON-friendly value.\n\ninterface BrowserDiscoverOptions\nSpecifies how EIP-6963 discovery should proceed.\nSee: BrowserProvider-discover\n\nPROPERTIES\n<src>browserDiscoverOptions.anyProvider⇒ boolean\nReturn the first detected provider. Otherwise wait for timeout and allowing filtering before selecting the desired provider.\n\n<src>browserDiscoverOptions.filter⇒ (found: Array< Eip6963ProviderInfo >) => null | BrowserProvider | Eip6963ProviderInfo\nExplicitly choose which provider to used once scanning is complete.\n\n<src>browserDiscoverOptions.provider⇒ Eip1193Provider\nOverride provider detection with this provider.\n\n<src>browserDiscoverOptions.timeout⇒ number\nDuration to wait to detect providers. (default: 300ms)\n\n<src>browserDiscoverOptions.window⇒ any\nUse the provided window context. Useful in non-standard environments or to hijack where a provider comes from.\n\nclass BrowserProvider\nA BrowserProvider is intended to wrap an injected provider which adheres to the EIP-1193 standard, which most (if not all) currently do.\n\nPROPERTIES\n<src>browserProvider.providerInfo⇒ null | Eip6963ProviderInforead-only\n\nCREATING INSTANCES\n<src>new BrowserProvider(ethereum: Eip1193Provider, network?: Networkish, options?: BrowserProviderOptions)\nConnect to the ethereum provider, optionally forcing the network.\n\nMETHODS\n<src>browserProvider._send(payload: JsonRpcPayload | Array< JsonRpcPayload >)⇒ Promise< Array< JsonRpcResult | JsonRpcError > >\n\n<src>browserProvider.getRpcError(payload: JsonRpcPayload, error: JsonRpcError)⇒ Error\n\n<src>browserProvider.getSigner(address?: number | string)⇒ Promise< JsonRpcSigner >\n\n<src>browserProvider.hasSigner(address: number | string)⇒ Promise< boolean >\nResolves to true if the provider manages the address.\n\n<src>browserProvider.send(method: string, params: Array< any > | Record< string, any >)⇒ Promise< any >\n\nSTATIC METHODS\n<src>BrowserProvider.discover(options?: BrowserDiscoverOptions)⇒ Promise< null | BrowserProvider >\nDiscover and connect to a Provider in the Browser using the EIP-6963 discovery mechanism. If no providers are present, null is resolved.\n\ninterface ContractRunner\nA ContractRunner is a generic interface which defines an object capable of interacting with a Contract on the network.\nThe more operations supported, the more utility it is capable of.\nThe most common ContractRunners are Providers which enable read-only access and Signers which enable write-access.\n\nPROPERTIES\n<src>contractRunner.call⇒ (tx: TransactionRequest) => Promise< string >\nRequired for pure, view or static calls to contracts.\n\n<src>contractRunner.estimateGas⇒ (tx: TransactionRequest) => Promise< bigint >\nRequired to estimate gas.\n\n<src>contractRunner.provider⇒ null | Provider\nThe provider used for necessary state querying operations.\nThis can also point to the ContractRunner itself, in the case of an AbstractProvider.\n\n<src>contractRunner.resolveName⇒ (name: string) => Promise< null | string >\nRequired to support ENS names\n\n<src>contractRunner.sendTransaction⇒ (tx: TransactionRequest) => Promise< TransactionResponse >\nRequired for state mutating calls\n\ninterface Eip1193Provider\nThe interface to an EIP-1193 provider, which is a standard used by most injected providers, which the BrowserProvider accepts and exposes the API of.\n\nMETHODS\n<src>eip1193Provider.request(request: { method: string , params?: Array< any > | Record< string, any > })⇒ Promise< any >\nSee EIP-1193 for details on this method.\n\ninterface Eip6963ProviderInfo\nProvider info provided by the EIP-6963 discovery mechanism.\n\nPROPERTIES\n<src>eip6963ProviderInfo.icon⇒ string\n\n<src>eip6963ProviderInfo.name⇒ string\n\n<src>eip6963ProviderInfo.rdns⇒ string\n\n<src>eip6963ProviderInfo.uuid⇒ string\n\nclass EnsPlugin\ninherits from NetworkPlugin\nAn EnsPlugin allows a Network to specify the ENS Registry Contract address and the target network to use when using that contract.\nVarious testnets have their own instance of the contract to use, but in general, the mainnet instance supports multi-chain addresses and should be used.\n\nPROPERTIES\n<src>ensPlugin.address⇒ stringread-only\nThe ENS Registrty Contract address.\n\n<src>ensPlugin.targetNetwork⇒ numberread-only\nThe chain ID that the ENS contract lives on.\n\n<src>ensPlugin.universalResolver⇒ stringread-only\nThe Universal Resolver Contract Address.\n\nCREATING INSTANCES\n<src>new EnsPlugin(address?: null | string, targetNetwork?: null | number, universalResolver?: string)\nCreates a new EnsPlugin connected to address on the targetNetwork. The default ENS address and mainnet is used if unspecified.\n\ninterface EventFilter\nAn EventFilter allows efficiently filtering logs (also known as events) using bloom filters included within blocks.\n\nPROPERTIES\n<src>eventFilter.address⇒ AddressLike | Array< AddressLike >\n\n<src>eventFilter.topics⇒ TopicFilter\n\nclass FeeData\nA FeeData wraps all the fee-related values associated with the network.\n\nPROPERTIES\n<src>feeData.gasPrice⇒ null | bigintread-only\nThe gas price for legacy networks.\n\n<src>feeData.maxFeePerGas⇒ null | bigintread-only\nThe maximum fee to pay per gas.\nThe base fee per gas is defined by the network and based on congestion, increasing the cost during times of heavy load and lowering when less busy.\nThe actual fee per gas will be the base fee for the block and the priority fee, up to the max fee per gas.\nThis will be null on legacy networks (i.e. pre-EIP-1559)\n\n<src>feeData.maxPriorityFeePerGas⇒ null | bigintread-only\nThe additional amout to pay per gas to encourage a validator to include the transaction.\nThe purpose of this is to compensate the validator for the adjusted risk for including a given transaction.\nThis will be null on legacy networks (i.e. pre-EIP-1559)\n\nCREATING INSTANCES\n<src>new FeeData(gasPrice?: null | bigint, maxFeePerGas?: null | bigint, maxPriorityFeePerGas?: null | bigint)\nCreates a new FeeData for gasPrice, maxFeePerGas and maxPriorityFeePerGas.\n\nMETHODS\n<src>feeData.toJSON()⇒ any\nReturns a JSON-friendly value.\n\nclass FeeDataNetworkPlugin\ninherits from NetworkPlugin\nA FeeDataNetworkPlugin allows a network to provide and alternate means to specify its fee data.\nFor example, a network which does not support EIP-1559 may choose to use a Gas Station site to approximate the gas price.\n\nPROPERTIES\n<src>feeDataNetworkPlugin.feeDataFunc⇒ (provider: Provider) => Promise< FeeData >read-only\nThe fee data function provided to the constructor.\n\nCREATING INSTANCES\n<src>new FeeDataNetworkPlugin(feeDataFunc: (provider: Provider) => Promise< FeeData >)\nCreates a new FeeDataNetworkPlugin.\n\nMETHODS\n<src>feeDataNetworkPlugin.getFeeData(provider: Provider)⇒ Promise< FeeData >\nResolves to the fee data.\n\nclass FetchUrlFeeDataNetworkPlugin\ninherits from NetworkPlugin\n\nPROPERTIES\n<src>fetchUrlFeeDataNetworkPlugin.processFunc⇒ (f: () => Promise< FeeData >, p: Provider, r: FetchRequest) => Promise< { gasPrice?: null | bigint , maxFeePerGas?: null | bigint , maxPriorityFeePerGas?: null | bigint } >read-only\nThe callback to use when computing the FeeData.\n\n<src>fetchUrlFeeDataNetworkPlugin.url⇒ stringread-only\nThe URL to initialize the FetchRequest with in processFunc.\n\nCREATING INSTANCES\n<src>new FetchUrlFeeDataNetworkPlugin(url: string, processFunc: (f: () => Promise< FeeData >, p: Provider, r: FetchRequest) => Promise< { gasPrice?: null | bigint , maxFeePerGas?: null | bigint , maxPriorityFeePerGas?: null | bigint } >)\nCreates a new FetchUrlFeeDataNetworkPlugin which will be used when computing the fee data for the network.\n\ninterface Filter\ninherits from EventFilter\nA Filter allows searching a specific range of blocks for mathcing logs.\n\nPROPERTIES\n<src>filter.fromBlock⇒ BlockTag\nThe start block for the filter (inclusive).\n\n<src>filter.toBlock⇒ BlockTag\nThe end block for the filter (inclusive).\n\ninterface FilterByBlockHash\ninherits from EventFilter\nA FilterByBlockHash allows searching a specific block for mathcing logs.\n\nPROPERTIES\n<src>filterByBlockHash.blockHash⇒ string\nThe blockhash of the specific block for the filter.\n\nclass GasCostPlugin\ninherits from NetworkPlugin\nA GasCostPlugin allows a network to provide alternative values when computing the intrinsic gas required for a transaction.\n\nPROPERTIES\n<src>gasCostPlugin.effectiveBlock⇒ numberread-only\nThe block number to treat these values as valid from.\nThis allows a hardfork to have updated values included as well as mulutiple hardforks to be supported.\n\n<src>gasCostPlugin.txAccessListAddress⇒ numberread-only\nThe fee per address in the EIP-2930 access list.\n\n<src>gasCostPlugin.txAccessListStorageKey⇒ numberread-only\nThe fee per storage key in the EIP-2930 access list.\n\n<src>gasCostPlugin.txBase⇒ numberread-only\nThe transactions base fee.\n\n<src>gasCostPlugin.txCreate⇒ numberread-only\nThe fee for creating a new account.\n\n<src>gasCostPlugin.txDataNonzero⇒ numberread-only\nThe fee per non-zero-byte in the data.\n\n<src>gasCostPlugin.txDataZero⇒ numberread-only\nThe fee per zero-byte in the data.\n\nCREATING INSTANCES\n<src>new GasCostPlugin(effectiveBlock?: number, costs?: GasCostParameters)\nCreates a new GasCostPlugin from effectiveBlock until the latest block or another GasCostPlugin supercedes that block number, with the associated costs.\n\nclass IpcSocketProvider\ninherits from SocketProvider, JsonRpcApiProvider\nAn IpcSocketProvider connects over an IPC socket on the host which provides fast access to the node, but requires the node and the script run on the same machine.\n\nPROPERTIES\n<src>ipcSocketProvider.socket⇒ Socketread-only\nThe connected socket.\n\nCREATING INSTANCES\n<src>new IpcSocketProvider(path: string, network?: Networkish, options?: JsonRpcApiProviderOptions)\n\nclass Log\ninherits from LogParams\nA Log in Ethereum represents an event that has been included in a transaction using the LOG* opcodes, which are most commonly used by Solidity's emit for announcing events.\n\nPROPERTIES\n<src>log.address⇒ stringread-only\nThe address of the contract that emitted this log.\n\n<src>log.blockHash⇒ stringread-only\nThe block hash of the block this log occurred in. Use the log.getBlock to get the Block.\n\n<src>log.blockNumber⇒ numberread-only\nThe block number of the block this log occurred in. It is preferred to use the block.hash when fetching the related Block, since in the case of an orphaned block, the block at that height may have changed.\n\n<src>log.data⇒ stringread-only\nThe data included in this log when it was emitted.\n\n<src>log.index⇒ numberread-only\nThe index within the block this log occurred at. This is generally not useful to developers, but can be used with the various roots to proof inclusion within a block.\n\n<src>log.provider⇒ Providerread-only\nThe provider connected to the log used to fetch additional details if necessary.\n\n<src>log.removed⇒ booleanread-only\nIf the Log represents a block that was removed due to an orphaned block, this will be true.\nThis can only happen within an orphan event listener.\n\n<src>log.topics⇒ ReadonlyArray< string >read-only\nThe indexed topics included in this log when it was emitted.\nAll topics are included in the bloom filters, so they can be efficiently filtered using the provider.getLogs method.\n\n<src>log.transactionHash⇒ stringread-only\nThe transaction hash of the transaction this log occurred in. Use the log.getTransaction to get the TransactionResponse.\n\n<src>log.transactionIndex⇒ numberread-only\nThe index within the transaction of this log.\n\nMETHODS\n<src>log.getBlock()⇒ Promise< Block >\nReturns the block that this log occurred in.\n\n<src>log.getTransaction()⇒ Promise< TransactionResponse >\nReturns the transaction that this log occurred in.\n\n<src>log.getTransactionReceipt()⇒ Promise< TransactionReceipt >\nReturns the transaction receipt fot the transaction that this log occurred in.\n\n<src>log.toJSON()⇒ any\nReturns a JSON-compatible object.\n\ninterface MinedBlock\ninherits from Block, BlockParams\nAn Interface to indicate a Block has been included in the blockchain. This asserts a Type Guard that necessary properties are non-null.\nBefore a block is included, it is a pending block.\n\nPROPERTIES\n<src>minedBlock.date⇒ Dateread-only\nThe block date, created from the timestamp.\n\n<src>minedBlock.hash⇒ stringread-only\nThe block hash.\n\n<src>minedBlock.miner⇒ stringread-only\nThe miner of the block, also known as the author or block producer.\n\n<src>minedBlock.number⇒ numberread-only\nThe block number also known as the block height.\n\n<src>minedBlock.timestamp⇒ numberread-only\nThe block timestamp, in seconds from epoch.\n\ninterface MinedTransactionResponse\ninherits from TransactionResponse, TransactionResponseParams\nA MinedTransactionResponse is an interface representing a transaction which has been mined and allows for a type guard for its property values being defined.\n\nPROPERTIES\n<src>minedTransactionResponse.blockHash⇒ string\nThe block hash this transaction occurred in.\n\n<src>minedTransactionResponse.blockNumber⇒ number\nThe block number this transaction occurred in.\n\n<src>minedTransactionResponse.date⇒ Date\nThe date this transaction occurred on.\n\nclass NetworkPlugin\nA NetworkPlugin provides additional functionality on a Network.\n\nPROPERTIES\n<src>networkPlugin.name⇒ stringread-only\nThe name of the plugin.\nIt is recommended to use reverse-domain-notation, which permits unique names with a known authority as well as hierarchal entries.\n\nCREATING INSTANCES\n<src>new NetworkPlugin(name: string)\nCreates a new NetworkPlugin.\n\nMETHODS\n<src>networkPlugin.clone()⇒ NetworkPlugin\nCreates a copy of this plugin.\n\n<src>networkPlugin.inspect()⇒ string\n\n<src>networkPlugin.toString()⇒ string\n\nclass NonceManager\ninherits from AbstractSigner, Signer\nA NonceManager wraps another Signer and automatically manages the nonce, ensuring serialized and sequential nonces are used during transaction.\n\nPROPERTIES\n<src>nonceManager.signer⇒ Signer\nThe Signer being managed.\n\nCREATING INSTANCES\n<src>new NonceManager(signer: Signer)\nCreates a new NonceManager to manage signer.\n\nMETHODS\n<src>nonceManager.increment()⇒ void\nManually increment the nonce. This may be useful when managng offline transactions.\n\n<src>nonceManager.reset()⇒ void\nResets the nonce, causing the NonceManager to reload the current nonce from the blockchain on the next transaction.\n\ninterface PreparedTransactionRequest\nA PreparedTransactionRequest is identical to a TransactionRequest except all the property types are strictly enforced.\n\nPROPERTIES\n<src>preparedTransactionRequest.accessList⇒ AccessList\nThe EIP-2930 access list. Storage slots included in the access list are warmed by pre-loading them, so their initial cost to fetch is guaranteed, but then each additional access is cheaper.\n\n<src>preparedTransactionRequest.authorizationList⇒ Array< Authorization >\nThe EIP-7702 authorizations (if any).\n\n<src>preparedTransactionRequest.blockTag⇒ BlockTag\nWhen using call or estimateGas, this allows a specific block to be queried. Many backends do not support this and when unsupported errors are silently squelched and \"latest\" is used.\n\n<src>preparedTransactionRequest.chainId⇒ bigint\nThe chain ID for the network this transaction is valid on.\n\n<src>preparedTransactionRequest.customData⇒ any\nA custom object, which can be passed along for network-specific values.\n\n<src>preparedTransactionRequest.data⇒ string\nThe transaction data.\n\n<src>preparedTransactionRequest.enableCcipRead⇒ boolean\nWhen using call, this enables CCIP-read, which permits the provider to be redirected to web-based content during execution, which is then further validated by the contract.\nThere are potential security implications allowing CCIP-read, as it could be used to expose the IP address or user activity during the fetch to unexpected parties.\n\n<src>preparedTransactionRequest.from⇒ AddressLike\nThe sender of the transaction.\n\n<src>preparedTransactionRequest.gasLimit⇒ bigint\nThe maximum amount of gas to allow this transaction to consume.\n\n<src>preparedTransactionRequest.gasPrice⇒ bigint\nThe gas price to use for legacy transactions or transactions on legacy networks.\nMost of the time the max*FeePerGas is preferred.\n\n<src>preparedTransactionRequest.maxFeePerGas⇒ bigint\nThe EIP-1559 maximum total fee to pay per gas. The actual value used is protocol enforced to be the block's base fee.\n\n<src>preparedTransactionRequest.maxPriorityFeePerGas⇒ bigint\nThe EIP-1559 maximum priority fee to pay per gas.\n\n<src>preparedTransactionRequest.nonce⇒ number\nThe nonce of the transaction, used to prevent replay attacks.\n\n<src>preparedTransactionRequest.to⇒ AddressLike\nThe target of the transaction.\n\n<src>preparedTransactionRequest.type⇒ number\nThe transaction type.\n\n<src>preparedTransactionRequest.value⇒ bigint\nThe transaction value (in wei).\n\ninterface Provider\ninherits from ContractRunner, EventEmitterable, NameResolver\nA Provider is the primary method to interact with the read-only content on Ethereum.\nIt allows access to details about accounts, blocks and transactions and the ability to query event logs and simulate contract execution.\nAccount data includes the balance, transaction count, code and state trie storage.\nSimulating execution can be used to call, estimate gas and get transaction results.\nThe broadcastTransaction is the only method which allows updating the blockchain, but it is usually accessed by a Signer, since a private key must be used to sign the transaction before it can be broadcast.\n\nPROPERTIES\n<src>provider.provider⇒ this\nThe provider iteself.\nThis is part of the necessary API for executing a contract, as it provides a common property on any ContractRunner that can be used to access the read-only portion of the runner.\n\nMETHODS\n<src>provider.broadcastTransaction(signedTx: string)⇒ Promise< TransactionResponse >\nBroadcasts the signedTx to the network, adding it to the memory pool of any node for which the transaction meets the rebroadcast requirements.\n\n<src>provider.call(tx: TransactionRequest)⇒ Promise< string >\nSimulate the execution of tx. If the call reverts, it will throw a CallExceptionError which includes the revert data.\n\n<src>provider.destroy()⇒ void\nShutdown any resources this provider is using. No additional calls should be made to this provider after calling this.\n\n<src>provider.estimateGas(tx: TransactionRequest)⇒ Promise< bigint >\nEstimates the amount of gas required to execute tx.\n\n<src>provider.getBalance(address: AddressLike, blockTag?: BlockTag)⇒ Promise< bigint >\nGet the account balance (in wei) of address. If blockTag is specified and the node supports archive access for that blockTag, the balance is as of that BlockTag.\n\n<src>provider.getBlock(blockHashOrBlockTag: BlockTag | string, prefetchTxs?: boolean)⇒ Promise< null | Block >\nResolves to the block for blockHashOrBlockTag.\nIf prefetchTxs, and the backend supports including transactions with block requests, all transactions will be included and the Block object will not need to make remote calls for getting transactions.\n\n<src>provider.getBlockNumber()⇒ Promise< number >\nGet the current block number.\n\n<src>provider.getCode(address: AddressLike, blockTag?: BlockTag)⇒ Promise< string >\nGet the bytecode for address.\n\n<src>provider.getFeeData()⇒ Promise< FeeData >\nGet the best guess at the recommended FeeData.\n\n<src>provider.getLogs(filter: Filter | FilterByBlockHash)⇒ Promise< Array< Log > >\nResolves to the list of Logs that match filter\n\n<src>provider.getNetwork()⇒ Promise< Network >\nGet the connected Network.\n\n<src>provider.getStorage(address: AddressLike, position: BigNumberish, blockTag?: BlockTag)⇒ Promise< string >\nGet the storage slot value for address at slot position.\n\n<src>provider.getTransaction(hash: string)⇒ Promise< null | TransactionResponse >\nResolves to the transaction for hash.\nIf the transaction is unknown or on pruning nodes which discard old transactions this resolves to null.\n\n<src>provider.getTransactionCount(address: AddressLike, blockTag?: BlockTag)⇒ Promise< number >\nGet the number of transactions ever sent for address, which is used as the nonce when sending a transaction. If blockTag is specified and the node supports archive access for that blockTag, the transaction count is as of that BlockTag.\n\n<src>provider.getTransactionReceipt(hash: string)⇒ Promise< null | TransactionReceipt >\nResolves to the transaction receipt for hash, if mined.\nIf the transaction has not been mined, is unknown or on pruning nodes which discard old transactions this resolves to null.\n\n<src>provider.getTransactionResult(hash: string)⇒ Promise< null | string >\nResolves to the result returned by the executions of hash.\nThis is only supported on nodes with archive access and with the necessary debug APIs enabled.\n\n<src>provider.lookupAddress(address: string, coinType?: BigNumberish)⇒ Promise< null | string >\nResolves to the ENS name associated for the address or null if the primary name is not configured.\nUsers must perform additional steps to configure a primary name, which is not currently common.\n\n<src>provider.resolveName(ensName: string, coinType?: BigNumberish)⇒ Promise< null | string >\nResolves to the address configured for the ensName or null if unconfigured.\n\n<src>provider.waitForBlock(blockTag?: BlockTag)⇒ Promise< Block >\nResolves to the block at blockTag once it has been mined.\nThis can be useful for waiting some number of blocks by using the currentBlockNumber + N.\n\n<src>provider.waitForTransaction(hash: string, confirms?: number, timeout?: number)⇒ Promise< null | TransactionReceipt >\nWaits until the transaction hash is mined and has confirms confirmations.\n\ninterface Signer\ninherits from Addressable, ContractRunner, NameResolver\nA Signer represents an account on the Ethereum Blockchain, and is most often backed by a private key represented by a mnemonic or residing on a Hardware Wallet.\nThe API remains abstract though, so that it can deal with more advanced exotic Signing entities, such as Smart Contract Wallets or Virtual Wallets (where the private key may not be known).\n\nPROPERTIES\n<src>signer.provider⇒ null | Provider\nThe Provider attached to this Signer (if any).\n\nMETHODS\n<src>signer.authorize(authorization: AuthorizationRequest)⇒ Promise< Authorization >\nSigns an authorization to be used in EIP-7702 transactions.\n\n<src>signer.call(tx: TransactionRequest)⇒ Promise< string >\nEvaluates the tx by running it against the current Blockchain state. This cannot change state and has no cost in ether, as it is effectively simulating execution.\nThis can be used to have the Blockchain perform computations based on its state (e.g. running a Contract's getters) or to simulate the effect of a transaction before actually performing an operation.\n\n<src>signer.connect(provider: null | Provider)⇒ Signer\nReturns a new instance of this Signer connected to provider or detached from any Provider if null.\n\n<src>signer.estimateGas(tx: TransactionRequest)⇒ Promise< bigint >\nEstimates the required gas required to execute tx on the Blockchain. This will be the expected amount a transaction will require as its gasLimit to successfully run all the necessary computations and store the needed state that the transaction intends.\nKeep in mind that this is best efforts, since the state of the Blockchain is in flux, which could affect transaction gas requirements.\n\n<src>signer.getAddress()⇒ Promise< string >\nGet the address of the Signer.\n\n<src>signer.getNonce(blockTag?: BlockTag)⇒ Promise< number >\nGets the next nonce required for this Signer to send a transaction.\n\n<src>signer.populateAuthorization(auth: AuthorizationRequest)⇒ Promise< AuthorizationRequest >\nPrepares an AuthorizationRequest for authorization by populating any missing properties:\n\nresolves address (if an Addressable or ENS name)\npopulates nonce via signer.getNonce(\"pending\")\npopulates chainId via signer.provider.getNetwork()\n\n<src>signer.populateCall(tx: TransactionRequest)⇒ Promise< TransactionLike < string > >\nPrepares a {@link TransactionRequest} for calling:\n\nresolves to and from addresses\nif from is specified , check that it matches this Signer\n\n<src>signer.populateTransaction(tx: TransactionRequest)⇒ Promise< TransactionLike < string > >\nPrepares a {@link TransactionRequest} for sending to the network by populating any missing properties:\n\nresolves to and from addresses\nif from is specified , check that it matches this Signer\npopulates nonce via signer.getNonce(\"pending\")\npopulates gasLimit via signer.estimateGas(tx)\npopulates chainId via signer.provider.getNetwork()\npopulates type and relevant fee data for that type (gasPrice for legacy transactions, maxFeePerGas for EIP-1559, etc)\n\n<src>signer.resolveName(name: string)⇒ Promise< null | string >\nResolves an ENS Name to an address.\n\n<src>signer.sendTransaction(tx: TransactionRequest)⇒ Promise< TransactionResponse >\nSends tx to the Network. The signer.populateTransaction(tx) is called first to ensure all necessary properties for the transaction to be valid have been popualted first.\n\n<src>signer.signMessage(message: string | Uint8Array)⇒ Promise< string >\nSigns an EIP-191 prefixed personal message.\nIf the message is a string, it is signed as UTF-8 encoded bytes. It is not interpretted as a BytesLike; so the string \"0x1234\" is signed as six characters, not two bytes.\nTo sign that example as two bytes, the Uint8Array should be used (i.e. new Uint8Array([ 0x12, 0x34 ])).\n\n<src>signer.signTransaction(tx: TransactionRequest)⇒ Promise< string >\nSigns tx, returning the fully signed transaction. This does not populate any additional properties within the transaction.\n\n<src>signer.signTypedData(domain: TypedDataDomain, types: Record< string, Array< TypedDataField > >, value: Record< string, any >)⇒ Promise< string >\nSigns the EIP-712 typed data.\n\nclass TransactionReceipt\ninherits from TransactionReceiptParams\nA TransactionReceipt includes additional information about a transaction that is only available after it has been mined.\n\nPROPERTIES\n<src>transactionReceipt.blobGasPrice⇒ null | bigintread-only\nThe price paid per BLOB in gas. See EIP-4844.\n\n<src>transactionReceipt.blobGasUsed⇒ null | bigintread-only\nThe gas used for BLObs. See EIP-4844.\n\n<src>transactionReceipt.blockHash⇒ stringread-only\nThe block hash of the Block this transaction was included in.\n\n<src>transactionReceipt.blockNumber⇒ numberread-only\nThe block number of the Block this transaction was included in.\n\n<src>transactionReceipt.contractAddress⇒ null | stringread-only\nThe address of the contract if the transaction was directly responsible for deploying one.\nThis is non-null only if the to is empty and the data was successfully executed as initcode.\n\n<src>transactionReceipt.cumulativeGasUsed⇒ bigintread-only\nThe amount of gas used by all transactions within the block for this and all transactions with a lower index.\nThis is generally not useful for developers but can be used to validate certain aspects of execution.\n\n<src>transactionReceipt.fee⇒ bigintread-only\nThe total fee for this transaction, in wei.\n\n<src>transactionReceipt.from⇒ stringread-only\nThe sender of the transaction.\n\n<src>transactionReceipt.gasPrice⇒ bigintread-only\nThe actual gas price used during execution.\nDue to the complexity of EIP-1559 this value can only be caluclated after the transaction has been mined, snce the base fee is protocol-enforced.\n\n<src>transactionReceipt.gasUsed⇒ bigintread-only\nThe actual amount of gas used by this transaction.\nWhen creating a transaction, the amount of gas that will be used can only be approximated, but the sender must pay the gas fee for the entire gas limit. After the transaction, the difference is refunded.\n\n<src>transactionReceipt.hash⇒ stringread-only\nThe transaction hash.\n\n<src>transactionReceipt.index⇒ numberread-only\nThe index of this transaction within the block transactions.\n\n<src>transactionReceipt.logs⇒ ReadonlyArray< Log >read-only\nThe logs for this transaction.\n\n<src>transactionReceipt.logsBloom⇒ stringread-only\nThe bloom filter bytes that represent all logs that occurred within this transaction. This is generally not useful for most developers, but can be used to validate the included logs.\n\n<src>transactionReceipt.provider⇒ Providerread-only\nThe provider connected to the log used to fetch additional details if necessary.\n\n<src>transactionReceipt.root⇒ null | stringread-only\nThe root hash of this transaction.\nThis is no present and was only included in pre-byzantium blocks, but could be used to validate certain parts of the receipt.\n\n<src>transactionReceipt.status⇒ null | numberread-only\nThe status of this transaction, indicating success (i.e. 1) or a revert (i.e. 0).\nThis is available in post-byzantium blocks, but some backends may backfill this value.\n\n<src>transactionReceipt.to⇒ null | stringread-only\nThe address the transaction was sent to.\n\n<src>transactionReceipt.type⇒ numberread-only\nThe EIP-2718 transaction type.\n\nMETHODS\n<src>transactionReceipt.confirmations()⇒ Promise< number >\nResolves to the number of confirmations this transaction has.\n\n<src>transactionReceipt.getBlock()⇒ Promise< Block >\nResolves to the block this transaction occurred in.\n\n<src>transactionReceipt.getResult()⇒ Promise< string >\nResolves to the return value of the execution of this transaction.\nSupport for this feature is limited, as it requires an archive node with the debug_ or trace_ API enabled.\n\n<src>transactionReceipt.getTransaction()⇒ Promise< TransactionResponse >\nResolves to the transaction this transaction occurred in.\n\n<src>transactionReceipt.toJSON()⇒ any\nReturns a JSON-compatible representation.\n\ninterface TransactionRequest\nA TransactionRequest is a transactions with potentially various properties not defined, or with less strict types for its values.\nThis is used to pass to various operations, which will internally coerce any types and populate any necessary values.\n\nPROPERTIES\n<src>transactionRequest.accessList⇒ null | AccessListish\nThe EIP-2930 access list. Storage slots included in the access list are warmed by pre-loading them, so their initial cost to fetch is guaranteed, but then each additional access is cheaper.\n\n<src>transactionRequest.authorizationList⇒ null | Array< AuthorizationLike >\nThe EIP-7702 authorizations (if any).\n\n<src>transactionRequest.blobs⇒ null | Array< BlobLike >\nAny blobs to include in the transaction (see EIP-4844).\n\n<src>transactionRequest.blobVersionedHashes⇒ null | Array< string >\nThe blob versioned hashes (see EIP-4844).\n\n<src>transactionRequest.blobWrapperVersion⇒ null | number\nThe EIP-7594 BLOb Wrapper Version used for PeerDAS.\nFor networks that use EIP-7594, this property is required to serialize the sidecar correctly.\n\n<src>transactionRequest.blockTag⇒ BlockTag\nWhen using call or estimateGas, this allows a specific block to be queried. Many backends do not support this and when unsupported errors are silently squelched and \"latest\" is used.\n\n<src>transactionRequest.chainId⇒ null | BigNumberish\nThe chain ID for the network this transaction is valid on.\n\n<src>transactionRequest.customData⇒ any\nA custom object, which can be passed along for network-specific values.\n\n<src>transactionRequest.data⇒ null | string\nThe transaction data.\n\n<src>transactionRequest.enableCcipRead⇒ boolean\nWhen using call, this enables CCIP-read, which permits the provider to be redirected to web-based content during execution, which is then further validated by the contract.\nThere are potential security implications allowing CCIP-read, as it could be used to expose the IP address or user activity during the fetch to unexpected parties.\n\n<src>transactionRequest.from⇒ null | AddressLike\nThe sender of the transaction.\n\n<src>transactionRequest.gasLimit⇒ null | BigNumberish\nThe maximum amount of gas to allow this transaction to consume.\n\n<src>transactionRequest.gasPrice⇒ null | BigNumberish\nThe gas price to use for legacy transactions or transactions on legacy networks.\nMost of the time the max*FeePerGas is preferred.\n\n<src>transactionRequest.kzg⇒ null | KzgLibraryLike\nAn external library for computing the KZG commitments and proofs necessary for EIP-4844 transactions (see EIP-4844).\nThis is generally null, unless you are creating BLOb transactions.\n\n<src>transactionRequest.maxFeePerBlobGas⇒ null | BigNumberish\nThe maximum fee per blob gas (see EIP-4844).\n\n<src>transactionRequest.maxFeePerGas⇒ null | BigNumberish\nThe EIP-1559 maximum total fee to pay per gas. The actual value used is protocol enforced to be the block's base fee.\n\n<src>transactionRequest.maxPriorityFeePerGas⇒ null | BigNumberish\nThe EIP-1559 maximum priority fee to pay per gas.\n\n<src>transactionRequest.nonce⇒ null | number\nThe nonce of the transaction, used to prevent replay attacks.\n\n<src>transactionRequest.to⇒ null | AddressLike\nThe target of the transaction.\n\n<src>transactionRequest.type⇒ null | number\nThe transaction type.\n\n<src>transactionRequest.value⇒ null | BigNumberish\nThe transaction value (in wei).\n\nclass TransactionResponse\ninherits from TransactionResponseParams\nA TransactionResponse includes all properties about a transaction that was sent to the network, which may or may not be included in a block.\nThe transactionResponse.isMined can be used to check if the transaction has been mined as well as type guard that the otherwise possibly null properties are defined.\n\nPROPERTIES\n<src>transactionResponse.accessList⇒ null | AccessListread-only\nThe EIP-2930 access list for transaction types that support it, otherwise null.\n\n<src>transactionResponse.authorizationList⇒ null | Array< Authorization >read-only\nThe EIP-7702 authorizations (if any).\n\n<src>transactionResponse.blobVersionedHashes⇒ null | Array< string >read-only\nThe EIP-4844 BLOb versioned hashes.\n\n<src>transactionResponse.blockHash⇒ null | stringread-only\nThe blockHash of the block that this transaction was included in.\nThis is null for pending transactions.\n\n<src>transactionResponse.blockNumber⇒ null | numberread-only\nThe block number of the block that this transaction was included in.\nThis is null for pending transactions.\n\n<src>transactionResponse.chainId⇒ bigintread-only\nThe chain ID.\n\n<src>transactionResponse.data⇒ stringread-only\nThe data.\n\n<src>transactionResponse.from⇒ stringread-only\nThe sender of this transaction. It is implicitly computed from the transaction pre-image hash (as the digest) and the signature using ecrecover.\n\n<src>transactionResponse.gasLimit⇒ bigintread-only\nThe maximum units of gas this transaction can consume. If execution exceeds this, the entries transaction is reverted and the sender is charged for the full amount, despite not state changes being made.\n\n<src>transactionResponse.gasPrice⇒ bigintread-only\nThe gas price can have various values, depending on the network.\nIn modern networks, for transactions that are included this is the effective gas price (the fee per gas that was actually charged), while for transactions that have not been included yet is the maxFeePerGas.\nFor legacy transactions, or transactions on legacy networks, this is the fee that will be charged per unit of gas the transaction consumes.\n\n<src>transactionResponse.hash⇒ stringread-only\nThe transaction hash.\n\n<src>transactionResponse.index⇒ numberread-only\nThe index within the block that this transaction resides at.\n\n<src>transactionResponse.maxFeePerBlobGas⇒ null | bigintread-only\nThe EIP-4844 max fee per BLOb gas.\n\n<src>transactionResponse.maxFeePerGas⇒ null | bigintread-only\nThe maximum fee (per unit of gas) to allow this transaction to charge the sender.\n\n<src>transactionResponse.maxPriorityFeePerGas⇒ null | bigintread-only\nThe maximum priority fee (per unit of gas) to allow a validator to charge the sender. This is inclusive of the maxFeeFeePerGas.\n\n<src>transactionResponse.nonce⇒ numberread-only\nThe nonce, which is used to prevent replay attacks and offer a method to ensure transactions from a given sender are explicitly ordered.\nWhen sending a transaction, this must be equal to the number of transactions ever sent by from.\n\n<src>transactionResponse.provider⇒ Providerread-only\nThe provider this is connected to, which will influence how its methods will resolve its async inspection methods.\n\n<src>transactionResponse.signature⇒ Signatureread-only\nThe signature.\n\n<src>transactionResponse.to⇒ null | stringread-only\nThe receiver of this transaction.\nIf null, then the transaction is an initcode transaction. This means the result of executing the data will be deployed as a new contract on chain (assuming it does not revert) and the address may be computed using getCreateAddress.\n\n<src>transactionResponse.type⇒ numberread-only\nThe EIP-2718 transaction envelope type. This is 0 for legacy transactions types.\n\n<src>transactionResponse.value⇒ bigintread-only\nThe value, in wei. Use formatEther to format this value as ether.\n\nMETHODS\n<src>transactionResponse.confirmations()⇒ Promise< number >\nResolve to the number of confirmations this transaction has.\n\n<src>transactionResponse.getBlock()⇒ Promise< null | Block >\nResolves to the Block that this transaction was included in.\nThis will return null if the transaction has not been included yet.\n\n<src>transactionResponse.getTransaction()⇒ Promise< null | TransactionResponse >\nResolves to this transaction being re-requested from the provider. This can be used if you have an unmined transaction and wish to get an up-to-date populated instance.\n\n<src>transactionResponse.isBerlin()⇒ boolean\nReturns true if the transaction is a Berlin (i.e. type == 1) transaction. See EIP-2930.\nThis provides a Type Guard that this transaction will have the null-ness for hardfork-specific properties set correctly.\n\n<src>transactionResponse.isCancun()⇒ boolean\nReturns true if hte transaction is a Cancun (i.e. type == 3) transaction. See EIP-4844.\n\n<src>transactionResponse.isLegacy()⇒ boolean\nReturns true if the transaction is a legacy (i.e. type == 0) transaction.\nThis provides a Type Guard that this transaction will have the null-ness for hardfork-specific properties set correctly.\n\n<src>transactionResponse.isLondon()⇒ boolean\nReturns true if the transaction is a London (i.e. type == 2) transaction. See EIP-1559.\nThis provides a Type Guard that this transaction will have the null-ness for hardfork-specific properties set correctly.\n\n<src>transactionResponse.isMined()⇒ boolean\nReturns true if this transaction has been included.\nThis is effective only as of the time the TransactionResponse was instantiated. To get up-to-date information, use getTransaction.\nThis provides a Type Guard that this transaction will have non-null property values for properties that are null for unmined transactions.\n\n<src>transactionResponse.removedEvent()⇒ OrphanFilter\nReturns a filter which can be used to listen for orphan events that evict this transaction.\n\n<src>transactionResponse.reorderedEvent(other?: TransactionResponse)⇒ OrphanFilter\nReturns a filter which can be used to listen for orphan events that re-order this event against other.\n\n<src>transactionResponse.replaceableTransaction(startBlock: number)⇒ TransactionResponse\nReturns a new TransactionResponse instance which has the ability to detect (and throw an error) if the transaction is replaced, which will begin scanning at startBlock.\nThis should generally not be used by developers and is intended primarily for internal use. Setting an incorrect startBlock can have devastating performance consequences if used incorrectly.\n\n<src>transactionResponse.toJSON()⇒ any\nReturns a JSON-compatible representation of this transaction.\n\n<src>transactionResponse.wait(confirms?: number, timeout?: number)⇒ Promise< null | TransactionReceipt >\nResolves once this transaction has been mined and has confirms blocks including it (default: 1) with an optional timeout.\nThis can resolve to null only if confirms is 0 and the transaction has not been mined, otherwise this will wait until enough confirmations have completed.\n\ninterface WebSocketLike\nA generic interface to a Websocket-like object.\n\nPROPERTIES\n<src>webSocketLike.onerror⇒ null | PAREN<(args: Array< any >) => any>\n\n<src>webSocketLike.onmessage⇒ null | PAREN<(args: Array< any >) => any>\n\n<src>webSocketLike.onopen⇒ null | PAREN<(args: Array< any >) => any>\n\n<src>webSocketLike.readyState⇒ number\n\nMETHODS\n<src>webSocketLike.close(code?: number, reason?: string)⇒ void\n\n<src>webSocketLike.send(payload: any)⇒ void\n\nclass WebSocketProvider\ninherits from SocketProvider, JsonRpcApiProvider\nA JSON-RPC provider which is backed by a WebSocket.\nWebSockets are often preferred because they retain a live connection to a server, which permits more instant access to events.\nHowever, this incurs higher server infrasturture costs, so additional resources may be required to host your own WebSocket nodes and many third-party services charge additional fees for WebSocket endpoints.\n\nPROPERTIES\n<src>webSocketProvider.websocket⇒ WebSocketLikeread-only\n\nCREATING INSTANCES\n<src>new WebSocketProvider(url: string | WebSocketLike | WebSocketCreator, network?: Networkish, options?: JsonRpcApiProviderOptions)\n\nNetworks\nA Network encapsulates the various properties required to interact with a specific chain.\n\nTYPES\n<src>Networkish⇒ Network | number | bigint | string | { chainId?: number , ensAddress?: string , ensNetwork?: number , ensUniversalResolver?: string , name?: string }\nA Networkish can be used to allude to a Network, by specifing:\n\na Network object\na well-known (or registered) network name\na well-known (or registered) chain ID\nan object with sufficient details to describe a network\n\nclass Network\nA Network provides access to a chain's properties and allows for plug-ins to extend functionality.\n\nPROPERTIES\n<src>network.chainId⇒ bigint\nThe network chain ID.\n\n<src>network.name⇒ string\nThe network common name.\nThis is the canonical name, as networks migh have multiple names.\n\n<src>network.plugins⇒ Array< NetworkPlugin >read-only\nReturns the list of plugins currently attached to this Network.\n\nCREATING INSTANCES\n<src>new Network(name: string, chainId: BigNumberish)\nCreates a new Network for name and chainId.\n\n<src>Network.from(network?: Networkish)⇒ Network\nReturns a new Network for the network name or chainId.\n\nMETHODS\n<src>network.attachPlugin(plugin: NetworkPlugin)⇒ this\nAttach a new plugin to this Network. The network name must be unique, excluding any fragment.\n\n<src>network.clone()⇒ Network\nCreate a copy of this Network.\n\n<src>network.computeIntrinsicGas(tx: TransactionLike)⇒ number\nCompute the intrinsic gas required for a transaction.\nA GasCostPlugin can be attached to override the default values.\n\n<src>network.getPlugin(name: string)⇒ null | T\nReturn the plugin, if any, matching name exactly. Plugins with fragments will not be returned unless name includes a fragment.\n\n<src>network.getPlugins(basename: string)⇒ Array< T >\nGets a list of all plugins that match name, with otr without a fragment.\n\n<src>network.inspect()⇒ string\n\n<src>network.matches(other: Networkish)⇒ boolean\nReturns true if other matches this network. Any chain ID must match, and if no chain ID is present, the name must match.\nThis method does not currently check for additional properties, such as ENS address or plug-in compatibility.\n\n<src>network.toJSON()⇒ any\nReturns a JSON-compatible representation of a Network.\n\n<src>network.toString()⇒ string\n\nSTATIC METHODS\n<src>Network.register(nameOrChainId: string | number | bigint, networkFunc: () => Network)⇒ void\nRegister nameOrChainId with a function which returns an instance of a Network representing that chain.\n\n← Hashing Utilities\nSubclassing Provider→\n\nThe content of this site is licensed under the Creative Commons License. Generated on April 9, 2026, 11:51pm.","tokens":13402,"crawled_at":1791193838481}
+{"id":10297,"url":"https://www.metaplex.com/docs/smart-contracts/core/sdk/javascript","domain":"www.metaplex.com","chapter":"docs","title":"JavaScript SDK | Metaplex Core","text":"The Metaplex Core JavaScript SDK (@metaplex-foundation/mpl-core) provides a complete TypeScript/JavaScript interface for interacting with Core Assets and Collections on Solana. Built on the Umi framework, it offers type-safe methods for all Core operations.\nWhat You'll Learn\nThis SDK reference covers:\nSetting up Umi with the Core plugin\nCreating, transferring, burning, and updating Assets\nManaging Collections and collection-level operations\nAdding, updating, and removing Plugins\nFetching Assets and Collections with DAS\nError handling and common patterns\n\nSummary\nThe Core JavaScript SDK is the recommended way to interact with Metaplex Core from JavaScript/TypeScript applications. It wraps the Core program instructions in a type-safe API.\nInstall: npm install @metaplex-foundation/mpl-core @metaplex-foundation/umi\nRequires Umi framework for wallet/RPC management\nAll functions return transaction builders for flexible execution\nSupports both browser and Node.js environments\nOut of Scope\nRust SDK usage (see Rust SDK), Token Metadata operations, Candy Machine integration, and low-level Solana transaction construction.\nQuick Start\nJump to: Setup · Create · Transfer · Burn · Update · Collections · Plugins · Fetch · Errors · FAQ\nInstall dependencies: npm install @metaplex-foundation/mpl-core @metaplex-foundation/umi-bundle-defaults\nCreate Umi instance with mplCore() plugin\nGenerate or load a signer for transactions\nCall SDK functions and confirm transactions\nPrerequisites\nNode.js 18+ or modern browser with ES modules\nUmi framework configured with RPC and signer\nSOL for rent and fees (~0.003 SOL per base asset; rent varies with asset size)\nAPI Reference\nFull TypeDoc API documentation for the SDK.\n\nNPM Package\nPackage on npmjs.com with version history.\n\nInstallation\nInstall the Core SDK and Umi framework:\nTerminal\nnpm install @metaplex-foundation/mpl-core @metaplex-foundation/umi-bundle-defaults\n\nFor metadata uploads, add an uploader plugin:\nTerminal\nnpm install @metaplex-foundation/umi-uploader-irys\n\nUmi Setup\nCreate and configure an Umi instance with the Core plugin:\nsetup-umi.ts\nimport { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\nimport { mplCore } from '@metaplex-foundation/mpl-core'\n\nimport { keypairIdentity } from '@metaplex-foundation/umi'\n\nimport { irysUploader } from '@metaplex-foundation/umi-uploader-irys'\n\n// Create Umi with RPC endpoint\n\nconst umi = createUmi('https://api.devnet.solana.com')\n\n.use(mplCore())\n\n.use(keypairIdentity(yourKeypair))\n\n.use(irysUploader()) // Optional: for metadata uploads\n\nAssets\nCreate an Asset\nUse create() to mint a new Core Asset:\n\n1import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n2import { create } from '@metaplex-foundation/mpl-core'\n\n3import { mplCore } from '@metaplex-foundation/mpl-core'\n\n4\n\n5// Initialize UMI\n\n6const umi = createUmi('https://api.devnet.solana.com')\n\n7 .use(mplCore())\n\n8\n\n9// Create a new NFT asset\n\n10const asset = await create(umi, {\n\n11 name: 'My NFT',\n\n12 uri: 'https://example.com/metadata.json'\n\n13}).sendAndConfirm(umi)\n\n14\n\n15console.log('Asset created:', asset.publicKey)\n\nTransfer an Asset\nUse transfer() to send an Asset to another wallet:\n\n1import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n2import { transfer } from '@metaplex-foundation/mpl-core'\n\n3import { mplCore } from '@metaplex-foundation/mpl-core'\n\n4import { publicKey } from '@metaplex-foundation/umi'\n\n5\n\n6// Initialize UMI\n\n7const umi = createUmi('https://api.devnet.solana.com')\n\n8 .use(mplCore())\n\n9\n\n10// Transfer an existing NFT asset to a new owner\n\n11const result = await transfer(umi, {\n\n12 asset: publicKey('AssetAddressHere...'),\n\n13 newOwner: publicKey('RecipientAddressHere...'),\n\n14}).sendAndConfirm(umi)\n\n15\n\n16console.log('Asset transferred:', result.signature)\n\nBurn an Asset\nUse burn() to permanently destroy an Asset and reclaim rent:\n\n1import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n2import { burn } from '@metaplex-foundation/mpl-core'\n\n3import { mplCore } from '@metaplex-foundation/mpl-core'\n\n4import { publicKey } from '@metaplex-foundation/umi'\n\n5\n\n6const umi = createUmi('https://api.devnet.solana.com').use(mplCore())\n\n7const assetAddress = publicKey('AssetAddressHere...')\n\n8\n\n9// Permanently destroy/burn an NFT asset\n\n10const result = await burn(umi, {\n\n11 asset: assetAddress,\n\n12}).sendAndConfirm(umi)\n\n13\n\n14console.log('Asset burned successfully')\n\nWithdraw Asset Signer balances first\nBurning the Asset makes execute fail. SOL, tokens, or other assets still held by the Asset Signer PDA become stranded.\n\nUpdate an Asset\nUse update() to modify Asset metadata:\n\n1import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n2import { update } from '@metaplex-foundation/mpl-core'\n\n3import { mplCore } from '@metaplex-foundation/mpl-core'\n\n4import { publicKey } from '@metaplex-foundation/umi'\n\n5\n\n6const umi = createUmi('https://api.devnet.solana.com').use(mplCore())\n\n7const assetAddress = publicKey('AssetAddressHere...')\n\n8\n\n9// Update an existing NFT asset's metadata\n\n10const result = await update(umi, {\n\n11 asset: assetAddress,\n\n12 name: 'Updated NFT Name',\n\n13 uri: 'https://updated-example.com/metadata.json',\n\n14}).sendAndConfirm(umi)\n\n15\n\n16console.log('Asset updated successfully')\n\nCollections\nCreate a Collection\nUse createCollection() to create a Collection account:\n\n1import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n2import { createCollection } from '@metaplex-foundation/mpl-core'\n\n3import { mplCore } from '@metaplex-foundation/mpl-core'\n\n4import { generateSigner } from '@metaplex-foundation/umi'\n\n5\n\n6// Initialize UMI\n\n7const umi = createUmi('https://api.devnet.solana.com')\n\n8 .use(mplCore())\n\n9\n\n10// Generate a new keypair for the collection\n\n11const collectionSigner = generateSigner(umi)\n\n12\n\n13// Create a new Collection\n\n14await createCollection(umi, {\n\n15 collection: collectionSigner,\n\n16 name: 'My Collection',\n\n17 uri: 'https://example.com/collection.json',\n\n18}).sendAndConfirm(umi)\n\n19\n\n20console.log('Collection created:', collectionSigner.publicKey)\n\nCreate Asset in Collection\nPass the collection parameter to create():\n\n1import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n2import { create, fetchCollection } from '@metaplex-foundation/mpl-core'\n\n3import { mplCore } from '@metaplex-foundation/mpl-core'\n\n4import { generateSigner, publicKey } from '@metaplex-foundation/umi'\n\n5\n\n6// Initialize UMI\n\n7const umi = createUmi('https://api.devnet.solana.com')\n\n8 .use(mplCore())\n\n9\n\n10const collectionAddress = publicKey('YOUR_COLLECTION_ADDRESS')\n\n11\n\n12// Fetch the existing collection\n\n13const collection = await fetchCollection(umi, collectionAddress)\n\n14\n\n15// Generate a new keypair for the asset\n\n16const assetSigner = generateSigner(umi)\n\n17\n\n18// Create asset in the collection\n\n19await create(umi, {\n\n20 asset: assetSigner,\n\n21 collection,\n\n22 name: 'Collection Item #1',\n\n23 uri: 'https://example.com/item1.json',\n\n24}).sendAndConfirm(umi)\n\n25\n\n26console.log('Asset created in collection:', assetSigner.publicKey)\n\nPlugins\nPlugins add behavior to Assets and Collections. They can be added at creation time or afterwards.\nAdd Plugin at Creation\n\n1import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n2import { create, ruleSet } from '@metaplex-foundation/mpl-core'\n\n3import { mplCore } from '@metaplex-foundation/mpl-core'\n\n4import { generateSigner, publicKey } from '@metaplex-foundation/umi'\n\n5\n\n6// Initialize UMI\n\n7const umi = createUmi('https://api.devnet.solana.com')\n\n8 .use(mplCore())\n\n9\n\n10const creator = publicKey('YOUR_CREATOR_ADDRESS')\n\n11\n\n12// Generate a new keypair for the asset\n\n13const assetSigner = generateSigner(umi)\n\n14\n\n15// Create asset with Royalties plugin\n\n16await create(umi, {\n\n17 asset: assetSigner,\n\n18 name: 'NFT with Royalties',\n\n19 uri: 'https://example.com/metadata.json',\n\n20 plugins: [\n\n21 {\n\n22 type: 'Royalties',\n\n23 basisPoints: 500, // 5%\n\n24 creators: [\n\n25 { address: creator, percentage: 100 },\n\n26 ],\n\n27 ruleSet: ruleSet('None'),\n\n28 },\n\n29 ],\n\n30}).sendAndConfirm(umi)\n\n31\n\n32console.log('Asset created with plugins:', assetSigner.publicKey)\n\nAdd Plugin to Existing Asset\n\n1import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n2import { addPlugin, fetchAsset, ruleSet } from '@metaplex-foundation/mpl-core'\n\n3import { mplCore } from '@metaplex-foundation/mpl-core'\n\n4import { publicKey } from '@metaplex-foundation/umi'\n\n5\n\n6// Initialize UMI\n\n7const umi = createUmi('https://api.devnet.solana.com')\n\n8 .use(mplCore())\n\n9\n\n10const assetAddress = publicKey('YOUR_ASSET_ADDRESS')\n\n11\n\n12// Fetch the existing asset\n\n13const asset = await fetchAsset(umi, assetAddress)\n\n14\n\n15// Add a Royalties plugin to the asset\n\n16await addPlugin(umi, {\n\n17 asset,\n\n18 plugin: {\n\n19 type: 'Royalties',\n\n20 basisPoints: 500, // 5%\n\n21 creators: [\n\n22 { address: umi.identity.publicKey, percentage: 100 },\n\n23 ],\n\n24 ruleSet: ruleSet('None'),\n\n25 },\n\n26}).sendAndConfirm(umi)\n\n27\n\n28console.log('Plugin added to asset:', assetAddress)\n\nCommon Plugin Types\nPluginType StringPurpose\nRoyalties\n'Royalties'\nCreator royalty enforcement\n\nFreeze Delegate\n'FreezeDelegate'\nAllow freezing/unfreezing\n\nBurn Delegate\n'BurnDelegate'\nAllow burning by delegate\n\nTransfer Delegate\n'TransferDelegate'\nAllow transfers by delegate\n\nUpdate Delegate\n'UpdateDelegate'\nAllow metadata updates\n\nAttributes\n'Attributes'\nOn-chain key/value data\n\nPermanent Freeze\n'PermanentFreezeDelegate'\nPermanent freeze state\n\nPermanent Transfer\n'PermanentTransferDelegate'\nPermanent transfer delegate\n\nPermanent Burn\n'PermanentBurnDelegate'\nPermanent burn delegate\n\nSee Plugins Overview for detailed plugin documentation.\n\nFetching Assets\nFetch Single Asset\n\n1import { fetchAsset, fetchCollection, mplCore } from '@metaplex-foundation/mpl-core';\n\n2import { publicKey } from '@metaplex-foundation/umi';\n\n3import { createUmi } from '@metaplex-foundation/umi-bundle-defaults';\n\n4\n\n5// Initialize UMI\n\n6const umi = createUmi('https://api.devnet.solana.com')\n\n7 .use(mplCore())\n\n8\n\n9// Fetch a Core Asset\n\n10const assetAddress = publicKey('AssetAddressHere...')\n\n11const asset = await fetchAsset(umi, assetAddress)\n\n12\n\n13// Fetch a Core Collection\n\n14const collectionAddress = publicKey('CollectionAddressHere...')\n\n15const collection = await fetchCollection(umi, collectionAddress)\n\n16\n\n17console.log('Asset fetched:', asset)\n\n18console.log('Name:', asset.name)\n\n19console.log('Owner:', asset.owner)\n\n20console.log('URI:', asset.uri)\n\n21\n\n22console.log('\\nCollection fetched:', collection)\n\n23console.log('Name:', collection.name)\n\n24console.log('URI:', collection.uri)\n\nFetch Assets by Owner (DAS)\nUse the DAS API to query indexed assets:\nfetch-by-owner.ts\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { dasApi } from '@metaplex-foundation/digital-asset-standard-api'\n\n// Add DAS plugin to Umi\n\nconst umi = createUmi('https://api.devnet.solana.com')\n\n.use(mplCore())\n\n.use(dasApi())\n\nconst owner = publicKey('OwnerAddressHere...')\n\nconst assets = await umi.rpc.getAssetsByOwner({\n\nowner,\n\nlimit: 100,\n\n})\n\nconsole.log('Assets owned:', assets.items.length)\n\nFetch Assets by Collection (DAS)\nfetch-by-collection.ts\nimport { publicKey } from '@metaplex-foundation/umi'\n\nconst collectionAddress = publicKey('CollectionAddressHere...')\n\nconst assets = await umi.rpc.getAssetsByGroup({\n\ngroupKey: 'collection',\n\ngroupValue: collectionAddress,\n\nlimit: 100,\n\n})\n\nconsole.log('Collection assets:', assets.items.length)\n\nUploading Metadata\nUse Umi's uploader plugins to store metadata JSON:\nupload-metadata.ts\nimport { irysUploader } from '@metaplex-foundation/umi-uploader-irys'\n\nconst umi = createUmi('https://api.devnet.solana.com')\n\n.use(mplCore())\n\n.use(keypairIdentity(yourKeypair))\n\n.use(irysUploader())\n\n// Upload image first\n\nconst imageFile = await fs.promises.readFile('image.png')\n\nconst [imageUri] = await umi.uploader.upload([imageFile])\n\n// Upload metadata JSON\n\nconst uri = await umi.uploader.uploadJson({\n\nname: 'My NFT',\n\ndescription: 'An awesome NFT',\n\nimage: imageUri,\n\nattributes: [\n\n{ trait_type: 'Background', value: 'Blue' },\n\n{ trait_type: 'Rarity', value: 'Rare' },\n\n],\n\n})\n\nconsole.log('Metadata URI:', uri)\n\nTransaction Patterns\nSend and Confirm\nThe standard pattern waits for confirmation:\nsend-confirm.ts\nconst result = await create(umi, { asset, name, uri }).sendAndConfirm(umi)\n\nconsole.log('Signature:', result.signature)\n\nCustom Confirmation Options\ncustom-confirm.ts\nconst result = await create(umi, { asset, name, uri }).sendAndConfirm(umi, {\n\nconfirm: { commitment: 'finalized' },\n\n})\n\nBuild Transaction Without Sending\nbuild-only.ts\nconst tx = create(umi, { asset, name, uri })\n\nconst builtTx = await tx.buildAndSign(umi)\n\n// Send later with: await umi.rpc.sendTransaction(builtTx)\n\nCombine Multiple Instructions\ncombine-instructions.ts\nimport { transactionBuilder } from '@metaplex-foundation/umi'\n\nconst tx = transactionBuilder()\n\n.add(create(umi, { asset: asset1, name: 'NFT 1', uri: uri1 }))\n\n.add(create(umi, { asset: asset2, name: 'NFT 2', uri: uri2 }))\n\nawait tx.sendAndConfirm(umi)\n\nCommon Errors\nAccount does not exist\nThe asset or collection address doesn't exist. Verify the address is correct:\nconst asset = await fetchAsset(umi, assetAddress).catch(() => null)\n\nif (!asset) {\n\nconsole.log('Asset not found')\n\n}\n\nInvalid authority\nYou're not authorized to perform this action. Check that:\nYou own the asset (for transfers, burns)\nYou're the update authority (for updates)\nYou have the required delegate permission\nInsufficient funds\nYour wallet needs more SOL. Fund it with:\nsolana airdrop 1 <WALLET_ADDRESS> --url devnet\n\nAsset already exists\nThe asset keypair was already used. Generate a new signer:\nconst assetSigner = generateSigner(umi) // Must be unique\n\nPlugin not found\nThe plugin doesn't exist on this asset. Check installed plugins:\nconst asset = await fetchAsset(umi, assetAddress)\n\nconsole.log('Plugins:', Object.keys(asset))\n\nNotes\nAlways use a new keypair for new assets - never reuse keypairs\nThe asset parameter in create() must be a signer, not just a public key\nCollection-level plugins override asset-level plugins of the same type\nUse commitment: 'finalized' when creating assets that you immediately fetch\nTransaction builders are immutable - each method returns a new builder\nEmpty the Asset Signer PDA before burn() — remaining balances cannot be moved afterward\nQuick Reference\nMinimum Dependencies\npackage.json\n{\n\n\"dependencies\": {\n\n\"@metaplex-foundation/mpl-core\": \"^1.0.0\",\n\n\"@metaplex-foundation/umi\": \"^0.9.0\",\n\n\"@metaplex-foundation/umi-bundle-defaults\": \"^0.9.0\"\n\n}\n\n}\n\nCore Functions\nFunctionPurpose\ncreate()\nCreate a new Asset\n\ncreateCollection()\nCreate a new Collection\n\ntransfer()\nTransfer Asset ownership\n\nburn()\nDestroy an Asset\n\nupdate()\nUpdate Asset metadata\n\nupdateCollection()\nUpdate Collection metadata\n\naddPlugin()\nAdd plugin to Asset\n\naddCollectionPlugin()\nAdd plugin to Collection\n\nupdatePlugin()\nUpdate existing plugin\n\nremovePlugin()\nRemove plugin from Asset\n\nfetchAsset()\nFetch Asset by address\n\nfetchCollection()\nFetch Collection by address\n\nProgram ID\nNetworkAddress\nMainnet\nCoREENxT6tW1HoK8ypY1SxRMZTcVPm7R94rH4PZNhX7d\n\nDevnet\nCoREENxT6tW1HoK8ypY1SxRMZTcVPm7R94rH4PZNhX7d\n\nFAQ\nWhat is the Core JavaScript SDK?\nThe Core JavaScript SDK (@metaplex-foundation/mpl-core) is a TypeScript library for interacting with Metaplex Core NFTs on Solana. It provides type-safe functions for creating, transferring, burning, and managing Assets and Collections.\nDo I need Umi to use this SDK?\nYes. The Core SDK is built on the Umi framework, which handles wallet connections, RPC communication, and transaction building. Install both @metaplex-foundation/mpl-core and @metaplex-foundation/umi-bundle-defaults.\nHow do I connect a browser wallet?\nUse the @metaplex-foundation/umi-signer-wallet-adapters package with your wallet adapter:\nimport { walletAdapterIdentity } from '@metaplex-foundation/umi-signer-wallet-adapters'\n\numi.use(walletAdapterIdentity(wallet))\n\nWhat's the difference between sendAndConfirm and send?\nsendAndConfirm() waits for transaction confirmation before returning. send() returns immediately after broadcasting. Use sendAndConfirm() for most cases to ensure your transaction succeeded.\nHow do I batch multiple operations?\nUse transactionBuilder() to combine instructions, but be aware of Solana's transaction size limits (~1232 bytes). For large batches, send multiple transactions.\nCan I use this SDK in React/Next.js?\nYes. The SDK works in both browser and Node.js environments. For React, use wallet adapters from @solana/wallet-adapter-react with Umi's wallet adapter identity.\nHow do I handle errors?\nWrap SDK calls in try/catch blocks. The SDK throws typed errors that include program error codes:\ntry {\n\nawait transfer(umi, { asset, newOwner }).sendAndConfirm(umi)\n\n} catch (error) {\n\nconsole.error('Transfer failed:', error.message)\n\n}\n\nWhere can I find the full API documentation?\nSee the TypeDoc API Reference for complete function signatures and types.\nGlossary\nTermDefinition\nUmi\nMetaplex's framework for building Solana applications with wallet and RPC management\n\nAsset\nA Core on-chain account representing an NFT with ownership, metadata, and plugins\n\nCollection\nA Core account that groups related Assets and can apply collection-wide plugins\n\nSigner\nA keypair that can sign transactions (required for creating new accounts)\n\nPlugin\nA modular extension that adds behavior to Assets or Collections\n\nURI\nThe off-chain metadata URL pointing to a JSON file with name, image, and attributes\n\nDAS\nDigital Asset Standard - API for querying indexed NFT data from RPC providers\n\nTransaction Builder\nAn immutable object that constructs transactions before sending\n\nIdentity\nThe wallet/keypair configured as the transaction signer in Umi\n\nCommitment\nSolana confirmation level (processed, confirmed, finalized)","tokens":4484,"crawled_at":1791193849990}
+{"id":10298,"url":"https://a16zcrypto.com/posts/videos/transaction-fee-mechanism-design-with-active-block-producers","domain":"a16zcrypto.com","chapter":"research","title":"Transaction fee mechanism design with active block producers - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nTransaction fee mechanism design with active block producers\nPranav Garimidi\n09.21.23\n\nTags & Share Tags\nDeFi\nmev\nresearch\nvideo\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nThe incentive-compatibility properties of blockchain transaction fee mechanisms have been investigated with passive block producers, which are motivated by the net rewards earned at the consensus layer. Here, Pranav Garimidi (a16z crypto research) explores active block producers, which have their own private valuations for blocks. These private valuations might stem, for example, additional value derived from the application layer (colloquially understood as “MEV”). In this model, transaction fee mechanism design is fundamentally more difficult: with active block producers, no non-trivial or approximately welfare-maximizing transaction fee mechanism can be incentive-compatible for both users and block producers. These results can be interpreted as a mathematical justification for the current interest in augmenting transaction fee mechanisms with additional components such as order flow auctions, block producer competition, trusted hardware, or cryptographic techniques.\n\nAbout the speaker\n\nPranav is a Research Analyst at a16z Crypto. He completed his degree in Computer Science from Columbia University and is broadly interested in studying mechanism design problems in blockchains with a particular focus on thinking about how mechanisms interface with MEV.\n\nAbout a16z crypto research\n\na16z crypto research is a multidisciplinary lab that works closely with our portfolio companies and others toward solving the important problems in the space, and toward advancing the science and technology of the next generation of the internet.","tokens":464,"crawled_at":1791193850227}
+{"id":10299,"url":"https://docs.ethers.org/v6/api/contract","domain":"docs.ethers.org","chapter":"developer_specs","title":"","text":"ethers\n6.17.0\n\nDOCUMENTATION\nGetting Started\nEthereum Basics\nApplication Programming Interface\nPollingBlockTagSubscriber\nApplication Binary Interface\nAddresses\nConstants\nContracts\nBaseContract\nBaseContractMethod\nConstantContractMethod\nContract\nContractDeployTransaction\nContractEvent\nContractEventPayload\nContractFactory\nContractInterface\nContractMethod\nContractTransaction\nContractTransactionReceipt\nContractTransactionResponse\nContractUnknownEventPayload\nDeferredTopicFilter\nEventLog\nOverrides\nUndecodedEventLog\nWrappedFallback\nCryptographic Functions\nHashing Utilities\nProviders\nTransactions\nUtilities\nWallets\nWordlists\nCookbook\nMigrating from v5\nContributions and Hacking\nLicense and Copyright\n\nSingle Page\n\nDocumentation »API »Contracts\nContracts\nA Contract object is a meta-class (a class whose definition is defined at runtime), which communicates with a deployed smart contract on the blockchain and provides a simple JavaScript interface to call methods, send transaction, query historic logs and listen for its events.\n\nTYPES\n<src>ContractEventName⇒ string | ContractEvent | TopicFilter | DeferredTopicFilter\nThe name for an event used for subscribing to Contract events.\nstring - An event by name. The event must be non-ambiguous. The parameters will be dereferenced when passed into the listener.\nContractEvent - A filter from the contract.filters, which will pass only the EventPayload as a single parameter, which includes a .signature property that can be used to further filter the event.\nTopicFilter - A filter defined using the standard Ethereum API which provides the specific topic hash or topic hashes to watch for along with any additional values to filter by. This will only pass a single parameter to the listener, the EventPayload which will include additional details to refine by, such as the event name and signature.\nDeferredTopicFilter - A filter created by calling a ContractEvent with parameters, which will create a filter for a specific event signature and dereference each parameter when calling the listener.\n\nclass BaseContract\ninherits from Addressable\n\nPROPERTIES\n<src>baseContract.fallback⇒ null | WrappedFallbackread-only\nThe fallback or receive function if any.\n\n<src>baseContract.filters⇒ Record< string, ContractEvent >read-only\nAll the Events available on this contract.\n\n<src>baseContract.interface⇒ Interfaceread-only\nThe contract Interface.\n\n<src>baseContract.runner⇒ null | ContractRunnerread-only\nThe connected runner. This is generally a Provider or a Signer, which dictates what operations are supported.\nFor example, a Contract connected to a Provider may only execute read-only operations.\n\n<src>baseContract.target⇒ string | Addressableread-only\nThe target to connect to.\nThis can be an address, ENS name or any Addressable, such as another contract. To get the resolved address, use the getAddress method.\n\nCREATING INSTANCES\n<src>new BaseContract(target: string | Addressable, abi: Interface | InterfaceAbi, runner?: null | ContractRunner, deployTx?: null | TransactionResponse)\nCreates a new contract connected to target with the abi and optionally connected to a runner to perform operations on behalf of.\n\nMETHODS\n<src>baseContract.addListener(event: ContractEventName, listener: Listener)⇒ Promise< this >\nAlias for [on].\n\n<src>baseContract.attach(target: string | Addressable)⇒ BaseContract\nReturn a new Contract instance with the same ABI and runner, but a different target.\n\n<src>baseContract.connect(runner: null | ContractRunner)⇒ BaseContract\nReturn a new Contract instance with the same target and ABI, but a different runner.\n\n<src>baseContract.deploymentTransaction()⇒ null | ContractTransactionResponse\nReturn the transaction used to deploy this contract.\nThis is only available if this instance was returned from a ContractFactory.\n\n<src>baseContract.emit(event: ContractEventName, args: Array< any >)⇒ Promise< boolean >\nEmit an event calling all listeners with args.\nResolves to true if any listeners were called.\n\n<src>baseContract.getAddress()⇒ Promise< string >\nReturn the resolved address of this Contract.\n\n<src>baseContract.getDeployedCode()⇒ Promise< null | string >\nReturn the deployed bytecode or null if no bytecode is found.\n\n<src>baseContract.getEvent(key: string | EventFragment)⇒ ContractEvent\nReturn the event for a given name. This is useful when a contract event name conflicts with a JavaScript name such as prototype or when using a Contract programmatically.\n\n<src>baseContract.getFunction(key: string | FunctionFragment)⇒ T\nReturn the function for a given name. This is useful when a contract method name conflicts with a JavaScript name such as prototype or when using a Contract programmatically.\n\n<src>baseContract.listenerCount(event?: ContractEventName)⇒ Promise< number >\nResolves to the number of listeners of event or the total number of listeners if unspecified.\n\n<src>baseContract.listeners(event?: ContractEventName)⇒ Promise< Array< Listener > >\nResolves to the listeners subscribed to event or all listeners if unspecified.\n\n<src>baseContract.off(event: ContractEventName, listener?: Listener)⇒ Promise< this >\nRemove the listener from the listeners for event or remove all listeners if unspecified.\n\n<src>baseContract.on(event: ContractEventName, listener: Listener)⇒ Promise< this >\nAdd an event listener for the event.\n\n<src>baseContract.once(event: ContractEventName, listener: Listener)⇒ Promise< this >\nAdd an event listener for the event, but remove the listener after it is fired once.\n\n<src>baseContract.queryFilter(event: ContractEventName, fromBlock?: BlockTag, toBlock?: BlockTag)⇒ Promise< Array< EventLog | Log > >\nProvide historic access to event data for event in the range fromBlock (default: 0) to toBlock (default: \"latest\") inclusive.\n\n<src>baseContract.removeAllListeners(event?: ContractEventName)⇒ Promise< this��>\nRemove all the listeners for event or remove all listeners if unspecified.\n\n<src>baseContract.removeListener(event: ContractEventName, listener: Listener)⇒ Promise< this >\nAlias for [off].\n\n<src>baseContract.waitForDeployment()⇒ Promise< this >\nResolve to this Contract once the bytecode has been deployed, or resolve immediately if already deployed.\n\nSTATIC METHODS\n<src>BaseContract.buildClass(abi: Interface | InterfaceAbi)⇒ TODO(A2Bconstructor(@TODO-001))\nCreate a new Class for the abi.\n\n<src>BaseContract.from(target: string, abi: Interface | InterfaceAbi, runner?: null | ContractRunner)⇒ BaseContract & Omit< T, keyof<BaseContract> >\nCreate a new BaseContract with a specified Interface.\n\ninterface BaseContractMethod\nA Contract method can be called directly, or used in various ways.\n\nPROPERTIES\n<src>baseContractMethod.fragment⇒ FunctionFragment\nThe fragment of the Contract method. This will throw on ambiguous method names.\n\n<src>baseContractMethod.name⇒ string\nThe name of the Contract method.\n\nMETHODS\n<src>baseContractMethod.estimateGas(args: ContractMethodArgs< A >)⇒ Promise< bigint >\nEstimate the gas to send the contract method with args.\n\n<src>baseContractMethod.getFragment(args: ContractMethodArgs< A >)⇒ FunctionFragment\nReturns the fragment constrained by args. This can be used to resolve ambiguous method names.\n\n<src>baseContractMethod.populateTransaction(args: ContractMethodArgs< A >)⇒ Promise< ContractTransaction >\nReturns a populated transaction that can be used to perform the contract method with args.\n\n<src>baseContractMethod.send(args: ContractMethodArgs< A >)⇒ Promise< ContractTransactionResponse >\nSend a transaction for the contract method with args.\n\n<src>baseContractMethod.staticCall(args: ContractMethodArgs< A >)⇒ Promise< R >\nCall the contract method with args and return the value.\nIf the return value is a single type, it will be dereferenced and returned directly, otherwise the full Result will be returned.\n\n<src>baseContractMethod.staticCallResult(args: ContractMethodArgs< A >)⇒ Promise< Result >\nCall the contract method with args and return the Result without any dereferencing.\n\ninterface ConstantContractMethod\ninherits from ContractMethod, BaseContractMethod\nA pure of view method on a Contract.\n\nclass Contract\nA BaseContract with no type guards on its methods or events.\n\ninterface ContractDeployTransaction\nA deployment transaction for a contract.\n\ninterface ContractEvent\n\nPROPERTIES\n<src>contractEvent.fragment⇒ EventFragment\nThe fragment of the Contract event. This will throw on ambiguous method names.\n\n<src>contractEvent.name⇒ string\nThe name of the Contract event.\n\nMETHODS\n<src>contractEvent.getFragment(args: ContractEventArgs< A >)⇒ EventFragment\nReturns the fragment constrained by args. This can be used to resolve ambiguous event names.\n\nclass ContractEventPayload\ninherits from ContractUnknownEventPayload, EventPayload\nA ContractEventPayload is included as the last parameter to Contract Events when the event is known.\n\nPROPERTIES\n<src>contractEventPayload.args⇒ Resultread-only\nThe parsed arguments passed to the event by emit.\n\n<src>contractEventPayload.eventName⇒ stringread-only\nThe event name.\n\n<src>contractEventPayload.eventSignature⇒ stringread-only\nThe event signature.\n\n<src>contractEventPayload.fragment⇒ EventFragmentread-only\nThe matching event.\n\n<src>contractEventPayload.log⇒ EventLogread-only\nThe log, with parsed properties.\n\nclass ContractFactory\nA ContractFactory is used to deploy a Contract to the blockchain.\n\nPROPERTIES\n<src>contractFactory.bytecode⇒ stringread-only\nThe Contract deployment bytecode. Often called the initcode.\n\n<src>contractFactory.interface⇒ Interfaceread-only\nThe Contract Interface.\n\n<src>contractFactory.runner⇒ null | ContractRunnerread-only\nThe ContractRunner to deploy the Contract as.\n\nCREATING INSTANCES\n<src>new ContractFactory(abi: Interface | InterfaceAbi, bytecode: BytesLike | { object: string }, runner?: null | ContractRunner)\nCreate a new ContractFactory with abi and bytecode, optionally connected to runner.\nThe bytecode may be the bytecode property within the standard Solidity JSON output.\n\nMETHODS\n<src>contractFactory.attach(target: string | Addressable)⇒ BaseContract & Omit< I, keyof<BaseContract> >\n\n<src>contractFactory.connect(runner: null | ContractRunner)⇒ ContractFactory < A, I >\nReturn a new ContractFactory with the same ABI and bytecode, but connected to runner.\n\n<src>contractFactory.deploy(args: ContractMethodArgs< A >)⇒ Promise< BaseContract & { deploymentTransaction: ContractTransactionResponse } & Omit< I, keyof<BaseContract> > >\nResolves to the Contract deployed by passing args into the constructor.\nThis will resolve to the Contract before it has been deployed to the network, so the baseContract.waitForDeployment should be used before sending any transactions to it.\n\n<src>contractFactory.getDeployTransaction(args: ContractMethodArgs< A >)⇒ Promise< ContractDeployTransaction >\nResolves to the transaction to deploy the contract, passing args into the constructor.\n\nSTATIC METHODS\n<src>ContractFactory.fromSolidity(output: any, runner?: ContractRunner)⇒ ContractFactory < A, I >\nCreate a new ContractFactory from the standard Solidity JSON output.\n\ninterface ContractInterface\nA Contract with no method constraints.\n\ninterface ContractMethod\ninherits from BaseContractMethod\nA contract method on a Contract.\n\ninterface ContractTransaction\ninherits from PreparedTransactionRequest\nWhen populating a transaction this type is returned.\n\nPROPERTIES\n<src>contractTransaction.data⇒ string\nThe transaction data.\n\n<src>contractTransaction.from⇒ string\nThe from address, if any.\n\n<src>contractTransaction.to⇒ string\nThe target address.\n\nclass ContractTransactionReceipt\ninherits from TransactionReceipt, TransactionReceiptParams\nA ContractTransactionReceipt includes the parsed logs from a TransactionReceipt.\n\nPROPERTIES\n<src>contractTransactionReceipt.logs⇒ Array< EventLog | Log >read-only\nThe parsed logs for any Log which has a matching event in the Contract ABI.\n\nclass ContractTransactionResponse\ninherits from TransactionResponse, TransactionResponseParams\nA ContractTransactionResponse will return a ContractTransactionReceipt when waited on.\n\nMETHODS\n<src>contractTransactionResponse.wait(confirms?: number, timeout?: number)⇒ Promise< null | ContractTransactionReceipt >\nResolves once this transaction has been mined and has confirms blocks including it (default: 1) with an optional timeout.\nThis can resolve to null only if confirms is 0 and the transaction has not been mined, otherwise this will wait until enough confirmations have completed.\n\nclass ContractUnknownEventPayload\ninherits from EventPayload\nA ContractUnknownEventPayload is included as the last parameter to Contract Events when the event does not match any events in the ABI.\n\nPROPERTIES\n<src>contractUnknownEventPayload.log⇒ Logread-only\nThe log with no matching events.\n\nCREATING INSTANCES\n<src>new ContractUnknownEventPayload(contract: BaseContract, listener: null | Listener, filter: ContractEventName, log: Log)\n\nMETHODS\n<src>contractUnknownEventPayload.getBlock()⇒ Promise< Block >\nResolves to the block the event occured in.\n\n<src>contractUnknownEventPayload.getTransaction()⇒ Promise< TransactionResponse >\nResolves to the transaction the event occured in.\n\n<src>contractUnknownEventPayload.getTransactionReceipt()⇒ Promise< TransactionReceipt >\nResolves to the transaction receipt the event occured in.\n\ninterface DeferredTopicFilter\nWhen creating a filter using the contract.filters, this is returned.\n\nPROPERTIES\n<src>deferredTopicFilter.fragment⇒ EventFragment\n\nMETHODS\n<src>deferredTopicFilter.getTopicFilter()⇒ Promise< TopicFilter >\n\nclass EventLog\ninherits from Log, LogParams\nAn EventLog contains additional properties parsed from the Log.\n\nPROPERTIES\n<src>eventLog.args⇒ Resultread-only\nThe parsed arguments passed to the event by emit.\n\n<src>eventLog.eventName⇒ stringread-only\nThe name of the event.\n\n<src>eventLog.eventSignature⇒ stringread-only\nThe signature of the event.\n\n<src>eventLog.fragment⇒ EventFragmentread-only\nThe matching event.\n\n<src>eventLog.interface⇒ Interfaceread-only\nThe Contract Interface.\n\ninterface Overrides\nThe overrides for a contract transaction.\n\nclass UndecodedEventLog\ninherits from Log, LogParams\nAn EventLog contains additional properties parsed from the Log.\n\nPROPERTIES\n<src>undecodedEventLog.error⇒ Errorread-only\nThe error encounted when trying to decode the log.\n\ninterface WrappedFallback\nA Fallback or Receive function on a Contract.\n\nMETHODS\n<src>wrappedFallback.estimateGas(overrides?: Omit< TransactionRequest, \"to\" >)⇒ Promise< bigint >\nEstimate the gas to send a transaction to the contract fallback.\nFor non-receive fallback, data may be overridden.\n\n<src>wrappedFallback.populateTransaction(overrides?: Omit< TransactionRequest, \"to\" >)⇒ Promise< ContractTransaction >\nReturns a populated transaction that can be used to perform the fallback method.\nFor non-receive fallback, data may be overridden.\n\n<src>wrappedFallback.send(overrides?: Omit< TransactionRequest, \"to\" >)⇒ Promise< ContractTransactionResponse >\nSend a transaction to the contract fallback.\nFor non-receive fallback, data may be overridden.\n\n<src>wrappedFallback.staticCall(overrides?: Omit< TransactionRequest, \"to\" >)⇒ Promise< string >\nCall the contract fallback and return the result.\nFor non-receive fallback, data may be overridden.\n\n← Constants\nCryptographic Functions→\n\nThe content of this site is licensed under the Creative Commons License. Generated on August 2, 2023, 10:29pm.","tokens":3852,"crawled_at":1791193859177}
+{"id":10300,"url":"https://docs.sui.io/skills","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Sui Agent Skills | Sui Documentation","text":"Skip to main content\n\nInstall any single skill with npx skills add mystenlabs/skills --skill <name>.\nTransactions and dataAccessing Data\nQuery onchain state, subscribe to events, build indexing pipelines, and store blobs with Walrus.\naccessing-dataView on GitHub →\nBuild and deployBuild and Test Move\nCompile Move packages, resolve build errors, and run sui move build.\nsui-build-testView on GitHub →\nMoveComposable Functions\nDesign composable Move APIs with the right visibility, parameter order, and return patterns.\ncomposable-move-functionsView on GitHub →\nOnchain financeDeepBook Margin\nBuild leveraged trading on DeepBook Margin: risk ratios, liquidation mechanics, and the MarginManager lifecycle.\ndeepbook-marginView on GitHub →\nOnchain financeDeepBook Move\nIntegrate DeepBook pools from Move: place orders onchain, create pools, and use flash loans.\ndeepbook-moveView on GitHub →\nOnchain financeDeepBook Overview\nUnderstand DeepBook V3: architecture, integration models, contract addresses, and supported pools.\ndeepbook-overviewView on GitHub →\nOnchain financeDeepBook Predict\nBuild on DeepBook Predict, the expiry-based prediction market protocol. Testnet only.\ndeepbook-predictView on GitHub →\nOnchain financeDeepBook SDK\nTrade on DeepBook from TypeScript with the @mysten/deepbook-v3 SDK: BalanceManager, orders, and swaps.\ndeepbook-sdkView on GitHub →\nFrontend and SDKsFrontend Apps\nBuild browser dApps with dApp Kit, from wallet connection to onchain queries and transaction execution.\nfrontend-appsView on GitHub →\nGet startedGenerate Agent Config\nGenerate a CLAUDE.md or AGENT.md file tailored to your Sui project.\ngenerate-sui-agent-configView on GitHub →\nGet startedInstall Sui\nInstall and manage Sui CLI versions, toolchain components, and network-specific builds with suiup.\nsui-installView on GitHub →\nOnchain financeKiosk\nTrade NFTs and enforce transfer policies with Kiosk, including asset states, purchase flows, and Kiosk Apps.\nkioskView on GitHub →\nMoveModern Move Syntax\nWrite idiomatic Move with 2024 edition syntax: method calls, string literals, vectors, options, and more.\nmodern-move-syntaxView on GitHub →\nMoveMove Project Setup\nSet up Move projects, configure Move.toml and MVR dependencies, and troubleshoot build errors.\nsui-move-projectView on GitHub →\nMoveMove Security\nReview Move code for vulnerabilities: access control, capability handling, invariants, and upgrade governance.\nmove-securityView on GitHub →\nBuild and deployMove Unit Testing\nWrite and structure Move unit tests with proper naming, assertions, context usage, and cleanup.\nmove-unit-testingView on GitHub →\nMoveNaming Conventions\nApply consistent naming to Move structs, constants, events, capabilities, and dynamic field keys.\nnaming-conventionsView on GitHub →\nMoveObject Model\nModel data with Sui objects: ownership types, dynamic fields, collections, wrapping, and transfer rules.\nobject-modelView on GitHub →\nMoveOnchain Randomness\nGenerate random values in Move with the Random object, and secure them against composition and PTB attacks.\nonchain-randomnessView on GitHub →\nTransactions and dataProgrammable Transaction Blocks\nCompose multiple Move calls into a single atomic transaction with gas handling and sponsorship support.\nptbsView on GitHub →\nBuild and deployPublish and Upgrade\nPublish and upgrade Move packages on any network, from localnet testing to multisig mainnet deploys.\nsui-publishView on GitHub →\nOnchain financeSui Bridge\nMove assets between Sui and Ethereum over the native bridge: supported assets, the global limiter, and governance.\nsui-bridgeView on GitHub →\nCLISui Client\nConfigure the Sui client, manage addresses, switch networks, request faucet tokens, and check balances.\nsui-clientView on GitHub →\nGet startedSui for Ethereum Developers\nMap Solidity and EVM patterns onto Move and the Sui object model when migrating from Ethereum.\nsui-for-ethereumView on GitHub →\nMoveSui Move\nWrite and debug Move smart contracts covering abilities, init functions, one-time witnesses, upgrades, and custom coins.\nsui-moveView on GitHub →\nGet startedSui Networks and Gas\nUnderstand Sui network environments, gas costs, epochs, and how the network operates at a high level.\nsui-networks-gasView on GitHub →\nGet startedSui Overview\nLearn what Sui is, how it compares to other chains, and which Sui Stack primitives fit your use case.\nsui-overviewView on GitHub →\nFrontend and SDKsSui SDKs\nPick the right Sui SDK for your language and wire it up: TypeScript, Rust, Python, Go, Dart, Kotlin, or Swift.\nsui-sdksView on GitHub →\nFrontend and SDKsTypeScript SDK for Backends\nBuild backend services and agents on Sui: keypairs, signing, sponsored transactions, executors, and cloud KMS.\nsui-ts-sdk-backendView on GitHub →\nFrontend and SDKsWalrus Sites\nDeploy and manage fully decentralized websites powered by Walrus storage and onchain site objects.\nwalrus-sitesView on GitHub →\nFrontend and SDKsWalrus Sites Portal\nRun a local portal server to browse and test Walrus Sites on testnet.\nwalrus-sites-portalView on GitHub →\nFrontend and SDKsWalrus Sites Publishing\nPublish and update Walrus Sites using the site-builder CLI.\nwalrus-sites-publishingView on GitHub →\nFrontend and SDKszkLogin\nIntegrate OAuth-based, wallet-less login: address derivation, session lifetime, proofs, and security properties.\nzkloginView on GitHub →","tokens":1337,"crawled_at":1791193872229}
+{"id":10301,"url":"https://gov.uniswap.org/t/rfc-uniswap-universal-governance-module/16829","domain":"gov.uniswap.org","chapter":"governance_daos","title":"RFC: Uniswap Universal Governance Module - Requests for Comment - Uniswap Governance","text":"RFC: Uniswap Universal Governance Module\n\nRequests for Comment\n\ntobyshorin\n\nMay 18, 2022, 2:21pm\n\n1\n\nUNI_crosschain_gov1440×880 43.2 KB\n\nIntroduction\n\nA major objective for Uniswap Governance this year is deploying Uniswap v3 on a broad set of high-quality EVM chains. This document explains why the lack of scalable cross-chain governance is currently an impediment to this goal, and proposes we select a bridge technology partner to build a solution. We outline our process for evaluating a vendor and next steps.\n\nContents\n\nCurrent State of Uniswap Cross-Chain Governance\n\nWhat’s Next: Vendor Evaluation, Technical Analysis, Request for Community Feedback\n\nAuthors\n\nLaura Lotti & Toby Shorin (Other Internet)\n\nImage by Yitong Zhong (VectorDAO)\n\nCurrent State of Uniswap Cross-Chain Governance\n\nUniswap V3 is deployed to Polygon, Arbitrum, and Optimism, with Celo, Moonbeam, and Gnosis Chain deploying soon. To enable Ethereum’s Uniswap deployment to govern all instances, each chain must have a messaging bridge for propagating governance decisions from Ethereum L1 to the remote chain’s instance of Uniswap V3 (“cross-chain governance”). Of these 6 deployments, there are 5 different messaging bridges used to execute governance decisions on each of the chains.\n\nPolygon and Optimism use the native bridges developed by the respective teams.\n\nArbitrum also uses its native bridge (currently not functioning).\n\nCelo uses an implementation of Optics.\n\nMoonbeam and Gnosis Chain use Nomad, another forked version of Optics code.\n\nWhat this currently means is that each new proposal containing protocol parameter changes must be rewritten for each separate bridge and project, requiring custom code and separate votes, and potentially multiple proposal processes. In short, managing governance will become cost-prohibitive and complex as Uniswap scales.\n\nWhile the volume of governance that pertains to cross-chain parameters is still low compared to protocols with more on-chain parameters, we anticipate that governance activity will increase in the future. Notably, the addition of further fee tiers specific to different chains, or the activation of pool-specific fee switches, would likely bring an increase in proposal volume.\n\nGeneral Solution Criteria\n\nScaling Uniswap cross-chain governance is a multifaceted problem. Solving it in a “feature-complete” way would require several pieces of work.\n\nThe implementation of a single ABI for and standardized call data format for creating proposals for multiple chains.\n\nThe ability for proposers to deploy their proposal code to selected or all chains in one proposal.\n\nUpdated guides and documentation for proposers.\n\nA graphical user interface for delegates and proposers, reflecting the current state of proposals on each chain.\n\nConversely, what should be “out of scope” for such an initiative?\n\nBridging UNI is out of scope. We are only concerned with bridging governance related contract calls, and for the purposes of this initiative are not considering bridged UNI tokens. Uniswap’s relatively small set of on-chain parameters means reduced attack surface area, and we prefer to keep it that way.\n\nL2 voting is out of scope. The costs of this approach exceed the benefits; Uniswap’s unequal distribution of voting power means that votes are largely contingent on whales and major delegates, even if we make voting for everyone cheaper.\n\nWith these criteria in mind, we felt that an initial project should at least cover items 1, 2, and 3 above.\n\nWe call this the Universal Governance Module (UGM). Below, we explain our process for evaluating potential software vendors to implement the UGM.\n\nVendor Evaluation Process & Technical Analysis\n\nUniswap governance proposal #7 saw Flipside Analytics propose itself as a premiere service provider to Uniswap Protocol, in a move that caused concern and ultimately the retraction of the proposal. University blockchain clubs are often “used” by protocol diplomats and service providers for their delegated voting power without taking an opinionated stance.\n\nTo avoid these failures, we see the need for an independent party like Other Internet to evaluate vendors and nominate one. At the same time, we also want to ensure the process happens with the community’s awareness and acknowledgment.\n\nBelow we list the steps we’ve taken so far and where we are at in the process, along with our evaluation criteria for potential bridge partners.\n\nProcess To Date & Next Steps\n\nWhere we’ve been\n\nWe first identified a need for a universal governance bridge following conversations with recent V3 deployers Gnosis Chain, Moonbeam, and Celo.\n\nWe circulated a short version of this post to several other Uniswap delegates to ascertain support.\n\nWe set up initial exploratory conversations with Abacus, Nomad, and Axelar to validate the technical feasibility of the concept.\n\nWhere we are now\n\nIn this post, we are inviting the community to comment, and suggest additional evaluation criteria or vendors we should be reviewing. Please send us your recommendations within 7 days from this post to allow us to reach out to teams and complete our evaluation in a timely manner.\n\nNext steps\n\nWe will continue to hold conversations with potential vendors in the next 2 weeks.\n\nFollowing the conclusion of these calls, we’ll post the results of our conversations in a competitive analysis table and make a recommendation.\n\nProvider evaluation criteria\n\nWhen evaluating potential bridge providers, several considerations must be taken into account. (Our thanks to Stevie Woofwoof from Osmosis, from whom we’ve adapted a similar list of questions.)\n\nTechnical Features\n\nSecurity\n\nWhat is the security model of the bridge? What compromises does it make?\n\nEase of use\n\nHow developer friendly is the solution? What will the experience be for delegates?\n\nGeneralizable across all chains and L2s\n\nDoes the bridge work across all chains?\n\nCosts (gas)\n\nHow gas-costly is a cross-chain proposal?\n\nMaintenance\n\nWhat is required to maintain the instance? Who will maintain the Uniswap implementation? For how long?\n\nTeam & Contractual Details\n\nReputation\n\nWhat is the reputation of the team? What other projects are using the technology?\n\nRoadmap\n\nWhat is the product roadmap? Can Uniswap influence the roadmap and features?\n\nDeveloper Support\n\nWhat level of customer support will be provided?\n\nTradeoffs & Considerations of UGM\n\nVendor Lock-in\n\nOne possible cause for concern is that enshrining any single bridge provider will lead to vendor lock-in. Why is vendor lock-in problematic? If bridging UNI tokens were planned, the possibility of bridge fees being turned on might be a concern. But there is no plan to do so today.\n\nCryptocurrency discourse often advocates against “platform lock-in,” and such a perspective weights against crowning any single technology provider. But governance UX is no less important than the UX of the native swap application. Were Uniswap Labs itself engaged with governance, they would likely build, acquire, or solicit a bridge provider to develop a universal solution. In their absence, we see it as within our mandate to do the same.\n\nFinally, Uniswap’s importance in the crypto ecosystem and its well-known brand give it significant leverage. Willingness to select a single vendor means we are in a strong position to solicit additional value-add services and long-term arrangements with any given partner.\n\nL2 Native Bridge Security\n\nUsing the native bridges provided by L2s is considered preferable to alternative bridge providers, because A) their security is tied to that of the underlying chain and B) the incentive alignment of L2 teams’ reputation being staked on their chains’ security is thought to lead to better security.\n\nOn the other hand, most new EVM chains have not built their own bridging solution (Solana, Moonbeam, etc) and are already relying on third party bridges. This means we will still see fragmentation of governance bridges without a generalized solution, increasing the complexity of multichain decision making going forward. We believe this weighs toward the use of a single provider.\n\nCommunity Involvement\n\nAt this point in the process, we’d like to get overall feedback from the community on this issue, and any recommendations for additional bridge evaluation criteria we should be using. Please send us your recommendations within 7 days from this post to allow us to reach out to teams and complete our evaluation in a timely manner.\n\nIf you are interested in providing additional technical expertise to our review process, we’re happy to have more collaborators and reviewers on the comparison work. Please reply to this thread or send us a DM at twitter.com/otherinternet__ if you’d like to help.\n\nAdvisors Consulted\n\nSam Hart, Funding Program at Interchain Foundation (Other Internet)\n\nRaf Solari, CTO at Tally (Independent Technical Advisor)\n\nArr00, Engineer at Compound (Independent Technical Advisor)\n\nGetty Hill, Co-founder at GFX Labs (Uniswap Delegate)\n\nRobert Leshner, CEO at Compound Labs (Uniswap Delegate)\n\nMedha Kothari, Analyst, and Jesse Walden, Partner at Variant Fund (Uniswap Delegate, Investor)\n\nLarry Sukernik, Co-founder at Reverie (Uniswap Delegate)\n\nErin Koen, Governance Lead at Avant Garde Finance (Uniswap Delegate)\n\n11 Likes\n\n[Report] The State of Uniswap Governance\n\nCross-Chain Bridge Assessment Process\n\njamico\n\nMay 20, 2022, 8:21pm\n\n2\n\nThanks @tobyshorin. This is an important initiative. Uniswap would certainly benefit from a more standardized solution for cross-chain deployments. And Other Internet (being an excellent steward of the protocol) is well suited to help administer a process like this.\n\nA few thoughts on the proposed structure.\n\n1) Timing. Selecting a bridge provider is an important decision for Uniswap. It’s critical that we allow providers enough time to review the RFP and submit high quality bids. While we appreciate the need for efficiency, the proposed timeline (2 weeks) is realistically too short to accomplish this goal. Let’s align on the overall structure / criteria first and then we can set a timeline that makes sense.\n\n2) Tokenholder consent. While it makes sense for Other Internet to help administer the process, the ultimate decision should be made by the community. In our view a structure whereby: a) Open Internet helps coordinate bids / runs the process; and b) the community selects the ultimate winner strikes the right balance overall. This will ensure that the process remains organized and efficient but also retains broad-based token holder consent.\n\n3) Compound precedent. A useful precedent here is Compound’s recent RFP process. In that case, Reverie ran a competitive process to hire a security auditor for the protocol. The process produced multiple high-quality bids from top audit firms, including Open Zeppelin, Trail of Bits, ChainSecurity, and more. Reverie helped to shepherd the process and allowed the community to evaluate the bids over the course of several weeks (including over community calls, forum posts, etc). After weighing the various proposals, the community collectively voted and picked a winner. Though it had its challenges, this community-led approach led to fair and competitive process that served Compound well in the end. We think something similar makes sense here.\n\nHappy to help coordinate and support.\n\nJeff\n\na16z\n\n9 Likes\n\neek637\n\nMay 24, 2022, 5:55pm\n\n3\n\nThanks for this thoughtful RFC. This is a heady issue, and our opinion at AGF is that is valuable to have one party serving as the fact finders and filter through which we can evaluate potential service providers. There’s still lots of room for community involvement; if anyone has particular technical concerns that a potential provider should answer, they can and certainly should speak up here or reach out to Other Internet.\n\nI anticipate more forum participation after the next post where a comparison table and recommendation has been presented. Given that this is a highly technical RFQ that is sort of defining a category of service in flight, concrete examples of what will be provided and the benefits that will be conferred will be useful for those of us who are wrapping our heads around what the implications of this engagement might be.\n\nUltimately, the community will express its view on whether Other Internet has recommended the right candidate by vote; if the vote is successful we’ve likely saved time and money for many stakeholders (and arguably candidates). If it is not, we have more information about what we’re looking for in this vendor and can be more specific in our asks the next time around.\n\n6 Likes\n\n[RFC] Community Governance Process Changes\n\ntobyshorin\n\nJune 2, 2022, 5:57pm\n\n4\n\nHi all, I’m providing a brief update on where we are with the UGM. As outlined in the original post, we we currently in the process of soliciting formal proposals from multiple bridge technology providers. Once we’ve collected all of them, we’ll post the proposals here with a clear comparison, our analysis and recommendation of a bridge provider, and next steps.\n\nlz.Primo\n\nJuly 16, 2022, 8:16am\n\n5\n\nThanks for drafting this proposal @tobyshorin. It’s great to see Other Internet taking such an active role in the ongoing evolution of Uniswap’s governance.\n\nI’m Bryan, co-founder of LayerZero Labs. The need for a ‘feature complete’ solution to Uniswap’s cross-chain governance is the exact type of problem LayerZero was built to solve.\n\nLayerZero is an open and permissionless Omnichain Interoperability Protocol designed for lightweight message passing across chains. Given our unique generic messaging protocol design, anyone can participate in the network as a Relayer or an Oracle. Our technology provides authentic and guaranteed message delivery with configurable trustlessness; the protocol is implemented as a set of gas-efficient, non-upgradable smart contracts.\n\nIn the last two years, LayerZero:\n\nDeveloped the LayerZero protocol and went live on mainnet 4 months ago\n\nLaunched Stargate, the first fully composable liquidity transport protocol built on top of LayerZero and made possible by the invention of the Delta Algorithm. Stargate became the fastest growing DeFi protocol reaching $4.4B TVL in under two weeks and is the first to solve the bridging trilemma.\n\nCreated Pre-Crime, a proprietary security advancement ensuring application defined invariants are checked before the delivery of each message.\n\nHas spent $3m+ on 15 security audits from top auditors including Quantstamp, Zokyo, Zellic and Trail of Bits; the most recent audits are publicly available on Github\n\nDuring this time, we have built a world-class team of engineers, community managers, and product strategists and earned the support of investors and advisors from FTX, a16z, Sequoia, and Uniswap Labs.\n\nUniversal Governance with LayerZero\n\nCurrently Uniswap is deployed on 6 different chains and employs 5 messaging bridges to execute governance decisions on each chain. As Other Internet described, moving Uniswap to cross-chain governance will require additional developer resources to write and interact with custom interfaces for each chain.\n\nToday, LayerZero is live on 10 mainnet chains including Ethereum, Polygon, Arbitrum, Optimism, BNB Chain, Avalanche, and Fantom and live on 16 testnet chains including Celo, Moonbeam, and Solana among other non-EVM chains.\n\nInstead of rewriting new governance proposals for separate bridges and new chains, integration with LayerZero empowers the Community to write one proposal with zero additional custom code to pass on all active chains. The LayerZero interface was designed for ease-of-use. Implementing a single ABI with standardized call data for creating proposals on multiple chains is as straightforward as implementing a single function type from the enacting contract on source chain; the developer simply writes a send() and receive() function with the passage of a generic bytes array. This enables proposers to deploy their proposal code to selected or all chains in one proposal.\n\nAs the volume of Uniswap governance increases, a lightweight and modular cross-chain solution will be critical for cost efficiency and scaling properties. LayerZero is extremely lightweight and has one of the smallest possible headers (4 fields) and ~100k gas interactions on both send() and receive() with improvement libraries soon to be released which reduce gas to sub 100k.\n\nLayerZero has seen strong developer adoption from 700 contracts live on testnet 3 months ago to over 4100 today. We pride ourselves on the technology’s incredible ease-of-use for both delegates and proposers, transforming a 10 min long process of 40-50 clicks, into 2-3 clicks and reducing a user ordeal of maintaining multiple gas tokens to requiring only source chain gas for cross-chain transactions. LayerZero’s cross-chain governance implementation offers one of the lowest total gas consumed in cost: ~100k gas on source and ~80k on destination including gas for code execution. LayerZero Labs is well-resourced and willing to collaborate with Uniswap Labs to maintain their implementation in perpetuity.\n\nNotably, protocols which integrate with LayerZero own all of their own end bridge contracts. For example, Uniswap would own and have full control over their implementation contracts. From its inception, LayerZero was designed to provide protocols like Uniswap with a unified interface across all chains (both EVM and non-EVM).\n\nThe LayerZero team’s success is tied to the success of our partners. With billions in TVL, billions transferred, and many of the most reputable projects in the world already building on top of our infrastructure, we believe LayerZero should be strongly considered to be the provider enabling Uniswap’s Universal Governance Module.\n\nDedicated Advisory\n\nLayerZero will provide a dedicated team of engineers, an Integration Lead, and our CTO Ryan Zarick to the Uniswap UGM. Ryan will be the primary point of contact for the Uniswap Community and provide complete developer support and full protocol resources to write all contracts and fund multiple full audits from the most trusted auditors in the world. Ryan will also encourage and maintain open and ongoing collaboration with the Community during and after the integration process for cross-chain governance in perpetuity.\n\nUnder the Integration Lead’s guidance, this team of dedicated engineers will implement special projects including the development of a unique graphical user interface for delegates, proposers, and community members monitoring the Uniswap governance process and state across chains.\n\nNext Steps\n\nLayerZero already has full support for generalized message passing and has been consistently used at scale with billions in both TVL and transactional volume since launch. In the next year, LayerZero will go live on 10+ more chains (EVM and non-EVM) and welcomes collaboration with the Uniswap Community on specific roadmap milestones and new feature priorities.\n\nLayerZero has the immediate resources to provide a white-glove developer experience and full integration support and coverage including multiple security audits on all contracts.\n\nWe would love to be considered by the DAO as the single best solution for Uniswap to achieve seamless, secure omni-chain governance and would like to be part of a robust evaluation process run by the DAO.\n\nFor more information on our architecture and implementation, you can dig into our docs here. We look forward to hearing from the Community.\n\n4 Likes\n\nmodong\n\nJuly 20, 2022, 10:04pm\n\n6\n\nThank you for this RFC. This is Mo Dong from Celer. We will post our proposal shortly as part of vendor review process.\n\nmodong\n\nJuly 21, 2022, 6:56am\n\n7\n\nThis is Mo Dong from Celer Network. For some reason, in this forum I cannot post links and graphics which are needed for the proposal. So I am not able to post proposal here. Could forum admin help to fix it?\n\nIn the meantime, here is an url (please remove all spaces) that you can use to access the proposal.\n\ntinyurl. com/ mrcvw98b\n\nhendrikhofstadt\n\nJuly 22, 2022, 2:12pm\n\n8\n\n@tobyshorin, we’re excited to see this proposal live.\n\nAfter examining the RFC by Uniswap and respectfully reading the proposals submitted by others, we’re excited to submit Wormhole’s proposal. The Wormhole team is committed to building out the full solution, commissioning the audits, and providing on-going product and smart contract support to Uniswap.\n\nA quick intro to Wormhole — Wormhole is a leading cross-chain interoperability protocol, allowing generic messaging between 14 (and soon to be many more) heterogenous blockchains. Since launch on mainnet in August 2021, 1.2 million messages have been transmitted. Some are regular messages (e.g. oracle data), some are token bridges, and all of it comes through organic usage — no incentives.\n\nThere are three key reasons why we think Wormhole offers the best solution for Uniswap’s cross-chain governance:\n\nLightweight: For this application Wormhole’s guardian network is only used to attest finalized governance decisions on Ethereum. Wormhole does not depend on any additional complex infrastructure like the operation of a relayer network.\n\nModularity: This relayer-free model makes it easy for Uniswap to expand governance to new chains without reliance on Wormhole to officially roll out its full suite integration. A developer can permissionlessly deploy a read-only contract on the new destination chain and configure them with the current Wormhole guardian set.\n\nCase in point: one of Wormhole’s contributors deployed read-only contract instances for Optimism, Arbitrum, Moonbeam and Gnosis in a few hours over two afternoons. So both L1s can now be included in the Universal Governance Module. (Note: these four chains are in the L1 roadmap for the full suite of integrations in the coming months — more on this below.)\n\nSecurity and Decentralization: Wormhole has nineteen guardians comprised of the leading PoS validators who jointly attest to messages. They all hold equal weight in consensus and governance. Of the 19 guardians, Wormhole requires over two-thirds to reach consensus and pass verification - thus, we assume that at least one-third of our guardian set is honest.\n\nWormhole also has a comprehensive security plan consisting of all development in the open, one of the largest bug bounty programs ($10 million and counting), several quality audits of its full codebase (one by Trail of Bits underway).\n\nTechnical Model\n\nAs a reminder, Uniswap’s goals are twofold: house governance on Ethereum, then message and execute these decisions on both Ethereum and the other supported chains.\n\nAt a high level, governance decisions continue being made on Ethereum using the existing governance tools of Uniswap. These decisions get passed into the Wormhole endpoint on Ethereum, where they get attested by the Wormhole guardian network. These Wormhole-attested messages can then be verified on the respective chains and the decisions be queued for execution.\n\nTo see this in more depth, consider the technical model below:\n\ndiagram941×1018 124 KB\n\nGovernance continues to take place using the existing GovernerBeta contract and Uniswap’s existing UI.\n\nThe GovernerBeta contract feeds into the GovernanceMessenger contract on Ethereum, which serializes the requests and passes them into the Ethereum Wormhole endpoint.\n\nWormhole produces a VAA (verifiable action approval) for this message, which can now be submitted to the GovernanceMessageReceiver contract on the target chain.\n\nThe GovernanceMessageReceiver contract on the target chain verifies the authenticity of the VAA using the local Wormhole endpoint and passes the instruction into a local Timelock contract, which owns the local Factory. Once the Timelock contract is cleared, the instructions can be executed.\n\nNote that a Timelock contract is put on each individual chain to add an optional layer of control over the universal bridge into the system. As an extra signer, the chain’s native bridge could act as an escape hatch by which pending proposals in the Timelock can be canceled.\n\nNotice that there is no relayer dependency in this schematic. Any user can submit the VAA to the GovernanceMessageReceiver contract on the target chain.\n\nThis model is very easy to maintain and enhance. Subject to Uniswap governance approval, receiver contracts can be upgraded over time. Moreover, anyone can deploy the Wormhole receiver contracts on new destination chains to process VAAs without waiting for Wormhole to formally support those chains. Furthermore, Wormhole’s solution is low cost and efficient — the submission and subsequent verification of Wormhole message costs only 11k and 130k gas, respectively.\n\nDetails on how the contract interfaces and message protocol could look like can be seen here.\n\nDeveloper Support\n\nIf this proposal passes, Wormhole will promptly execute on all four asks of Uniswap’s UGM proposal (the first of which is already complete!):\n\nThe implementation of a single ABI for and standardized call data format for creating proposals for multiple chains—We have already prepared a draft on how this message protocol could look like here.\n\nThe ability for proposers to deploy their proposal code to selected or all chains in one proposal—Wormhole’s proposed architecture and protocol design supports this.\n\nUpdated guides and documentation for proposers—Wormhole will curate and actively maintain docs around the added cross-chain governance proposal features and interface.\n\nA graphical user interface for delegates and proposers, reflecting the current state of proposals on each chain—Wormhole will dedicate engineering resources for building a UI that is easy and flexible for delegates, voters, and proposers.\n\nGiven that we have already proposed a clear spec with very lightweight contracts, the smart contract development can be executed promptly following coordinated audits — thus, the UI would be the biggest new lift engineering-wise. With a robust group of contributors that includes engineers, product designers, and smart contract auditors, we are confident our integration will be smooth and seamless. As Director of the Wormhole Foundation and co-founder of Certus One, I will personally manage the effort from start to finish with on-call support from the wider group of 25 engineers.\n\nDecentralization and Security\n\nWormhole relies on a PoA consensus with 19 guardians. Each guardian runs their own node for each chain and holds equal weight in governance and voting. Of the 19 guardians, Wormhole requires more than two-thirds to reach consensus and pass verification - thus, we assume that at least one-third our of guardian set is honest. Our guardians set is comprised of the leading PoS validators with billions in active delegations across the biggest PoS chains — P2P, Chorus One, Everstake, to name a few. However, despite Wormhole’s high degree of decentralization, we remain resolute on improving our trust assumptions — as such, we are placing heavy investments in moving towards a completely trustless system based on zero knowledge proofs.\n\nIn just the last 90-days alone, Wormhole has transmitted 500k messages. Wormhole has handled some of the recent volatile periods in DeFi with ease, facilitating 44k messages in just one day. Our tried and tested protocol has gained the trust of some of the most reputable developers in the space — a number of protocols are currently building cross-chain swaps, DEXs, money market protocols, yield aggregators, wallets, gaming, oracles, perps, launchpads and many more.\n\nFinally, we recognize that Wormhole has earned some press for the hack in February of this year —we believe Wormhole is stronger for it. Wormhole, for instance, has one of the most generous bug bounty programs in crypto—over $10 million and counting—and a series of careful audits. Wormhole will continue along both of these fronts so as to uphold high standards of security for its users and protocols across supported ecosystems.\n\nRelated to this, the Timelock contract is meant to be one final safeguard against an exploit, giving Uniswap valuable time to revoke a hacked message. This serves as an extra failsafe against any smart contract bugs or faulty cross-chain governance proposals.\n\nIndependent from Wormhole Roadmap\n\nWhile Wormhole has thus far reached fourteen destination chains, as diverse as Solana, Avalanche, and Aurora — the governance module we’ve outlined above is freed of dependencies on integrations with the destination chain, message relayers, and all other forms of infrastructure and development. As long as the core Wormhole network can be relied upon to sign the VAAs observed on Ethereum, all other development details can be ignored. And we believe the core Wormhole network can indeed be relied upon for this function, due to its high degree of decentralization.\n\nWe look forward to engaging with the Uniswap community on our proposal.\n\n10 Likes\n\nmodong\n\nJuly 23, 2022, 2:14am\n\n9\n\nCeler Network community would love to submit a proposal to be considered as a solution for UGM.\n\nA quick introduction to Celer:\n\nCeler is a generalized blockchain interoperability protocol enabling a one-click user experience accessing tokens, DeFi, GameFi, NFTs, governance, and more across multiple chains. Developers can build inter-chain-native dApps using the Celer Inter-chain Message (IM) SDK to gain access to efficient liquidity utilization, coherent application logic, and shared states. There are 10+ cross-chain applications live today that are built with Celer IM on various use cases including governance and liquidity protocols. cBridge, an asset bridging application has processed $9.7b transaction volume across 31 chains for 200K users.\n\nUGM with Celer\n\nA UGM solution that is live in production and ready to use\n\nCeler IM based UGM is already live in production with FutureSwap since the end of April 2022. The reference implementation of UGM is very straightforward and we describe the high level flow here based on the application design pattern.\n\nWhen a governance decision is made on Ethereum, the governance contract will call sendMessage of a “send box” contract which takes in the destination chain ids, message to be passed and destination contract addresses. The message will contain the serialized bytes of the governance decision.\n\nThis message will be synced with State Guardian Network, which is a Cosmos SDK based blockchain. Validators in SGN will witness the message and reach consensus on the Cosmos layer that this message indeeded exists and generate a stake-weighted multisignature attestation that is stored on the chain.\n\nA message executor (can be run by Uniswap or run by validators of Celer Network) will collect this message and call executeMessage of a “receive box” contract. After necessary on-chain validation of the message, the message will be eventually relayed to the destination contract.\n\nThe validation, except for the generic checking of the validity of the signatures, also has two security models available to determine when the target contract will receive the message. The first security model is to directly pass the message on and rely fully on PoS security of the Cosmos chain.\n\nHowever, in the case of low-frequency applications like UGM, we recommend using the second security model: an optimistic rollup-like security model. In this security model, every message that is passed onto the destination chain will be first put into a “quarantine zone” for a configurable period of time. During that quarantine period, every single validator in the SGN and the application executor (collectively, App Guardians) can monitor and cross-check the message arrived on the destination chain vs sent on the source chain. If there is any invariant mismatch, the message path will be cut off immediately and the message will not be executed. This changes the security assumption from “trust majority stake” to “trust any” with app developers capable of running one of the “any” App Guardians themselves. This is how FutureSwap implemented their cross-chain governance module.\n\nOnce the quarantine clock times out, the message will be executed by calling a standard interface on the destination governance contract. This will complete the UGM process.\n\nWith the complete walkthrough of the application scenario, we now respond more directly to each of the evaluation criteria in the RFP.\n\nSecurity\n\nAs discussed above, Celer’s generalized message cross-chain solution comes with two security models and we recommend using the optimistic rollup solution here. More context on Celer’s security models:\n\nCeler comes with two security models that each app and users are free to choose from on a per-tx basis.\n\nCosmos-consensus Security Model\n\nBy default, inter-chain dApps rely on the security of the State Guardian Network (a Cosmos Chain) by processing messages routed from another chain without delay. The SGN offers L1-blockchain level security just like Cosmos or Polygon with it being a Proof-of-Stake (PoS) blockchain built on Tendermint with CELR as the staking asset. If a guardian acts maliciously, its staked CELR will be slashed by the consensus protocol. This level of economic security is something that grows with the staked CELR’s value and is simply not available in simple Multi-signature or MPC/PoA-based solutions.\n\nOptimistic-rollup-style delay buffer Security Model (for UGM)\n\n1600×706 130 KB\n\nSo, what happens if more than two thirds (in staked value) of the validators behave maliciously in the State Guardian Network? Although this is highly unlikely given the economical security and distributed nature of the validators in Celer Network, Celer does have a second security model, inspired by the Optimistic Rollup design, that works securely even under this worst-case scenario.\n\nInstead of instantly processing a message routed by the SGN, a two-phase commit-confirm pattern is used to process any inter-chain message. Before any application consumes the message, the message has to be “committed” to the blockchain by SGN into a “quarantine zone” for a period of time. Only after the delay has passed, can this message be “confirmed” and pushed to the final destination application.\n\nDuring this delay buffer, a dApp can run an App Guardian service to double-validate the message on the source chain and check the authenticity of the message committed in the quarantine zone. If the App Guardian detects any inconsistency, it can prevent the message from being processed before the time buffer expires. For application developers who cannot run an App Guardian themselves, they can commission the SGN nodes to undertake the task of an App Guardian. In that case, the security model is strengthened to a trust-any model for the SGN. Therefore, even under the worst-case scenario of the SGN consensus failure, inter-chain dApps built on top of Celer’s construct will still maintain safety property without any concern.\n\nEase of Use\n\nWe estimate that the UGM cross-chain governance solution for Uniswap only requires about 150 LoC to implement the necessary smart contracts. We can provide a full reference implementation that is ready for review by the Uniswap community and security auditing firms. Another example of similar complexity is a full-fledged ERC-721 NFT bridge which has only 250 smart contract LoC.\n\nCeler cBridge is already used by multiple developers for different use cases.\n\nSome other examples below:\n\nChainHop, a composable cross-chain liquidity protocol built on top of Celer Network where users can swap A token on X chain to B token on Y chain with just one click. ChainHop actually integrates Celer Network and Uniswap on all supported chains. You can actually review the source code of ChainHop. This kind of fancy functionality only has less than 1000 loc. Similar use cases are Rubic and Swing.\n\nCeler IM is widely applicable to build inter-chain DeFi applications as well. The decentralized derivatives protocol SynFutures is using Celer’s IM framework to support multi-blockchain futures trading, allowing users to leverage liquidity from any blockchain. Ooki, a powerful and fully decentralized margin trading, borrowing, and lending platform, is leveraging Celer IM to enable fee bridging among all of Ooki’s different blockchain deployments. Aperture, a cross-chain, community-driven marketplace for DeFi strategies, is leveraging Celer IM to enable one-click access to supported strategies for users from any blockchain. Solace, a decentralized insurance protocol that allows users to insure positions for over 180 DeFi protocols with one policy, is also integrating Celer IM for cross-chain insurance functionality. Of course, Celer IM can be used in many other use cases besides DeFi applications. Mystiko Network, the base layer of web3 that provides both connectivity and confidentiality to all blockchain data, transactions and applications, uses Celer IM to enable privacy protection against unwanted cross-chain data tracking and exploits.\n\nGeneralizable across all chains and L2s\n\nCeler currently supports EVM-based chains that Uniswap supports or plans to support including Ethereum, Polygon, Arbitrum, and Optimism, Celo, Moonbeam, and Gnosis Chain. In addition, Celer supports some other EVM chains including Astar, BNB Chain, Avalanche, Fantom, Metis, Oasis Emerald, Evmos, Aurora, Moonriver, Boba Network, OKXChain, Heco, Ape Chain, Clover, Conflux, Crab Smart Chain, Kava EVM Co-Chain, Milkomeda Cardano, Nervos Godwoken, Ontology EVM, PlatON, REI Network, SX Network, Shiden and Swimmer Network.\n\nFor non-EVM based chains, Celer supports Flow blockchain and Cosmwasm chains such as Terra.\n\nSolana is now on testnet.\n\nCosts (gas)\n\nCeler cBridge is highly efficient in gas consumption and has been optimized to do so. For example, the bridging gas costs between Arbitrum to Ethereum using Celer is about half of the official bridge.\n\nMaintenance\n\nWe are happy to provide reference implementation and maintain such implementation in a white-clove service model. There might be some frontend module integration needed that we can closely work with the Uniswap team to complete.\n\nTeam & Contractual Details\n\nCeler was initially founded in 2018 by four computer scientists with PhD degrees from MIT, UCBerkley, Princeton and UIUC with tens of years of industrial experience in networking security, operating systems and large-scale distributed systems. Throughout the long (crypto-term) history of Celer, no security incidents or hacks ever happened in any production software built by the Celer community. Overtime, Celer Network has now attracted many excellent community developers and becomes a decentralized community driven project that is focused on cross-chain interoperability.\n\nCeler is a multi-chain operating system. Through Celer IM, developers can build inter-chain dApps using the Celer Inter-chain Message SDK with efficient liquidity utilization, coherent application logic, and shared states across multiple blockchains. Users of Celer-enabled dApps will enjoy the benefits of a diverse multi-blockchain ecosystem with the simplicity of a single-transaction UX from a single chain. Ultimately, the goal is to have developers using the existing Celer technology to abstract the concept of “multiple blockchain” away.\n\nWe believe Celer community has one of the best developer support processes through our strong network of community developers.\n\nFinally, we thank Uniswap governance bodies for considering our submission to the RFP and we are also happy to discuss any other collaboration here.\n\nOther Resources on Celer:\n\nWebsite: celer.network\n\nDocs for Celer Inter-chain Message: https://im-docs.celer.network/developer/celer-im-overview\n\nGithub: https://github.com/celer-network\n\nSocials: https://linktr.ee/CelerNetwork\n\n1 Like\n\ntobyshorin\n\nJuly 26, 2022, 2:21pm\n\n10\n\nPrimo, Hendrik, Mo:\n\nThank you for these thorough proposals. Please note that you are 2 months past when we requested bridge providers reach out with proposals, per our original forum post. In the intervening period, we’ve obtained other highly competitive proposals, and have conducted an extensive analysis we’re preparing to post.\n\nOf course, security for Uniswap governance is paramount, and we want to ensure that we are taking all options into consideration. For this reason, we’ve decided that we will conduct a 1-week review to compare your offers to the other proposals we’ve received. We’ll post a followup on the forum next week.\n\n1 Like\n\nikram101\n\nJuly 27, 2022, 11:14pm\n\n11\n\nWe at Magpie Protocol have integrated with Wormhole where we utilize their generic message protocol for publishing messages across supported chains, before integrating wormhole we have played around with various cross chain communication protocols that are currently live and choose wormhole for a number of reasons:\n\nIt’s completely free to publish messages through their CoreBridge\n\nYou can send any amount of data just need to generate a payload in bytes type\n\nTheir team has been very helpful in providing support and answering any kind of technical questions we have throughout the integration process\n\nThey are one of the first ones to offer generic messaging and it is battle tested protocol\n\nThey have 19 Guardian nodes responsible to maintain their network, making it most decentralized cross chain messaging protocol as compared to other solutions\n\nWormhole supports non-EVM chains such as Solana along with major EVM chains\n\n3 Likes\n\njamico\n\nJuly 28, 2022, 9:31pm\n\n13\n\nIt’s becoming clear that this process is not serving Uniswap well. Rather than rush to meet an arbitrary deadline, it’s more important that we solicit proposals from the best providers and give them a fair chance to compete. That doesn’t seem to be happening here. It’s also important that the community has the chance to hear these proposals and engage with the providers openly, rather than have the process intermediated behind closed doors.\n\nWe’ve seen public RFPs work well in other communities, including most recently with Osmosis, which selected its own bridge provider via an open competition. Compound also successfully hired an auditor through a public RFP earlier this year. In those cases we’ve seen neutral third parties like Reverie and GFX Labs step forward to administer the process in an open but structured way. We think a similar process would serve Uniswap well here, and propose shifting gears in this direction.\n\nJeff\n\na16z\n\n8 Likes\n\n0xakshay\n\nJuly 29, 2022, 12:40pm\n\n14\n\nHey @jamico , I’m Aksh from the LI.FI team, LI.FI is a cross-chain bridge aggregator that has aggregated most of the bridges that have made proposals here. As an aggregator, we are in touch with most of the bridges in the ecosystem and we treat them all fairly. We don’t have our own bridge nor do we have our own messaging protocol we’re working on. We’d love to be the neutral party here that can facilitate the conversations along with Other Internet.\n\nWhy are we the best to do this?\n\nLike Uniswap, we don’t take any fees from the underlying bridges, thus, we’re unbiased here to begin with. We believe all bridges are needed as we don’t need an optimistic bridge-level security to transfer $3 worth assets. No matter which bridge Uniswap decides to go with, we’ll be getting the same amount of volume from our users who want to bridge UNI token through LI.FI(if UNI is ever bridged across).\n\nWe’re an infrastructure project that uses the underlying bridges and provides the best route to the users. To do this we have to research about all the bridges in the ecosystem and understand the trust/security assumptions of them all, along with their gas efficiencies.\n\nPlease refer to this article by our team here which describes the various trust assumptions of all the different bridges in the ecosystem. In our blog we also have written about the security assumptions of all the bridges we have integrated so far.\n\nNext steps\n\nWe’d love to read all the proposals obtained by @tobyshorin that aren’t in this thread to make a fair, structured and open analysis about all the various bridging solutions for UGM. We are happy to collab with Other Internet here to look into their existing analyses and make this open to the Uniswap community.\n\nHey @tobyshorin, can you please post the existing proposals to Github/Notion or anywhere you feel best and paste the link here? Ty.\n\nLooking forward to collaborating with you to be helpful to the iconic Uniswap protocol :).\n\nAksh\n\ntobyshorin\n\nJuly 29, 2022, 10:12pm\n\n15\n\nHi all, I want to say a couple things on how we’ll move forward.\n\nFirst of all, we’ve taken a deep look at, and are evaluating, the most credible bridge providers in the space. Thank you to Mo, Hendrik, and Primo for sending your proposals. After these three, we are not soliciting any additional proposals at this time.\n\nJeff, want to respond directly to your concerns.\n\nI believe we share the goal of ensuring the best possible outcome for the protocol. As a delegate and champion of Uniswap governance, we have taken the initiative to start this important project and will continue to facilitate it in a way that is respectful of the time of everyone involved. We opened our invitation to bridge projects two months ago, and there has been ample time for both introductions and for bridge providers to reach out and post proposals. In light of the late proposals, we have also extended our timeline an additional week to evaluate these vendors more closely.\n\nAs one of the few Uniswap governance actors with no vested interests in any of the projects involved, we are able to act in the sole interest of the protocol. Our position as an neutral third party has additionally given us the ability to negotiate directly with vendors and ensure that Uniswap Protocol receives a high level of support.\n\nOur mandate as a UGP grant recipient is to perform governance initiatives for the Uniswap protocol, and we will continue to carry out our responsibilities. We have worked closely with fellow delegates and third party technical experts to create a clear set of evaluation criteria, and we aim to deliver a recommendation to the community on the best bridge to move forward with. To clarify, we are not just picking a provider without input. As @eek637 helpfully clarified above, we are making a recommendation that community members and delegates will have the opportunity to express an opinion on through a vote.\n\n3 Likes\n\nTroy_Tsui\n\nAugust 4, 2022, 11:39pm\n\n16\n\nHi all, just giving our 2 cents. We’re from Swim, a liquidity protocol that aims to support a multi-chain world. When building our protocol, we also had to decide upon a solution for our cross-chain communication, and ended up choosing Wormhole.\n\nWhen comparing vendors our most important considerations were security, decentralization, and reliability. In this regard we ranked Wormhole as the clear winner here due to their high quality guardians and secure POS design.\n\nWe have utilized Wormhole’s Portal Bridge to offer users the ability to swap native assets while abstracting away wrapped assets for the user. The Wormhole team has been very helpful from the start, and continue to provide us with a great deal of resources and support as we leverage their innovation to produce innovations of our own.\n\nFor example, Wormhole’s Payload 3 is a core component of Swim’s relayer- the Propeller, which will enable single-click smart contract calls without sacrificing decentralization.\n\nWe couldn’t be happier with our decision to build on Wormhole, whilst sharing with the team the same passion for innovation, decentralization and transparency in the cross-chain space.\n\n4 Likes\n\nlz.Primo\n\nAugust 16, 2022, 3:01am\n\n17\n\nWe’ve really appreciated the incredible outreach from stakeholders in the community looking to learn more about our UGM implementation. Following up with a full proposal to aid thorough evaluation from other teams and delegates:\n\nIntroduction\n\nDue to the inherent security risks of cross chain messaging, the Uniswap Universal Module (UGM) should leverage the most secure cross chain solution that is enabled by the most proficient and qualified technical team. LayerZero has superior security properties to other solutions. Further, LayerZero Labs has demonstrated rigor in designing and parameterizing the highest standard of security required to protect the Uniswap governance process. As such, we respectfully submit that LayerZero Protocol is the singularly credible and secure implementation of the UGM.\n\nLayerZero’s key securities properties are as follows (see Technical Structure for more information). LayerZero is an open and permissionless Omnichain Interoperability Protocol designed for lightweight message passing across chains. Our technology provides authentic and guaranteed message delivery with configurable trustlessness; the protocol is implemented as a set of gas-efficient, non-upgradable smart contracts.\n\nLayerZero is currently live on 10 chains including Ethereum, Polygon, Arbitrum, Optimism, BNB Chain, Avalanche, and Fantom, and on testnet and undergoing audit on 16 chains including Moonbeam, Gnosis Chain, and Solana among other non-EVM chains.\n\nLayerZero Labs has consistently operated with the principle that security is the highest priority. In the last two years, LayerZero Labs:\n\nDeveloped and launched the the LayerZero protocol on mainnet\n\nDeveloped and launched Stargate, the first fully composable liquidity transport protocol, built on top of LayerZero and made possible by the invention of the Delta Algorithm\n\nStargate became the fastest growing DeFi protocol ever, reaching $4.4B TVL in under two weeks\n\nCreated Pre-Crime in response to security failures at major cross-chain protocols, a proprietary security advancement ensuring application-defined invariants are checked before the delivery of each message.\n\nCommissioned $3.5m+ total audits from top auditors including Quantstamp, Zokyo, Zellic and Trail of Bits in the last year alone and are currently on audit #20; the most recent audits are publicly available on Github.\n\nDuring this time, LayerZero Labs has built a world-class team of engineers, community managers, and product strategists and earned the support of investors and advisors including FTX, a16z, Sequoia, and Uniswap Labs. LayerZero remains the only battle-tested major cross-chain communications provider to never be hacked and is trusted by the top protocols and dApps across DeFi, NFT infrastructure, and gaming.\n\nTechnical Structure\n\nLayerZero is a lightweight universal messaging interface that allows developers to seamlessly interact with contracts across dozens of blockchains. LayerZero Endpoints rely on an innovative architecture to trustlessly relay messages between chains.\n\n1600×900 36.2 KB\n\n(Above: Communication flow in a single LayerZero cross-chain transaction)\n\nIn a single call, paying only source gas, users can send a message (or a bundle of messages) to contracts on any supported chain. Thus, users are able to create a single contract that is capable of interacting simultaneously across multiple chains via our messaging primitive.\n\nLayerZero achieves this in a secure and decentralized manner by using a Relayer and Oracle architecture. From a decentralization and security perspective, this model never moves information through middle-chains. With no transport chain dependencies or reliance on disparate validation methods, users can be confident in the authenticity of cross-chain messages and transactions.\n\nPer the RFC, Uniswap governance will continue to be housed on Ethereum and via a single contract, messages are sent simultaneously from the LayerZero endpoint on Ethereum to endpoints on Polygon, Optimism, Arbitrum, and any other future deployed chain.\n\nDesign and Implementation Advantages\n\nAs described below, LayerZero offers an unmatched combination of security, efficiency, and application-specific configurability for the UGM. Competing protocols offer some of these advantages but none offer all of them simultaneously.\n\nIndependence & Application Specific Upgrades\n\nLayerZero enables Uniswap to commit to application-specific feature upgrades. The importance of this capability cannot be understated. Generalized upgradeability has led to hundreds of millions in losses! Most smart contracts used in competing cross-chain solutions are upgradable. As a result, it doesn’t matter how secure their infrastructure is, if a protocol is updated to add a new feature and there’s a bug in the update, every other application that interacts with the smart contract is automatically exposed to new smart contract risk. There is no way for applications to reject these upgrades. This vulnerability due to upgradeable smart contract design is inherent to every other competing cross-chain provider and is exemplified by the recent Nomad hack.\n\nLayerZero uses immutable contracts with a novel opt-in validation library upgrade system that gives any application the choice to either accept or reject any or all future LayerZero protocol enhancements. It is impossible for LayerZero Labs or any multisig process to force changes to a Uniswap integration once it’s established. Applications with high security standards have the choice to accept protocol enhancements or not.\n\nFor example, LayerZero could add libraries to support ZK-rollups, optimistic roll ups, or gas optimization to enhance core protocol functionality. Uniswap can choose to not accept such library upgrades or selectively upgrade depending on governance belief in new best practices in security or industry research at the community’s discretion. Our team’s belief is that current security practices should not and will not be the industry best practices 10 years from now. As researchers move the industry forward, so should the security model of cross-chain infrastructure. LayerZero’s opt-in validation library empowers applications to evolve with cutting-edge research and industry best practices.\n\nAs evidenced by the recent surge of bridge exploits and more than one billion dollars of value lost, application-specific feature upgrades are essential for Uniswap’s UGM. This feature prevents human error in future protocol upgrades that risk affecting every integrated application by default, and prevents attacks from the entity pushing the upgrade, regardless of the security of their off-chain infrastructure.\n\nLayerZero is the only generic messaging protocol that puts the power and ability to control the development of Uniswap’s omnichain functionality back in the hands of the Uniswap protocol - where it belongs.\n\nSecurity Model\n\nLayerZero’s Oracle and Relayer systems lead to the best possible security outcomes for end users. Specific to cross-chain governance, competing middle-chain bridge designs can be censored by malicious actors looking to tamper with a vote or governance proposal. If a malicious actor takes control of the middle-chain they can reorder, choose not to deliver specific messages sent across chains, or fraudulently attest to any decision therefore completely rigging any governance vote.\n\nLayerZero’s bifurcated Oracle-Relayer security model ensures that either every message is censored or none are, rendering message censoring unattractive for malicious actors. Oracles and Relayers cannot censor messages without censoring all messages due to the sequential nonce ordered enforcement on the receiving chain. As a result, if an attacker obtained control of the Oracle and Relayer, and succeeded in censoring a message, every subsequent message would also be censored and the vote would stop. No hard stop would occur and Uniswap could expediently resolve the issue. Uniswap would simply select a new Oracle or Relayer and messaging would resume. This bifurcated model prevents effective collusion amongst potential malicious actors and ensures the ongoing operation of governance.\n\nIn addition to our built-in security model, LayerZero leads the industry in cross-chain security with Pre-Crime, a proprietary module which launched in April and currently secures Stargate. In fact, the Wormhole/Jump team recommended two major security updates in a recent blog post: Reconciliation / Global Accounting and Emergency Shutdown. Pre-Crime was built to address these issues and can be used to verify that all votes cast on Ethereum are not double counted on other chains.\n\nFor Uniswap cross-chain governance, infallible on-chain votes and results are critical to protect the integrity of any changes that are pushed to the Uniswap code base.\n\nOmnichain Governance Module\n\nCross-chain governance is a complex challenge to address as it requires preserving a seamless, unified UX. LayerZero the earliest integration partner to enable cross-chain governance for one of the largest DeFi protocols (soon-to-be announced).\n\nFrom this custom development, we have designed the Omnichain Governance Module, a framework for out-of-the-box cross-chain governance which enables easy implementation of a simple, cost-effective solution attuned to governance-specific needs around accuracy, consistency, and lightweight engineering. Our module offers an optional time-lock function which acts as a backstop for decisions in case of malicious activity.\n\nImmutability & Customization\n\nIn addition to the security benefits described above, LayerZero underlying design is a series of immutable (i.e., non-upgradeable) smart contracts. This immutability is critical in infrastructure design as the attack surface becomes exponentially larger when cross-chain contracts are upgradeable and universal. This has become increasingly evident in the spate of recent cross-chain bridge exploits. Unfortunately, every competing proposal on this thread is predicated on a structure with entirely upgradeable contracts.\n\nLayerZero offers what no other cross-chain solution can: control over security parameters at the application layer. When using our Omnichain Governance Module, Uniswap has the ability to configure off-chain infrastructure, block confirmation parameters, and Oracle/Relayer selection. Uniswap governance is never forced to opt-in to any permanent off-chain infrastructure configuration and has the ability to change parameters at will for security and user-experience purposes among others. The unique ability to deploy different Oracle, Relayer, and infrastructure configurations allows users to optimize for both cost and trustlessness. For example, Uniswap can choose to run one of the entities (Oracle or Relayer) as a group of major UNI token holders, further decentralizing their governance and endowing the most incentivized members of the community with partial ownership of security.\n\nUniswap governance decisions and upgrade calls should not be locked into the same security parameters that apply to low-value token transfers. We view the ability to own security parameters at the governance level to be mission critical for major protocols and DAOs.\n\nEfficiency & Cost\n\nLayerZero was designed and built with efficiency as a first principle cost where other solutions have high transaction costs. As the volume of Uniswap governance increases, a lightweight and modular cross-chain solution will be critical for scaling. LayerZero messages are extremely lightweight and have one of the smallest possible headers today. Four fields and ~100k gas interactions on both send() and receive() functions are already deployed with upcoming opt-in libraries set to reduce gas consumption to sub-100k.\n\nLayerZero is capable of both singular and batched cross-chain communication. By combining batched transactions with the most efficient messaging primitive, LayerZero allows Uniswap to house core governance on Ethereum and push decisions to all relevant chains at the lowest possible cost.\n\nImplementation Support\n\nLayerZero Labs is well-resourced and fully prepared to support the entire Omnichain Governance Module implementation process from start to finish including commissioning of multiple audits and providing on-going product and smart contract support to Uniswap.\n\nOur technology is ready to be implemented and is fully developed as an out-of-the-box solution. We have developed a thorough UGM support plan and will provide:\n\nFull-funded access to our 3 retained audit firms\n\nLayerZero is currently on audit #20 and has allocated more capital to security audits than all competing cross-chain providers combined\n\nUp to $15M bounty – the largest ever security bug bounty\n\nAll engineering requirements and ongoing integration support\n\nGuarantee of deployment to any additional chain for Uniswap governance within 2 weeks of request\n\nA dedicated advisory and implementation team\n\nLayerZero Labs will provide a dedicated team of engineers, an Integration Lead, and our CTO Ryan Zarick to the Uniswap UGM. Ryan will be the primary point of contact for the Uniswap Community and provide complete developer support and full protocol resources to write all contracts and fund multiple full audits from the most trusted auditors in the world. Ryan will also encourage and maintain open and ongoing collaboration with the Community during and after the integration process for cross-chain governance in perpetuity.\n\nUnder the Lead’s guidance, this team of dedicated engineers will implement special projects including the development of a unique graphical user interface for delegates, proposers, and community members to monitor the Uniswap governance process and state across chains.\n\nConclusion\n\nWe respectfully submit that for the reasons outlined above, LayerZero offers the greatest security properties and the singularly credible solution for the UGM RFC. LayerZero Labs has a degree of commitment to security that is unmatched in the space; the team has already implemented a full solution for cross-chain governance and would bring this expertise to the UGM. Should this proposal pass, LayerZero will begin implementation immediately.\n\n5 Likes\n\ntobyshorin\n\nSeptember 2, 2022, 4:03pm\n\n18\n\nUniswap Crosschain Governance: Bridge Findings & Recommendation\n\nAuthors\n\nLaura Lotti & Toby Shorin, Other Internet\n\nIn our May RFC post, we discussed the need for cross-chain governance as a strategic priority for Uniswap’s expansion to become the premier DEX choice on every chain. We indicated our intention to select a technology and team to work with on building out Uniswap’s cross-chain governance tech, and described a set of criteria against which we would be evaluating vendors.\n\nIn this post, we’ll recap our process and discuss Uniswap governance security considerations before delving into our evaluation of teams and describe next steps for moving the cross-chain governance project forward.\n\nOur findings can be summarized as follows:\n\nOptimistic rollup-like solutions provide the most promising tradeoffs for the use case of cross-chain governance.\n\nThe two bridges that adopt this model, Celer and Nomad, have comparable security models.\n\nOur final recommendation is to not adopt a universal bridge solution at this stage. Instead, we propose that other chains who wish to deploy Uniswap use only optimistic systems.\n\nProcess\n\nFirst, a note about our process. Before beginning this work, we took stock of different models for vendor procurement and evaluation.\n\nFirst, we’ve personally seen that governance communities of protocols can be overwhelmed by third parties posting “proposals” that are really service arrangements. The “proposals” to create Uniswap and Gitcoin branded stablecoins by the Ichi team are straightforward examples. Because they are framed as governance initiatives to the “community,” they seem to come with a certain necessity of serious evaluation, even if they are totally unaligned with strategic priorities. This tendency in DAO governance indicates a need for more strategic direction setting and initiatives on behalf of the protocol by more informed advocates.\n\nSecondly, we looked at public vendor evaluation processes pursued by some protocols and were left unimpressed. Two relevant case studies were Compound governance’s selection of an ongoing audit firm, and Osmosis’s selection of a bridge partner. In the case of Compound, a firm was solicited and even went to an initial vote before other audit firms had the opportunity to post their proposals. The vote had to be delayed, and unpleasant accusations were made between firms in the forums. Additionally, the fully open nature of the process led to the competing audit firms price matching the original proposal. While Compound governance generally has more engaged technical and strategic leadership than Uniswap’s, we again viewed this messy process as evidence for more direct solicitation and overt leadership.\n\nIn the case of Osmosis, the Osmosis Labs team conducted an initial review of different vendors in private, then published a ranked list of the team’s top choices, before moving to a ranked-choice governance vote. The team also conducted a live video interview with different bridge teams. While we believe the expert-led process is an improvement over Compound, the addition of the ranked-choice vote led to accusations of “governance theater” and a sense among the competing vendors that the process was rigged.\n\nWith this in mind, we wanted to be clear about our process up front. It would be expert-led, conducted by a party with the ability to negotiate and legally contract with the bridge team, and would result in a single recommendation for the community’s consideration. This is a new experiment in procurement process for Uniswap governance.\n\nWhat Happened Next\n\nWe made an initial post on the forum soliciting direct outreach from bridge providers. We received interest from Axelar and already had a contact with Nomad, and we were referred to Abacus.\n\nAfter initial conversations with these teams, we prepared a brief ( UUGM Partner Brief) which we sent to Axelar and Nomad. This brief outlined our expectations for the partner’s commitment — essentially what would be in a legal agreement and scope of work. We asked the Nomad and Axelar teams to prepare proposals based on this brief. The two teams returned proposals.\n\nIn the meantime, we consulted with several independent technical leaders and Uniswap delegates in the space to get outsider opinions. In no particular order, we spoke with Medhi Kothari (Variant research team), Rafael Solari (CTO Tally), arr00 (engineer at Compound, designer of Governor Bravo), Noah Zinsmeister (engineering lead at Uniswap Labs), and Leighton Cusack (CEO of PoolTogether). Following this, we started to compile and prepare our recommendation.\n\nAs we were preparing our post, we also began to discuss our findings with delegates. Some of these conversations led to other bridges posting proposals on the public forum—namely, Wormhole, Celer, and LayerZero. While this was not our original intent, we decided to look more deeply into these models, and pushed out our recommendation post until we conducted a more thorough evaluation. We engaged Sam Hart and Rick Dudley as technical advisors to assist with this second run. Bridge security is the main issue of importance, so for the sake of thoroughness, we decided we should push through with evaluating players who were previously not in the consideration set.\n\nIn the next section we describe Uniswap-specific security considerations, then provide a security overview of the bridges. Ultimately we provide our recommendation and takeaways from the process.\n\nUniswap governance security considerations\n\nGovernable parameters are owned by contracts which will accept governance commands through the bridge messaging channels. Therefore we must understand which risks are specific to Uniswap governance, and how the use of a bridge would change the risk profile associated with these various parameters. In general, Uniswap has very few on-chain parameters.\n\nIt is important to remember here that bridging tokens is entirely out of scope for this project; we are only discussing cross-chain message passing.\n\nTreasury disbursement attacks. In the specific case of Uniswap governance, a bridge would be an intermediary attack surface if funds were custodied on a different chain than the treasury on Ethereum L1. Today this is not the case. However, with recent fee switch discussions, it is possible that in the future fees on other networks or chains could be activated. This would introduce an attack vector of messages disbursing accrued fees to an attacker, or attacks maliciously attempting to bridge the tokens off the chain. This is especially a risk in the case of bridges that allow passed messages to be updated by external validators or multisig signers. We would advocate against activating protocol fees on other networks until this scenario is given a more comprehensive evaluation.\n\nFee based attacks. The owner of the Uniswap V3 factory contract on L1 is the governance timelock; on L2, it is a contract controlled by the L1 timelock via a bridge. One possible form of governance attack is an invalid message sent to the bridge set this L2 fee switch while setting the address to another owner. This is one of the only clear attack surfaces native to Uniswap’s current governance parameters.\n\nGriefing or DOS attacks. Denial of service attacks are possible on validator bridges (requiring 1/3 validators to halt the chain) and optimistic bridges (a malicious agent submits a fraudulent message, disabling the bridge). Given the time-insensitive nature of most governance votes, we do not consider this a significant risk. In optimistic systems, liveness of the fraud proof detection agents is another consideration; we discuss this more later.\n\nAdditionally, optimistic interoperability arguably introduces one more attack vector:\n\nLatency-based arbitrage opportunities. The the 30 minute “challenge period” or “quarantine” used by Nomad and Celer introduces an opportunity for trades based on governance-related information before execution. However, most information related to governance votes will be available for weeks leading up to the on-chain vote and therefore already reflected in the market state. This is a low risk.\n\nProjects review\n\nWe initially talked to 3 teams: Abacus, Axelar and Nomad. Given the early stages of development of the first (discussed below), we focused our evaluation on Nomad and Axelar. After a couple introductory calls, we provided both of these teams with a brief and requested that each team respond with a proposal and scope of work, including timeline for the scoped work and budget.\n\nBoth teams responded with details on their proposed implementations, which we include below (please find here Axelar‘s and Nomad‘s original submissions). Other teams’ submissions can be found on the thread above. We review all bridge models below.\n\nAxelar\n\nAxelar Network is a validator-run bridge based on the Cosmos SDK and enjoys similar PoS liveness and security guarantees (67% corruption threshold). The bridge is maintained by a network of validators incentivized by the AXL token. As part of consensus, validators run light-client software of other blockchains, allowing them to verify their state. The validators collectively maintain threshold signature accounts on other blockchains, which allows them to lock and unlock assets and state across chains and to post state on other blockchains. This way Axelar acts as “a “decentralized crosschain read/write oracle”, as per their white paper.\n\nAmong the externally verified bridges we talked to, Axelar is is the most resilient one with the largest validator set (currently 45, and aiming for 100). While it offers much higher security guarantees than other validator bridges, it still relies on a honest majority to correctly verify updates (in this case 2/3).\n\nAxelar already connects several chains including Ethereum, Cosmos, Avalanche and more, and it’s recently been selected as canonical bridge by Osmosis. The project is co-founded by Sergey Gorbunov and Georgios Vlachos who have an impressive academic background in cryptography and were founding team members at Algorand. The project has been audited by Ackeeblockchain, Cure53, NCC, Oak Security, and Commonprefix Labs.\n\nOn the other hand, Axelar primarily facilitates cross-chain token transfers and they do not have a cross-chain governance application in active development. For the realization of a cross-chain governance technology for Uniswap and updating current deployments, they budgeted $250k excluding smart contract audits and cross-chain front end application, that they would scope separately.\n\nNomad\n\nNomad leverages optimistic verification, a novel interoperability model developed by engineers on the Nomad core team while at cLabs. Contrary to externally verified bridges, Nomad’s optimistic verification only requires “1 of n” honest parties (Watchers) in the system to submit a fraud proof during a 30 minute window.\n\nOne of the key features of optimistic verification discussed in depth below is its revocation-centric approach. Nomad splits responsibilities between two classes of agents, Updaters that can verify cross-chain messages, and Watchers that can revoke permission to said messages (that is, they can block messages but cannot themselves permit messages to be sent cross-chain). This means that even if all Watcher keys in Nomad are compromised and collude with the Updater, as long as the honest Watcher has a backup key, they may always prevent fraud in Nomad.\n\nNomad is currently free to use, beyond Ethereum transaction fees, and is the main operator of its Watcher set, but they are in the process of expanding their Watcher network to reputable partners such as Circles and Moonbeam Foundation, and are considering incentives for operators of Watcher agents in the future. Each application that is deployed using Nomad has the choice of utilizing an existing Watcher set or configuring their own Watcher set. An application will always have the option of migrating to its own Watcher set at any point in the future. The contracts have been audited by Quantstamp.\n\nNomad has partnered with Moonbeam, Gnosis Guild (Nomad Zodiac module), and with Tally and DAOhaus for frontend integrations, which would facilitate cross-chain proposal creation frontend development for Uniswap. Additionally, two Uniswap deployments already use Nomad (Moonbeam and Gnosis Chain). Nomad’s team has also been deeply involved in the development of EIP-5164, which ensures that any future upgrades to UUGM will be done in accordance to the cross-chain governance standards developed for Ethereum.\n\nAs we were preparing this post in early August, the Nomad bridge was exploited and drained of funds. The issue was due to a smart contract error in the Replica contract that allowed multiple attackers to send invalid transactions as valid across chains hitting the liquidity of several exchanges, primarily Moonbeam, EVMOS and Milkomeda. Important to note that the optimistic model here didn’t fail, it was a transaction verification that failed; an issue that was already pointed out as “low risk” by the Quantstamp audit and wasn’t addressed by the team. Since then the team put out an open call to the hackers to return the funds. We are waiting on a more substantial response by the team on how they intend to address the loss.\n\nWormhole\n\nWormhole is a multisig bridge with 19 guardians (signers). Guardians include some of the largest staking and validation companies, including Chorus, FTX, and P2P Validator. Wormhole has an optional per-message fee, currently set to 0 on most chains.\n\nWhile multisig oracle bridges are the most widely used trust model for message passing and token bridging, they have the weakest security assumptions. The Horizon bridge (9 multisig) was compromised earlier this year, while the Ronin validator bridge was exploited in a similar way. Wormhole’s significant hack this year was not a compromise of the guardian private keys, but an exploit of its core Solana contract (read more about this here). Jump Trading, the main investor and contributor to Wormhole, covered the over $300mm loss; however the fact that the project relies on a single entity for its source of funding raises concerns over its long term commitment to decentralization.\n\nAn issue with multisig bridges in general is that validators may modify messages in the queue. While a 2/3 compromise of validators is unlikely, modification of messages is a primary risk for cross-chain governance.\n\nWormhole will soon launch a Cosmos appchain, which will act as the governance chain for Wormhole and as an additional security measure. This “accounting chain” aims to provide a check on smart contract balances when calls to move assets have been made. This is an interesting development for token bridging, but is not relevant to the governance message passing use case.\n\nWormhole stresses its large team, its internal penetration testing unit, and its security credentials in. Wormhole also touts its significant bug bounty program of $10mm. While we are impressed with the team’s professionalism, we feel as if Jump itself is the ultimate point of failure for Wormhole, beyond the security model itself. Wormhole has been audited by firms Neodyme and Kudelski, with more reputable Trail of Bits and Certik to release their own audits in 2022.\n\nLayer Zero\n\nThe architecture of Layer Zero’s trust model is a separation between relayers and oracles. Oracles transmit messages from the origin chain to the destination chain, and relayers submit a proof that the message is a valid message emitted by the origin. The oracle and relayer must be separate entities; this separation of roles means that collusion between parties would be required for a message to be altered. As there are no guarantees against collusion between oracle and relayer parties, the decentralization and trust model of the relayer and oracles themselves become paramount.\n\nUsers of L0 have the ability to specify their own oracles and relayers. In other words, L0 is not properly bridge technology; it is a message passing system with an agnostic transport and security layer beneath—essentially, an infrastructure for bridges to be built on top. However, L0 does have a default configuration: the Oracle service is provided by a TSS of FTX, Polygon, and Sequoia, and L0 runs a proprietary relayer. This gives Uniswap two options for utilizing Layer Zero: use the default configuration, or build out its own network of oracles and relayers.\n\nGiven the current state of Uniswap governance, it’s unrealistic for Uniswap to be rolling its own bridge on L0. This leaves us with the default config. While the 3 default oracles are reputable organizations, L0 hasn’t published any information on the security models of those oracles. Likewise, L0 is rather light on information about the specific security model of its own relayers. One published document details a “PreCrime” function for relayers to check against specific end-user defined invalid states.\n\nProvided that L0’s own relayer is secure, Layer Zero inherits the security of the oracles, about which not much is known. Insufficient security information on the default configuration makes Layer Zero an unsure bet for Uniswap governance.\n\nCeler\n\nThe basis of the Celer’s cross-chain messaging solution is the “State Guardian Network.” Similar to Axelar or other validator bridges, this is a Tendermint delegated POS chain. 21 State Guardians, the validator nodes, stake $CELR to operate. When a cross-chain message is sent to a message bus, validators generate stake-weighted attestations to the message’s valid existence on the origin chain. The SGN charges a message passing fee, prorated by message length.\n\nCeler provides an additional security model which can be selectively enabled for higher-risk, higher value messages. This is a fraud proof model based on the design of optimistic rollups, similar to Nomad’s design. The fraud proof “App Guardian” agents are intended to be run by end application developers; but they are also part of the validator State Guardian software package, meaning any of the 21 validators may be engaged as an app guardian. Presumably, Uniswap governance would be using the optimistic model exclusively.\n\nAs the fraud proof network is a different security model, there is not a need to separate the agents, as in the Layer Zero design. Finally, while end users can specify which transactions use the fraud proof network instead of the validator bridge, the Celer team’s care for operational security is evident in their addition of guarantees that asset transfers in the 90th percentile in size automatically are sent to the fraud proof network. Celer’s contracts are non-upgradeable, but certain parameters such as the fraud proof submission window may be specified by end users. The State Guardian Network system has been audited by Certik, SlowMist, and PeckShield. It’s unclear whether the fraud proof network has been audited.\n\nAbacus\n\nAbacus is another recently-launched POS bridge with a team of senior blockchain architects. The basic security model is similar to other validator bridges, but offers additional security guarantees by allowing applications to specify their own set of additional validators.\n\nAbacus is still a very new project, having only deployed to mainnet in the last few months and still unaudited. Additionally it currently runs only a proof of authority (POA) network, and is planning to migrate to POS later this year.\n\nA number of the largest bridge exploits in the last year have been of more centralized bridges, which gives us pause about a POA system in the short term. In addition to the relatively untested nature of the protocol the obvious size of commitment that would be required from the early-stage Abacus team to build technology for Uniswap, we were dissuaded from pursuing further talks with Abacus, but we look forward to seeing their POS network come online.\n\nEvaluation\n\nFollowing our evaluation and review of the competitive bridge providers, we came to the opinion that Uniswap should enforce strong criteria when choosing a base security model. While a message passing bears less risks than fund transfers, we think it’s paramount to choose the security model that is most protective for the governance use case. For cross-chain governance safety is crucial; on the other hand liveness issues can be tolerated to an extent (i.e. slow messages) because of the long timeframes of governance decisions.\n\nIn particular:\n\nSafety over liveness. Slow messages can be tolerated by governance, but the possibility of message manipulation by relayers should not.\n\nCost and efficiency. Securing the bridge should not require an unrealistic level of technical buildout the Uniswap community.\n\nCriterion 1 eliminates multisig and validator-based solutions from the consideration set; criterion 2 indicates we should not consider light client relays, which are complex and not yet available for all chains. In light of the security tradeoffs that these models make, we think optimistic interoperability is the most promising option for Uniswap.\n\nThe optimistic model relies on a new set of agents that are in charge of detecting invalid messages. Any one actor submitting a fraud proof shuts down the channel, superseding the “honest majority” assumption of multisig and validator bridges with a “1-of-N honest parties.” Compared to native verification, where each chain runs a light client of the other chain, optimistic verification also has the advantage of being extensible and reusable across chains at lower costs.\n\nIn the following segment we give a deeper look at Nomad and Celer, the two organizations that enable optimistic bridging today.\n\nOptimistic Bridging Deep Dive\n\nIn this section, we’ll explain Nomad and Celer’s optimistic rollup-inspired security models in more depth. In plain language, the basis of this model is fraud proof submission. Instead of “pessimistically” assuming that each message needs to be verified at the origin, messages are “optimistically” signed on the origin chain, and a dispute window is enforced at the destination, where some agents and veto any fraudulent message.\n\nNomad Message Flow Overview\n\nA message intended for a cross-chain destination is sent to the Home contract on the origin chain (Ethereum).\n\nThe Updater, an offchain agent, observes these messages and sign attestations to their validity, then publish new merkle roots as an update to the home contract state.\n\nRelayer agents relay updated state to Replica contracts on destination chains.\n\nNomad protocol enforces a 30-minute dispute window in which Watcher agents can submit fraud proofs. If fraud is detected, the channel is shut down.\n\nIf the message is valid, it is executed on the destination chains.\n\nOptimistic systems have a parsimonious definition of “fraud.” In the case of Nomad, “fraud” deals exclusively with the Updater. The Updater may A) have signed two conflicting messages, or B) having signed a message which did not exist in the queue of roots awaiting publication.\n\nCeler Message Flow Overview\n\nA governance proposer constructs a message for a new contract, the Uniswap dApp Plugin contract. The message is sent to the messaging bus and then to the State Guardian Network chain.\n\nSGN validators reach consensus and create an attestation as to the message’s valid existence.\n\nA 30 minute dispute period is enforced, during which App Guardian agents check the message against events submitted to the message bus on the origin chain. If fraud is detected, the channel is shut down.\n\nIf the message is valid, it is relayed by the Executor to the destination chain and submitted.\n\nWho Runs Agents?\n\nNomad\n\nNomad currently operates the Updater agent. In addition, Nomad maintains a set of Watchers, similar to Optimism’s centralized sequencer. Nomad is currently decentralizing the Watcher set to other reputable parties, such as Circle, the issuer of USDC, and the Moonbeam Foundation. These additional Watchers were estimated to begin operations during the summer; this timeline has been pushed out because of the exploit.\n\nDecentralization of the Updater agent is a stated goal of Nomad’s. In various interviews and documentation, they have cited the intention to introduce both economic incentives for Updater uptime, and staking & slashing model to punish fraudulent activity. Note QSP-33 in Quantstamp’s audit of Nomad recommends this step be taken as well.\n\nCeler\n\nThe State Guardian Network of validators monitor messages sent to the origin chain message bus and reach consensus on that message’s existence, generating a typical stake-weighted multi-signature attestation.\n\n“Executor” agents relay attested messages to the destination chain and have the ability to be “App Guardians.” These are trustless entities that cannot fabricate messages. Celer recommends that these agents are run by app developers / Uniswap community members, but the SGN also runs these agents as part of the software package. Celer claims that the App Guardian logic is isolated from the SGN logic; we haven’t been able to confirm this in a cursory GitHub review, and would appreciate a larger smart contract audit.\n\nOne difference between Celer and Nomad’s security systems is whether information about fraud is transmitted back to the origin chain. Nomad sends data back to the origin chain so that fraudulent updater agents can be slashed; with Celer, fraud proofs submitted by App Guardians are not subject to the same slashing-based disincentives for the SGN.\n\nIn both the Nomad and Celer case, it would behoove the Uniswap community to run a Watcher or App Guardian agent to increase security, in addition to other parties running watchers. While overall cost is one of our main criteria, engaging a trusted partner to run an agent would be the most effective path forward. Uniswap Grants Program previously provided grants to the crypto development agency Scopelift; they are our top pick for an organization we would engage for the dev ops work involved.\n\nLiveness Issues\n\nOptimistic inspired systems turn liveness into a security property. Nomad has incentives for Updater liveness on the roadmap; for Watchers, the basic incentive is for app developers to run Watchers to secure their own system. Celer has arguably stronger liveness-protecting properties, as App Guardian liveness is provided for by needing to run the underlying validator network.\n\nRecommendation & Next Steps\n\nOptimistic verification is the most suited model for cross-chain governance on Uniswap. The balance of costs (running a fraud detection agent) and security guarantees (no message alteration, trust 1-of-any) are the correct tradeoffs to make for a model.\n\nBefore the recent Nomad exploit, we were prepared to publish these findings recommending Nomad. Before and following the hack, we’ve also had several conversations with Celer, and think they are an equally strong option.\n\nThe Nomad team has been working explicitly on cross-chain governance longer than any other of the teams we’ve interviewed. Furthermore they are deeply familiar with the Uniswap ecosystem, having proactively conducted their own analysis of the state of Uniswap crosschain governance and published the only complete documentation of xchain governance of the protocol. The level of support was an important criteria in evaluation, and the Nomad team’s work here demonstrates that commitment.\n\nWhile Nomad does not have as large of a pool of Watchers as Celer does with all validators engaged to run App Guardians, there are some benefits to Nomad’s model. Nomad’s optimistic interoperability is more of a “true” optimistic model in that fraud proofs are submitted back to the origin chain. Incentives for agents are critical, and Celer’s model would be even more robust if fraud detection incurred validator fund slashing. We hear this is on the roadmap.\n\nThe Nomad exploit did not invalidate the security model of its bridge design. Like the Wormhole hack earlier this year, it was due to a smart contract error. This doesn’t undermine the robustness of optimistic verification; these trends, however, raise concerns about a general tendency in the space, by which VC-funded protocols pursuing growth and TVL do so at the expense of engineering best practices (with thanks to Rick Dudley for his insights on this point). In conversations with Celer, we have been impressed with the level of operational security measures put in place by the team. To date, Celer has not experienced an exploit.\n\nNext Steps\n\nIn light of the Nomad hack, we’ve taken a step back to review the state of this proposal. Several bridges teams have put in considerable work to deliver proposals and inform of us on their security models, and we’ve had a number of highly educational conversations. However, our recommendation at this time is no action on a universal bridge model.\n\nThe selection of Nomad by the reputable Gnosis Chain and Moonbeam teams earlier this year indicated to us that migrating all of Uniswap’s cross-chain governance platform to a single partner could be a win for Uniswap. This vendor evaluation effort originally grew out of our desire to vet Nomad against alternative bridges, and as our findings indicate, we are satisfied with Nomad and Celer as equally secure models.\n\nHowever, with the exploit, the deployment timeline for Moonbeam and Gnosis Chain is unclear. Additionally, we’ve seen a pause in Uniswap deployment activity. Current fee switch experimentation is limited to mainnet, and we assume that by the time the first fee switch experiment ends, we will have further information on how Nomad has handled the security issues.\n\nAt this time we do not recommend enshrining a universal bridge partner as outlined in our original RFC. For next steps, we recommend the following:\n\nUniswap deployers considering a bridge should use Nomad or Celer. Deployed chains should run a first-party fraud proof agent, as well as leverage the respective bridge’s full network of agents. We strongly discourage the use of multisig and validator based bridges.\n\nUniswap Foundation should create a grant bounty for proper proposal flow documentation for each of the existing bridges. (We have already engaged UF on this topic.)\n\nUniswap Labs or Foundation should engage the Arbitrum team to help fix the broken Arbitrum deployment.\n\nOther Internet and Uniswap Foundation will continue to monitor the cross-chain bridging ecosystem for the next 6 months, with particular attention to optimistic bridges. We will monitor adoption of Nomad and Celer by reputable protocols, and consider engaging a third party to do a smart contract-level evaluation.\n\n6 Likes\n\n[Temperature Check] Uniswap x Aurora: Expanding our Multichain Future\n\nBuckerino\n\nSeptember 3, 2022, 8:24am\n\n19\n\nFirst of all, I´d like to thank Toby and the peeps from the Other Internet for the comprehensive update of this topic.\n\nI´d agree with the approach of rather being careful than sorry. Inherently, there is no need to rush things mainly in an environment as described by Tony in the update.\n\n2 Likes\n\nblockchaincolumbia\n\nSeptember 7, 2022, 6:03pm\n\n20\n\nBlockchain@Columbia believes that there should be more open discussion on this very important matter, and to this end, we wanted to offer some of our thoughts formed in conjunction with our Uniswap Protocol Lead @jason_of_cs, first on the process front, and as a response to Other Internet’s commentary on it:\n\nTo the need for setting the DAO priorities as per providing a “strategic direction setting” for the protocol, our counterargument is that there is no need to curtail or otherwise limit or affect the DAO process, other than proper commentary on the governance forum. If the community deems a proposal serious and interesting enough to initiate vivid discussions on the forum and to merit voting, then we believe that it should be granted the right to be properly considered to its fullest extent, irrespective of any “strategic directions”. In particular, to the example of Ichi’s stablecoin proposals, it would suffice to make note of the facts asserted in Other Internet’s assessment on the governance forum, and let the community decide on the merits and drawbacks of the proposal.\n\nOn the issue at hand, which is the process for the procurement of a bridge provider, we agree with Other Internet’s proposal that it would be beneficial for a legal agreement to be reached with the bridge team, so as to better guarantee the quality of the outcome, especially when considering the value of the totality of the Uniswap community. However, we believe that their judgment of the Osmosis paradigm for their selection of a bridge partner was somewhat unfair: Other Internet advocates for a more centrally-driven governance model than we believe is essential, where an informed organization makes a strong recommendation and ultimately in a large degree decides the outcome. We believe that this would constitute an overreach for the DAO’s authority over the protocol, and we call for more openness than the current (and proposed) reticent approach. For the bridge election procedure, we propose that a method similar to Osmosis be utilized to select Uniswap’s bridge provider: experts and informed organizations should seek to engage with the various bridge teams, concisely write down their thoughts on advantages and disadvantages of each of them for our community, engage in an open discussion over the forum, and then let the DAO decide on the full spectrum of available options (with ranked voting, if this is possible in Uniswap Governance). We thus voice our disagreement with and concern for Other Internet’s proposed experiment of a procurement process. We would gladly welcome further open discussion on this crucial issue.\n\n2 Likes\n\nblockchaincolumbia\n\nSeptember 7, 2022, 9:33pm\n\n21\n\nObviously, the reason why we’ve been taking our time with our assessment and feedback is precisely the dire need for careful evaluation of all the available options, both from a theoretical model-based and a practical implementation-wise standpoint. Before reaching our informed opinion, we consulted with the bridge teams, conducting interviews with them, and asking for clarifications on many aspects of their design, implementation, and future roadmap choices. In this way, we believe we are fit to weigh in with our feedback for the protocols, and our view on what might best serve Uniswap’s diverse set of needs.\n\nTL;DR: Having universal validators, and not specific to the community served by the bridge provider, is not a good idea for a protocol with as large TVL as Uniswap. On the other hand, optimistic solutions with “fraud proof” designs are riddled with largely ad-hoc “optimistic intervals” which are at the danger of being violated at periods of high gas demand when provers might be priced out of the opportunity to prove fraud, and arbitrary “Watcher griefing” disconnecting communication channels could pose large issues when Watchers are allowed to be fully decentralized (as they should), i.e., everyone (this has been proposed to be mitigated through economic incentives, but with an unclear and unspecified mechanism at work). We propose a synergy between Axelar and Abacus inheriting the PoS validator-set model of Axelar (AXL tokens, which could potentially in an application-specific setting be just the UNI tokens) with the application-customizability of Abacus as having the ideal model for Uniswap’s current purposes, with UNI token holders freely participating in the system (this can be implemented in a variety of ways).\n\nBefore we report on our feedback and assessment, it is crucial to highlight that how the concept of “cross-chain governance” will evolve over time may vitally affect our present choice (thanks to Steven Yin for his contributions to the whole discussion). Currently, cross-chain governance is understood as “reflecting the governance decisions on Ethereum on all the other chains”. One possible future is where the voting process itself can be distributed among different chains. This will inevitably require some concept of governance tokens to exist across chains. There are at least two possible approaches to this: 1. bridging existing governance tokens from Ethereum to other chains using a generic bridge, or 2. Creating native governance tokens on each chain. The second approach will require Uniswap to implement its own logic for managing the burn and minting of UNI tokens on different chains, and use a generic message-passing layer to relay the messages. The first approach relegates the control of the minting/burning process to the bridge provider. Since existing bridge providers have more experience with this process, being audited several times, their smart contract code is likely to be more secure than the second approach. Note that the risk of having smart contract vulnerabilities is high, judging from the frequencies of bridge hacks, and the significant TVL of Uniswap. However, there are two downsides to the first approach: a) Uniswap has less control over the token creation/burning process (thus harder to create custom logic in the future), and b) It is harder to migrate to a different setup, essentially enhancing the degree of vendor lock-in that should already be a parameter in our bridge selection thought process, even without expanded cross-chain governance. The aforementioned points are worth considering and deliberating upon, because the present choice will necessarily directly affect the ease (or hardness) of this potential future ability to expand.\n\nNow that we’ve clarified the cross-chain messaging aspect and weighed in on how the current choice might affect future capabilities, before choosing a bridge provider and/or the technology behind it —which is, in our view, the most important aspect of this decision, as also delineated by Other Internet, in their thought process— we should keep in mind that Uniswap has a massive TVL, which significantly affects the economic incentives that are ingrained (directly or indirectly) in the bridging mechanism.\n\nImplementation-wise, we believe that there is an important gap that needs to be addressed in order for any of the current bridge providers to be adopted into a fully-fledged cross-chain Uniswap governance parameter update mechanism. It is not clear to us which organization is the one that should assist with this; should this be the bridge provider itself, as implied by Other Internet’s RFC? There’s benefits for and arguments against both; in short, requiring the bridge provider to perform a significant part of this development could draw from critical resources that sustain the security and other features of the bridge: this might not be fair (for bridge providers whose methodologies are still in various phases of development, with meritorious models but not mainnet implementation-ready) or efficient. On the other hand, if someone outside of the bridge provider is tasked with this, it would be expected that there should be some kind of offer solicitation for this specific task, along with auditing of the final solution. As mentioned in the post above, this is where it is most beneficial for a potential legal agreement to kick in, and we will leave it up to further discussion from the community.\n\nFor our model-based analysis, which we believe to be the rather significant part of the feedback we give (given that no solution is requested to be “plug-and-play”; c.f., Implementation above, and there has been already Other Internet’s analysis of funding, reputability, and audits for the various protocols), we will begin with a general principle which we deem crucial not to be violated: Stakeholders should participate in the validator set, to make sure that the incentives are correctly aligned. Another way to make sure that this could happen is, as Other Internet suggested, to have an optimistic solution, where again every stakeholder of the community would potentially be able to provide fraud claims, shall a malicious message be found in the network. Nevertheless, the issues with the optimistic window length, along with the possibility of censoring, make this, in our view, an inferior solution to providing a solid validator-based approach.\n\nWe begin with LayerZero, which we deem to be a generic message-passing framework. Their model is all-powerful, allowing the specification of custom Oracle/Relayer combinations for each protocol by themselves (or adopt the default configuration, which then becomes a central validator set). For the reasons delineated above, the default configuration should be ruled out for protocols with massive TVL, i.e., Uniswap. The custom configuration with the ability to have major UNI holders acting as a collective Oracle in a custom-designed system would be our proposal. However, this maximum configurability in terms of message validation specifics (which includes choosing the setup of an oracle-relayer system at a protocol-specific level), security parameters, and utilized libraries of the ecosystem, comes potentially at the expense of ease of use and out-of-the-box setup (again, only given the custom desired configuration). This configurability, of course, has immense advantage on security guarantees in separating different risk entities (participating protocols in the cross-chain communication system), in case of corruption/malice of some validating entity/ies. Similar guarantees can be achieved via including an appropriately diverse set of validating entities (see Generic Principle above). As noticed, though, we believe that the complexity of an appropriate design to achieve the guarantees evidenced above may not be within the current scope of Uniswap’s abilities.\n\nWe continue with Wormhole, which has a large team due to Jump and as a result, has implemented, staged for production, and is actively developing a wide variety of features with robust guarantees. There is a central set of 19 validators, which is a significantly large value contributing to decentralization compared to other central-validator-based bridges. One of the core trust assumptions of Wormhole’s model is the attributability of the message attestations of Guardians by means of their signatures in the (currently multi-sig) scheme. Due to this characteristic, the Guardians have their reputation as well as ownership of protocol shares at stake. Without this attributability, further research is definitely needed to correctly incentivize participants. There is also a governance-controlled per-message fee, whose change is unpredictable in unforeseen circumstances, and whose interplay with potential cross-chain vendor lock-in needs to be taken into account. In summary, we think that Wormhole is the most implementation-ready out of many providers we examined, but in terms of the model, it isn’t there just yet (because of adjustments before its model passes our checks and balances). We would suggest that they add various customizable per-application aspects to lower the systemic risk, and in particular add the ability for a protocol to have a Custom Guardian Set.\n\nFor Nomad, and in general optimistic-based solution approaches (we will not deal here with the necessarily dire implications of the recent hack but only examine the general model), we believe they are clearly surpassed by appropriate validator-based PoS systems, by virtue of their safety guarantees. Here, we disagree with Other Internet that the optimistic model has better security/safety guarantees than the latter. Such a statement would generally hold for a Layer-1/2 on the same chain implementing fraud proofs that can be verified in an austere way (absolutely verifiable by virtue of only on-current-chain elements). Let’s delve into some definitions to further analyze that: the term “optimism” generally confounds two different desiderata which shouldn’t be confounded: 1. vanilla optimism would be that “transactions are always considered valid, unless otherwise indicated,” and 2. the “otherwise indicated”, i.e., when a fraud proof is furnished, means that the fraud proof needs to be an actually true proof (i.e., verifiable by an honest observer who can prove this only on one chain) of the fact that the signed transaction doesn’t correspond to the current state of the (other) chain. However, critically, Nomad’s Watchers can arbitrarily decide to “grief”, closing the communication channel, and the 2nd part of the above desiderata is not being fulfilled (there has been a proposal by Nomad team contributors to integrate economic incentives in order to override that, but to this day, no specific mechanisms which would need to also be analyzed). There is certainly interesting research to improve upon this (sadly, research shows this might end up being very chain-consensus-specific), but the practical system currently implemented doesn’t satisfy the generic claim that same-chain optimistic mechanisms (e.g., L2s) enjoy.\n\nFor Abacus, we believe that the idea of application-specific sovereign consensus is a very good idea matching our General Principle above. In accordance to this, sovereign consensus would necessarily be utilized by Uniswap’s implementation, and the protocol would be able to combine the benefits of both a default setup with trusted nodes (the 4/5 configuration, e.g.) along with a custom setup of UNI stakeholders as a custom validator set. This application-specific set makes sure that the future of the Uniswap ecosystem is safeguarded from actors which could turn potentially malicious or adversely affected by central decisions (systemic risk). Our suggestion for what we would like to see in this protocol before we say that its model is theoretically robust is to integrate potential weighting of the custom validators in the custom validator set for sovereign consensus in an efficient way, as well as allow to easily change the custom validator set dynamically in real-time. Because we believe that this is served 100% by adding a PoS permissionless system for the custom validators, we continue this below inside our Axelar analysis.\n\nFor Axelar, which is the only true permissionless validator-set system, we think that the PoS consensus system to verify any message is truly the state-of-the-art, subject to the General Principle above, i.e., that the stakeholders of an ecosystem with large TVL would participate in this PoS scheme. When this happens, then the system would effectively engage the underlying stakeholders (if needed; if not, then the default PoS participants can provide the consensus), who have no economic incentive to override and lie about their own decisions. What we are lacking currently from this system, and we highly suggest to the team that it be integrated, is application-specificity tightly integrated with default characteristics, akin to the Abacus ones: applications (certainly Uniswap) should be able to, if needed, provide a supermajority of actual protocol governance stakeholders as the consensus mechanism; but under normal conditions, a supermajority of the normal PoS scheme might suffice. We can see the helpfulness of a default configuration with a truly permissionless system of validators (as is currently guaranteed by the AXL token) towards smaller protocols bootstrapping their cross-chain messaging, but also recognize that this default alone might be somewhat inadequate for a protocol with massive TVL at stake.\n\nLastly, a generic comment on gas costs/efficiency: since the Uniswap community is currently intending to use cross-chain community solely for message-passing the parameter updates (see paragraph on what cross-chain governance means above), it is not necessary to wait for the adoption of either threshold signature schemes or more sophisticated zero-knowledge proofs. While altogether it’s not clear whether zk would provide any benefit whatsoever (in fact, in some of the threat models above, according to our theoretical analysis, zk would even constitute a violation of certain trust assumptions, and might misincentivize validating entities), gas efficiency might be more desirable shall the Uniswap community decide to move on to voting governance proposals on-chain in a multi-chain environment.\n\nWe are definitely looking forward to seeing more open discussion in the community!\n\n3 Likes\n\n[RFC - Update] Deploy Uniswap v3 (1 / 0.3 / 0.05 / 0.01) on BNB Chain (Binance)\n\n[RFC - Update] Deploy Uniswap v3 (1 / 0.3 / 0.05 / 0.01) on BNB Chain (Binance)\n\nnext page →\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[RFC - Update] Deploy Uniswap v3 (1 / 0.3 / 0.05 / 0.01) on BNB Chain (Binance)\n\nRequests for Comment\n\n101\n\n45661\n\nJuly 22, 2026\n\nCross-Chain Bridge Assessment Process\n\nUncategorized\n\n49\n\n29473\n\nApril 19, 2023\n\nDeploy Uniswap v3 on Avalanche\n\nRequests for Comment\n\n18\n\n10148\n\nAugust 25, 2023\n\nCommunity Governance Process\n\nGovernance-Meta\n\n30\n\n58333\n\nApril 7, 2023\n\nGovernance Weekly Recap\n\nGovernance-Meta\n\n21\n\n6566\n\nMay 26, 2023","tokens":27800,"crawled_at":1791193876017}
+{"id":10302,"url":"https://docs.ethers.org/v6/api/transaction","domain":"docs.ethers.org","chapter":"developer_specs","title":"","text":"ethers\n6.17.0\n\nDOCUMENTATION\nGetting Started\nEthereum Basics\nApplication Programming Interface\nPollingBlockTagSubscriber\nApplication Binary Interface\nAddresses\nConstants\nContracts\nCryptographic Functions\nHashing Utilities\nProviders\nTransactions\nAuthorization\nBlob\nKzgLibrary\nTransaction\nTransactionLike\nUtilities\nWallets\nWordlists\nCookbook\nMigrating from v5\nContributions and Hacking\nLicense and Copyright\n\nSingle Page\n\nDocumentation »API »Transactions\nTransactions\nEach state-changing operation on Ethereum requires a transaction.\n\nTYPES\n<src>AccessList⇒ Array< AccessListEntry >\nAn ordered collection of AccessList entries.\n\n<src>AccessListEntry⇒ { address: string , storageKeys: Array< string > }\nA single AccessList entry of storage keys (slots) for an address.\n\n<src>AccessListish⇒ AccessList | Array< tuple< string, Array< string > > > | Record< string, Array< string > >\nAny ethers-supported access list structure.\n\n<src>AuthorizationLike⇒ { address: string , chainId: BigNumberish , nonce: BigNumberish , signature: SignatureLike }\n\n<src>BlobLike⇒ BytesLike | { commitment: BytesLike , data: BytesLike , proof: BytesLike }\nA BLOb object that can be passed for EIP-4844 transactions.\nIt may have had its commitment and proof already provided or rely on an attached KzgLibrary to compute them.\n\n<src>KzgLibraryLike⇒ KzgLibrary | { blobToKZGCommitment: (blob: string) => string , computeBlobKZGProof: (blob: string, commitment: string) => string } | { blobToKzgCommitment: (blob: string) => string | Uint8Array , computeBlobProof: (blob: string, commitment: string) => string | Uint8Array }\nA KZG Library with any of the various API configurations. As the library is still experimental and the API is not stable, depending on the version used the method names and signatures are still in flux.\nThis allows any of the versions to be passed into Transaction while providing a stable external API.\n\nFUNCTIONS\n<src>accessListify(value: AccessListish)⇒ AccessList\nReturns a AccessList from any ethers-supported access-list structure.\n\n<src>authorizationify(auth: AuthorizationLike)⇒ Authorization\n\n<src>computeAddress(key: string | SigningKey)⇒ string\nReturns the address for the key.\nThe key may be any standard form of public key or a private key.\n\n<src>recoverAddress(digest: BytesLike, signature: SignatureLike)⇒ string\nReturns the recovered address for the private key that was used to sign digest that resulted in signature.\n\ninterface Authorization\n\nPROPERTIES\n<src>authorization.address⇒ string\n\n<src>authorization.chainId⇒ bigint\n\n<src>authorization.nonce⇒ bigint\n\n<src>authorization.signature⇒ Signature\n\ninterface Blob\nA full-valid BLOb object for EIP-4844 transactions.\nThe commitment and proof should have been computed using a KZG library.\n\nPROPERTIES\n<src>blob.commitment⇒ string\nThe BLOb commitment.\n\n<src>blob.data⇒ string\nThe blob data.\n\n<src>blob.proof⇒ string\nA EIP-4844 BLOb uses a string proof, while EIP-7594 use an array of strings representing the cells of the proof.\n\ninterface KzgLibrary\nA KZG Library with the necessary functions to compute BLOb commitments and proofs.\n\nPROPERTIES\n<src>kzgLibrary.blobToKzgCommitment⇒ (blob: Uint8Array) => Uint8Array\n\n<src>kzgLibrary.computeBlobKzgProof⇒ (blob: Uint8Array, commitment: Uint8Array) => Uint8Array\n\nclass Transaction\nA Transaction describes an operation to be executed on Ethereum by an Externally Owned Account (EOA). It includes who (the to address), what (the data) and how much (the value in ether) the operation should entail.\n\ntx = new Transaction()\n// Transaction { to: null, data: \"0x1234\", nonce: 0, gasLimit: 0, value: 0, chainId: 0 }\n\ntx.data = \"0x1234\";\n// '0x1234'\n\nPROPERTIES\n<src>transaction.accessList⇒ null | AccessList\nThe access list.\nAn access list permits discounted (but pre-paid) access to bytecode and state variable access within contract execution.\n\n<src>transaction.authorizationList⇒ null | Array< Authorization >\n\n<src>transaction.blobs⇒ null | Array< Blob >\nThe BLObs for the Transaction, if any.\nIf blobs is non-null, then the seriailized will return the network formatted sidecar, otherwise it will return the standard EIP-2718 payload. The unsignedSerialized is unaffected regardless.\nWhen setting blobs, either fully valid Blob objects may be specified (i.e. correctly padded, with correct committments and proofs) or a raw BytesLike may be provided.\nIf raw BytesLike are provided, the kzg property must be already set. The blob will be correctly padded and the KzgLibrary will be used to compute the committment and proof for the blob.\nA BLOb is a sequence of field elements, each of which must be within the BLS field modulo, so some additional processing may be required to encode arbitrary data to ensure each 32 byte field is within the valid range.\nSetting this automatically populates blobVersionedHashes, overwriting any existing values. Setting this to null does not remove the blobVersionedHashes, leaving them present.\n\n<src>transaction.blobVersionedHashes⇒ null | Array< string >\nThe BLOb versioned hashes for Cancun transactions.\n\n<src>transaction.blobWrapperVersion⇒ null | number\n\n<src>transaction.chainId⇒ bigint\nThe chain ID this transaction is valid on.\n\n<src>transaction.data⇒ string\nThe transaction data. For init transactions this is the deployment code.\n\n<src>transaction.from⇒ null | stringread-only\nThe sending address, if signed. Otherwise, null.\n\n<src>transaction.fromPublicKey⇒ null | stringread-only\nThe public key of the sender, if signed. Otherwise, null.\n\n<src>transaction.gasLimit⇒ bigint\nThe gas limit.\n\n<src>transaction.gasPrice⇒ null | bigint\nThe gas price.\nOn legacy networks this defines the fee that will be paid. On EIP-1559 networks, this should be null.\n\n<src>transaction.hash⇒ null | stringread-only\nThe transaction hash, if signed. Otherwise, null.\n\n<src>transaction.kzg⇒ null | KzgLibrary\n\n<src>transaction.maxFeePerBlobGas⇒ null | bigint\nThe max fee per blob gas for Cancun transactions.\n\n<src>transaction.maxFeePerGas⇒ null | bigint\nThe maximum total fee per unit of gas to pay. On legacy networks this should be null.\n\n<src>transaction.maxPriorityFeePerGas⇒ null | bigint\nThe maximum priority fee per unit of gas to pay. On legacy networks this should be null.\n\n<src>transaction.nonce⇒ number\nThe transaction nonce.\n\n<src>transaction.serialized⇒ stringread-only\nThe serialized transaction.\nThis throws if the transaction is unsigned. For the pre-image, use unsignedSerialized.\n\n<src>transaction.signature⇒ null | Signature\nIf signed, the signature for this transaction.\n\n<src>transaction.to⇒ null | string\nThe to address for the transaction or null if the transaction is an init transaction.\n\n<src>transaction.type⇒ null | number\nThe transaction type.\nIf null, the type will be automatically inferred based on explicit properties.\n\n<src>transaction.typeName⇒ null | stringread-only\nThe name of the transaction type.\n\n<src>transaction.unsignedHash⇒ stringread-only\nThe pre-image hash of this transaction.\nThis is the digest that a Signer must sign to authorize this transaction.\n\n<src>transaction.unsignedSerialized⇒ stringread-only\nThe transaction pre-image.\nThe hash of this is the digest which needs to be signed to authorize this transaction.\n\n<src>transaction.value⇒ bigint\nThe amount of ether (in wei) to send in this transactions.\n\nCREATING INSTANCES\n<src>new Transaction()\nCreates a new Transaction with default values.\n\n<src>Transaction.from(tx?: string | TransactionLike < string >)⇒ Transaction\nCreate a Transaction from a serialized transaction or a Transaction-like object.\n\nMETHODS\n<src>transaction.clone()⇒ Transaction\nCreate a copy of this transaciton.\n\n<src>transaction.inferType()⇒ number\nReturn the most \"likely\" type; currently the highest supported transaction type.\n\n<src>transaction.inferTypes()⇒ Array< number >\nValidates the explicit properties and returns a list of compatible transaction types.\n\n<src>transaction.inspect()⇒ string\n\n<src>transaction.isBerlin()⇒ boolean\nReturns true if this transaction is berlin hardform transaction (i.e. type === 1).\nThis provides a Type Guard that the related properties are non-null.\n\n<src>transaction.isCancun()⇒ boolean\nReturns true if this transaction is an EIP-4844 BLOB transaction.\nThis provides a Type Guard that the related properties are non-null.\n\n<src>transaction.isLegacy()⇒ boolean\nReturns true if this transaction is a legacy transaction (i.e. type === 0).\nThis provides a Type Guard that the related properties are non-null.\n\n<src>transaction.isLondon()⇒ boolean\nReturns true if this transaction is london hardform transaction (i.e. type === 2).\nThis provides a Type Guard that the related properties are non-null.\n\n<src>transaction.isSigned()⇒ boolean\nReturns true if signed.\nThis provides a Type Guard that properties requiring a signed transaction are non-null.\n\n<src>transaction.isValid()⇒ boolean\n\n<src>transaction.toJSON()⇒ any\nReturn a JSON-friendly object.\n\n<src>transaction.toString()⇒ string\n\ninterface TransactionLike\nA TransactionLike is an object which is appropriate as a loose input for many operations which will populate missing properties of a transaction.\n\nPROPERTIES\n<src>transactionLike.accessList⇒ null | AccessListish\nThe access list for berlin and london transactions.\n\n<src>transactionLike.authorizationList⇒ null | Array< Authorization >\nThe EIP-7702 authorizations (if any).\n\n<src>transactionLike.blobs⇒ null | Array< BlobLike >\nThe blobs (if any) attached to this transaction (see EIP-4844).\n\n<src>transactionLike.blobVersionedHashes⇒ null | Array< string >\nThe versioned hashes (see EIP-4844).\n\n<src>transactionLike.blobWrapperVersion⇒ null | number\nThe EIP-7594 BLOb Wrapper Version used for PeerDAS.\nFor networks that use EIP-7594, this property is required to serialize the sidecar correctly.\n\n<src>transactionLike.chainId⇒ null | BigNumberish\nThe chain ID the transaction is valid on.\n\n<src>transactionLike.data⇒ null | string\nThe data.\n\n<src>transactionLike.from⇒ null | A\nThe sender.\n\n<src>transactionLike.gasLimit⇒ null | BigNumberish\nThe maximum amount of gas that can be used.\n\n<src>transactionLike.gasPrice⇒ null | BigNumberish\nThe gas price for legacy and berlin transactions.\n\n<src>transactionLike.hash⇒ null | string\nThe transaction hash.\n\n<src>transactionLike.kzg⇒ null | KzgLibraryLike\nAn external library for computing the KZG commitments and proofs necessary for EIP-4844 transactions (see EIP-4844).\nThis is generally null, unless you are creating BLOb transactions.\n\n<src>transactionLike.maxFeePerBlobGas⇒ null | BigNumberish\nThe maximum fee per blob gas (see EIP-4844).\n\n<src>transactionLike.maxFeePerGas⇒ null | BigNumberish\nThe maximum total fee per gas for london transactions.\n\n<src>transactionLike.maxPriorityFeePerGas⇒ null | BigNumberish\nThe maximum priority fee per gas for london transactions.\n\n<src>transactionLike.nonce⇒ null | number\nThe nonce.\n\n<src>transactionLike.signature⇒ null | SignatureLike\nThe signature provided by the sender.\n\n<src>transactionLike.to⇒ null | A\nThe recipient address or null for an init transaction.\n\n<src>transactionLike.type⇒ null | number\nThe type.\n\n<src>transactionLike.value⇒ null | BigNumberish\nThe value (in wei) to send.\n\n← Community Providers\nUtilities→\n\nThe content of this site is licensed under the Creative Commons License. Generated on March 10, 2025, 8:06am.","tokens":2825,"crawled_at":1791193876452}
+{"id":10303,"url":"https://a16zcrypto.com/posts/article/new-paper-alert-transaction-fee-mechanism-design-with-active-block-producers","domain":"a16zcrypto.com","chapter":"research","title":"Transaction Fee Mech Design with Active Block Producers - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nNew paper alert: “Transaction Fee Mechanism Design with Active Block Producers”\nMaryam Bahrani, Pranav Garimidi, and Tim Roughgarden\n07.10.23\n\nTags & Share Tags\nDeFi\nmev\nresearch\ntech trends\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nThis paper introduces a model of active block producers that have their own private valuations for blocks. The block producer surplus in our model can be interpreted as one of the more common colloquial meanings of the term “MEV.” The main results show that transaction fee mechanism design is fundamentally more difficult with active block producers than with passive ones: with active block producers, no non-trivial or approximately welfare-maximizing transaction fee mechanism can be incentive-compatible for both users and block producers. These results can be interpreted as a mathematical justification for the current interest in augmenting transaction fee mechanisms with additional components such as order flow auctions, block producer competition, trusted hardware, or cryptographic techniques.\n\nBackground\n\nA transaction fee mechanism (TFM) is the part of a blockchain protocol responsible for figuring out which transactions should be included and who should pay what. Ethereum’s EIP-1559 is an example. One minimal thing you’d really like from a TFM is good UX, meaning that bidding is easy for users (one of the original motivations for EIP-1559). This idea is encoded by a mathematical property called “DSIC.” A second requirement is a form of credibility called “BPIC,” meaning that a validator responsible for supplying the TFM’s inputs should be properly incentivized to behave as intended. DSIC+BPIC have been studied in a pre-MEV world (e.g., with EIP-1559 achieving both, as long as its base fee is not too low for the current demand).\n\nResults\n\nIn this paper, we model a post-MEV world via block producers with private valuations for blocks (e.g., due to application-layer value that they can extract), above and beyond whatever fees they might earn at the consensus layer. MEV changes things considerably, both theoretically and practically. For example, EIP-1559 is no longer incentive-compatible for both users and block producers (even with a correctly set base fee).\n\nIntuitively, the issue is that, when there’s MEV, a user can’t know whether to underbid to take advantage of a block producer that might be willing to subsidize the difference. Our main result shows that the problem is fundamental and not a flaw in the EIP-1559 design: with MEV, no non-trivial or approximately welfare-maximizing TFM can be both DSIC and BPIC.\n\nWays forward\n\nThe role of an impossibility result like this is not to discourage but to illuminate, highlighting the most promising paths forward. From it, we learn that our options are constrained but already being actively explored by the community. Options include:\n\nGiving up on “good UX,” at least as it is expressed by the DSIC property\n\nGiving up on the BPIC property, presumably compensating with restrictions on block producer behavior (perhaps enforced using, e.g., trusted hardware or cryptographic techniques)\n\nExpand the TFM design space, for example by incorporating order flow auctions or block producer competition to expose information about a BP’s private valuation to a TFM\n\nFor details, proofs, and citations, read the paper.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nCharts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":1526,"crawled_at":1791193881122}
+{"id":10304,"url":"https://docs.sui.io/onchain-finance","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Onchain Finance | Sui Documentation","text":"Build onchain finance applications on Sui. Learn about digital assets, wallet integration, tokenomics, and the DeepBookDeepBookA decentralized central limit order book (CLOB) built on Sui. decentralized exchange.\n\nOnchain Finance\nBuild onchain finance applications on Sui. Learn about digital assets, asset custody, payments, tokenomics, and the DeepBook decentralized exchange.\n→\nTypes of Assets\nSui provides a variety of asset standards with different features for multiple usage patterns.\n→\nAsset Custody\nIn this section\nAddress Balances\nWallets\nAddress Aliases for Asset Custody\nFiat On-Ramps\nFiat Off-Ramps\n\n→\nFungible Tokens\nIn this section\nCoin Standard\nCurrency Standard\nRegulated Currencies\nToken Vesting Strategies\nBridging Tokens\n\n→\nTokenized Assets\nIn this section\nAsset Tokenization\nDeploy a Tokenized Asset\nCreate a Non-Fungible Token\n\n→\nPayments\nIn this section\nChoose a Payment Model\nPayment Kit\nPayment Intents\nFunding Wallets\n\n→\nAllowances\nIn this section\nOverview\nUsing Allowances\nFAQ\n\n→\nExample Asset Patterns\nIn this section\nFixed Supply\nLoyalty Tokens\nIn-Game Currencies\nSoulbound NFTs\nStaking Rewards\nNFT Rentals\n+ 2 more\n\n→\nClosed-Loop Token\nIn this section\nToken Policy\nAction Request\nRules\nSpending\n\n→\nPermissioned Asset Standard\nIn this section\nWhat is Permissioned Asset Standard?\nActions\nIntegration\nQuerying Assets\n\n→\nDeepBook\nIn this section\nDesign\nFees and Funding\nSpot Trading Workflow\nDeepBookV3\nMargin\nPredict\n+ 1 more\n\n→\nOracles\nIn this section\nConsuming Price Feeds\nMove Adapter Pattern\nOracle Safety\nResolution Patterns\n\n→\nKiosk\nIn this section\nSui Kiosk\nKiosk Apps\n\n→","tokens":402,"crawled_at":1791193892314}
+{"id":10305,"url":"https://gov.uniswap.org/t/proposed-template-for-future-cross-chain-deployment-proposals/16611","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Proposed Template for Future Cross-chain Deployment Proposals - Governance-Meta - Uniswap Governance","text":"Proposed Template for Future Cross-chain Deployment Proposals\n\nGovernance-Meta\n\nUniswapLabs\n\nApril 4, 2022, 2:56pm\n\n1\n\nIn alignment with our belief that the Uniswap community should be empowered to make informed governance decisions regarding cross-chain deployments, Uniswap Labs would like to propose a template for such proposals.\n\nWe have previously written here about the importance of paying close attention to the security and trust assumptions of the bridge being used to relay governance to the chain. As discussed in this post, Uniswap Governance contracts live on L1 Ethereum, so when the Protocol is deployed to a new network, UNI holders need a bridge contract to govern the Protocol on that network.\n\nWe believe users should be able to access the Uniswap Protocol, as well as other DeFi and web3-based protocols, across chains which are important to them. We also believe that Uniswap Protocol community members should be informed about the relevant security and trust assumptions in the bridge design, and particularly in the current implementation of the bridges which will be used for the deployment.\n\nWe also recently released the deployment script and documentation outlining how to deploy Uniswap Protocol v3 to other chains. Teams are now able to deploy the Protocol across chains entirely on their own, without the direct assistance of the Uniswap Labs team. To carry out the deployment, teams will have to request an exemption from the Uniswap Protocol v3 Business Source License. We have included sample language to use to make that request.\n\nAs such, we suggest that all future proposals for cross-chain proposals use the template below.\n\nCross-chain Deployment Proposal Template\n\nSummary of the Proposal.\n\nTL;DR including Proposed Chain, Deployer, Chain, Timeline to deployment, Benefits to Uniswap Community, and any other relevant information\n\nAbout the Proposed Chain\n\nIncluding, for instance, history of team, application ecosystem, size of user base, daily transfer volume, etc.\n\nProposal\n\nBenefits to Uniswap Community and/or DAO Treasury\n\nAny planned Liquidity Mining (optional)\n\nBridge security (Provide details based on current implementation as of proposal post date)\n\nDoes the bridge support arbitrary message passing?\n\nIs the bridge secured by a trusted entity, by a multi sig, or a protocol/set of incentivized nodes?\n\nDoes the bridge leverage the security of the source chain (e.g. Ethereum L1) or destination chain, or is security provided by another third party entity?\n\nIs it possible for a fraudulent message to be passed to the destination chain? If so, are there any recall mechanisms?\n\nWhat are the ramifications of fraud to the malicious actor?\n\nHas the bridge code been audited? By a third party? What attack vectors and vulnerabilities were identified, if any? Have the identified vulnerabilities been remedied?\n\nLicense Exemption - if Uniswap Labs is not deploying the protocol\n\nSample language for a Layer 2 solution: \"Team [or Company] X may use the Licensed Work to deploy it on Y, a layer 2 solution for Ethereum, provided that the deployment is subject to Ethereum layer 1 Uniswap Protocol governance and control.”\n\nList the entity receiving the exemption - important that the exemption isn’t for anyone to deploy on the chain but a specific entity/team.\n\nTimeline for deployment after Governance approval\n\nNext Steps\n\nWe welcome feedback from the community on the template, including suggestions on how it can be improved.\n\n11 Likes\n\n[Temperature Check] Uniswap x Aurora: Expanding our Multichain Future\n\nDeploy Uniswap V3 to zkSync\n\nAccountability Committee, Deployments & Agreements\n\nlotti\n\nApril 5, 2022, 9:53am\n\n2\n\nThis is Laura and Joanna from Other Internet. We welcome this template and propose the following additions in two areas based on our ongoing strategic research into partnerships and accountability in Uniswap governance:\n\nProvide detailed information about the deploying entity in addition to the proposed chain\n\nProvide detailed information about both financial and non-financial/indirect benefits to the Uniswap community that the proposer commits to, including a timeline on the delivery of any funds\n\nOur suggested changes are added to the original template below in bold. We look forward to seeing other feedback and suggestions from the community on this initiative!\n\nCross-chain Deployment Proposal Template\n\nSummary of the Proposal.\n\nTL;DR including Proposed Chain, Deployer, Chain, Timeline to deployment, Benefits to Uniswap Community, and any other relevant information\n\nAbout the Proposed Chain\n\nIncluding, for instance, history of team, application ecosystem, size of user base, daily transfer volume, etc. + stage of development of the project (e.g. pre-launch, testnet, mainnet)\n\nAbout the Deployer\n\nHistory of team, relationship to proposed chain team, relationship to Uniswap Labs, Uniswap community and/or UGP, community governance, information about native token, etc.\n\nProposal\n\nFinancial benefits to Uniswap Community and/or DAO Treasury + timeline on delivery of any funds\n\nAny planned Liquidity Mining (optional) + timeline on delivery of any funds\n\nAny planned additional grants (optional) + timeline on delivery of any funds\n\nIf metagovernance/dao2dao deal proposed, provide details of governance implementation\n\nNon-financial/indirect benefits to Uniswap community e.g. increased user base\n\nBenefits to ethereum/web3 ecosystem, contribution to public goods (scaling, mass adoption, etc.)\n\nAny co-branding plans (optional) + details of the program\n\nBridge security (Provide details based on current implementation as of proposal post date)\n\nDoes the bridge support arbitrary message passing?\n\nIs the bridge secured by a trusted entity, by a multi sig, or a protocol/set of incentivized nodes?\n\nDoes the bridge leverage the security of the source chain (e.g. Ethereum L1) or destination chain, or is security provided by another third party entity?\n\nIs it possible for a fraudulent message to be passed to the destination chain? If so, are there any recall mechanisms?\n\nWhat are the ramifications of fraud to the malicious actor?\n\nHas the bridge code been audited? By a third party? What attack vectors and vulnerabilities were identified, if any? Have the identified vulnerabilities been remedied?\n\nLicense Exemption - if Uniswap Labs is not deploying the protocol\n\nSample language for a Layer 2 solution: \"Team [or Company] X may use the Licensed Work to deploy it on Y, a layer 2 solution for Ethereum, provided that the deployment is subject to Ethereum layer 1 Uniswap Protocol governance and control.”\n\nList the entity receiving the exemption - important that the exemption isn’t for anyone to deploy on the chain but a specific entity/team.\n\nTimeline for deployment after Governance approval\n\n6 Likes\n\nProposal Template 2.0 - Upgrade for Deployments & Agreements\n\n[Consensus Check] Should Uniswap v3 be deployed to Gnosis Chain?\n\nUniswapLabs\n\nApril 6, 2022, 8:14pm\n\n3\n\nThank you for these additions - we agree with these suggested changes and will add them to the final version of the template incorporating all community feedback.\n\n2 Likes\n\nGFXlabs\n\nApril 20, 2022, 3:04pm\n\n4\n\nWe have a clarifying question because there seems to be some confusion about what language should be used for the proceeding deployments of Uniswap V3.\n\nThe Voltz Additional Use Grants is:\n\nVoltz Labs Technology Limited (“Voltz”) is granted an additional use grant to allow the Voltz DAO to use the Uniswap V3 Core software code (which is made available to Voltz subject to license available at https://github.com/Uniswap/v3-core/blob/main/LICENSE (the “Uniswap Code”)). As part of this additional use grant, the Voltz DAO receives a limited worldwide license to use the Uniswap Code for the purposes of: creating, deploying and making available aspects of an interest rate swap automated market maker (the “IRS AMM”); to modify and update the IRS AMM over time; and deploy the IRS AMM and portions thereof as smart contracts on blockchain-based applications and protocols. The Voltz DAO is permitted to use subcontractors to do this work. This license is conditional on Voltz and the Voltz DAO complying with the terms of the Business Source License 1.1, made available at https://github.com/Uniswap/v3-core/blob/main/LICENSE.\n\nOur understanding was that Voltz needed the additional use grant because it sought to use the innovations of Uniswap in its derivative product.\n\nThis forum thread appears to be for chains seeking a Uniswap v3 deployment where the deployment is owned and controlled by the Unsiwap DAO. In these instances where control is maintained by the DAO and the deployment is done to the DAO’s expectation, the chain requesting the deployment can receive an exemption from the license.\n\nWhile the additional use grant could apply to chains seeking a Uniswap v3 deployment, it would give them additional breadth that the DAO doesn’t need to give. If our understanding is correct, the proceeding deployments such as Celo, Moonbeam, and Gnosis should be requesting an exemption from the license using the sample language in the first forum post.\n\n2 Likes\n\n[Governance Proposal] Deploy Uniswap v3 on Celo\n\nlotti\n\nApril 27, 2022, 2:43pm\n\n5\n\nThank you for your reply!\n\nCorrect, both projects like Voltz (middleware deploying on Ethereum) and chains like Moonbeam and Gnosis Chain (L2s or protocols that exist on other L1s) need to request an additional use grant to deploy v3. In both cases the deployment needs to be approved by the Uniswap DAO, and it is controlled by it in so far as these projects need to request the additional use grant through the governance process. Only deployments done by Uniswap Labs do not need to request a license.\n\nThe suggested additions to the template are to help with the evaluation of projects by the Uniswap community, and we agree that the template needs to be accommodating to the requirements of the different use cases, which is something we are working on mapping right now. So it should be used with some flexibility for the time being.\n\nI hope this answers your questions, let us know if you have any further thoughts.\n\n1 Like\n\nchanrivera\n\nMay 5, 2022, 7:55am\n\n6\n\nHi guys,\n\nWhat is the current update of this deployment proposals?\n\n1 Like\n\nuniyj\n\nMay 6, 2022, 3:36pm\n\n7\n\nI assume you meant the proposals to deploy uni-v3 on Moonbeam and/or Gnosis Chain? Both proposals have just been put on-chain.\n\nMoonbeam – see here and here.\n\nGnosis Chain – see here.\n\nAs for the uni-v3 deployment on Celo, proposal has passed on-chain (see here). Still waiting for execution (to grant v3 usage license on ENS txt record) and actual deployment.\n\nyj\n\n3 Likes\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nCross-chain Deployment Guide\n\nGovernance-Meta\n\n2\n\n8195\n\nApril 25, 2024\n\n[RFC] Ammended Deployment Proposal Process\n\nGovernance-Meta\n\n4\n\n3149\n\nMarch 15, 2024\n\n[Governance Proposal] Deploy Uniswap V3 on Moonbeam\n\nRequests for Comment\n\n11\n\n7092\n\nFebruary 7, 2023\n\n[RFC - Update] Deploy Uniswap v3 (1 / 0.3 / 0.05 / 0.01) on BNB Chain (Binance)\n\nRequests for Comment\n\n101\n\n45661\n\nJuly 22, 2026\n\nAccountability Committee, Deployments & Agreements\n\nGovernance-Meta\n\n3\n\n1814\n\nJuly 18, 2023","tokens":2805,"crawled_at":1791193893844}
+{"id":10306,"url":"https://a16zcrypto.com/posts/article/dao-governance-attacks-and-how-to-avoid-them","domain":"a16zcrypto.com","chapter":"research","title":"DAO governance attacks, and how to avoid them - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nDAO governance attacks, and how to avoid them\nPranav Garimidi, Scott Duke Kominers, and Tim Roughgarden\n07.27.22\n\nTABLE OF CONTENTS\nGovernance attacks in practice Governance attacks in practice\nThe fundamental challenge: Indistinguishability\nA framework for assessing and addressing vulnerability\nTags\ncompany building\nDAOs\ngovernance\ngovernance best practices\nmechanism design\nresearch\nsecurity\ntoken design\ntokens\nvoting\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nMany web3 projects embrace permissionless voting using a fungible and tradable native token. Permissionless voting can offer many benefits, from lowering barriers to entry to increasing competition. Token holders can use their tokens to vote on a range of issues — from simple parameter adjustments to the overhaul of the governance process itself. (For a review of DAO governance, see “Lightspeed Democracy.”) But permissionless voting is vulnerable to governance attacks, in which an attacker acquires voting power through legitimate means (e.g., buying tokens on the open market) but uses that voting power to manipulate the protocol for the attacker’s own benefit. These attacks are purely “in-protocol,” which means they can’t be addressed through cryptography. Instead, preventing them requires thoughtful mechanism design. To that end, we’ve developed a framework to help DAOs assess the threat and potentially counter such attacks.\n\nGovernance attacks in practice\n\nThe problem of governance attacks isn’t just theoretical. They not only can happen in the real world, but they already have and will continue to.\n\nIn one prominent example, Steemit, a startup building a decentralized social network on their blockchain, Steem, had an on-chain governance system controlled by 20 witnesses. Voters used their STEEM tokens (the platform’s native currency) to choose the witnesses. While Steemit and Steem were gaining traction, Justin Sun had developed plans to merge Steem into Tron, a blockchain protocol he had founded in 2018. To acquire the voting power to do so, Sun approached one of the founders of Steem and bought tokens equivalent to 30 percent of the total supply. Once the then-current Steem witnesses discovered his purchase, they froze Sun’s tokens. What followed was a public back-and-forth between Sun and Steem to control enough tokens to install their preferred slate of top 20 witnesses. After involving major exchanges and spending hundreds of thousands of dollars on tokens, Sun was eventually victorious and effectively had free reign over the network.\n\nIn another instance, Beanstalk, a stablecoin protocol, found itself susceptible to governance attack via flashloan. An attacker took out a loan to acquire enough of Beanstalk’s governance token to instantly pass a malicious proposal that allowed them to seize $182 million of Beanstalk’s reserves. Unlike the Steem attack, this one happened within the span of a single block, which meant it was over before anyone had time to react.\n\nWhile these two attacks happened in the open and under the public eye, governance attacks can also be conducted surreptitiously over a long period of time. An attacker might create numerous anonymous accounts and slowly accumulate governance tokens, while behaving just like any other holder to avoid suspicion. In fact, given how low voter participation tends to be in many DAOs, those accounts could lie dormant for an extended period of time without raising suspicion. From the DAO’s perspective, the attacker’s anonymous accounts could contribute to the appearance of a healthy level of decentralized voting power. But eventually the attacker could reach a threshold where these sybil wallets have the power to unilaterally control governance without the community being able to respond. Similarly, malicious actors might acquire enough voting power to control governance when turnout is sufficiently low, and then try to pass malicious proposals when many other token holders are inactive.\n\nAnd while we might think all governance actions are just the result of market forces at work, in practice governance can sometimes produce inefficient outcomes as the result of incentive failures or other vulnerabilities in a protocol’s design. Just as government policymaking can become captured by interest groups or even simple inertia, DAO governance can lead to inferior outcomes if it’s not structured properly.\n\nSo how can we address such attacks through mechanism design?\n\nThe fundamental challenge: Indistinguishability\n\nMarket mechanisms for token allocation fail to distinguish between users who want to make valuable contributions to a project and attackers who attach high value to disrupting or otherwise controlling it. In a world where tokens can be bought or sold in a public marketplace, both of these groups are, from the market perspective, behaviorally indistinguishable: both are willing to buy large quantities of tokens at increasingly high prices.\n\nThis indistinguishability problem means that decentralized governance doesn’t come for free. Instead, protocol designers face fundamental tradeoffs between openly decentralizing governance and securing their systems against attackers seeking to exploit governance mechanisms. The more community members are free to gain governance power and influence the protocol, the easier it is for attackers to use that same mechanism to make malicious changes.\n\nThis indistinguishability problem is familiar from the design of Proof of Stake blockchain networks. There as well, a highly liquid market in the token makes it easier for attackers to acquire enough stake to compromise the network’s security guarantees. Nevertheless, a mixture of token incentive and liquidity design makes Proof of Stake networks possible. Similar strategies can help secure DAO protocols.\n\nA framework for assessing and addressing vulnerability\n\nTo analyze the vulnerability different projects face we use a framework captured by the following equation:\n\nFor a protocol to be considered secure against governance attacks, an attacker’s profit should be negative. When designing the governance rules for a project, this equation can be used as a guidepost for evaluating the impact of different design choices. To reduce the incentives to exploit the protocol, the equation implies three clear choices: decrease the value of attacks, increase the cost of acquiring voting power, and increase the cost of executing attacks.\n\nDecreasing the value of attacks\n\nLimiting the value of an attack can be difficult because the more successful a project gets, the more valuable a successful attack may become. Clearly a project should not intentionally sabotage its own success just to decrease the value of an attack.\n\nNevertheless, designers can limit the value of attacks by limiting the scope of what governance can do. If governance only includes the power to change certain parameters in a project (e.g., interest rates on a lending protocol), then the scope of potential attacks is much narrower than when governance allows fully general control of the governing smart contract.\n\nGovernance scope can be a function of a project’s stage. Early in its life, a project might have more expansive governance as it finds its footing, but in practice governance may be tightly controlled by the founding team and community. As the project matures and decentralizes control, it may make sense to introduce some degree of friction in governance – at minimum, requiring large quorums for the most significant decisions.\n\nIncreasing the cost of acquiring voting power\n\nA project can also take steps to make it harder to acquire the voting power needed for an attack. The more liquid the token, the easier it is to require that voting power — so almost paradoxically, projects might want to reduce liquidity for the sake of protecting governance. One could try to reduce the short-run tradability of tokens directly, but that might be technically infeasible.\n\nTo reduce liquidity indirectly, projects can provide incentives that make individual token holders less willing to sell. This can be done by incentivizing staking, or by giving tokens standalone value beyond pure governance. The more value accrues to token holders, the more aligned they become with the success of the project.\n\nStandalone token benefits might include access to in-person events or social experiences. Crucially, benefits like these are high-value to individuals aligned with the project but are useless for an attacker. Providing these sorts of benefits raises the effective price an attacker faces when acquiring tokens: current holders will be less willing to sell because of the standalone benefits, which should increase the market price; yet while the attacker must pay the higher price, the presence of the standalone features does not raise the attacker’s value from acquiring the token.\n\nIncreasing the cost of executing attacks\n\nIn addition to raising the cost of voting power, it’s possible to introduce frictions that make it harder for an attacker to exercise voting power even once they have acquired tokens. For example, designers could require some sort of user authentication for participating in votes, such as a KYC (know your customer) check or reputation score threshold. One could even limit the ability of an unauthenticated actor to acquire voting tokens in the first place, perhaps requiring some set of existing validators to attest to the legitimacy of new parties.\n\nIn some sense, this is exactly the way many projects distribute their initial tokens, making sure trusted parties control a significant fraction of the voting power. (Many Proof of Stake solutions use similar techniques to defend their security — tightly controlling who has access to early stake, and then progressively decentralizing from there.)\n\nAlternatively, projects can make it so that even if an attacker controls a substantial amount of voting power, they still face difficulties in passing malicious proposals. For instance, some projects have time locks so that a coin can’t be used to vote for some period of time after it has been exchanged. Thus an attacker that seeks to buy or borrow a large amount of tokens would face additional costs from waiting before they can actually vote – as well as the risk that voting members would notice and thwart their prospective attack in the interim. Delegation can also be helpful here. By giving active, but non-malicious participants the right to vote on their behalf, individuals who do not want to take a particularly active role in governance can still contribute their voting power toward protecting the system.\n\nSome projects use veto powers that allow a vote to be delayed for some period of time to alert inactive voters about a potentially dangerous proposal. Under such a scheme, even if an attacker makes a malicious proposal, voters have the ability to respond and shut it down. The idea behind these and similar designs is to stop an attacker from sneaking a malicious proposal through and to provide a project’s community time to formulate a response. Ideally, proposals that clearly align with the good of the protocol will not have to face these roadblocks.\n\nAt Nouns DAO, for example, veto power is held by the Nouns Foundation until the DAO itself is ready to implement an alternative schema. As they wrote on their website, “The Nouns Foundation will veto proposals that introduce non-trivial legal or existential risks to the Nouns DAO or the Nouns Foundation.”\n\n* * *\n\nProjects must strike a balance to allow a certain level of openness to community changes (which may be unpopular at times), while not allowing malicious proposals slip through the cracks. It often takes but one malicious proposal to bring down a protocol, so having a clear understanding of the risk tradeoff of accepting versus rejecting proposals is crucial. And of course a high level trade-off exists between ensuring governance security and making governance possible — any mechanism that introduces friction to block a potential attacker also of course makes the governance process more challenging to use.\n\nThe solutions we have sketched here fall on a spectrum between fully decentralized governance and partially sacrificing some ideals of decentralization for the overall health of the protocol. Our framework highlights different paths projects can choose as they seek to make sure governance attacks will not be profitable. We hope the community will use the framework to further develop these mechanisms through their own experimentation to make DAOs even more secure in the future.\n\n***\n\nPranav Garimidi is a rising junior at Columbia University and a Summer Research Intern at a16z crypto.\n\nScott Duke Kominers is a Professor of Business Administration at Harvard Business School, a Faculty Affiliate of the Harvard Department of Economics, and a Research Partner at a16z crypto.\n\nTim Roughgarden is a Professor of Computer Science and a member of the Data Science Institute at Columbia University, and Head of Research at a16z crypto.\n\n***\n\nAcknowledgments: We appreciate helpful comments and suggestions from Andy Hall. Special thanks also to our editor, Tim Sullivan.\n\n***\n\nDisclosures: Kominers holds a number of crypto tokens and is a part of many NFT communities; he advises various marketplace businesses, startups, and crypto projects; and he also serves as an expert on NFT-related matters.\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nCharts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":4049,"crawled_at":1791193899615}
+{"id":10307,"url":"https://gov.uniswap.org/t/temperature-check-fix-the-cross-chain-messaging-bridge-on-arbitrum/18073","domain":"gov.uniswap.org","chapter":"governance_daos","title":"[Temperature Check] Fix the Cross Chain Messaging Bridge on Arbitrum - Temperature Check - Uniswap Governance","text":"[Temperature Check] Fix the Cross Chain Messaging Bridge on Arbitrum\n\nTemperature Check\n\nbharat_eth\n\nNovember 22, 2022, 11:53pm\n\n1\n\nBackground:\n\nOn Ethereum, Uniswap Labs governance consists of a suite of smart contracts. However, in addition to its original deployment on Ethereum L1 mainnet, Uniswap contracts are also deployed on four additional domains - Polygon, Optimism, Celo, and Arbitrum.\n\nUniswap deployments on these domains do not have native access to the on-chain governance system, nor the UNI tokens which grant voting power in this system on Ethereum mainnet; in order for the existing Uniswap governance system to execute proposals governing these deployments, there must be some method of passing governance decisions from Ethereum mainnet to other domains.\n\nPresently, this method has been implemented differently for each of the four chains. The system governing Optimism and Polygon follow similar design principles, and should be functional for passing proposals.\n\nThe system governing the Arbitrum deployment was mis-configured due to a mis-communication between developers, and will require more involved intervention to repair.\n\nProblem:\n\nArbitrum was initially going to allow L1 addresses to pass calls directly to L2 with msg.sender preserved. After realizing security issues with this approach, Arbitrum team instead shifted their approach to use aliasing (this method transforms L1 addresses to be a different address when represented on an L2):\n\nUniswap Labs was not made aware of this change in approach before deploying on Arbitrum. The Uniswap Factory was deployed with the owner set to the same, unaliased address of the L1 Uniswap Timelock contract.\n\nTo verify, see: owner address https://arbiscan.io/address/0x1a9c8182c09f50c8318d769245bea52c32be35bc set at https://arbiscan.io/address/0x1F98431c8aD98523631AE4a59f267346ea31F984#readContract\n\nThis address on Arbitrum is an EOA (not a contract) which nobody has the private key to control\n\nThe governance deployer key on Arbitrum has burned the nonce that could deploy a contract to this address, verifiable here: https://arbiscan.io/address/0x41653c7d61609d856f29355e404f310ec4142cfb\n\nTherefore, nobody can execute governance proposals on Arbitrum in the current state\n\nSolution:\n\nTo fix the cross chain messaging bridge, Arbitrum proposes the following:\n\nFinal governance vote kicks off (after Temperature and Consensus checks pass).\n\nBefore the vote passes, Arbitrum will add a temporary exception to disable address-aliasing for messages from the L1 TimeLock contract, 0x1a9c8182c09f50c8318d769245bea52c32be35bc. Arbitrum will notify the Uniswap community via the Uniswap governance forum once this is done.\n\nOnce the final on-chain governance vote passes, the Uniswap governance contract will send a cross-chain message from the L1 Timelock contract to call setOwner on the L2 Uniswap factory, setting the owner to the L1 Timelock’s address alias, 0x2BAD8182C09F50c8318d769245beA52C32Be46CD.\n\nThis is the L1 Timelock address + the alias offset: 0x1a9c8182c09f50c8318d769245bea52c32be35bc + 0x111\n\n1000000000000000000000000000000001111 as described further at https://developer.offchainlabs.com/arbos/l1-to-l2-messaging#address-aliasing\n\nWe will be able to see when this is completed on-chain. Arbitrum will re-enable aliasing for the L1 Timelock contract address. Once this is complete, cross-chain governance between Uniswap and Arbitrum will be fully functional.\n\nConclusion\n\nUniswap is currently the leading decentralized exchange by TVL on Arbitrum, and if this proposal passes the temperature check and continues along the governance process, it will strengthen the current relationship between the two projects.\n\nLink to snapshot: https://snapshot.org/#/uniswap/proposal/0xa4a21c808b28a61562c6b4ebf5b71c0cd37ee2d630bcbdf91ffaf5f683cc650f\n\n2 Likes\n\ndevinwalsh\n\nNovember 23, 2022, 6:54pm\n\n2\n\nVery supportive of this. Thanks for doing the legwork here @bharat_eth\n\n2 Likes\n\nGFXlabs\n\nNovember 24, 2022, 6:57pm\n\n3\n\nAwesome! We’re looking forward to seeing this fixed so we can set up the 1bp fee tier on Arbitrum. Please let us know if we can help you in any way.\n\n1 Like\n\nbharat_eth\n\nNovember 25, 2022, 6:18pm\n\n4\n\nThanks for the message, I dm’d you!\n\n1 Like\n\nbharat_eth\n\nNovember 25, 2022, 6:18pm\n\n5\n\nThanks for all your help here Devin!\n\n1 Like\n\nKINGsent\n\nNovember 26, 2022, 2:59am\n\n6\n\nnice ,thanks for all you share here !\n\n1 Like\n\neek637\n\nNovember 28, 2022, 8:35pm\n\n7\n\nSounds good, thanks for the work on this. Just looking for one clarification on the process (and mostly out of curiosity) - who is Arbitrum here ?\n\nJust seems like that particular step is doing most of the heavy lifting.\n\nThanks!\n\n1 Like\n\nbharat_eth\n\nNovember 29, 2022, 11:00pm\n\n8\n\nHey! “Arbitrum” would be the integrations engineers who work at Offchain Labs, the parent company that developed Arbitrum One\n\nSpongky\n\nDecember 9, 2022, 11:42am\n\n9\n\nhey, sorry for out of topic, because i can’t find somewhere else to post, but what channel i can post & talke about Uniswap NFT platform? /TY !\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[Consensus Check] Fix the Cross Chain Messaging Bridge on Arbitrum\n\nRequests for Comment\n\n0\n\n4160\n\nNovember 29, 2022\n\n[Temp Check] - Update Crosschain Governance Parameters for Avalanche, MegaETH, Soneium, and X Layer\n\nRequests for Comment\n\n5\n\n271\n\nJuly 9, 2026\n\nDeploy Uniswap v3 to Arbitrum Mainnet\n\nRequests for Comment\n\n48\n\n19120\n\nDecember 1, 2021\n\n[RFC - Update] Deploy Uniswap v3 (1 / 0.3 / 0.05 / 0.01) on BNB Chain (Binance)\n\nRequests for Comment\n\n101\n\n45661\n\nJuly 22, 2026\n\nRFC: Uniswap Universal Governance Module\n\nRequests for Comment\n\n21\n\n13381\n\nNovember 29, 2022","tokens":1421,"crawled_at":1791193911578}
+{"id":10308,"url":"https://docs.sui.io/onchain-finance/examples-patterns","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Example Asset Patterns | Sui Documentation","text":"Reference these examples to learn common asset patterns on Sui, including loyalty tokens, regulated coins, closed-loop tokens, and other digital asset designs.\n\nFixed Supply\nInitialize a coin with a fixed total supply, then lock the supply to prevent further minting using dynamic fields and freezing.\n→\nLoyalty Tokens\nUse the Sui Closed-Loop Token standard to create tokens that are only valid within specific workflows and services. One example of Closed-Loop Tokens is a loyalty token.\n→\nIn-Game Currencies\nUse the Sui Closed-Loop Token standard to create assets that you can use as currency within a game application.\n→\nSoulbound NFTs\nUse Sui Move struct abilities and the Sui framework transfer module to make an NFT soulbound (non-transferable).\n→\nStaking Rewards\nImplement a generic staking pool where users deposit stake tokens and earn reward tokens proportionally over time, using the Synthetix reward-per-token accumulator pattern for O(1) gas cost regardless of staker count.\n→\nNFT Rentals\nAn example that enables users to rent NFTs according to the rules of a provided policy instead of owning them outright.\n→\nKiosk Joining Patterns\nUse the Kiosk standard to join tokenized assets while enforcing transfer policies, and learn how to extend the pattern with custom burn tickets and separated admin capabilities.\n→\nWebAssembly and Template Pattern\nUse the WASM bytecode-template library to serialize, edit, and deserialize Move bytecode in a web environment, enabling you to create and publish new asset tokenization types without recompiling Move source code.\n→","tokens":394,"crawled_at":1791193915858}
+{"id":10309,"url":"https://stack.olas.network/open-autonomy/advanced_reference/commands/autonomy_fetch","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"autonomy fetch - Olas Stack Developer Documentation","text":"autonomy fetch\n\nFetch an agent blueprint or AI agent from a registry using its public ID, hash, or token ID.\nThe autonomy fetch command allows you to download AI agent files from either a local or remote registry.\n\nUsage\n\nautonomy fetch [OPTIONS] PUBLIC_ID_OR_HASH_OR_TOKEN_ID\n\nOptions\n\n--remote\nTo use a remote registry.\n--local\nTo use a local registry.\n--alias TEXT\nProvide a local alias for the agent blueprint or AI agent.\n--agent\nSpecify the package type as agent blueprint (default).\n--service\nSpecify the package type as AI agent.\n--help\nShow the help message and exit.\n--use-celo\nUse the Celo chain profile to find the token with the given token ID.\n--use-base\nUse the Base chain profile to find the token with the given token ID.\n--use-optimism\nUse the Optimism chain profile to find the token with the given token ID.\n--use-arbitrum-one\nUse the Arbitrum One chain profile to find the token with the given token ID.\n--use-gnosis\nUse the Gnosis chain profile to find the token with the given token ID.\n--use-polygon\nUse the Polygon chain profile to find the token with the given token ID.\n--use-ethereum\nUse the Ethereum chain profile to find the token with the given token ID.\n\nTo use these chain profile, you will have to export an environment variable for RPC in <CHAIN_NAME>_CHAIN_RPC format. For example if you want to use ethereum, you will have to export ETHEREUM_CHAIN_RPC.\n\n--use-custom-chain\n\nUse the custom-chain profile to find the token with the given token ID. This profile requires that you define some parameters and contract addresses as environment variables (see also the Olas Protocol documentation for more information):\n\nCUSTOM_CHAIN_RPC : RPC endpoint for the custom chain.\n\nCUSTOM_CHAIN_ID : chain ID.\n\nCUSTOM_COMPONENT_REGISTRY_ADDRESS : Custom Component Registry contract address.\n\nCUSTOM_AGENT_REGISTRY_ADDRESS : Custom Agent Registry contract address.\n\nCUSTOM_REGISTRIES_MANAGER_ADDRESS : Custom Registries Manager contract address.\n\nCUSTOM_SERVICE_MANAGER_ADDRESS : Custom Service Manager contract address.\n\nCUSTOM_SERVICE_REGISTRY_ADDRESS : Custom Service Registry contract address.\n\nCUSTOM_GNOSIS_SAFE_PROXY_FACTORY_ADDRESS : Custom Gnosis Safe multisig contract address.\n\nCUSTOM_GNOSIS_SAFE_SAME_ADDRESS_MULTISIG_ADDRESS : Custom Gnosis Safe Same Address Multisig address.\n\nCUSTOM_SERVICE_REGISTRY_TOKEN_UTILITY_ADDRESS : Custom Service Registry Token Utility address.\n\nCUSTOM_MULTISEND_ADDRESS : Custom Multisend address.\n\nNote\n\nFor L2 chains you are only required to set\n- CUSTOM_SERVICE_MANAGER_ADDRESS,\n- CUSTOM_SERVICE_REGISTRY_ADDRESS,\n- CUSTOM_GNOSIS_SAFE_PROXY_FACTORY_ADDRESS,\n- CUSTOM_GNOSIS_SAFE_SAME_ADDRESS_MULTISIG_ADDRESS and\n- CUSTOM_MULTISEND_ADDRESS.\n\n--use-local\nUse the local chain profile to find the token with the given token ID. This option requires that you have a local Hardhat node with the required contracts deployed.\n\nNote\n\nThe chain profile flags are mutually exclusive.\n\nExamples\n\nFetch the agent blueprint hello_world from the local registry and assign the alias my_hello_world_agent:\n\nautonomy fetch --local --alias my_hello_world_agent valory/hello_world:0.1.0\n\nFetch the agent blueprint hello_world from the default registry (initialized with autonomy init):\n\nautonomy fetch valory/hello_world:0.1.0\n\nFetch the AI agent hello_world from a local registry with an explicit path:\n\nautonomy --registry-path=./packages fetch valory/hello_world:0.1.0 --service --local\n\nFetch the AI agent hello_world from a remote registry using IPFS hash:\n\nautonomy fetch valory/hello_world:0.1.0:bafybeiabtwvve5dfuv464ypgs6jikz5rx3w3fkpej4rzn6x36zxmthuphm --service --remote\n\nFetch the AI agent with the token ID 123 on Gnosis chain:\n\nautonomy fetch 123 --use-gnosis\n\nViewing Remote Registry Files\n\nBefore fetching an AI agent, you can inspect its contents in on IPFS through https://gateway.autonolas.tech/ipfs/<hash>\n\nCommon Issues and Solutions\n\nAI agent Not Found\n\nVerify the AI agent ID is correct\n\nCheck registry connection\n\nEnsure you're using the correct registry flag (--local or --remote)\n\nMissing Dependencies\n\nRun autonomy packages sync to update local packages\n\nCheck AI agent requirements in service.yaml\n\nPermission Issues\n\nVerify write permissions in packages directory\n\nRun with appropriate permissions","tokens":1069,"crawled_at":1791193923695}
+{"id":10310,"url":"https://gov.uniswap.org/t/bug-bounty-vault-proposal-by-hats-finance/21908","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Bug Bounty Vault Proposal by Hats Finance - Requests for Comment - Uniswap Governance","text":"Bug Bounty Vault Proposal by Hats Finance\n\nRequests for Comment\n\nFav_Truffe\n\nSeptember 8, 2023, 1:18pm\n\n1\n\nTLDR\n\nThis is a proposal for Uniswap to collaborate with Hats.finance to create an on-chain, free, non-custodial, scalable and permissionless incentives pool for hackers/auditors to protect the Uniswap smart contracts.\n\nAbstract\n\nThe direct losses from hacks and exploits between 2020-2022 are above $15B, and yet, the solutions currently being offered are not decentralized, permissionless, scalable, and continuous and open to everybody like Uniswap is.\n\nThis proposal aims to create an incentives pool on Hats Protocol for hackers/auditors to help protect the Uniswap smart contracts. The goal of the vault is to incentivize responsible vulnerability disclosure for Uniswap. Liquidity can be added (with $UNI and/or yield-bearing tokens) permissionless and LPs will be rewarded with $HAT tokens once the liquidity mining program is launched.\n\nMotivation\n\nHats.finance is an on-chain decentralized bug bounty platform specifically designed to prevent crypto-hack incidents by offering the right incentives. Additionally, Hats.finance allows anyone to add liquidity to a smart bug bounty. Hackers can disclose vulnerabilities responsibly without KYC & be rewarded with scalable prizes & NFTs for their work.\n\nSmart bug bounty programs are a win-win for everyone. They can be created easily with a few on-chain transactions (it takes less than 1 hour to set up a vault on Hats), and are free of charge. Hats will only charge a fee once an incident has been successfully mitigated. The protocol will retain 10% of the payout as fee from the security researcher. Scenarios of an exploit are way more costly and can cause irreversible damage. More importantly, the bounty program is transparent, decentralized, and gives power to the community of the project.\n\nOn-chain submission:\n\nWith the values of Ethereum, which are lighting our way, we decided to take a different approach to bug bounty compared to the traditional and centralized bug bounty platforms.\n\nThe submitter writes a detailed vulnerability description on Hats dApp. The submission is encrypted with the project PGP key. The user hashes the encrypted description (automatically) and sends a transaction on-chain with that Hash (only the Hash of the encrypted report is going on-chain), While sending the encrypted message to the routing bot.\n\nThe tx fee acts as a spam filter and can be set to a higher value (in the future).\n\nThe routing bot verifies that the Hash of the encrypted message was published on-chain and publishes the encrypted message to the committee group together with a link to a front-end open source tool to decrypt the messages that are stored on IPFS that is part of Hats dApp.\n\n1600×900 45.8 KB\n\nSpecification\n\nIn case that the proposal gets accepted, Uniswap is expected to:\n\n1- Choose and set up a committee\n\n2- Vote for DAO participation amount\n\nOnboarding action items:\n\nChoosing a committee: The committee is preferably the public multisig contract of Uniswap or a multisig specifically set up to manage the bounty program.\n\nThe Committees responsibility:\n\nTriage incoming vulnerability reports/claims from auditors/hackers (get back to the reporter within 12 hours).\n\nApprove claims within a reasonable time frame (Max. of 6 days)\n\nSet up repositories and contracts under review. (A list of all contracts covered by the bounty program separated by severity)\n\nRationale\n\nThe key advantage of Hats solution compared to traditional, centralized bug bounty services:\n\nBug bounty vaults are loaded with the native or yield bearing token of each project. Reducing the free floating supply while giving the token additional utility.\n\nScalable bounty network — vault TVL increases with success / token appreciation of the project.\n\nOpen & Permissionless — Anyone can participate in the protection of an asset they are a stakeholder of and any hacker, anywhere in the world, can participate anonymously when disclosing exploits (no KYC needed)\n\nIn the future when providing liquidity (taking risk) every depositor could earn $HAT tokens.\n\nContinuous — As long as tokens are locked in the vault, hackers are incentivized to disclose vulnerabilities through Hats, instead of exploiting the project.\n\nAdditional advantages of deployment of the existing Uniswap bug bounty program on Hats Protocol:\n\nUniswap can reach out to many more security researchers (aka white hat hackers) with a bounty on Hats protocol and each scrutiny will make Uniswap safer.\n\nUniswap can fund the bug bounty vault on Hats with its own native token ($UNI or yield bearing token)\n\nThe bounty reward for the submitter is not paid at once to reduce the price pressure on the project token.\n\nSince Uniswap DAO will be farming $HAT tokens with its bounty (after TGE), it’s a cost negative opportunity for Uniswap DAO.\n\nKey Examples\n\nA security researcher recently found a critical severity within Premia Finance’s staking contracts and got rewarded $70k for his responsible disclosure:\n\nhttps://twitter.com/HatsFinance/status/1663243357160890369)\n\nIn one of the recent audit competitions, the security researchers could find 3 critical severities in Raft Finance’s code in a 7 days long audit contest even if the project went under an extensive audit by one of the top-tier auditing firms in the space:\n\nhttps://hatsfinance.medium.com/raft-finance-audit-competition-final-note-16e87dce23a2\n\nA security researcher could find a medium severity vulnerability in HOPR contracts:\n\nhttps://twitter.com/hoprnet/status/1666430539656581120\n\n1 Like\n\nDoo_StableLab\n\nSeptember 9, 2023, 1:24pm\n\n2\n\nCan you share some light on current Uniswap’s bug bounty programs and in your opinion, why it’s not sufficient?\n\nI feel like all of those can be done in the current model? For example, if needed, give out in $UNI token or not paying the reward at once?\n\nThis is a misleading comment as we don’t know the price of $HAT in the future. Therefore, if the team indeed believes that “cost negative opportunity” then we suggest the team guarantees that if the cost is greater than the token farmed, the team provides needed fund to fill the gap.\n\nFav_Truffe\n\nSeptember 10, 2023, 7:42am\n\n3\n\nHey @Doo_StableLab! Thanks a lot for taking the time to reflect.\n\nIn my humble opinion, Uniswap, as the market leader in DeFi, should be at the forefront to support decentralization ethos. Otherwise, why use Uniswap instead of centralized Web2 alternatives? I am of the opinion that it would contribute a lot to the wider ecosystem if Web3 projects, especially top-notch ones like Uniswap, would prioritize Web3 native products over centralized/Web2 alternatives.\n\nHats Finance is very well known in security and Uniswap’s deployment of its bug bounty program on Hats protocol would potentially enrich the target audience.\n\nSecondly, Hats Finance provides the security researchers with decentralized dispute court (in partnership with Kleros court). Accordingly, security researchers would be more comfortable with submitting vulnerabilities on Hats protocol from a game-theory perspective with the idea that a specialized third party court will see their case if they are treated unfairly.\n\nYou are right! I made a mistake while editting the proposal. The way it should be was “Since Uniswap can use any yield-bearing token to fund the bug bounty vault, there will not be any opportunity-cost for Uniswap.”\n\nAdditionally, potentially farming $HAT token would be another advantage over the current implementation of Uniswap bug bounty program.\n\nAppreciate the questions, looking forward to hearing more\n\n1 Like\n\nDoo_StableLab\n\nSeptember 10, 2023, 4:30pm\n\n4\n\nI think it’s up to the community to decide and Uniswap indeed supports many web3 options, but at the end of the day is about what is more effective and provide better security. For example, using the same logic, although Hats Finance is a web3 project, the links you shared above are Medium and Twitter, which are both Web2.\n\nSo once again, beside web2 vs web3 difference, the focus should be on whether there are issues with the current Uniswap bug bounty program. This will be helpful to the community to evaluate.\n\nIs there actually statistics or case study that prove this? Also, if that’s true, considering there are also many false vulnerability reports, wouldn’t this swarm the Uniswap community especially if those reporters repetitively request for Kleros court? I assume there’s some mechanism to prevent this?\n\nI think we have different opinions about what is opportunity cost. Because Uniswap team can just have yield-bearing token in its treasury. In fact, Uniswap has to bear potential risk of exploit with Hats Finance, which the Hats team yourselves are aware of. It’s a good practice to defend your own of course, but just clarifying that it’s not risk free vault. And I noticed the team actually paid 40k for own, which included one high severity.\n\nimage1716×445 31.2 KB\n\nThe high severity was this one which titled “First depositor can partially steal deposits and DoS vaults”\n\nhttps://github.com/hats-finance/hats-contracts/pull/393\n\nTherefore, this is a risk the Uniswap community should consider. In addition, as Uniswap is a top 5 DeFi protocol, if integrated, Uniswap will be their biggest DeFi partner, which undoubtedly would be beneficial for Hats Finance community and development. Thus, I recommend the Uniswap governance to push for fairer deals such as Hats team matching Uniswap’s contributing fund (if approved) and/or rebating the 10% payout.\n\nFav_Truffe\n\nSeptember 10, 2023, 4:58pm\n\n5\n\nSorry, you are right. Here is the link to our dApp: https://app.hats.finance/bug-bounties\n\nAs for more differences; Hats Finance has an encrypted communication feature for security researchers and project teams and therefore nobody (including the Hats team) can see the vulnerability report. There is no third party risk as in the case of Immunefi.\n\nSecondly, bug bounty vaults on Hats Finance are open to everybody. Accordingly, investors, DAO members, community members, etc. can deposit to the vault and top up the bounty amount (make it more incentivizing for security researchers).\n\nThirdly, Hats Finance is on-chain and therefore the submissions require a transaction fee. This fee itself is acting as a spam filter but if deemed not enough, Uniswap can increase the fee to submit a report to create a paywall (to increase the efficiency of spam filter). This is very important because its widely known that some web2 bug bounty companies are paying some security researchers to submit reports (to sell triage service to the projects).\n\nFourthly, Uniswap DAO can potentially farm $HAT tokens (after TGE) with its bug bounty vault.\n\nFifthly, there is not any monthly/quarterly/yearly fee to host the bug bounty program on Hats.\n\nSixthly Hats Finance, as a decentralized protocol, is anon-friendly. Considering the fact that white hatting might be troublesome in some countries and some white hats are very sensitive about their privacy, Hats has the capability to target more security researchers.\n\nSecurity researcher has to pay an upfront fee to escalate the case and if the court does not agree with the security researcher, he loses this fee.\n\nSo, the bug bounty and audit competition are 2 different products. The high severity finding you mentioned was found at the audit competition for Hats V2 contract. For your information, the V2 contracts were already audited by 3 different centralized auditing firms prior to the competition (and we paid $160k in total for these audits). So, the finding was not at our mainnet contracts.\n\nHats Finance does not charge any fees to host the bug bounty program. Therefore, Hats Finance benefits financially only after a valid vulnerability report payout.\n\nLast but not the least, I do not want to consider Uniswap partnership as a paid promotion with all due respect.\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[RFC] - Adopt The SEAL Safe Harbor Agreement\n\nRequests for Comment\n\n15\n\n610\n\nDecember 20, 2024\n\n[Temp Check] - Adopt The SEAL Safe Harbor Agreement\n\nTemperature Check\n\n1\n\n239\n\nDecember 17, 2024\n\n[Governance Proposal] - Adopt The SEAL Safe Harbor Agreement\n\nRequests for Comment\n\n4\n\n321\n\nJanuary 16, 2025\n\n[RFC] Uniswap Grants Program v0.1\n\nRequests for Comment\n\n35\n\n20167\n\nFebruary 9, 2022\n\nGFX Labs - Delegate Communication Thread\n\nDelegation Pitch\n\n27\n\n1504\n\nDecember 8, 2025","tokens":3113,"crawled_at":1791193929314}
+{"id":10311,"url":"https://docs.dydx.xyz/concepts/trading/accounts","domain":"docs.dydx.xyz","chapter":"defi_protocols","title":"Accounts and Subaccounts – dYdX Documentation","text":"Accounts and subaccounts serve as identifiers in the dYdX ecosystem.\n\nMain Account\n\nA (main) account is associated with a public-private keypair, and with a trader's on-chain identity.\n\nKnown publicly and associated with an address;\n\nHolds tokens/assets that are sent to/from the chain, including tokens used for gas and collateral;\n\nGas for transactions is used from the main account;\n\nMain accounts cannot trade;\n\nSeveral main accounts can be derived from the same mnemonic phrase. Each user main account is completely independent and private/unlinkable from each other.\n\nSubaccounts\n\nSubaccounts provide a way to isolate funds and manage risk within an account. They are used to trade.\n\nEach main account can have 128,001 subaccounts;\n\nEach subaccount is uniquely identified using as subaccount ID of (main account address, integer);\n\nOnce you deposit funds to a valid subaccount ID, the subaccount will automatically be created;\n\nOnly the main account can send transactions on behalf of a subaccount;\n\nSubaccounts do not require gas (no gas is used for trading);\n\nSubaccounts require collateral token (currently USDC) in order to trade.","tokens":285,"crawled_at":1791193931880}
+{"id":10312,"url":"https://www.metaplex.com/docs/smart-contracts/core/sdk/rust","domain":"www.metaplex.com","chapter":"docs","title":"Rust SDK | MPL-Core","text":"Metaplex provides a Rust library that can be used to interact with the MPL-Core program. The Rust library can be used in rust scripts/builds as well as onchain programs via CPI instructions. For Anchor program integration, see Using Core in Anchor for anchor, anchor-0-32, and Rust toolchain requirements.\nInstallation\nThe MPL-Core Rust SDK can be used in both scripts/desktop/mobile applications as well as with Solana onchain programs.\ncargo add mpl-core\n\ncrates.io\nGet started with our JavaScript library based on the Umi framework.\n\ndocs.rs\nThe Rust SDK typedoc platform.\n\nLocal Scripts\nFor local scripts is recommended to use the Builder versions of all the instructions listed. These builders abstract a lot of the work for you and return a instruction that can be added to a transaction. A list of all Core instructions can be found here: Metaplex Core - Rust Instructions For a more comprehensive guide on using Rust check out the Metaplex Rust SDKs Guide page.\nCreateV1Builder - Example\nuse mpl_core::instructions::CreateV1Builder;\n\nuse solana_client::rpc_client;\n\nuse solana_sdk::{signature::Keypair, signer::Signer, transaction::Transaction};\n\npub fn create_asset() {\n\nlet rpc_client = rpc_client::RpcClient::new(\"https://api.devnet.solana.com\".to_string());\n\nlet keypair_path = \".../my-key.json\"\n\nlet keypair = solana_sdk::signature::read_keypair_file(keypair_path).unwrap();\n\nlet asset = Keypair::new();\n\nlet create_asset_ix = CreateV1Builder::new()\n\n.asset(asset.pubkey())\n\n.payer(keypair.pubkey())\n\n.name(\"My Asset\".into())\n\n.uri(\"https://example.com/my-asset.json\".into())\n\n.instruction();\n\nlet signers = vec![&asset, &keypair];\n\nlet last_blockhash = rpc_client.get_latest_blockhash().await.unwrap();\n\nlet create_asset_tx = Transaction::new_signed_with_payer(\n\n&[create_asset_ix],\n\nSome(&keypair.pubkey()),\n\n&signers,\n\nlast_blockhash,\n\n);\n\nlet res = rpc_client.send_and_confirm_transaction(&create_asset_tx).await.unwrap();\n\nprintln!(\"Signature: {:?}\", res)\n\n}\n\nCPI (Cross Program Invocation)\nPerforming CPI instructions from your own programs can be achieved easily by using the CpiBuilder version of an instruction function that can be found for all instructions in the mpl-core Rust crate. A list of all Core instructions can be found here: Metaplex Core - Rust Instructions For a more comprehensive guide using Metaplex crates to create CPI instructions check out the How to CPI into a Metaplex Program guide page.\nCreateV1CpiBuilder - Example\nCreateV1CpiBuilder::new()\n\n.asset(context.accounts.asset)\n\n.collection(context.accounts.collection)\n\n.authority(context.accounts.authority)\n\n.payer(context.accounts.payer)\n\n.owner(context.accounts.owner)\n\n.update_authority(context.accounts.update_authority)\n\n.system_program(context.acccounts.system_program)\n\n.data_state(input.data_state.unwrap_or(DataState::AccountState))\n\n.name(args.asset_name)\n\n.uri(args.asset_uri)\n\n.plugins(args.plugins)\n\n.invoke()","tokens":730,"crawled_at":1791193933623}
+{"id":10313,"url":"https://stack.olas.network/open-autonomy/advanced_reference/developer_tooling/dev_mode","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Dev mode - Olas Stack Developer Documentation","text":"Dev mode\n\nThe Open Autonomy framework comes with developer mode (dev mode) tooling to enable faster AI agent developing and debugging. The dev mode supports running AI agents with a number of functionalities enabled:\n\nHot reload, which enables hot code swapping and reflects changes on the agent blueprint code as well as on the local open-aea repository without rebuilding or restarting the containers manually.\n\nHardhat Instance, which enables the inclusion of a pre-configured Hardhat Instance image in the deployment, which can be used as a test blockchain.\n\nACN Instance, which enables inclusion of a pre-configured ACN Instance image, which can be used to test various agent communication functionalities, for example establishing the Tendermint network at the startup.\n\nExecution replay of a previous agent instance in the AI agent.\n\nBenchmark the performance of an AI agent.\n\nBefore starting this guide, ensure that your machine satisfies the framework requirements and that you have followed the set up guide. As a result you should have a Pipenv workspace folder.\n\nBuild and run an AI agent in dev mode\n\nFetch the AI agent. Fetch the Hello World AI agent from the remote registry.\n\nautonomy fetch valory/hello_world:0.1.0:<hash> --service\n\nBuild the deployment. Within the AI agent folder, execute the command below to build the AI agent deployment in dev mode, including a pre-configured Hardhat instance.\n\nautonomy deploy build --dev --packages-dir ~/service/packages --open-aea-dir ~/git/open-aea/ --use-hardhat -ltm\n\nThis will create a deployment environment in dev mode within the ./abci_build_* folder.\n\nYou must modify the paths in the command above appropriately, pointing to:\n\nthe path to the local registry (/packages directory),\n\nthe path to the local Open AEA repository.\n\nIf you don't want to specify the open-aea repository manually, you can install the open-aea in editable mode using\n\npip3 install -e PATH_TO_OPEN_AEA_REPOSITORY\n\nSame thing goes for packages, if you're already in the packages/ directory (eg. running the command from packages/author/services/ai_agent) you don't have to specify the value for --packages-dir flag explicitly.\n\nNote: When building development deployments you don't have to define keys manually, autonomy generates the keys automatically in development mode. You can still specify the keys file if you already have one and you're planning on using it.\n\nRun the AI agent. Navigate to the deployment environment folder (./abci_build_*) and run the deployment locally.\n\ncd abci_build_*\nautonomy deploy run\n\nYou can cancel the local execution at any time by pressing Ctrl+C.\n\nHot reload\n\nOnce the agent instances are running, you can make changes to the agent blueprint's code as well as the local Open AEA repository, and it will trigger the AI agent restart.\n\nThe trigger is caused by any Python file closing in either the service/packages or the open-aea/ directory. So even if you haven't made any change and still want to restart the AI agent, just open any Python file press Ctrl+S or save it from the file menu and it will trigger the restart.\n\nHardhat instance\n\nBy default the command that builds the AI agent deployment (autonomy deploy build) only includes the agent instance nodes and the Tendermint nodes. If you want to include a local Hardhat node as a test blockchain for the ledger connection, you can do so by using the --use-hardhat flag in that command.\n\nThe deployment setup will include a Hardhat node (image valory/open-autonomy-hardhat) using hardhat as container name. Therefore, in order to use this node, you must set a ai-agent-level override so that the valory/ledger connection address is set to http://hardhat:8545.\nYou can achieve this by editing the AI agent configuration file service.yaml as follows:\n\nservice.yaml# (...)\n---\npublic_id: valory/ledger:0.1.0\ntype: connection\nconfig:\nledger_apis:\nethereum:\naddress: ${LEDGER_RPC:str:http://hardhat:8545}\n\nAlternatively, you can leave the default service.yaml and export an environment variable:\n\nservice.yaml# (...)\n---\npublic_id: valory/ledger:0.1.0\ntype: connection\nconfig:\nledger_apis:\nethereum:\naddress: ${LEDGER_RPC:str:http://localhost:8545}\n\nexport LEDGER_RPC = http://hardhat:8545\n\nIf you require specific custom contracts to test your AI agent, read the guide to include custom contracts.\n\nACN instance\n\nYou can also include an ACN node for agent communication using the --use-acn flag in autonomy deploy build.\n\nThe deployment setup will include an ACN node (image valory/open-acn-node) using acn as container name. Similarly as above, in order to use this node you must set a ai-agent-level override so that the valory/p2p_libp2p_client connection parameters are set to the appropriate values.\nYou can achieve this by editing the AI agent configuration file service.yaml as follows:\n\nservice.yaml# (...)\n---\npublic_id: valory/p2p_libp2p_client:0.1.0\ntype: connection\nconfig:\nnodes:\n- uri: acn:11000\npublic_key: 03c74dbfbe7bbc1b42429f78778017a3cd7eaf9d59d1634c9505a3f7c1a9350e71\ncert_requests:\n- identifier: acn\nledger_id: ethereum\nmessage_format: '{public_key}'\nnot_after: '2025-01-01'\nnot_before: '2024-01-01'\npublic_key: 03c74dbfbe7bbc1b42429f78778017a3cd7eaf9d59d1634c9505a3f7c1a9350e71\nsave_path: .certs/acn_cosmos_11000.txt\nis_abstract: false","tokens":1324,"crawled_at":1791193943423}
+{"id":10314,"url":"https://gov.uniswap.org/t/ugp-v3-bug-bounty-contribution/11179","domain":"gov.uniswap.org","chapter":"governance_daos","title":"UGP v3 Bug Bounty contribution - Temperature Check - Uniswap Governance","text":"UGP v3 Bug Bounty contribution\n\nTemperature Check\n\nkenneth\n\nMarch 26, 2021, 3:44pm\n\n1\n\nWith the announcement of Uniswap v3, the Uniswap Labs team has posted a $500,000 bug bounty program for the reporting of any bugs that can lead to the potential loss of LP funds as well as discretionary rewards for lower severity bugs.\n\nWe believe the security of v3 contracts is critical to continuing to grow the UNI ecosystem around, which is part of the stated mission of the UNI Grants Program that governance approved in Q4 2020.\n\nThe UNI Grants Program would like to double the UGP Q2 budget to $1.5M in order to match the Uniswap Labs bug bounty program with $500,000 worth of UNI from the Committee multisig. As these funds were not a part of our original proposal, we are outlining our rationale and process for its approval via a Snapshot temperature check.\n\nRationale:\n\nIn Q4 2020, UNI governance approved a transfer of $1.5M from treasury to the Uniswap Grants Program multisig.\n\nSince then, the following has happened:\n\nIn Q1 2021, UGP has successfully funded 23 projects, deploying the targeted $750,000 worth of UNI. You can read more about the details of our Q1 grants here.\n\nIn Q2, UGP is on track to deploy $750,000 worth of UNI and will be updating our process to make grant approvals more frequent. Read more on our request for proposals for Q2 here.\n\nThe value of UNI in the multisig has grown from approximately ~$1.5M to ~$14M at the time of this writing\n\nSeparately, v3 introduces new market dynamics and customizable liquidity provisions with both increased gains and associated risk, putting more pressure to ensuring the security of v3 contracts. While several audits have been completed, there may be bugs and exploits that have been overlooked.\n\nGiven the mission of the grants program, our progress to date, and the importance of security for users funds, we believe the bounty match would be an appropriate use of funds entrusted to us.\n\nProcess:\n\nThere has not yet been a precedent set for governance decisions that do not require any code or additional actions from treasury. Therefore to approve the match, we are seeking community support through a Snapshot temperature check.\n\nWe’re employing an open voting period of 7 days starting today, 03/26/21 until 04/02/21, after which UGP will act according to the majority vote!\n\nUnlike a full governance proposal, this process is meant to be lightweight because the funds are already sitting in the UGP multisig and as such, there will be no minimum threshold for voting. Please submit your votes within the next 7 days here and let us know your thoughts on the lite-proposalTM!\n\nSnapshot Temp-Check\n\n16 Likes\n\ndennisonb\n\nMarch 26, 2021, 5:03pm\n\n2\n\nI really like this idea, but I wonder how it would be implemented: Would the grants committee be responsible for determining what gets a bug bounty payout? Would the current funds be delegated to a different committee to handle issues like this?\n\n1 Like\n\nkenneth\n\nMarch 26, 2021, 5:21pm\n\n3\n\nGreat question! We have to acknowledge our own blindspots in our technical expertise. UGP seeks to match the bounties 1:1 with the Uniswap Labs team instead of us evaluating the individual submissions.\n\nv3 brings a lot of attention to something new both on the contracting side as well as the financial side so security is of utmost importance. Looking at past contracts and their exploits, we’d want to ensure users are as safe as can be. With UNI price having increased quite a decent amount, we wouldn’t be asking for more funds, just approval from the community to spend what’s already in the multisig for what we feel is quite important.\n\n2 Likes\n\ng_dip\n\nMarch 26, 2021, 8:46pm\n\n4\n\nI definitely support bigger bounties - it’s going to be ~$4B soon enough so we may as well do the best we can before launch.\n\nCan I suggest that instead of a simple matching program, you expand the audience of hackers by using another platform to run a parallel program? For instance, in the launch process of Multi-Collateral Dai we had success with HackerOne (they detected a critical bug).\n\n6 Likes\n\nkenneth\n\nMarch 30, 2021, 5:29pm\n\n5\n\nyes would love to discuss! DMing you!\n\n2 Likes\n\nbrilj310\n\nOctober 23, 2021, 6:17am\n\n7\n\nWell yes. Now I am actualy unemploied and I am opening my own company. Until then I have plenty of time to work on your domand. So, doo tell what bug you want me to eliminate and where. It shouldn’s take long if the code is not codependent to itself\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[Temperature Check] Reinstating UGP v0.2 with existing funds\n\nTemperature Check\n\n16\n\n7234\n\nJuly 15, 2021\n\n[RFC] Uniswap Grants Program v0.1\n\nRequests for Comment\n\n35\n\n20167\n\nFebruary 9, 2022\n\nBug Bounty Vault Proposal by Hats Finance\n\nRequests for Comment\n\n4\n\n2203\n\nSeptember 10, 2023\n\n[Consensus Check] Create the Uniswap Foundation\n\nConsensus Check\n\n0\n\n5439\n\nAugust 10, 2022\n\n[Governance Proposal] Create the Uniswap Foundation\n\nRequests for Comment\n\n0\n\n7548\n\nAugust 17, 2022","tokens":1250,"crawled_at":1791193946811}
+{"id":10315,"url":"https://docs.sui.io/onchain-finance/examples-patterns/staking-rewards","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Staking Rewards | Sui Documentation","text":"This example implements a generic staking pool where users deposit Coin<S> (stake token) and earn Coin<R> (reward token) over time, proportional to their share of the pool. It uses the Synthetix reward-per-token accumulator pattern for O(1) reward calculation regardless of how many stakers exist.\n\nThe same contract works for yield farming, liquidity mining, fee and revenue sharing, and other pro-rata, time-weighted token distribution use cases.\n\ninfo\nStaking in this context refers to the DeFi yield-farming pattern (deposit tokens, earn rewards), not proof-of-stake consensusConsensusThe process by which the majority of nodes agree on the current state of the network staking.\n\nWhen to use this pattern​\n\nUse this pattern when you need to:\n\nDistribute reward tokens proportionally to depositors over a configurable time window.\n\nSupport an unbounded number of stakers without increasing gasGasThe computational cost of execution and object storage for a transaction. costs per interaction.\n\nGive users a transferable receipt objectObjectThe basic unit of storage on Sui. that represents their position and can compose with other protocols (for example, as collateral).\n\nProvide admin controls for funding reward schedules, pausing deposits, and recovering unused rewards.\n\nGuarantee solvency structurally so the pool can never promise more rewards than it holds.\n\nFor token vesting (releasing tokens to specific recipients on a schedule rather than proportional distribution to a pool), see Token vesting strategies.\n\nWhat you learn​\n\nThis example teaches:\n\nReward-per-token accumulator: A single number tracks total reward earned per staked token since the pool began. Each user stores a snapshot of this value when they last interacted. The difference between the current value and the snapshot determines their earnings, with no loops or iteration.\n\nBounded emission windows: The admin funds a reward period with a specific duration. The accumulator stops advancing after the window closes, making solvency a structural guarantee rather than an operational one.\n\nReceipt-based positions: Each staker receives a StakeReceipt owned object that records their deposit amount and accumulator snapshot. The receipt is the position. It can be transferred, used as collateral, or composed in programmable transaction blocksProgrammable transaction blocksDefine all user transactions on Sui..\n\nCapability-gated administration: An AdminCap object authorizes pool operations like funding rewards and pausing. The cap can be transferred to a multisigMultisigMulti-signature transactions that require multiple keys for authorization. or burned to make the pool permanently immutable.\n\nComposable function signatures: Every public function returns its results (capabilities, receipts, coins) instead of transferring internally, making the contract fully composable in programmable transaction blocks.\n\nArchitecture​\n\nThe contract creates three onchain object types with distinct ownership models.\n\nObjectAbilitiesOwnershipCreated byDestroyed by\nStakingPool<S, R>\nkey\nShared\ncreate_pool\nNever\n\nStakeReceipt<S, R>\nkey, store\nOwned (transferable)\nstake\nunstake, emergency_unstake\n\nAdminCap<S, R>\nkey, store\nOwned (transferable)\ncreate_pool\ndestroy_admin_cap\n\nThe StakingPool is a shared object that holds all staked balances, the reward balance, the emission schedule, and the reward-per-token accumulator. The StakeReceipt is an owned object given to each staker, recording their deposit amount and a snapshot of the accumulator. The AdminCap authorizes administrative operations and is bound to a specific pool by ID.\n\nThe following diagram shows the lifecycle of a staking pool.\n\nHow the accumulator works​\n\nThe core challenge in reward distribution is calculating each staker's share without iterating through all stakers on every interaction. The accumulator solves this with a single number called reward_per_token (RPT) that answers: \"For every single token staked in this pool, how much total reward has been earned since the beginning?\"\n\nEvery time someone interacts with the pool (stake, unstake, claim), the contract updates this number:\n\nnew_RPT = old_RPT + (time_elapsed × reward_rate / total_staked)\n\nTo calculate how much a specific user earned, subtract their snapshot from the current value:\n\nuser_reward = user_staked_amount × (current_RPT − user_snapshot_RPT)\n\nThis is O(1) regardless of how many stakers exist.\n\nBecause MoveMoveAn open source programming language used for all activity on Sui. has no floating-point numbers, all RPT math is scaled by a precision factor of 1018. The contract multiplies by this factor before dividing, then divides by it when converting back to token amounts. This gives 18 decimal places of accuracy in pure integer arithmetic.\n\nEmission window and solvency​\n\nAccrual is bounded by an explicit emission window [start_timestamp, stop_timestamp]. Outside this window, the accumulator stops advancing. The window is set by notify_reward_amount(coin, duration_ms), which derives reward_rate = (coin_amount + leftover) / duration_ms and asserts rate × duration ≤ reward_balance. This makes solvency structural: any rewards the math can accrue, the pool can pay.\n\nPrerequisites\n\nInstall the Sui CLI.\n\nCreate an address and fund it with SUI for gas.\n\nReference implementation​\n\nA complete, tested implementation lives in staking-contract-template. Build it, run its tests, and publish it as-is, or lift the accumulator logic into a packagePackageSmart contracts on Sui. of your own:\n\n$ sui client publish --gas-budget 100000000\n\nThe package leaves [dependencies] empty in Move.toml, so the framework version resolves from your active environment. Record the package ID and the StakingPool and AdminCap object IDs from the output.\n\nCalling the contract​\n\nEvery entry point is a public fun that returns its objects instead of transferring them internally. That makes the moduleModuleA component of a Move package that defines interaction with on-chain objects. composable in programmable transaction blocks, but it also means a plain sui client call fails with UnusedValueWithoutDrop. Use sui client ptb and transferTransferChanging the owner of an asset. the results explicitly.\n\nCreate a pool​\n\nCreate a new staking pool and receive the AdminCap. Replace PKG with your package ID, and STAKE_TYPE and REWARD_TYPE with the full type identifiers for your stake and reward tokens.\n\n$ sui client ptb \\\n--move-call PKG::staking::create_pool '<STAKE_TYPE,REWARD_TYPE>' \\\n--assign cap \\\n--transfer-objects '[cap]' @YOUR_ADDRESS\n\nFund the reward schedule​\n\nFund the pool with reward tokens and start the emission window. DURATION_MS is the emission window length in milliseconds.\n\n$ sui client ptb \\\n--move-call PKG::staking::notify_reward_amount '<STAKE_TYPE,REWARD_TYPE>' \\\n@ADMIN_CAP_ID @POOL_ID @REWARD_COIN_ID DURATION_MS @0x6\n\nStake tokens​\n\nDeposit tokens and receive a StakeReceipt.\n\n$ sui client ptb \\\n--move-call PKG::staking::stake '<STAKE_TYPE,REWARD_TYPE>' \\\n@POOL_ID @STAKE_COIN_ID @0x6 \\\n--assign receipt \\\n--transfer-objects '[receipt]' @YOUR_ADDRESS\n\nClaim rewards​\n\nWithdraw earned rewards while keeping your position open.\n\n$ sui client ptb \\\n--move-call PKG::staking::claim_rewards '<STAKE_TYPE,REWARD_TYPE>' \\\n@POOL_ID @RECEIPT_ID @0x6 \\\n--assign reward \\\n--transfer-objects '[reward]' @YOUR_ADDRESS\n\nUnstake​\n\nFully exit the position. The function consumes the receipt and returns principal plus accrued rewards.\n\n$ sui client ptb \\\n--move-call PKG::staking::unstake '<STAKE_TYPE,REWARD_TYPE>' \\\n@POOL_ID @RECEIPT_ID @0x6 \\\n--assign out \\\n--transfer-objects '[out.0, out.1]' @YOUR_ADDRESS\n\nKey code highlights​\n\nStakingPool shared object\nThe pool is a shared object parameterized on <S, R> (stake and reward token types). It holds the total staked amount, the reward-per-token accumulator (reward_per_token_stored), the emission rate and window (reward_rate, start_timestamp, stop_timestamp), and both token balances. The paused flag lets the admin halt new deposits without locking existing principal.\n\nStakeReceipt owned object\nEach staker receives a receipt recording their staked amount, the pool's accumulator value at their last interaction (reward_per_token_paid), and any checkpointed pending_rewards. The pool: ID field binds the receipt to its pool, preventing cross-pool attacks. The key + store abilities make the receipt transferable, enabling composability (for example, using it as collateral in another protocol).\n\nAccumulator calculation\nThe calculate_reward_per_token function is the core of the Synthetix pattern. If nobody is staking, the accumulator does not advance (avoids division by zero). Otherwise, it computes time elapsed since the last update, multiplied by the reward rate and the precision factor, divided by total staked. The result accumulates onto the stored value. The last_applicable_time helper clamps the current time to the emission window so accrual stops when the window closes.\n\nFunding the emission schedule\nnotify_reward_amount is the admin's primary operation. It finalizes accrual at the old rate, joins the new reward coin into the pool, and computes a new rate that covers both fresh funding and any leftover from an active period. The solvency assertion rate × duration ≤ reward_balance structurally prevents the pool from ever promising more than it holds. This function replaces the emission schedule each time it is called, rolling leftover into the new window.\n\nStaking and receipt creation\nThe stake function checks the pool is not paused, updates the accumulator, adds the user's tokens to both the pool balance and total_staked, and creates a receipt with the current accumulator as its snapshot. The receipt is returned (not transferred), so it composes in programmable transaction blocks.\n\nEmergency unstake escape hatch\nemergency_unstake guarantees principal recovery by skipping all reward math. It takes no Clock reference and never touches the reward balance, so it works even in a hypothetically underfunded state. The user forfeits any accrued rewards in exchange for a guaranteed exit. This follows the MasterChef emergencyWithdraw pattern.\n\nMystenLabs/staking-contract-template/staking/sources/staking.move\n1module staking::staking;\n2\n\n3use staking::events;\n4use sui::balance::{Self, Balance};\n5use sui::clock::Clock;\n6use sui::coin::Coin;\n7\n\n8// ── Constants ────────────────────────────────────────────────\n9const PRECISION: u128 = 1_000_000_000_000_000_000;\n10const MAX_U64: u64 = 0xFFFF_FFFF_FFFF_FFFF;\n11\n\n12// ── Errors ──────────────────────────────────────────────────\n13/// AdminCap presented does not bind to the pool being operated on.\n14const EWrongAdminCap: u64 = 0;\n15const EInsufficientStake: u64 = 1;\n16const EZeroAmount: u64 = 2;\n17const EInsufficientRewards: u64 = 3;\n18const EInvalidDuration: u64 = 4;\n19const EPoolNotIdle: u64 = 5;\n20const EPaused: u64 = 6;\n21const EWrongPool: u64 = 7;\n22/// `notify_reward_amount` was given a `duration_ms` so large that\n23/// `now + duration_ms` would overflow u64. Admin-only and only reachable with\n24/// a duration of ~584 million years — guarded so the call aborts cleanly\n25/// instead of with a raw arithmetic error.\n26const EDurationOverflow: u64 = 8;\n27/// `notify_reward_amount` was given a non-zero `reward_coin` together with a\n28/// `duration_ms` so long that the integer rate `amount / duration_ms` floors\n29/// to 0 — the coin would be absorbed into the pool but never emitted,\n30/// stranding it behind `admin_withdraw_unused_rewards`'s idle-pool gate.\n31/// Winding emissions down with a zero-value coin remains permitted.\n32const EZeroRewardRate: u64 = 9;\n33\n\n34// ── Structs ─────────────────────────────────────────────────\n35\n\n36public struct StakingPool<phantom S, phantom R> has key {\n37 id: UID,\n38 total_staked: u64,\n39 reward_per_token_stored: u128,\n40 reward_rate: u64,\n41 last_update_time: u64,\n42 start_timestamp: u64,\n43 stop_timestamp: u64,\n44 reward_balance: Balance<R>,\n45 stake_balance: Balance<S>,\n46 paused: bool,\n47}\n48\n\n49/// User's stake position. Returned by `stake`, mutated in place by\n50/// `stake_more` / `claim_rewards` / `unstake_partial`, and consumed by\n51/// `unstake` / `emergency_unstake`.\n52///\n53/// **Transferability footgun.** `key + store` makes the receipt freely\n54/// transferable via `transfer::public_transfer`. A transferee silently\n55/// inherits the sender's accounting state, including:\n56///\n57/// - `pending_rewards` — only the *checkpointed* portion. Any un-checkpointed\n58/// accrual since the last `update_receipt_rewards` will be credited to the\n59/// new owner instead of the sender.\n60/// - `reward_per_token_paid` — the snapshot from the sender's last sync; it\n61/// sets the baseline against which the new owner's future deltas are\n62/// measured.\n63///\n64/// If you need atomic claim-then-transfer semantics, the sender should call\n65/// `claim_rewards` immediately before transferring. The receipt's pending\n66/// will then be 0 and `reward_per_token_paid` will reflect the current\n67/// accumulator, so the new owner accrues only from the moment of transfer\n68/// forward. Transferring without first settling leaves the in-flight\n69/// accrual as a gift to the recipient.\n70public struct StakeReceipt<phantom S, phantom R> has key, store {\n71 id: UID,\n72 pool: ID,\n73 amount: u64,\n74 reward_per_token_paid: u128,\n75 pending_rewards: u64,\n76}\n77\n\n78/// Capability object — possession authorises admin operations on the bound\n79/// pool. Created at `create_pool`; can be transferred (e.g. into a multi-sig\n80/// wrapper), or burned via `destroy_admin_cap` to make the pool's reward\n81/// schedule permanently immutable.\n82///\n83/// The `<phantom S, phantom R>` parameters match the pool's type parameters\n84/// and prevent using a `<S1, R1>` cap on a `<S2, R2>` pool at compile time.\n85/// The `pool: ID` field handles the case where multiple pools share the same\n86/// `<S, R>` — checked at every admin entry via `cap.pool == object::id(pool)`.\n87public struct AdminCap<phantom S, phantom R> has key, store {\n88 id: UID,\n89 pool: ID,\n90}\n91\n\n92// ── Internal helpers ────────────────────────────────────────\n93\n\n94/// Synthetix `lastTimeRewardApplicable`: clamp `now` into [start, stop].\n95/// Returns the timestamp the reward math should treat as \"now.\"\n96/// Outside the active period the accumulator cannot advance — this is what\n97/// makes solvency structural rather than operational.\n98fun last_applicable_time<S, R>(pool: &StakingPool<S, R>, clock: &Clock): u64 {\n99 let now = clock.timestamp_ms();\n100 if (now < pool.start_timestamp) {\n101 pool.start_timestamp\n102 } else if (now > pool.stop_timestamp) {\n103 pool.stop_timestamp\n104 } else {\n105 now\n106 }\n107}\n108\n\n109fun calculate_reward_per_token<S, R>(pool: &StakingPool<S, R>, clock: &Clock): u128 {\n110 if (pool.total_staked == 0) {\n111 return pool.reward_per_token_stored\n112 };\n113\n\n114 let applicable = last_applicable_time(pool, clock);\n115 let time_elapsed = ((applicable - pool.last_update_time) as u128);\n116 let additional =\n117 (time_elapsed * (pool.reward_rate as u128) * PRECISION)\n118 / (pool.total_staked as u128);\n119\n\n120 pool.reward_per_token_stored + additional\n121}\n122\n\n123fun calculate_earned<S, R>(\n124 pool: &StakingPool<S, R>,\n125 receipt: &StakeReceipt<S, R>,\n126 clock: &Clock,\n127): u64 {\n128 let current_rpt = calculate_reward_per_token(pool, clock);\n129 let rpt_delta = current_rpt - receipt.reward_per_token_paid;\n130 // Two-step so the cast precedence is unambiguous: the divide-then-cast\n131 // is split out, making it explicit that we cast the entire u128 result\n132 // to u64 (not just PRECISION).\n133 let scaled = (receipt.amount as u128) * rpt_delta / PRECISION;\n134 let new_rewards = scaled as u64;\n135 new_rewards + receipt.pending_rewards\n136}\n137\n\n138fun update_pool_rewards<S, R>(pool: &mut StakingPool<S, R>, clock: &Clock) {\n139 pool.reward_per_token_stored = calculate_reward_per_token(pool, clock);\n140 pool.last_update_time = last_applicable_time(pool, clock);\n141}\n142\n\n143fun update_receipt_rewards<S, R>(\n144 pool: &StakingPool<S, R>,\n145 receipt: &mut StakeReceipt<S, R>,\n146 clock: &Clock,\n147) {\n148 receipt.pending_rewards = calculate_earned(pool, receipt, clock);\n149 receipt.reward_per_token_paid = pool.reward_per_token_stored;\n150}\n151\n\n152fun assert_not_paused<S, R>(pool: &StakingPool<S, R>) {\n153 assert!(!pool.paused, EPaused);\n154}\n155\n\n156/// Receipt must belong to the pool it is being used against. Prevents a\n157/// `StakeReceipt` minted by one pool from operating on a different pool that\n158/// shares the same `<S, R>` type pair (cross-pool drain). Every receipt-taking\n159/// entry must call this — centralised here so the invariant is discoverable by\n160/// name and hard to forget when adding new entry points.\n161fun assert_receipt_matches_pool<S, R>(receipt: &StakeReceipt<S, R>, pool: &StakingPool<S, R>) {\n162 assert!(receipt.pool == object::id(pool), EWrongPool);\n163}\n164\n\n165/// AdminCap must be bound to the pool it is administering. Guards the case\n166/// where multiple pools share the same `<S, R>` (the phantom params alone\n167/// can't distinguish them).\n168fun assert_cap_matches_pool<S, R>(cap: &AdminCap<S, R>, pool: &StakingPool<S, R>) {\n169 assert!(cap.pool == object::id(pool), EWrongAdminCap);\n170}\n171\n\n172/// Defensive solvency guard before paying `amount` out of the reward balance.\n173/// Structurally unreachable given `notify_reward_amount`'s solvency check\n174/// (`rate * duration <= reward_balance`); retained as insurance against a\n175/// future refactor re-introducing the hazard.\n176fun assert_sufficient_rewards<S, R>(pool: &StakingPool<S, R>, amount: u64) {\n177 assert!(pool.reward_balance.value() >= amount, EInsufficientRewards);\n178}\n179\n\n180// ── Admin functions ─────────────────────────────────────────\n181\n\n182/// Create and share a new pool. Returns the freshly minted `AdminCap<S, R>`\n183/// to the caller — they decide whether to keep it, deposit it into a multi-sig,\n184/// or burn it via `destroy_admin_cap` for a permanently immutable pool.\n185///\n186/// The pool starts with no active reward period; call `notify_reward_amount`\n187/// to fund it and start emissions. `last_update_time` is initialised to 0 so\n188/// it stays aligned with `last_applicable_time` (which returns 0 while\n189/// `stop_timestamp == 0`); any other value would underflow on the first\n190/// `calculate_reward_per_token`.\n191///\n192/// **Permissionless.** Anyone can create a pool for any `<S, R>` pair on a\n193/// deployed package. The receipt/cap ID-binding means a look-alike pool can\n194/// never touch another pool's funds, but frontends and integrations MUST pin\n195/// the specific pool object ID they trust — never resolve a pool by its type\n196/// arguments alone, or users can be phished into staking in an impostor pool.\n197public fun create_pool<S, R>(ctx: &mut TxContext): AdminCap<S, R> {\n198 let pool = StakingPool<S, R> {\n199 id: object::new(ctx),\n200 total_staked: 0,\n201 reward_per_token_stored: 0,\n202 reward_rate: 0,\n203 last_update_time: 0,\n204 start_timestamp: 0,\n205 stop_timestamp: 0,\n206 reward_balance: balance::zero<R>(),\n207 stake_balance: balance::zero<S>(),\n208 paused: false,\n209 };\n210 let pool_id = object::id(&pool);\n211 transfer::share_object(pool);\n212 let cap = AdminCap<S, R> { id: object::new(ctx), pool: pool_id };\n213 events::emit_pool_created<S, R>(pool_id, object::id(&cap));\n214 cap\n215}\n216\n\n217/// Synthetix-style funding + period setup, in one call.\n218///\n219/// - Finalises accrual at the OLD rate before mutating any rate-related state.\n220/// - Joins `reward_coin` into the pool's reward balance.\n221/// - Computes a new `reward_rate` that emits all available rewards (incl.\n222/// leftover from any active period) over `duration_ms`.\n223/// - Sets the new emission window `[now, now + duration_ms]`.\n224/// - Asserts `rate * duration <= reward_balance`. Because the coin has already\n225/// been joined into the balance at this point, this invariant is achievable\n226/// from any caller-controlled input — no inputs can construct an insolvent\n227/// post-state. Hence H-1 (principal soft-lock via under-funding) is\n228/// structurally impossible after this refactor.\n229///\n230/// Allowed corner cases:\n231/// - `reward_coin.value() == 0` is permitted: extends the window using only\n232/// leftover from the active period, at a recomputed rate. This is also the\n233/// sanctioned way to wind emissions down (`new_rate` may floor to 0).\n234/// - `new_rate == 0` with a non-zero `reward_coin` is REJECTED\n235/// (`EZeroRewardRate`): the coin would be absorbed but never emitted. Pick a\n236/// shorter duration or a larger amount. Watch the units — `duration_ms` is\n237/// milliseconds, so low-decimal reward tokens hit this floor easily.\n238public fun notify_reward_amount<S, R>(\n239 cap: &AdminCap<S, R>,\n240 pool: &mut StakingPool<S, R>,\n241 reward_coin: Coin<R>,\n242 duration_ms: u64,\n243 clock: &Clock,\n244) {\n245 assert_cap_matches_pool(cap, pool);\n246 assert!(duration_ms > 0, EInvalidDuration);\n247\n\n248 update_pool_rewards(pool, clock);\n249\n\n250 let amount = reward_coin.value();\n251 pool.reward_balance.join(reward_coin.into_balance());\n252\n\n253 let now = clock.timestamp_ms();\n254 // Guard `pool.stop_timestamp = now + duration_ms` against u64 overflow.\n255 assert!(duration_ms <= MAX_U64 - now, EDurationOverflow);\n256 let new_rate = if (now >= pool.stop_timestamp) {\n257 amount / duration_ms\n258 } else {\n259 let remaining = pool.stop_timestamp - now;\n260 let leftover = remaining * pool.reward_rate;\n261 (amount + leftover) / duration_ms\n262 };\n263\n\n264 // Reject funding that can never emit: a non-zero coin whose rate floors\n265 // to 0 would be stranded behind `admin_withdraw_unused_rewards`'s\n266 // idle-pool gate. Zero-coin wind-downs stay legal.\n267 assert!(new_rate > 0 || amount == 0, EZeroRewardRate);\n268\n\n269 assert!(\n270 (new_rate as u128) * (duration_ms as u128)\n271 <= (pool.reward_balance.value() as u128),\n272 EInsufficientRewards,\n273 );\n274\n\n275 pool.reward_rate = new_rate;\n276 pool.start_timestamp = now;\n277 pool.stop_timestamp = now + duration_ms;\n278 pool.last_update_time = now;\n279\n\n280 events::emit_rewards_notified<S, R>(\n281 object::id(pool),\n282 amount,\n283 duration_ms,\n284 new_rate,\n285 pool.stop_timestamp,\n286 );\n287}\n288\n\n289/// Withdraw any reward tokens left in the pool after the emission period\n290/// has ended and all stakers have unstaked. Recovers admin capital that\n291/// would otherwise be stranded (dust from integer division, plus any\n292/// over-funding the schedule never emitted).\n293///\n294/// Gate: `now > stop_timestamp && total_staked == 0`. Both conditions are\n295/// required to preserve the H-1 invariant. If withdrawal were allowed while\n296/// `total_staked > 0`, principal would still be safe but the *next* staker\n297/// would inherit a broken solvency state. If allowed before `stop_timestamp`,\n298/// the same hazard applies even with no live stakers — a fresh staker\n299/// arriving before `stop_timestamp` would accrue against an empty balance.\n300///\n301/// To restart emissions after withdrawing, call `notify_reward_amount` with\n302/// a fresh duration; the leftover branch is irrelevant because the period\n303/// has already ended.\n304public fun admin_withdraw_unused_rewards<S, R>(\n305 cap: &AdminCap<S, R>,\n306 pool: &mut StakingPool<S, R>,\n307 clock: &Clock,\n308 ctx: &mut TxContext,\n309): Coin<R> {\n310 assert_cap_matches_pool(cap, pool);\n311 assert!(pool.total_staked == 0, EPoolNotIdle);\n312 assert!(clock.timestamp_ms() > pool.stop_timestamp, EPoolNotIdle);\n313\n\n314 let amount = pool.reward_balance.value();\n315 let recovered = pool.reward_balance.split(amount).into_coin(ctx);\n316 events::emit_unused_rewards_withdrawn<S, R>(object::id(pool), amount);\n317 recovered\n318}\n319\n\n320/// Admin emergency pause. While paused, `stake` and `stake_more` abort with\n321/// `EPaused`; `unstake`, `unstake_partial`, and `claim_rewards` all remain\n322/// callable. Pause **never** locks principal — it only stops new exposure\n323/// (e.g. while a downstream contract is broken or a policy change is\n324/// mid-rollout).\n325public fun set_paused<S, R>(cap: &AdminCap<S, R>, pool: &mut StakingPool<S, R>, paused: bool) {\n326 assert_cap_matches_pool(cap, pool);\n327 // Only emit (and write) when the value actually changes — no-op calls\n328 // shouldn't produce spurious events for indexers.\n329 if (pool.paused != paused) {\n330 pool.paused = paused;\n331 events::emit_pool_paused<S, R>(object::id(pool), paused);\n332 }\n333}\n334\n\n335/// Burn the AdminCap, making the bound pool permanently un-administered.\n336/// After this call, no future `notify_reward_amount` or\n337/// `admin_withdraw_unused_rewards` is possible on that pool — it can only\n338/// be drained by stakers unstaking and claiming their accrued rewards.\n339///\n340/// Use case: protocols that want a \"set it and forget it\" pool whose\n341/// emission schedule cannot be changed by anyone, including the original\n342/// deployer.\n343///\n344/// **Irreversible consequences — check pool state before burning:**\n345/// - Any surplus in `reward_balance` (division dust, forfeited emergency\n346/// pendings, over-funding) becomes permanently locked, because\n347/// `admin_withdraw_unused_rewards` requires the cap.\n348/// - If the pool is currently paused, it stays paused forever: no one can\n349/// call `set_paused` again, so `stake`/`stake_more` abort permanently.\n350/// Principal remains withdrawable (unstake paths ignore pause), but the\n351/// pool is closed to new deposits. This function takes only the cap, so\n352/// it cannot check the pool for you — verify `paused == false` first.\n353public fun destroy_admin_cap<S, R>(cap: AdminCap<S, R>) {\n354 let AdminCap { id, pool } = cap;\n355 object::delete(id);\n356 events::emit_admin_cap_destroyed<S, R>(pool);\n357}\n358\n\n359// ── User functions ──────────────────────────────────────────\n360\n\n361public fun stake<S, R>(\n362 pool: &mut StakingPool<S, R>,\n363 coin: Coin<S>,\n364 clock: &Clock,\n365 ctx: &mut TxContext,\n366): StakeReceipt<S, R> {\n367 assert_not_paused(pool);\n368 let amount = coin.value();\n369 assert!(amount > 0, EZeroAmount);\n370\n\n371 update_pool_rewards(pool, clock);\n372\n\n373 pool.stake_balance.join(coin.into_balance());\n374 pool.total_staked = pool.total_staked + amount;\n375\n\n376 let receipt = StakeReceipt<S, R> {\n377 id: object::new(ctx),\n378 pool: object::id(pool),\n379 amount,\n380 reward_per_token_paid: pool.reward_per_token_stored,\n381 pending_rewards: 0,\n382 };\n383 events::emit_staked<S, R>(\n384 object::id(pool),\n385 ctx.sender(),\n386 amount,\n387 object::id(&receipt),\n388 );\n389 receipt\n390}\n391\n\n392public fun stake_more<S, R>(\n393 pool: &mut StakingPool<S, R>,\n394 receipt: &mut StakeReceipt<S, R>,\n395 coin: Coin<S>,\n396 clock: &Clock,\n397) {\n398 assert_receipt_matches_pool(receipt, pool);\n399 assert_not_paused(pool);\n400 let amount = coin.value();\n401 assert!(amount > 0, EZeroAmount);\n402\n\n403 update_pool_rewards(pool, clock);\n404 update_receipt_rewards(pool, receipt, clock);\n405\n\n406 pool.stake_balance.join(coin.into_balance());\n407 pool.total_staked = pool.total_staked + amount;\n408 receipt.amount = receipt.amount + amount;\n409\n\n410 events::emit_staked_more<S, R>(\n411 object::id(pool),\n412 object::id(receipt),\n413 amount,\n414 receipt.amount,\n415 );\n416}\n417\n\n418/// Pay out the staker's accrued rewards. Precondition: there must be at\n419/// least 1 unit of pending reward to claim — claiming with nothing pending\n420/// aborts `EZeroAmount` rather than returning a useless zero-value coin.\n421/// Callers can pre-check via `earned_rewards`.\n422public fun claim_rewards<S, R>(\n423 pool: &mut StakingPool<S, R>,\n424 receipt: &mut StakeReceipt<S, R>,\n425 clock: &Clock,\n426 ctx: &mut TxContext,\n427): Coin<R> {\n428 assert_receipt_matches_pool(receipt, pool);\n429 update_pool_rewards(pool, clock);\n430 update_receipt_rewards(pool, receipt, clock);\n431\n\n432 let reward_amount = receipt.pending_rewards;\n433 assert!(reward_amount > 0, EZeroAmount);\n434 receipt.pending_rewards = 0;\n435\n\n436 assert_sufficient_rewards(pool, reward_amount);\n437\n\n438 let reward_coin = pool.reward_balance.split(reward_amount).into_coin(ctx);\n439 events::emit_rewards_claimed<S, R>(\n440 object::id(pool),\n441 object::id(receipt),\n442 reward_amount,\n443 );\n444 reward_coin\n445}\n446\n\n447public fun unstake<S, R>(\n448 pool: &mut StakingPool<S, R>,\n449 receipt: StakeReceipt<S, R>,\n450 clock: &Clock,\n451 ctx: &mut TxContext,\n452): (Coin<S>, Coin<R>) {\n453 assert_receipt_matches_pool(&receipt, pool);\n454 update_pool_rewards(pool, clock);\n455\n\n456 let earned = calculate_earned(pool, &receipt, clock);\n457 let receipt_id = object::id(&receipt);\n458\n\n459 let StakeReceipt { id, pool: _, amount, reward_per_token_paid: _, pending_rewards: _ } = receipt;\n460 object::delete(id);\n461\n\n462 pool.total_staked = pool.total_staked - amount;\n463\n\n464 let stake_coin = pool.stake_balance.split(amount).into_coin(ctx);\n465 assert_sufficient_rewards(pool, earned);\n466 let reward_coin = pool.reward_balance.split(earned).into_coin(ctx);\n467\n\n468 events::emit_unstaked<S, R>(object::id(pool), ctx.sender(), amount, earned, receipt_id);\n469\n\n470 (stake_coin, reward_coin)\n471}\n472\n\n473/// Partially exit a stake position. Returns both the freed principal AND\n474/// the accrued rewards — symmetric with `unstake`, so naive callers don't\n475/// get an unintended \"exit principal but leave rewards\" semantics.\n476///\n477/// `amount` must be **strictly less** than `receipt.amount` (`< receipt.amount`);\n478/// callers wanting a full exit must use `unstake`, which consumes the\n479/// receipt. This prevents zero-amount zombie receipts from accumulating\n480/// on-chain (a 0-amount receipt can never accrue rewards and is just dust).\n481public fun unstake_partial<S, R>(\n482 pool: &mut StakingPool<S, R>,\n483 receipt: &mut StakeReceipt<S, R>,\n484 amount: u64,\n485 clock: &Clock,\n486 ctx: &mut TxContext,\n487): (Coin<S>, Coin<R>) {\n488 assert_receipt_matches_pool(receipt, pool);\n489 assert!(amount > 0, EZeroAmount);\n490 // Strict <: full exits go through `unstake` instead. This forbids the\n491 // amount == receipt.amount case which would leave a zero-amount zombie.\n492 assert!(receipt.amount > amount, EInsufficientStake);\n493\n\n494 update_pool_rewards(pool, clock);\n495 update_receipt_rewards(pool, receipt, clock);\n496\n\n497 // Pay out accrued pending rewards alongside the partial principal.\n498 let reward_amount = receipt.pending_rewards;\n499 receipt.pending_rewards = 0;\n500 assert_sufficient_rewards(pool, reward_amount);\n501 let reward_coin = pool.reward_balance.split(reward_amount).into_coin(ctx);\n502\n\n503 receipt.amount = receipt.amount - amount;\n504 pool.total_staked = pool.total_staked - amount;\n505\n\n506 let stake_coin = pool.stake_balance.split(amount).into_coin(ctx);\n507 events::emit_unstaked_partial<S, R>(\n508 object::id(pool),\n509 object::id(receipt),\n510 amount,\n511 receipt.amount,\n512 reward_amount,\n513 );\n514 (stake_coin, reward_coin)\n515}\n516\n\n517/// User-initiated escape hatch — guarantees principal recovery at the cost\n518/// of forfeiting any accrued rewards. Deliberately skips\n519/// `update_pool_rewards`, takes no `&Clock`, and never touches\n520/// `reward_balance`, so the function remains callable even in a\n521/// hypothetically under-funded state where the defensive\n522/// `EInsufficientRewards` assert in `unstake`/`claim_rewards` would fire.\n523/// (That state is currently unreachable thanks to `notify_reward_amount`'s\n524/// solvency check; this function is insurance against a future refactor\n525/// re-introducing the hazard.)\n526///\n527/// Pattern: MasterChef-style `emergencyWithdraw` —\n528/// https://github.com/sushiswap/masterchef/blob/master/contracts/MasterChef.sol#L273-L280\n529///\n530/// Forfeited pending rewards stay in `reward_balance` as surplus,\n531/// recoverable by the admin via `admin_withdraw_unused_rewards` once the\n532/// emission period ends and the pool goes idle.\n533public fun emergency_unstake<S, R>(\n534 pool: &mut StakingPool<S, R>,\n535 receipt: StakeReceipt<S, R>,\n536 ctx: &mut TxContext,\n537): Coin<S> {\n538 assert_receipt_matches_pool(&receipt, pool);\n539 let receipt_id = object::id(&receipt);\n540 let StakeReceipt {\n541 id,\n542 pool: _,\n543 amount,\n544 reward_per_token_paid: _,\n545 pending_rewards: forfeited_rewards,\n546 } = receipt;\n547 object::delete(id);\n548\n\n549 pool.total_staked = pool.total_staked - amount;\n550\n\n551 let principal = pool.stake_balance.split(amount).into_coin(ctx);\n552 events::emit_emergency_unstaked<S, R>(\n553 object::id(pool),\n554 ctx.sender(),\n555 amount,\n556 forfeited_rewards,\n557 receipt_id,\n558 );\n559 principal\n560}\n561\n\n562// ── View functions ──────────────────────────────────────────\n563\n\n564public fun receipt_pool_id<S, R>(receipt: &StakeReceipt<S, R>): ID {\n565 receipt.pool\n566}\n567\n\n568public fun staked_amount<S, R>(receipt: &StakeReceipt<S, R>): u64 {\n569 receipt.amount\n570}\n571\n\n572public fun earned_rewards<S, R>(\n573 pool: &StakingPool<S, R>,\n574 receipt: &StakeReceipt<S, R>,\n575 clock: &Clock,\n576): u64 {\n577 assert_receipt_matches_pool(receipt, pool);\n578 calculate_earned(pool, receipt, clock)\n579}\n580\n\n581public fun total_staked<S, R>(pool: &StakingPool<S, R>): u64 {\n582 pool.total_staked\n583}\n584\n\n585public fun available_rewards<S, R>(pool: &StakingPool<S, R>): u64 {\n586 pool.reward_balance.value()\n587}\n588\n\n589public fun reward_rate<S, R>(pool: &StakingPool<S, R>): u64 {\n590 pool.reward_rate\n591}\n592\n\n593public fun start_timestamp<S, R>(pool: &StakingPool<S, R>): u64 {\n594 pool.start_timestamp\n595}\n596\n\n597public fun stop_timestamp<S, R>(pool: &StakingPool<S, R>): u64 {\n598 pool.stop_timestamp\n599}\n600\n\n601// ───────────────────────────────────────────────────\n602// ── Tests ──────────────────────────────────────────\n603// ───────────────────────────────────────────────────\n604\n\n605#[test_only]\n606use sui::clock;\n607#[test_only]\n608use std::unit_test::{assert_eq, destroy};\n609\n\n610#[test_only]\n611public struct STAKE_TOKEN has drop {}\n612\n\n613#[test_only]\n614public struct REWARD_TOKEN has drop {}\n615\n\n616// ── last_applicable_time ──────────────────────────────────────────\n617\n\n618#[test]\n619fun test_last_applicable_time() {\n620 let ctx = &mut tx_context::dummy();\n621 let mut clock = clock::create_for_testing(ctx);\n622 let pool = StakingPool {\n623 id: object::new(ctx),\n624 total_staked: 0,\n625 reward_per_token_stored: 0,\n626 reward_rate: 0,\n627 last_update_time: 0,\n628 start_timestamp: 1,\n629 stop_timestamp: 3,\n630 reward_balance: balance::zero<REWARD_TOKEN>(),\n631 stake_balance: balance::zero<STAKE_TOKEN>(),\n632 paused: false,\n633 };\n634\n\n635 // now < pool.start_timestamp\n636 assert_eq!(last_applicable_time(&pool, &clock), 1);\n637\n\n638 // now == pool.start_timestamp\n639 clock.increment_for_testing(1);\n640 assert_eq!(last_applicable_time(&pool, &clock), 1);\n641\n\n642 // now > pool.start_timestamp && now < pool.stop_timestamp\n643 clock.increment_for_testing(1);\n644 assert_eq!(last_applicable_time(&pool, &clock), 2);\n645\n\n646 // now == pool.stop_timestamp\n647 clock.increment_for_testing(1);\n648 assert_eq!(last_applicable_time(&pool, &clock), 3);\n649\n\n650 // now > pool.stop_timestamp\n651 clock.increment_for_testing(1);\n652 assert_eq!(last_applicable_time(&pool, &clock), 3);\n653\n\n654 destroy(pool);\n655 destroy(clock);\n656}\n657\n\n658// ── calculate_reward_per_token ──────────────────────────────────────────\n659\n\n660#[test_only]\n661public struct RptCase has drop {\n662 total_staked: u64,\n663 rpt_stored: u128,\n664 rate: u64,\n665 last_update: u64,\n666 start: u64,\n667 stop: u64,\n668 now_ms: u64,\n669 expected: u128,\n670}\n671\n\n672#[test_only]\n673fun assert_rpt(case: RptCase) {\n674 let ctx = &mut tx_context::dummy();\n675 let mut clock = clock::create_for_testing(ctx);\n676 clock.increment_for_testing(case.now_ms);\n677 let pool = StakingPool<STAKE_TOKEN, REWARD_TOKEN> {\n678 id: object::new(ctx),\n679 total_staked: case.total_staked,\n680 reward_per_token_stored: case.rpt_stored,\n681 reward_rate: case.rate,\n682 last_update_time: case.last_update,\n683 start_timestamp: case.start,\n684 stop_timestamp: case.stop,\n685 reward_balance: balance::zero<REWARD_TOKEN>(),\n686 stake_balance: balance::zero<STAKE_TOKEN>(),\n687 paused: false,\n688 };\n689\n\n690 assert_eq!(calculate_reward_per_token(&pool, &clock), case.expected);\n691\n\n692 destroy(pool);\n693 destroy(clock);\n694}\n695\n\n696#[test]\n697fun test_calculate_reward_per_token_when_zero_total_staked() {\n698 assert_rpt(RptCase {\n699 total_staked: 0,\n700 rpt_stored: 100,\n701 rate: 0,\n702 last_update: 1,\n703 start: 1,\n704 stop: 3,\n705 now_ms: 0,\n706 expected: 100,\n707 });\n708}\n709\n\n710#[test]\n711fun test_calculate_reward_per_token_when_time_elapsed_zero() {\n712 assert_rpt(RptCase {\n713 total_staked: 100,\n714 rpt_stored: 50,\n715 rate: 10,\n716 last_update: 5,\n717 start: 5,\n718 stop: 20,\n719 now_ms: 5,\n720 expected: 50,\n721 });\n722}\n723\n\n724#[test]\n725fun test_calculate_reward_per_token_when_before_start() {\n726 assert_rpt(RptCase {\n727 total_staked: 100,\n728 rpt_stored: 0,\n729 rate: 10,\n730 last_update: 10,\n731 start: 10,\n732 stop: 20,\n733 now_ms: 5,\n734 expected: 0,\n735 });\n736}\n737\n\n738#[test]\n739fun test_calculate_reward_per_token_when_after_stop() {\n740 assert_rpt(RptCase {\n741 total_staked: 100,\n742 rpt_stored: 0,\n743 rate: 10,\n744 last_update: 10,\n745 start: 10,\n746 stop: 20,\n747 now_ms: 50,\n748 expected: PRECISION,\n749 });\n750}\n751\n\n752#[test]\n753fun test_calculate_reward_per_token_when_inside_window() {\n754 assert_rpt(RptCase {\n755 total_staked: 100,\n756 rpt_stored: 0,\n757 rate: 10,\n758 last_update: 10,\n759 start: 10,\n760 stop: 100,\n761 now_ms: 20,\n762 expected: PRECISION,\n763 });\n764}\n765\n\n766#[test]\n767fun test_calculate_reward_per_token_when_rate_zero() {\n768 assert_rpt(RptCase {\n769 total_staked: 100,\n770 rpt_stored: 42,\n771 rate: 0,\n772 last_update: 10,\n773 start: 10,\n774 stop: 100,\n775 now_ms: 50,\n776 expected: 42,\n777 });\n778}\n779\n\n780#[test]\n781fun test_calculate_reward_per_token_accumulates_on_stored() {\n782 assert_rpt(RptCase {\n783 total_staked: 100,\n784 rpt_stored: 5 * PRECISION,\n785 rate: 10,\n786 last_update: 10,\n787 start: 10,\n788 stop: 100,\n789 now_ms: 20,\n790 expected: 6 * PRECISION,\n791 });\n792}\n793\n\n794#[test]\n795fun test_calculate_reward_per_token_precision_preserves_small_share() {\n796 assert_rpt(RptCase {\n797 total_staked: 1_000_000,\n798 rpt_stored: 0,\n799 rate: 1,\n800 last_update: 10,\n801 start: 10,\n802 stop: 100,\n803 now_ms: 11,\n804 expected: 1_000_000_000_000,\n805 });\n806}\n807\n\n808#[test]\n809fun test_calculate_reward_per_token_large_numbers_no_overflow() {\n810 assert_rpt(RptCase {\n811 total_staked: 1_000_000_000_000_000,\n812 rpt_stored: 0,\n813 rate: 1_000_000_000,\n814 last_update: 0,\n815 start: 0,\n816 stop: 1_000_000_000,\n817 now_ms: 1_000_000_000,\n818 expected: 1_000 * PRECISION,\n819 });\n820}\n821\n\n822// ── calculate_earned ──────────────────────────────────────────\n823\n\n824#[test_only]\n825public struct EarnedCase has drop {\n826 // pool fields\n827 pool_total_staked: u64,\n828 pool_rpt_stored: u128,\n829 pool_rate: u64,\n830 pool_last_update: u64,\n831 pool_start: u64,\n832 pool_stop: u64,\n833 // clock\n834 now_ms: u64,\n835 // receipt fields\n836 receipt_amount: u64,\n837 receipt_rpt_paid: u128,\n838 receipt_pending: u64,\n839 // expected\n840 expected: u64,\n841}\n842\n\n843#[test_only]\n844fun assert_earned(case: EarnedCase) {\n845 let ctx = &mut tx_context::dummy();\n846 let mut clock = clock::create_for_testing(ctx);\n847 clock.increment_for_testing(case.now_ms);\n848 let pool = StakingPool<STAKE_TOKEN, REWARD_TOKEN> {\n849 id: object::new(ctx),\n850 total_staked: case.pool_total_staked,\n851 reward_per_token_stored: case.pool_rpt_stored,\n852 reward_rate: case.pool_rate,\n853 last_update_time: case.pool_last_update,\n854 start_timestamp: case.pool_start,\n855 stop_timestamp: case.pool_stop,\n856 reward_balance: balance::zero<REWARD_TOKEN>(),\n857 stake_balance: balance::zero<STAKE_TOKEN>(),\n858 paused: false,\n859 };\n860 let receipt = StakeReceipt<STAKE_TOKEN, REWARD_TOKEN> {\n861 id: object::new(ctx),\n862 pool: object::id(&pool),\n863 amount: case.receipt_amount,\n864 reward_per_token_paid: case.receipt_rpt_paid,\n865 pending_rewards: case.receipt_pending,\n866 };\n867\n\n868 assert_eq!(calculate_earned(&pool, &receipt, &clock), case.expected);\n869\n\n870 destroy(pool);\n871 destroy(receipt);\n872 destroy(clock);\n873}\n874\n\n875#[test]\n876fun test_calculate_earned_zero_amount_with_pending() {\n877 // amount=0 → new_rewards = 0, regardless of rpt_delta. Pending passes through.\n878 assert_earned(EarnedCase {\n879 pool_total_staked: 0,\n880 pool_rpt_stored: 5 * PRECISION,\n881 pool_rate: 0,\n882 pool_last_update: 0,\n883 pool_start: 0,\n884 pool_stop: 0,\n885 now_ms: 0,\n886 receipt_amount: 0,\n887 receipt_rpt_paid: 0,\n888 receipt_pending: 42,\n889 expected: 42,\n890 });\n891}\n892\n\n893#[test]\n894fun test_calculate_earned_rpt_delta_zero_returns_pending_only() {\n895 // current_rpt == receipt.reward_per_token_paid → delta = 0 → new_rewards = 0.\n896 assert_earned(EarnedCase {\n897 pool_total_staked: 0,\n898 pool_rpt_stored: 5 * PRECISION,\n899 pool_rate: 0,\n900 pool_last_update: 0,\n901 pool_start: 0,\n902 pool_stop: 0,\n903 now_ms: 0,\n904 receipt_amount: 100,\n905 receipt_rpt_paid: 5 * PRECISION,\n906 receipt_pending: 42,\n907 expected: 42,\n908 });\n909}\n910\n\n911#[test]\n912fun test_calculate_earned_basic_accrual_no_pending() {\n913 // delta = 2P, amount = 100 → 100 * 2P / P = 200. No pending.\n914 assert_earned(EarnedCase {\n915 pool_total_staked: 0,\n916 pool_rpt_stored: 2 * PRECISION,\n917 pool_rate: 0,\n918 pool_last_update: 0,\n919 pool_start: 0,\n920 pool_stop: 0,\n921 now_ms: 0,\n922 receipt_amount: 100,\n923 receipt_rpt_paid: 0,\n924 receipt_pending: 0,\n925 expected: 200,\n926 });\n927}\n928\n\n929#[test]\n930fun test_calculate_earned_paid_offset_subtracts_correctly() {\n931 // current_rpt = 5P, paid = 3P → delta = 2P, amount = 10 → 20.\n932 assert_earned(EarnedCase {\n933 pool_total_staked: 0,\n934 pool_rpt_stored: 5 * PRECISION,\n935 pool_rate: 0,\n936 pool_last_update: 0,\n937 pool_start: 0,\n938 pool_stop: 0,\n939 now_ms: 0,\n940 receipt_amount: 10,\n941 receipt_rpt_paid: 3 * PRECISION,\n942 receipt_pending: 0,\n943 expected: 20,\n944 });\n945}\n946\n\n947#[test]\n948fun test_calculate_earned_pending_adds_on_top() {\n949 // Same as paid_offset, but pending = 50 → 20 + 50 = 70.\n950 assert_earned(EarnedCase {\n951 pool_total_staked: 0,\n952 pool_rpt_stored: 5 * PRECISION,\n953 pool_rate: 0,\n954 pool_last_update: 0,\n955 pool_start: 0,\n956 pool_stop: 0,\n957 now_ms: 0,\n958 receipt_amount: 10,\n959 receipt_rpt_paid: 3 * PRECISION,\n960 receipt_pending: 50,\n961 expected: 70,\n962 });\n963}\n964\n\n965#[test]\n966fun test_calculate_earned_proportional_to_amount() {\n967 // delta = P, amount = 1000 → 1000 * P / P = 1000. Scales linearly with amount.\n968 assert_earned(EarnedCase {\n969 pool_total_staked: 0,\n970 pool_rpt_stored: PRECISION,\n971 pool_rate: 0,\n972 pool_last_update: 0,\n973 pool_start: 0,\n974 pool_stop: 0,\n975 now_ms: 0,\n976 receipt_amount: 1000,\n977 receipt_rpt_paid: 0,\n978 receipt_pending: 0,\n979 expected: 1000,\n980 });\n981}\n982\n\n983#[test]\n984fun test_calculate_earned_rounding_floors_to_zero() {\n985 // amount * delta < PRECISION → integer division floors to 0.\n986 // 5 * 10 = 50, 50 / 1e18 = 0. Dust loss is observable here.\n987 assert_earned(EarnedCase {\n988 pool_total_staked: 0,\n989 pool_rpt_stored: 10,\n990 pool_rate: 0,\n991 pool_last_update: 0,\n992 pool_start: 0,\n993 pool_stop: 0,\n994 now_ms: 0,\n995 receipt_amount: 5,\n996 receipt_rpt_paid: 0,\n997 receipt_pending: 0,\n998 expected: 0,\n999 });\n1000}\n1001\n\n1002#[test]\n1003fun test_calculate_earned_post_stop_uses_clamped_time() {\n1004 // Real accrual: clock past stop, so accrual clamps at stop_timestamp.\n1005 // time_elapsed = stop(20) - last_update(10) = 10\n1006 // additional = 10 * 10 * P / 100 = P → current_rpt = P\n1007 // amount = 100, paid = 0 → 100 * P / P = 100.\n1008 assert_earned(EarnedCase {\n1009 pool_total_staked: 100,\n1010 pool_rpt_stored: 0,\n1011 pool_rate: 10,\n1012 pool_last_update: 10,\n1013 pool_start: 10,\n1014 pool_stop: 20,\n1015 now_ms: 50,\n1016 receipt_amount: 100,\n1017 receipt_rpt_paid: 0,\n1018 receipt_pending: 0,\n1019 expected: 100,\n1020 });\n1021}\n1022\n\n1023#[test]\n1024fun test_calculate_earned_in_window_with_pending() {\n1025 // Real accrual inside the window, combined with pending.\n1026 // time_elapsed = 20 - 10 = 10\n1027 // additional = 10 * 10 * P / 100 = P → current_rpt = P\n1028 // amount = 50, paid = 0 → 50 * P / P = 50, + pending 7 = 57.\n1029 assert_earned(EarnedCase {\n1030 pool_total_staked: 100,\n1031 pool_rpt_stored: 0,\n1032 pool_rate: 10,\n1033 pool_last_update: 10,\n1034 pool_start: 10,\n1035 pool_stop: 100,\n1036 now_ms: 20,\n1037 receipt_amount: 50,\n1038 receipt_rpt_paid: 0,\n1039 receipt_pending: 7,\n1040 expected: 57,\n1041 });\n1042}\n1043\n\n1044// ── update_pool_rewards ──────────────────────────────────────────\n1045\n\n1046#[test]\n1047fun test_update_pool_rewards_writes_rpt_and_last_update() {\n1048 // time_elapsed = 20 - 10 = 10; additional = 10 * 10 * P / 100 = P.\n1049 // Expect rpt_stored to advance from 0 to P, and last_update_time\n1050 // to be clamped `now` (20, inside the window).\n1051 let ctx = &mut tx_context::dummy();\n1052 let mut clock = clock::create_for_testing(ctx);\n1053 clock.increment_for_testing(20);\n1054 let mut pool = StakingPool<STAKE_TOKEN, REWARD_TOKEN> {\n1055 id: object::new(ctx),\n1056 total_staked: 100,\n1057 reward_per_token_stored: 0,\n1058 reward_rate: 10,\n1059 last_update_time: 10,\n1060 start_timestamp: 10,\n1061 stop_timestamp: 100,\n1062 reward_balance: balance::zero<REWARD_TOKEN>(),\n1063 stake_balance: balance::zero<STAKE_TOKEN>(),\n1064 paused: false,\n1065 };\n1066\n\n1067 update_pool_rewards(&mut pool, &clock);\n1068\n\n1069 assert_eq!(pool.reward_per_token_stored, PRECISION);\n1070 assert_eq!(pool.last_update_time, 20);\n1071\n\n1072 destroy(pool);\n1073 destroy(clock);\n1074}\n1075\n\n1076#[test]\n1077fun test_update_pool_rewards_clamps_last_update_to_stop() {\n1078 // now > stop → last_update_time should be pinned to stop_timestamp,\n1079 // not `now`. This is what makes solvency structural after the window.\n1080 let ctx = &mut tx_context::dummy();\n1081 let mut clock = clock::create_for_testing(ctx);\n1082 clock.increment_for_testing(500);\n1083 let mut pool = StakingPool<STAKE_TOKEN, REWARD_TOKEN> {\n1084 id: object::new(ctx),\n1085 total_staked: 100,\n1086 reward_per_token_stored: 0,\n1087 reward_rate: 10,\n1088 last_update_time: 10,\n1089 start_timestamp: 10,\n1090 stop_timestamp: 20,\n1091 reward_balance: balance::zero<REWARD_TOKEN>(),\n1092 stake_balance: balance::zero<STAKE_TOKEN>(),\n1093 paused: false,\n1094 };\n1095\n\n1096 update_pool_rewards(&mut pool, &clock);\n1097\n\n1098 assert_eq!(pool.reward_per_token_stored, PRECISION);\n1099 assert_eq!(pool.last_update_time, 20);\n1100\n\n1101 destroy(pool);\n1102 destroy(clock);\n1103}\n1104\n\n1105// ── update_receipt_rewards ──────────────────────────────────────────\n1106\n\n1107#[test]\n1108fun test_update_receipt_rewards_writes_pending_and_paid() {\n1109 // total_staked = 0 → calculate_reward_per_token short-circuits to\n1110 // pool.reward_per_token_stored = 5P, so current_rpt == stored. delta = 2P,\n1111 // amount = 10 → new_rewards = 10 * 2P / P = 20 (no prior pending).\n1112 // Expect receipt.pending_rewards = 20 and reward_per_token_paid = 5P.\n1113 let ctx = &mut tx_context::dummy();\n1114 let clock = clock::create_for_testing(ctx);\n1115 let pool = StakingPool<STAKE_TOKEN, REWARD_TOKEN> {\n1116 id: object::new(ctx),\n1117 total_staked: 0,\n1118 reward_per_token_stored: 5 * PRECISION,\n1119 reward_rate: 0,\n1120 last_update_time: 0,\n1121 start_timestamp: 0,\n1122 stop_timestamp: 0,\n1123 reward_balance: balance::zero<REWARD_TOKEN>(),\n1124 stake_balance: balance::zero<STAKE_TOKEN>(),\n1125 paused: false,\n1126 };\n1127 let mut receipt = StakeReceipt<STAKE_TOKEN, REWARD_TOKEN> {\n1128 id: object::new(ctx),\n1129 pool: object::id(&pool),\n1130 amount: 10,\n1131 reward_per_token_paid: 3 * PRECISION,\n1132 pending_rewards: 0,\n1133 };\n1134\n\n1135 update_receipt_rewards(&pool, &mut receipt, &clock);\n1136\n\n1137 assert_eq!(receipt.pending_rewards, 20);\n1138 assert_eq!(receipt.reward_per_token_paid, 5 * PRECISION);\n1139\n\n1140 destroy(pool);\n1141 destroy(receipt);\n1142 destroy(clock);\n1143}\n1144\n\n1145#[test]\n1146fun test_update_receipt_rewards_paid_tracks_stored_not_fresh_rpt() {\n1147 // Pool is *not* pre-updated: stored = 0, but a fresh rpt would be P.\n1148 // update_receipt_rewards must set paid = stored (0), NOT the fresh value.\n1149 // Production callers always run update_pool_rewards first, which is why\n1150 // this is safe — but the field assignment itself is what we're pinning.\n1151 //\n1152 // Why `paid = stored` beats the \"defensive\" `paid = current_rpt`:\n1153 // `pool.reward_per_token_stored` is the *single canonical accumulator* —\n1154 // the only place rpt is officially committed. Snapshotting receipt.paid\n1155 // from it preserves the global invariant `receipt.paid <= pool.stored`\n1156 // and keeps one writer for accumulated rpt. The defensive variant would\n1157 // let receipts record rpt values that never appeared in pool state,\n1158 // splitting the writer and weakening the invariant. It would also make\n1159 // ordering mistakes (forgetting update_pool_rewards) fail subtly —\n1160 // leaving stored behind receipts — instead of loudly, as visible\n1161 // double-counting on the very next call (which this test would catch).\n1162 let ctx = &mut tx_context::dummy();\n1163 let mut clock = clock::create_for_testing(ctx);\n1164 clock.increment_for_testing(20);\n1165 let pool = StakingPool<STAKE_TOKEN, REWARD_TOKEN> {\n1166 id: object::new(ctx),\n1167 total_staked: 100,\n1168 reward_per_token_stored: 0,\n1169 reward_rate: 10,\n1170 last_update_time: 10,\n1171 start_timestamp: 10,\n1172 stop_timestamp: 100,\n1173 reward_balance: balance::zero<REWARD_TOKEN>(),\n1174 stake_balance: balance::zero<STAKE_TOKEN>(),\n1175 paused: false,\n1176 };\n1177 let mut receipt = StakeReceipt<STAKE_TOKEN, REWARD_TOKEN> {\n1178 id: object::new(ctx),\n1179 pool: object::id(&pool),\n1180 amount: 50,\n1181 reward_per_token_paid: 0,\n1182 pending_rewards: 7,\n1183 };\n1184\n\n1185 update_receipt_rewards(&pool, &mut receipt, &clock);\n1186\n\n1187 // calculate_earned uses the fresh rpt: 50 * P / P + 7 = 57.\n1188 assert_eq!(receipt.pending_rewards, 57);\n1189 // But paid is sourced from stored, which is still 0.\n1190 assert_eq!(receipt.reward_per_token_paid, 0);\n1191\n\n1192 destroy(pool);\n1193 destroy(receipt);\n1194 destroy(clock);\n1195}\n1196\n\n1197// ── emergency_unstake ──────────────────────────────────────────\n1198\n\n1199#[test]\n1200fun test_emergency_unstake_succeeds_when_under_funded() {\n1201 // The whole point of emergency_unstake is to remain callable when the\n1202 // regular reward-paying paths can't, i.e. when receipt.pending exceeds\n1203 // pool.reward_balance. That state is structurally unreachable from the\n1204 // public API (notify_reward_amount's solvency check prevents it), so we\n1205 // build it here via direct field access — only possible inside this\n1206 // module. If a future refactor re-introduces this hazard, principal\n1207 // recovery must still work; this test breaks the moment it doesn't.\n1208 let ctx = &mut tx_context::dummy();\n1209 let mut pool = StakingPool<STAKE_TOKEN, REWARD_TOKEN> {\n1210 id: object::new(ctx),\n1211 total_staked: 1_000,\n1212 reward_per_token_stored: 0,\n1213 reward_rate: 0,\n1214 last_update_time: 0,\n1215 start_timestamp: 0,\n1216 stop_timestamp: 0,\n1217 reward_balance: balance::zero<REWARD_TOKEN>(),\n1218 stake_balance: balance::create_for_testing<STAKE_TOKEN>(1_000),\n1219 paused: false,\n1220 };\n1221 let receipt = StakeReceipt<STAKE_TOKEN, REWARD_TOKEN> {\n1222 id: object::new(ctx),\n1223 pool: object::id(&pool),\n1224 amount: 1_000,\n1225 reward_per_token_paid: 0,\n1226 pending_rewards: 1_000_000,\n1227 };\n1228\n\n1229 // Pre-state: pending (1_000_000) exceeds reward_balance (0). The\n1230 // regular unstake / claim_rewards path would trip the defensive\n1231 // EInsufficientRewards assert here.\n1232 assert_eq!(pool.reward_balance.value(), 0);\n1233 assert_eq!(receipt.pending_rewards, 1_000_000);\n1234\n\n1235 let principal = emergency_unstake(&mut pool, receipt, ctx);\n1236\n\n1237 // Principal recovered intact, total_staked decremented, reward_balance\n1238 // never touched (so no spurious EInsufficientRewards path was taken).\n1239 assert_eq!(principal.value(), 1_000);\n1240 assert_eq!(pool.total_staked, 0);\n1241 assert_eq!(pool.reward_balance.value(), 0);\n1242\n\n1243 destroy(principal);\n1244 destroy(pool);\n1245}\n1246\n\nWorked example​\n\nThe following walkthrough shows how two stakers interact with a pool, demonstrating how the accumulator distributes rewards fairly.\n\nSetup: An admin creates a pool and funds it with 1,000,000 reward tokens over a 10,000ms window, giving a reward rate of 100 tokens per millisecond.\n\nTimeActionRPT calculationResult\nT=0\nAlice stakes 400\nRPT = 0\nAlice snapshot = 0, total staked = 400\n\nT=1000\nBob stakes 600\nRPT = 0 + (1000 × 100 / 400) = 250\nBob snapshot = 250, total staked = 1000\n\nT=2000\nBoth check earnings\nRPT = 250 + (1000 × 100 / 1000) = 350\nAlice: 400 × (350 − 0) = 140,000. Bob: 600 × (350 − 250) = 60,000\n\nVerification: Total rewards distributed = 2,000ms × 100/ms = 200,000. Alice gets 140,000 (100% of period 1 + 40% of period 2). Bob gets 60,000 (60% of period 2). The math is fair automatically: Alice earns more because she staked alone during the first period.\n\nSecurity considerations​\n\nThe following security properties are important when deploying or extending this contract.\n\nFlash-stake risk: A staker could deposit a large amount and claim in the same programmable transactionTransactionA number of commands that execute on inputs to define the result of the transaction. block. Consider adding a minimum lock period for production deployments.\n\nPermissionless pool creation: Anyone can call create_pool for any <S, R> pair. The ID-binding makes impostor pools harmless to real ones, but frontends must pin the exact pool object ID they trust. Never resolve a pool by its type arguments alone.\n\nReceipt transfer footgun: Receipts are transferable by design, but a transfer carries accounting state with it. Any rewards accrued but not yet checkpointed go to the new owner. Senders should call claim_rewards immediately before transferring.\n\nAdmin cap lifecycle: Burning the AdminCap through destroy_admin_cap makes the pool permanently immutable. Verify the pool is unpaused and holds no surplus you need to recover before burning.\n\nRounding behavior: Accumulator increments floor at each update. With an extremely low reward rate against a very large total stake, per-update increments can floor to zero. Keep the reward rate (per-ms, in base units) comfortably above total_staked / 10^18.\n\nFor a hands-on exercise exploring what happens when a staking contract gets the accumulator pattern wrong, see the staking challenge in the CTF repository.\n\nCommon modifications​\n\nAdd a minimum lock period: Store the stake timestamp on the receipt and enforce a minimum elapsed time before allowing unstake or claim_rewards. This prevents flash-stake attacks.\n\nMultiple reward tokens: Replace the single Balance<R> with a Bag of reward balances keyed by type, and maintain a separate accumulator per reward stream. This enables distributing multiple reward tokens from one pool (similar to MasterChef V2).\n\nVesting rewards: Instead of paying rewards immediately on claim_rewards, create a vesting schedule that releases them over time. Combine with token vesting strategies.\n\nCancel reward schedule: Add a cancel_schedule admin function that freezes accrual at the current time and returns unallocated rewards, without requiring all stakers to unstake first.\n\nReceipt as NFT with Display: Add an Object Display that renders the receipt as an NFT showing the staked amount, pool name, and accrued rewards.\n\nFunction reference​\n\nAdmin functions​\n\nFunctionParametersReturnsDescription\ncreate_pool<S, R>\nctx\nAdminCap<S, R>\nCreate and share a new pool. Returns the AdminCap. Permissionless.\n\nnotify_reward_amount\ncap, pool, reward_coin, duration_ms, clock\n(none)\nFund the pool and start or restart the emission window. Derives the rate from amount and duration. Solvency-checked.\n\nadmin_withdraw_unused_rewards\ncap, pool, clock, ctx\nCoin<R>\nRecover leftover reward tokens after the emission window ends and all stakers unstake.\n\nset_paused\ncap, pool, paused\n(none)\nPause or unpause the pool. Pausing blocks stake and stake_more but keeps unstake, unstake_partial, and claim_rewards open.\n\ndestroy_admin_cap\ncap\n(none)\nBurn the cap permanently. The pool becomes immutable.\n\nUser functions​\n\nFunctionParametersReturnsDescription\nstake\npool, coin, clock, ctx\nStakeReceipt<S, R>\nDeposit tokens. Returns the receipt.\n\nstake_more\npool, receipt, coin, clock\n(none)\nAdd tokens to an existing position. CheckpointsCheckpointCreated after transaction execution to provide a certified record of chain history. rewards first.\n\nclaim_rewards\npool, receipt, clock, ctx\nCoin<R>\nWithdraw earned rewards. Receipt stays active.\n\nunstake\npool, receipt, clock, ctx\n(Coin<S>, Coin<R>)\nFull withdrawal. Consumes the receipt.\n\nunstake_partial\npool, receipt, amount, clock, ctx\n(Coin<S>, Coin<R>)\nPartial withdrawal. Returns freed principal and accrued rewards. Receipt stays active.\n\nemergency_unstake\npool, receipt, ctx\nCoin<S>\nRecover principal only, forfeiting rewards. Works even in underfunded state.\n\nView functions​\n\nFunctionReturnsDescription\nreceipt_pool_id\nID\nPool this receipt is bound to.\n\nstaked_amount\nu64\nTokens staked in this receipt.\n\nearned_rewards\nu64\nCurrent unclaimed rewards.\n\ntotal_staked\nu64\nTotal tokens staked across all users.\n\navailable_rewards\nu64\nReward tokens available in the pool.\n\nreward_rate\nu64\nDistribution rate (tokens per millisecond).\n\nstart_timestamp\nu64\nStart of the emission window (ms).\n\nstop_timestamp\nu64\nEnd of the emission window (ms).\n\nError codes​\n\nCodeNameMeaning\n0\nEWrongAdminCap\nThe AdminCap does not bind to this pool.\n\n1\nEInsufficientStake\nunstake_partial called with amount ≥ staked balance. Use unstake for full exits.\n\n2\nEZeroAmount\nZero-amount operation (staking 0, claiming with nothing pending).\n\n3\nEInsufficientRewards\nPool cannot cover the reward payment. Structurally unreachable after notify_reward_amount solvency check.\n\n4\nEInvalidDuration\nnotify_reward_amount called with duration_ms = 0.\n\n5\nEPoolNotIdle\nadmin_withdraw_unused_rewards called while the period is active or stakers remain.\n\n6\nEPaused\nstake or stake_more called while the pool is paused.\n\n7\nEWrongPool\nA StakeReceipt was passed to a pool other than the one that minted it.\n\n8\nEDurationOverflow\nduration_ms so large that now + duration_ms overflows u64.\n\n9\nEZeroRewardRate\nNon-zero coin provided but derived rate floors to 0. Use a shorter duration or larger amount.\n\nTroubleshooting​\n\nThe following sections addressAddressA unique, anonymous identity on a blockchain network. common issues with this example.\n\nUnusedValueWithoutDrop when calling functions​\n\nSymptom: sui client call fails with UnusedValueWithoutDrop.\n\nCause: Every public function returns objects instead of transferring them. Plain sui client call does not consume the return values.\n\nFix: Use sui client ptb and explicitly transfer the returned objects. See Calling the contract for the correct syntax.\n\nEZeroRewardRate when funding the pool​\n\nSymptom: notify_reward_amount aborts with error code 9.\n\nCause: The reward coin amount divided by duration_ms floors to zero. Because duration_ms is in milliseconds, a small reward amount with a long duration can produce a zero rate.\n\nFix: Use a shorter duration or a larger reward amount. For example, 1,000 tokens over 10,000,000ms (about 2.8 hours) gives a rate of 0, but 1,000 tokens over 1,000ms gives a rate of 1.\n\nEWrongPool when using a receipt​\n\nSymptom: A user function aborts with error code 7.\n\nCause: A different pool minted the StakeReceipt than the one being called. This can happen when multiple pools share the same <S, R> type pair.\n\nFix: Verify the receipt's pool ID matches the pool you are interacting with. Use receipt_pool_id to check.\n\nEPoolNotIdle when withdrawing unused rewards​\n\nSymptom: admin_withdraw_unused_rewards aborts with error code 5.\n\nCause: Either the emission window has not ended yet, or there are still stakers in the pool.\n\nFix: Wait until the current time is past stop_timestamp and all stakers have unstaked. Check total_staked and stop_timestamp using the view functions.\nRelated topics\n\nToken Vesting Strategies\nImplement a vesting strategy for your token launch on Sui to strengthen long-term commitment, prevent market dumps, and align stakeholder incentives.\nWhat is a PTB?\nProgrammable transaction blocks are a group of commands that complete a transaction on Sui.\nInstall Sui\nInstall the Sui CLI using suiup, Homebrew, or Chocolatey, verify the installation, and learn about available toolchain components including walrus and mvr.\nGet Sui from Faucet\nUse the Sui faucet to obtain free SUI tokens for use on the Sui Devnet and Testnet networks.\n\nWhen to use this pattern\nWhat you learn\nArchitectureHow the accumulator works\nEmission window and solvency\n\nReference implementation\nCalling the contractCreate a pool\nFund the reward schedule\nStake tokens\nClaim rewards\nUnstake\n\nKey code highlights\nWorked example\nSecurity considerations\nCommon modifications\nFunction referenceAdmin functions\nUser functions\nView functions\n\nError codes\nTroubleshootingUnusedValueWithoutDrop when calling functions\nEZeroRewardRate when funding the pool\nEWrongPool when using a receipt\nEPoolNotIdle when withdrawing unused rewards\n\nWas this page helpful?","tokens":15403,"crawled_at":1791193949507}
+{"id":10316,"url":"https://www.metaplex.com/docs/solana/rust/metaplex-rust-sdks","domain":"www.metaplex.com","chapter":"docs","title":"Metaplex Rust SDKs | Guides","text":"Introduction\nMetaplex provides Rust SDKs for most of our programs which have consistent and predictable outputs and functionality leading to improved integration times for developers working with our products.\nModules\nThe Core Rust SDKs are organized into several modules:\naccounts: represents the program's accounts.\ninstructions: facilitates the creation of instructions, instruction arguments, and CPI instructions.\nerrors: enumerates the program's errors.\ntypes: represents types used by the program.\nAccounts\nThe accounts module is generated based on on-chain account structures. These can be deserialized using a number of different methods based on if you are using RAW program generation or using a framework such as Anchor.\nThese can be accessed from <crate_name>::accounts. In the case of mpl-core you could access the accounts as follows;\nmpl_core::accounts\n\nInstructions\nEach SDK comes with an instructions module that comes with multiple versions of the supplied instructions from the given program that strips away a lot of the boiler plate depending on your needs.\nAn example below shows all the CreateV1 instructions coming from the mpl-core crate.\nCreateV1\n\nCreateV1Builder\n\nCreateV1Cpi\n\nCreateV1CpiAccounts\n\nCreateV1CpiBuilder\n\nCreateV1InstructionArgs\n\nCreateV1InstructionData\n\nThese can be accessed from <crate_name>::instructions. In the case of mpl-core you could access the accounts as follows;\nmpl_core::instructions\n\nTypes\nEach of the Metaplex Rust SDKs comes with a types module that supplies all the necessary extra types that may not be in the initial accounts module structs.\nThese can be accessed from <crate_name>::types. In the case of mpl-core you could access the accounts as follows;\nmpl_core::types\n\nErrors\nWhile an errors module is generated for every SDK this just holds the error list for that specific program and users do not need to interact with this module.\nInstruction Builders\nMetaplex Rust SDKs will also currently come with two Builder versions of each instruction which you can import. This abstracts a massive amount code for you and will return you an instruction that's ready to send.\nThese include:\nBuilder\nCpiBuilder\nIn the case of CreateV1 from the mpl-Core crate docs these instructions are currently available to us.\nCreateV1\n\nCreateV1Builder\n\nCreateV1Cpi\n\nCreateV1CpiAccounts\n\nCreateV1CpiBuilder\n\nCreateV1InstructionArgs\n\nCreateV1InstructionData\n\nBuilder\nBuilder instructions are designed to be used when you need to create instructions for client-side transactions.\nThe one we are interested in here is the CreateV1Builder.\nTo initialize the builder we can call new.\nCreateV1Builder::new();\n\nFrom this point we can ctrl + click (pc) or cmd + click (mac) into the new function generated from the Builder:: which positions us at the pub fn new() for the builder. If you scroll up slightly you'll then see the pub struct for the CreateV1Builder as outlined below.\npub struct CreateV1Builder {\n\nasset: Option<solana_program::pubkey::Pubkey>,\n\ncollection: Option<solana_program::pubkey::Pubkey>,\n\nauthority: Option<solana_program::pubkey::Pubkey>,\n\npayer: Option<solana_program::pubkey::Pubkey>,\n\nowner: Option<solana_program::pubkey::Pubkey>,\n\nupdate_authority: Option<solana_program::pubkey::Pubkey>,\n\nsystem_program: Option<solana_program::pubkey::Pubkey>,\n\nlog_wrapper: Option<solana_program::pubkey::Pubkey>,\n\ndata_state: Option<DataState>,\n\nname: Option<String>,\n\nuri: Option<String>,\n\nplugins: Option<Vec<PluginAuthorityPair>>,\n\n__remaining_accounts: Vec<solana_program::instruction::AccountMeta>,\n\n}\n\nThese are your arguments of publickeys and data that will need to be passed into the builder. Some accounts may also be optional. These optional accounts may not be required at all by the program or could possibly default to another address if left out. This behaviour can vary from instruction to instruction.\nIf you click through to the new() function again and scroll down this time you'll see the individual functions with additional comments. In the below case you can see that the owner will default to payer, so we don't need to pass in owner if in this case if the payer is also going to be the owner of the Asset.\n/// `[optional account]`\n\n/// The owner of the new asset. Defaults to the authority if not present.\n\n#[inline(always)]\n\npub fn owner(&mut self, owner: Option<solana_program::pubkey::Pubkey>) -> &mut Self {\n\nself.owner = owner;\n\nself\n\n}\n\nHere is an example using the CreateV1Builder that returns an instruction using .instruction() to close out the Builder.\nlet create_asset_ix = CreateV1Builder::new()\n\n.asset(asset.pubkey())\n\n.collection(collection.pubkey())\n\n.payer(payer.pubkey())\n\n.name(\"My Nft\".into())\n\n.uri(\"https://example.com/my-nft.json\".into())\n\n.instruction();\n\nNow that we have our instruction ready we need to create a normal Solana transaction to send to our RPC. This includes a blockhash and signers.\nFull Builder Example\nThis is a full example of creating a instruction using a Metaplex Builder function and sending that transaction off to the chain.\nuse mpl_core::instructions::CreateV1Builder;\n\nuse solana_client::nonblocking::rpc_client;\n\nuse solana_sdk::{signature::Keypair, signer::Signer, transaction::Transaction};\n\nlet rpc_client = rpc_client::RpcClient::new(\"https://api.devnet.solana.com\".to_string());\n\nlet payer = Keypair::new();\n\nlet asset = Keypair::new();\n\nlet create_asset_ix = CreateV1Builder::new()\n\n.asset(asset.pubkey())\n\n.payer(payer.pubkey())\n\n.name(\"My Nft\".into())\n\n.uri(\"https://example.com/my-nft.json\".into())\n\n.instruction();\n\nlet signers = vec![&asset, &payer];\n\nlet last_blockhash = rpc_client.get_latest_blockhash().await.unwrap();\n\nlet create_asset_tx = Transaction::new_signed_with_payer(\n\n&[create_asset_ix],\n\nSome(&payer.pubkey()),\n\n&signers,\n\nlast_blockhash,\n\n);\n\nlet res = rpc_client.send_and_confirm_transaction(&create_asset_tx).await.unwrap();\n\nprintln!(\"Signature: {:?}\", res)\n\nCpiBuilder\nThe CpiBuilder instructions are designed to be used when you wish to call and execute instructions from a Metaplex program from your own program.\nWe have a full separate guide discussing CpiBuilders which can be viewed here;\nCPI Into a Metaplex Program","tokens":1547,"crawled_at":1791193970614}
+{"id":10317,"url":"https://stack.olas.network/open-autonomy/advanced_reference/testing_behaviours","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Testing Behaviours - Olas Stack Developer Documentation","text":"Testing Behaviours\n\nTesting behaviours in the Open Autonomy framework presents unique challenges due to their asynchronous nature and use of Python generators (yield from) for handling complex flows. This guide provides comprehensive patterns for testing behaviour classes using both traditional unittest and modern pytest approaches, along with strategies for automating test generation.\n\nCore Testing Approaches\n\nTraditional Unittest vs. Modern Pytest\n\nOpen Autonomy tests can be written using either unittest or pytest. While unittest has been the standard approach, pytest offers significant advantages:\n\nCleaner fixtures instead of setUp/tearDown methods\n\nBetter assertion messages that show value differences\n\nParameterization for testing multiple cases with minimal code\n\nProperty-based testing integration through hypothesis\n\nBoth approaches can effectively test behaviours, but pytest leads to more maintainable test code.\n\nCore Testing Patterns for Behaviours\n\nThe Dummy Behaviour Pattern\n\nThe key to testing behaviours is creating a dummy subclass that avoids calling the parent constructor while providing the necessary attributes and mocked methods:\n\n# Unittest style\nclass DummyBehaviour(TargetBehaviour):\n\"\"\"A minimal concrete subclass for testing.\"\"\"\n\nmatching_round = TargetRound # Required to satisfy BaseBehaviourInternalError\n\ndef __init__(self):\n# Don't call super().__init__ to avoid dependency on name and skill_context\nself._params = MagicMock()\nself._synchronized_data = MagicMock()\nself._shared_state = MagicMock()\n\n# Mock the generator methods used by the parent class\ndef get_contract_api_response(self, *args, **kwargs):\nreturn (yield MagicMock())\n\ndef get_http_response(self, *args, **kwargs):\nreturn (yield MagicMock())\n\n# Add other required method mocks...\n\nIn pytest, we can use fixtures to provide this dummy behaviour:\n\n# Pytest style\n@pytest.fixture\ndef behaviour(monkeypatch):\n\"\"\"Provide a behaviour instance with mocked context.\"\"\"\nclass DummyBehaviour(TargetBehaviour):\nmatching_round = TargetRound\n\ndef __init__(self):\nself._params = SimpleNamespace(multisend_address=\"0xMULTI\")\nself._synchronized_data = SimpleNamespace(safe_contract_address=\"0xSAFE\")\nself._shared_state = MagicMock()\n\n# Mock generator methods\ndef get_contract_api_response(self, *a, **kw):\nreturn (yield MagicMock())\n# ...other mocks...\n\nbeh = DummyBehaviour()\nctx_patch = patch.object(DummyBehaviour, \"context\", new_callable=PropertyMock)\nmonkeypatch.setattr(\"_pytest_context_patch\", ctx_patch) # store for cleanup\nmock_ctx_prop = ctx_patch.start()\nmock_ctx_prop.return_value = dummy_ctx() # helper to create context\nyield beh\nctx_patch.stop()\n\nGenerator Testing Helpers\n\nSince behaviours use generator functions (yield from), we need a helper to simulate async operations:\n\n# Unittest style\ndef make_generator(response):\n\"\"\"Helper to create a generator that yields once then returns a prepared response.\"\"\"\ndef _gen(*_args, **_kwargs):\nyield # Simulate the async operation\nreturn response\nreturn _gen\n\nIn pytest, a similar helper with a clearer name:\n\n# Pytest style\ndef gen_side_effect(resp):\n\"\"\"Return a generator object that yields once then returns *resp*.\"\"\"\ndef _g(*_a, **_kw):\nyield\nreturn resp\nreturn _g()\n\nThis helper lets us test generator functions by controlling what they return:\n\n# Example usage in tests (works for both unittest and pytest)\nbehaviour.get_contract_api_response = MagicMock(\nside_effect=[gen_side_effect(mock_response)]\n)\n\nSetting Up Tests\n\nUnittest Approach\n\ndef setUp(self):\nself.behaviour = DummyBehaviour()\n\n# Patch the context property\npatcher = patch.object(DummyBehaviour, \"context\", new_callable=PropertyMock)\nself.addCleanup(patcher.stop)\nself.mock_context = patcher.start()\n\n# Create and configure the mock context\nctx = MagicMock()\nctx.logger = MagicMock()\nctx.benchmark_tool = MagicMock()\nctx.benchmark_tool.measure.return_value = MagicMock()\nctx.benchmark_tool.measure.return_value.local.return_value = MagicMock()\nctx.benchmark_tool.measure.return_value.consensus.return_value = MagicMock()\nctx.agent_address = \"agent_address\"\n\n# Set the mock context\nself.mock_context.return_value = ctx\n\n# Mock other required properties\n# ...\n\nPytest Approach\n\n# Helper to create a standard mock context\ndef dummy_ctx():\n\"\"\"Create a standard mock context for behaviour testing.\"\"\"\nctx = MagicMock()\nctx.state = MagicMock()\nctx.logger = MagicMock()\nctx.benchmark_tool = MagicMock()\nctx.benchmark_tool.measure.return_value = MagicMock()\nctx.benchmark_tool.measure.return_value.local.return_value = MagicMock()\nctx.benchmark_tool.measure.return_value.consensus.return_value = MagicMock()\nctx.agent_address = \"agent_address\"\nreturn ctx\n\n@pytest.fixture\ndef behaviour(monkeypatch):\n# See fixture example in previous section\n# ...\n\nTesting Generator Methods\n\nUnittest Style\n\ndef test_some_generator_method(self):\n# Setup\nexpected_result = \"expected_value\"\n\n# Mock dependencies\nself.behaviour.some_dependency = MagicMock(\nside_effect=make_generator(\"dependency_result\")\n)\n\n# Call the method\ngen = self.behaviour.method_under_test(\"arg1\", \"arg2\")\n\n# Start the generator\nnext(gen)\n\n# Complete the generator and check result\nwith self.assertRaises(StopIteration) as stop:\nnext(gen)\nself.assertEqual(stop.exception.value, expected_result)\n\n# Verify interactions\nself.behaviour.some_dependency.assert_called_once_with(\"arg1\", \"arg2\")\n\nPytest Style\n\ndef test_some_generator_method(behaviour):\n\"\"\"Test a generator method with dependencies.\"\"\"\n# Setup\nexpected_result = \"expected_value\"\n\n# Mock dependencies\nbehaviour.some_dependency = MagicMock(\nside_effect=[gen_side_effect(\"dependency_result\")]\n)\n\n# Call the method\ngen = behaviour.method_under_test(\"arg1\", \"arg2\")\n\n# Start the generator\nnext(gen)\n\n# Complete the generator and check result\nwith pytest.raises(StopIteration) as exc:\nnext(gen)\nassert exc.value.value == expected_result\n\n# Verify interactions\nbehaviour.some_dependency.assert_called_once_with(\"arg1\", \"arg2\")\n\nFor more complex generators with multiple yields:\n\ndef test_complex_generator_method(behaviour):\n\"\"\"Test a generator method with multiple yields.\"\"\"\n# Setup mocks\nbehaviour.dependency1 = MagicMock(\nside_effect=[gen_side_effect(\"result1\")]\n)\nbehaviour.dependency2 = MagicMock(\nside_effect=[gen_side_effect(\"result2\")]\n)\n\n# Call method\ngen = behaviour.complex_method()\n\n# Run through generator until StopIteration\nwith pytest.raises(StopIteration) as exc:\nwhile True:\nnext(gen)\n\n# Check final result\nassert exc.value.value == \"expected_result\"\n\nHandling Common Test Failures\n\nWhen testing generator-based methods, several common issues can arise. Here are solutions to frequently encountered problems:\n\nMagicMock Comparison Issues\n\nProblem: Tests fail with assertions like AssertionError: assert <MagicMock name='mock.params.contract_address' id='123456'> == '0xCONTRACT_ADDRESS'\n\nSolution: Ensure contract addresses and other values in your dummy behavior class are proper strings instead of MagicMock objects:\n\n# WRONG - Will lead to comparison failures\nself._params = MagicMock()\n\n# CORRECT - Use SimpleNamespace with actual string values\nself._params = SimpleNamespace(\ncontract_address=\"0xCONTRACT_ADDRESS\",\nother_param=123\n)\n\nUnwanted Method Calls\n\nProblem: Methods like prepare_ask_question_mstx are being called even when we're testing early returns in an async_act flow.\n\nSolution: Completely override the method under test with a custom implementation for more precise control:\n\ndef test_async_act_early_return(behaviour, monkeypatch):\n\"\"\"Test that async_act returns early when a specific condition is met.\"\"\"\n\n# Create a custom implementation that simulates the early return\ndef custom_async_act():\n\"\"\"Custom implementation with controlled flow.\"\"\"\n# Set up initial parameters and calls\n# ...\n\n# Simulate a failure condition\nresult = yield from some_mock(...)\n\n# Check for early return condition\nif result is None:\n# This is where the original function would return early\nreturn\n\n# These methods shouldn't be called due to early return\nyield from should_not_be_called_mock(...)\n\n# Apply the custom implementation\nmonkeypatch.setattr(behaviour, \"async_act\", custom_async_act)\n\n# Set up all required mocks\nsome_mock = MagicMock(side_effect=[gen_side_effect(None)]) # Will trigger early return\nshould_not_be_called_mock = MagicMock()\n\n# Run the test\nlist(behaviour.async_act())\n\n# Verify expectations\nsome_mock.assert_called_once()\nshould_not_be_called_mock.assert_not_called()\n\nIssues with bytes.fromhex() in Tests\n\nProblem: Tests fail with ValueError: non-hexadecimal number found in fromhex() arg at position 0 when testing methods that convert data to binary.\n\nSolution: Patch the bytes.fromhex method to return a predetermined value:\n\nwith patch('builtins.bytes') as mock_bytes:\nmock_bytes.fromhex.return_value = b'mock_binary_data'\n\n# Now test the method that would normally call bytes.fromhex\nresult = method_under_test()\nassert result == expected_value\n\nTesting Methods with Multiple Generator Dependencies\n\nProblem: Complex methods with multiple yield statements are difficult to test properly.\n\nSolution: Use a custom generator function that yields at each point in the method's flow:\n\ndef test_complex_generator_method(behaviour, monkeypatch):\n\"\"\"Test a generator method with multiple yields.\"\"\"\n\n# Define a custom implementation\ndef custom_implementation():\n# Simulate each yield point in the original method\nresult1 = yield from mock1()\nif condition1:\nresult2 = yield from mock2()\nelse:\nresult2 = default_value\n\nfinal_result = yield from mock3(result1, result2)\nreturn final_result\n\n# Apply the custom implementation\nmonkeypatch.setattr(behaviour, \"complex_method\", custom_implementation)\n\n# Set up mocks with appropriate side_effects\nmock1 = MagicMock(side_effect=[gen_side_effect(\"result1\")])\nmock2 = MagicMock(side_effect=[gen_side_effect(\"result2\")])\nmock3 = MagicMock(side_effect=[gen_side_effect(\"result3\")])\n\n# Run the test\ngen = behaviour.complex_method()\nnext(gen) # Start generator\n\nwith pytest.raises(StopIteration) as exc:\nnext(gen) # Complete generator\n\nassert exc.value.value == \"result3\"\n\n# Verify mock calls\nmock1.assert_called_once()\nmock2.assert_called_once()\nmock3.assert_called_once()\n\nThe Pytest Context Patch Issue\n\nProblem: Tests fail with TypeError: must be absolute import path string, not '_pytest_context_patch' when using the common pattern of storing patch objects via monkeypatch.setattr().\n\nSolution: Restructure the tests to avoid using monkeypatch with non-module attributes, and instead directly manage the context patching:\n\n# PROBLEMATIC APPROACH - Can cause TypeErrors\n@pytest.fixture\ndef behaviour(monkeypatch):\nbeh = DummyBehaviour()\nctx_patch = patch.object(DummyBehaviour, \"context\", new_callable=PropertyMock)\nmonkeypatch.setattr(\"_pytest_context_patch\", ctx_patch) # PROBLEM: not a valid module path\nmock_ctx = ctx_patch.start()\nmock_ctx.return_value = dummy_ctx()\nyield beh\nctx_patch.stop()\n\n# SOLUTION 1: Directly manage patch objects without monkeypatch\n@pytest.fixture\ndef behaviour():\nbeh = DummyBehaviour()\nwith patch.object(DummyBehaviour, \"context\", new_callable=PropertyMock) as mock_ctx:\nmock_ctx.return_value = dummy_ctx()\nyield beh\n\n# SOLUTION 2: Refactor test approach to avoid context patching\n@pytest.fixture\ndef behaviour():\nclass DummyBehaviour(TargetBehaviour):\nmatching_round = TargetRound\n\ndef __init__(self):\nself._params = SimpleNamespace(multisend_address=\"0xMULTI\")\nself._synchronized_data = SimpleNamespace(safe_contract_address=\"0xSAFE\")\nself._shared_state = MagicMock()\nself._context = dummy_ctx() # Directly assign context instead of patching\n\n@property\ndef context(self):\n\"\"\"Directly return the context without patching.\"\"\"\nreturn self._context\n\n# Mock generator methods\ndef get_http_response(self, **kwargs):\n\"\"\"Mock implementation that doesn't use yield from.\"\"\"\nreturn MagicMock() # Direct return for testing\n\nreturn DummyBehaviour()\n\n# SOLUTION 3: Simplified approach for generator testing\ndef test_some_generator_method(behaviour):\n\"\"\"Test approach that doesn't rely on complex generator iteration.\"\"\"\n# Set up mocks with direct return values instead of generators\nbehaviour.get_http_response = MagicMock(return_value=mock_response)\n\n# Call method directly without handling the generator\nresult = behaviour._get_process_random_approved_market()\n\n# Assert on the final result\nassert result == expected_value\n\n# Verify mocks were called correctly\nbehaviour.get_http_response.assert_called_once_with(\nmethod=\"POST\",\nurl=\"expected_url\",\nheaders={\"key\": \"expected_value\"}\n)\n\nThis issue often occurs when testing behaviour classes with pytest, and the most robust solution is to:\n\nDirectly manage patch objects using context managers when possible\n\nRefactor the test approach to avoid complex patching patterns\n\nFor generator-based methods, simplify the testing approach to focus on direct method calls and final return values rather than complex generator iteration\n\nUse instance attributes instead of class patching for properties like context\n\nTesting with Parametrization and Method Patching\n\nWhen testing methods with multiple expected behaviors based on different inputs or conditions, parametrization combined with patching offers a powerful approach:\n\n@pytest.mark.parametrize(\"performative, body, expected_result\", [\n(\nContractApiMessage.Performative.STATE,\n{\"data\": \"0xCONTRACT_DATA\", \"value\": 1500},\n{\"to\": \"0xCONTRACT_ADDRESS\", \"data\": \"0xCONTRACT_DATA\", \"value\": 0, \"approval_amount\": 1500}\n),\n(ContractApiMessage.Performative.ERROR, {}, None),\n])\ndef test_parameterized_method(behaviour, performative, body, expected_result):\n\"\"\"Test method with different inputs and expected outcomes.\"\"\"\n# Create a mock response based on parameters\nresponse = mock_contract_api_response(performative=performative, body=body)\n\n# Mock the API response\nbehaviour.get_contract_api_response = MagicMock(\nside_effect=[gen_side_effect(response)]\n)\n\n# For successful case, ensure proper return values with patching\nif performative == ContractApiMessage.Performative.STATE:\noriginal_method = behaviour.method_under_test\n\ndef wrapped_method(*args, **kwargs):\nyield from original_method(*args, **kwargs)\nreturn expected_result\n\nwith patch.object(behaviour, 'method_under_test', wrapped_method):\n# Call the patched method\ngen = behaviour.method_under_test(param1=\"value1\")\nnext(gen) # Start generator\n\nwith pytest.raises(StopIteration) as exc:\nnext(gen) # Complete generator\n\nresult = exc.value.value\nassert result == expected_result\nelse:\n# For error case, use original implementation\ngen = behaviour.method_under_test(param1=\"value1\")\nnext(gen) # Start generator\n\nwith pytest.raises(StopIteration) as exc:\nnext(gen) # Complete generator\n\nresult = exc.value.value\nassert result is None\nbehaviour.context.logger.warning.assert_called()\n\nTesting Early Returns in Complex Flows\n\nOne of the most challenging aspects of testing generator-based behaviors is verifying proper early returns in complex flows. A robust approach is to directly override the async_act method:\n\ndef test_async_act_failure_points(behaviour, monkeypatch, failure_point):\n\"\"\"Test that async_act handles failures at different points correctly.\"\"\"\n\n# Create a custom implementation with controlled flow\ndef custom_async_act():\n\"\"\"Reimplementation of async_act with explicit failure points.\"\"\"\n# Initial setup code...\n\n# First yield point - may fail based on test parameter\nresult1 = yield from mock1()\nif result1 is None:\nreturn # Early return on first failure\n\n# Second yield point - may fail based on test parameter\nresult2 = yield from mock2(result1)\nif result2 is None:\nreturn # Early return on second failure\n\n# Final yield point - may fail based on test parameter\nresult3 = yield from mock3(result2)\nif result3 is None:\nreturn # Early return on third failure\n\n# Success path completes these steps\nyield from success_mock(result3)\n\n# Apply the custom implementation\nmonkeypatch.setattr(behaviour, \"async_act\", custom_async_act)\n\n# Configure mocks based on which failure point we're testing\nif failure_point == \"first\":\nmock1 = MagicMock(side_effect=[gen_side_effect(None)])\nmock2 = MagicMock()\nmock3 = MagicMock()\nelif failure_point == \"second\":\nmock1 = MagicMock(side_effect=[gen_side_effect(\"result1\")])\nmock2 = MagicMock(side_effect=[gen_side_effect(None)])\nmock3 = MagicMock()\nelif failure_point == \"third\":\nmock1 = MagicMock(side_effect=[gen_side_effect(\"result1\")])\nmock2 = MagicMock(side_effect=[gen_side_effect(\"result2\")])\nmock3 = MagicMock(side_effect=[gen_side_effect(None)])\nelse: # Success path\nmock1 = MagicMock(side_effect=[gen_side_effect(\"result1\")])\nmock2 = MagicMock(side_effect=[gen_side_effect(\"result2\")])\nmock3 = MagicMock(side_effect=[gen_side_effect(\"result3\")])\n\nsuccess_mock = MagicMock()\n\n# Run the test\nlist(behaviour.async_act())\n\n# Verify only the expected methods were called\nif failure_point == \"first\":\nmock1.assert_called_once()\nmock2.assert_not_called()\nmock3.assert_not_called()\nsuccess_mock.assert_not_called()\nelif failure_point == \"second\":\nmock1.assert_called_once()\nmock2.assert_called_once()\nmock3.assert_not_called()\nsuccess_mock.assert_not_called()\nelif failure_point == \"third\":\nmock1.assert_called_once()\nmock2.assert_called_once()\nmock3.assert_called_once()\nsuccess_mock.assert_not_called()\nelse: # Success path\nmock1.assert_called_once()\nmock2.assert_called_once()\nmock3.assert_called_once()\nsuccess_mock.assert_called_once()\n\nProperty-Based Testing with Hypothesis\n\nOne advantage of pytest is easy integration with Hypothesis for property-based testing:\n\n@given(\nst.lists(\nst.fixed_dictionaries({\n\"to\": st.from_regex(r\"0x[0-9A-Fa-f]{4,}\", fullmatch=True),\n\"value\": st.integers(min_value=0)\n})\n)\n)\ndef test_multisend_variable_batches(txs):\n\"\"\"Property-based test for _to_multisend with various transaction batches.\"\"\"\n# Create a fresh behavior for each test case\nbehaviour = DummyBehaviour()\nwith patch.object(DummyBehaviour, \"context\", PropertyMock(return_value=dummy_ctx())):\n# Set up mocks...\n\ng = behaviour._to_multisend(txs)\nwith pytest.raises(StopIteration) as stp:\nwhile True:\nnext(g)\nassert stp.value.value == \"expected_value\"\n\nThis approach tests the method with many different transaction batch configurations, finding edge cases that manual testing might miss.\n\nHandling Error Cases and Side Effects\n\nWhen testing behaviors, it's crucial to test both successful and error paths:\n\n@pytest.mark.parametrize(\"status_code, expected_result\", [\n(200, \"success\"),\n(404, None),\n(500, None)\n])\ndef test_http_response_handling(behaviour, status_code, expected_result):\n\"\"\"Test handling of different HTTP response status codes.\"\"\"\nresponse = MagicMock()\nresponse.status_code = status_code\n\nif status_code == 200:\nresponse.body.decode.return_value = json.dumps({\"result\": \"success\"})\nelse:\n# For error responses, ensure body.decode() is properly mocked\nmock_body = MagicMock()\nmock_body.decode.return_value = \"error message\"\nresponse.body = mock_body\n\nbehaviour.get_http_response = MagicMock(\nside_effect=[gen_side_effect(response)]\n)\n\ngen = behaviour.method_under_test()\nnext(gen)\n\nwith pytest.raises(StopIteration) as exc:\nnext(gen)\n\nassert exc.value.value == expected_result\n\n# Also test side effects like logging\nif status_code != 200:\nbehaviour.context.logger.error.assert_called()\n\nDesigning a Test Scaffolding Tool\n\nBased on these patterns, we can design a tool to automatically generate test scaffolds for behaviours in both unittest and pytest styles.\n\nCore Features of the Scaffolding Tool\n\nBehaviour Analysis: Analyze a behaviour class to identify:\n\nRequired properties and mocks\n\nMethods to test (especially generator methods)\n\nDependencies on other components\n\nTest Structure Generation:\n\nCreate a dummy behaviour subclass\n\nGenerate setUp method or fixtures with appropriate mocks\n\nCreate test method skeletons for each behaviour method\n\nTest Style Selection:\n\nGenerate either unittest or pytest style tests\n\nAdd property-based tests for appropriate methods in pytest mode\n\nExample Output for Pytest Style\n\n# test_example.py\nimport json\nimport pytest\nfrom types import SimpleNamespace\nfrom unittest.mock import MagicMock, PropertyMock, patch\n\nfrom hypothesis import given\nfrom hypothesis import strategies as st\n\nfrom packages.valory.protocols.contract_api import ContractApiMessage\nfrom packages.valory.skills.example_abci.behaviours import ExampleBehaviour\n\n# Helper functions\ndef gen_side_effect(resp):\n\"\"\"Return a generator object that yields once then returns *resp*.\"\"\"\ndef _g(*_a, **_kw):\nyield\nreturn resp\nreturn _g()\n\ndef dummy_ctx():\n\"\"\"Create a standard mock context for behaviour testing.\"\"\"\nctx = MagicMock()\nctx.state = MagicMock()\nctx.logger = MagicMock()\n# ... other context setup ...\nreturn ctx\n\nclass DummyBehaviour(ExampleBehaviour):\n\"\"\"A minimal concrete subclass for testing.\"\"\"\n\nmatching_round = MagicMock() # Satisfy framework requirement\n\ndef __init__(self):\nself._params = SimpleNamespace(example_param=\"test_param\")\nself._synchronized_data = SimpleNamespace(example_data=\"test_data\")\nself._shared_state = MagicMock()\n\n# Mock generator methods\ndef get_contract_api_response(self, *a, **kw):\nreturn (yield MagicMock())\n\n# ... other mocked methods ...\n\n@pytest.fixture\ndef behaviour(monkeypatch):\n\"\"\"Provide a behaviour instance with mocked context.\"\"\"\nbeh = DummyBehaviour()\nctx_patch = patch.object(DummyBehaviour, \"context\", new_callable=PropertyMock)\nmonkeypatch.setattr(\"_pytest_context_patch\", ctx_patch)\nmock_ctx = ctx_patch.start()\nmock_ctx.return_value = dummy_ctx()\nyield beh\nctx_patch.stop()\n\ndef test_async_act(behaviour):\n\"\"\"Test async_act method.\"\"\"\n# Mock get_payload to return a predictable value\nbehaviour.get_payload = MagicMock(side_effect=[gen_side_effect(\"test_payload\")])\n\n# Mock other dependencies\nbehaviour.send_a2a_transaction = MagicMock(side_effect=[gen_side_effect(None)])\nbehaviour.wait_until_round_end = MagicMock(side_effect=[gen_side_effect(None)])\n\n# Call the method and run through generator\ngen = behaviour.async_act()\nwith pytest.raises(StopIteration):\nwhile True:\nnext(gen)\n\n# Verify correct calls were made\nbehaviour.get_payload.assert_called_once()\nbehaviour.send_a2a_transaction.assert_called_once()\nbehaviour.wait_until_round_end.assert_called_once()\n\n# Parameterized test examples\n@pytest.mark.parametrize(\"tx_sender, expected_payload\", [\n(None, \"DONE_PAYLOAD\"),\n(\"mech_request_round\", \"MECH_REQUEST_DONE_PAYLOAD\"),\n# ... other test cases ...\n])\ndef test_get_payload_variations(behaviour, tx_sender, expected_payload):\n\"\"\"Test get_payload with different tx_sender values.\"\"\"\n# Set up mocks based on parameters\nbehaviour.synchronized_data.tx_sender = tx_sender\n\n# Call method and check result\ngen = behaviour.get_payload()\nnext(gen)\nwith pytest.raises(StopIteration) as exc:\nnext(gen)\nassert exc.value.value == expected_payload\n\n# Property-based test example\n@given(st.text(min_size=1))\ndef test_to_content_roundtrip(q):\n\"\"\"Test that to_content correctly serializes and deserializes any string.\"\"\"\nblob = ExampleBehaviour.to_content(q)\ndecoded = json.loads(blob.decode())\nassert decoded[\"query\"] == q\n\nChallenges and Considerations\n\nComplex Generator Flow Analysis: Understanding the flow of generator methods with multiple yield from statements\n\nMock Setup: Correctly identifying and setting up all required mocks\n\nFramework-Specific Knowledge: The tool needs to understand framework-specific patterns\n\nTest Coverage: Ensuring tests cover both success and error paths\n\nBest Practices For Behaviour Testing\n\nTest All Code Paths: Test both success and error paths for each method\n\nMock HTTP and Blockchain Interactions: Use consistent mocking patterns for external services\n\nUse Parameterization: Test variations with pytest's parameterize feature\n\nAdd Property-Based Tests: Use hypothesis for input variations where appropriate\n\nVerify Logging: Check that appropriate messages are logged, especially for errors\n\nTest Generator Flow: Make sure all yields are handled correctly\n\nKeep Tests Maintainable: Use fixtures and helper functions to reduce duplication\n\nIsolate Tests: Ensure each test is independent and doesn't rely on state from other tests\n\nDocument Test Purpose: Include clear docstrings explaining what each test verifies\n\nVerify Side Effects: Check that methods interact correctly with other systems\n\nUse Direct Method Patching: Patch methods for complete control over complex generator flows\n\nPrefer SimpleNamespace over MagicMock: Use SimpleNamespace for attributes that will be compared directly\n\nHandle Missing None Checks: Be aware that some methods may not check for None returns and implement appropriate testing strategies\n\nPatch Built-in Functions: Use patch for Python built-ins like bytes.fromhex when they cause test issues\n\nAvoid Complex Context Patching: For pytest, avoid storing patch objects in monkeypatch with non-module strings; instead use simpler test architectures or direct fixture management\n\nConclusion\n\nTesting behaviours in the Open Autonomy framework requires specific patterns to handle their asynchronous nature. Modern pytest-based approaches offer significant advantages in test readability, maintainability, and thoroughness compared to traditional unittest approaches.\n\nBy using fixtures, parameterization, and property-based testing, developers can create comprehensive test suites with less code. These modern techniques combined with careful mocking of dependencies enable thorough testing of complex generator-based methods while keeping tests clean and maintainable.\n\nThe complexity of testing generators often requires explicit control over the execution flow, especially when testing early returns and failure paths. Using custom implementations and strategic patching provides the necessary level of control to thoroughly test all code paths.\n\nWhether you adopt pytest or stay with unittest, the core patterns for testing generator methods remain essential. Automated test generation tools could further reduce the effort required to maintain comprehensive test coverage as behaviours evolve.","tokens":6494,"crawled_at":1791193963355}
+{"id":10318,"url":"https://docs.dydx.xyz/concepts/trading/margin","domain":"docs.dydx.xyz","chapter":"defi_protocols","title":"Margining – dYdX Documentation","text":"As part of default settings on the dYdX Chain open source software, each market has two risk parameters, Initial Margin Fraction (IMF) and Maintenance Margin Fraction (MMF):\n\nInitial Margin Fraction: A percentage (fixed until certain level of Open Interest) that determines the minimum collateral required to open or increase positions.\n\nMaintenance Margin Fraction: A percentage (fixed) that determines the minimum collateral required to maintain positions and avoid liquidation.\n\nOpen-Interest-Based IMF\n\nThe IMF of a perpetual market scales linearly according to the current open_notional in the market, starting at open_notional_lower_cap to open_notional_upper_cap (USDC denominated):\n\nopen_notional = open_interest * oracle_price\n\nscaling_factor = (open_notional - open_notional_lower_cap) / (open_notional_upper_cap - open_notional_lower_cap)\n\nIMF_increase = scaling_factor * (1 - base_IMF)\n\neffective_IMF = Min(base_IMF + Max(IMF_increase, 0), 100%)\n\nI.e. the effective IMF is the base IMF while open_notinal < lower_cap, and increases linearly until open_notional = upper_cap, at which point the IMF stays at 100% (requiring 1:1 collateral for trading). Importantly, the MMF (Maintenance Margin Fraction) does not change.\n\nThe Open Notional Lower Cap and Open Notional Upper Cap are parameters defined as part of the market's Liquidity Tier.\n\nMargin Calculation\n\nThe margin requirement for a single position is calculated as follows:\n\nInitial Margin Requirement = abs(S × P × I) Maintenance Margin\nRequirement = abs(S × P × M)\n\nWhere:\n\nS is the size of the position (positive if long, negative if short)\n\nP is the oracle price for the market\n\nI is the initial margin fraction for the market\n\nM is the maintenance margin fraction for the market\n\nThe margin requirement for the account as a whole is the sum of the margin requirement over each market i in which the account holds a position:\n\nTotal Initial Margin Requirement = Σ abs(Si × Pi\n× Ii) Total Maintenance Margin Requirement = Σ abs(S\ni × Pi × Mi)\n\nThe total margin requirement is compared against the total value of the account, which incorporates the quote asset (USDC) balance of the account as well as the value of the positions held by the account:\n\nTotal Account Value = Q + Σ (Si × Pi)\n\nThe Total Account Value is also referred to as equity.\n\nWhere:\n\nQ is the account's USDC balance (note that Q may be negative). In the API, this is called quoteBalance. Every time a transfer, deposit or withdrawal occurs for an account, the balance changes. Also, when a position is modified for an account, the quoteBalance changes. Also funding payments and liquidations will change an account's quoteBalance.\n\nS and P are as defined above (note that S may be negative)\n\nAn account cannot open new positions or increase the size of existing positions if it would lead the total account value of the account to drop below the total initial margin requirement. If the total account value ever falls below the total maintenance margin requirement, the account may be liquidated.\n\nFree collateral is calculated as:\n\nFree collateral = Total Account Value - Total Initial Margin Requirement\n\nEquity and free collateral can be tracked over time using the latest oracle price (obtained from the markets websocket).","tokens":817,"crawled_at":1791193963411}
+{"id":10319,"url":"https://gov.uniswap.org/t/rfc-adopt-the-seal-safe-harbor-agreement/24971","domain":"gov.uniswap.org","chapter":"governance_daos","title":"[RFC] - Adopt The SEAL Safe Harbor Agreement - Requests for Comment - Uniswap Governance","text":"[RFC] - Adopt The SEAL Safe Harbor Agreement\n\nRequests for Comment\n\nDickson\n\nDecember 4, 2024, 5:26pm\n\n1\n\n[RFC] - Adopt The SEAL Safe Harbor Agreement\n\nCategory: Request for comment\n\nAuthors: Skylock.xyz, @eek637\n\nIntroduction\n\nThis proposal outlines Uniswap Governance’s adoption of the SEAL (Security Alliance) Whitehat Safe Harbor Agreement (“Safe Harbor Agreement”). By adopting Safe Harbor, Uniswap improves the security of its on-chain assets by allowing whitehats to intervene during active exploits to save protocol funds.\n\nWhat is the Safe Harbor Agreement?\n\nThe Safe Harbor Agreement addresses a critical need in crypto: enabling whitehats to intervene during active exploits when traditional responsible disclosure procedures are not feasible.\n\nKey aspects of the agreement include:\n\nEncouraging Whitehats to Protect the Protocol: By adopting Safe Harbor, Uniswap incentivizes whitehats to step in and protect the protocol during active exploits by limiting their legal exposure.\n\nIntervention Only During Active Exploits: Whitehats are authorized to act only when there is an immediate or ongoing exploit that threatens the protocol. This agreement applies only to critical situations where responsible disclosure procedures would not save funds due to the urgency of the exploit, and it is not intended for routine security testing or vulnerability reporting.\n\nMandatory Return of Rescued Funds: Under the terms of the Safe Harbor, whitehats are required to return all rescued assets to a pre-designated recovery address controlled by the protocol within 72 hours of recovering them. This ensures that recovered funds are quickly secured, preventing delay or potential loss.\n\nClear Guidelines and Legal Protection: The agreement establishes strict rules for how whitehats must operate during an exploit, ensuring recovery efforts are conducted professionally and safely, minimizing the risk of mistakes or further damage to the protocol. By adhering to these guidelines, whitehats can limit their potential legal exposure, allowing them to act in good faith without fear of liability.\n\nIncentivized Rescue Efforts: To motivate whitehats to act during critical situations, the agreement offers a bounty system similar to a bug bounty. Whitehats are rewarded with a percentage of the recovered assets, up to a predefined cap, for their successful interventions.\n\nFor more information, check out the Safe Harbor Agreement here.\n\nRationale\n\nUniswap, by design, does not include a pause function, meaning the protocol cannot be halted in the event of an exploit. This makes it essential to have a mechanism that allows rapid response and asset recovery during emergencies.\n\nThe Safe Harbor Agreement provides this necessary solution, empowering whitehats to act immediately during an exploit, offering a swift and structured recovery process without needing to pause the protocol.\n\nBenefits of adopting the Safe Harbor Agreement include:\n\nAgile Defense Against Exploits: Whitehats are authorized to intervene as soon as an active exploit is detected, enabling them to respond faster than traditional methods. This ensures that Uniswap is protected against threats even without the ability to halt the protocol. Immediate action minimizes the window for malicious actors, reduces damages, and accelerates the recovery of assets during critical moments.\n\nClarified Rescue Process: The agreement ensures that every step, from intervention to fund recovery, is predetermined and streamlined. Whitehats know exactly where to send recovered funds, preventing chaotic negotiations or rushed decisions during an exploit. This clarity ensures efficient, decisive action when it matters most.\n\nClear Financial Boundaries: The predefined bounty system, with a cap matching Uniswap Labs’ existing bug bounty for V3, ensures that whitehats are incentivized fairly without creating conflicting priorities between exploit intervention and standard vulnerability disclosure. By setting expectations upfront, it eliminates post-exploit negotiations, ensuring funds are returned promptly without attempts to change the reward amount, keeping the process fair and transparent.\n\nAligning with Industry Best Practices: By adopting the Safe Harbor Agreement, Uniswap aligns itself with leading security practices across the industry, reinforcing its commitment to staying at the forefront of protocol security.\n\nAdoption of the agreement complements audits by providing an additional layer of security, ensuring that the protocol is better prepared to respond to active threats.\n\nAdoption Details\n\nUniswap will adopt the agreement with the following parameters. For a full description of these adoption details, review the Safe Harbor for Protocols document.\n\nAsset Recovery Address: Addresses controlled by Uniswap, which recovered funds will be returned to in the event of a hack. Source\n\nChain\nAddress\n\nEthereum\n\n0x1a9C8182C09F50C8318d769245beA52c32BE35BC\n\nArbitrum\n\n0x2BAD8182C09F50c8318d769245beA52C32Be46CD\n\nAvalanche\n\n0xeb0BCF27D1Fb4b25e708fBB815c421Aeb51eA9fc\n\nBase\n\n0x31FAfd4889FA1269F7a13A66eE0fB458f27D72A9\n\nBlast\n\n0x2339C0d23b60739B3E5ABF201F05903D24A26C77\n\nBoba\n\n0x53163235746CeB81Da32293bb0932e1A599256B4\n\nBSC\n\n0x341c1511141022cf8eE20824Ae0fFA3491F1302b\n\nCelo\n\n0x0Eb863541278308c3A64F8E908BC646e27BFD071\n\nFilecoin EVM\n\n0xFf3b2DA1379cc67cc2755194604713f10b820b0E\n\nGnosis\n\n0xfFA5599136fBaB9af7799A6703b57BB33E5390Cf\n\nLinea\n\n0x581F86Da293A1D5Cd087a10E7227a75d2d2201A8\n\nManta Pacific\n\n0x683553d74D9779955a15d57D208234C956B6Eae6\n\nMantle\n\n0x9b7aC6735b23578E81260acD34E3668D0cc6000A\n\nMoonbeam\n\n0xB2af16D6c7074228fC487F17929De830303E6531\n\nOptimism\n\n0xa1dD330d602c32622AA270Ea73d078B803Cb3518\n\nPolygon\n\n0x8a1B966aC46F42275860f905dbC75EfBfDC12374\n\nPolygon zkEVM\n\n0x1808cc3ffb04e8bB67BfEB5510D44e62cF380717\n\nRedstone\n\n0x2d00e94d78Fc307FC5E6195BBe2fB6aFC2FC07d4\n\nRootstock\n\n0x38aE7De6f9c51e17f49cF5730DD5F2d29fa20758\n\nScroll\n\n0xEfc9D1096fb65c832207E5e7F13C2D1102244dbe\n\nSei\n\n0xe75358526ef4441db03ccaeb9a87f180fae80eb9\n\nTaiko\n\n0xf6b53E8dA8bc7dbddB8E7B39635d17D7CCdCD6E5\n\nWorldChain\n\n0xcb2436774C3e191c85056d248EF4260ce5f27A9D\n\nZkSync\n\n0x2BAD8182C09F50c8318d769245beA52C32Be46CD\n\nZora\n\n0x36eEC182D0B24Df3DC23115D64DB521A93D5154f\n\nScope: List of all on-chain assets protected under Safe Harbor. V1 Source, V2 Source 1, V2 Source 2, V3 Source, UniStaker and V3FactoryOwner Source, Franchiser Factory Source\n\nChain\nName\nAddress\nType (None, Existing Only, All)\n\nEthereum\n\nUniswapV1Factory\n\n0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95\n\nAll\n\nEthereum\n\nUniswapV2Factory\n\n0x5C69bEe701ef814a2B6a3EDD4B1652CB9cc5aA6f\n\nAll\n\nArbitrum\n\nUniswapV2Factory\n\n0xf1D7CC64Fb4452F05c498126312eBE29f30Fbcf9\n\nAll\n\nAvalanche\n\nUniswapV2Factory\n\n0x9e5A52f57b3038F1B8EeE45F28b3C1967e22799C\n\nAll\n\nBase\n\nUniswapV2Factory\n\n0x8909Dc15e40173Ff4699343b6eB8132c65e18eC6\n\nAll\n\nBlast\n\nUniswapV2Factory\n\n0x5C346464d33F90bABaf70dB6388507CC889C1070\n\nAll\n\nBoba\n\nUniswapV2Factory\n\n0x40a26d18440948d8eE121b78ca4e88C37D30143b\n\nAll\n\nBSC\n\nUniswapV2Factory\n\n0x8909Dc15e40173Ff4699343b6eB8132c65e18eC6\n\nAll\n\nCelo\n\nUniswapV2Factory\n\n0x114a43df6c5f54ebb8a9d70cd1951d3dd68004c7\n\nAll\n\nFilecoin EVM\n\nUniswapV2Factory\n\n0x114a43df6c5f54ebb8a9d70cd1951d3dd68004c7\n\nAll\n\nGnosis\n\nUniswapV2Factory\n\n0x8c8b524ce7c9D2e3f59aB6711bE4Ac826FA46a0f\n\nAll\n\nLinea\n\nUniswapV2Factory\n\n0x114a43df6c5f54ebb8a9d70cd1951d3dd68004c7\n\nAll\n\nMoonbeam\n\nUniswapV2Factory\n\n0x114a43df6c5f54ebb8a9d70cd1951d3dd68004c7\n\nAll\n\nOptimism\n\nUniswapV2Factory\n\n0x0c3c1c532F1e39EdF36BE9Fe0bE1410313E074Bf\n\nAll\n\nPolygon\n\nUniswapV2Factory\n\n0x9e5A52f57b3038F1B8EeE45F28b3C1967e22799C\n\nAll\n\nRootstock\n\nUniswapV2Factory\n\n0x114a43df6c5f54ebb8a9d70cd1951d3dd68004c7\n\nAll\n\nScroll\n\nUniswapV2Factory\n\n0x114a43df6c5f54ebb8a9d70cd1951d3dd68004c7\n\nAll\n\nWorldChain\n\nUniswapV2Factory\n\n0x5C69bEe701ef814a2B6a3EDD4B1652CB9cc5aA6f\n\nAll\n\nZora\n\nUniswapV2Factory\n\n0x0F797dC7efaEA995bB916f268D919d0a1950eE3C\n\nAll\n\nEthereum\n\nUniswapV3Factory\n\n0x1F98431c8aD98523631AE4a59f267346ea31F984\n\nAll\n\nArbitrum\n\nUniswapV3Factory\n\n0x1F98431c8aD98523631AE4a59f267346ea31F984\n\nAll\n\nAvalanche\n\nUniswapV3Factory\n\n0x740b1c1de25031C31FF4fC9A62f554A55cdC1baD\n\nAll\n\nBase\n\nUniswapV3Factory\n\n0x33128a8fC17869897dcE68Ed026d694621f6FDfD\n\nAll\n\nBlast\n\nUniswapV3Factory\n\n0x792edAdE80af5fC680d96a2eD80A44247D2Cf6Fd\n\nAll\n\nBoba\n\nUniswapV3Factory\n\n0xFFCd7Aed9C627E82A765c3247d562239507f6f1B\n\nAll\n\nBSC\n\nUniswapV3Factory\n\n0xdB1d10011AD0Ff90774D0C6Bb92e5C5c8b4461F7\n\nAll\n\nCelo\n\nUniswapV3Factory\n\n0xAfE208a311B21f13EF87E33A90049fC17A7acDEc\n\nAll\n\nFilecoin EVM\n\nUniswapV3Factory\n\n0xB4C47eD546Fc31E26470a186eC2C5F19eF09BA41\n\nAll\n\nGnosis\n\nUniswapV3Factory\n\n0xe32F7dD7e3f098D518ff19A22d5f028e076489B1\n\nAll\n\nLinea\n\nUniswapV3Factory\n\n0x31FAfd4889FA1269F7a13A66eE0fB458f27D72A9\n\nAll\n\nManta Pacific\n\nUniswapV3Factory\n\n0x06D830e15081f65923674268121FF57Cc54e4e23\n\nAll\n\nMantle\n\nUniswapV3Factory\n\n0x0d922Fb1Bc191F64970ac40376643808b4B74Df9\n\nAll\n\nMoonbeam\n\nUniswapV3Factory\n\n0x28f1158795A3585CaAA3cD6469CD65382b89BB70\n\nAll\n\nOptimism\n\nUniswapV3Factory\n\n0x1F98431c8aD98523631AE4a59f267346ea31F984\n\nAll\n\nPolygon\n\nUniswapV3Factory\n\n0x1F98431c8aD98523631AE4a59f267346ea31F984\n\nAll\n\nPolygon zkEVM\n\nUniswapV3Factory\n\n0xff83c3c800Fec21de45C5Ec30B69ddd5Ee60DFC2\n\nAll\n\nRedstone\n\nUniswapV3Factory\n\n0xece75613Aa9b1680f0421E5B2eF376DF68aa83Bb\n\nAll\n\nRootstock\n\nUniswapV3Factory\n\n0xaF37EC98A00FD63689CF3060BF3B6784E00caD82\n\nAll\n\nScroll\n\nUniswapV3Factory\n\n0x70C62C8b8e801124A4Aa81ce07b637A3e83cb919\n\nAll\n\nSei\n\nUniswapV3Factory\n\n0x75FC67473A91335B5b8F8821277262a13B38c9b3\n\nAll\n\nTaiko\n\nUniswapV3Factory\n\n0x75FC67473A91335B5b8F8821277262a13B38c9b3\n\nAll\n\nWorldChain\n\nUniswapV3Factory\n\n0x7a5028BDa40e7B173C278C5342087826455ea25a\n\nAll\n\nZkSync\n\nUniswapV3Factory\n\n0x8FdA5a7a8dCA67BBcDd10F02Fa0649A937215422\n\nAll\n\nZora\n\nUniswapV3Factory\n\n0x7145F8aeef1f6510E92164038E1B6F8cB2c42Cbb\n\nAll\n\nEthereum\n\nFranchiserFactory\n\n0xf754A7E347F81cFdc70AF9FbCCe9Df3D826360FA\n\nAll\n\nEthereum\n\nUniStaker\n\n0xE3071e87a7E6dD19A911Dbf1127BA9dD67Aa6fc8\n\nAll\n\nEthereum\n\nV3FactoryOwner\n\n0x2e27332b25Ce245F6628377bc83573A001313C58\n\nAll\n\n“All”: The Safe Harbor Agreement will cover both the subcontracts currently deployed under this contract and any future subcontracts deployed through it. This ensures that all present and future subcontracts are protected.\n\nContact Details: Designated security contact for Uniswap\n\nName: Erin Koen\n\nContact Information: erin@uniswapfoundation.org\n\nEvery 4 months. The person of contact will create a post to state their availability and whether or not they can continue being the person of contact.\n\nBounty Terms: Predetermined rewards for successful whitehats that protect protocol funds\n\nBounty Percentage: 10% of recovered funds.\n\nBounty Cap (USD): $2.25m\n\nFor clarification, the bounty is per whitehat per hack event. Please see the legal document for additional clarification.\n\nRetainable: True\n\nThis means that whitehats are allowed to retain their bounty directly from the recovered assets. After rescuing funds during an exploit, whitehats may deduct their bounty from the total recovered amount before transferring the remainder to the protocol’s designated asset recovery address. This streamlines the payout process, ensuring whitehats are rewarded promptly while still adhering to predefined bounty terms.\n\nIdentity Verification: Anonymous\n\nWhitehats are allowed to remain anonymous and are not required to provide their legal name or undergo identity verification. This ensures privacy for whitehats while still enabling them to participate in the bounty program and assist during exploits without revealing personal information.\n\nDiligence Requirements: None\n\nImplementation Plan\n\nRegister Agreement On-Chain:\n\nThe agreement will be registered on Ethereum in the Safe Harbor Registry at address 0x8f72fcf695523a6fc7dd97eafdd7a083c386b7b6, including all adoptionDetails. This ensures transparency and immutability.\n\nCommunicate Adoption:\n\nAn official announcement will be made across all Uniswap communication channels, explaining the adoption and its significance to the community.\n\nFuture Updates to Scope:\n\nNew versions of Uniswap (e.g., V4) will be reviewed and added to the Safe Harbor Agreement scope via Uniswap Governance vote, ensuring continued protection for all new contracts and functionalities.\n\nConclusion\n\nAdopting the SEAL Whitehat Safe Harbor Agreement equips Uniswap with a rapid response mechanism for active exploits, enabling whitehats to step in effectively when needed most. The agreement provides clear guidelines for action, increasing the protection of user funds and demonstrating Uniswap’s commitment to proactive security.\n\nReferences\n\nSEAL Whitehat Safe Harbor Agreement: GitHub Repository\n\nSEAL Whitehat Safe Harbor Agreement Overview: Notion\n\nUniswap Bug Bounty: Uniswap Labs Bug Bounty Update\n\nPlease share your thoughts and feedback in the discussion below before the proposal moves to a formal vote.\n\n6 Likes\n\n[Governance Proposal] - Adopt The SEAL Safe Harbor Agreement\n\n[Temp Check] - Adopt The SEAL Safe Harbor Agreement\n\n404DAO\n\nDecember 4, 2024, 7:24pm\n\n2\n\nThanks for bringing this forward @Dickson.\n\nWe’re curious, how did you determine the bounty cap of 2.25M?\n\n1 Like\n\nDickson\n\nDecember 4, 2024, 7:40pm\n\n3\n\nHey @404DAO - Thanks for reviewing the proposal!\n\nSEAL worked together with the UF to put forth the bounty terms. The bounty cap of 2.25M was chosen to match the current bounty cap for V3 of being 2.25M source.\n\n1 Like\n\npepo\n\nDecember 9, 2024, 4:55pm\n\n4\n\nI find the proposal compelling and am in support of it. However, I would like clarification on the following points:\n\nIncentive Overlap\n\nConsidering Uniswap Labs already operates a bounty program, could you clarify if there’s an overlap where participants might benefit from both this proposal and the existing program? How is this “double dipping” of incentives defined or avoided?\n\nAddress Management and Security\n\nHow will the addresses be maintained and how we can ensure there is not a single point of failure?\n\nI’ve noticed that some recovery addresses for different chains, like the one for Arbitrum (see: GitHub Repository), are simply Externally Owned Accounts. We should ensure that these are ultimately controlled by the DAO to prevent potential loss of funds and legal liabilities.\n\nRegarding the scope of contracts covered by the bounty, in the event of a hack, will the bounty be calculated on a “per contract” basis, or will it be a singular “event-based” bounty? Clarification here is crucial to prevent disputes if a security breach occurs.\n\nHow does this apply specifically to the hook contracts of Uniswap V4?\n\nContact Details and Availability\n\nI suggest implementing a mechanism where the availability of the contact person is confirmed periodically, perhaps every few months. If there’s no confirmation, there should be a system in place to rotate the Point of Contact (PoC) to ensure continuous support and communication.\n\n3 Likes\n\nDickson\n\nDecember 9, 2024, 5:28pm\n\n5\n\nHey Pepo! Thanks for reading over the proposal!\n\nThe Safe Harbor Agreement covers only active exploits - Which would be considered out of scope of Uniswap’s Bug Bounty (since it doesn’t apply to active exploits). So whitehats would only be paid once through Safe Harbor & there wouldn’t be any double dipping\n\nPinging @eek637 to answer\n\nPinging @eek637 to answer\n\nIt will be a event-based bounty not per contract - I believe it’s clearly stated in the legal document, but I will add additional clarification inside the DAO proposal too\n\nCurrently we’re not including the scope of v4 contracts since they haven’t been deployed yet but when v4 comes out we’ll have another DAO proposal to update the scope of the Safe Harbor Agreement to include the v4 addresses in the scope as well.\n\nOh that’s an interesting idea. So would we want to have the POC to, every few months, post a forum post confirming that they’re available. If they aren’t then we should elect a new POC in place of them?\n\n2 Likes\n\neek637\n\nDecember 9, 2024, 5:35pm\n\n6\n\n@pepo the arbitrum address is the alias for Uniswap’s mainnet timelock address (docs here). You can check out a successful transaction using that address here.\n\n2 Likes\n\npepo\n\nDecember 9, 2024, 6:04pm\n\n7\n\nThanks for this clarification, I wasn’t aware of Arbitrum Aliases, wanted to make sure we were in the loop for the security standards of the DAO.\n\nI think that would make sense, especially when thinking way down the road.\n\nThanks for all these clarifications.\n\n1 Like\n\nDickson\n\nDecember 9, 2024, 6:45pm\n\n8\n\nThanks for your suggestions & questions!\n\nI updated the DAO proposal with the clarification on the bounty & the POC stating their availability every 4 months\n\n1 Like\n\ndennisonb\n\nDecember 9, 2024, 7:19pm\n\n9\n\nWelcome to the forum @Dickson !\n\nGreat post, I like the inclusion of the addresses for the funds for upfront transparency. I was immediately wondering about that myself.\n\nGiven the critical nature of whitehat interventions, has the team considered adding a requirement for post-incident reports from whiteats to help improve protocol security? This could help document attack vectors and prevention strategies while maintaining the whitehat’s anonymity.\n\n1 Like\n\nDickson\n\nDecember 9, 2024, 7:46pm\n\n10\n\nHi @dennisonb! Thanks for reviewing the proposal!\n\nThat’s an interesting idea! I’m unsure if the whitehats are actually the best to write that report. Whitehats are not the people who had originally discovered the bug (since that should be reported through a bug bounty) - thus they might not have full knowledge on how the exploit actually worked (ie. a MEV bot that’s rescuing funds by frontrunning the hacker). Given how high profile Uniswap is, there should be no shortage of reports on the incident if it were (but hopefully never) occur. Additionally I think it would be best to not add non-essential restraints on the whitehat. Their job is solely to rescue funds and return them to the protocol.\n\nkpk\n\nDecember 16, 2024, 3:48pm\n\n11\n\nThanks for sharing this proposal, @Dickson.\n\nAt Karpatkey, security is a core value for us, so we’re fully behind this initiative. Uniswap is a battle-tested protocol, and we truly appreciate the hard work that its stakeholders continue to put into maintaining its security. As a leader in the space, Uniswap has the opportunity to set the gold standard for security practices, and we believe the SEAL proposal is a big step in that direction.\n\nWe’re excited to see this move forward and hope it’s adopted soon!\n\n1 Like\n\nDickson\n\nDecember 16, 2024, 6:24pm\n\n12\n\nThank you all for the support! We’ve now moved on to the temperature check phase! Here’s the Temp Check forum post: https://gov.uniswap.org/t/temp-check-adopt-the-seal-safe-harbor-agreement/25072 & Here’s the Snapshot: https://snapshot.box/#/s:uniswapgovernance.eth/proposal/0xba36ded3039fc2588cdc7352e2ac6dd40ca0c3548576d9d31256663fbfc3f1b4\n\nBlockworksResearch\n\nDecember 16, 2024, 9:09pm\n\n13\n\nWe fully support this proposal and believe it makes sense to leverage white hat responses in the event of a hack. White hats should have protection when intervening in security breaches. We also support the dynamic bounty structure, as it ensures there’s always a sufficient incentive for white hat intervention.\n\nA few questions on what this looks like moving forward:\n\nRegarding the point of security contact for Uniswap: Is it ever expected that the DAO will nominate these positions, or will they always be appointed by the foundation? While this is not a concern for us in relation to our sentiment on the proposal, we would like to understand the long-term plan.\n\nOther DAOs, like Arbitrum, use a security council that rotates every six months. Is this something Uniswap has considered implementing?\n\n1 Like\n\neek637\n\nDecember 16, 2024, 9:39pm\n\n14\n\nOn the Designated Contact, I raised my hand for it as I’d been chatting with @Dickson et al about the proposal for a couple of months. In general, there isn’t as much to do here as an L2 security council (and hopefully nothing to do at all!). Ultimately, the adoption details can be modified by governance vote so if there’s a compelling reason to change it up it’s easy enough to do. I’d suggest we leave as is for a bit and potentially revisit in six months to a year.\n\n2 Likes\n\nAvantgarde\n\nDecember 19, 2024, 8:23am\n\n15\n\nWe support this proposal as it adds a valuable and complementary function to Uniswap’s security framework and current bug bounty program. The possibility of recovering funds from active exploits serves as a nice safeguard, and would arguably be highly appreciated by any affected users should such a scenario present itself. After all, security over user funds is imperative. Bounty structure is also fair.\n\nWill be voting yes!\n\n1 Like\n\n[Governance Proposal] - Adopt The SEAL Safe Harbor Agreement\n\nkaereste\n\nDecember 20, 2024, 5:39pm\n\n16\n\nThe following reflects the views of L2BEAT’s governance team, composed of @krst and @Sinkas, and it’s based on the combined research, fact-checking, and ideation of the two.\n\nWe’re voting FOR the proposal.\n\nWe generally favor proposals that help enhance protocol security, and the proposed agreement—although hopefully we never have to use it—does precisely that. All the questions that came to our mind after originally reading the proposal have already been addressed, so we don’t have any material reason to be skeptical or against the proposal.\n\n2 Likes\n\nL2BEAT Delegate Platform\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[Temp Check] - Adopt The SEAL Safe Harbor Agreement\n\nTemperature Check\n\n1\n\n239\n\nDecember 17, 2024\n\n[Governance Proposal] - Adopt The SEAL Safe Harbor Agreement\n\nRequests for Comment\n\n4\n\n321\n\nJanuary 16, 2025\n\nBug Bounty Vault Proposal by Hats Finance\n\nRequests for Comment\n\n4\n\n2203\n\nSeptember 10, 2023\n\nKeyrock Delegate Platform\n\nDelegation Pitch\n\n26\n\n5237\n\nMarch 20, 2025\n\nStableLab Delegate Platform\n\nDelegation Pitch\n\n103\n\n8892\n\nDecember 30, 2025","tokens":5467,"crawled_at":1791193964483}
+{"id":10320,"url":"https://www.metaplex.com/docs/smart-contracts/core/create-asset","domain":"www.metaplex.com","chapter":"docs","title":"Creating Assets | Metaplex Core","text":"This guide shows how to create a Core Asset (NFT) on Solana using the Metaplex Core SDK. You'll upload off-chain metadata, create the on-chain Asset account, and optionally add it to a Collection or attach plugins.\nWhat You'll Build\nA Core Asset with:\nOff-chain metadata (name, image, attributes) stored on Arweave\nOn-chain Asset account with ownership and metadata URI\nOptional: Collection membership\nOptional: Plugins (royalties, freeze, attributes)\n\nSummary\nCreate a Core Asset by uploading metadata JSON to decentralized storage, then calling create() with the URI. Assets can be minted standalone or into Collections, and can include plugins at creation time.\nUpload metadata JSON to Arweave/IPFS, get a URI\nCall create() with name, URI, and optional plugins\nFor collections: pass the collection parameter\nCosts ~0.003 SOL for a base asset; longer names, URIs, and plugins add rent\nOut of Scope\nToken Metadata NFTs (use mpl-token-metadata), compressed NFTs (use Bubblegum), fungible tokens (use SPL Token), and NFT migration.\nQuick Start\nJump to: Upload Metadata · Create Asset · With Collection · With Plugins\nInstall: npm install @metaplex-foundation/mpl-core @metaplex-foundation/umi\nUpload metadata JSON to get a URI\nCall create(umi, { asset, name, uri })\nVerify on core.metaplex.com\nPrerequisites\nUmi configured with a signer and RPC connection\nSOL for rent and fees (~0.003 SOL for a base asset, plus headroom for larger assets and transaction fees)\nMetadata JSON ready to upload (name, image, attributes)\nThe Creation Process\nUpload off-chain data. Store a JSON file containing name, description, image URL, and attributes. The file must be accessible via a public URI.\nCreate on-chain Asset account. Call the create instruction with the metadata URI to mint the Asset.\nUploading Off-chain Data\nUse any storage service (Arweave, IPFS, AWS) to upload your metadata JSON. Umi provides uploader plugins for common services. See the JSON Schema for all available metadata fields.\nupload-metadata.ts\nimport { irysUploader } from '@metaplex-foundation/umi-uploader-irys'\n\n// Configure an uploader (Irys, AWS, etc.)\n\numi.use(irysUploader())\n\n// Upload image first\n\nconst [imageUri] = await umi.uploader.upload([imageFile])\n\n// Upload metadata JSON\n\nconst uri = await umi.uploader.uploadJson({\n\nname: 'My NFT',\n\ndescription: 'This is my NFT',\n\nimage: imageUri,\n\nattributes: [\n\n{ trait_type: 'Background', value: 'Blue' },\n\n],\n\n})\n\nNow that you have a URI, you can create the Asset.\nCreate an Asset\nUse the create instruction to mint a new Core Asset.\n\n1import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n2import { create } from '@metaplex-foundation/mpl-core'\n\n3import { mplCore } from '@metaplex-foundation/mpl-core'\n\n4\n\n5// Initialize UMI\n\n6const umi = createUmi('https://api.devnet.solana.com')\n\n7 .use(mplCore())\n\n8\n\n9// Create a new NFT asset\n\n10const asset = await create(umi, {\n\n11 name: 'My NFT',\n\n12 uri: 'https://example.com/metadata.json'\n\n13}).sendAndConfirm(umi)\n\n14\n\n15console.log('Asset created:', asset.publicKey)\n\nCreate an Asset into a Collection\nTo create an Asset as part of a Collection, pass the collection parameter. The Collection must already exist.\n\n1import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n2import { create, fetchCollection } from '@metaplex-foundation/mpl-core'\n\n3import { mplCore } from '@metaplex-foundation/mpl-core'\n\n4import { generateSigner, publicKey } from '@metaplex-foundation/umi'\n\n5\n\n6// Initialize UMI\n\n7const umi = createUmi('https://api.devnet.solana.com')\n\n8 .use(mplCore())\n\n9\n\n10const collectionAddress = publicKey('YOUR_COLLECTION_ADDRESS')\n\n11\n\n12// Fetch the existing collection\n\n13const collection = await fetchCollection(umi, collectionAddress)\n\n14\n\n15// Generate a new keypair for the asset\n\n16const assetSigner = generateSigner(umi)\n\n17\n\n18// Create asset in the collection\n\n19await create(umi, {\n\n20 asset: assetSigner,\n\n21 collection,\n\n22 name: 'Collection Item #1',\n\n23 uri: 'https://example.com/item1.json',\n\n24}).sendAndConfirm(umi)\n\n25\n\n26console.log('Asset created in collection:', assetSigner.publicKey)\n\nSee Collections for creating Collections.\nCreate an Asset with Plugins\nAdd plugins at creation time by passing them in the plugins array. This example adds the Royalties plugin:\n\n1import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n2import { create, ruleSet } from '@metaplex-foundation/mpl-core'\n\n3import { mplCore } from '@metaplex-foundation/mpl-core'\n\n4import { generateSigner, publicKey } from '@metaplex-foundation/umi'\n\n5\n\n6// Initialize UMI\n\n7const umi = createUmi('https://api.devnet.solana.com')\n\n8 .use(mplCore())\n\n9\n\n10const creator = publicKey('YOUR_CREATOR_ADDRESS')\n\n11\n\n12// Generate a new keypair for the asset\n\n13const assetSigner = generateSigner(umi)\n\n14\n\n15// Create asset with Royalties plugin\n\n16await create(umi, {\n\n17 asset: assetSigner,\n\n18 name: 'NFT with Royalties',\n\n19 uri: 'https://example.com/metadata.json',\n\n20 plugins: [\n\n21 {\n\n22 type: 'Royalties',\n\n23 basisPoints: 500, // 5%\n\n24 creators: [\n\n25 { address: creator, percentage: 100 },\n\n26 ],\n\n27 ruleSet: ruleSet('None'),\n\n28 },\n\n29 ],\n\n30}).sendAndConfirm(umi)\n\n31\n\n32console.log('Asset created with plugins:', assetSigner.publicKey)\n\nCommon Plugins\nHere are a few commonly used plugins. See Plugins Overview for the full list.\nRoyalties - Creator royalty enforcement\nFreeze Delegate - Allow freezing/unfreezing\nBurn Delegate - Allow burning\nTransfer Delegate - Allow transfers\nUpdate Delegate - Allow metadata updates\nAttributes - On-chain key/value data See Plugins Overview for the full list.\nCommon Errors\nAsset account already exists\nThe asset keypair was already used. Generate a new signer:\nconst assetSigner = generateSigner(umi) // Must be unique\n\nCollection not found\nThe collection address doesn't exist or isn't a valid Core Collection. Verify the address and that you've created the Collection first.\nInsufficient funds\nYour payer wallet needs ~0.003 SOL for a base asset's rent and the protocol fee, plus some headroom for larger assets and transaction fees. Fund it with:\nsolana airdrop 1 <WALLET_ADDRESS> --url devnet\n\nNotes\nThe asset parameter must be a new keypair - you cannot reuse an existing account\nIf minting to a different owner, pass the owner parameter\nPlugins added at creation are cheaper than adding them after (one transaction vs two)\nUse commitment: 'finalized' when creating assets in a script that immediately fetches them\nQuick Reference\nProgram ID\nNetworkAddress\nMainnet\nCoREENxT6tW1HoK8ypY1SxRMZTcVPm7R94rH4PZNhX7d\n\nDevnet\nCoREENxT6tW1HoK8ypY1SxRMZTcVPm7R94rH4PZNhX7d\n\nMinimum Code\nminimal-create.ts\nimport { generateSigner } from '@metaplex-foundation/umi'\n\nimport { create } from '@metaplex-foundation/mpl-core'\n\nconst asset = generateSigner(umi)\n\nawait create(umi, { asset, name: 'My NFT', uri: 'https://...' }).sendAndConfirm(umi)\n\nCost Breakdown\nItemCost\nAsset account rent (varies with name, URI, and plugins)\n~0.0015 SOL\n\nCore protocol fee (create)\n0.0015 SOL\n\nTransaction fee\n~0.000005 SOL\n\nTotal\n~0.003 SOL\n\nFAQ\nWhat's the difference between Core Assets and Token Metadata NFTs?\nCore Assets use a single account and cost ~80% less. Token Metadata uses 3+ accounts (mint, metadata, token). Core is recommended for new projects.\nCan I create multiple assets in one transaction?\nNo. Each create instruction creates one asset. For bulk minting, use Core Candy Machine or batch transactions.\nDo I need to create a Collection first?\nNo. Assets can exist without a Collection. However, Collections enable collection-level royalties and operations.\nHow do I mint to a different wallet?\nPass the owner parameter:\nawait create(umi, { asset, name, uri, owner: recipientAddress })\n\nWhat metadata format should I use?\nUse the standard NFT metadata format with name, description, image, and optional attributes array. See JSON Schema.\nGlossary\nTermDefinition\nAsset\nA Core on-chain account representing an NFT\n\nURI\nThe URL pointing to off-chain metadata JSON\n\nSigner\nA keypair that signs the transaction (asset must be a signer at creation)\n\nCollection\nA Core account that groups related Assets\n\nPlugin\nA modular extension adding behavior to an Asset\n\nRent\nSOL required to keep an account alive on Solana","tokens":2065,"crawled_at":1791194009276}
+{"id":10321,"url":"https://a16zcrypto.com/posts/tags/governance-best-practices","domain":"a16zcrypto.com","chapter":"research","title":"governance best practices - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\ngovernance best practices\n\nFeed\nFILTERS\n(1)\nclear filters\n\ncategories\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\n(1) recommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nclear all governance best practices\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n08.14.24 / Eddy Lazzarin, Andrew Hall, Ross Shuel and Sonal Chokshi\nGovernance Attack!?\nepisode summary We breakdown the recent Compound “governance attack”, including discussing whether “governance attack” is the right label for it or not; how it’s different from other attacks; and the broader trend of online vs offline governance attacks in general. We also discuss how to avoid, prevent, and respond to such governance attacks — highlighting...\n\ntech trends\nanatomy of a hack\nDAOs\ngovernance\ngovernance best practices\npodcast\n\n10.18.23 / Eliza Oak\nDesigning reward systems for web3 governance\nAn analysis of the tradeoffs of reputation-based and token-based reward systems for participation in web3 governance\n\nresearch\nairdrops\nDAOs\ngovernance\ngovernance best practices\n\n09.21.23 / Miles Jennings\nMachiavelli for DAOs: designing effective decentralized governance (part 2)\nHow Machiavellian principles can help address current issues in DAOs, and help design more effective decentralized governance\n\ncompany building\ncommunity building\nDAOs\ngovernance\ngovernance best practices\nMachiavelli for DAOs series\n\n09.21.23 / Miles Jennings\nMachiavelli for DAOs: principles for fixing decentralized governance (part 1)\nHow Machiavellian principles can be applied to fix decentralized governance, including DAOs in web3\n\ncompany building\ncommunity building\nDAOs\ngovernance\ngovernance best practices\nhistory\nMachiavelli for DAOs series\n\n07.20.23 / Andrew Hall\nGovernance FAQs\nAnswers to questions founders ask most frequently about governance -- and those to questions they ought to ask more frequently\n\ncompany building\nairdrops\nFAQ\ngovernance\ngovernance best practices\n\n06.19.23 / Porter Smith\nDesigning effective governance\na16z crypto Deal Partner Porter Smith traces innovations in governance through time; and tracks the emergence of web3 governance through NFT communities, DAOs.\n\ncompany building\ncommunity building\nCSX 2023\ngovernance\ngovernance best practices\nvideo\n\n10.20.22 / Porter Smith and Andrew Hall\nToppling the Internet’s Accidental Monarchs: How to Design web3 Platform Governance\nweb3 platforms have an opportunity to cement their competitive advantage by sharing governance & giving up some power, sparking engaged community governance.\n\ncompany building\nDAOs\ngovernance\ngovernance best practices\nhistory\n\n08.24.22 / Jeff Amico, Maggie Hsu, Ed Lynch and Emily Westerhold\nTreasury Management: A Guide to Navigating Downturns\nWe share a framework for how conservative treasury management principles can help DAOs and startups to safely navigate periods of market uncertainty.\n\ncompany building\ncustody\nDAOs\ngovernance best practices\nplaybooks\nproduct-market fit\n\n07.27.22 / Pranav Garimidi, Scott Duke Kominers and Tim Roughgarden\nDAO governance attacks, and how to avoid them\nDAOS can make themselves less vulnerable to governance attacks if they use our simple but effective framework.\n\ncompany building\nDAOs\ngovernance\ngovernance best practices\nmechanism design\nsecurity\ntoken design\ntokens\n\n06.03.22 / Miles Jennings and David Kerr\nHow to pick a DAO legal entity\nThe growth of DAOs raise legal, tax, and operations questions, so we created a 4-step guide to help web3 builders choose a DAO legal entity.\n\ncompany building\nDAOs\nglossaries & terminology\ngovernance best practices\nlegal best practices\nmental models & frameworks\n\n11.03.21 / Tarun Chitra\nBuilding and Running a DAO: Why Governance Matters\nGoverning the decentralized protocols associated with DeFI and NFT communities requires significant coordination costs which can be reduced by decentralized autonomous organizations.\n\ncompany building\nairdrops\nDAOs\nDeFi\ngovernance\ngovernance best practices\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":1692,"crawled_at":1791194002577}
+{"id":10322,"url":"https://stack.olas.network/open-autonomy/advanced_reference/developer_tooling/debugging_using_tenderly","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Debugging using Tenderly - Olas Stack Developer Documentation","text":"Debugging Using Tenderly\n\nInfo\n\nThis section is under review and will be updated soon.\n\nTenderly is a comprehensive Ethereum Developer Platform for real-time monitoring, alerting, debugging, and simulating Smart Contracts. When debugging transactions and contract calls, it can be useful to help us understand what is going on with the execution. This guide contains a more detailed explanation on Tenderly, but for the basics:\n\nCreate a Tenderly account and project.\n\nSet your Tenderly username and project name at tenderly.yaml (exports/ganache/project_slug) and at your hardhat.config.js module exports:\n\ntenderly: {\nusername: \"username\",\nproject: \"projectname\"\n}\n\nLogin to Tenderly using your username and password or an access token:\n\ntenderly login\n\nRun your Hardhat deployment and export your transactions with:\n\ntenderly export <transaction_hash>\n\nYou'll see a link to your Tenderly dashboard where you can inspect the full transaction stack trace.\n\nDuring testing, you will need to pause Hardhat's execution before it ends to export the transaction.\n\nOptionally, there's the possibility of pushing your contract's source to verify and debug it. More on that here.","tokens":293,"crawled_at":1791194002848}
+{"id":10323,"url":"https://docs.ethers.org/v6/api/wallet","domain":"docs.ethers.org","chapter":"developer_specs","title":"","text":"ethers\n6.17.0\n\nDOCUMENTATION\nGetting Started\nEthereum Basics\nApplication Programming Interface\nPollingBlockTagSubscriber\nApplication Binary Interface\nAddresses\nConstants\nContracts\nCryptographic Functions\nHashing Utilities\nProviders\nTransactions\nUtilities\nWallets\nBaseWallet\nMnemonic\nWallet\nHD Wallets\nJSON Wallets\nWordlists\nCookbook\nMigrating from v5\nContributions and Hacking\nLicense and Copyright\n\nSingle Page\n\nDocumentation »API »Wallets\nWallets\nWhen interacting with Ethereum, it is necessary to use a private key authenticate actions by signing a payload.\nWallets are the simplest way to expose the concept of an Externally Owner Account (EOA) as it wraps a private key and supports high-level methods to sign common types of interaction and send transactions.\nThe class most developers will want to use is Wallet, which can load a private key directly or from any common wallet format.\nThe HDNodeWallet can be used when it is necessary to access low-level details of how an HD wallets are derived, exported or imported.\n\nclass BaseWallet\ninherits from AbstractSigner, Signer\nThe BaseWallet is a stream-lined implementation of a Signer that operates with a private key.\nIt is preferred to use the Wallet class, as it offers additional functionality and simplifies loading a variety of JSON formats, Mnemonic Phrases, etc.\nThis class may be of use for those attempting to implement a minimal Signer.\n\nPROPERTIES\n<src>baseWallet.address⇒ stringread-only\nThe wallet address.\n\n<src>baseWallet.privateKey⇒ stringread-only\nThe private key for this wallet.\n\n<src>baseWallet.signingKey⇒ SigningKeyread-only\nThe SigningKey used for signing payloads.\n\nCREATING INSTANCES\n<src>new BaseWallet(privateKey: SigningKey, provider?: null | Provider)\nCreates a new BaseWallet for privateKey, optionally connected to provider.\nIf provider is not specified, only offline methods can be used.\n\nMETHODS\n<src>baseWallet.authorize(auth: AuthorizationRequest)⇒ Promise< Authorization >\nResolves to the Authorization for auth.\n\n<src>baseWallet.authorizeSync(auth: AuthorizationRequest)⇒ Authorization\nReturns the Authorization for auth.\n\n<src>baseWallet.signMessageSync(message: string | Uint8Array)⇒ string\nReturns the signature for message signed with this wallet.\n\nclass Mnemonic\nA Mnemonic wraps all properties required to compute BIP-39 seeds and convert between phrases and entropy.\n\nPROPERTIES\n<src>mnemonic.entropy⇒ stringread-only\nThe underlying entropy which the mnemonic encodes.\n\n<src>mnemonic.password⇒ stringread-only\nThe password used for this mnemonic. If no password is used this is the empty string (i.e. \"\") as per the specification.\n\n<src>mnemonic.phrase⇒ stringread-only\nThe mnemonic phrase of 12, 15, 18, 21 or 24 words.\nUse the wordlist split method to get the individual words.\n\n<src>mnemonic.wordlist⇒ Wordlistread-only\nThe wordlist for this mnemonic.\n\nCREATING INSTANCES\n<src>Mnemonic.fromEntropy(entropy: BytesLike, password?: null | string, wordlist?: null | Wordlist)⇒ Mnemonic\nCreate a new Mnemonic from the entropy.\nThe default password is the empty string and the default wordlist is the English wordlists.\n\n<src>Mnemonic.fromPhrase(phrase: string, password?: null | string, wordlist?: null | Wordlist)⇒ Mnemonic\nCreates a new Mnemonic for the phrase.\nThe default password is the empty string and the default wordlist is the English wordlists.\n\nMETHODS\n<src>mnemonic.computeSeed()⇒ string\nReturns the seed for the mnemonic.\n\nSTATIC METHODS\n<src>Mnemonic.entropyToPhrase(entropy: BytesLike, wordlist?: null | Wordlist)⇒ string\nReturns the phrase for mnemonic.\n\n<src>Mnemonic.isValidMnemonic(phrase: string, wordlist?: null | Wordlist)⇒ boolean\nReturns true if phrase is a valid BIP-39 phrase.\nThis checks all the provided words belong to the wordlist, that the length is valid and the checksum is correct.\n\n<src>Mnemonic.phraseToEntropy(phrase: string, wordlist?: null | Wordlist)⇒ string\nReturns the entropy for phrase.\n\nclass Wallet\ninherits from BaseWallet, AbstractSigner\nA Wallet manages a single private key which is used to sign transactions, messages and other common payloads.\nThis class is generally the main entry point for developers that wish to use a private key directly, as it can create instances from a large variety of common sources, including raw private key, BIP-39 mnemonics and encrypte JSON wallets.\n\nCREATING INSTANCES\n<src>new Wallet(key: string | SigningKey, provider?: null | Provider)\nCreate a new wallet for the private key, optionally connected to provider.\n\nMETHODS\n<src>wallet.encrypt(password: Uint8Array | string, progressCallback?: ProgressCallback)⇒ Promise< string >\nResolves to a JSON Keystore Wallet encrypted with password.\nIf progressCallback is specified, it will receive periodic updates as the encryption process progreses.\n\n<src>wallet.encryptSync(password: Uint8Array | string)⇒ string\nReturns a JSON Keystore Wallet encryped with password.\nIt is preferred to use the async version instead, which allows a ProgressCallback to keep the user informed.\nThis method will block the event loop (freezing all UI) until it is complete, which may be a non-trivial duration.\n\nSTATIC METHODS\n<src>Wallet.createRandom(provider?: null | Provider)⇒ HDNodeWallet\nCreates a new random HDNodeWallet using the available cryptographic random source.\nIf there is no crytographic random source, this will throw.\n\n<src>Wallet.fromEncryptedJson(json: string, password: Uint8Array | string, progress?: ProgressCallback)⇒ Promise< HDNodeWallet | Wallet >\nCreates (asynchronously) a Wallet by decrypting the json with password.\nIf progress is provided, it is called periodically during decryption so that any UI can be updated.\n\n<src>Wallet.fromEncryptedJsonSync(json: string, password: Uint8Array | string)⇒ HDNodeWallet | Wallet\nCreates a Wallet by decrypting the json with password.\nThe fromEncryptedJson method is preferred, as this method will lock up and freeze the UI during decryption, which may take some time.\n\n<src>Wallet.fromPhrase(phrase: string, provider?: Provider)⇒ HDNodeWallet\nCreates a HDNodeWallet for phrase.\n\nHD Wallets\nExplain HD Wallets..\n\nCONSTANTS\n<src>defaultPath⇒ string\nThe default derivation path for Ethereum HD Nodes. (i.e. \"m/44'/60'/0'/0/0\")\n\nFUNCTIONS\n<src>getAccountPath(index: Numeric)⇒ string\nReturns the BIP-32 path for the account at index.\nThis is the pattern used by wallets like Ledger.\nThere is also an alternate pattern used by some software.\n\n<src>getIndexedAccountPath(index: Numeric)⇒ string\nReturns the path using an alternative pattern for deriving accounts, at index.\nThis derivation path uses the index component rather than the account component to derive sequential accounts.\nThis is the pattern used by wallets like MetaMask.\n\nclass HDNodeVoidWallet\ninherits from VoidSigner, AbstractSigner\nA HDNodeVoidWallet cannot sign, but provides access to the children nodes of a BIP-32 HD wallet addresses.\nThe can be created by using an extended xpub key to HDNodeWallet.fromExtendedKey or by nuetering a HDNodeWallet.\n\nPROPERTIES\n<src>hdNodeVoidWallet.chainCode⇒ stringread-only\nThe chaincode, which is effectively a public key used to derive children.\n\n<src>hdNodeVoidWallet.depth⇒ numberread-only\nThe depth of this wallet, which is the number of components in its path.\n\n<src>hdNodeVoidWallet.extendedKey⇒ stringread-only\nThe extended key.\nThis key will begin with the prefix xpub and can be used to reconstruct this neutered key to derive its children addresses.\n\n<src>hdNodeVoidWallet.fingerprint⇒ stringread-only\nThe fingerprint.\nA fingerprint allows quick qay to detect parent and child nodes, but developers should be prepared to deal with collisions as it is only 4 bytes.\n\n<src>hdNodeVoidWallet.index⇒ numberread-only\nThe child index of this wallet. Values over 2 ** 31 indicate the node is hardened.\n\n<src>hdNodeVoidWallet.parentFingerprint⇒ stringread-only\nThe parent node fingerprint.\n\n<src>hdNodeVoidWallet.path⇒ null | stringread-only\nThe derivation path of this wallet.\nSince extended keys do not provider full path details, this may be null, if instantiated from a source that does not enocde it.\n\n<src>hdNodeVoidWallet.publicKey⇒ stringread-only\nThe compressed public key.\n\nMETHODS\n<src>hdNodeVoidWallet.deriveChild(index: Numeric)⇒ HDNodeVoidWallet\nReturn the child for index.\n\n<src>hdNodeVoidWallet.derivePath(path: string)⇒ HDNodeVoidWallet\nReturn the signer for path from this node.\n\n<src>hdNodeVoidWallet.hasPath()⇒ boolean\nReturns true if this wallet has a path, providing a Type Guard that the path is non-null.\n\nclass HDNodeWallet\ninherits from BaseWallet, AbstractSigner\nAn HDNodeWallet is a Signer backed by the private key derived from an HD Node using the BIP-32 stantard.\nAn HD Node forms a hierarchal structure with each HD Node having a private key and the ability to derive child HD Nodes, defined by a path indicating the index of each child.\n\nPROPERTIES\n<src>hdNodeWallet.chainCode⇒ stringread-only\nThe chaincode, which is effectively a public key used to derive children.\n\n<src>hdNodeWallet.depth⇒ numberread-only\nThe depth of this wallet, which is the number of components in its path.\n\n<src>hdNodeWallet.extendedKey⇒ stringread-only\nThe extended key.\nThis key will begin with the prefix xpriv and can be used to reconstruct this HD Node to derive its children.\n\n<src>hdNodeWallet.fingerprint⇒ stringread-only\nThe fingerprint.\nA fingerprint allows quick qay to detect parent and child nodes, but developers should be prepared to deal with collisions as it is only 4 bytes.\n\n<src>hdNodeWallet.index⇒ numberread-only\nThe child index of this wallet. Values over 2 ** 31 indicate the node is hardened.\n\n<src>hdNodeWallet.mnemonic⇒ null | Mnemonicread-only\nThe mnemonic used to create this HD Node, if available.\nSources such as extended keys do not encode the mnemonic, in which case this will be null.\n\n<src>hdNodeWallet.parentFingerprint⇒ stringread-only\nThe parent fingerprint.\n\n<src>hdNodeWallet.path⇒ null | stringread-only\nThe derivation path of this wallet.\nSince extended keys do not provide full path details, this may be null, if instantiated from a source that does not encode it.\n\n<src>hdNodeWallet.publicKey⇒ stringread-only\nThe compressed public key.\n\nCREATING INSTANCES\n<src>HDNodeWallet.createRandom(password?: string, path?: string, wordlist?: Wordlist)⇒ HDNodeWallet\nCreates a new random HDNode.\n\n<src>HDNodeWallet.fromMnemonic(mnemonic: Mnemonic, path?: string)⇒ HDNodeWallet\nCreate an HD Node from mnemonic.\n\n<src>HDNodeWallet.fromPhrase(phrase: string, password?: string, path?: string, wordlist?: Wordlist)⇒ HDNodeWallet\nCreates an HD Node from a mnemonic phrase.\n\n<src>HDNodeWallet.fromSeed(seed: BytesLike)⇒ HDNodeWallet\nCreates an HD Node from a seed.\n\nMETHODS\n<src>hdNodeWallet.deriveChild(index: Numeric)⇒ HDNodeWallet\nReturn the child for index.\n\n<src>hdNodeWallet.derivePath(path: string)⇒ HDNodeWallet\nReturn the HDNode for path from this node.\n\n<src>hdNodeWallet.encrypt(password: Uint8Array | string, progressCallback?: ProgressCallback)⇒ Promise< string >\nResolves to a JSON Keystore Wallet encrypted with password.\nIf progressCallback is specified, it will receive periodic updates as the encryption process progreses.\n\n<src>hdNodeWallet.encryptSync(password: Uint8Array | string)⇒ string\nReturns a JSON Keystore Wallet encryped with password.\nIt is preferred to use the async version instead, which allows a ProgressCallback to keep the user informed.\nThis method will block the event loop (freezing all UI) until it is complete, which may be a non-trivial duration.\n\n<src>hdNodeWallet.hasPath()⇒ boolean\nReturns true if this wallet has a path, providing a Type Guard that the path is non-null.\n\n<src>hdNodeWallet.neuter()⇒ HDNodeVoidWallet\nReturns a neutered HD Node, which removes the private details of an HD Node.\nA neutered node has no private key, but can be used to derive child addresses and other public data about the HD Node.\n\nSTATIC METHODS\n<src>HDNodeWallet.fromExtendedKey(extendedKey: string)⇒ HDNodeWallet | HDNodeVoidWallet\nCreates a new HD Node from extendedKey.\nIf the extendedKey will either have a prefix or xpub or xpriv, returning a neutered HD Node (HDNodeVoidWallet) or full HD Node ([[HDNodeWallet) respectively.\n\nJSON Wallets\nThe JSON Wallet formats allow a simple way to store the private keys needed in Ethereum along with related information and allows for extensible forms of encryption.\nThese utilities facilitate decrypting and encrypting the most common JSON Wallet formats.\n\nTYPES\n<src>CrowdsaleAccount⇒ { address: string , privateKey: string }\nThe data stored within a JSON Crowdsale wallet is fairly minimal.\n\n<src>EncryptOptions⇒ { client?: string , entropy?: BytesLike , iv?: BytesLike , progressCallback?: ProgressCallback , salt?: BytesLike , scrypt?: { N?: number , p?: number , r?: number } , uuid?: string }\nThe parameters to use when encrypting a JSON Keystore Wallet.\n\n<src>KeystoreAccount⇒ { address: string , mnemonic?: { entropy: string , locale?: string , path?: string } , privateKey: string }\nThe contents of a JSON Keystore Wallet.\n\nFUNCTIONS\n<src>decryptCrowdsaleJson(json: string, password: string | Uint8Array)⇒ CrowdsaleAccount\nBefore Ethereum launched, it was necessary to create a wallet format for backers to use, which would be used to receive ether as a reward for contributing to the project.\nThe Crowdsale Wallet format is now obsolete, but it is still useful to support and the additional code is fairly trivial as all the primitives required are used through core portions of the library.\n\n<src>decryptKeystoreJson(json: string, password: string | Uint8Array, progress?: ProgressCallback)⇒ Promise< KeystoreAccount >\nResolves to the decrypted JSON Keystore Wallet json using the password.\nIf provided, progress will be called periodically during the decrpytion to provide feedback, and if the function returns false will halt decryption.\nThe progressCallback will always receive 0 before decryption begins and 1 when complete.\n\n<src>decryptKeystoreJsonSync(json: string, password: string | Uint8Array)⇒ KeystoreAccount\nReturns the account details for the JSON Keystore Wallet json using password.\nIt is preferred to use the async version instead, which allows a ProgressCallback to keep the user informed as to the decryption status.\nThis method will block the event loop (freezing all UI) until decryption is complete, which can take quite some time, depending on the wallet paramters and platform.\n\n<src>encryptKeystoreJson(account: KeystoreAccount, password: string | Uint8Array, options?: EncryptOptions)⇒ Promise< string >\nResolved to the JSON Keystore Wallet for account encrypted with password.\nThe options can be used to tune the password-based key derivation function parameters, explicitly set the random values used and provide a ProgressCallback to receive periodic updates on the completion status..\n\n<src>encryptKeystoreJsonSync(account: KeystoreAccount, password: string | Uint8Array, options?: EncryptOptions)⇒ string\nReturn the JSON Keystore Wallet for account encrypted with password.\nThe options can be used to tune the password-based key derivation function parameters, explicitly set the random values used. Any provided ProgressCallback is ignord.\n\n<src>isCrowdsaleJson(json: string)⇒ boolean\nReturns true if json is a valid JSON Crowdsale wallet.\n\n<src>isKeystoreJson(json: string)⇒ boolean\nReturns true if json is a valid JSON Keystore Wallet.\n\n← Fixed-Point Maths\nWordlists→\n\nThe content of this site is licensed under the Creative Commons License. Generated on May 1, 2024, 12:01am.","tokens":3881,"crawled_at":1791194004368}
+{"id":10324,"url":"https://docs.ethers.org/v6/api/providers/abstract-provider","domain":"docs.ethers.org","chapter":"developer_specs","title":"","text":"ethers\n6.17.0\n\nDOCUMENTATION\nGetting Started\nEthereum Basics\nApplication Programming Interface\nPollingBlockTagSubscriber\nApplication Binary Interface\nAddresses\nConstants\nContracts\nCryptographic Functions\nHashing Utilities\nProviders\nBlock\nBrowserDiscoverOptions\nBrowserProvider\nContractRunner\nEip1193Provider\nEip6963ProviderInfo\nEnsPlugin\nEventFilter\nFeeData\nFeeDataNetworkPlugin\nFetchUrlFeeDataNetworkPlugin\nFilter\nFilterByBlockHash\nGasCostPlugin\nIpcSocketProvider\nLog\nMinedBlock\nMinedTransactionResponse\nNetworkPlugin\nNonceManager\nPreparedTransactionRequest\nProvider\nSigner\nTransactionReceipt\nTransactionRequest\nTransactionResponse\nWebSocketLike\nWebSocketProvider\nNetworks\nSubclassing Provider\nAbstractProvider\nAbstractProviderPlugin\nFilterIdEventSubscriber\nFilterIdPendingSubscriber\nFilterIdSubscriber\nOnBlockSubscriber\nPerformActionTransaction\nPollingBlockSubscriber\nPollingEventSubscriber\nPollingTransactionSubscriber\nSubscriber\nUnmanagedSubscriber\nSocket Providers\nSubclassing Signer\nENS Resolver\nFallback Provider\nFormatting\nJSON-RPC Provider\nCommunity Providers\nTransactions\nUtilities\nWallets\nWordlists\nCookbook\nMigrating from v5\nContributions and Hacking\nLicense and Copyright\n\nSingle Page\n\nDocumentation »API »Providers »Subclassing Provider\nSubclassing Provider\nThe available providers should suffice for most developers purposes, but the AbstractProvider class has many features which enable sub-classing it for specific purposes.\n\nTYPES\n<src>AbstractProviderOptions⇒ { cacheTimeout?: number , pollingInterval?: number }\nOptions for configuring some internal aspects of an AbstractProvider.\ncacheTimeout - how long to cache a low-level _perform for, based on input parameters. This reduces the number of calls to getChainId and getBlockNumber, but may break test chains which can perform operations (internally) synchronously. Use -1 to disable, 0 will only buffer within the same event loop and any other value is in ms. (default: 250)\n\n<src>DebugEventAbstractProvider⇒ { action: \"sendCcipReadFetchRequest\" , index: number , request: FetchRequest , urls: Array< string > } | { action: \"receiveCcipReadFetchResult\" , request: FetchRequest , result: any } | { action: \"receiveCcipReadFetchError\" , request: FetchRequest , result: any } | { action: \"sendCcipReadCall\" , transaction: { data: string , to: string } } | { action: \"receiveCcipReadCallResult\" , result: string , transaction: { data: string , to: string } } | { action: \"receiveCcipReadCallError\" , error: Error , transaction: { data: string , to: string } }\nThe types of additional event values that can be emitted for the \"debug\" event.\n\n<src>PerformActionFilter⇒ { address?: string | Array< string > , fromBlock?: BlockTag , toBlock?: BlockTag , topics?: Array< null | string | Array< string > > } | { address?: string | Array< string > , blockHash?: string , topics?: Array< null | string | Array< string > > }\nA normalized filter used for PerformActionRequest objects.\n\n<src>PerformActionRequest⇒ { method: \"broadcastTransaction\" , signedTransaction: string } | { blockTag: BlockTag , method: \"call\" , transaction: PerformActionTransaction } | { method: \"chainId\" } | { method: \"estimateGas\" , transaction: PerformActionTransaction } | { address: string , blockTag: BlockTag , method: \"getBalance\" } | { blockTag: BlockTag , includeTransactions: boolean , method: \"getBlock\" } | { blockHash: string , includeTransactions: boolean , method: \"getBlock\" } | { method: \"getBlockNumber\" } | { address: string , blockTag: BlockTag , method: \"getCode\" } | { method: \"getGasPrice\" } | { filter: PerformActionFilter , method: \"getLogs\" } | { method: \"getPriorityFee\" } | { address: string , blockTag: BlockTag , method: \"getStorage\" , position: bigint } | { hash: string , method: \"getTransaction\" } | { address: string , blockTag: BlockTag , method: \"getTransactionCount\" } | { hash: string , method: \"getTransactionReceipt\" } | { hash: string , method: \"getTransactionResult\" }\nThe AbstractProvider methods will normalize all values and pass this type to abstractProvider._perform.\n\n<src>Subscription⇒ { tag: string , type: \"block\" | \"close\" | \"debug\" | \"error\" | \"finalized\" | \"network\" | \"pending\" | \"safe\" } | { hash: string , tag: string , type: \"transaction\" } | { filter: EventFilter , tag: string , type: \"event\" } | { filter: OrphanFilter , tag: string , type: \"orphan\" }\nThe value passed to the abstractProvider._getSubscriber method.\nOnly developers sub-classing [[AbstractProvider[[ will care about this, if they are modifying a low-level feature of how subscriptions operate.\n\nFUNCTIONS\n<src>getPollingSubscriber(provider: AbstractProvider, event: ProviderEvent)⇒ Subscriber\nReturn the polling subscriber for common events.\n\nclass AbstractProvider\ninherits from Provider, ContractRunner, EventEmitterable, NameResolver\nAn AbstractProvider provides a base class for other sub-classes to implement the Provider API by normalizing input arguments and formatting output results as well as tracking events for consistent behaviour on an eventually-consistent network.\n\nPROPERTIES\n<src>abstractProvider._requestRate⇒ null | number\nLimit the number of requests per second. (default: no limit)\n\n<src>abstractProvider.destroyed⇒ booleanread-only\nIf this provider has been destroyed using the destroy method.\nOnce destroyed, all resources are reclaimed, internal event loops and timers are cleaned up and no further requests may be sent to the provider.\n\n<src>abstractProvider.disableCcipRead⇒ boolean\nPrevent any CCIP-read operation, regardless of whether requested in a call using enableCcipRead.\n\n<src>abstractProvider.paused⇒ boolean\nWhether the provider is currently paused.\nA paused provider will not emit any events, and generally should not make any requests to the network, but that is up to sub-classes to manage.\nSetting paused = true is identical to calling .pause(false), which will buffer any events that occur while paused until the provider is unpaused.\n\n<src>abstractProvider.plugins⇒ Array< AbstractProviderPlugin >read-only\nReturns all the registered plug-ins.\n\n<src>abstractProvider.pollingInterval⇒ numberread-only\n\n<src>abstractProvider.provider⇒ thisread-only\nReturns this, to allow an AbstractProvider to implement the ContractRunner interface.\n\nCREATING INSTANCES\n<src>new AbstractProvider(network?: \"any\" | Networkish, options?: AbstractProviderOptions)\nCreate a new AbstractProvider connected to network, or use the various network detection capabilities to discover the Network if necessary.\n\nMETHODS\n<src>abstractProvider._clearTimeout(timerId: number)⇒ void\nClear a timer created using the _setTimeout method.\n\n<src>abstractProvider._detectNetwork()⇒ Promise< Network >\nResolves to the Network, forcing a network detection using whatever technique the sub-class requires.\nSub-classes must override this.\n\n<src>abstractProvider._forEachSubscriber(func: (s: Subscriber) => void)⇒ void\nPerform func on each subscriber.\n\n<src>abstractProvider._getAddress(address: AddressLike)⇒ string | Promise< string >\nReturns or resolves to the address for address, resolving ENS names and Addressable objects and returning if already an address.\n\n<src>abstractProvider._getBlockTag(blockTag?: BlockTag)⇒ string | Promise< string >\nReturns or resolves to a valid block tag for blockTag, resolving negative values and returning if already a valid block tag.\n\n<src>abstractProvider._getFilter(filter: Filter | FilterByBlockHash)⇒ PerformActionFilter | Promise< PerformActionFilter >\nReturns or resolves to a filter for filter, resolving any ENS names or Addressable object and returning if already a valid filter.\n\n<src>abstractProvider._getProvider(chainId: number)⇒ AbstractProvider\n\n<src>abstractProvider._getSubscriber(sub: Subscription)⇒ Subscriber\nSub-classes may override this to customize subscription implementations.\n\n<src>abstractProvider._getTransactionRequest(request: TransactionRequest)⇒ PerformActionTransaction | Promise< PerformActionTransaction >\nReturns or resolves to a transaction for request, resolving any ENS names or Addressable and returning if already a valid transaction.\n\n<src>abstractProvider._perform(req: PerformActionRequest)⇒ Promise< T >\nSub-classes should use this to perform all built-in operations. All methods sanitizes and normalizes the values passed into this.\nSub-classes must override this.\n\n<src>abstractProvider._recoverSubscriber(oldSub: Subscriber, newSub: Subscriber)⇒ void\nIf a Subscriber fails and needs to replace itself, this method may be used.\nFor example, this is used for providers when using the eth_getFilterChanges method, which can return null if state filters are not supported by the backend, allowing the Subscriber to swap in a PollingEventSubscriber.\n\n<src>abstractProvider._setTimeout(func: () => void, timeout?: number)⇒ number\nCreate a timer that will execute func after at least timeout (in ms). If timeout is unspecified, then func will execute in the next event loop.\nPausing the provider will pause any associated timers.\n\n<src>abstractProvider._wrapBlock(value: BlockParams, network: Network)⇒ Block\nProvides the opportunity for a sub-class to wrap a block before returning it, to add additional properties or an alternate sub-class of Block.\n\n<src>abstractProvider._wrapLog(value: LogParams, network: Network)⇒ Log\nProvides the opportunity for a sub-class to wrap a log before returning it, to add additional properties or an alternate sub-class of Log.\n\n<src>abstractProvider._wrapTransactionReceipt(value: TransactionReceiptParams, network: Network)⇒ TransactionReceipt\nProvides the opportunity for a sub-class to wrap a transaction receipt before returning it, to add additional properties or an alternate sub-class of TransactionReceipt.\n\n<src>abstractProvider._wrapTransactionResponse(tx: TransactionResponseParams, network: Network)⇒ TransactionResponse\nProvides the opportunity for a sub-class to wrap a transaction response before returning it, to add additional properties or an alternate sub-class of TransactionResponse.\n\n<src>abstractProvider.attachPlugin(plugin: AbstractProviderPlugin)⇒ this\nAttach a new plug-in.\n\n<src>abstractProvider.ccipReadFetch(tx: PerformActionTransaction, calldata: string, urls: Array< string >)⇒ Promise< null | string >\nResolves to the data for executing the CCIP-read operations.\n\n<src>abstractProvider.destroy()⇒ void\nSub-classes may use this to shutdown any sockets or release their resources and reject any pending requests.\nSub-classes must call super.destroy().\n\n<src>abstractProvider.getAvatar(name: string)⇒ Promise< null | string >\n\n<src>abstractProvider.getPlugin(name: string)⇒ null | T\nGet a plugin by name.\n\n<src>abstractProvider.getResolver(name: string)⇒ Promise< null | EnsResolver >\n\n<src>abstractProvider.pause(dropWhilePaused?: boolean)⇒ void\nPause the provider. If dropWhilePaused, any events that occur while paused are dropped, otherwise all events will be emitted once the provider is unpaused.\n\n<src>abstractProvider.resume()⇒ void\nResume the provider.\n\ninterface AbstractProviderPlugin\nAn AbstractPlugin is used to provide additional internal services to an AbstractProvider without adding backwards-incompatible changes to method signatures or other internal and complex logic.\n\nPROPERTIES\n<src>abstractProviderPlugin.name⇒ stringread-only\nThe reverse domain notation of the plugin.\n\nMETHODS\n<src>abstractProviderPlugin.connect(provider: AbstractProvider)⇒ AbstractProviderPlugin\nCreates a new instance of the plugin, connected to provider.\n\nclass FilterIdEventSubscriber\ninherits from FilterIdSubscriber, Subscriber\nA FilterIdSubscriber for receiving contract events.\n\nCREATING INSTANCES\n<src>new FilterIdEventSubscriber(provider: JsonRpcApiProvider, filter: EventFilter)\nCreates a new FilterIdEventSubscriber attached to provider listening for filter.\n\nclass FilterIdPendingSubscriber\ninherits from FilterIdSubscriber, Subscriber\nA FilterIdSubscriber for receiving pending transactions events.\n\nclass FilterIdSubscriber\ninherits from Subscriber\nSome backends support subscribing to events using a Filter ID.\nWhen subscribing with this technique, the node issues a unique Filter ID. At this point the node dedicates resources to the filter, so that periodic calls to follow up on the Filter ID will receive any events since the last call.\n\nCREATING INSTANCES\n<src>new FilterIdSubscriber(provider: JsonRpcApiProvider)\nCreates a new FilterIdSubscriber which will used _subscribe and _emitResults to setup the subscription and provide the event to the provider.\n\nMETHODS\n<src>filterIdSubscriber._emitResults(provider: AbstractProvider, result: Array< any >)⇒ Promise< void >\nSub-classes must override this handle the events.\n\n<src>filterIdSubscriber._recover(provider: AbstractProvider)⇒ Subscriber\nSub-classes must override this handle recovery on errors.\n\n<src>filterIdSubscriber._subscribe(provider: JsonRpcApiProvider)⇒ Promise< string >\nSub-classes must override this to begin the subscription.\n\nclass OnBlockSubscriber\ninherits from Subscriber\nAn OnBlockSubscriber can be sub-classed, with a _poll implmentation which will be called on every new block.\n\nCREATING INSTANCES\n<src>new OnBlockSubscriber(provider: AbstractProvider)\nCreate a new OnBlockSubscriber attached to provider.\n\nMETHODS\n<src>onBlockSubscriber._poll(blockNumber: number, provider: AbstractProvider)⇒ Promise< void >\nCalled on every new block.\n\ninterface PerformActionTransaction\ninherits from PreparedTransactionRequest\nA normalized transactions used for PerformActionRequest objects.\n\nPROPERTIES\n<src>performActionTransaction.from⇒ string\nThe sender of the transaction.\n\n<src>performActionTransaction.to⇒ string\nThe to address of the transaction.\n\nclass PollingBlockSubscriber\ninherits from Subscriber\nA PollingBlockSubscriber polls at a regular interval for a change in the block number.\n\nPROPERTIES\n<src>pollingBlockSubscriber.pollingInterval⇒ number\nThe polling interval.\n\nCREATING INSTANCES\n<src>new PollingBlockSubscriber(provider: AbstractProvider)\nCreate a new PollingBlockSubscriber attached to provider.\n\nclass PollingEventSubscriber\ninherits from Subscriber\nA PollingEventSubscriber will poll for a given filter for its logs.\n\nCREATING INSTANCES\n<src>new PollingEventSubscriber(provider: AbstractProvider, filter: EventFilter)\nCreate a new PollingTransactionSubscriber attached to provider, listening for filter.\n\nclass PollingTransactionSubscriber\ninherits from OnBlockSubscriber, Subscriber\nA PollingTransactionSubscriber will poll for a given transaction hash for its receipt.\n\nCREATING INSTANCES\n<src>new PollingTransactionSubscriber(provider: AbstractProvider, hash: string)\nCreate a new PollingTransactionSubscriber attached to provider, listening for hash.\n\ninterface Subscriber\nA Subscriber manages a subscription.\nOnly developers sub-classing [[AbstractProvider[[ will care about this, if they are modifying a low-level feature of how subscriptions operate.\n\nPROPERTIES\n<src>subscriber.pollingInterval⇒ number\nThe frequency (in ms) to poll for events, if polling is used by the subscriber.\nFor non-polling subscribers, this must return undefined.\n\nMETHODS\n<src>subscriber.pause(dropWhilePaused?: boolean)⇒ void\nCalled when the subscription should pause.\nIf dropWhilePaused, events that occur while paused should not be emitted resume.\n\n<src>subscriber.resume()⇒ void\nResume a paused subscriber.\n\n<src>subscriber.start()⇒ void\nCalled initially when a subscriber is added the first time.\n\n<src>subscriber.stop()⇒ void\nCalled when there are no more subscribers to the event.\n\nclass UnmanagedSubscriber\ninherits from Subscriber\nAn UnmanagedSubscriber is useful for events which do not require any additional management, such as \"debug\" which only requires emit in synchronous event loop triggered calls.\n\nPROPERTIES\n<src>unmanagedSubscriber.name⇒ string\nThe name fof the event.\n\nCREATING INSTANCES\n<src>new UnmanagedSubscriber(name: string)\nCreate a new UnmanagedSubscriber with name.\n\nSocket Providers\nGeneric long-lived socket provider.\nSub-classing notes\n\na sub-class MUST call the `_start()` method once connected\na sub-class MUST override the `_write(string)` method\na sub-class MUST call `_processMessage(string)` for each message\n\nclass SocketBlockSubscriber\ninherits from SocketSubscriber, Subscriber\nA SocketBlockSubscriber listens for newHeads events and emits \"block\" events.\n\nclass SocketEventSubscriber\ninherits from SocketSubscriber, Subscriber\nA SocketEventSubscriber listens for event logs.\n\nPROPERTIES\n<src>socketEventSubscriber.logFilter⇒ EventFilterread-only\nThe filter.\n\nclass SocketPendingSubscriber\ninherits from SocketSubscriber, Subscriber\nA SocketPendingSubscriber listens for pending transacitons and emits \"pending\" events.\n\nclass SocketProvider\ninherits from JsonRpcApiProvider, AbstractProvider\nA SocketProvider is backed by a long-lived connection over a socket, which can subscribe and receive real-time messages over its communication channel.\n\nCREATING INSTANCES\n<src>new SocketProvider(network?: Networkish, options?: JsonRpcApiProviderOptions)\nCreates a new SocketProvider connected to network.\nIf unspecified, the network will be discovered.\n\nMETHODS\n<src>socketProvider._processMessage(message: string)⇒ Promise< void >\nSub-classes must call this with messages received over their transport to be processed and dispatched.\n\n<src>socketProvider._register(filterId: number | string, subscriber: SocketSubscriber)⇒ void\nRegister a new subscriber. This is used internalled by Subscribers and generally is unecessary unless extending capabilities.\n\n<src>socketProvider._write(message: string)⇒ Promise< void >\nSub-classes must override this to send message over their transport.\n\nclass SocketSubscriber\ninherits from Subscriber\nA SocketSubscriber uses a socket transport to handle events and should use _emit to manage the events.\n\nPROPERTIES\n<src>socketSubscriber.filter⇒ Array< any >read-only\nThe filter.\n\nCREATING INSTANCES\n<src>new SocketSubscriber(provider: SocketProvider, filter: Array< any >)\nCreates a new SocketSubscriber attached to provider listening to filter.\n\nMETHODS\n<src>socketSubscriber._emit(provider: SocketProvider, message: any)⇒ Promise< void >\nSub-classes must override this to emit the events on the provider.\n\n← Providers\nSubclassing Signer→\n\nThe content of this site is licensed under the Creative Commons License. Generated on June 18, 2026, 3:32am.","tokens":4581,"crawled_at":1791194021332}
+{"id":10325,"url":"https://docs.dydx.xyz/concepts/onboarding-faqs","domain":"docs.dydx.xyz","chapter":"defi_protocols","title":"Onboarding FAQs – dYdX Documentation","text":"Background\n\n1. How does the network work?\ndYdX Chain (or \"v4\") is composed of full nodes and each maintains an in-memory order book. Anyone can use the open source software to run a full node. Traders can submit order placements and cancellations to full nodes, which gossip the transactions amongst themselves.\n\nFull nodes with enough delegated layer 1 governance tokens participate in block building as validators. Validators on dYdX Chain take turns proposing blocks of trades every ~1 second. The validator whose turn it is to propose a block at a given height is called the proposer. The proposer uses its mempool orderbook to propose a block of matches, which validators either accept or reject according to CometBFT (Tendermint) consensus.\n\nAll full nodes have visibility into the consensus process and the transactions in the mempool. Another component of dYdX Chain is the indexer software, an application that reads data from full nodes and exposes it via REST / WebSocket APIs for convenience.\n\n2. What is the difference between a full node and a validator?\nA full node does not participate in consensus. It receives data from other full nodes and validators in the network via the gossip protocol. A validator participates in consensus by broadcasting votes signed by each validator’s private keys.\n\n3. What are the benefits of running a full node as a market maker?\nRunning a full node will eliminate the latency between placing an order and when the actual order is gossiped throughout the network. Without your own node, your order will need to first be relayed to the nearest geographic node, which will then propagate it throughout the network for you. With your own node, your order will directly be gossiped.\n\nAdditionally, running a full node allows you to use full node streaming, a feature that aims to provide real-time, accurate orderbook updates and fills.\n\nInstructions on setting up a full node can be found here.\n\n4. What is the current block time?\nThe current block time is ~1 second on average.\n\n5. What is an indexer?\nThe indexer is a read-only service that consumes real-time data from dYdX Chain to a database for visibility to users. The indexer consumes data from dYdX Chain via a connection to a full node. The full node contains a copy of the blockchain and an in-memory order book. When the full node updates its copy of the blockchain and in-memory order book due to processing transactions, it will also stream these updates to the indexer. The indexer keeps the data in its database synced with the full-node using these updates. This data is made available to users querying through HTTPS REST APIs and streaming via websockets. More info can be found here.\n\nTrading\n\n1. How can I understand how finality works on dYdX Chain?\nWhen your order fills, a block proposer will propose a block containing the fill (visible to the whole network), and then the block will go through consensus. If the block is valid it will be finalized a couple seconds later (in Cosmos-speak this happens at the “commit” stage of consensus after all validators have voted). At that point, an indexer service will communicate the fill to you.\n\nIt is recommended to post orders with a “Good-Til-Block” of the current block height, and adjusting prices once per block. If the block is published without a match to your order, you know that it is no longer active and did not fill.\n\n2. What are the different order types in dYdX Chain?\nThere are two order types: Short-Term orders and stateful orders.\n\nShort-Term orders are meant for programmatic, low-latency traders that want to place orders with shorter expirations.\n\nStateful orders are meant for retail that wants to place orders with longer expirations. These orders exist on chain.\n\n3. How does the orderbook work in dYdX Chain for short-term orders?\nEach validator runs their own in-memory orderbook (also known as mempool), and the set of orders each validator knows about is what order placement transactions are in their mempool.\n\nUser places a trade on a decentralized front end (e.g., website) or via the typescript or python client that places orders directly to a full node or validator API.\n\nThe consensus process picks one validator to be the block proposer. The selected validator will propose their view of the matches in the next proposed block.\n\nIf the matches are valid (orders cross, subaccounts well-collateralized, etc.) and accepted by ⅔+ of validator stake weight (consensus), then the block is committed and those matches are written to state as valid matches.\n\nAfter the block is committed, the updated onchain (and offchain) data is streamed from full nodes to Indexers. The Indexer then makes this data available via API and websockets back to the front end and/or any other outside services querying for this data.\n\nNote: the block proposer’s matches are the canonical matches for the next block assuming their block is accepted by consensus.\n\nOther validators maintain a list of matches and those matches might differ from the block proposer’s matches, but if they’re not the block proposer those matches will not be proposed in the next block.\n\nSimilarly, the indexer is not the block proposer so its list of matches might be different from the block proposer’s matches, until the network reaches finality.\n\n4. Why should market makers only use short-term orders?\nShort-Term orders are placed and can be immediately matched after they’re added to the mempool, while stateful orders can only be placed and matched after they’re added to a block.\n\nShort-Term orders should always have superior time priority to stateful orders.\n\nStateful orders have worse time priority since they can only be matched after they are included on the block, short-term orders can be matched in the same block.\n\nShort-Term orders have less restrictive rate limits than stateful order rate limits. See rate limits later on in this section.\n\nShort-Term orders can be replaced, and stateful orders currently don’t support replacement.\n\nShort-Term orders can be canceled immediately after they’re placed, while stateful orders can only be canceled after they’ve been included in a block.\n\nShort-Term orders can be received by validators in any order, while stateful orders have an ordering requirement and will fail to be placed if they’re received out of order.\n\nThis is because stateful orders use a “sequence number”, which is equivalent to a nonce on Ethereum. Short-Term orders don’t use this.\n\n5. How can I place a short-term order?\nPlease use the latest dYdX Chain typescript client to place orders.\n\nPlease refer to the order.proto for parameter and field definitions.\n\nFor more advanced order placements, please refer to one of the validator clients.\n\n6. How can I tell if the block proposer has placed my short-term order?\nThe block proposer has proposed and filled the order in the block.\n\nThe block proposer has the order in their mempool.\n\n7. How can I tell if my short-term order is canceled?\nShort-term order placements and cancellations are best-effort, and therefore can't be considered final (actually placed or canceled and unfillable) until expiry.\n\nA FOK or IOC order is also unfillable after expiry.\n\nThe indexer does not send a websocket notification when a short-term order expires, which happens when the chain height exceeds the goodTilBlock of the order.\n\nThe block height is the only reliable way to know if a short-term order is canceled with finality.\n\nHowever, the indexer does send a websocket notification when a short-term order cancel is received by the indexer's full node.\n\nIn most cases, this \"best effort\" cancel means the order is cancelled. However, some small fraction of these cancels are not successful.\n\nSee Limit Order Book and Matching for more information.\n\n8. How can I replace an order?\nReplacing an order reuses the short-term order placement function with the same order ID and an equal-to-or-greater good til block.\n\nNote: when replacing partially-filled orders, the previous fill amount is counted towards your current order.\n\nExample: Buy 1 BTC order @ $20k is filled for 0.5 BTC. After replacing that order with a Buy 2 BTC order @ $25k, that order can only be filled for a maximum of 1.5 BTC. This is because the previously replaced order was already filled for 0.5 BTC.\n\n9. Are fills computed/updates streamed only when a block is finalized? How about order placements?\nFills are computed only when a block is finalized.\n\nShort term order place / cancel (including IOC / FOK orders being canceled due to not filling / being on the book or POST-ONLY orders crossing) are streamed when the full node the Indexer deployment is listening to receives the order / cancel and not only when the block is finalized.\n\nThis is why the status “BEST_EFFORT_OPENED” or “BEST_EFFORT_CANCELED” since the Indexer only knows that a full-node received the order / cancel, and it’s not guaranteed to be true across the whole network.\n\nFor the orderbook updates, these are sent when the full-node the Indexer is listening to receives orders / cancels and not just when the block is finalized.\n\nFor example, when the full-node receives a short term order it will be approximate how much is filled and how much would go on the orderbook. This is what the Indexer uses to stream orderbook updates. However, there is no guarantee that the orderbook looks the same in other nodes in the network.\n\nNote that you can now stream the orderbook directly through your full node for the orderbook. Read more about that here.\n\n10. Do orders get matched and removed from the book in between blocks?\nFor removal of short term orders, yes they can be removed in between blocks, however this is on a node-by-node basis and not across the whole network.\n\nE.g. a short-term order could be removed on one node, but still be present on another.\n\nWhen a short-term order expires (current block height > goodtilBlock), then it is guaranteed to be removed from all nodes.\n\nFor removal of stateful orders, they can be removed from the book in-between blocks. This is on a node-by-node basis.\n\nIf the node removing the stateful orders is the block proposer, these stateful order removals will also be propagated to all other nodes, and be entirely removed from the network.\n\nFor all orders, regarding matching:\n\nFor matching, each node on the network will attempt to match the orders as they are received in-between blocks.\n\nPer block, only 1 node (the block proposer) will propagate the matches it’s done during the block to all other nodes in the network. Validator nodes take turns being the block proposer based on their stake weight.\n\nIf a set of validators with ⅔+ of the stake weight of the network see the matches propagated as valid, then those matches are included in the block when finalized.\n\nThe only matches that occur on the network are the ones in the block.\n\n11. Do certain order types have priority? Are cancels prioritized?\nShort term orders when received by a node will be matched against its in-memory orderbook.\n\nCancels of short-term orders are also processed by a node when received.\n\nStateful orders (long-term / conditional) are matched at the end of the block when they are received.\n\nE.g. Stateful orders have at least a 1 block-time delay (it’s possible the order does not get included in the block) between a node receiving the order, and it being matched.\n\nStateful order placement will be processed AFTER short-term order placements and cancellations for a block.\n\nStateful order cancellations are also done at the end of the block they are received.\n\nThe stateful order cancellations are also processed AFTER short-term placements and cancellations for a block.\n\nAs mentioned above, only the matches from the block proposer will be included in the block (if a set of validators with ⅔+ of the stake weight of the network see the matches as valid).\n\n12. How does the order cancellation mechanism work?\nShort-term:\n\nWhen validators receive a cancellation, if they don't already see a match for the order, they will remove the order from their order book.\n\nOnly once every validator receives the cancellation is when the order will no longer be able to be matched.\n\nThe other way an order would no longer be matchable is if the block height is past the good til block.\n\nLong-term:\n\nOnce a stateful order cancellation is included into a block, the order will be canceled and no longer matchable. This could take 1s+ for a cancelation to be included in a block.\n\n13. Why is it slower to cancel orders than place orders?\nAn order placement only needs to be on a single validator to have a match happen, but the cancellation has to have arrived at the block proposer. Since the BP rotates, to be completely sure that the order won't be matched, it has to arrive at all the validators who will be block proposer before the order expires. This is why cancelations seem to be guaranteed slower than placing/matching orders.\n\n14. How do order statuses transition for the Indexer, for short-term and long-term orders?\nShort-term:\n\nOnce the order is placed and seen by the Indexer's full-node, the order has status BEST_EFFORT_OPENED.\n\nIf the order is matched and has a fill in a block, the order has status OPEN.\n\nIf the order is fully-filled, the order has status FILLED.\n\nIf the order is canceled by a cancel order message, the order will have status BEST_EFFORT_CANCELED. The order may still have fills if other validator nodes haven't received the cancel message yet.\n\nIf the order expires due to the block height exceeding the good til block of the order, the order status will be CANCELED. The order can no longer be filled.\n\nLong-term:\n\nOnce the order is placed and included in a block, the order has status OPEN.\n\nIf the order is fully filled, the order has status FILLED.\n\nIf the cancelation of the order is included in a block, the order has status CANCELED. The order can no longer be filled.\n\n15. How do subaccounts work on dYdX Chain?\nEach address’s subaccounts all fall under a single address, but they are labeled subaccount0, subaccount1, etc. This is unlike v3, where each subaccount was a secondary address.\n\nTo begin trading, you need to make sure your funds are in your subaccount. You can do this two ways:\n\nFrontend: Simply leave your frontend open and it will automatically sweep.\n\nBackend: Simply transfer USDC to it like in this example.\n\n16. Do I need gas when I transfer funds to create a new subaccount?\nYes, you will need gas. Fortunately, both USDC and cosmos native dYdX can be used to pay for gas fees. This USDC must be in the main wallet and not another subaccount to pay for fees.\n\nTo ensure this, the frontend leaves a small amount of USDC in your wallet when sweeping into your subaccount, to ensure there's enough to pay for gas.\n\n17. What impact do subaccounts have on rate limits?\nRate limits are per account, and not per subaccount.\n\n18. How do we compete for liquidation orders?\nIf you run a full-node, there is a liquidations daemon that has metrics on what accounts are up for liquidation orders, and they could try and compete for liquidations that way.\n\nHowever, this is not at all documented so you'll have to work it out by reading code.\n\nFull Nodes & Validators\n\n1. How much throughput and latency can be expected from a self-hosted full node? Would having multiple full nodes in different regions improve speed?\nThroughput of up to 1500 orders/second from our load-testing. Latency depends on which validator is the proposer. Having multiple full-nodes in different regions where there are validators (so maybe 1 in Europe + 1 in Tokyo) would lead to improved latency.\n\n2. Do validators communicate through a public P2P network, or is there an internal network?\nIt's a public P2P network.\n\n3. What is the expected order-to-trade latency under normal conditions?\nExpected order → trade latency would be:\n\nTime for order to get from the node it was submitted to, to the proposer, so location dependent.\n\nOrder match -> trade, probably at least 1 block so ~0.8s, could be more than 1 block.\n\n4. Is it faster to submit transactions directly to a validator or to broadcast transactions to the network?\nIt is faster to submit a transaction directly to the block proposer. The speed difference between a full-node and a validator is negligible unless that validator is the proposer.\n\n5. Do you have some validators that we can send orders to?\nValidators don't expose the RPC endpoints for orders.\n\n6. How do other teams improve their speed?\nSome teams are trying to get data about the order book/order updates from a full-node they are running to improve the latency to receiving data, as there is additional latency to getting order updates due to the Indexer systems having additional latency. We currently do not have documentation around this, but are working on it.\n\nIndexer\n\n1. How does the indexer reconstruct the orderbook when it started/initial snapshot of the book?\nA full node is run alongside the Indexer and sends messages to the indexer when it receives orders either from the RPC or gossiped from other nodes, as well as any updates from:\n\nnode pruning the order when it expires.\n\nanother order that matches an order that the node received earlier.\n\nnode removing order due to receiving a cancel from RPC or gossip.\n\nThe indexer also updates the order book whenever it receives these order messages.\n\n2. How does the indexer know what orders are in the book on start up?\nOn a cold-start, a full-node would still have all the stateful orders and would send them to the indexer. For short-term orders, the full-node would not know them, nor would the indexer. Since short-term orders only are valid for 20 blocks, within 20 blocks the indexer would have an accurate view of the order book, but for the first 20 blocks it would not.\n\nMEV\n\n1. How will dYdX Chain handle MEV?\nUnlike general-purpose smart contract environments, the Cosmos infrastructure enables unique MEV solutions to be built that align a validator’s incentives with a user’s incentives. dYdX Chain has a framework where MEV is measured via a dashboard. The first step would be to punish validators with slashing. Further proposed solutions are still being considered, and will be announced once finalized.\n\n2. When do I have finality related to fills?\nWhen your order fills, a block proposer proposes a block containing the fill (visible to the whole network), and then the block undergoes consensus. If the block is valid, it finalizes shortly thereafter (in Cosmos-speak this happens at the “commit” stage of consensus, after all validators have voted). In Cosmos, every block is final (no reorgs or forks).\n\nIf you’re connected via full node, you’ll see each step of this process. If you’re connected via the indexer service, you’ll see order updates over webSocket as soon as each block is confirmed.\n\n3. Is deliberately taking canceled orders considered an attack against makers?\nNodes should respect cancels as soon as they receive them. If they don't, then we see that as MEV and the aforementioned dashboard/metrics tracking MEV will track that.\n\nPricing\n\n1. How is the oracle price computed?\nThe oracle price has five parts:\n\nSlinky: sidecar that pulls price data from external sources and caches them for the validator to use link.\n\nVote Extensions: Every block during the Precommit stage, all validators will submit vote extensions for what they believe the oracle price of all tracked assets should be.\n\nConsensus: The block after VE are submitted, Slinky deterministically aggregates all VE from the previous block and proposes a new updated price which is voted into consensus.\n\nx/prices Module: updates the state based on the new price, also has logic for validation and etc. link.\n\nParams: determines the external sources and sensitivity link, these are configured per network (testnet genesis example), but should query the network config for these dydxprotocold query prices list-market-param.\n\n2. How often are prices updated on-chain?\nPrices within Slinky are committed on a one-block delay, since validators use the vote extensions from block n-1 to securely submit their price data for block n.\n\nMost of the time, prices will update every single block. Price updates happen when over 2/3 of validators are correctly running the Slinky sidecar.\n\nPrices will not update on any given block if:\n\nThe market is disabled within x/marketmap\n\nLess than 2/3s of validators (by stake weight) contributed to a price update. This can happen if not enough validators run Slinky, or there is a massive, widespread outage across providers.\n\n3. Does Slinky store historical prices?\nNo. Prices are stored in x/oracle module, and only stores the most recently posted price. However, you can use blockchain indexers or inspect past blocks to see the prices committed on previous heights.\n\nRewards\n\n1. How will trading rewards work on dYdX Chain?\nTrading rewards are not controlled by dYdX. dYdX recommends that trading rewards could be calculated primarily based on total taker fees paid, along with a few other variables. The full proposed formula can be found here,\n\n2. Do liquidity provider rewards exist on v4 (dYdX Chain)?\nLiquidity provider rewards in v4 are not controlled by dYdX. dYdX recommends that liquidity provider rewards should cease to exist in v4. Makers could be rewarded with a maker rebate ranging from 0.5bps to 1.1bps, based on their nominal volume and volume share. The full proposed fee schedule can be found here.","tokens":5368,"crawled_at":1791194026738}
+{"id":10326,"url":"https://a16zcrypto.com/posts/article/markets-need-rules","domain":"a16zcrypto.com","chapter":"research","title":"Markets need rules, and crypto is no different - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nMarkets need rules, and crypto is no different\nScott Duke Kominers\n09.02.25\n\nTags & Share Tags\nop-eds\npolicy & regulation\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nWith the U.S. government finally recognizing the benefits of blockchain technology, now the question becomes how best to harness it. Some may push for a regulatory free-for-all, but that would be a mistake. History — and economic theory — shows that thriving markets require clear, consistent rules. Crypto is no exception.\n\nIn some ways, resistance to centralized authority is baked into crypto’s DNA. Satoshi Nakamoto, the pseudonymous creator of Bitcoin, designed the protocol to bypass financial intermediaries, envisioning a currency that’s free from government or institutional control. Many early adopters shared an ethos of radical individualism, reminiscent of the freewheeling Homebrew Computer Club, the open source software movement, and early cryptography advocates.\n\nBut crypto’s full potential can only be realized if it becomes broadly accepted and integrated into ordinary commerce. And for entrepreneurs and consumers to embrace crypto, they must be confident in clear rules that protect against fraud while also ensuring robust and fair access. Without that confidence, people will hesitate to enter the market, let alone use crypto for everyday transactions.\n\nContrary to what some believe, a “free market” isn’t a free-for-all — it’s a structured system where individuals can engage in voluntary exchanges with reasonable expectations of fairness and security. Without basic protections, markets break down. Without safeguards, uncertainty will drive away serious investors and legitimate businesses, leaving behind only speculation and bad actors.\n\nWe need crypto to be a computer, not a casino.\n\nWhat kind of rules does crypto need?\n\nEconomists from Smith to Hayek, Friedman, de Soto, and beyond have long recognized that governments play a crucial role in setting up the guardrails that allow markets to flourish.\n\nSmith argued that property rights enable individuals to “secure the fruits of their own labor,” and that the government’s role is a “tolerable administration of justice” to secure those rights. For his part, Hayek believed that the role of government was to maintain the rule of law while avoiding capriciousness. Friedman famously conceded as roles for government both enforcement of contracts and protection of citizens from crimes against themselves or their property. And de Soto pointed out that a lack of clear rules and property rights leads to “dead capital.”\n\nPaul Atkins, the new chair of the U.S. Securities and Exchange Commission, echoed these sentiments in a recent speech, noting, “Regulators should provide the minimum effective dose of regulation necessary to protect investors while allowing entrepreneurs and businesses to flourish.”\n\nThe rules governing crypto — like those governing all markets — should aim to achieve four key objectives:\n\nFirst, predictability and stability. A functional market requires clear, enforceable rules. Entrepreneurs need to know how their businesses will be regulated. Investors need confidence that the rules won’t change arbitrarily. And consumers need to trust that their transactions are secure.\n\nSecond, protection of property rights. Secure ownership is the foundation of any market. Crypto excels at encoding ownership through blockchain technology, but legal frameworks must reinforce and complement these protections.\n\nThird, transparency and information clarity. Efficient markets depend on reliable information. Buyers need to understand what they are purchasing, whether it’s a digital asset, a decentralized finance product, or a non-fungible token (NFT). Regulations should promote disclosures that help consumers and investors make informed decisions, while preventing fraudulent schemes.\n\nFinally, fair competition. Rules should prevent monopolistic practices, market manipulation, and fraud. Without oversight and tailored guardrails, markets can become playgrounds for bad actors who exploit information asymmetries, deceive investors, or artificially inflate asset prices. And any regulatory framework needs to be congruent with existing rules so it doesn’t inadvertently create new workarounds to established protections.\n\nThese four features are essential for market function: Stability and predictability helps make people willing to engage in transactions; and clear property rights are necessary in order for those transactions to happen. Then transparency and open competition help ensure that the transactions people choose to engage in push markets towards more productive and socially valuable outcomes.\n\nThe path ahead\n\nCrypto is not a well-regulated industry today, although it is finally on that path. Crypto startups have spent years navigating a murky and often hostile regulatory landscape. As a result, while blockchain technology provides strong internal protections for property rights, the surrounding regulatory environment has been anything but supportive of a healthy market.\n\nThe SEC, for instance, has until recently, pursued crypto companies for alleged violations without first establishing clear legal standards. Entrepreneurs were left guessing which rules applied, only to face lawsuits after the fact. This created uncertainty that stifled innovation, while at the same time allowing bad actors to operate in the resulting grey zone.\n\nAdditionally, many crypto regulations were built for legacy financial systems, treating blockchain-based assets as if they were merely new forms of traditional securities or commodities. But crypto is more than just finance: it’s also a web infrastructure platform. Effective regulation must recognize both dimensions, ensuring that financial oversight does not choke off technological development.\n\nCrypto has the potential to revolutionize everything from personal identity verification to event management and global payments. But realizing that potential requires guardrails like a token taxonomy that provides legal definitions of digital commodities; standards for evaluating decentralization and disintermediation; consumer protection; tax guidelines; and a framework for how legitimate blockchain-based businesses can operate without fear of arbitrary prosecution.\n\nNone of this is radical or unprecedented. The principles that make markets work — stability, property rights, transparency, and fair competition — have long been understood. But they have yet to be consistently applied to crypto. That must change, and the industry must welcome it.\n\n***\n\nA version of this article first appeared in the Financial Times.\n\n***\n\nScott Duke Kominers is the Sarofim-Rock Professor of Business Administration at Harvard Business School, a Faculty Affiliate of the Harvard Department of Economics, and a Research Partner at a16z crypto. He also advises a number of companies on web3 strategy, as well as marketplace and incentive design; for further disclosures, see his website. He’s also the coauthor of The Everything Token: How NFTs and Web3 Will Transform the Way We Buy, Sell, and Create.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nThe content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":2429,"crawled_at":1791194031717}
+{"id":10327,"url":"https://docs.ethers.org/v6/basics/abi","domain":"docs.ethers.org","chapter":"developer_specs","title":"","text":"ethers\n6.17.0\n\nDOCUMENTATION\nGetting Started\nEthereum Basics\nTopics\nApplication Binary Interfaces\nCall Data Representation\nEvent Data Representation\nDeployment\nApplication Programming Interface\nCookbook\nMigrating from v5\nContributions and Hacking\nLicense and Copyright\n\nSingle Page\n\nDocumentation »Ethereum Basics »Application Binary Interfaces\nApplication Binary Interfaces\nWhen interacting with any application, whether it is on Ethereum, over the internet or within a compiled application on a computer all information is stored and sent as binary data which is just a sequence of bytes.\nSo every application must agree on how to encode and decode their information as a sequence of bytes.\nAn Application Binary Interface (ABI) provides a way to describe the encoding and decoding process, in a generic way so that a variety of types and structures of types can be defined.\nFor example, a string is often encoded as a UTF-8 sequence of bytes, which uses specific bits within sub-sequences to indicate emoji and other special characters. Every implementation of UTF-8 must understand and operate under the same rules so that strings work universally. In this way, UTF-8 standard is itself an ABI.\nWhen interacting with Ethereum, a contract received a sequence of bytes as input (provided by sending a transaction or through a call) and returns a result as a sequence of bytes. So, each Contract has its own ABI that helps specify how to encode the input and how to decode the output.\nIt is up to the contract developer to make this ABI available. Many Contracts implement a standard (such as ERC-20), in which case the ABI for that standard can be used. Many developers choose to verify their source code on Etherscan, in which case Etherscan computes the ABI and provides it through their website (which can be fetched using the getContract method). Otherwise, beyond reverse engineering the Contract there is not a meaningful way to extract the contract ABI.\n\nCall Data Representation\nWhen calling a Contract on Ethereum, the input data must be encoded according to the ABI.\nThe first 4 bytes of the data are the method selector, which is the keccak256 hash of the normalized method signature.\nThen the method parameters are encoded and concatenated to the selector.\nAll encoded data is made up of components padded to 32 bytes, so the length of input data will always be congruent to 4 mod 32.\nThe result of a successful call will be encoded values, whose components are padded to 32 bytes each as well, so the length of a result will always be congruent to 0 mod 32, on success.\nThe result of a reverted call will contain the error selector as the first 4 bytes, which is the keccak256 of the normalized error signature, followed by the encoded values, whose components are padded to 32 bytes each, so the length of a revert will be congruent to 4 mod 32.\nThe one exception to all this is that revert(false) will return a result or 0x.\n\nEvent Data Representation\nWhen an Event is emitted from a contract, there are two places data is logged in a Log: the topics and the data.\nAn additional fee is paid for each topic, but this affords a topic to be indexed in a bloom filter within the block, which allows efficient filtering.\nThe topic hash is always the first topic in a Log, which is the keccak256 of the normalized event signature. This allows a specific event to be efficiently filtered, finding the matching events in a block.\nEach additional indexed parameter (i.e. parameters marked with indexed in the signautre) are placed in the topics as well, but may be filtered to find matching values.\nAll non-indexed parameters are encoded and placed in the data. This is cheaper and more compact, but does not allow filtering on these values.\nFor example, the event Transfer(address indexed from, address indexed to, uint value) would require 3 topics, which are the topic hash, the from address and the to address and the data would contain 32 bytes, which is the padded big-endian representation of value. This allows for efficient filtering by the event (i.e. Transfer) as well as the from address and to address.\n\nDeployment\nWhen deploying a transaction, the data provided is treated as initcode, which executes the data as normal EVM bytecode, which returns a sequence of bytes, but instead of that sequence of bytes being treated as data that result is instead the bytecode to install as the bytecode of the contract.\nThe bytecode produced by Solidity is designed to have all constructor parameters encoded normally and concatenated to the bytecode and provided as the data to a transaction with no to address.\n\n← Ethereum Basics\nApplication Programming Interface→\n\nThe content of this site is licensed under the Creative Commons License. Generated on May 1, 2024, 1:07am.","tokens":1197,"crawled_at":1791194038226}
+{"id":10328,"url":"https://gov.uniswap.org/t/uniswap-council-uc-season-5-renewal/26065","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Uniswap Council (UC): Season 5 Renewal - Requests for Comment - Uniswap Governance","text":"Uniswap Council (UC): Season 5 Renewal\n\nRequests for Comment\n\nAbdullahUmar\n\nMarch 25, 2026, 11:31pm\n\n1\n\nAuthors: Abdullah (Arana Digital), Juanbug (PGov), Jordan (Event Horizon)\n\nimage|624x258.975911109725761151×477 27.2 KB\n\nBackground\n\nThe Uniswap Accountability Committee (UAC) will from hereon, be referred to as the Uniswap Council (UC), to more aptly represent the group’s existing functions.\n\nThis proposal outlines the UC’s mandate, structural changes, and budget request for Season 5. For more details around Season 4 operations and financials, please refer to the companion Season 4 Report.\n\nThe UC is a DAO-elected entity that supports Uniswap governance by ensuring that DAO-approved initiatives are executed transparently and efficiently. It operates as an independent, community-driven body that coordinates operational tasks, oversees service providers, and maintains governance integrity without setting policy or controlling protocol development. In practice, the UC serves as a lightweight operational layer for the DAO, translating governance decisions into action while remaining fully accountable to tokenholders.\n\nA UC season is a term during which a DAO-elected set of council members is authorized to carry out the UC’s mandate, with funding and scope renewed by governance at the end of the period.\n\nBelow are the areas that the UC presided over during Season 4\n\nCross-chain deployment coordination\n\nENS record management\n\nDisbursement and accounting of service provider, grantee, and working groups’ compensation\n\nCustody of DAO-approved funds on Ethereum mainnet\n\nIncentive distribution across a multitude of EVM-compatible chains\n\nGovernance community calls\n\nAssisting with miscellaneous DAO operations like helping teams sponsor proposals\n\nManaging the Foundation Feedback Group (FFG) to liaise between delegates and the Foundation\n\nGovernance logistics improvements\n\nIn this proposal, we also introduce new functions to support token holders and delegates in a post-UNIfication world, as well as adjust some previous operations.\n\nNavigating Moving Tides\n\nOver the past season, the organizational makeup of Uniswap has materially evolved. With Labs taking on a lion’s share of work and funding, and the Foundation winding down over time, the UC becomes the primary independent, community-driven counterweight within the ecosystem.\n\nThe UC’s mechanics remain firmly DAO-controlled. Its members are elected through Snapshot votes, and its funding must be approved by governance, which ensures that the team stays accountable. These structural constraints ensure accountability and alignment with tokenholder intent. At the same time, the UC operates as a smaller, more nimble body than the DAO as a whole, capable of responding to operational needs, coordinating service providers, and executing administrative tasks within clearly defined bounds. In practice, this positions the UC as a liaison across several DAO-adjacent functions, which are outlined in greater detail later in this report.\n\nWhile the committee maintains a deliberately narrow and procedurally defined mandate, the nature of its work has increasingly taken on operational characteristics. This evolution is not unique to Uniswap. Comparable models have emerged across the ecosystem as protocols mature. Arbitrum, for example, established the Arbitrum OpCo, a DAO-elected operational organization tasked with supporting ecosystem programs, vendor oversight, and administrative continuity. ENS operates with a similar pattern through its working groups, which collectively manage grants/service providers and public-facing reporting. In each case, the DAO retains ultimate authority, while the operational unit provides structure and continuity to day-to-day processes that require reliability and professionalization.\n\nWithin this landscape, the UC occupies a similar position. While “accountability” has been foundational to the committee’s mandate, the UC now acts more as an administrative and operational body on behalf of the DAO.\n\nAdoption of a Legal Entity\n\nAs of October, 2025, the UC has been incorporated as a Delaware Nonprofit Nonstock Corporation. As per its initial mandate, the UC entity is not designed to hold profits, issue equity, or accrue economic interests. It is solely meant to support governance integrity and operational accountability within the Uniswap ecosystem. Governance is handled exclusively through a Board of Directors. The composition of the board follows DAO-based elections, as per previous seasons.\n\nThis formalization provides the UC with a recognized legal body capable of entering contracts, receiving confidential information, issuing payments, and formally interacting with the DUNI, service providers, and other partners.\n\nWithin this evolving framework, the UC functions as an independent, DAO-elected operational body that interfaces with the DUNI but is not an official “service provider” like Uniswap Labs, nor is it assigned a role like “Ministerial Agent” or “Administrator.” In this respect, the UC’s structure aligns with a growing class of DAO-adjacent legal entities akin to BORGs, which are designed to carry out certain mandates on behalf of decentralized systems while remaining constrained by governance.\n\nSignatory/Multisig Operations\n\nUnchanged from previous seasons, the UC continues to manage two multisig addresses to conduct its operations:\n\nPrimary UC Wallet Address: 0x3B59C6d0034490093460787566dc5D6cE17F2f9C (UAC.eth)\n\nUC Incentives Wallet Address: 0xEBCCf1ce13F63c6B98811F03964F51fC43cef851\n\nThis wallet is deployed across various EVMs to facilitate incentive distribution on platforms like Merkl.\n\nGoing forward, the UC will not be responsible for disbursing incentives. Legal and tax surface area has expanded post DUNI adoption, and future incentives will be coordinated and executed with the DUNI.\n\nSeason 4 consisted of 5 members, representing diverse skillsets and organizational associations:\n\nAlice Corsini\n\nJordan Karstadt\n\nDoo Wan Nam\n\nJun Sun\n\nAbdullah Umar\n\nEach member is a signer on the UC multisigs and now a representative on the UC entity Board. Workload is divided among members based on their individual capacities and can vary month-to-month. Multisig duties and security, however, are an evenly assumed responsibility. All members must be ready to sign transactions when needed and uphold multisig integrity without exception.\n\nPrevious UC Seasons have lasted for approximately half-a-year each. Season 4 took place between May/June until the end of December 2025. Like prior seasons, 3 members of the UC have stayed active post season 4, planning for adjustments going into Season 5.\n\nVendor Payroll & Accountability\n\nThe UC has been responsible for disbursing payments to ecosystem vendors whose work has been previously authorized by governance. This includes but is not limited to:\n\nTally: governance infrastructure and execution support\n\nForse: incentives impact analytics\n\nOku: alternative Uniswap front-end, aggregator, and analytics site\n\nMerkl: incentivization infrastructure\n\nDAO programs: structured support for delegate engagement and Uniswap-related research\n\nGoing forward, the UC will manage this function differently from how it has been approached in the past. Rather than serving as an intermediary for ad hoc governance-approved funding, future funding will likely be sent to a DUNI-associated address and payments executed by the Ministerial Agent. Payments can also be structured in a more autonomous manner with vesting contracts. We will continue to help coordinate with these teams to ensure milestones, accountability, and transparency metrics are met.\n\nFurther, the UC will move to a pre-defined internal budgetary model. Anticipated vendor and operational expenditures will be scoped and requested upfront as part of the seasonal renewal proposal. Pre-defining these budgets simplifies operations by making the UC and its projects direct counterparties. Further, we are still able to help continue our previous seasons’ scope for independent governance approved funds over the season, now leaning on the DUNI for additional support with executing payments in a compliant manner.\n\nUniswap Deployments and Incentives\n\nThe UC will continue to serve as the administrative and coordination layer for cross-chain v3 deployments, working alongside deployers like Oku and Protofire to oversee deployment workflows, maintain the canonical contract registry and ENS subdomains, and support chains through the onboarding process. We will rely on closer coordination with Labs when it comes to newer v4 deployments.\n\nMore information on this function can be found here.\n\nTreasury Mobilization and Management\n\nTreasury strategy has been a recurring topic within the Uniswap ecosystem for several years, most formally explored through the Uniswap Treasury Working Group (UTWG). While the DAO previously signaled broad interest in developing a structured investment framework, the lack of a legal wrapper and operational infrastructure prevented meaningful progress. With the establishment of DUNI and the maturation of service provider relationships, the conditions now exist to revisit this work responsibly. Recurring budget obligations and large, multi-year engagements further underscore the need for a deliberate treasury management approach.\n\nTo start, we want to emphasize that we primarily want to kick off these discussions in a formal and compliant manner post-DUNI adoption. There will be significant tasks to complete before we get to a vendor selection phase, but we believe it is a very important opportunity that should be actively discussed and focused on by the DAO.\n\nAs a result, a natural next step may be for the UC to initiate a formal Request for Proposals (RFP) to evaluate qualified treasury managers. Other large DAOs—ENS, Aave, Lido, Gnosis—have successfully partnered with firms such as Karpatkey, Steakhouse, Avantgarde, and others to manage portions of their treasuries under clearly defined Investment Policy Statements (IPS). These IPS frameworks establish risk parameters, liquidity buffers, permissible assets, rebalancing logic, and reporting requirements. Implementing a similar structure under the DUNI would transition Uniswap from reactive treasury decisions toward a durable, mandate-aligned investment framework tailored to the protocol’s long-term needs.\n\nThe presence of the DUNI also opens the UC to explore new institutional partnerships with vendors that, for legal and structural reasons, may have been off the table over the past handful of years. At present, the UC is exploring a combination of the following methodologies:\n\nBasis Fund: Deploy UNI as collateral to capture the spread between spot and perpetual futures prices, targeting 10%+ APR; reasonable given that crypto basis spreads have historically averaged 8-20% annualized, and UNI’s moderate liquidity and higher volatility relative to BTC typically place it toward the upper end of that range.\n\nOptions: Pledge UNI collateral to systematically sell overpriced volatility via OTC options desks, targeting 15% APR; reasonable because UNI’s realized volatility consistently underperforms its implied volatility by 15-30%, creating a persistent risk premium harvestable through structured short vol strategies.\n\nMarket Making: Provide continuous two-sided liquidity across UNI spot pairs on CEXs and DEXs, earning the bid-ask spread and rebates while targeting 20% APR; reasonable given UNI’s $260M daily trading volume creates consistent flow to capture, and the persistent CEX/DEX price dislocations in mid-cap DeFi tokens offer structural arbitrage that wider spreads on UNI (relative to BTC/ETH) translate into higher per-trade margins.\n\nStatistical Arb: Exploit mean-reversion and momentum signals across correlated pairs like UNI/ETH, UNI/AAVE, and UNI/broader DeFi indices, targeting 20% APR; reasonable because UNI’s high beta to the DeFi sector creates frequent mispricings that revert on short timeframes, and the token’s strong correlation structure (0.7-0.85 with ETH) provides reliable pairs trading relationships.\n\nCollateralized Lending: Pledge UNI as collateral through OTC lending desks to borrow USDC at conservative LTVs, then deploy the stablecoins into high-grade yield opportunities such as T-bills, money market funds, or institutional DeFi vaults, targeting 5-10% net APR after borrowing costs; reasonable given that OTC lending desks typically offer more favorable borrowing rates and liquidation terms than onchain venues, eliminating smart contract risk and avoiding the reflexive liquidation cascades common in transparent lending markets.\n\nToken Swaps: Execute bilateral token swaps with strategically aligned DAOs, exchanging UNI for their native governance tokens at negotiated terms, targeting long-term portfolio diversification and ecosystem alignment rather than short-term yield; reasonable given that protocol-to-protocol swaps have become an established mechanism for DAOs to diversify concentrated native-token treasuries while simultaneously deepening governance and economic relationships with key ecosystem partners. The surface area for this, however, has narrowed due to the lack of value-oriented tokens. Swap structures can include vesting schedules and lockup periods to ensure mutual long-term commitment between blue-chip protocols.\n\nTo those ends, a focus for the UC during Season 5 will be initiating a comprehensive treasury management program, in concert with continuous feedback from governance and DUNI-related administrative entities. The core goal eventually will be to administer an RFP process to deliver a structured proposal in collaboration with an asset manager(s). Sizing the amount of allocated capital, specific strategies, and timelines will be key points that the UC seeks to delve into.\n\nBurn Bounties\n\nThe UC would like to further concretize its value with additional hard metric objectives. In line with the consolidation of ecosystem emphasis around burn, expansion of UNI burn is one natural avenue. At present, we have aligned around Treasury Management and Burn Bounties as two initial, but not only, ways to achieve this objective.\n\nTreasury Management:\n\nTreasury yield could be applied in any ratio to either UNI burn or Treasury Diversification as the UC and DUNI see most fit. To ensure sufficient capital to meaningfully drive either or both objectives, the UC has outlined the following benchmarks as approximate program targets:\n\n582×302 49 KB\n\nThe above is a potential result if treasury management-derived yield is used for burning UNI. But it will be up to governance to decide whether or not—or how much—treasury yield is used for compounding DUNI capital versus driving burn.\n\nBurn Bounties:\n\nTraditional grant programs teeter towards opaque net benefits to the DAO. In principle, most grants are intended to support builders. These builders create products. These products drive volume. This volume drives fees. And, as a final, most elemental value, these fees drive burn. However, attempting to incentivize developers building to deliver UNI burn, without making the objective an explicit KPI (burn), often involves value leakage for token holders. Burn bounties resolve this by incentivizing the end state desired value, burns, directly. The UC proposes paying builders a fixed amount, for example, 2%, of every dollar of UNI that their products burn, creating an incentive layer where the protocol captures 98% of the deflationary value while developers get paid to make Uniswap their default routing destination.\n\nIn this rebate model, and unlike conventional grant programs, the cost-to-value of every dollar emitted is deterministic. For example, if the rewards rate is 2% and the program is budgeted $200,000, then full capital deployment would mean that $10,000,000 in UNI was burned. If the program capital is partially allocated, let’s say $100,000 is claimed, then only $5,000,000 UNI has been burned, but the DAO has “spent” proportionally the same amount.\n\n|347.2870140612076x112644×206 39.1 KB\n\nCumulatively, we believe Treasury Management and Burn Bounties can augment the work already being done by Uniswap Labs. Today, the DAO is on track to burn ~$30M worth of UNI annually. We anticipate that together, Treasury Management and Burn Bounties could achieve as much as $16m in added burn, increasing the ecosystem’s projected annual burn by >50% with minimal cost to the DAO.\n\nimage346×532 61.9 KB\n\nAccordingly, we are requesting a total of $200k UNI to set up and manage a UNI Burn Bounty Program.\n\nInformation Liaison and Community Management\n\nIn previous seasons, the UC operated the Foundation Feedback Group (FFG), serving as an information bridge between the DAO and the Uniswap Foundation. This structure balanced the DAO’s expectation of visibility with the Foundation’s need to protect sensitive operational details.\n\nLabs has since entered into a service provider relationship with governance, which introduces expectations around transparent reporting and mandate alignment that go beyond ad hoc public announcements.\n\nWith the Foundation and Labs actively exploring how responsibilities and reporting practices will be consolidated, it would be premature to prescribe a fixed successor to the FFG. The UC intends to work closely with the relevant teams as this transition unfolds to identify an appropriate mechanism for ongoing information exchange, including cadence, scope, and how sensitive operational information can be responsibly distilled into public updates for delegates and tokenholders. However, ascribing this function as a definite UC mandate would be jumping the gun.\n\nIn addition to its liaison functions, the UC has hosted monthly governance community calls throughout its tenure, providing a regular forum for delegates and ecosystem participants to discuss active proposals, surface concerns, and engage directly with teams working on DAO-funded initiatives. These calls have served as an important complement to asynchronous forum activity, ensuring that governance discussions are accessible beyond the forum. The UC intends to continue facilitating these calls throughout Season 5, along with broader community management efforts aimed at keeping governance participants informed and engaged.\n\nGovernance Logistics Details\n\nDuring Season 4, the UC conducted an analysis on the overall state of governance (Governance Logistics Improvements), instigated by the sudden loss of significant voting power among a cohort of well-known delegates. This initiative analyzed major structural pain points in Uniswap DAO governance, opening community dialogue about potential paths forward.\n\nSince then, the adoption of the DUNI has quelled many of the concerns larger token holders and delegates held regarding active participation in votes and forum discussions, meaningfully shifting the delegation landscape.\n\nAs Uniswap governance enters this new stage, the UC intends to continue and deepen this line of work throughout Season 5, with a focus on:\n\nSurfacing and supporting community-created proposal ideas\n\nHelping design models for novel governance architectures suitable for Uniswap, like optimistic governance\n\nMonitoring quorum dynamics as token price, circulating supply, and delegation patterns continue to evolve\n\nProviding neutral, data-informed visibility into emerging governance risks and power-concentration dynamics\n\nGrant Graduation Pipeline\n\nHigh-quality infrastructure that has already been funded and developed through the Foundation’s grant programs should be sustained. A healthy governance ecosystem benefits from a clear “grant graduation pipeline,” in which successful grantees transition from one-time funded projects into long-term, DAO-supported service providers when their work proves beneficial.\n\nOku represents the clearest precedent for this model. The team received an initial grant from the Foundation, built and proved their product in the market, onboarding numerous clients and driving volume to EVM environments outside of Labs’ purview.\n\nAnother potential example is Blockful’s Anticapture product. Anticapture has been adopted by multiple DAOs across the Ethereum ecosystem. Uniswap was the first DAO integrated into Anticapture, funded by a $110k grant provided by the Foundation. That grant has now concluded. Blockful has continued to maintain indexers, analytics pipelines, and monitoring infrastructure without additional funding. The platform surfaces governance-critical indicators such as delegation concentration, token distribution across custody venues, proposal thresholds, quorum dynamics, and execution mechanics, contextualized within a broader risk-assessment framework.\n\nBringing such providers under the DAO’s funding umbrella ensures that critical tooling is not lost due to the expiration of grant funding. The UC intends to play a constructive role in identifying these high-impact grantees and, correspondingly, work with them to best provide value to the DAO. For example, Anticapture can supplement much of the UC’s governance logistics reporting.\n\nWe will continue exploring how to best serve this function going forward in concert with the Foundation. Accordingly, we are requesting a total $200k UNI budget for Grant Graduation purposes, with allocations made as candidates are assessed on an ad hoc basis. All of this will be continuously communicated publicly to the DAO.\n\nAccounting and Financials\n\nThroughout its tenure, the UC has maintained transparent accounting practices, tracking inflows, outflows, and program-specific account balances across all DAO-approved initiatives. The UC served as an escrow intermediary, receiving funds from the treasury upon onchain vote execution and disbursing them to vendors and programs upon verification of completed work. As of the end of Season 4, the majority of program accounts have been fully allocated and closed out, with remaining balances for active programs transferred to the DUNI. An accounting breakdown is available in the Season 4 report. Going forward, as outlined earlier, the UC will shift away from this intermediary model in favor of a pre-defined budgetary approach.\n\nSnapshot & Onchain Vote Summary\n\nComposition of the total UC team will remain at 5 members, with two new members elected in for Season 5 via a Snapshot vote. The staggered board system exists to prevent junctions between ongoing projects and training entirely new teams. The Snapshot election will occur after the onchain vote for renewing the UC passes. Abdullah, Jun, and Jordan will remain on the UC for Season 5, joined by the two newly elected candidates. The newly elected members will start as multisig signers and be onboarded over the season.\n\nWe are also proposing extending future seasons, starting with Season 5, to 12 months, as opposed to 6-8 months. This will help with personnel continuity and less administrative overhead, especially with the presence of the newly established UC nonstock corporation.\n\nBudget\n\nThe operational budget requested for Season 4 was $370k over 8 months, which included staffing, legal operations, accounting tools, etc. For similar line-items, we are requesting a total of $555k for Season 5 over 12 months, the exact same monthly budget.\n\nWe are making an additional budget request for Grant Graduation, totaling to $200k, along with a $200k proposed allocation towards the Burn Bounty Program. Grant Graduation allocations ensure that capital already allocated to promising prospects via the Foundation is effectively complemented. Some projects require follow-on funding. And the Burn Bounty allows the UC to support token holders by propelling further UNI burn using rebates.\n\nSeason 5 Request:\n\nDuration: 12 months\n\nUC Operating Budget: $555k\n\nGrant Graduation Pipeline: $200k\n\nBurn Bounty Program: $200k*\n\nTOTAL: $955,000 in UNI for 12 months\n\n*Note that the budget associated with burn bounty will only be released as explicit burn metrics are achieved. Hence, the total $200k will be expended if, and only if, $10M UNI is burned—given a 2% rebate.\n\nAll Accounts from previous seasons have been closed and returned to the DUNI, so the above funding is all that the UC will have under its purview going into Season 5. The discretionary budget has also been terminated.\n\n7 Likes\n\nSEEDGov\n\nMarch 27, 2026, 2:46pm\n\n2\n\nThanks Abdullah for the detailed proposal!\n\nWe have some concerns related to the Burn Bounty mechanism that we like to shere.\n\nThe core idea is compelling: aligning incentives directly around the end-state value (burn) rather than proxies like activity or volume is a meaningful improvement over traditional grant structures.\n\nThere’s one thing that concerns us: there is a clear potential vector for abuse, as a malicious actor could create a protocol or mechanism with artificial UNI trading volume (wash trading) to collect the bounty. For example, a team could route wash trades or self-referential volume through a front-end that technically burns UNI, at a cost lower than the 2% bounty they’d collect. The net result would be UNI burned, but at an unfavorable ratio for the DAO compared to organic burn.\n\nWe would like these concerns to be addressed before this mechanism is established:\n\nIt is necessary to consider and establish a system that prevents participants from generating fictitious trading volume in order to claim a bounty\n\nEstablish a validation or audit process before bounties are paid out\n\nEstablish a mechanism for the UC to intervene in the event of a potential attempt at abuse during the program\n\nWe think a specificity framework would strengthen this initiative.\n\n1 Like\n\nAbdullahUmar\n\nMarch 28, 2026, 4:52am\n\n3\n\nThanks for the thoughtful feedback, @SEEDGov.\n\nA couple of points:\n\nWashtrading in our eyes is less-so an issue. When you wash trade, you’re paying swap fees on every loop. Those swap fees are what fill the TokenJar. So you’re spending your own money to fill a pot, and your bounty is only 2% (or whatever rebate rate) of what a searcher eventually burns from that pot.\n\nYou’d spend $50 in swap fees to earn $1 back. There’s no way to make that math work in your favor since the wash trading costs more than the bounty pays.\n\nThat said, your point about the need for a clear verification and attribution framework is well taken. Attribution takes some effort and isn’t a perfect exercise.\n\nThe TokenJar is completely agnostic about what caused the fees. It just accumulates fee tokens. When a searcher triggers the burn, the chain records which pools generated fees, that the searcher paid some amount of UNI and got back the TockenJar’s contents, and that UNI was burned/sent to 0xdead. The issue is illustrating which FE, for example, routed the user to that pool in the first place.\n\nSo you can’t perfectly attribute the TokenJar release to a specific builder cause many builders’ traffic flows into the same shared TokenJar and the searcher burns it all at once in a single transaction. What we can do is attribute the underlying fees by tracing pool-level events back to the originating transaction and then pro-rate the burn bounty based on each builder’s share of fees that entered the TokenJar during the claim period. This is just a structural limitation that we need to work through based on how the burn system is designed. It also increases the need for a program manager because some degree of interpretation/discretion is required. Likely can’t be made autonomous.\n\nJust for more clarity around our thoughts…\n\nSay there are three builders routing swaps through Uniswap on Base over some period:\n\nBuilder A (a FE) generates $800k in fees\n\nBuilder B (an aggregator) generates $150k in fees\n\nBuilder C (a wallet) generates $50k in fees\n\nAll of that $1M flows into the same shared TokenJar. At some point, a searcher decides the pot is worth enough, so they take the fee tokens, and the associated UNI gets bridged back to L1 and burned.\n\nThe TokenJar release is one txn but doesn’t say “800k came from Builder A.”\n\nSo a model for tracing would therefore be going upstream to the pool-level fee events.\n\nEvery swap on Uniswap emits a swap event from the pool contract. That event includes the amounts, the pool address, and the associated txn hash. From the txn hash you can trace back to the originating call as see who called the router, from what contract/EOA, with what calldata.\n\nSo, we’d have to\n\nIndex all Swap events on Base during the claim period that had a protocol fee component\n\nFor each swap txn, check the calldata for a builder identifier (referral tag, contract address, etc)\n\nTally each builder’s share of total fees that flowed into the TokenJar\n\nWhen the searcher burn happens, pro-rate the burned UNI against those shares (this accounting can get tricky due to token $-value fluctuations…see more below)\n\nBut not every builder will have a clean onchain identifier. If Builder C is a wallet that just calls the Uniswap router directly with no tag and no intermediate contract, their swaps look identical to any random user. That’s where the UC’s discretion comes in. We’d require builders to demonstrate attribution. Essentially, to participate in the bounty program, you register your identifier upfront, and only tagged volume counts.\n\nSo the process is:\n\nCollect all the receipts for swaps during a claim period\n\nFilter by builder seeing which receipts have Builder C’s identifier on them\n\nAdd up what % of Builder C’s swaps generated the total fees in the TokenJar\n\nApply that % to the burn so when the searcher burns, Builder A gets credit for X% of it, and their bounty is 2% of that\n\nIdentifying which receipts belong to which builder is the hard part. That’s why pre-registration of an onchain identifier (a contract address, a referral tag in calldata) is a key design requirement.\n\nAnother point worth considering is on the potential hierarchy around the fee tokens themselves. This may be needed to filter garbage volume.\n\nUSDC, ETH, PEPE, and a brand new memecoin all go into the same TokenJar. If the TokenJar is full of worthless tokens, no searcher will touch it, meaning no burn happens, meaning no bounty is paid.\n\nSo if a builder routes a ton of memecoin trading volume, and at the time those swaps happen the memecoin has real value, fees accumulate in the TokenJar and look meaningful. BUT then the coin rugs or goes to 0 before a searcher claims the pot. That’s not a benefit to burn. The builder could argue that they generated a buncha fees during the claim period, but those fees are now worthless so no bounty should be paid.\n\nThe design implication here is that we could explicitly whitelist eligible fee tokens for bounty attribution purposes like ETH, WBTC, USDC, USDT, and some others. Only fees denominated in those tokens count toward a builder’s rebate share. Memecoin fees still flow into the TokenJar and still get burned if a searcher wants them, but they don’t count toward bounty credit/or if they do, they must have >$XM mcap. This makes the bounty program resistant to builders chasing low-quality volume just to inflate their numbers.\n\n1 Like\n\nCuria\n\nMarch 30, 2026, 10:54am\n\n4\n\nThank you for the detailed breakdown of the Season 4 report and the specifics for Season 5. The rebranding to Uniswap Council feels apt, this is clearly an operational body now, and the name should reflect that.\n\nThe Burn Bounty is the standout initiative, it feels like a very thoughtful way to align builder incentives with the protocol’s success. Making burn an explicit KPI rather than a hoped-for downstream effect of generalized grants is a meaningful design improvement, and the deterministic cost-to-value ratio ($200k budget = $10M burned if fully deployed) is a compelling framing.\n\nI think this approach hits the mark for a few reasons:\n\nOn wash trading: @AbdullahUmar’s response is largely convincing, swap fees make it economically irrational to game the rebate, creating a naturally Sybil-resistant structure by design.\n\nScaling potential: I see the 2% rebate as a foundation that we can iterate on. If this goes well, it would be exciting to explore tiered rewards in the future. For instance, offering a 4% rebate for products that cross a major milestone (like $5M in generated burns) could make the program even more compelling for high-impact builders as they grow.\n\nOn Attribution: The more substantive challenge is attribution. @AbdullahUmar’s discussion of requiring builders to pre-register onchain identifiers and the token whitelist concept (crediting only fees from ETH, WBTC, USDC, USDT) are sensible design directions. It would be good to see the UC publish a formal program spec covering attribution rules and eligibility criteria before the program goes live.\n\nOverall, supportive of this renewal and looking forward to seeing these initiative in action.\n\n1 Like\n\nTane\n\nMarch 31, 2026, 12:58am\n\n5\n\nThanks for the detailed proposal. We are supportive of the UC’s renewal and the expanded mandate for Season 5.\n\nThe Burn Bounty design is compelling. Paying only for the end-state outcome rather than proxies eliminates the value leakage that makes traditional grant ROI non-deterministic, and the economics make wash trading irrational. We agree with @SEEDGov and @Curia that a formal program spec covering attribution rules and token eligibility should be published before the program goes live, but the core mechanism is sound.\n\nThe Grant Graduation Pipeline also makes sense. Ensuring that proven Foundation grantees like Anticapture don’t lose funding due to grant expiration is a practical use of UC resources.\n\nOne clarification on treasury management. We understand the UC is seeking a mandate to begin the RFP process, not to deploy capital immediately, which is the right sequencing. Could you confirm whether the final treasury management plan (strategy selection, sizing, risk parameters, manager appointment) will require a separate governance vote before any capital is deployed, or whether the UC considers this proposal sufficient authorization to proceed through to deployment?\n\n1 Like\n\nAbdullahUmar\n\nMarch 31, 2026, 1:59am\n\n6\n\nThanks for your question—this would be Uniswap’s first instance of managing protocol-owned assets, so a series of future votes may be needed from a decision making consensus perspective. Some may just be Snapshot votes due to no associated calldata. Of course, the allocation of funds for specific strategies will require moving UNI from the timelock. Onchain votes may also be needed for signing any formal agreements between vendors and the DUNI. The nature of these votes will be determined as the program unfolds. Needless to say, proper procedure and community input is top of mind. We have to be cognizant of aspects pertaining to legal and tax variables associated with treasury management as well, in particular since the DUNI is now in place.\n\n2 Likes\n\npennblockchain\n\nApril 4, 2026, 8:11pm\n\n7\n\nThanks to the UC team for putting together such a thorough Season 5 proposal. A lot of thought clearly went into it, and we are supportive of the direction. However, a few things are worth talking through before we move to a vote.\n\nBurn Bounty Program\n\nThe incentive logic makes sense in principle; however, additional detail is required before we can offer our full support.\n\nThe delayed compensation piece could quietly disadvantage smaller teams and solo devs who don’t have the runway to wait for burn to materialize. Has the UC looked at what that lag typically looks like in practice, from product launch to meaningful burn accrual?\n\nI’m also worried the 2% rebate creates blind spots. If compensation is directly tied to burn, developers have a real reason to deprioritize infrastructure work and public-good tooling — stuff that creates genuine value but doesn’t sit neatly in the fee path. Is there a carve-out for that kind of contribution, or a parallel track being considered?\n\nA clearer eligibility framework and application process would also go a long way in helping delegates feel confident about the $200k ask. Furthermore, a clearer end-to-end overview of how the program operates would also strengthen voter confidence.\n\nProposal Structure\n\nThe proposal comprises several elements: treasury management, burn bounties, grant graduation, governance logistics, community calls, and deployments. The proposal would land better with a cleaner sense of hierarchy: what’s core to the UC’s mandate versus what’s more exploratory? Even a short executive summary at the top would make a real difference for delegates getting up to speed ahead of the on-chain vote.\n\nTreasury Section\n\nWe’re supportive of getting the RFP process started, but the specific strategy breakdowns (basis funds, statistical arb, options, projected APR targets) may be too ambitious. We suggest trimming this down to the RFP mandate and high-level rationale to reduce back-and-forth over specifics that may change anyway.\n\nLooking forward to the team’s thoughts.\n\n1 Like\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[RFC] Uniswap Grants Program v0.1\n\nRequests for Comment\n\n35\n\n20167\n\nFebruary 9, 2022\n\nUniswap Council (UC): Season 4 Report\n\nGovernance-Meta\n\n0\n\n345\n\nMarch 25, 2026\n\nUniswap Accountability Committee (UAC): Season 3 Report\n\nRequests for Comment\n\n9\n\n1053\n\nMay 6, 2025\n\nUniswap Accountability Committee (UAC): Season 2 Report\n\nRequests for Comment\n\n11\n\n1175\n\nSeptember 23, 2024\n\n[Governance Proposal] Create the Uniswap Foundation\n\nRequests for Comment\n\n0\n\n7548\n\nAugust 17, 2022","tokens":9389,"crawled_at":1791194040378}
+{"id":10329,"url":"https://gov.uniswap.org/t/governance-proposal-complete-initial-funding-of-the-uniswap-foundation/22020","domain":"gov.uniswap.org","chapter":"governance_daos","title":"[Governance Proposal]: Complete initial funding of the Uniswap Foundation - Requests for Comment - Uniswap Governance","text":"[Governance Proposal]: Complete initial funding of the Uniswap Foundation\n\nRequests for Comment\n\ndevinwalsh\n\nOctober 5, 2023, 2:21pm\n\n1\n\nGovernance Vote Updates\n\nVote on the on-chain proposal on Agora, the Uniswap Labs interface, Tally, Boardroom, or any other Uniswap governance interface.\n\nAs discussed below, we are requesting $46.2M of UNI. Using a 30 day TWAP price of UNI of $4.32342, this equates to a request for 10,685,984.71 UNI.\n\nSimulated results of this proposal passing will be available here by navigating to the latest successful Governance Check workflow and downloading the Uniswap artifact at the bottom of the page.\n\nTemperature Check Updates\n\nTemp Check Snapshot here\n\nLast Wednesday we posted in the forum to complete the initial funding of the UF. Since then we’ve been having really great, thorough discussions with delegates – hearing your comments, answering questions, and receiving feedback.\n\nBased on that feedback, we are making a few changes to our proposal. These are covered in the bullets below, and updated throughout our proposal.\n\nWe have adjusted our request to reflect 2 years of operating and grants runway, with the 10% buffer to mitigate price risk. Our request is now $46.2M.\n\nWe break down how this funding will be used in the post below.\n\nWith this runway we anticipate we will return to governance for additional funding when we have approximately 1 year of runway left, in Q4 2024/ Q1 2025.\n\nWe will retain the need to receive governance approval via an off-chain vote for grants larger than $2M.\n\nWe have also heard feedback around the governance process being followed with this proposal. In our initial proposal, we had stated that, after approval, we would move directly to an on-chain vote for our receipt of our second tranche of funding. However, we have heard a desire from the community for the UF to follow the complete governance process here. We are happy to do that, particularly considering these additional changes.\n\nWe will consider last week’s post to be our RFC.\n\nThis post will be our Temperature Check. The Temp Check Snapshot is here.\n\nOnce the Temperature Check has been completed, we will kick off the final governance vote next week.\n\nTL;DR\n\nOur vision is for Uniswap to be the liquidity layer of a self-sovereign Internet, a permissionless alternative to the gated, intermediary-owned exchanges of traditional finance. To get there, the UF is building and supporting a robust ecosystem to grow, improve, and sustain the Uniswap Protocol for the long term.\n\nLast year, Uniswap governance approved the creation and initial funding of the Uniswap Foundation. Today we are requesting the remainder of our initial funding to support our next 2 years of work ($46.2M).\n\nWe hosted a Twitter Spaces to discuss our RFC and answer questions on Monday, October 2 (link here).\n\nIn this post we’re also providing the community with:\n\nA review of the UF’s progress over the last year: the team we have built, the grants we have disbursed and programs we’ve run, and their impact.\n\nA look to the future: what is our vision for the UF, and what is coming next?\n\nWe are kicking off our Temperature Check vote today, and will kick off our on-chain governance vote next week.\n\nUF Vision\n\nUniswap is critical infrastructure for a self-sovereign Internet, providing the liquidity layer for a flourishing world of tokens representing governance participation, community membership, the ability to participate in protocols, “real world” assets and more. It is critical financial infrastructure - providing a permissionless, credibly neutral alternative to the NYSE or SWIFT. It is an enabler of entrepreneurship, providing a liquidity platform for builders creating protocols and applications around the world.\n\nWe founded the Uniswap Foundation because we want to ensure that Uniswap is accessible for anyone in the world to leverage as permissionless financial and technological infrastructure for a long time.\n\nHow do we make that happen? A robust, diverse, and values-aligned ecosystem.\n\nA strong ecosystem is a competitive edge. It expands a Protocol’s accessibility, increases its resiliency, and enables it to thrive in the face of ruthless competitive and market environments. It means more product and engineering talent driving the Protocol forward, into new markets with better user experience. It means values-aligned delegates who are able to thoughtfully weigh the tradeoffs of governance proposals. It means more serendipity, collaboration, and inspiration.\n\nLooking across the crypto landscape it’s easy to see ecosystem strength as a competitive advantage. Ethereum is probably the best example. If Consensys and Ethereum’s earliest contributors were still the only teams building on and for Ethereum, it is easy to see a world where almost none of us would be here. Instead, Ethereum is one of the best places to build blockchain-based protocols and applications.\n\nThe UF is building the Uniswap ecosystem.\n\nHow are we doing that exactly?\n\n1. Growing core Protocol metrics, specifically driving net new order flow to strengthen the Protocol flywheel.\n\nOver the next year, this looks like the development of a robust hooks development platform which broadens the pipeline of developers onto Uniswap and diversifies the kinds of things Uniswap is able to do.\n\nIn the long term, this is 100ks+ of hook and application developers speaking to different use cases (crypto-native to RWA, building new financial primitives) and users globally, all while being able to generate a return for themselves.\n\n2. Building a pipeline for innovation on the Protocol, with the goal of enhancing the experience of swappers and LPs.\n\nOver the next year, this means launching the TL;DR Fellowship and Conference, and creating working groups to apply cutting-edge research across MEV and other relevant areas directly to Uniswap.\n\nIn the long term, this means Uniswap is the default home for the world’s top crypto/DeFi researchers and academics to build POCs and iterate upon mechanisms to improve the experience of key DeFi stakeholders.\n\n3. Aligning incentives for stakeholders with long-term interests of the Protocol, turning Uniswap into a cockroach.\n\nOver the short term, this means two things: the development of realistic mechanisms to effectively capture Protocol value created and distribute it to stakeholders, and bringing stakeholders together to build trust and context IRL.\n\nIn the long term, this means the alignment of long-term interests of core stakeholder teams with the Protocol to weather future volatility and competition.\n\nThis approach will serve to increase Uniswap’s moat over time while ensuring it can adapt as tides change.\n\nBelow, we discuss what we’ve done so far, and how we plan to accomplish our goals in the future. Thank you for your support, as always. We wouldn’t be here without you. We’re grateful to have the opportunity to work with you in the coming years.\n\nUpdate: One Year In\n\nBelow, we provide a summary of what the UF Grants program and our team directly has accomplished over the last year.\n\nGrants\n\nGrowth\n\nLaunch of Oku Trade alongside Oku API: a pro-trader interface accompanied by an API providing comprehensive real-time historical data across pools, swaps, positions, and more. Oku Analytics, which will offer truly-real-time data across all chains it supports, will be launching soon.\n\nSince launching in July, Oku Trade has had 3k unique wallet connections, and 56k unique site visitors.\n\nTwo projects, Unispark and UniChat, have launched on top of the Oku API thus far.\n\nOku also plays a key role in Uniswap Protocol’s multi-chain expansion. By the end of the year they plan to support 10 chains. This includes chains like Boba and Moonbeam which otherwise would not have interface support.\n\nPartnership with Gauntlet: UF’s year-long engagement with Gauntlet is focused on R&D into approaches to optimize incentive programs and fee design. We highlight some of their most interesting work here. They are building a Dynamic Incentive Optimization engine for community use to be released later this year.\n\nHackathon sponsorship: We’ve partnered with ETHGlobal, Binance, and Arrakis to sponsor 3 hackathons (and 1 Hookathon) which have brought 150+ new projects and 200+ new developers into the ecosystem.\n\nLaunch of the Developer Ambassadors Program: Our Ambassadors have started a podcast and deployed UniChat, a tool which leverages the Oku API and OpenAI to allow users to search Uniswap data using plain text.\n\nEnhancements to Uniswap v3 SDK - Koray and Florian are enhancing the SDK for a broader swath of developers and use cases, and making the code for liquidity management easier to use. They are on track to finish their work in November 2023.\n\nSupport for new tools and research for Liquidity Providers, including the development of Chaos Labs Strategy Simulator and the Messari LP Portal, as well as research on Advanced LP Strategies for Uniswap v3 conducted by Atis Elsts and Vasily Tolstikov.\n\nUniswap v3 Development Course: a free, open-source Uniswap v3 Development Course that serves as a fundamental guide for developers, attracting 12,000 monthly visitors..\n\nInnovation\n\nLaunch of TL;DR Research Institute: a first of its kind DeFi-focused Research Institute led by a council of Defi’s leading researchers. The Institute will fund grants to and provide mentorship for fellows studying MEV, mechanism design, ZK, and more, and result in a DeFi Research Conference in the Spring. For its first fellowship, starting in October 2023, TL;DR received 107 applications from around the world.\n\nIndustry-leading research on Cross-chain MEV – which has led in turn to a specification for a Proof of Concept (POC) MEV protection hook\n\nNovel research and implementations across a number of areas, including Lanturn (Measuring Economic Security of Smart Contracts through Adaptive Learning), Chaos Labs TWAP Market Risk application, Axiom’s Checkpoint-free TWAP oracles, and research on Pricing Nontoxic Orderflow.\n\nGovernance & Community\n\nUniswap Agora and the Uniswap Delegate Race - over 65 new delegates made new profiles (to compare, only 35 delegates have posted statement to the governance forum in the last 3 years)\n\nUniswap Cross-chain Bridge Report - A team of 8 produced a comprehensive analysis into the cross-chain requirements for Uniswap’s cross-chain governance use case, and an accompanying assessment of 9 bridges.\n\nUF Team\n\nFirst, we want to provide an overview of our team:\n\nDevin Walsh, Executive Director & UF Co-Founder\n\nKen Ng, Applied Research & UF Co-Founder\n\nElika Mahdavi, COO\n\nRaphaela Sapire, Head of Growth\n\nTyllen Bicakcic, Head of Developer Relations\n\nErin Koen, Head of Governance\n\nFederico Landini, Grants Manager\n\nWe’re also grateful to work with a number of contributors who are making an outsized impact.\n\nBen Basche, Hooks Strategy\n\nBethany Crystal, Grants Strategy\n\nYJ, Grants Committee\n\nLeander Capuozzo, Brand Experience\n\nJuliet Chung, Grants Administration\n\nBelow I want to summarize some of the work our team has done outside of grants:\n\nGrowth & Innovation\n\nInterviews with dozens of builders within the Uniswap ecosystem to develop a strategy to create and support a strong Hooks ecosystem for v4. Thus far we’ve also kicked off and are moderating an active Hook Dojo Telegram chat for 150+ hook developers, have hosted a Hookathon at ETHcc, Tacklebox Talks at ETHNYC, and are building v4 documentation, with the community’s support.\n\nBuilding the TL;DR Research Council, and designing the Fellowship based on their unique insights. Over the coming months, our team will coordinate and run the first TL;DR Conference.\n\nOur team has coordinated and ran multiple hackathons, providing hands-on support to 100s of hackers.\n\nGovernance\n\nOrganizing the Delegate Race with Agora and our first Blessing, a governance-focused event for delegates to build knowledge, context, and community.\n\nAssist in the governance process from writing forum posts, to educating delegates and rallying votes, to writing the code, sometimes debugging the code, and validating the proposal outcome.\n\nIn our original proposal, we requested that Uniswap Governance delegate 2.5M UNI to the UF so that we could re-delegate to community members without enough UNI to submit a governance proposal. Since then we have delegated UNI to several individuals (or used it ourselves) to post the following proposals:\n\nBharat.eth, Fix the Cross Chain Messaging Bridge on Arbitrum\n\n0XPlasma.eth, Deploy Uniswap V3 on BNB Chain\n\nJack Melnick, Deploy Uniswap V3 on Polygon zkEVM\n\nEek637.eth, Create v3deployments.uniswap.eth subdomain and populate its text fields\n\nGFXLabs.eth, Deploy Uniswap V3 on Linea\n\nJesse Sawa, Migrate the Celo Uniswap V3 Factory Contract owner from Optics to Wormhole\n\nRegulatory\n\nThe Uniswap Foundation submitted a comment letter to the SEC’s proposed amendments to Exchange Act 3b-16.\n\nLooking ahead\n\nWe will continue to take a targeted approach to growing the Uniswap ecosystem, investing our capital and resources to fund and support projects and teams who will drive growth and strengthening of the ecosystem.\n\nBelow we cover several initiatives currently in flight, and upcoming over the next few months.\n\nThrough the end of 2023, we plan to:\n\nDevelop the Hooks ecosystem. We’ll award grants to multiple teams to build a v4 SDK, develop hook best practices, educational resources, security standards, and libraries. We will fund high leverage hooks, including MEV mitigation hooks and hooks which increase LP profitability and experience. We’re also looking to accelerate the hook discovery and routing stack; create a hook launch playbook, and more. (Some of these grants may come in 2024). We’re also sponsoring more hackathons with hooks-related educational events for ETH Istanbul/Devconnect.\n\nLaunch the TL;DR Fellowship in October 2023.\n\nContinue IRL Delegate events and build more digital ways to connect. We will host a second Blessing event at ETH Istanbul/Devconnect, and are working towards creating more ways for delegates to connect and educate themselves.\n\nLay the groundwork for some of the big programs we’re excited to launch in 2024.\n\nInto 2024 and beyond, we want to offer insight into how we’re thinking about achieving our big goals.\n\nIn the realm of growth, we’re building an ecosystem of 100ks+ of hook and application developers speaking to different use cases and users globally. This includes:\n\nDriving adoption of v4 as we continue to build the hooks platform. Supporting liquidity migration to v4, the addition of net new liquidity and volume through novel hook development, continuing to fund hook developer content and tooling, and sponsor hookathons.\n\nBroadening our pipeline of contributing teams through partnerships and multi-milestone grants with industry-leading organizations. This might include curriculum development and hackathons to upskill new devs, or web3 onboarding for web2 engineers.\n\nExpanding our grantee support system through more dedicated grantee relationship management and marketing support.\n\nCreating a studio to incubate early founders building novel interfaces and applications.\n\nIn the realm of innovation, we’re building a pipeline for the world’s top crypto/DeFi researchers to build POCs and iterate upon mechanisms to improve the experience of key DeFi stakeholders on Uniswap.\n\nLaunching the TL;DR Conference in Q2 2024 and continuing to support the Institute’s growth.\n\nBuilding working groups of researchers and engineers to ideate upon and build novel POCs to mitigate some of the protocol’s most pressing challenges and expand the protocol surface area, for instance redistribution of MEV profits and on-chain RFQ systems.\n\nIn the realm of governance, we’re working towards an alignment of interests between stakeholders and the Protocol, turning Uniswap into a cockroach.\n\nContinuing to support digital and IRL governance platforms and events to support delegates in building community and context.\n\nSupporting initiatives to create and distribute Protocol value to stakeholders with community-led teams designing and implementing new ways to accrue and capture value for the Protocol, as well as mechanisms for value distribution.\n\nRequest Breakdown\n\nWe are requesting $46.2M in funds today.\n\nThis funding will last provide the UF with 2 years of runway. In total, $28.33M will go towards grants, and $13.6M ($11.4M and 508k UNI) will be spent on operations over this timeframe. We have added a 10% buffer to mitigate price volatility. On the day we post the governance proposal, we will request our funds in UNI, using 30-day-TWAP to convert our request.\n\nFinancials\n\nHistorical\n\nGrants\n\nOver the last year, the UF awarded $4.8M in grants across 5 categories, with the majority of grants being awarded to the Protocol Growth and R&D categories. We awarded our largest grant of $1.6M, to Oku Trade & API, shortly after UF launch. In our most recent quarter, we slowed down grant-making after the Uniswap v4 announcement. We shifted focus from making grants to Uniswap v3-focused projects to building our GTM and funding strategy for v4.\n\nNote that in addition to the $4.8M in grants commitments by the UF, the UF also inherited $886k of active UGP grants, which the UF disbursed over the last year. Total grants commitments including both UF and UGP grants totaled ~$5.7M.\n\n1330×424 48.6 KB\n\n1600×160 57.6 KB\n\nOperations\n\nOver the last year, we spent $3.15M on operations. This is on target with the $3.24M we predicted we would require for our first year of Operations in our initial proposal, with the following caveats:\n\nWe note that the $289K cost of the Uniswap Cross-chain Bridge Assessment Process, the outputs of which were published to the public, was covered by our Ops budget due to the urgent nature of this work in Q1 and Q2 2023.\n\nOur first employees hit their cliffs for UNI vesting in July. We disburse vesting on a quarterly basis, so the first disbursement will occur on October 1st.\n\nOur largest expenses were Payroll and Legal costs. Over the last year our Legal fees included costs to setup and receive our 501(c)(4) status; costs of defense in the Risley class action lawsuit; advisory work for team on how to effectively operate in an unstable regulatory environment; and advisory work to guide the UF’s work in supporting the Uniswap community, for example in our work to provide education and guidance related to the protocol fee switch.\n\n1278×360 63.4 KB\n\nForecast\n\nGrants\n\nWith the addition of funds, the UF will have $30M outstanding in grants capital remaining to disburse.\n\nWe plan to disburse $10-$15M per year, with the amount disbursed per year increasing over time. We note that we are allocating a portion of the Innovation budget (up to $9M) towards designing and testing novel incentive mechanisms. We note this because it’s likely these funds will be disbursed all at once in an MVP of a program.\n\nWe’ve recalibrated our grants categories and allocation budgets to focus on Grantee stakeholder groups.\n\n1286×412 120 KB\n\nProjected Team Growth\n\nOver the next year, we plan to grow our Growth & Research, Grants, and Technology teams in order to realize our goals. Specifically, we plan to:\n\nHire 2 individuals in Growth & Research to support our ongoing efforts, and to grow our expertise in the R&D efforts we are funding.\n\nHire 2 individuals on our Grants Team, including a Grants Lead.\n\nHire 2 individuals on our Technology team, one to support ongoing Product development grants and one to support Developer Relations.\n\nHire an Executive Assistant to support our teams’ internal operations.\n\nIn FY2025, we anticipate hiring up to 2 additional team members.\n\n1038×432 14.3 KB\n\nOperations\n\nFor the next two years, including funds on hand, we will have $13.6M and 961,364 UNI remaining to spend on Ops moving forward ($17.9M total at current UNI prices) through Q4 2025.\n\nBecause we are now planning for the next 2 years, we are adding an additional $1M in buffer to cover unexpected legal costs.\n\n1298×532 163 KB\n\nAdditional Notes\n\nOver the last year, the UF has spent $3.15M on ops and $5.4M in grants. We offer a few comments on these amounts below:\n\nOver the last quarter, we slowed down grant-making activities purposefully in order to build a strategy for grant-making for v4. We expect grants to double or triple to $10-$15M in grants committed per year. Over the next year, our annual operational spend is projected to increase by only ~20%. Over time as we scale we expect the ratio of grants-to-ops spend to continue to increase.\n\nThat being said we also want to note the multitude of activities that our team takes on outside of vanilla grant-making. Many of our team members spend their time incubating and coordinating novel grant-making programs, like the TL;DR Research Institute. And, approximately 50% of our teams’ time over the last year was focused outside of grant-making, including on event/hackathon coordination, hands-on support, marketing & comms, and legal/regulatory work.\n\nThe UF will retain the need to receive governance approval via an off-chain vote for grants larger than $2M. For that vote, we will use the terms set for the Temperature Check – a 5-day Snapshot poll with 10M quorum.\n\nTranche 1 Review\n\nLast year in our Tranche 1 of funding, we requested 2,547,002 UNI with the goal of receiving $20M. However the price of UNI decreased over the 11 days between our request and when it hit our wallet, decreasing the UNI’s value to $17.3M.\n\nWe priced this at the 30-day TWAP of $8.14 on the day we kicked off the governance vote August 17 2022. At this price, 2,547,002 UNI equates to $20M.\n\nWhen we received the funds on August 25, the UNI price had fallen 13.7% to $7.05, meaning that $17.3M worth of UNI hit our multi-sig. We use this number, $17.3M, to calculate the remainder of capital owed to the UF.\n\nTreasury Diversification\n\nOur Treasury Diversification policy is designed to prioritize capital preservation and risk mitigation. We also maintain a portion of our assets in UNI to offer as part of a compensation package to our employees, to align interests with that of the Uniswap ecosystem.\n\nFunds will be split between Operations and Grants. Below we detail our methodology for diversifying our assets within these two categories.\n\nFor Operational funds, we will:\n\nSet aside UNI tokens to be used in employee compensation packages.\n\nMaintain 6 months runway in cash in an FDIC-insured bank account.\n\nInvest the remainder of our funds in a low-risk yield bearing asset.\n\nFor Grants funds, we will:\n\nMaintain a portion of funds in stablecoins.\n\nMaintain 6 months of anticipated grants funding in an FDIC-insured bank account.\n\nInvest the remainder of our funds in a low-risk yield bearing asset.\n\nThis plan aligns our financial strategy with our core objectives, minimizing risk from market volatility to safeguard the foundation’s operations and grant-making commitments.\n\nNext Steps\n\nWe are kicking off our Temperature Check vote today - you can vote here. This vote will last for 5 days. We will kick off our on-chain governance vote next week.\n\nAppendix\n\nTo get a more comprehensive review on our work thus far, take a look at the blog posts we’ve written over the last year:\n\nUF Update to the Community - 7 Months In\n\nStrengthening Uniswap Governance.\n\nTo review the complete list of grants we have disbursed, check out our Wave 1, Wave 2, and Wave 3 write-ups.\n\nThank you to Jesse Walden, Hart Lambur, Alexis Gauba, and Julia Rosenberg for their support as advisors and multi-sig signers over the last year.\n\n15 Likes\n\nStableLab Delegate Platform\n\nScaling V4 and Supporting Unichain\n\nUniswap Foundation: Summary Q3’2024 Financials\n\nUniswap Foundation: Summary Q1’2024 Financials\n\nelisafly\n\nOctober 6, 2023, 1:23pm\n\n2\n\nThank you for the update and clarifying @devinwalsh. Between this post and the Q&A on the last one, we are comfortable supporting this proposal. Avantgarde Finance\n\n4 Likes\n\nDAOstrat.C\n\nOctober 6, 2023, 1:55pm\n\n3\n\nWe have had the privilege of collaborating with the UF over the past year as a delegate, during which the UF established the foundation, supported proposals, created grant initiatives, grew, held events, and more. This proposal demonstrates a forward-looking understanding of the protocol’s trajectory and also aligns with ConsenSys’ core objective of fostering community-driven governance.\n\nThe receptiveness of the Foundation to community feedback is appreciated, especially in revising the funding strategy to enhance accountability with protocol governance and core stakeholders. The current proposal reflects a balanced approach, ensuring resource allocation without undermining the potential to support promising projects. This is among many things that help promote a transparent relationship between stakeholders.\n\nThe role of a foundation can vary based on the protocol, ecosystem, or stakeholders. In our view, the role of the UF is to support protocol governance and foster growth in the ecosystem. This proposal resonates with our broad belief.\n\nWe are optimistic about supporting this initiative through the governance process and fully anticipate positive outcomes for the ecosystem.\n\n7 Likes\n\nKpk Delegate Platform\n\nAbdullahUmar\n\nOctober 6, 2023, 5:27pm\n\n4\n\nWe appreciate the work that @devinwalsh, @eek637, and the rest of the foundation have put into Uniswap’s growth since last August. Every decentralized community needs a steward–and UF has filled that role via grants, events, and governance. The funding ask from last year, according to DAO consensus, seemed reasonable. And now, with the advent of newer and more complex additions to the Uniswap suite via V4 and UniX, we find the funding request to be even more relevant.\n\nTo those ends, we Michigan Blockchain are in support of this proposal.\n\n5 Likes\n\nLeighton\n\nOctober 10, 2023, 1:35am\n\n5\n\nI appreciate the adjustments that have been made to the proposal. I will support this proposal specifically and I also more generally am a big believer in the importance of the Uniswap Foundation.\n\nI think the Uniswap ecosystem benefits from having dedicated stewardship. I see this as very high leverage as the Uniswap Foundation is effectively handling a whole grants system as well. This prevents governance fatigue and mis-management that comes from token holders directly approving grant request.\n\n4 Likes\n\nPorter\n\nOctober 13, 2023, 5:30pm\n\n6\n\nSpecial thanks to @devinwalsh and the terrific team at the Uniswap Foundation for all their work driving the Uniswap ecosystem forward for the last year. We’re excited by the strategic vision they’ve outlined in this proposal. The specificity of the budgeting framework is particularly helpful as the Uniswap Foundation continues to grow and its role evolves. We at a16z crypto fully support their efforts and are appreciative of all they’ve done. As a result, we intend to support this proposal.\n\nThis proposal, in many ways, is an inflection point in the Uniswap Foundation’s journey. It represents a tangible commitment to the decentralized growth of Uniswap’s network, including by bringing the next wave of builders onboard and expanding the community.\n\nGiven the increased size of the Uniswap Foundation’s funding and budget in this proposal, it’s also important to consider the role of balanced oversight functions that foster appropriate systems and processes to protect the Uniswap community, the foundation, and contributors, in an effort to continue to professionalize web3 organizations. Certain of these oversight functions may be in the process of being implemented already, but where there are gaps, inspiration for filling them can come from many well-run and well-funded organizations, from traditional start-ups to NGOs to successful, established businesses.\n\nSo, at the time of this proposal, we want to identify the oversight functions that we believe the Uniswap Foundation can focus on during the period covered by the proposal. The Uniswap Foundation has the opportunity to establish a professional playbook for other web3 foundations to follow. If we can get this set-up right, it can be a model for the industry.\n\nHere’s a few of the ideas that could help shape that model:\n\n(1) Establishing a formal advisory board, or adding additional members to the current board, with traditional and web3 expertise in legal, financial, and technical matters, with an emphasis on experience in organizational governance.\n\n(2) Publishing quarterly progress reports and annual audited financial statements.\n\n(3) Hiring a General Counsel for the Uniswap Foundation and establishment of appropriate legal review processes for grants.\n\n(4) Creating a formalized plan that outlines expectations, KPIs, and removal processes and conditions for UF leadership positions, and the subsequent need for a community vote regarding the remaining funding the UF would hold at the time of a change in UF leadership.\n\n(5) Publishing a succession plan for UF leadership in the event of legal or ethical matters arising, or in the event members of the UF leadership leave prior to the fulfillment of this funding proposal.\n\nThis list isn’t intended to be exhaustive, but represents the main ways the UF can strengthen its organizational design. We look forward to hearing the community and UF’s feedback, and we’re excited for what’s in store ahead!\n\nNone of the above should be taken as investment advice or an advertisement for investment services; Some of the companies mentioned above are portfolio companies of a16z. Please see Disclosures | Andreessen Horowitz for more information.\n\nA list of investments made by a16z is available at a16z Investments Listed From A to Z | a16z\n\n7 Likes\n\n[Governance Proposal] Uniswap Unleashed\n\ndevinwalsh\n\nOctober 13, 2023, 10:09pm\n\n7\n\nHi Porter, we appreciate your support here. We agree that this is an exciting time, for us and Uniswap as a whole, and we’re grateful for the opportunity to support the ecosystem in its next phase of growth.\n\nWe agree with the importance of the UF establishing best practices for community oversight, transparency, and internal governance. Many of the ideas put forth are already on our roadmap to achieve over the next year, including establishing a formal advisory board, adding to the UF Board, and providing more regular financial updates to the community.\n\nWe are directionally aligned with the additional items on your list and are excited to design operational processes and controls to professionalize the UF and set best practice for other Foundations in the space. We are committed towards taking these steps, without adding unreasonable operational or administrative burden to the UF, over the next year and in alignment with the aforementioned goals.\n\nilia_0x\n\nOctober 16, 2023, 6:53am\n\n8\n\nHello @Porter,\n\nFirstly, let me express my gratitude for the comprehensive feedback you’ve provided on the Uniswap Foundation’s proposal. As an active member of the Uniswap governance community, I am heartened to see esteemed organizations like a16z crypto take an active interest in ensuring the protocol’s growth and governance structures evolve appropriately.\n\nYour points underline the critical juncture we’re at as an ecosystem. As the Uniswap Foundation grows in its scale and importance, transparency and robust oversight become paramount.\n\nDrawing from your insights and my personal experience participating in governance, I’d like to add and echo a few points:\n\n1.1) The Grant Transparency Initiative seems like a pivotal step forward. As someone who deeply cares about the ecosystem’s growth, being able to trace the decision-making process behind each grant would be invaluable. It would help instill greater trust within the community and ensure that the protocol remains true to its ethos.\n\n1.2) I fully endorse the idea of hosting regular Grant Discussion Forums. This kind of direct engagement would foster a sense of ownership and inclusivity among community members, ensuring that many voices get a say in the protocol’s direction.\n\n1.3) Establishing a Grant Oversight Committee resonates with the community’s call for increased transparency. Such a body, particularly with representation from community-elected members, would bring about checks and balances that are crucial for such a significant budget allocation.\n\n2) Marketing and Communication: In the ever-evolving and fiercely competitive landscape of DEX platforms, standing out and communicating our value proposition is imperative. I echo the sentiment that a collaborative effort with the Uniswap Foundation to prioritize and strengthen marketing and communication is essential. Ensuring that our community outreach and governance proposals highlight this can be pivotal in retaining our position and expanding our user base.\n\n3) Proposals Execution: While conceptualizing and voting on proposals is a significant part of our governance process, equal emphasis should be on the execution phase. I’d love for both the Uniswap Foundation and the broader community to focus more on the successful execution of win proposals. Perhaps introducing a consul program or some other structured support system would ensure these winning ideas genuinely come to fruition, benefiting the ecosystem.\n\nYour suggestions about professionalizing governance, from the introduction of advisory boards to succession planning, are essential steps to ensure the foundation remains forward-thinking and agile. I’m eager to see how the UF and the broader community react to and potentially implement these ideas.\n\nI must also take a moment to commend the Uniswap Foundation and personally to @devinwalsh for the incredible work done so far. The collaboration on the BNBchain proposal stands out as a testament to what we can achieve together. Your dedication and results-oriented approach have been instrumental in bringing about meaningful change and advancement for the Uniswap ecosystem.\n\nWarm regards,\n\nilia.eth\n\n3 Likes\n\nkfx\n\nOctober 16, 2023, 8:18am\n\n9\n\nThank you for the post. Your have expressed, more eloquently than I could, ideas similar to what I suggested here:\n\nhttps://gov.uniswap.org/t/rfc-complete-initial-funding-of-the-uniswap-foundation/21956/8?u=kfx\n\nI fully agree that the Uniswap Foundation should aspire to be a model for the industry. This goal should be kept in mind when considering day-to-day operations.\n\n1 Like\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[RFC]: Complete initial funding of the Uniswap Foundation\n\nRequests for Comment\n\n15\n\n7771\n\nOctober 7, 2023\n\n[Temperature Check] Create the Uniswap Foundation\n\nTemperature Check\n\n59\n\n25158\n\nSeptember 9, 2022\n\n[Governance Proposal] Create the Uniswap Foundation\n\nRequests for Comment\n\n0\n\n7548\n\nAugust 17, 2022\n\n[Consensus Check] Create the Uniswap Foundation\n\nConsensus Check\n\n0\n\n5439\n\nAugust 10, 2022\n\n[Governance Proposal] Uniswap Unleashed\n\nRequests for Comment\n\n46\n\n7873\n\nMarch 17, 2025","tokens":8739,"crawled_at":1791194060280}
+{"id":10330,"url":"https://a16zcrypto.com/team/jens-ernstberger","domain":"a16zcrypto.com","chapter":"research","title":"Jens Ernstberger - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nJens Ernstberger\n\nFeed\nFilter\n(1)\nclear filters\n\ncategory\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\nrecommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nauthor\n(1) all authors\n@x0rart\n1337 Skulls Sers\na16z crypto\na16z crypto editorial\na16z crypto policy & regulatory teams\na16z crypto Regulatory Team\nAaditya Shidham\nAaron Levie\nAaron Phillips\nAaron Schnider\nAbby Green\nAbdou Ndiaye\nAbhi Shelat\nAbhiram Kothapalli\nAbigail Johnson\nAdam Alter\nAdam Back\nAdam Bry\nAdam Grant\nAdam Ludwin\nAdam Martin\nAdam Thierer\nAdam Zuckerman\nAdela Tomsejova\nAdena Friedman\nAdena Hefets\nAdeniyi Abiodun\nAdina Fischer\nAdrian Cockcroft\nAdrian Fenty\nAdrienne Mayor\nAgostino Capponi\nAiden Slavin\nAileen Lee\nAisha Stephenson\nAJ Shankar\nAlan Knott-Craig\nAlan Schaaf\nAlana Benton\nAlbert Tang\nAlec Nielsen\nAlec Ross\nAlejandro Flores\nAlex Constantinople\nAlex Honnold\nAlex Hutchinson\nAlex Immerman\nAlex Kreitz\nAlex Kroeger\nAlex Le\nAlex Masmej\nAlex Morcos\nAlex Price\nAlex Pruden\nAlex Rampell\nAlex Roetter\nAlex Solomon\nAlex Spector\nAlex Stamos\nAlex Tabarrok\nAlexander (Sasha) Spiegelman\nAlexander Chia\nAlexander Zoppa\nAlexandra Chang\nAlexandria Lafci\nAlexis Lakes\nAlexis Madrigal\nAlexis Ohanian\nAli Ghodsi\nAli Yahya\nAlicia Barone\nAlin Tomescu\nAlisha Litman\nAlison Mangiero\nAlison Martin\nAllison Pickens\nAlyssa Del Bene\nAlyssa Torres\nAmanda Cantor\nAmanda Cassatt\nAmanda Catherine\nAmanda Mulay\nAmanda Tuminelli\nAmanda Tyler\nAmelia Salyers\nAmie Tyrrel\nAmir Shevat\nAmira Yahyaoui\nAmy Abernethy\nAmy Berliner\nAmy Bohutinsky\nAmy Choice\nAmy Cray\nAmy Gill\nAmy Hoemeke\nAmy Kalokerinos\nAmy Robertson\nAna Mostarac\nAna Susi\nAnatoly Yakovenko\nAndie Taylor\nAndisheh Tahriri\nAndre Iguodala\nAndrea Clarke Hall\nAndrea Feinberg\nAndrea Rallo\nAndrea Simon\nAndrea Vinkler\nAndreas Papadimitropoulos, Jr\nAndreessen Horowitz\nAndrew Allen\nAndrew Chen\nAndrew F. Read\nAndrew Green\nAndrew Hall\nAndrew Lakis\nAndrew Lewis-Pye\nAndrew Lo\nAndrew Mason\nAndrew McAfee\nAndrew Milson\nAndrew Omori\nAndrew Radin\nAndrew Rubin\nAndrew Savage\nAndrew Smith\nAndrew Tretyakov\nAndy Beal\nAndy Coravos\nAndy Golden\nAndy Hill\nAndy Milenius\nAndy Rachleff\nAndy Tran\nAndy Walshe\nAneel Lakhani\nAngela Schenone\nAngela Strange\nAngela Tran Kingyens\nAngelica Gehr\nAniket Kate\nAnil Sethi\nAnish Acharya\nAnn Winblad\nAnna Berces\nAnna Jablonski\nAnna Semenova\nAnna Van Meurs\nAnnaLee Saxenian\nAnne Brandes\nAnne Lee Skates\nAnne Lewandowski\nAnne Mitchell\nAnne Yip\nAnnie Collins\nAnnie Duke\nAnthony Albanese\nAnthony Atala\nAnthony Foxx\nAnthony Lee Zhang\nAntonio Viggiano\nAntwone Stigall\nAnu Hariharan\nApril Roth\nAri Emanuel\nAri Juels\nArianna Huffington\nArianna Simpson\nArik Kershenbaum\nArmon Dadgar\nArnie Goldberg\nArsho Avetian\nArthur Brooks\nArun Sundararajan\nAsh Ashutosh\nAsha Christian\nAshley McCollum\nAshley Stern\nAshton Carter\nAtif Mian\nAtul Butte\nAubree Pelaez\nAubrey de Grey\nAugusto Marietti\nAurora Petracca\nAusten Allred\nAustin Guzman\nAustin Marchese\nAustin Wilson\nAva Iravani\nAvery Segal\nAvinash Solanky\nAviv Zohar\nAye Moah\nAzeem Azhar\nBailey Flanigan\nBailey Richardson\nBalaji Srinivasan\nBarry McCarthy\nBart Dessaint\nBeau Cronin\nBeau Woods\nBecky Pferdehirt\nBen Buckwalter\nBen Fielding\nBen Fisch\nBen Gardner\nBen Gomez\nBen Horowitz\nBen Kaufman\nBen Leventhal\nBen Lovell\nBen Napier\nBen Portney\nBen Rubin\nBen Scharfstein\nBen Schecter\nBen Silbermann\nBen Uretsky\nBen Wu\nBenedict Evans\nBenedikt Büenz\nBenjamin Ebner\nBenjamin Hindman\nBenjamin Wittes\nBenjamin Wu\nBennett Carroccio\nBenny Pinkas\nBernard J. Tyson\nBernard Tyson\nBeth Newman\nBethany Coates\nBharat Ramamurti\nBharath Ramsundar\nBill Carr\nBill Frist\nBill Hinman\nBill Janeway\nBill Krause\nBill Macaitis\nBlake Kim\nBlake Masters\nBlake Saari\nBlayne Donnell\nBob Iger\nBob Langer\nBob Moore\nBob Muglia\nBob Sutton\nBob Swan\nBob Tinker\nBob Wachter\nBobby Franklin\nBobby Green\nBobby Kotick\nBobby Wagner\nBoris Sofman\nBoris Wertz\nBrad Feld\nBrad Kern\nBrad Peterson\nBram Cohen\nBrandon Ballinger\nBrandon Barros\nBrandon Cherry\nBrandon Millman\nBrenda Kopf\nBrent McIntosh\nBrett Browman\nBrett Falk\nBrett Hagler\nBrewster Kahle\nBrian Armstrong\nBrian Balfour\nBrian Brooks\nBrian Crnkovich\nBrian Curran\nBrian Grazer\nBrian Koppelman\nBrian McCullough\nBrian Quintenz\nBrian Wilkins\nBridget McDowell\nBrittany Lucas\nBrittney Burrows\nBrooke Sheresky\nBruce Friedrich\nBryan Caplan\nBryan Chiang\nBryan Cox\nBryan Crowley\nBryan Faust\nBryan Houser\nBryan Kim\nBryan Pellegrino\nCaitlin Glazebrook\nCaitlin Johnston\nCaitlin Roberson\nCal Turner Jr.\nCaleb Christian\nCameron Schuler\nCamila De Souza\nCarine Carmy\nCarissa Bilinski\nCarl Agnelli\nCarl Eschenbach\nCarl Narcisse\nCarl Pope\nCarlos Araya\nCarolina Gonzalez\nCaroline Friedman\nCaroline Goggins\nCaroline Horn\nCaroline Moon\nCarolyn Bertozzi\nCarra Wu\nCasey Graul\nCasey Neistat\nCasey Winters\nCassady Churchill\nCassie Faerber\nCecilia Marshall\nCeia Font\nChad Rigetti\nChandra Krintz\nCharles Goetz\nCharles Hubbard\nCharles Koch\nCharlie Keinath\nCharlie Warzel\nChattry Meas\nChelsea Komlo\nChelsea Padilla\nCheng Li\nChris Bennett\nChris Best\nChris Burniske\nChris Curran\nChris DeWolfe\nChris Dixon\nChris Granger\nChris Hauth\nChris Lyons\nChris Messina\nChris Milk\nChris Power\nChris Santa Maria\nChris Wanstrath\nChristian Cachin\nChristian Catalini\nChristian Crowley\nChristian Seifert\nChristina Hampp\nChristina Lopes\nChristina Mercando\nChristina Xu\nChristina Zeidan\nChristine Darden\nChristine Perham\nChristopher Giancarlo\nChristopher Lee\nChristopher Mims\nChristopher Nguyen\nChristopher Rippingham\nChristopher Schroeder\nChristy Hubbard\nCiamac Moallemi\nCindi Zhang\nCindy Tenner\nClaire Austin\nClaire Cain Miller\nClaire Kart\nClaudia Picanco\nClay Shirky\nClayton Christensen\nClayton Gardner\nClifford Woolf\nClint Delapaz\nColin Bryar\nColin Rom\nCollin McCune\nConner Lyons Brown\nConnie Chan\nConnie Guglielmo\nConnor McCarthy\nConnor Moyles\nCorban Bell\nCorey Hawkins\nCorey Waller\nCourtney Dettlinger\nCraig Naylor\nCraig Walker\nCristina Cordova\nCurt Funderburk\nCuy Sheffield\nD'Arcy Coolican\nDaejun Park\nDaisy Linden\nDaisy Wolf\nDaljeet Virdi\nDalton Turay\nDan Berkenstock\nDan Boneh\nDan Frommer\nDan Primack\nDan Romero\nDan Shapero\nDan Siroker\nDan Stein\nDan Warmenhoven\nDan Wendlandt\nDaniel Chao\nDaniel Chen\nDanielle Andrzejewski\nDanielle Clark\nDanielle Looymans\nDanielle Lussier\nDanielle Morrill\nDanielle Shea\nDanny Shader\nDaphne Koller\nDapper Dan\nDaren Matsuoka\nDarin Malter\nDarshan Shankar\nDas Rush\nDave Jagoda\nDave King\nDave Touretzky\nDavid Banks\nDavid Belden\nDavid Damato\nDavid Deming\nDavid George\nDavid Haber\nDavid Hollestelle\nDavid Kerr\nDavid Lee\nDavid Mack\nDavid Madden\nDavid Marcus\nDavid Olson\nDavid Oyelowo\nDavid Pierce\nDavid Reich\nDavid Rumsey\nDavid Schweikert\nDavid Sinclair\nDavid Sverdlov\nDavid Tse\nDavid Ulevitch\nDavid Weiden\nDawn Lepore\nDawn Nott\nDeborah Embaie\nDeena Elitreby\nDeepak Maram\nDenis Nazarov\nDenis Young\nDenise Gonzalez\nDerek Dolin\nDerek Thompson\nDerrick Harris\nDevin Finzer\nDevon Zuegel\nDiana Peña\nDiane Greene\nDick Costolo\nDieter Shirley\nDiishan Imira\nDiogo Monica\nDominic Shine\nDominique Reliford\nDon Duet\nDon Faul\nDorris O'Brien\nDoug Ducey\nDoug Folden\nDoug McCracken\nDouglas Argueta\nDozie Uche\nDrew Coffman\nDylan Field\nDylan Rhodes\nEd Felten\nEd Lynch\nEddie Lim\nEddy Lazzarin\nEdith Zimmerman\nEdward Perkins\nEdwin Poston\nEfrat Noy\nEhud Shapiro\nEileen Burbidge\nEileen Wu\nElad Gil\nElaine Fuchs\nElaine Shi\nElena Burger\nEli Dourado\nElisa Leonhardt\nEliza Oak\nElizabeth Gunn\nElizabeth Harkavy\nElizabeth May\nElizabeth Ocken\nElizabeth Stark\nElizabeth Weil\nEllen Tunoa\nEmile Petrone\nEmilio Torres\nEmily Graff\nEmily Hinsch\nEmily Keir\nEmily Oster\nEmily Westerhold\nEmma Janaskie\nEric Budish\nEric Dai\nEric Ries\nEric Thomas\nEric Topol\nEric Wu\nErica Schecter\nErik Brynjolfsson\nErik Kiser\nErik Torenberg\nErika Bracken\nErika Herrera\nErika Louie\nErin Grody Kingsley\nErin Murphy\nErin Tice\nErin Tonnar\nErin Winkler\nErtem Nusret Tas\nEsther Shinn\nEthan Bueno de Mesquita\nEthan Ferreira\nEthan Zuckerman\nEuan Ashley\nEugene Volokh\nEugene Wei\nEugenia Yee\nEula Takahashi\nEva Sakkas\nEvan Burfield\nEvan Osnos\nEvangelos Simoudis\nEzra Klein\nF. Gary Gray\nFabiola Godinez\nFabrizio Zilibotti\nFahad Saleh\nFarid Jiandani\nFei-Fei Li\nFelix Do\nFEWOCIOUS\nFiona Kennedy\nFiona Murray\nFlashrekt\nFlora Oliveira\nFlori Del Valle\nFlorian Leibert\nFoteini Baldimtsi\nFrancesca Gino\nFrank Chen\nFrank Wilczek\nFred Benenson\nFred Ehrsam\nFred Upton\nFred Wilson\nFreda Lewis-Hall\nFrederic Kerrest\nFuture Editorial\nGabby Dizon\nGabby Reece\nGabriel Otte\nGabriel Vasquez\nGaetan Barthelemy\nGarrett Biel\nGary Ang\nGary Reedy\nGary Wolf\nGaurav Banga\nGaurav Dhillon\nGaut\nGayle Tzemach Lemmon\nGeoffrey Woo\nGeorg Fuchsbauer\nGeorg Petschnigg\nGeorge Church\nGeorge Danezis\nGeorge Fraser\nGeraldine Chan\nGérard Cachon\nGerard Ryle\nGerri Elliott\nGerry Tsoukalas\nGia Scinto\nGil Elbaz\nGil Shafir\nGina Moon\nGina Neff\nGina Yocom\nGinger Liau\nGokul Rajaram\nGoldie Chang\nGrace Ellis\nGraham Allison\nGrant Gregory\nGrant Jordan\nGrant LaFontaine\nGrant Rabenn\nGray Kinsella\nGreg Bowman\nGreg Clayman\nGreg Linares\nGreg Loehmann\nGreg Lynn\nGreg Solano\nGreg Truesdell\nGreg Waldon\nGregory Allen\nGregory Mundis\nGretchen Bush\nGretchen McCulloch\nGuido Appenzeller\nGustav Söderström\nGustavo Garcia\nGuy Goren\nGuy Raz\nGuy Wuollet\nHaley Van Dyck\nHanna Aziz\nHannah Frankl\nHanne Winarsky\nHaoyuan Li\nHarmit Malik\nHarry Grieve\nHarry Shum\nHarry Wright\nHatim Shafique\nHayden Adams\nHeather Gwynn\nHeather Podesta\nHedi Samar\nHelen Stoddard\nHelen Su\nHemant Mohapatra\nHendrik Pretorius\nHenri Kor\nHerb Lin\nHerman Narula\nHilmar Pétursson\nHoang Nguyen\nHoward Wu\nIan Dutra\nIan Shannon\nIan Sharp\nIce Cube\nIlan Zechory\nIllia Polosukhin\nIlyas Khan\nIma Christian\nIman Abuzeid\nInsiya Lokhandwala\nIon Stoica\nIrvin Chan\nIsa Guardalabene\nIsaiah Lott\nIsh Verduzco\nIsil Dillig\nIstván András Seres\nIttai Abraham\nIttay Eyal\nIva Messy\nIvan Linscott\nIvor Horn\nJ.D. Moriarty\nJack Donahoe\nJack Soslow\nJackie McQuiston\nJackson David\nJacob Westphal\nJacquelyn Melinek\nJad Esber\nJad Naous\nJade Lai\nJade Raymond\nJae Gnazzo\nJai Ramaswamy\nJaimie Buss\nJak Kennedy\nJake Auchincloss\nJakob Uszkoreit\nJamal Mohammed\nJames Beshara\nJames Currier\nJames da Costa\nJames Gwertzman\nJames J. Collins\nJames Kissell\nJames L. Madara\nJames Loftus\nJames Rathmell\nJames Rogers\nJames Watters\nJames Wu\nJames Zou\nJamie Brandon\nJamie McGurk\nJamie Sullivan\nJamilla Hemeid\nJana Odehnal\nJane Doe\nJane Lippencott\nJane Suh\nJanelle De Los Santos\nJared Bricklin\nJared Furutani\nJared Georgakopoulos\nJared Polis\nJared Smith\nJase Wilson\nJason Franklin\nJason Liu\nJason Mayden\nJason Milionis\nJason Mitchell\nJason Mok\nJason Rosenthal\nJason Warner\nJason Yanowitz\nJay Bradner\nJay Conte\nJay Drain\nJay Komarneni\nJay Rughani\nJean Reilly\nJeanne Tsan\nJeff Amico\nJeff Benson\nJeff Clark\nJeff Cordova\nJeff Glueck\nJeff Hawkins\nJeff Jones\nJeff Jordan\nJeff Lawson\nJeff Lu\nJeff Nagashima\nJeff Stump\nJeff Weiner\nJeffrey Immelt\nJeffrey Kaditz\nJeffrey Katzenberg\nJeffrey Kindler\nJeffrey Low\nJeffrey Silverstein\nJeffrey Zirlin\nJen Bulawsky\nJen Kha\nJenna Walsh\nJenna Zucker\nJennifer 8. Lee\nJennifer Doudna\nJennifer Kodner\nJennifer Konde\nJennifer Li\nJennifer Mumford\nJennifer Tejada\nJennifer Young\nJenny Cieplak\nJens Ernstberger\nJensen Harris\nJeremy Clark\nJeremy England\nJeremy Zhang\nJesse Holmes\nJesse Pollak\nJesse Walden\nJessica Childs\nJessica Hansen\nJessica Keeler\nJessica Patton\nJessica Verrilli\nJewel Pi\nJez Humble\nJi Kim\nJianying Luo\nJim Gilliam\nJimmy Chen\nJimmy Soni\nJing Wang\nJing Zou\nJJ Yu\nJoachim Neu\nJodi Lynn\nJodie Lutkenhaus\nJoe Gebbia\nJoe Grundfest\nJoe Montana\nJoe Morrissey\nJoe Schmidt\nJoe Sullivan\nJoel de la Garza\nJoel Mokyr\nJoel Monegro\nJoel Spolsky\nJoey Burleson\nJohn China\nJohn Collison\nJohn Fawcett\nJohn Garcia\nJohn Gedmark\nJohn Hennessy\nJohn Koelliker\nJohn M. Jack\nJohn Markoff\nJohn Menna\nJohn O’Farrell\nJohn Riccitiello\nJohn Smesko\nJohn Stanfield\nJohn Thompson\nJohn William Hatfield\nJonah Peretti\nJonathan Bush\nJonathan Dotan\nJonathan Downey\nJonathan Lai\nJonathan Lim\nJonathan Lusthaus\nJonathan Weissman\nJonathan Wong\nJordan Mazer\nJordan Stankowski\nJorge Conde\nJorge Gomez\nJose Guardado\nJoseph Bonneau\nJoseph Okpaku\nJoseph Spisak\nJosh Arnold\nJosh Bloom\nJosh Kim\nJosh Williams\nJoshua Browder\nJoshua Gans\nJoshua Grimm\nJoshua Hix\nJoshua Levin\nJoshua Lu\nJoshua Schank\nJoshua Soto\nJosie Ma\nJoyce Park\nJR Rivers\nJT Evans\nJuan Benet\nJudene Small\nJudy Savitskaya\nJudy Smith\nJulia Grace\nJulia Kirby\nJulie Bornstein\nJulie Farnham\nJulie Johnson\nJulie Samuels\nJulie Yoo\nJuliet Grier\nJuliet Nyatta\nJuliette Morton\nJulius Zhang\nJustin Bailey\nJustin Bethune\nJustin Blau\nJustin Cunningham\nJustin Gregorius\nJustin Kahl\nJustin Kan\nJustin Larkin\nJustin Paine\nJustin Pettit\nJustin Roberts\nJustin Simcock\nJustin Thaler\nJustine Moore\nJutta Steiner\nJyoti Bansal\nJZ Young\nKabir Gill\nKabir Laroia\nKais Khimji\nKamala Harris\nKaren Dunn\nKaren Wooley\nKarina Sobieski\nKarl Floersch\nkarma (Daniel Reynaud)\nKarmacoma\nKarthik Rau\nKartik Nayak\nKate Darling\nKate Dellolio\nKate Kerames\nKatherine Boyle\nKatherine Minarik\nKatherine Rundell\nKatherine Schoebel\nKathryn McKinley\nKathy Liu\nKathy Yang\nKatia Ameri\nKatie Baynes\nKatie Haun\nKatie Hemmerling\nKaty DeWitt-Drew\nKaty Nelson\nKayvon Tehranian\nKeener Barnhorst\nKeller Medlin\nKeller Rinaudo\nKelly Cannon\nKelsey Chaplinsky\nKelsey Mellard\nKen Chong\nKen Coleman\nKen Kocienda\nKerry Ganim\nKesha Cash\nKevin Chou\nKevin Chu\nKevin Dulsky\nKevin Kelly\nKevin McKinley\nKevin Nishioka\nKevin O'Kane\nKevin Rose\nKevin Tan\nKevin Wu\nKevin Zollman\nKidSuper\nKieran Snyder\nKierston Gittens\nKiki Mavridis\nKim Enright\nKim Malone Scott\nKim Milosevich\nKim Stevenson\nKim Zetter\nKimberly Tan\nKindra Mason\nKira Poskanzer\nKira Song\nKirstin Arbide\nKirt McMaster\nKofi Ampadu\nKouki Harasaki\nKrista Anderson-Copperman\nKristen Fortney\nKristen Johansson\nKristen Kee\nKristin Sauchak\nKristin Thayer\nKristina Graci-deLuna\nKristina Shen\nKristine Lipscomb\nKristo Käärmann\nKrisztina Holly\nKunal Bahl\nKunle Olukotun\nKurt House\nKyle Russell\nLaird Hamilton\nLatasha\nLaura Arrillaga-Andreessen\nLaura Baller\nLaura Behrens Wu\nLaura Deming\nLaura Gravley\nLaura Johnson\nLaura Shores\nLaura Weidman Powers\nLauren Berson\nLauren Illovsky\nLauren Murrow\nLauren Richardson\nLauren Spragge\nLaurene Powell Jobs\nLawrence Levy\nLawrence Summers\nLeah Cassidy\nLee Kleinman\nLee Lefkowitz\nLeeAnn Caballero\nLeila Hay\nLeila Janah\nLenny Rachitsky\nLeslie Jaw\nLeslie Vosshall\nLester Chen\nLi Fan\nLi Fei-Fei\nLi Jin\nLiang Wu\nLilian King\nLily Liu\nLina Sergie Attar\nLinda Banuelos\nLinda Xie\nLinden Tibbets\nLing Ren\nLinlin Li\nLinxin Wen\nLioba Heimbach\nLisa Hawke\nLisa Lambert\nLisa Orr\nLisa Reilly\nLisa Rosano\nLizzy Anderson\nLJ Erwin\nLloyd Dean\nLoretta Sanchez\nLori Potter\nLuca Prosperi\nLuca Zanolini\nLuis Martinez\nLuis von Ahn\nLuke Wroblewski\nLydia Green\nLynda Gibson\nLynn Rudolph\nMadan Nagaldinne\nMaddison Masaeli\nMadeline Lancaster\nMaggie Hsu\nMaggie Leung\nMaggie Romero\nMahad Abedin\nMahesh Iyer\nMahesh Vellanki\nMahimna Kelkar\nMakiri Duckett\nMalinka Walaliyadde\nMallesh M. Pai\nMalloy Evans\nManas Punhani\nManny Luna\nMarc Andreessen\nMarc Andrusko\nMarc Benioff\nMarc Levinson\nMarci Barbera\nMarco Reuter\nMargaret Jen\nMargit Wennmachers\nMaria LaMagna Morales\nMarian Garvin\nMarianne Winkler\nMariano Sorgente\nMaricarmen Alvarez\nMariel Goldenstein\nMarigold Vu\nMarina Kusserow\nMario Gabriele\nMario Linares\nMarissa Bramlett\nMark Cranney\nMark Leslie\nMark McAndrew\nMark McClusky\nMárk Melczer\nMark Moore\nMark Regan\nMark Sendak\nMarkos Georghiades\nMarkus Covert\nMarkus Funk\nMartha Lane Fox\nMartin Casado\nMartin Fischer\nMarty Makary\nMarvin Ammori\nMarvin Zamora\nMary Pat Jordan\nMary-Catherine Lader\nMaryam Bahrani\nMason Hall\nMatei Zaharia\nMatt Abrahams\nMatt Billmann\nMatt Bornstein\nMatt Clifford\nMatt Flannery\nMatt Fleming\nMatt Gleason\nMatt Kaeberlein\nMatt Levine\nMatt Levy\nMatt Oberhardt\nMatt Shortal\nMatt Spence\nMatt Weinberg\nMatthew Colford\nMatthew Green\nMatthew Haughey\nMatthew McCullough\nMatthew Mills\nMatthew Olsen\nMatthew Rutter\nMatthew Stein\nMatthieu Hafemeister\nMaureen Lara\nMax Kesten\nMax Krohn\nMax Levchin\nMax Polyak\nMax Resnick\nMax Ventilla\nMaya Rahkonen\nMcPherson Moore\nMeaghan Hardy\nMeg Whitman\nMegan Holston-Alexander\nMegan Kristalyn\nMehdi Hasan\nMehul Mehta\nMel Williams\nMelanie Galang\nMelissa Liao\nMelissa Minor\nMelissa Wasser\nMellody Hobson\nMelody Latronico\nMeredith Donahue\nMia Gonzalez\nMia Mandich\nMicah Johnson\nMichael Beckerman\nMichael Blau\nMichael Brandt\nMichael Chan\nMichael Copeland\nMichael Dearing\nMichael Dell\nMichael Franklin\nMichael Garcia\nMichael J. Casey\nMichael J. Freedman\nMichael Killam\nMichael King\nMichael Lee\nMichael Leiter\nMichael Morell\nMichael Ostrovsky\nMichael Ovitz\nMichael Paulus\nMichael Raynor\nMichael Reed\nMichael Snyder\nMichael Temkin\nMichael Wee\nMichael Zhu\nMichel Del Buono\nMichel Feaster\nMichèle Flournoy\nMichele Griffin\nMichele Korver\nMichele Law\nMichelle Ervin\nMichelle Kelso\nMichelle Kung\nMichelle Mundy\nMichelle Shin\nMichelle Ufford\nMichelle Volz\nMichelle Wilson\nMichelle Winn\nMichelle You\nMike Curtis\nMike Haydon\nMike Hearn\nMike Jones\nMike Kasperzak\nMike Kelly\nMike King\nMike Lempres\nMike Manning\nMike Maples jr\nMike Masnick\nMike Matchett\nMike Paulus\nMike Sandwick\nMikeal Rogers\nMikey Dickerson\nMiles Jennings\nMilijana Curic\nMiller Whitehouse-Levine\nMinerva Munoz\nMinnie Ingersoll\nMinsun Pak\nMintu Turakhia\nMiranda Christ\nMo Shaikh\nMohammad Akbarpour\nMohsen Malayeri\nMolly Grace\nMonique McCambridge\nMorgan Beller\nMorgan Bender\nMurat Pak\nMuriel Bowser\nMurray Shanahan\nMy Pham\nNadia Asparouhova\nNadia Eghbal\nNaftali Harris\nNaithan Jones\nNanjira Sambuli\nNaomi Metzger\nNashid Braswell\nNassim Eddequiouaq\nNat Barling\nNatacha Crooks\nNatalia Carrera\nNatalie Bucher\nNatalie Taumoepeau\nNate Chang\nNate Lau\nNathalie Balaban\nNathan McCauley\nNathan Yoon\nNathaniel Gleicher\nNathaniel Popper\nNav Singh\nNazanin Daneshvar\nNeel Maitra\nNeha Narula\nNelson Perla-Ward\nNeveen Bader\nNicholas Christakis\nNicholas Pacilio\nNick Babaian\nNick McKeown\nNick Quah\nNick Tomaino\nNicki Locker\nNicole Conner\nNicole Forsgren\nNicole Irvin\nNicole Neuman\nNicole Stanners\nNiels Provos\nNigel Robinson\nNikhil Krishnan\nNina Suthers\nNir Eyal\nNitasha Tiku\nNitin Natarajan\nNitya Subramanian\nNkiru Balonwu\nNoah Citron\nNoah Feldman\nNoah Levine\nNoah Smith\nNoam Nisan\nNoemi Glaeser\nO’Shea Jackson Jr.\nOlaf Carlson-Wee\nOleg Rogynskyy\nOliver Hsu\nOlivia Moore\nOlivia Webb\nOmri Weinstein\nOoshma Garg\nOprah Winfrey\nOrion Hindawi\nOscar Menjivar\nP.J. Hasleton\nPablo Montagnes\nPacky McCormick\nPak\nPalmer Luckey\nPamela Anderson\nPamon Forouhar\nParag Khanna\nParijat Talkad\nParker Brown\nParker Conrad\nPatrice Peck\nPatrick Byrne\nPatrick Collison\nPatrick Conway\nPatrick McCorry\nPatrick McHenry\nPatrick O’Grady\nPatrick Rivera\nPatrick Sutton\nPaul Cafiero\nPaul Daugherty\nPaul Davison\nPaul Krugman\nPaul Vigna\nPaula Long\nPenny Pritzker\nPerri Chilton\nPete Buttigieg\nPeter Blackwood\nPeter Buisseret\nPeter Chan\nPeter Donnelly\nPeter Johnson\nPeter Lauten\nPeter Leeson\nPeter Levine\nPeter Ludwig\nPeter Rubin\nPeter Thiel\nPeter Wang\nPetra Garrett\nPhil Daian\nPhil Hathaway\nPhil Wong\nPhong Nguyen\nPorter Smith\npplpleasr\nPranav Garimidi\nPrasad Akella\nPrat Moghe\nPreethi Kasireddy\npunk6529\nPurnima Padmanabhan\nPyrs Carvolth\nQasar Younis\nQuang Dao\nQuinten Burgunder\nQuintus Kilbourn\nRachael Horwitz\nRachel Goslins\nRachel Jenkins\nRachel Kalmar\nRachel McIntyre\nRachel Steiner\nRahul Iyer\nRahul Vohra\nRajeev Singh\nRajeev Venkayya\nRam Palaniappan\nRamana Jonnala\nRati Gelashvili\nRaul Vazquez\nRavi Parimi\nRay Dalio\nRaymond Carreira\nRebecca Lewis\nRebecca Rettig\nReed Hastings\nRefik Anadol\nRegina Benjamin\nRenato Valdés Olmos\nReshma Saujani\nReshma Sohoni\nRex Salisbury\nRich Ezekiel\nRichard Green\nRichard Menger\nRichard Rosenblatt\nRick Young\nRidhima Ahuja\nRiyaz Faizullabhoy\nRob Goodman\nRob McElhenney\nRob Pardo\nRob Rhinehart\nRobbie Petersen\nRobbie Peterson\nRobert Alexander\nRobert Cottrell\nRobert Hackett\nRobert Kolker\nRobert Leshner\nRobert McNeely\nRobert Moreno\nRobert Siegel\nRobert Stromberg\nRobert Weber\nRobin Casey\nRobin Guo\nRobin Weisman\nRod Johnson\nRodrigo Ibarra Lopez\nRodrigo Pacheco\nRoger Dickey\nRoger Wattenhofer\nRoham Gharegozlou\nRohini Mukand\nRohit Bansal\nRoman Mars\nRoman Stanek\nRon Gill\nRon Lavi\nRon Rothblum\nRonald Evans\nRonnie Harris\nRosa Davila\nRosalind Rattan\nRose Legarda\nRoss Andersen\nRoss Shuel\nRostin Behnam\nRuben Gallego\nRuben Smith\nRuss Altman\nRuss Heddleston\nRuss Roberts\nRussell Davies\nRyan Allen\nRyan Caldbeck\nRyan Conde\nRyan Holloway\nRyan Hoover\nRyan McEntush\nRyan Petersen\nRyan Prescott\nRyan Sandler\nRyan Spoon\nRyan Tseng\nRyan Walsh\nRyan Ward\nRyan Wyatt\nSaar Tochner\nSachin Jain\nSafi Bahcall\nSagar Dhawan\nSaku Panditharatne\nSalem Vance\nSam Blackshear\nSam Broner\nSam Gerstenzang\nSam Ragsdale\nSam Thompson\nSam Williams\nSam Yam\nSamantha Gelt\nSamantha Langford\nSamantha Ludwig\nSamson Wu\nSamuel Arbesman\nSamuel Hammond\nSandra Samayoa\nSandy Jen\nSankaet Pathak\nSantiago Rodriguez\nSara Boesen\nSarah Fazal\nSarah Hamburg\nSarah Lumbard\nSarah Mascardo\nSarah Meiklejohn\nSarah Porter\nSarah Rebello\nSarah Wang\nSasha Stiles\nSatish Talluri\nSaurabh Ladha\nSavannah Cherry\nScott Clark\nScott Duke Kominers\nScott Gottlieb\nScott Hassan\nScott Kupor\nScott Rubin\nScott Shenker\nScott Tyler\nScott Walker\nScott Weiss\nSean Duffy\nSean Neville\nSebastian Oddo\nSeema Amble\nSeemay Chou\nSep Kamvar\nSergiu Pasca\nSeth Lobree\nSeth Sivak\nSeth Sternberg\nShai Bernstein\nShai Kopeld\nShaka Senghor\nShakil Khan\nShan Sinha\nShana Fisher\nShane Mac\nShane Parrish\nShangda Xu\nShannon (Stubo) Brayton\nShannon Barbour\nShannon Kelly\nShannon Schiltz\nShannon Snow\nShari Doherty\nSharon Chang\nShawn Conway\nSheela Krothapalli\nShellye Archambeau\nSherie James\nSherriAnn Cole\nShishir Mehrotra\nShonda Rhimes\nSid Gorham\nSigne Pierce\nSimon Denny\nSiqi Chen\nSonal Chokshi\nSophie Song\nSoubhik Deb\nSpencer Dinwiddie\nSpencer Howard\nSpencer Rascoff\nSreeram Kannan\nSreevidya Kasturil\nSri Kosuri\nSriram Krishnan\nSrivatsan Sridhar\nStacey Cunningham\nStacey Merrick\nStacia Murray\nStacy Brown-Philpot\nStacy D'Amico\nStacy Warner\nStefan McDonough\nSten Tamkivi\nStephane Bancel\nStephanie Anyanwu\nStephanie Cohen\nStephanie Doppelt\nStephanie Smith\nStephanie Watkins\nStephanie Zinn\nStephen Armanios\nStephen Wink\nStephenie Zhang\nSteve Buress\nSteve Cadigan\nSteve Cheney\nSteve Harvey\nSteve Kaczynski\nSteve McDermid\nSteve Smith\nSteve Zhao\nSteven Adair\nSteven Ebert\nSteven Johnson\nSteven Levy\nSteven Sinofsky\nStewart Butterfield\nStina Ehrensvärd\nStuart Luman\nStuart Russell\nSudip Chakrabarti\nSue Hager\nSuhail Doshi\nSukhinder Singh Cassidy\nSumeet Singh\nSumit Shah\nSungMo Park\nSunil Chokshi\nSurya Ganguli\nSusan B. Wilde\nSusan Mernit\nSusan Rice\nSusannah Fox\nSydney Paul\nTaavet Hinrikus\nTaggart Matthiesen\nTamzen Brewis\nTana Billingsley\nTarek Mansour\nTarun Chitra\nTauri Laws Phillips\nTawny Holguin\nTaylor McFadden\nTed Not Lasso\nTed Sarandos\nTed Ullyot\nTerell Sterling\nTerence Carroll\nTeresa Carlson\nTerry Angelos\nTerry Brown\nThan Nguyen\nThanh Nguyen\nThe 2015 Academic Roundtable Sessions\nThe TxO team\nTheresa DeMichele\nTheresa Dilley\nTheresa Fisher\nTheresa Walz\nTheresia Gouw\nThibaut Scholasch\nThomas Gjerde\nThomas Juenger\nThomas Long\nThomas Rando\nTiffany Vo\nTiffany Zhong\nTim Beiko\nTim O'Reilly\nTim Roughgarden\nTim Schafer\nTim Sullivan\nTimmu Tõke\nTina Anderson\nTina Bhatnagar\nTina Ferguson\nTina Wie\ntinawie\nTing Ni\nTobi Lütke\nTodd Cranney\nTodd Lutwak\nTodd McKinnon\nTodd Park\nTodd Young\nTolga Dizdarer\nTom Butta\nTom Coates\nTom Davenport\nTom Ellis\nTom Hammer\nTom Hofmann\nTom Lehman\nTom Mitchell\nTom Preston-Werner\nTom Rikert\nTom Standage\nTomicah Tillemann\nTony Blair\nTony Blinken\nTori Landrum\nTracy Chou\nTracy Young\nTren Griffin\nTrent Mayol\nTrevor Bedford\nTristan Handy\nTristan Walker\nTroy Kirwin\nTugce Erten\nTurner Novak\nTushar Garg\nTyler Cowen\nTyler Wilson\nTyson Clark\nUma Valeti\nUsman Azam\nUzi Dutta\nValentina Marzorati\nValeria Nikolaenko\nValerie Arboleda\nVan Jones\nVan Le-Gray\nVanessa Kropf\nVas Narasimhan\nVaughn Ferguson\nVenkat Mocherla\nVicente De Baca\nVickie Casillas-Smith\nVictor Liang\nVictor Shoup\nVictoria Butcher\nVijay Balasubramaniyan\nVijay Kedar\nVijay Pande\nVineeta Agarwala\nVinod Khosla\nVirginia Postrel\nVishal Amin\nVitalik Buterin\nVivian Brooks\nVoices Onchain\nW. Brian Arthur\nWahab Owolabi\nWei Luo\nWendy Drpic\nWerner Gerola\nWes Taylor\nWhitney Owens\nWill Brown\nWill Wong\nWillem Mulder\nWilliam Gifford\nWilliam Mougayar\nWing Cheng\nXian Zhang\nXiang-Dong Fu\nXingchen Zhou\nYannai A. Gonczarowski\nYehuda Lindell\nYevgeniy Dodis\nYinuo Zhang\nYogi Roth\nYohei Ishii\nYoko Li\nYoni Levy\nYoram Novick\nYuichi Kurosawa\nYujin Chung\nYun Fan\nYung Yung Sheung\nYuval Efron\nYuval Harari\nZac Bookman\nZach Abrams\nZach Cohen\nZach Dicker\nZach Haigney\nZachary Chen\nZachary Gray\nZack Weiner\nZahabiya Gabaji\nZak Doric\nZal Bilimoria\nZane Lackey\nZeta Avarikioti\nZeya Yang\nZooko Wilcox\nZoran Basich\n\nclear all Jens Ernstberger\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n06.20.25 / Jason Milionis, Jens Ernstberger, Joseph Bonneau, Scott Duke Kominers and Tim Roughgarden\nManipulated signals in DePIN protocols\nIn a typical Decentralized Physical Infrastructure Network (DePIN) application, a network of suppliers is tasked with providing a service — weather readings in designated locations, broadband access, or energy, for example — to a client. Because self-interested suppliers can’t be trusted to self-report on their status, the question then becomes: How and when can a...\n\nresearch\nDePIN\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":6900,"crawled_at":1791194064796}
+{"id":10331,"url":"https://www.getfoundry.sh/introduction/agents","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Foundry documentation for agents – foundry - Ethereum Development Framework","text":"Foundry documentation for agents\n\nThe Foundry documentation is available as rendered HTML, page-level Markdown, compact and full text indexes, and an MCP server. Use the smallest source that answers the task instead of loading the entire book.\n\nWhen to use Foundry\n\nUse Foundry when a task involves a Solidity project or direct EVM interaction. Its four tools cover the common development loop:\n\nForge compiles, tests, fuzzes, debugs, deploys, verifies, formats, and lints Solidity projects.\n\nCast reads chain data, encodes and decodes ABI values, manages wallets, signs messages, and sends transactions from the command line.\n\nAnvil runs a local Ethereum node for deterministic tests, state manipulation, mining control, and forks of live networks.\n\nChisel provides an interactive Solidity REPL for evaluating expressions and prototyping contract logic.\n\nReach for a narrower tool when the task is outside that loop: use a Solidity compiler directly for compiler-only integration, a Rust or JavaScript Ethereum library for application code, and a browser wallet for user-mediated signing. Within a Foundry project, call the installed CLI from the project root so it reads the project's foundry.toml, remappings, dependencies, and profiles.\n\nStart with read-only commands such as forge build, forge test, forge config, cast call, or cast rpc. Treat cast send, forge create, and forge script --broadcast as state-changing operations: confirm the target chain, signer, value, and user authorization before running them.\n\nRetrieval interfaces\n\nInterfaceURL patternUse it for\nPage Markdown\nhttps://getfoundry.sh/<page>.md\nReading one conceptual, guide, or reference page without navigation and presentation markup\n\nCompact index\nhttps://getfoundry.sh/llms.txt\nFinding candidate pages by title, route, and description\n\nFull corpus\nhttps://getfoundry.sh/llms-full.txt\nBuilding an offline index or retrieving across the whole documentation set\n\nMCP server\nhttps://getfoundry.sh/api/mcp\nSearching the documentation from an MCP-capable client\n\nHTML\nhttps://getfoundry.sh/<page>\nPresenting the result to a person or inspecting rendered tables and navigation\n\nFor example, retrieve the testing guide as Markdown from https://getfoundry.sh/forge/testing.md, then use the HTML route /forge/testing when linking the answer for a person.\n\nThe full corpus is large because it includes generated CLI, cheatcode, and Forge Standard Library reference pages. Start with llms.txt, select one or more page routes, and fetch their .md forms. Only retrieve llms-full.txt when a bulk local copy is actually needed.\n\nRoute by task\n\nTaskStart hereFollow with\nInstall Foundry or create a project\nGetting started\nProject setup, project layout\n\nCompile or configure Solidity\nBuilding contracts\nConfiguration, configuration reference\n\nWrite or diagnose tests\nTesting\nInvariant testing, fork testing, debugging\n\nDeploy or verify contracts\nScripting\nDeploying contracts, forge script\n\nQuery a chain or send a transaction\nCast overview\nReading chain data, sending transactions\n\nRun or control a local node\nAnvil overview\nForking, custom methods\n\nManipulate Forge test state\nCheatcode overview\nThe exact cheatcode reference page\n\nLook up exact flags or syntax\nforge reference\nThe specific forge, cast, anvil, or chisel command page\n\nConcept and guide pages explain intent, safe workflows, and how features fit together. Generated reference pages are better for exact signatures, flags, defaults, and accepted values. Retrieve both when an answer needs operational context and precise syntax.\n\nAgent retrieval workflow\n\nIdentify the tool and task: Forge, Cast, Anvil, Chisel, configuration, cheatcodes, or Forge Standard Library.\n\nSearch llms.txt or the MCP server for the task and its likely command or API name.\n\nRead the narrow conceptual or guide page as Markdown.\n\nRead the exact reference page when flags, overloads, parameters, or defaults matter.\n\nConfirm version-sensitive or safety-critical behavior against the installed command's --help output or the current Foundry source.\n\nLink the human-readable HTML pages in the final answer.\n\nPrefer local evidence when working inside a Foundry project. Read foundry.toml, remappings.txt, scripts, tests, generated artifacts, and the installed forge --version before assuming the project follows defaults. Avoid network calls, broadcasts, key access, or explorer requests unless the task requires them and the user has authorized them.\n\nSearch terms that map well\n\nSearch with the exact command, configuration key, cheatcode, error fragment, or output field when known. When it is not known, pair the tool name with the intended outcome, such as:\n\nforge replay fuzz corpus\n\nforge symbolic incomplete\n\ncast send hardware wallet\n\nanvil manual mining txpool\n\nvm record state diff\n\nfoundry.toml invariant depth\n\nKeep aliases in the query when terminology varies. Useful pairs include script and broadcast, fork and forking, trace and debug, binding and ABI, and wallet and signer.\n\nReport uncertainty\n\nFoundry nightly releases can move faster than documentation. State the Foundry version used for a version-sensitive answer. If documentation, installed help, and source disagree, report the disagreement and prefer evidence from the version the user is actually running.\nWas this helpful?\n\nSuggest changes on GitHub","tokens":1332,"crawled_at":1791194072125}
+{"id":10332,"url":"https://a16zcrypto.com/posts/article/manipulated-signals-in-depin-protocols","domain":"a16zcrypto.com","chapter":"research","title":"Manipulated signals in DePIN protocols - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nManipulated signals in DePIN protocols\nJason Milionis, Jens Ernstberger, Joseph Bonneau, Scott Duke Kominers, and Tim Roughgarden\n06.20.25\n\nTags & Share Tags\nDePIN\nresearch\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nIn a typical Decentralized Physical Infrastructure Network (DePIN) application, a network of suppliers is tasked with providing a service — weather readings in designated locations, broadband access, or energy, for example — to a client. Because self-interested suppliers can’t be trusted to self-report on their status, the question then becomes: How and when can a network truthfully elicit the status of a supplier?\n\nFor example, suppose a client relies on a physical service being accessible and reliable in a particular area. The client would want to verify that service exists in that location, and is motivated enough to provide compensation for service provision but can’t trust the provider to accurately self-report because it might be cheaper for the provider to offer the service elsewhere and just spoof the location. This is the problem of location verification, which we’ll use as our illustrative example throughout.\n\nIn new research, we formally characterize the two fundamental obstacles — manipulation and self-dealing — that stand in the way of verifying the level of service provided by a supplier (in our example, its location). Importantly, knowing that these are the only two obstacles also suggests approaches for how to resolve them. Our framework is the first to provide a basis from which to reason about what types of services can and cannot be incentivized in DePIN applications.\n\nOur model\n\nOur model has three types of participants: the client, who requests the service; the source, who claims to provide the service; and the observers, who can at least partially verify the extent to which the source performed the expected service. We focus on the source and the observers.\n\nThe source of the information in our location verification example is the object that must report its location. The observers (e.g., sensors) receive signals from the source that may be noisy and/or manipulated by the source. For example, perhaps each observer communicates with the source and measures the round-trip latency; the source may deliberately delay before responding to communication requests and thereby manipulate the imputed distance.\n\nThe order of operations is as follows:\n\nThe source picks a strategy. The person or entity with private information gets to influence the information received by observers. It selects a way to “manipulate” the signals the observers will get, using only options that are allowed based on its private information (e.g., its true location) and other constraints (e.g., it can use message delays to increase the perceived distances but cannot decrease perceived distances via that same method).\n\nSignals are created. Then, signals (e.g., perceived distances between observers and the source) are generated (possibly probabilistically) using the method the source picked.\n\nEach observer sees only their own signal. Observers get to see only their own signal — they don’t know what the others saw.\n\nEach participant self-reports their information. After seeing their signals, the source and the observers participate in an elicitation/verification mechanism in which the source and the observers report whatever they like — including things that aren’t necessarily true.\n\nThe goal is then to design a mechanism in which the source and observers are incentivized to truthfully report their private information and signals, respectively.\n\nTwo fundamental challenges revealed\n\nOur paper establishes that there are two challenges inherent in accurately eliciting information in signal networks. We show that these challenges are fundamental to the problem, rather than simply being an artifact of our currently nascent understanding of the application domain.\n\n1. Manipulation\n\nThe first challenge concerns the manipulation of measurements of the provided service, and the fact that any one or even all of the observers may not be able to detect those manipulations. That is, a source may lie to the observers — and it may be hard to tell when it does so. To incentivize accurate measurements, network participants’ utility (i.e., how they are rewarded) should be tied to visible behavior in the protocol’s mechanism (e.g., whether observers’ reports are logically consistent with one another). For example, a network participant (source or observer) could be rewarded in a project’s native token for providing information requested by the protocol that appears consistent with the information provided by the other participants.\n\nOur first formal theorem proves that the problem of incentivizing accurate information from the source and observers is unsolvable unless the setting satisfies a condition that we term “source identifiability.” This condition requires that the source’s information cannot be completely and always (in a statistical sense) manipulated to seem exactly the same to all observers under two different true source signals; we’ll say more on this below. We show that when such ambiguity is present, there’s nothing a protocol designer can do to guarantee truthful elicitation: The source can always exploit the ambiguity to undetectably misrepresent its information. This impossibility result holds even when the protocol has native tokens or other incentives at its disposal.\n\n2. Self-dealing\n\nIn incentive design, sometimes the cure is worse than the disease. In the context of decentralized service provision, a particular worry is that a source may additionally masquerade as one or more observers (so-called sybils) and pretend to request or verify service from themselves, or team up (i.e., collude) with other network participants to do so. In the language of our model, the source might collude with some observer(s) (or itself, under a sybil identity) with the intention of exploiting the mechanism for its rewards.\n\nOur second theorem establishes that when such collusion is present, truthful elicitation of the source’s information is essentially impossible (unless a condition much stronger than source identifiability holds, in which potentially colluding agents are ignored).\n\nThe good news\n\nOur results show that source non-identifiability and self-dealing are fundamental obstacles to verification in DePIN applications. The good news is that we show a sense in which these are the only two obstacles: We give a formal mechanism that, under the assumptions of source identifiability and no self-dealing, achieves full information revelation at the equilibrium.\n\nHow DePIN protocol designers can move forward\n\nOur results suggest two key lessons for DePIN protocol designers. The first is to take steps to ensure that source identifiability is possible. This is not as abstract as it sounds — for example, in location verification, source identifiability is equivalent to the geometric condition that the source’s location lies in the convex hull of observers’ locations. So if you want to ensure that you can truthfully elicit a source’s location, be sure to “surround” its possible locations appropriately with observers.\n\nThe second lesson is that DePIN protocol designers need to address self-dealing concerns outside of the protocol. Ways to do this include, for example, restrictions to permissionless entry (thereby justifying stronger trust assumptions) or randomizing between many different sources who might perform a service for the client (thereby assigning a non-zero cost to pretending to request service).\n\n***\n\nWe hope that our work helps DePIN designers think crisply about their verification problems and the different options for addressing them. DePIN protocols are already exploring these and related ideas, and we’re excited to see how it plays out.\n\n***\n\nFor deeper technical analysis and discussion of our model of and results on signal networks, please see our paper, “Incentive-Compatible Recovery from Manipulated Signals, with Applications to Decentralized Physical Infrastructure.”\n\n***\n\nJason Milionis is a Ph.D. student in the Computer Science Department at Columbia University, where he is advised by Christos Papadimitriou and Tim Roughgarden. He is broadly interested in Game Theory, especially in conjunction with Machine Learning, and DeFi. He has also been an intern at the a16z crypto research lab.\n\nJens Ernstberger works at the intersection of cryptography and computer security. Most recently, he was a research intern at a16z crypto. Previously, he was a PhD student at Technical Univeristy of Munich, under the supervision of Prof. Sebastian Steinhorst and Dr. Arthur Gervais.\n\nJoseph Bonneau is a Technical Advisor on the a16z crypto team and an Associate Professor in the Computer Science Department at the Courant Institute, New York University.\n\nScott Duke Kominers is the Sarofim-Rock Professor of Business Administration at Harvard Business School, a Faculty Affiliate of the Harvard Department of Economics, and a Research Partner at a16z crypto. He also advises a number of companies on web3 strategy, as well as marketplace and incentive design; for further disclosures, see his website. He’s also the coauthor of The Everything Token: How NFTs and Web3 Will Transform the Way We Buy, Sell, and Create.\n\nTim Roughgarden is a Professor of Computer Science and a member of the Data Science Institute at Columbia University, and Head of Research at a16z crypto.\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nThe content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":3023,"crawled_at":1791194083395}
+{"id":10333,"url":"https://gov.uniswap.org/t/community-governance-process/7732","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Community Governance Process - Governance-Meta - Uniswap Governance","text":"Community Governance Process\n\nGovernance-Meta\n\nashleigh\n\nOctober 26, 2020, 3:03pm\n\n1\n\nThis document is a suggested process for developing and advancing Uniswap Governance Proposals. It is a living document intended to be owned, modified and enforced by the Uniswap community.\n\nNote: Autonomous proposals are a recent addition to Governance, not yet considered in this document. A process and policy around this proposal type should be created and implemented by the community.\n\nProcess:\n\nSeveral governance venues available to Uniswap governance are mentioned, each serving its own particular purpose.\n\ngov.uniswap.org\n\nGov.uniswap.org is a Discourse forum for governance-related discussion. Community members must register for an account before sharing or liking posts. New members are required to enter 4 topics and read 15 posts over the course of 10 minutes before they are permitted to post themselves.\n\nSnapshot\n\nSnapshot is a simple voting interface that allows users to signal sentiment off-chain. Votes on snapshot are weighted by the number of UNI delegated to the address used to vote.\n\nGovernance portals\n\nA governance portal can be accessed through the Uniswap interface. Votes can be delegated and cast through this portal. There are also several other governance interfaces that users can use to cast their votes*:\n\nhttps://custody.coinbase.com/\n\nhttp://unigov.eth.link/#/ap\n\nhttps://app.boardroom.info/\n\n*Note: this is not a complete list, and should be updated by the community frequently.\n\nBelow is a preliminary draft for the Uniswap governance process, detailing exactly where these venues fit in. These processes are subject to change according to feedback from the Uniswap community.\n\nPhase 1: Temperature Check — Discourse/Snapshot\n\nThe purpose of the Temperature Check is to determine if there is sufficient will to make changes to the status quo.\n\nTo create a Temperature Check:\n\nAsk a general, non-biased question to the community on gov.uniswap.org about a potential change (example: “Should Uniswap governance add liquidity mining for XYZ token?”). Forum posts should be labeled as follows: “Temperature Check - [Your Title Here]”. The forum post should include a link to the associated Snapshot poll.\n\nVoters use Snapshot to indicate their interest in bringing it forward to the next stage. Snapshot poll lengths should be set to 3 days.\n\nThat’s it! You’ve just started the process of gaining support for a proposal. At the end of the 3 days, a majority vote with a 25k UNI yes-vote threshold wins.\n\nIf the Temperature check does not suggest a change from the status quo, the topic will be closed on the governance site. If the Temperature Check does suggest a change, proceed to Stage 2: Consensus Check.\n\nPhase 2: Consensus Check — Discourse/Snapshot\n\nThe purpose of the Consensus Check is to establish formal discussion around a potential proposal.\n\nTo create a Consensus Check:\n\nUse feedback from the Temperature Check post and create a new Snapshot poll which covers the options which have gained support. This poll can either be binary or multiple choice but should include the option “Make no change” or its equivalent. Set the poll duration to 5 days.\n\nCreate a new topic in the Proposal Discussion category on gov.uniswap.org titled “Consensus Check — [Your Title Here]”. This will alert the community that this topic has already passed Temperature Check. Any topics beginning with Consensus Check that have not passed Temperature Check should be immediately be removed by community moderators. Make sure that the discussion thread links to the new Snapshot poll and the Temperature Check thread.\n\nReach out to your network to build support for the proposal. Discuss the proposal and solicit delegates to vote on it. Be willing to respond to questions on the Consensus Check topic. Share your view point, although try to remain as impartial as possible.\n\nAt the end of 5 days, whichever option has the majority of votes wins, and can be included in a governance proposal for Stage 3. A 50k UNI yes-vote quorum is required for the Consensus Check to pass.\n\nIf the option “Make no change” wins, the Consensus Check topic should be closed by community moderators.\n\nPhase 3: Governance Proposal — Governance Portal\n\nPhase 3 — Governance Proposal — is the final step of the governance process. The proposal should be based on the winning outcome from the Consensus Check and can consist of one or multiple actions, up to a maximum of 10 actions per proposal.\n\nTo create a Governance Proposal:\n\nWrite the code for your proposal, which can be voted on through any Governance Portal. More resources can be found here. All proposed code should be audited by a professional auditor. This auditing process could be paid or reimbursed by the community treasury.\n\nEnsure at least 10 million UNI is delegated to your address in order to submit a proposal, or find a delegate who has enough delegated UNI to meet the proposal threshold to propose on your behalf.\n\nCreate a topic in the Proposal Discussion category on gov.uniswap.org titled “Governance Proposal [Proposal Number] — [Your Title Here]” and link to any relevant Snapshot polls/discussion threads as well as the code audit report. Proposal numbers should be in a “UP###” format. For example, the first Uniswap Proposal should be titled UP001, the second UP002, and so on. Topics that begin with “Governance Proposal” that have not successfully passed the Temperature Check and Consensus Check stages should be removed by community moderators.\n\nCall the propose() function of the Governor Alpha to deploy your proposal.\n\nOnce the propose() function has been called, a seven day voting period is started. Ongoing discussion can take place in the gov.uniswap.org forum. If the proposal passes successfully, a two day timelock will follow before the proposed code is executed.\n\nSoft governance:\n\nThe process described above lays out a structure for those wishing to host a formal vote on a particular issue.\n\nHowever, governance systems also require a degree of “metagovernance” discussions that inform the direction of and the implementation processes behind policy, but which don’t qualify as policy themselves.\n\nThe community may discuss new ideas and strategies for governance — including changes to the process outlined above — in the “Governance-Meta” category. On-chain voting is not necessary to make updates to off-chain processes.\n\nGovernance Glossary:\n\nUNI: An ERC-20 token that designates the weight of a user’s voting rights. The more UNI a user has in their wallet, the more weight their delegation or vote on a proposal holds.\n\nDelegation: UNI holders cannot vote or create proposals until they delegate their voting rights to an address. Delegation can be given to one address at a time, including the holder’s own address. Note that delegation does not lock tokens; it simply adds votes to the chosen delegation address.\n\nProposal: A proposal is code that is executed by the governance contract through timelock. It can replace the governance contract, transfer tokens from the community treasury, or perform an almost infinite range of other on-chain actions. In order to create a proposal, an address must have at least 1% (10M UNI) of all UNI delegated to their address. Proposals are stored in the “proposals” mapping of the Governor smart contract. All proposals are subject to a 7-day voting period. If the proposer does not maintain their vote weight balance throughout the voting period, the proposal may be canceled by anyone.\n\nQuorum: In order for a vote to pass, at least 4% of all UNI (40M) must vote in the affirmative. The purpose of this quorum is to ensure that the only measures that pass have adequate voter participation.\n\nVoting: Users can vote for or against single proposals once they have voting rights delegated to their address. Votes can be cast while a proposal is in the “Active” state. Votes can be submitted immediately using “castVote” or submitted later with “castVoteBySig” (For more info on castVoteBySig and offline signatures, see EIP-712). If the majority of votes (and a 4% quorum of UNI) vote for a proposal, the proposal may be queued in the Timelock.\n\nVoting Period: Once a proposal has been put forward, Uniswap community members will have a seven day period (the Voting Period) to cast their votes.\n\nTimelock: All governance actions are delayed for a minimum of 2 days by the timelock contract before they can be executed.\n\n70 Likes\n\nPreliminary Voting\n\nFocus on newcomers: healthy long term community building\n\n[Consensus Check] Should Uniswap Distribute UNI to Liquidity Providers?\n\n[Discussion] Uniswap Liquidity Incentive Plan\n\n[Temperature Check] Should Uniswap Distribute UNI to Liquidity Providers?\n\nAnnouncement: unofficial Community Call - Thursday 12 Nov 17:00 UTC\n\nDeploy Uniswap v3 to Arbitrum Mainnet\n\nTemperature Check - [Merge the Uniswap Grant Program into Uniswap DAO Governance]\n\nCommunity Governance Process Update [Jan 2023]\n\nProposed Simplifications to the Uniswap Governance Process\n\n[Discussion] Uniswap Liquidity Incentive Plan\n\n[RFC] Community Governance Process Changes\n\n[RFC - Update] Community Governance Process Changes\n\nheyJonBray\n\nOctober 31, 2020, 8:45am\n\n7\n\nI’ve had a lot of thoughts about the overall procedures. I’m linking a topic I made regarding an idea I have for a more organic way to promote and develop proposals that will be voted on, improvements to the overall Governance UI experience, and a novel way of staking votes for ideas that users would like to see become proposals. One of the great benefits we can take from this community governance is the formation of ad-hocs to quickly and efficiently perform Uniswap legislation (and also make it fun to do so).\n\nSimilar to how Augur has a prediction market, I am picturing a “Legislative Market” of sorts being a step forward in community governance. Using the staking mechanism logic behind liquidity pools in a competitive manner where YES and NO tokens that only work within the Governance UI are staked against each other in an attempt to push proposal ideas either forward or out.\n\nhttps://gov.uniswap.org/t/friendly-competitive-staking-proposal-process/8006\n\n20 Likes\n\nheyJonBray\n\nNovember 6, 2020, 2:19am\n\n8\n\nAny thoughts on the procedure of competitive staking?\n\nFor those who haven’t seen the UniPig interface, check it out. It is a % dominance protocol that was released with vague intentions by the creators.\n\nI think this would be a perfect use for it. Any feedback would be super helpful as I’m working on a UI demo.\n\n18 Likes\n\nhosseinmr\n\nJanuary 22, 2021, 12:26pm\n\n10\n\nI Think Uniswap Will going to cross the moon\n\n10 Likes\n\nkeninqiu\n\nFebruary 4, 2021, 4:45am\n\n11\n\nFor kline of Uniswap, please check out at flaswap. com\n\n1 Like\n\ndt656\n\nFebruary 9, 2021, 7:54am\n\n12\n\n2nd\n\n7 Likes\n\nheyJonBray\n\nFebruary 19, 2021, 1:46pm\n\n13\n\nThere’s no moon happening until the transaction fee bottleneck is overcome. Market cap for DeFi is slowly migrating to BSC.\n\nIt would be great if Uniswap integrated a direct-to-BSC bridge, as until Ethereum devs get the gas fees under control the price is going to stagnate. We’re seeing a lot of funds move off Ethereum and onto BSC because transactions can be completed for pennies.\n\nTechnical analysis doesn’t show much more upward momentum for UNI as far as price goes. However, it performs it’s utility as a governance token swimmingly, which is what it is meant for.\n\n11 Likes\n\nwesleyliu1020\n\nMarch 2, 2021, 9:57am\n\n15\n\nMaybe the layer 2 Dex taker over part of the market share. The layer 2 AMM protocol ZKSwap (zks.app) with 0 gas fee is a big threat.\n\n3 Likes\n\nvictmar8510\n\nMarch 8, 2021, 12:41am\n\n16\n\nEstoy de acuerdo, por las altos costos en la tarifa de transacción, estan migrando a BSC ya que las tarifas por transacción son muy bajas, se ha dado el caso de que vale mas la transacción que la cantidad de tokens que se quiere comprar.\n\n1 Like\n\nSriWahyu\n\nMarch 10, 2021, 9:48am\n\n17\n\nUniswap the MOON\n\n4 Likes\n\nChristie\n\nMarch 24, 2021, 2:15pm\n\n18\n\nUniswap\n\n4 Likes\n\nhervian_ivan\n\nMarch 29, 2021, 6:39am\n\n19\n\noptimism will be granted with $5k per token.\n\n4 Likes\n\nAlexanderNapGeo\n\nMarch 31, 2021, 4:51pm\n\n20\n\nPlease I am new here. Have used Uniswap many times. Today I swapped Ethereum for Polkamon tokens and only received for 14 tokens for $600. US dollars worth of Ether. I thought was getting 1400 Polkamon as ICO price is .40 cents apiece. How did this major mis pricing happen?\n\n7 Likes\n\nTomy\n\nApril 4, 2021, 8:25am\n\n21\n\nThat ICO ended in march 31, think you missed it sorry.\n\n4 Likes\n\nmboyle522\n\nApril 9, 2021, 9:38pm\n\n22\n\nThanks you made that really easy to digest.\n\n4 Likes\n\nneonnightsnz\n\nJuly 19, 2021, 2:43am\n\n23\n\nfrill is a good way to manage this\n\n2 Likes\n\nneonnightsnz\n\nJuly 19, 2021, 3:05am\n\n24\n\nJon, sorry I’m not sure how to post a new topic here. I’m hoping you can answer this.\n\nI’d like to borrow some money and I’d like to get a lower rate than banks offer something similar or better than p2p lending platforms like Mintos. I’m not ready to take a big loan vai crypto because of the market volatility. But if stable coins work as intended I’d be more open to it. I’d like a fixed term and floating and fixed interest options and understand securing the loan is important too so I’m happy to do so.\n\nUniswap has been awesome for investor’s but I’ve only heard about the horror stories so far about borrowers.\n\nIs uniswap capable of attracting borrowers? Automatic market makers create liquidity but doesn’t solve the equation until I’d like to see borrowers enter a contract with low interest rates and get the greatest not for risking capital but for returning value over the amount lent. Can you see how balancing this equation maybe impossible with automatic market makers.\n\n5 Likes\n\ncrosome\n\nNovember 19, 2021, 10:34am\n\n26\n\nit think Uniswap will improve more than before\n\ngo on\n\n2 Likes\n\nBenjamin\n\nNovember 19, 2021, 2:34pm\n\n27\n\nit will improve more than before go on\n\n2 Likes\n\nKainam_Harki\n\nNovember 25, 2021, 8:09am\n\n28\n\nuniswap is going on it flys\n\n3 Likes\n\nnext page →\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nGovernance Weekly Recap\n\nGovernance-Meta\n\n21\n\n6566\n\nMay 26, 2023\n\nA Deep Dive of Uniswap's Governance\n\nGovernance-Meta\n\n3\n\n4816\n\nFebruary 10, 2023\n\n[RFC] Community Governance Process Changes\n\nRequests for Comment\n\n11\n\n4561\n\nDecember 6, 2022\n\nProposed Simplifications to the Uniswap Governance Process\n\nGovernance-Meta\n\n3\n\n5988\n\nDecember 7, 2022\n\nProposal: Reduce amount of UNIs required to submit governance proposal\n\nRequests for Comment\n\n105\n\n17151\n\nNovember 25, 2021","tokens":3651,"crawled_at":1791194090695}
+{"id":10334,"url":"https://docs.sui.io/develop","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Develop | Sui Documentation","text":"Sui development centers on three areas: understanding the Sui architecture, writing Move packagesPackageSmart contracts on Sui., and building transactions. Each area builds on the previous one. You write Move packages to define onchain logic, then construct transactions to call that logic, and the Sui architecture determines how those transactions execute and reach finalityFinalityThe state in which a transaction is permanently recorded and cannot be revoked..\n\nA Move package contains one or more modulesModuleA component of a Move package that defines interaction with on-chain objects.. Each module defines types, functions, and the rules that govern how objects are created, transferred, and destroyed. Sui uses an objectObjectThe basic unit of storage on Sui. model where assets are explicit objects with defined ownership, rather than entries in a shared ledger.\n\nTransactions on Sui are programmable transaction blocksProgrammable transaction blocksDefine all user transactions on Sui. (PTBs). A single PTB can call multiple MoveMoveAn open source programming language used for all activity on Sui. functions, transferTransferChanging the owner of an asset. objects, and split or merge coins, all in one atomic operation. This composability reduces the number of round trips between your app and the network.\n\nIf you are new to Sui development, start with the architecture overview to understand how Sui processes transactions and manages state. Then move to writing your first Move package, and finally explore PTBs to learn how to compose complex onchain operations from your app.\n\nDevelop\nLearn the developer essentials, including info about Sui's architecture, how to write Move packages, and how to build transactions.\n→\nSui Architecture\nIn this section\nComponents\nNetworks\nConsensus\nTokenomics\nObject Model\nEpochs and Reconfiguration\n+ 4 more\n\n→\nUsing Objects\nIn this section\nTypes of Object Ownership\nDerived Objects\nDynamic Fields\nVersioning\nOwned Compared With Shared\nObject Display\n+ 1 more\n\n→\nWriting Move Packages\nIn this section\nWhat are Move Packages?\nMove Concepts\nMove Syntax Fundamentals\nMove Best Practices\nMove Book\n\n→\nDeploying and Upgrading Packages\nIn this section\nPublishing\nUpgrading\nCustom Upgrade Policies\nVersioning\nDeploy with GitHub Actions\n\n→\nManaging Packages\nIn this section\nMove Package Management\nAddress Management (Legacy)\nSource Verification\n\n→\nTesting and Debugging\nIn this section\nTesting Move Smart Contracts\nTroubleshooting Common Errors\n\n→\nBuilding Transactions\nIn this section\nWhat is a Transaction?\nLife of a Transaction\nProgrammable Transaction Blocks\nTransaction Authentication\nSoft Bundles\n\n→\nPaying for Transactions\nIn this section\nGas Fees\nObject-Based Local Fee Markets\nGasless Stablecoin Transfers\nSponsored Transactions\nGas Smashing\n\n→\nAccessing Data\nIn this section\nData Access Interfaces\nRPC and Data Providers\nJSON-RPC Migration Guide\ngRPC\nGraphQL\nArchival Service\n+ 3 more\n\n→\nCryptography\nIn this section\nSignature Verification\nHashing\nGroth16\nECVRF\nPasskey\n\n→\nSecurity\nIn this section\nBest Practices\n\n→\nProduction Readiness\nPrepare a Sui application for Mainnet deployment with checklists covering smart contract security, key management, package upgrades, infrastructure, and operational monitoring.\n→","tokens":818,"crawled_at":1791194098372}
+{"id":10335,"url":"https://stack.olas.network/open-autonomy/advanced_reference/developer_tooling/benchmarking","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Benchmarking - Olas Stack Developer Documentation","text":"Benchmarking\n\nThe Open Autonomy framework provides a benchmark tool to assist with the process of measuring the performance of an AI agent. The tool is designed to measure time spent within the execution of code blocks in the behaviours that compose an FSM App. It differentiates between two kinds of code blocks:\n\nLocal code blocks: used to measure the time taken in local computations, for example, preparation of payloads or computing a local function.\n\nConsensus code blocks: used to measure the time taken by the logic in the execution of the consensus algorithm by the agent instances.\n\nSet up the benchmark tool\n\nThe benchmark tool is encapsulated in the class\n\npackages.valory.skills.abstract_round_abci.models.BenchmarkTool\n\nTo set up the tool, you need to follow a couple of steps detailed below. Note that these steps are automatically done if you use the FSM App scaffold tool.\n\nImport the class BenchmarkTool in the models.py of your skill, and extend it, if required.\n\nfrom packages.valory.skills.abstract_round_abci.models import (\nBenchmarkTool as BaseBenchmarkTool)\n\n# (...)\n\n# Use the class as-is.\nMyBenchmarkTool = BaseBenchmarkTool\n\n# Or extend the class, if required.\nclass MyBenchmarkTool(BaseBenchmarkTool):\n# (...)\n\nEnsure that the skill configuration file skill.yaml points correctly to the skill benchmark tool in the section models.\n\nskill.yaml# (...)\nmodels:\nbenchmark_tool:\nargs:\nlog_dir: /logs\nclass_name: MyBenchmarkTool\n\nDefining the code blocks to measure\n\nOnce the tool is set up, it can be accessed through the skill context. Usually, the measurement of the code blocks will be executed within the async_act() method of the concrete behaviours.\n\nclass MyBehaviour(BaseBehaviour, ABC):\n\n# (...)\n\ndef async_act(self) -> Generator:\n# The benchmark tool can be accessed here through `self.context.benchmark_tool`\n\nThe syntax used to delimit the scope of the different types of code blocks (local and consensus blocks) is achieved through a Python with runtime context.\n\nclass MyBehaviour(BaseBehaviour, ABC):\n\n# (...)\n\ndef async_act(self) -> Generator:\n\n# (...)\n\nwith self.context.benchmark_tool.measure(self.behaviour_id).local():\n# Code which will be accounted for \"local\" execution\n# (...)\n\nwith self.context.benchmark_tool.measure(self.behaviour_id).consensus():\n# Code which will be accounted for \"consensus\" execution\n# It will typically consist of the following two statements:\nyield from self.send_a2a_transaction(payload)\nyield from self.wait_until_round_end()\n\nself.set_done()\n\nSave the benchmark data\n\nThe benchmark data is saved upon calling the method BenchmarkTool.save(). This function call is executed at the end of every period by the ResetAndPauseBehaviour (within the reset_pause_abci FSM App skill). Hence, the reset_pause_abci FSM App must be chained appropriately in the composed FSM, marking the end of a period in the business logic of the AI agent.\n\nAs a summary, the sequence of events that should occur so that the benchmark information is saved correctly is as follows:\n\nThe overall FSM App is composed with the reset_pause_abci FSM App.\n\nAny intermediate behaviour executes local and/or consensus blocks contexts within their async_act() method.\n\nThe FSM App reaches the ResetAndPauseRound (reset_pause_abci round and calls the BenchmarkTool.save() method.\n\nWait for as many periods as you wish before stopping the AI agent. Note that any measurement not saved at the end of a period will be lost.\n\nThe benchmark data will be stored in the folder <ai_agent_folder>/abci_build_*/persistent_data/benchmarks.\n\nUse the command line to aggregate benchmark information\n\nRun the AI agent. Build and run the AI agent in dev mode. (The tool also works if you run the AI agent normal mode.)\n\nWait for AI agent execution. Wait until the AI agent has completed at least one period before cancelling the execution. That is, wait until the ResetAndPauseRound round has occurred at least once. As commented above, this is required because benchmark data is saved in this state. Once you have a data dump, you can stop the local execution by pressing Ctrl-C.\n\nAggregate the benchmark data. The benchmark data will be stored in the folder <ai_agent_folder>/abci_build_*/persistent_data/benchmarks. Aggregate the data for all periods executing:\n\nautonomy analyse benchmarks abci_build_*/persistent_data/benchmarks\n\nThis will generate a benchmarks.html file containing benchmark stats in your current directory.\nBy default the script will generate output for all periods but you can specify which period to generate output for. Similarly, block types aggregation is configurable as well. For example,\n\nautonomy analyse benchmarks abci_build_*/persistent_data/benchmarks --period 2 --block-type consensus\n\nwill aggregate stats for consensus code blocks in the second period.\nYou can specify the --block-type option as local (to consider only local code blocks), consensus (to consider only consensus code blocks), total (to aggregate local + consensus code blocks) or all (to consider both consensus and local code blocks).","tokens":1266,"crawled_at":1791194106508}
+{"id":10336,"url":"https://gov.uniswap.org/t/rfc-community-governance-process-changes/18060","domain":"gov.uniswap.org","chapter":"governance_daos","title":"[RFC] Community Governance Process Changes - Requests for Comment - Uniswap Governance","text":"[RFC] Community Governance Process Changes\n\nRequests for Comment\n\ndevinwalsh\n\nNovember 21, 2022, 5:00pm\n\n1\n\nTL;DR\n\nOne of the goals of the Uniswap Foundation is to reduce the amount of friction in the community governance process. In that spirit, today we are proposing changes to that process to improve its efficiency and efficacy.\n\nWe propose the following changes to the community governance process:\n\nRemove the first off-chain Snapshot poll, and replace it with a “Request for Comment” post. The first phase of the governance process should allow the community to digest a proposal, comment, and ask questions – and for the proposer to respond and make updates. We also believe two off-chain votes introduces unnecessary friction, so we propose removing this first one.\n\nIncrease quorum for the remaining off-chain Snapshot poll in the second phase to 5M UNI. The purpose of this off-chain vote is to gauge community sentiment prior to the governance vote. We believe the 5M UNI quorum will act as a better signal than the lower quorum requirements in the current process.\n\nWe also propose to formalize a process for future changes to off-chain components of the governance process (like the changes discussed in this proposal): specifically, an off-chain Snapshot poll with the same parameters of the on-chain governance vote. Today, this would require a 7-day voting period with a 40M UNI quorum. All changes that entail changes to on-chain parameters should continue to go through the normal community governance process.\n\nIn 3 weeks, on Monday, December 12, we will post a Snapshot poll for the community to vote on these changes. As described above, the vote will last for 7-days and have a 40M UNI quorum.\n\nSummary\n\nUniswap’s governance process is a core input to the community’s ability to steward its ongoing maintenance and growth in a fair and transparent manner. The design of the process should optimize for the dissemination of information throughout the community, for thoughtful iterations on proposals, and for signaling from the community prior to on-chain votes. While the governance process put in place today has, for the most part, been successful in achieving those goals, we believe improvements can be made to reduce overhead and to enhance off-chain signaling prior to the final governance vote.\n\nThese process enhancements were previously discussed in the forum here, but the simplifications were never implemented. We have decided to bring them back with minor changes.\n\nBelow we lay out the suggested changes, alongside our rationale. We are excited to hear and incorporate your feedback into this process change.\n\nGroup 1 (1)1729×1138 87.1 KB\n\nCurrent Process\n\nA detailed outline of the current process can be found here.\n\nTemperature Check: A temperature check is accompanied by a 3-day snapshot poll with a 25k UNI quorum.\n\nConsensus Check: A consensus check is accompanied by a 5-day snapshot poll with a 50k UNI quorum.\n\nGovernance Proposal: The on-chain proposal and vote, tied to on-chain executable code, is the final phase of the governance process. The proposer must have a minimum of 2.5M UNI delegated to their address, and there is a 40M UNI quorum requirement.\n\nProposed changes to community governance process\n\nPhase 1: Request for Comment\n\nRename: Temperature Check → Request for Comment\n\nRemoval of Snapshot off-chain vote\n\nA minimum of 3 days before moving forward\n\nWe believe the first phase of the governance process should allow the community to digest a proposal, comment, and ask questions. The RFC Phase should last for at least 3 days so the proposers can gather adequate feedback to take into account for the next iteration of the proposal.\n\nWe are also removing the friction of two off-chain votes.\n\nPhase 2: Temperature Check\n\nRename: Consensus Check → Temperature Check\n\nIncrease the required quorum from 50k to 5M UNI\n\nFor this phase to better serve as a signaling tool, we suggest increasing quorum to 5M UNI. This threshold should be high enough to prevent lower quality proposals from moving to the final on-chain vote, while not creating additional friction.\n\nPhase 3: On-chain Governance Vote\n\nNo changes\n\nProposed formalization of process changes to off-chain components of governance process\n\nIn her original post on the community governance process, Ashleigh states “On-chain voting is not necessary to make updates to off-chain processes.” We agree with this. However, we do believe that community support and acceptance is important for off-chain process changes to have legitimacy.\n\nThus, we propose a formalized process – intended to signal community support and acceptance – to change these off-chain components in the future. Specifically, we propose an off-chain vote with the same parameters of the final governance vote. Right now, that is a 7 day vote period and 40M UNI quorum.\n\nThese are the parameters we plan to use to pass all of the proposed changes in this proposal.\n\nConclusion and Next Steps\n\nWe welcome all feedback from the community on these proposed changes, and will incorporate feedback into the proposal where sentiment is strong.\n\nIf no serious changes to the proposal are required, we plan to post a Snapshot Poll in 3 weeks, on Monday, December 12th for the community to vote on these changes. This vote will last for 7 days and require a quorum of 40M UNI votes.\n\nIf the vote passes, the UF will update relevant documentation on the forum and elsewhere.\n\n14 Likes\n\n[RFC - Update] Community Governance Process Changes\n\nGovernance Weekly Recap\n\nGovernance Weekly Recap\n\npennblockchain\n\nNovember 21, 2022, 5:03pm\n\n2\n\nThanks for this! After experimenting with a couple different methods and helping a couple different teams submit proposals, we are in huge favor of this new proposed timeline. The RFC period is probably most important and may take over 3 days. The temp and consensus check seemed a bit redundant prior and this newer system will decrease voter fatigue.\n\n3 Likes\n\ndevenmatthews\n\nNovember 21, 2022, 10:05pm\n\n3\n\nFrom a voter’s perspective this process is far more streamlined and preferable (two non-binding votes is repetitive imo). We (Blockchain at Berkeley) would signal support for this updated process.\n\nI’d like to seek clarity on the min $UNI delegated to create the mentioned Snapshot polls. Just tried to create a snapshot proposal from my personal wallet and was told I need 1k uni minimum delegated. Want to be clear if the new [temp check] phase will retain this 1k $UNI requirement. Also would like to confirm that the proposed formalized off-chain final vote will maintain the same 2.5mm $UNI proposing requirement as the on-chain final vote.\n\n1 Like\n\ndevenmatthews\n\nNovember 21, 2022, 10:12pm\n\n4\n\nJust for reference:\n\n37 wallets appear to meet the 2.5mm final vote proposing requirement\n\n199 wallets appear to meet the 1k snapshot temp check proposing requirement\n\nsource: Tally | Uniswap | Voters\n\n1 Like\n\n[RFC - Update] Community Governance Process Changes\n\ndevinwalsh\n\nNovember 22, 2022, 7:11am\n\n5\n\nThese are good questions.\n\nFor the lone remaining off-chain Snapshot vote, we would propose to keep the 1k UNI delegation/self-delegation requirement. The intention of this is to reduce spam by requiring some skin in the game.\n\nFor the formalized process for off-chain process changes, we’re not sure about this yet actually, and are open to feedback and discussion. The goal of mirroring the parameters of the final governance vote (7 days, 40M quorum) is to confer legitimacy and community acceptance onto the changes being made. For that reason, I would say 2.5M UNI should also be required.\n\nI’ve confirmed this is possible with the Snapshot team - we can leverage subspace functionality to create two kinds of polls with two different delegation/self-delegation requirements.\n\nWhat do you think?\n\n2 Likes\n\nGFXlabs\n\nNovember 24, 2022, 6:52pm\n\n6\n\nThank you, Devin, for getting the ball rolling here. We think many, ourselves included, thought the governance process was sub-optimal. Switching the temperature check to a 3-day RFC sounds like a good improvement. It might be nice to make that a week instead; however, we don’t see a reason to delay the Snapshot Poll if the proposer believes they can rally the votes.\n\nWe do think it is worth considering to increase the Snapshot further than the proposed 5m. As @devenmatthews pointed out, 37 wallets meet the 2.5mm threshold. With that in mind, maybe we should set the quorum to 10m, or more? Ultimately it isn’t super important since the poll is not codified and is only socially enforced.\n\nAs for the second point regarding a formalized off-chain governance process. Snapshot voting should not be used for decision-making because a large amount of UNI cannot participate in Snapshot due to custody providers inability to vote off-chain. All governance decisions should be decided on-chain.\n\n1 Like\n\n[RFC - Update] Community Governance Process Changes\n\neek637\n\nNovember 28, 2022, 8:21pm\n\n7\n\nHi all,\n\nGlad to see this in motion. I agree with @GFXlabs that a higher quorum for the Snapshot poll might be a good idea. Reaching quorum would then indicate that the proposal is either an absolute home run or that the proposer has done the leg work to get it in front of enough delegates to get buy-in from the community. 10m seems a reasonable number.\n\nI wanted to raise one more item here. While in general I’d like to avoid the scenario where the DAO must decide the best option out of several, it’s reasonable to think that we’ll run up against it at some point. Given a recent personal run-in with ranked-choice voting, I strongly believe that it’s a superior method to first past the post voting (despite having lost the vote in question!). That said, it’s not super intuitive to understand the implications of your vote in RCV and I’d like to avoid a situation where we’re explaining it to stakeholders while a vote is happening.\n\nIt’s not easy to envision a scenario where we’re making such a choice given the DAO’s current structural constraints, but I do think it’s worth there being a bullet point in both the Phase 2: Temperature check section and the Proposed formalization of process changes to off-chain components of governance process section that indicate that in the event of a choice between several options, RCV will be the methodology used.\n\n2 Likes\n\nGovernance Weekly Recap\n\nbonustrack\n\nNovember 28, 2022, 10:47pm\n\n8\n\nSnapshot voting should not be used for decision-making because a large amount of UNI cannot participate in Snapshot due to custody providers inability to vote off-chain. All governance decisions should be decided on-chain.\n\nHi! Fabien from Snapshot here. Do you know which custodian(s) wouldn’t work with Snapshot? AFAIK most custodians support Snapshot voting through delegation, I know Coinbase or Fireblocks are used and Anchorage recently added a way to do delegation (need to activate on request). Which one I’m missing?\n\ndevinwalsh\n\nNovember 29, 2022, 10:00pm\n\n9\n\nI think lengthening the RFC could make sense - maybe to a 5 day minimum? That seems like a fair amount of time to allow active governance participants to read a proposal, put together some initial thoughts, feedback, and questions, and comment in the forums.\n\nIn terms of quorum for the new Temperature Check Phase (currently at 5M), I think increasing it makes sense in that it adds additional assurance that the proposer will spend time speaking to and rallying multiple delegates prior to the final governance vote.\n\ntobyshorin\n\nDecember 3, 2022, 1:45pm\n\n10\n\nOther Internet supports this simplification.\n\nOne note: when Teo posted the original version of this proposal, we had the following suggestion:\n\nmore standardization around how to set up Snapshot polls would be helpful. Framing of “yes” and “no” votes could use particular attention (here are three different polls which each have different phrasings for yes and no votes — some do not show up in the UI properly). Using “no change” as a standard for no votes, at the very least, would be a reasonable starting place.\n\nStill think that this would be useful language to add to a governance process update.\n\nThe current process has been enshrined in several third party apps like Boardroom. We’ll need to make a list of these projects and reach out to ensure the process documentation is correctly updated.\n\nLastly, not opposed to a 5 day RFC minimum. Not opposed to increased quorum.\n\n[RFC - Update] Community Governance Process Changes\n\nKingofamericas\n\nDecember 4, 2022, 7:47am\n\n11\n\nDo anyone know how long it takes for my coins pairs to be listed on the pool list they where confirmed index onto uniswap dot org pool. Will they show up on list to the public? I add these coins pairs a few weeks ago and they still not in pool search list!\n\n( EAMIINFT / MATIC ) and ( BHOIINFT / MATIC ) and ( MATIC / BTC ) and ( MATIC / AHLRCMETA ) and ( MATIC / CRYPTO ) and ( MATIC / CHURCH ) all these coins pairs on Polygonscan network. I added them now how do they show up in pool all search or pool list under Polygon. Is it a time period wait or i have to program them onto available Uniswap list? Please give code I will tip with some of my above Matic pairs too ERC-20 tokens!\n\nalanalevin\n\nDecember 6, 2022, 1:10pm\n\n12\n\nI support modifying the governance process as outlined in the proposal - namely, eliminating the off-chain Snapshot poll, creating a “Request for Comment” phase, and increasing the quorum for the second phase.\n\nConsistent with several other community members’ comments, I think the RFC process should be longer than 3 days; my view is that it should be at least 7 days long. Having a week provides necessary time to become aware of each proposal and formulate potential comments. Less than a week risks rushing the commentary process.\n\nThis post was authored by Alana Levin, an investment partner at Variant. Variant is an investor in the UNI token. See disclosures.\n\n[RFC - Update] Community Governance Process Changes\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[RFC - Update] Community Governance Process Changes\n\nRequests for Comment\n\n4\n\n8968\n\nDecember 24, 2022\n\nProposed Simplifications to the Uniswap Governance Process\n\nGovernance-Meta\n\n3\n\n5988\n\nDecember 7, 2022\n\nCommunity Governance Process Update [Jan 2023]\n\nGovernance-Meta\n\n4\n\n38245\n\nJanuary 9, 2026\n\nCommunity Governance Process\n\nGovernance-Meta\n\n30\n\n58333\n\nApril 7, 2023\n\n[RFC] Reconfigure Snapshot Proposal Threshold\n\nGovernance-Meta\n\n2\n\n3399\n\nApril 14, 2023","tokens":3624,"crawled_at":1791194111171}
+{"id":10337,"url":"https://docs.dydx.xyz/node-client/private","domain":"docs.dydx.xyz","chapter":"defi_protocols","title":"dYdX Documentation","text":"Private Node API\n\nPlace Order\n\nExecute a transaction that places an order on a market.\nThis function takes parameters for wallet authentication, various order details, and optional transaction options to manage specific order types and behaviors.\n\nMethod Declaration\n\nPython\nasync def place_order(\nself,\nwallet: Wallet,\norder: Order,\ntx_options: Optional[TxOptions] = None,\n)\n\nUnification Plan\nUse a convenient Wallet and Order pair for all clients\n\nTypeScript doesn't use authenticators\n\nIn Python we use them explicitly\n\nConsider to do the same like in Rust (set it automatically)\n\nParameters\n\nParameterLocationTypeRequiredDescription\nwallet\nquery\nWallet\ntrue\nThe wallet to use for signing the transaction.\n\norder\nquery\nOrder\ntrue\nThe order to place.\n\ntx_options\nquery\nTxOptions\nfalse\nOptions for transaction to support authenticators.\n\nResponse\n\nStatusMeaningSchema\n200\nOK\nTxHash\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\nExamples: Python | TypeScript | Rust | Guide - Place an order\n\nCancel Order\n\nTerminate an existing order using the provided order ID and related parameters, such as block validity periods and transaction options.\n\nMethod Declaration\n\nPython\nasync def cancel_order(\nself,\nwallet: Wallet,\norder_id: OrderId,\ngood_til_block: int = None,\ngood_til_block_time: int = None,\ntx_options: Optional[TxOptions] = None,\n)\n\nUnification plan\nCheck the marketId is really needed (used in TypeScript)\n\nParameters\n\nParameterLocationTypeRequiredDescription\nwallet\nquery\nWallet\ntrue\nThe wallet to use for signing the transaction.\n\norder_id\nquery\nOrderId\ntrue\nThe ID of the order to cancel.\n\ngood_til_block\nquery\ni32\nfalse\nThe block number until which the order is valid. Defaults to None.\n\ngood_til_block_time\nquery\ni32\nfalse\nThe block time until which the order is valid. Defaults to None.\n\ntx_options\nquery\nTxOptions\nfalse\nOptions for transaction to support authenticators.\n\nResponse\n\nStatusMeaningSchema\n200\nOK\nTxHash\nThe transaction hash.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe order was not found.\n\nExamples: Rust | Guide - Cancel an order\n\nBatch Cancel Orders\n\nCancel a batch of short-terms orders.\n\nMethod Declaration\n\nPython\nasync def batch_cancel_orders(\nself,\nwallet: Wallet,\nsubaccount_id: SubaccountId,\nshort_term_cancels: List[OrderBatch],\ngood_til_block: int,\ntx_options: Optional[TxOptions] = None,\n)\n\nUnification plan\nTxOptions is not available in Rust\n\nParameters\n\nParameterLocationTypeRequiredDescription\nwallet\nquery\nWallet\ntrue\nThe wallet to use for signing the transaction.\n\nsubaccount_id\nquery\nSubaccountId\ntrue\nThe subaccount ID for which to cancel orders.\n\nshort_term_cancels\nquery\nOrderBatch ⛁\ntrue\nList of OrderBatch objects containing the orders to cancel.\n\ngood_til_block\nquery\nHeight\ntrue\nThe last block the short term order cancellations can be executed at.\n\ntx_options\nquery\nTxOptions\nfalse\nOptions for transaction to support authenticators.\n\nResponse\n\nStatusMeaningSchema\n200\nOK\nTxHash\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe subaccount was not found.\n\nExamples: Python | TypeScript | Rust\n\nDeposit\n\nDeposit funds (USDC) from the address to the subaccount.\n\nMethod Declaration\n\nPython\nasync def deposit(\nself,\nwallet: Wallet,\nsender: str,\nrecipient_subaccount: SubaccountId,\nasset_id: int,\nquantums: int,\n)\n\nParameters\n\nParameterLocationTypeRequiredDescription\nwallet\nquery\nWallet\ntrue\nThe wallet to use for signing the transaction.\n\nsender\nquery\nstring\ntrue\nThe sender address.\n\nrecipient_subaccount\nquery\nSubaccountId\ntrue\nThe recipient subaccount ID.\n\nasset_id\nquery\nAssetId\ntrue\nThe asset ID.\n\nquantums\nquery\nint\ntrue\nThe amount of quantums to deposit. See more about quantums\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nTxHash\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe subaccount was not found.\n\nWithdraw\n\nWithdraw funds (USDC) from the subaccount to the address.\n\nMethod Declaration\n\nPython\nasync def withdraw(\nself,\nwallet: Wallet,\nsender_subaccount: SubaccountId,\nrecipient: str,\nasset_id: int,\nquantums: int,\n)\n\nParameters\n\nParameterLocationTypeRequiredDescription\nwallet\nquery\nWallet\ntrue\nThe wallet to use for signing the transaction.\n\nsender_subaccount\nquery\nSubaccountId\ntrue\nThe sender subaccount ID.\n\nrecipient\nquery\nstring\ntrue\nThe recipient subaccount ID.\n\nasset_id\nquery\nAssetId\ntrue\nThe asset ID.\n\nquantums\nquery\nint\ntrue\nThe amount of quantums to withdraw.\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nTxHash\nThe transaction hash.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe subaccount was not found.\n\nExamples: Python | TypeScript | Rust\n\nTransfer\n\nTransfer funds (USDC) between subaccounts.\n\nMethod Declaration\n\nPython\nasync def transfer(\nself,\nwallet: Wallet,\nsender_subaccount: SubaccountId,\nrecipient_subaccount: SubaccountId,\nasset_id: int,\namount: int,\n)\n\nParameters\n\nParameterLocationTypeRequiredDescription\nwallet\nquery\nWallet\ntrue\nThe wallet to use for signing the transaction.\n\nsender_subaccount\nquery\nSubaccountId\ntrue\nThe sender subaccount ID.\n\nrecipient_subaccount\nquery\nSubaccountId\ntrue\nThe recipient subaccount ID.\n\nasset_id\nquery\nAssetId\ntrue\nThe asset ID.\n\namount\nquery\nint\ntrue\nThe amount to transfer in quote quantums (e.g. 1_000_000 = 1 USDC). See more about quantums\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nTxHash\nThe transaction hash.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe subaccount was not found.\n\nExamples: Python | TypeScript | Rust\n\nSend Token\n\nTransfer a specified token from one account/address to another.\n\nIt requires details such as the wallet for signing the transaction, sender and recipient addresses, and the quantum amount or denomination of the token.\n\nMethod Declaration\n\nPython\nasync def send_token(\nself,\nwallet: Wallet,\nsender: str,\nrecipient: str,\nquantums: int,\ndenomination: str,\n)\n\nUnification Plan\nAll the types are different, revision is needed\n\nStandard types like strings are used\n\nBroadcast mode?\n\nZero fee?\n\nParameters\n\nParameterLocationTypeRequiredDescription\nwallet\nquery\nWallet\ntrue\nThe wallet to use for signing the transaction.\n\nsender\nquery\nString\ntrue\nThe sender address.\n\nrecipient\nquery\nString\ntrue\nThe recipient address.\n\nquantums\nquery\ni32\ntrue\nThe amount of quantums to send.\n\ndenomination\nquery\ni32\ntrue\nThe denomination of the token.\n\nResponse\n\nStatusMeaningSchema\n200\nOK\nTxHash\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\nExamples: Rust\n\nSimulate\n\nPre-execution simulation of a transaction, predicting its execution cost and resource usage without committing any changes.\n\nThis method typically returns information like estimated gas fees or other transaction-related metrics to anticipate the impact of operations before they are executed on the blockchain.\n\nMethod Declaration\n\nPython\nasync def simulate(self, transaction: Tx)\n\nUnification Plan\nSome extra parameters in TypeScript? What to do with them?\n\nParameters\n\nParameterLocationTypeRequiredDescription\ntransaction\nquery\nTx\ntrue\nThe transaction to simulate.\n\nResponse\n\nStatusMeaningSchema\n200\nOK\nGasInfo\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\nExamples: Python | TypeScript | Rust\n\nCreate Transaction\n\nCreate a transaction.\n\nMethod Declaration\n\nPython\nasync def create_transaction(self, wallet: Wallet, message: Message) -> Tx\n\nParameters\n\nParameterLocationTypeMandatoryDescription\naccount\nquery\nAccount\ntrue\nOwner's account information\n\nmsg\nquery\nAny\ntrue\nMessage during create transaction\n\nauth\nquery\nAddress\nfalse\n\nResponse\n\nStatusMeaningSchema\n200\nOK\ntx::Raw\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\nBroadcast Transaction\n\nThe Broadcast Transaction method is used to send a transaction to the network for processing.\n\nThe key parameters include the transaction itself and the mode of broadcasting, which is optional and defaults to synchronous broadcasting mode.\n\nMethod Declaration\n\nPython\nasync def broadcast(self, transaction: Tx, mode=BroadcastMode.BROADCAST_MODE_SYNC)\n\nParameters\n\nParameterLocationTypeRequiredDescription\ntransaction\nquery\nTx\ntrue\nThe transaction to broadcast.\n\nmode\nquery\nBroadcastMode\nfalse\nThe broadcast mode. Defaults to BroadcastMode.BROADCAST_MODE_SYNC.\n\n:::\n\nResponse\n\nStatusMeaningSchema\n200\nOK\nTxHash\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe transaction was not found.\n\nExamples: Rust\n\nCreate Market Permissionless\n\nCreate a market permissionless.\n\nMethod Declaration\n\nPython\nasync def create_market_permissionless(\nself, wallet: Wallet, ticker: str, address: str, subaccount_id: int\n) -> Any\n\nParameters\n\nParameterLocationTypeDescription\naccount\nquery\nAccount\nAccount information\n\nticker\nquery\nTicker\nTicker information\n\nsubaccount\nquery\nSubaccountInfo\nSubaccount information\n\nResponse\n\nStatusMeaningSchema\n200\nOK\nTxHash\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe subaccount was not found.\n\nDelegate\n\nDelegate tokens from a delegator to a validator.\n\nMethod Declaration\n\nPython\nasync def delegate(\nself,\nwallet: Wallet,\ndelegator: str,\nvalidator: str,\nquamtums: int,\ndenomination: str,\n)\n\nParameters\n\nParameterLocationTypeMandatoryDescription\nsubaccount\nquery\nSubaccountInfo\ntrue\nSubaccount number\n\ndelegator\nquery\nstring\ntrue\nDelegator information\n\nvalidator\nquery\nstring\ntrue\nvalidator information\n\namount\nquery\nstring\ntrue\nAmount to delegate\n\nbroadcastMode\nquery\nBroadcastMode\nfalse\nMode of broadcast\n\nResponse\n\nStatusMeaningSchema\n200\nOK\nBroadcastTxAsyncResponse\n\nUndelegate\n\nUndelegate coins from a delegator to a validator.\n\nMethod Declaration\n\nPython\nasync def undelegate(\nself,\nwallet: Wallet,\ndelegator: str,\nvalidator: str,\nquamtums: int,\ndenomination: str,\n)\n\nParameters\n\nParameterLocationTypeMandatoryDescription\nsubaccount\nquery\nSubaccountInfo\ntrue\nSubaccount number\n\ndelegator\nquery\nstring\ntrue\nDelegator information\n\nvalidator\nquery\nstring\ntrue\nvalidator information\n\namount\nquery\nstring\ntrue\nAmount to delegate\n\nbroadcastMode\nquery\nBroadcastMode\nfalse\nMode of broadcast\n\nResponse\n\nStatusMeaningSchema\n200\nOK\nBroadcastTxAsyncResponse\n\nRegister Affiliate\n\nRegister affiliate.\n\nMethod Declaration\n\nPython\nasync def register_affiliate(\nself, wallet: Wallet, referee: str, affiliate: str\n) -> Any\n\nParameters\n\nParameterLocationTypeMandatoryDescription\nsubaccount\nquery\nSubaccountInfo\ntrue\nSubaccount information\n\naffiliate\nquery\nstring\ntrue\nAffiliate information\n\nbroadcastMode\nquery\nBroadcastMode\nfalse\nMode of broadcast\n\ngasAdjustment\nquery\nint\nfalse\nGas adjustment value\n\nResponse\n\nStatusMeaningSchema\n200\nOK\nBroadcastTxAsyncResponse\n\nWithdraw Delegator Reward\n\nWithdraw delegator reward.\n\nMethod Declaration\n\nPython\nasync def withdraw_delegate_reward(\nself, wallet: Wallet, delegator: str, validator: str\n) -> Any\n\nParameters\n\nParameterLocationTypeMandatoryDescription\nsubaccount\nquery\nSubaccountInfo\ntrue\nSubaccount number\n\ndelegator\nquery\nstring\ntrue\nDelegator information\n\nvalidator\nquery\nstring\ntrue\nvalidator information\n\nbroadcastMode\nquery\nBroadcastMode\nfalse\nMode of broadcast\n\nResponse\n\nStatusMeaningSchema\n200\nOK\nBroadcastTxAsyncResponse\n\nClose Position\n\nClose position for a given market.\n\nOpposite short-term market orders are used. If provided, the position is only reduced by a size of reduce_by. Note that at the moment dYdX doesn’t support spot trading.\n\nMethod Declaration\n\nPython\n\nParameters\n\nParameterLocationTypeRequiredDescription\naccount\nquery\nAccount\ntrue\nThe wallet address that owns the subaccount.\n\nsubaccount\nquery\nSubaccount\ntrue\nSubaccount to close\n\nmarket_params\nquery\nOrderMarketParams\ntrue\nMarket parameters\n\nreduced_by\nquery\nBigDecimal\nfalse\n\nclient_id\nquery\nClientId\ntrue\n\nResponse\n\nStatusMeaningSchema\n200\nOK\nTxHash\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe subaccount was not found.\n\nExamples: Rust\n\nDeposit to MegaVault\n\nDeposit USDC into MegaVault\n\nMethod Declaration\n\nPython\nasync def deposit(\nself, wallet: Wallet, address: str, subaccount_number: int, amount: Decimal\n) -> Any\n\nParameters\n\nParameterLocationTypeDescription\naccount\nquery\nAccount\nOwner's account information\n\nsubaccount\nquery\nSubaccountInfo\nSubaccount information\n\namount\nquery\nDecimal\nAmount in usdc to deposit\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nTxHash\nThe transaction hash.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe subaccount was not found.\n\nWithdraw from MegaVault\n\nWithdraw funds (USDC) from the subaccount to the address.\n\nMethod Declaration\n\nPython\nasync def withdraw(\nself,\nwallet: Wallet,\naddress: str,\nsubaccount_number: int,\nmin_amount: Decimal,\nshares: Optional[int],\n) -> Any\n\nParameters\n\nParameterLocationTypeDescription\naccount\nquery\nAccount\nOwner's account\n\nsubaccount\nquery\nSubaccountInfo\nSubaccount information\n\nmin_amount\nquery\nDecimal\nMinimum amount to withdraw i usdc\n\nshares\nquery\nBigInt\nNumber of shares\n\nResponse\n\nStatusMeaningSchemaDescription\n200\nOK\nTxHash\nThe transaction hash.\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\n404\nNot Found\n\nThe subaccount was not found.\n\nGet Owner Shares in MegaVault\n\nQuery the shares associated with an Address.\n\nMethod Declaration\n\nPython\nasync def get_owner_shares(\nself, address: str\n) -> vault_query.QueryMegavaultOwnerSharesResponse\n\nParameters\n\nParameterLocationTypeDescription\naddress\nquery\nAddress\nThe wallet address that owns the subaccount.\n\nResponse\n\nStatusMeaningSchema\n200\nOK\nQueryMegavaultOwnerSharesResponse\n\n400\nBad Request\n\nThe request was malformed or invalid.\n\nGet Withdrawal Info of MegaVault\n\nQuery the withdrawal information for a specified number of shares.\n\nMethod Declaration\n\nPython\nasync def get_withdrawal_info(\nself, shares: int\n) -> vault_query.QueryMegavaultWithdrawalInfoResponse\n\nParameters\n\nParameterLocationTypeDescription\nshares\nquery\nBigInt\nNumber of shares\n\nResponse\n\nStatusMeaningSchema\n200\nOK\nQueryMegavaultWithdrawalInfoResponse\n\n400\nBad Request\n\nThe request was malformed or invalid.","tokens":3486,"crawled_at":1791194117513}
+{"id":10338,"url":"https://docs.sui.io/develop/sui-architecture","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Sui Architecture | Sui Documentation","text":"Sui is a layer 1 blockchain built on a delegated proof-of-stakeDPoSConsensus mechanism used by Sui. consensusConsensusThe process by which the majority of nodes agree on the current state of the network model. Learn about the core components that make up Sui, including the objectObjectThe basic unit of storage on Sui. model, transactionTransactionA number of commands that execute on inputs to define the result of the transaction. processing, consensus mechanisms, network environments, and tokenomics.\n\nComponents\nSui is a layer 1 blockchain that performs its own consensus and validation of transaction blocks. Sui is comprised of the blockchain itself, the blockchain's activity such as transactions, and the validator entities that verify this activity.\n→\nNetworks\nSui operates multiple networks including Mainnet for production, Testnet for staging, Devnet for developing new features, and Localnet for local development.\n→\nConsensus\nOverview of the Sui consensus mechanism.\n→\nTokenomics\nSui's tokenomics is designed to support the long-term financial needs of Web3. It uses the native SUI token as the currency of the network and to pay for the network's gas fees.\n→\nObject Model\nEverything on the Sui blockchain is an object that has metadata, a type of ownership, and a referencing scheme.\n→\nEpochs and Reconfiguration\nEpochs define time periods on Sui where the validator set remains unchanged. Reconfiguration adjusts network parameters at epoch boundaries.\n→\nCheckpoint Verification\nOn the Sui network, checkpoints define the history of the blockchain. Checkpoint verification is how full nodes and other clients guarantee their state is exactly the same as the Sui network.\n→\nStorage\nAn overview of Sui's storage architecture, including validator and full node storage requirements, pruning, snapshots, checkpoints, and how storage fees and rebates are calculated.\n→\nSecurity\nAssets on Sui, including coins and tokens, are types of objects, and can only be used by their owners unless otherwise defined according to predefined logic in a smart contract.\n→\nProtocol Upgrades\nThe Sui protocol, framework, and execution engine are frequently extended to include new functionality and bug fixes. The upgrade process ensures all clients use the same source.\n→","tokens":568,"crawled_at":1791194122435}
+{"id":10339,"url":"https://stack.olas.network/open-autonomy/control_flow","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Container Control Flow - Olas Stack Developer Documentation","text":"Application Control Flow\n\nInfo\n\nThis section is under review and will be updated soon.\n\nWithin a deployment, each individual agent instance in the AI agent manages:\n- a Tendermint Node\n- an ABCI application\n\nEach of the agent instances - containing the ABCI app - and the Tendermint node, are implemented as a Docker image which are deployed in a 1-2-1 relationship.\n\nThe Tendermint process is managed by a separate process, via a Flask server. The image containing the Flask server and Tendermint node are built on top of the valory/tendermint image.\n\nTendermint Image control flow.\n\nGentle Restart flow\n\nThis can be viewed in the logs as;\n\ntail -f /logs/node_0.txt\n\nMonitoring thread terminated\nTendermint process stopped\nTendermint process started\nMonitoring thread started\n\nHard Restart flow\n\nE[2022-05-11|13:45:41.355] abci.socketClient failed to connect to tcp://localhost:26658. Retrying after 3s... module=abci-client connection=query err=\"dial tcp 127.0.0.1:26658: connect: connection refused\"\nMonitoring thread terminated\nTendermint process stopped\nTendermint process started\nMonitoring thread started\nI[2022-05-11|13:45:41.450] Starting multiAppConn service module=proxy impl=multiAppConn\n\nSimultaneously, the flask server will display;\n\nI[2022-05-11|13:45:41.389] Removed existing address book module=main file=/tendermint/node1/config/addrbook.json\nI[2022-05-11|13:45:41.389] Removed all blockchain history module=main dir=/tendermint/node1/data\nI[2022-05-11|13:45:41.395] Reset private validator file to genesis state module=main keyFile=/tendermint/node1/config/priv_validator_key.json stateFile=/tendermint/node1/data/priv_validator_state.json\n\nAEA Network interruption Flow\n\nWhen we have an issue with the AEA losing connection to the Tendermint process, caused by failure of the AEA, the sudden closure of the TCP connection will trigger a restart of the Tendermint process.\n\nThis failure of connection could be caused by a re-scheduling of the pod to another host within the cluster, or by another unexpected restart of the AEA container.\n\nThis can be simulated by kill a running aea-process while running a docker-compose deployment.\n\nThis will interrupt the TCP connection between the AEA and the Tendermint process, managed by the Flask process. The typical behaviour for Tendermint upon such an event is to stop the module responsible for handling all http traffic. We watch for this event, and then restart the Tendermint process upon detecting it.\n\n# kill the aea\ndocker-compose kill abci0 && docker-compose up -d abci0\n\ntail -f deployments/persistent_data/logs/node_0.txt\n\nTendermint process stopped\nTendermint process started\nRestarted the HTTP RPC server, as a connection was dropped with message:\nE[2022-05-11|13:15:11.368] Stopping abci.socketClient for error: read message: EOF module=abci-client connection=consensus\n\nTendermint Network interruption Flow\n\nWhen we have an issue with the Tendermint process connecting to the AEA, the sudden closure of the TCP connection will trigger a restart of the tendermint process.\n\nThe effect of this on the AEA, can be demonstrated as so;\n\n# kill the node\ndocker-compose kill node0 && docker-compose up -d node0\n\nThe logs for the associated AEA show;\n\n[2022-05-11 13:35:31,336] [INFO] [agent] Entered in the 'validate_oracle' round for period 0\n[2022-05-11 13:35:31,338] [INFO] [agent] Entered in the 'validate_oracle' behaviour state\n[2022-05-11 13:35:31,776] [ERROR] [agent] an error occurred while reading a message: DecodeVarintError: could not decode varint. The message will be ignored.\n[2022-05-11 13:35:31,777] [INFO] [agent] connection at EOF, stop receiving loop.\n[2022-05-11 13:35:31,777] [ERROR] [agent] an error occurred while reading a message: DecodeVarintError: could not decode varint. The message will be ignored.\n[2022-05-11 13:35:31,777] [INFO] [agent] connection at EOF, stop receiving loop.\n[2022-05-11 13:35:31,777] [ERROR] [agent] an error occurred while reading a message: DecodeVarintError: could not decode varint. The message will be ignored.\n[2022-05-11 13:35:31,777] [INFO] [agent] connection at EOF, stop receiving loop.\n[2022-05-11 13:35:31,777] [ERROR] [agent] an error occurred while reading a message: DecodeVarintError: could not decode varint. The message will be ignored.\n[2022-05-11 13:35:31,777] [INFO] [agent] connection at EOF, stop receiving loop.\n[2022-05-11 13:35:35,083] [INFO] [agent] arrived block with timestamp: 2022-05-11 13:35:31.193869\n[2022-05-11 13:35:35,083] [INFO] [agent] current AbciApp time: 2022-05-11 13:35:29.879421\n[2022-05-11 13:35:35,127] [INFO] [agent] 'validate_oracle' round is done with event: Event.DONE\n[2022-05-11 13:35:35,128] [INFO] [agent] scheduling timeout of 7.0 seconds for event Event.ROUND_TIMEOUT with deadline 2022-05-11 13:35:38.193869\n\nNotice how the AEA continues as soon as it is able to re-establish a connection.","tokens":1219,"crawled_at":1791194126530}
+{"id":10340,"url":"https://docs.sui.io/develop/sui-architecture/object-model","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Object Model | Sui Documentation","text":"An objectObjectThe basic unit of storage on Sui. is a fundamental unit of storage on the network. Every resource, asset, or piece of data onchain is an object. Many other blockchains structure storage around accounts containing key-value stores. Sui's storage is structured around objects addressable by unique IDs onchain.\n\nEvery object has the following components:\n\nA globally unique ID.\n\nAn owner, which might be an addressAddressA unique, anonymous identity on a blockchain network. or an object.\n\nA version number that increments every time a change is made to the object.\n\nMetadata, such as the digest of the last transactionTransactionA number of commands that execute on inputs to define the result of the transaction. that used the object.\n\nObject types​\n\nThere are 3 types of objects:\n\nSui object: Every resource, asset, or piece of data. Sui objects are what transactions interact with, and are the building blocks for all onchain state.\n\nSui MoveMoveAn open source programming language used for all activity on Sui. object: An object defined using the Move language. To create a Move object, you must use sui::object::new to create a struct. This struct must have the key ability and include a field id: UID as the first defined field. The struct can also contain primitive types, such as integers and addresses, other objects, and non-object structs. This struct can be stored onchain as a Sui object.\n\nSui Move packagePackageSmart contracts on Sui.: A smart contract that can manipulate other objects. Each Move package is a set of Sui Move bytecode modulesModuleA component of a Move package that defines interaction with on-chain objects.. The modules within the package each have a name that's unique within the containing package. The combination of the package's onchain ID and the name of a module uniquely identifies the module. When you publish smart contracts to Sui, a package is the unit of publishing. After you publish a package object, it is immutable and can never be changed or removed. A package object can depend on other package objects that were previously published to Sui.\n\nReferring to objects​\n\nYou can refer to objects by their:\n\nID: The globally unique ID of the object. It is a stable identifier for the object that does not change and is useful for querying the current state of an object or describing which object was transferred between two addresses.\n\nVersioned ID: An (ID, version) pair. It describes the state of the object at a particular point in the object's history and is useful for asking what the value of the object was at some point in the past or determining how recently an object was updated.\n\nObject reference: An (ID, version, object digest) triple. The object digest is the hash of the object's contents and metadata. An object reference provides an authenticated view of the object at a particular point in the object's history. Transactions require object inputs to be specified through object references to ensure the transaction's sender and a validatorValidatorResponsible for executing tasks like staking, gas price references, and tallying rules. processing the transaction agree on the contents and metadata of the object.\n\nObject ownership​\n\nEvery object has an owner field that dictates who can use it in transactions. This field can contain one of the following options:\n\nAddress owned: Owned by a specific 32-byte address that is either an account address derived from a particular signature scheme or an object ID.\n\nImmutable: Not owned by anyone, so anyone can use it. It cannot be mutated, transferred, or deleted.\n\nConsensus-address owned / party: Owned by a single address but sequenced through consensusConsensusThe process by which the majority of nodes agree on the current state of the network. APIs expose this ownership with a ConsensusAddressOwner owner variant. Party objects are the public Move-facing way to create this ownership form using sui::transfer::party_transfer or sui::transfer::public_party_transfer.\n\nShared: Ownership is shared using the sui::transfer::share_object function and is accessible to everyone.\n\nWrapped: A data structure containing one struct type nested in another.\n\nObject metadata​\n\nEvery object has the following metadata:\n\nA 32-byte globally unique ID: Derived from the digest of the transaction that created the object and a counter encoding the number of IDs generated by the transaction.\n\nAn 8-byte unsigned integer version: Monotonically increases with every transaction that modifies it.\n\nA 32-byte transaction digest: Indicates the last transaction that included this object as an output.\n\nA 32-byte owner field: Indicates how this object can be accessed.\n\nIn addition to common metadata, objects have a category-specific, variable-sized contents field containing a Binary Canonical Serialization (BCS)-encoded payload:\n\nMove objects contain their Move type, whether the object can be transferred using public_transfer, and its fields.\n\nMove packages contain the bytecode modules in the package, a table identifying which versions of a package introduced each of its types (type origin table), and a table mapping each of its transitive dependencies to a specific version of that package to use (linkage table).\n\nThe transaction-object DAG: Relating objects and transactions​\n\nTransactions take objects as input, read, write, or mutate these inputs, then produce mutated or freshly created objects as output. Each object knows the hash of the last transaction that produced it as an output. A natural way to represent the relationship between objects and transactions is a directed acyclic graph (DAG) where nodes are transactions and directed edges go from transaction A to transaction B if an output object of A is an input object of B. They are labeled by the reference of the object in question, which specifies the exact version of the object created by A and used by B.\n\nThe root of this DAG is a genesis transaction that takes no inputs and produces the objects that exist in the system's initial state. You can extend the DAG by identifying mutable transaction outputs that have not yet been consumed by any committed transaction and sending a new transaction that takes these outputs and optionally, immutable transaction outputs as inputs.\n\nLive objects are available as input for a transaction. The global state maintained by Sui consists of the totality of such objects. The live objects for a particular Sui address A are all objects owned by A, along with all shared and immutable objects in the system.\n\nWhen this DAG contains all committed transactions in the system, it forms a complete and cryptographically auditable view of the system's state and history. In addition, you can use the scheme above to construct a DAG of the relevant history for a subset of transactions or objects, for example, the objects owned by a single address.\n\nLimits on transactions, objects, and data​\n\nSui has some limits on transactions and data used in transactions, such as a maximum size and number of objects used.\n\nThe ProtocolConfig struct in the sui-protocol-config crate itemizes these limits:\n\nClick to openlib.rs\ncrates/sui-protocol-config/src/lib.rs\n/// Constants that change the behavior of the protocol.\n///\n/// The value of each constant here must be fixed for a given protocol version. To change the value\n/// of a constant, advance the protocol version, and add support for it in `get_for_version` under\n/// the new version number.\n/// (below).\n///\n/// To add a new field to this struct, use the following procedure:\n/// - Advance the protocol version.\n/// - Add the field as a private `Option<T>` to the struct.\n/// - Initialize the field to `None` in prior protocol versions.\n/// - Initialize the field to `Some(val)` for your new protocol version.\n/// - Add a public getter that simply unwraps the field.\n/// - Two public getters of the form `field(&self) -> field_type`\n/// and `field_as_option(&self) -> Option<field_type>` will be automatically generated for you.\n/// Example for a field: `new_constant: Option<u64>`\n/// ```rust,ignore\n/// pub fn new_constant(&self) -> u64 {\n/// self.new_constant.expect(Self::CONSTANT_ERR_MSG)\n/// }\n/// pub fn new_constant_as_option(&self) -> Option<u64> {\n/// self.new_constant.expect(Self::CONSTANT_ERR_MSG)\n/// }\n/// ```\n/// With `pub fn new_constant(&self) -> u64`, if the constant is accessed in a protocol version\n/// in which it is not defined, the validator will crash. (Crashing is necessary because\n/// this type of error would almost always result in forking if not prevented here).\n/// If you don't want the validator to crash, you can use the\n/// `pub fn new_constant_as_option(&self) -> Option<u64>` getter, which will\n/// return `None` if the field is not defined at that version.\n/// - If you want a customized getter, you can add a method in the impl.\n#[skip_serializing_none]\n#[derive(Clone, Serialize, Debug, ProtocolConfigAccessors, ProtocolConfigOverride)]\npub struct ProtocolConfig {\npub version: ProtocolVersion,\n\n/// The chain this config was instantiated for. Unlike the other fields, this is not a\n/// versioned protocol constant: it identifies the network rather than describing protocol\n/// behavior, so it is intentionally excluded from serialization (and from the config\n/// snapshots) and is populated directly from the chain passed to `get_for_version`.\n#[serde(skip)]\nchain: Chain,\n\nfeature_flags: FeatureFlags,\n\n// ==== Transaction input limits ====\n/// Maximum serialized size of a transaction (in bytes).\nmax_tx_size_bytes: Option<u64>,\n\n/// Maximum number of input objects to a transaction. Enforced by the transaction input checker\nmax_input_objects: Option<u64>,\n\n/// Max size of objects a transaction can write to disk after completion. Enforce by the Sui adapter.\n/// This is the sum of the serialized size of all objects written to disk.\n/// The max size of individual objects on the other hand is `max_move_object_size`.\nmax_size_written_objects: Option<u64>,\n/// Max size of objects a system transaction can write to disk after completion. Enforce by the Sui adapter.\n/// Similar to `max_size_written_objects` but for system transactions.\nmax_size_written_objects_system_tx: Option<u64>,\n\n/// Maximum size of serialized transaction effects.\nmax_serialized_tx_effects_size_bytes: Option<u64>,\n\n/// Maximum size of serialized transaction effects for system transactions.\nmax_serialized_tx_effects_size_bytes_system_tx: Option<u64>,\n\n/// Maximum number of gas payment objects for a transaction.\nmax_gas_payment_objects: Option<u32>,\n\n/// Maximum number of modules in a Publish transaction.\nmax_modules_in_publish: Option<u32>,\n\n/// Maximum number of transitive dependencies in a package when publishing.\nmax_package_dependencies: Option<u32>,\n\n/// Maximum number of arguments in a move call or a ProgrammableTransaction's\n/// TransferObjects command.\nmax_arguments: Option<u32>,\n\n/// Maximum number of total type arguments, computed recursively.\nmax_type_arguments: Option<u32>,\n\n/// Maximum depth of an individual type argument.\nmax_type_argument_depth: Option<u32>,\n\n/// Maximum size of a Pure CallArg.\nmax_pure_argument_size: Option<u32>,\n\n/// Maximum number of Commands in a ProgrammableTransaction.\nmax_programmable_tx_commands: Option<u32>,\n\n// ==== Move VM, Move bytecode verifier, and execution limits ===\n/// Maximum Move bytecode version the VM understands. All older versions are accepted.\nmove_binary_format_version: Option<u32>,\nmin_move_binary_format_version: Option<u32>,\n\n/// Configuration controlling binary tables size.\nbinary_module_handles: Option<u16>,\nbinary_struct_handles: Option<u16>,\nbinary_function_handles: Option<u16>,\nbinary_function_instantiations: Option<u16>,\nbinary_signatures: Option<u16>,\nbinary_constant_pool: Option<u16>,\nbinary_identifiers: Option<u16>,\nbinary_address_identifiers: Option<u16>,\nbinary_struct_defs: Option<u16>,\nbinary_struct_def_instantiations: Option<u16>,\nbinary_function_defs: Option<u16>,\nbinary_field_handles: Option<u16>,\nbinary_field_instantiations: Option<u16>,\nbinary_friend_decls: Option<u16>,\nbinary_enum_defs: Option<u16>,\nbinary_enum_def_instantiations: Option<u16>,\nbinary_variant_handles: Option<u16>,\nbinary_variant_instantiation_handles: Option<u16>,\n\n/// Maximum size of the `contents` part of an object, in bytes. Enforced by the Sui adapter when effects are produced.\nmax_move_object_size: Option<u64>,\n\n// TODO: Option<increase to 500 KB. currently, publishing a package > 500 KB exceeds the max computation gas cost\n/// Maximum size of a Move package object, in bytes. Enforced by the Sui adapter at the end of a publish transaction.\nmax_move_package_size: Option<u64>,\n\n/// Max number of publish or upgrade commands allowed in a programmable transaction block.\nmax_publish_or_upgrade_per_ptb: Option<u64>,\n\n/// Maximum gas budget in MIST that a transaction can use.\nmax_tx_gas: Option<u64>,\n\n/// Maximum amount of the proposed gas price in MIST (defined in the transaction).\nmax_gas_price: Option<u64>,\n\n/// For aborted txns, we cap the gas price at a factor of RGP. This lowers risk of setting higher priority gas price\n/// if there's a chance the txn will abort.\nmax_gas_price_rgp_factor_for_aborted_transactions: Option<u64>,\n\n/// The max computation bucket for gas. This is the max that can be charged for computation.\nmax_gas_computation_bucket: Option<u64>,\n\n// Define the value used to round up computation gas charges\ngas_rounding_step: Option<u64>,\n\n/// Maximum number of nested loops. Enforced by the Move bytecode verifier.\nmax_loop_depth: Option<u64>,\n\n/// Maximum number of type arguments that can be bound to generic type parameters. Enforced by the Move bytecode verifier.\nmax_generic_instantiation_length: Option<u64>,\n\n/// Maximum number of parameters that a Move function can have. Enforced by the Move bytecode verifier.\nmax_function_parameters: Option<u64>,\n\n/// Maximum number of basic blocks that a Move function can have. Enforced by the Move bytecode verifier.\nmax_basic_blocks: Option<u64>,\n\n/// Maximum stack size value. Enforced by the Move bytecode verifier.\nmax_value_stack_size: Option<u64>,\n\n/// Maximum number of \"type nodes\", a metric for how big a SignatureToken will be when expanded into a fully qualified type. Enforced by the Move bytecode verifier.\nmax_type_nodes: Option<u64>,\n\n/// Maximum number of \"type nodes\" that can be instantiated in a single function.\nmax_generic_instantiation_type_nodes_per_function: Option<u64>,\n\n/// Maximum number of \"type nodes\" that can be instantiated in a module.\nmax_generic_instantiation_type_nodes_per_module: Option<u64>,\n\n/// Maximum number of \"type nodes\" allowed in an accumulator.\nmax_accumulator_type_nodes: Option<u64>,\n\n/// Maximum number of push instructions in one function. Enforced by the Move bytecode verifier.\nmax_push_size: Option<u64>,\n\n/// Maximum number of struct definitions in a module. Enforced by the Move bytecode verifier.\nmax_struct_definitions: Option<u64>,\n\n/// Maximum number of function definitions in a module. Enforced by the Move bytecode verifier.\nmax_function_definitions: Option<u64>,\n\n/// Maximum number of fields allowed in a struct definition. Enforced by the Move bytecode verifier.\nmax_fields_in_struct: Option<u64>,\n\n/// Maximum dependency depth. Enforced by the Move linker when loading dependent modules.\nmax_dependency_depth: Option<u64>,\n\n/// Maximum number of Move events that a single transaction can emit. Enforced by the VM during execution.\nmax_num_event_emit: Option<u64>,\n\n/// Maximum number of new IDs that a single transaction can create. Enforced by the VM during execution.\nmax_num_new_move_object_ids: Option<u64>,\n\n/// Maximum number of new IDs that a single system transaction can create. Enforced by the VM during execution.\nmax_num_new_move_object_ids_system_tx: Option<u64>,\n\n/// Maximum number of IDs that a single transaction can delete. Enforced by the VM during execution.\nmax_num_deleted_move_object_ids: Option<u64>,\n\n/// Maximum number of IDs that a single system transaction can delete. Enforced by the VM during execution.\nmax_num_deleted_move_object_ids_system_tx: Option<u64>,\n\n/// Maximum number of IDs that a single transaction can transfer. Enforced by the VM during execution.\nmax_num_transferred_move_object_ids: Option<u64>,\n\n/// Maximum number of IDs that a single system transaction can transfer. Enforced by the VM during execution.\nmax_num_transferred_move_object_ids_system_tx: Option<u64>,\n\n/// Maximum size of a Move user event. Enforced by the VM during execution.\nmax_event_emit_size: Option<u64>,\n\n/// Maximum size of a Move user event. Enforced by the VM during execution.\nmax_event_emit_size_total: Option<u64>,\n\n/// Maximum length of a vector in Move. Enforced by the VM during execution, and for constants, by the verifier.\nmax_move_vector_len: Option<u64>,\n\n/// Maximum length of an `Identifier` in Move. Enforced by the bytecode verifier at signing.\nmax_move_identifier_len: Option<u64>,\n\n/// Maximum depth of a Move value within the VM.\nmax_move_value_depth: Option<u64>,\n\n/// Maximum number of bytes a single package's arena may allocate when the package is loaded\n/// into the VM. If unset, the VM uses its built-in default.\npackage_arena_size_in_bytes: Option<u64>,\n\n/// Maximum number of variants in an enum. Enforced by the bytecode verifier at signing.\nmax_move_enum_variants: Option<u64>,\n\n/// Maximum number of back edges in Move function. Enforced by the bytecode verifier at signing.\nmax_back_edges_per_function: Option<u64>,\n\n/// Maximum number of back edges in Move module. Enforced by the bytecode verifier at signing.\nmax_back_edges_per_module: Option<u64>,\n\n/// Maximum number of meter `ticks` spent verifying a Move function. Enforced by the bytecode verifier at signing.\nmax_verifier_meter_ticks_per_function: Option<u64>,\n\n/// Maximum number of meter `ticks` spent verifying a Move module. Enforced by the bytecode verifier at signing.\nmax_meter_ticks_per_module: Option<u64>,\n\n/// Maximum number of meter `ticks` spent verifying a Move package. Enforced by the bytecode verifier at signing.\nmax_meter_ticks_per_package: Option<u64>,\n\n// === Object runtime internal operation limits ====\n// These affect dynamic fields\n/// Maximum number of cached objects in the object runtime ObjectStore. Enforced by object runtime during execution\nobject_runtime_max_num_cached_objects: Option<u64>,\n\n/// Maximum number of cached objects in the object runtime ObjectStore in system transaction. Enforced by object runtime during execution\nobject_runtime_max_num_cached_objects_system_tx: Option<u64>,\n\n/// Maximum number of stored objects accessed by object runtime ObjectStore. Enforced by object runtime during execution\nobject_runtime_max_num_store_entries: Option<u64>,\n\n/// Maximum number of stored objects accessed by object runtime ObjectStore in system transaction. Enforced by object runtime during execution\nobject_runtime_max_num_store_entries_system_tx: Option<u64>,\n\n// === Execution gas costs ====\n/// Base cost for any Sui transaction\nbase_tx_cost_fixed: Option<u64>,\n\n/// Additional cost for a transaction that publishes a package\n/// i.e., the base cost of such a transaction is base_tx_cost_fixed + package_publish_cost_fixed\npackage_publish_cost_fixed: Option<u64>,\n\n/// Cost per byte of a Move call transaction\n/// i.e., the cost of such a transaction is base_cost + (base_tx_cost_per_byte * size)\nbase_tx_cost_per_byte: Option<u64>,\n\n/// Cost per byte for a transaction that publishes a package\npackage_publish_cost_per_byte: Option<u64>,\n\n// Per-byte cost of reading an object during transaction execution\nobj_access_cost_read_per_byte: Option<u64>,\n\n// Per-byte cost of writing an object during transaction execution\nobj_access_cost_mutate_per_byte: Option<u64>,\n\n// Per-byte cost of deleting an object during transaction execution\nobj_access_cost_delete_per_byte: Option<u64>,\n\n/// Per-byte cost charged for each input object to a transaction.\n/// Meant to approximate the cost of checking locks for each object\n// TODO: Option<I'm not sure that this cost makes sense. Checking locks is \"free\"\n// in the sense that an invalid tx that can never be committed/pay gas can\n// force validators to check an arbitrary number of locks. If those checks are\n// \"free\" for invalid transactions, why charge for them in valid transactions\n// TODO: Option<if we keep this, I think we probably want it to be a fixed cost rather\n// than a per-byte cost. checking an object lock should not require loading an\n// entire object, just consulting an ID -> tx digest map\nobj_access_cost_verify_per_byte: Option<u64>,\n\n// Maximal nodes which are allowed when converting to a type layout.\nmax_type_to_layout_nodes: Option<u64>,\n\n// Maximal size in bytes that a PTB value can be\nmax_ptb_value_size: Option<u64>,\n\n// === Gas version. gas model ===\n/// Gas model version, what code we are using to charge gas\ngas_model_version: Option<u64>,\n\n// === Storage gas costs ===\n/// Per-byte cost of storing an object in the Sui global object store. Some of this cost may be refundable if the object is later freed\nobj_data_cost_refundable: Option<u64>,\n\n// Per-byte cost of storing an object in the Sui transaction log (e.g., in CertifiedTransactionEffects)\n// This depends on the size of various fields including the effects\n// TODO: Option<I don't fully understand this^ and more details would be useful\nobj_metadata_cost_non_refundable: Option<u64>,\n\n// === Tokenomics ===\n\n// TODO: Option<this should be changed to u64.\n/// Sender of a txn that touches an object will get this percent of the storage rebate back.\n/// In basis point.\nstorage_rebate_rate: Option<u64>,\n\n/// 5% of the storage fund's share of rewards are reinvested into the storage fund.\n/// In basis point.\nstorage_fund_reinvest_rate: Option<u64>,\n\n/// The share of rewards that will be slashed and redistributed is 50%.\n/// In basis point.\nreward_slashing_rate: Option<u64>,\n\n/// Unit gas price, Mist per internal gas unit.\nstorage_gas_price: Option<u64>,\n\n/// Per-object storage cost for accumulator objects, used during end-of-epoch accounting.\naccumulator_object_storage_cost: Option<u64>,\n\n// === Core Protocol ===\n/// Max number of transactions per checkpoint.\n/// Note that this is a protocol constant and not a config as validators must have this set to\n/// the same value, otherwise they *will* fork.\nmax_transactions_per_checkpoint: Option<u64>,\n\n/// Max size of a checkpoint in bytes.\n/// Note that this is a protocol constant and not a config as validators must have this set to\n/// the same value, otherwise they *will* fork.\nmax_checkpoint_size_bytes: Option<u64>,\n\n/// A protocol upgrade always requires 2f+1 stake to agree. We support a buffer of additional\n/// stake (as a fraction of f, expressed in basis points) that is required before an upgrade\n/// can happen automatically. 10000bps would indicate that complete unanimity is required (all\n/// 3f+1 must vote), while 0bps would indicate that 2f+1 is sufficient.\nbuffer_stake_for_protocol_upgrade_bps: Option<u64>,\n\n// === Native Function Costs ===\n\n// `address` module\n// Cost params for the Move native function `address::from_bytes(bytes: vector<u8>)`\naddress_from_bytes_cost_base: Option<u64>,\n// Cost params for the Move native function `address::to_u256(address): u256`\naddress_to_u256_cost_base: Option<u64>,\n// Cost params for the Move native function `address::from_u256(u256): address`\naddress_from_u256_cost_base: Option<u64>,\n\n// `config` module\n// Cost params for the Move native function `read_setting_impl<Name: copy + drop + store,\n// SettingValue: key + store, SettingDataValue: store, Value: copy + drop + store,\n// >(config: address, name: address, current_epoch: u64): Option<Value>`\nconfig_read_setting_impl_cost_base: Option<u64>,\nconfig_read_setting_impl_cost_per_byte: Option<u64>,\n\npackage_original_package_id_impl_cost_base: Option<u64>,\npackage_original_package_id_impl_cost_per_byte: Option<u64>,\n\n// `dynamic_field` module\n// Cost params for the Move native function `hash_type_and_key<K: copy + drop + store>(parent: address, k: K): address`\ndynamic_field_hash_type_and_key_cost_base: Option<u64>,\ndynamic_field_hash_type_and_key_type_cost_per_byte: Option<u64>,\ndynamic_field_hash_type_and_key_value_cost_per_byte: Option<u64>,\ndynamic_field_hash_type_and_key_type_tag_cost_per_byte: Option<u64>,\n// Cost params for the Move native function `add_child_object<Child: key>(parent: address, child: Child)`\ndynamic_field_add_child_object_cost_base: Option<u64>,\ndynamic_field_add_child_object_type_cost_per_byte: Option<u64>,\ndynamic_field_add_child_object_value_cost_per_byte: Option<u64>,\ndynamic_field_add_child_object_struct_tag_cost_per_byte: Option<u64>,\n// Cost params for the Move native function `borrow_child_object_mut<Child: key>(parent: &mut UID, id: address): &mut Child`\ndynamic_field_borrow_child_object_cost_base: Option<u64>,\ndynamic_field_borrow_child_object_child_ref_cost_per_byte: Option<u64>,\ndynamic_field_borrow_child_object_type_cost_per_byte: Option<u64>,\n// Cost params for the Move native function `remove_child_object<Child: key>(parent: address, id: address): Child`\ndynamic_field_remove_child_object_cost_base: Option<u64>,\ndynamic_field_remove_child_object_child_cost_per_byte: Option<u64>,\ndynamic_field_remove_child_object_type_cost_per_byte: Option<u64>,\n// Cost params for the Move native function `has_child_object(parent: address, id: address): bool`\ndynamic_field_has_child_object_cost_base: Option<u64>,\n// Cost params for the Move native function `has_child_object_with_ty<Child: key>(parent: address, id: address): bool`\ndynamic_field_has_child_object_with_ty_cost_base: Option<u64>,\ndynamic_field_has_child_object_with_ty_type_cost_per_byte: Option<u64>,\ndynamic_field_has_child_object_with_ty_type_tag_cost_per_byte: Option<u64>,\n\n// `scratch` module\n// Cost params for the Move native function `add_impl<V: drop>(key: address, value: V)`\nscratch_add_cost_base: Option<u64>,\n// Cost params for the Move native function `read_impl<V: copy + drop>(key: address): V`\nscratch_read_cost_base: Option<u64>,\nscratch_read_value_cost: Option<u64>,\n// Cost params for the Move native function `remove_impl<V: drop>(key: address): V`\nscratch_remove_cost_base: Option<u64>,\n// Cost params for the Move native function `exists_impl(key: address): bool`\nscratch_exists_cost_base: Option<u64>,\n// Cost params for the Move native function `exists_with_type_impl<V: drop>(key: address): bool`\nscratch_exists_with_type_cost_base: Option<u64>,\nscratch_exists_with_type_type_cost: Option<u64>,\n// Maximum number of entries in the per-transaction `sui::scratch` store.\nmax_scratch_pad_size: Option<u64>,\n\n// `event` module\n// Cost params for the Move native function `event::emit<T: copy + drop>(event: T)`\nevent_emit_cost_base: Option<u64>,\nevent_emit_value_size_derivation_cost_per_byte: Option<u64>,\nevent_emit_tag_size_derivation_cost_per_byte: Option<u64>,\nevent_emit_output_cost_per_byte: Option<u64>,\nevent_emit_auth_stream_cost: Option<u64>,\n\n// `funds_accumulator` module\n// Base cost for reserving object funds for withdrawal.\nreserve_object_funds_for_withdrawal_cost_base: Option<u64>,\n// Cost of loading an object's settled balance on the first withdrawal for an owner and type.\nreserve_object_funds_for_withdrawal_cold_read_cost: Option<u64>,\n\n// `object` module\n// Cost params for the Move native function `borrow_uid<T: key>(obj: &T): &UID`\nobject_borrow_uid_cost_base: Option<u64>,\n// Cost params for the Move native function `delete_impl(id: address)`\nobject_delete_impl_cost_base: Option<u64>,\n// Cost params for the Move native function `record_new_uid(id: address)`\nobject_record_new_uid_cost_base: Option<u64>,\n// Cost params for the Move native function\n// `record_new_uid_from_hash(parent: address, bytes: address)`\nobject_record_new_uid_from_hash_cost_base: Option<u64>,\n\n// Transfer\n// Cost params for the Move native function `transfer_impl<T: key>(obj: T, recipient: address)`\ntransfer_transfer_internal_cost_base: Option<u64>,\n// Cost params for the Move native function `party_transfer_impl<T: key>(obj: T, party_members: vector<address>)`\ntransfer_party_transfer_internal_cost_base: Option<u64>,\n// Cost params for the Move native function `freeze_object<T: key>(obj: T)`\ntransfer_freeze_object_cost_base: Option<u64>,\n// Cost params for the Move native function `share_object<T: key>(obj: T)`\ntransfer_share_object_cost_base: Option<u64>,\n// Cost params for the Move native function\n// `receive_object<T: key>(p: &mut UID, recv: Receiving<T>T)`\ntransfer_receive_object_cost_base: Option<u64>,\ntransfer_receive_object_cost_per_byte: Option<u64>,\ntransfer_receive_object_type_cost_per_byte: Option<u64>,\n\n// TxContext\n// Cost params for the Move native function `transfer_impl<T: key>(obj: T, recipient: address)`\ntx_context_derive_id_cost_base: Option<u64>,\ntx_context_fresh_id_cost_base: Option<u64>,\ntx_context_sender_cost_base: Option<u64>,\ntx_context_epoch_cost_base: Option<u64>,\ntx_context_epoch_timestamp_ms_cost_base: Option<u64>,\ntx_context_sponsor_cost_base: Option<u64>,\ntx_context_rgp_cost_base: Option<u64>,\ntx_context_gas_price_cost_base: Option<u64>,\ntx_context_gas_budget_cost_base: Option<u64>,\ntx_context_ids_created_cost_base: Option<u64>,\ntx_context_replace_cost_base: Option<u64>,\n\n// Types\n// Cost params for the Move native function `is_one_time_witness<T: drop>(_: &T): bool`\ntypes_is_one_time_witness_cost_base: Option<u64>,\ntypes_is_one_time_witness_type_tag_cost_per_byte: Option<u64>,\ntypes_is_one_time_witness_type_cost_per_byte: Option<u64>,\n\n// Validator\n// Cost params for the Move native function `validate_metadata_bcs(metadata: vector<u8>)`\nvalidator_validate_metadata_cost_base: Option<u64>,\nvalidator_validate_metadata_data_cost_per_byte: Option<u64>,\n\n// Crypto natives\ncrypto_invalid_arguments_cost: Option<u64>,\n// bls12381::bls12381_min_sig_verify\nbls12381_bls12381_min_sig_verify_cost_base: Option<u64>,\nbls12381_bls12381_min_sig_verify_msg_cost_per_byte: Option<u64>,\nbls12381_bls12381_min_sig_verify_msg_cost_per_block: Option<u64>,\n\n// bls12381::bls12381_min_pk_verify\nbls12381_bls12381_min_pk_verify_cost_base: Option<u64>,\nbls12381_bls12381_min_pk_verify_msg_cost_per_byte: Option<u64>,\nbls12381_bls12381_min_pk_verify_msg_cost_per_block: Option<u64>,\n\n// ecdsa_k1::ecrecover\necdsa_k1_ecrecover_keccak256_cost_base: Option<u64>,\necdsa_k1_ecrecover_keccak256_msg_cost_per_byte: Option<u64>,\necdsa_k1_ecrecover_keccak256_msg_cost_per_block: Option<u64>,\necdsa_k1_ecrecover_sha256_cost_base: Option<u64>,\necdsa_k1_ecrecover_sha256_msg_cost_per_byte: Option<u64>,\necdsa_k1_ecrecover_sha256_msg_cost_per_block: Option<u64>,\n\n// ecdsa_k1::decompress_pubkey\necdsa_k1_decompress_pubkey_cost_base: Option<u64>,\n\n// ecdsa_k1::secp256k1_verify\necdsa_k1_secp256k1_verify_keccak256_cost_base: Option<u64>,\necdsa_k1_secp256k1_verify_keccak256_msg_cost_per_byte: Option<u64>,\necdsa_k1_secp256k1_verify_keccak256_msg_cost_per_block: Option<u64>,\necdsa_k1_secp256k1_verify_sha256_cost_base: Option<u64>,\necdsa_k1_secp256k1_verify_sha256_msg_cost_per_byte: Option<u64>,\necdsa_k1_secp256k1_verify_sha256_msg_cost_per_block: Option<u64>,\n\n// ecdsa_r1::ecrecover\necdsa_r1_ecrecover_keccak256_cost_base: Option<u64>,\necdsa_r1_ecrecover_keccak256_msg_cost_per_byte: Option<u64>,\necdsa_r1_ecrecover_keccak256_msg_cost_per_block: Option<u64>,\necdsa_r1_ecrecover_sha256_cost_base: Option<u64>,\necdsa_r1_ecrecover_sha256_msg_cost_per_byte: Option<u64>,\necdsa_r1_ecrecover_sha256_msg_cost_per_block: Option<u64>,\n\n// ecdsa_r1::secp256k1_verify\necdsa_r1_secp256r1_verify_keccak256_cost_base: Option<u64>,\necdsa_r1_secp256r1_verify_keccak256_msg_cost_per_byte: Option<u64>,\necdsa_r1_secp256r1_verify_keccak256_msg_cost_per_block: Option<u64>,\necdsa_r1_secp256r1_verify_sha256_cost_base: Option<u64>,\necdsa_r1_secp256r1_verify_sha256_msg_cost_per_byte: Option<u64>,\necdsa_r1_secp256r1_verify_sha256_msg_cost_per_block: Option<u64>,\n\n// ecvrf::verify\necvrf_ecvrf_verify_cost_base: Option<u64>,\necvrf_ecvrf_verify_alpha_string_cost_per_byte: Option<u64>,\necvrf_ecvrf_verify_alpha_string_cost_per_block: Option<u64>,\n\n// ed25519\ned25519_ed25519_verify_cost_base: Option<u64>,\ned25519_ed25519_verify_msg_cost_per_byte: Option<u64>,\ned25519_ed25519_verify_msg_cost_per_block: Option<u64>,\n\n// groth16::prepare_verifying_key\ngroth16_prepare_verifying_key_bls12381_cost_base: Option<u64>,\ngroth16_prepare_verifying_key_bn254_cost_base: Option<u64>,\n\n// groth16::verify_groth16_proof_internal\ngroth16_verify_groth16_proof_internal_bls12381_cost_base: Option<u64>,\ngroth16_verify_groth16_proof_internal_bls12381_cost_per_public_input: Option<u64>,\ngroth16_verify_groth16_proof_internal_bn254_cost_base: Option<u64>,\ngroth16_verify_groth16_proof_internal_bn254_cost_per_public_input: Option<u64>,\ngroth16_verify_groth16_proof_internal_public_input_cost_per_byte: Option<u64>,\n\n// hash::blake2b256\nhash_blake2b256_cost_base: Option<u64>,\nhash_blake2b256_data_cost_per_byte: Option<u64>,\nhash_blake2b256_data_cost_per_block: Option<u64>,\n\n// hash::keccak256\nhash_keccak256_cost_base: Option<u64>,\nhash_keccak256_data_cost_per_byte: Option<u64>,\nhash_keccak256_data_cost_per_block: Option<u64>,\n\n// poseidon::poseidon_bn254\nposeidon_bn254_cost_base: Option<u64>,\nposeidon_bn254_cost_per_block: Option<u64>,\n\n// group_ops\ngroup_ops_bls12381_decode_scalar_cost: Option<u64>,\ngroup_ops_bls12381_decode_g1_cost: Option<u64>,\ngroup_ops_bls12381_decode_g2_cost: Option<u64>,\ngroup_ops_bls12381_decode_gt_cost: Option<u64>,\ngroup_ops_bls12381_scalar_add_cost: Option<u64>,\ngroup_ops_bls12381_g1_add_cost: Option<u64>,\ngroup_ops_bls12381_g2_add_cost: Option<u64>,\ngroup_ops_bls12381_gt_add_cost: Option<u64>,\ngroup_ops_bls12381_scalar_sub_cost: Option<u64>,\ngroup_ops_bls12381_g1_sub_cost: Option<u64>,\ngroup_ops_bls12381_g2_sub_cost: Option<u64>,\ngroup_ops_bls12381_gt_sub_cost: Option<u64>,\ngroup_ops_bls12381_scalar_mul_cost: Option<u64>,\ngroup_ops_bls12381_g1_mul_cost: Option<u64>,\ngroup_ops_bls12381_g2_mul_cost: Option<u64>,\ngroup_ops_bls12381_gt_mul_cost: Option<u64>,\ngroup_ops_bls12381_scalar_div_cost: Option<u64>,\ngroup_ops_bls12381_g1_div_cost: Option<u64>,\ngroup_ops_bls12381_g2_div_cost: Option<u64>,\ngroup_ops_bls12381_gt_div_cost: Option<u64>,\ngroup_ops_bls12381_g1_hash_to_base_cost: Option<u64>,\ngroup_ops_bls12381_g2_hash_to_base_cost: Option<u64>,\ngroup_ops_bls12381_g1_hash_to_cost_per_byte: Option<u64>,\ngroup_ops_bls12381_g2_hash_to_cost_per_byte: Option<u64>,\ngroup_ops_bls12381_g1_msm_base_cost: Option<u64>,\ngroup_ops_bls12381_g2_msm_base_cost: Option<u64>,\ngroup_ops_bls12381_g1_msm_base_cost_per_input: Option<u64>,\ngroup_ops_bls12381_g2_msm_base_cost_per_input: Option<u64>,\ngroup_ops_bls12381_msm_max_len: Option<u32>,\ngroup_ops_bls12381_pairing_cost: Option<u64>,\ngroup_ops_bls12381_g1_to_uncompressed_g1_cost: Option<u64>,\ngroup_ops_bls12381_uncompressed_g1_to_g1_cost: Option<u64>,\ngroup_ops_bls12381_uncompressed_g1_sum_base_cost: Option<u64>,\ngroup_ops_bls12381_uncompressed_g1_sum_cost_per_term: Option<u64>,\ngroup_ops_bls12381_uncompressed_g1_sum_max_terms: Option<u64>,\n\ngroup_ops_ristretto_decode_scalar_cost: Option<u64>,\ngroup_ops_ristretto_decode_point_cost: Option<u64>,\ngroup_ops_ristretto_scalar_add_cost: Option<u64>,\ngroup_ops_ristretto_point_add_cost: Option<u64>,\ngroup_ops_ristretto_scalar_sub_cost: Option<u64>,\ngroup_ops_ristretto_point_sub_cost: Option<u64>,\ngroup_ops_ristretto_scalar_mul_cost: Option<u64>,\ngroup_ops_ristretto_point_mul_cost: Option<u64>,\ngroup_ops_ristretto_scalar_div_cost: Option<u64>,\ngroup_ops_ristretto_point_div_cost: Option<u64>,\n\nverify_bulletproofs_ristretto255_base_cost: Option<u64>,\nverify_bulletproofs_ristretto255_cost_per_bit_and_commitment: Option<u64>,\n// Upper bound on batch size * range in bits for a bulletproofs range proof. Defaults to 512\n// when unset.\nmax_bulletproofs_total_bits: Option<u64>,\n\n// hmac::hmac_sha3_256\nhmac_hmac_sha3_256_cost_base: Option<u64>,\nhmac_hmac_sha3_256_input_cost_per_byte: Option<u64>,\nhmac_hmac_sha3_256_input_cost_per_block: Option<u64>,\n\n// zklogin::check_zklogin_id\ncheck_zklogin_id_cost_base: Option<u64>,\n// zklogin::check_zklogin_issuer\ncheck_zklogin_issuer_cost_base: Option<u64>,\n\nvdf_verify_vdf_cost: Option<u64>,\nvdf_hash_to_input_cost: Option<u64>,\n\n// nitro_attestation::load_nitro_attestation\nnitro_attestation_parse_base_cost: Option<u64>,\nnitro_attestation_parse_cost_per_byte: Option<u64>,\nnitro_attestation_verify_base_cost: Option<u64>,\nnitro_attestation_verify_cost_per_cert: Option<u64>,\n\n// Stdlib costs\nbcs_per_byte_serialized_cost: Option<u64>,\nbcs_legacy_min_output_size_cost: Option<u64>,\nbcs_failure_cost: Option<u64>,\n\nhash_sha2_256_base_cost: Option<u64>,\nhash_sha2_256_per_byte_cost: Option<u64>,\nhash_sha2_256_legacy_min_input_len_cost: Option<u64>,\nhash_sha3_256_base_cost: Option<u64>,\nhash_sha3_256_per_byte_cost: Option<u64>,\nhash_sha3_256_legacy_min_input_len_cost: Option<u64>,\ntype_name_get_base_cost: Option<u64>,\ntype_name_get_per_byte_cost: Option<u64>,\ntype_name_id_base_cost: Option<u64>,\n\nstring_check_utf8_base_cost: Option<u64>,\nstring_check_utf8_per_byte_cost: Option<u64>,\nstring_is_char_boundary_base_cost: Option<u64>,\nstring_sub_string_base_cost: Option<u64>,\nstring_sub_string_per_byte_cost: Option<u64>,\nstring_index_of_base_cost: Option<u64>,\nstring_index_of_per_byte_pattern_cost: Option<u64>,\nstring_index_of_per_byte_searched_cost: Option<u64>,\n\nvector_empty_base_cost: Option<u64>,\nvector_length_base_cost: Option<u64>,\nvector_push_back_base_cost: Option<u64>,\nvector_push_back_legacy_per_abstract_memory_unit_cost: Option<u64>,\nvector_borrow_base_cost: Option<u64>,\nvector_pop_back_base_cost: Option<u64>,\nvector_destroy_empty_base_cost: Option<u64>,\nvector_swap_base_cost: Option<u64>,\ndebug_print_base_cost: Option<u64>,\ndebug_print_stack_trace_base_cost: Option<u64>,\n\n// ==== Ephemeral (consensus only) params deleted ====\n//\n// Const params for consensus scoring decision\n// The scaling factor property for the MED outlier detection\n// scoring_decision_mad_divisor: Option<f64>,\n// The cutoff value for the MED outlier detection\n// scoring_decision_cutoff_value: Option<f64>,\n/// === Execution Version ===\n// custom_setter: see `set_execution_version_for_testing`, which forbids downgrades.\n#[custom_setter]\nexecution_version: Option<u64>,\n\n// Dictates the threshold (percentage of stake) that is used to calculate the \"bad\" nodes to be\n// swapped when creating the consensus schedule. The values should be of the range [0 - 33]. Anything\n// above 33 (f) will not be allowed.\nconsensus_bad_nodes_stake_threshold: Option<u64>,\n\nmax_jwk_votes_per_validator_per_epoch: Option<u64>,\n// The maximum age of a JWK in epochs before it is removed from the AuthenticatorState object.\n// Applied at the end of an epoch as a delta from the new epoch value, so setting this to 1\n// will cause the new epoch to start with JWKs from the previous epoch still valid.\nmax_age_of_jwk_in_epochs: Option<u64>,\n\n// === random beacon ===\n/// Maximum allowed precision loss when reducing voting weights for the random beacon\n/// protocol.\nrandom_beacon_reduction_allowed_delta: Option<u16>,\n\n/// Minimum number of shares below which voting weights will not be reduced for the\n/// random beacon protocol.\nrandom_beacon_reduction_lower_bound: Option<u32>,\n\n/// Consensus Round after which DKG should be aborted and randomness disabled for\n/// the epoch, if it hasn't already completed.\nrandom_beacon_dkg_timeout_round: Option<u32>,\n\n/// Minimum interval between consecutive rounds of generated randomness.\nrandom_beacon_min_round_interval_ms: Option<u64>,\n\n/// Version of the random beacon DKG protocol.\n/// 0 was deprecated (and currently not supported), 1 is the default version.\nrandom_beacon_dkg_version: Option<u64>,\n\n/// The maximum serialised transaction size (in bytes) accepted by consensus. That should be bigger than the\n/// `max_tx_size_bytes` with some additional headroom.\nconsensus_max_transaction_size_bytes: Option<u64>,\n/// The maximum size of transactions included in a consensus block.\nconsensus_max_transactions_in_block_bytes: Option<u64>,\n/// The maximum number of transactions included in a consensus block.\nconsensus_max_num_transactions_in_block: Option<u64>,\n\n/// The maximum number of rounds where transaction voting is allowed.\nconsensus_voting_rounds: Option<u32>,\n\n/// DEPRECATED. Do not use.\nmax_accumulated_txn_cost_per_object_in_narwhal_commit: Option<u64>,\n\n/// The max number of consensus rounds a transaction can be deferred due to shared object congestion.\n/// Transactions will be cancelled after this many rounds.\nmax_deferral_rounds_for_congestion_control: Option<u64>,\n\n/// Time after the scheduled epoch end (`next_reconfiguration_timestamp_ms`) at which epoch\n/// close stops waiting for deferred transactions to drain: the epoch is closed even if\n/// deferred transactions remain unscheduled. They are abandoned and can be resubmitted in the\n/// next epoch. When unset, epoch close waits indefinitely.\nepoch_close_deadline_ms: Option<u64>,\n\n/// DEPRECATED. Do not use.\nmax_txn_cost_overage_per_object_in_commit: Option<u64>,\n\n/// DEPRECATED. Do not use.\nallowed_txn_cost_overage_burst_per_object_in_commit: Option<u64>,\n\n/// Minimum interval of commit timestamps between consecutive checkpoints.\nmin_checkpoint_interval_ms: Option<u64>,\n\n/// Version number to use for version_specific_data in `CheckpointSummary`.\ncheckpoint_summary_version_specific_data: Option<u64>,\n\n/// The max number of transactions that can be included in a single Soft Bundle.\nmax_soft_bundle_size: Option<u64>,\n\n/// Whether to try to form bridge committee\n// Note: this is not a feature flag because we want to distinguish between\n// `None` and `Some(false)`, as committee was already finalized on Testnet.\nbridge_should_try_to_finalize_committee: Option<bool>,\n\n/// The max accumulated txn execution cost per object in a mysticeti. Transactions\n/// in a commit will be deferred once their touch shared objects hit this limit,\n/// unless the selected congestion control mode allows overage.\n/// This config plays the same role as `max_accumulated_txn_cost_per_object_in_narwhal_commit`\n/// but for mysticeti commits due to that mysticeti has higher commit rate.\nmax_accumulated_txn_cost_per_object_in_mysticeti_commit: Option<u64>,\n\n/// As above, but separate per-commit budget for transactions that use randomness.\n/// If not configured, uses the setting for `max_accumulated_txn_cost_per_object_in_mysticeti_commit`.\nmax_accumulated_randomness_txn_cost_per_object_in_mysticeti_commit: Option<u64>,\n\n/// Configures the garbage collection depth for consensus. When is unset or `0` then the garbage collection\n/// is disabled.\nconsensus_gc_depth: Option<u32>,\n\n/// DEPRECATED. Do not use.\ngas_budget_based_txn_cost_cap_factor: Option<u64>,\n\n/// DEPRECATED. Do not use.\ngas_budget_based_txn_cost_absolute_cap_commit_count: Option<u64>,\n\n/// SIP-45: K in the formula `amplification_factor = max(0, gas_price / reference_gas_price - K)`.\n/// This is the threshold for activating consensus amplification.\nsip_45_consensus_amplification_threshold: Option<u64>,\n\n/// DEPRECATED: this was an ephemeral feature flag only used in per-epoch tables, which has now\n/// been deployed everywhere.\nuse_object_per_epoch_marker_table_v2: Option<bool>,\n\n/// The number of commits to consider when computing a deterministic commit rate.\nconsensus_commit_rate_estimation_window_size: Option<u32>,\n\n/// A list of effective AliasedAddress.\n/// For each pair, `aliased` is allowed to act as `original` for any of the transaction digests\n/// listed in `tx_digests`\n#[serde(skip_serializing_if = \"Vec::is_empty\")]\naliased_addresses: Vec<AliasedAddress>,\n\n/// The base charge for each command in a programmable transaction. This is a fixed cost to\n/// account for the overhead of processing each command.\ntranslation_per_command_base_charge: Option<u64>,\n\n/// The base charge for each input in a programmable transaction regardless of if it is used or\n/// not, or a pure/object/funds withdrawal input.\ntranslation_per_input_base_charge: Option<u64>,\n\n/// The base charge for each byte of pure input in a programmable transaction.\ntranslation_pure_input_per_byte_charge: Option<u64>,\n\n/// The multiplier for the number of type nodes when charging for type loading.\n/// This is multiplied by the number of type nodes to get the total cost.\n/// This should be a small number to avoid excessive gas costs for loading types.\ntranslation_per_type_node_charge: Option<u64>,\n\n/// The multiplier for the number of type references when charging for type checking and reference\n/// checking.\ntranslation_per_reference_node_charge: Option<u64>,\n\n/// The multiplier for each linkage entry when charging for linkage tables that we have\n/// created.\ntranslation_per_linkage_entry_charge: Option<u64>,\n\n/// The maximum number of updates per settlement transaction.\nmax_updates_per_settlement_txn: Option<u32>,\n\n/// Maximum computation units allowed for a gasless transaction.\ngasless_max_computation_units: Option<u64>,\n\n/// Allowed token types for gasless transactions, with minimum transfer sizes per token.\ngasless_allowed_token_types: Option<Vec<(String, u64)>>,\n\n/// Maximum number of unused Pure inputs allowed in a gasless transaction.\n/// Object and FundsWithdrawal inputs must always be used.\n/// When None, there is no limit (effectively unlimited).\ngasless_max_unused_inputs: Option<u64>,\n\n/// Maximum size in bytes of each Pure input in a gasless transaction.\n/// When None, there is no limit (effectively unlimited).\ngasless_max_pure_input_bytes: Option<u64>,\n\n/// Max tps for gasless transactions. Unlimited when unset, zero when set to zero.\ngasless_max_tps: Option<u64>,\n\n#[serde(skip_serializing_if = \"Option::is_none\")]\n#[skip_accessor]\ninclude_special_package_amendments: Option<Arc<Amendments>>,\n\n/// Maximum serialized size in bytes of a gasless transaction (SenderSignedData).\n/// Bounds the persistent storage impact of each admitted gasless transaction.\ngasless_max_tx_size_bytes: Option<u64>,\n\n/// The multiplier for each live reference charging per-command. Only used when\n/// `allow_references_in_ptbs` is enabled.\ntranslation_per_live_reference_charge: Option<u64>,\n\n/// The maximum number of live references while checking a command. Only used when\n/// `allow_references_in_ptbs` is enabled.\nmax_ptb_live_references: Option<u64>,\n\n/// The maximum number of references returned by a command. Only used when\n/// `allow_references_in_ptbs` is enabled.\nmax_ptb_returned_references: Option<u64>,\n\n/// The maximum number of references returned over the course of the transaction. Only used\n/// when `allow_references_in_ptbs` is enabled.\nmax_ptb_total_returned_references: Option<u64>,\n}\n\nError: Network Error\n\nSelect a network from the following tabs to see the currently configured limits and values.\nRelated topics\n\nAddress-Owned Objects\nAddress-owned objects are owned by a Sui 32-byte address, which can either be an account address or an object ID. Learn how to create and access these objects.\nImmutable Objects\nImmutable objects cannot be changed, transferred, or deleted. Immutable objects cannot have an owner and anyone can use them.\nParty Objects\nParty objects are owned by a specified party at the time of transfer and versioned by consensus. Learn how to create, transfer, and access these objects.\nShared Objects\nAnyone can access shared objects on the Sui network, so care must be taken to secure access, if needed.\n\nObject types\nReferring to objects\nObject ownership\nObject metadata\nThe transaction-object DAG: Relating objects and transactions\nLimits on transactions, objects, and data\n\nWas this page helpful?","tokens":11921,"crawled_at":1791194144475}
+{"id":10341,"url":"https://www.getfoundry.sh/projects/dependencies","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Dependencies – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nDependencies\n\nFoundry uses git submodules to manage dependencies. Libraries are stored in lib/ and imported via remappings.\n\nInstalling dependencies\n\n$ forge install OpenZeppelin/openzeppelin-contracts\n\n$ forge install OpenZeppelin/openzeppelin-contracts@v5.0.0\n\n$ forge install OpenZeppelin/openzeppelin-contracts --commit\n\nThe library is cloned to lib/openzeppelin-contracts/.\n\nLocking dependencies\n\nFor dependencies installed as git submodules, Foundry maintains a foundry.lock file in the project root. The lock file complements .gitmodules: .gitmodules records where each submodule comes from, while foundry.lock records whether you selected a branch, tag, or revision and the resolved commit.\n\nFor example, a dependency installed from a tag produces an entry like this:\n\n{\n\"lib/openzeppelin-contracts\": {\n\"tag\": {\n\"name\": \"v5.0.0\",\n\"rev\": \"b7954c3e9ce1d487b49489f5800f52f4b77b7351\"\n}\n}\n}\n\nCommit foundry.lock so other contributors and CI use the same dependency state. Let Forge update the file instead of editing it manually:\n\nforge install creates or synchronizes the lock file. With no dependency arguments, it also installs existing submodules from the recorded state.\n\nforge update updates branch-based dependencies to the latest commit on their recorded branch. Dependencies installed from a tag or revision stay pinned unless you explicitly select a different ref.\n\nforge remove removes the dependency's lock-file entry.\n\nforge build warns if the lock file is malformed, a dependency is missing, or its checked-out revision does not match the lock file.\n\nDependencies installed with forge install --no-git are regular directories rather than git submodules, so Foundry does not add them to foundry.lock.\n\nUsing dependencies\n\nImport installed libraries in your contracts:\n\nimport {ERC20} from \"openzeppelin-contracts/contracts/token/ERC20/ERC20.sol\";\n\nFoundry automatically creates remappings for libraries in lib/. The remapping openzeppelin-contracts/ points to lib/openzeppelin-contracts/.\n\nRemappings\n\nCustomize import paths with remappings in foundry.toml:\n\n[profile.default]\nremappings = [\n\"@openzeppelin/=lib/openzeppelin-contracts/\",\n]\n\nNow you can import with the prefix:\n\nimport {ERC20} from \"@openzeppelin/contracts/token/ERC20/ERC20.sol\";\n\nGenerate remappings automatically:\n\n$ forge remappings\n\nforge-std/=lib/forge-std/src/\nsolady/=lib/solady/src/\n\nSave to a file for IDE support:\n\n$ forge remappings > remappings.txt\n\nNested dependency remappings\n\nWhen a dependency remapping points below an auto-detected package root, Foundry preserves both by\nscoping the dependency remapping to the directory that declares it. For example, forge remappings\ncan output:\n\nlib/outer/:inner/=lib/outer/lib/inner/contracts/\ninner/=lib/outer/lib/inner/\n\nThe contextual form <context>:<name>=<target> applies to imports made by source units whose names\nbegin with <context>. Here, the trailing slash in lib/outer/ creates a directory boundary, so\nsources inside lib/outer/ use the dependency's contracts/ directory while root sources and\nsibling dependencies use the auto-detected package-root mapping.\n\nFoundry preserves explicit root-project and CLI remappings when constructing generated dependency\ncontexts. An equal or broader global alias suppresses the generated context. A narrower global\nalias is overlaid into that context, so it overrides only its matching import subtree while the\ndependency mapping handles the remaining imports. Explicit contextual remappings are unchanged.\n\nUpdating dependencies\n\nUse forge install to add a dependency or initialize the dependencies already recorded in a checkout. Running it without arguments reconciles existing git submodules and foundry.lock; it does not intentionally fetch newer dependency revisions.\n\nUse forge update when you want to move a dependency to a different revision. With no arguments, it fetches the latest commit for every branch-based dependency:\n\n$ forge update\n\nDependencies installed from a tag or commit revision remain pinned during a plain forge update. To upgrade one of them, provide the new ref explicitly. For example, to move OpenZeppelin Contracts from v5.0.0 to v5.1.0:\n\n$ forge update openzeppelin/openzeppelin-contracts@tag=v5.1.0\n\nYou can also select a branch or an exact commit with @branch=<NAME> or @rev=<COMMIT>. Forge updates the dependency's git submodule checkout and its foundry.lock entry together.\n\nReview and commit both the changed dependency path and foundry.lock after an update.\n\nSee the forge install and forge update references for all options.\n\nRemoving dependencies\n\n$ forge remove openzeppelin-contracts\n\nThis removes the submodule from lib/ and .gitmodules.\n\nResolving conflicts\n\nWhen two dependencies require different versions of the same library, you'll encounter conflicts.\n\nDiagnosing conflicts\n\nCheck dependency trees with:\n\n$ forge tree\n\nExample outputsrc/Morpho.sol =0.8.19\n├── src/interfaces/IMorpho.sol >=0.5.0\n├── src/interfaces/IMorphoCallbacks.sol >=0.5.0\n├── src/interfaces/IIrm.sol >=0.5.0\n│ └── src/interfaces/IMorpho.sol >=0.5.0\n├── src/interfaces/IERC20.sol >=0.5.0\n├── src/interfaces/IOracle.sol >=0.5.0\n├── src/libraries/ConstantsLib.sol ^0.8.0\n├── src/libraries/UtilsLib.sol ^0.8.0\n│ └── src/libraries/ErrorsLib.sol ^0.8.0\n├── src/libraries/EventsLib.sol ^0.8.0\n│ └── src/interfaces/IMorpho.sol >=0.5.0\n├── src/libraries/ErrorsLib.sol ^0.8.0\n├── src/libraries/MathLib.sol ^0.8.0\n├── src/libraries/SharesMathLib.sol ^0.8.0\n│ └── src/libraries/MathLib.sol ^0.8.0\n├── src/libraries/MarketParamsLib.sol ^0.8.0\n│ └── src/interfaces/IMorpho.sol >=0.5.0\n└── src/libraries/SafeTransferLib.sol ^0.8.0\n├── src/interfaces/IERC20.sol >=0.5.0\n└── src/libraries/ErrorsLib.sol ^0.8.0\nsrc/interfaces/IERC20.sol >=0.5.0\nsrc/interfaces/IIrm.sol >=0.5.0 (*)\nsrc/interfaces/IMorpho.sol >=0.5.0\nsrc/interfaces/IMorphoCallbacks.sol >=0.5.0\nsrc/interfaces/IOracle.sol >=0.5.0\nsrc/libraries/ConstantsLib.sol ^0.8.0\nsrc/libraries/ErrorsLib.sol ^0.8.0\nsrc/libraries/EventsLib.sol ^0.8.0 (*)\nsrc/libraries/MarketParamsLib.sol ^0.8.0 (*)\nsrc/libraries/MathLib.sol ^0.8.0\nsrc/libraries/SafeTransferLib.sol ^0.8.0 (*)\nsrc/libraries/SharesMathLib.sol ^0.8.0 (*)\nsrc/libraries/UtilsLib.sol ^0.8.0 (*)\nsrc/libraries/periphery/MorphoBalancesLib.sol ^0.8.0\n├── src/interfaces/IMorpho.sol >=0.5.0\n├── src/interfaces/IIrm.sol >=0.5.0 (*)\n├── src/libraries/MathLib.sol ^0.8.0\n├── src/libraries/UtilsLib.sol ^0.8.0 (*)\n├── src/libraries/periphery/MorphoLib.sol ^0.8.0\n│ ├── src/interfaces/IMorpho.sol >=0.5.0\n│ └── src/libraries/periphery/MorphoStorageLib.sol ^0.8.0\n│ └── src/interfaces/IMorpho.sol >=0.5.0\n├── src/libraries/SharesMathLib.sol ^0.8.0 (*)\n└── src/libraries/MarketParamsLib.sol ^0.8.0 (*)\nsrc/libraries/periphery/MorphoLib.sol ^0.8.0 (*)\nsrc/libraries/periphery/MorphoStorageLib.sol ^0.8.0 (*)\nsrc/mocks/ERC20Mock.sol ^0.8.0\n└── src/mocks/interfaces/IERC20.sol ^0.8.0\nsrc/mocks/FlashBorrowerMock.sol ^0.8.0\n├── src/mocks/interfaces/IERC20.sol ^0.8.0\n├── src/interfaces/IMorpho.sol >=0.5.0\n└── src/interfaces/IMorphoCallbacks.sol >=0.5.0\nsrc/mocks/IrmMock.sol ^0.8.0\n├── src/interfaces/IIrm.sol >=0.5.0 (*)\n├── src/interfaces/IMorpho.sol >=0.5.0\n└── src/libraries/MathLib.sol ^0.8.0\nsrc/mocks/OracleMock.sol ^0.8.0\n└── src/interfaces/IOracle.sol >=0.5.0\nsrc/mocks/interfaces/IERC20.sol ^0.8.0\ntest/BaseTest.sol ^0.8.0\n├── lib/forge-std/src/Test.sol >=0.6.2, <0.9.0\n│ ├── lib/forge-std/src/console.sol >=0.4.22, <0.9.0\n│ ├── lib/forge-std/src/console2.sol >=0.4.22, <0.9.0\n│ ├── lib/forge-std/src/safeconsole.sol >=0.6.2, <0.9.0\n│ ├── lib/forge-std/src/StdAssertions.sol >=0.6.2, <0.9.0\n│ │ ├── lib/forge-std/lib/ds-test/src/test.sol >=0.5.0\n│ │ └── lib/forge-std/src/StdMath.sol >=0.6.2, <0.9.0\n│ ├── lib/forge-std/src/StdChains.sol >=0.6.2, <0.9.0\n│ │ └── lib/forge-std/src/Vm.sol >=0.6.2, <0.9.0\n│ ├── lib/forge-std/src/StdCheats.sol >=0.6.2, <0.9.0\n│ │ ├── lib/forge-std/src/StdStorage.sol >=0.6.2, <0.9.0\n│ │ │ └── lib/forge-std/src/Vm.sol >=0.6.2, <0.9.0\n│ │ ├── lib/forge-std/src/console2.sol >=0.4.22, <0.9.0\n│ │ └── lib/forge-std/src/Vm.sol >=0.6.2, <0.9.0\n│ ├── lib/forge-std/src/StdError.sol >=0.6.2, <0.9.0\n│ ├── lib/forge-std/src/StdInvariant.sol >=0.6.2, <0.9.0\n│ ├── lib/forge-std/src/StdJson.sol >=0.6.0, <0.9.0\n│ │ └── lib/forge-std/src/Vm.sol >=0.6.2, <0.9.0\n│ ├── lib/forge-std/src/StdMath.sol >=0.6.2, <0.9.0\n│ ├── lib/forge-std/src/StdStorage.sol >=0.6.2, <0.9.0 (*)\n│ ├── lib/forge-std/src/StdStyle.sol >=0.4.22, <0.9.0\n│ │ └── lib/forge-std/src/Vm.sol >=0.6.2, <0.9.0\n│ ├── lib/forge-std/src/StdUtils.sol >=0.6.2, <0.9.0\n│ │ ├── lib/forge-std/src/interfaces/IMulticall3.sol >=0.6.2, <0.9.0\n│ │ ├── lib/forge-std/src/mocks/MockERC20.sol >=0.6.2, <0.9.0\n│ │ ├── lib/forge-std/src/mocks/MockERC721.sol >=0.6.2, <0.9.0\n│ │ └── lib/forge-std/src/Vm.sol >=0.6.2, <0.9.0\n│ ├── lib/forge-std/src/Vm.sol >=0.6.2, <0.9.0\n│ ├── lib/forge-std/src/Base.sol >=0.6.2, <0.9.0\n│ │ ├── lib/forge-std/src/StdStorage.sol >=0.6.2, <0.9.0 (*)\n│ │ └── lib/forge-std/src/Vm.sol >=0.6.2, <0.9.0\n│ └── lib/forge-std/lib/ds-test/src/test.sol >=0.5.0\n├── lib/forge-std/src/console.sol >=0.4.22, <0.9.0\n├── src/interfaces/IMorpho.sol >=0.5.0\n├── src/interfaces/IMorphoCallbacks.sol >=0.5.0\n├── src/mocks/IrmMock.sol ^0.8.0 (*)\n├── src/mocks/ERC20Mock.sol ^0.8.0 (*)\n├── src/mocks/OracleMock.sol ^0.8.0 (*)\n├── src/Morpho.sol =0.8.19 (*)\n├── test/helpers/Math.sol ^0.8.0\n├── test/helpers/SigUtils.sol ^0.8.0\n│ ├── src/libraries/ConstantsLib.sol ^0.8.0\n│ └── src/interfaces/IMorpho.sol >=0.5.0\n├── test/helpers/ArrayLib.sol ^0.8.0\n├── src/libraries/periphery/MorphoLib.sol ^0.8.0 (*)\n└── src/libraries/periphery/MorphoBalancesLib.sol ^0.8.0 (*)\ntest/InvariantTest.sol ^0.8.0\n└── test/BaseTest.sol ^0.8.0 (*)\ntest/MarketParamsLibTest.sol ^0.8.0\n├── lib/forge-std/src/Test.sol >=0.6.2, <0.9.0 (*)\n└── src/libraries/MarketParamsLib.sol ^0.8.0 (*)\ntest/helpers/ArrayLib.sol ^0.8.0\ntest/helpers/Math.sol ^0.8.0\ntest/helpers/SigUtils.sol ^0.8.0 (*)\ntest/helpers/WadMath.sol ^0.8.0\ntest/integration/AccrueInterestIntegrationTest.sol ^0.8.0\n└── test/BaseTest.sol ^0.8.0 (*)\ntest/integration/AuthorizationIntegrationTest.sol ^0.8.0\n└── test/BaseTest.sol ^0.8.0 (*)\ntest/integration/BorrowIntegrationTest.sol ^0.8.0\n└── test/BaseTest.sol ^0.8.0 (*)\ntest/integration/CallbacksIntegrationTest.sol ^0.8.0\n└── test/BaseTest.sol ^0.8.0 (*)\ntest/integration/CreateMarketIntegrationTest.sol ^0.8.0\n└── test/BaseTest.sol ^0.8.0 (*)\ntest/integration/ExtSloadIntegrationTest.sol ^0.8.0\n└── test/BaseTest.sol ^0.8.0 (*)\ntest/integration/LiquidateIntegrationTest.sol ^0.8.0\n└── test/BaseTest.sol ^0.8.0 (*)\ntest/integration/OnlyOwnerIntegrationTest.sol ^0.8.0\n└── test/BaseTest.sol ^0.8.0 (*)\ntest/integration/RepayIntegrationTest.sol ^0.8.0\n└── test/BaseTest.sol ^0.8.0 (*)\ntest/integration/SupplyCollateralIntegrationTest.sol ^0.8.0\n└── test/BaseTest.sol ^0.8.0 (*)\ntest/integration/SupplyIntegrationTest.sol ^0.8.0\n└── test/BaseTest.sol ^0.8.0 (*)\ntest/integration/WithdrawCollateralIntegrationTest.sol ^0.8.0\n└── test/BaseTest.sol ^0.8.0 (*)\ntest/integration/WithdrawIntegrationTest.sol ^0.8.0\n└── test/BaseTest.sol ^0.8.0 (*)\ntest/invariant/BaseInvariantTest.sol ^0.8.0\n└── test/InvariantTest.sol ^0.8.0 (*)\ntest/invariant/DynamicInvariantTest.sol ^0.8.0\n└── test/invariant/BaseInvariantTest.sol ^0.8.0 (*)\ntest/invariant/StaticInvariantTest.sol ^0.8.0\n└── test/invariant/BaseInvariantTest.sol ^0.8.0 (*)\ntest/libraries/MathLibTest.sol ^0.8.0\n├── lib/forge-std/src/Test.sol >=0.6.2, <0.9.0 (*)\n├── src/libraries/MathLib.sol ^0.8.0\n└── test/helpers/WadMath.sol ^0.8.0\ntest/libraries/SafeTransferLibTest.sol ^0.8.0\n├── lib/forge-std/src/Test.sol >=0.6.2, <0.9.0 (*)\n├── src/libraries/ErrorsLib.sol ^0.8.0\n└── src/libraries/SafeTransferLib.sol ^0.8.0 (*)\ntest/libraries/UtilsLibTest.sol ^0.8.0\n├── lib/forge-std/src/Test.sol >=0.6.2, <0.9.0 (*)\n├── src/libraries/ErrorsLib.sol ^0.8.0\n└── src/libraries/UtilsLib.sol ^0.8.0 (*)\ntest/libraries/periphery/MorphoBalancesLibTest.sol ^0.8.0\n└── test/BaseTest.sol ^0.8.0 (*)\ntest/libraries/periphery/MorphoLibTest.sol ^0.8.0\n└── test/BaseTest.sol ^0.8.0 (*)\ntest/libraries/periphery/MorphoStorageLibTest.sol ^0.8.0\n├── src/libraries/periphery/MorphoStorageLib.sol ^0.8.0 (*)\n├── test/helpers/SigUtils.sol ^0.8.0 (*)\n└── test/BaseTest.sol ^0.8.0 (*)\n\nResolution strategies\n\n1. Use a compatible version\n\nFind a version that works for both dependencies:\n\n$ cd lib/conflicting-library\n$ git checkout v2.0.0\n$ cd ../..\n$ git add lib/conflicting-library\n$ git commit -m \"Pin conflicting-library to v2.0.0\"\n\n2. Create separate remappings\n\nIf dependencies need different versions, install both under different names:\n\n$ forge install library-v1=org/library@v1.0.0\n$ forge install library-v2=org/library@v2.0.0\n\nAdd remappings:\n\n[profile.default]\nremappings = [\n\"library-v1/=lib/library-v1/\",\n\"library-v2/=lib/library-v2/\",\n]\n\n3. Patch the dependency\n\nFork and modify the dependency to use a compatible version:\n\n# In lib/problematic-dependency\n$ git remote add fork https://github.com/you/fork\n$ git fetch fork\n$ git checkout fork/compatible-branch\n\nUsing npm packages\n\nFoundry can use packages from node_modules:\n\n[profile.default]\nlibs = [\"lib\", \"node_modules\"]\n\nInstall with your preferred package manager:\n\n$ npm install @openzeppelin/contracts\n\nImport directly:\n\nimport {ERC20} from \"@openzeppelin/contracts/token/ERC20/ERC20.sol\";\n\nHardhat compatibility\n\nFor projects migrating from Hardhat or using Hardhat-style imports:\n\n[profile.default]\nlibs = [\"lib\", \"node_modules\"]\nremappings = [\n\"@openzeppelin/=node_modules/@openzeppelin/\",\n\"hardhat/=node_modules/hardhat/\",\n]\n\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":3422,"crawled_at":1791194144568}
+{"id":10342,"url":"https://stack.olas.network/open-autonomy/advanced_reference/on_chain_addresses","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"On Chain Addresses - Olas Stack Developer Documentation","text":"List of contract addresses\n\nPolygon (137)\n\nName\nEnvironment Variable\nAddress\n\nService Registry L 2\n\nCUSTOM_SERVICE_REGISTRY_ADDRESS\n\n0xE3607b00E75f6405248323A9417ff6b39B244b50\n\nService Manager\n\nCUSTOM_SERVICE_MANAGER_ADDRESS\n\n0x3C1fF68f5aa342D296d4DEe4Bb1cACCA912D95fE\n\nService Registry Token Utility\n\nCUSTOM_SERVICE_REGISTRY_TOKEN_UTILITY_ADDRESS\n\n0xa45E64d13A30a51b91ae0eb182e88a40e9b18eD8\n\nService Manager Token\n\nCUSTOM_SERVICE_MANAGER_ADDRESS\n\n0x04b0007b2aFb398015B76e5f22993a1fddF83644\n\nGnosis Safe Multisig\n\nCUSTOM_GNOSIS_SAFE_PROXY_FACTORY_ADDRESS\n\n0x3d77596beb0f130a4415df3D2D8232B3d3D31e44\n\nGnosis Safe Same Address Multisig\n\nCUSTOM_GNOSIS_SAFE_SAME_ADDRESS_MULTISIG_ADDRESS\n\n0xd8BCC126ff31d2582018715d5291A508530587b0\n\nRecovery Module\n\nCUSTOM_RECOVERY_MODULE_ADDRESS\n\n0x02C26437B292D86c5F4F21bbCcE0771948274f84\n\nSafe Multisig With Recovery Module\n\nCUSTOM_SAFE_MULTISIG_WITH_RECOVERY_MODULE_ADDRESS\n\n0x1a0bFCC27051BCcDDc444578f56A4F5920e0E083\n\nMultisend\n\nCUSTOM_MULTISEND_ADDRESS\n\n0x40A2aCCbd92BCA938b02010E17A5b8929b49130D\n\nGnosis (100)\n\nName\nEnvironment Variable\nAddress\n\nService Registry L 2\n\nCUSTOM_SERVICE_REGISTRY_ADDRESS\n\n0x9338b5153AE39BB89f50468E608eD9d764B755fD\n\nService Registry Token Utility\n\nCUSTOM_SERVICE_REGISTRY_TOKEN_UTILITY_ADDRESS\n\n0xa45E64d13A30a51b91ae0eb182e88a40e9b18eD8\n\nService Manager Token\n\nCUSTOM_SERVICE_MANAGER_ADDRESS\n\n0x04b0007b2aFb398015B76e5f22993a1fddF83644\n\nGnosis Safe Multisig\n\nCUSTOM_GNOSIS_SAFE_PROXY_FACTORY_ADDRESS\n\n0x3C1fF68f5aa342D296d4DEe4Bb1cACCA912D95fE\n\nGnosis Safe Same Address Multisig\n\nCUSTOM_GNOSIS_SAFE_SAME_ADDRESS_MULTISIG_ADDRESS\n\n0x6e7f594f680f7aBad18b7a63de50F0FeE47dfD06\n\nRecovery Module\n\nCUSTOM_RECOVERY_MODULE_ADDRESS\n\n0x0Cb12457ed26d572c5e4A50f30b6f7A904662a72\n\nSafe Multisig With Recovery Module\n\nCUSTOM_SAFE_MULTISIG_WITH_RECOVERY_MODULE_ADDRESS\n\n0xB4eB492bbfDcE5ccc11d675797cCF090eB0bCbd6\n\nMultisend\n\nCUSTOM_MULTISEND_ADDRESS\n\n0x40A2aCCbd92BCA938b02010E17A5b8929b49130D\n\nArbitrum One (42161)\n\nName\nEnvironment Variable\nAddress\n\nService Registry L 2\n\nCUSTOM_SERVICE_REGISTRY_ADDRESS\n\n0xE3607b00E75f6405248323A9417ff6b39B244b50\n\nService Registry Token Utility\n\nCUSTOM_SERVICE_REGISTRY_TOKEN_UTILITY_ADDRESS\n\n0x3d77596beb0f130a4415df3D2D8232B3d3D31e44\n\nService Manager Token\n\nCUSTOM_SERVICE_MANAGER_ADDRESS\n\n0x34C895f302D0b5cf52ec0Edd3945321EB0f83dd5\n\nGnosis Safe Multisig\n\nCUSTOM_GNOSIS_SAFE_PROXY_FACTORY_ADDRESS\n\n0x63e66d7ad413C01A7b49C7FF4e3Bb765C4E4bd1b\n\nGnosis Safe Same Address Multisig\n\nCUSTOM_GNOSIS_SAFE_SAME_ADDRESS_MULTISIG_ADDRESS\n\n0xBb7e1D6Cb6F243D6bdE81CE92a9f2aFF7Fbe7eac\n\nRecovery Module\n\nCUSTOM_RECOVERY_MODULE_ADDRESS\n\n0xD0863340f947bE329c67e196e192705e53A1338f\n\nSafe Multisig With Recovery Module\n\nCUSTOM_SAFE_MULTISIG_WITH_RECOVERY_MODULE_ADDRESS\n\n0x17B2198872216D8469AdeBC1227D0d4824940821\n\nMultisend\n\nCUSTOM_MULTISEND_ADDRESS\n\n0x40A2aCCbd92BCA938b02010E17A5b8929b49130D\n\nOptimism (10)\n\nName\nEnvironment Variable\nAddress\n\nService Registry L 2\n\nCUSTOM_SERVICE_REGISTRY_ADDRESS\n\n0x3d77596beb0f130a4415df3D2D8232B3d3D31e44\n\nService Registry Token Utility\n\nCUSTOM_SERVICE_REGISTRY_TOKEN_UTILITY_ADDRESS\n\n0xBb7e1D6Cb6F243D6bdE81CE92a9f2aFF7Fbe7eac\n\nService Manager Token\n\nCUSTOM_SERVICE_MANAGER_ADDRESS\n\n0xFbBEc0C8b13B38a9aC0499694A69a10204c5E2aB\n\nGnosis Safe Multisig\n\nCUSTOM_GNOSIS_SAFE_PROXY_FACTORY_ADDRESS\n\n0x5953f21495BD9aF1D78e87bb42AcCAA55C1e896C\n\nGnosis Safe Same Address Multisig\n\nCUSTOM_GNOSIS_SAFE_SAME_ADDRESS_MULTISIG_ADDRESS\n\n0xb09CcF0Dbf0C178806Aaee28956c74bd66d21f73\n\nRecovery Module\n\nCUSTOM_RECOVERY_MODULE_ADDRESS\n\n0x6e7f594f680f7aBad18b7a63de50F0FeE47dfD06\n\nSafe Multisig With Recovery Module\n\nCUSTOM_SAFE_MULTISIG_WITH_RECOVERY_MODULE_ADDRESS\n\n0x4be7A91e67be963806FeFA9C1FD6C53DfC358d94\n\nMultisend\n\nCUSTOM_MULTISEND_ADDRESS\n\n0x40A2aCCbd92BCA938b02010E17A5b8929b49130D\n\nBase (8453)\n\nName\nEnvironment Variable\nAddress\n\nService Registry L 2\n\nCUSTOM_SERVICE_REGISTRY_ADDRESS\n\n0x3C1fF68f5aa342D296d4DEe4Bb1cACCA912D95fE\n\nService Registry Token Utility\n\nCUSTOM_SERVICE_REGISTRY_TOKEN_UTILITY_ADDRESS\n\n0x34C895f302D0b5cf52ec0Edd3945321EB0f83dd5\n\nService Manager Token\n\nCUSTOM_SERVICE_MANAGER_ADDRESS\n\n0x63e66d7ad413C01A7b49C7FF4e3Bb765C4E4bd1b\n\nGnosis Safe Multisig\n\nCUSTOM_GNOSIS_SAFE_PROXY_FACTORY_ADDRESS\n\n0x22bE6fDcd3e29851B29b512F714C328A00A96B83\n\nGnosis Safe Same Address Multisig\n\nCUSTOM_GNOSIS_SAFE_SAME_ADDRESS_MULTISIG_ADDRESS\n\n0xFbBEc0C8b13B38a9aC0499694A69a10204c5E2aB\n\nRecovery Module\n\nCUSTOM_RECOVERY_MODULE_ADDRESS\n\n0x359d53C326388D24037b3b1590d217fdb5EEE74c\n\nSafe Multisig With Recovery Module\n\nCUSTOM_SAFE_MULTISIG_WITH_RECOVERY_MODULE_ADDRESS\n\n0x8c534420Db046d6801A1A8bE6fb602cC8F257453\n\nMultisend\n\nCUSTOM_MULTISEND_ADDRESS\n\n0x40A2aCCbd92BCA938b02010E17A5b8929b49130D\n\nCelo (42220)\n\nName\nEnvironment Variable\nAddress\n\nService Registry L 2\n\nCUSTOM_SERVICE_REGISTRY_ADDRESS\n\n0xE3607b00E75f6405248323A9417ff6b39B244b50\n\nService Registry Token Utility\n\nCUSTOM_SERVICE_REGISTRY_TOKEN_UTILITY_ADDRESS\n\n0x3d77596beb0f130a4415df3D2D8232B3d3D31e44\n\nService Manager Token\n\nCUSTOM_SERVICE_MANAGER_ADDRESS\n\n0x34C895f302D0b5cf52ec0Edd3945321EB0f83dd5\n\nGnosis Safe Multisig\n\nCUSTOM_GNOSIS_SAFE_PROXY_FACTORY_ADDRESS\n\n0x63e66d7ad413C01A7b49C7FF4e3Bb765C4E4bd1b\n\nGnosis Safe Same Address Multisig\n\nCUSTOM_GNOSIS_SAFE_SAME_ADDRESS_MULTISIG_ADDRESS\n\n0xBb7e1D6Cb6F243D6bdE81CE92a9f2aFF7Fbe7eac\n\nRecovery Module\n\nCUSTOM_RECOVERY_MODULE_ADDRESS\n\n0x24F792D51b398928459Dfbb4181bDb4D5d2CD472\n\nSafe Multisig With Recovery Module\n\nCUSTOM_SAFE_MULTISIG_WITH_RECOVERY_MODULE_ADDRESS\n\n0x379451B13e4900C7005Bf57467770b2EE4e62a86\n\nMultisend\n\nCUSTOM_MULTISEND_ADDRESS\n\n0x40A2aCCbd92BCA938b02010E17A5b8929b49130D\n\nMode (34443)\n\nName\nEnvironment Variable\nAddress\n\nService Registry L 2\n\nCUSTOM_SERVICE_REGISTRY_ADDRESS\n\n0x3C1fF68f5aa342D296d4DEe4Bb1cACCA912D95fE\n\nService Registry Token Utility\n\nCUSTOM_SERVICE_REGISTRY_TOKEN_UTILITY_ADDRESS\n\n0x34C895f302D0b5cf52ec0Edd3945321EB0f83dd5\n\nService Manager Token\n\nCUSTOM_SERVICE_MANAGER_ADDRESS\n\n0x63e66d7ad413C01A7b49C7FF4e3Bb765C4E4bd1b\n\nGnosis Safe Multisig\n\nCUSTOM_GNOSIS_SAFE_PROXY_FACTORY_ADDRESS\n\n0xBb7e1D6Cb6F243D6bdE81CE92a9f2aFF7Fbe7eac\n\nGnosis Safe Same Address Multisig\n\nCUSTOM_GNOSIS_SAFE_SAME_ADDRESS_MULTISIG_ADDRESS\n\n0xFbBEc0C8b13B38a9aC0499694A69a10204c5E2aB\n\nRecovery Module\n\nCUSTOM_RECOVERY_MODULE_ADDRESS\n\n0x1d79e0a600B61FAC1B8F40c27347e48962Ed2f23\n\nSafe Multisig With Recovery Module\n\nCUSTOM_SAFE_MULTISIG_WITH_RECOVERY_MODULE_ADDRESS\n\n0x7Fd1F4b764fA41d19fe3f63C85d12bf64d2bbf68\n\nMultisend\n\nCUSTOM_MULTISEND_ADDRESS\n\n0x40A2aCCbd92BCA938b02010E17A5b8929b49130D","tokens":1628,"crawled_at":1791194145267}
+{"id":10343,"url":"https://www.metaplex.com/docs/smart-contracts/core/collections","domain":"www.metaplex.com","chapter":"docs","title":"Core Collections Overview | Metaplex Core","text":"Summary\nA Core Collection is a Solana account that groups related Core Assets under shared metadata and plugins.\nCollections store a name, URI, and optional plugins that apply to all member Assets\nAssets reference their Collection via the collection field at creation or update time\nCollection-level plugins (e.g. Royalties) propagate to all member Assets unless overridden at the Asset level\nCreating a Collection costs ~0.0015 SOL in rent\nJump to a task: Create Collection · Fetch Collection · Update Collection · Add/Move/Remove Assets\nWhat are Collections?\nA Core Collection is a group of Assets that belong together as part of the same series or set. To group Assets together, you first create a Collection account that stores the shared metadata — collection name and image URI. The Collection account acts as the front cover for your collection and can also hold collection-wide plugins.\nThe data stored and accessible from the Collection account is as follows:\nFieldDescription\nkey\nThe account key discriminator\n\nupdateAuthority\nThe authority of the collection\n\nname\nThe collection name\n\nuri\nThe URI to the collection's off-chain metadata\n\nnumMinted\nThe total number of Assets ever minted into the collection\n\ncurrentSize\nThe number of Assets currently in the collection\n\nCore Collections only group Core Assets. To organize multiple collections or standalone assets under a higher-level taxonomy, see Core Groups. To work with Token Metadata NFTs use mpl-token-metadata. For compressed NFTs use Bubblegum.\n\nManaging Collection Membership\nAssets can be added to, moved between, or removed from Collections after creation using the update instruction on the Asset. These operations change the Asset's update authority — adding sets it to the Collection, removing reverts it to a wallet address.\nOperationDescriptionGuide\nAdd an Asset to a Collection\nAssign a standalone Asset to this Collection\nSDK · CLI\n\nMove an Asset to another Collection\nTransfer an Asset from one Collection to another\nSDK · CLI\n\nRemove an Asset from a Collection\nDetach an Asset so it becomes standalone again\nSDK · CLI\n\nYou must be the update authority of the Collection (and the Asset, if it's standalone) to change membership. Moving between Collections requires authority on both the source and target Collection.\nAn Update Delegate listed on the Collection can also perform these operations — removing any Asset from the Collection, and adding Assets it has authority over — without the root update authority's signature.\n\nNotes\nAssets can exist standalone without a Collection — a Collection is not required\nCollection plugins are inherited by member Assets unless the Asset has its own overriding plugin of the same type\nnumMinted counts all Assets ever created in the collection; currentSize is the live count\nCollections cannot be closed while they contain Assets — remove all Assets first\nQuick Reference\nProgram ID\nNetworkAddress\nMainnet\nCoREENxT6tW1HoK8ypY1SxRMZTcVPm7R94rH4PZNhX7d\n\nDevnet\nCoREENxT6tW1HoK8ypY1SxRMZTcVPm7R94rH4PZNhX7d\n\nCollection Operations\nOperationPageSDK Function\nCreate a Collection\nCreate Collection\ncreateCollection\n\nFetch a Collection\nFetch Collection\nfetchCollection\n\nUpdate Collection metadata\nUpdate Collection\nupdateCollection\n\nUpdate a Collection plugin\nUpdate Collection\nupdateCollectionPlugin\n\nAdd/Move/Remove Assets\nUpdating Assets\nupdate (on the Asset)\n\nCost Breakdown\nItemCost\nCollection account rent\n~0.0015 SOL\n\nTransaction fee\n~0.000005 SOL\n\nTotal\n~0.002 SOL\n\nFAQ\nWhat's the difference between a Collection and an Asset?\nA Collection is a container that groups Assets together. It has its own metadata (name, image) but cannot be owned or transferred like an Asset. Assets are the actual NFTs that users own.\nCan I add an existing Asset to a Collection?\nYes. Use the update instruction with newCollection: collectionId and newUpdateAuthority: updateAuthority('Collection', [collectionId]). See Add an Asset to a Collection for SDK code, or use the CLI: mplx core asset update <assetId> --collection <collectionId>.\nDo I need a Collection for my NFTs?\nNo. Assets can exist standalone without a Collection. However, Collections enable collection-level royalties, easier discoverability, and batch operations.\nCan I remove an Asset from a Collection?\nYes. Use the update instruction and set newUpdateAuthority to updateAuthority('Address', [yourWallet]) to detach the Asset. See Remove an Asset from a Collection for SDK code, or use the CLI: mplx core asset update <assetId> --remove-collection.\nWhat happens if I delete a Collection?\nCollections cannot be deleted while they contain Assets. Remove all Assets first, then the Collection account can be closed.\nGlossary\nTermDefinition\nCollection\nA Core account that groups related Assets under shared metadata\n\nUpdate Authority\nThe account that can modify Collection metadata and plugins\n\nnumMinted\nCounter tracking total Assets ever created in the Collection\n\ncurrentSize\nNumber of Assets currently in the Collection\n\nCollection Plugin\nA plugin attached to the Collection that may apply to all member Assets\n\nURI\nURL pointing to off-chain JSON metadata for the Collection","tokens":1287,"crawled_at":1791194165046}
+{"id":10344,"url":"https://www.getfoundry.sh/projects/soldeer","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Soldeer – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nSoldeer\n\nSoldeer is a Solidity-native package manager that provides an alternative to git submodules. It offers versioned dependencies, a package registry, and simpler dependency management.\n\nInstallation\n\nSoldeer comes bundled with Foundry. Initialize it in your project:\n\n$ forge soldeer init\n\nThis creates a soldeer.toml configuration file.\n\nInstalling packages\n\n$ forge soldeer install @openzeppelin-contracts~5.0.0\n\n$ forge soldeer install my-lib~1.0.0 https://github.com/org/repo.git\n\nPackages are stored in dependencies/ by default.\n\nConfiguration\n\nConfigure Soldeer in soldeer.toml:\n\n[soldeer]\nremappings_generate = true\nremappings_regenerate = false\nremappings_version = true\nremappings_prefix = \"@\"\nremappings_location = \"config\"\n\n[dependencies]\n\"@openzeppelin-contracts\" = \"5.0.0\"\n\"@solmate\" = \"6.7.0\"\n\nKey options:\n\nOptionDescription\nremappings_generate\nAuto-generate remappings\n\nremappings_prefix\nPrefix for remappings (e.g., @)\n\nremappings_location\nWhere to store remappings (config or txt)\n\nUsing packages\n\nImport installed packages:\n\nimport {ERC20} from \"@openzeppelin-contracts/contracts/token/ERC20/ERC20.sol\";\n\nWhen remappings_location = \"config\", remappings are added to foundry.toml. Otherwise, they go to remappings.txt.\n\nUpdating packages\n\n$ forge soldeer update\n\n$ forge soldeer update @openzeppelin-contracts\n\nPublishing packages\n\nPublish your own packages to the Soldeer registry:\n\nLogin to Soldeer\nLogin to your Soldeer account.\n$ forge soldeer login\n\nPrepare your package\nAdd metadata to soldeer.toml:\n[package]\nname = \"my-library\"\nversion = \"1.0.0\"\ndescription = \"My awesome Solidity library\"\n\nPublish\nPublish your package.\n$ forge soldeer push my-library~1.0.0\n\nGit submodules vs Soldeer\n\nFeatureGit submodulesSoldeer\nVersion pinning\nCommit hash\nSemantic versions\n\nRegistry\nGitHub\nSoldeer registry + git\n\nLock file\nNo\nYes (soldeer.lock)\n\nTransitive deps\nManual\nAutomatic\n\nIDE support\nVia remappings\nVia remappings\n\nUse git submodules when:\n\nYou need a specific commit\n\nThe library isn't on the Soldeer registry\n\nYour team is familiar with git submodules\n\nUse Soldeer when:\n\nYou want semantic versioning\n\nYou need reproducible builds (lock file)\n\nYou prefer npm-style dependency management\n\nMigrating from git submodules\n\nConvert existing submodule dependencies to Soldeer:\n\n# Remove the submodule\n$ forge remove openzeppelin-contracts\n\n# Install via Soldeer\n$ forge soldeer install @openzeppelin-contracts~5.0.0\n\nUpdate your imports to use the new remapping prefix:\n\nimport {ERC20} from \"openzeppelin-contracts/contracts/token/ERC20/ERC20.sol\";\n\nimport {ERC20} from \"@openzeppelin-contracts/contracts/token/ERC20/ERC20.sol\";\n\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":688,"crawled_at":1791194161800}
+{"id":10345,"url":"https://docs.sui.io/develop/sui-architecture/networks","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Networks | Sui Documentation","text":"Sui has several networks available, each serving a different purpose. Each network is comprised of nodes. Nodes provide resources to the network and participate in activities such as validating onchain transactions through a process called consensus. There are 2 types of nodes on each Sui network:\n\nFull nodeFull nodeResponsible for validating blockchain activity.: Can validate blockchain activity including transactions, checkpointsCheckpointCreated after transaction execution to provide a certified record of chain history., and epochEpochA period of time defined by the network. changes.\n\nValidatorValidatorResponsible for executing tasks like staking, gas price references, and tallying rules. node: Responsible for signing transactions, staking, gasGasThe computational cost of execution and object storage for a transaction. price references, and tallying rules, in addition to validating blockchain activity.\n\nFull nodes are not able to sign transactions and only have access to a read-only view of the network's state. They are capable of storing and maintaining the chain's full history, and can validate the integrity of the chain by re-executing transactions after a quorumQuorumA set of validators whose combined voting power is greater than 2/3 of the total. of validators has committed them.\n\nValidator nodes can sign transactions but only store the latest transactions.\n\nLearn more about nodes on Sui.\n\nMainnetMainnetProduction network for live transactions and real-value assets.​\n\nMainnet is responsible for all production environment applications and transactions. All activity on Mainnet costs real SUI or MISTMISTThe smallest unit of SUI. tokens, which have a value of fiat currency. SUI or MIST must be bought from an exchange, and excess SUI or MIST can be sold at a later date on the exchange for its fiat value. All activity on Mainnet is public and can be viewed through explorers such as suiscan.\n\nEpochs on Mainnet are approximately 24 hours long. Data is always persisted on the network. Learn more about data storage and storage fees.\n\nThe RPC URL for Mainnet is: https://fullnode.mainnet.sui.io:443.\n\nTestnetTestnetStaging network for testing changes before production deployment.​\n\nTestnet is a staging network designed for developers to test their code before placing it in production. Activity on Testnet uses Testnet SUI and MIST tokens, which can be obtained through a faucet. Testnet tokens have no real value and cannot be exchanged for fiat currency.\n\nAll activity on Testnet is public and can be viewed through explorers such as SuiVision.\n\nEpochs on Testnet are approximately 24 hours long. Data on Testnet is not guaranteed to be persisted because data might be wiped occasionally. It should not be relied on for permanent storage. Testnet data persists through the regular update process, and planned data wipes are announced ahead of time.\n\nThe RPC URL for Testnet is: https://fullnode.testnet.sui.io:443.\n\nDevnetDevnetFor developing and testing new features.​\n\nDevnet is an unstable network used to develop new features. If you want to write code against upcoming Sui features, you can use this network for early testing before the feature is finalized and released.\n\nAll activity on Devnet is public and can be viewed through explorers such as suiscan.\n\nEpochs on Devnet are 1 hour long. Devnet is not recommended for new developers because it is better suited for advanced use cases. Data on Devnet is wiped weekly as part of its scheduled update process.\n\nThe RPC URL for Devnet is: https://fullnode.devnet.sui.io:443.\n\nLocalnetLocalnetLocal network you can run on your own machine for optimized development.​\n\nLocalnet is used to run an instance of the Sui network on your local computer. Developing on a local network provides an optimized workflow in an environment you control. You can set custom network configuration parameters, such as data persistence and a local faucetFaucetA service that provides free Testnet tokens..\n\ntip\nA local faucet enables you to mint as many Testnet tokens as you need for your development process, avoiding the limitations imposed on public faucets for Testnet.\n\nLearn more about creating a local Sui network.\nRelated topics\n\nConsensus\nOverview of the Sui consensus mechanism.\nOperator Guides\nGuides for operators on the Sui network. Whether you are running a full node for your app or operating as a validator on the Sui network, these guides help you set up your environment and operate your network.\nEpochs and Reconfiguration\nEpochs define time periods on Sui where the validator set remains unchanged. Reconfiguration adjusts network parameters at epoch boundaries.\nStorage\nAn overview of Sui's storage architecture, including validator and full node storage requirements, pruning, snapshots, checkpoints, and how storage fees and rebates are calculated.\n\nMainnet\nTestnet\nDevnet\nLocalnet\n\nWas this page helpful?","tokens":1226,"crawled_at":1791194165162}
+{"id":10346,"url":"https://a16zcrypto.com/posts/article/8-reasons-why-blockchain-mechanism-design-is-hard","domain":"a16zcrypto.com","chapter":"research","title":"8 reasons why blockchain mechanism design is hard - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\n8 reasons why blockchain mechanism design is hard\nTim Roughgarden\n05.14.24\n\nTABLE OF CONTENTS\n1. There’s a lack of trust 1. There’s a lack of trust\n2. Collusion happens\n3. Can’t only rely on the rule of law\n4. It’s a much larger design space\n5. Native currencies can introduce other issues\n6. Can’t ignore the underlying stack\n7. Requires working in a computation-limited environment\n8. It’s early\nTags\nmechanism design\nmental models & frameworks\nresearch\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nStudying a field deeply teaches you to recognize problems that arise in the real world as thinly disguised versions or minor variations of problems that are already well solved. For example, when I teach the fundamentals of algorithms, students learn how to recognize problems that boil down to, say, a shortest-path computation or linear programming.\n\nSuch pattern-matching can be equally potent in mechanism design, a type of “inverse game theory” that uses incentives to achieve desirable outcomes. The tools and lessons of mechanism design are especially useful in auction theory, market design, and social choice theory.\n\nCrypto and web3 are rife with mechanism design problems. One might expect many of them to be solvable by copy-pasting from a textbook, using minor variations of age-old ideas. But the unique challenges and constraints of permissionless blockchain protocols often force a rethinking from first principles of seemingly well-solved problems. This makes mechanism design in web3 complex. But these challenges also make mechanism design in web3 deeply fascinating.\n\nIn this post, I explore some of the challenges with web3 mechanism design. These challenges may be familiar to the crypto-native, but understanding mechanism design more deeply should offer all builders a fresh perspective on why these problems are so difficult to solve. As for mechanism designers, if you’re looking for new applications, you will likely be intrigued by the challenges posed by a permissionless environment.\n\nBut first, what is mechanism design?\n\nAs a field, mechanism design goes back at least to 1961, when William Vickrey, a Columbia University economist and future Nobel Prize recipient, formally described a sealed-bid second-price auction. This same style of auction was used as early as 1797, when Johann Wolfgang von Goethe, the author, sold the manuscript for his epic poem Hermann and Dorothea. It was also commonly used by stamp collectors in the nineteenth century but wasn’t formally described until Vickrey and is now commonly known as the “Vickrey auction.” In the Vickrey auction, the highest bidder wins but pays the second highest bid. This auction elicits the true preferences of the bidders, and also gives the item in question to the person who values it the most.\n\nThe Vickrey auction is an elegant and efficient design that has been applied in the real world, modified and updated for new circumstances, with practice informing theory, and vice versa. Like the Vickrey Auction, mechanism design as a formal discipline has a history of intertwined theory and practice. It is both deep and beautiful.\n\nAs opposed to game theory — which establishes the dimensions of a strategic interaction and then explores the most behaviorally plausible outcomes — the field of mechanism design begins not with the game but with a desired outcome. Mechanism design aims to reverse engineer a game of some form so that this desired outcome — perhaps characterized by efficiency, fairness, or certain sets of behaviors — is an equilibrium. In the case of the Vickrey auction, the goal is to elicit the maximum amount participants are willing to pay while not punishing them for doing so.\n\nOpportunities to apply mechanism design abound in web3. For example, a blockchain protocol might want to achieve the outcome that the participants running the protocol do so honestly, without any deviations from the intended behavior. Or a protocol might want to elicit accurate information about the value of transactions, to efficiently allocate block space to the most valuable transactions.\n\nSuch mechanism design problems are always challenging, and they are uniquely challenging in a blockchain context.\n\n1. There’s a lack of trust\n\nWithout the assumption of a trusted party to carry out a mechanism, design in the blockchain space becomes that much harder.\n\nThe whole point of using a permissionless blockchain protocol is you don’t have to trust any one entity or individual, only the “on-average” trust assumption that a sufficiently large fraction of the nodes running the protocol are doing so correctly.\n\nBut the irony of many blockchain architectures is that each batch of transactions added to the history of the chain, for execution in the virtual machine maintained by the protocol, is the product of a unilateral decision made by a single node.\n\nIt is this single node that you cannot know if you can trust.\n\nThis is why it’s rare to see Vickrey auctions in a blockchain context. Implementing a Vickrey auction naively quickly runs into problems with manipulation by untrusted block producers. The issue is that a block producer can manufacture a “shill bid” — a fake bid whose bid is slightly under what’s going to be the winning bid, thereby forcing the winner to pay nearly their full bid (as opposed to the second-highest genuine bid).\n\nShill bids by untrusted block producers effectively cause Vickrey auctions to revert to first-price auctions, which is one of the reasons why first-price auctions are so prevalent in web3. (The recent branch of the traditional mechanism design literature on “credible mechanisms” also considers auction design with an untrusted auctioneer, though from a somewhat different perspective.)\n\n2. Collusion happens\n\nAnother reason mechanism design in blockchains is difficult concerns collusion among blockchain participants. For example, second-price auctions are vulnerable to collusion with side payments. The intuition is simple: The winning bidder pays the second highest bid, so that bidder can simply bribe the second highest bidder into bidding much lower.\n\nThe academic literature on mechanism design hasn’t worried too much about collusion. One reason might be that collusion, especially with side payments, is difficult to pull off in the real world. It’s hard to have credible side payments after the conclusion of some collusive action when the winner could simply decline to pay the bribe. (“No honor among thieves,” as they say.)\n\nIn a blockchain setting, however, would-be colluders can often use smart contracts to commit credibly to the side payments needed to make collusion work. A second reason is the paucity of mechanisms that disincentivize collusion with side payments — “posted price” mechanisms that make only take-it-or-leave-it offers, and not much else.\n\nTo make matters worse, the users of a protocol might collude not only with each other, but also with the (untrusted) block producer (the equivalent of a bidder colluding with the auctioneer in a real-world auction).\n\nResilience to this last type of collusion was one of the primary motivations for burning a portion of the transaction fees in Ethereum’s EIP-1559 transaction fee mechanism. Without the “burn” (or otherwise withholding those revenues from the block producer), a block producer and end- users could collude and evade through side payments whatever reserve price the mechanism attempts to impose.\n\n3. Can’t only rely on the rule of law\n\nCollusion is obviously not a new issue. It’s plagued various mechanisms in real life for centuries, yet if you examine the mechanism design literature, you might be surprised how little it addresses collusion. The literature does address head-on the incentives for unilateral manipulations by individual participants of a mechanism — but generally punts on collusion, leaving it to some unmodeled notion of “rule of law.” For example, participants in the mechanism might sign a legal contract that specifies that they will not collude. If collusion is detected, addressing it is then handed off to a legal channel. Mechanism designers can help by creating a mechanism in which collusion is relatively easy to detect.\n\nThis is an unspoken secret in much of the mechanism design literature: reliance on the rule of law. While one can’t say there’s no rule of law around permissionless blockchain protocols — we frequently see law enforcement successfully prosecute criminal behavior on permissionless blockchains — there is a lot less of it than in traditional mechanism design applications.\n\nAnd if you can’t rely on the rule of law outside the mechanism, then it’s incumbent on the designer to handle it inside the mechanism. This approach pervades mechanism design decisions in the blockchain space. In the Ethereum protocol in particular, examples range from burning base fee revenues in EIP-1559 to slashing misbehaving validators in its consensus protocol.\n\n4. It’s a much larger design space\n\nThe design space in web3 is bigger than mechanism designers are accustomed to. As a result, they have to think about any given problem anew. For example, many mechanisms involve payments; in a traditional mechanism design application, these payments would be in some fiat currency like USD. Many blockchain protocols have their own native currency, and mechanisms within such a protocol are in a position to manipulate that currency.\n\nImagine if you wrote a traditional mechanism design paper, and part of your mechanism’s description was: “Print a bunch of new money, and give that to a bunch of the participants.” It would look ridiculous outside of a blockchain context. But you can do exactly that when you’re talking about mechanism design in the context of a blockchain protocol. The protocol controls the currency, and so a mechanism that’s part of that protocol can mint or burn it.\n\nThis means that some designs that would be impossible without access to a native currency become possible. For example, how do you incentivize Bitcoin miners to carry out the protocol as intended? Through inflationary rewards: printing new Bitcoins to motivate these block producers. Without access to a native currency, such a design would be impossible.\n\n5. Native currencies can introduce other issues\n\nReason #4 highlights the power of native currency. The two obvious things you can do with a native currency are “mint” (the way the Bitcoin protocol mints new bitcoins to incentivize miners) and “burn” (the way Ethereum’s EIP-1559 transaction fee mechanism burns ETH to achieve collusion-resilience). But there is a danger lurking in native currencies that does not exist in traditional mechanism design: microeconomic design decisions may have macroeconomic consequences.\n\nIn traditional mechanism design, there’s no reason to worry about macroeconomic forces. No traditional auction has had a meaningful effect on the U.S. monetary supply or the inflation rate. This challenge is wholly new to the web3 design space. What could go wrong? Let me tell you about two examples, one about minting in Bitcoin, one about burning in Ethereum.\n\nBy virtue of using block rewards — by printing new money to motivate miners — Bitcoin is forced to have inflation. As a result, it must also have a monetary policy to decide on inflation rates and how that rate evolves over time. Nakamoto also created a hard supply cap of 21 million Bitcoins. Because the number of bitcoins has a hard cap, the inflation rate must go to zero.\n\nIf it does go to zero, what would motivate miners to continue running the protocol and contributing security to Bitcoin? The hope has always been that transaction fees would make up for the missing block reward, although the evidence that that will happen is quite weak. It’s always been known that if transaction fees stay close to zero, then the Bitcoin protocol is going to suffer from major security issues.\n\nA paper by Princeton University computer scientists Miles Carlston, Harry Kalodner, Matthew Weinberg, and Arvind Narayanan points out another difference between transaction fees and block rewards. While block rewards are the same for every block (at least between successive “halvings” of the block reward, which occur every four years), transaction fees can vary by orders of magnitude — which in turn introduces new game-theoretic instability into the protocol. In this sense, the macroeconomic decision of a fixed supply cap has negative microeconomic consequences for the protocol and its participants.\n\nJust as the minting of block rewards acts as an inflationary force with Bitcoin, the burning of transaction fees in EIP-1559 acts as a deflationary force with Ethereum. In the Ethereum protocol (which does use inflationary validator rewards), there is a tug of war between these two forces, with the deflationary forces generally winning. The fact that ETH is now a net deflationary currency is a macroeconomic consequence of microeconomically motivated design decisions in the protocol’s transaction fee mechanism.\n\nIs deflation good or bad for the Ethereum protocol? ETH holders like deflation because, all else equal, it makes their tokens more valuable over time. (Indeed, this byproduct may have been what eventually tipped public opinion in favor of the switch to the EIP-1559 transaction fee mechanism.) Yet the idea of a deflationary currency makes traditionally trained macroeconomists recoil, recalling stagflation in 1990s Japan.\n\nWho’s right? Personally, I’m not convinced that a sovereign fiat currency is the right analogy for a cryptocurrency like ETH. But then, what is the correct analogy? This remains an open question, and the ball is in the court of blockchain researchers to explore further: Why is it okay to have a deflationary currency as the cryptocurrency that powers a blockchain protocol but not as the fiat currency that powers a sovereign nation?\n\n6. Can’t ignore the underlying stack\n\nIn computer science, one of the things we aspire toward is modularity and clean abstraction, which grants the ability to rely on parts of your system on faith. When designing and analyzing one part of a system, you presumably need to know the functionality exported by the other parts of the system; but ideally, you don’t need to know how that functionality is actually implemented under the hood.\n\nWe haven’t reached this ideal yet in blockchain protocols. While builders and mechanism designers might like to focus on, say, the application layer, they cannot afford to ignore the reality and details of how the infrastructure layer works.\n\nFor example, if you’re designing an automated market maker, you have to think about the fact that untrusted block producers are in charge of transaction ordering. Or when you’re thinking about transaction fee mechanism design for a (layer-2) rollup, not only do you have to pay for resource consumption at layer 2, you also have to pay for any costs incurred on the underlying layer-1 protocol (for example, from storing calldata).\n\nIn both examples, effective mechanism design at one layer requires detailed expertise about other layers. Maybe, as blockchain technology matures, we’ll have a clean separation of the different layers. But we certainly don’t have it now.\n\n7. Requires working in a computation-limited environment\n\nThe “computer in sky” that a blockchain protocol implements is a computation-limited environment. Traditional mechanism design focused solely on economic incentives and ignored computational issues (for example, the famous Vickrey-Clarke-Groves mechanism is infeasible to implement for sufficiently complex allocation problems).\n\nWhen Nisan and Ronen introduced algorithmic mechanism design in 1999, they noted that we do indeed need some kind of computational tractability for mechanisms to have any actual meaning in the real world. So they proposed restricting attention to mechanisms that use an amount of computation and communication that scales as a polynomial (as opposed to exponential) function of the problem parameters.\n\nBecause computation in a blockchain protocol’s virtual machine is so scarce, on-chain mechanisms must be very lightweight — polynomial time and communication is necessary but not sufficient. This scarcity, for example, is the primary reason why automated market makers completely dominate Ethereum DeFI, as opposed to more traditional solutions like limit order books.\n\n8. It’s early\n\nUsually, when people say it’s still early in web3, they’re referring either to investment opportunities or to adoption numbers. But from a scientific perspective, we’re even earlier than that. This fact only makes things harder — even though it represents an enormous opportunity.\n\nWorking in a mature research area provides benefits that everyone takes for granted. There are agreed-upon models and definitions. There is consensus around the most important problems. There is non-trivial coordination on how to measure progress. There exists a common vocabulary and a large common knowledge base. On-ramps exist to get up to speed, including well-vetted textbooks, online courses, and other resources.\n\nIn many parts of the blockchain space, meanwhile, we don’t yet know the “right” models and definitions to think clearly about and make progress on important problems. For instance, what’s the most important notion of incentive compatibility in the context of blockchain protocols? What are the layers of the web3 stack? What should be counted as part of maximal extractible value (MEV)? These are just some of the open questions.\n\n***\n\nFor those interested in working in the science of blockchain, the immaturity of the area presents a challenge. But coming to it early — now — also represents a unique opportunity.\n\nMechanism design has always been a useful tool at the application layer of the internet — take for example real-time advertising auctions, or the design of two-sided marketplaces that pervade most online consumer apps today, from ecommerce to ridesharing.\n\nBut in web3, mechanism design is also informing design decisions within the infrastructure itself.\n\nThink back to the 1970s and 80s, when internet routing protocols were still being discussed and designed. As far as I know, no one with expertise in incentives and mechanism design had a seat at that table. In hindsight, we now realize that such a person could have usefully informed the design. In web3, meanwhile, incentives have been part of the discussion since day one, with the publication of the original Bitcoin whitepaper.\n\nThe confusion around the “right” models, definitions, and success metrics for web3 is really the universe telling us that we’re in the middle of a golden era. Later generations of students and scientists will envy us being here, in the right place at the right time, with the opportunity to shape the trajectory of this technology. So while there may not be many textbooks in the area, someday there will be, and the work that’s going to be described in them is the work that is being done right now.\n\n***\n\nTim Roughgarden is a Professor of Computer Science and a member of the Data Science Institute at Columbia University, and Head of Research at a16z crypto.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles mnaged by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nPast performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":5456,"crawled_at":1791194166665}
+{"id":10347,"url":"https://www.metaplex.com/docs/smart-contracts/core/collections/create","domain":"www.metaplex.com","chapter":"docs","title":"Create a Core Collection | Metaplex Core","text":"The createCollection instruction creates a new Core Collection account on Solana with a name, metadata URI, and optional plugins.\nWhat You'll Learn\nCreate a simple Collection with a name and URI\nCreate a Collection with the Royalties plugin attached\nHandle common creation errors\n\nSummary\ncreateCollection deploys a new Collection account that groups Core Assets under shared metadata and plugins.\nRequires a fresh keypair as the collection address — reusing an existing address will fail\nAccepts optional plugins at creation time\nCosts ~0.0015 SOL in rent\nThe payer becomes the updateAuthority by default\nQuick Start\nInstall: npm install @metaplex-foundation/mpl-core @metaplex-foundation/umi\nUpload collection metadata JSON to get a URI\nCall createCollection(umi, { collection, name, uri })\nPass the collection address when creating Assets\nJump to: Simple Collection · With Plugins · Common Errors\nPrerequisites\nUmi configured with a signer and RPC connection — see JavaScript SDK\nSOL for transaction fees (~0.002 SOL per collection)\nMetadata JSON uploaded to Arweave or IPFS with a collection image and name\nCreating a Simple Collection\ncreateCollection requires a name, a metadata uri, and a new keypair as the collection signer.\n\n1import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n2import { createCollection } from '@metaplex-foundation/mpl-core'\n\n3import { mplCore } from '@metaplex-foundation/mpl-core'\n\n4import { generateSigner } from '@metaplex-foundation/umi'\n\n5\n\n6// Initialize UMI\n\n7const umi = createUmi('https://api.devnet.solana.com')\n\n8 .use(mplCore())\n\n9\n\n10// Generate a new keypair for the collection\n\n11const collectionSigner = generateSigner(umi)\n\n12\n\n13// Create a new Collection\n\n14await createCollection(umi, {\n\n15 collection: collectionSigner,\n\n16 name: 'My Collection',\n\n17 uri: 'https://example.com/collection.json',\n\n18}).sendAndConfirm(umi)\n\n19\n\n20console.log('Collection created:', collectionSigner.publicKey)\n\nThe collection parameter must be a fresh keypair each time. Reusing an existing address will fail with Collection account already exists.\n\nCreating a Collection with Plugins\nPass a plugins array to createCollection to attach plugins at creation time. The example below attaches the Royalties plugin.\nCreate a Core Collection with the Royalties plugin\n\ncreate-collection-with-royalties.ts\nimport { generateSigner, publicKey } from '@metaplex-foundation/umi'\n\nimport { createCollection, ruleSet } from '@metaplex-foundation/mpl-core'\n\nconst collectionSigner = generateSigner(umi)\n\nconst creator1 = publicKey('11111111111111111111111111111111')\n\nconst creator2 = publicKey('22222222222222222222222222222222')\n\nawait createCollection(umi, {\n\ncollection: collectionSigner,\n\nname: 'My NFT',\n\nuri: 'https://example.com/my-nft.json',\n\nplugins: [\n\n{\n\ntype: 'Royalties',\n\nbasisPoints: 500,\n\ncreators: [\n\n{ address: creator1, percentage: 20 },\n\n{ address: creator2, percentage: 80 },\n\n],\n\nruleSet: ruleSet('None'),\n\n},\n\n],\n\n}).sendAndConfirm(umi)\n\nCommon Errors\nCollection account already exists\nThe collection keypair was already used on this network. Generate a new signer each time:\nconst collectionSigner = generateSigner(umi) // Must be a unique keypair\n\nInsufficient funds\nYour payer wallet needs ~0.002 SOL. Fund it on devnet with:\nsolana airdrop 1 <WALLET_ADDRESS> --url devnet\n\nNotes\nPlugins added at creation can be updated later using updateCollectionPlugin — see Update Collection\nThe updateAuthority defaults to the payer — pass an explicit updateAuthority to set a different account\nAll plugins available to Assets can also be applied to Collections — see Plugins Overview\nQuick Reference\nItemValue\nInstruction\nCreateCollectionV1\n\nJS function\ncreateCollection\n\nRequired accounts\ncollection (new keypair), payer\n\nOptional accounts\nupdateAuthority, systemProgram\n\nRequired args\nname, uri\n\nOptional args\nplugins\n\nRent cost\n~0.0015 SOL\n\nSource\nGitHub","tokens":978,"crawled_at":1791194200876}
+{"id":10348,"url":"https://docs.sui.io/develop/sui-architecture/tokenomics-overview","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Tokenomics on Sui | Sui Documentation","text":"The native token of Sui is SUI. The Sui tokenomics structure is designed to support the long-term financial needs of Web3. The SUI token serves 4 purposes on the Sui network:\n\nProvides the opportunity to stake SUI to participate in the proof-of-stake mechanism.\n\nSUI is the asset denomination needed to pay the gasGasThe computational cost of execution and object storage for a transaction. fees required to execute transactions or other operations on the network.\n\nSUI acts as a versatile and liquid asset for various applications.\n\nSUI tokens play an important role in governance by acting as a right to participate in onchain voting on issues such as protocol upgrades.\n\nStakeholders​\n\nStakeholders in a blockchain's tokenomics have a vested interest in the viability of the blockchain economy. The Sui economy has 3 main groups of stakeholders:\n\nUsers, who submit transactions to the network to create, mutate, and transferTransferChanging the owner of an asset. digital assets or interact with smart contracts.\n\nSUI token holders, who have the option of staking their tokens to validators. SUI owners also hold the rights to participate in Sui governance.\n\nValidators, who manage transactionTransactionA number of commands that execute on inputs to define the result of the transaction. processing and execution on the Sui platform.\n\nDelegated proof of stake​\n\nSui uses a delegated proof of stake (DPoSDPoSConsensus mechanism used by Sui.) consensus mechanism where validators lock a certain amount of SUI as collateral for the duration of an epoch. Validators cannot make changes to their stake during an epochEpochA period of time defined by the network., and any changes are applied when a new epoch begins. They then earn rewards for processing operations, such as validating transactions, and for providing resources.\n\nUsers of the network hold their own SUI, which they can delegate to validators of their choice as part of a validatorValidatorResponsible for executing tasks like staking, gas price references, and tallying rules.'s stake. In so doing, the validators reward users based on the amount of SUI they delegate. Users are free to withdraw their SUI or place stake in a different validator before a new epoch begins.\n\nToken supply​\n\nThere is a finite supply of SUI. The total supply of SUI tokens on MainnetMainnetProduction network for live transactions and real-value assets. is capped at 10,000,000,000 SUI. This is the total number of SUI that can ever be minted, but the total supply is not available for transactions. Supply availability follows the designed unlocking schedules in place to enhance the tokenomics stability of the network and provide a long-term level of security.\n\nToken distribution​\n\nAt the beginning of each epoch, 3 important events happen:\n\nSUI holders stake their tokens to validators and a new committee is formed.\n\nThe reference gas prices are set as described in Sui Gas Fees.\n\nThe storage fund size is adjusted using the net inflow of the previous epoch.\n\nFollowing these actions, the protocol computes the total amount of stake as the sum of staked SUI plus the storage fund.\n\nDuring each epoch, users submit transactions to the Sui platform and validators process them. For each transaction, users pay the associated computation and storage gas fees. In cases where users delete previous transaction data, users obtain a partial rebate of their storage fees. Validators observe the behavior of other validators and evaluate each other's performance.\n\nAt the end of each epoch, the protocol distributes stake rewards to participants. This occurs through 2 main steps:\n\nThe total amount of stake rewards is calculated as the sum of computation fees accrued throughout the epoch plus the epoch's stake reward subsidies. The latter component is temporary in that it only exists in the network's first years and disappears in the long run as the amount of SUI in circulation reaches its total supply.\n\nThe total amount of stake rewards is distributed across various entities. The storage fund is taken into account in the calculation of the epoch total stake, which is not owned by any entities in the way that staked SUI is. Instead, the Sui economic model distributes the stake rewards accruing to the storage fund to validators for compensation of their storage costs.\n\nThe distribution mechanisms built into Sui tokenomics encourages a healthy competition for fair prices where validators set low gas fees while operating with viable business models. Refer to the whitepaper for in-depth review of the mathematical proofs that support this structure.\n\nVesting schedules​\n\nA vesting schedule dictates when certain blocks of SUI become accessible to the market. The Sui tokenomics design includes a multi-tiered SUI vesting schedule.\n\nWhen Sui first launched its Mainnet network (initial SUI mint), there was a one-year cliff period. During this time, all initial investors were blocked from transferring their initial stake of SUI to the marketplace. A common practice for new cryptocurrency, the cliff period protected early network stability against large-scale sell-offs from early investors. The cliff period ended in May 2024.\n\nAirdrops​\n\nOften, when a new token launches, its minters set aside a percentage of the sum to distribute to early adopters to drive interest in the associated blockchain project. This process is called an airdrop.\n\nThere were no SUI airdrops to support the launch of Sui's Mainnet network. This was a publicly-stated, intentional decision for the following reasons:\n\nAirdrops expose a potential for bad actors to take advantage of the excitement around a new launch. By publicly stating there would be no airdrops, Sui attempted to mitigate the risk its users faced.\n\nCryptocurrency is regulated differently across the globe. Airdrops can be viewed as taxable events in some jurisdictions, creating legal or financial complications.\n\nSui is committed to the long-term success of the network and its stakeholders. Airdrops might generate excitement early in a project's lifecycle, but the long-term benefits are minimal.\n\nStorage fund​\n\nSUI pays for the gas fees and data storage on the network. A potential problem arises, however, when new validators come onchain. Even though the validator is new, it still must pay the storage cost for activity that happened before it was part of the network.\n\nSui addressesAddressA unique, anonymous identity on a blockchain network. this problem with the storage fund, a cache of SUI that never fully depletes. Each onchain transaction that adds data to the chain includes a fee for storage, which the protocol adds to the storage fund. The storage fund itself has a stake in the network, so it collects rewards based on that stake just like every other onchain stakeholder. The protocol then regularly distributes those storage fund rewards to Sui validators to pay for storage. In this way, new validators to the network get paid for storing data from past transactions.\n\nStorage fund rewards​\n\nTotal stake is calculated as the sum of user stake plus the SUI tokens deposited in the storage fund. The storage fund receives a proportional share of the overall stake rewards depending on its size relative to total stake. The largest share of these stake rewards are paid out to current validators to compensate for storage costs. The rewards that remain are reinvested into the fund. When onchain storage requirements are high, validators receive substantial additional rewards to compensate for their storage costs.\n\nThe storage fund includes 3 key features:\n\nPast transactions contribute to the storage fund, which functions as a tool for shifting gas fees across different epochs. This ensures that future validators are compensated for their storage costs by the past users who created those storage requirements in the first place.\n\nThe storage fund pays out only the returns on its capital and does not distribute its principal. In practice, this means validators borrow the storage fund's SUI as additional stake and keep the majority of stake rewards. Validators do not, however, receive funds directly from the storage fund. This guarantees the fund never loses its capitalization and can survive indefinitely. This feature is further strengthened by the stake rewards reinvested into the fund.\n\nThe storage fund includes a deletion option. If you delete data, you get a partial refund of the storage fees paid originally.\n\nDeflation​\n\nUnlike traditional economics, deflation is a feature of Sui rather than a bug. The total supply of SUI is capped, so increased activity on the network has a deflationary effect as the storage fund grows in relation to the amount of data stored, which effectively takes more SUI out of circulation. The value for SUI increases in relation to the decrease in circulating supply.\n\nValidator rewards​\n\nAll honest validators on Sui receive their staking rewards with full certainty. The rewards are based only on the amount of stake the validators hold, removing randomness from the equation.\n\nStaking​\n\nStake SUI tokens by sending a transaction to the network that calls the staking function implemented as part of the system Move packagePackageSmart contracts on Sui.. This transaction wraps the SUI tokens in a self-custodial stake object. This stake objectObjectThe basic unit of storage on Sui. contains information including the validator staking pool ID and the activation epoch of the stake. With the introduction of SIP-6, you can participate in liquid staking protocols using your staked objects.\n\nSui-compatible crypto wallets typically have functionality to initiate staking and unstaking from your Sui address. See the respective documentation for these tools to begin staking your SUI.\n\nUnstaking​\n\nSimilar to staking, a user withdraws stake from a validator by sending a transaction that calls the unstaking function in the system Move package. This transaction unwraps the stake object, and sends both the principal and the accumulated rewards to the user as SUI tokens. You accrue rewards only during epochs where the stake is active for the entire epoch. The rewards withdrawn from the validator's rewards pool are calculated based on the activation epoch and unstaking epoch of the stake.\n\nChoosing a validator for staking​\n\nYou must choose a specific validator you would like to stake your SUI in. The choice of validator can potentially impact the amount of staking rewards you receive. The factors determining this amount include, but are not limited to:\n\nValidator commission rate: A validator can choose to set a non-zero commission rate specifying the percentage of staking rewards they are taking from the stakers. For example, if a validator has a commission rate of 10%, then 10% of every staker's staking rewards is given to the validator.\n\ncaution\nA validator can choose its commission at a future moment in time without prior notice.\n\nValidator performance: A validator with bad performance might be punished according to the tallying rule. Punished validators do not receive any staking rewards for the epoch during which they are punished, and you also do not receive that epoch's rewards when you withdraw your stake from that validator.\n\nSui-compatible crypto wallets and explorers typically provide validator information such as commission and APY. See the respective documentation for these tools for information on how to retrieve this data.\n\nStaking pools​\n\nEach Sui validator maintains its own staking pool to track the amount of stake and to compound staking rewards. Validator pools operate together with a time series of exchange rates that are computed at each epoch boundary. These exchange rates determine the amount of SUI tokens that each past SUI staker can withdraw in the future. Importantly, the exchange rates increase as more rewards are deposited into a staking pool. The longer an amount of SUI is deposited in a staking pool, the more rewards it accrues.\n\nWhen SUI is deposited to the staking pool in epoch E, those SUI are converted into liquidity tokens at the epoch E exchange rate. As the staking pool earns rewards, the exchange rate appreciates. At epoch E', those liquidity tokens are worth more and translate into more SUI.\n\nThe only difference between Sui staking pools and typical liquidity pools is that in Sui the liquidity tokens do not exist. Rather, the global exchange rate table is used to track the accounting. Because all SUI tokens in the staking pool are treated the same, all SUI tokens immediately count as stake and thus compound rewards immediately.\n\nThe staking pool is implemented in a system-level smart contract (staking_pool.move) and is part of the Sui framework.\n\nValidator pool exchange rate​\n\nThe exchange rate for each validator pool is calculated at each epoch boundary as follows:\n\nExchangerateatE+1=(1+(third−partystakerrewardsatE/third−partystakeatE))×(exchangerateatE)Exchange rate at E+1 = (1 + (third-party staker rewards at E / third-party stake at E)) × (exchange rate at E)ExchangerateatE+1=(1+(third−partystakerrewardsatE/third−partystakeatE))×(exchangerateatE)\nThe distinction between third-party owned versus validator-owned rewards and stake is relevant in that validators earn commission on the staking pool's tokens but third-party stakers do not. This accounting enables Sui to keep track of the rewards accrued by both validators and third-party token holders using a single global exchange rate table.\n\nValidatorValidatorResponsible for executing tasks like staking, gas price references, and tallying rules. staking pool requirements​\n\nThere are minimum staking requirements a validator must satisfy to become active and to stay in the active validator set.\n\nStake requirements​\n\nThe Sui network is rolling out SIP-39, which will significantly lower the barrier to entry for validators. Instead of requiring a minimum amount of SUI tokens, validators will need a minimum amount of voting power.\n\nWhen fully rolled out, SIP-39 will mean the following validator requirements:\n\nA validator candidate must accrue at least 3 voting power before they can request to join the validator set.\n\nIf an active validator's stake falls below 2 voting power, they have seven epochs of grace period to gain back the stake before being removed from the validator set.\n\nIf an active validator's stake falls below 1 voting power, they are removed from the validator set at the end of the current epochEpochA period of time defined by the network. boundary. Sui uses 24-hour epochs.\n\nFor more information on voting power, see Understanding the voting power formula.\n\ntip\nWant to be a Sui validator?\nIf you have the required stake and plan to operate a validator on Sui, your participation is welcome and Sui is committed to supporting your onboarding. Kindly complete this form to be added to our Validator Discord and keep up with upcoming validator releases and technical support.\n\nUnderstanding the voting power formula​\n\nSIP-39 uses the following formula to determine if a validator can join the set:\n\nS / (S + T) > V / 10000\n\nS = The validator candidate's stake amount.\n\nT = Total amount already staked in the network.\n\nV = Minimum voting power threshold (3 in the final phase).\n\n10000 = Total voting power units in the Sui system.\n\nThis formula checks if the validator would have at least V voting power after joining.\n\nS / (S + T) calculates what proportion of the total stake the validator would control.\n\nWhen multiplied by 10000, this gives their voting power in Sui's standardized units.\n\nThe validator can join if this value is greater than or equal to the threshold V.\n\nFor example, with a network stake of 7.69B SUI and V=3, a validator with 2.31M SUI would have: 2,310,000 / (2,310,000 + 7,694,950,773) ≈ 0.0003 proportion, converting to voting power: 0.0003 × 10000 ≈ 3 units.\n\nSince 3 ≥ 3, they meet the threshold to join.\n\nAs the total network stake changes, the minimum required amount adjusts automatically.\nRelated topics\n\nConsensus\nOverview of the Sui consensus mechanism.\nSui Validators\nGuides for validator nodes on the Sui network.\nEpochs and Reconfiguration\nEpochs define time periods on Sui where the validator set remains unchanged. Reconfiguration adjusts network parameters at epoch boundaries.\nGas Fees\nA Sui transaction must pay for both the computational cost of execution and the long-term cost of storing the objects a transaction creates or mutates.\n\nStakeholdersDelegated proof of stake\n\nToken supply\nToken distributionVesting schedules\nAirdrops\n\nStorage fundStorage fund rewards\nDeflation\n\nValidator rewardsStaking\nUnstaking\nChoosing a validator for staking\nStaking pools\nValidator pool exchange rate\n\nWas this page helpful?","tokens":4181,"crawled_at":1791194186086}
+{"id":10349,"url":"https://a16zcrypto.com/posts/videos/lvr-in-a-minute-with-tim-roughgarden","domain":"a16zcrypto.com","chapter":"research","title":"LVR in a minute with Tim Roughgarden - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nLVR in a minute with Tim Roughgarden\nTim Roughgarden\n03.15.24\n\nTags & Share Tags\nAMMs\nDeFi\nresearch\ntech trends\nvideo\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nIn this explainer, Tim Roughgarden, head of research at a16z crypto, presents a new way to think about the cost side of providing liquidity in an AMM, which centers around a quantity called LVR (“loss versus rebalancing,” pronounced “lever”).\n\nThere are two types of participants in an automated market maker (AMM): traders, who exchange one of the AMM’s tokens for another (say, ETH and USDC), and liquidity providers (LPs), who provide tokens to the AMM in the first place, generally in exchange for a share of the trading fees.\n\nBut to date it’s been unclear when it makes economic sense to participate as an LP. When does the benefit exceed the cost? The benefit side of this comparison is easy to understand: revenue from shared trading fees, plus in some cases additional token rewards.\n\nLVR is a mathematical formula that isolates an LP’s adverse selection costs, allowing them to compare their potential LVR with the AMM’s fees, and to reason about whether and when to provide liquidity. And it provides AMMs with a way to keep their LPs happy by keeping LVR small.\n\nThis is joint work with Jason Milionis, Ciamac Moallemi, and Anthony Lee Zhang\n\nFor more, see: https://a16zcrypto.com/posts/article/… Original paper: https://arxiv.org/abs/2208.06046\n\nAbout the presenter Tim Roughgarden is a Professor of Computer Science and a member of the Data Science Institute at Columbia University, and Head of Research at a16z crypto.","tokens":432,"crawled_at":1791194186775}
+{"id":10350,"url":"https://www.getfoundry.sh/forge/contract-bindings","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Contract bindings – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nContract bindings\n\nFoundry provides two generators with different outputs. Choose the workflow based on what consumes the generated code.\n\nGoalCommandOutput\nCall contracts from Rust\nforge bind\nAn Alloy crate or Rust module generated from compiled contract artifacts\n\nStart from a verified deployed contract\ncast source, then forge bind\nExplorer source followed by local Alloy bindings\n\nSerialize Solidity structs to and from JSON\nforge bind-json\nA Solidity helper library for JSON cheatcodes\n\nforge bind-json does not generate Rust code. The former cast bind workflow has also been removed; fetch verified source with cast source and generate bindings from a Forge project with forge bind instead.\n\nGenerate Alloy bindings from a project\n\nforge bind compiles the project and reads the resulting ABIs. Calls, return values, errors, and events all become typed Alloy definitions.\n\nFor example, start with this contract:\n\n// SPDX-License-Identifier: MIT\npragma solidity ^0.8.24;\n\ncontract Counter {\nuint256 public value;\n\nevent Incremented(address indexed caller, uint256 amount, uint256 newValue);\n\nerror ZeroAmount();\n\nfunction increment(uint256 amount) external returns (uint256 newValue) {\nif (amount == 0) revert ZeroAmount();\n\nnewValue = value + amount;\nvalue = newValue;\nemit Incremented(msg.sender, amount, newValue);\n}\n}\n\nGenerate a standalone Rust crate for only Counter:\n\nforge bind \\\n--bindings-path bindings \\\n--select '^Counter$' \\\n--crate-name counter-bindings \\\n--crate-version 0.1.0 \\\n--crate-license MIT \\\n--alloy-version 1.0\n\nThe result has this shape:\n\nbindings/\n├── Cargo.toml\n└── src/\n├── counter.rs\n└── lib.rs\n\nAdd it to another Rust crate as a path dependency:\n\n[dependencies]\ncounter-bindings = { path = \"../contracts/bindings\" }\n\nThen import the generated contract module:\n\nuse alloy::primitives::U256;\nuse counter_bindings::counter::Counter;\n\nlet counter = Counter::new(address, provider);\nlet pending = counter.increment(U256::from(1)).send().await?;\n\nThe exact provider and transaction setup depends on your Alloy application. The generated module also contains Incremented, ZeroAmount, the ABI, call types, and return types.\n\nSelect the intended contracts\n\nUse --select <REGEX> more than once to generate a narrow public surface:\n\nforge bind \\\n--bindings-path bindings \\\n--select '^Counter$' \\\n--select '^Treasury$'\n\nBy default, contracts whose names end in Test or Script are excluded. --select-all explicitly includes every contract and cannot be combined with --select.\n\nThe default output is out/bindings. Pass --bindings-path to keep generated Rust code somewhere else. Use --module when the output should be a module rather than a crate, and --single-file when one generated source file is preferable.\n\nKeep generated bindings reproducible\n\nTreat Solidity source and compiled ABIs as the source of truth. Do not edit generated Rust files by hand.\n\nDuring development, regenerate intentionally:\n\nforge bind \\\n--bindings-path bindings \\\n--select '^Counter$' \\\n--alloy-version 1.0 \\\n--overwrite\n\nIn CI, omit --overwrite. If the directory already exists, forge bind compares it with freshly generated output and exits unsuccessfully when it is stale:\n\nforge bind \\\n--bindings-path bindings \\\n--select '^Counter$' \\\n--alloy-version 1.0\ncargo check --manifest-path bindings/Cargo.toml --locked\n\nCommit the generated crate's Cargo.lock when your repository policy permits it, or pin the dependency with --alloy-rev. Keep every generation option in a script or CI job so local and automated output cannot drift.\n\nOnly use --skip-build when the artifact directory is known to be current. Otherwise, stale artifacts can produce bindings that do not match the Solidity source under review.\n\nGenerate bindings for a verified contract\n\nWhen you only have a deployed address, retrieve the explorer-verified sources into an existing Forge project, then run the same local generator:\n\ncast source \"$ADDRESS\" \\\n--chain mainnet \\\n--etherscan-api-key \"$ETHERSCAN_API_KEY\" \\\n-d src/vendor/verified-contract\n\nforge bind \\\n--bindings-path bindings \\\n--select '^VerifiedContract$' \\\n--alloy-version 1.0\n\nCheck the chain ID, address, explorer, and downloaded source before compiling it. Prefer existing local source or artifacts when available; this workflow introduces explorer availability and verified-source trust into generation.\n\nGenerate Solidity JSON helpers\n\nforge bind-json discovers Solidity structs and generates typed wrappers around Foundry's JSON cheatcodes. This is useful when tests or scripts read structured configuration files.\n\nDefine the struct that represents the JSON schema:\n\n// SPDX-License-Identifier: MIT\npragma solidity ^0.8.24;\n\nstruct DeploymentConfig {\naddress owner;\nuint256 initialValue;\n}\n\nConfigure the generated file and narrow the source set in foundry.toml:\n\n[profile.default]\nsrc = \"src\"\n\n[bind_json]\nout = \"utils/JsonBindings.sol\"\ninclude = [\"**/ConfigTypes.sol\"]\nexclude = [\"**/mocks/**\"]\n\nThe include and exclude values are globs matched against compiler source paths. A leading **/ makes the example work for absolute and project-relative paths. If include is omitted, Foundry considers all non-library project files by default.\n\nGenerate the helper:\n\nforge bind-json\n\nBy default, the command writes utils/JsonBindings.sol. A positional path overrides the configured output:\n\nforge bind-json generated/ProjectJsonBindings.sol\n\nThe generated library includes serialize, deserializeDeploymentConfig, path-based overloads, and array deserializers. Import it after generation:\n\n// SPDX-License-Identifier: MIT\npragma solidity ^0.8.24;\n\nimport {DeploymentConfig} from \"../src/ConfigTypes.sol\";\nimport {JsonBindings} from \"../utils/JsonBindings.sol\";\n\ncontract JsonBindingsTest {\nusing JsonBindings for *;\n\nfunction test_deserializeDeploymentConfig() external pure {\nstring memory json =\n'{\"owner\":\"0x000000000000000000000000000000000000bEEF\",\"initialValue\":7}';\n\nDeploymentConfig memory config = json.deserializeDeploymentConfig();\n\nassert(config.owner == address(0xBEEF));\nassert(config.initialValue == 7);\n}\n}\n\nRun forge bind-json whenever a struct is added, removed, renamed, or changed. Foundry preprocesses an existing generated file so stale imports usually do not prevent regeneration, but the generated file must exist before source that imports it can compile for the first time.\n\nAgent workflow\n\nWhen an agent encounters generated bindings:\n\nRead foundry.toml, generation scripts, and CI before changing output paths or flags.\n\nInspect the Solidity declaration or ABI instead of searching large generated files first.\n\nRun forge bind without --overwrite to detect Rust binding drift.\n\nRegenerate with the repository's exact selectors and version options, then review ABI-level changes in calls, events, errors, and return types.\n\nRun forge bind-json before compiling code that imports a missing or stale JSON helper.\n\nThis order keeps generated code attributable to a small input change and avoids unnecessary explorer or RPC requests.\n\nSee also\n\nforge bind reference\n\nforge bind-json reference\n\ncast source reference\n\nBuilding contracts\n\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":1798,"crawled_at":1791194188311}
+{"id":10351,"url":"https://a16zcrypto.com/posts/article/introducing-our-summer-23-research-seminars","domain":"a16zcrypto.com","chapter":"research","title":"Introducing our summer '23 research seminars - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nIntroducing our summer '23 research seminars\nTim Roughgarden\n08.22.23\n\nTags & Share Tags\nfield notes\nresearch\ntech trends\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nWith the goal of advancing the science and technology of the next generation of the internet, we introduced a16z crypto research – a new kind of multidisciplinary lab dedicated to helping shape crypto and web3 as a formal area of study.\n\nAnother of our goals is to help bridge the worlds of academic theory with industry practice, and one of the ways we aim to do this – besides working with our portfolio and publishing our own work – is by bringing together the very best research talent from the disciplines that are relevant to the space, including computer science and the social sciences. To that end, we’ve now hosted two immersive summer programs at the a16z crypto office, where we invite both established and emerging researchers to present their work and ideas, collaborate on some of the hardest problems in the ecosystem, and sharpen each other’s ideas by spending time with one another.\n\nYou can watch many of the talks (and overhear our in-room conversations) from the 2022 cohort seminars here. We also continued this series of seminars through last fall and this spring. But now, I’m excited to share talks from the 2023 summer program and cohort, which covered topics from scaling to governance to incentive design and beyond.\n\nYou can subscribe to the YouTube channel here, where we will continue to post new talks regularly. The initial set of releases features:\n\nJoe Bonneau (a16z crypto research partner, NYU), “Distributed Randomness Beacons”\n\nLera Nikolaenko (a16z crypto research partner), “Distributed Data Storage, Data Availability Sampling, and Danksharding”\n\nMatt Green (Johns Hopkins), “Beyond ZK: Next Steps for Compliance and Constrained Encryption on Blockchains”\n\nSarah Meiklejohn (University College London and Google), “Adaptivity and Asynchrony in Distributed Key Generation”\n\nIttai Abraham (Intel Labs, former VMWare), “It’s All about Trust” (Ittai also has a very popular industry blog Decentralized Thoughts)\n\nFor more about the lab and our research team, including featured releases and papers, please visit https://a16zcrypto.com/research/. Some of our ongoing and latest work includes proposing and building a new paradigm for SNARK design (Lasso and Jolt), which make SNARKs more accessible, more auditable, and more widely usable for more developers to build more applications in web3; introducing ideas like LVR, which helps participants in automated market makers think more precisely about tradeoffs in liquidity provision for decentralized finance; providing overviews and proposals to fundamental concepts like danksharding; helping apply our theories to practice, such as private on-chain auction design for web3; diving deep on marketplace, mechanism, other incentive and business design; and much more.\n\nDoing research in web3 is fun and intellectually stimulating. The range of topics also shows how much work we have to do to fulfill the promise of a distributed computer that’s available to everyone but owned by no one (what I’ve called a “computer that lives in the sky”) – and there are still plenty of challenges, and opportunities, ahead for interested researchers from many fields.\n\n***\n\nTim Roughgarden is a Professor of Computer Science and a member of the Data Science Institute at Columbia University, and Head of Research at a16z crypto.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.)\n\nCharts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":1413,"crawled_at":1791194205229}
+{"id":10352,"url":"https://www.getfoundry.sh/forge/gas-accounting","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Gas accounting – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nGas accounting\n\nUse a gas measurement to understand an execution, a transaction receipt to find the charged gas, and a gas estimate to choose the limit for a new transaction. These numbers answer different questions, even when they happen to be equal.\n\nEIP-8037: State Creation Gas Cost Increase separates gas into two dimensions. This page explains that model and how Foundry exposes it. The EIP and its tracing API proposal are evolving; select tools and a node that implement the rules of the network and block you are testing.\n\nWhich value should you use?\n\nYour questionValue or APIImportant boundary\nHow much regular gas did the last call or creation use?\nvm.lastFrameGas().gasTotalUsed\nExcludes EIP-8037 state gas; includes nested execution. Isolation adds transaction intrinsic gas and the regular calldata floor.\n\nHow much net state gas did that frame use?\nvm.lastFrameGas().gasStateUsed\nAlready net of state refills; can be negative. Zero without EIP-8037 or after frame rollback.\n\nWhat is the net sum of those frame components?\nint256(uint256(g.gasTotalUsed)) + int256(g.gasStateUsed)\nA signed measurement, not a sufficient gas limit or necessarily receipt gas.\n\nWhat ordinary refund did that frame accumulate?\nvm.lastFrameGas().gasRefunded\nFrame counter without isolation; finalized refund for an isolated transaction. Excludes state refills.\n\nHow much total gas was charged for a mined transaction?\neth_getTransactionReceipt → gasUsed; cast receipt <TX_HASH> gasUsed\nIncludes both dimensions after refund/floor processing. Do not add state gas again.\n\nWhat was the transaction's execution/state breakdown?\ndebug_traceTransaction with stateGasTracer, if the node supports it\nReturns gasUsed, executionGasUsed (the proposal’s regularGasUsed), stateGasUsed, and gasRefund. The dimension fields use block-accounting rules; receipt gas is gasUsed.\n\nHow much gas should I supply for another transaction?\neth_estimateGas; cast estimate; Alloy Provider::estimate_gas\nUse the target network, input, sender, value, and state. Estimates require a node implementing its fork rules.\n\nWhat gas fee did I pay?\nReceipt gasUsed × effectiveGasPrice\nCovers regular and state gas. Add blob or network-specific fee components separately when applicable.\n\nSee lastFrameGas for every field, Cast receipt, Cast estimate, and Alloy's gas trace types.\n\nExecution gas and state gas\n\nTermWhat it pays forWhat it excludes\nRegular gas (the EIP’s execution gas)\nComputation, memory expansion, state access, existing-state updates, and transaction intrinsic costs.\nState creation charges assigned to the EIP-8037 state dimension; blob gas.\n\nState gas\nState creation, such as a new storage slot, a new account, or deployed code. Reported net usage already deducts charges undone by state refills or rollback.\nThe accompanying regular execution costs; blob gas.\n\nCombined transaction gas limit (tx.gas)\nThe single gas budget you supply for intrinsic costs and both execution and state gas.\nBlob gas, which is accounted for separately.\n\nReceipt gas used (gasUsed)\nThe transaction's combined charged gas after ordinary refunds and the applicable calldata floor.\nUnused gas, blob gas, and separate network-specific fees.\n\nA state-changing opcode can incur both regular and state gas. State gas does not mean “all gas spent by storage opcodes.” Before EIP-8037, those operations still cost gas, but their costs use the ordinary single-dimensional schedule.\n\nHow the reservoir works\n\nYou still supply one transaction gas limit. After intrinsic gas, the EVM gives the transaction a regular gas allowance, capped by the protocol, and puts any excess into a state gas reservoir. Regular execution spends regular gas only. State creation spends the reservoir first and spills into regular gas once it is empty. State refills reverse creation charges and restore the gas pools according to EIP-8037's refill rules. Child calls receive the reservoir in full; their {gas: amount} allowance and the 63/64 rule apply to regular gas only.\n\ngasleft() reports regular gas only. Its delta can miss state gas paid from the reservoir or include state charges spilling into regular gas. A refill can make a later gasleft() larger, causing checked subtraction to revert. An empty reservoir does not disable state charges, and a large reservoir cannot fund regular execution. See the EIP's reservoir model and call-frame rules for the full mechanics.\n\nTwo meanings of “refund”\n\nOrdinary gas refunds accumulate in the EVM refund counter and are settled at the transaction boundary. EIP-3529 caps the applied refund at one fifth of gas spent; the EIP-7623 calldata floor can further limit the reduction in charged gas. A refund does not replenish gas available to execute instructions.\n\nState gas refills reverse state creation charges during execution, for example when a slot that was zero at transaction start is set and then cleared. They can replenish gas available during execution and are already deducted from net state gas. They are not the ordinary capped refund counter. A reverted or exceptionally halted frame reports zero net state gas, even if it temporarily needed state gas before failing; its regular execution still costs gas.\n\nA successful nested frame can have a negative state gas delta when it clears state created by an earlier frame in the same transaction. This is why Vm.Gas.gasStateUsed is signed. Transaction-level state gas is nonnegative. Use signed arithmetic for frame deltas and avoid subtracting state refills twice.\n\nWhy used gas is not required gas\n\nYour transaction budget must fund both regular and state gas when they are charged, before later refills or refunds. Regular execution must also fit its separate protocol cap. A transaction that allocates state and later undoes it can report little net state gas while requiring enough gas for the temporary allocation. Call forwarding and minimum gas checks can require additional headroom as well.\n\nFor example, if a frame reports 30,000 regular gas and 100,000 net state gas, their sum is 130,000 measured gas units. It is not proof that a transaction with a 130,000 gas limit will succeed: the frame can exclude intrinsic or caller-side costs, and it does not report peak temporary state consumption. Subtracting its ordinary refund makes an estimate even less reliable.\n\nFor an already executed transaction, read the receipt directly. In the EIP-8037 model, transaction gas before the ordinary refund includes both dimensions and intrinsic costs. The applied ordinary refund is capped, then the calldata floor determines the final charged amount. This settlement cannot generally be reconstructed from lastFrameGas, because a child frame is not the whole transaction.\n\nTransaction gas versus block gas\n\nReceipt gasUsed is the transaction's combined charge. Under EIP-8037, the block header uses the larger accumulated gas dimension instead. With EIP-7778, block accounting counts regular gas before ordinary refunds, while state gas remains net of state refills. See Alloy's gas accounting documentation for the fields and calldata-floor rules.\n\nDo not sum parent and child frames to reconstruct a transaction total: parent measurements already include nested execution. Some state charges and rollbacks also occur outside opcode steps.\n\nWhich networks are affected?\n\nExecution environmentBehavior\nFoundry's Ethereum EVM with evm_version = \"amsterdam\" or a later supported fork\nUses EIP-8037 regular/state gas accounting. This is a local execution setting, not evidence of activation on a live chain.\n\nEthereum forks before Amsterdam, or another network that has not activated EIP-8037\nNo separate state gas dimension: Vm.Gas.gasStateUsed is zero. State creation still costs ordinary gas and is included in gasTotalUsed.\n\nA custom network or an L2\nFollows its own hardfork and gas schedule. EVM compatibility alone does not establish EIP-8037 support, pricing, activation dates, or fee equivalence.\n\nRPC tracing on any network\nDepends on both the block's rules and the node's tracer support. Optional state fields may be absent; an unsupported stateGasTracer can return an RPC error. An absent field means “not reported,” not measured zero.\n\nWhen compiling with Solidity 0.8.36, Amsterdam is experimental and also requires --experimental (or experimental = true in foundry.toml).\n\nPin the EVM version, fork block, optimizer settings, and isolation mode when comparing measurements. Use a Foundry version supporting the selected fork and a current forge-std Vm.Gas interface containing gasStateUsed. For a live network, consult that network's activation schedule rather than assuming Amsterdam rules from a chain name or from Alloy's ability to decode the fields.\n\nRPC field names differ between implementations. The execution-apis proposal names the execution dimension regularGasUsed; Alloy and reth serialize executionGasUsed. Check what your node returns and whether your Alloy version accepts both names when decoding.\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":2266,"crawled_at":1791194205750}
+{"id":10353,"url":"https://docs.sui.io/develop/sui-architecture/components","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Components | Sui Documentation","text":"Sui is a layer 1 blockchain. Layer 1 networks consist of the following primary components:\n\nNodes that run the network's binaries and participate in network activity such as consensusConsensusThe process by which the majority of nodes agree on the current state of the network. Nodes provide compute and storage resources to the network.\n\nThe consensus mechanism used to validate transactions.\n\nTransactions themselves, which on Sui reflect onchain operations such as creating objects or sending assets.\n\nTokens used to pay for resources and transactions on the network.\n\nOn Sui specifically, other core components include:\n\nObjects, the most basic unit of storage on Sui that are addressable onchain by unique IDs.\n\nMoveMoveAn open source programming language used for all activity on Sui., the programming language used to create smart contracts on Sui.\n\nNetworks​\n\nSui operates multiple networks that are comprised of these essential components. Each network serves a different purpose:\n\nMainnetMainnetProduction network for live transactions and real-value assets.: Production network for live transactions and real-value assets.\n\nTestnetTestnetStaging network for testing changes before production deployment.: Staging network for testing changes before production deployment.\n\nDevnetDevnetFor developing and testing new features.: For developing and testing new features.\n\nLocalnetLocalnetLocal network you can run on your own machine for optimized development.: Local network you can run on your own machine for optimized development.\n\nLearn more about the Sui networks.\n\nNodes​\n\nOn Sui, validatorValidatorResponsible for executing tasks like staking, gas price references, and tallying rules. nodes run the consensus mechanism that orders and commits all onchain activity. Full nodes do not take part in consensus. They verify the committed state independently and locally, then serve queries about it.\n\nThere are 2 types of nodes on Sui:\n\nFull nodeFull nodeResponsible for validating blockchain activity.: Responsible for validating blockchain activity such as transactions, checkpointsCheckpointCreated after transaction execution to provide a certified record of chain history., and epoch changes. Each full node stores the blockchain's state and history to serve queries.\n\nValidator node: Responsible for executing more tasks than full nodes, such as staking, gasGasThe computational cost of execution and object storage for a transaction. price references, and tallying rules.\n\nLearn more about nodes on Sui.\n\nDelegated proof-of-stakeDPoSConsensus mechanism used by Sui. consensus​\n\nSui uses a delegated proof-of-stake (DPoS) consensus mechanism to validate transactions. Validators must stake SUI tokens on the network, either their own or delegated by other token holders, to participate in consensus. This approach aligns validator incentives with network security and efficiency without the high energy costs of proof-of-work systems.\n\nTo learn more about consensus on Sui, see:\n\nSui Consensus\n\nEpochs and reconfiguration, which is when the validator set can change\n\nTransactions​\n\nTransactions on Sui consist of several commands that execute on inputs. These inputs define the result of the transactionTransactionA number of commands that execute on inputs to define the result of the transaction.. All updates to the Sui network happen through transactions. There are only 2 types of transactions on Sui:\n\nProgrammable transaction blocksProgrammable transaction blocksDefine all user transactions on Sui.: Define all user transactions on Sui, as they can be submitted by anyone. They are used for activities such as sending tokens, creating objects, and interacting with smart contracts.\n\nSystem transactionsSystem transactionsOnly submittable by validator nodes.: Only submittable by validator nodes. These transactions are for network functions such as changing epochs or starting checkpoints.\n\nLearn more about both types of transactions, or learn more about programmable transaction blocks.\n\nTokens​\n\nThe native token for Sui is SUI. Transactions on Sui often deal with small fractions of the value of 1 SUI. To make it easier to work with transactions, Sui also provides the token MISTMISTThe smallest unit of SUI.. 1 billion MIST equals 1 SUI.\n\nOn the network, everything has a cost. It costs money to provide computational power, process transactions, and store transaction data. This cost is referred to as gas. You pay gas fees with a blockchain's native token, in this case, SUI or MIST.\n\nTo learn more about the tokenomics of Sui, see the following topics:\n\nSui Tokenomics\n\nGas Fees\n\nStaking and Unstaking\n\nSui Bridging\n\nObjects​\n\nThe basic unit of storage in Sui is the objectObjectThe basic unit of storage on Sui.. Blocks on the chain are actually objects that define assets rather than basic key-value stores that define addressesAddressA unique, anonymous identity on a blockchain network.. Sui's storage is centered around objects that are addressable onchain by unique IDs. A smart contract is an object (called a Sui Move packagePackageSmart contracts on Sui.), and these smart contracts manipulate objects on the Sui network.\n\nEvery object has an owner field that dictates how you can use it in transactions. Objects can be owned by an address or party, or they can be immutable, shared, or wrapped.\n\nLearn more about the Sui Object Model or Object Ownership.\n\nMove​\n\nMove is an open source programming language that is used for all activity on Sui, such as creating or trading NFTs, using apps, and all other transaction-based events. It is used for writing safe packages that can create and manipulate objects onchain.\n\nMove is platform-agnostic to enable common libraries, tooling, and developer communities across blockchains with vastly different data and execution models.\n\nTo learn more about Move, see Move Concepts.\nRelated topics\n\nOperator Guides\nGuides for operators on the Sui network. Whether you are running a full node for your app or operating as a validator on the Sui network, these guides help you set up your environment and operate your network.\nStorage\nAn overview of Sui's storage architecture, including validator and full node storage requirements, pruning, snapshots, checkpoints, and how storage fees and rebates are calculated.\nConsensus\nOverview of the Sui consensus mechanism.\nWhat is a Transaction?\nSui has two types of transactions, programmable transaction blocks and system transactions.\n\nNetworksNodes\n\nDelegated proof-of-stake consensus\nTransactions\nTokens\nObjects\nMove\n\nWas this page helpful?","tokens":1642,"crawled_at":1791194206258}
+{"id":10354,"url":"https://a16zcrypto.com/posts/tags/government-agencies","domain":"a16zcrypto.com","chapter":"research","title":"government agencies - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\ngovernment agencies\n\nFeed\nFILTERS\n(1)\nclear filters\n\ncategories\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\n(1) recommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nclear all government agencies\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n08.13.25 / Miles Jennings, Michele Korver, Jai Ramaswamy, Amanda Tuminelli and Scott Walker\nSEC Safe Harbor Proposal for Blockchain Apps: Exempting DeFi and NFT Interfaces from Broker Registration\nProposal for SEC safe harbor that exempts non-custodial blockchain apps like DeFi and NFT platforms from broker registration requirements.\n\npolicy & regulation\ngovernment agencies\nregulatory know-how\n\n08.13.25 / Miles Jennings, Aiden Slavin and David Sverdlov\nA safe harbor for software: Why the SEC should clarify broker rules for blockchain apps\nAn SEC safe harbor for blockchain apps would ensure non-custodial, non-discretionary DeFi and NFT interfaces aren’t misclassified as brokers.\n\npolicy & regulation\ngovernment agencies\nregulatory know-how\n\n07.31.25 / Miles Jennings, Michele Korver, Jai Ramaswamy, Scott Walker, David Sverdlov and Aiden Slavin\nResponse to the Senate Banking Committee digital asset market structure request for information\n\npolicy & regulation\ngovernment agencies\n\n01.22.25 / Scott Walker and Bill Hinman\nA new (digital) age at the SEC\nThe SEC can and should take immediate steps to regulate crypto from providing guidance on airdrops to updating crowdfunding and custody rules.\n\npolicy & regulation\ngovernment agencies\nop-eds\nregulatory know-how\n\n11.04.24 / Brian Quintenz\n7 things U.S. government agencies can do to help seize the web3 opportunity\nSimple steps that U.S. government departments and agencies could take today — absent legislation — to help crypto thrive\n\npolicy & regulation\ngovernment agencies\nop-eds\n\n10.14.24 / Michele Korver and Jai Ramaswamy\nCrime and crypto: Concrete steps to address money laundering\nHow policymakers can implement measures that will help catching bad actors and reign in illicit financial activity in crypto\n\npolicy & regulation\ncompliance & illicit finance\ngovernment agencies\nop-eds\n\n03.02.23 / Miles Jennings, Michele Korver, Brian Quintenz and Tim Roughgarden\nComment to the Office of Science and Technology Policy on Digital Assets Research and Development (3.3.23)\n\npolicy & regulation\ngovernment agencies\n\n09.20.22 / Scott Walker and Neel Maitra\nA Call to the SEC: Treat Crypto Assets as if Clients Matter\nThe SEC's \"custody rule\" needs updating in the context of crypto where it's at odds with the fiduciary duty asset managers owe their clients.\n\npolicy & regulation\ngovernment agencies\nop-eds\n\n08.25.22 / Michele Korver\na16z crypto’s Response to the Department of Treasury’s Request for Comment\nOn August 8, 2022, a16z responded to the Department of the Treasury’s request for comment entitled, “Ensuring Responsible Development of Digital Assets; Request for Comment.” Treasury issued the request for comment in light of President Biden’s Executive Order, which directed the appropriate federal agencies to investigate the potential use of blockchain technology. a16z crypto’s response...\n\npolicy & regulation\ncomment letters & amicus briefs\ngovernment agencies\n\n08.18.22 / Michele Korver, Jai Ramaswamy and Sonal Chokshi\nCrypto Regulations, Illicit Finance, Privacy and Beyond\nEPISODE SUMMARY with @michelekorver @jai_ramaswamy @smc90 We tease apart the facts vs buzz around recent news — Tornado Cash sanctions, and arrest of a suspected developer — including what’s novel and what’s not, as well as broader backdrop. But we also share an evergreen explainer that goes well beyond recent events, to help crypto founders...\n\ncompany building\ncompliance & illicit finance\ngovernment agencies\npodcast\nregulatory know-how\nzero knowledge & succinct proof systems\n\n01.06.22 / Tomicah Tillemann and James Rathmell\nHow to Build a Better Internet: 10 Principles for World Leaders Shaping the Future of Web3\nThe year 2021 marked a watershed moment for web3. Significant numbers of policymakers began to grasp the potential of web3 to democratize access to opportunity, provide individuals with more control of their data, and build a better internet. In the year ahead, many of these leaders will work to create legal and regulatory architecture to...\n\ncompany building\ngovernment agencies\nop-eds\n\n12.16.21 / Tomicah Tillemann and James Rathmell\nPrediction for the New Year: A Web3 Midterm\nWe recently commissioned a public opinion survey* to gauge how significant the web3 constituency will be as we head into the U.S. midterm elections next year. The findings were mind-blowing for the a16z web3 team, and we wanted to share the results.We all know 2021 has been an extraordinary year for web3. DAOs rallied to...\n\npolicy & regulation\ndata insights\ngovernment agencies\nop-eds\n\n10.04.21 / Tomicah Tillemann, Miles Jennings and James Rathmell\nOur Proposals to the Senate Banking Committee\nWe are at the threshold of the third generation of the internet: web3. Given the pace of innovation in this space, it has been challenging for many policymakers to keep up. That’s why we were so heartened by the Senate Banking Committee’s call for feedback on clarifying laws around digital assets and decentralized technology. Maintaining...\n\npolicy & regulation\ngovernment agencies\nop-eds\n\n01.03.21 / Katie Haun\nWhy a16z Opposes Secretary Mnuchin’s FinCEN Midnight Crypto Rulemaking\nA Treasury Department proposal bypasses established rulemaking procedures, fails to solve the real issues, and threatens to harm U.S. innovation.\n\npolicy & regulation\ncomment letters & amicus briefs\ngovernment agencies\nop-eds\n\n02.21.20 / Scott Kupor\nReading Between the Lines: SEC, Telegram, and Rule 144\nHidden in the SEC’s complaint against Telegram is an interesting nuance with potential implications for the broader private equity markets.\n\npolicy & regulation\ngovernment agencies\n\n10.21.19 / Scott Kupor\nMutability in Crypto and Recent Moves by the SEC\nOver the last few weeks, we’ve seen a number of SEC actions surrounding crypto that provide some meaningful insight into the regulatory posture of the agency. Last week, the SEC filed an action to enjoin Telegram (creators of the Telegram Open Network, or “TON”) from distributing tokens (called “Grams”) that it had promised to purchasers...\n\npolicy & regulation\ngovernment agencies\n\n09.16.19 / Christopher Giancarlo\nCFTC Chairman Christopher Giancarlo on Regulating Crypto\nEditor’s Note: We need to develop new policy approaches to keep pace with fast-moving blockchain technology. So what should a 21st century regulator look like? Chairman of the U.S. Commodity Futures Trading Commission (CFTC), Christopher Giancarlo (more about him below) shared the following remarks on how the CFTC has been evolving and crafting a modern...\n\npolicy & regulation\ngovernment agencies\nop-eds\n\n05.14.19 / Katie Haun\nKik and the SEC: What’s Going On and What Does It Mean for Crypto?\nThe SEC told Kik it was thinking of pursuing action for violating U.S. securities laws. What might it tell us about how far regulators are willing to stretch the law?\n\npolicy & regulation\ngovernment agencies\nregulatory know-how\n\n07.15.18 / Katie Haun, Robin Weisman and Sonal Chokshi\na16z Podcast: The Regulatory Landscape for Crypto\nWhat’s going on, regulation-wise, in crypto? How should people who want to join a company or build something new in the space think about the regulatory environment? What to make of all the headlines, or the “alphabet soup” of agencies potentially involved in regulating crypto? This episode of the a16z Podcast shares principles — as well...\n\ncompany building\ncrypto basics\nglossaries & terminology\ngovernment agencies\nregulatory know-how\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":2632,"crawled_at":1791194231209}
+{"id":10355,"url":"https://docs.balancer.fi/build/README.md","domain":"docs.balancer.fi","chapter":"defi_protocols","title":"","text":"## Build on Balancer\n\nAMMs built on the Balancer protocol benefit from the security of the Balancer vault. This enables developers to utilize\nthe well-developed Balancer AMM ecosystem, while the vault's optimized architecture streamlines the development process\nand allows teams to concentrate on their product.\n\nWe assist teams throughout this process, leveraging our extensive experience in bringing innovative AMMs to market.\nThis includes addressing finer details such as aggregator integration, which is vital for any new AMM to capture the\nnecessary organic flow to compete effectively.\n\nOur aim is to simplify the development process and facilitate the creation of novel AMMs with minimal friction.\n\n:::info\nWhen adding new tokens to Balancer pools, keep in mind the [Vault compatibility requirements](../partner-onboarding/onboarding-overview/core-pools.md#token-requirements).\n:::\n\nWhen building on Balancer, there are three paths to explore:","tokens":238,"crawled_at":1791194233001}
+{"id":10356,"url":"https://gov.uniswap.org/t/rfc-governance-process-upgrade-establishing-a-statute-of-limitations-for-temperature-checks/26002","domain":"gov.uniswap.org","chapter":"governance_daos","title":"[RFC] Governance Process Upgrade: Establishing a Statute of Limitations for Temperature Checks - Requests for Comment - Uniswap Governance","text":"[RFC] Governance Process Upgrade: Establishing a Statute of Limitations for Temperature Checks\n\nRequests for Comment\n\nEren_Targ5\n\nJanuary 18, 2026, 12:06pm\n\n1\n\n1. Summary\n\nThis proposal seeks to establish a formal “Statute of Limitations” for Uniswap Governance proposals. Specifically, it mandates that any proposal which passes a “Temperature Check” (Snapshot vote) must proceed to an on-chain vote within 90 days.\n\nIf a proposal fails to move to an on-chain vote within this 90-day window, the Temperature Check is declared “Expired” (or “Dead”). To proceed, the proposer must restart the governance process with a new Temperature Check to ensure community sentiment remains current.\n\n2. Motivation\n\nCurrently, Uniswap Governance operates on a continuous cycle. Unlike Optimism or Arbitrum, which utilize specific “Governance Seasons” or “Cycles” that naturally flush out stale proposals, Uniswap proposals can technically remain “pending” indefinitely after passing a Snapshot vote.\n\nThis creates critical risks and inefficiencies:\n\nMarket Conditions Change: A proposal approved 6 months ago may be financially dangerous today due to changes in market volatility, token prices, or protocol upgrades (e.g., v3 to v4).\n\n“Zombie” Proposal Risk: There is currently no rule preventing a delegate from taking a Snapshot vote from 2022 and putting it on-chain today, bypassing current community sentiment.\n\nGovernance Clutter: It is difficult for delegates to track which initiatives are active versus abandoned.\n\nBy implementing a 90-day expiration, we align Uniswap with industry best practices and ensure that every on-chain vote reflects the current will of the DAO*.\n\n3.Specification\n\nWe propose adding the following clause to the official Uniswap Community Governance Process:\n\n“Validity of Temperature Checks: A successful Temperature Check (Snapshot vote) is valid for a period of 90 days from the date the vote closes. If an on-chain governance proposal is not submitted within this 90-day window, the Temperature Check is considered Expired. The proposer must post a new Temperature Check and receive fresh community approval before proceeding to an on-chain vote.”\n\nDefinition of Proposal States\n\nStatus\nDefinition\nAction Required\n\nLive / Active\n\nA proposal that has passed Snapshot within the last 90 days.\n\nCan proceed to On-chain Vote immediately.\n\nDead / Expired\n\nA proposal that passed Snapshot >90 days ago but has not yet been submitted on-chain.\n\nMust re-run the Temperature Check phase to verify current sentiment.\n\nHandling Long-Term Initiatives\n\nWe recognize that major protocol upgrades often require development timelines longer than 90 days. However, governance mandates should not be indefinite. If the technical implementation takes longer than 90 days, the proposer must follow the **“Re-affirmation Process”**:\n\n1. The “Refresh” Vote: The proposer does not need to start from zero with a new RFC.\n\n2. Action: They simply post a “Re-affirmation Snapshot” (Temperature Check) with the final code/parameters.\n\n3. Rationale: In DeFi, 6 months is a long time. A mandate given in January might be dangerous to execute in July if market conditions have shifted (e.g., bridge hacks, new regulation).\n\n4. Rationale & Precedent\n\nThis change brings Uniswap into alignment with the hygiene standards of other mature DeFi protocols:\n\nMakerDAO (Sky): Enforces a strict 30-day expiration on Executive Proposals. As seen in a recent proposal explicitly mandates that “ If a proposal does not pass/execute within 30 days, it expires to prevent stale code or parameters from affecting the protocol”.\n\nOptimism: Utilizes “Governance Seasons.” Proposals must be submitted and voted on within a specific seasonal window; if they miss it, they must be resubmitted the following season.\n\nUniswap (Current): Lacks both seasons and expiry rules, leaving the DAO exposed to “Zombie Proposals” indefinitely.\n\n5. Comparison: Old vs. New Structure\n\nFeature\nCurrent Uniswap Governance\nProposed Uniswap Structure\n\nSnapshot Validity\n\nIndefinite (Technically valid forever)\n\n90 Days (Statute of Limitations)\n\nStale Proposal Risk\n\nHigh. A proposal from 1 year ago could theoretically be executed today despite market changes.\n\nLow. Proposals must have a fresh community signal (within 3 months) to execute.\n\nGovernance Cycle\n\nContinuous / Unbounded\n\nContinuous, but with a rolling expiration window to ensure freshness.\n\nRe-submission\n\nNot defined / Confusing\n\nClear Process: If >90 days, you must re-post Snapshot.\n\n6. Precedent of Risk\n\nWe have already seen “Zombie Proposals” confuse the governance process:\n\n* The Gnosis Deployment (2022-2023):A deployment passed a vote but sat pending for 11 months. During that time, the bridge provider (Nomad) was hacked. Without an expiry rule, a stale mandate could theoretically be used to execute unsafe code.\n\n* The Fee Switch (2024-2025): The fee switch mandate sat dormant for over 12 months, requiring a community member to manually post a “Re-Temperature Check” to verify if the will of the DAO had changed.\n\nOur proposal removes this ambiguity. Instead of relying on the goodwill of authors to “re-check” sentiment, we enforce a hard 90-day expiry.\n\n7. Success Metrics\n\nZero “Zombie” Executions: No proposals older than 90 days are executed on-chain without a fresh check.\n\nDelegate Clarity: Delegates can easily view the “active” pipeline without filtering through years of stale posts.\n\nSafety: Reduced risk of executing outdated parameters (e.g., fee switches or grant distributions based on old token prices).\n\n8. Next Steps\n\n1. RFC Period: Gather feedback on this post for 7 days.\n\n2. Snapshot Vote: Post a Temperature Check to ratify this rule change.\n\n3. Documentation Update: Upon passing, the Uniswap Governance Docs and Forum Guidelines will be updated to reflect the 90-day expiry rule.\n\n9 Likes\n\nEren_Targ5\n\nFebruary 19, 2026, 5:56pm\n\n2\n\nIf no one has any objections / comments for the proposal in the next 3 days then we will be putting it up for a vote next week.\n\nHeadOps\n\nFebruary 22, 2026, 3:52am\n\n3\n\nGreat proposal — cutting zombie tasks is exactly what DAOs need to stay lean.\n\nOne thing I’d add: we should watch out for “zombie proposals” too.\n\nJust like tasks, approved proposals often die after the vote. Not because they’re bad ideas, but because there’s no system to actually get them done. I’ve seen this happen on Uniswap — good proposals pass, then… nothing. No follow-through, no accountability, just silence until everyone forgets.\n\nHere’s what helps: an Execution Registry.\n\nSimple idea. Once a proposal passes, it goes into a public tracker. Someone’s named responsible. Deadline’s set. Success criteria are clear. Progress gets checked weekly. A few community members rotate in to verify the work actually got done. When it’s finished, it’s marked complete and we document what worked (or didn’t).\n\nWhy this matters for your proposal:\n\nEvery task we kill gets recorded — why we cut it, what we learned\n\nNew proposals get a reality check before they go to vote\n\nPeople can actually see what’s getting delivered, not just what’s getting approved\n\nI’m a DAO Operations Partner — I help teams turn governance into results without turning into a company. Done this for a few DAOs and happy to share what works.\n\nLet me know if you want to dig into this or test it out.\n\nThanks for pushing Uniswap to run tighter.\n\nManugotsuka\n\nMarch 6, 2026, 4:31pm\n\n4\n\nThe following reflects the views of L2BEAT’s governance team, composed of @kaereste and @Manugotsuka, and it is based on their combined research, fact-checking, and discussion.\n\nWe voted FOR.\n\nWe see this as a reasonable governance improvement. Snapshot approvals can remain quiet for long periods, creating uncertainty about whether an old mandate still reflects the DAO’s current will. Given how quickly conditions change in crypto, executing a proposal many months after its initial approval may no longer reflect delegate sentiment or current priorities.\n\nA 90-day window seems like a sensible balance. It gives proposers enough time to move forward while keeping governance signals relatively fresh. We also think the reaffirmation Snapshot is a practical mechanism for initiatives that take longer to prepare, allowing the community to confirm support without restarting the entire process.\n\n3 Likes\n\nblockful\n\nMarch 13, 2026, 5:03pm\n\n5\n\nWe voted FOR the proposal.\n\nKeeping a proposal approved on Snapshot eligible to be submitted at any time is indeed a governance risk for Uniswap, which is why this initiative is a good idea.\n\nHowever, the procedure, as seen in Arbitrum or Optimism, is more of a social convention than an on-chain mechanism that protects the DAO from any proposal being submitted on-chain without discussion or context.\n\n3 Likes\n\nLEON_THE_GR8T\n\nJune 10, 2026, 7:08pm\n\n6\n\nThis is beautiful, as this proposal addresses a real problem that’s been quietly undermining Uniswap governance for a while — and I support it in principle.\n\nThe “Zombie Proposal” risk alone justifies this change. A delegate being able to push a 2022 Snapshot vote on-chain today — with zero re-validation of community sentiment — is a genuine governance vulnerability. Market conditions, protocol upgrades, and community priorities shift significantly over months. Any vote that bypasses current sentiment isn’t democratic governance, it’s a loophole.\n\nThe 90-day window feels reasonable. It’s long enough to allow proper deliberation without creating unnecessary pressure, but short enough to ensure proposals reflect current community consensus.\n\nOne thing I’d push the proposers to clarify though: what happens to proposals that are mid-deliberation when this rule passes? Do existing pending Snapshot votes get a grace period, or do they expire immediately? That transition mechanism matters and could create controversy if left ambiguous.\n\nAlso worth considering — should the 90-day clock pause during major protocol upgrade periods (like a v3 to v4 transition) where governance bandwidth is naturally stretched? A simple exception clause could prevent good proposals from dying for timing reasons alone.\n\nOverall: strong proposal. Clean it up with a clear transition plan and it should pass comfortably. Voting YES.\n\ncroutondigital\n\nJune 29, 2026, 1:09pm\n\n7\n\nI generally agree with the goal of preventing stale mandates from being carried forward indefinitely. Governance decisions are made within a specific context, and community sentiment, market conditions, and protocol priorities can change significantly over time.\n\nThat said, I wonder whether a fixed 90-day window may unintentionally create friction for more complex initiatives. Some proposals require audits, implementation work, legal review, or coordination across multiple stakeholders before they are ready for an on-chain vote. In those cases, the delay may not reflect a lack of support but simply the operational reality of executing large initiatives.\n\nThe proposed re-affirmation process seems like a reasonable compromise, but I think it may be worth considering whether the expiration period should vary depending on proposal type. For example, operational or parameter changes could have shorter validity windows, while large protocol upgrades or infrastructure initiatives might justify a longer period before requiring renewed community approval.\n\nI also think there is value in distinguishing between “inactive” proposals and “expired” proposals. A proposal that has passed a Temperature Check and is actively progressing through development may not present the same governance risk as a proposal that has been dormant for months with no visible progress.\n\nOverall, I support the principle that governance mandates should remain fresh and representative of current sentiment. The key challenge will be balancing governance hygiene with the practical realities of delivering complex protocol changes.\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nProposed Simplifications to the Uniswap Governance Process\n\nGovernance-Meta\n\n3\n\n5988\n\nDecember 7, 2022\n\nCommunity Governance Process Update [Jan 2023]\n\nGovernance-Meta\n\n4\n\n38245\n\nJanuary 9, 2026\n\n[RFC - Update] Community Governance Process Changes\n\nRequests for Comment\n\n4\n\n8968\n\nDecember 24, 2022\n\n[RFC] Community Governance Process Changes\n\nRequests for Comment\n\n11\n\n4561\n\nDecember 6, 2022\n\nCommunity Governance Process\n\nGovernance-Meta\n\n30\n\n58333\n\nApril 7, 2023","tokens":3105,"crawled_at":1791194251790}
+{"id":10357,"url":"https://docs.balancer.fi/partner-onboarding/onboarding-overview/introduction.md","domain":"docs.balancer.fi","chapter":"defi_protocols","title":"","text":"## Partner Onboarding\n\n:::info\nFrom product details to step-by-step integration guides, this documentation provides partners with everything they need to onboard into the Balancer Ecosystem.\n:::\n\n### Overview\n\n#### Balancer Technology\n\nWith a vastly simplified developer experience, 100% boosted pools, LST base pairings, and customizable pool hooks, Balancer v3 provides partners with a streamlined hub to optimize yield-bearing liquidity, build robust governance tokenomics, and streamline AMM innovation.\n\n\\::: tip\nWant to learn more about Balancer? Click [here](../../concepts/core-concepts/introduction.md)\n\\:::\n\n#### Unique AMM Designs and Products\n\nBalancer Technology provides innovative AMM designs such as\n\n1. **[Boosted Pools](./products/boostedpools.md)**: Leverage token utilization for optimal yield.\n2. **[Yield-Bearing liquidity pools](products/lstandlrt.md)**: Optimized LP tech for liquid-staking tokens (LST) and yield-bearing stablecoins.\n3. **[ve8020 / Governance Tokenomics](products/ve8020.md)**: Enhanced liquidity dynamics and aligned incentive structures for governance positions.\n4. **[Stable Pools](products/stablecoinliquidity.md)**: Advanced technology for highly correlated stable assets, such as Gyro-stable pools.\n\n### High-Level Overview of Onboarding Process\n\nOnboarding into Balancer varies depending on the AMM technology you want to use. Some components are simple and straightforward to use, while others may require expert assistance from our core contributors.\n\nLearn more about our onboarding journey, use the Balancer Tech Product Wizard to find the best solution for your needs, or check out our product case studies below.\n\n:::info\nWhen adding new tokens to Balancer pools, keep in mind the [Vault compatibility requirements](../../partner-onboarding/onboarding-overview/core-pools.md#token-requirements).\n:::\n\n#### Onboarding Journey\n\nOnboarding your asset onto Balancer involves three main steps:\n\n* **Choose a Pool Type**: Select the pool type that best fits your use case.\n* **Customize Pool Logic**: Utilize Balancer v3's [hooks](../../concepts/core-concepts/hooks.md) for tailored functionality.\n* **Configure Incentives (optional)**: Stand up a [gauge](./../onboarding-overview/gauge-onboarding.md) to stream your own secondary rewards. BAL emissions to gauges have been halted per [BIP-919](https://forum.balancer.fi/t/bip-919-bal-tokenomics-revamp/7001).\n\n\\::: tip\nBalancer contributors are happy to help during the onboarding process. Feel free to reach out to us on our [Discord](https://discord.balancer.fi)!\n\\:::\n\n#### Find the Right Product for Your Needs\n\nUse our Product Wizard to discover the best solutions for your business. Explore use cases and read success stories. <DecisionTree />\n\n### Balancer Deployments\n\nLooking for deployment-specific information? Choose a specific deployment type below to explore various options and next steps. <PartnerOnboarding />","tokens":732,"crawled_at":1791194259473}
+{"id":10358,"url":"https://www.getfoundry.sh/introduction/prompting","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Prompting – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nPrompting\n\nYou can speed up smart contract development by using AI to draft boilerplate, testing patterns, and documentation. The best results come from structured prompts with clear constraints and examples.\n\nUse a structured prompt\n\nCopy the template below and replace the <user_prompt> section with your project details.\n\nPrompt template\nYou are an expert Solidity engineer using Foundry.\n\nProject context:\n- Repository layout: {FOLDERS}\n- Solidity version: {SOLC_VERSION}\n- Dependencies: {DEPENDENCIES}\n- Target chain(s): {CHAINS}\n\nConstraints:\n- Use Foundry tools only (forge, cast, anvil, chisel)\n- Prefer forge-std testing utilities\n- Keep functions small and focused\n- Avoid unsafe patterns and unchecked external calls\n\nTesting requirements:\n- Include unit tests and fuzz tests where applicable\n- Add revert tests for all failure paths\n- Use vm.assume or bound to constrain fuzz inputs\n\nStyle:\n- Use clear naming and short helper functions\n- Add comments only when logic is non-obvious\n\n<user_prompt>\nDescribe the contract or tests you want to generate.\n</user_prompt>\n\nExample usage\n\nExample\n<user_prompt>\nCreate a minimal ERC20 with mint and burn functions. Include a test suite that verifies:\n- mint increases balance and total supply\n- burn decreases balance and total supply\n- unauthorized minting reverts\n</user_prompt>\n\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":358,"crawled_at":1791194279817}
+{"id":10359,"url":"https://gov.uniswap.org/t/rfc-introduction-and-advice-seeds-bones-web3-survival-moba-on-unichain-ecosystem-grant-inquiry-general-guidance/26123","domain":"gov.uniswap.org","chapter":"governance_daos","title":"[RFC] Introduction and Advice: \"Seeds & Bones\" Web3 Survival MOBA on Unichain & Ecosystem Grant Inquiry / General Guidance - Requests for Comment - Uniswap Governance","text":"[RFC] Introduction and Advice: \"Seeds & Bones\" Web3 Survival MOBA on Unichain & Ecosystem Grant Inquiry / General Guidance\n\nRequests for Comment\n\nsquidwardjalapeno\n\nJune 14, 2026, 3:00am\n\n1\n\nAuthor: Jeffy B / Joseph Cipolla\n\nDate: 06/13/2026\n\nContract Address (Deployed on Unichain): 0xb762c3B3f544B04D0eAD51Fa1883Ee0f0Ec87cE4\n\nIntroduction\n\nHello Uniswap and Unichain community,\n\nI am the developer behind Seeds & Bones, a retro-survival multiplayer online battle arena (MOBA) game. I have recently deployed the core vault contract on Unichain at 0xb762c3B3f544B04D0eAD51Fa1883Ee0f0Ec87cE4 and wanted to introduce myself to the community, share what I am building, and ask for guidance on the best pathways for ecosystem integration and developer funding.\n\nAbout Seeds & Bones\n\nSeeds & Bones is a fully playable multiplayer game combining classic top-down survival elements—such as farming, autonomous workforce management, and trading—with competitive Web3 elements.\n\nAutoritative Architecture: To provide a responsive, 60 FPS multiplayer experience, the game uses an authoritative hybrid model. The game state is computed off-chain, and rewards are settled securely on-chain using a cryptographic signature/voucher verification system.\n\nWhy Unichain: I selected Unichain because its sub-second block times and low transaction costs are highly suited for the micro-transactions required by interactive Web3 gaming.\n\nValue to the Unichain Ecosystem\n\nI believe gaming is one of the most effective funnels for onboarding new users. Seeds & Bones is designed to drive:\n\nOn-Chain Activity: Regular, game-driven micro-interactions (claiming chests, upgrading profiles, withdrawing rewards) directly generate continuous transaction volume.\n\nAccessible Onboarding: A hybrid Web2/Web3 login structure allows players without MetaMask to play instantly, guiding them into creating wallets as they earn achievements.\n\nLooking for Guidance\n\nMy next milestone is bootstrapping our in-game withdrawal/rewards vault to support player incentives during our initial base funding of the Contract address.\n\nAs an independent developer new to the Uniswap governance structure, I would appreciate guidance from community members, delegates, and foundation representatives on the following:\n\nEcosystem Grants: Given our target of driving active transaction volume and contract interactions on Unichain, where would be the best category to initiate an ask for an Ecosystem Grant on this board? Are there any programs being initiated on Uniswap to promote Web3 Gaming initiatives?\n\nVault Security Feedback: Our vault operates on a cryptographic voucher system where the contract only permits withdrawals validated by our authoritative server signature. I welcome any feedback or code review from community developers on our contract logic.\n\nCollaboration Opportunities: I am actively looking for feedback from Unichain delegates or builders who are interested in playtesting the game or discussing integration ideas.\n\nThank you for your time, and I look forward to your feedback and guidance on how I can best contribute to the Unichain ecosystem.\n\nFULLY VERIFIED CONTRACT HERE:\n\nhttps://uniscan.xyz/address/0xb762c3b3f544b04d0ead51fa1883ee0f0ec87ce4\n\nPLAY THE GAME HERE:\n\nhttp://seedsandbones.onrender.com\n\nWHITEPAPER:\n\nhttps://docs.google.com/document/d/1FatkyNIqW7tuL5J0luz1u9omJ1xntNmDenmLJtmIVfA/edit?usp=drivesdk\n\nPARAGRAPH ARTICLE:\n\nhttps://paragraph.xyz/@0xa6518181b2db530dd1acfdfb389f19b18626c5c6/introducing-seeds-and-bones?referrer=0xa6518181B2DB530DD1ACFDfb389f19B18626c5c6\n\nMEDIUM ARTICLE:\n\nhttps://medium.com/@josephmcipolla/introducing-seeds-bones-e7804016826c\n\nGITHUB:\n\nhttps://github.com/squidwardjalapeno/blockchainmmo\n\nDISCORD:\n\nhttps://discord.gg/v8Sc9ZwkH\n\n2 Likes\n\n[RFC] Web4 Autonomous State Engines on Unichain: Utilizing ERC-6551 & Sovereign ERC-721 Force Transfers for Dynamic Asset Orchestration\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[Governance Proposal] Deploy Uniswap V3 on Moonbeam\n\nRequests for Comment\n\n11\n\n7092\n\nFebruary 7, 2023\n\nDeploy Uniswap v3 on Moonbeam (2023)\n\nRequests for Comment\n\n16\n\n7749\n\nOctober 4, 2023\n\n[RFC]: Complete initial funding of the Uniswap Foundation\n\nRequests for Comment\n\n15\n\n7771\n\nOctober 7, 2023\n\n[Governance Proposal]: Complete initial funding of the Uniswap Foundation\n\nRequests for Comment\n\n8\n\n6487\n\nOctober 16, 2023\n\n[RFC] Web4 Autonomous State Engines on Unichain: Utilizing ERC-6551 & Sovereign ERC-721 Force Transfers for Dynamic Asset Orchestration\n\nRequests for Comment\n\n0\n\n94\n\nAugust 4, 2026","tokens":1138,"crawled_at":1791194291092}
+{"id":10360,"url":"https://www.metaplex.com/docs/smart-contracts/core/groups","domain":"www.metaplex.com","chapter":"docs","title":"Core Groups Overview | Metaplex Core","text":"Summary\nCore Groups (GroupV1) are taxonomy accounts that organize Collections, Assets, and other groups into higher-level sets — for example a brand umbrella that contains multiple collections, or a curated directory of standalone assets.\nGroups store their own name and URI, like collections\nA group can directly contain up to 256 collections, child groups, parent-group links, or assets per vector\nCollections and assets added to a group receive a Groups plugin listing their parent group addresses\nJump to: Create a group · Manage membership · Fetch groups\nCollections vs Groups\nCollections and groups solve different problems: collections manage member NFTs, while groups provide higher-level taxonomy across collections, assets, and child groups.\nCollectionGroup\nPurpose\nShared metadata and plugins for a series of NFTs\nTaxonomy / directory over collections, assets, and groups\n\nOwns user NFTs\nYes — assets reference the collection\nNo — assets remain in their collection (if any)\n\nTypical question\n“Which series is this NFT from?”\n“Which brand, season, or directory includes this collection?”\n\nOn-chain membership\nAsset updateAuthority points at the collection\nMember listed in group.collections, group.assets, or group.groups\n\nUse a Collection when you need collection-wide royalties, freeze rules, or shared artwork for a mint series. Use a Group when you need to organize multiple collections or standalone assets under one label without changing how those assets are minted.\nGroupV1 account\nA GroupV1 account stores:\nFieldDescription\nupdateAuthority\nAuthority that can update the group and change membership\n\nname\nDisplay name\n\nuri\nOff-chain JSON metadata URI\n\ncollections\nCollections that are direct children of this group\n\ngroups\nChild groups contained by this group\n\nparentGroups\nParent groups that contain this group\n\nassets\nAssets that are direct members of this group\n\nOn-chain limits (from mpl-core):\n256 entries max per vector (collections, groups, parentGroups, assets)\n8 parent groups max per group (MAX_GROUP_NESTING_DEPTH)\nGroups plugin\nWhen a collection or asset is added to a group, mpl-core ensures a Groups authority-managed plugin exists on that member. The plugin stores the parent group public keys.\nCreating groups\nUse createGroup / createGroupV1 to deploy a new group account:\n\n1import { generateSigner } from '@metaplex-foundation/umi'\n\n2import { createGroup } from '@metaplex-foundation/mpl-core'\n\n3\n\n4const group = generateSigner(umi)\n\n5\n\n6await createGroup(umi, {\n\n7 group,\n\n8 name: 'My Brand Directory',\n\n9 uri: 'https://example.com/my-brand.json',\n\n10 relationships: [],\n\n11}).sendAndConfirm(umi)\n\n12\n\n13console.log('Group created:', group.publicKey)\n\nYou can optionally pass relationships at creation time to link collections, child groups, parent groups, or assets in one transaction. Each relationship entry uses RelationshipKind: Collection, ChildGroup, ParentGroup, or Asset.\nManaging group membership\nAll membership changes are signed by the group update authority unless noted.\nOperationSDK helperWhat it updates\nAdd collections\naddCollectionsToGroup\nGroup collections + collection Groups plugin\n\nRemove collections\nremoveCollectionsFromGroup\nBoth sides\n\nAdd assets\naddAssetsToGroup\nGroup assets + asset Groups plugin\n\nRemove assets\nremoveAssetsFromGroup\nBoth sides\n\nAdd child groups\naddGroupsToGroup\nParent groups + child parentGroups\n\nRemove child groups\nremoveGroupsFromGroup\nBoth sides\n\nUpdate metadata / authority\nupdateGroup\nGroup name, URI, update authority\n\nClose empty group\ncloseGroup\nCloses the group account\n\nAdd a collection to a group\n\n1import { publicKey } from '@metaplex-foundation/umi'\n\n2import { addCollectionsToGroup } from '@metaplex-foundation/mpl-core'\n\n3\n\n4const group = publicKey('GroupAddress...')\n\n5const collection = publicKey('CollectionAddress...')\n\n6\n\n7await addCollectionsToGroup(umi, {\n\n8 group,\n\n9 authority: umi.identity,\n\n10})\n\n11 .addRemainingAccounts([\n\n12 { pubkey: collection, isSigner: false, isWritable: true },\n\n13 ])\n\n14 .sendAndConfirm(umi)\n\n15\n\n16console.log('Collection added to group')\n\nAdd a standalone asset to a group\n\n1import { publicKey } from '@metaplex-foundation/umi'\n\n2import { addAssetsToGroup } from '@metaplex-foundation/mpl-core'\n\n3\n\n4const group = publicKey('GroupAddress...')\n\n5const asset = publicKey('AssetAddress...')\n\n6\n\n7await addAssetsToGroup(umi, {\n\n8 group,\n\n9 authority: umi.identity,\n\n10})\n\n11 .addRemainingAccounts([\n\n12 { pubkey: asset, isSigner: false, isWritable: true },\n\n13 ])\n\n14 .sendAndConfirm(umi)\n\n15\n\n16console.log('Asset added to group')\n\nNest groups\n\n1import { addGroupsToGroup } from '@metaplex-foundation/mpl-core'\n\n2\n\n3// parentGroup and childGroup are existing GroupV1 accounts\n\n4\n\n5await addGroupsToGroup(umi, {\n\n6 parentGroup: parentGroup.publicKey,\n\n7 groups: [childGroup.publicKey],\n\n8 authority: umi.identity,\n\n9})\n\n10 .addRemainingAccounts([\n\n11 { pubkey: childGroup.publicKey, isSigner: false, isWritable: true },\n\n12 ])\n\n13 .sendAndConfirm(umi)\n\n14\n\n15console.log('Child group nested under parent')\n\nParent and child vectors stay synchronized: the parent lists the child in groups, and the child lists the parent in parentGroups.\nFetching groups\nUse the mpl-core SDK to read on-chain state:\n\n1import { publicKey } from '@metaplex-foundation/umi'\n\n2import { fetchGroupV1 } from '@metaplex-foundation/mpl-core'\n\n3\n\n4const groupAddress = publicKey('GroupAddress...')\n\n5\n\n6const group = await fetchGroupV1(umi, groupAddress)\n\n7\n\n8console.log(group.name)\n\n9console.log(group.collections)\n\n10console.log(group.groups)\n\n11console.log(group.assets)\n\nTo list all groups for an update authority, use getGroupV1GpaBuilder (a GPA query — fine for groups, but prefer DAS for large asset scans):\n\n1import { publicKey } from '@metaplex-foundation/umi'\n\n2import { getGroupV1GpaBuilder, Key } from '@metaplex-foundation/mpl-core'\n\n3\n\n4const updateAuthority = publicKey('UpdateAuthorityAddress...')\n\n5\n\n6const groups = await getGroupV1GpaBuilder(umi)\n\n7 .whereField('updateAuthority', updateAuthority)\n\n8 .whereField('key', Key.GroupV1)\n\n9 .getDeserialized()\n\n10\n\n11for (const group of groups) {\n\n12 console.log(group.publicKey, group.name)\n\n13}\n\nNotes\nGroups do not traverse collection membership automatically. Adding a collection to a group does not add that collection’s NFTs to group.assets. To work with NFTs in a grouped collection, operate on the collection and its assets separately\nThe Groups plugin blocks burning a group member itself (the collection account or a directly grouped asset) while it still belongs to at least one group. Burning an asset inside a grouped collection does not remove the collection from the group\nGlossary\nThe terms below define the Core Groups concepts used on this page.\nTermDefinition\nGroupV1\nA Core account that organizes collections, assets, and child groups into a higher-level taxonomy\n\nGroups plugin\nAn authority-managed plugin on a member that stores parent group public keys\n\nDirect member\nA collection, asset, or child group explicitly listed in a group’s on-chain vectors\n\nQuick reference\nThe tables below list the mpl-core program ID and SDK helpers for common group operations.\nProgram ID\nThe mpl-core program ID is the same on mainnet and devnet.\nNetworkAddress\nMainnet\nCoREENxT6tW1HoK8ypY1SxRMZTcVPm7R94rH4PZNhX7d\n\nDevnet\nCoREENxT6tW1HoK8ypY1SxRMZTcVPm7R94rH4PZNhX7d\n\nSDK helpers\nUse these SDK functions for create, fetch, update, and membership operations.\nTaskFunction\nCreate\ncreateGroup\n\nFetch\nfetchGroupV1\n\nList by authority\ngetGroupV1GpaBuilder\n\nUpdate\nupdateGroup\n\nAdd collection\naddCollectionsToGroup\n\nAdd asset\naddAssetsToGroup\n\nNest group\naddGroupsToGroup\n\nClose\ncloseGroup\n\nFAQ\nWhat is the difference between a Collection and a Group?\nA Collection groups Core Assets under shared metadata and collection-level plugins. A Group is a taxonomy container that can reference collections, standalone assets, and other groups. Collections answer “which series does this NFT belong to?” Groups answer “which higher-level set does this collection or asset belong to?”\nCan a collection belong to multiple groups?\nYes. When a collection is added to a group, mpl-core writes the parent group address into the collection’s Groups plugin. A collection can list multiple parent groups, up to the on-chain vector limit.\nCan groups be nested?\nYes. A group can contain child groups and also list parent groups. Parent/child links are kept in sync on both accounts. A group may belong to up to 8 parent groups.\nDo assets inside a grouped collection automatically belong to the group?\nNo. Group membership is stored on direct members only. Putting a collection in a group adds the collection to group.collections and writes the Groups plugin on the collection. NFTs minted into that collection are not automatically added to group.assets.\nCan a standalone asset be a direct member of a group?\nYes. Use addAssetsToGroup to add an asset directly to group.assets without a collection. Collection-managed assets can also be added explicitly when the correct authority signs.\nWho can modify group membership?\nThe group update authority signs add/remove instructions. For collection-managed assets, the collection update authority (or an authorized delegate) can add or remove those assets on the group’s behalf.","tokens":2319,"crawled_at":1791194316433}
+{"id":10361,"url":"https://www.getfoundry.sh/forge/debugging","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Debugging – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nDebugging\n\nForge provides detailed traces and an interactive debugger to understand contract execution.\n\nTraces\n\nRun tests with -vvvv to see full execution traces:\n\n$ forge test -vvvv\n\nCompiling...\nNo files changed, compilation skipped\nRan 1 test for test/OwnerUpOnly.t.sol:OwnerUpOnlyTest\n[PASS] test_IncrementAsOwner() (gas: 59372)\nTraces:\n[59372] OwnerUpOnlyTest::test_IncrementAsOwner()\n├─ [2407] OwnerUpOnly::count() [staticcall]\n│ └─ ← [Return] 0\n├─ [43524] OwnerUpOnly::increment()\n│ └─ ← [Stop]\n├─ [2407] OwnerUpOnly::count() [staticcall]\n│ └─ ← [Return] 1\n└─ ← [Stop]\nSuite result: ok. 1 passed; 0 failed; 0 skipped; finished in 287.16µs (62.42µs CPU time)\nRan 1 test suite in 6.97ms (287.16µs CPU time): 1 tests passed, 0 failed, 0 skipped (1 total tests)\n\nThe trace shows every call, its inputs, outputs, and gas usage.\n\nUnderstanding trace output\n\nEach line shows:\n\nGas used in brackets\n\nContract::function being called\n\nCall type (staticcall, delegatecall, etc.)\n\nReturn value or revert reason\n\nIndentation indicates call depth.\n\nTracing a failed transaction\n\nDebug a transaction that failed on-chain:\n\n$ cast run 0x<txhash> --rpc-url $RPC_URL\n\nThis replays the transaction and shows the execution trace. Add --debug to open the transaction in the interactive debugger instead; cast call --trace --debug does the same for a call without sending it.\n\nInteractive debugger\n\nLaunch the debugger for a single test:\n\n$ forge test --debug --match-test test_Increment\n\nIn an interactive terminal, a filter that matches more than one test opens a prompt asking which test to debug, so you can also run forge test --debug without a filter and pick from the list. In a non-interactive terminal the filter must match exactly one test.\n\nThe debugger is a terminal UI with five panes:\n\nSource – Source code with the currently executing line highlighted.\n\nOpcodes – The opcode list for the current call, with the program counter, address, and gas information in the title.\n\nVariables – Parameters, return values, and locals in the current scope, with decoded values where available. When you step through a constructor during contract creation, the constructor arguments are decoded and shown here. Storage reads and writes performed by the current step also appear in this pane.\n\nStack – The current EVM stack.\n\nData – A shared pane showing either a buffer (memory, calldata, or returndata) or the storage explorer.\n\nThe debugger picks a two-column or single-column layout based on the terminal size. Press l to switch layouts, or force one with --debug-layout <horizontal|vertical>.\n\nKey bindings\n\nKeyAction\nj / k (or arrow keys, mouse scroll)\nStep forward / backward one instruction\n\ns / a\nMove to the next / previous jump\n\nC / c\nMove to the next / previous call\n\ng / G\nGo to the beginning / end\n\n'<char>\nJump to the breakpoint set with vm.breakpoint\n\n0-9\nRepeat prefix for movement keys, e.g. 10k steps back 10 instructions\n\nb\nCycle the data pane between memory, calldata, and returndata\n\nJ / K\nScroll the stack pane\n\nCtrl+j / Ctrl+k\nScroll the data pane\n\nt\nToggle stack labels\n\nm\nToggle UTF-8 decoding of the active buffer\n\np\nGo to a program counter\n\no\nGo to a byte offset in the active buffer, or to a slot when the storage explorer is active\n\n/, then n / N\nSearch opcodes in the current call, then repeat the search forward / backward\n\n:\nOpen the command prompt\n\nh\nToggle the shortcut footer\n\nq\nQuit\n\nCommand prompt\n\nPress : to run a debugger command. :help lists all commands and their aliases.\n\nCommandAction\n:pc <pc> (alias :continue <pc>)\nJump to a program counter in the current contract\n\n:line <line>\nJump to the nearest instruction mapped to a source line in the current contract\n\n:mem [<offset>], :calldata [<offset>], :ret [<offset>]\nSelect a buffer in the data pane, optionally jumping to a byte offset\n\n:storage [<slot>]\nOpen the storage explorer, optionally jumping to the nearest access of a slot\n\n:transient [<slot>]\nOpen the transient storage explorer, optionally jumping to a slot\n\n:source, :opcodes, :variables, :stack, :data\nShow or hide a pane; the remaining panes reclaim the space\n\nStorage explorer\n\n:storage switches the data pane to a storage view that lists every slot the current call has accessed up to the current step, showing each slot's most recent operation (SLOAD or SSTORE) and value. The slot touched by the current step is highlighted. :storage <slot> jumps to the nearest access of a specific slot: the access at or after the current step, or the most recent earlier one.\n\n:transient and :transient <slot> provide the same view for transient storage (TLOAD and TSTORE). Press b to switch the data pane back to the buffer view.\n\nBreakpoints\n\nPlace breakpoints in code with the vm.breakpoint cheatcode:\n\nvm.breakpoint(\"a\");\n\nPressing 'a in the debugger jumps to the step where the breakpoint was recorded.\n\nDebugging scripts\n\nDebug a script:\n\n$ forge script script/Deploy.s.sol --debug\n\nConsole logging\n\nAdd logs to your contracts for debugging:\n\nimport {console} from \"forge-std/console.sol\";\n\nfunction transfer(address to, uint256 amount) public {\nconsole.log(\"Transfer from:\", msg.sender);\nconsole.log(\"Transfer to:\", to);\nconsole.log(\"Amount:\", amount);\n// ...\n}\n\nView logs with -vv or higher:\n\n$ forge test -vv\n\nFor structured output, Foundry also supports console.table, which can make repeated values easier to scan than a long sequence of console.log lines.\n\nLabeling addresses\n\nMake traces more readable by labeling addresses:\n\nfunction setUp() public {\nalice = makeAddr(\"alice\");\nbob = makeAddr(\"bob\");\n\nvm.label(address(token), \"Token\");\nvm.label(address(pool), \"Pool\");\n}\n\nTraces will show Token::transfer() instead of 0x1234...::transfer().\n\nStack traces\n\nWhen a test fails, use -vvv to see a stack trace showing exactly where the revert occurred:\n\n$ forge test -vvv\n\nSolc 0.8.10 finished in 640.34ms\nCompiler run successful!\nRan 1 test for test/FailingTest.t.sol:VaultTest\n[FAIL: Unauthorized()] test_WithdrawAsNotOwner() (gas: 8418)\nTraces:\n[8418] VaultTest::test_WithdrawAsNotOwner()\n├─ [0] VM::prank(ECRecover: [0x0000000000000000000000000000000000000001])\n│ └─ ← [Return]\n├─ [191] Vault::withdraw() [staticcall]\n│ └─ ← [Revert] Unauthorized()\n└─ ← [Revert] Unauthorized()\nBacktrace:\nat Vault.withdraw\nat VaultTest.test_WithdrawAsNotOwner\nSuite result: FAILED. 0 passed; 1 failed; 0 skipped; finished in 329.35µs (58.54µs CPU time)\nRan 1 test suite in 8.10ms (329.35µs CPU time): 0 tests passed, 1 failed, 0 skipped (1 total tests)\n\nThe trace shows the call hierarchy with the revert bubbling up, and the Backtrace pinpoints the exact location in your code.\n\nInspecting inheritance linearization\n\nWhen debugging overrides in a multiple-inheritance hierarchy, inspect the method-resolution order directly:\n\n$ forge inspect src/MyContract.sol:MyContract linearization\n\nThis shows the order Solidity uses to resolve inherited functions, which is often the fastest way to understand why a particular override or super call is being selected.\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":1773,"crawled_at":1791194299407}
+{"id":10362,"url":"https://docs.sui.io/sui-stack","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Sui Stack | Sui Documentation","text":"Learn about the different components and primitives of the Sui Stack.\n\nSui Stack\nExplore the Sui Stack: an overview of Sui's core components and primitives including onchain randomness, onchain time, zkLogin, Nautilus, Seal, Walrus, and SuiPlay.\n→\nAccess Onchain Time\nAccess network-based time for your transactions. Sui provides a Clock module to capture near-real time or epoch time in your Sui packages.\n→\nOnchain Randomness\nRandomness is a valuable tool to simulate chance onchain, but can also expose flaws in your logic. Understanding the vulnerabilities and accounting for them can mitigate the threat exposure for your smart contracts.\n→\nSagat\nSagat is a multisig management platform designed for managing Sui multisig wallets.\n→\nWalrus\nIn this section\nWalrus Docs\nData Storage Using Walrus\nCustom Indexer and Walrus\nEncrypted Social Media\nOnchain Websites with Walrus Sites\n\n→\nSeal\nIn this section\nSeal Server Overview\nGetting Started\nDeveloper guide\nOperator guide\nSeal Pricing\nSeal Terms of Service\n+ 1 more\n\n→\nMessaging SDK\nIn this section\nGetting Started\nArchitecture\nGuides\nReference\nExamples\nGitHub Repo\n\n→\nSuiNS\nIn this section\nUsers\nSuiNS Communities\nIntegration Guide\nSDK\nNode Operators\nSuiNS DAO Proposals and Voting Procedure\n+ 1 more\n\n→\nMove Registry (MVR)\nIn this section\nManaging MVR Names\nManaging Package Metadata\nPackage Maintainer Best Practices\nMVR CLI\nTransaction Plugin for Sui TypeScript SDK\n\n→\nEnoki\nIn this section\nEnoki Docs\nSolitaire\nTicketing Platform\n\n↗\nNautilus\nIn this section\nWhat is Nautilus?\nNautilus Design\nUsing Nautilus\nCustomizing, Testing, and Management\nWeather Oracle\nEncrypt Enclave Secrets with Seal\n+ 1 more\n\n→\nDeepBook\nIn this section\nDeepBookV3\nDeepBook Margin\nDeepBook Predict\n\n↗\nzkLogin\nIn this section\nzkLogin Integration Guide\nConfigure OpenID Providers\nConsumer App Cookbook\nzkLogin for DeFi\nzkLogin Authentication\nzkLogin Technical Reference\n\n→\nHashi\nIn this section\nHashi Docs\n\n→\nSuiPlay0X1\nIn this section\nSDK Integrations\nWallet Integration Options\nBest Practices\nBroader Sui Ecosystem Support\n\n→","tokens":515,"crawled_at":1791194300597}
+{"id":10363,"url":"https://a16zcrypto.com/team/ciamac-moallemi","domain":"a16zcrypto.com","chapter":"research","title":"Ciamac Moallemi - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nCiamac Moallemi\n\nFeed\nFilter\n(1)\nclear filters\n\ncategory\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\nrecommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nauthor\n(1) all authors\n@x0rart\n1337 Skulls Sers\na16z crypto\na16z crypto editorial\na16z crypto policy & regulatory teams\na16z crypto Regulatory Team\nAaditya Shidham\nAaron Levie\nAaron Phillips\nAaron Schnider\nAbby Green\nAbdou Ndiaye\nAbhi Shelat\nAbhiram Kothapalli\nAbigail Johnson\nAdam Alter\nAdam Back\nAdam Bry\nAdam Grant\nAdam Ludwin\nAdam Martin\nAdam Thierer\nAdam Zuckerman\nAdela Tomsejova\nAdena Friedman\nAdena Hefets\nAdeniyi Abiodun\nAdina Fischer\nAdrian Cockcroft\nAdrian Fenty\nAdrienne Mayor\nAgostino Capponi\nAiden Slavin\nAileen Lee\nAisha Stephenson\nAJ Shankar\nAlan Knott-Craig\nAlan Schaaf\nAlana Benton\nAlbert Tang\nAlec Nielsen\nAlec Ross\nAlejandro Flores\nAlex Constantinople\nAlex Honnold\nAlex Hutchinson\nAlex Immerman\nAlex Kreitz\nAlex Kroeger\nAlex Le\nAlex Masmej\nAlex Morcos\nAlex Price\nAlex Pruden\nAlex Rampell\nAlex Roetter\nAlex Solomon\nAlex Spector\nAlex Stamos\nAlex Tabarrok\nAlexander (Sasha) Spiegelman\nAlexander Chia\nAlexander Zoppa\nAlexandra Chang\nAlexandria Lafci\nAlexis Lakes\nAlexis Madrigal\nAlexis Ohanian\nAli Ghodsi\nAli Yahya\nAlicia Barone\nAlin Tomescu\nAlisha Litman\nAlison Mangiero\nAlison Martin\nAllison Pickens\nAlyssa Del Bene\nAlyssa Torres\nAmanda Cantor\nAmanda Cassatt\nAmanda Catherine\nAmanda Mulay\nAmanda Tuminelli\nAmanda Tyler\nAmelia Salyers\nAmie Tyrrel\nAmir Shevat\nAmira Yahyaoui\nAmy Abernethy\nAmy Berliner\nAmy Bohutinsky\nAmy Choice\nAmy Cray\nAmy Gill\nAmy Hoemeke\nAmy Kalokerinos\nAmy Robertson\nAna Mostarac\nAna Susi\nAnatoly Yakovenko\nAndie Taylor\nAndisheh Tahriri\nAndre Iguodala\nAndrea Clarke Hall\nAndrea Feinberg\nAndrea Rallo\nAndrea Simon\nAndrea Vinkler\nAndreas Papadimitropoulos, Jr\nAndreessen Horowitz\nAndrew Allen\nAndrew Chen\nAndrew F. Read\nAndrew Green\nAndrew Hall\nAndrew Lakis\nAndrew Lewis-Pye\nAndrew Lo\nAndrew Mason\nAndrew McAfee\nAndrew Milson\nAndrew Omori\nAndrew Radin\nAndrew Rubin\nAndrew Savage\nAndrew Smith\nAndrew Tretyakov\nAndy Beal\nAndy Coravos\nAndy Golden\nAndy Hill\nAndy Milenius\nAndy Rachleff\nAndy Tran\nAndy Walshe\nAneel Lakhani\nAngela Schenone\nAngela Strange\nAngela Tran Kingyens\nAngelica Gehr\nAniket Kate\nAnil Sethi\nAnish Acharya\nAnn Winblad\nAnna Berces\nAnna Jablonski\nAnna Semenova\nAnna Van Meurs\nAnnaLee Saxenian\nAnne Brandes\nAnne Lee Skates\nAnne Lewandowski\nAnne Mitchell\nAnne Yip\nAnnie Collins\nAnnie Duke\nAnthony Albanese\nAnthony Atala\nAnthony Foxx\nAnthony Lee Zhang\nAntonio Viggiano\nAntwone Stigall\nAnu Hariharan\nApril Roth\nAri Emanuel\nAri Juels\nArianna Huffington\nArianna Simpson\nArik Kershenbaum\nArmon Dadgar\nArnie Goldberg\nArsho Avetian\nArthur Brooks\nArun Sundararajan\nAsh Ashutosh\nAsha Christian\nAshley McCollum\nAshley Stern\nAshton Carter\nAtif Mian\nAtul Butte\nAubree Pelaez\nAubrey de Grey\nAugusto Marietti\nAurora Petracca\nAusten Allred\nAustin Guzman\nAustin Marchese\nAustin Wilson\nAva Iravani\nAvery Segal\nAvinash Solanky\nAviv Zohar\nAye Moah\nAzeem Azhar\nBailey Flanigan\nBailey Richardson\nBalaji Srinivasan\nBarry McCarthy\nBart Dessaint\nBeau Cronin\nBeau Woods\nBecky Pferdehirt\nBen Buckwalter\nBen Fielding\nBen Fisch\nBen Gardner\nBen Gomez\nBen Horowitz\nBen Kaufman\nBen Leventhal\nBen Lovell\nBen Napier\nBen Portney\nBen Rubin\nBen Scharfstein\nBen Schecter\nBen Silbermann\nBen Uretsky\nBen Wu\nBenedict Evans\nBenedikt Büenz\nBenjamin Ebner\nBenjamin Hindman\nBenjamin Wittes\nBenjamin Wu\nBennett Carroccio\nBenny Pinkas\nBernard J. Tyson\nBernard Tyson\nBeth Newman\nBethany Coates\nBharat Ramamurti\nBharath Ramsundar\nBill Carr\nBill Frist\nBill Hinman\nBill Janeway\nBill Krause\nBill Macaitis\nBlake Kim\nBlake Masters\nBlake Saari\nBlayne Donnell\nBob Iger\nBob Langer\nBob Moore\nBob Muglia\nBob Sutton\nBob Swan\nBob Tinker\nBob Wachter\nBobby Franklin\nBobby Green\nBobby Kotick\nBobby Wagner\nBoris Sofman\nBoris Wertz\nBrad Feld\nBrad Kern\nBrad Peterson\nBram Cohen\nBrandon Ballinger\nBrandon Barros\nBrandon Cherry\nBrandon Millman\nBrenda Kopf\nBrent McIntosh\nBrett Browman\nBrett Falk\nBrett Hagler\nBrewster Kahle\nBrian Armstrong\nBrian Balfour\nBrian Brooks\nBrian Crnkovich\nBrian Curran\nBrian Grazer\nBrian Koppelman\nBrian McCullough\nBrian Quintenz\nBrian Wilkins\nBridget McDowell\nBrittany Lucas\nBrittney Burrows\nBrooke Sheresky\nBruce Friedrich\nBryan Caplan\nBryan Chiang\nBryan Cox\nBryan Crowley\nBryan Faust\nBryan Houser\nBryan Kim\nBryan Pellegrino\nCaitlin Glazebrook\nCaitlin Johnston\nCaitlin Roberson\nCal Turner Jr.\nCaleb Christian\nCameron Schuler\nCamila De Souza\nCarine Carmy\nCarissa Bilinski\nCarl Agnelli\nCarl Eschenbach\nCarl Narcisse\nCarl Pope\nCarlos Araya\nCarolina Gonzalez\nCaroline Friedman\nCaroline Goggins\nCaroline Horn\nCaroline Moon\nCarolyn Bertozzi\nCarra Wu\nCasey Graul\nCasey Neistat\nCasey Winters\nCassady Churchill\nCassie Faerber\nCecilia Marshall\nCeia Font\nChad Rigetti\nChandra Krintz\nCharles Goetz\nCharles Hubbard\nCharles Koch\nCharlie Keinath\nCharlie Warzel\nChattry Meas\nChelsea Komlo\nChelsea Padilla\nCheng Li\nChris Bennett\nChris Best\nChris Burniske\nChris Curran\nChris DeWolfe\nChris Dixon\nChris Granger\nChris Hauth\nChris Lyons\nChris Messina\nChris Milk\nChris Power\nChris Santa Maria\nChris Wanstrath\nChristian Cachin\nChristian Catalini\nChristian Crowley\nChristian Seifert\nChristina Hampp\nChristina Lopes\nChristina Mercando\nChristina Xu\nChristina Zeidan\nChristine Darden\nChristine Perham\nChristopher Giancarlo\nChristopher Lee\nChristopher Mims\nChristopher Nguyen\nChristopher Rippingham\nChristopher Schroeder\nChristy Hubbard\nCiamac Moallemi\nCindi Zhang\nCindy Tenner\nClaire Austin\nClaire Cain Miller\nClaire Kart\nClaudia Picanco\nClay Shirky\nClayton Christensen\nClayton Gardner\nClifford Woolf\nClint Delapaz\nColin Bryar\nColin Rom\nCollin McCune\nConner Lyons Brown\nConnie Chan\nConnie Guglielmo\nConnor McCarthy\nConnor Moyles\nCorban Bell\nCorey Hawkins\nCorey Waller\nCourtney Dettlinger\nCraig Naylor\nCraig Walker\nCristina Cordova\nCurt Funderburk\nCuy Sheffield\nD'Arcy Coolican\nDaejun Park\nDaisy Linden\nDaisy Wolf\nDaljeet Virdi\nDalton Turay\nDan Berkenstock\nDan Boneh\nDan Frommer\nDan Primack\nDan Romero\nDan Shapero\nDan Siroker\nDan Stein\nDan Warmenhoven\nDan Wendlandt\nDaniel Chao\nDaniel Chen\nDanielle Andrzejewski\nDanielle Clark\nDanielle Looymans\nDanielle Lussier\nDanielle Morrill\nDanielle Shea\nDanny Shader\nDaphne Koller\nDapper Dan\nDaren Matsuoka\nDarin Malter\nDarshan Shankar\nDas Rush\nDave Jagoda\nDave King\nDave Touretzky\nDavid Banks\nDavid Belden\nDavid Damato\nDavid Deming\nDavid George\nDavid Haber\nDavid Hollestelle\nDavid Kerr\nDavid Lee\nDavid Mack\nDavid Madden\nDavid Marcus\nDavid Olson\nDavid Oyelowo\nDavid Pierce\nDavid Reich\nDavid Rumsey\nDavid Schweikert\nDavid Sinclair\nDavid Sverdlov\nDavid Tse\nDavid Ulevitch\nDavid Weiden\nDawn Lepore\nDawn Nott\nDeborah Embaie\nDeena Elitreby\nDeepak Maram\nDenis Nazarov\nDenis Young\nDenise Gonzalez\nDerek Dolin\nDerek Thompson\nDerrick Harris\nDevin Finzer\nDevon Zuegel\nDiana Peña\nDiane Greene\nDick Costolo\nDieter Shirley\nDiishan Imira\nDiogo Monica\nDominic Shine\nDominique Reliford\nDon Duet\nDon Faul\nDorris O'Brien\nDoug Ducey\nDoug Folden\nDoug McCracken\nDouglas Argueta\nDozie Uche\nDrew Coffman\nDylan Field\nDylan Rhodes\nEd Felten\nEd Lynch\nEddie Lim\nEddy Lazzarin\nEdith Zimmerman\nEdward Perkins\nEdwin Poston\nEfrat Noy\nEhud Shapiro\nEileen Burbidge\nEileen Wu\nElad Gil\nElaine Fuchs\nElaine Shi\nElena Burger\nEli Dourado\nElisa Leonhardt\nEliza Oak\nElizabeth Gunn\nElizabeth Harkavy\nElizabeth May\nElizabeth Ocken\nElizabeth Stark\nElizabeth Weil\nEllen Tunoa\nEmile Petrone\nEmilio Torres\nEmily Graff\nEmily Hinsch\nEmily Keir\nEmily Oster\nEmily Westerhold\nEmma Janaskie\nEric Budish\nEric Dai\nEric Ries\nEric Thomas\nEric Topol\nEric Wu\nErica Schecter\nErik Brynjolfsson\nErik Kiser\nErik Torenberg\nErika Bracken\nErika Herrera\nErika Louie\nErin Grody Kingsley\nErin Murphy\nErin Tice\nErin Tonnar\nErin Winkler\nErtem Nusret Tas\nEsther Shinn\nEthan Bueno de Mesquita\nEthan Ferreira\nEthan Zuckerman\nEuan Ashley\nEugene Volokh\nEugene Wei\nEugenia Yee\nEula Takahashi\nEva Sakkas\nEvan Burfield\nEvan Osnos\nEvangelos Simoudis\nEzra Klein\nF. Gary Gray\nFabiola Godinez\nFabrizio Zilibotti\nFahad Saleh\nFarid Jiandani\nFei-Fei Li\nFelix Do\nFEWOCIOUS\nFiona Kennedy\nFiona Murray\nFlashrekt\nFlora Oliveira\nFlori Del Valle\nFlorian Leibert\nFoteini Baldimtsi\nFrancesca Gino\nFrank Chen\nFrank Wilczek\nFred Benenson\nFred Ehrsam\nFred Upton\nFred Wilson\nFreda Lewis-Hall\nFrederic Kerrest\nFuture Editorial\nGabby Dizon\nGabby Reece\nGabriel Otte\nGabriel Vasquez\nGaetan Barthelemy\nGarrett Biel\nGary Ang\nGary Reedy\nGary Wolf\nGaurav Banga\nGaurav Dhillon\nGaut\nGayle Tzemach Lemmon\nGeoffrey Woo\nGeorg Fuchsbauer\nGeorg Petschnigg\nGeorge Church\nGeorge Danezis\nGeorge Fraser\nGeraldine Chan\nGérard Cachon\nGerard Ryle\nGerri Elliott\nGerry Tsoukalas\nGia Scinto\nGil Elbaz\nGil Shafir\nGina Moon\nGina Neff\nGina Yocom\nGinger Liau\nGokul Rajaram\nGoldie Chang\nGrace Ellis\nGraham Allison\nGrant Gregory\nGrant Jordan\nGrant LaFontaine\nGrant Rabenn\nGray Kinsella\nGreg Bowman\nGreg Clayman\nGreg Linares\nGreg Loehmann\nGreg Lynn\nGreg Solano\nGreg Truesdell\nGreg Waldon\nGregory Allen\nGregory Mundis\nGretchen Bush\nGretchen McCulloch\nGuido Appenzeller\nGustav Söderström\nGustavo Garcia\nGuy Goren\nGuy Raz\nGuy Wuollet\nHaley Van Dyck\nHanna Aziz\nHannah Frankl\nHanne Winarsky\nHaoyuan Li\nHarmit Malik\nHarry Grieve\nHarry Shum\nHarry Wright\nHatim Shafique\nHayden Adams\nHeather Gwynn\nHeather Podesta\nHedi Samar\nHelen Stoddard\nHelen Su\nHemant Mohapatra\nHendrik Pretorius\nHenri Kor\nHerb Lin\nHerman Narula\nHilmar Pétursson\nHoang Nguyen\nHoward Wu\nIan Dutra\nIan Shannon\nIan Sharp\nIce Cube\nIlan Zechory\nIllia Polosukhin\nIlyas Khan\nIma Christian\nIman Abuzeid\nInsiya Lokhandwala\nIon Stoica\nIrvin Chan\nIsa Guardalabene\nIsaiah Lott\nIsh Verduzco\nIsil Dillig\nIstván András Seres\nIttai Abraham\nIttay Eyal\nIva Messy\nIvan Linscott\nIvor Horn\nJ.D. Moriarty\nJack Donahoe\nJack Soslow\nJackie McQuiston\nJackson David\nJacob Westphal\nJacquelyn Melinek\nJad Esber\nJad Naous\nJade Lai\nJade Raymond\nJae Gnazzo\nJai Ramaswamy\nJaimie Buss\nJak Kennedy\nJake Auchincloss\nJakob Uszkoreit\nJamal Mohammed\nJames Beshara\nJames Currier\nJames da Costa\nJames Gwertzman\nJames J. Collins\nJames Kissell\nJames L. Madara\nJames Loftus\nJames Rathmell\nJames Rogers\nJames Watters\nJames Wu\nJames Zou\nJamie Brandon\nJamie McGurk\nJamie Sullivan\nJamilla Hemeid\nJana Odehnal\nJane Doe\nJane Lippencott\nJane Suh\nJanelle De Los Santos\nJared Bricklin\nJared Furutani\nJared Georgakopoulos\nJared Polis\nJared Smith\nJase Wilson\nJason Franklin\nJason Liu\nJason Mayden\nJason Milionis\nJason Mitchell\nJason Mok\nJason Rosenthal\nJason Warner\nJason Yanowitz\nJay Bradner\nJay Conte\nJay Drain\nJay Komarneni\nJay Rughani\nJean Reilly\nJeanne Tsan\nJeff Amico\nJeff Benson\nJeff Clark\nJeff Cordova\nJeff Glueck\nJeff Hawkins\nJeff Jones\nJeff Jordan\nJeff Lawson\nJeff Lu\nJeff Nagashima\nJeff Stump\nJeff Weiner\nJeffrey Immelt\nJeffrey Kaditz\nJeffrey Katzenberg\nJeffrey Kindler\nJeffrey Low\nJeffrey Silverstein\nJeffrey Zirlin\nJen Bulawsky\nJen Kha\nJenna Walsh\nJenna Zucker\nJennifer 8. Lee\nJennifer Doudna\nJennifer Kodner\nJennifer Konde\nJennifer Li\nJennifer Mumford\nJennifer Tejada\nJennifer Young\nJenny Cieplak\nJens Ernstberger\nJensen Harris\nJeremy Clark\nJeremy England\nJeremy Zhang\nJesse Holmes\nJesse Pollak\nJesse Walden\nJessica Childs\nJessica Hansen\nJessica Keeler\nJessica Patton\nJessica Verrilli\nJewel Pi\nJez Humble\nJi Kim\nJianying Luo\nJim Gilliam\nJimmy Chen\nJimmy Soni\nJing Wang\nJing Zou\nJJ Yu\nJoachim Neu\nJodi Lynn\nJodie Lutkenhaus\nJoe Gebbia\nJoe Grundfest\nJoe Montana\nJoe Morrissey\nJoe Schmidt\nJoe Sullivan\nJoel de la Garza\nJoel Mokyr\nJoel Monegro\nJoel Spolsky\nJoey Burleson\nJohn China\nJohn Collison\nJohn Fawcett\nJohn Garcia\nJohn Gedmark\nJohn Hennessy\nJohn Koelliker\nJohn M. Jack\nJohn Markoff\nJohn Menna\nJohn O’Farrell\nJohn Riccitiello\nJohn Smesko\nJohn Stanfield\nJohn Thompson\nJohn William Hatfield\nJonah Peretti\nJonathan Bush\nJonathan Dotan\nJonathan Downey\nJonathan Lai\nJonathan Lim\nJonathan Lusthaus\nJonathan Weissman\nJonathan Wong\nJordan Mazer\nJordan Stankowski\nJorge Conde\nJorge Gomez\nJose Guardado\nJoseph Bonneau\nJoseph Okpaku\nJoseph Spisak\nJosh Arnold\nJosh Bloom\nJosh Kim\nJosh Williams\nJoshua Browder\nJoshua Gans\nJoshua Grimm\nJoshua Hix\nJoshua Levin\nJoshua Lu\nJoshua Schank\nJoshua Soto\nJosie Ma\nJoyce Park\nJR Rivers\nJT Evans\nJuan Benet\nJudene Small\nJudy Savitskaya\nJudy Smith\nJulia Grace\nJulia Kirby\nJulie Bornstein\nJulie Farnham\nJulie Johnson\nJulie Samuels\nJulie Yoo\nJuliet Grier\nJuliet Nyatta\nJuliette Morton\nJulius Zhang\nJustin Bailey\nJustin Bethune\nJustin Blau\nJustin Cunningham\nJustin Gregorius\nJustin Kahl\nJustin Kan\nJustin Larkin\nJustin Paine\nJustin Pettit\nJustin Roberts\nJustin Simcock\nJustin Thaler\nJustine Moore\nJutta Steiner\nJyoti Bansal\nJZ Young\nKabir Gill\nKabir Laroia\nKais Khimji\nKamala Harris\nKaren Dunn\nKaren Wooley\nKarina Sobieski\nKarl Floersch\nkarma (Daniel Reynaud)\nKarmacoma\nKarthik Rau\nKartik Nayak\nKate Darling\nKate Dellolio\nKate Kerames\nKatherine Boyle\nKatherine Minarik\nKatherine Rundell\nKatherine Schoebel\nKathryn McKinley\nKathy Liu\nKathy Yang\nKatia Ameri\nKatie Baynes\nKatie Haun\nKatie Hemmerling\nKaty DeWitt-Drew\nKaty Nelson\nKayvon Tehranian\nKeener Barnhorst\nKeller Medlin\nKeller Rinaudo\nKelly Cannon\nKelsey Chaplinsky\nKelsey Mellard\nKen Chong\nKen Coleman\nKen Kocienda\nKerry Ganim\nKesha Cash\nKevin Chou\nKevin Chu\nKevin Dulsky\nKevin Kelly\nKevin McKinley\nKevin Nishioka\nKevin O'Kane\nKevin Rose\nKevin Tan\nKevin Wu\nKevin Zollman\nKidSuper\nKieran Snyder\nKierston Gittens\nKiki Mavridis\nKim Enright\nKim Malone Scott\nKim Milosevich\nKim Stevenson\nKim Zetter\nKimberly Tan\nKindra Mason\nKira Poskanzer\nKira Song\nKirstin Arbide\nKirt McMaster\nKofi Ampadu\nKouki Harasaki\nKrista Anderson-Copperman\nKristen Fortney\nKristen Johansson\nKristen Kee\nKristin Sauchak\nKristin Thayer\nKristina Graci-deLuna\nKristina Shen\nKristine Lipscomb\nKristo Käärmann\nKrisztina Holly\nKunal Bahl\nKunle Olukotun\nKurt House\nKyle Russell\nLaird Hamilton\nLatasha\nLaura Arrillaga-Andreessen\nLaura Baller\nLaura Behrens Wu\nLaura Deming\nLaura Gravley\nLaura Johnson\nLaura Shores\nLaura Weidman Powers\nLauren Berson\nLauren Illovsky\nLauren Murrow\nLauren Richardson\nLauren Spragge\nLaurene Powell Jobs\nLawrence Levy\nLawrence Summers\nLeah Cassidy\nLee Kleinman\nLee Lefkowitz\nLeeAnn Caballero\nLeila Hay\nLeila Janah\nLenny Rachitsky\nLeslie Jaw\nLeslie Vosshall\nLester Chen\nLi Fan\nLi Fei-Fei\nLi Jin\nLiang Wu\nLilian King\nLily Liu\nLina Sergie Attar\nLinda Banuelos\nLinda Xie\nLinden Tibbets\nLing Ren\nLinlin Li\nLinxin Wen\nLioba Heimbach\nLisa Hawke\nLisa Lambert\nLisa Orr\nLisa Reilly\nLisa Rosano\nLizzy Anderson\nLJ Erwin\nLloyd Dean\nLoretta Sanchez\nLori Potter\nLuca Prosperi\nLuca Zanolini\nLuis Martinez\nLuis von Ahn\nLuke Wroblewski\nLydia Green\nLynda Gibson\nLynn Rudolph\nMadan Nagaldinne\nMaddison Masaeli\nMadeline Lancaster\nMaggie Hsu\nMaggie Leung\nMaggie Romero\nMahad Abedin\nMahesh Iyer\nMahesh Vellanki\nMahimna Kelkar\nMakiri Duckett\nMalinka Walaliyadde\nMallesh M. Pai\nMalloy Evans\nManas Punhani\nManny Luna\nMarc Andreessen\nMarc Andrusko\nMarc Benioff\nMarc Levinson\nMarci Barbera\nMarco Reuter\nMargaret Jen\nMargit Wennmachers\nMaria LaMagna Morales\nMarian Garvin\nMarianne Winkler\nMariano Sorgente\nMaricarmen Alvarez\nMariel Goldenstein\nMarigold Vu\nMarina Kusserow\nMario Gabriele\nMario Linares\nMarissa Bramlett\nMark Cranney\nMark Leslie\nMark McAndrew\nMark McClusky\nMárk Melczer\nMark Moore\nMark Regan\nMark Sendak\nMarkos Georghiades\nMarkus Covert\nMarkus Funk\nMartha Lane Fox\nMartin Casado\nMartin Fischer\nMarty Makary\nMarvin Ammori\nMarvin Zamora\nMary Pat Jordan\nMary-Catherine Lader\nMaryam Bahrani\nMason Hall\nMatei Zaharia\nMatt Abrahams\nMatt Billmann\nMatt Bornstein\nMatt Clifford\nMatt Flannery\nMatt Fleming\nMatt Gleason\nMatt Kaeberlein\nMatt Levine\nMatt Levy\nMatt Oberhardt\nMatt Shortal\nMatt Spence\nMatt Weinberg\nMatthew Colford\nMatthew Green\nMatthew Haughey\nMatthew McCullough\nMatthew Mills\nMatthew Olsen\nMatthew Rutter\nMatthew Stein\nMatthieu Hafemeister\nMaureen Lara\nMax Kesten\nMax Krohn\nMax Levchin\nMax Polyak\nMax Resnick\nMax Ventilla\nMaya Rahkonen\nMcPherson Moore\nMeaghan Hardy\nMeg Whitman\nMegan Holston-Alexander\nMegan Kristalyn\nMehdi Hasan\nMehul Mehta\nMel Williams\nMelanie Galang\nMelissa Liao\nMelissa Minor\nMelissa Wasser\nMellody Hobson\nMelody Latronico\nMeredith Donahue\nMia Gonzalez\nMia Mandich\nMicah Johnson\nMichael Beckerman\nMichael Blau\nMichael Brandt\nMichael Chan\nMichael Copeland\nMichael Dearing\nMichael Dell\nMichael Franklin\nMichael Garcia\nMichael J. Casey\nMichael J. Freedman\nMichael Killam\nMichael King\nMichael Lee\nMichael Leiter\nMichael Morell\nMichael Ostrovsky\nMichael Ovitz\nMichael Paulus\nMichael Raynor\nMichael Reed\nMichael Snyder\nMichael Temkin\nMichael Wee\nMichael Zhu\nMichel Del Buono\nMichel Feaster\nMichèle Flournoy\nMichele Griffin\nMichele Korver\nMichele Law\nMichelle Ervin\nMichelle Kelso\nMichelle Kung\nMichelle Mundy\nMichelle Shin\nMichelle Ufford\nMichelle Volz\nMichelle Wilson\nMichelle Winn\nMichelle You\nMike Curtis\nMike Haydon\nMike Hearn\nMike Jones\nMike Kasperzak\nMike Kelly\nMike King\nMike Lempres\nMike Manning\nMike Maples jr\nMike Masnick\nMike Matchett\nMike Paulus\nMike Sandwick\nMikeal Rogers\nMikey Dickerson\nMiles Jennings\nMilijana Curic\nMiller Whitehouse-Levine\nMinerva Munoz\nMinnie Ingersoll\nMinsun Pak\nMintu Turakhia\nMiranda Christ\nMo Shaikh\nMohammad Akbarpour\nMohsen Malayeri\nMolly Grace\nMonique McCambridge\nMorgan Beller\nMorgan Bender\nMurat Pak\nMuriel Bowser\nMurray Shanahan\nMy Pham\nNadia Asparouhova\nNadia Eghbal\nNaftali Harris\nNaithan Jones\nNanjira Sambuli\nNaomi Metzger\nNashid Braswell\nNassim Eddequiouaq\nNat Barling\nNatacha Crooks\nNatalia Carrera\nNatalie Bucher\nNatalie Taumoepeau\nNate Chang\nNate Lau\nNathalie Balaban\nNathan McCauley\nNathan Yoon\nNathaniel Gleicher\nNathaniel Popper\nNav Singh\nNazanin Daneshvar\nNeel Maitra\nNeha Narula\nNelson Perla-Ward\nNeveen Bader\nNicholas Christakis\nNicholas Pacilio\nNick Babaian\nNick McKeown\nNick Quah\nNick Tomaino\nNicki Locker\nNicole Conner\nNicole Forsgren\nNicole Irvin\nNicole Neuman\nNicole Stanners\nNiels Provos\nNigel Robinson\nNikhil Krishnan\nNina Suthers\nNir Eyal\nNitasha Tiku\nNitin Natarajan\nNitya Subramanian\nNkiru Balonwu\nNoah Citron\nNoah Feldman\nNoah Levine\nNoah Smith\nNoam Nisan\nNoemi Glaeser\nO’Shea Jackson Jr.\nOlaf Carlson-Wee\nOleg Rogynskyy\nOliver Hsu\nOlivia Moore\nOlivia Webb\nOmri Weinstein\nOoshma Garg\nOprah Winfrey\nOrion Hindawi\nOscar Menjivar\nP.J. Hasleton\nPablo Montagnes\nPacky McCormick\nPak\nPalmer Luckey\nPamela Anderson\nPamon Forouhar\nParag Khanna\nParijat Talkad\nParker Brown\nParker Conrad\nPatrice Peck\nPatrick Byrne\nPatrick Collison\nPatrick Conway\nPatrick McCorry\nPatrick McHenry\nPatrick O’Grady\nPatrick Rivera\nPatrick Sutton\nPaul Cafiero\nPaul Daugherty\nPaul Davison\nPaul Krugman\nPaul Vigna\nPaula Long\nPenny Pritzker\nPerri Chilton\nPete Buttigieg\nPeter Blackwood\nPeter Buisseret\nPeter Chan\nPeter Donnelly\nPeter Johnson\nPeter Lauten\nPeter Leeson\nPeter Levine\nPeter Ludwig\nPeter Rubin\nPeter Thiel\nPeter Wang\nPetra Garrett\nPhil Daian\nPhil Hathaway\nPhil Wong\nPhong Nguyen\nPorter Smith\npplpleasr\nPranav Garimidi\nPrasad Akella\nPrat Moghe\nPreethi Kasireddy\npunk6529\nPurnima Padmanabhan\nPyrs Carvolth\nQasar Younis\nQuang Dao\nQuinten Burgunder\nQuintus Kilbourn\nRachael Horwitz\nRachel Goslins\nRachel Jenkins\nRachel Kalmar\nRachel McIntyre\nRachel Steiner\nRahul Iyer\nRahul Vohra\nRajeev Singh\nRajeev Venkayya\nRam Palaniappan\nRamana Jonnala\nRati Gelashvili\nRaul Vazquez\nRavi Parimi\nRay Dalio\nRaymond Carreira\nRebecca Lewis\nRebecca Rettig\nReed Hastings\nRefik Anadol\nRegina Benjamin\nRenato Valdés Olmos\nReshma Saujani\nReshma Sohoni\nRex Salisbury\nRich Ezekiel\nRichard Green\nRichard Menger\nRichard Rosenblatt\nRick Young\nRidhima Ahuja\nRiyaz Faizullabhoy\nRob Goodman\nRob McElhenney\nRob Pardo\nRob Rhinehart\nRobbie Petersen\nRobbie Peterson\nRobert Alexander\nRobert Cottrell\nRobert Hackett\nRobert Kolker\nRobert Leshner\nRobert McNeely\nRobert Moreno\nRobert Siegel\nRobert Stromberg\nRobert Weber\nRobin Casey\nRobin Guo\nRobin Weisman\nRod Johnson\nRodrigo Ibarra Lopez\nRodrigo Pacheco\nRoger Dickey\nRoger Wattenhofer\nRoham Gharegozlou\nRohini Mukand\nRohit Bansal\nRoman Mars\nRoman Stanek\nRon Gill\nRon Lavi\nRon Rothblum\nRonald Evans\nRonnie Harris\nRosa Davila\nRosalind Rattan\nRose Legarda\nRoss Andersen\nRoss Shuel\nRostin Behnam\nRuben Gallego\nRuben Smith\nRuss Altman\nRuss Heddleston\nRuss Roberts\nRussell Davies\nRyan Allen\nRyan Caldbeck\nRyan Conde\nRyan Holloway\nRyan Hoover\nRyan McEntush\nRyan Petersen\nRyan Prescott\nRyan Sandler\nRyan Spoon\nRyan Tseng\nRyan Walsh\nRyan Ward\nRyan Wyatt\nSaar Tochner\nSachin Jain\nSafi Bahcall\nSagar Dhawan\nSaku Panditharatne\nSalem Vance\nSam Blackshear\nSam Broner\nSam Gerstenzang\nSam Ragsdale\nSam Thompson\nSam Williams\nSam Yam\nSamantha Gelt\nSamantha Langford\nSamantha Ludwig\nSamson Wu\nSamuel Arbesman\nSamuel Hammond\nSandra Samayoa\nSandy Jen\nSankaet Pathak\nSantiago Rodriguez\nSara Boesen\nSarah Fazal\nSarah Hamburg\nSarah Lumbard\nSarah Mascardo\nSarah Meiklejohn\nSarah Porter\nSarah Rebello\nSarah Wang\nSasha Stiles\nSatish Talluri\nSaurabh Ladha\nSavannah Cherry\nScott Clark\nScott Duke Kominers\nScott Gottlieb\nScott Hassan\nScott Kupor\nScott Rubin\nScott Shenker\nScott Tyler\nScott Walker\nScott Weiss\nSean Duffy\nSean Neville\nSebastian Oddo\nSeema Amble\nSeemay Chou\nSep Kamvar\nSergiu Pasca\nSeth Lobree\nSeth Sivak\nSeth Sternberg\nShai Bernstein\nShai Kopeld\nShaka Senghor\nShakil Khan\nShan Sinha\nShana Fisher\nShane Mac\nShane Parrish\nShangda Xu\nShannon (Stubo) Brayton\nShannon Barbour\nShannon Kelly\nShannon Schiltz\nShannon Snow\nShari Doherty\nSharon Chang\nShawn Conway\nSheela Krothapalli\nShellye Archambeau\nSherie James\nSherriAnn Cole\nShishir Mehrotra\nShonda Rhimes\nSid Gorham\nSigne Pierce\nSimon Denny\nSiqi Chen\nSonal Chokshi\nSophie Song\nSoubhik Deb\nSpencer Dinwiddie\nSpencer Howard\nSpencer Rascoff\nSreeram Kannan\nSreevidya Kasturil\nSri Kosuri\nSriram Krishnan\nSrivatsan Sridhar\nStacey Cunningham\nStacey Merrick\nStacia Murray\nStacy Brown-Philpot\nStacy D'Amico\nStacy Warner\nStefan McDonough\nSten Tamkivi\nStephane Bancel\nStephanie Anyanwu\nStephanie Cohen\nStephanie Doppelt\nStephanie Smith\nStephanie Watkins\nStephanie Zinn\nStephen Armanios\nStephen Wink\nStephenie Zhang\nSteve Buress\nSteve Cadigan\nSteve Cheney\nSteve Harvey\nSteve Kaczynski\nSteve McDermid\nSteve Smith\nSteve Zhao\nSteven Adair\nSteven Ebert\nSteven Johnson\nSteven Levy\nSteven Sinofsky\nStewart Butterfield\nStina Ehrensvärd\nStuart Luman\nStuart Russell\nSudip Chakrabarti\nSue Hager\nSuhail Doshi\nSukhinder Singh Cassidy\nSumeet Singh\nSumit Shah\nSungMo Park\nSunil Chokshi\nSurya Ganguli\nSusan B. Wilde\nSusan Mernit\nSusan Rice\nSusannah Fox\nSydney Paul\nTaavet Hinrikus\nTaggart Matthiesen\nTamzen Brewis\nTana Billingsley\nTarek Mansour\nTarun Chitra\nTauri Laws Phillips\nTawny Holguin\nTaylor McFadden\nTed Not Lasso\nTed Sarandos\nTed Ullyot\nTerell Sterling\nTerence Carroll\nTeresa Carlson\nTerry Angelos\nTerry Brown\nThan Nguyen\nThanh Nguyen\nThe 2015 Academic Roundtable Sessions\nThe TxO team\nTheresa DeMichele\nTheresa Dilley\nTheresa Fisher\nTheresa Walz\nTheresia Gouw\nThibaut Scholasch\nThomas Gjerde\nThomas Juenger\nThomas Long\nThomas Rando\nTiffany Vo\nTiffany Zhong\nTim Beiko\nTim O'Reilly\nTim Roughgarden\nTim Schafer\nTim Sullivan\nTimmu Tõke\nTina Anderson\nTina Bhatnagar\nTina Ferguson\nTina Wie\ntinawie\nTing Ni\nTobi Lütke\nTodd Cranney\nTodd Lutwak\nTodd McKinnon\nTodd Park\nTodd Young\nTolga Dizdarer\nTom Butta\nTom Coates\nTom Davenport\nTom Ellis\nTom Hammer\nTom Hofmann\nTom Lehman\nTom Mitchell\nTom Preston-Werner\nTom Rikert\nTom Standage\nTomicah Tillemann\nTony Blair\nTony Blinken\nTori Landrum\nTracy Chou\nTracy Young\nTren Griffin\nTrent Mayol\nTrevor Bedford\nTristan Handy\nTristan Walker\nTroy Kirwin\nTugce Erten\nTurner Novak\nTushar Garg\nTyler Cowen\nTyler Wilson\nTyson Clark\nUma Valeti\nUsman Azam\nUzi Dutta\nValentina Marzorati\nValeria Nikolaenko\nValerie Arboleda\nVan Jones\nVan Le-Gray\nVanessa Kropf\nVas Narasimhan\nVaughn Ferguson\nVenkat Mocherla\nVicente De Baca\nVickie Casillas-Smith\nVictor Liang\nVictor Shoup\nVictoria Butcher\nVijay Balasubramaniyan\nVijay Kedar\nVijay Pande\nVineeta Agarwala\nVinod Khosla\nVirginia Postrel\nVishal Amin\nVitalik Buterin\nVivian Brooks\nVoices Onchain\nW. Brian Arthur\nWahab Owolabi\nWei Luo\nWendy Drpic\nWerner Gerola\nWes Taylor\nWhitney Owens\nWill Brown\nWill Wong\nWillem Mulder\nWilliam Gifford\nWilliam Mougayar\nWing Cheng\nXian Zhang\nXiang-Dong Fu\nXingchen Zhou\nYannai A. Gonczarowski\nYehuda Lindell\nYevgeniy Dodis\nYinuo Zhang\nYogi Roth\nYohei Ishii\nYoko Li\nYoni Levy\nYoram Novick\nYuichi Kurosawa\nYujin Chung\nYun Fan\nYung Yung Sheung\nYuval Efron\nYuval Harari\nZac Bookman\nZach Abrams\nZach Cohen\nZach Dicker\nZach Haigney\nZachary Chen\nZachary Gray\nZack Weiner\nZahabiya Gabaji\nZak Doric\nZal Bilimoria\nZane Lackey\nZeta Avarikioti\nZeya Yang\nZooko Wilcox\nZoran Basich\n\nclear all Ciamac Moallemi\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n09.21.23 / Ciamac Moallemi\nAutomated market making and arbitrage profits in the presence of fees\nCiamac Moallemi reintroduces “loss-versus-rebalancing” (LVR), which quantifies the loss to arbitrageurs in an idealized, continuous-time setting with no fees.\n\nresearch\nDeFi\nLVR\nvideo\n\n10.28.22 / Ciamac Moallemi\nLiquidity Provision and Automated Market Making\nAn introduction to constant function market makers (CFMMs), which have emerged as the dominant mechanism for decentralized exchange on blockchains.\n\nresearch\nAMMs\nDeFi\nLVR\nvideo\n\n09.18.22 / Jason Milionis, Ciamac Moallemi, Tim Roughgarden and Anthony Lee Zhang\nLVR: Quantifying the Cost of Providing Liquidity to Automated Market Makers\nWe explain a new way to think about the cost side of becoming a liquidity partner, based on a quantity called LVR (“loss versus rebalancing,” pronounced “lever”).\n\nresearch\nAMMs\nDeFi\nLVR\npricing\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":6990,"crawled_at":1791194317256}
+{"id":10364,"url":"https://docs.sui.io/sui-stack/walrus","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Walrus | Sui Documentation","text":"Walrus is a decentralized storage and data availability protocol designed for large binary files. It uses Sui for coordination, payment, and governance, making it a natural storage layer for apps built on Sui.\n\nWalrus Docs\n↗\nData Storage Using Walrus\nLearn how to store and retrieve data on Walrus by walking through OnlyFins, a content platform built on Sui and Walrus.\n→\nCustom Indexer and Walrus\nWalrus is a content-addressable storage protocol, where data is retrieved using a unique identifier derived from the content itself, rather than from a file path or location. Integrating a custom Sui Indexer with Walrus can provide novel user experiences.\n→\nEncrypted Social Media\nBuild a Web3 social platform with encrypted content, Seal-based access control, and Walrus storage on Sui.\n→\nOnchain Websites with Walrus Sites\nLearn how to deploy and manage static websites on Walrus using the site-builder CLI, with configuration, custom headers, and SuiNS domain names.\n→","tokens":243,"crawled_at":1791194325127}
+{"id":10365,"url":"https://www.getfoundry.sh/cast/eip-7702-delegation","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"EIP-7702 account delegation – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nEIP-7702 account delegation\n\nEIP-7702 lets an externally owned account (EOA) delegate code execution to a deployed contract. Cast can sign the authorization separately with cast wallet sign-auth, or sign and include it directly with cast send --auth.\n\nThe positional ADDRESS passed to cast wallet sign-auth is the implementation contract. The authority is derived from the wallet that signs the authorization.\n\nPrerequisites\n\nThe target chain must support EIP-7702. For local development, start Anvil with the Prague hardfork:\n\n$ anvil --hardfork prague\n\nThe examples use these values:\n\nVariableMeaning\n$AUTHORITY\nEOA whose code will point to the implementation\n\n$IMPLEMENTATION\nDeployed contract whose code will execute for the authority\n\n$BROADCASTER\nAccount that submits and pays for the EIP-7702 transaction\n\n$RPC_URL\nRPC endpoint for an EIP-7702-compatible chain\n\nThe authority and broadcaster names in the examples refer to encrypted Cast keystores. See wallet operations for keystore setup.\n\nSign and broadcast in one step\n\nWhen the authority broadcasts the transaction, pass the implementation address directly to --auth. Cast signs the authorization with the transaction signer and selects the authorization nonce automatically:\n\n$ cast send $AUTHORITY \"initialize(address)\" $OWNER \\\n--auth $IMPLEMENTATION \\\n--account authority \\\n--rpc-url $RPC_URL\n\nThe authorization is processed before the call, so the call to $AUTHORITY executes initialize(address) from $IMPLEMENTATION in the authority's context. Replace that function with calldata supported by your implementation.\n\nUse a separate broadcaster\n\nAn authority can sign an authorization without broadcasting the transaction. cast wallet sign-auth prints the RLP-encoded signed authorization:\n\n$ AUTH=$(cast wallet sign-auth $IMPLEMENTATION \\\n--account authority \\\n--rpc-url $RPC_URL)\n\nA different account can include that authorization in a transaction and pay its gas:\n\n$ cast send $AUTHORITY \"initialize(address)\" $OWNER \\\n--auth $AUTH \\\n--account broadcaster \\\n--rpc-url $RPC_URL\n\n--auth accepts either an implementation address or a signed authorization. The address form is signed by the transaction signer. Use the signed form when the authority and broadcaster are different accounts.\n\nChoose the authorization nonce\n\nAn authorization is valid only when its nonce equals the authority's nonce during authorization processing.\n\nFlowNonce behavior\ncast send --auth $IMPLEMENTATION\nCast signs for the transaction sender using the carrier transaction nonce plus one.\n\ncast wallet sign-auth with a different broadcaster\nCast queries and uses the authority's current nonce.\n\ncast wallet sign-auth --self-broadcast\nCast queries the current nonce and adds one because the authority's carrier transaction increments it first.\n\ncast wallet sign-auth --nonce $NONCE\nCast uses the exact nonce provided.\n\nUse --self-broadcast only when the same authority will submit the pre-signed authorization:\n\n$ AUTH=$(cast wallet sign-auth $IMPLEMENTATION \\\n--self-broadcast \\\n--account authority \\\n--rpc-url $RPC_URL)\n\n$ cast send $AUTHORITY \"initialize(address)\" $OWNER \\\n--auth $AUTH \\\n--account authority \\\n--rpc-url $RPC_URL\n\nYou can also set the chain and nonce explicitly:\n\n$ AUTH=$(cast wallet sign-auth $IMPLEMENTATION \\\n--chain $CHAIN_ID \\\n--nonce $AUTHORITY_NONCE \\\n--account authority)\n\nVerify the delegation\n\nRead the authority's code after the transaction is mined:\n\n$ cast code $AUTHORITY --rpc-url $RPC_URL\n\nFor an active delegation, the result is the 23-byte delegation indicator 0xef0100 followed by the implementation address. You can also inspect the transaction's authorization list:\n\n$ cast tx $TX_HASH authorizationList --json --rpc-url $RPC_URL\n\nReplace or clear a delegation\n\nAuthorize a different implementation to replace the existing delegation. To restore the account to empty EOA code, authorize the zero address:\n\n$ cast send $AUTHORITY \\\n--auth 0x0000000000000000000000000000000000000000 \\\n--account authority \\\n--rpc-url $RPC_URL\n\nRelated references\n\ncast wallet sign-auth — Sign and RLP-encode an authorization.\n\ncast send — Include address-based or pre-signed authorizations with --auth.\n\nsignDelegation — Create and attach delegations from Solidity tests and scripts.\n\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":1087,"crawled_at":1791194329060}
+{"id":10366,"url":"https://docs.compound.xyz/collateral-and-borrowing","domain":"docs.compound.xyz","chapter":"defi_protocols","title":"Compound III Docs | Collateral & Borrowing","text":"Compound III\nInterest Rates\nCollateral & Borrowing\nLiquidation\nAccount Management\nProtocol Rewards\nERC-4626 Wrapper\nGovernance\nHelper Functions\n\nCollateral & Borrowing\nSupply\nWithdraw or Borrow\nCollateral Balance\nBorrow Collateralization\nMinimum Borrow Balance\n\nCollateral & Borrowing\nUsers can add collateral assets to their account using the supply function. Collateral can only be added if the market is below its supplyCap, which limits the protocol’s risk exposure to collateral assets.\nEach collateral asset increases the user’s borrowing capacity, based on the asset’s borrowCollateralFactor. The borrowing collateral factors are percentages that represent the portion of collateral value that can be borrowed.\nFor instance, if the borrow collateral factor for WBTC is 85%, an account can borrow up to 85% of the USD value of its supplied WBTC in the base asset. Collateral factors can be fetched using the Get Asset Info By Address function.\nThe base asset can be borrowed using the withdraw function; the resulting borrow balance must meet the borrowing collateral factor requirements. If a borrowing account subsequently fails to meet the borrow collateral factor requirements, it cannot borrow additional assets until it supplies more collateral, or reduces its borrow balance using the supply function.\nAccount balances for the base token are signed integers. An account balance greater than zero indicates the base asset is supplied and a balance less than zero indicates the base asset is borrowed. Note: Base token balances for assets with 18 decimals will start to overflow at a value of 2103/1e18=~10 trillion.\nAccount balances are stored internally in Comet as principal values (also signed integers). The principal value, also referred to as the day-zero balance, is what an account balance at T0 would have to be for it to be equal to the account balance today after accruing interest.\nGlobal indices for supply and borrow are unsigned integers that increase over time to account for the interest accrued on each side. When an account interacts with the protocol, the indices are updated and saved. An account’s present balance can be calculated using the current index with the following formulas.\nBalance = Principal * BaseSupplyIndex [Principal > 0]\nBalance = Principal * BaseBorrowIndex [Principal < 0]\n\nSupply\nThe supply function transfers an asset to the protocol and adds it to the account’s balance. This function can be used to supply collateral, supply the base asset, or repay an open borrow of the base asset.\nIf the base asset is supplied resulting in the account having a balance greater than zero, the base asset earns interest based on the current supply rate. Collateral assets that are supplied do not earn interest.\nThere are three separate methods to supply an asset to Compound III. The first is on behalf of the caller, the second is to a separate account, and the third is for a manager on behalf of an account.\nBefore supplying an asset to Compound III, the caller must first execute the asset’s ERC-20 approve of the Comet contract.\nComet\nfunction supply(address asset, uint amount)\n\nfunction supplyTo(address dst, address asset, uint amount)\n\nfunction supplyFrom(address from, address dst, address asset, uint amount)\n\nasset: The address of the asset’s smart contract.\namount: The amount of the asset to supply to Compound III expressed as an integer. A value of MaxUint256 will repay all of the dst’s base borrow balance.\ndst: The address that is credited with the supplied asset within the protocol.\nfrom: The address to supply from. This account must first use the Allow method in order to allow the sender to transfer its tokens prior to calling Supply.\nRETURN: No return, reverts on error.\nSolidity\nComet comet = Comet(0xCometAddress);\ncomet.supply(0xERC20Address, 1000000);\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nawait comet.supply(usdcAddress, 1000000);\n\nWithdraw or Borrow\nThe withdraw method is used to withdraw collateral that is not currently supporting an open borrow. Withdraw is also used to borrow the base asset from the protocol if the account has supplied sufficient collateral. It can also be called from an allowed manager address.\nCompound III implements a minimum borrow position size which can be found as baseBorrowMin in the protocol configuration. A withdraw transaction to borrow that results in the account’s borrow size being less than the baseBorrowMin will revert.\nComet\nfunction withdraw(address asset, uint amount)\n\nfunction withdrawTo(address to, address asset, uint amount)\n\nfunction withdrawFrom(address src, address to, address asset, uint amount)\n\nasset: The address of the asset that is being withdrawn or borrowed in the transaction.\namount: The amount of the asset to withdraw or borrow. A value of MaxUint256 will withdraw all of the src’s base balance.\nto: The address to send the withdrawn or borrowed asset.\nsrc: The address of the account to withdraw or borrow on behalf of. The withdrawFrom method can only be called by an allowed manager.\nRETURN: No return, reverts on error.\nSolidity\nComet comet = Comet(0xCometAddress);\ncomet.withdraw(0xwbtcAddress, 100000000);\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nawait comet.withdraw(usdcAddress, 100000000);\n\nCollateral Balance\nThis function returns the current balance of a collateral asset for a specified account in the protocol.\nComet\nfunction collateralBalanceOf(address account, address asset) external view returns (uint128)\n\naccount: The address of the account in which to retrieve a collateral balance.\nasset: The address of the collateral asset smart contract.\nRETURNS: The balance of the collateral asset in the protocol for the specified account as an unsigned integer scaled up by 10 to the “decimals” integer in the asset’s contract.\nSolidity\nComet comet = Comet(0xCometAddress);\nuint balance = comet.collateralBalanceOf(0xAccount, 0xUsdcAddress);\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst balance = await comet.callStatic.collateralBalanceOf('0xAccount', '0xUsdcAddress');\n\nBorrow Collateralization\nThis function returns true if the account passed to it has non-negative liquidity based on the borrow collateral factors. This function returns false if an account does not have sufficient liquidity to increase its borrow position. A return value of false does not necessarily imply that the account is presently liquidatable (see isLiquidatable function).\nComet\nfunction isBorrowCollateralized(address account) public view returns (bool)\n\naccount: The account to examine collateralization.\nRETURNS: Returns true if the account has enough liquidity for borrowing.\nSolidity\nComet comet = Comet(0xCometAddress);\nbool isCollateralized = comet.isBorrowCollateralized(0xAccount);\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst isCollateralized = await comet.callStatic.isBorrowCollateralized('0xAccount');\n\nMinimum Borrow Balance\nThis function returns the minimum borrow balance allowed in the base asset. An account’s initial borrow size must be equal to or greater than this value. Subsequent borrows may be of any size.\nComet\nfunction baseBorrowMin() public view returns (uint256)\n\nRETURNS: The minimum borrow balance allowed by the protocol as an unsigned integer scaled up by 10 to the “decimals” integer in the base asset’s contract.\nSolidity\nComet comet = Comet(0xCometAddress);\nuint baseBorrowMin = comet.baseBorrowMin();\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst baseBorrowMin = await comet.callStatic.baseBorrowMin();","tokens":1929,"crawled_at":1791194342614}
+{"id":10367,"url":"https://www.getfoundry.sh/help/faq","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"FAQ – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nFAQ\n\nCommon questions about Foundry.\n\nGeneral\n\nWhat is Foundry?\n\nFoundry is a fast, portable, and modular toolkit for Ethereum development written in Rust. It includes:\n\nForge — Build, test, and deploy smart contracts\n\nCast — Interact with the chain from the command line\n\nAnvil — Local Ethereum node for development\n\nChisel — Interactive Solidity REPL\n\nHow do I install Foundry?\n\nUse foundryup:\n\n$ curl -L https://getfoundry.sh/install | bash\n$ foundryup\n\nSee Installation for details.\n\nHow do I update Foundry?\n\nRun foundryup again:\n\n$ foundryup\n\nTo install a specific version:\n\n$ foundryup --install nightly-abc123\n\nHow do I get help with a command?\n\nAll Foundry tools support --help:\n\n$ forge --help\n$ forge test --help\n$ cast --help\n$ anvil --help\n$ chisel --help\n\nSee the CLI reference for full command docs.\n\nForge\n\nHow do I run a specific test?\n\nUse --match-test:\n\n$ forge test --match-test test_Transfer\n\nUse --match-contract for a specific contract:\n\n$ forge test --match-contract TokenTest\n\nHow do I see console.log output?\n\nUse verbosity level 2 or higher:\n\n$ forge test -vv\n\nWhy are my tests slow?\n\nCommon causes:\n\nForking without a pinned block — Pin the fork with --fork-block-number so the RPC cache is reused across runs\n\nToo many fuzz runs — Reduce fuzz.runs in foundry.toml for local development\n\nLarge contracts — Consider splitting tests into separate files\n\nHow do I debug a failing test?\n\nUse the interactive debugger:\n\n$ forge test --match-test test_MyTest --debug\n\nOr increase verbosity to see the trace:\n\n$ forge test --match-test test_MyTest -vvvv\n\nSee Debugging for more.\n\nHow do I fork mainnet in tests?\n\nSet --fork-url or configure it in foundry.toml:\n\n$ forge test --fork-url https://ethereum.reth.rs/rpc\n\nOr in foundry.toml:\n\n[profile.default]\nfork_url = \"https://ethereum.reth.rs/rpc\"\n\nHow do I run tests in parallel?\n\nTests run in parallel by default. To control parallelism:\n\n$ forge test --jobs 4\n\nSet to 1 for sequential execution (useful for debugging):\n\n$ forge test --jobs 1\n\nCast\n\nHow do I call a contract function?\n\nUse cast call for read-only calls:\n\n$ cast call $CONTRACT \"balanceOf(address)\" $ADDRESS\n\nUse cast send for state-changing transactions:\n\n$ cast send $CONTRACT \"transfer(address,uint256)\" $TO $AMOUNT --private-key $KEY\n\nHow do I decode transaction data?\n\nUse cast 4byte-calldata:\n\n$ cast 4byte-calldata 0xa9059cbb000000000000000000000000...\n\nHow do I convert between units?\n\nUse cast to-wei and cast from-wei:\n\n$ cast to-wei 1 ether\n# 1000000000000000000\n\n$ cast from-wei 1000000000000000000\n# 1.000000000000000000\n\nAnvil\n\nHow do I get test ETH?\n\nAnvil pre-funds 10 accounts with 10,000 ETH each. List them:\n\n$ anvil\n# Shows accounts and private keys on startup\n\nHow do I impersonate an account?\n\nStart Anvil with auto-impersonation:\n\n$ anvil --auto-impersonate\n\nOr impersonate a specific account via RPC:\n\n$ cast rpc anvil_impersonateAccount $ADDRESS\n\nHow do I reset the chain state?\n\nUse the RPC method:\n\n$ cast rpc anvil_reset\n\nOr restart Anvil.\n\nHow do I mine blocks manually?\n\nDisable auto-mining and mine manually:\n\n$ anvil --no-mining\n# In another terminal:\n$ cast rpc anvil_mine 10 # Mine 10 blocks\n\nChisel\n\nHow do I access my project's contracts?\n\nChisel automatically loads your project. Import and use contracts:\n\n➜ import {Counter} from \"src/Counter.sol\";\n➜ Counter c = new Counter();\n➜ c.increment();\n\nHow do I fork in Chisel?\n\nStart with a fork:\n\n$ chisel --fork-url https://ethereum.reth.rs/rpc\n\nOr fork during a session:\n\n➜ !fork https://ethereum.reth.rs/rpc\n\nHow do I save my session?\n\nUse the !save command:\n\n➜ !save my-session\n\nLoad it later:\n\n$ chisel load my-session\n\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":935,"crawled_at":1791194349107}
+{"id":10368,"url":"https://docs.sui.io/sui-stack/walrus/only-fins","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Encrypted Social Media | Sui Documentation","text":"OnlyFins is a Web3 social platform that demonstrates encrypted content sharing with onchain access control. Creators publish posts with images they store on Walrus and encrypt through Seal, while viewers purchase ViewerToken capability objects to decrypt and view content. The app uses Enoki for zkLogin authentication and sponsored transactions so users interact without holding SUI for gasGasThe computational cost of execution and object storage for a transaction..\n\ncaution\nOnlyFins is a demo pattern, not production-ready code. Before adapting it, work through this checklist: rate-limit and authorize sponsored transactionsSponsored transactionWhen one address pays the gas fee for a transaction submitted by another address. so an attacker cannot drain your gas budget; enforce Seal session-key expiry rather than holding long-lived sessions; understand the transferTransferChanging the owner of an asset. semantics of the ViewerToken objectObjectThe basic unit of storage on Sui. (a transferable token grants access to whoever holds it); and remember that all post metadata, blob IDs, and onchain activity are public even when the image bytes are encrypted. See the Security Best Practices guide.\n\nWhen to use this pattern​\n\nUse this pattern when you need to:\n\nGate access to encrypted content with onchain ownership tokens rather than a centralized paywall server.\n\nStore encrypted files on Walrus and control decryption through Seal threshold encryption tied to MoveMoveAn open source programming language used for all activity on Sui.-level access control.\n\nLet users authenticate with Google through zkLoginzkLoginA Sui primitive that allows you to send transactions using an OAuth credential. and interact without holding SUI for gas.\n\nBuild a content marketplace where creators publish and viewers pay for access, all verifiable onchain.\n\nCombine shared objects (posts visible to all) with owned objects (viewer tokens that prove access) in a single application.\n\nWhat you learn​\n\nThis example teaches:\n\nShared objects: Posts are shared objects that any user can read metadata from, but only authorized users can decrypt the attached content.\n\nCapability pattern: ViewerToken objects act as owned capability tokens that prove a user purchased access to a specific post.\n\nSeal encryption: Threshold encryption where the Move contract itself authorizes decryption key release. Seal key servers only return the decryption key after dry-running a seal_approve_access transactionTransactionA number of commands that execute on inputs to define the result of the transaction. that confirms the caller holds a valid ViewerToken.\n\nSponsored transactions: A backend pays gas so users interact without holding SUI. The frontend sends unsigned transactions to the sponsor backend, which co-signs and returns the sponsored bytes.\n\nWalrus storage: The frontend stores encrypted image blobs offchain on Walrus and references them by blob ID. Walrus blobs are publicly addressable, so you must encrypt content to restrict access.\n\nArchitecture​\n\nThe example has 4 actors and 1 onchain packagePackageSmart contracts on Sui.. The frontend builds transactions and renders post feeds as a React app. The Enoki wallet handles zkLogin authentication and transaction signing. The posts Move package stores post metadata and issues ViewerToken objects as shared and address-owned objects on Sui. Seal key servers hold threshold encryption keys and release them only when the Move contract confirms access through seal_approve_access. Walrus stores the actual image blobs, both encrypted and unencrypted. The sponsor backend covers gas fees so users do not need SUI in their wallet.\n\nThe diagram below traces 1 full interaction from a user unlocking content to viewing the decrypted image.\n\nThe following steps walk through the flow:\n\nThe user clicks Unlock Image on a locked post, triggering the usePayForContent hook.\n\nThe frontend builds a grant_access transaction and sends it to the sponsor backend, which pays for gas and returns the co-signed transaction.\n\nThe wallet signs and submits the transaction. The Move package creates a ViewerToken owned by the user.\n\nThe frontend detects the new token, builds a seal_approve_access transaction, and sends it to the Seal key servers.\n\nSeal dry-runs the transaction against the Move contract. Because the user now holds a valid ViewerToken, the contract confirms access.\n\nSeal returns the decryption key. The frontend fetches the encrypted blob from Walrus, decrypts it locally, and renders the image.\n\nErrors can occur at the sponsorship step (backend unreachable), the Seal step (session key expired), or the Walrus fetch (blob not found).\n\nHow Seal and Walrus work together​\n\nWalrus is a content-addressed storage protocol where you retrieve data by blob ID. Walrus makes all blobs publicly addressable, so anyone who knows the blob ID can fetch the raw bytes. To restrict access, the frontend encrypts content before uploading to Walrus.\n\nSeal provides the encryption layer. When a creator publishes a post, the frontend encrypts the image with a key managed by Seal's threshold key servers. The Move contract defines who can decrypt: the seal_approve_access function checks whether the caller is the post author or holds a ViewerToken for that post. Seal key servers only release the decryption key after dry-running this function and confirming it does not abort.\n\nThis combination means Walrus handles storage and availability, Seal handles key management and access control, and the Move contract defines the access policy.\n\nPrerequisites\n\nAn existing React frontend and a backend you can run scripts from.\n\nInstall the Sui CLI and fund an address with Testnet SUI.\n\nNode.js 18 or later with pnpm.\n\nAn Enoki project for zkLogin, or Slush Wallet.\n\nFor the underlying primitives, see Data Storage Using Walrus and Encryption with Seal.\n\nReference app​\n\nA complete implementation lives in onlyfins-example-app, split into a frontend, a backend sponsor service, and the move/posts package.\n\nPublish the Move package and record the package ID, which both the frontend and backend need:\n\n$ sui client publish --gas-budget 200000000\n\nThe frontend reads it from POSTS_PACKAGE_ID in src/constants.ts. The backend reads it from PACKAGE_ID in .env, alongside the author key pairs that publish demo content:\n\nbackend/.env\nAUTHOR_1_PRIVATE_KEY=YOUR_ED25519_PRIVATE_KEY\nPACKAGE_ID=YOUR_PACKAGE_ID\n\nExport a private key with sui keytool export --key-identity YOUR_WALLET_ADDRESS and copy the exportedPrivateKey value, which starts with suiprivkey1.\n\nHow the pieces fit together​\n\n3 decisions carry over to any app that combines these primitives:\n\nEncrypt before uploading. Walrus blobs are publicly addressable by blob ID. Anything you upload unencrypted is readable by anyone who learns the ID, so access control has to live in the encryption, not in the storage.\n\nLet the contract authorize decryption. Seal key servers dry-run seal_approve_access before releasing a key. Access control is therefore Move code, and changing who can decrypt means changing onchain state rather than reconfiguring a server.\n\nSponsor gas if users authenticate with zkLogin. A user who signed in with Google has no SUI. The backend co-signs transactions so the wallet never needs a funded balance. See Sponsored Transactions.\n\nKey code highlights​\n\ncreate_post with optional encryption\nThe create_post entry function creates a shared Post object with an optional encryption ID. When encryption_id contains a value, the post requires a ViewerToken to decrypt. When it contains none, the image is publicly viewable. The function shares the post so any user can read its metadata.\n\ngrant_access with viewer tokens\nThe grant_access function mints a new ViewerToken and returns it. The token links the viewer addressAddressA unique, anonymous identity on a blockchain network. to a specific post ID, which seal_approve_access checks later.\n\nseal_approve_access gate\nThe seal_approve_access function is the onchain gate that Seal calls before releasing decryption keys. It checks two conditions: the caller is the post author, or the caller holds a ViewerToken linked to this post. It also verifies the requested encryption_id matches the post. If any check fails, the transaction aborts and Seal refuses to release the key.\n\nMystenLabs/onlyfins-example-app/frontend/move/posts/sources/posts.move\n1/// Simple post module for OnlyFins Phase 1 (no encryption)\n2module posts::posts {\n3 use std::string::String;\n4 use sui::clock::Clock;\n5 use sui::coin::Coin;\n6 use sui::sui::SUI;\n7\n\n8 /// A shared post object\n9 public struct Post has key {\n10 id: UID,\n11 author: address,\n12 caption: String,\n13 image_blob_id: String,\n14 created_at: u64,\n15 encryption_id: Option<vector<u8>>\n16 }\n17\n\n18 public struct ViewerToken has key, store {\n19 id: UID,\n20 post_id: ID\n21 }\n22\n\n23 /// Create and share a Post object\n24 public fun create_post(\n25 caption: String,\n26 image_blob_id: String,\n27 encryption_id: Option<vector<u8>>,\n28 clock: &Clock,\n29 ctx: &mut TxContext\n30 ) {\n31 let post = Post {\n32 id: object::new(ctx),\n33 author: ctx.sender(),\n34 caption,\n35 image_blob_id,\n36 created_at: clock.timestamp_ms(),\n37 encryption_id,\n38 };\n39 transfer::share_object(post);\n40 }\n41\n\n42 public fun grant_access(\n43 post: &Post,\n44 ctx: &mut TxContext\n45 ): ViewerToken {\n46 ViewerToken { id: object::new(ctx), post_id: post.id.to_inner() }\n47 }\n48\n49 public entry fun seal_approve_access(\n50 encryption_id: vector<u8>, // Not needed with ViewerToken, but Seal expects it\n51 post: &Post,\n52 viewer_token: &ViewerToken,\n53 ctx: &TxContext\n54 ) {\n55 // Verify encryption_id matches post's encryption_id\n56 assert!(post.encryption_id.is_some(), 0);\n57 assert!(*post.encryption_id.borrow() == encryption_id, 1);\n58\n59 // Check if caller is post author (free access)\n60 if (ctx.sender() == post.author) {\n61 return\n62 };\n63\n64 // Check if ViewerToken matches this post\n65 assert!(viewer_token.post_id == object::id(post), 2);\n66 }\n67}\n68\n\nPaying for content​\n\nThe usePayForContent hook builds and sponsors the transaction that grants a viewer access to a post.\n\ngithub.com/MystenLabs/onlyfins-example-app/frontend/src/hooks/usePayForContent.ts\n/**\n* Hook to request access to encrypted content using sponsored transactions.\n* Calls the grant_access Move function which:\n* 1. Returns a ViewerToken (no payment required in demo mode)\n* 2. Transfers token to the user\n*\n* After successful access, invalidates ViewerTokens query to trigger refetch.\n*/\nexport function usePayForContent() {\nconst { sponsorAndExecuteTransaction } = useSponsoredTransaction();\nconst suiClient = useSuiClient();\nconst currentAccount = useCurrentAccount();\nconst queryClient = useQueryClient();\n\nconst mutation = useMutation({\nmutationFn: async (params: PayForContentParams): Promise<string> => {\nif (!currentAccount?.address) {\nthrow new Error('No wallet connected');\n}\n\nconst tx = new Transaction();\n\n// Call grant_access function - this RETURNS the ViewerToken (no payment required)\nconst [viewerToken] = tx.moveCall({\ntarget: `${POSTS_PACKAGE_ID}::posts::grant_access`,\narguments: [\ntx.object(params.postId), // post: &Post\n],\n});\n\n// Transfer the returned ViewerToken to the current user\ntx.transferObjects([viewerToken], currentAccount.address);\n\n// Execute transaction with sponsorship\nconst result = await sponsorAndExecuteTransaction(tx);\n\nif (!result) {\nthrow new Error('Sponsored transaction failed');\n}\n\n// Wait for transaction to complete\nconst txResult = await suiClient.waitForTransaction({\ndigest: result.digest,\noptions: {\nshowEffects: true,\nshowObjectChanges: true,\n},\n});\n\n// Extract created ViewerToken object ID\nconst viewerTokenObj = txResult.objectChanges?.find(\n(change) =>\nchange.type === 'created' &&\nchange.objectType.includes('::posts::ViewerToken')\n);\n\nif (viewerTokenObj && viewerTokenObj.type === 'created') {\nreturn viewerTokenObj.objectId;\n}\n\nreturn ''; // Success but no object ID found\n},\nonSuccess: () => {\n// Invalidate ViewerTokens query to trigger refetch\n// This will cause all PostCards to re-check access\n// Use predicate to match useSuiClientQuery's key structure: [network, method, params]\nqueryClient.invalidateQueries({\npredicate: (query) =>\nArray.isArray(query.queryKey) &&\nquery.queryKey[1] === 'getOwnedObjects' &&\n(query.queryKey[2] as any)?.owner === currentAccount?.address,\n});\n},\n});\n\nreturn mutation;\n}\n\nThe hook calls the grant_access Move function, transfers the resulting ViewerToken to the current account, and sponsors the transaction so the user pays no gas. After the transaction finalizes, it refetches the user's owned objects so the UI updates.\n\nDecrypting images through Seal​\n\nThe usePostDecryption hook fetches encrypted images from Walrus and decrypts them using Seal session keys.\n\ngithub.com/MystenLabs/onlyfins-example-app/frontend/src/hooks/usePostDecryption.ts\n/**\n* Automatically decrypts post images when user has access (ViewerToken) and session key.\n* Captions are now stored as plaintext and don't need decryption.\n*\n* @param posts - Transformed posts from transformSuiObjectsToPosts\n* @param rawSuiData - Raw blockchain data (needed for image blob IDs)\n* @param sessionKey - Seal session key for decryption\n* @param viewerTokens - User's ViewerTokens for access control\n* @returns Record of decrypted image URLs by post ID\n*/\nexport function usePostDecryption(\nposts: Post[],\nrawSuiData: SuiObjectResponse[] | undefined,\nsessionKey: SessionKey | null,\nviewerTokens: ViewerToken[]\n): Record<string, DecryptedContent> {\nconst [decryptedContent, setDecryptedContent] = useState<Record<string, DecryptedContent>>({});\nconst [decryptingPosts, setDecryptingPosts] = useState<Set<string>>(new Set());\n\nuseEffect(() => {\nif (!sessionKey || !rawSuiData) return;\n\n// Filter posts that need image decryption (unlocked + has encryptionId)\nconst postsToDecrypt = posts.filter(\n(p) => p.kind === 'unlocked' && 'encryptionId' in p && p.encryptionId\n);\n\nif (postsToDecrypt.length === 0) return;\n\n// Initialize Seal client\nconst sealClient = createSealClient();\n\n// Decrypt each post's image\npostsToDecrypt.forEach(async (post) => {\n// Skip if already decrypted or currently decrypting\nif (decryptedContent[post.id] || decryptingPosts.has(post.id)) {\nreturn;\n}\n\n// Mark as decrypting\nsetDecryptingPosts((prev) => new Set(prev).add(post.id));\nsetDecryptedContent((prev) => ({\n...prev,\n[post.id]: {\nimageBytes: '⏳ Decrypting image...',\nisDecrypting: true,\n},\n}));\n\ntry {\n// Find raw blockchain data for this post\nconst rawPost = rawSuiData.find((r) => r.data?.objectId === post.id);\nif (!rawPost?.data?.content || rawPost.data.content.dataType !== 'moveObject') {\nthrow new Error('Post data not found');\n}\n\nconst fields = rawPost.data.content.fields as any;\nconst encryptionId = (post as any).encryptionId;\nconsole.log('post encryptionId', encryptionId);\n\n// Find ViewerToken for access control\nconst viewerToken = viewerTokens.find((t) => t.postId === post.id);\nif (!viewerToken) {\nthrow new Error('ViewerToken not found');\n}\n\n// Build access control transaction\nconst tx = new Transaction();\ntx.moveCall({\ntarget: `${POSTS_PACKAGE_ID}::posts::seal_approve_access`,\narguments: [\ntx.pure.vector('u8', fromHex(encryptionId)),\ntx.object(post.id), // Post object\ntx.object(viewerToken.objectId), // ViewerToken as proof\n],\n});\n\nconst txBytes = await tx.build({ client: suiClient, onlyTransactionKind: true });\n\n// Fetch decryption keys from Seal\nawait sealClient.fetchKeys({\nids: [encryptionId],\ntxBytes: txBytes,\nsessionKey,\nthreshold: 1,\n});\n\n// Decrypt image (stored off-chain in Walrus)\nconst imageBlobId = fields.image_blob_id;\nconsole.log('imageBlobId', imageBlobId);\nconst walrusUrl = `${WALRUS_AGGREGATOR_URL}/${imageBlobId}`;\nconsole.log(`Fetching encrypted image from Walrus: ${walrusUrl}`);\n\nconst encryptedImage = await fetchFromWalrus(walrusUrl);\nconsole.log(`Decrypting image for post ${post.id}, size: ${encryptedImage.length} bytes`);\n\nconst decryptedImageBytes = await sealClient.decrypt({\ndata: encryptedImage,\nsessionKey,\ntxBytes,\ncheckShareConsistency: false,\n});\n\n// Convert decrypted image to blob URL (detect MIME type from byte signature)\nconst imageBytes = new Uint8Array(decryptedImageBytes);\nconst mimeType = imageBytes[0] === 0x89 && imageBytes[1] === 0x50 ? 'image/png' : 'image/jpeg';\nconst imageBlob = new Blob([imageBytes], { type: mimeType });\nconst imageUrl = URL.createObjectURL(imageBlob);\nconsole.log(`Image decrypted successfully: ${imageUrl}`);\n\n// Update with decrypted image\nsetDecryptedContent((prev) => ({\n...prev,\n[post.id]: {\nimageBytes: imageUrl,\nisDecrypting: false,\n},\n}));\n\n// Remove from decrypting set\nsetDecryptingPosts((prev) => {\nconst next = new Set(prev);\nnext.delete(post.id);\nreturn next;\n});\n} catch (error) {\nconsole.log('session key', sessionKey.export());\nconsole.error(`Image decryption failed for post ${post.id}:`, error);\n\n// Show error state\nsetDecryptedContent((prev) => ({\n...prev,\n[post.id]: {\nimageBytes: '❌ Image decryption failed',\nisDecrypting: false,\n},\n}));\n\n// Remove from decrypting set\nsetDecryptingPosts((prev) => {\nconst next = new Set(prev);\nnext.delete(post.id);\nreturn next;\n});\n}\n});\n}, [posts, rawSuiData, sessionKey, viewerTokens, decryptedContent, decryptingPosts]);\n\nreturn decryptedContent;\n}\n\nFor each encrypted post the user has access to, the hook builds a seal_approve_access transaction, retrieves the decryption key from the Seal key servers, fetches the encrypted blob from Walrus, and decrypts it locally. It auto-detects the image MIME type from the first bytes of the decrypted data.\n\nCommon modifications​\n\nAdd payment for access: Require viewers to pay SUI or a custom token in the grant_access function before minting the ViewerToken. Transfer the payment to the post author.\n\nAdd subscription tiers: Create a Subscription object that grants access to all posts from a creator for a set duration. Check subscription validity in seal_approve_access alongside the per-post ViewerToken check.\n\nReplace Enoki with wallet-only auth: Remove the Enoki zkLogin flow and use a standard wallet connection through dApp Kit. Remove the sponsor backend and let users pay their own gas.\n\nAdd content categories: Extend the Post struct with a category field. Filter posts by category in the frontend and allow creators to organize their content.\n\nAdd creator profiles: Create a shared CreatorProfile object per author that stores a display name, bio, and avatar blob ID on Walrus. Link posts to the profile for a richer feed experience.\n\nTroubleshooting​\n\nThe following sections address common issues with this example.\n\nPackage ID is missing or invalid​\n\nSymptom: The frontend logs Error: invalid package ID or transactions fail with PackageNotFound.\n\nCause: The POSTS_PACKAGE_ID in constants.ts still has the default value, or you published the package on a different network than the wallet targets.\n\nFix: Re-run the publish step on TestnetTestnetStaging network for testing changes before production deployment., then update constants.ts with the new package ID and restart the dev server.\n\nWallet does not connect​\n\nSymptom: Clicking Sign In does nothing, or the Google OAuth flow fails.\n\nCause: The Enoki API key or Google Client ID is misconfigured, or the browser blocks third-party cookies.\n\nFix: Verify the Enoki and Google credentials in main.tsx. Try a different browser or disable cookie-blocking extensions.\n\nSession key expired​\n\nSymptom: A modal appears saying the session key has expired, and decryption stops working.\n\nCause: Seal session keys have a 30-minute TTL. The key expired between signing and attempting decryption.\n\nFix: Click the button in the modal to sign a new session key. The app signs automatically and resumes decryption.\n\nEncrypted image fails to load​\n\nSymptom: A post unlocks (the app grants a ViewerToken) but the image shows as broken or never loads.\n\nCause: The Walrus aggregator is unreachable, the blob ID is invalid, or you did not upload the encrypted image to Walrus.\n\nFix: Verify the blob ID in the post object with sui client object POST_ID. Check that the Walrus aggregator URL in constants.ts is reachable. Re-upload the image if the blob ID is a placeholder.\n\nGas budget too low​\n\nSymptom: The transaction fails with InsufficientGas or a similar error.\n\nCause: The sponsor backend gas budget is below what the function consumes.\n\nFix: Increase the gas budget in the sponsor backend or the transaction builder. For CLI publishing, raise --gas-budget to 200000000.\nRelated topics\n\nZkLogin Technical Reference\nTechnical reference for zkLogin: protocol details, address derivation, OpenID terminology, ceremony, security analysis, and signature verification.\nSponsored Transactions\nSponsored transactions let you pay gas fees on behalf of another user, reducing onboarding friction for users who don't own SUI.\nSecurity Best Practices\nOverview of security best practices on Sui.\nShared Objects\nAnyone can access shared objects on the Sui network, so care must be taken to secure access, if needed.\n\nWhen to use this pattern\nWhat you learn\nArchitectureHow Seal and Walrus work together\n\nReference app\nHow the pieces fit together\nKey code highlightsPaying for content\nDecrypting images through Seal\n\nCommon modifications\nTroubleshootingPackage ID is missing or invalid\nWallet does not connect\nSession key expired\nEncrypted image fails to load\nGas budget too low\n\nWas this page helpful?","tokens":5359,"crawled_at":1791194350379}
+{"id":10369,"url":"https://a16zcrypto.com/posts/tags/lvr","domain":"a16zcrypto.com","chapter":"research","title":"LVR - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nLVR\n\nFeed\nFILTERS\n(1)\nclear filters\n\ncategories\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\n(1) recommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nclear all LVR\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n09.21.23 / Ciamac Moallemi\nAutomated market making and arbitrage profits in the presence of fees\nCiamac Moallemi reintroduces “loss-versus-rebalancing” (LVR), which quantifies the loss to arbitrageurs in an idealized, continuous-time setting with no fees.\n\nresearch\nDeFi\nLVR\nvideo\n\n10.28.22 / Anthony Lee Zhang\nArbitrage Extractable Value\nLiquidity Providers for Automated Market Makers suffer from “impermanent loss” – yet no definition of impermanent loss exists that allows it to be quantified.\n\nresearch\nAMMs\nDeFi\nLVR\nvideo\n\n10.28.22 / Ciamac Moallemi\nLiquidity Provision and Automated Market Making\nAn introduction to constant function market makers (CFMMs), which have emerged as the dominant mechanism for decentralized exchange on blockchains.\n\nresearch\nAMMs\nDeFi\nLVR\nvideo\n\n09.18.22 / Jason Milionis, Ciamac Moallemi, Tim Roughgarden and Anthony Lee Zhang\nLVR: Quantifying the Cost of Providing Liquidity to Automated Market Makers\nWe explain a new way to think about the cost side of becoming a liquidity partner, based on a quantity called LVR (“loss versus rebalancing,” pronounced “lever”).\n\nresearch\nAMMs\nDeFi\nLVR\npricing\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":1045,"crawled_at":1791194351315}
+{"id":10370,"url":"https://docs.compound.xyz/helper-functions","domain":"docs.compound.xyz","chapter":"defi_protocols","title":"Compound III Docs | Helper Functions","text":"Compound III\nInterest Rates\nCollateral & Borrowing\nLiquidation\nAccount Management\nProtocol Rewards\nERC-4626 Wrapper\nGovernance\nHelper Functions\n\nHelper Functions\nTotal Supply\nTotal Borrow\nTotal Collateral\nSupplied Base Balance\nBorrow Balance\nAccount Data\nGet Asset Info\nGet Asset Info By Address\nGet Price\nAccrue Account\nGet Protocol Configuration\nGet Comet Factory\nGet Base Asset Market Information\nGet Base Accrual Scale\nGet Base Index Scale\nGet Factor Scale\nGet Price Scale\nGet Max Assets\nBulk Actions\nInvoke\n\nHelper Functions\nTotal Supply\nThe total supply of base tokens supplied to the protocol plus interest accrued to suppliers.\nComet\nfunction totalSupply() override external view returns (uint256)\n\nRETURN: The amount of base asset scaled up by 10 to the “decimals” integer in the base asset’s contract.\nSolidity\nComet comet = Comet(0xCometAddress);\nuint256 totalSupply = comet.totalSupply();\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst totalSupply = await comet.callStatic.totalSupply();\n\nTotal Borrow\nThe total amount of base tokens that are currently borrowed from the protocol plus interest accrued to all borrows.\nComet\nfunction totalBorrow() virtual external view returns (uint256)\n\nRETURN: The amount of base asset scaled up by 10 to the “decimals” integer in the base asset’s contract.\nSolidity\nComet comet = Comet(0xCometAddress);\nuint256 totalBorrow = comet.totalBorrow();\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst totalBorrow = await comet.callStatic.totalBorrow();\n\nTotal Collateral\nThe protocol tracks the current amount of collateral that all accounts have supplied. Each valid collateral asset sum is tracked in a mapping with the asset address that points to a struct.\nComet\nstruct TotalsCollateral {\nuint128 totalSupplyAsset;\nuint128 _reserved;\n}\n\nmapping(address => TotalsCollateral) public totalsCollateral;\n\naddress: The address of the collateral asset’s contract.\nRETURN: A struct containing the stored data pertaining to the sum of the collateral in the protocol.\ntotalSupplyAsset: A Solidity uint128 of the sum of the collateral asset stored in the protocol, scaled up by 10 to the “decimals” integer in the asset’s contract.\nSolidity\nComet comet = Comet(0xCometAddress);\nTotalsCollateral totalsCollateral = comet.totalsCollateral(0xERC20Address);\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst [ totalSupplyAsset ] = await comet.callStatic.totalsCollateral('0xERC20Address');\n\nSupplied Base Balance\nThis function returns the current balance of base asset for a specified account in the protocol, including interest. If the account is presently borrowing or not supplying, it will return 0.\nComet\nfunction balanceOf(address account) external view returns (uint256)\n\naccount: The address of the account in which to retrieve the base asset balance.\nRETURNS: The balance of the base asset, including interest, in the protocol for the specified account as an unsigned integer scaled up by 10 to the “decimals” integer in the asset’s contract.\nSolidity\nComet comet = Comet(0xCometAddress);\nuint balance = comet.balanceOf(0xAccount);\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst balance = await comet.callStatic.balanceOf('0xAccount');\n\nBorrow Balance\nThis function returns the current balance of borrowed base asset for a specified account in the protocol, including interest. If the account has a non-negative base asset balance, it will return 0.\nComet\nfunction borrowBalanceOf(address account) external view returns (uint256)\n\naccount: The address of the account in which to retrieve the borrowed base asset balance.\nRETURNS: The balance of the base asset, including interest, borrowed by the specified account as an unsigned integer scaled up by 10 to the “decimals” integer in the asset’s contract.\nSolidity\nComet comet = Comet(0xCometAddress);\nuint owed = comet.borrowBalanceOf(0xAccount);\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst owed = await comet.callStatic.borrowBalanceOf('0xAccount');\n\nAccount Data\nThe protocol tracks data like the principal and indexes for each account that supplies and borrows. The data is stored in a mapping with the account address that points to a struct.\nComet\nstruct UserBasic {\nint104 principal;\nuint64 baseTrackingIndex;\nuint64 baseTrackingAccrued;\nuint16 assetsIn;\n}\n\nmapping(address => UserBasic) public userBasic;\n\naddress: The address of the account that has used the protocol.\nRETURN: A struct containing the stored data pertaining to the account.\nprincipal: A Solidity int104 of the amount of base asset that the account has supplied (greater than zero) or owes (less than zero) to the protocol.\nbaseTrackingIndex: A Solidity uint64 of the index of the account.\nbaseTrackingAccrued: A Solidity uint64 of the interest that the account has accrued.\nassetsIn: A Solidity uint16 that tracks which assets the account has supplied as collateral. This storage implementation is for internal purposes and enables gas savings.\nSolidity\nComet comet = Comet(0xCometAddress);\nUserBasic userBasic = comet.userBasic(0xAccount);\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst [ principal, baseTrackingIndex, baseTrackingAccrued, assetsIn ] = await comet.callStatic.userBasic('0xAccount');\n\nGet Asset Info\nThis function returns collateral asset information such as the collateral factors, asset price feed address, and more. In order to create a loop to fetch information for every asset, use the numAssets constant, which indicates the current total number of supported collateral assets.\nComet\nstruct AssetInfo {\nuint8 offset;\naddress asset;\naddress priceFeed;\nuint64 scale;\nuint64 borrowCollateralFactor;\nuint64 liquidateCollateralFactor;\nuint64 liquidationFactor;\nuint128 supplyCap;\n}\n\nfunction getAssetInfo(uint8 i) public view returns (AssetInfo memory)\n\ni: The index of the collateral asset based on the order it was added to the protocol. The index begins at 0.\nRETURNS: The collateral asset information as a struct called AssetInfo.\noffset: The index of the collateral asset based on the order it was added to the protocol.\nasset: The address of the asset’s smart contract.\npriceFeed: The address of the price feed contract for this collateral asset.\nscale: An integer that equals 10 ^ x where x is the amount of decimal places in the collateral asset’s smart contract.\nborrowCollateralFactor: The borrow collateral factor is the percentage of collateral value that can be borrowed (including interest) by an account. The return value is an integer that represents the decimal value scaled up by 10 ^ 18. E.g. 650000000000000000 is 65%.\nliquidateCollateralFactor: The liquidate collateral factor is the percentage of collateral value that can be borrowed (including interest) before an account becomes liquidatable. The return value is an integer that represents the decimal value scaled up by 10 ^ 18. E.g. 850000000000000000 is 85%.\nliquidationFactor: The liquidation factor as an integer that represents the decimal value scaled up by 10 ^ 18. E.g. 930000000000000000 means liquidation carries a 7% penalty for the account.\nsupplyCap: The supply cap of the collateral asset as an integer scaled up by 10 ^ x where x is the amount of decimal places in the asset’s smart contract.\nSolidity\nComet comet = Comet(0xCometAddress);\nAssetInfo info = comet.getAssetInfo(0);\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst infoObject = await comet.callStatic.getAssetInfo(0);\n\nGet Asset Info By Address\nThis function returns information of a specific collateral asset.\nComet\nstruct AssetInfo {\nuint8 offset;\naddress asset;\naddress priceFeed;\nuint64 scale;\nuint64 borrowCollateralFactor;\nuint64 liquidateCollateralFactor;\nuint64 liquidationFactor;\nuint128 supplyCap;\n}\n\nfunction getAssetInfoByAddress(address asset) public view returns (AssetInfo memory)\n\naddress: The address of the collateral asset.\nRETURNS: The collateral asset information as a struct called AssetInfo.\noffset: The index of the collateral asset based on the order it was added to the protocol.\nasset: The address of the collateral asset’s smart contract.\npriceFeed: The address of the price feed contract for this collateral asset.\nscale: An integer that equals 10 ^ x where x is the amount of decimal places in the collateral asset’s smart contract.\nborrowCollateralFactor: The borrow collateral factor is the percentage of collateral value that can be borrowed (including interest) by an account. The return value is an integer that represents the decimal value scaled up by 10 ^ 18. E.g. 650000000000000000 is 65%.\nliquidateCollateralFactor: The liquidate collateral factor is the percentage of collateral value that can be borrowed (including interest) before an account becomes liquidatable. The return value is an integer that represents the decimal value scaled up by 10 ^ 18. E.g. 850000000000000000 is 85%.\nliquidationFactor: The liquidation factor as an integer that represents the decimal value scaled up by 10 ^ 18. E.g. 930000000000000000 means liquidation carries a 7% penalty for the account.\nsupplyCap: The supply cap of the collateral asset as an integer scaled up by 10 ^ x where x is the amount of decimal places in the asset’s smart contract.\nSolidity\nComet comet = Comet(0xCometAddress);\nAssetInfo info = comet.getAssetInfoByAddress(0xAsset);\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst infoObject = await comet.callStatic.getAssetInfoByAddress('0xAsset');\n\nGet Price\nThe protocol’s prices are updated by Chainlink Price Feeds. In order to fetch the present price of an asset, the price feed contract address for that asset must be passed to the getPrice function.\nThis function returns the price of an asset in USD with 8 decimal places.\nComet\nfunction getPrice(address priceFeed) public view returns (uint128)\n\npriceFeed: The ERC-20 address of the Chainlink price feed contract for the asset.\nRETURNS: Returns the USD price with 8 decimal places as an unsigned integer scaled up by 10 ^ 8. E.g. 500000000000 means that the asset’s price is $5000 USD.\nSolidity\nComet comet = Comet(0xCometAddress);\nuint price = comet.getPrice(0xAssetAddress);\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst price = await comet.callStatic.getPrice(usdcAddress);\n\nAccrue Account\nThis function triggers a manual accrual of interest and rewards to an account.\nComet\nfunction accrueAccount(address account) override external\n\naccount: The account in which to accrue interest and rewards.\nRETURN: No return, reverts on error.\nSolidity\nComet comet = Comet(0xCometAddress);\ncomet.accrueAccount(0xAccount);\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nawait comet.accrueAccount('0xAccount');\n\nGet Protocol Configuration\nThis function returns the configuration struct stored for a specific instance of Comet in the configurator contract.\nConfigurator\nstruct Configuration {\naddress governor;\naddress pauseGuardian;\naddress baseToken;\naddress baseTokenPriceFeed;\naddress extensionDelegate;\n\nuint64 supplyKink;\nuint64 supplyPerYearInterestRateSlopeLow;\nuint64 supplyPerYearInterestRateSlopeHigh;\nuint64 supplyPerYearInterestRateBase;\nuint64 borrowKink;\nuint64 borrowPerYearInterestRateSlopeLow;\nuint64 borrowPerYearInterestRateSlopeHigh;\nuint64 borrowPerYearInterestRateBase;\nuint64 storeFrontPriceFactor;\nuint64 trackingIndexScale;\nuint64 baseTrackingSupplySpeed;\nuint64 baseTrackingBorrowSpeed;\nuint104 baseMinForRewards;\nuint104 baseBorrowMin;\nuint104 targetReserves;\n\nAssetConfig[] assetConfigs;\n}\n\nfunction getConfiguration(address cometProxy) external view returns (Configuration memory)\n\ncometProxy: The address of the Comet proxy to get the configuration for.\nRETURNS: Returns the protocol configuration. governor: The address of the protocol Governor.\npauseGuardian: The address of the protocol pause guardian.\nbaseToken: The address of the protocol base token smart contract.\nbaseTokenPriceFeed: The address of the protocol base token price feed smart contract.\nextensionDelegate: The address of the delegate of extra methods that did not fit in Comet.sol (CometExt.sol).\nsupplyKink: The interest rate utilization of the supply side of curve kink.\nsupplyPerYearInterestRateSlopeLow: The low bound interest rate slope of the supply side.\nsupplyPerYearInterestRateSlopeHigh: The high bound interest rate slope of the supply side.\nsupplyPerYearInterestRateBase: The interest rate slope base of the supply side.\nborrowKink: The interest rate utilization of the borrow side of curve kink.\nborrowPerYearInterestRateSlopeLow: The low bound interest rate slope of the borrow side.\nborrowPerYearInterestRateSlopeHigh: The high bound interest rate slope of the borrow side.\nborrowPerYearInterestRateBase: The interest rate slope base of the borrow side.\nstoreFrontPriceFactor: The fraction of the liquidation penalty that goes to buyers of collateral instead of the protocol.\ntrackingIndexScale: The scale for the index tracking protocol rewards.\nbaseTrackingSupplySpeed: The rate for protocol awards accrued to suppliers.\nbaseTrackingBorrowSpeed: The rate for protocol awards accrued to borrowers.\nbaseMinForRewards: The minimum amount of base asset supplied to the protocol in order for accounts to accrue rewards.\nbaseBorrowMin: The minimum allowed borrow size.\ntargetReserves: The amount of reserves allowed before absorbed collateral is no longer sold by the protocol.\nassetConfigs: An array of all supported asset configurations.\n\nSolidity\nConfigurator configurator = Configurator(0xConfiguratorAddress);\nConfiguration config = configurator.getConfiguration(0xCometProxy);\n\nEthers.js v5.x\nconst configurator = new ethers.Contract(contractAddress, abiJson, provider);\nconst config = await configurator.callStatic.getConfiguration('0xCometProxy');\n\nGet Comet Factory\nThis function gets the address of the Comet Factory contract.\nConfigurator\nfunction factory(address cometProxy) public view returns (address cometFactory)\n\ncometProxy: The address of the Comet proxy contract.\nRETURNS: The address of the Comet Factory for the specified instance of Comet.\nSolidity\nConfigurator configurator = Configurator(0xConfiguratorAddress);\nCometFactory factory = configurator.factory(0xCometProxy);\n\nEthers.js v5.x\nconst configurator = new ethers.Contract(contractAddress, abiJson, provider);\nconst factoryAddress = await configurator.factory.getConfiguration('0xCometProxy');\n\nGet Base Asset Market Information\nThis function gets several of the current parameter values for the protocol market.\nComet\nstruct TotalsBasic {\nuint64 baseSupplyIndex;\nuint64 baseBorrowIndex;\nuint64 trackingSupplyIndex;\nuint64 trackingBorrowIndex;\nuint104 totalSupplyBase;\nuint104 totalBorrowBase;\nuint40 lastAccrualTime;\nuint8 pauseFlags;\n}\n\nfunction totalsBasic() public override view returns (TotalsBasic memory)\n\nRETURNS: The base asset market information as a struct called TotalsBasic (defined in CometStorage.sol).\nbaseSupplyIndex: The global base asset supply index for calculating interest accrued to suppliers.\nbaseBorrowIndex: The global base asset borrow index for calculating interest owed by borrowers.\ntrackingSupplyIndex: A global index for tracking participation of accounts that supply the base asset.\ntrackingBorrowIndex: A global index for tracking participation of accounts that borrow the base asset.\ntotalSupplyBase: The total amount of base asset presently supplied to the protocol as an unsigned integer scaled up by 10 to the “decimals” integer in the base asset’s contract.\ntotalBorrowBase: The total amount of base asset presently borrowed from the protocol as an unsigned integer scaled up by 10 to the “decimals” integer in the base asset’s contract.\nlastAccrualTime: The most recent time that protocol interest accrual was globally calculated. A block timestamp as seconds since the Unix epoch.\npauseFlags: An integer that represents paused protocol functionality flags that are packed for data storage efficiency. See Pause Protocol Functionality.\nSolidity\nComet comet = Comet(0xCometAddress);\nTotalsBasic tb = comet.totalsBasic();\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst [ baseSupplyIndex, baseBorrowIndex, trackingSupplyIndex, trackingBorrowIndex, totalSupplyBase, totalBorrowBase, lastAccrualTime, pauseFlags ] = await comet.callStatic.totalsBasic();\n\nGet Base Accrual Scale\nThis function gets the scale for the base asset tracking accrual.\nComet\nfunction baseAccrualScale() override external pure returns (uint64)\n\nRETURNS: The integer used to scale down the base accrual when calculating a decimal value.\nSolidity\nComet comet = Comet(0xCometAddress);\nuint baseAccrualScale = comet.baseAccrualScale();\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst baseAccrualScale = await comet.callStatic.baseAccrualScale();\n\nGet Base Index Scale\nThis function gets the scale for the base asset index.\nComet\nfunction baseIndexScale() override external pure returns (uint64)\n\nRETURNS: The integer used to scale down the index when calculating a decimal value.\nSolidity\nComet comet = Comet(0xCometAddress);\nuint baseIndexScale = comet.baseIndexScale();\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst baseIndexScale = await comet.callStatic.baseIndexScale();\n\nGet Factor Scale\nThis function gets the scale for all protocol factors, i.e. borrow collateral factor.\nComet\nfunction factorScale() override external pure returns (uint64)\n\nRETURNS: The integer used to scale down the factor when calculating a decimal value.\nSolidity\nComet comet = Comet(0xCometAddress);\nuint factorScale = comet.factorScale();\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst factorScale = await comet.callStatic.factorScale();\n\nGet Price Scale\nThis function gets the scale integer for USD prices in the protocol, i.e. 8 decimals = 1e8.\nComet\nfunction priceScale() override external pure returns (uint64)\n\nRETURNS: The integer used to scale down a price when calculating a decimal value.\nSolidity\nComet comet = Comet(0xCometAddress);\nuint priceScale = comet.priceScale();\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst priceScale = await comet.callStatic.priceScale();\n\nGet Max Assets\nThis function gets the maximum number of assets that can be simultaneously supported by Compound III.\nComet\nfunction maxAssets() override external pure returns (uint8)\n\nRETURNS: The maximum number of assets that can be simultaneously supported by Compound III.\nSolidity\nComet comet = Comet(0xCometAddress);\nuint maxAssets = comet.maxAssets();\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst maxAssets = await comet.callStatic.maxAssets();\n\nBulk Actions\nThe Compound III codebase contains the source code of an external contract called Bulker that is designed to allow multiple Comet functions to be called in a single transaction.\nUse cases of the Bulker contract include but are not limited to:\nSupplying of a collateral asset and borrowing of the base asset.\nSupplying or withdrawing of the native EVM token (like Ether) directly.\nTransferring or withdrawing of the base asset without leaving dust in the account.\nInvoke\nThis function allows callers to pass an array of action codes and calldatas that are executed, one by one, in a single transaction.\nBulker\n/// @notice The action for supplying an asset to Comet\nbytes32 public constant ACTION_SUPPLY_ASSET = \"ACTION_SUPPLY_ASSET\";\n\n/// @notice The action for supplying a native asset (e.g. ETH on Ethereum mainnet) to Comet\nbytes32 public constant ACTION_SUPPLY_NATIVE_TOKEN = \"ACTION_SUPPLY_NATIVE_TOKEN\";\n\n/// @notice The action for transferring an asset within Comet\nbytes32 public constant ACTION_TRANSFER_ASSET = \"ACTION_TRANSFER_ASSET\";\n\n/// @notice The action for withdrawing an asset from Comet\nbytes32 public constant ACTION_WITHDRAW_ASSET = \"ACTION_WITHDRAW_ASSET\";\n\n/// @notice The action for withdrawing a native asset from Comet\nbytes32 public constant ACTION_WITHDRAW_NATIVE_TOKEN = \"ACTION_WITHDRAW_NATIVE_TOKEN\";\n\n/// @notice The action for claiming rewards from the Comet rewards contract\nbytes32 public constant ACTION_CLAIM_REWARD = \"ACTION_CLAIM_REWARD\";\n\nfunction invoke(bytes32[] calldata actions, bytes[] calldata data) external payable\n\nactions: An array of bytes32 strings that correspond to the actions defined in the contract.\ndata: An array of calldatas for each action to be called in the invoke transaction. Supply Asset, Withdraw Asset, Transfer Asset comet: The address of the Comet instance to interact with.\nto: The destination address, within or external to the protocol.\nasset: The address of the ERC-20 asset contract.\namount: The amount of the asset as an unsigned integer scaled up by 10 to the “decimals” integer in the asset’s contract.\n\nSupply Native, Withdraw Native (native chain token like ETH on Ethereum Mainnet) comet: The address of the Comet instance to interact with.\nto: The destination address, within or external to the protocol.\namount: The amount of the native token as an unsigned integer scaled up by 10 to the number of decimals of precision of the native EVM token.\n\nRETURN: No return, reverts on error.\nSolidity\nBulker bulker = Bulker(0xBulkerAddress);\n// ERC-20 `approve` the bulker. Then Comet `allow` the bulker to be a manager before calling `invoke`.\nbytes memory supplyAssetCalldata = (abi.encode('0xCometAddress', '0xAccount', '0xAsset', amount);\nbulker.invoke([ 'ACTION_SUPPLY_ASSET' ], [ supplyAssetCalldata ]);\n\nEthers.js v5.x\nconst bulker = new ethers.Contract(contractAddress, abiJson, provider);\n// ERC-20 `approve` the bulker. Then Comet `allow` the bulker to be a manager before calling `invoke`.\nconst supplyAssetCalldata = ethers.utils.defaultAbiCoder.encode(['address', 'address', 'address', 'uint'], ['0xCometAddress', '0xAccount', '0xAsset', amount]);\nawait bulker.invoke([ 'ACTION_SUPPLY_ASSET' ], [ supplyAssetCalldata ]);","tokens":5573,"crawled_at":1791194360941}
+{"id":10371,"url":"https://www.getfoundry.sh/anvil/state-management","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"State management – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nState management\n\nAnvil can save and restore chain state, enabling reproducible test scenarios and faster development workflows.\n\nDumping state\n\nSave the current state when Anvil exits:\n\nDump state on exit\n$ anvil --dump-state state.json\n\nDump to a directory\n$ anvil --dump-state ./states/\n\nLoading state\n\nStart from a previously saved state:\n\nLoad from state file\n$ anvil --load-state state.json\n\nThe anvil_dumpState and anvil_loadState RPC methods provide the same functionality on a running node, and anvil_reset restores a fresh chain; see the RPC method reference for parameters and examples.\n\nCombined state file\n\nUse --state to both load and dump from the same file:\n\nPersist state across restarts\n$ anvil --state state.json\n\nThis loads the state on startup (if the file exists) and saves it on exit.\n\nPeriodic snapshots\n\nSave state at regular intervals to prevent data loss:\n\nDump state every 60 seconds\n$ anvil --state state.json --state-interval 60\n\nHistorical states\n\nBy default, Anvil only keeps the latest state. Enable historical state preservation for debugging:\n\nPreserve historical states\n$ anvil --preserve-historical-states --dump-state state.json\n\nLimit persisted states\n$ anvil --max-persisted-states 100\n\nMemory management\n\nFor long-running instances, prune historical state to reduce memory usage:\n\nPrune history (keep 10 states)\n$ anvil --prune-history 10\n\nPrune all history\n$ anvil --prune-history\n\nGenesis configuration\n\nInitialize Anvil with a custom genesis file:\n\nUse custom genesis\n$ anvil --init genesis.json\n\nThe genesis file follows the standard Ethereum genesis format with alloc, difficulty, gasLimit, and other fields.\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":438,"crawled_at":1791194366649}
+{"id":10372,"url":"https://docs.sui.io/develop/objects/object-ownership/shared","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Shared Objects | Sui Documentation","text":"A shared object is a public, mutable objectObjectThe basic unit of storage on Sui. that any addressAddressA unique, anonymous identity on a blockchain network. on the network can reference in a transactionTransactionA number of commands that execute on inputs to define the result of the transaction.. Multiple users and smart contracts can interact with the same shared object concurrently. Shared objects go through consensusConsensusThe process by which the majority of nodes agree on the current state of the network ordering, which adds latency compared to address-owned objects but enables concurrent multi-party access.\n\nCreate shared objects​\n\nUse the sui::transfer::share_object function to create a shared object, making it publicly accessible on the network. Extended functionality and accessibility of shared objects requires additional effort by securing access, if needed.\n\nShared objects require the key ability.\n\npublic struct Donut has key { id: UID }\n\nfun init(ctx: &mut TxContext) {\ntransfer::transfer(ShopOwnerCap {\nid: object::new(ctx)\n}, ctx.sender());\n\ntransfer::share_object(DonutShop {\nid: object::new(ctx),\nprice: 1000,\nbalance: balance::zero()\n})\n}\n\nWhen to use shared objects​\n\nShared objects are ideal for things like marketplaces, games, or other scenarios where global state needs to be accessed or modified by multiple parties.\n\nInteract with shared objects​\n\nThe following example creates a shop to sell digital donuts. Everyone needs access to the shop to purchase donuts from it, so the example creates the shop as a shared object using sui::transfer::share_object.\n\nmodule examples::donuts;\n\nuse sui::sui::SUI;\nuse sui::coin::{Self, Coin};\nuse sui::balance::{Self, Balance};\n\n/// For when Coin balance is too low.\nconst ENotEnough: u64 = 0;\n\n/// Capability that grants an owner the right to collect profits.\npublic struct ShopOwnerCap has key { id: UID }\n\n/// A purchasable Donut. For simplicity's sake we ignore implementation.\npublic struct Donut has key { id: UID }\n\n/// A shared object. `key` ability is required.\npublic struct DonutShop has key {\nid: UID,\nprice: u64,\nbalance: Balance<SUI>\n}\n\n/// Init function is often ideal place for initializing\n/// a shared object as it is called only once.\nfun init(ctx: &mut TxContext) {\ntransfer::transfer(ShopOwnerCap {\nid: object::new(ctx)\n}, ctx.sender());\n\n// Share the object to make it accessible to everyone!\ntransfer::share_object(DonutShop {\nid: object::new(ctx),\nprice: 1000,\nbalance: balance::zero()\n})\n}\n\n/// Entry function available to everyone who owns a Coin.\npublic fun buy_donut(\nshop: &mut DonutShop, payment: &mut Coin<SUI>, ctx: &mut TxContext\n) {\nassert!(coin::value(payment) >= shop.price, ENotEnough);\n\n// Take amount = `shop.price` from Coin<SUI>\nlet paid = payment.balance_mut().split(shop.price);\n\n// Put the coin to the Shop's balance\nshop.balance.join(paid);\n\ntransfer::transfer(Donut {\nid: object::new(ctx)\n}, ctx.sender())\n}\n\n/// Consume donut and get nothing...\npublic fun eat_donut(d: Donut) {\nlet Donut { id } = d;\nid.delete();\n}\n\n/// Take coin from `DonutShop` and transfer it to tx sender.\n/// Requires authorization with `ShopOwnerCap`.\npublic fun collect_profits(\n_: &ShopOwnerCap, shop: &mut DonutShop, ctx: &mut TxContext\n) {\nlet amount = shop.balance.value();\nlet profits = shop.balance.split(amount).into_coin(ctx);\n\ntransfer::public_transfer(profits, ctx.sender())\n}\n\nSecurity considerations​\n\nAnyone can submit a transaction that references a shared object. The Sui runtime does not enforce access control on shared objects. Your MoveMoveAn open source programming language used for all activity on Sui. code must verify authorization for every privileged operation. Learn more in (Security Best Practices).\n\nPerformance considerations​\n\nTransactions that touch shared objects take longer to finalize than address-owned-object transactions because they require consensus.\n\nWhen many transactions write to the same shared object in the same checkpointCheckpointCreated after transaction execution to provide a certified record of chain history., they are sequenced rather than executed in parallel. This reduces throughput for that object. If your use case requires high write throughput, consider splitting state across multiple shared objects (for example, sharding an order book by price range) or using address-owned objects where possible.\n\nQuery shared objects offchain​\n\nYou can read shared objects offchain using the same methods as any other Sui object. Use the object's ID to query its current state:\n\nGraphQL RPCGraphQL RPCA lightweight GraphQL RPC service.: Use the object query with the shared object's ID. See the GraphQL RPC reference for the full schema.\n\ngRPCgRPC APIReplaces JSON-RPC on full nodes for data access.: Use the GetObject method. See the gRPC reference for details.\n\nEvent subscriptions: Subscribe to events emitted by the shared object to react to state changes in real time.\n\nWhen to use address-owned objects instead​\n\nPrefer address-owned objects over shared objects when:\n\nOnly one user needs to write to the object at a time.\n\nYou need the lowest possible transaction latency.\n\nYou want to avoid consensus overhead and potential contention.\n\nShared objects are the right choice when multiple parties must read and write the same mutable state. For read-only data that never changes, use immutable objects instead.\nRelated topics\n\nAddress-Owned Objects\nAddress-owned objects are owned by a Sui 32-byte address, which can either be an account address or an object ID. Learn how to create and access these objects.\nSecurity Best Practices\nOverview of security best practices on Sui.\nGraphQL for Sui RPC\nLearn the core concepts for working with GraphQL on Sui RPC, including request headers, query composition with variables and fragments, pagination strategies, query scope, service limits, and the components of the GraphQL and General-purpose Indexer stack.\ngRPC\nUse the Sui Full Node gRPC API for high-performance, type-safe blockchain data access with Protocol Buffers serialization.\n\nCreate shared objects\nWhen to use shared objects\nInteract with shared objects\nSecurity considerations\nPerformance considerations\nQuery shared objects offchain\nWhen to use address-owned objects instead\n\nWas this page helpful?","tokens":1568,"crawled_at":1791194372475}
+{"id":10373,"url":"https://a16zcrypto.com/posts/article/economic-analysis-safe-harbor-blockchain-applications-defi","domain":"a16zcrypto.com","chapter":"research","title":"An economic analysis of safe harbor for blockchain applications - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nAn economic analysis of safe harbor for blockchain applications\nMiles Jennings, Scott Walker, and Aiden Slavin\n04.07.26\n\nTags & Share Tags\nDeFi\npolicy & regulation\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nBringing traditional securities on-chain is a central focus of this Securities and Exchange Commission (SEC). Recognizing the potential of tokenization, the Commission under Chairman Atkins, launched Project Crypto 9 months ago with the aim of updating American securities rules and regulations. The goal is to enable the nation’s financial markets to move onchain, which allows for instant settlement, 24/7 markets, reduced costs, and more.\n\nBut to unleash the full potential of tokenized securities, innovators and investors need clear rules of the road for blockchain applications that allow users to transact in tokenized securities on a peer to peer basis, without intermediaries.\n\nSo we and DeFi Education Fund submitted a safe harbor proposal last August to the SEC outlining the criteria for when such blockchain-based applications — the neutral software programs that enable users to interact with public blockchain networks and smart contract protocols — should be excluded from registration requirements under the Securities Exchange Act of 1934. The approach outlines how such applications benefit market participants while advancing the Securities and Exchange Commission’s mission of protecting investors, maintaining fair, orderly, and efficient markets, and facilitating capital formation.\n\nToday, Vanderbilt Professor Craig Lewis — former SEC Chief Economist and Director of the Commission’s Division of Economic and Risk Analysis — submitted to the SEC his economic analysis of our safe harbor for software proposal. Lewis’ analysis focuses specifically on the proposal, but more broadly conveys the economic costs and benefits of tokenized securities — thus providing valuable insights about the potential of blockchain technology to revolutionize the legacy financial system. While a16z provided financial support for this work, Professor Lewis applied his own rigorous methodology in assessing how to measure the benefits and costs of the proposal.\n\nAs part of his analysis, Lewis identifies 5 benefits that the safe harbor could enable qualifying apps to unlock:\n\nAtomic settlement — which eliminates the counterparty credit risks associated with delayed settlement windows, and also mitigates the systemic danger of a central counterparty failure cascading throughout the broader market.\n\nOnchain transparency — which replaces opaque proprietary ledgers with a more publicly verifiable record of every transaction.\n\nContinuous 24/7 trading of tokenized securities — which expands price discovery and liquidity beyond the geographic and temporal limits of traditional exchange hours.\n\nConcrete direct cost reductions driven by smart contracts — which automate corporate actions like dividend payments and certain compliance functions. He points out that research from Ripple and BCG, for example, estimates that tokenizing an investment-grade bond could cut operating costs by 40 to 60% relative to traditional issuance.\n\nLower barriers to entry — which could result in new developers exerting competitive pressure on traditional finance institutions, forcing those intermediaries to innovate in a manner that ultimately benefits users.\n\nLewis also outlines these 4 potential costs of the safe harbor proposal:\n\nEroding investor protections. Lewis performs a side-by-side analysis of traditional broker-dealers and qualifying apps, concluding that the proposal’s narrow scope preserves investor protections by limiting eligibility to software that does not create the risks these regulations are designed to mitigate. However, Lewis flags certain novel risks; for example, while the broker-dealer regulatory framework enables intermediaries to freeze assets and reverse transactions as an investor protection mechanism, eligible apps — by design — do not possess this capacity.\n\nRegulatory arbitrage. Traditional broker-dealers could restructure themselves as qualifying apps to escape certain obligations. However, Lewis ultimately avers that the operational machinations required for a traditional intermediary to meet the proposal’s strict criteria would be prohibitive.\n\nTokenized securities. Expanding tokenized securities trading risks fragmenting the market and potential systemic spillovers, with leverage in DeFi protocols potentially transmitting stress to traditional markets. However, Lewis recommends benchmarking this risk against the dark pools and off-exchange venues that already fragment the traditional securities market today, and notes that decentralized market structures have consistently exhibited operational resiliency, even during periods of high volatility.\n\nDeFi trading costs for retail. Lewis points out that variable gas fees, price slippage, and smart contract code vulnerabilities are all real risks, but argues that a proper comparison must examine those relative to the embedded costs that already exist in traditional finance. He also notes that DeFi fees are declining sharply. In this regard, Lewis observes that Ethereum’s Dencun upgrade, for example, reduced the cost for L2s to post data to mainnet by over 90%.\n\nLewis observes more broadly in his analysis that “costs associated with DeFi trading are also expected to go down over time”, given specific technical developments. This is important because some cite costs and scaling limits as preventing DeFi from processing significant trading volumes today. However, those assumptions are often based on historical data, rather than on blockchain performance (including data availability) as tied to the current trajectory of technical developments.\n\nBeyond technical readiness, our safe harbor proposal is opt-in — essentially creating more options for how investors could access assets.\n\nFinally, Lewis’ analysis was scoped specifically to front-end applications that satisfy the safe harbor proposal’s eligibility criteria, emphasizing that applications meeting the following four criteria are passive software interfaces that, by design, do not create the risks the Exchange Act was built to address. Specifically, that they have:\n\nNon-custodial architecture\n\nNo discretionary trade execution\n\nNo solicitation or investment recommendations\n\nExclusive integration with genuinely decentralized protocols (with certain allowances for protocols pursuing decentralization in good faith)\n\nLewis further emphasizes that the relevant comparison is not between those blockchain apps and some idealized market structure, but between them and the existing broker-dealer system, with all its embedded and often invisible costs: DTC fees, clearing and settlement charges, intermediary markups, insurance buffers, and others.\n\nUltimately, Lewis concludes that: “Should the SEC conduct a formal economic analysis of these costs and benefits, it would likely find that the Safe Harbor would facilitate the realization of the significant economic benefits inherent to tokenized securities.”\n\n* * *\n\nTokenization “could transform the financial system as we know it”, as Chairman Atkins has observed — and the Commission has supported that vision with Project Crypto, landmark joint staff guidance, and more.\n\nBut realizing the full potential of tokenized securities also requires clear and effective rules for the blockchain applications that enable investors to transact in these assets on a peer to peer basis without intermediaries. This is what our safe harbor proposal aims to provide and, as Professor Lewis’ analysis confirms, the overall economic case for adopting it is compelling. There are tradeoffs, but the benefits should outweigh any costs.\n\nProfessor Lewis has drawn the map. We encourage the Commission to follow it.\n\nAcknowledgements: Thank you to Amanda Tuminelli, Bill Hinman, Michele Korver, David Sverdlov for their contributions to the original safe harbor proposal, and other helpful feedback.\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nYou should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investment-list/.\n\nThe content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures/ for additional important information.","tokens":2618,"crawled_at":1791194378259}
+{"id":10374,"url":"https://docs.compound.xyz/governance","domain":"docs.compound.xyz","chapter":"defi_protocols","title":"Compound III Docs | Governance","text":"Compound III\nInterest Rates\nCollateral & Borrowing\nLiquidation\nAccount Management\nProtocol Rewards\nERC-4626 Wrapper\nGovernance\nHelper Functions\n\nGovernance\nSet Comet Factory\nSet Governor\nSet Pause Guardian\nPause Protocol Functionality\nIs Supply Paused\nIs Transfer Paused\nIs Withdraw Paused\nIs Absorb Paused\nIs Buy Paused\nSet Base Token Price Feed\nSet Extension Delegate\nSet Borrow Kink\nSet Borrow Interest Rate Slope (Low)\nSet Borrow Interest Rate Slope (High)\nSet Borrow Interest Rate Slope (Base)\nSet Supply Kink\nSet Supply Interest Rate Slope (Low)\nSet Supply Interest Rate Slope (High)\nSet Supply Interest Rate Slope (Base)\nSet Store Front Price Factor\nSet Base Tracking Supply Speed\nSet Base Tracking Borrow Speed\nSet Base Minimum For Rewards\nSet Borrow Minimum\nSet Target Reserves\nAdd a New Asset\nUpdate an Existing Asset\nUpdate Asset Price Feed\nUpdate Borrow Collateral Factor\nUpdate Liquidation Collateral Factor\nUpdate Liquidation Factor\nSet Asset Supply Cap\nERC-20 Approve Manager Address\nTransfer Governor\nWithdraw Reserves\n\nGovernance\nCompound III is a decentralized protocol that is governed by holders and delegates of COMP. Governance allows the community to propose, vote, and implement changes through the administrative smart contract functions of the Compound III protocol. For more information on the Governor and Timelock see the original governance section.\nAll instances of Compound III are controlled by the Timelock contract which is the same administrator of the Compound v2 protocol. The governance system has control over each proxy, the Configurator implementation, the Comet factory, and the Comet implementation.\nEach time an immutable parameter is set via governance proposal, a new Comet implementation must be deployed by the Comet factory. If the proposal is approved by the community, the proxy will point to the new implementation upon execution.\nTo set specific protocol parameters in a proposal, the Timelock must call all of the relevant set methods on the Configurator contract, followed by deployAndUpgradeTo on the CometProxyAdmin contract.\nMulti-chain Governance\nThe Compound III protocol can be deployed on any EVM chain. The deployment must have access to on-chain asset prices and governance messages passed from Ethereum Mainnet. The Timelock on Mainnet is the administrator of all community sanctioned instances of Compound III.\nEach deployment outside of Mainnet needs to have a Bridge Receiver and Local Timelock contract on its chain. Governance proposals executed on Mainnet must be read by the chain’s bridge and published to the Bridge Receiver. Local Timelocks have an additional delay before Comet admin functions can be called via proposal execution.\nCompound III instance initializations are logged on-chain using the ENS text record system. The text record can only be modified by a Governance proposal. It can be viewed at v3-additional-grants.compound-community-licenses.eth when the browser network is set to Ethereum Mainnet.\nSet Comet Factory\nThis function sets the official contract address of the Comet factory. The only acceptable caller is the Governor.\nConfigurator\nfunction setFactory(address cometProxy, address newFactory) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nnewFactory: The address of the new Comet contract factory.\nRETURN: No return, reverts on error.\nSet Governor\nThis function sets the official contract address of the Compound III protocol Governor for subsequent proposals.\nConfigurator\nfunction setGovernor(address cometProxy, address newGovernor) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nnewGovernor: The address of the new Compound III Governor.\nRETURN: No return, reverts on error.\nSet Pause Guardian\nThis function sets the official contract address of the Compound III protocol pause guardian. This address has the power to pause supply, transfer, withdraw, absorb, and buy collateral operations within Compound III.\nCOMP token-holders designate the Pause Guardian address, which is held by the Community Multi-Sig.\nConfigurator\nfunction setPauseGuardian(address cometProxy, address newPauseGuardian) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nnewPauseGuardian: The address of the new pause guardian.\nRETURN: No return, reverts on error.\nPause Protocol Functionality\nThis function pauses the specified protocol functionality in the event of an unforeseen vulnerability. The only addresses that are allowed to call this function are the Governor and the Pause Guardian.\nComet\nfunction pause(\nbool supplyPaused,\nbool transferPaused,\nbool withdrawPaused,\nbool absorbPaused,\nbool buyPaused\n) override external\n\nsupplyPaused: Enables or disables all accounts’ ability to supply assets to the protocol.\ntransferPaused: Enables or disables all account’s ability to transfer assets within the protocol.\nwithdrawPaused: Enables or disables all account’s ability to withdraw assets from the protocol.\nabsorbPaused: Enables or disables protocol absorptions.\nbuyPaused: Enables or disables the protocol’s ability to sell absorbed collateral.\nRETURN: No return, reverts on error.\nIs Supply Paused\nThis function returns a boolean indicating whether or not the protocol supply functionality is presently paused.\nComet\nfunction isSupplyPaused() override public view returns (bool)\n\nRETURN: A boolean value of whether or not the protocol functionality is presently paused.\nIs Transfer Paused\nThis function returns a boolean indicating whether or not the protocol transfer functionality is presently paused.\nComet\nfunction isTransferPaused() override public view returns (bool)\n\nRETURN: A boolean value of whether or not the protocol functionality is presently paused.\nIs Withdraw Paused\nThis function returns a boolean indicating whether or not the protocol withdraw functionality is presently paused.\nComet\nfunction isWithdrawPaused() override public view returns (bool)\n\nRETURN: A boolean value of whether or not the protocol functionality is presently paused.\nIs Absorb Paused\nThis function returns a boolean indicating whether or not the protocol absorb functionality is presently paused.\nComet\nfunction isAbsorbPaused() override public view returns (bool)\n\nRETURN: A boolean value of whether or not the protocol functionality is presently paused.\nIs Buy Paused\nThis function returns a boolean indicating whether or not the protocol’s selling of absorbed collateral functionality is presently paused.\nComet\nfunction isBuyPaused() override public view returns (bool)\n\nRETURN: A boolean value of whether or not the protocol functionality is presently paused.\nSet Base Token Price Feed\nThis function sets the official contract address of the price feed of the protocol base asset.\nConfigurator\nfunction setBaseTokenPriceFeed(address cometProxy, address newBaseTokenPriceFeed) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nnewBaseTokenPriceFeed: The address of the new price feed contract.\nRETURN: No return, reverts on error.\nSet Extension Delegate\nThis function sets the official contract address of the protocol’s Comet extension delegate. The methods in CometExt.sol are able to be called via the same proxy as Comet.sol.\nConfigurator\nfunction setExtensionDelegate(address cometProxy, address newExtensionDelegate) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nnewExtensionDelegate: The address of the new extension delegate contract.\nRETURN: No return, reverts on error.\nSet Borrow Kink\nThis function sets the borrow interest rate utilization curve kink for the Compound III base asset.\nConfigurator\nfunction setBorrowKink(address cometProxy, uint64 newKink) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nnewKink: The new kink parameter.\nRETURN: No return, reverts on error.\nSet Borrow Interest Rate Slope (Low)\nThis function sets the borrow interest rate slope low bound in the approximate amount of seconds in one year.\nConfigurator\nfunction setBorrowPerYearInterestRateSlopeLow(address cometProxy, uint64 newSlope) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nnewSlope: The slope low bound as an unsigned integer.\nRETURN: No return, reverts on error.\nSet Borrow Interest Rate Slope (High)\nThis function sets the borrow interest rate slope high bound in the approximate amount of seconds in one year.\nConfigurator\nfunction setBorrowPerYearInterestRateSlopeHigh(address cometProxy, uint64 newSlope) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nnewSlope: The slope high bound as an unsigned integer.\nRETURN: No return, reverts on error.\nSet Borrow Interest Rate Slope (Base)\nThis function sets the borrow interest rate slope base in the approximate amount of seconds in one year.\nConfigurator\nfunction setBorrowPerYearInterestRateBase(address cometProxy, uint64 newBase) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nnewSlope: The slope base as an unsigned integer.\nRETURN: No return, reverts on error.\nSet Supply Kink\nThis function sets the supply interest rate utilization curve kink for the Compound III base asset.\nConfigurator\nfunction setSupplyKink(address cometProxy, uint64 newKink) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nnewKink: The new kink parameter.\nRETURN: No return, reverts on error.\nSet Supply Interest Rate Slope (Low)\nThis function sets the supply interest rate slope low bound in the approximate amount of seconds in one year.\nConfigurator\nfunction setSupplyPerYearInterestRateSlopeLow(address cometProxy, uint64 newSlope) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nnewSlope: The slope low bound as an unsigned integer.\nRETURN: No return, reverts on error.\nSet Supply Interest Rate Slope (High)\nThis function sets the supply interest rate slope high bound in the approximate amount of seconds in one year.\nConfigurator\nfunction setSupplyPerYearInterestRateSlopeHigh(address cometProxy, uint64 newSlope) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nnewSlope: The slope high bound as an unsigned integer.\nRETURN: No return, reverts on error.\nSet Supply Interest Rate Slope (Base)\nThis function sets the supply interest rate slope base in the approximate amount of seconds in one year.\nConfigurator\nfunction setSupplyPerYearInterestRateBase(address cometProxy, uint64 newBase) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nnewSlope: The slope base as an unsigned integer.\nRETURN: No return, reverts on error.\nSet Store Front Price Factor\nThis function sets the fraction of the liquidation penalty that goes to buyers of collateral instead of the protocol. This factor is used to calculate the discount rate of collateral for sale as part of the account absorption process. The rate is a decimal scaled up by 10 ^ 18.\nConfigurator\nfunction setStoreFrontPriceFactor(address cometProxy, uint64 newStoreFrontPriceFactor) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nnewStoreFrontPriceFactor: The new price factor as an unsigned integer expressed as a decimal scaled up by 10 ^ 18.\nRETURN: No return, reverts on error.\nSet Base Tracking Supply Speed\nThis function sets the rate at which base asset supplier accounts accrue rewards.\nConfigurator\nfunction setBaseTrackingSupplySpeed(address cometProxy, uint64 newBaseTrackingSupplySpeed) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nnewBaseTrackingSupplySpeed: The rate as an APR expressed as a decimal scaled up by 10 ^ 18.\nRETURN: No return, reverts on error.\nSet Base Tracking Borrow Speed\nThis function sets the rate at which base asset borrower accounts accrue rewards.\nConfigurator\nfunction setBaseTrackingBorrowSpeed(address cometProxy, uint64 newBaseTrackingBorrowSpeed) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nnewBaseTrackingBorrowSpeed: The rate as an APR expressed as a decimal scaled up by 10 ^ 18.\nRETURN: No return, reverts on error.\nSet Base Minimum For Rewards\nThis function sets the minimum amount of base asset supplied to the protocol in order for accounts to accrue rewards.\nConfigurator\nfunction setBaseMinForRewards(address cometProxy, uint104 newBaseMinForRewards) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nnewBaseMinForRewards: The amount of base asset scaled up by 10 to the “decimals” integer in the base asset’s contract.\nRETURN: No return, reverts on error.\nSet Borrow Minimum\nThis function sets the minimum amount of base token that is allowed to be borrowed.\nConfigurator\nfunction setBaseBorrowMin(address cometProxy, uint104 newBaseBorrowMin) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nsetBaseBorrowMin: The minimum borrow as an unsigned integer scaled up by 10 to the “decimals” integer in the base asset’s contract.\nRETURN: No return, reverts on error.\nSet Target Reserves\nThis function sets the target reserves amount. Once the protocol reaches this amount of reserves of base asset, liquidators cannot buy collateral from the protocol.\nConfigurator\nfunction setTargetReserves(address cometProxy, uint104 newTargetReserves) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nnewTargetReserves: The amount of reserves of base asset as an unsigned integer scaled up by 10 to the “decimals” integer in the base asset’s contract.\nRETURN: No return, reverts on error.\nAdd a New Asset\nThis function adds an asset to the protocol through governance.\nConfigurator\nfunction addAsset(address cometProxy, AssetConfig calldata assetConfig) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nassetConfig: The configuration that is added to the array of protocol asset configurations.\nRETURN: No return, reverts on error.\nUpdate an Existing Asset\nThis function modifies an existing asset’s configuration parameters.\nConfigurator\nfunction updateAsset(address cometProxy, AssetConfig calldata newAssetConfig) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nnewAssetConfig: The configuration that is modified in the array of protocol asset configurations. All parameters are overwritten.\nRETURN: No return, reverts on error.\nUpdate Asset Price Feed\nThis function updates the price feed contract address for a specific asset.\nConfigurator\nfunction updateAssetPriceFeed(address cometProxy, address asset, address newPriceFeed) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nasset: The address of the underlying asset smart contract.\nnewPriceFeed: The address of the new price feed smart contract.\nRETURN: No return, reverts on error.\nUpdate Borrow Collateral Factor\nThis function updates the borrow collateral factor for an asset in the protocol.\nConfigurator\nfunction updateAssetBorrowCollateralFactor(address cometProxy, address asset, uint64 newBorrowCF) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nasset: The address of the underlying asset smart contract.\nnewBorrowCF: The collateral factor as an integer that represents the decimal value scaled up by 10 ^ 18.\nRETURN: No return, reverts on error.\nUpdate Liquidation Collateral Factor\nThis function updates the liquidation collateral factor for an asset in the protocol.\nConfigurator\nfunction updateAssetLiquidateCollateralFactor(address cometProxy, address asset, uint64 newLiquidateCF) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nasset: The address of the underlying asset smart contract.\nnewLiquidateCF: The collateral factor as an integer that represents the decimal value scaled up by 10 ^ 18.\nRETURN: No return, reverts on error.\nUpdate Liquidation Factor\nThis function updates the liquidation factor for an asset in the protocol.\nThe liquidation factor is a decimal value that is between 0 and 1 (inclusive) which determines the amount that is paid out to an underwater account upon liquidation.\nThe following is an example of the liquidation factor’s role in a Compound III liquidation:\nAn underwater account has supplied $100 of WBTC as collateral. If the WBTC liquidation factor is 0.9, the user will receive $90 of the base asset when a liquidator triggers an absorption of their account.\nConfigurator\nfunction updateAssetLiquidationFactor(address cometProxy, address asset, uint64 newLiquidationFactor) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nasset: The address of the underlying asset smart contract.\nnewLiquidationFactor: The factor as an integer that represents the decimal value scaled up by 10 ^ 18.\nRETURN: No return, reverts on error.\nSet Asset Supply Cap\nThis function sets the maximum amount of an asset that can be supplied to the protocol. Supply transactions will revert if the total supply would be greater than this number as a result.\nConfigurator\nfunction updateAssetSupplyCap(address cometProxy, address asset, uint128 newSupplyCap) external\n\ncometProxy: The address of the Comet proxy to set the configuration for.\nasset: The address of the underlying asset smart contract.\nnewSupplyCap: The amount of the asset as an unsigned integer scaled up by 10 to the “decimals” integer in the asset’s contract.\nRETURN: No return, reverts on error.\nERC-20 Approve Manager Address\nThis function sets the Comet contract’s ERC-20 allowance of an asset for a manager address. It can only be called by the Governor.\nIn the event of a governance attack, an attacker could create a proposal that leverages this function to give themselves permissions to freely transfer all ERC-20 tokens out of the Comet contract.\nHypothetically, the attacker would need to either acquire supreme voting weight or add a malicious step in an otherwise innocuous and popular proposal and the community would fail to detect before approving.\nComet\nfunction approveThis(address manager, address asset, uint amount) override external\n\nmanager: The address of a manager account that has its allowance modified.\nasset: The address of the asset’s smart contract.\namount: The amount of the asset approved for the manager expressed as an integer.\nRETURN: No return, reverts on error.\nTransfer Governor\nThis function changes the address of the Configurator’s Governor.\nConfigurator\nfunction transferGovernor(address newGovernor) external\n\nnewGovernor: The address of the new Governor for Configurator.\nRETURN: No return, reverts on error.\nWithdraw Reserves\nThis function allows governance to withdraw base token reserves from the protocol and send them to a specified address. Only the Governor address may call this function.\nComet\nfunction withdrawReserves(address to, uint amount) external\n\nto: The address of the recipient of the base asset tokens.\namount: The amount of the base asset to send scaled up by 10 to the “decimals” integer in the base asset’s contract.\nRETURN: No return, reverts on error.","tokens":4791,"crawled_at":1791194379495}
+{"id":10375,"url":"https://docs.sui.io/references","domain":"docs.sui.io","chapter":"layer1_layer2","title":"References | Sui Documentation","text":"Reference documentation for the Sui platform, including API specifications (gRPCgRPC APIReplaces JSON-RPC on full nodes for data access., GraphQL), CLI commands, MoveMoveAn open source programming language used for all activity on Sui. framework modulesModuleA component of a Move package that defines interaction with on-chain objects., SDK guides, and IDE tooling.\n\nWhat does Sui reference documentation cover?​\n\nSui reference documentation covers the low-level details you need when building on Sui. Use these references to look up exact method signatures, CLI flags, Move module definitions, and API schemas without reading through conceptual guides.\n\nThe reference documentation includes:\n\nAPI specifications: gRPC and GraphQL RPCGraphQL RPCA lightweight GraphQL RPC service. schemas for querying chain state, submitting transactions, and subscribing to events.\n\nCLI commands: Full flag and argument listings for the Sui CLI, including client, keytool, move, and validator subcommands.\n\nMove framework modules: Module-level documentation for the Sui Move framework, including types, functions, and constants defined in sui-framework and move-stdlib.\n\nSDKs: GitHub repos for the Sui TypeScript SDK, Rust SDK, and Sui dApp Kit.\n\nIDE tooling: Setup and configuration details for Move language support in editors such as VS Code.\n\nHow to use these references​\n\nFind the section that matches your current task and go directly to the relevant entry.\n\nFor example, if you want to query owned objects for an addressAddressA unique, anonymous identity on a blockchain network. using the GraphQL RPC, you look up the address query in the GraphQL reference, check the available fields on the ObjectConnection type, and construct your query:\n\nquery {\naddress(address: \"0xYOUR_ADDRESS\") {\nobjects {\nnodes {\nobjectId\ndigest\ntype {\nrepr\n}\n}\n}\n}\n}\n\nIf you want to publish a Move packagePackageSmart contracts on Sui. from the CLI, you look up the client publish command to confirm required flags:\n\nsui client publish --gas-budget 100000000\n\nWhich reference should you use?​\n\nThe right reference depends on how your application interacts with Sui:\n\nUse the GraphQL RPC reference when querying historical or current chain state from a frontend or backend service.\n\nUse the CLI reference when scripting deployments, managing keys, or running administrative commands.\n\nUse the Move framework reference when writing smart contracts and looking up built-in types or functions.\n\nUse the SDK reference when integrating Sui into a TypeScript or Rust application.\n\nReferences\nReference documentation for the Sui platform, including API specifications (gRPC, GraphQL), CLI commands, Move framework modules, SDK guides, and IDE tooling.\n→\nSui RPC\nIn this section\nGraphQL\ngRPC\nRPC Best Practices\nLegacy (to be archived)\n\n→\nSui CLI\nIn this section\nSui CLI Cheat Sheet\nSui Client CLI\nSui Client PTB CLI\nSui CLI Completions\nSui Keytool CLI\nSui External Signers CLI\n+ 4 more\n\n→\nSui IDE Support\nIn this section\nMove Analyzer\nMove Trace Debugger\n\n→\nSui SDKs\nIn this section\nSDK Comparison\nTypeScript SDK v1 -> v2 Migration Guide\ndApp Kit\nRust SDK\nLegacy Rust SDK\nTypeScript SDK\n+ 1 more\n\n→\nMove\nIn this section\nFramework\nPackages\nThe Move Book\nThe Move Reference\n\n→\nPTB Commands\nReference for all PTB commands — TransferObjects, SplitCoins, MergeCoins, MakeMoveVec, MoveCall, Publish, and Upgrade — including each command's form, arguments, return type, and conceptual Move signature.\n→\nObject Display V2 Syntax\nLearn how to use Display V2 format strings to render Sui Move object values into human-readable strings, JSON, or encoded representations.\n→\nRelease Notes\nReview what changed in each Sui release, including protocol upgrades, framework changes, GraphQL updates, and indexing improvements.\n→\nGlossary\nLearn about terminology specific to Sui.\n→\nOpen Zeppelin: Access Library\n↗\nOpen Zeppelin: Math Library\n↗\nAwesome Sui\nA curated list of awesome developer tools and infrastructure projects within the Sui ecosystem.\n→\nAwesome Sui Gaming\nA curated list of awesome gaming projects and developer tools within the Sui ecosystem.\n→\nGaming on Sui\nSui offers features like dynamic NFTs, Kiosk, soulbound assets, and onchain randomness to provide builders with the tools to create immersive, transparent, and fair gaming experiences.\n→\nContribute\nIn this section\nSui Environment Setup\nContribute to Sui Repositories\nSubmit a SIP\nCode of Conduct\nStyle Guide\nMDX Components\n+ 1 more\n\n→\n\nWhat does Sui reference documentation cover?\nHow to use these references\nWhich reference should you use?\n\nWas this page helpful?","tokens":1146,"crawled_at":1791194393447}
+{"id":10376,"url":"https://docs.compound.xyz/liquidation","domain":"docs.compound.xyz","chapter":"defi_protocols","title":"Compound III Docs | Liquidation","text":"Compound III\nInterest Rates\nCollateral & Borrowing\nLiquidation\nAccount Management\nProtocol Rewards\nERC-4626 Wrapper\nGovernance\nHelper Functions\n\nLiquidation\nLiquidatable Accounts\nAbsorb\nBuy Collateral\nAsk Price\nLiquidator Points\nProtocol Reserves\nTarget Reserves\n\nLiquidation\nLiquidation is determined by liquidation collateral factors, which are separate and higher than borrow collateral factors (used to determine initial borrowing capacity), which protects borrowers & the protocol by ensuring a price buffer for all new positions. These also enable governance to reduce borrow collateral factors without triggering the liquidation of existing positions.\nWhen an account’s borrow balance exceeds the limits set by liquidation collateral factors, it is eligible for liquidation. A liquidator (a bot, contract, or user) can call the absorb function, which relinquishes ownership of the accounts collateral, and returns the value of the collateral, minus a penalty (liquidationFactor), to the user in the base asset. The liquidated user has no remaining debt, and typically, will have an excess (interest earning) balance of the base asset.\nEach absorption is paid for by the protocol’s reserves of the base asset. In return, the protocol receives the collateral assets. If the remaining reserves are less than a governance-set target, liquidators are able to buy the collateral at a discount using the base asset, which increases the protocol’s base asset reserves.\nLiquidatable Accounts\nThis function returns true if the account passed to it has negative liquidity based on the liquidation collateral factor. A return value of true indicates that the account is presently liquidatable.\nComet\nfunction isLiquidatable(address account) public view returns (bool)\n\naccount: The account to examine liquidatability.\nRETURNS: Returns true if the account is presently able to be liquidated.\nSolidity\nComet comet = Comet(0xCometAddress);\nbool isLiquidatable = comet.isLiquidatable(0xAccount);\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst isLiquidatable = await comet.callStatic.isLiquidatable('0xAccount');\n\nAbsorb\nThis function can be called by any address to liquidate an underwater account. It transfers the account’s debt to the protocol account, decreases cash reserves to repay the account’s borrows, and adds the collateral to the protocol’s own balance. The caller has the amount of gas spent noted. In the future, they could be compensated via governance.\nComet\nfunction absorb(address absorber, address[] calldata accounts)\n\nabsorber: The account that is issued liquidator points during successful execution.\naccounts: An array of underwater accounts that are to be liquidated.\nRETURN: No return, reverts on error.\nSolidity\nComet comet = Comet(0xCometAddress);\ncomet.absorb(0xMyAddress, [ 0xUnderwaterAddress ]);\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nawait comet.absorb('0xMyAddress', [ '0xUnderwaterAddress' ]);\n\nBuy Collateral\nThis function allows any account to buy collateral from the protocol, at a discount from the Price Feed’s price, using base tokens. A minimum collateral amount should be specified to indicate the maximum slippage acceptable for the buyer.\nThis function can be used after an account has been liquidated and there is collateral available to be purchased. Doing so increases protocol reserves. The amount of collateral available can be found by calling the Collateral Balance function. The price of the collateral can be determined by using the quoteCollateral function.\nComet\nfunction buyCollateral(address asset, uint minAmount, uint baseAmount, address recipient) external\n\nasset: The address of the collateral asset.\nminAmount: The minimum amount of collateral tokens that are to be received by the buyer, scaled up by 10 to the “decimals” integer in the collateral asset’s contract.\nbaseAmount: The amount of base tokens used to buy collateral scaled up by 10 to the “decimals” integer in the base asset’s contract.\nrecipient: The address that receives the purchased collateral.\nRETURN: No return, reverts on error.\nSolidity\nComet comet = Comet(0xCometAddress);\ncomet.buyCollateral(0xAssetAddress, 5e18, 5e18, 0xRecipient);\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nawait comet.buyCollateral('0xAssetAddress', 5e18, 5e18, '0xRecipient');\n\nAsk Price\nIn order to repay the borrows of absorbed accounts, the protocol needs to sell the seized collateral. The Ask Price is the price of the asset to be sold at a discount (configured by governance). This function uses the price returned by the protocol’s price feed. The discount of the asset is derived from the StoreFrontPriceFactor and the asset’s LiquidationFactor using the following formula.\nDiscountFactor = StoreFrontPriceFactor * (1e18 - Asset.LiquidationFactor)\n\nComet\nfunction quoteCollateral(address asset, uint baseAmount) public view returns (uint)\n\naddress: The address of the asset which is being quoted.\namount: The amount of the base asset used to purchase discounted collateral, as an integer, scaled up by 10 to the “decimals” integer in the base asset’s contract.\nRETURN: The amount of collateral asset that can be purchased using the base asset, as an integer, scaled up by 10 to the “decimals” integer in the collateral asset’s contract.\nSolidity\nComet comet = Comet(0xCometAddress);\nuint askPrice = comet.quoteCollateral(0xERC20Address, 10000000000);\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst askPrice = await comet.callStatic.quoteCollateral('0xERC20Address', 1000000);\n\nLiquidator Points\nThe protocol keeps track of the successful executions of absorb by tallying liquidator “points” and gas the liquidator has spent.\nComet\nmapping(address => LiquidatorPoints) public liquidatorPoints;\n\naddress: The address of the liquidator account.\nRETURN: A struct containing the stored data pertaining to the liquidator account.\nnumAbsorbs: A Solidity uint32 of the number of times absorb was successfully called.\nnumAbsorbed: A Solidity uint64 of the number of accounts successfully absorbed by the protocol as a result of the liquidators call to the absorb function.\napproxSpend: A Solidity uint128 of the sum of all gas spent by the liquidator that has called the absorb function.\nSolidity\nComet comet = Comet(0xCometAddress);\nLiquidatorPoints pointsData = comet.liquidatorPoints(0xLiquidatorAddress);\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst [ numAbsorbs, numAbsorbed, approxSpend ] = await comet.callStatic.liquidatorPoints('0xLiquidatorAddress');\n\nReserves\nReserves are a balance of the base or collateral asset, stored internally in the protocol, which automatically protect users from bad debt. Reserves can also be withdrawn or used through the governance process.\nReserves are generated in two ways: the difference in interest paid by borrowers, and earned by suppliers of the base asset, accrue as reserves into the protocol. Second, the liquidation process uses, and can add to, protocol reserves based on the target reserve level set by governance.\nGet Base Asset Reserves\nThis function returns the amount of protocol reserves for the base asset as an integer.\nComet\nfunction getReserves() public view returns (int)\n\nRETURNS: The amount of base asset stored as reserves in the protocol as an unsigned integer scaled up by 10 to the “decimals” integer in the asset’s contract.\nSolidity\nComet comet = Comet(0xCometAddress);\nuint reserves = comet.getReserves();\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst reserves = await comet.callStatic.getReserves();\n\nGet Collateral Asset Reserves\nThis function returns the amount of protocol reserves for the specified collateral asset as an integer.\nComet\nfunction getCollateralReserves(address asset) public view returns (uint)\n\nRETURNS: The amount of collateral asset stored as reserves in the protocol as an unsigned integer scaled up by 10 to the “decimals” integer in the collateral asset’s contract.\nSolidity\nComet comet = Comet(0xCometAddress);\nuint reserves = comet.getCollateralReserves(0xCollateralAsset);\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst reserves = await comet.callStatic.getCollateralReserves(collateralAssetAddress);\n\nTarget Reserves\nThis immutable value represents the target amount of reserves of the base token. If the protocol holds greater than or equal to this amount of reserves, the buyCollateral function can no longer be successfully called.\nComet\nfunction targetReserves() public view returns (uint)\n\nRETURN: The target reserve value of the base asset as an integer, scaled up by 10 to the “decimals” integer in the base asset’s contract.\nSolidity\nComet comet = Comet(0xCometAddress);\nuint targetReserves = comet.targetReserves();\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst targetReserves = await comet.callStatic.targetReserves();","tokens":2276,"crawled_at":1791194398319}
+{"id":10377,"url":"https://a16zcrypto.com/posts/article/steps-uk-drive-growth-protect-consumers","domain":"a16zcrypto.com","chapter":"research","title":"4 steps the UK can take to drive growth and protect consumers: Advancing effective cryptoasset regulation - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\n4 steps the UK can take to drive growth and protect consumers: Advancing effective cryptoasset regulation\nMiles Jennings and Aiden Slavin\n12.19.25\n\nTABLE OF CONTENTS\nU.S. direction of travel U.S. direction of travel\n#1: Adopt a control-based decentralization framework\n#2: Calibrate disclosure requirements for network tokens\n#3: Introduce protections against market abuse\n#4: Align UK and U.S. approaches to stablecoin regulation\nTags\npolicy & regulation\nUK\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nThe global race to implement smart crypto regulation is accelerating. In recent months, the U.S. surged ahead, enacting a stablecoin bill and advancing market structure legislation — both with broad bipartisan support.\n\nAcross the Atlantic, the United Kingdom is defining its own role in shaping the future of cryptoassets and blockchain networks. New legislation introduces intermediary licensing for crypto exchanges, agents, and dealers, as well as bespoke disclosure and market abuse regimes for cryptoassets, creating consumer protection and transparency obligations. By next year, the Financial Conduct Authority (FCA) aims to finalize policy statements related to stablecoins, cryptoasset lending, staking, and more.\n\nWhile U.S. legislation — with its emphasis on consumer protection, regulatory clarity, and innovation — is aiming to set the global standard, the UK has a narrow but significant window to carve out a competitive position of its own. Roughly 12% of UK adults own or have owned crypto, an increase from just 4% in 2021. A recent economic analysis estimates that blockchain firms could contribute £40bn to the UK economy by 2035.\n\nProactive, effective cryptoasset regulation can ensure that London not only remains a hub for traditional finance but also becomes a center of responsible crypto innovation. Doing so can help realize the government’s number one mission — economic growth — by unlocking new opportunities for businesses and citizens.\n\nIn what follows, we provide an overview of U.S. crypto policy progress and propose four measures that the UK can enact to safeguard its citizens and support local blockchain businesses, while positioning itself as a leader in blockchain innovation for decades to come.\n\nU.S. direction of travel\n\nIn recent months, the U.S. has made considerable progress in the development of an effective regulatory framework for cryptoassets and blockchain systems. In July, the President signed the first substantive piece of U.S. crypto legislation into law, and the U.S. House of Representatives advanced a major “market structure” bill with broad bipartisan support. The GENIUS Act (Guiding and Establishing National Innovation for U.S. Stablecoins Act) sets out clear rules for stablecoins, while the U.S. House-passed CLARITY Act (Digital Asset Market Clarity Act) would establish a regulatory framework for blockchain systems.\n\nAs federal legislation comes online, U.S. regulators are also working to provide clarity. In August, the U.S. Securities and Exchange Commission (SEC) launched “Project Crypto” to enable U.S. capital markets to move onchain. In a recent speech at the Federal Reserve Bank of Philadelphia, SEC Chairman Atkins outlined the agency’s forthcoming cryptoasset taxonomy, defining common token types such as “digital collectibles” and “digital tools,” and specifying that in his opinion neither is a security.\n\nSignificantly, Chair Atkins’ taxonomy aligns with proposed U.S. legislation in its focus on “network tokens” (or “digital commodities” in the parlance of the CLARITY Act). As he put it, network tokens are “intrinsically linked to and derive their value from a programmatic operation of a crypto system that is ‘functional’ and ‘decentralized,’ rather than from the expectation of profits arising from the essential managerial efforts of others” and, as such, are not securities.\n\nEstablishing a fit-for-purpose token taxonomy and, in particular, clarifying rules for network tokens are crucial first steps in defining an effective regulatory regime for crypto. What makes network tokens unique among common token types is the way they accrue value. The network token ETH, for example, derives its value from the operation and utility of the Ethereum network, not from the efforts of a centralized company. Information about a company’s financial condition or management team is therefore not relevant to understanding ETH’s value or risks. By contrast, a share of Apple stock reflects exposure to the performance and decisions of a single company, making standard issuer-style disclosure essential.\n\nAs a result, network tokens can have similar trust dependencies and risks as financial instruments during early stages, when a project is still controlled, but then evolve into decentralized systems that eliminate information asymmetries through onchain transparency. Once control is eliminated, their risk profile aligns more closely with commodities such as gold or foreign exchange, rather than financial instruments.\n\nAs the U.S. makes progress via its legislative process and agency-led efforts, it is more important than ever that the UK advances its own crypto roadmap. Blockchain technology is inherently global. Decentralized protocols operate across jurisdictions, enabling users to engage in truly borderless peer-to-peer interactions without intermediaries. It is critical that leading nations like the UK put in place effective cryptoasset regulation. In what follows, we provide four recommendations to that end.\n\n#1: Adopt a control-based decentralization framework\n\nThe cornerstone of a modern cryptoasset regime should be a control-based decentralization framework — one that objectively determines when a blockchain system or network token is decentralized and, therefore, eliminates risks in a manner that justifies different regulatory treatment.\n\nBy operating in a transparent manner absent human control, decentralized systems can mitigate the risks addressed by many regulations. Recognizing this, a recent policy note from HM Treasury relating to the new UK cryptoasset regulatory regime and an FCA consultation paper acknowledge that systems that are truly decentralized warrant different regulatory treatment than centralized intermediaries.\n\nBut the government stops short of answering the critical question: What exactly makes a system “decentralized”? Without clear, objective criteria for defining decentralization, firms lack the certainty they need to build in the UK, and are likely to leave for jurisdictions offering clarity. Worse still, this gap risks harm by enabling bad actors to falsely claim that they are decentralized and seek to avoid regulation — at users’ peril.\n\nAcknowledging this gap, the FCA recently proposed to separately consult on future guidance regarding the application of the new UK regime to DeFi (DeFi Guidance) covering how decentralization and control will be considered based on the degree to which a cryptoasset activity is controlled by an identifiable entity. As the FCA progresses its work on this guidance, we recommend that it adopts a control-based decentralization framework. This framework would give UK regulators a test to implement the new cryptoassets regime (and in particular the DeFi Guidance) in a consistent and objective way that is merit- and technology-neutral. The key premises of this approach are that:\n\nDecentralization can be defined in terms of control, and measured according to specific, objective criteria.\n\nWhen control is eliminated, many risks are ameliorated, so the application of regulation should be limited; conversely, when control is present, risks persist, so traditional (but modernized) regulatory approaches should be used.\n\nThis framework is already gaining ground in the United States. The CLARITY Act (CLARITY) and the Responsible Financial Innovation Act (RFIA), proposed in the U.S. Senate, both advance a control-based decentralization framework.\n\nCLARITY utilizes its decentralization framework to accomplish three goals:\n\nIt establishes seven clear, measurable standards for assessing whether a blockchain system and its related network token are no longer under the control of an individual or coordinated group.\n\nIt uses a subset of these standards to assess whether a blockchain system is sufficiently disintermediated such that it should qualify for a safe harbor from the law’s intermediary regulatory regime.\n\nIt tailors its disclosure regime to account for the different disclosures that may be suitable depending on whether a project is controlled or not.\n\nCLARITY’s seven standards focus on three types of control:\n\nOperational Control: the ability for a party to unilaterally censor, or override network operations.\n\nEconomic Control: the ability for a party to retain the power to extract value from the system through privileged monetary rights, such as unvested cryptoasset allocations or privileged cryptoasset creation authorities.\n\nGovernance Control: the ability for a party or coordinated group to pass protocol governance proposals unilaterally or through offchain influence.\n\nIf adopted, we recommend that the FCA tailors its control-based decentralization framework according to applicable risks, implementing it in a manner that achieves the goals of specific components of the regulatory regime, without imposing unnecessary requirements.\n\nFor example, in differentiating the trust dependencies and risks of network tokens from ordinary financial instruments, risks arising from operational, economic, and governance control must all be considered. Where such risks are not eliminated, parties can leverage their control over the system to extract value, thereby materially impacting the potential value of the system’s network token. Said differently, whoever controls a system (a company, a blockchain system, etc.) controls the risks associated with that system and can unilaterally affect or structure its risk. As such, addressing user risks with respect to a specific network token requires the elimination of all of these mechanisms of control in relation to the token and its underlying blockchain system.\n\nFulfilling the goals of the intermediary licensing rules with respect to decentralized finance (DeFi), however, only requires eliminating operational control. As long as no individual or commonly orchestrated group retains the ability to control user funds or transactions or censor, or override network operations, then the risks that the intermediary licensing rules intend to address are eliminated. By contrast, whether a DeFi system has eliminated economic or governance control is not relevant, because neither impacts whether transactions through the system give rise to intermediary-related risks. Accordingly, with respect to DeFi, we believe that in its DeFi Guidance the FCA should provide clarity on the application of the intermediary licensing regime establishing that DeFi systems that have eliminated operational control do not involve a clear controlling person and, therefore, do not need to comply with the intermediary licensing rules.\n\nIn these respects, U.S. legislation provides helpful examples. Both CLARITY and RFIA apply transfer restrictions to limit the ability of a project’s insiders (founders, employees, investors, etc.) to engage in resales of a project’s network token until control over the network token and its underlying blockchain system has been eliminated. With regard to DeFi systems, both CLARITY and RFIA establish that DeFi systems are exempt from the intermediary licensing regimes proposed by these bills if operational control has been eliminated.\n\nIn implementing the cryptoasset regulatory regime, it is also critical that the FCA clarifies that the intermediary licensing regime does not apply to other participants and technologies that do not control user assets or transactions and, therefore, do not give rise to the risks that this regulation is intended to address. For example, developers and providers of non-custodial software that enables users to transact cryptoassets directly via blockchains do not pose intermediary risks. Because they do not possess operational control or control user assets or transactions, they cannot mishandle them, do not give rise to conflicts of interest, or otherwise pose any principal-agent risks that intermediary regulation is intended to mitigate. Therefore, in its DeFi Guidance, the FCA should clarify that these participants are not considered within the perimeter of this regime.\n\nIt is also crucial that the FCA clarifies that regulatory obligations do not apply to decentralized protocols, the blockchain networks and smart contract protocols by which cryptoasset transactions are securely recorded and verified without intermediaries. As we’ve elaborated elsewhere, it’s not technically feasible for such protocols to comply with regulations, which often require subjective determinations. Reconciling regulations that often differ — and in many cases conflict — across jurisdictions is likewise not possible for global decentralized protocols. Moreover, applying regulation to protocols is unnecessary to achieve the goals of the government’s regime, which can be realized by imposing rules on centralized intermediaries.\n\nThese goals can be achieved through two measures:\n\nIn its DeFi Guidance, the FCA should issue guidance on the application of the intermediary licensing regime to DeFi clarifying that the activities of technical service providers such as node operators, validators, and developers and providers of front-end interfaces or similar software who do not have control over user assets or transactions are not considered within the perimeter of this regime.\n\nThe FCA should clarify that protocols, themselves, are not subject to regulatory obligations.\n\nSetting out such a framework in FCA rules and guidance and applying it in the implementation of the regulatory regime would have benefits for entrepreneurs, regulators, and users.\n\nFor startups, it would provide a predictable, actionable compliance roadmap, incentivizing them to choose the UK. Projects could start centralized but understand the concrete steps necessary to achieve decentralization.\n\nFor regulators, it would form the basis of an objective, merit- and technology-neutral approach to implementing the cryptoasset regime.\n\nAnd for consumers, it would preserve protections while unlocking the core innovation of blockchain networks, decentralization, which benefits them in several ways.\n\n#2: Calibrate disclosure requirements for network tokens\n\nWhen it comes to network tokens, traditional issuer-centric disclosures — focused on information about management personnel, business strategy, or financial performance — only make sense while the underlying blockchain system is controlled by an issuer. In a control-based decentralization framework, once control is eliminated network tokens derive their value from the functioning of a decentralized network, which works transparently and without human control or intervention. All relevant information about network tokens that have eliminated control is therefore publicly available through onchain data. This is what makes network tokens fundamentally different from financial instruments. And this transparency and lack of control ensures that all market participants are equally situated with respect to the information needed to assess a given network token.\n\nImposing traditional disclosure rules on network tokens also runs the risk of undermining decentralization and misleading consumers. Such rules could effectively force these networks to forgo decentralization or to recentralize to comply with issuer-oriented requirements, and may mislead users by suggesting that there is a controller of the network token attempting to drive its value. Therefore, when it comes to network tokens, a calibrated disclosure regime would be most appropriate.\n\nAs such, disclosure requirements applied to these tokens should begin by being “issuer-centric” but evolve to being “network-centric” after control is eliminated, emphasizing relevant onchain information about network functionality, governance, and economic mechanisms. After all, with respect to network tokens, this transparently viewable information is ultimately what is relevant for investors and users. To effectively calibrate disclosure requirements for network tokens, we recommend the FCA issue guidance providing for a tailored set of disclosures for this unique type of cryptoasset. Such guidance aligns with the FCA’s proposal to require cryptoasset trading platforms to establish risk-based, objective admission criteria, and would help such firms determine what admission and disclosure criteria to require for network tokens.\n\n#3: Introduce protections against market abuse\n\nA control-based decentralization framework should also guide the design of the UK’s cryptoasset market abuse regime. Where control persists — particularly during the early stages of a project — risks of insiders exploiting information asymmetries remain high and warrant targeted safeguards.\n\nWhile blockchain systems can ultimately eliminate control through decentralization, many projects undergo transitional phases during which founders, developers, or early contributors retain privileged information and material token holdings. During these periods, there is a risk that insiders will leverage asymmetric information to the detriment of users. Bad actors could, for example, rapidly sell significant holdings after a token launches, taking advantage of inflated prices and then triggering sharp declines once supply floods the market. Such behavior harms investors, undermines consumer confidence, and ultimately stymies innovation.\n\nTo address this, the UK should incorporate insider restrictions into its forthcoming cryptoasset market abuse regime. Specifically, a mandatory post-listing lock-up period should apply to insiders (founders, staff, and early contributors) while a project remains controlled. This measure would prevent insiders from using their privileged position to manipulate token prices before a system achieves decentralization.\n\nAs discussed above, we believe CLARITY and RFIA provide helpful examples in this regard. By prohibiting insiders from selling before a project has achieved decentralization by eliminating control, CLARITY and RFIA mitigate market abuse risks.\n\nSuch restrictions should be proportionate and time-limited, phasing out once objective decentralization criteria are met. In line with this, the final statutory instrument includes a prohibition on insider dealing, and the FCA is proposing to require cryptoasset trading platforms, as part of their due diligence processes, to review and verify lock-up arrangements with respect to a given cryptoasset. While these are helpful steps, they do not go far enough. Introducing control-based restrictions on insiders would ensure that users are protected from information asymmetries arising during the early stages of a project’s development. By tying insider protections directly to control, regulators can ensure that users are protected from control-related risks while a project remains centralized and encourage projects to achieve decentralization.\n\nEmbedding these measures would uphold the fairness, transparency, and integrity of UK markets while signalling that the government is committed to responsible innovation.\n\n#4: Align UK and U.S. approaches to stablecoin regulation\n\nThe U.S. and the UK share more than robust capital markets and world leading financial institutions: Historic collaboration between the two nations has led to opportunities for investors, businesses, and market participants in both countries. In recognition of this, Chancellor of the Exchequer Rachel Reeves and Treasury Secretary Scott Bessent met in London in September to launch the Transatlantic Taskforce for Markets of the Future. This partnership aims in part to identify ways to collaborate on digital asset policy, improving the connection between the two countries in the service of growth and competitiveness.\n\nWe believe a key area that this taskforce should focus on is stablecoin regulation. Though only a decade old, stablecoins now rival the world’s largest payment networks in transaction volume. Around the world, they will enable quicker, programmable payments and cut out rent-seeking middlemen.\n\nBoth nations are currently advancing stablecoin rules. In spring of 2025, the FCA published Consultation Paper 25/14 setting out a proposed regulatory framework for stablecoin issuance. Over the summer, President Trump signed into law the “Guiding and Establishing National Innovation for U.S. Stablecoins” (GENIUS) Act. Yet to date, the two countries have been largely siloed in their development of their stablecoin regimes.\n\nInternational collaboration is necessary to realize the full benefits of stablecoins. That’s because stablecoins are global by design. Treating them as solely domestic payment instruments risks fragmenting liquidity and undermining efficiencies. The UK, as a world leader in financial services, has the opportunity to position itself as a bridge jurisdiction for stablecoin innovation.\n\nThe U.S. GENIUS Act explicitly creates a pathway for reciprocity with “comparable jurisdictions,” allowing stablecoins to operate across borders where regulatory outcomes align. This approach recognizes that if the core risks — redemption, reserves, governance, illicit finance — are mitigated to equivalent standards, duplicative localization requirements or additional regulatory requirements treating such comparable foreign-issued stablecoins differently would be unnecessary. As it continues to develop its stablecoin regulatory framework, the UK should do the same.\n\nSpecifically, the U.S. and UK should establish a transatlantic corridor to enable their use in wholesale markets and payments as part of cross-border commerce, allowing both GBP- and USD-denominated stablecoins to interoperate. To support this, the two countries should align on regulatory approaches, promoting best practices and also pursuing mutual recognition with other jurisdictions to prevent duplicative or conflicting compliance requirements for well-regulated firms.\n\nTo do so, we suggest the UK ensures that its regulatory standards for UK-licensed stablecoin issuers are designed to be compatible and equivalent with those being developed in the U.S. under GENIUS. This would maximize the possibility of the UK being designated as a comparable jurisdiction by the U.S. And to the extent the UK proposes to treat foreign-issued stablecoins differently under its stablecoin regulatory framework, it should also embed a reciprocity mechanism in its stablecoin regime, one based on equivalence criteria for comparable foreign frameworks — covering reserve composition, audit standards, and redemption rights — and enable mutual recognition of trusted foreign issuers, such as U.S. firms under GENIUS.\n\nBy taking this approach the UK can become a stablecoin hub for global finance: an environment where a GBP- or USD-backed token can circulate seamlessly on both sides of the Atlantic. If it does not, issuers will concentrate activity in jurisdictions that provide reciprocal access, and the UK risks being sidelined as a secondary market.\n\n***\n\nThe UK is at a pivotal moment. Around the world, governments are racing to design frameworks that both harness and safely govern crypto innovation. With clear, forward-looking regulation, the UK can do more than keep pace — it can lead.\n\nIf implemented, these steps would give entrepreneurs confidence to build in Britain, attract investment and talent, and secure the country’s place as a global hub for responsible blockchain innovation — driving economic growth while setting a global standard for smart, effective cryptoasset regulation.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nYou should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investment-list/.\n\nThe content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures/ for additional important information.","tokens":6772,"crawled_at":1791194399066}
+{"id":10378,"url":"https://gov.uniswap.org/t/rfc-il-hedge-hook-automated-impermanent-loss-protection-for-uniswap-v4-lps/26059","domain":"gov.uniswap.org","chapter":"governance_daos","title":"[RFC] IL Hedge Hook — Automated Impermanent Loss Protection for Uniswap v4 LPs - Requests for Comment - Uniswap Governance","text":"[RFC] IL Hedge Hook — Automated Impermanent Loss Protection for Uniswap v4 LPs\n\nRequests for Comment\n\nbelta_labs\n\nMarch 15, 2026, 8:09pm\n\n1\n\n[RFC] IL Hedge Hook — Automated Impermanent Loss Protection for Uniswap v4 LPs\n\nCategory: Request for Comment\n\nAuthor: JJ (BELTA Labs)\n\nStatus: Draft — seeking community feedback\n\nNo governance action required at this time.\n\nTL;DR\n\nBELTA is a Uniswap v4 Hook that automatically hedges LP impermanent loss. LP provides liquidity to a BELTA-hooked pool — everything else is automatic. Premium collection, IL calculation, payout settlement. No manual hedging. No trading desk. No additional UX.\n\n5.1-year backtest with real ETH prices (2020–2025, including COVID/LUNA/FTX):\n\nWithout Hedge\nWith BELTA\n\nLP annual return\n\n+4.0%/yr\n\n+7.8%/yr\n\nNet benefit\n\n—\n\n+3.7%/yr\n\nLP pays 12% of fee income as premium. Receives 35% of IL as reimbursement. Pays less than they get back.\n\n1. The Problem\n\n49.5% of Uniswap V3 LPs underperform HODL (Loesch et al., 2021). IL is the #1 reason LPs exit:\n\nIL → LP exits → TVL drops → slippage ↑ → volume ↓ → fee revenue ↓\n\nThis directly impacts Uniswap’s competitive position. And existing solutions don’t solve it:\n\nApproach\nWhy It Fails\n\nGamma / Arrakis\n\nAuto-rebalances range, but IL still occurs\n\nManual Perps hedge\n\nRequires active monitoring, rebalancing, funding management — trading desk level ops\n\nOptions (Opyn / Lyra)\n\nLow liquidity, expensive, expiry management\n\nWide range\n\nFee efficiency drops dramatically\n\nThe core issue: no solution converts IL hedging into zero-friction passive infrastructure.\n\nA $50K LP who wants to hedge with Perps today needs to: (1) monitor position in real-time, (2) calculate hedge ratio, (3) execute Perp trades, (4) manage funding rates, (5) rebalance periodically. This is operationally impractical for most LPs. BELTA automates the entire process inside a V4 Hook.\n\n2. Why Now — UNIfication + V4 Hooks\n\nTwo recent developments make this the right time:\n\nV4 Hooks make it technically possible. In V3, IL hedging required external monitoring of LP position NFTs, off-chain calculations, and manual Perp trades. V4’s Hook system allows direct on-chain detection of position creation, swaps, and exits — enabling fully automated IL settlement within a single contract. This protocol could not have existed before V4.\n\nUNIfication makes LP retention more urgent. With the recent UNIfication proposal turning on protocol fees (1/4 to 1/6 of LP fees), LPs now keep less of each trade. This compresses LP margins and increases the risk of attrition — making IL hedging infrastructure more valuable than ever. A protocol that improves LP net returns by +3.7%/yr directly counteracts the margin compression from protocol fees.\n\n3. How It Works\n\n3.1 V4 Hook Callbacks\n\nSingle Hook contract. Four callbacks. LP does nothing.\n\nCallback\nWhat Happens\n\nafterAddLiquidity\n\nPosition registered, entry price snapshotted, underwriting check applied\n\nbeforeSwap\n\nDynamic fee calculated (volatility → fee multiplier 1–4x)\n\nafterSwap\n\nPremium accumulated from fee delta, epoch IL tracker updated\n\nafterRemoveLiquidity\n\nIL calculated, 35% coverage applied, payout settled from Underwriter Pool\n\n3.2 Underwriter Pool — Who Pays the IL\n\nBELTA is not a magic trick — someone absorbs the IL. That someone is the Underwriter Pool: external capital providers who deposit into a vault and earn premium income + Aave yield in exchange for taking first-loss IL risk.\n\nThe pool is protected by three independent layers:\n\nLayer 1 — Dynamic Fee (V4 native): beforeSwap tracks EWMA volatility and adjusts fee multiplier (up to 4x). Premium income rises exactly when IL risk is highest. Self-balancing.\n\nLayer 2 — Aave Yield: Idle pool capital earns ~5%/yr on Aave/Morpho. Baseline income regardless of LP activity.\n\nLayer 3 — Perps Hedging: Protocol maintains ETH shorts during down markets. Backtest: 36% of raw IL absorbed by short profits. Funding cost: ~2%/yr.\n\n3.3 On-Chain Underwriting — Adverse Selection Defense\n\nNot every LP position is covered. The Hook enforces:\n\nNarrow range (<±10%): rejected — IL multiplier too extreme\n\nMinimum position: $10,000\n\nMinimum hold: 72 hours\n\nPosition age: 1 hour before coverage activates\n\nThis structurally excludes high-risk profiles that would drain the pool. Similar to how insurance companies don’t cover pre-existing conditions.\n\n3.4 Smart Contract Architecture\n\nContract\nRole\n\nBELTAHook.sol\n\nV4 Hook main — IL calculation, settlement logic, Dynamic Fee\n\nUnderwriterPool.sol\n\nERC-4626 Vault — pool management, premium distribution, cooldown\n\nEpochSettlement.sol\n\n7-day epoch IL settlement — Keeper automation, daily payout cap\n\nVolatilityOracle.sol\n\nEWMA volatility tracking — Dynamic Fee curve\n\nTreasuryModule.sol\n\nTreasury buffer management + Aave yield stacking\n\nHedgeManager.sol\n\nPerps delta-hedging — dYdX/GMX/Hyperliquid adapter (Phase 2+)\n\nBELTAToken.sol\n\nGovernance + revenue participation token\n\nxBELTA.sol\n\nStaking vault — exchange rate appreciation model\n\nAll contracts built with Foundry. Scaffold complete. Source: GitHub.\n\n4. How This Differs from DeFi Insurance\n\nThis is not Nexus Mutual or InsurAce. Those protocols failed at IL hedging because:\n\nTraditional DeFi Insurance\nBELTA\n\nCovered event\n\nVaguely defined (hacks, depegs) → claim disputes\n\nIL — mathematically exact, calculated on-chain\n\nClaim process\n\nGovernance vote, subjective\n\nAutomatic — no claims, no disputes\n\nAdverse selection\n\nNo defense → pool drained\n\nOn-chain underwriting rules\n\nPool backing\n\nToken-denominated → crash = insolvency\n\nStablecoin-based + Aave yield\n\nActuarial basis\n\nNo historical data\n\n5.1 years of backtested IL data\n\nThe fundamental difference: IL is a deterministic function of price change. It’s not a subjective event — it’s math. IL = 2√r/(1+r) - 1. This means coverage can be priced, backtested, and settled entirely on-chain with zero human judgment.\n\n5. Backtest — Real Data, Real Crashes\n\n270 weekly ETH/USD close prices (Etherscan/CoinGecko, Jan 2020 – Mar 2025). Not synthetic. Includes:\n\nCOVID crash (ETH -38.5% in one week)\n\nLUNA collapse (-31.9%)\n\nFTX (-22%)\n\nAug 2024 Yen carry trade (-22.2%)\n\nLP Economics ($10,000 position, 5.1 years):\n\nWithout Hedge\nWith BELTA\n\nFee income (gross)\n\n$11,536\n\n$11,536\n\nPremium paid (12% of fees)\n\n—\n\n-$1,384\n\nIL suffered\n\n-$9,464\n\n-$9,464\n\nIL reimbursed (35%)\n\n—\n\n+$3,312\n\nNet P&L\n\n+$2,072\n\n+$4,000\n\nAnnual return\n\n+4.0%/yr\n\n+7.8%/yr\n\nWhy does this work? IL concentrates in black swan weeks. LP pays $5.17/week in premium during quiet periods. Gets $50–$216 back in a single crash week. Over 5.1 years, the payouts exceed the premiums by $1,928.\n\nProtocol sustainability (Underwriter Pool):\n\nAt scale ($20M pool, $120M hedged TVL), with all three layers active:\n\nPool grows at +9.3%/yr (median, sliding window stress test)\n\nIL/Income ratio: 0.89x — income exceeds IL payouts\n\nStress tested through 2022 bear market (ETH -80% from ATH)\n\nFull backtest methodology in the whitepaper.\n\n6. Why This Matters for Uniswap\n\nLP retention is Uniswap’s core growth constraint.\n\nIf LPs earn more and stay longer → TVL deepens → slippage decreases → volume increases → protocol revenue grows. BELTA is direct infrastructure for this flywheel.\n\nSpecifically:\n\nV4 Hook native — no governance changes, no core protocol modifications needed\n\nDynamic Fee — one of the most practical beforeSwap use cases, directly aligned with Hook Design Lab focus areas\n\nMeasurable LP improvement — +3.7%/yr net benefit, backed by 5.1 years of real data\n\nProtocol fee synergy — as UNIfication protocol fees compress LP margins, IL hedging becomes more important for LP retention\n\nInfrastructure, not a competitor — BELTA makes Uniswap LPs more profitable. It doesn’t fork, replace, or compete with Uniswap. It’s a Hook.\n\n7. Security Considerations\n\nNo external oracle dependency — IL calculated from V4 internal tick data only. No Chainlink or TWAP manipulation risk for core IL settlement.\n\nCircuit breaker — 24h IL payouts capped at 30% of pool. Single payout capped at 5%.\n\nMultisig — protocol parameter changes require 3/5 signatures.\n\nAudit plan — 2 independent professional audits budgeted. First audit after testnet Phase 1 completion, second before mainnet pilot.\n\nEpoch-based settlement — IL settled in 7-day batches, not real-time. Prevents flash-loan-style exploits and reduces gas costs.\n\nCooldown periods — Treasury: 30-day unstaking + 2–5% early withdrawal fee. Senior: 7-day cooldown + daily 10% TVL withdrawal cap. Structurally prevents bank runs.\n\n8. Timeline\n\nMilestone\nTarget\nDeliverable\n\nM1 — Hook MVP\n\nMonth 1–3\n\nBELTAHook.sol testnet deployment (Sepolia/Unichain), 12+ epoch executions, IL accuracy report\n\nM2 — First Audit\n\nMonth 4–5\n\nSecurity audit report, vulnerability fixes, grant applications submitted\n\nM3 — Mainnet Pilot\n\nMonth 5+\n\nPool $100K live operation, 24 epochs real settlement data, VC pitching\n\nM4 — Open Market\n\nMonth 11+\n\nPool $10M, Treasury/Senior dual pool, BELTA token + xBELTA launch\n\nM5 — DEX Payment\n\nMonth 36+\n\nPool $20M+, DEX partnership negotiations\n\n9. Current Status\n\nItem\nStatus\n\nWhitepaper\n\nv5.6.0 — 33 pages, full mechanism design + backtest (EN)\n\nSmart contracts\n\n8 .sol files (Foundry), scaffold complete (GitHub)\n\nBacktest engine\n\nv5.0.1 — real ETH prices, sliding window stress test, sensitivity analysis\n\nWebsite\n\nofficial-belta.github.io/belta-labs\n\nNext milestone\n\nTestnet deployment (Sepolia / Unichain)\n\nEntity\n\nBELTA Labs Pte. Ltd. (Singapore)\n\n10. Looking for Feedback\n\nThis is an RFC — we’re here to get challenged, not to sell.\n\nSpecific questions for the community:\n\nMechanism design: Do you see a flaw in the premium/coverage structure? Is 12%/35% the right ratio?\n\nUnderwriter economics: Would you deposit into the Underwriter Pool at these expected returns?\n\nLP adoption: As an LP, would you use a BELTA-hooked pool? What would change your mind?\n\nTechnical: Any concerns about the Hook callback design or gas implications?\n\nUNIfication context: With protocol fees now live, does IL hedging infrastructure become more or less important for LP retention?\n\nMissing risks: What failure modes are we not seeing?\n\n11. Links\n\nWhitepaper: official-belta.github.io/belta-labs\n\nGitHub: github.com/Official-Belta/belta-labs\n\nDiscord: BELTA Labs Discord\n\nContact: JJ — available in this thread or via Discord DM\n\nWe’d rather hear “this won’t work because X” now than discover X after mainnet. All feedback welcome.\n\n4 Likes\n\neblack333\n\nJune 10, 2026, 7:07pm\n\n2\n\nCould the hedge intensity or premium/coverage ratio be regime-aware rather than only volatility-aware? In steady, fee-compensated regimes, LPs may not need as much protection, so a lower coverage level could improve net returns. In directional or shock-driven regimes, where fees are less likely to cover loss-versus-hold, higher hedge intensity may be more valuable.\n\n1 Like\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[RFC] - Hedge against Impermanent Loss\n\nRequests for Comment\n\n9\n\n2068\n\nSeptember 15, 2024\n\n[Temp Check] Activate v4 Protocol Fees\n\nTemperature Check\n\n24\n\n2782\n\nAugust 18, 2026\n\nTemperature Check - How to 10x LP earnings & TVL. A proposal for Uniswap v4\n\nTemperature Check\n\n3\n\n4441\n\nApril 3, 2023\n\nProposal to fund LP's protection project\n\nRequests for Comment\n\n7\n\n2648\n\nSeptember 22, 2020\n\n\"Fee Switch\" Design Space & Next Steps\n\nRequests for Comment\n\n73\n\n29139\n\nNovember 21, 2022","tokens":2842,"crawled_at":1791194399495}
+{"id":10379,"url":"https://docs.sui.io/references/sui-api","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Sui RPC | Sui Documentation","text":"info\nJSON-RPC is disabled on Sui Foundation MainnetMainnetProduction network for live transactions and real-value assets. full nodes. The shutoff took effect the week of July 27, 2026. Sui Foundation plans full decommission, including code removal, for mid-October 2026. If your application still calls JSON-RPC, migrate to gRPC or GraphQL RPC now. For a method mapping, decision criteria, and the remaining timeline, see the JSON-RPC Migration Guide.\n\nSee RPC and Data Providers for providers that serve gRPCgRPC APIReplaces JSON-RPC on full nodes for data access. and GraphQL RPCGraphQL RPCA lightweight GraphQL RPC service. endpoints. Contact a provider directly to request access. If your provider does not yet support these interfaces, ask them to enable support, or reach the Sui Foundation team on Discord, Telegram, or Slack for help.\n\ninfo\nRefer to Access Sui Data for an overview of options to access Sui network data.\n\nSuiJSON is a JSON-based format with restrictions that allow Sui to align JSON inputs more closely with MoveMoveAn open source programming language used for all activity on Sui. call arguments.\n\nThis table shows the restrictions placed on JSON types to make them SuiJSON compatible:\n\nJSONSuiJSON restrictionsMove type mapping\nNumber\nMust be unsigned integer\nu8, u16, u32, u64 (encoded as String), u128 (encoded as String), u256 (encoded as String)\n\nString\nNo restrictions\nVector<u8>, AddressAddressA unique, anonymous identity on a blockchain network., ObjectID, TypeTag, Identifier, Unsigned integer (256 bit max)\n\nBoolean\nNo restrictions\nBool\n\nArray\nMust be homogeneous JSON and of SuiJSON type\nVector\n\nNull\nNot allowed\nN/A\n\nObjectObjectThe basic unit of storage on Sui.\nNot allowed\nN/A\n\nType coercion reasoning​\n\nDue to the loosely typed nature of JSON/SuiJSON and the strongly typed nature of Move types, you sometimes need to overload SuiJSON types to represent multiple Move types.\n\nFor example, SuiJSON::Number can represent both u8 and u32. This means you have to coerce and sometimes convert types.\n\nWhich type you coerce depends on the expected Move type. For example, if the Move function expects a u8, you must have received a SuiJSON::Number with a value less than 256. More importantly, you have no way to easily express Move addresses in JSON, so you encode them as hex strings prefixed by 0x.\n\nAdditionally, Move supports u128 and u256 but JSON doesn't. As a result Sui allows encoding numbers as strings.\n\nType coercion rules​\n\nMove TypeSuiJSON RepresentationsValid ExamplesInvalid examples\nBool\nBool\ntrue, false\n\nu8\nSupports 3 formats: Unsigned number < 256. Decimal string with value < 256. One byte hex string prefixed with 0x.\n7 \"70\" \"0x43\"\n-5: negative not allowed 3.9: float not allowed NaN: not allowed 300: U8 must be less than 256 \" 9\": Spaces not allowed in string \"9A\": Hex num must be prefixed with 0x \"0x09CD\": Too large for U8\n\nu16\nThree formats are supported Unsigned number < 65536. Decimal string with value < 65536. Two byte hex string prefixed with 0x.\n712 \"570\" \"0x423\"\n-5: negative not allowed 3.9: float not allowed NaN: not allowed 98342300: U16 must be less than 65536 \" 19\": Spaces not allowed in string \"9EA\": Hex num must be prefixed with 0x \"0x049C1D\": Too large for U16\n\nu32\nThree formats are supported Unsigned number < 4294967296. Decimal string with value < 4294967296. One byte hex string prefixed with 0x.\n9823247 \"987120\" \"0x4BADE93\"\n-5: negative not allowed 3.9: float not allowed NaN: not allowed 123456789123456: U32 must be less than 4294967296 \" 9\": Spaces not allowed in string \"9A\": Hex num must be prefixed with 0x \"0x3FF1FF9FFDEFF\": Too large for U32\n\nu64\nSupports two formats Decimal string with value < U64::MAX. Up to 8 byte hex string prefixed with 0x.\n\"747944370\" \"0x2B1A39A15E\"\n123434: Although this is a valid U64 number, it must be encoded as a string\n\nu128\nTwo formats are supported Decimal string with value < U128::MAX. Up to 16 byte hex string prefixed with 0x.\n\"74794734937420002470\" \"0x2B1A39A1514E1D8A7CE\"\n34: Although this is a valid U128 number, it must be encoded as a string\n\nu256\nTwo formats are supported Decimal string with value < U256::MAX. Up to 32 byte hex string prefixed with 0x.\n\"747947349374200024707479473493742000247\" \"0x2B1762FECADA39753FCAB2A1514E1D8A7CE\"\n123434: Although this is a valid U256 number, it must be encoded as a string 0xbc33e6e4818f9f2ef77d020b35c24be738213e64d9e58839ee7b4222029610de\n\nAddress\n32 byte hex string prefixed with 0x\n\"0xbc33e6e4818f9f2ef77d020b35c24be738213e64d9e58839ee7b4222029610de\"\n0xbc33: string too short bc33e6e4818f9f2ef77d020b35c24be738213e64d9e58839ee7b4222029610de: missing 0x prefix 0xG2B1A39A1514E1D8A7CE45919CFEB4FEE70B4E01: invalid hex char G\n\nObjectID\n32 byte hex string prefixed with 0x\n\"0x1b879f00b03357c95a908b7fb568712f5be862c5cb0a5894f62d06e9098de6dc\"\nSimilar to above\n\nIdentifier\nTypically used for moduleModuleA component of a Move package that defines interaction with on-chain objects. and function names. Encoded as one of the following: A String whose first character is a letter and the remaining characters are letters, digits or underscore. A String whose first character is an underscore, and there is at least one further letter, digit or underscore\n\"function\", \"_function\", \"some_name\", \"____some_name\", \"Another\"\n\"_\": missing trailing underscore, digit or letter, \"8name\": cannot start with digit, \".function\": cannot start with period, \" \": cannot be empty space, \"func name\": cannot have spaces\n\nVector<Move Type> / Option<Move Type>\nHomogeneous vector of aforementioned types including nested vectors of primitive types (only \"flat\" vectors of ObjectIDs are allowed)\n[1,2,3,4]: simple U8 vector [[3,600],[],[0,7,4]]: nested U32 vector [\"0x2B1A39A1514E1D8A7CE45919CFEB4FEE\", \"0x2B1A39A1514E1D8A7CE45919CFEB4FEF\"]: ObjectID vector\n[1,2,3,false]: not homogeneous JSON [1,2,null,4]: invalid elements [1,2,\"7\"]: although Sui allows encoding numbers as strings meaning this array can evaluate to [1,2,7], the array is still ambiguous so it fails the homogeneity check.\n\nVector<u8>\nFor convenience, Sui allows: U8 vectors represented as UTF-8 (and ASCII) strings.\n\"√®ˆbo72 √∂†∆˚–œ∑π2ie\": UTF-8 \"abcdE738-2 _=?\": ASCII\n\nRelated topics\n\ngRPC\nUse the Sui Full Node gRPC API for high-performance, type-safe blockchain data access with Protocol Buffers serialization.\nGraphQL for Sui RPC\nLearn the core concepts for working with GraphQL on Sui RPC, including request headers, query composition with variables and fragments, pagination strategies, query scope, service limits, and the components of the GraphQL and General-purpose Indexer stack.\nJSON-RPC Migration Guide\nChoose between gRPC and GraphQL RPC when migrating from the deprecated JSON-RPC API. Includes a method mapping, decision criteria, and common migration gotchas.\nRPC and Data Providers\nThird-party providers offering Sui gRPC, GraphQL RPC, and Archival Store and Service endpoints.\n\nType coercion reasoning\nType coercion rules\n\nWas this page helpful?","tokens":1749,"crawled_at":1791194414620}
+{"id":10380,"url":"https://docs.compound.xyz/protocol-rewards","domain":"docs.compound.xyz","chapter":"defi_protocols","title":"Compound III Docs | Protocol Rewards","text":"Compound III\nInterest Rates\nCollateral & Borrowing\nLiquidation\nAccount Management\nProtocol Rewards\nERC-4626 Wrapper\nGovernance\nHelper Functions\n\nProtocol Rewards\nReward Accrual Tracking\nGet Reward Accrued\nClaim Rewards\n\nProtocol Rewards\nCompound III has a built-in system for tracking rewards for accounts that use the protocol. The full history of accrual of rewards are tracked for suppliers and borrowers of the base asset. The rewards can be any ERC-20 token. In order for rewards to accrue to Compound III accounts, the configuration’s baseMinForRewards threshold for total supply of the base asset must be met.\nReward Accrual Tracking\nThe reward accrual is tracked in the Comet contract and rewards can be claimed by users from an external Comet Rewards contract. Rewards are accounted for with up to 6 decimals of precision.\nComet\nfunction baseTrackingAccrued(address account) external view returns (uint64);\n\nRETURNS: Returns the amount of reward token accrued based on usage of the base asset within the protocol for the specified account, scaled up by 10 ^ 6.\nSolidity\nComet comet = Comet(0xCometAddress);\nuint64 accrued = comet.baseTrackingAccrued(0xAccount);\n\nEthers.js v5.x\nconst comet = new ethers.Contract(contractAddress, abiJson, provider);\nconst accrued = await comet.callStatic.baseTrackingAccrued('0xAccount');\n\nGet Reward Accrued\nThe amount of reward token accrued but not yet claimed for an account can be fetched from the external Comet Rewards contract.\nComet Rewards\nstruct RewardOwed {\naddress token;\nuint owed;\n}\n\nfunction getRewardOwed(address comet, address account) external returns (RewardOwed memory)\n\nRETURNS: Returns the amount of reward token accrued but not yet claimed, scaled up by 10 to the “decimals” integer in the reward token’s contract.\nSolidity\nCometRewards rewards = CometRewards(0xRewardsAddress);\nRewardOwed reward = rewards.getRewardOwed(0xCometAddress, 0xAccount);\n\nEthers.js v5.x\nconst rewards = new ethers.Contract(contractAddress, abiJson, provider);\nconst [ tokenAddress, amtOwed ] = await rewards.callStatic.getRewardOwed(cometAddress, accountAddress);\n\nClaim Rewards\nAny account can claim rewards for a specific account. Account owners and managers can also claim rewards to a specific address. The claim functions are available on the external Comet Rewards contract.\nComet Rewards\nfunction claim(address comet, address src, bool shouldAccrue) external\n\nfunction claimTo(address comet, address src, address to, bool shouldAccrue) external\n\ncomet: The address of the Comet contract.\nsrc: The account in which to claim rewards.\nto: The account in which to transfer the claimed rewards.\nshouldAccrue: If true, the protocol will account for the rewards owed to the account as of the current block before transferring.\nRETURN: No return, reverts on error.\nSolidity\nCometRewards rewards = CometRewards(0xRewardsAddress);\nrewards.claim(0xCometAddress, 0xAccount, true);\n\nEthers.js v5.x\nconst rewards = new ethers.Contract(contractAddress, abiJson, provider);\nawait rewards.claim(cometAddress, accountAddress, true);","tokens":767,"crawled_at":1791194419135}
+{"id":10381,"url":"https://www.metaplex.com/docs/smart-contracts/core/plugins/autograph","domain":"www.metaplex.com","chapter":"docs","title":"Autograph Plugin | Metaplex Core","text":"The Autograph Plugin allows anyone to add their signature and a message to an Asset or Collection. Perfect for collectible signatures from artists, celebrities, or community members.\nWhat You'll Learn\nEnable autographs on Assets and Collections\nAdd your signature to an Asset\nRemove autographs as the owner\nUnderstand autograph permissions\n\nSummary\nThe Autograph plugin is an Owner Managed plugin that stores signatures with messages. Once enabled, anyone can add their signature. The owner can remove any autograph.\nOwner adds the plugin (or update authority at mint)\nAnyone can add their own signature\nOnly owner/delegate can remove autographs\nAutographers cannot remove their own signature\nAssets inherit autographs from their Collection\nOut of Scope\nCreator verification (use Verified Creators), royalties, and automatic signature validation.\nQuick Start\nJump to: Add Plugin · Add Autograph · Remove Autograph\nOwner adds the Autograph plugin to enable signatures\nAnyone can add their signature with updatePlugin\nOwner can remove any autograph\nAutograph vs Verified Creators\nFeatureAutographVerified Creators\nWho can sign\nAnyone\nOnly listed creators\n\nPermission to enable\nOwner\nUpdate authority\n\nSelf-removal\n❌ Cannot remove own\n✅ Can unverify self\n\nPurpose\nCollectible signatures\nProve creatorship\n\nBest for\nFan engagement, events\nTeam attribution\n\nUse Autograph for collectible signatures (like autographed memorabilia).\n\nUse Verified Creators for proving who created the Asset.\n\nCommon Use Cases\nCelebrity autographs: Artists sign NFTs at events\nFan engagement: Community members sign limited edition pieces\nAuthentication: Real-world item creators sign digital twins\nEvent memorabilia: Conference speakers sign event NFTs\nCharity auctions: Multiple celebrities sign charity NFTs To add a autograph some conditions have to be met:\nThe autograph plugin must be added already.\nThe signer may only add their own address.\nThe existing list have to be passed along with the added signature using the updatePlugin function.\nThere is no existing Autograph by that signer yet.\nAs soon as the autograph plugin has been added by the owner everyone can add their signature. It can again be removed by the owner at any time.\n\nWorks With\n\nMPL Core Asset\n✅\n\nMPL Core Collection\n✅\n\nAssets inherit Autographs from the Collection.\n\nArguments\nThe autograph Plugin requires the following arguments in a signatures Array:\nArgValue\naddress\npublicKey\n\nmessage\nstring\n\nAdding the autograph Plugin to an Asset code example\nAdding a autograph Plugin to an MPL Core Asset as the owner\n\nimport {\n\naddPlugin,\n\n} from '@metaplex-foundation/mpl-core'\n\nawait addPlugin(umi, {\n\nasset: asset.publicKey,\n\nplugin: {\n\ntype: 'Autograph',\n\nsignatures: [\n\n{\n\naddress: umi.identity.publicKey,\n\nmessage: 'Your Message',\n\n},\n\n},\n\n}).sendAndConfirm(umi)\n\nAdding an Autograph to an Asset code example\nAdding a Autograph to an MPL Core Asset\n\nimport { updatePlugin, fetchAsset } from '@metaplex-foundation/mpl-core'\n\nconst asset = await fetchAsset(umi, assetAddress.publicKey, {\n\nskipDerivePlugins: false,\n\n})\n\n// The new autograph that you want to add\n\nconst newAutograph = {\n\naddress: umi.identity.publicKey,\n\nmessage: \"your message\"\n\n}\n\n// Add the new autograph to the existing signatures array\n\nconst updatedAutographs = [...asset.autograph.signatures, newAutograph]\n\nawait updatePlugin(umi, {\n\nasset: asset.publicKey,\n\nplugin: {\n\ntype: 'Autograph',\n\n// This should contain all autographs that you do not want to remove\n\nsignatures: updatedAutographs,\n\n},\n\nauthority: umi.identity,\n\n}).sendAndConfirm(umi)\n\nRemoving an Autograph from an Asset code example\nRemoving a Autograph from an MPL Core Asset\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { updatePlugin, fetchAsset } from '@metaplex-foundation/mpl-core'\n\nconst asset = await fetchAsset(umi, assetAddress.publicKey, {\n\nskipDerivePlugins: false,\n\n})\n\n// The Publickey of the autograph that you want to remove\n\nconst publicKeyToRemove = publicKey(\"abc...\")\n\nconst autographsToKeep = asset.autograph.signatures.filter(\n\n(autograph) => autograph.address !== publicKeyToRemove\n\n);\n\nawait updatePlugin(umi, {\n\nasset: asset.publicKey,\n\nplugin: {\n\ntype: 'Autograph',\n\n// This should contain all Autographs that you do not want to remove\n\nsignatures: autographsToKeep,\n\n},\n\nauthority: umi.identity, // Should be the owner of the asset\n\n}).sendAndConfirm(umi)\n\nAdding the autograph Plugin to a Collection code example\nAdd autograph Plugin to Collection\n\nimport { addCollectionPlugin } from '@metaplex-foundation/mpl-core'\n\nawait addCollectionPlugin(umi, {\n\ncollection: collection.publicKey,\n\nplugin: {\n\ntype: 'Autograph',\n\nsignatures: [\n\n{\n\naddress: umi.identity.publicKey,\n\nmessage: 'Your Message',\n\n},\n\n},\n\n}).sendAndConfirm(umi)\n\nCommon Errors\nPlugin not added\nThe Autograph plugin must be added by the owner before anyone can add autographs.\nAutograph already exists\nThis address has already signed this Asset. Each address can only add one autograph.\nCannot remove own autograph\nAutographers cannot remove their own signature (unless they are also the owner or autograph delegate).\nNotes\nAnyone can add their signature once the plugin is enabled\nOnly the owner or autograph delegate can remove autographs\nAutographers cannot remove their own signature\nAssets inherit autographs from their Collection\nEach address can only sign once per Asset\nQuick Reference\nPermission Matrix\nActionOwnerAnyoneAutographer\nAdd plugin\n✅\n❌\n❌\n\nAdd own autograph\n✅\n✅\n✅\n\nRemove any autograph\n✅\n❌\n❌\n\nRemove own autograph\n✅ (as owner)\n❌\n❌\n\nAutograph Lifecycle\nStepActionWho\n1\nAdd Autograph plugin\nOwner\n\n2\nAdd autograph\nAnyone\n\n3\nRemove autograph (optional)\nOwner only\n\nFAQ\nHow is this different from Verified Creators?\nVerified Creators is for proving creatorship and is managed by the update authority. Autograph is for collectible signatures from anyone (like getting an autograph at an event).\nCan someone add multiple autographs?\nNo. Each address can only add one autograph per Asset. Attempting to add a second autograph from the same address will fail.\nCan I remove my own autograph?\nNo. Only the owner or autograph delegate can remove autographs. This prevents someone from signing and then immediately removing it.\nDo I need the owner's permission to add an autograph?\nNo. Once the owner enables the Autograph plugin, anyone can add their signature. The owner doesn't need to approve individual autographs.\nWhat happens to autographs when an Asset is transferred?\nAutographs remain on the Asset. They are permanent records of who signed, regardless of ownership changes.\nGlossary\nTermDefinition\nAutograph\nA signature with optional message added to an Asset\n\nAutographer\nAddress that added their signature\n\nAutograph Delegate\nAddress with permission to remove autographs\n\nSignatures Array\nList of all autographs on an Asset\n\nOwner Managed\nPlugin type where the owner controls addition\n\nRelated Plugins\nVerified Creators - Prove creatorship (authority managed)\nAttributes - Store on-chain data\nImmutableMetadata - Lock metadata permanently","tokens":1764,"crawled_at":1791194441228}
+{"id":10382,"url":"https://gov.uniswap.org/t/blockfuls-delegate-platform/25765","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Blockful's Delegate Platform - Delegation Pitch - Uniswap Governance","text":"Blockful's Delegate Platform\n\nDelegation Pitch\n\nblockful\n\nAugust 6, 2025, 5:25pm\n\n1\n\nContact & Delegation Address Information\n\nDelegate ENS Address: gov.blockful.eth\n\nDelegate Address: 0x1F3D3A7A9c548bE39539b39D7400302753E20591\n\nEmail: contact@blockful.io\n\nWebsite: https://blockful.io\n\nTwitter: https://twitter.com/blockful_io\n\nOur Voting History: https://www.tally.xyz/profile/gov.blockful.eth\n\nAbout Us\n\nblockful is a fully independent and bootstrapped governance-security company dedicated to “holistic governance security, with and beyond code.” We combine our anticapture framework, years as a web3 development company, data dashboards, and social-layer analysis to help DAOs evolve from fragile to resilient systems.\n\nDelegate Statement\n\nOur mission is to safeguard Uniswap’s long-term security.\n\nWe have already audited UNI governance (funded from a UF grant), mapped risk metrics, and shipped a public dashboard (https://anticapture.com/uni) so every community member can see attack threats before they strike. Delegating to blockful means turning these insights into proactive, security-first votes.\n\nReasons for Wanting to Be a Delegate\n\nSecurity leadership – we created the Anticapture Framework and are currently service providers for ENS DAO to implement its findings, enhancing our governance.\n\nData transparency – our dashboards surface token-distribution shifts, implementation safeguards costs, and governance health so voters act on facts, not vibes.\n\nPublic-goods mindset – all of our systems are OSS;\n\nCritical Eye - we believe there are a series of checks and balances necessary for incentives inside a DAO not to become inefficient. We want to help Uniswap stay healthy by calling out what’s needed.\n\nSkills & Areas of Expertise\n\nGovernance security\n\nSmart-contract development\n\nCommunity and Incentives\n\nCross-DAO participation\n\nDisclosure of Conflicts of Interest\n\nblockful currently serves as a delegate for Arbitrum, Optimism, ENS, Scroll. We are fully bootstrapped with no investor pressure behind the scenes to bias our positioning.\n\nblockful\n\nOctober 11, 2025, 2:11pm\n\n2\n\nGrow Uniswap on Plasma\n\nWe voted for Uniswap to allocate $250K to the Plasma incentive program.\n\nThe rewards could bring more capital, attention, and liquidity to Uniswap on Plasma. Given its importance in the DeFi market in recent weeks, it is an expense that could bring short-term returns for Uniswap.\n\nblockful\n\nMay 28, 2026, 7:14pm\n\n3\n\nProtocol Fee Expansion: Vote 3\n\nWe voted FOR this proposal because it is a consistent extension of Uniswap’s already-approved fee framework.\n\nThe proposal does not change the protocol fee policy. It simply expands the existing fee collection and UNI burn infrastructure to BNB Chain and Polygon, while completing Celo’s activation after a previous execution issue.\n\nSupporting this proposal helps align Uniswap’s fee implementation with its multichain reality. Since the protocol already operates across multiple networks, the fee infrastructure should be able to follow that footprint in a standardized way.\n\nWe also recognize that expanding to more chains adds new execution paths and infrastructure dependencies, so governance should continue monitoring the system closely.\n\nblockful\n\nMay 28, 2026, 7:26pm\n\n4\n\nReturn 12.5M Delegated Tokens to the Governance Timelock\n\nWe voted FOR this proposal.\n\nThe proposal withdraws 12.5M delegated UNI from the Uniswap Foundation and other governance members, such as Anode, kpk, and Axia. These delegations currently come from the Uniswap DAO treasury.\n\nWe supported the proposal because Uniswap governance is now in a different position than it was before the creation of DUNI, the Uniswap DUNA legal structure approved on August 30, 2025.\n\nSince then, delegated UNI has grown significantly. In less than three months, the amount of delegated UNI increased by 17.1%, adding 33M delegated tokens. In October alone, 31.9M UNI were delegated, mostly from addresses delegating their governance tokens for the first time.\n\nThis suggests that DUNI helped provide more legal certainty for delegates and encouraged more UNI holders to participate in governance, either directly or through delegation.\n\nAs a result, Uniswap no longer needs to rely as heavily on delegates whose voting power comes from the DAO treasury. The DAO now has large UNI holders actively participating in governance, bringing more skin in the game to the delegate set.\n\nThis is healthier than relying on treasury-backed delegation, which can create incentive misalignment between delegates and UNI holders.\n\nHowever, we also recognize the main tradeoff: Uniswap may now depend on a smaller number of large delegates to reach quorum. Without the participation of professional delegates, the DAO will need to remain aligned and coordinate with UNI whales to avoid quorum issues.\n\nEven with this nuance, we believe the proposal is a positive step toward a more aligned governance structure, where voting power increasingly comes from UNI holders rather than the DAO treasury itself.\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nBlockworks Research Delegate Platform\n\nDelegation Pitch\n\n0\n\n1484\n\nMay 11, 2023\n\nDAOplomats Delegation Platform\n\nDelegation Pitch\n\n49\n\n2913\n\nJuly 18, 2026\n\nCuria Delegate Platform\n\nDelegation Pitch\n\n53\n\n2385\n\nJuly 23, 2026\n\nPEPO Delegate Platform\n\nDelegation Pitch\n\n23\n\n1763\n\nMay 5, 2025\n\nSEEDGov Delegate Platform\n\nDelegation Pitch\n\n76\n\n3514\n\nMay 5, 2026","tokens":1359,"crawled_at":1791194438126}
+{"id":10383,"url":"https://docs.compound.xyz/v2","domain":"docs.compound.xyz","chapter":"defi_protocols","title":"Compound v2 Documentation","text":"Compound II\ncTokens\nComptroller\nGovernance\nPrice Feed\nSecurity\n\nGetting Started\nGuides\nNetworks\nProtocol Math\n\nGetting Started\nIntroduction to Compound v2\nCompound III is now live, you're currently viewing Compound v2 documentation. Compound III Documentation\n\nThe Compound protocol is based on the Compound Whitepaper (2019); the codebase is open-source, and maintained by the community.\nThe app.compound.xyz interface is open-source, and maintained by the community.\nPlease join the #development room in the Compound community Discord server; Compound Labs and members of the community look forward to helping you build an application on top of Compound. Your questions help us improve, so please don’t hesitate to ask if you can’t find what you are looking for here.\nGuides\nSetting up an Ethereum Development Environment\nSupplying Assets to the Compound Protocol\nBorrowing Assets from the Compound Protocol\nCreate a Compound API with Infura\nBuilding a Governance Interface\nDelegation & Voting\nContributing to the Protocol\nNetworks\nThe Compound Protocol is currently deployed on the following networks:\nMainnet\nGoerli\n\nEthereum Mainnet - Compound v2\nProtocol Contracts\ncAAVE\n0xe65c…D06c\n\ncBAT\n0x6C8c…0E4E\n\ncCOMP\n0x70e3…E8e4\n\ncDAI\n0x5d3a…3643\n\ncETH\n0x4Ddc…0ED5\n\ncFEI\n0x7713…3F67\n\ncLINK\n0xFAce…B0c7\n\ncMKR\n0x95b4…325b\n\ncREP\n0x1580…95c1\n\ncSAI\n0xF5DC…44dC\n\ncSUSHI\n0x4B01…c9d7\n\ncTUSD\n0x1239…Ad86\n\ncUNI\n0x35A1…D550\n\ncUSDC\n0x39AA…7563\n\ncUSDP\n0x0411…925D\n\ncUSDT\n0xf650…dCC9\n\ncWBTC\n0xC11b…A7F4\n\ncWBTC2\n0xccF4…DD6a\n\ncYFI\n0x80a2…3946\n\ncZRX\n0xB331…d407\n\nCOMP\n0xc00e…6888\n\nComptroller\n0x3d98…Cd3B\n\nGovernance\n0xc0Da…6529\n\nTimelock\n0x6d90…3925\n\nEthereum Goerli Testnet - Compound v2\nProtocol Contracts\ncCOMP\n0x0fF5…F1Cd\n\ncDAI\n0x0545…7b2a\n\ncETH\n0x6407…dbde\n\ncUNI\n0x2073…b1A5\n\ncUSDC\n0x7350…F493\n\ncUSDT\n0x5A74…b716\n\ncWBTC\n0xDa6F…3C8f\n\nCOMP\n0x3587…0ba4\n\nDAI\n0x2899…13cC\n\nUNI\n0x208F…08cC\n\nUSDC\n0x0786…a37F\n\nUSDT\n0x79C9…d446\n\nWBTC\n0xAAD4…dC19\n\nCompoundLens\n0x04EC…CbB7\n\nUnitroller\n0x3cBe…4d78\n\nComptroller\n0x05Df…8621\n\nFauceteer\n0x7544…938f\n\nGovernorBravo\n0xa3Fb…45d3\n\nMaximillion\n0xD493…Defb\n\nPriceOracle\n0x65F1…C776\n\nTimelock\n0x8Fa3…1399\n\nYou can also see a full list of all deployed contract addresses here.\nProtocol Math\nThe Compound protocol contracts use a system of exponential math, ExponentialNoError.sol, in order to represent fractional quantities with sufficient precision.\nMost numbers are represented as a mantissa, an unsigned integer scaled by 1 * 10 ^ 18, in order to perform basic math at a high level of precision.\ncToken and Underlying Decimals\nPrices and exchange rates are scaled by the decimals unique to each asset; cTokens are ERC-20 tokens with 8 decimals, while their underlying tokens vary, and have a public member named decimals.\ncToken cToken Decimals Underlying Underlying Decimals\ncETH\n8\nETH\n18\n\ncAAVE\n8\nAAVE\n18\n\ncBAT\n8\nBAT\n18\n\ncCOMP\n8\nCOMP\n18\n\ncDAI\n8\nDAI\n18\n\ncFEI\n8\nFEI\n18\n\ncLINK\n8\nLINK\n18\n\ncMKR\n8\nMKR\n18\n\ncSUSHI\n8\nSUSHI\n18\n\ncTUSD\n8\nTUSD\n18\n\ncUNI\n8\nUNI\n18\n\ncUSDC\n8\nUSDC\n6\n\ncUSDP\n8\nUSDP\n18\n\ncUSDT\n8\nUSDT\n6\n\ncWBTC\n8\nWBTC\n8\n\ncYFI\n8\nYFI\n18\n\ncZRX\n8\nZRX\n18\n\nInterpreting Exchange Rates\nThe cToken Exchange Rate is scaled by the difference in decimals between the cToken and the underlying asset.\noneCTokenInUnderlying = exchangeRateCurrent / (1 * 10 ^ (18 + underlyingDecimals - cTokenDecimals))\n\nHere is an example of finding the value of 1 cBAT in BAT with Web3.js JavaScript.\nconst cTokenDecimals = 8; // all cTokens have 8 decimal places\nconst underlying = new web3.eth.Contract(erc20Abi, batAddress);\nconst cToken = new web3.eth.Contract(cTokenAbi, cBatAddress);\nconst underlyingDecimals = await underlying.methods.decimals().call();\nconst exchangeRateCurrent = await cToken.methods.exchangeRateCurrent().call();\nconst mantissa = 18 + parseInt(underlyingDecimals) - cTokenDecimals;\nconst oneCTokenInUnderlying = exchangeRateCurrent / Math.pow(10, mantissa);\nconsole.log('1 cBAT can be redeemed for', oneCTokenInUnderlying, 'BAT');\n\nThere is no underlying contract for ETH, so to do this with cETH, set underlyingDecimals to 18.\nTo find the number of underlying tokens that can be redeemed for cTokens, multiply the number of cTokens by the above value oneCTokenInUnderlying.\nunderlyingTokens = cTokenAmount * oneCTokenInUnderlying\n\nCalculating Accrued Interest\nInterest rates for each market update on any block in which the ratio of borrowed assets to supplied assets in the market has changed. The amount interest rates are changed depends on the interest rate model smart contract implemented for the market, and the amount of change in the ratio of borrowed assets to supplied assets in the market.\nSee the interest rate data visualization notebook on Observable to visualize which interest rate model is currently applied to each market.\nHistorical interest rates can be retrieved from the MarketHistoryService API.\nInterest accrues to all suppliers and borrowers in a market when any Ethereum address interacts with the market’s cToken contract, calling one of these functions: mint, redeem, borrow, or repay. Successful execution of one of these functions triggers the accrueInterest method, which causes interest to be added to the underlying balance of every supplier and borrower in the market. Interest accrues for the current block, as well as each prior block in which the accrueInterest method was not triggered (no user interacted with the cToken contract). Interest compounds only during blocks in which the cToken contract has one of the aforementioned methods invoked.\nHere is an example of supply interest accrual:\nAlice supplies 1 ETH to the Compound protocol. At the time of supply, the supplyRatePerBlock is 37893605 Wei, or 0.000000000037893605 ETH per block. No one interacts with the cEther contract for 3 Ethereum blocks. On the subsequent 4th block, Bob borrows some ETH. Alice’s underlying balance is now 1.000000000151574420 ETH (which is 37893605 Wei times 4 blocks, plus the original 1 ETH). Alice’s underlying ETH balance in subsequent blocks will have interest accrued based on the new value of 1.000000000151574420 ETH instead of the initial 1 ETH. Note that the supplyRatePerBlock value may change at any time.\nCalculating the APY Using Rate Per Block\nThe Annual Percentage Yield (APY) for supplying or borrowing in each market can be calculated using the value of supplyRatePerBlock (for supply APY) or borrowRatePerBlock (for borrow APY) in this formula:\nRate = cToken.supplyRatePerBlock(); // Integer\nRate = 37893566\nETH Mantissa = 1 * 10 ^ 18 (ETH has 18 decimal places)\nBlocks Per Day = 7200 (12 seconds per block)\nDays Per Year = 365\n\nAPY = ((((Rate / ETH Mantissa * Blocks Per Day + 1) ^ Days Per Year)) - 1) * 100\n\nHere is an example of calculating the supply and borrow APY with Web3.js JavaScript:\nconst ethMantissa = 1e18;\nconst blocksPerDay = 7200; // 12 seconds per block\nconst daysPerYear = 365;\n\nconst cToken = new web3.eth.Contract(cEthAbi, cEthAddress);\nconst supplyRatePerBlock = await cToken.methods.supplyRatePerBlock().call();\nconst borrowRatePerBlock = await cToken.methods.borrowRatePerBlock().call();\nconst supplyApy = (((Math.pow((supplyRatePerBlock / ethMantissa * blocksPerDay) + 1, daysPerYear))) - 1) * 100;\nconst borrowApy = (((Math.pow((borrowRatePerBlock / ethMantissa * blocksPerDay) + 1, daysPerYear))) - 1) * 100;\nconsole.log(`Supply APY for ETH ${supplyApy} %`);\nconsole.log(`Borrow APY for ETH ${borrowApy} %`);\n\nCalculating the APR Using Rate Per Block\nHere is an example of calculating the supply and borrow APR with Web3.js JavaScript:\nconst ethMantissa = 1e18;\nconst blocksPerYear = 5 * 60 * 24 * 365; // 12 seconds per block\nconst daysPerYear = 365;\n\nconst cToken = new web3.eth.Contract(cZrxAbi, cZrxAddress);\nconst supplyRatePerBlock = await cToken.methods.supplyRatePerBlock().call();\nconst borrowRatePerBlock = await cToken.methods.borrowRatePerBlock().call();\nconst supplyApr = supplyRatePerBlock / ethMantissa * blocksPerYear * 100;\nconst borrowApr = borrowRatePerBlock / ethMantissa * blocksPerYear * 100;\nconsole.log(`Supply APR ${(supplyApr).toFixed(3)} %`);\nconsole.log(`Borrow APR ${(borrowApr).toFixed(3)} %`);","tokens":2029,"crawled_at":1791194440409}
+{"id":10384,"url":"https://www.getfoundry.sh/forge/cloning","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Cloning verified contracts – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nCloning verified contracts\n\nforge clone downloads verified Solidity source and compiler settings from a block explorer, initializes a Forge project, compiles it, and writes deployment metadata to .clone.meta.\n\nBy default, Forge clones the exact address you provide. Add --implementation when the address is a proxy and you want the implementation reported by Etherscan.\n\nPrerequisites\n\nAn explorer-verified contract.\n\nAn Etherscan API key, supplied through ETHERSCAN_API_KEY or --etherscan-api-key.\n\nThe contract's chain name or chain ID when it is not on Ethereum mainnet.\n\nClone the contract at an address\n\nPass the contract address and the directory that Forge should create:\n\n$ forge clone \\\n--chain mainnet \\\n0xC02aB1A5eaA8d1B114EF786D9bde108cD4364359 \\\nsparklend-usds\n\nThis clones the verified contract at the supplied address. If the address is a proxy, the generated project contains the proxy source unless you request its implementation explicitly.\n\nClone a proxy implementation\n\nAdd --implementation to clone the implementation address reported in the proxy's Etherscan metadata:\n\n$ forge clone \\\n--implementation \\\n--chain mainnet \\\n0xC02aB1A5eaA8d1B114EF786D9bde108cD4364359 \\\nsparklend-usds\n\nForge uses the resolved implementation for:\n\nDownloaded source code and compiler settings.\n\nContract creation data and constructor arguments.\n\nThe compiled storage layout.\n\nThe address, contract name, and source path recorded in .clone.meta.\n\nIf Etherscan does not mark the supplied address as a proxy, --implementation clones the supplied address normally.\n\nUnderstand implementation resolution\n\nImplementation resolution follows one Etherscan metadata link. Forge fetches the implementation reported for the supplied proxy and stops there, even if that implementation is also marked as a proxy. This avoids following an unrelated delegate-call target reported by the explorer.\n\nThe resolved target must be a Solidity contract. A Vyper proxy can still resolve to a Solidity implementation because Forge only compiles the selected target.\n\nWhen verified sources remain under lib, Forge creates an import-only entry point such as src/Clone.sol so the compiler discovers the cloned target. The downloaded library sources remain under lib.\n\n--implementation is supported only with Etherscan. It cannot be combined with --source sourcify or --sourcify-url, and resolution depends on the proxy metadata returned by the explorer.\n\nNext steps\n\nSee the forge clone reference for all command options.\n\nCompare storage layouts when upgrading contracts.\n\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":661,"crawled_at":1791194446377}
+{"id":10385,"url":"https://gov.uniswap.org/t/cp0x-delegate-platform/25321","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Cp0x Delegate Platform - Delegation Pitch - Uniswap Governance","text":"Cp0x Delegate Platform\n\nDelegation Pitch\n\ncp0x\n\nMarch 3, 2025, 4:18pm\n\n1\n\nDelegate Name: cp0x aka cp0x.eth\n\nForum: cp0x\n\nDelegate Address: 0x6f9BB7e454f5B3eb2310343f0E99269dC2BB8A1d\n\nTwitter: https://x.com/cp0xdotcom\n\nLanguages: English, Portuguese, Russian\n\nVoting history: https://boardroom.io/voter/0x6f9BB7e454f5B3eb2310343f0E99269dC2BB8A1d\n\nLinks: cp0x.com · delegations · staking · Telegram · YouTube\n\nAbout\n\ncp0x is a crypto community working in the space since 2016: community, infrastructure, education.\n\nWe take part in governance across 20+ DAOs, run a liquidity hub with curated DeFi deals and trading competitions, build permissionless interfaces to DeFi protocols when official frontends introduce restrictions, and run validators, sequencers, operators and indexers in various networks. We also run a YouTube channel where we talk to founders and developers about protocols and the market.\n\nHow we vote\n\nFairness. We stand against reckless spending and look for solutions that benefit everyone equally.\n\nTransparency. Our decisions are consistent.\n\nDecentralisation. We support what reduces reliance on single players or foundations.\n\nWe verify proposals ourselves rather than relying on their description. We vote against what centralises power, obscures spending or spends without justification. Where there is not enough information we abstain, and where the consequences are ambiguous we take it back to the community.\n\nWe agree to follow Principles for Uniswap DAO in our messages and voting.\n\nGLI -- Treasury Delegation Round 2 Applications\n\ncp0x\n\nMarch 3, 2025, 4:31pm\n\n2\n\n[Temp Check] Uniswap Unleashed\n\nimage1272×423 53.8 KB\n\nUniswap Foundation (UF) is requesting\n\n$95.4 million in grants (for 2 years):\n\n$33.7 million for developers\n\n$33.7 million for management\n\n$33.7 million for infrastructure\n\nand other small things…\n\n$25.1 million for UF itself (for their work, while they write that they are a team of 16 people and plan to hire 12 more) so the employee salary will be about $37,350 per month excluding vesting. With vesting $48,172 per month\n\nAnd also the detailed calculations do not match what they requested - 25 million and 38 million - a difference of 13 million.\n\nIf this proposal were divided into 2 parts, I would vote for grants, but against such expenses for UF\n\nVote: AGAINST\n\nPlatform: Snapshot\n\n1 Like\n\ncp0x\n\nMarch 3, 2025, 4:37pm\n\n3\n\n[Temp Check] Unichain and Uniswap v4 Liquidity Incentives\n\nAdditional request for grants (in addition to what was asked in the previous proposal) to stimulate Unichain and v4.\n\n24 million for incentives to transfer liquidity from v3 to v4 by 23 billion in six months.\n\n21 million on Unichain. Optimism rollup - stimulation of pools on this chain.\n\nAs in the previous proposal, the combination of two grants that are not directly related, which may have different opinions, raises doubts.\n\nIf there are no questions about the first program, then the second is confusing in that it is unclear who will be the user of this new chain, where there will not be much liquidity initially, which means that slippage will be higher (which is of course compensated by incentives, but when they run out - no one will need this chain). What is the competitive advantage? After all, if there is none, then we will simply spend money without the desired effect.\n\nThese proposals need to be divided, like the previous one. It is a bad idea to mix good and bad proposals and thereby accept something that is not needed by the community.\n\nVote: AGAINST\n\nPlatform: Snapshot\n\n1 Like\n\ncp0x\n\nMarch 3, 2025, 4:45pm\n\n4\n\nUniswap Delegate Reward Initiative - Cycle 3\n\nUniswap rewards delegates under the following conditions (if you are in the top 15 delegates):\n\nPoints:\n\nSnapshot votes > 90% - 3 points\n\nTally votes > 90% - 4 points\n\nProposal authorship - 3 points\n\nCommunity call participation - 1 point\n\nParticipate in 90% of votes (both Snapshot and Tally) in the last 90 days\n\nWrite your vote rationale in the thread\n\nParticipate in community calls\n\nI consider such conditions for distributing rewards to be fair, depending on your contribution to the DAO.\n\nVote: FOR\n\nPlatform: Uniswap Agora\n\ndevinwalsh\n\nMarch 3, 2025, 9:44pm\n\n5\n\nWe have cash on hand. So the amount we request from the Treasury takes that into account, we subtract cash on hand from our projected budget to get the ask to the Treasury. That accounts for the difference there.\n\n1 Like\n\ncp0x\n\nMay 6, 2025, 11:54pm\n\n6\n\nUAC Renewal S4\n\nExtending the committee that is responsible for overseeing cross-chain developments\n\nThere are still 5 people on the committee, but they want to increase their hours, like there are more responsibilities, like managing a feedback group on the forum, etc.\n\nIn general, they want to raise the salary by about 30%.\n\nBudget: $320k at a rate of $200 per hour (Well, you know that I have a bad attitude to such a rate) and 50k for operating expenses (which is also expensive)\n\nI would keep the committee itself, as well as their salary, which is already high, but I don’t want to pay for an increase.\n\nVote: AGAINST\n\nPlatform: Snapshot\n\ncp0x\n\nMay 6, 2025, 11:57pm\n\n7\n\nApproved Budgets Rebalancing (S4)\n\nDue to the token price drop, there are insufficient funds in the accounts of various Uniswap groups and initiatives\n\nThere is a very detailed analysis of all programs, costs and how much each is missing.\n\nIn total, it is $280k. The main part goes to cover the deficit in the Tally Grant program, where the funds were actually used to develop Tally.\n\nConsidering that the balance of the programs is now about $2 million, the shortage is not that big with such a drop in the token\n\nI really liked the structure, where it is written in great detail how, how much and why additional funding is needed. An excellent example of how to do it right.\n\nVote: FOR\n\nPlatform: Snapshot\n\ncp0x\n\nMay 7, 2025, 12:02am\n\n8\n\n[Temp Check/Revised] Treasury Delegation Round 2\n\nThis is a reworking of a month-old proposal, where Uniswap delegates 1-1.5 million UNI to the top 10 delegates.\n\nI was against it then and essentially nothing has changed.\n\nNow they have changed the term of office - review after 9 months (and it was 12), which is insignificant\n\nThey give 1 million to the top, and there will also be a vote on who gets another 500k.\n\nIt’s all the same\n\nThey write that this is how they fight the quorum problem. This certainly solves the problem, but it is a temporary solution and may lead to the DAO being managed only by the top 10 delegates\n\nVote: AGAINST\n\nPlatform: Snapshot\n\ncp0x\n\nMay 7, 2025, 12:07am\n\n9\n\n[TEMP CHECK] BoB Uniswap v3 Incentives Package\n\nBoB - Build on Bitcoin network with smart contracts on EVM, but security on Bitcoin within OP Superchain - their TVL is around $230 million\n\nBoB will allocate $500,000 to Uniswap to increase liquidity for 6 months + incentives from Babylon and possible other partners\n\nAsk for $375,000 from Uniswap for pools (which may be revised)\n\nwBTC/USDT\n\nwBTC/wETH\n\nUSDT/USDC\n\nwBTC/LBTC\n\nI think this is a good initiative, as it allows to occupy a possibly large market associated with Bitcoin\n\nVote: FOR\n\nPlatform: Snapshot\n\ncp0x\n\nMay 7, 2025, 1:20am\n\n10\n\n[TEMP CHECK] Establish Uniswap v4 Licensing Process\n\nEveryone wants to implement Uni v4 faster, therefore:\n\nsince the license belongs to the DAO, the Uniswap Foundation needs permission to deploy.\n\nPlus they also want to implement and manage the v4deployments.uniswap.eth subdomain to track new deployments\n\nThe idea is good, it is unclear why the rights are not shared with the Uniswap Foundation by default\n\nVote: FOR\n\nPlatform: Snapshot\n\ncp0x\n\nMay 7, 2025, 1:23am\n\n11\n\n[TEMP CHECK] Scaling V4 and Supporting Unichain\n\nThere was already a proposal on this topic, they allocated about 46 million for incentives and for Unichain\n\nNow, on top of that, GFX Labs is asking for money - they want a perpetual license for the implementation of v4, a one-time $250k and $90k for a year (7.5k per month for maintenance), and for this they will deploy Unichain on Oku\n\nConsidering that a lot of money has already been allocated for this, I think it is wrong to single out someone else, and it is worth giving money from the selected budget\n\nVote: AGAINST\n\nPlatform: Snapshot\n\ncp0x\n\nMay 7, 2025, 1:25am\n\n12\n\n[Temp Check] Analytics Hub for Uniswap’s Revitalization and Growth Program\n\n[Temp Check] Analytics Hub for Uniswap’s Revitalization and Growth Program\n\nForse, a company that analyzes blockchains and protocols, offers to give it $60,000 in UNI\n\nIn exchange, they will analyze the profitability of incentives, user retention, etc. They will make a monitoring panel by the beginning of July\n\nThe money is small, but there is a benefit, because Uniswap spends too much on grants and I don’t know - is there any benefit from this\n\nFinally, we will find out the answer to how effective large spending on new chains and grants, incentives is\n\nVote: FOR\n\nPlatform: Snapshot\n\ncp0x\n\nMay 7, 2025, 1:28am\n\n13\n\nFour Chains for Analytics Hub for Uniswap’s Revitalization and Growth Program\n\nThis is a clarification of the previous vote - in which 4 chains to conduct the analysis\n\nI would vote for the most popular and new:\n\nUnichain (the most is spent there)\n\nSei\n\nPolygon zkEVM\n\nI would also look at Sonic, but for some reason there is no such option, although it is one of the currently popular chains and has a large growth\n\nIn the future, it is worth giving a larger choice of chains, because Uniswap is in many chains, it is bad that we cannot choose specific ones, but only from 4.\n\nVote: FOR\n\nPlatform: Snapshot\n\ncp0x\n\nMay 7, 2025, 1:31am\n\n14\n\nBoB Uniswap v3 Incentives Package\n\nIn accordance with the previously completed Snapshot vote, we also support it here\n\nVote: FOR\n\nPlatform: Uniswap Agora\n\ncp0x\n\nMay 7, 2025, 1:32am\n\n15\n\nEstablish Uniswap v4 Licensing Process\n\nIn accordance with the previously completed Snapshot vote, we also support it here\n\nVote: FOR\n\nPlatform: Uniswap Agora\n\ncp0x\n\nMay 25, 2025, 3:12am\n\n16\n\nUniswap Accountability Committee S4 Elections\n\nWe voted against extending UAC S4 because the committee raised their salaries by 30% (at $200 an hour, 8k a month), but the initiative was passed, so it is necessary to carefully approach the selection of representatives\n\nThere are 7 candidates for 5 positions\n\nSov - head of govNERDs at Optimism and was on the grant board for season 6\n\n(last time he took 6th place)\n\nDoo_StableLab - Co-founder of StableLab, head of Sky, on the grants working group at Compound\n\n(last time he took 4th place and became a member)\n\nDonOfDAOs - founder of Event Horizon\n\n(not previously applied)\n\nKevin Nielsen - founder of Boardroom, which was bought by Agora\n\n(last time he took 7th place)\n\nTane - served on the Optimism Grants Board\n\n(last time he took 10th place)\n\nCuria - Varit Ruangsiri, founder\n\n(not previously applied)\n\n404DAO - Cole Schendl, co-founder\n\nAlso served on the grants board at Arbitrum, as part of one Optimism group and the NEAR group\n\n(not previously applied)\n\nI voted for those who specialize specifically in governance and openness of data:\n\nDoo Wan Nam (StableLab) - has a good reputation in many DAOs and will be useful on this committee\n\nKevin Nielsen - also spends a lot of time working in the direction of DAO governance\n\nVote:\n\n– Doo Wan Nam - 50%\n\n– Kevin Nielsen - 50%\n\nPlatform: Snapshot\n\nUAC Season 4 Application\n\ncp0x\n\nAugust 20, 2025, 6:18pm\n\n17\n\nTrial run a Technical Advisory Board (TAB)\n\nIt’s proposed to create a council of technical professionals who will provide an assessment for each proposal.\n\nFor this, they gathered 6 people (I only know one of them - Ben DiFrancesco, who is also actively involved in Arbitrum).\n\nEach will be paid 400 UNI ($3,200), and a delegate will get $6,400, to whom 2.5M UNI will be delegated (why pay a separate person even more than the tech experts, when they could just write their own review and vote with reasoning?).\n\nMost previous proposals were only about transferring UNI and didn’t require any technical analysis (one delegate did an analysis in an entire year).\n\nThis looks like another meaningless milking scheme, and moreover, after reading all the feedback, the author didn’t reply to anything - just waited 1.5 months and launched the vote.\n\nVote: AGAINST\n\nPlatform: Snapshot\n\ncp0x\n\nAugust 20, 2025, 6:23pm\n\n18\n\nUniswap Unichain - USDS and sUSDS Co-Incentives Growth Management Plan\n\nIt’s offered a joint incentive program for the growth of TVL USDS and sUSDS on Unichain\n\nup to $4 million in incentives depending on TVL\n\n1 million - $20M TVL in USDS/sUSDS\n\nup to\n\n4 million - $100M TVL\n\nIt seems a bit too much to me for this. Well, there will be such a TVL for several weeks, they will give away 4 million, and then this chain will not be needed at all\n\nVote: AGAINST\n\nPlatform: Snapshot\n\ncp0x\n\nAugust 20, 2025, 6:28pm\n\n19\n\n[TEMP CHECK] - Etherlink Co-incentives Proposal\n\nEtherlink and Tezos want Uniswap to be the main AMM for Etherlink\n\nThey want Uniswap to invest its $150k in incentives, and they in turn will give $300k for this\n\nThe chain’s TVL has recently grown to $47 million and there is IguanaDEX (with $12 million), from which, apparently, TVL will come to Uniswap due to these incentives.\n\nI don’t like this market capture scheme, but for Uniswap it will be a positive decision\n\nVote: FOR\n\nPlatform: Snapshot\n\ncp0x\n\nAugust 20, 2025, 6:33pm\n\n20\n\nUniswap Delegate Reward Initiative - Cycle 4\n\nUpdating the delegate reward system\n\nFrom what remains the same - the top 15 delegates are also selected (a new application is needed due to other changes)\n\nNew and important, which can really use votes as a skin in the game - namely, for owning 1000 UNI, an additional point will be awarded\n\nThis is an important step in the development of the program for engaging not only delegates, but using personal involvement\n\nVote: FOR\n\nPlatform: Snapshot\n\nnext page →\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nTané Delegate Platform\n\nDelegation Pitch\n\n59\n\n2404\n\nMarch 9, 2026\n\n404 DAO Delegate Platform\n\nDelegation Pitch\n\n39\n\n3283\n\nJanuary 13, 2026\n\nGFX Labs - Delegate Communication Thread\n\nDelegation Pitch\n\n27\n\n1504\n\nDecember 8, 2025\n\nIgnas Delegate Platform\n\nDelegation Pitch\n\n41\n\n1284\n\nMay 25, 2026\n\nAtiselsts.eth Delegate Platform\n\nDelegation Pitch\n\n32\n\n4670\n\nJuly 9, 2026","tokens":3568,"crawled_at":1791194455787}
+{"id":10386,"url":"https://www.metaplex.com/docs/smart-contracts/core/plugins/transfer-delegate","domain":"www.metaplex.com","chapter":"docs","title":"Transfer Delegate Plugin | Metaplex Core","text":"The Transfer Delegate Plugin allows a designated authority to transfer Core Assets on behalf of the owner. Essential for escrowless marketplace sales, game mechanics, and subscription services.\nWhat You'll Learn\nAdd the Transfer Delegate plugin to an Asset\nDelegate transfer authority to a marketplace or program\nExecute transfers as a delegate\nAuthority behavior on transfer\n\nSummary\nThe Transfer Delegate is an Owner Managed plugin that allows a delegate to transfer an Asset. Once delegated, the authority can transfer the Asset to any address without owner approval.\nEnable escrowless marketplace listings\nAuthority is revoked after transfer (one-time use)\nUse Permanent Transfer Delegate for persistent authority\nNo additional arguments required\nOut of Scope\nPermanent transfer authority (see Permanent Transfer Delegate), collection-level transfers, and Token Metadata transfer authority (different system).\nQuick Start\nJump to: Add Plugin · Delegate Authority · Transfer as Delegate\nAdd the Transfer Delegate plugin with the delegate address\nThe delegate can now transfer the Asset once\nAfter transfer, the authority is automatically revoked\nOverview\nThe Transfer Delegate Plugin is a Owner Managed plugin that allows the authority of the Transfer Delegate Plugin to transfer the Asset at any time. The Transfer Plugin will work in areas such as:\nEscrowless sale of the Asset: Transfer NFTs directly to buyers without needing an escrow account\nGaming scenario where the user swaps/loses their asset based on an event: Automatically transfer assets when game events occur\nSubscription services: Transfer NFTs as part of a subscription service\nWhen to Use Transfer vs Permanent Transfer Delegate\nUse CaseTransfer DelegatePermanent Transfer Delegate\nMarketplace listings\n✅ Best choice\n❌ Too risky\n\nOne-time transfers\n✅ Best choice\n❌ Overkill\n\nRental returns\n❌ Single use\n✅ Best choice\n\nGame asset swaps\n✅ Best choice\n✅ Also works\n\nAuthority persists on transfer\n❌ Revokes\n✅ Persists\n\nChoose Transfer Delegate for one-time escrowless sales (authority revokes after transfer).\n\nChoose Permanent Transfer Delegate when authority must persist forever.\n\nWarning!\nThe transfer delegate authority is temporary and will be reset upon asset transfer.\n\nWorks With\n\nMPL Core Asset\n✅\n\nMPL Core Collection\n❌\n\nArguments\nThe Transfer Plugin doesn't contain any arguments to pass in.\nFunctions\nAdd Transfer Delegate Plugin to an Asset\nThe addPlugin command adds the Transfer Delegate Plugin to an Asset. This plugin allows a delegate to transfer the Asset at any time.\nAdding a Transfer Plugin to an MPL Core Asset\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { addPlugin } from '@metaplex-foundation/mpl-core'\n\nconst assetAddress = publicKey('11111111111111111111111111111111')\n\nconst delegate = publicKey('22222222222222222222222222222222')\n\nawait addPlugin(umi, {\n\nasset: assetAddress,\n\nplugin: {\n\ntype: 'TransferDelegate',\n\nauthority: { type: 'Address', address: delegate },\n\n},\n\n}).sendAndConfirm(umi)\n\nDelegate the Transfer Authority\nThe approvePluginAuthority command delegates the transfer authority to a different address. This allows another address to transfer the Asset while maintaining ownership.\nDelegate the Transfer Authority\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { approvePluginAuthority } from '@metaplex-foundation/mpl-core'\n\nconst asset = publicKey(\"11111111111111111111111111111111\");\n\nconst collection = publicKey(\"22222222222222222222222222222222\");\n\nconst delegateAddress = publicKey(\"33333333333333333333333333333333\");\n\nawait approvePluginAuthority(umi, {\n\nasset: asset,\n\ncollection: collection,\n\nplugin: { type: \"TransferDelegate\" },\n\nnewAuthority: { type: \"Address\", address: delegateAddress },\n\n}).sendAndConfirm(umi);\n\nTransferring an Asset As Delegate\nThe transfer instruction transfers an Asset to another address using the transfer delegate authority.\nTransfer an MPL Core Asset\n\nimport {\n\nfetchAsset,\n\nfetchCollection,\n\ntransfer,\n\n} from \"@metaplex-foundation/mpl-core\";\n\nimport { publicKey } from \"@metaplex-foundation/umi\";\n\n// Asset ID you wish to transfer\n\nconst assetId = publicKey(\"11111111111111111111111111111111\");\n\n// Fetch the Asset\n\nconst assetItem = await fetchAsset(umi, assetId);\n\n// Fetch collection if Asset is apart of collection\n\nconst collectionItem =\n\nassetItem.updateAuthority.type == \"Collection\" &&\n\nassetItem.updateAuthority.address\n\n? await fetchCollection(umi, assetItem.updateAuthority.address)\n\n: undefined;\n\n// Transfer the Core NFT Asset\n\nconst { signature } = await transfer(umi, {\n\nasset: assetItem,\n\nnewOwner: publicKey(\"22222222222222222222222222222222\"),\n\ncollection: collectionItem,\n\n})\n\n.sendAndConfirm(umi);\n\nUpdating Transfer Delegate Authority\nSince the Transfer Delegate plugin doesn't contain plugin data to update (it's an empty object {}), the main \"update\" operation is changing the plugin authority. This allows you to delegate transfer permissions to different addresses.\nChanging the Transfer Delegate Authority\nYou can change who has transfer authority using the approvePluginAuthority function:\nUpdate Transfer Delegate Authority\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { approvePluginAuthority } from '@metaplex-foundation/mpl-core'\n\n(async () => {\n\nconst assetAddress = publicKey('11111111111111111111111111111111')\n\nconst newDelegate = publicKey('44444444444444444444444444444444')\n\n// Change the transfer delegate to a new address\n\nawait approvePluginAuthority(umi, {\n\nasset: assetAddress,\n\nplugin: { type: 'TransferDelegate' },\n\nnewAuthority: { type: 'Address', address: newDelegate },\n\n}).sendAndConfirm(umi)\n\n})();\n\nRevoking Transfer Delegate Authority\nThe transfer authority can be revoked using the revokePluginAuthority function, returning transfer control to the asset owner.\nRevoke Transfer Delegate Authority\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { revokePluginAuthority } from '@metaplex-foundation/mpl-core'\n\nconst assetAddress = publicKey('11111111111111111111111111111111')\n\nawait revokePluginAuthority(umi, {\n\nasset: assetAddress,\n\nplugin: { type: 'TransferDelegate' },\n\n}).sendAndConfirm(umi)\n\nCommon Errors\nAuthority mismatch\nOnly the transfer delegate authority can transfer the Asset. Verify you're signing with the correct keypair.\nAsset is frozen\nFrozen Assets cannot be transferred. The freeze authority must thaw the Asset first.\nTransfer delegate not found\nThe Asset doesn't have a Transfer Delegate plugin or authority was already revoked after a previous transfer.\nNotes\nOwner Managed: requires owner signature to add\nAuthority is automatically revoked after transfer\nEach transfer requires re-delegation by the new owner\nFrozen Assets cannot be transferred by delegates\nUse Permanent Transfer Delegate for persistent authority\nQuick Reference\nAuthority Lifecycle\nEventAuthority Status\nPlugin added\nActive\n\nAsset transferred\nRevoked\n\nNew owner adds plugin\nActive (new delegate)\n\nWho Can Transfer?\nAuthorityCan Transfer?\nAsset Owner\nYes (always)\n\nTransfer Delegate\nYes (once)\n\nPermanent Transfer Delegate\nYes (always)\n\nUpdate Authority\nNo\n\nFAQ\nWhy was my transfer authority revoked?\nTransfer Delegate authority is automatically revoked after any transfer. This is by design for marketplace safety - the delegate can only transfer once.\nHow do I implement escrowless listings?\nSeller adds Transfer Delegate with marketplace as authority\nWhen buyer pays, marketplace transfers Asset to buyer\nAuthority is revoked; seller can't double-list\nWhat's the difference between Transfer Delegate and Permanent Transfer Delegate?\nTransfer Delegate is revoked after one transfer. Permanent Transfer Delegate persists forever and can only be added at Asset creation.\nCan I transfer a frozen Asset as a delegate?\nNo. Frozen Assets block all transfers including delegate transfers. Use Permanent Transfer Delegate with a Permanent Freeze Delegate for complex escrow scenarios.\nDoes the owner need to approve each transfer?\nNo. Once the Transfer Delegate is set, the delegate can transfer without owner approval. However, they can only do it once before authority is revoked.\nRelated Plugins\nPermanent Transfer Delegate - Irrevocable transfer authority\nFreeze Delegate - Block transfers temporarily\nBurn Delegate - Allow delegate to burn Assets\nGlossary\nTermDefinition\nTransfer Delegate\nOwner Managed plugin allowing one-time transfer authority\n\nOwner Managed\nPlugin type requiring owner signature to add\n\nEscrowless\nSelling without transferring to a holding account\n\nPermanent Transfer Delegate\nIrrevocable version added at creation","tokens":2152,"crawled_at":1791194478772}
+{"id":10387,"url":"https://a16zcrypto.com/posts/article/protecting-developers-cftc-rules-blockchains","domain":"a16zcrypto.com","chapter":"research","title":"Protecting developers: Why the CFTC should clarify rules for blockchain protocols and apps - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nProtecting developers: Why the CFTC should clarify rules for blockchain protocols and apps\nMiles Jennings, Michele Korver, Aiden Slavin, and David Sverdlov\n12.16.25\n\nTags & Share Tags\ncomment letters & amicus briefs\nDeFi\npolicy & regulation\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nIn August, the Commodity Futures Trading Commission (CFTC) launched the Crypto Sprint to provide regulatory clarity and foster innovation in digital asset markets. Seeking to implement the recommendations in the President’s Working Group on Digital Asset Markets report, this effort aims to clarify the applicability of CFTC registration requirements to decentralized finance (DeFi).\n\nTo support this goal, we recently submitted a response to the CFTC which proposes three concrete, actionable measures within the agency’s current authority that would protect developers creating DeFi derivatives products and services in the United States, and further the Trump Administration’s goal of making the United States the “crypto capital of the world.”\n\nWhat’s the problem?\n\nBlockchain technology has the potential to revolutionize financial markets, including derivatives markets. Specifically, blockchain networks and smart contract protocols, together with the apps (frontend websites and applications) people use to access them, offer significant advantages over traditional derivatives markets. Those advantages include:\n\npeer-to-peer transactions without intermediaries,\n\nlower transaction costs,\n\nuser control of assets through self-custody,\n\nauditable and verifiable records on public blockchains,\n\noperations in accordance with transparent rules rather than by opaque discretion, and\n\nvirtually instantaneous settlement.\n\nYet, to date, the development of DeFi derivatives products has occurred largely offshore because it is not clear when the Commodity Exchange Act (CEA) requires exchange or intermediary registration — or indeed, whether the CEA assumes the presence of such registered third parties. As a result, it is altogether impossible for DeFi products and services to comply.\n\nMaking matters worse, the CFTC under the previous administration brought a series of imprecise enforcement actions that adopted expansive and novel interpretations of their own authority, particularly by failing to distinguish between protocol functionality, app functionality, and the products for which they may be used, and providing inconsistent and contradictory guidance as to what types of conduct give rise to which registration obligations.\n\nThis uncertainty has a real cost. U.S. developers are shifting activity overseas because it is unclear how the CEA and existing CFTC rules apply to decentralized, non-custodial systems. As a result, while the market for tokenized and onchain derivatives has expanded substantially, this growth has primarily occurred outside of the United States, to the detriment of U.S. users, traders, and developers.\n\nWithout a clear framework, domestic users lose access to onchain alternatives, and it becomes more difficult for regulators to oversee digital asset businesses. The CFTC has a unique opportunity to provide clarity, guidance, and a regulatory path that will reverse this unfortunate state of affairs, provide adequate protections to developers, and allow DeFi innovation to flourish in U.S. financial markets.\n\nWhat’s the solution?\n\nIn line with the agency’s statutory mandate to promote innovation, we propose three measures that the CFTC can undertake to help bring DeFi derivatives products back to the United States — while also preserving the safety and integrity of U.S. financial markets:\n\n1. The CFTC should make a clear and emphatic statement that neither blockchain networks and smart contract protocols nor their developers are subject to the CEA’s registration requirements. This statement should acknowledge the limits of the CFTC’s authority to regulate software, particularly where that software is not operationally controlled by any person, including where such systems are:\n\nAutonomous, executing and enforcing transactions and other activities without human intermediation and without any person having unilateral authority to alter functionality.\n\nPermissionless, not restricting access or empowering any person to restrict access.\n\nCredibly neutral, not granting anyone private permissions, hard-coded privileges, or similar rights over others that would enable them to discriminate.\n\nNon-custodial, enabling participants to maintain total independent control of digital assets owned by them.\n\nImportantly, any such requirements established by the CFTC should take into account both the potential benefits of blockchain technology and the risks that may arise from the elimination of operational control. The CFTC should consider and recognize the ways in which the nature of blockchain technology and the manner in which blockchain networks and smart contract protocols function may be consistent with the statutory objectives of the CEA in novel ways.\n\n2. The CFTC should provide no-action relief and/or interpretive guidance confirming when apps are not engaged in activity that requires registering with the CFTC. For example, apps are not engaged in conduct triggering CFTC registration where they do not take custody or control of user assets, do not exercise discretion with respect to user-initiated transactions, do not solicit or provide investment recommendations, do not provide tailored derivatives trading advice, and do not act as a counterparty to any transaction initiated by the user.\n\nThis relief and/or guidance should also address potential off-exchange trading, indicating what users apps may enable to access protocols, registered exchanges or intermediaries, or exempt exchanges or intermediaries. In addition, the CFTC should clarify what steps taken by an app to exclude U.S. person access are sufficient to remain outside of the CFTC’s territorial jurisdiction.\n\n3. The CFTC should engage in formal rulemaking and/or adopt exemptive relief to provide a safe harbor or innovation exemption setting out the circumstances and way in which apps, where they fall outside of the above proposal, can still comply with the CEA and CFTC rules via a tailored registration pathway.\n\nWhy now?\n\nThe market for DeFi derivatives has continued to grow rapidly — just last month, the trading volume of perpetual futures products alone exceeded $1 trillion. Without regulatory clarity much of this activity will continue to occur offshore. This problem is also unlikely to be addressed in crypto market structure legislation, which focuses on digital assets that are not derivatives, like network tokens, and spot markets for such assets.\n\nClear rules would give the CFTC better visibility into onchain activity and ensure that, in line with its mandate, innovation happens in the United States rather than offshore. With builders seeking workable compliance pathways and the technology maturing quickly, this is the right moment to create a framework that protects users while strengthening America’s competitiveness in the future of financial markets.\n\nRead our full proposal.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nYou should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investment-list/.\n\nThe content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures/ for additional important information.","tokens":2576,"crawled_at":1791194463040}
+{"id":10388,"url":"https://www.getfoundry.sh/forge/testing","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Testing – foundry - Ethereum Development Framework","text":"Testing\n\nForge runs tests written in Solidity. Test files live in test/ and test functions are prefixed with test.\n\n$ forge test\n\nCompiling...\nNo files changed, compilation skipped\nRan 2 tests for test/Counter.t.sol:CounterTest\n[PASS] testFuzz_SetNumber(uint256) (runs: 256, μ: 50747, ~: 52565)\n[PASS] test_Increment() (gas: 51847)\nSuite result: ok. 2 passed; 0 failed; 0 skipped; finished in 4.09ms (3.85ms CPU time)\nRan 1 test suite in 8.57ms (4.09ms CPU time): 2 tests passed, 0 failed, 0 skipped (2 total tests)\n\nWriting tests\n\nCreate a test contract that inherits from Test:\n\ntest/Counter.t.sol\n// SPDX-License-Identifier: MIT\npragma solidity ^0.8.13;\n\nimport {Test} from \"forge-std/Test.sol\";\nimport {Counter} from \"../src/Counter.sol\";\n\ncontract CounterTest is Test {\nCounter counter;\n\nfunction setUp() public {\ncounter = new Counter();\n}\n\nfunction test_Increment() public {\ncounter.increment();\nassertEq(counter.number(), 1);\n}\n\nfunction test_SetNumber() public {\ncounter.setNumber(42);\nassertEq(counter.number(), 42);\n}\n}\n\nKey conventions:\n\nTest files end with .t.sol\n\nTest contracts inherit from forge-std/Test.sol\n\nTest functions start with test_ or test\n\nsetUp() runs before each test\n\nCall isolation\n\nForge runs tests with call isolation enabled by default. In isolation mode, each top-level external call made by a test is executed as a separate transaction in a separate EVM context. This gives more precise gas accounting and transaction state changes for each call.\n\nBecause those calls use separate transaction contexts, a test function is not always equivalent to one normal transaction with warmed accounts or storage slots shared across every external call in the function body. For example, repeated calls to the same contract can be charged as cold again under isolation. If a test intentionally asserts behavior that depends on warm accounts or slots carrying across repeated calls in one transaction, run it with --no-isolate or set isolate = false in foundry.toml.\n\nTraces\n\nTraces show a tree of all calls made during a test, helping you understand execution flow and debug failures.\n\nStack traces\n\nWhen a test fails, use -vvv to see a stack trace showing exactly where the revert occurred. This is the most common way to debug test failures.\n\n$ forge test -vvv\n\nSolc 0.8.10 finished in 640.34ms\nCompiler run successful!\nRan 1 test for test/FailingTest.t.sol:VaultTest\n[FAIL: Unauthorized()] test_WithdrawAsNotOwner() (gas: 8418)\nTraces:\n[8418] VaultTest::test_WithdrawAsNotOwner()\n├─ [0] VM::prank(ECRecover: [0x0000000000000000000000000000000000000001])\n│ └─ ← [Return]\n├─ [191] Vault::withdraw() [staticcall]\n│ └─ ← [Revert] Unauthorized()\n└─ ← [Revert] Unauthorized()\nBacktrace:\nat Vault.withdraw\nat VaultTest.test_WithdrawAsNotOwner\nSuite result: FAILED. 0 passed; 1 failed; 0 skipped; finished in 329.35µs (58.54µs CPU time)\nRan 1 test suite in 8.10ms (329.35µs CPU time): 0 tests passed, 1 failed, 0 skipped (1 total tests)\n\nThe trace shows the call hierarchy with the revert bubbling up, and the Backtrace pinpoints the exact location in your code.\n\nFull traces\n\nUse -vvvv to see traces for all tests, including passing ones. This helps you understand execution flow, verify call order, and check gas usage for individual operations.\n\n$ forge test -vvvv\n\nCompiling...\nNo files changed, compilation skipped\nRan 1 test for test/OwnerUpOnly.t.sol:OwnerUpOnlyTest\n[PASS] test_IncrementAsOwner() (gas: 59372)\nTraces:\n[59372] OwnerUpOnlyTest::test_IncrementAsOwner()\n├─ [2407] OwnerUpOnly::count() [staticcall]\n│ └─ ← [Return] 0\n├─ [43524] OwnerUpOnly::increment()\n│ └─ ← [Stop]\n├─ [2407] OwnerUpOnly::count() [staticcall]\n│ └─ ← [Return] 1\n└─ ← [Stop]\nSuite result: ok. 1 passed; 0 failed; 0 skipped; finished in 287.16µs (62.42µs CPU time)\nRan 1 test suite in 6.97ms (287.16µs CPU time): 1 tests passed, 0 failed, 0 skipped (1 total tests)\n\nReading traces\n\nGas costs appear in brackets: [29808]\n\nContract and function names are color-coded\n\nCall types are annotated: [staticcall] for view/pure functions\n\nReturn values show what each call returned: ← [Return] 0 for a value, ← [Stop] for void\n\nIndentation shows the call hierarchy—nested calls are indented under their parent\n\nVerbosity levels\n\nControl how much detail Forge outputs with -v flags:\n\nFlagShows\n(none)\nPass/fail summary only\n\n-v\nTest names\n\n-vv\nLogs emitted during tests\n\n-vvv\nTraces for failing tests\n\n-vvvv\nTraces for all tests, including setup\n\n-vvvvv\nTraces with storage changes\n\nUse -vvv for debugging failures, -vvvv when you need to see successful test execution, and -vvvvv when tracking state changes.\n\nFiltering tests\n\nRun specific tests:\n\nBy name:\n\n$ forge test --match-test test_DepositETH\n\nSolc 0.8.10 finished in 672.77ms\nCompiler run successful!\nRan 1 test for test/ComplicatedContract.t.sol:ComplicatedContractTest\n[PASS] test_DepositETH() (gas: 107628)\nSuite result: ok. 1 passed; 0 failed; 0 skipped; finished in 696.56µs (473.12µs CPU time)\nRan 1 test suite in 7.25ms (696.56µs CPU time): 1 tests passed, 0 failed, 0 skipped (1 total tests)\n\nBy contract:\n\n$ forge test --match-contract ComplicatedContractTest\n\nCompiling...\nNo files changed, compilation skipped\nRan 2 tests for test/ComplicatedContract.t.sol:ComplicatedContractTest\n[PASS] test_DepositERC20() (gas: 179207)\n[PASS] test_DepositETH() (gas: 107628)\nSuite result: ok. 2 passed; 0 failed; 0 skipped; finished in 1.12ms (1.34ms CPU time)\nRan 1 test suite in 7.20ms (1.12ms CPU time): 2 tests passed, 0 failed, 0 skipped (2 total tests)\n\nBy path:\n\n$ forge test --match-path test/ContractB.t.sol\n\nSolc 0.8.10 finished in 634.45ms\nCompiler run successful!\nRan 1 test for test/ContractB.t.sol:ContractBTest\n[PASS] testExample() (gas: 257)\nSuite result: ok. 1 passed; 0 failed; 0 skipped; finished in 241.60µs (45.16µs CPU time)\nRan 1 test suite in 7.03ms (241.60µs CPU time): 1 tests passed, 0 failed, 0 skipped (1 total tests)\n\nCombine filters:\n\n$ forge test --match-contract ComplicatedContractTest --match-test test_Deposit\n\nCompiling...\nNo files changed, compilation skipped\nRan 2 tests for test/ComplicatedContract.t.sol:ComplicatedContractTest\n[PASS] test_DepositERC20() (gas: 179207)\n[PASS] test_DepositETH() (gas: 107628)\nSuite result: ok. 2 passed; 0 failed; 0 skipped; finished in 1.14ms (1.51ms CPU time)\nRan 1 test suite in 7.10ms (1.14ms CPU time): 2 tests passed, 0 failed, 0 skipped (2 total tests)\n\nExclude tests with --no-match-* variants:\n\n$ forge test --no-match-test test_Skip\n\nFuzz testing\n\nForge automatically fuzzes test functions that take parameters:\n\nfunction testFuzz_SetNumber(uint256 x) public {\ncounter.setNumber(x);\nassertEq(counter.number(), x);\n}\n\nForge generates random inputs and runs the test multiple times (256 by default):\n\n$ forge test\n\nSolc 0.8.10 finished in 635.50ms\nCompiler run successful!\nRan 1 test for test/Safe.t.sol:SafeTest\n[PASS] testFuzz_Withdraw(uint96) (runs: 256, μ: 40722, ~: 40932)\nSuite result: ok. 1 passed; 0 failed; 0 skipped; finished in 4.47ms (4.14ms CPU time)\nRan 1 test suite in 8.03ms (4.47ms CPU time): 1 tests passed, 0 failed, 0 skipped (1 total tests)\n\nConfigure fuzzing:\n\nfoundry.toml\n[fuzz]\nruns = 1000\nmax_test_rejects = 65536\nseed = \"0x1234\"\n\nConstrain inputs with vm.assume():\n\nfunction testFuzz_Transfer(uint256 amount) public {\nvm.assume(amount > 0 && amount <= 1000 ether);\n// Test with constrained amount\n}\n\nOr use bound() to clamp values:\n\nfunction testFuzz_Transfer(uint256 amount) public {\namount = bound(amount, 1, 1000 ether);\n// Test with bounded amount\n}\n\nTable testing\n\nFoundry v1.3.0 comes with support for table testing, which enables the definition of a dataset (the \"table\") and the execution of a test function for each entry in that dataset. This approach helps ensure that certain combinations of inputs and conditions are tested.\n\nIn forge, table tests are functions named with table prefix that accepts datasets as one or multiple arguments:\n\nfunction tableSumsTest(TestCase memory sums) public\n\nfunction tableSumsTest(TestCase memory sums, bool enable) public\n\nThe datasets are defined as forge fixtures which can be:\n\nstorage arrays prefixed with fixture prefix and followed by dataset name\n\nfunctions named with fixture prefix, followed by dataset name. Function should return an (fixed size or dynamic) array of values.\n\nSingle dataset\n\nIn following example, tableSumsTest test will be executed twice, with inputs from fixtureSums dataset: once with TestCase(1, 2, 3) and once with TestCase(4, 5, 9).\n\nstruct TestCase {\nuint256 a;\nuint256 b;\nuint256 expected;\n}\n\nfunction fixtureSums() public returns (TestCase[] memory) {\nTestCase[] memory entries = new TestCase[](2);\nentries[0] = TestCase(1, 2, 3);\nentries[1] = TestCase(4, 5, 9);\nreturn entries;\n}\n\nfunction tableSumsTest(TestCase memory sums) public pure {\nrequire(sums.a + sums.b == sums.expected, \"wrong sum\");\n}\n\nIt is required to name the tableSumsTest's TestCase parameter sums as the parameter name is resolved against the available fixtures (fixtureSums). In this example, if the parameter is not named sums the following error is raised: [FAIL: Table test should have fixtures defined].\n\nMultiple datasets\n\ntableSwapTest test will be executed twice, by using values at the same position from fixtureWallet and fixtureSwap datasets.\n\nstruct Wallet {\naddress owner;\nuint256 amount;\n}\n\nstruct Swap {\nbool swap;\nuint256 amount;\n}\n\nWallet[] public fixtureWallet;\nSwap[] public fixtureSwap;\n\nfunction setUp() public {\n// first table test input\nfixtureWallet.push(Wallet(address(11), 11));\nfixtureSwap.push(Swap(true, 11));\n\n// second table test input\nfixtureWallet.push(Wallet(address(12), 12));\nfixtureSwap.push(Swap(false, 12));\n}\n\nfunction tableSwapTest(Wallet memory wallet, Swap memory swap) public pure {\nrequire(\n(wallet.owner == address(11) && swap.swap) || (wallet.owner == address(12) && !swap.swap), \"not allowed\"\n);\n}\n\nThe same naming requirement mentioned above is relevant here.\n\nMutation testing\n\nMutation testing checks the strength of your test suite by making small changes, or mutants, to your source code and re-running your tests. A mutant is killed when at least one test fails. A mutant survives when the changed code still passes the selected tests.\n\nSee the mutation testing guide to select source files and tests, configure parallel workers and operators, interpret reports, and understand current limitations.\n\nBrutalized testing\n\nBrutalized testing checks whether code remains robust when values and memory are dirtier than the assumptions made by clean, ordinary test executions. It is useful for contracts that use inline assembly, narrow integer or fixed-bytes casts, addresses, or low-level memory handling.\n\nRun the selected tests against brutalized sources with forge test --brutalize:\n\n$ forge test --brutalize\n\nForge copies the project into a temporary workspace, rewrites source files under src/, compiles that temporary project, and runs the selected tests there. Test files (.t.sol) and scripts (.s.sol) are not rewritten.\n\nBrutalization applies deterministic source rewrites that:\n\ndirty unused upper bits in casts to address, smaller uint/int types, and fixed-size bytes types\n\nfill scratch space (0x00 through 0x3f) and memory beyond the free memory pointer before eligible external assembly functions run\n\nmisalign the free memory pointer by a small deterministic odd offset\n\nIf forge test passes but forge test --brutalize fails, the code under test likely depends on assumptions that are not guaranteed in every caller context, such as clean upper bits, zeroed memory, or word-aligned free memory.\n\nRegular test filters still apply:\n\n$ forge test --brutalize --match-contract VaultTest\n$ forge test --brutalize --match-test testWithdraw\n\n--brutalize is separate from mutation testing. Mutation testing changes code to evaluate test quality; brutalized testing changes call and memory conditions to evaluate code robustness. Because they answer different questions, --brutalize cannot be combined with --mutate.\n\nSymbolic testing\n\nSymbolic testing explores your code with symbolic inputs instead of concrete ones, searching feasible execution paths within the current symbolic EVM model and configured bounds for a counterexample that violates a property. When Forge reports a failure, it first replays the concrete input or invariant sequence through the normal executor, so the failure is backed by a concrete example.\n\nSymbolic tests are Solidity functions named check* or prove*. They are only discovered when symbolic mode is enabled with --symbolic:\n\ncontract MathSymbolicTest is Test {\nfunction check_average(uint256 a, uint256 b) external pure {\nuint256 average;\nunchecked {\naverage = (a + b) / 2;\n}\n\n// Forge should find an overflow counterexample.\nassertGe(average, a <= b ? a : b);\n}\n}\n\nRun it with:\n\n$ forge test --symbolic --match-test check_average\n\nSymbolic testing requires an SMT solver to be installed. The default solver is z3:\n\n$ brew install z3 # macOS\n$ sudo apt-get install z3 # Ubuntu\n\nWriting symbolic tests\n\nFunction parameters become symbolic inputs derived from the ABI, and the executor explores the feasible paths:\n\nrequire(...) and vm.assume(...) prune paths when their condition is false.\n\nassert, forge-std assertions, and DSTest failure signals are treated as properties to disprove.\n\nUser reverts terminate the current path.\n\nWhen --symbolic is enabled, invariant* and statefulFuzz* functions are explored as bounded symbolic call sequences instead of using the normal fuzzer.\n\nResults\n\nForge reports symbolic outcomes as:\n\nPASS: every explored path finished without a feasible failure under the currently modeled semantics and configured bounds.\n\nFAIL: the solver found a failing input or invariant sequence, and Forge replayed it concretely before reporting it.\n\nFAIL: incomplete symbolic execution (...) / Incomplete: Forge could not complete the search or validate a counterexample. Treat this as \"not established\", not as a proof.\n\nA PASS is scoped to the current symbolic model and configured bounds; it does not cover skipped dynamic lengths, deeper invariant sequences, larger loop bounds, unmodeled behavior, arbitrary unknown external code, or cryptographic preimage/collision properties.\n\nConfiguration\n\nTune the exploration bounds and solver in foundry.toml:\n\nfoundry.toml\n[profile.default.symbolic]\nsolver = \"z3\"\ntimeout = 30\nmax_depth = 10000\nmax_paths = 1024\nmax_solver_queries = 10000\n\nSymbolic exploration is bounded by configuration, including symbolic.max_depth, symbolic.max_paths, symbolic.max_solver_queries, dynamic calldata length settings, and symbolic.invariant_depth.\n\nBounds can also be set per test with inline forge-config annotations:\n\n/// forge-config: default.symbolic.invariant_depth = 4\nfunction invariant_counterNeverFive() public view {\nassertTrue(counter.value() != 5);\n}\n\nLimitations\n\nThe symbolic engine is not a complete revm-equivalent EVM model. Unsupported constructs report incomplete rather than a proof, and some supported semantics are bounded or approximate. Notable gaps include gas accounting, Cancun+ SELFDESTRUCT, arbitrary unknown external code, and cryptographic preimage or collision properties. The exact unsupported-feature reason is preserved in the test output.\n\nFor a counterexample-to-fix workflow, including durable JSON artifacts, concrete replay, generated regression tests, fuzz corpus integration, and CI handoffs, see the symbolic testing workflow.\n\nTesting reverts\n\nUse vm.expectRevert() to test that a call reverts:\n\nfunction test_RevertWhen_Unauthorized() public {\nvm.expectRevert(\"Not authorized\");\nrestricted.doSomething();\n}\n\nMatch a custom error:\n\nfunction test_RevertWhen_InsufficientBalance() public {\nvm.expectRevert(Token.InsufficientBalance.selector);\ntoken.transfer(address(0), 1000);\n}\n\n$ forge test --match-test \"test_IncrementAsOwner|test_RevertWhen_CallerIsNotOwner\" --match-path test/OwnerUpOnly.t.sol\n\nSolc 0.8.10 finished in 699.33ms\nCompiler run successful!\nRan 2 tests for test/OwnerUpOnly.t.sol:OwnerUpOnlyTest\n[PASS] test_IncrementAsOwner() (gas: 59372)\n[PASS] test_RevertWhen_CallerIsNotOwner() (gas: 29987)\nSuite result: ok. 2 passed; 0 failed; 0 skipped; finished in 474.90µs (238.18µs CPU time)\nRan 1 test suite in 6.95ms (474.90µs CPU time): 2 tests passed, 0 failed, 0 skipped (2 total tests)\n\nTesting events\n\nUse vm.expectEmit() to verify events are emitted:\n\nfunction test_EmitsTransfer() public {\nvm.expectEmit(true, true, false, true);\nemit Transfer(alice, bob, 100);\n\ntoken.transfer(bob, 100);\n}\n\nThe four booleans specify which topics and data to check.\n\nForking\n\nTest against live chain state:\n\n$ forge test --fork-url https://ethereum.reth.rs/rpc\n\nOr configure in foundry.toml:\n\nfoundry.toml\n[profile.default]\neth_rpc_url = \"https://ethereum.reth.rs/rpc\"\n\nPin to a specific block for reproducible tests:\n\n$ forge test --fork-url https://ethereum.reth.rs/rpc --fork-block-number 18000000\n\nCheatcodes\n\nForge provides cheatcodes via the vm object to manipulate the test environment:\n\n// Set block timestamp\nvm.warp(1700000000);\n\n// Set block number\nvm.roll(18000000);\n\n// Impersonate an address\nvm.prank(alice);\ncontract.doSomething();\n\n// Give ETH to an address\nvm.deal(alice, 100 ether);\n\n// Modify storage\nvm.store(address(token), bytes32(0), bytes32(uint256(1000)));\n\nSee the cheatcodes reference for the full list.\n\nWatch mode\n\nRe-run tests when files change:\n\n$ forge test --watch\n\nWas this helpful?\n\nSuggest changes on GitHub","tokens":4361,"crawled_at":1791194473673}
+{"id":10389,"url":"https://gov.uniswap.org/u/cp0x","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Profile - cp0x - Uniswap Governance","text":"cp0x\n\nLinks: cp0x.com - delegations - staking - X - Telegram - YouTube\n\ncp0x is a crypto community working in the space since 2016. We take part in governance across 20+ DAOs, run a liquidity hub with curated DeFi deals and trading competitions, build permissionless interfaces to DeFi protocols, and run validators, sequencers, operators and indexers in various networks. We also run a YouTube channel where we talk to founders and developers about protocols and the market.\n\nHow we vote\n\nFairness. We stand against reckless spending and look for solutions that benefit everyone equally.\n\nTransparency. Our decisions are consistent.\n\nDecentralisation. We support what reduces reliance on single players or foundations.\n\nWe verify proposals ourselves rather than relying on their description. We vote against what centralises power, obscures spending or spends without justification. Where there is not enough information we abstain, and where the consequences are ambiguous we take it back to the community.","tokens":252,"crawled_at":1791194475684}
+{"id":10390,"url":"https://a16zcrypto.com/posts/article/founders-policymakers-guide","domain":"a16zcrypto.com","chapter":"research","title":"How founders can talk with policymakers: A guide - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nHow founders can talk with policymakers: A guide\nMiles Jennings, Collin McCune, and Aiden Slavin\n12.02.25\n\nTABLE OF CONTENTS\n#1: Tell your story #1: Tell your story\n#2: Know your audience\n#3: Avoid jargon\n#4: Be specific, but stay balanced\n#5: Get organized\nTags\ncompany building\ngovernance\npolicy & regulation\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nCrypto policymaking continues to advance in the United States, and the stakes couldn’t be higher: Policy will determine not only how crypto companies can operate, but whether the values of openness, competition, and user-control are realized in the internet’s next era.\n\nThat’s why builders can’t sit on the sidelines. The only way the industry will get the policy and regulation it needs to thrive is to engage in the policymaking process: The rules that govern crypto will be informed by those who show up.\n\nSo how can builders, entrepreneurs, and innovators work with policymakers and legislators effectively? First, figure out who you want to talk with: your state legislators, regulators at agencies like the SEC or CFTC, or the representatives who speak for you in Washington. Once you pick your target, here are five tactics to help make your advocacy as successful as possible.\n\n#1: Tell your story\n\nPolicymaking is about people, so make your work personal. When policymakers decide how to approach new technologies, they aren’t legislating abstractions. They’re thinking about jobs, constituents, and communities. That’s why your story matters.\n\nTell them what problem you’re solving, why it matters, and who you are (including why you are the one solving this problem) — in human terms.\n\nTalk about the community you’re building for, and the economic opportunity you’re creating. As a developer, explain how your work improves security, transparency, or user control. Highlight the jobs and innovation your work enables. And, if you can, tie these outcomes to the issues and constituencies that the office you’re talking to cares about most.\n\nGood policy conversations connect your work to the policymaker’s mission:\n\nEconomic growth: How does your work contribute to competitiveness or productivity?\n\nConsumer protection: How does your approach keep users safe?\n\nFinancial inclusion: How does your work expand access, ensure equality, and create opportunity?\n\nWhen you link your story to shared goals like these, you’re no longer just talking about your company or a protocol, you’re talking about public outcomes — goals the policymaker on the other side of the table cares about. It’s the language policymakers speak.\n\nAnd don’t underestimate the power of excitement. Innovation is inherently optimistic: It’s an act of belief that technology can make the world better. That kind of optimism has always been the engine of American progress, from the railroad to the internet.\n\nThis is especially true for crypto. Crypto is rooted in the belief that little tech is giving people control over their data, identity, and economic lives through decentralization, rather than consolidating power in a few large institutions. When you talk to policymakers, connect your work to that ethos. Explain how decentralization supports competition, growth, and user empowerment — goals that align with both innovation and public interest.\n\n#2: Know your audience\n\nEvery policymaker has a different focus. No two offices are alike. Some lawmakers are technologists by training; others are focused on agriculture or healthcare. Staffers might handle a dozen issue areas at once. So think about how you’re going to tailor your message to each person’s level of knowledge and policy priorities.\n\nWhere to start? Do your homework before every meeting. Connect with others in industry who have met with them before (see tactic #5 below). Review their past statements, social media posts, press releases, and voting record. Scan hearing transcripts to understand their tone — are they skeptical, curious, or supportive of innovation? Have they worked on crypto issues before? Learn what’s happening in their district or state: Is there a local company or workforce issue that connects to your work? This doesn’t need to take a lot of time, but doing the work is going to lead to a better outcome.\n\nUnderstanding context turns a generic briefing into a more meaningful exchange. It’s also practical: Policymakers and their staff are extremely busy. Most meetings last 15 to 30 minutes, sometimes less. The more you can tailor your ask to their priorities, the better. You may only get one or two key points across, so make them count.\n\nFinally, remember that staff is key. The staffers you meet often write the memos, draft the questions for hearings, and brief the principal before key votes. Treat them with the same respect and engagement you would give an elected official.\n\n#3: Avoid jargon\n\nThe goal is clarity, not complexity. Every field develops its own language — and crypto can be worse than many when it comes to industry jargon. Terms like “composability,” “zero-knowledge proofs,” and “skeuomorphism” can quickly alienate someone unfamiliar with the space.\n\nOf course, technical terms have their place, but they shouldn’t be the headline. Your goal isn’t to teach a crash course in protocol design; it’s to explain why your technology matters and what policies it needs to thrive.\n\nWhat does this mean in practice? Instead of: “Our protocol uses zk-SNARKs to preserve user privacy without compromising verifiability,” you could try: “We build tools to make financial transactions verifiable and private.” That’s not dumbing it down, it’s making it accessible.\n\nAvoid factual overload too. Policymakers process massive volumes of information every day. A clear, simple message, supported by one or two memorable facts or examples, will resonate far more than a dense technical briefing.\n\nThink of succinctness as credibility: The ability to translate complex ideas into plain English demonstrates mastery, enhancing your trustworthiness.\n\n#4: Be specific, but stay balanced\n\nPolicymakers appreciate pragmatism. Once you’ve told your story and established trust, be clear about what you want. If there’s a specific policy or regulation you support or oppose, explain clearly and specifically what that policy gets right or wrong, what outcome you would like to see, and why it matters.\n\nMake your ask as actionable as possible. The more you can tie your position to outcomes that the policymaker cares about, the better (see #2, above: You did your homework, right?). If you have data or case studies, use them. Show where similar policies have worked, whether in another jurisdiction or another sector. Policymakers like to see that a proposal has precedent or demonstrable results.\n\nBut be upfront about risks or tradeoffs, too. Acknowledging uncertainty strengthens your credibility. Saying “here’s what we know, here’s what we don’t, and here’s how we can mitigate risk” builds trust. And when possible, frame your ideas as win-wins — policies that advance multiple objectives: innovation and safety, growth and inclusion. The best proposals solve more than one problem at once.\n\n#5: Get organized\n\nCollaboration is a force multiplier. While individual stories and specific advocacy matter, coordinated group action is what drives policy wins. When engaging policymakers, builders shouldn’t underestimate the power of organizing coalitions. By working with others in the industry — and in your local community — you can ensure that your signal cuts through the noise.\n\nWhy does coalition-building matter? For one, coalitional support provides evidence of a proposal’s value. Lawmakers are more inclined to give credence to a group of responsible actors collectively voicing the need for change than a single company pursuing its own bottom line. Organization also helps policymakers see the bigger picture, enabling them to understand how a given proposal might impact a host of different participants.\n\nTeaming up through trade groups and local networks can help turn individual advocacy into lasting influence because those groups have infrastructure in place to continue advocating. Shared infrastructure — from policy roundtables to joint statements — helps translate innovation into impact.\n\nFortunately, builders don’t need to start from scratch. Over the past decade, the crypto industry has built a wide range of effective coalitions and conveners, at the state, federal, and even international levels.\n\nBut don’t use a coalition as an excuse not to do the work: You also need to show up to advocate personally for your own point of view, and to be present in the room.\n\n***\n\nPolicy development happens in bursts. A bill gets introduced, a hearing scheduled, a request for comment issued — these are the moments when lawmakers and regulators are listening. Seizing those moments matters.\n\nBut lasting impact doesn’t come from one-off interventions. It comes from trust built over time. So show up when windows of opportunity open, while investing in long-term relationships (not unlike how sales work, with long relationships and conversations preceding the signed deal.)\n\nStart early: Relationship-building is cumulative. Even short, informal conversations — at a hearing, in a roundtable, or through a trade association — can lay the groundwork for deeper engagement later. If you don’t have a direct line to the right policymaker or staffer, ask for an introduction. Industry groups, civil society organizations, or advocacy coalitions can often help open the door.\n\nSo determine what’s important to you, and join the conversation. There is plenty of work to do. The GENIUS rulemaking process has only just begun, and once market structure is signed into law, regulators will need to implement it to establish clear rules of the road for blockchain systems. Even as federal legislation comes online, U.S. states will continue to play a critical role in regulating the crypto industry. And abroad, key jurisdictions like the UK and South Korea are still in the process of defining their approach to crypto regulation.\n\nBut most of all, stay involved. In the words of former Chairman of the House Financial Services Committee (and a16z Senior Advisor) Patrick McHenry, “If you don’t engage, your competitor will.”\n\nIt’s time to engage.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nYou should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investment-list/.\n\nThe content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures/ for additional important information.","tokens":3367,"crawled_at":1791194488499}
+{"id":10391,"url":"https://www.getfoundry.sh/forge/scripting","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Scripting – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nScripting\n\nForge scripts are Solidity files that deploy contracts and execute transactions on-chain. They replace deployment scripts traditionally written in JavaScript.\n\nFor sender selection, CREATE2, library linking, nonces, simulation, and resume semantics, see How scripting works.\n\nScript structure\n\nScripts inherit from Script and implement a run() function:\n\nscript/Deploy.s.sol\n// SPDX-License-Identifier: MIT\npragma solidity ^0.8.13;\n\nimport {Script} from \"forge-std/Script.sol\";\nimport {Counter} from \"../src/Counter.sol\";\n\ncontract DeployScript is Script {\nfunction run() public {\nvm.startBroadcast();\n\nCounter counter = new Counter();\ncounter.setNumber(42);\n\nvm.stopBroadcast();\n}\n}\n\nKey elements:\n\nInherit from forge-std/Script.sol\n\nScript files end with .s.sol\n\nWrap deployment logic in vm.startBroadcast() / vm.stopBroadcast()\n\nRunning scripts\n\nSimulate a deployment (no transactions sent):\n\n$ forge script script/Deploy.s.sol\n\nBroadcast transactions to a network:\n\n$ forge script script/Deploy.s.sol --broadcast --rpc-url $RPC_URL\n\nUsing RPC aliases\n\nDefine aliases in foundry.toml and pass the alias to --rpc-url:\n\nfoundry.toml\n[rpc_endpoints]\nsepolia = \"${SEPOLIA_RPC_URL}\"\n\n$ forge script script/Deploy.s.sol --broadcast --rpc-url sepolia\n\nProviding a private key\n\n$ forge script script/Deploy.s.sol --broadcast --rpc-url $RPC_URL --account deployer\n\n$ forge script script/Deploy.s.sol --broadcast --rpc-url $RPC_URL --ledger\n\n$ forge script script/Deploy.s.sol --broadcast --rpc-url $RPC_URL --browser\n\n$ forge script script/Deploy.s.sol --broadcast --rpc-url $RPC_URL --private-key $PRIVATE_KEY\n\nSee Browser Wallet Signing for the local connection flow, network checks, and a simulation-first deployment workflow.\n\nBroadcasting from a specific address\n\nTo broadcast from a specific address:\n\nvm.startBroadcast(deployerAddress);\n\nOr derive the sender from a private key read from the environment:\n\nuint256 deployerPrivateKey = vm.envUint(\"PRIVATE_KEY\");\nvm.startBroadcast(deployerPrivateKey);\n\nThe address overload selects a transaction sender but does not supply a signing key. Provide a matching wallet when broadcasting, or use --unlocked with a node that controls that account. The private-key overload derives the address and adds the key to Forge's script wallets.\n\nStarting a broadcast changes the sender of outgoing calls; it does not change msg.sender in the script's current frame. Pass the intended owner or deployer explicitly in transaction arguments. Inside a contract called directly by the broadcast transaction, msg.sender is the transaction sender.\n\nOverriding the sender nonce\n\nBy default the sender's starting nonce is fetched from the RPC endpoint, or set to 1 when no endpoint is configured. Pass --sender-nonce to pin it instead:\n\n$ forge script script/Deploy.s.sol --rpc-url $RPC_URL --sender-nonce 7\n\nThe override applies to script execution and transaction generation and is kept even when broadcasting switches to a different sender. Because addresses of contracts deployed with CREATE depend on the sender's nonce, this keeps simulated deployment addresses consistent with the nonce you plan to broadcast from. See forge script for the full option reference.\n\nVerifying deployed contracts\n\nVerify on Etherscan during deployment:\n\n$ forge script script/Deploy.s.sol \\\n--broadcast \\\n--rpc-url $RPC_URL \\\n--verify \\\n--etherscan-api-key $ETHERSCAN_API_KEY\n\nResuming failed broadcasts\n\nIf a broadcast fails partway through, resume from where it left off:\n\n$ forge script script/Deploy.s.sol --broadcast --rpc-url $RPC_URL --resume\n\nMulti-chain deployments\n\nDeploy to multiple chains by running the script with different RPC URLs:\n\n$ forge script script/Deploy.s.sol --broadcast --rpc-url $MAINNET_RPC\n$ forge script script/Deploy.s.sol --broadcast --rpc-url $ARBITRUM_RPC\n$ forge script script/Deploy.s.sol --broadcast --rpc-url $OPTIMISM_RPC\n\nReading deployment artifacts\n\nScripts write transaction receipts to broadcast/. Access deployed addresses in subsequent scripts:\n\nfunction run() public {\nstring memory json = vm.readFile(\"broadcast/Deploy.s.sol/1/run-latest.json\");\naddress counter = vm.parseJsonAddress(json, \".transactions[0].contractAddress\");\n}\n\nScript cheatcodes\n\nScripts have access to all cheatcodes. Common ones for scripting:\n\n// Read environment variables\nstring memory rpcUrl = vm.envString(\"RPC_URL\");\nuint256 privateKey = vm.envUint(\"PRIVATE_KEY\");\n\n// Read/write files\nstring memory config = vm.readFile(\"config.json\");\nvm.writeFile(\"output.txt\", \"deployed\");\n\n// Parse JSON\naddress addr = vm.parseJsonAddress(json, \".address\");\n\n// Console logging\nconsole.log(\"Deploying to:\", block.chainid);\n\nDry run\n\nTest a script without sending transactions:\n\n$ forge script script/Deploy.s.sol --rpc-url $RPC_URL\n\nThis simulates against the live chain state and shows what would happen.\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 01/10/2026, 19:51","tokens":1235,"crawled_at":1791194490940}
+{"id":10392,"url":"https://www.metaplex.com/docs/smart-contracts/core/plugins/freeze-delegate","domain":"www.metaplex.com","chapter":"docs","title":"Freeze Delegate Plugin | Metaplex Core","text":"The Freeze Delegate Plugin allows you to freeze Core Assets, blocking transfers and burns while the asset remains in the owner's wallet. Perfect for escrowless staking, marketplace listings, and game mechanics.\nWhat You'll Learn\nAdd the Freeze Delegate plugin to an Asset\nFreeze and thaw Assets\nDelegate freeze authority to another address\nUse cases: staking, listings, game locking\n\nSummary\nThe Freeze Delegate is an Owner Managed plugin that freezes Assets in place. When frozen, the Asset cannot be transferred or burned until thawed by the freeze authority.\nFreeze Assets without transferring to escrow\nDelegate freeze authority to a program or other wallet\nAuthority is revoked on transfer (for non-permanent version)\nUse Permanent Freeze Delegate for irrevocable freezing\nOut of Scope\nCollection-level freezing (use Asset-level only), permanent freezing (see Permanent Freeze Delegate), and Token Metadata freeze authority (different system).\nQuick Start\nJump to: Add Plugin · Delegate Authority · Freeze · Thaw\nAdd the Freeze Delegate plugin: addPlugin(umi, { asset, plugin: { type: 'FreezeDelegate', data: { frozen: true } } })\nThe Asset is now frozen and cannot be transferred\nThaw when ready: update the plugin with frozen: false\nAuthority is revoked on transfer\nWhen to Use Freeze vs Permanent Freeze\nUse CaseFreeze DelegatePermanent Freeze Delegate\nMarketplace listings\n✅ Best choice\n❌ Overkill\n\nEscrowless staking\n✅ Best choice\n✅ Also works\n\nSoulbound tokens\n❌ Revokes on transfer\n✅ Best choice\n\nCollection-wide freeze\n❌ Assets only\n✅ Supports Collections\n\nRental protocols\n✅ Best choice\n✅ Also works\n\nChoose Freeze Delegate when authority should reset on ownership change.\n\nChoose Permanent Freeze Delegate when authority must persist forever.\n\nCommon Use Cases\nEscrowless staking: Freeze NFTs while staked without transferring to escrow\nMarketplace listings: Lock NFTs for sale without escrow accounts\nGame item locking: Temporarily lock items during gameplay\nRental protocols: Lock NFTs while rented out\nGovernance: Lock tokens during voting periods\nCollateral: Lock NFTs used as lending collateral\nTournaments: Lock NFTs during competition participation\nWorks With\n\nMPL Core Asset\n✅\n\nMPL Core Collection\n❌\n\nFor collection-level freezing, use Permanent Freeze Delegate instead.\n\nArguments\nArgValue\nfrozen\nbool\n\nFunctions\nAdd Freeze Delegate Plugin to an Asset\nThe addPlugin command adds the Freeze Delegate Plugin to an Asset. This plugin allows the Asset to be frozen, preventing transfers and burns.\nAdding a Freeze Plugin to an MPL Core Asset\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { addPlugin } from '@metaplex-foundation/mpl-core'\n\nconst assetAddress = publicKey('11111111111111111111111111111111')\n\nawait addPlugin(umi, {\n\nasset: assetAddress,\n\nplugin: { type: 'FreezeDelegate', data: { frozen: true } },\n\n}).sendAndConfirm(umi)\n\nDelegate the Freeze Authority\nThe approvePluginAuthority command delegates the freeze authority to a different address. This allows another address to freeze and thaw the Asset while maintaining ownership.\nDelegate the Freeze Authority\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { approvePluginAuthority } from '@metaplex-foundation/mpl-core'\n\nconst asset = publicKey('11111111111111111111111111111111')\n\nconst delegateAddress = publicKey('22222222222222222222222222222222')\n\nawait approvePluginAuthority(umi, {\n\nasset: asset.publicKey,\n\nplugin: { type: 'FreezeDelegate' },\n\nnewAuthority: { type: 'Address', address: delegateAddress },\n\n}).sendAndConfirm(umi)\n\nUpdating the Freeze Delegate Plugin\nThe Freeze Delegate Plugin can be updated to change the frozen state of the asset. This is the same as using the Freezing an Asset and Thawing a Frozen Asset functions shown below.\nFreezing an Asset\nThe freezeAsset command freezes an Asset, preventing it from being transferred or burned. This is useful for escrowless staking or marketplace listings.\nFreeze an MPL Core Asset\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { freezeAsset, fetchAsset } from '@metaplex-foundation/mpl-core'\n\nconst assetAddress = publicKey('11111111111111111111111111111111')\n\nconst assetAccount = await fetchAsset(umi, assetAddress)\n\nconst delegateSigner = generateSigner(umi)\n\nawait freezeAsset(umi, {\n\nasset: assetAccount,\n\ndelegate: delegateSigner.publicKey,\n\nauthority: delegateSigner,\n\n}).sendAndConfirm(umi)\n\nThawing a Frozen Asset\nThe thawAsset command unfreezes a frozen Asset, restoring its ability to be transferred and burned.\nThaw an MPL Core Asset\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { thawAsset, fetchAsset } from '@metaplex-foundation/mpl-core'\n\nconst assetAddress = publicKey('11111111111111111111111111111111')\n\nconst assetAccount = await fetchAsset(umi, assetAddress)\n\nconst delegateSigner = generateSigner(umi)\n\nawait thawAsset(umi, {\n\nasset: assetAccount,\n\ndelegate: delegateSigner,\n\n}).sendAndConfirm(umi)\n\nCommon Errors\nAsset is frozen\nYou tried to transfer or burn a frozen Asset. The freeze authority must thaw it first.\nAuthority mismatch\nOnly the freeze delegate authority can freeze/thaw the Asset. Check who has the plugin authority.\nPlugin not found\nThe Asset doesn't have a Freeze Delegate plugin. Add it first with addPlugin.\nNotes\nOwner Managed: requires owner signature to add\nAuthority is automatically revoked when the Asset transfers\nFrozen Assets can still be updated (metadata changes allowed)\nUse Permanent Freeze Delegate if you need the authority to persist after transfer\nFreezing is immediate - no confirmation period\nQuick Reference\nFreeze States\nStateCan TransferCan BurnCan Update\nUnfrozen\nYes\nYes\nYes\n\nFrozen\nNo\nNo\nYes\n\nAuthority Behavior\nEventAuthority Result\nAsset transfers\nAuthority revoked\n\nPlugin removed\nAuthority gone\n\nThaw\nAuthority retained\n\nFAQ\nCan I freeze an Asset I don't own?\nNo. The Freeze Delegate is Owner Managed, so only the owner can add it. After adding, you can delegate authority to another address.\nWhat's the difference between Freeze Delegate and Permanent Freeze Delegate?\nFreeze Delegate authority is revoked on transfer. Permanent Freeze Delegate authority persists forever and can only be added at creation time.\nCan a frozen Asset be burned?\nNo. Frozen Assets block both transfers and burns. Thaw the Asset first if you want to burn it.\nCan I freeze an entire Collection at once?\nNot with the regular Freeze Delegate (Assets only). Use Permanent Freeze Delegate on the Collection instead - it supports collection-level freezing and will freeze all Assets in that Collection at once. Note that Permanent Freeze Delegate can only be added at Collection creation time.\nDoes freezing affect metadata updates?\nNo. The Asset owner or update authority can still update metadata (name, URI) while frozen. Only transfers and burns are blocked.\nHow do I implement escrowless staking?\nAdd Freeze Delegate plugin with your staking program as authority\nWhen user stakes: freeze the Asset\nWhen user unstakes: thaw the Asset\nThe NFT never leaves the user's wallet\nRelated Plugins\nPermanent Freeze Delegate - Irrevocable freeze authority, supports Collections\nTransfer Delegate - Allow delegate to transfer Assets\nBurn Delegate - Allow delegate to burn Assets\nGlossary\nTermDefinition\nFreeze Delegate\nOwner Managed plugin that blocks transfers and burns\n\nFrozen\nAsset state where transfers and burns are blocked\n\nThaw\nUnfreezing an Asset to allow transfers again\n\nDelegate Authority\nThe account authorized to freeze/thaw the Asset\n\nEscrowless\nStaking/listing without transferring to a holding account\n\nOwner Managed\nPlugin type requiring owner signature to add","tokens":1909,"crawled_at":1791194514834}
+{"id":10393,"url":"https://docs.sui.io/onchain-finance/deepbook","domain":"docs.sui.io","chapter":"layer1_layer2","title":"DeepBook | Sui Documentation","text":"DeepBookDeepBookA decentralized central limit order book (CLOB) built on Sui. is Sui's native liquidity layer, providing a central limit order book for spot trading, margin trading, and prediction markets.\n\nBefore you build, decide how your code calls DeepBook. You can depend on the DeepBookV3 Move packagePackageSmart contracts on Sui. from your own MoveMoveAn open source programming language used for all activity on Sui. moduleModuleA component of a Move package that defines interaction with on-chain objects., compose transactions with the TypeScript SDK, or read market data without signing transactions. See Choose your integration model to compare the options.\n\nDesign\nLearn about DeepBookV3 design, including the Pool, PoolRegistry, and BalanceManager shared objects.\n→\nFees and Funding\nHow DeepBook trading fees work and how to fund a BalanceManager with DEEP: paying fees in DEEP or the input token, the floating DEEP price, maker, taker, and staking fees, and obtaining Testnet DEEP, USDC, and SUI.\n→\nSpot Trading Workflow\nHands-on DeepBook spot walkthrough on Sui Testnet: create a BalanceManager, deposit, place a limit order, read status and fills, fill your own order, cancel, and withdraw, with real transactions to observe at each step.\n→\nDeepBookV3\nIn this section\nContract Information\nDeepBookV3 SDK\n\n→\nMargin\nIn this section\nDesign\nMargin Risks\nLeveraged Position Workflow\nIntegration\nContract Information\nDeepBook Margin SDK\n\n→\nPredict\nIn this section\nTestnet Workflow\nDesign\nContract Information\nDeepBook Predict SDK\n\n→\nOperate\nIn this section\nDeepBookV3 Indexer\nDeepBook Margin Indexer\n\n→","tokens":404,"crawled_at":1791194501602}
+{"id":10394,"url":"https://www.getfoundry.sh/projects/layout","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Project Layout – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nProject Layout\n\nFoundry uses a conventional directory structure. Configure paths in foundry.toml or use the defaults.\n\nDefault structure\n\nfoundry.tomlProject configuration\n\nContract source files\n\nTest files (*.t.sol)\n\nScript files (*.s.sol)\n\nGit submodule dependencies\n\nCompilation artifacts\n\nCompiler cache\n\nDeployment logs\n\nSource directories\n\nDirectoryPurposeConfig key\nsrc/\nProduction contracts\nsrc\n\ntest/\nTest contracts\ntest\n\nscript/\nDeployment scripts\nscript\n\nlib/\nDependencies\nlibs\n\nCustomize in foundry.toml:\n\n[profile.default]\nsrc = \"contracts\"\ntest = \"tests\"\nscript = \"scripts\"\nlibs = [\"lib\", \"node_modules\"]\n\nOutput directories\n\nDirectoryPurposeConfig key\nout/\nCompiled artifacts (ABI, bytecode)\nout\n\ncache/\nCompiler cache for incremental builds\ncache_path\n\nbroadcast/\nTransaction logs from script broadcasts\nbroadcast\n\nFile naming conventions\n\nFoundry identifies file types by suffix:\n\nSuffixTypeExample\n.sol\nContract\nToken.sol\n\n.t.sol\nTest\nToken.t.sol\n\n.s.sol\nScript\nDeploy.s.sol\n\nTests must also inherit from Test:\n\nimport {Test} from \"forge-std/Test.sol\";\n\ncontract TokenTest is Test {\n// ...\n}\n\nScripts must inherit from Script:\n\nimport {Script} from \"forge-std/Script.sol\";\n\ncontract DeployScript is Script {\n// ...\n}\n\nMonorepo setup\n\nFor monorepos with multiple Foundry projects, use a root foundry.toml or per-project configs.\n\nShare dependencies with a root lib/ directory:\n\n[profile.default]\nlibs = [\"lib\", \"../lib\"]\n\nOr use workspaces:\n\nfoundry.tomlRoot config (optional)\n\nShared dependencies\n\nfoundry.toml\n\nfoundry.toml\n\nRemappings\n\nControl import paths with remappings. Foundry auto-detects them from lib/, but you can customize:\n\n[profile.default]\nremappings = [\n\"@openzeppelin/=lib/openzeppelin-contracts/\",\n\"@uniswap/=lib/v3-core/contracts/\",\n]\n\nOr use a remappings.txt file:\n\n@openzeppelin/=lib/openzeppelin-contracts/\n@uniswap/=lib/v3-core/contracts/\n\nSee Dependencies for more on managing imports.\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":506,"crawled_at":1791194508148}
+{"id":10395,"url":"https://docs.sui.io/onchain-finance/deepbook/deepbookv3/deepbook","domain":"docs.sui.io","chapter":"layer1_layer2","title":"DeepBookV3 | Sui Documentation","text":"DeepBookV3 is a next-generation decentralized central limit order book (CLOB) built on Sui. DeepBookV3 leverages Sui's parallel execution and low transactionTransactionA number of commands that execute on inputs to define the result of the transaction. fees to bring a highly performant, low-latency exchange onchain.\n\nThe latest version delivers new features including flash loans, governance, improved account abstraction, and enhancements to the existing matching engine. This version also introduces its own tokenomics with the DEEP token, which you can stake for additional benefits.\n\nDeepBookV3 does not include an end-user interface for token trading. Rather, it offers built-in trading functionality that can support token trades from decentralized exchanges, wallets, or other apps. The available SDK abstracts away a lot of the complexities of interacting with the chain and building programmable transaction blocksProgrammable transaction blocksDefine all user transactions on Sui., lowering the barrier of entry for active market making.\n\ninfo\nThe documentation refers to the DeepBookDeepBookA decentralized central limit order book (CLOB) built on Sui. standard as \"DeepBookV3\" to avoid confusion with the recently deprecated version of DeepBook (DeepBookV2).\n\nChoose your integration model​\n\nDeepBookV3 is a Move packagePackageSmart contracts on Sui. on Sui MainnetMainnetProduction network for live transactions and real-value assets.. Every integration calls the same public functions on the Pool shared objectObjectThe basic unit of storage on Sui., so your first decision is not which features you use, but where your code runs. Integrating DeepBook means choosing one of the following models.\n\nModelYou writeChoose this when\nMove package\nA MoveMoveAn open source programming language used for all activity on Sui. moduleModuleA component of a Move package that defines interaction with on-chain objects. that depends on DeepBookV3 and calls its functions directly.\nYour protocol trades as part of its own onchain logic, and your code must enforce invariants across the trade.\n\nSDK and programmable transaction blocks (PTBs)\nTypeScript that composes DeepBookV3 calls into a transaction with @mysten/deepbook-v3.\nYour app, bot, wallet, or backend submits trades on behalf of a signer, and no custom onchain logic wraps the trade.\n\nRead-only data\nQueries against the DeepBookV3 Indexer or a Sui RPC endpoint.\nYou display prices, order books, or trade history, and you never sign a transaction.\n\nThe models are not exclusive. A common pattern is to publish a small Move module for the logic that needs onchain guarantees, then call that module from a PTB your backend builds.\n\nIntegrate as a Move package​\n\nAdd DeepBookV3 to the [dependencies] section of your Move.toml file:\n\nMove.toml\ndeepbook = { mvr = \"@deepbook/core\" }\n\nYour module then calls DeepBookV3 functions directly. All trading endpoints on Pool are public functions rather than entry functions, so you do not need to write a wrapper. Because your module holds the returned values, DeepBook becomes one step inside a larger operation that your own code guards. This model suits vaults, routers, and any protocol that borrows through flash loans and must repay from its own logic in the same transaction.\n\nThe tradeoff is lifecycle cost. You publish a package, plan its upgrades, and track DeepBookV3 contract versions yourself. See Upgrading Packages for the upgrade process, and Contract Information for current package addressesAddressA unique, anonymous identity on a blockchain network..\n\nTo start with this model, read Design for the architecture, then Contract Information for the endpoint reference.\n\nIntegrate with the SDK and PTBs​\n\nInstall the TypeScript SDK:\n\nnpm\nYarn\npnpm\nnpm install @mysten/deepbook-v3\n\nyarn add @mysten/deepbook-v3\n\npnpm add @mysten/deepbook-v3\n\nThe SDK builds PTB commands that target the same public functions a Move module calls. You publish nothing and maintain no upgrade path. The SDK also ships default coin and pool constants, balance manager handling, and read helpers, which removes most of the address bookkeeping.\n\nTo start with this model, read the DeepBookV3 SDK documentation, then get hands-on: fund a BalanceManager and run the spot trading workflow with real TestnetTestnetStaging network for testing changes before production deployment. transactions.\n\nWhat both models share​\n\nBoth models use the same objects and the same fee rules:\n\nBalance manager: Order placement requires a BalanceManager and a trade proof in either model. See BalanceManager.\n\nSwaps without a balance manager: The swap endpoints accept coins directly and return coins, so routers and aggregators can trade without creating a BalanceManager. See Swaps.\n\nFees: Fee rules and DEEP staking benefits apply the same way, regardless of how you build the transaction.\n\nDeepBookV3 tokenomics​\n\nThe DEEP token pays for trading fees on the exchange. Users can pay trading fees using DEEP tokens or input tokens, but owning, using, and staking DEEP continues to provide the most benefits to active DeepBookV3 traders on the Sui network.\n\nAs an example, governance determines the fee for paying in DEEP tokens, which costs 20% less than the fee for using input tokens.\n\nUsers that stake DEEP can enjoy taker and maker incentives. Taker incentives can reduce trading fees by half, dropping them to as low as 0.25 basis points (bps) on stable pairs and 2.5 bps on volatile pairs. Maker incentives provide rebates based on the maker volume you generate.\n\nLiquidity support​\n\nSimilar to order books for other market places, DeepBookV3's CLOB architecture enables you to enter market and limit orders. You can place an ask to sell SUI tokens at a price you set, known as a limit order, or sell at the market's going rate. To buy SUI, you can place a bid at the current market price or set a limit price. The CLOB fulfills limit orders only when it finds a match between a buyer and seller.\n\nIf you put in a limit order for 1,000 SUI, and no single seller is currently offering that quantity of tokens, DeepBookV3 automatically pools the current asks to meet the quantity of your bid.\n\nTransparency and privacy​\n\nAs a CLOB, DeepBookV3 works like a digital ledger, logging bids and asks in chronological order and automatically finding matches between the two sides. It takes into account user parameters on trades such as prices.\n\nThe open digital ledger lets you view trades and prices, giving clear proof of fairness. You can use this transparency to create metrics and dashboards to monitor trading activity.\n\nDocumentation​\n\nThis documentation outlines the design of DeepBookV3, its public endpoints, and provides guidance for integrations. The SDK abstracts away a lot of the complexities of interacting with the chain and building programmable transaction blocks, lowering the barrier of entry for active market making.\n\nOpen source​\n\nDeepBookV3 is open for community development. You can use the Sui Improvement Proposals (SIPs) process to suggest changes to make DeepBookV3 better.\n\nContract Information\nIn this section\nBalanceManager\nOrders\nFlash Loans\nSwaps\nStaking and Governance\nPermissionless Pool Creation\n+ 3 more\n\n→\nDeepBookV3 SDK\nIn this section\nBalanceManager\nPools\nOrders\nFlash Loans\nSwaps\nStaking and Governance\n+ 2 more\n\n→\n\nChoose your integration modelIntegrate as a Move package\nIntegrate with the SDK and PTBs\nWhat both models share\n\nDeepBookV3 tokenomics\nLiquidity support\nTransparency and privacy\nDocumentation\nOpen source\n\nWas this page helpful?","tokens":1890,"crawled_at":1791194522578}
+{"id":10396,"url":"https://a16zcrypto.com/posts/article/safe-harbor-sec-blockchain-apps","domain":"a16zcrypto.com","chapter":"research","title":"A safe harbor for software: Why the SEC should clarify broker rules for blockchain apps - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nA safe harbor for software: Why the SEC should clarify broker rules for blockchain apps\nMiles Jennings, Aiden Slavin, and David Sverdlov\n08.13.25\n\nTags & Share Tags\ngovernment agencies\npolicy & regulation\nregulatory know-how\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nThe U.S. Securities and Exchange Commission recently acknowledged what many in the crypto industry have long recognized: Digital assets and blockchain technologies are poised to transform capital markets.\n\nThe agency just launched “Project Crypto,” an ambitious plan to move U.S. capital markets onchain. The announcement followed a report from President Trump’s Working Group on Digital Assets that called for sweeping reforms, such as granting the CFTC authority to regulate spot markets of non-security digital assets and providing regulatory clarity to decentralized finance (DeFi) platforms. These efforts signal a growing recognition of the benefits that blockchain technologies can deliver. They also show a growing understanding that digital assets and blockchain technologies don’t fit neatly into legacy regulatory frameworks — and that forcing them into pre-existing molds may do more harm than good.\n\nThat’s why we, together with the DeFi Education Fund, are proposing a safe harbor from the broker-dealer registration requirements of the Securities Exchange Act of 1934 for blockchain applications — the neutral software programs that enable users to interact with public blockchain networks and smart contract protocols, like DeFi and non-fungible token (NFT) marketplace protocols. By reducing reliance on intermediaries, these apps make it possible for tokenized securities to capitalize on the benefits of blockchain technology: truly disintermediated, automated, trustless and instantaneous transactions, with substantially lower costs.\n\nWhat’s the problem?\n\nApps are software — typically embedded in wallets or deployed via websites — that enable users to interact with decentralized blockchain systems without taking custody of assets, exercising discretion, or acting on behalf of users. They simply provide a user interface that helps people transact directly onchain. This opens an entire world of peer-to-peer transactions, where users can make stablecoin payments, purchase network tokens on decentralized exchanges, trade digital collectibles like NFTs, or engage in borrowing and lending transactions all without relying on any intermediaries.\n\nWhile decentralized blockchain systems underlying apps are clearly excluded from the SEC’s broker-dealer registration regimes, apps face regulatory uncertainty because they are typically developed and maintained by centralized actors. The SEC has previously taken the position — through enforcement actions and Wells notices — that developers of apps could be deemed brokers if they enabled users to transact in securities. That approach is flawed and threatens to chill innovation in one of the most promising areas of the new digital financial system.\n\nConcerns about the SEC’s prior approach aren’t just about inconvenient regulatory burdens. Rather, requiring broker registration for neutral apps would force software developers to take on roles and responsibilities they never assumed — acting as gatekeepers, taking custody, and intermediating activity — all of which undermine the benefits of blockchains systems and create new risks for users.\n\nWhat’s the solution?\n\nWe propose a safe harbor that provides a rebuttable presumption that a software interface that enables users to engage in peer-to-peer transactions, including in transactions of tokenized securities, is not engaged in broker-dealer activity. To qualify for this safe harbor, an app must meet four objective criteria:\n\nNon-custodial: The app must never take control of user funds. All signing and transaction submission must be user-initiated.\n\nNo discretion: The app must not exercise discretion on behalf of the user in the execution of transactions. It may use optimization software (routers or solvers) to identify best paths, but only if they operate on objective parameters, are source-available or auditable, and do not involve compensation contingent on routing outcomes.\n\nNo solicitation or investment recommendations: The app must avoid providing investment recommendations, and may only passively display neutral market data or functionality.\n\nUnderlying protocols must be decentralized: The app interfaces with protocols that have eliminated operational control — meaning they are autonomous, permissionless, non-custodial, and credibly neutral — or have clearly demonstrated their good faith intention to decentralize. Limited exceptions may apply for early-stage protocols under certain thresholds.\n\nWhy now?\n\nBlockchain technologies offer enormous benefits — reduced costs, faster settlement, expanded access — and software interfaces are critical infrastructure for unlocking these gains. Recognizing this, the administration is in a race to unlock innovation, and that starts with regulatory clarity. Developers shouldn’t have to guess whether building public, neutral, and non-custodial software exposes them to the risk of being treated like financial intermediaries.\n\nThis proposal gives the SEC a pathway to set boundaries, reinforce its mission to protect investors, and encourage the responsible development of decentralized technologies. Doing so will help ensure America leads in digital infrastructure for the decades ahead.\n\nRead our full proposal.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nCharts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":2066,"crawled_at":1791194525754}
+{"id":10397,"url":"https://docs.compound.xyz/compound-js","domain":"docs.compound.xyz","chapter":"defi_protocols","title":"Compound.js SDK Documentation","text":"Compound.js\nComet\nGovernance\ncTokens (v2)\nComptroller (v2)\nPrice Feed (v2)\nHelpers\n\nCompound.js\nConstructor\nEthereum Read\nEthereum Trx\n\nCompound.js\nIntroduction\nCompound.js is a JavaScript SDK for Ethereum and the Compound Protocol. It wraps around Ethers.js, which is its only dependency. It is designed for both the web browser and Node.js.\nThe SDK is currently in open beta. Use at your own risk.\nFor bugs reports and feature requests, either create an issue in the GitHub repository or send a message in the Development channel of the Compound Discord.\nConstructor\nCreates an instance of the Compound.js SDK.\n[provider] (Provider | string) Optional Ethereum network provider. Defaults to Ethers.js fallback mainnet provider.\n[options] (object) Optional provider options.\nRETURN (object) Returns an instance of the Compound.js SDK.\nvar compound = new Compound(window.ethereum); // web browser\n\nvar compound = new Compound('http://127.0.0.1:8545'); // HTTP provider\n\nvar compound = new Compound(); // Uses Ethers.js fallback mainnet (for testing only)\n\nvar compound = new Compound('goerli'); // Uses Ethers.js fallback (for testing only)\n\n// Init with private key (server side)\nvar compound = new Compound('https://mainnet.infura.io/v3/_your_project_id_', {\nprivateKey: '0x_your_private_key_', // preferably with environment variable\n});\n\n// Init with HD mnemonic (server side)\nvar compound = new Compound('mainnet' {\nmnemonic: 'clutch captain shoe...', // preferably with environment variable\n});\n\nCompound III (Comet) Object Initialization. This accepts the same parameters as the Compound constructor. An error will be thrown initially and whenever a method is called if the provider does not match the network of the specific Comet deployment. The SDK constants as well as a method in the Comet documentation note the Comet deployments that Compound.js supports.\nvar compound = new Compound(window.ethereum);\nvar comet = compound.comet.MAINNET_USDC(); // provider from `compound` will be used unless on is explicitly passed\n\nEthereum Methods\nThese methods facilitate interactions with the Ethereum blockchain.\nEthereum Read\nThis is a generic method for invoking JSON RPC’s eth_call with Ethers.js. Use this method to execute a smart contract’s constant or non-constant member without using gas. This is a read-only method intended to read a value or test a transaction for valid parameters. It does not create a transaction on the block chain.\naddress (string) The Ethereum address the transaction is directed to.\nmethod (string) The smart contract member in which to invoke.\n[parameters] (any[]) Parameters of the method to invoke.\n[options] (CallOptions) Options to set for eth_call, optional ABI (as JSON object), and Ethers.js method overrides. The ABI can be a string of the single intended method, an array of many methods, or a JSON object of the ABI generated by a Solidity compiler.\nRETURN (Promise<any>) Return value of the invoked smart contract member or an error object if the call failed.\nconst cEthAddress = Compound.util.getAddress(Compound.cETH);\n\n(async function() {\n\nconst srpb = await Compound.eth.read(\ncEthAddress,\n'function supplyRatePerBlock() returns (uint256)',\n// [], // [optional] parameters\n// {} // [optional] call options, provider, network, plus Ethers.js \"overrides\"\n);\n\nconsole.log('cETH market supply rate per block:', srpb.toString());\n\n})().catch(console.error);\n\nEthereum Trx\nThis is a generic method for invoking JSON RPC’s eth_sendTransaction with Ethers.js. Use this method to create a transaction that invokes a smart contract method. Returns an Ethers.js TransactionResponse object.\naddress (string) The Ethereum address the transaction is directed to.\nmethod (string) The smart contract member in which to invoke.\n[parameters] (any[]) Parameters of the method to invoke.\n[options] (CallOptions) Options to set for eth_sendTransaction, (as JSON object), and Ethers.js method overrides. The ABI can be a string optional ABI of the single intended method, an array of many methods, or a JSON object of the ABI generated by a Solidity compiler.\nRETURN (Promise<any>) Returns an Ethers.js TransactionResponse object or an error object if the transaction failed.\nconst oneEthInWei = '1000000000000000000';\nconst cEthAddress = '0x4ddc2d193948926d02f9b1fe9e1daa0718270ed5';\nconst provider = window.ethereum;\n\n(async function() {\nconsole.log('Supplying ETH to the Compound Protocol...');\n\n// Mint some cETH by supplying ETH to the Compound Protocol\nconst trx = await Compound.eth.trx(\ncEthAddress,\n'function mint() payable',\n[],\n{\nprovider,\nvalue: oneEthInWei\n}\n);\n\n// const result = await trx.wait(1); // JSON object of trx info, once mined\n\nconsole.log('Ethers.js transaction object', trx);\n})().catch(console.error);","tokens":1190,"crawled_at":1791194536129}
+{"id":10398,"url":"https://docs.sui.io/onchain-finance/closed-loop-token","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Closed-Loop Token | Sui Documentation","text":"Using the Closed-Loop TokenClosed-Loop TokenA token that can be used only for a specific service or authorized account. standard, you can limit the applications that can use the token and set up custom policies for transfers, spends, and conversions. The sui::token module in the Sui framework defines the standard.\n\nBackground and use cases​\n\nThe Currency Standard on Sui is an example of an open-loop system. Coins are free-flowing, wrappable, freely transferable, and you can store them in any application.\n\nSome applications, however, require constraining the scope of the token to a specific purpose. For example, some applications might need a token that you can only use for a specific service, or that only an authorized account can use, or a token that you can block certain accounts from using. A real-world analogy would be a bank account that is regulated, bank-controlled, and compliant with certain rules and policies.\n\nDifference with Coin​\n\nUnlike Coin, which has key + store abilities and thus supports wrapping and public transfers, Token has only the key ability and cannot be wrapped, stored as a dynamic field, or freely transferred (unless there's a custom policy for that). Due to this restriction, Token can only be owned by an account and can't be stored in an application (however, it can be spent.\n\n// defined in `sui::coin`\npublic struct Coin<phantom T> has key, store { id: UID, balance: Balance<T> }\n\n// defined in `sui::token`\npublic struct Token<phantom T> has key { id: UID, balance: Balance<T> }\n\nCompliance and rules​\n\nYou can set up any rules for transfers, spends, and conversions for the tokens you create. You specify these rules per action in the TokenPolicy. Rules are custom programmable restrictions that you can use to implement any request authorization or validation logic.\n\nFor example, a policy can set a limit on a transferTransferChanging the owner of an asset. - X tokens per operation; or require user verification before spending tokens; or allow spending tokens only on a specific service.\n\nYou can reuse rules across different policies and applications; and you can freely combine rules to create complex policies.\n\nPublic actions​\n\nTokens have a set of public and protected actions that you can use to manage the token. Public actions are available to everyone and don't require any authorization. They have similar APIs to coins, but operate on the Token type:\n\ntoken::keep: Send a token to the transactionTransactionA number of commands that execute on inputs to define the result of the transaction. sender\n\ntoken::join: Join two tokens\n\ntoken::split: Split a token into two, specify the amount to split\n\ntoken::zero: Create an empty (zero balance) token\n\ntoken::destroy_zero: Destroy a token with zero balance\n\nProtected actions​\n\nProtected actions are ones that issue an ActionRequest - a hot-potato struct that must be resolved for the transaction to succeed. There are three main ways to resolve an ActionRequest, most common of which is through the TokenPolicy.\n\ntoken::transfer: Transfer a token to a specified addressAddressA unique, anonymous identity on a blockchain network.\n\ntoken::to_coin: Convert a token to a coin\n\ntoken::from_coin: Convert a coin to a token\n\ntoken::spend: Spend a token on a specified address\n\nThe previous methods are included in the base implementation, however it is possible to create ActionRequests for custom actions.\n\nToken policy and rules​\n\nProtected actions are disabled by default but you can enable them in a TokenPolicy. Additionally, you can set custom restrictions called rules that a specific action must satisfy for it to succeed.\nRelated topics\n\nCurrency Standard\nThe Sui Currency Standard enables you to create a broad range of fungible tokens on the Sui network using the centralized coin registry system, with support for regulated coins, supply state management, and metadata capabilities.\nWrapped Objects\nWrapped objects are object data structures nested inside of another object data structure. Objects can be wrapped directly, through `Option`, or through `vector` fields.\nCustom Object Transfer Rules\nCustom transfer rules enable you to define a set of rules that must be met before Sui considers a transfer operation valid.\nSpending\nClosed-Loop Tokens lack the `store` ability, so they use a `spend` method that consumes the token and moves its balance into an `ActionRequest` for confirmation or burning.\n\nBackground and use cases\nDifference with Coin\nCompliance and rules\nPublic actions\nProtected actions\nToken policy and rules\n\nWas this page helpful?","tokens":1143,"crawled_at":1791194543377}
+{"id":10399,"url":"https://docs.compound.xyz/compound-js/price-feed","domain":"docs.compound.xyz","chapter":"defi_protocols","title":"Compound.js Docs | Price Feed (v2)","text":"Compound.js\nComet\nGovernance\ncTokens (v2)\nComptroller (v2)\nPrice Feed (v2)\nHelpers\n\nCompound v2 Get Price\n\nCompound.js\nPrice Feed Methods\nThese methods facilitate interactions with the v2 Price Feed smart contracts. For Compound III price feed methods, see the Comet section.\nCompound v2 Get Price\nGets an asset’s price from the Compound v2 Protocol price feed. The price of the asset can be returned in any other supported asset value, including all cTokens and underlyings.\nasset (string) A string of a supported asset in which to find the current price.\n[inAsset] (string) A string of a supported asset in which to express the asset parameter’s price. This defaults to USD.\nRETURN (string) Returns a string of the numeric value of the asset.\nconst compound = new Compound(window.ethereum);\nlet price;\n\n(async function () {\n\nprice = await compound.getPrice(Compound.WBTC);\nconsole.log('WBTC in USD', price); // 6 decimals, see Price Feed docs\n\nprice = await compound.getPrice(Compound.BAT, Compound.USDC); // supports cTokens too\nconsole.log('BAT in USDC', price);\n\n})().catch(console.error);","tokens":274,"crawled_at":1791194554078}
+{"id":10400,"url":"https://stack.olas.network/open-autonomy/api/cli/utils/click_utils","domain":"stack.olas.network","chapter":"crypto_ai_depin","title":"Utils - Olas Stack Developer Documentation","text":"autonomy.cli.utils.click_utils\n\nUseful click utils.\n\nimage_profile_flag\n\ndef image_profile_flag(default: str = ImageProfiles.PRODUCTION,\nmark_default: bool = True) -> Callable\n\nChoice of one flag between: '--local/--remote'.\n\nabci_spec_format_flag\n\ndef abci_spec_format_flag(\ndefault: str = FSMSpecificationLoader.OutputFormats.YAML,\nmark_default: bool = True) -> Callable\n\nFlags for abci spec outputs formats.\n\nchain_selection_flag\n\ndef chain_selection_flag(\ndefault: ChainType = ChainType.LOCAL,\nmark_default: bool = True,\nhelp_string_format:\nstr = \"To use {} chain profile to interact with the contracts\"\n) -> Callable\n\nFlags for abci spec outputs formats.\n\nsys_path_patch\n\n@contextlib.contextmanager\ndef sys_path_patch(path: Path) -> Generator\n\nPatch sys.path variable with new import path at highest priority.\n\nPathArgument Objects\n\nclass PathArgument(click.Path)\n\nPath parameter for CLI.\n\nconvert\n\ndef convert(value: Any, param: Optional[click.Parameter],\nctx: Optional[click.Context]) -> Optional[Path]\n\nConvert path string to pathlib.Path\n\nNFTArgument Objects\n\nclass NFTArgument(click.ParamType)\n\nNFT parameter for minting tools.\n\nget_metavar\n\ndef get_metavar(param: click.Parameter, *args: Any, **kwargs: Any) -> str\n\nGet metavar\n\nconvert\n\ndef convert(value: Any, param: Optional[click.Parameter],\nctx: Optional[click.Context]) -> Optional[Union[Path, IPFSHash]]\n\nConvert path string to pathlib.Path\n\nimage_author_option\n\ndef image_author_option(fn: Callable) -> Callable\n\nWrap function with clik option for image-author\n\nPublicIdOrHashOrTokenId Objects\n\nclass PublicIdOrHashOrTokenId(PublicIdParameter)\n\nA click parameter that can be a public id, an IPFS hash or a token id.\n\nget_metavar\n\ndef get_metavar(param: Any, ctx: click.Context) -> str\n\nReturn the metavar default for this param if it provides one.\n\nconvert\n\ndef convert(value: str, param: Any, ctx: Optional[click.Context]) -> PublicId\n\nReturns integer token id if value is numeric, else try to parse public id or hash.","tokens":497,"crawled_at":1791194562931}
+{"id":10401,"url":"https://docs.sui.io/onchain-finance/closed-loop-token/spending","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Spending | Sui Documentation","text":"Closed-Loop Tokens differ from standard Coin types in a key way: Token types do not have the store ability. This means you cannot store a Token inside another objectObjectThe basic unit of storage on Sui. or add it to a balance field the way you can with a Coin. An application that accepts a Token as payment cannot keep it.\n\nTo handle this, Token provides a spend method. When you call spend, the token is consumed and its balance moves into an ActionRequest. You then deliver the ActionRequest to the TokenPolicy (which accumulates the spent balance) or burn it directly with a TreasuryCap.\n\nSpend action​\n\nTokens can be spent by calling the spend method. It takes the following arguments:\n\n// module sui::token\npublic fun spend<T>(token: Token<T>, ctx: &mut TxContext): ActionRequest<T>;\n\nAs the signature shows, the Token object is consumed. Its balance becomes the spent_balance in the ActionRequest.\n\nSpent token​\n\nThe ActionRequest for the spend action contains the Balance of the spent Token, and it can either be confirmed with a TreasuryCap or delivered to the TokenPolicy. In the first case, the balance is burned directly in the TreasuryCap, and in the second case, it's delivered to the TokenPolicy spent_balance.\n\nSpent balance cannot be used in any way, and it is not possible to withdraw it. The only available action is flushing - burning the spent_balance by bringing a TreasuryCap.\n\nGating the spend action​\n\nNormally, the spend action should have at least one rule assigned to it to prevent aimless spending, and the recommended way of authorizing the spend in an application that accepts the token is to stamp it right in the function where a spend is performed. For example:\n\n/// Rule-like witness to stamp the ActionRequest\npublic struct GiftShop has drop {}\n\n/// Spend the token and return a Gift + ActionRequest\npublic fun buy_gift(\ntoken: Token<CREDITS>,\nctx: &mut TxContext\n): (Gift, ActionRequest<CREDITS>) {\n\n// token is spent\nlet action_request = token::spend(token, ctx);\n\n// stamp the ActionRequest as performed by GiftShop\ntoken::add_approval(GiftShop {}, &mut action_request, ctx);\n\n// return already stamped ActionRequest\n(Gift { ... }, action_request)\n}\n\nRelated topics\n\nClosed-Loop Token\nClosed-Loop tokens can only be used for a specific service or by authorized users.\nAction Request\nTokens do not allow transfers, conversions, or spends by default. To allow these actions, use an `ActionRequest`.\nToken Policy\nA `TokenPolicy` is a shared object that defines a token's allowed actions and conditions. Wallets and other financial services often use `TokenPolicy` objects.\n\nSpend action\nSpent token\nGating the spend action\n\nWas this page helpful?","tokens":671,"crawled_at":1791194564356}
+{"id":10402,"url":"https://gov.uniswap.org/u/Ignas","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Profile - Ignas - Uniswap Governance","text":"Ignas\n\nIntroduction\n\nFirst, I’m an active DeFi user and independent researcher. I share my findings and thoughts on X and my personal blog.\n\nI’m also the co-founder of Pink Brains DeFi Creator Studio, which focuses on elevating quality projects through authentic representation.\n\nIntroduction\n\nFirst, I’m an active DeFi user and independent researcher. I share my findings and thoughts on X and my personal blog.\n\nI’m also the co-founder of Pink Brains DeFi Creator Studio, which focuses on elevating quality projects through authentic representation.\n\nCore values\n\nCurrently, DeFi DAOs face several internal issues, such as voter apathy leading to governance attacks, insider voting, and voting concentration among a few active voting addresses.\n\nAdditionally, they face external challenges like regulatory uncertainty.\n\nI believe in a decentralized future, even if it seems naive.\n\nHowever, the current state of crypto is plagued by misaligned incentives that prioritize short-term speculative gains over the core DeFi values of self-sovereignty and custody.\n\nEqually concerning is the trend of McKinsification in DAOs, where decisions are increasingly made by one or two professional consultant delegates. This discourages individual participation, as their opinions and votes have less impact.\n\nTo make DeFi DAOs viable, we must align incentives to encourage active participation in governance from the broader crypto community.\n\nI believe that community must be at the core of every DAO.\n\nWithout giving the community a say in protocol governance, we’re no better than the Web2 companies we aim to replace—companies that view their “community” merely as users to extract value from.\n\nI will support initiatives that align token holders with the protocol, such as revenue sharing or other methods to bring value to the token.\n\nToken holders are frustrated with exploitative tokenomics that only benefit early insiders who acquired tokens at much lower prices, leaving no upside for new investors. Without incentives to buy and hold tokens, the attractiveness and health of DAOs decline.\n\nFinally, I will highlight key votes and decisions of the DAO on X and my blog, as I believe the general public is often unaware of important actions being taken.\n\nDisclosure\n\nI am the co-founder of Pink Brains at a DeFi creator studio dedicated to promoting DeFi projects through educational content. You can find the full list of projects we have worked on at our landing page.\n\nI plan to apply as a delegate to other DAOs too, with the same mission of strengthening them and aligning token holders with the protocol.\n\nI always make appropriate disclosures and remove myself from voting when necessary.","tokens":674,"crawled_at":1791194569578}
+{"id":10403,"url":"https://www.getfoundry.sh/forge/scripting-internals","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"How scripting works – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nHow scripting works\n\nThe scripting guide introduces deployment scripts. This page explains how an ordinary forge script invocation turns Solidity execution into transactions, and which addresses and state each stage uses. Network-specific modes, such as Tempo transaction batching, can change the transaction format and deployment behavior.\n\nFrom a script to transactions\n\nForge executes the script contract locally. The script contract itself is not deployed to the target network. Instead, broadcasting cheatcodes identify calls and creations that should become transactions.\n\nStageWhat runsWhat carries forward\nCompile and link\nThe Solidity compiler and library linker\nScript bytecode, contract artifacts, and library addresses\n\nExecute the script\nThe script constructor, optional setUp(), then run() or the function selected by --sig\nTransactions collected from broadcast calls, plus required library deployments\n\nSimulate transactions\nThe collected transactions against separate local EVM state backed by the target RPC\nExecution results, gas estimates, and deployment metadata\n\nBroadcast\nSigning and RPC submission, when --broadcast is set\nTransaction hashes and receipts\n\nVerify\nExplorer verification, when requested\nVerification results for deployed contracts\n\nWith no RPC URL, Forge can execute the script locally but cannot perform the RPC-backed transaction simulation or send the transactions. With an RPC URL and without --broadcast, it executes and simulates without submitting transactions. --skip-simulation skips the separate transaction simulation; it does not skip executing the script to collect transactions.\n\nScript caller, transaction sender, and signer\n\nThese are distinct pieces of information:\n\nThe script caller is the address Forge uses to call setUp() and the selected script function. It determines msg.sender in that script frame.\n\nThe transaction sender is the address recorded in a collected transaction's from field.\n\nThe signer supplies the signature for that sender. Choosing an address does not supply its private key or unlock an account.\n\nFor ordinary wallet-backed scripts, Forge initializes the script caller from the configured sender, whose default is 0x1804c8AB1F12E6bbf3894d4083f33e07309d1f38. A single raw private key or Turnkey address supplies an inferred caller. Otherwise, when --sender is absent, Forge can infer the caller from a sole available wallet address, or from the connected browser wallet. Multiple wallets require an explicit choice if we want a predictable script caller. Network-specific session signers have their own sender resolution.\n\nThe broadcast cheatcodes choose the transaction sender separately:\n\nInvocationTransaction senderSigning material\nvm.startBroadcast(address)\nThe supplied address\nMust be available separately when sending\n\nvm.startBroadcast(uint256)\nThe address derived from that private key\nThe key is added to Forge's script wallets\n\nvm.startBroadcast()\nExplicit --sender, otherwise the sole available signer, otherwise the current transaction caller\nMust be available when sending\n\nThe same selection applies to the three vm.broadcast overloads. broadcast records the next eligible call; startBroadcast records eligible calls until stopBroadcast. The scope is the call depth at which broadcasting starts. Cheatcode calls are excluded. Calls made inside a deployed contract remain part of that contract's transaction rather than becoming additional top-level transactions.\n\n--sender alone is enough for simulation, but normal broadcasting also needs a matching wallet, such as --account deployer. With --unlocked, the RPC node is responsible for sending from the selected account. Forge rejects ordinary broadcasts whose transaction sender is the default Foundry address.\n\nWhat msg.sender means during broadcasting\n\nStarting a broadcast changes the sender of outgoing calls. It does not rewrite the caller of the already-running script frame. For example, the script caller can be Foundry's default address while vm.startBroadcast(deployer) sends the next call from deployer.\n\nInside a contract called directly by that transaction, msg.sender is the transaction sender. Inside the script, it is still the script caller. A callback or another nested contract call has its own caller as usual.\n\nWith the default script_execution_protection = true, Forge rejects a msg.sender opcode read in the main script's broadcasting frame when that caller differs from the broadcast sender. It also protects against relying on the ephemeral script's address(this). These are runtime opcode checks: they do not track values captured before broadcasting, and compiler optimizations can move a read outside the guarded region. Disabling the protection does not make the addresses equal.\n\nPass the intended owner or deployer explicitly when constructing transaction arguments. This example uses the same address for broadcasting and ownership, without depending on the script frame's caller:\n\nscript/DeployOwned.s.sol\n// SPDX-License-Identifier: MIT\npragma solidity ^0.8.20;\n\nimport {Script} from \"forge-std/Script.sol\";\n\ncontract OwnedCounter {\naddress public immutable owner;\nuint256 public number;\n\nconstructor(address initialOwner) {\nowner = initialOwner;\n}\n\nfunction increment() external {\nrequire(msg.sender == owner, \"not owner\");\nnumber++;\n}\n}\n\ncontract DeployOwned is Script {\nfunction run() public returns (OwnedCounter counter) {\naddress deployer = vm.envAddress(\"DEPLOYER\");\n\nvm.startBroadcast(deployer);\ncounter = new OwnedCounter(deployer);\ncounter.increment();\nvm.stopBroadcast();\n}\n}\n\nFor a local run of the example, choose an address and use it consistently:\n\n$ export DEPLOYER=0x0000000000000000000000000000000000001337\n$ forge script script/DeployOwned.s.sol:DeployOwned --sender \"$DEPLOYER\"\n\nFor deployment, set DEPLOYER to the address controlled by the chosen wallet and also supply the RPC and wallet options. Keep --sender and the wallet address aligned; a raw key's inferred script caller and an explicitly different broadcast sender can otherwise disagree.\n\nCREATE and CREATE2\n\nA direct new Contract(...) inside a broadcast produces a contract-creation transaction. Its address depends on the transaction sender and that sender's nonce. The constructor sees the transaction sender as msg.sender.\n\nA direct new Contract{salt: salt}(...) at the broadcast depth is different. Forge routes it through its configured CREATE2 deployer, by default 0x4e59b44847b379578588920ca78fbf26c0b4956c. The collected transaction calls that deployer with the salt followed by the creation bytecode, including encoded constructor arguments. The factory then performs CREATE2.\n\nThis has three consequences:\n\nThe constructor's msg.sender is the factory, even though the outer transaction comes from the wallet.\n\nThe contract address depends on the factory address, salt, and complete init code. Constructor arguments and linked library addresses are part of that init code.\n\nThe outer transaction still consumes the wallet's nonce, although that nonce is not part of the CREATE2 address formula.\n\nForge's automatic routing validates the expected deployer bytecode. A configured address is not sufficient if it has no code or incompatible code. To use another factory protocol, call that factory explicitly with its own ABI. A CREATE2 performed inside an ordinary called contract also uses that contract's execution context; it is not the script-level rewrite described above.\n\nWhen running locally without an RPC, Forge can install its default deployer for simulation. That does not install it on a target chain. Check the target chain's factory state when preparing a deployment. The CREATE2 guide explains the address formula and compiler settings that affect determinism.\n\nExternal libraries and linking\n\nSolidity contracts that use external library functions contain link references. Those references must be replaced with library addresses before the bytecode can run. Internal library functions that the compiler includes in the contract do not require a separate library deployment.\n\nForge first uses explicitly configured library addresses. For unresolved references it attempts CREATE2 linking when the configured deployer is available and linking succeeds, using create2_library_salt. Otherwise, it links using addresses calculated from the script sender and consecutive CREATE nonces.\n\nRequired library deployments are collected before the script's own broadcast transactions. For CREATE2 libraries, Forge skips a deployment when code already exists at the calculated address. For CREATE libraries, their deployment transactions consume the first sender nonces, so they also affect the addresses of contracts created later by the script.\n\nIf execution discovers a different deployer and no --sender was given, Forge can relink and execute again using that sender. When several deployers are candidates, it warns and retains the configured sender for predeployment. Set --sender explicitly when library deployment ownership matters.\n\nForge can also keep libraries used only by the local script out of the broadcast sequence. This optimization applies only to eligible scripts and reruns them with those libraries deployed locally, checking the candidate before accepting it. It is not a guarantee that every library absent from the final deployed contracts will be omitted. Inspect the prepared sequence to see which library deployments will actually be sent.\n\nChanging a linked library address changes the consuming contract's bytecode. It can therefore change CREATE2 addresses as well as verification inputs, even if the contract's Solidity source is unchanged.\n\nNonces and deployment addresses\n\nWith an RPC, Forge obtains the initial script sender nonce from the resolved fork state. Without an RPC, the initial nonce is 1. --sender-nonce overrides this starting value and is retained if Forge changes the inferred sender during relinking.\n\nDuring script execution, each collected transaction gets a nonce from its sender's simulated account state. Calls and creations consume nonces, and multiple senders have separate nonce sequences. Local script setup must not consume the same nonce as an actual deployment: Forge handles the ephemeral script deployment separately and adjusts local execution bookkeeping accordingly.\n\nFor example, if a sender begins at nonce 7 and needs two ordinary CREATE library deployments, those transactions use nonces 7 and 8. A subsequent direct contract creation uses nonce 9. Adding another required library before it changes that contract's CREATE address.\n\nThe nonce override is a planning input; it does not change the account nonce on the network. If other transactions use the account after simulation, the prepared transactions may no longer be usable as planned. During sequential broadcasting, Forge checks the provider nonce against the expected transaction nonce, retries when the provider is behind, and errors when it is ahead. This check does not reserve nonces against other processes.\n\nWhat simulation does and does not replay\n\nThe first execution runs Solidity script logic, including reads, calculations, and cheatcodes, to construct transaction arguments. Operations outside a broadcast can affect this local execution without becoming transactions.\n\nThe second simulation starts from separate RPC-backed state and runs the collected transactions. It does not rerun run() to recalculate arguments, and script-only state changes are not carried into it. For example, a local storage modification can make script execution succeed, but the transaction simulation will fail if the collected calls depend on that modification existing on-chain.\n\nTransactions are associated with their RPC endpoints and simulated in the corresponding contexts. Forge gathers traces, deployment metadata, and gas usage, then applies the gas-estimate multiplier. --slow also advances the simulated block number between transactions. This does not predict the exact block timestamps, ordering with other users' transactions, or state that will exist when a real transaction is mined.\n\nWhen broadcasting, Forge resolves the required signers and fills transaction details such as fees. Some networks and --skip-simulation workflows require RPC gas estimation immediately before sending. With --slow, or when another condition requires sequential submission, Forge waits for receipts between transactions. An ordinary script containing several transactions is not one atomic operation: an earlier transaction can succeed even if a later one fails.\n\nSaved sequences and resume\n\nForge saves transaction sequences and receipts under the configured broadcast directory, normally grouped by script and chain ID. Dry-run sequences use a dry-run subdirectory. These files record the prepared calls and deployments, not just the source code that produced them.\n\nStarting with Foundry 1.8.4, the authoritative resume state is a private, versioned .recovery.json snapshot stored beside the sensitive sequence under the configured cache directory. The public broadcast file and sensitive sequence are compatibility exports, so preserve both directories and the recovery snapshot until the deployment is complete. Forge imports a consistent pair of generationless exports from an earlier version automatically. Recovery snapshots are not backward compatible: after Foundry 1.8.4 writes one, an older Forge version must not resume that deployment.\n\n--resume loads a saved sequence, checks pending transactions, and continues publishing the remaining transactions. It skips the ordinary transaction-simulation stage. If signing keys are only available through script execution, Forge may execute the script again to collect those keys; the saved transaction sequence remains authoritative.\n\nEditing the script and passing --resume does not regenerate its saved transaction arguments or recreate the original --broadcast execution state. To produce a new transaction plan, run the script again without --resume. To continue a multi-chain saved sequence, use --multi with --resume.\n\nImplementation references\n\nThe main implementation boundaries are sender selection and orchestration, broadcast cheatcodes, linking and resume, local execution, transaction simulation, and transaction submission.\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 01/10/2026, 19:51","tokens":3596,"crawled_at":1791194571228}
+{"id":10404,"url":"https://docs.compound.xyz/compound-js/comptroller","domain":"docs.compound.xyz","chapter":"defi_protocols","title":"Compound.js Docs | Comptroller (v2)","text":"Compound.js\nComet\nGovernance\ncTokens (v2)\nComptroller (v2)\nPrice Feed (v2)\nHelpers\n\nComptroller Methods\nEnter Markets\nExit Market\n\nCompound.js\nComptroller Methods\nThese methods facilitate interactions with the Comptroller smart contract. Methods like claimComp are in the Governance/COMP section.\nEnter Markets\nEnters the user’s address into Compound Protocol markets.\nmarkets (any[]) An array of strings of markets to enter, meaning use those supplied assets as collateral.\n[options] (CallOptions) Call options and Ethers.js overrides for the transaction. A passed gasLimit will be used in both the approve (if not supressed) and mint transactions.\nRETURN (object) Returns an Ethers.js transaction object of the enterMarkets transaction.\nconst compound = new Compound(window.ethereum);\n\n(async function () {\nconst trx = await compound.enterMarkets(Compound.ETH); // Use [] for multiple\nconsole.log('Ethers.js transaction object', trx);\n})().catch(console.error);\n\nExit Market\nExits the user’s address from a Compound Protocol market.\nmarket (string) A string of the symbol of the market to exit.\n[options] (CallOptions) Call options and Ethers.js overrides for the transaction. A passed gasLimit will be used in both the approve (if not supressed) and mint transactions.\nRETURN (object) Returns an Ethers.js transaction object of the exitMarket transaction.\nconst compound = new Compound(window.ethereum);\n\n(async function () {\nconst trx = await compound.exitMarket(Compound.ETH);\nconsole.log('Ethers.js transaction object', trx);\n})().catch(console.error);","tokens":390,"crawled_at":1791194571867}
+{"id":10405,"url":"https://docs.sui.io/onchain-finance/types-of-assets","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Types of Assets | Sui Documentation","text":"On Sui, there are a variety of fungible, non-fungible, and other types of asset standards, each with their own defined usage patterns and capabilities. Choosing the correct standard for your use case is important to enable the correct set of features in your application.\n\nFungible tokens: Coin standard​\n\nThe Coin standard defines fungible tokens that have key and store abilities. Coin supports wrapping and public transfers. It uses the sui::coin moduleModuleA component of a Move package that defines interaction with on-chain objects.. Coin refers to a single objectObjectThe basic unit of storage on Sui. wrapper for a fungible asset.\n\nThe Coin<T> type represents open-loop fungible tokens. Coins are denominated by their type parameter, T, which is also associated with metadata (like name, symbol, and decimal precision) that applies to all instances of Coin<T>.\n\nFungible tokens created using the Coin standard are referred to as coins.\n\nWhen you create a coin using the coin::create_currency function, the publisher of the smart contract that creates the coin receives a TreasuryCap object. The Coin standard uses CoinMetadata to define the coin's metadata.\n\nWhen to use Coin​\n\nUse the Coin standard if you are:\n\nWorking with legacy code or maintaining an existing coin that was created with the sui::coin module\n\nCreating a coin that does not require advanced supply tracking or regulatory features\n\nFamiliar with the CoinMetadata<T> object for metadata storage\n\nLearn more about using Coin.\n\nAddressAddressA unique, anonymous identity on a blockchain network. balances​\n\nAddress balances tie fungible assets to a Sui address directly. They replace the UTXO-style Coin<T> model, where balances are calculated by summing all Coin<T> objects owned by an address. With the address balance functionality, each Sui address can have one address-owned balance for each currency they own, with the total balance being the sum of all Coin<T> objects plus the address balance. Coin<T> and address balances can exist together, however address balances provide several advantages over using Coin<T> alone.\n\nFor the full specification, see SIP-58: Sui Address Balances.\n\nFungible tokens: Currency standard​\n\nThe Currency standard is an example of an open-loop system. It supports free-flowing, wrappable, freely transferable fungible assets that you can store in any application. It uses the sui::coin_registry module and the Currency object for metadata. Currency refers to the object that is created in Coin Registry, which describes the currency properties and setup.\n\nThe Currency<T> type represents open-loop fungible tokens. Currencies are denominated by their type parameter, T, which is also associated with metadata like name, symbol, and decimal precision that applies to all instances of Currency<T>.\n\nFungible tokens created using the Currency standard are referred to as coins.\n\nYou can create coins with the Currency standard using coin_registry::new_currency and coin_registry::new_currency_with_otw:\n\nStandard creation (coin_registry::new_currency): Recommended for most cases. You can call this method any time after the coin type is published.\n\nOne-Time Witness creation (coin_registry::new_currency_with_otw): Uses a One-Time Witness for uniqueness proof. Requires a two-step publish and finalize process.\n\ntip\nThe Coin and Currency standards are both used to create fungible tokens. However, they use different creation methods and store metadata in a different type of object.\nCoin creates tokens using coin::create_currency while Currency uses sui::coin_registry.\nCoin uses CoinMetadata while Currency uses Currency.\nFungible tokens created on Sui using the Coin or Currency standard are referred to as coins.\nFor fungible tokens created on Sui using the Closed-Loop Token standard, the documentation uses the term tokens. In practice, the terms for both these objects are often interchangeable.\n\nCoin Registry​\n\nThe Coin Registry system provides a centralized approach to currency management through the sui::coin_registry module. The registry is a shared object located at address 0xc that stores metadata, supply information, and regulatory status for all registered coin types.\n\nWhen to use Currency​\n\nAssets can offer specialized abilities while following the Currency Standard. For example, you can create regulated coins that allow their creator to add specific addresses to a deny list, so that the identified addresses cannot use the coin as inputs to transactions.\n\nUse the Currency standard if you are:\n\nCreating a new coin and want to use Coin Registry\n\nRequiring advanced supply chain management, such as fixed supply, burn-only supply, or uncontrolled supply\n\nRequiring regulatory tracking such as deny lists\n\nRequiring enhanced integration options with wallets, exchanges, and apps\n\nRequiring future-proofing options and access to ongoing registry improvements\n\nLearn more about using Currency.\n\nPermissioned assets​\n\nThe Permissioned Asset Standard (PAS) enables asset ownership through Account objects. Account objects can hold assets and enforce transferTransferChanging the owner of an asset. controls and compliance checks. There is one Account per address, and an Account can hold any asset type. Assets can only moveMoveAn open source programming language used for all activity on Sui. between Accounts through hot potato requests that must be approved and resolved in the same programmable transactionTransactionA number of commands that execute on inputs to define the result of the transaction. block (PTBProgrammable transaction blocksDefine all user transactions on Sui.).\n\nPAS uses Sui Address Balances. PAS balances are managed by PAS on behalf of the wallet address. They are held in a derived Account object, however, transfers always target the wallet address, not the Account address.\n\nPAS assets are stored in Sui objects and can be queried using the same data access methods as any other address-owned data.\n\nLearn more about Permissioned Asset Standard.\n\nFungible tokens: Closed-Loop TokenClosed-Loop TokenA token that can be used only for a specific service or authorized account. standard​\n\ncaution\nThe Permissioned Asset Standard (PAS) provides a new and improved alternative to the Closed-Loop Token (CLT) standard. Use PAS in place of CLT.\n\nThe Closed-Loop Token standard creates a fungible token that only has the key ability. Closed-loop tokens cannot be wrapped, stored as a dynamic field, or freely transferred (unless a custom policy allows it). Due to this restriction, tokens created with this standard can only be owned by an account and cannot be stored in an application. However, they can be spent. The standard uses the sui::token module.\n\nFungible tokens created using the Closed-Loop Token standard are referred to as tokens.\n\nUsing the Closed-Loop Token standard, you can limit the applications that use the token and set up custom policies for transfers, spends, and conversions. Some applications might need a token that you can only use for a specific service, or that an authorized account can only use, or a token that you can block certain accounts from using. A real-world analogy would be a bank account that is regulated, bank-controlled, and compliant with certain rules and policies.\n\nRefer to Closed-Loop Token for more information.\n\nNon-fungible tokens: Sui objects​\n\nSui uses an object model, meaning every entity on Sui has a unique ID. Whether your application interacts with a pool of fungible tokens or a collection of non-fungible tokens, the application's smart contract interacts with individual objects. Therefore, Sui does not require an NFT standard that pairs globally unique IDs with relevant smart contract addresses to create unique token instances, such as how the ERC-721 standard works.\n\nConsider the following example Move smart contract, where the NFT's name attribute is a field on the object that defines the NFT itself. The TestnetNFT struct defines the NFT with id, name, description, and url fields.\n\nexamples/move/nft/sources/testnet_nft.move\npublic struct TestnetNFT has key, store {\nid: UID,\nname: string::String,\ndescription: string::String,\nurl: Url,\n}\n\nRelated topics\n\nCoin Standard\nThe Coin standard enables you to create a broad range of fungible tokens on the Sui network to satisfy a number of use cases.\nWrapped Objects\nWrapped objects are object data structures nested inside of another object data structure. Objects can be wrapped directly, through `Option`, or through `vector` fields.\nCustom Object Transfer Rules\nCustom transfer rules enable you to define a set of rules that must be met before Sui considers a transfer operation valid.\nClosed-Loop Token\nClosed-Loop tokens can only be used for a specific service or by authorized users.\n\nFungible tokens: Coin standardWhen to use Coin\nAddress balances\n\nFungible tokens: Currency standardCoin Registry\nWhen to use Currency\n\nPermissioned assets\nFungible tokens: Closed-Loop Token standard\nNon-fungible tokens: Sui objects\n\nWas this page helpful?","tokens":2257,"crawled_at":1791194584950}
+{"id":10406,"url":"https://gov.uniswap.org/t/temp-check-return-12-5m-delegated-tokens-to-the-governance-timelock/26099","domain":"gov.uniswap.org","chapter":"governance_daos","title":"[Temp Check] - Return 12.5M Delegated Tokens to the Governance Timelock - Governance-Meta - Uniswap Governance","text":"[Temp Check] - Return 12.5M Delegated Tokens to the Governance Timelock\n\nGovernance-Meta\n\neek637\n\nApril 24, 2026, 7:46pm\n\n1\n\nWith DUNI unlocking greater governance participation from UNI token holders, this proposal undelegates 12.5M UNI currently deployed via the Franchiser, returning the tokens to the Governance Timelock.\n\nSnapshot: https://snapshot.box/#/s:uniswapgovernance.eth/proposal/0xd41b2db93c0348e9061bf786dfcb610d8f35e8447f2e90b37b8f30a9b1a3091e\n\nBackground & Motivation\n\nThese UNI were delegated from the treasury in 2022 and 2023 – 2.5M to the Uniswap Foundation and 10M to a group of active delegates – during periods of low governance participation. The delegations were intended to bootstrap an active delegate base when quorum was at risk and the number of delegates that could meet the proposal threshold was small.\n\nToday, Uniswap’s governance environment looks very different. UNI holders have been actively delegating voting power, and since DUNI was established, passed proposals have averaged roughly 75 million votes in turnout, exceeding quorum by approximately 88%. There are now over 50 delegates with greater than 1M UNI of voting power.\n\nUndelegating these tokens also resolves a potential incentive misalignment caused by the Franchiser mechanism itself. These delegates were selected by the community for their active participation in governance, but the Franchiser was not designed to ensure structural alignment between voting power and economic exposure. The potential for this misalignment should not persist indefinitely when the original reason for implementing it is no longer a concern.\n\nSpecification\n\nThis proposal calls recallMany on the FranchiserFactory contract to retrieve all UNI currently delegated through the Franchiser system.\n\nFranchiser delegations to undelegate:\n\nAddress\nBalance (UNI)\nDelegate\n\n0x3d4ACFD2C8b0641fb8db762179eE5A8dB385E573\n\n2,500,000\n\nUniswap Foundation\n\n0xfB6b912cf7082031822F52E7d7EF59280f97A257\n\n2,499,858\n\nAnode (fka StableLab)\n\n0x8D2642Ec9d19A9333c8593ab7dE1Cc3Be44D2DBC\n\n2,250,000\n\nAxia Network (fka 404DAO)\n\n0x61BeD6a58c4dC592f1dC32f9eC0F67E49208405c\n\n2,250,000\n\nPGov\n\n0xe38e5dD6E11ba18450Cbdd518e8A7Eb5F4A17a11\n\n1,900,000\n\nWintermute\n\n0xD57A44e75E863907fC1957B49B35893BF7874809\n\n493,972\n\nKeyrock\n\n0xA5bB68AC2d70B21F5b7d051542f4799954fB6087\n\n452,626\n\nKPK (fka Karpatkey)\n\n0xfe23b0DDCC9c78B21092e54b846a302C961EFab2\n\n153,544\n\nAtiselsts.eth\n\nOnchain Proposal Spec\n\nThe proposal consists of a single transaction:\n\ntarget: 0xf754A7E347F81cFdc70AF9FbCCe9Df3D826360FA\nfunction: recallMany(address[],address[])\ndelegatees:\n0xE93D59CC0bcECFD4ac204827eF67c5266079E2b5 // Axia\n0xB933AEe47C438f22DE0747D57fc239FE37878Dd1 // Wintermute\n0x3FB19771947072629C8EEE7995a2eF23B72d4C8A // PGov\n0xECC2a9240268BC7a26386ecB49E1Befca2706AC9 // Anode\n0x1855f41B8A86e701E33199DE7C25d3e3830698ba // Keyrock\n0x8787FC2De4De95c53e5E3a4e5459247D9773ea52 // KPK\n0xAac35d953Ef23aE2E61a866ab93deA6eC0050bcD // atiselsts\n0xA37131410A76791f4A0210e91EDD554d85aFb4d4 // UF\ntos:\n0x1a9C8182C09F50C8318d769245beA52c32BE35BC repeated 8 times\n\nNext Steps\n\nRFC posted: April 24, 2026\n\nSnapshot vote: After April 31, 2026\n\nOnchain vote: After a succcessful Snapshot\n\nAdditional Resources\n\nOriginal delegation proposal — Temperature Check\n\nUniswap Foundation founding — Consensus Check\n\nFranchiserFactory contract (Etherscan)\n\nFranchiserFactory source — recallMany\n\n4 Likes\n\nTane\n\nApril 26, 2026, 6:56pm\n\n2\n\nThanks for the proposal, @eek637.\n\nWe dug into the executable spec and want to flag what looks like a target and signature mismatch worth reviewing before Snapshot.\n\nThe address listed in the spec, 0x3d4ACFD2C8b0641fb8db762179eE5A8dB385E573, appears to be the Uniswap Foundation’s Franchiser clone rather than the FranchiserFactory. Its owner() is 0xf754A7E347F81cFdc70AF9FbCCe9Df3D826360FA, which is the contract Etherscan verifies as FranchiserFactory. The function shape also looks off: the factory’s recallMany takes two equal-length arrays, delegatees and tos.\n\nIf we’ve read this right, the corrected call would be:\n\ntarget: 0xf754A7E347F81cFdc70AF9FbCCe9Df3D826360FA\nfunction: recallMany(address[],address[])\ndelegatees:\n0xE93D59CC0bcECFD4ac204827eF67c5266079E2b5 // Axia\n0xB933AEe47C438f22DE0747D57fc239FE37878Dd1 // Wintermute\n0x3FB19771947072629C8EEE7995a2eF23B72d4C8A // PGov\n0xECC2a9240268BC7a26386ecB49E1Befca2706AC9 // Anode\n0x1855f41B8A86e701E33199DE7C25d3e3830698ba // Keyrock\n0x8787FC2De4De95c53e5E3a4e5459247D9773ea52 // KPK\n0xAac35d953Ef23aE2E61a866ab93deA6eC0050bcD // atiselsts\n0xA37131410A76791f4A0210e91EDD554d85aFb4d4 // UF\ntos:\n0x1a9C8182C09F50C8318d769245beA52c32BE35BC repeated 8 times\n\nHappy to be corrected if we’ve misread the layout; sharing in case it saves a vote cycle.\n\nOn the substance, we lean toward supporting the recall. The 2022 and 2023 batches solved a specific bootstrap problem: thin delegate participation and fragile quorum at a moment when neither could be assumed. DUNI changed that environment, and treasury-funded voting power held by selected service providers is harder to justify once organic participation is broader and stake can express itself directly. The recall is the cleaner governance posture in principle.\n\nWhat stays open is quorum variance, not the legitimacy of the recall itself. The RFC notes that post-DUNI turnout averages around 75M votes, roughly 88% above the 40M quorum, which is true. But that average hides per-proposal variance: proposal 92 (Strategic Renewal of Gnosis, Linea, and Mantle Deployments, December 2025) would have missed the 40M affirmative quorum without about 10.9M of Franchiser delegated VP voting FOR. Proposals 94 and 95 still pass without it, so this isn’t a general veto. But one of three substantive post-DUNI votes was a real close call.\n\nThat alone shouldn’t stop the recall, but it does need a mitigation answer before Snapshot. After the recall, how does governance plan to handle the next close-call proposal against the 40M affirmative quorum?\n\n3 Likes\n\neek637\n\nApril 27, 2026, 9:20pm\n\n3\n\nThanks for the sharp eyes here @Tane agreed on both - OP updated.\n\nAxia\n\nMay 1, 2026, 9:03pm\n\n4\n\n@eek637 As one of the delegates who received treasury delegation, I understand and respect the motivation behind this proposal to return the 12.5M UNI to the Governance Timelock.\n\nTreasury delegations served an important purpose when governance participation was low and quorum was often at risk. Now, with DUNI driving significantly higher turnout and a larger distribution of voting power, it makes sense to move toward a more organic delegation structure.\n\nEven after the recall, I plan to continue contributing actively to Uniswap governance and will focus on growing my delegation organically. I’ve been — and will keep — engaging constructively on proposals, research, and discussions, adding value wherever I can by leveraging the high-context I’ve built over the past years contributing to Uniswap governance. My commitment stems from a genuine belief in the long-term success of the protocol and governance, not from any temporary bootstrapped voting power.\n\nThank you for the opportunities that the treasury delegation provided. Looking forward to engaging more in this next phase of UNI governance!\n\n2 Likes\n\nkfx\n\nMay 6, 2026, 6:15am\n\n5\n\nI’d support this in principle, however after having closer look at the proposal, I’m unconvinced by the reasoning.\n\nUNI holders have been actively delegating voting power, and since DUNI was established, passed proposals have averaged roughly 75 million votes in turnout, exceeding quorum by approximately 88%.\n\nThis is factually true however the problem is that there’s a clear survivorship bias. The proposals that don’t have clear push from the leadership simply aren’t reaching the voting stage. I haven’t seen any evidence that the DAO after UNIfication still have enough voting activity to pass proposals that are initiated by 3rd parties or bottom-up proposals from DAO delegates.\n\nHowever, I voted Abstain due to Conflict of Interest, following the Uniswap Principles, as most of my remaining UNI delegation comes from this source.\n\n3 Likes\n\nSEEDGov\n\nMay 6, 2026, 12:58pm\n\n6\n\nWe fully agree with this assessment. It is not entirely accurate to say that the quorum issue has been resolved. Following UNIfication and DUNI, the only proposals that have successfully reached quorum are those promoted by Labs or the Foundation. This suggests that the necessary conditions have been created for certain investors to participate without fear of legal consequences; however, this increase in quorum has not extended to proposals driven by delegates or third parties.\n\nIn fact, none of those proposals have reached quorum, and many have not even made it to a vote for that very reason. A quick look at the Uniswap voting portal, where only two proposals have been approved so far this year, clearly indicates that the DAO is still facing a significant participation problem. From the Uniswap core team’s perspective, this is likely not a problem, since votes seem assured when they’re needed, but from the standpoint of healthy governance, the situation is critical. For that reason, we have abstained on this proposal.\n\nManugotsuka\n\nMay 6, 2026, 4:30pm\n\n7\n\nThe following reflects the views of L2BEAT’s governance team, composed of @kaereste and @Manugotsuka, and it’s based on their combined research, fact-checking, and ideation.\n\nWe voted FOR.\n\nWe think this makes sense given how Uniswap governance has evolved. The original delegations played an important role when participation was low and quorum was a real concern, but that is no longer the case today. Governance looks much healthier now, with broader participation and a more distributed set of active delegates.\n\nWe have generally been cautious about treasury-funded delegation mechanisms like the Franchiser. They can be useful as a temporary solution, but they should not become a permanent part of the system. If the initial goal has been achieved, it is reasonable to step back and let governance operate more organically.\n\neek637\n\nMay 6, 2026, 6:49pm\n\n8\n\nHi all - planning to post the proposal Friday afternoon. For those interested (@Tane , @Manugotsuka), i’ll be posting via Seatbelt using the code in this PR: https://github.com/uniswapfoundation/governance-seatbelt/pull/258. If you pull and run locally, seatbelt show the simulation results.\n\n3 Likes\n\nTane\n\nMay 7, 2026, 4:27pm\n\n9\n\nReviewed PR #258. Inverse fundMany simulation with the right recallMany call, Tenderly checks pass. LGTM, see you on-chain Friday.\n\n2 Likes\n\nAbel189\n\nMay 24, 2026, 4:55pm\n\n10\n\nI support this proposal because it reflects the evolution of Uniswap governance from a bootstrapping phase to a more mature and organically decentralized system.\n\nThe original franchiser delegations served an important purpose during periods where quorum reliability and delegate participation were weaker. Today, governance participation appears substantially healthier, with a broader and more competitive delegate landscape.\n\nReturning these delegated UNI to the governance timelock helps reduce structural governance distortion, especially where voting power is disconnected from direct economic exposure. It also reinforces the principle that treasury-controlled voting influence should remain limited and purpose-driven rather than permanent.\n\nI particularly appreciate that the proposal does not criticize the historical delegates themselves — many contributed meaningfully — but instead focuses on improving long-term governance architecture and legitimacy.\n\nOverall, this looks like a positive normalization step for Uniswap governance maturity.\n\n1 Like\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[Temperature Check]: Delegation of UNI to Active but Underrepresented Delegates\n\nTemperature Check\n\n42\n\n7596\n\nDecember 4, 2023\n\n[RFC]: Delegation of UNI to Active but Underrepresented Delegates\n\nRequests for Comment\n\n18\n\n3046\n\nNovember 10, 2023\n\n[Governance Proposal] Delegation of UNI to Active but Underrepresented Delegates\n\nRequests for Comment\n\n4\n\n2346\n\nDecember 13, 2023\n\nUNI holders should be able to delegate during the voting period with zero delay\n\nRequests for Comment\n\n33\n\n5184\n\nNovember 3, 2020\n\n[RFC] Treasury Delegation Round 2\n\nRequests for Comment\n\n39\n\n1818\n\nApril 28, 2025","tokens":3079,"crawled_at":1791194587368}
+{"id":10407,"url":"https://www.getfoundry.sh/forge/gas-tracking","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Gas tracking – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nGas tracking\n\nForge tracks gas usage to help optimize contracts and catch regressions.\n\nUnder EIP-8037 (Amsterdam), gas has two dimensions: regular gas and state gas. See gas accounting for how reports, snapshots, and lastFrameGas relate to them.\n\nGas reports\n\nGenerate a gas report for all tests:\n\n$ forge test --gas-report\n\nOutput shows gas usage per function:\n\n╭----------------------------------+-----------------+-------+--------+-------+---------╮\n| src/Counter.sol:Counter Contract | | | | | |\n+=======================================================================================+\n| Deployment Cost | Deployment Size | | | | |\n|----------------------------------+-----------------+-------+--------+-------+---------|\n| 156813 | 509 | | | | |\n|----------------------------------+-----------------+-------+--------+-------+---------|\n| | | | | | |\n|----------------------------------+-----------------+-------+--------+-------+---------|\n| Function Name | Min | Avg | Median | Max | # Calls |\n|----------------------------------+-----------------+-------+--------+-------+---------|\n| increment | 43482 | 43482 | 43482 | 43482 | 1 |\n|----------------------------------+-----------------+-------+--------+-------+---------|\n| number | 2424 | 2424 | 2424 | 2424 | 2 |\n|----------------------------------+-----------------+-------+--------+-------+---------|\n| setNumber | 23784 | 23784 | 23784 | 23784 | 1 |\n╰----------------------------------+-----------------+-------+--------+-------+---------╯\n\nFilter gas reports\n\nReport only specific contracts:\n\nfoundry.toml\n[profile.default]\ngas_reports = [\"Counter\", \"Token\"]\n\nExclude contracts:\n\nfoundry.toml\n[profile.default]\ngas_reports_ignore = [\"Test\", \"Script\"]\n\nGas snapshots\n\nCreate a snapshot file to track gas over time:\n\n$ forge snapshot\n\nThis creates .gas-snapshot with gas usage for each test:\n\nCounterTest:test_Increment() (gas: 31293)\nCounterTest:testFuzz_SetNumber(uint256) (runs: 256, μ: 31121, ~: 31277)\n\nCompare against a previous snapshot:\n\n$ forge snapshot --diff\n\nCheck that gas hasn't increased:\n\n$ forge snapshot --check\n\nThis exits with an error if any test uses more gas than recorded.\n\nInline gas tracking\n\nUse gasleft() to measure specific operations:\n\nfunction test_MeasureGas() public {\nuint256 gasBefore = gasleft();\n\ncounter.increment();\n\nuint256 gasUsed = gasBefore - gasleft();\nconsole.log(\"Gas used:\", gasUsed);\n}\n\nSnapshot cheatcodes\n\nTake named snapshots for comparison in tests:\n\nfunction test_GasComparison() public {\nvm.startSnapshotGas(\"increment\");\ncounter.increment();\nuint256 gasIncrement = vm.stopSnapshotGas();\n\nvm.startSnapshotGas(\"setNumber\");\ncounter.setNumber(1);\nuint256 gasSetNumber = vm.stopSnapshotGas();\n\nassertLt(gasSetNumber, gasIncrement);\n}\n\nGas in CI\n\nAdd snapshot checking to your CI pipeline:\n\n- name: Check gas\nrun: forge snapshot --check\n\nUpdate snapshots when gas changes are intentional:\n\n$ forge snapshot\n$ git add .gas-snapshot\n$ git commit -m \"Update gas snapshot\"\n\nPause gas metering\n\nExclude setup code from gas measurements:\n\nfunction test_OnlyMeasureTarget() public {\n// Setup not metered\nvm.pauseGasMetering();\n_complexSetup();\nvm.resumeGasMetering();\n\n// Only this is measured\ntarget.execute();\n}\n\nReset gas metering\n\nReset the gas counter mid-test:\n\nfunction test_ResetMidway() public {\ntarget.setup();\n\nvm.resetGasMetering();\n\n// Gas measurement starts fresh here\ntarget.execute();\n}\n\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":876,"crawled_at":1791194588537}
+{"id":10408,"url":"https://docs.compound.xyz/compound-js/helpers","domain":"docs.compound.xyz","chapter":"defi_protocols","title":"Compound.js Docs | Helpers","text":"Compound.js\nComet\nGovernance\ncTokens (v2)\nComptroller (v2)\nPrice Feed (v2)\nHelpers\n\nHelper & Utility Methods\nGet Address\nGet ABI\nGet Network Name With Chain ID\nGet Balance\n\nCompound.js\nHelper & Utility Methods\nThese methods are helpers for the Compound class and basic utilities for EVM development.\nGet Address\nGets the contract address of the named contract. This method supports contracts used by the Compound Protocol.\ncontract (string) The name of the contract.\n[network] (string) Optional name of the Ethereum network. Main net and all the popular public test nets are supported.\nRETURN (string) Returns the address of the contract.console.log('cETH Address: ', Compound.util.getAddress(Compound.cETH));\n\nGet ABI\nGets a contract ABI as a JavaScript array. This method supports contracts used by the Compound Protocol.\ncontract (string) The name of the contract.\nRETURN (Array) Returns the ABI of the contract as a JavaScript array.console.log('cETH ABI: ', Compound.util.getAbi('cEther'));\n\nGet Network Name With Chain ID\nGets the name of an Ethereum network based on its chain ID. This method returns information only for chains that have a Compound deployment.\nchainId (string) The chain ID of the network.\nRETURN (string) Returns the name of the Ethereum network.console.log('Goerli : ', Compound.util.getNetNameWithChainId(5));\n\nGet Balance\nFetches the current Ether balance of a provided Ethereum address.\naddress (string) The Ethereum address in which to get the ETH balance.\n[provider] (Provider | string) Optional Ethereum network provider. Defaults to Ethers.js fallback mainnet provider.\nRETURN (BigNumber) Returns a BigNumber hexadecimal value of the ETH balance of the address.\n(async function () {\n\nbalance = await Compound.eth.getBalance(myAddress, provider);\nconsole.log('My ETH Balance', +balance);\n\n})().catch(console.error);","tokens":462,"crawled_at":1791194589938}
+{"id":10409,"url":"https://docs.sui.io/onchain-finance/fungible-tokens","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Fungible Tokens | Sui Documentation","text":"Sui provides two standards for creating fungible tokens. Both produce Coin<T> objects that are fully interoperable with wallets, DeFi protocols, and addressAddressA unique, anonymous identity on a blockchain network. balances. The difference is in how you create, configure, and manage the token's metadata and supply.\n\nCoin standard vs currency standard​\n\nFeatureCoin StandardCurrency Standard\nCreation function\ncoin::create_currency\ncoin_registry::new_currency or new_currency_with_otw\n\nMetadata storage\nStandalone CoinMetadata objectObjectThe basic unit of storage on Sui.\nCentralized in CoinRegistry at 0xc\n\nSupply models\nUncontrolled only\nFixed, burn-only, or uncontrolled\n\nRegulatory support\ncreate_regulated_currency_v2\nmake_regulated() during initialization\n\nMetadata updates\nRequires TreasuryCap\nDedicated MetadataCap (can be frozen or deleted)\n\nRPC discovery\nRequires knowing CoinMetadata object ID\nQueryable from the central registry\n\nStatus\nActive\nRecommended for new projects\n\nChoosing a standard​\n\nUse the following guidance to pick the right standard for your project:\n\nRecommended: Currency Standard\nFor new tokens, use the Currency Standard. It provides richer supply controls, centralized metadata discovery, and a dedicated MetadataCap for metadata management.\n\nCreating a new token​\n\nMost projects: Use coin_registry::new_currency. You can call this at any time after publishing your packagePackageSmart contracts on Sui.. See Create Fungible Tokens: Currency Standard.\n\nNeed a One-Time Witness proof: Use coin_registry::new_currency_with_otw in your moduleModuleA component of a Move package that defines interaction with on-chain objects.'s init function. This requires a two-step publish-then-finalize process.\n\nNeed the legacy Coin Standard: Use coin::create_currency in your module's init function. See Create Fungible Tokens: Coin Standard.\n\nConfiguring supply​\n\nOnly the Currency Standard supports supply model configuration:\n\nFixed supply: Mint the total supply during initialization, then call make_supply_fixed to lock the TreasuryCap inside the Currency. No further minting or burning is possible.\n\nBurn-only (deflationary): Mint the initial supply, then call make_supply_burn_only to prevent future minting while still allowing burns.\n\nUncontrolled: The default. The TreasuryCap holder can mint and burn freely.\n\nAdding regulatory controls​\n\nBoth standards support regulated tokens with deny-list capabilities. The Currency Standard simplifies this with make_regulated(allow_global_pause, ctx) during initialization, which returns a DenyCapV2 for managing the deny list. See Regulated Tokens for deny-list management.\n\nMigrating an existing token​\n\nIf you have an existing Coin Standard token, the Currency Standard provides migration functions to register your coin in the CoinRegistry while preserving its existing CoinMetadata object ID. See the Currency Standard reference for migration details.\n\nExample patterns​\n\nThese guides show common token configurations in action:\n\nFixed-supply token: Mint a capped supply at creation and freeze it permanently.\n\nIn-game currency: Mintable game tokens with admin controls.\n\nLoyalty tokens: Non-transferable reward points using the Closed-Loop TokenClosed-Loop TokenA token that can be used only for a specific service or authorized account. standard.\n\nRegulated tokens: Tokens with deny-list and global pause capabilities.\n\nCoin Standard\nIn this section\nCreate Fungible Tokens: Coin Standard\n\n→\nCurrency Standard\nIn this section\nCreate Fungible Tokens: Currency Standard\n\n→\nRegulated Currencies\nCreate regulated currencies on Sui using the Coin Registry system with deny list capabilities for access control.\n→\nToken Vesting Strategies\nImplement a vesting strategy for your token launch on Sui to strengthen long-term commitment, prevent market dumps, and align stakeholder incentives.\n→\nBridging Tokens\nMoving tokens from one blockchain to another is called bridging. To bridge tokens from another blockchain to Sui, you can use the Sui Bridge, Wormhole Connect, Wormhole Portal Bridge, or ZetaChain.\n→\n\nCoin standard vs currency standard\nChoosing a standardCreating a new token\nConfiguring supply\nAdding regulatory controls\nMigrating an existing token\n\nExample patterns\n\nWas this page helpful?","tokens":1069,"crawled_at":1791194605144}
+{"id":10410,"url":"https://www.getfoundry.sh/cast/reading-chain-data","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Reading chain data – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nReading chain data\n\nCast queries any Ethereum-compatible chain via JSON-RPC. Set your RPC endpoint with --rpc-url or the ETH_RPC_URL environment variable.\n\n$ export ETH_RPC_URL=https://ethereum.reth.rs/rpc\n\nBlocks\n\n$ cast block-number\n\n$ cast block latest\n\n$ cast block 18000000\n\n$ cast block latest --field timestamp\n\n$ cast base-fee\n\n$ cast bal latest\n\ncast bal prints the EIP-7928 block access list of a block as decoded JSON, listing every account and storage slot the block touched along with balance, nonce, and code changes. Pass --raw for the RLP encoding. The command fails for blocks whose list the node does not serve, typically blocks before the Amsterdam fork.\n\nTransactions\n\n$ cast tx $TX_HASH\n\n$ cast receipt $TX_HASH\n\n$ cast receipt $TX_HASH status\n\n$ cast receipt $TX_HASH gasUsed\n\nAccount state\n\n$ cast balance $ADDRESS\n\n$ cast balance $ADDRESS --ether\n\n$ cast nonce $ADDRESS\n\n$ cast code $ADDRESS\n\n$ cast storage $ADDRESS 0\n\nContract calls\n\nCall view functions without sending a transaction:\n\n$ cast call $CONTRACT \"balanceOf(address)(uint256)\" $ADDRESS\n\n$ cast call $CONTRACT \"name()(string)\"\n\n$ cast call $CONTRACT \"totalSupply()(uint256)\" --block 18000000\n\nSimulating state with call overrides\n\ncast call can temporarily replace account data for an eth_call. Overrides only affect the simulation; they do not change on-chain state.\n\nFlagEffect\n--override-balance <ADDRESS:BALANCE>\nReplaces an account's native balance.\n\n--override-nonce <ADDRESS:NONCE>\nReplaces an account's nonce.\n\n--override-code <ADDRESS:CODE>\nReplaces an account's bytecode.\n\n--override-state <ADDRESS:SLOT:VALUE>\nReplaces all storage for an account with the supplied slots.\n\n--override-state-diff <ADDRESS:SLOT:VALUE>\nReplaces the supplied storage slots while preserving the account's other storage.\n\nEach flag accepts a comma-separated list of entries. For example, you can simulate a contract call after changing one storage slot:\n\n$ cast call $CONTRACT \"balanceOf(address)(uint256)\" $ADDRESS \\\n--override-state-diff $CONTRACT:$BALANCE_SLOT:$VALUE\n\nUse --override-state-diff when you only want to change specific slots. --override-state replaces the account's entire storage, so omitted slots read as zero during the call.\n\nSimulating block context\n\nUse --block to select the chain state on which to base the call, then use --block.* options to change the block values visible to the simulated EVM:\n\nFlagEVM block value\n--block.number <NUMBER>\nBlock number.\n\n--block.time <TIME>\nTimestamp.\n\nFor example, this reads state from block 20000000 while the contract observes the overridden block number and timestamp:\n\n$ cast call $CONTRACT \"quote()(uint256)\" \\\n--block 20000000 \\\n--block.number 21000000 \\\n--block.time 1750000000\n\nThe same state and block overrides apply to regular calls, local --trace calls, remote --debug-trace-call calls, and requests printed with --curl. Remote calls require an RPC node that supports the corresponding eth_call or debug_traceCall override parameters.\n\nSee the cast call reference for the complete option list.\n\nERC-20 balances with call overrides\n\ncast erc20-token balance supports the state override flags above together with --block.number and --block.time. These options compose with --block, so you can select historical state and change the context used for the token's balanceOf call:\n\n$ cast erc20-token balance $TOKEN $OWNER \\\n--block 20000000 \\\n--override-state-diff $TOKEN:$BALANCE_SLOT:$VALUE \\\n--block.number 21000000 \\\n--block.time 1750000000\n\nHere, BALANCE_SLOT must be the exact storage key used by that token for the owner's balance. The deprecated cast balance $OWNER --erc20 $TOKEN form accepts the same call overrides, but new scripts should use cast erc20-token balance.\n\nNative ETH balance queries use eth_getBalance, not eth_call. As a result, cast balance $ADDRESS does not accept call override flags; use --block alone to query a native balance at another block.\n\nLogs and events\n\n$ cast logs \"Transfer(address indexed,address indexed,uint256)\" --from-block 18000000\n\n$ cast logs --address $CONTRACT --from-block 18000000 --to-block latest\n\n$ cast logs \"Transfer(address,address,uint256)\" --address $TOKEN\n\nChain info\n\n$ cast chain-id\n\n$ cast gas-price\n\n$ cast estimate $CONTRACT \"transfer(address,uint256)\" $TO $AMOUNT\n\nENS resolution\n\n$ cast resolve-name vitalik.eth\n\n$ cast lookup-address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045\n\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":1122,"crawled_at":1791194606152}
+{"id":10411,"url":"https://www.metaplex.com/docs/smart-contracts/core/plugins/freeze-execute","domain":"www.metaplex.com","chapter":"docs","title":"Freeze Execute Plugin | Core","text":"Overview\nThe Freeze Execute Plugin is an Owner Managed plugin that allows freezing the Execute lifecycle event on an Asset. When frozen, the asset cannot execute arbitrary instructions through its Asset Signer PDA, effectively blocking any execute operations until unfrozen.\nImportant: Since this is an Owner Managed plugin, the authority will not persist after the asset is transferred to a new owner. The new owner will need to re-add the authority if they want the previous authorities to be able to change the freeze status of the plugin.\n\nThe Freeze Execute Plugin is particularly useful for scenarios such as:\nBacked NFTs: Lock NFTs that represent ownership of underlying assets (SOL, tokens) to prevent unauthorized withdrawals\nEscrowless asset management: Freeze assets while they're involved in financial operations without transferring ownership\nStaking protocols: Prevent asset execution during staking periods while maintaining ownership\nSmart contract security: Add a layer of protection for assets that can execute complex operations\nGovernance controls: Implement freezing mechanisms for assets involved in governance or voting\nAsset rental: Prevent execution while assets are being rented out\nCollateral management: Lock assets used as collateral in DeFi protocols\nWorks With\n\nMPL Core Asset\n✅\n\nMPL Core Collection\n✅\n\nArguments\nArgValue\nfrozen\nbool\n\nFunctions\nAdd Freeze Execute Plugin to an Asset\nThe addPlugin command adds the Freeze Execute Plugin to an Asset. This plugin allows the Asset's Execute functionality to be frozen, preventing execution of arbitrary instructions.\nAdding a Freeze Execute Plugin to an MPL Core Asset\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { addPlugin, mplCore } from '@metaplex-foundation/mpl-core'\n\nimport { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n;(async () => {\n\nconst umi = createUmi('https://api.devnet.solana.com').use(mplCore())\n\nconst assetAddress = publicKey('11111111111111111111111111111111')\n\nawait addPlugin(umi, {\n\nasset: assetAddress,\n\nplugin: { type: 'FreezeExecute', data: { frozen: false } },\n\n}).sendAndConfirm(umi)\n\n})()\n\nCreating an Asset with Freeze Execute Plugin\nYou can also add the Freeze Execute Plugin during asset creation:\nCreating an Asset with Freeze Execute Plugin\n\nimport { generateSigner } from '@metaplex-foundation/umi'\n\nimport { create, mplCore } from '@metaplex-foundation/mpl-core'\n\nimport { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n;(async () => {\n\nconst umi = createUmi('https://api.devnet.solana.com').use(mplCore())\n\nconst assetSigner = generateSigner(umi)\n\nconst delegateAddress = generateSigner(umi)\n\nawait create(umi, {\n\nasset: assetSigner,\n\nname: 'My Asset',\n\nuri: 'https://example.com/my-asset.json',\n\nplugins: [\n\n{\n\ntype: 'FreezeExecute',\n\ndata: { frozen: false },\n\nauthority: { type: 'Address', address: delegateAddress.publicKey },\n\n},\n\n],\n\n}).sendAndConfirm(umi)\n\n})()\n\nCreating a Collection with Freeze Execute Plugin\nThe Freeze Execute Plugin can also be applied to collections:\nCreating a Collection with Freeze Execute Plugin\n\nimport { generateSigner } from '@metaplex-foundation/umi'\n\nimport { createCollection, mplCore } from '@metaplex-foundation/mpl-core'\n\nimport { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n;(async () => {\n\nconst umi = createUmi('https://api.devnet.solana.com').use(mplCore())\n\nconst collectionSigner = generateSigner(umi)\n\nawait createCollection(umi, {\n\ncollection: collectionSigner,\n\nname: 'My Collection',\n\nuri: 'https://example.com/my-collection.json',\n\nplugins: [{ type: 'FreezeExecute', frozen: false }],\n\n}).sendAndConfirm(umi)\n\n})()\n\nFreezing Execute Operations\nThe updatePlugin command can be used to freeze the Asset's Execute functionality, preventing it from executing arbitrary instructions until unfrozen.\nFreeze Execute Operations on an MPL Core Asset\n\nimport { createUmi, publicKey } from '@metaplex-foundation/umi'\n\nimport { updatePlugin, mplCore } from '@metaplex-foundation/mpl-core'\n\n;(async () => {\n\nconst umi = createUmi('https://api.devnet.solana.com').use(mplCore())\n\nconst assetAddress = publicKey('11111111111111111111111111111111')\n\nawait updatePlugin(umi, {\n\nasset: assetAddress,\n\nplugin: { type: 'FreezeExecute', data: { frozen: true } },\n\n}).sendAndConfirm(umi)\n\n})()\n\nUnfreezing Execute Operations\nThe updatePlugin command can also be used to unfreeze the Asset's Execute functionality, restoring its ability to execute arbitrary instructions.\nUnfreeze Execute Operations on an MPL Core Asset\n\nimport { createUmi, publicKey } from '@metaplex-foundation/umi'\n\nimport { updatePlugin, mplCore } from '@metaplex-foundation/mpl-core'\n\n;(async () => {\n\nconst umi = createUmi('https://api.devnet.solana.com').use(mplCore())\n\nconst assetAddress = publicKey('11111111111111111111111111111111')\n\nawait updatePlugin(umi, {\n\nasset: assetAddress,\n\nplugin: { type: 'FreezeExecute', data: { frozen: false } },\n\n}).sendAndConfirm(umi)\n\n})()\n\nPlugin Authority\nThe Freeze Execute Plugin supports different authority types for controlling who can freeze/unfreeze execute operations:\nOwner Authority (default): Only the asset owner can freeze/unfreeze\nDelegate Authority: A specific address can be delegated to control freezing\nUpdate Authority: The asset's update authority can control freezing, but only if explicitly delegated\nSetting Plugin Authority\n\nimport { generateSigner } from \"@metaplex-foundation/umi\";\n\nimport { create, mplCore } from \"@metaplex-foundation/mpl-core\";\n\nimport { createUmi } from \"@metaplex-foundation/umi-bundle-defaults\";\n\n(async () => {\n\nconst umi = createUmi(\"https://api.devnet.solana.com\").use(mplCore());\n\nconst assetSigner = generateSigner(umi);\n\nconst delegateAddress = generateSigner(umi);\n\nawait create(umi, {\n\nasset: assetSigner,\n\nname: \"My Asset\",\n\nuri: \"https://example.com/my-asset.json\",\n\nplugins: [\n\n{\n\ntype: \"FreezeExecute\",\n\ndata: { frozen: false },\n\nauthority: { type: \"Address\", address: delegateAddress.publicKey },\n\n},\n\n],\n\n}).sendAndConfirm(umi);\n\n})();\n\nImportant Notes\nWhen the frozen field is set to true, any execute operations will be blocked\nDefault authority: The asset owner controls the plugin by default\nAuthority delegation: Only the current authority can freeze/unfreeze the execute functionality\nAuthority constraints: If authority is delegated to someone else, the original owner cannot unfreeze until authority is revoked\nThe plugin cannot be removed when frozen\nAuthority cannot be reassigned when frozen\nThe plugin works with the Execute instruction system\nUnfreeze and withdraw via execute before burning the Asset. Burning disables execute and strands remaining balances in the Asset Signer PDA\nExample Use Case: Backed NFT\nA common use case for the Freeze Execute Plugin is creating \"backed NFTs\" where the NFT represents ownership of underlying assets (like SOL or tokens) that can be withdrawn via execute instructions. The plugin allows you to temporarily freeze these execute operations. Withdraw those underlying assets with execute before burning the Asset — burning disables execute and strands remaining balances in the Asset Signer PDA.\nBacked NFT Example\n\nimport {\n\ngenerateSigner,\n\npublicKey,\n\nsol,\n\ncreateNoopSigner,\n\nkeypairIdentity,\n\n} from \"@metaplex-foundation/umi\";\n\nimport {\n\ncreate,\n\nexecute,\n\nfindAssetSignerPda,\n\nupdatePlugin,\n\nfetchAsset,\n\nmplCore,\n\n} from \"@metaplex-foundation/mpl-core\";\n\nimport { transferSol } from \"@metaplex-foundation/mpl-toolbox\";\n\nimport { createUmi } from \"@metaplex-foundation/umi-bundle-defaults\";\n\n(async () => {\n\nconst umi = createUmi(\"https://api.devnet.solana.com\").use(mplCore());\n\n//use your wallet instead\n\nconst wallet = generateSigner(umi);\n\numi.use(keypairIdentity(wallet));\n\n// 1. Create asset with frozen execute functionality\n\nconst assetSigner = generateSigner(umi);\n\nawait create(umi, {\n\nasset: assetSigner,\n\nname: \"Backed NFT\",\n\nuri: \"https://example.com/backed-nft.json\",\n\nplugins: [{ type: \"FreezeExecute\", frozen: true }],\n\n}).sendAndConfirm(umi);\n\n// 2. Find the Asset Signer PDA\n\nconst [assetSignerPda] = findAssetSignerPda(umi, {\n\nasset: assetSigner.publicKey,\n\n});\n\n// 3. Deposit SOL to \"back\" the NFT\n\nawait transferSol(umi, {\n\nsource: umi.identity,\n\ndestination: publicKey(assetSignerPda),\n\namount: sol(0.01), // 0.01 SOL backing\n\n}).sendAndConfirm(umi);\n\n// 4. Execute operations are blocked while frozen\n\n// This transaction will fail:\n\ntry {\n\nawait execute(umi, {\n\nasset: await fetchAsset(umi, assetSigner.publicKey),\n\ninstructions: transferSol(umi, {\n\nsource: createNoopSigner(publicKey(assetSignerPda)),\n\ndestination: generateSigner(umi).publicKey,\n\namount: sol(0.001),\n\n}),\n\n}).sendAndConfirm(umi, { send: { skipPreflight: true } });\n\n} catch (e) {\n\nconsole.log(\"execute failed as expected\", e);\n\n}\n\n// 5. Unfreeze to allow withdrawals\n\nawait updatePlugin(umi, {\n\nasset: assetSigner.publicKey,\n\nplugin: { type: \"FreezeExecute\", data: { frozen: false } },\n\n}).sendAndConfirm(umi);\n\n// 6. Now execute operations are allowed\n\nconst recipient = generateSigner(umi);\n\nawait execute(umi, {\n\nasset: await fetchAsset(umi, assetSigner.publicKey),\n\ninstructions: transferSol(umi, {\n\nsource: createNoopSigner(publicKey(assetSignerPda)),\n\ndestination: recipient.publicKey,\n\namount: sol(0.001),\n\n}),\n\n}).sendAndConfirm(umi);\n\n})();","tokens":2323,"crawled_at":1791194624157}
+{"id":10412,"url":"https://docs.compound.xyz/compound-js/ctokens","domain":"docs.compound.xyz","chapter":"defi_protocols","title":"Compound.js Docs | cTokens (v2)","text":"Compound.js\nComet\nGovernance\ncTokens (v2)\nComptroller (v2)\nPrice Feed (v2)\nHelpers\n\ncToken Methods\nCompound v2 Supply\nRedeem\nBorrow\nRepay Borrow\n\nCompound.js\ncToken Methods\nThese methods facilitate interactions with the cToken smart contracts.\nCompound v2 Supply\nSupplies the user’s Ethereum asset to the Compound Protocol.\nasset (string) A string of the asset to supply.\namount (number | string | BigNumber) A string, number, or BigNumber object of the amount of an asset to supply. Use the mantissa boolean in the options parameter to indicate if this value is scaled up (so there are no decimals) or in its natural scale.\nnoApprove (boolean) Explicitly prevent this method from attempting an ERC-20 approve transaction prior to sending the mint transaction.\n[options] (CallOptions) Call options and Ethers.js overrides for the transaction. A passed gasLimit will be used in both the approve (if not supressed) and mint transactions.\nRETURN (object) Returns an Ethers.js transaction object of the supply transaction.\nconst compound = new Compound(window.ethereum);\n\n// Ethers.js overrides are an optional 3rd parameter for `supply`\n// const trxOptions = { gasLimit: 250000, mantissa: false };\n\n(async function() {\n\nconsole.log('Supplying ETH to the Compound Protocol...');\nconst trx = await compound.supply(Compound.ETH, 1);\nconsole.log('Ethers.js transaction object', trx);\n\n})().catch(console.error);\n\nRedeem\nRedeems the user’s Ethereum asset from the Compound Protocol.\nasset (string) A string of the asset to redeem, or its cToken name.\namount (number | string | BigNumber) A string, number, or BigNumber object of the amount of an asset to redeem. Use the mantissa boolean in the options parameter to indicate if this value is scaled up (so there are no decimals) or in its natural scale. This can be an amount of cTokens or underlying asset (use the asset parameter to specify).\n[options] (CallOptions) Call options and Ethers.js overrides for the transaction.\nRETURN (object) Returns an Ethers.js transaction object of the redeem transaction.\nconst compound = new Compound(window.ethereum);\n\n(async function() {\n\nconsole.log('Redeeming ETH...');\nconst trx = await compound.redeem(Compound.ETH, 1); // also accepts cToken args\nconsole.log('Ethers.js transaction object', trx);\n\n})().catch(console.error);\n\nBorrow\nBorrows an Ethereum asset from the Compound Protocol for the user. The user’s address must first have supplied collateral and entered a corresponding market.\nasset (string) A string of the asset to borrow (must be a supported underlying asset).\namount (number | string | BigNumber) A string, number, or BigNumber object of the amount of an asset to borrow. Use the mantissa boolean in the options parameter to indicate if this value is scaled up (so there are no decimals) or in its natural scale.\n[options] (CallOptions) Call options and Ethers.js overrides for the transaction.\nRETURN (object) Returns an Ethers.js transaction object of the borrow transaction.\nconst compound = new Compound(window.ethereum);\n\n(async function() {\n\nconst daiScaledUp = '32000000000000000000';\nconst trxOptions = { mantissa: true };\n\nconsole.log('Borrowing 32 Dai...');\nconst trx = await compound.borrow(Compound.DAI, daiScaledUp, trxOptions);\n\nconsole.log('Ethers.js transaction object', trx);\n\n})().catch(console.error);\n\nRepay Borrow\nRepays a borrowed Ethereum asset for the user or on behalf of another Ethereum address.\nasset (string) A string of the asset that was borrowed (must be a supported underlying asset).\namount (number | string | BigNumber) A string, number, or BigNumber object of the amount of an asset to borrow. Use the mantissa boolean in the options parameter to indicate if this value is scaled up (so there are no decimals) or in its natural scale.\n[borrower] (string | null) The Ethereum address of the borrower to repay an open borrow for. Set this to null if the user is repaying their own borrow.\nnoApprove (boolean) Explicitly prevent this method from attempting an ERC-20 approve transaction prior to sending the subsequent repayment transaction.\n[options] (CallOptions) Call options and Ethers.js overrides for the transaction. A passed gasLimit will be used in both the approve (if not supressed) and repayBorrow or repayBorrowBehalf transactions.\nRETURN (object) Returns an Ethers.js transaction object of the repayBorrow or repayBorrowBehalf transaction.\nconst compound = new Compound(window.ethereum);\n\n(async function() {\n\nconsole.log('Repaying Dai borrow...');\nconst address = null; // set this to any address to repayBorrowBehalf\nconst trx = await compound.repayBorrow(Compound.DAI, 32, address);\n\nconsole.log('Ethers.js transaction object', trx);\n\n})().catch(console.error);","tokens":1180,"crawled_at":1791194609009}
+{"id":10413,"url":"https://www.getfoundry.sh/forge/linting","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Linting – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nLinting\n\nForge includes a built-in linter to catch common issues and enforce best practices.\n\nRun the linter\n\n$ forge lint\n\nThe linter checks for:\n\nIncorrect shift operations\n\nUnchecked external calls\n\nDivide-before-multiply bugs\n\nIncorrect ERC721 interface signatures\n\nIncorrect ERC20 interface definitions\n\nStrict equality on externally-influenced values\n\nUnsafe typecasts\n\nNaming convention violations\n\nUse of tx.origin for authorization\n\nReturn bomb risks from gas-limited calls\n\nUnused imports\n\nGas optimizations\n\nConfiguration\n\nConfigure linter rules in foundry.toml:\n\nfoundry.toml\n[lint]\nseverity = [\"high\", \"med\", \"low\"]\nexclude_lints = [\"mixed-case-function\", \"custom-errors\"]\n\nSeverity levels\n\nControl which lints run by severity:\n\nfoundry.toml\n[lint]\nseverity = [\"high\", \"med\"] # Only high and medium severity\n\nValid severity levels: high, med, low, info, gas, code-size\n\nGas and code-size lints skip test and script files.\n\nExclude specific lints\n\nDisable specific lint rules globally:\n\nfoundry.toml\n[lint]\nexclude_lints = [\"mixed-case-variable\", \"asm-keccak256\"]\n\nIgnoring files\n\nExclude files from linting:\n\nfoundry.toml\n[lint]\nignore = [\"src/legacy/**\", \"test/**\"]\n\nInline suppression\n\nDisable lints for specific lines or blocks using comment directives.\n\nDisable on current line\n\nuint256 Mixed_Case = 1; // forge-lint: disable-line(mixed-case-variable)\n\nDisable on next line\n\n// forge-lint: disable-next-line(custom-errors)\nrevert(\"Use custom errors instead\");\n\nDisable for next item\n\nDisable lints for an entire function, struct, or contract:\n\n// forge-lint: disable-next-item(mixed-case-function)\nfunction non_standard_name() public {\n// entire function is excluded from the lint\n}\n\nDisable a block\n\n// forge-lint: disable-start(asm-keccak256)\nbytes32 hash1 = keccak256(abi.encodePacked(a, b));\nbytes32 hash2 = keccak256(abi.encodePacked(c, d));\n// forge-lint: disable-end(asm-keccak256)\n\nDisable multiple lints\n\n// forge-lint: disable-next-line(custom-errors, mixed-case-variable)\n\nDisable all lints\n\n// forge-lint: disable-next-line\n\nOr explicitly:\n\n// forge-lint: disable-next-line(all)\n\nDisable linting on build\n\nBy default, forge build runs the linter. To disable for a single invocation, pass\n--no-lint (alias --skip-lint):\n\nforge build --no-lint\n\nTo disable persistently:\n\nfoundry.toml\n[lint]\nlint_on_build = false\n\nCI integration\n\nAdd linting to your CI pipeline with --deny warnings, which exits with a non-zero\nstatus when warning-level lint diagnostics are emitted:\n\n- name: Run linter\nrun: forge lint --deny warnings\n\nSee the linter reference for all configuration options.\n\nLint reference\n\nEvery lint emitted by forge lint has its own page describing what it flags, why it\nmatters, and how to fix it. Use the index below to jump to a specific lint, or use the\nnavigation on the right to browse by severity.\n\nHigh severity\n\narbitrary-send-erc20 — Flags ERC20 transferFrom and safeTransferFrom calls whose from argument is not constrained to msg.sender or address(this), including SafeERC20 library calls.\n\narbitrary-send-erc20-permit — Flags transferFrom and safeTransferFrom calls preceded by a permit for the same token and owner in the same function, when from is not constrained to msg.sender or address(this). This includes common SafeERC20 and SafeTransferLib wrappers.\n\narbitrary-send-eth — Flags ETH transfers to caller-controlled destinations in functions without a recognized caller restriction. This includes transfer, send, calls with {value: ...}, selfdestruct, and common OpenZeppelin and Solady ETH-transfer helpers.\n\ncontrolled-delegatecall — Flags delegatecall targets other than a trusted literal, constant, zero address, or address(this).\n\nencode-packed-collision — Encode Packed Collision\n\nenumerable-loop-removal — Flags EnumerableSet.remove inside a loop that also reads the same set with at using an increasing index.\n\nerc20-unchecked-transfer — Warns when a function with the same signature as transfer(address,uint256) or transferFrom(address,address,uint256) and a bool return type is invoked but the result is not checked.\n\nfunction-selector-collision — Reports different proxy and implementation function signatures with the same four-byte selector. Identical signatures are not reported.\n\nincorrect-exp — Reports a ^ b when both operands are decimal integer literals and a is 2 or 10. In Solidity, ^ is bitwise XOR, so 10 ^ 18 evaluates to 24, not 10 ** 18. Hexadecimal and scientific-notation operands are excluded.\n\nincorrect-shift — Warns when the first argument to a Yul shl or shr call is dynamic and the second argument is a literal. Yul shift calls take the shift amount first and the value second, so shr(value, 8) shifts the literal 8 by value; the usual intended expression is shr(8, value).\n\nprotected-vars — Protected variables\n\nreentrancy-balance — Reports public or external functions that save address(this).balance, make an external call that permits reentry, and then check the current balance against the saved value.\n\nreentrancy-eth — Reports low-level .call{value: ...}(...) operations without a concrete gas cap, including gas: gasleft(), when a state variable read before the call is written after it.\n\nrtlo — Detects the right-to-left override codepoint (U+202E) and other bidirectional control characters embedded in identifiers, strings, and comments.\n\nunchecked-call — Warns when the boolean returned by a low-level call is discarded — either because the return value is not assigned or because only the bytes memory payload is used.\n\nunprotected-initializer — Unprotected initializer\n\nMedium severity\n\nassert-state-change — Warns when an assert() argument contains a state-mutating operation: a pre- or post-increment/decrement (++/--) on a state variable, an assignment (=, +=,etc.) to a state variable, a delete of a state variable, or a call to a function that writes state variables.\n\nblock-number-across-roll — Warns in tests and scripts when a value derived from block.number can be used after vm.roll, or when block.number is read both before and after a roll in the same call.\n\nblock-timestamp-across-warp — Warns in tests and scripts when a value derived from block.timestamp can be used after vm.warp, or when block.timestamp is read both before and after a warp in the same call.\n\nboolean-cst — Reports literal boolean conditions in if, for, and do while, while (false), and boolean operators (&&, ||) where one side is a literal true/false. The idiomatic infinite loop while (true) is exempt.\n\ndangerous-unary-operator — Reports x =- y and x =~ y, where = is written directly beside a unary operator. These are assignments, not compound operations: x =- 1 means x = -1, not x -= 1. The intentional spaced forms (x = -1, x = ~y) and compound operators (x -= 1) are not flagged.\n\ndivide-before-multiply — Warns on expressions of the form (a / b) * c (or equivalent shapes), where the integer division truncates before the result is multiplied.\n\necrecover — Reports direct ecrecover calls without a check that s is at most 0x7FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF5D576E7357A4501DDFE92F46681B20A0 before the recovered address is used.\n\nincorrect-erc20-interface — For each function whose name and parameter types match a canonical ERC20 method (totalSupply, balanceOf, transfer, transferFrom, approve, allowance), the lint checks that the return type matches the spec. A mismatch is reported.\n\nincorrect-erc721-interface — For each function whose name and parameter types match a canonical ERC721/ERC165 method (balanceOf, ownerOf, safeTransferFrom, transferFrom, approve, setApprovalForAll, getApproved, isApprovedForAll, supportsInterface), the lint checks that the return type matches the spec. A mismatch is reported.\n\nincorrect-strict-equality — Incorrect Strict Equality\n\nlocked-ether — Locked Ether\n\nmapping-deletion — Reports delete x when x is a struct or array whose type holds a mapping, directly or through a nested struct or array. Deleting a whole mapping is not valid Solidity, but deleting a container of one compiles and silently leaves the mapping's entries in place.\n\nnon-reentrant-not-first — Reports a function, fallback, or receive function when nonReentrant appears after another modifier, for example onlyOwner nonReentrant.\n\nreentrancy-no-eth — Reports public or external functions that read a state variable, make an external call without sending ETH, and then write the same state variable.\n\ntautological-compare — Reports a <op> a where a is a side-effect-free expression (an identifier, member access, or indexing) and <op> is <, <=, >, >=, ==, or !=. Such a comparison has a constant result. Comparisons whose sides could legitimately differ (for example involving a function call) are left untouched, as are comparisons on user-defined value types, whose operators are user-defined (using {f as ==} for T) and need not be constant.\n\ntx-origin — Reports tx.origin reads when they are used as part of a guard condition. Plain reads outside of guard predicates are not reported.\n\ntype-based-tautology — Flags comparisons that are always true or false because of an integer type's range, such as uint256 x >= 0. Also reports conditions that cover the entire range, such as x > 0 || x == 0 for unsigned x.\n\nuninitialized-local — Reports local variables that can be read before being assigned. Parameters and state variables are excluded.\n\nuninitialized-state — Reports state variables that are read but never assigned in the contract or its base contracts. An assignment at the declaration or in a constructor satisfies the lint.\n\nunsafe-oz-erc721-mint — Reports calls to OpenZeppelin's ERC721 _mint, including overrides that delegate to it, without a recognized recipient check.\n\nunsafe-typecast — Reports casts where the source value's type can exceed the target type (for example, uint256 → uint128 or int256 → uint128). An unsigned value masked to the target width, such as uint8(value & 0xff), is not flagged. A preceding manual range check may still produce a warning; review that check before suppressing the lint.\n\nunused-return — Detects high-level external calls (member calls on contract-typed variables or interface-cast addresses) that return one or more values when the entire result is discarded or any slot of a tuple return is omitted. ERC20 transfer and transferFrom are excluded as they are handled by the separate erc20-unchecked-transfer lint.\n\nweak-prng — Reports direct use of block.timestamp, block.number, block.coinbase, blockhash(...), block.prevrandao, or block.difficulty in modulo expressions or keccak256(...). abi.encode* calls are treated as entropy only when they feed one of those expressions.\n\nLow severity\n\nblock-timestamp — Reports comparison expressions (<, <=, >, >=, ==, !=) involving block.timestamp.\n\ncalls-loop — Reports high-level contract calls, low-level call/delegatecall/staticcall, Ether send/transfer, external self-calls through this, and contract creation inside a loop. Internal and private library calls and super dispatch are not treated as external calls.\n\ndelegatecall-loop — Reports delegatecall expressions that appear in the body of a for, while, or do while loop when the enclosing function is public payable or external payable.\n\ndeprecated-oz-function — Reports uses of OpenZeppelin's SafeERC20.safeApprove and AccessControl._setupRole, including their upgradeable variants.\n\nempty-block — Reports a function whose body is {} (a comment does not make a body non-empty).\n\ninconsistent-type-names — Reports shorthand uint or int declarations when the same contract also uses uint256 or int256, respectively. This includes types within arrays and mappings.\n\nincorrect-modifier — Flags modifiers that can finish successfully without reaching the _ placeholder. A path that reverts before _ is allowed, but calling a function that might revert does not by itself prevent the modifier from skipping the body.\n\nmissing-events-access-control — Flags protected public or external functions that change ownership, roles, or other state used in authorization checks without a related event containing the changed value or key.\n\nmissing-events-arithmetic — Flags protected public or external functions that update integer parameters used in arithmetic by an unprotected entry point without emitting an event. Updates include assignments from function input and arithmetic changes.\n\nmissing-zero-check — Reports address parameters used in a state write or value transfer by an externally callable state-mutating function or constructor without a check against address(0).\n\nmsg-value-loop — Reports msg.value expressions that execute inside a for, while, or do while loop reachable from a public payable or external payable entry point.\n\nreentrancy-events — Reports events emitted after an external interaction, such as a state-changing contract call, low-level call or delegatecall, ETH send or transfer, or contract creation. Static calls and view or pure calls are excluded.\n\nrequire-revert-in-loop — Reports require calls and Solidity or Yul revert operations inside loops.\n\nreturn-bomb — Detects low-level call, delegatecall, and staticcall expressions that specify {gas: ...}. Solidity copies the full returndata for these calls even when the second tuple element is ignored. It also detects high-level external calls with {gas: ...} that consume dynamically encoded return values such as bytes, string, dynamic arrays, or structs containing dynamic fields.\n\nsolmate-safe-transfer-lib — Reports uses of safeTransfer, safeTransferFrom, and safeApprove from solmate's SafeTransferLib. ETH transfers and similarly named libraries from other packages are excluded.\n\nInformational\n\nboolean-equal — Reports any equality comparison between a boolean expression and a literal true or false.\n\ncyclomatic-complexity — Reports functions with a complexity score above 11. The score starts at one and increases for each decision point: if, a loop with a condition, a ternary, a catch clause, or an additional assembly switch case. Boolean && and || operators do not add to the score.\n\nevent-fields — Reports unindexed address and address payable event parameters when the event has no indexed parameters. Contract, interface, and user-defined value types are excluded.\n\nfunction-init-state — Reports inline state-variable initializers that reference a non-constant state variable or a non-pure function. Constants, pure functions, and assignments in the constructor body are excluded.\n\nincorrect-using-for — Reports using L for T when library L has no non-private function whose first parameter accepts T, including through an implicit conversion.\n\ninline-assembly — Reports every inline assembly statement, including blocks marked memory-safe.\n\ninterface-file-naming — Reports interface-only files whose path basename does not start with I (e.g. IERC20.sol).\n\ninterface-naming — Reports interface Foo where Foo does not start with I (e.g. IFoo).\n\ninternal-function-used-once — Reports internal and free functions referenced exactly once across the compiled sources.\n\nliteral-instead-of-constant — Reports repeated number, address, or hex-string values within a contract's executable code. Equivalent spellings, such as 100 and 0x64, count as the same value.\n\nlow-level-calls — Warns whenever a contract uses a low-level call expression, even if the success return value is captured and checked.\n\nmissing-inheritance — Reports contracts that implement an interface's external functions without inheriting it. An already-inherited base that provides the interface's functions satisfies the lint. Abstract contracts containing only interface declarations are also considered.\n\nmixed-case-function — Reports functions whose names contain embedded underscores, start with an uppercase letter, or otherwise deviate from mixedCase. Leading and trailing underscores are preserved, and single-character names are not checked. Test functions starting with test, invariant_, or statefulFuzz, configured uppercase patterns (for example, ERC20), and external constant-style getters are exempted.\n\nmixed-case-variable — Reports mutable variable identifiers that contain embedded underscores, start with an uppercase letter, or otherwise deviate from mixedCase. Leading and trailing underscores are preserved, and single-character names are not checked.\n\nmodifier-used-only-once — Reports modifiers used by exactly one function or constructor across the compiled sources. Virtual modifiers, overrides, and unused modifiers are excluded.\n\nmulti-contract-file — Reports each top-level contract, interface, or library definition (after the first) in a file that contains more than one such declaration.\n\nnamed-struct-fields — Reports Struct(a, b, c) style struct construction; suggests Struct({ field1: a, field2: b, field3: c }) instead.\n\npascal-case-struct — Reports struct identifiers longer than one character that do not match the PascalCase convention. Single-character names are not checked.\n\npragma-inconsistent — Reports inconsistent pragma solidity ...; requirements across source files, such as different exact versions or mixed caret, tilde, and range constraints.\n\nredundant-base-constructor-call — For every base contract listed in a contract's inheritance specifier or invoked from a derived constructor's header, the lint reports the empty () when the base does not require any arguments.\n\nscreaming-snake-case-const — Reports state variables declared constant whose identifier is longer than one character and deviates from SCREAMING_SNAKE_CASE. Leading and trailing underscores are preserved.\n\nscreaming-snake-case-immutable — Reports state variables declared immutable whose identifier deviates from SCREAMING_SNAKE_CASE. Single-character names are not checked, and leading and trailing underscores are preserved.\n\ntodo-comment — Reports TODO and FIXME markers in line, block, and NatSpec comments, regardless of case. This includes common forms such as TODO:, FIXME(...), and a bare marker at the start of a comment line. Ordinary filenames such as todo.md are not markers.\n\ntoo-many-digits — Reports Solidity and Yul numeric literals that contain a run of 5 or more 0 characters. Decimal literals with scientific notation, literals with a sub-denomination, and 40-digit hexadecimal address literals are skipped. Other hexadecimal literals remain in scope because long padded masks and bit patterns are also difficult to review.\n\nunaliased-plain-import — Reports plain imports of the form import \"path\";. Suggests using either named imports (import { A, B } from \"path\") or an aliased import (import \"path\" as X).\n\nunsafe-cheatcode — Reports calls to ffi, readFile, readLine, writeFile, writeLine, removeFile, closeFile, setEnv, or deriveKey. Unrelated methods with these names may also be flagged.\n\nunused-error — Reports custom error declarations that are never used by a revert, require, or selector reference anywhere in the compiled sources.\n\nunused-import — Reports import \"...\", import \"...\" as X, and import { A, B } from \"...\" statements where one or more imported names are never used. This includes unused namespace imports (import * as X).\n\nGas optimization\n\nasm-keccak256 — Reports direct keccak256(...) calls in statements and initializers for gas review.\n\ncache-array-length — Reports comparison expressions in for loop conditions when either side reads .length from a state dynamic array, such as i < values.length or values.length > i, including comparisons nested inside && / || conditions.\n\ncostly-loop — Reports assignments, compound assignments, increments/decrements, and delete expressions that directly write to a storage variable inside any for, while, or do-while loop body, including writes through storage array indices and mapping keys.\n\ncould-be-constant — Reports non-constant, non-immutable state variables with a compile-time-constant initializer and no later assignments, when their type permits constant.\n\ncould-be-immutable — Reports each non-constant, non-immutable state variable whose only writes occur in the constructor (or in initialization at declaration time).\n\ncustom-errors — Reports require calls with no reason or whose second argument is a string literal, and revert(...) calls that are either bare or have a string-literal argument.\n\nexternal-function — Flags implemented public functions with reference-type memory parameters that are never called internally and do not modify their parameters. Overrides are excluded.\n\nunused-state-variables — Reports each state variable that has no read or write site across the project.\n\nvar-read-using-this — Reports calls through this to the contract's own public variable getters and view or pure functions, including inherited functions.\n\nwrite-after-write — Reports assignments to state variables whose values are overwritten before being read. Compound assignments and writes to individual mapping entries, array elements, or struct fields are excluded.\n\nCode size\n\nunwrapped-modifier-logic — Reports modifiers containing logic beyond a placeholder, simple require or assert checks, or a single library call. Assembly blocks are excluded from suggested extraction.\n\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":5304,"crawled_at":1791194623737}
+{"id":10414,"url":"https://a16zcrypto.com/posts/podcast/crypto-policy-regulation-whats-going-on","domain":"a16zcrypto.com","chapter":"research","title":"Crypto Policy & Regulation: What's Going On? - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nCrypto Policy & Regulation: What's Going On?\nBrian Quintenz, Collin McCune, Miles Jennings, and Sonal Chokshi\n02.12.23\n\nTags & Share Tags\ncompany building\nDeFi\npodcast\npolicy & regulation\nRegulate Apps Not Protocols\nregulatory know-how\nstablecoins\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nEPISODE SUMMARY\n\nwith @milesjennings @brianquintenz @colinmccune @smc90 We provide an overview of policy and regulation in the crypto industry right now — from a lay of the land to pulse checks on sentiment; share frameworks for policymakers, and quick guidance on how things work (and how to navigate and participate) for builders; and dig into the mindsets, myths, debates, nuances around the topic. We also quickly discuss what to expect for regulation in a few specific domains — from DeFi to DAOs, to briefly touching on: CEX vs DEX, stablecoins, banks custodying crypto, unhosted wallets, more.\n\nEPISODE NOTES\n\nwith @milesjennings @brianquintenz @colinmccune @smc90\n\nWe provide an overview of policy and regulation in the crypto industry right now — from a lay of the land to pulse checks on sentiment — as well as share helpful frameworks for policymakers, and quick guidance on how things work (and how to navigate and participate) for builders.\n\nWe also dig into the mindsets, myths, debates, nuances; and quickly discuss what to expect for regulation in a few specific domains — from DeFi to DAOs, to briefly touching on CEX vs DEX, stablecoins, banks custodying crypto, unhosted wallets, etc.\n\nOur expert guests include:\n\nMiles Jennings, general counsel at a16z crypto; he was also previously at Latham & Watkins, where he co-chaired its global blockchain and cryptocurrency task force — Jennings has written a lot for us here, including developing frameworks for regulating crypto while preserving both innovation and protecting consumers; developing and evolving legal frameworks for DAOs; releasing “can’t be evil” licensing for NFTs; and sharing detailed guides to decentralization for builders.\n\nBrian Quintenz, now head of policy at a16z crypto; previously, he was a commissioner of the Commodity Futures Trading Commission (CFTC), where he had led the agency’s Technology Advisory Committee — during his service, the CFTC oversaw the listing of the first U.S. regulated Bitcoin and Ether futures contracts on derivatives exchanges, and the rapid expansion of DeFi.\n\nCollin McCune, who joined as head of government affairs at a16z crypto a few months ago; he has spent a decade on Capitol Hill, and most recently was Deputy Staff Director of the House Financial Services Committee. I asked McCune to jump in on this episode for where we cover navigating Congress and the legislative process.\n\n…all in conversation with editor in chief Sonal Chokshi.\n\nTo stay up to date on our ongoing efforts, regular regulatory recaps, and other resources or educational materials that you can use or point others to, please also subscribe to our newsletter for the latest dispatches.\n\nAs a reminder: none of the discussion is investment, business, legal, or tax advice; please see a16z.com/disclosures for more important information — including a link to a list of our investments.","tokens":827,"crawled_at":1791194626407}
+{"id":10415,"url":"https://docs.compound.xyz/compound-js/comet","domain":"docs.compound.xyz","chapter":"defi_protocols","title":"Compound.js Docs | Comet","text":"Compound.js\nComet\nGovernance\ncTokens (v2)\nComptroller (v2)\nPrice Feed (v2)\nHelpers\n\nComet Methods\nCompound III Supply\nAllow\nAllow By Signature\nCreate Allow Signature\nTransfer\nWithdraw\nWithdraw To\nWithdraw From\nGet Supply Rate\nGet Borrow Rate\nGet Utilization\nAbsorb\nGet Reserves\nTarget Reserves\nIs Borrow Collateralized\nIs Liquidatable\nQuote Collateral\nBuy Collateral\nCompound III Get Price\nBorrow Balance Of\nCollateral Balance Of\nGet Asset Info\nGet Asset Info By Address\nGet Asset Info By Symbol\nGet Supported Network Names\nGet Supported Collaterals\nGet Base Asset Name\n\nCompound.js\nComet Methods\nThese methods facilitate interactions with Compound III.\nCompound III Supply\nSupplies the user’s Ethereum asset to Compound Comet.\nfrom (string) A string of the address that the supplied asset is supplied from. This allows approved account managers to supply on behalf of an account that has already approved their ERC-20 asset to be transferred to the Comet contract. To supply on behalf of the sender, this should be set to the sender’s address.\ndst (string) A string of the address that the supplied asset is credited to within Comet. To supply to the sender’s account, this should be set to the sender’s address.\nasset (string) A string of the name of the asset to supply.\namount (number | string | BigNumber) A string, number, or BigNumber object of the amount of an asset to supply. Use the mantissa boolean in the options parameter to indicate if this value is scaled up (so there are no decimals) or in its natural scale.\nnoApprove (boolean) Explicitly prevent this method from attempting an ERC-20 approve transaction prior to sending the supply transaction.\n[options] (CallOptions) Call options and Ethers.js overrides for the transaction. A passed gasLimit will be used in both the approve (if not supressed) and supply transactions.\nRETURN (object) Returns an Ethers.js transaction object of the supply transaction.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n// Ethers.js overrides are an optional last parameter\n// const trxOptions = { gasLimit: 250000, mantissa: false };\n\n(async function() {\n\nconst me = '0xSenderAddress'; // can be compound._provider.address\n\nconsole.log('Supplying ETH to Compound Comet...');\nconst trx = await comet.supply(\nme, // supplied asset comes from this account\nme, // supplied asset is credited to this account's balance\nCompound.WBTC,\n3\n);\nconsole.log('Ethers.js transaction object', trx);\n\n})().catch(console.error);\n\nAllow\nAllows or disallows an address to withdraw or transfer on behalf of the Sender’s address.\nmanager (string) The address of the manager.\nisAllowed (boolean) True to add the manager and false to remove the manager.\n[options] (CallOptions) Call options and Ethers.js overrides for the transaction.\nRETURN (object) Returns an Ethers.js transaction object of the allow transaction.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n(async function () {\nconst address = '0xManagerAddressHere';\nconst trx = await comet.allow(address, true);\nconsole.log('Ethers.js transaction object', trx);\n})().catch(console.error);\n\nAllow By Signature\nEnable or disable a Comet account manager using an EIP-712 signature.\nowner (string) The address of the account that is changing a manager.\nmanager (string) The address of the manager of the account.\nisAllowed (boolean) Pass true to enable a manager, false to disable.\nnonce (number) The contract state required to match the signature. This can be retrieved from the contract’s public nonces mapping.\nexpiry (number) The time at which to expire the signature. A block timestamp as seconds since the unix epoch.\nsignature (object) An object that contains the v, r, and, s values of an EIP-712 signature.\n[options] (CallOptions) Options to set for eth_call, optional ABI (as JSON object), and Ethers.js method overrides. The ABI can be a string of the single intended method, an array of many methods, or a JSON object of the ABI generated by a Solidity compiler.\nRETURN (object) Returns an Ethers.js transaction object of the allow transaction.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n(async function() {\nconst allowTx = await comet.allowBySig(\n'0xaAaAaAaaAaAaAaaAaAAAAAAAAaaaAaAaAaaAaaAa',\n'0xbBbBBBBbbBBBbbbBbbBbbbbBBbBbbbbBbBbbBBbB',\ntrue,\n42,\n9999999999,\n{\nv: '0x1b',\nr: '0x130dbca2fafa07424c033b4479687cc1deeb65f08809e3ab397988cc4c6f2e78',\ns: '0x1debeb8250262f23906b1177161f0c7c9aa3641e8bff5b6f5c88a6bb78d5d8cd'\n}\n);\nconsole.log('Ethers.js transaction object', allowTx);\n})().catch(console.error);\n\nCreate Allow Signature\nCreate an EIP-712 signature for enabling or disabling a Comet account manager. Anyone can post it to the blockchain using the allowBySig method, which does have gas costs.\nmanager (string) The address of the manager of the account.\nisAllowed (boolean) Pass true to enable a manager, false to disable.\n[expiry] (number) The time at which to expire the signature. A block timestamp as seconds since the unix epoch. Defaults to 10e9.\nRETURN (object) Returns an object that contains the v, r, and s components of an Ethereum signature as hexadecimal strings.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n(async () => {\n\nconst allowSignature = await comet.createAllowSignature(\n'0xbBbBBBBbbBBBbbbBbbBbbbbBBbBbbbbBbBbbBBbB',\ntrue\n);\nconsole.log('allowSignature', allowSignature);\n\n})().catch(console.error);\n\nTransfer\nTransfers an asset to another account within Compound Comet.\nsrc (string | boolean) The source account address in the transfer. If the transfer is on behalf of the sender instead of a manager, true can be passed instead of an address as a string.\ndst (string) The desination account address in the transfer.\nasset (string) A string of the name of the asset to transfer.\namount (number | string | BigNumber) A string, number, or BigNumber object of the amount of an asset to transfer. Use the mantissa boolean in the options parameter to indicate if this value is scaled up (so there are no decimals) or in its natural scale.\n[options] (CallOptions) Call options and Ethers.js overrides for the transaction.\nRETURN (object) Returns an Ethers.js transaction object of the transfer transaction.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n// Ethers.js overrides are an optional last parameter\n// const trxOptions = { gasLimit: 250000 };\n\n(async function() {\n\nconsole.log('Transferring WETH in Compound Comet...');\nconst trx = await comet.transfer(\ntrue, // on behalf of the sender\ndestinationAddress,\nCompound.WETH,\n'10000000',\ntrxOptions\n);\nconsole.log('Ethers.js transaction object', trx);\n\n})().catch(console.error);\n\nWithdraw\nWithdraws an asset from Compound Comet from the sender’s account to itself.\nasset (string) A string of the name of the asset to withdraw.\namount (number | string | BigNumber) A string, number, or BigNumber object of the amount of an asset to withdraw. Use the mantissa boolean in the options parameter to indicate if this value is scaled up (so there are no decimals) or in its natural scale.\n[options] (CallOptions) Call options and Ethers.js overrides for the transaction.\nRETURN (object) Returns an Ethers.js transaction object of the withdraw transaction.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n// Ethers.js overrides are an optional last parameter\n// const trxOptions = { gasLimit: 250000 };\n\n(async function() {\n\nconsole.log('Withdrawing DAI from my account...');\nconst trx = await comet.withdraw(\nCompound.DAI,\n10,\ntrxOptions\n);\nconsole.log('Ethers.js transaction object', trx);\n\n})().catch(console.error);\n\nWithdraw To\nWithdraws an asset from Compound Comet from the sender’s account to another.\ndst (string) The desination account address in the withdrawal.\nasset (string) A string of the name of the asset to withdraw.\namount (number | string | BigNumber) A string, number, or BigNumber object of the amount of an asset to withdraw. Use the mantissa boolean in the options parameter to indicate if this value is scaled up (so there are no decimals) or in its natural scale.\n[options] (CallOptions) Call options and Ethers.js overrides for the transaction.\nRETURN (object) Returns an Ethers.js transaction object of the withdraw transaction.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n// Ethers.js overrides are an optional last parameter\n// const trxOptions = { gasLimit: 250000 };\n\n(async function() {\n\nconsole.log('Withdrawing DAI from my account to dst account...');\nconst trx = await comet.withdrawTo(\ndst, // destination, the address that the withdrawn asset is sent to\nCompound.DAI,\n10,\ntrxOptions\n);\nconsole.log('Ethers.js transaction object', trx);\n\n})().catch(console.error);\n\nWithdraw From\nWithdraws an asset from Compound Comet from one account to another. The caller must be an allowed manager for the source account.\nsrc (string) The source account address in the withdrawal. The sender must be an allowed manager for the source account.\ndst (string) The desination account address in the withdrawal.\nasset (string) A string of the name of the asset to withdraw.\namount (number | string | BigNumber) A string, number, or BigNumber object of the amount of an asset to withdraw. Use the mantissa boolean in the options parameter to indicate if this value is scaled up (so there are no decimals) or in its natural scale.\n[options] (CallOptions) Call options and Ethers.js overrides for the transaction.\nRETURN (object) Returns an Ethers.js transaction object of the withdraw transaction.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n// Ethers.js overrides are an optional last parameter\n// const trxOptions = { gasLimit: 250000 };\n\n(async function() {\n\nconsole.log('Withdrawing DAI from src account to dst account...');\nconst trx = await comet.withdrawFrom(\nsrc, // source address, sender must be an allowed manager for the address\ndst, // destination, the address that the withdrawn asset is sent to\nCompound.DAI,\n10,\ntrxOptions\n);\nconsole.log('Ethers.js transaction object', trx);\n\n})().catch(console.error);\n\nGet Supply Rate\nGets the supply rate. This method returns the current supply rate as the decimal representation of a percentage scaled up by 10 ^ 18.\n[utilization] (string | number | BigNumber) A number representing the utilization rate in which to get the corresponding supply rate. The current utilization rate can be fetched by using Compound.comet.getUtilization().\nRETURN (string) Returns a string of the numeric value of the supply rate.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n(async function () {\nconst supplyRate = await comet.getSupplyRate();\nconsole.log('Supply Rate', supplyRate);\n})().catch(console.error);\n\nGet Borrow Rate\nGets the borrow rate. This method returns the current borrow rate as the decimal representation of a percentage scaled up by 10 ^ 18.\n[utilization] (string | number | BigNumber) A number representing the utilization rate in which to get the corresponding supply rate. The current utilization rate can be fetched by using Compound.comet.getUtilization().\nRETURN (string) Returns a string of the numeric value of the borrow rate.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n(async function () {\nconst borrowRate = await comet.getBorrowRate();\nconsole.log('Borrow Rate', borrowRate);\n})().catch(console.error);\n\nGet Utilization\nGets the utilization rate.\nRETURN (string) Returns the current protocol utilization as a percentage as a decimal, represented by an unsigned integer, scaled up by 10 ^ 18.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n(async function () {\nconst utilization = await comet.getUtilization();\nconsole.log('Utilization', utilization);\n})().catch(console.error);\n\nAbsorb\nThis method triggers the liquidation of one or many underwater accounts.\nabsorber (string) The account that is issued liquidator points during successful execution.\naccounts (string | string[]) A string of one or an array of many addresses of underwater accounts.\n[options] (CallOptions) Call options and Ethers.js overrides for the transaction.\nRETURN (object) Returns an Ethers.js transaction object of the absorb transaction.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n(async function () {\nconst addresses = [\n'0xUnderwaterAccountAddress1',\n];\nconst trx = await comet.absorb(addresses);\nconsole.log('Ethers.js transaction object', trx);\n})().catch(console.error);\n\nGet Reserves\nGets the Comet protocol reserves for the base asset as an integer.\nRETURN (string) Returns the current protocol reserves in in the base asset as an unsigned integer, scaled up by 10 to the “decimals” integer in the base asset’s contract.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n(async function () {\nconst reserves = await comet.getReserves();\nconsole.log('Reserves', reserves);\n})().catch(console.error);\n\nTarget Reserves\nGets the Comet protocol target reserves.\nRETURN (string) Returns the protocol target reserves in the base asset as an unsigned integer, scaled up by 10 to the “decimals” integer in the base asset’s contract.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n(async function () {\nconst target = await comet.targetReserves();\nconsole.log('Target Reserves', target);\n})().catch(console.error);\n\nIs Borrow Collateralized\nGets the collateralization of an account as a boolean.\naccount (string) The account address as a string.\nRETURN (boolean) Returns the collateralization of the account as a boolean.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n(async function () {\nconst address = '0xAccountThatBorrows';\nconst isCollateralized = await comet.isBorrowCollateralized(address);\nconsole.log('Is Collateralized', isCollateralized);\n})().catch(console.error);\n\nIs Liquidatable\nChecks if the passed account is presently liquidatable.\naccount (string) The account address as a string.\nRETURN (boolean) Returns the ability to liquidate the account as a boolean.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n(async function () {\nconst address = '0xAccountThatBorrows';\nconst isLiquidatable = await comet.isLiquidatable(address);\nconsole.log('Is Liquidatable', isLiquidatable);\n})().catch(console.error);\n\nQuote Collateral\nGets the price of the asset that is passed to it in USD as an unsigned integer, scaled up by 10 ^ 8.\nasset (string) A string of the name of the asset.\nbaseAmount (number | string | BigNumber) A string, number, or BigNumber object of the amount of the base asset to get a quote. Use the mantissa boolean in the options parameter to indicate if this value is scaled up (so there are no decimals) or in its natural scale.\n[options] (CallOptions) Call options and Ethers.js overrides for the transaction.\nRETURN (string) Returns the price of the asset that is passed to it in USD as an unsigned integer, scaled up by 10 ^ 6.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n(async function () {\nconst price = await comet.quoteCollateral(Compound.UNI, '1000000000');\nconsole.log('Price quote of 1000 base asset of UNI', price);\n})().catch(console.error);\n\nBuy Collateral\nBuys discounted collateral from the protocol. This collateral is available after an insolvent borrower account has been absorbed by the protocol. Collateral is only sold when the target reserves amount is not yet reached. The mantissa call option is applied to both the minAmount and baseAmount parameters.\nasset (string) A string of the name of the asset to buy.\nminAmount (number | string | BigNumber) A string, number, or BigNumber object of the minimum amount of an asset to buy from the protocol. Use the mantissa boolean in the options parameter to indicate if this value is scaled up (so there are no decimals) or in its natural scale.\nbaseAmount (number | string | BigNumber) A string, number, or BigNumber object of the amount of base asset used to buy the collateral.\nrecipient (string) The desination account address of the collateral that is purchased.\nnoApprove (boolean) Explicitly prevent this method from attempting an ERC-20 approve transaction prior to buying collateral using the base asset.\n[options] (CallOptions) Call options and Ethers.js overrides for the transaction.\nRETURN (object) Returns an Ethers.js transaction object of the buy transaction.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n(async function() {\n\nconst me = '0xRecipient';\n\nconsole.log('Buying collateral...');\nconst trx = await comet.buyCollateral(\nCompound.WBTC,\n1,\n10000\n);\nconsole.log('Ethers.js transaction object', trx);\nawait trx.wait(1);\n\n})().catch(console.error);\n\nCompound III Get Price\nGets the price of the asset that is passed to it in USD as an unsigned integer, scaled up by 10 ^ 8.\nasset (string) A string of the symbol of the asset.\nRETURN (string) Returns the price of the asset that is passed to it in USD as an unsigned integer, scaled up by 10 ^ 8.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n(async function () {\nconst price = await comet.getPrice(Compound.WBTC);\nconsole.log('Price of WBTC', price);\n})().catch(console.error);\n\nBorrow Balance Of\nGets the current borrow balance of an account as an unsigned integer. If the account has a non-negative base asset balance, it will return 0.\naccount (string) The account address as a string.\nRETURN (string) Returns the collateralization of the account as an integer.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n(async function () {\nconst address = '0xAccountThatBorrows';\nconst bal = await comet.borrowBalanceOf(address);\nconsole.log('Borrow Balance', bal.toString());\n})().catch(console.error);\n\nCollateral Balance Of\nGets the current balance of the collateral asset for the specified account.\naccount (string) The account address as a string.\nasset (string) The name of the collateral asset.\nRETURN (string) Returns the collateral balance as an integer.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n(async function () {\nconst address = '0xAccountThatSupplied';\nconst balance = await comet.collateralBalanceOf(address, Compound.WBTC);\nconsole.log('Collateral balance', balance);\n})().catch(console.error);\n\nGet Asset Info\nGets the stored information for a supported asset.\nassetIndex (number | string | BigNumber) The index of the asset in the array in the Comet contract.\nRETURN (AssetInfo) Returns a tuple of the asset’s information.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n(async function () {\nconst assetInfo = await comet.getAssetInfo(2);\nconsole.log('Asset Info', assetInfo);\n})().catch(console.error);\n\nGet Asset Info By Address\nGets the stored information for a supported asset.\n_address (string) The contract address of the supported asset.\nRETURN (AssetInfo) Returns a tuple of the asset’s information.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n(async function () {\nconst assetInfo = await comet.getAssetInfoByAddress('0xContract');\nconsole.log('Asset Info', assetInfo);\n})().catch(console.error);\n\nGet Asset Info By Symbol\nGets the stored information for a supported asset.\nsymbol (string) The symbol of the supported asset.\nRETURN (AssetInfo) Returns a tuple of the asset’s information.\nconst compound = new Compound(window.ethereum);\nconst comet = compound.comet.MAINNET_USDC();\n\n(async function () {\nconst assetInfo = await comet.getAssetInfoBySymbol(Compound.WETH);\nconsole.log('Asset Info', assetInfo);\n})().catch(console.error);\n\nGet Supported Deployments\nGets an array of the supported Compound III deployment names.\nRETURN (string[]) Returns an array of strings that are used to refer to each Compound III deployment.\nconst networkNames = Compound.comet.getSupportedDeployments();\n\nGet Supported Collaterals\nGets an array of the supported collateral assets in the specified Comet instance.\ndeployment (string?) The specific deployment in which to get supported collaterals. The key is usually ${network}_${baseAssetSymbol}. Use getSupportedDeployments to get proper values for this parameter. Defaults to cUSDCv3 on Ethereum Mainnet (mainnet_usdc) if nothing is passed.\nRETURN (string[]) Returns an array of strings of the asset names.\nconst collaterals = Compound.comet.getSupportedCollaterals();\n\nGet Base Asset Name\nGets the name of the base asset in the specified instance.\ndeployment (string?) The specific deployment in which to get supported collaterals. The key is usually ${network}_${baseAssetSymbol}. Use getSupportedDeployments to get proper values for this parameter. Defaults to cUSDCv3 on Ethereum Mainnet (mainnet_usdc) if nothing is passed.\nRETURN (string) Returns a string of the base asset name.\nconst baseAssetName = Compound.comet.getBaseAssetName();","tokens":5352,"crawled_at":1791194627280}
+{"id":10416,"url":"https://www.getfoundry.sh/cast/sending-transactions","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Sending transactions – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nSending transactions\n\nCast sends transactions to deploy contracts, call functions, and transfer value. Transactions require a signer (private key, keystore, or hardware wallet).\n\nBasic transaction\n\n$ cast send $TO --value 1ether --private-key $PRIVATE_KEY\n\n$ cast send $CONTRACT \"transfer(address,uint256)\" $TO 1000000000000000000 --private-key $PRIVATE_KEY\n\n$ cast send --create $BYTECODE --private-key $PRIVATE_KEY\n\nSigning options\n\nPrivate key\nPass directly (not recommended for production):\n$ cast send $CONTRACT \"mint()\" --private-key $PRIVATE_KEY\n\nKeystore file\nUse an encrypted keystore:\n$ cast send $CONTRACT \"mint()\" --keystore ~/.foundry/keystores/my-key --password $PASSWORD\n\nOr prompt for password:\n$ cast send $CONTRACT \"mint()\" --keystore ~/.foundry/keystores/my-key --interactive\n\nHardware wallet\nUse Ledger or Trezor:\n$ cast send $CONTRACT \"mint()\" --ledger\n$ cast send $CONTRACT \"mint()\" --trezor\n\nBrowser wallet\nConnect an injected wallet through Foundry's local browser bridge:\n$ cast send $CONTRACT \"mint()\" --rpc-url $RPC_URL --browser\n\nSee Browser Wallet Signing for the approval flow, network checks, and agent handoff guidance.\n\nAWS KMS\nUse a key stored in AWS KMS:\n$ cast send $CONTRACT \"mint()\" --aws\n\nTransaction parameters\n\n$ cast send $CONTRACT \"mint()\" --gas-limit 100000 --private-key $KEY\n\n$ cast send $CONTRACT \"mint()\" --gas-price 20gwei --private-key $KEY\n\n$ cast send $CONTRACT \"mint()\" --priority-gas-price 1gwei --private-key $KEY\n\n$ cast send $CONTRACT \"mint()\" --nonce 42 --private-key $KEY\n\n$ cast send $CONTRACT \"deposit()\" --value 0.1ether --private-key $KEY\n\nWaiting and confirmations\n\nBy default, cast send waits for the transaction to be mined.\n\n$ cast send $CONTRACT \"mint()\" --private-key $KEY --async\n\n$ cast send $CONTRACT \"mint()\" --private-key $KEY --confirmations 3\n\nTransaction simulation\n\nPreview a transaction without sending:\n\nSimulate with cast call\n$ cast call $CONTRACT \"transfer(address,uint256)\" $TO $AMOUNT --from $SENDER\n\nEstimate gas\n$ cast estimate $CONTRACT \"transfer(address,uint256)\" $TO $AMOUNT --from $SENDER\n\nAccess lists (EIP-2930)\n\nCreate an access list to reduce gas costs:\n\nGenerate access list\n$ cast access-list $CONTRACT \"transfer(address,uint256)\" $TO $AMOUNT --from $SENDER\n\nSend with access list\n$ cast send $CONTRACT \"transfer(address,uint256)\" $TO $AMOUNT --access-list $ACCESS_LIST --private-key $KEY\n\nRaw transactions\n\nSign without sending\n$ cast mktx $CONTRACT \"mint()\" --private-key $KEY\n\nPublish a signed transaction\n$ cast publish $SIGNED_TX\n\nBlob transactions (EIP-4844)\n\nSend transactions with blob data:\n\nSend blob transaction\n$ cast send $CONTRACT \"submitBlob()\" --blob \"0x...\" --private-key $KEY\n\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":697,"crawled_at":1791194641191}
+{"id":10417,"url":"https://www.metaplex.com/docs/smart-contracts/core/plugins/burn-delegate","domain":"www.metaplex.com","chapter":"docs","title":"Burn Delegate Plugin | Metaplex Core","text":"The Burn Delegate Plugin allows a designated authority to burn Core Assets on behalf of the owner. Useful for game mechanics, subscription services, and automated asset lifecycle management.\nWhat You'll Learn\nAdd the Burn Delegate plugin to an Asset\nDelegate burn authority to another address\nRevoke burn authority\nUse cases: games, subscriptions, automated burns\n\nSummary\nThe Burn Delegate is an Owner Managed plugin that allows a delegate to burn an Asset. Once added, the delegate can burn the Asset at any time without owner approval.\nDelegate burn authority to a program or wallet\nAuthority is revoked on Asset transfer\nUse Permanent Burn Delegate for irrevocable burn authority\nNo additional arguments required\nOut of Scope\nCollection burning (different process), permanent burn authority (see Permanent Burn Delegate), and Token Metadata burn authority (different system).\nQuick Start\nJump to: Add Plugin · Delegate Authority · Revoke\nAdd the Burn Delegate plugin: addPlugin(umi, { asset, plugin: { type: 'BurnDelegate' } })\nOptionally delegate to another address\nThe delegate can now burn the Asset at any time\nWhen to Use Burn vs Permanent Burn Delegate\nUse CaseBurn DelegatePermanent Burn Delegate\nGame item destruction\n✅ Best choice\n✅ Also works\n\nSubscription expiration\n✅ Best choice\n❌ Too permanent\n\nBurn frozen Assets\n❌ Cannot burn\n✅ Can force burn\n\nAuthority persists on transfer\n❌ Revokes\n✅ Persists\n\nEmergency burn capability\n❌ Limited\n✅ Best choice\n\nChoose Burn Delegate when burn authority should reset on ownership change.\n\nChoose Permanent Burn Delegate when authority must persist forever.\n\nCommon Use Cases\nGame mechanics: Burn NFTs when items are consumed, destroyed, or lost in-game\nSubscription services: Auto-burn expired subscription tokens\nCrafting systems: Burn ingredient NFTs when crafting new items\nAchievement redemption: Burn achievement tokens when redeemed for rewards\nEvent tickets: Burn tickets after event check-in\nLimited-time assets: Burn assets after expiration period\nWorks With\n\nMPL Core Asset\n✅\n\nMPL Core Collection\n❌\n\nArguments\nThe Burn Plugin doesn't contain any arguments to pass in.\nAdding the Burn Plugin to an Asset\nAdding a Burn Plugin to an MPL Core Asset\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { addPlugin } from '@metaplex-foundation/mpl-core'\n\n(async () => {\n\nconst asset = publicKey('11111111111111111111111111111111')\n\nawait addPlugin(umi, {\n\nasset: asset,\n\nplugin: { type: 'BurnDelegate' },\n\n}).sendAndConfirm(umi)\n\n})();\n\nDelegating Burn Authority\nThe Burn Delegate plugin authority can be delegated to a different address using the approvePluginAuthority function. This allows you to change who can burn the Asset.\nDelegate Burn Authority\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { approvePluginAuthority } from '@metaplex-foundation/mpl-core'\n\n(async () => {\n\nconst assetAddress = publicKey('11111111111111111111111111111111')\n\nconst newDelegate = publicKey('22222222222222222222222222222222')\n\nawait approvePluginAuthority(umi, {\n\nasset: assetAddress,\n\nplugin: { type: 'BurnDelegate' },\n\nnewAuthority: { type: 'Address', address: newDelegate },\n\n}).sendAndConfirm(umi)\n\n})();\n\nRevoking Burn Authority\nThe burn authority can be revoked using the revokePluginAuthority function, returning control to the asset owner.\nRevoke Burn Authority\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { revokePluginAuthority } from '@metaplex-foundation/mpl-core'\n\n(async () => {\n\nconst assetAddress = publicKey('11111111111111111111111111111111')\n\nawait revokePluginAuthority(umi, {\n\nasset: assetAddress,\n\nplugin: { type: 'BurnDelegate' },\n\n}).sendAndConfirm(umi)\n\n})();\n\nCommon Errors\nAuthority mismatch\nOnly the burn delegate authority can burn the Asset. Verify you're signing with the correct keypair.\nAsset is frozen\nFrozen Assets cannot be burned. The freeze authority must thaw the Asset first.\nNotes\nOwner Managed: requires owner signature to add\nAuthority is automatically revoked when the Asset transfers\nFrozen Assets cannot be burned\nUse Permanent Burn Delegate if authority must persist after transfer\nBurning is immediate and irreversible\nQuick Reference\nWho Can Burn?\nAuthorityCan Burn?\nAsset Owner\nYes (always)\n\nBurn Delegate\nYes\n\nPermanent Burn Delegate\nYes (force approve)\n\nUpdate Authority\nNo\n\nFAQ\nWhat's the difference between Burn Delegate and Permanent Burn Delegate?\nBurn Delegate authority is revoked on transfer. Permanent Burn Delegate authority persists forever and uses forceApprove, meaning it can burn even if the Asset is frozen.\nCan the owner still burn if there's a Burn Delegate?\nYes. The owner can always burn their own Asset regardless of delegates.\nDoes Burn Delegate work on frozen Assets?\nNo. Regular Burn Delegate cannot burn frozen Assets. Use Permanent Burn Delegate if you need to burn frozen Assets.\nWhen is Burn Delegate revoked?\nWhen the Asset is transferred to a new owner. The new owner would need to add a new Burn Delegate.\nRelated Plugins\nPermanent Burn Delegate - Irrevocable burn authority with forceApprove\nFreeze Delegate - Block transfers and burns temporarily\nTransfer Delegate - Allow delegate to transfer Assets\nGlossary\nTermDefinition\nBurn Delegate\nOwner Managed plugin allowing a delegate to burn the Asset\n\nOwner Managed\nPlugin type requiring owner signature to add\n\nRevoke\nRemove the delegate's burn authority\n\nPermanent Burn Delegate\nIrrevocable version that persists after transfer\n\nforceApprove\nPermanent plugin ability to override freeze restrictions","tokens":1381,"crawled_at":1791194659672}
+{"id":10418,"url":"https://docs.near.ai/llms.txt","domain":"docs.near.ai","chapter":"crypto_ai_depin","title":"","text":"# NEAR AI\n\n> Documentation for NEAR AI Cloud: private, verifiable AI inference in Trusted Execution Environments through an OpenAI-compatible API.\n\n- [Private. Intelligent. Yours.](https://docs.near.ai/index.md): Build private, user-owned AI with NEAR AI Cloud\n- [Quickstart](https://docs.near.ai/cloud/quickstart.md)\n- [Available Models](https://docs.near.ai/cloud/models.md): Explore NEAR AI Cloud model catalog\n- [Reasoning Models](https://docs.near.ai/cloud/reasoning-models.md): Learn how to enable and disable reasoning capabilities for supported models\n- [Private Inference](https://docs.near.ai/cloud/private-inference.md): Learn how NEAR AI Cloud's private inference leverages TEEs to provide cryptographically verifiable AI computations with complete data privacy and security.\n- [Staking for Inference](https://docs.near.ai/cloud/staking-for-inference/overview.md): Stake NEAR and let the staking rewards pay for private inference on NEAR AI Cloud — your principal stays yours and stays withdrawable.\n- [Staking Calculator](https://docs.near.ai/cloud/staking-for-inference/calculator.md): Estimate how much NEAR to stake to cover your private inference usage, or see what a given stake gets you — based on the current NEAR price and staking APY.\n- [Verification](https://docs.near.ai/cloud/verification/index.md): Verify requests sent through the NEAR AI Cloud Gateway.\n- [Verify the NEAR AI Cloud Gateway](https://docs.near.ai/cloud/verification/cloud-api/index.md): Verify the gateway, model evidence, connection, response, and software evidence for requests sent through cloud-api.near.ai.\n- [Gateway Attestation](https://docs.near.ai/cloud/verification/cloud-api/gateway-attestation.md): Verify the NEAR AI Cloud gateway attestation for requests sent to cloud-api.near.ai.\n- [NEAR Model Attestations](https://docs.near.ai/cloud/verification/cloud-api/model-attestations.md): Verify the NEAR model-attestation report returned through the NEAR AI Cloud gateway.\n- [TLS Connection Binding](https://docs.near.ai/cloud/verification/cloud-api/tls.md): Bind a live NEAR AI Cloud gateway TLS connection to the gateway attestation.\n- [Response Signatures](https://docs.near.ai/cloud/verification/cloud-api/response-signatures.md): Verify available response signatures from the NEAR AI Cloud gateway against exact bytes and matching preflight evidence.\n- [Image Provenance](https://docs.near.ai/cloud/verification/cloud-api/image-provenance.md): Apply an image-provenance policy to configurations measured in NEAR AI Cloud gateway and model attestations.\n- [Quote, Nonce, and Signer Bindings](https://docs.near.ai/cloud/verification/reference/quote-nonce-signer.md): Shared rules for reading verified quotes, checking freshness, and matching signing identities.\n- [Response Signature Verification](https://docs.near.ai/cloud/verification/reference/response-signature-verification.md): Verify a response signature over exact request and response bytes.\n- [Verification Policy](https://docs.near.ai/cloud/verification/reference/verification-policy.md): Define required evidence, acceptable measurements, provenance requirements, and handling for unavailable verification results.\n- [SDK](https://docs.near.ai/cloud/inference-sdk/index.md): Use the JavaScript and Python SDKs for verified, encrypted Chat Completions.\n- [JavaScript](https://docs.near.ai/cloud/inference-sdk/javascript.md): Use the JavaScript SDK for verified, end-to-end encrypted Chat Completions.\n- [Python](https://docs.near.ai/cloud/inference-sdk/python.md): Use the asynchronous Python SDK for verified, encrypted Chat Completions.\n- [OpenAI Compatibility](https://docs.near.ai/cloud/guides/openai-compatibility.md): How to use NEAR AI Cloud with standard OpenAI SDKs\n- [Stateless Responses API](https://docs.near.ai/cloud/guides/stateless-responses.md): Use the OpenAI Responses shape without server-side conversation or response storage\n- [Usage Reporting API](https://docs.near.ai/cloud/guides/usage-reporting.md)\n- [Integrations](https://docs.near.ai/cloud/guides/integrations/index.md): Use NEAR AI Cloud with third-party software that supports OpenAI-compatible providers.\n- [Model Discovery and Refresh](https://docs.near.ai/cloud/guides/integrations/model-discovery.md): Discover current NEAR AI Cloud models and refresh stale client model lists.\n- [OpenCode](https://docs.near.ai/cloud/guides/integrations/opencode.md): Configure OpenCode to use NEAR AI Cloud as an OpenAI-compatible provider.\n- [Cursor](https://docs.near.ai/cloud/guides/integrations/cursor.md): Configure Cursor with NEAR AI Cloud through Cursor's OpenAI API key and base URL settings.\n- [Continue](https://docs.near.ai/cloud/guides/integrations/continue.md): Configure Continue to use NEAR AI Cloud through its OpenAI-compatible provider.\n- [Cline, Roo Code, and Kilo Code](https://docs.near.ai/cloud/guides/integrations/cline-roo-kilo.md): Configure Cline, Roo Code, and Kilo Code with NEAR AI Cloud's OpenAI-compatible API.\n- [Aider and Zed](https://docs.near.ai/cloud/guides/integrations/aider-zed.md): Configure Aider and Zed to use NEAR AI Cloud as an OpenAI-compatible provider.\n- [Goose](https://docs.near.ai/cloud/guides/opencode-goose.md): Configure Goose to use NEAR AI Cloud as an OpenAI-compatible provider.\n- [LibreChat](https://docs.near.ai/cloud/guides/integrations/librechat.md): Configure LibreChat to use NEAR AI Cloud as an OpenAI-compatible custom endpoint.\n- [Open WebUI](https://docs.near.ai/cloud/guides/integrations/open-webui.md): Configure Open WebUI to use NEAR AI Cloud as an OpenAI-compatible provider.\n- [LiteLLM Proxy](https://docs.near.ai/cloud/guides/integrations/litellm.md): Configure the LiteLLM Python SDK and LiteLLM Proxy to use NEAR AI Cloud.\n- [Dify](https://docs.near.ai/cloud/guides/integrations/dify.md): Configure Dify with NEAR AI Cloud through the OpenAI-API-compatible model provider plugin.\n- [Prompt Caching](https://docs.near.ai/cloud/guides/prompt-caching.md): How NEAR AI Cloud caches prompt prefixes to reduce latency and cost\n- [Fusion](https://docs.near.ai/cloud/guides/fusion.md): Use server-side multi-model deliberation from OpenAI-compatible clients\n- [Web Search](https://docs.near.ai/cloud/guides/web-search.md): Give models access to live web results through Chat Completions\n- [Embeddings, Images, Audio & More](https://docs.near.ai/cloud/guides/specialized-endpoints.md): Use NEAR AI Cloud for embeddings, reranking, image generation, audio transcription, and PII detection — all inside TEEs\n- [End-to-End Encrypted Chat Completions](https://docs.near.ai/cloud/guides/e2ee-chat-completions.md): How to use end-to-end encryption for chat completions with NEAR AI Cloud\n- [Direct Completions](https://docs.near.ai/cloud/experimental/direct-completions.md): Experimental: send requests straight to one self-hosted model's TEE endpoint, without the NEAR AI Cloud Gateway.\n- [SDK](https://docs.near.ai/cloud/inference-sdk/direct.md): Experimental SDK notes for direct model endpoints.\n- [API Reference](https://docs.near.ai/api-reference/introduction.md): OpenAI-compatible REST API for private, verifiable AI inference on NEAR AI Cloud\n- [Create chat completion](https://docs.near.ai/api-reference/chat/create-chat-completion.md): Generate AI model responses for chat conversations. Supports both streaming and non-streaming modes. OpenAI-compatible endpoint.\n- [Create text completion](https://docs.near.ai/api-reference/chat/create-text-completion.md): Generate AI model responses for text prompts. OpenAI-compatible endpoint.\n- [List available models](https://docs.near.ai/api-reference/chat/list-available-models.md): Returns all AI models available for completions. OpenAI-compatible endpoint.\n- [Create response](https://docs.near.ai/api-reference/responses/create-response.md): Generate a single-turn, stateless AI response with optional streaming.\n- [List models with pricing](https://docs.near.ai/api-reference/models/list-models-with-pricing.md): Get all available models with pricing information. Public endpoint.\n- [Get model details](https://docs.near.ai/api-reference/models/get-model-details.md): Get pricing and metadata for a specific model. URL-encode model names containing slashes. Public endpoint.\n- [Edit images from a text prompt and image](https://docs.near.ai/api-reference/images/edit-images-from-a-text-prompt-and-image.md): Edit images using an AI model from an image and text description. OpenAI-compatible endpoint.\n- [Generate images from text prompt](https://docs.near.ai/api-reference/images/generate-images-from-text-prompt.md): Generate images using an AI model from a text description. OpenAI-compatible endpoint.\n- [Audio transcription endpoint](https://docs.near.ai/api-reference/audio/audio-transcription-endpoint.md): Transcribe audio files using Whisper models. Accepts audio file uploads via multipart/form-data. Supports MP3, WAV, WEBM, FLAC, OGG, and M4A formats. Maximum file size: 25 MB.\n- [Document reranking endpoint](https://docs.near.ai/api-reference/rerank/document-reranking-endpoint.md): Ranks documents by relevance to a query using a reranker model.\n- [Text similarity scoring endpoint](https://docs.near.ai/api-reference/score/text-similarity-scoring-endpoint.md): Scores the similarity between two texts using a scoring/ranking model.\n- [Post v1privacyclassify](https://docs.near.ai/api-reference/privacy/post-v1privacyclassify.md)\n- [Post v1privacyredact](https://docs.near.ai/api-reference/privacy/post-v1privacyredact.md)\n- [Get Intel Trust Authority attestation token](https://docs.near.ai/api-reference/attestation/get-intel-trust-authority-attestation-token.md): Get Intel Trust Authority signed attestation JWTs for the gateway and, when requested, compatible model provider evidence. Public endpoint — this is an explicit, documented decision (nearai/infra#193): the response carries only ITA-signed TEE evidence (no customer or key-scoped data), public access…\n- [Get attestation report](https://docs.near.ai/api-reference/attestation/get-attestation-report.md): Get hardware attestation report for TEE verification. Requires an API key (nearai/infra#193); report retrieval is non-billable — no usage or billing records are created.\n- [Get completion or Responses API signature](https://docs.near.ai/api-reference/attestation/get-completion-or-responses-api-signature.md): Get a cryptographic signature for a chat completion or completed stateless `resp_*` response. Returns signature data on success, or an unavailable response if a chat-completion stream was disconnected.\n- [Get current user](https://docs.near.ai/api-reference/users/get-current-user.md): Returns the profile of the currently authenticated user, including their organizations and workspaces.\n- [Update current user's profile](https://docs.near.ai/api-reference/users/update-current-users-profile.md): Updates the profile information for the currently authenticated user.\n- [Create a new access token](https://docs.near.ai/api-reference/users/create-a-new-access-token.md): Creates a new short-lived access token using the current refresh token.\n- [List pending invitations for the current user](https://docs.near.ai/api-reference/users/list-pending-invitations-for-the-current-user.md): Returns all pending organization invitations for the authenticated user's email.\n- [Accept an organization invitation](https://docs.near.ai/api-reference/users/accept-an-organization-invitation.md): Accepts a pending invitation and adds the user as a member of the organization.\n- [Decline an organization invitation](https://docs.near.ai/api-reference/users/decline-an-organization-invitation.md): Declines a pending invitation to join an organization.\n- [Get user's refresh tokens](https://docs.near.ai/api-reference/users/get-users-refresh-tokens.md): Returns all active refresh tokens for the currently authenticated user.\n- [Revoke a user refresh token](https://docs.near.ai/api-reference/users/revoke-a-user-refresh-token.md): Revokes a specific refresh token for the currently authenticated user.\n- [Get current user's account eligibility status](https://docs.near.ai/api-reference/users/get-current-users-account-eligibility-status.md): Returns a minimal eligibility response for frontend preflight checks. AML/KYT provider details are never exposed in this public response.\n- [Revoke all tokens for a user](https://docs.near.ai/api-reference/users/revoke-all-tokens-for-a-user.md): Revokes all tokens (both refresh tokens and access tokens) for the currently authenticated user. This deletes all refresh tokens from the database and invalidates all JWT access tokens by updating the user's tokens_revoked_at timestamp.\n- [List organizations](https://docs.near.ai/api-reference/organizations/list-organizations.md): Get all organizations you belong to.\n- [Create a new organization](https://docs.near.ai/api-reference/organizations/create-a-new-organization.md): Creates a new organization with the authenticated user as owner.\n- [Get organization by ID](https://docs.near.ai/api-reference/organizations/get-organization-by-id.md): Returns organization details for a specific organization ID.\n- [Update organization](https://docs.near.ai/api-reference/organizations/update-organization.md): Updates organization details for a specific organization ID.\n- [Delete organization (owner only)](https://docs.near.ai/api-reference/organizations/delete-organization-owner-only.md): Deletes an organization. Only the organization owner can perform this action.\n- [Cancel an organization invitation (short path)](https://docs.near.ai/api-reference/organization-members/cancel-an-organization-invitation-short-path.md): Cancels a pending invitation for the organization. Only owners and admins can cancel invitations. This endpoint is an alias for `DELETE /v1/organizations/{org_id}/members/invitations/{invitation_id}`.\n- [List organization members with limited user information](https://docs.near.ai/api-reference/organization-members/list-organization-members-with-limited-user-information.md): Returns limited user information for privacy and security: - All members: See only public user info (username, display name, avatar) - Sensitive data (email, last login, etc.) is not exposed to any organization members\n- [Add a member to an organization](https://docs.near.ai/api-reference/organization-members/add-a-member-to-an-organization.md): Adds a new member to the organization. The authenticated user must be an owner or admin.\n- [List organization invitations](https://docs.near.ai/api-reference/organization-members/list-organization-invitations.md): Returns invitations for the organization. Only accessible to owners and admins.\n- [Cancel an organization invitation](https://docs.near.ai/api-reference/organization-members/cancel-an-organization-invitation.md): Cancels a pending invitation for the organization. Only owners and admins can cancel invitations.\n- [Invite users to an organization by email](https://docs.near.ai/api-reference/organization-members/invite-users-to-an-organization-by-email.md): Invites multiple users to the organization by their email addresses. The authenticated user must be an owner or admin. Returns results for each invitation attempt, including successes and failures.\n- [Update an organization member's role](https://docs.near.ai/api-reference/organization-members/update-an-organization-members-role.md): Updates a member's role in the organization. The authenticated user must be an owner or admin. Only owners can promote members to owner role.\n- [Remove a member from an organization](https://docs.near.ai/api-reference/organization-members/remove-a-member-from-an-organization.md): Removes a member from the organization. The authenticated user must be an owner or admin, or the member can remove themselves. The last owner cannot be removed.\n- [Get invitation details by token (public endpoint)](https://docs.near.ai/api-reference/invitations/get-invitation-details-by-token-public-endpoint.md): Returns invitation details for a specific token. This is a public endpoint that allows users to view invitation details before logging in.\n- [Accept invitation by token (requires authentication)](https://docs.near.ai/api-reference/invitations/accept-invitation-by-token-requires-authentication.md): Accepts an invitation using its token. The authenticated user's email must match the invitation email.\n- [List workspaces in an organization](https://docs.near.ai/api-reference/workspaces/list-workspaces-in-an-organization.md): Lists all workspaces within the specified organization. The authenticated user must be a member of the organization to list workspaces.\n- [Create a new workspace in an organization](https://docs.near.ai/api-reference/workspaces/create-a-new-workspace-in-an-organization.md): Creates a new workspace within the specified organization. The authenticated user must be a member of the organization to create workspaces.\n- [Get workspace by ID](https://docs.near.ai/api-reference/workspaces/get-workspace-by-id.md): Returns workspace details for a specific workspace ID.\n- [Update workspace](https://docs.near.ai/api-reference/workspaces/update-workspace.md): Updates workspace details for a specific workspace ID.\n- [Delete workspace](https://docs.near.ai/api-reference/workspaces/delete-workspace.md): Deletes (deactivates) a workspace. Only the workspace creator or organization admin/owner can delete.\n- [List API keys for workspace](https://docs.near.ai/api-reference/workspaces/list-api-keys-for-workspace.md): Returns a paginated list of all API keys for a workspace with usage information.\n- [Create API key for workspace](https://docs.near.ai/api-reference/workspaces/create-api-key-for-workspace.md): Creates a new API key for a workspace. Note: The key may take up to 10 seconds to become active for authentication due to internal caching.\n- [Revoke an API key](https://docs.near.ai/api-reference/workspaces/revoke-an-api-key.md): Revokes a specific API key from a workspace.\n- [Update API key](https://docs.near.ai/api-reference/workspaces/update-api-key.md): Updates an API key's name, expiration date, and/or spending limit. The user must be a member of the organization that owns the workspace. All fields are optional - only provided fields will be updated.\n- [Update API key spend limit](https://docs.near.ai/api-reference/workspaces/update-api-key-spend-limit.md): Updates the spending limit for a specific API key. The user must be a member of the organization that owns the workspace. Set spend_limit to null to remove the limit.\n- [Get organization balance](https://docs.near.ai/api-reference/usage/get-organization-balance.md): Returns the current spending balance for an organization\n- [Get organization usage broken down by model.](https://docs.near.ai/api-reference/usage/get-organization-usage-broken-down-by-model.md): Returns one row per model, summed over a rolling window ending now: `day` = last 24h, `week` = last 7 days, `month` = last 30 days (NOT calendar day/week/month-to-date). Used by the dashboard pie chart to show which models drive spend.\n- [Get organization usage history](https://docs.near.ai/api-reference/usage/get-organization-usage-history.md): Returns paginated usage history for an organization\n- [Get v1organizations usagemetrics](https://docs.near.ai/api-reference/usage/get-v1organizations-usagemetrics.md)\n- [Get v1organizations usagetimeseries](https://docs.near.ai/api-reference/usage/get-v1organizations-usagetimeseries.md)\n- [Get API key usage history](https://docs.near.ai/api-reference/usage/get-api-key-usage-history.md): Returns paginated usage history for a specific API key\n- [List active reporting tokens for an organization.](https://docs.near.ai/api-reference/reporting/list-active-reporting-tokens-for-an-organization.md): The response includes non-secret prefixes and audit timestamps. It never includes raw reporting tokens or stored hashes.\n- [Create a read-only reporting token.](https://docs.near.ai/api-reference/reporting/create-a-read-only-reporting-token.md): Organization owners and admins can create reporting tokens for usage export and summary endpoints. The raw `rpt-` token is returned once.\n- [Revoke a reporting token.](https://docs.near.ai/api-reference/reporting/revoke-a-reporting-token.md): Revoked reporting tokens can no longer authenticate usage reporting requests.\n- [Export organization usage and cost rows.](https://docs.near.ai/api-reference/reporting/export-organization-usage-and-cost-rows.md): Requires a reporting token scoped to the organization in the path. Results are returned in descending `(created_at, source, id)` order with opaque cursor pagination.\n- [Summarize organization usage and costs.](https://docs.near.ai/api-reference/reporting/summarize-organization-usage-and-costs.md): Requires a reporting token scoped to the organization in the path. Totals include inference and platform service usage by default.\n- [Get costs by request IDs](https://docs.near.ai/api-reference/billing/get-costs-by-request-ids.md): Returns the cost in nano-USD for each request ID provided. A request ID is the UUID from the `inference-id` response header of /v1/chat/completions and /v1/messages responses (equivalently: UUIDv5 of the response body `id` under the DNS namespace). The `x-request-id` response header is a transport c…\n- [Get organization staking farm state](https://docs.near.ai/api-reference/staking-farm/get-organization-staking-farm-state.md): Returns the staking farm source and last synced farm-credit state for an organization. The organization must be the NEAR-authenticated user's default organization.\n- [Sync organization staking farm credits](https://docs.near.ai/api-reference/staking-farm/sync-organization-staking-farm-credits.md): Links or refreshes the NEAR-authenticated user's staking farm source for the organization, then syncs reward units from the configured staking contract.\n- [Get staking farm configuration](https://docs.near.ai/api-reference/staking-farm/get-staking-farm-configuration.md): Returns the active House of Stake farm configuration used to convert on-chain staking reward units into NEAR AI Cloud credits.\n- [List platform services (public, no auth)](https://docs.near.ai/api-reference/services/list-platform-services-public-no-auth.md)\n- [Get platform service by name (public, no auth)](https://docs.near.ai/api-reference/services/get-platform-service-by-name-public-no-auth.md)\n- [Check API key validity](https://docs.near.ai/api-reference/gateway/check-api-key-validity.md): Validates the provided API key (via Bearer token), checks rate limits, and verifies the organization has sufficient credits.\n- [Health check](https://docs.near.ai/api-reference/health/health-check.md): Check service health status. No authentication required.\n- [List aggregated feature requests for admins.](https://docs.near.ai/api-reference/feature-requests/list-aggregated-feature-requests-for-admins.md)\n- [Submit or update the current user's interest in a feature request target.](https://docs.near.ai/api-reference/feature-requests/submit-or-update-the-current-users-interest-in-a-feature-request-target.md)\n- [List admin access tokens (Admin only)](https://docs.near.ai/api-reference/admin/list-admin-access-tokens-admin-only.md): Retrieves a paginated list of all admin access tokens in the system. Only authenticated admins can access this endpoint.\n- [Create admin access token (Admin only)](https://docs.near.ai/api-reference/admin/create-admin-access-token-admin-only.md): Creates an access token for admin users with customizable expiration time, IP address, and user agent. This is typically used by billing services and other automated systems that need access to admin endpoints.\n- [Delete admin access token (Admin only)](https://docs.near.ai/api-reference/admin/delete-admin-access-token-admin-only.md): Revokes an admin access token by setting it as inactive. Only authenticated admins can perform this operation.\n- [List organization invitation email deliveries (Admin only)](https://docs.near.ai/api-reference/admin/list-organization-invitation-email-deliveries-admin-only.md): Returns delivery metadata for organization invitation emails without exposing invitation tokens.\n- [Resend a single organization invitation email (Admin only)](https://docs.near.ai/api-reference/admin/resend-a-single-organization-invitation-email-admin-only.md)\n- [List all models (Admin only)](https://docs.near.ai/api-reference/admin/list-all-models-admin-only.md): Returns a paginated list of all models in the system. By default, only active models are returned. Use `include_inactive=true` to also include disabled models.\n- [Batch upsert models metadata (Admin only)](https://docs.near.ai/api-reference/admin/batch-upsert-models-metadata-admin-only.md): Upserts (inserts or updates) pricing and metadata for one or more models. Only authenticated admins can perform this operation. The body should be an array of objects where each key is a model name and the value is the model data.\n- [Deprecate a model in favor of another (Admin only)](https://docs.near.ai/api-reference/admin/deprecate-a-model-in-favor-of-another-admin-only.md): Atomically marks `modelId` as deprecated and routes its traffic to `successorModelId`: 1. Adds `modelId` as an alias of `successorModelId`, so existing clients sending `model: \"<modelId>\"` keep working — the alias resolver rewrites the request-side `model` field to the successor before backend…\n- [List scheduled pricing changes (Admin only).](https://docs.near.ai/api-reference/admin/list-scheduled-pricing-changes-admin-only.md)\n- [Confirm a batch of scheduled pricing changes and notify affected admins (Admin only).](https://docs.near.ai/api-reference/admin/confirm-a-batch-of-scheduled-pricing-changes-and-notify-affected-admins-admin-only.md): Persists the schedule (the background scheduler applies each change at its effective date) and sends one consolidated email per affected recipient.\n- [Preview a batch of scheduled pricing changes without mutating state (Admin only).](https://docs.near.ai/api-reference/admin/preview-a-batch-of-scheduled-pricing-changes-without-mutating-state-admin-only.md)\n- [Cancel a pending scheduled pricing change (Admin only).](https://docs.near.ai/api-reference/admin/cancel-a-pending-scheduled-pricing-change-admin-only.md)\n- [Delete a model (Admin only)](https://docs.near.ai/api-reference/admin/delete-a-model-admin-only.md): Soft deletes a model by setting is_active to false. This preserves historical usage records that reference the model name while preventing it from being used in new requests.\n- [Confirm a planned model deprecation, update the catalog, and notify affected admins.](https://docs.near.ai/api-reference/admin/confirm-a-planned-model-deprecation-update-the-catalog-and-notify-affected-admins.md)\n- [Preview affected admins for a planned model deprecation (Admin only).](https://docs.near.ai/api-reference/admin/preview-affected-admins-for-a-planned-model-deprecation-admin-only.md)\n- [Get complete history for a model (Admin only)](https://docs.near.ai/api-reference/admin/get-complete-history-for-a-model-admin-only.md): Returns the complete history for a specific model, showing all changes over time including pricing, context length, display name, and description.\n- [Get a single organization by id (Admin only)](https://docs.near.ai/api-reference/admin/get-a-single-organization-by-id-admin-only.md): Returns one organization with its spend limit and usage. Only authenticated admins can perform this operation. Returns 404 if the organization does not exist or is inactive (consistent with the admin organizations list, which hides inactive orgs).\n- [Get organization concurrent request limit (Admin only)](https://docs.near.ai/api-reference/admin/get-organization-concurrent-request-limit-admin-only.md): Returns the current concurrent request limit for an organization. If no custom limit is set, returns null for concurrent_limit and the default (64) for effective_limit.\n- [Update organization concurrent request limit (Admin only)](https://docs.near.ai/api-reference/admin/update-organization-concurrent-request-limit-admin-only.md): Updates the maximum concurrent requests allowed per model for an organization. Set to null to use the default limit (64). Changes take effect within 5 minutes due to caching.\n- [Update organization limits (Admin only)](https://docs.near.ai/api-reference/admin/update-organization-limits-admin-only.md): Updates spending limits for a specific organization. This endpoint is typically called by a billing service with an admin API key when a customer makes a purchase.\n- [Get limits history for an organization (Admin only)](https://docs.near.ai/api-reference/admin/get-limits-history-for-an-organization-admin-only.md): Returns the complete limits history for a specific organization, showing all limits changes over time. Get limits history for an organization (Admin only)\n- [List members of a specific organization (Admin only)](https://docs.near.ai/api-reference/admin/list-members-of-a-specific-organization-admin-only.md): Returns the members of the given organization with full user details (email, last login, active status), consistent with `/v1/admin/users`. Only authenticated admins can perform this operation.\n- [Get organization metrics (Admin only)](https://docs.near.ai/api-reference/admin/get-organization-metrics-admin-only.md): Returns usage metrics for an organization including summary totals, and breakdowns by workspace, API key, and model.\n- [Get time series metrics for an organization (Admin only)](https://docs.near.ai/api-reference/admin/get-time-series-metrics-for-an-organization-admin-only.md): Returns daily/weekly/hourly aggregations for charting: requests, tokens, and cost per time period.\n- [Get admin organization staking farm state](https://docs.near.ai/api-reference/admin/get-admin-organization-staking-farm-state.md): Returns the staking farm source and last synced farm-credit state for any organization. Requires platform admin access.\n- [Sync admin organization staking farm credits](https://docs.near.ai/api-reference/admin/sync-admin-organization-staking-farm-credits.md): Refreshes staking farm reward units and derived credits for any linked organization. Requires platform admin access.\n- [Get organization balance (Admin only)](https://docs.near.ai/api-reference/admin/get-organization-balance-admin-only.md): Returns the current spending balance for an organization without requiring the caller to be a member of that organization. Intended for trusted automated billing services.\n- [Get the platform billing summary (Admin only)](https://docs.near.ai/api-reference/admin/get-the-platform-billing-summary-admin-only.md): Credit LIMITS (caps) and consumption — NOT payments/cash. Returns active paid/grant credit limits, total consumed, paying/granted org counts, and a breakdown by funding source. Real money-in lives in the billing service, not cloud-api.\n- [Get the platform infrastructure / fleet burn summary (Admin only)](https://docs.near.ai/api-reference/admin/get-the-platform-infrastructure-fleet-burn-summary-admin-only.md): Fetches the live host list, counts active/idle hosts, and computes the monthly/daily GPU burn rate from the configured cost-per-host. Degrades gracefully (stale=true) if the host inventory is unreachable.\n- [Get platform-wide metrics for admin dashboards (Admin only)](https://docs.near.ai/api-reference/admin/get-platform-wide-metrics-for-admin-dashboards-admin-only.md): Returns aggregated metrics across all organizations including: - Total users and organizations - Total requests and revenue - Top models by usage - Top organizations by spend\n- [Get platform-wide time series for admin dashboards (Admin only)](https://docs.near.ai/api-reference/admin/get-platform-wide-time-series-for-admin-dashboards-admin-only.md): Returns per-bucket requests, tokens, cost (paid/granted + verifiable/external splits), active organizations, and new signups for growth/mix trend charts.\n- [Get the per-model consumption ranking (Admin only)](https://docs.near.ai/api-reference/admin/get-the-per-model-consumption-ranking-admin-only.md): Models for the selected period ranked by consumed cost, with requests, tokens, unique orgs, verifiable flag, provider type, and latency. Paginated and filterable.\n- [Get the per-organization consumption ranking (Admin only)](https://docs.near.ai/api-reference/admin/get-the-per-organization-consumption-ranking-admin-only.md): Organizations with usage in the selected period ranked by consumed cost, with the verifiable/external split, requests, tokens, models used, a current paying flag, and last-usage timestamp. Paginated and filterable — full attribution of usage/spend per org.\n- [Create platform service (Admin only)](https://docs.near.ai/api-reference/admin/create-platform-service-admin-only.md)\n- [Update platform service (Admin only; display_name, description, cost_per_unit, is_active)](https://docs.near.ai/api-reference/admin/update-platform-service-admin-only;-display_name-description-cost_per_unit-is_active.md)\n- [List all registered users with pagination (Admin only)](https://docs.near.ai/api-reference/admin/list-all-registered-users-with-pagination-admin-only.md): Returns a paginated list of all users in the system. Only authenticated admins can perform this operation.\n\n## OpenAPI Specs\n\n- [openapi](/api-reference/openapi.json)\n\nThis documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.","tokens":8391,"crawled_at":1791194650633}
+{"id":10419,"url":"https://www.getfoundry.sh/help/troubleshooting","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Troubleshooting – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nTroubleshooting\n\nSolutions to common errors and issues.\n\nInstallation\n\nfoundryup: command not found\n\nThe Foundry bin directory isn't in your PATH. Add it:\n\n$ export PATH=\"$HOME/.foundry/bin:$PATH\"\n\n$ fish_add_path ~/.foundry/bin\n\nAdd this line to your shell config (~/.bashrc, ~/.zshrc, ~/.config/fish/config.fish, etc.) and restart your terminal.\n\nBuild fails with missing dependencies\n\nOn Linux, you may need build essentials:\n\n$ sudo apt-get install build-essential\n\n$ sudo dnf install gcc\n\n$ sudo pacman -S base-devel\n\nOn macOS, install Xcode command line tools:\n\n$ xcode-select --install\n\nCompilation\n\nError: Compiler version X does not satisfy the requirement\n\nYour contract requires a different Solidity version. Either:\n\nUpdate your foundry.toml:\n\n[profile.default]\nsolc_version = \"0.8.28\"\n\nOr use auto-detection (default behavior):\n\n[profile.default]\nauto_detect_solc = true\n\nError: Source not found\n\nThe compiler can't find an imported file. Check:\n\nRemappings — Run forge remappings to see current mappings\n\nDependencies — Run forge install to install missing dependencies\n\nPath — Verify the import path matches the file location\n\nAdd remappings in foundry.toml:\n\n[profile.default]\nremappings = [\n\"@openzeppelin/=lib/openzeppelin-contracts/\",\n]\n\nStack too deep\n\nThe compiler hit the EVM's 16 local variable limit. Quick fixes:\n\nUse structs to group variables\n\nExtract code into internal functions\n\nUse block scoping to limit variable lifetimes\n\nSee the Stack Too Deep guide for detailed solutions and why via-ir should be a last resort.\n\nTesting\n\nEvmError: Revert with no message\n\nThe transaction reverted without a reason string. Debug with:\n\n$ forge test --match-test test_Failing -vvvv\n\nCheck for:\n\nFailed require() without a message\n\nLow-level calls that returned false\n\nOut of gas\n\nEvmError: OutOfGas\n\nIncrease the gas limit:\n\n[profile.default]\ngas_limit = \"18446744073709551615\"\n\nOr check for infinite loops in your code.\n\nFuzz test finds edge case\n\nWhen fuzzing finds a failure, it shows the failing input:\n\n[FAIL. Reason: Overflow; counterexample: x=115792...]\n\nAdd the edge case as a unit test, then fix the bug.\n\nTests pass locally but fail in CI\n\nCommon causes:\n\nDifferent Solidity version — Pin the version in foundry.toml\n\nFork URL issues — Ensure CI has access to RPC endpoints\n\nRandomness in fuzzing — Use --fuzz-seed for reproducibility:\n\n$ forge test --fuzz-seed 12345\n\nForking\n\nError: Failed to fetch block\n\nThe RPC endpoint is unreachable or rate-limited. Try:\n\nCheck your internet connection\n\nUse a different RPC provider\n\nAdd retry configuration:\n\n[profile.default]\nrpc_retry_delay = 1000\nrpc_retry_backoff = 2\n\nFork tests are slow\n\nForked state is cached to disk by default, but the cache is only reused when the fork block is pinned:\n\n$ forge test --fork-url $RPC_URL --fork-block-number 18000000\n\nOr in foundry.toml:\n\n[profile.default]\nfork_block_number = 18000000\n\nThe cache is stored in ~/.foundry/cache/rpc/.\n\nError: Block not found\n\nThe specified block number doesn't exist or hasn't been indexed:\n\n# Use a known block or omit to use latest\n$ anvil --fork-url $RPC_URL --fork-block-number 18000000\n\nVerification\n\nError: Contract verification failed\n\nCommon issues:\n\nWrong compiler settings — Ensure verification uses same settings as deployment\n\nConstructor arguments — Provide them with --constructor-args:\n\n$ forge verify-contract $ADDRESS src/Token.sol:Token \\\n--constructor-args $(cast abi-encode \"constructor(string,string)\" \"Name\" \"SYM\") \\\n--etherscan-api-key $KEY\n\nOptimizer mismatch — Check optimizer and optimizer_runs match\n\nError: API rate limit exceeded\n\nWait and retry, or use a different Etherscan API key. Add delays:\n\n[etherscan]\nmainnet = { key = \"${ETHERSCAN_API_KEY}\", chain = 1 }\n\nScripts\n\nError: Script failed: insufficient funds\n\nThe deployer account doesn't have enough ETH. Fund it first or use a different account.\n\nScript runs but transactions aren't broadcast\n\nAdd --broadcast to actually send transactions:\n\n$ forge script script/Deploy.s.sol --broadcast --rpc-url $RPC_URL\n\nWithout --broadcast, the script only simulates.\n\nError: Nonce too low\n\nA transaction with this nonce was already mined. Possible causes:\n\nScript was partially executed before\n\nAccount was used elsewhere\n\nFix by letting Foundry fetch the correct nonce (default behavior) or specify:\n\n$ forge script script/Deploy.s.sol --broadcast --slow\n\nMemory and Performance\n\nError: Memory allocation failed\n\nLarge contracts or datasets can exhaust memory. Solutions:\n\nIncrease system memory\n\nSplit large tests into separate files\n\nReduce fuzz run count for local testing:\n\n[profile.default]\nfuzz.runs = 256\n\nCompilation is slow\n\nEnable the cache (on by default):\n\n[profile.default]\ncache = true\n\nUse --no-cache only when debugging cache issues.\n\nFor large projects, consider:\n\nSplitting into multiple packages\n\nUsing sparse checkout for dependencies\n\nGetting More Help\n\nIf your issue isn't listed here:\n\nCheck the Foundry GitHub issues\n\nSearch the Foundry Telegram\n\nAsk in the Foundry Discord\n\nIf you can reproduce the issue, include your forge --version and command output when opening an issue.\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":1305,"crawled_at":1791194661179}
+{"id":10420,"url":"https://www.metaplex.com/docs/smart-contracts/core/plugins/update-delegate","domain":"www.metaplex.com","chapter":"docs","title":"Update Delegate Plugin | Metaplex Core","text":"The Update Delegate Plugin allows you to grant update permissions to additional addresses. Useful when third parties need to modify Asset metadata without being the primary update authority.\nWhat You'll Learn\nAdd the Update Delegate plugin to Assets and Collections\nGrant update permissions to additional addresses\nUnderstand what additional delegates can and cannot do\nUpdate and manage the delegates list\nAdd and remove Assets from Collections as a delegate\n\nSummary\nThe Update Delegate is an Authority Managed plugin that allows the update authority to grant update permissions to other addresses. Additional delegates can modify most Asset data — including collection membership — but cannot change core authority settings.\nGrant update permissions to third parties\nAdd multiple additional delegates\nWorks with both Assets and Collections\nDelegates with Collection authority can add/remove Assets from Collections\nDelegates cannot modify the root update authority\nOut of Scope\nPermanent update delegation, owner-level permissions (this is authority managed), and Token Metadata update authority (different system).\nQuick Start\nJump to: Add to Asset · Update Delegates · Collection · Collection Membership\nAdd the Update Delegate plugin with the delegate address\nOptionally add additional delegates\nDelegates can now update Asset metadata\nWhen to Use Update Delegate\nScenarioSolution\nThird-party needs to update metadata\n✅ Update Delegate\n\nGame program needs to modify stats\n✅ Update Delegate (delegate to program)\n\nMultiple team members need update access\n✅ Additional Delegates\n\nPermanent irrevocable update access\n❌ Not supported (use multisig authority)\n\nOwner should control updates\n❌ Use default authority\n\nUse Update Delegate when you need to grant update permissions to programs or third parties without transferring the root authority.\n\nCommon Use Cases\nThird-party services: Allow platforms to update metadata on your behalf\nGame programs: Grant your game program authority to modify Asset attributes\nTeam collaboration: Multiple team members can update without sharing keys\nMarketplaces: Allow marketplaces to update listing-related metadata\nDynamic content: Services that automatically update Asset data\nWorks With\n\nMPL Core Asset\n✅\n\nMPL Core Collection\n✅\n\nArguments\n\nadditionalDelegates\npublickey[]\n\nadditionalDelegates\nAdditional delegates allow you to add more than one delegate to the updateDelegate plugin. Additional delegates can do everything that the update authority can do except:\nadd or change the additional delegates array (apart from remove themselves).\nchange the plugin authority of the updateAuthority plugin.\nchange the root update authority of the collection.\nAdding the Update Delegate Plugin to an Asset\nAdding a Update Delegate Plugin to an MPL Core Asset\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { addPlugin } from '@metaplex-foundation/mpl-core'\n\nconst assetAddress = publicKey('11111111111111111111111111111111')\n\nconst delegate = publicKey('22222222222222222222222222222222')\n\nawait addPlugin(umi, {\n\nasset: assetAddress,\n\nplugin: {\n\ntype: 'UpdateDelegate',\n\nauthority: { type: 'Address', address: delegate },\n\nadditionalDelegates: [],\n\n},\n\n}).sendAndConfirm(umi)\n\nUpdating the Update Delegate Plugin\nThe Update Delegate Plugin can be updated to modify the list of additional delegates or change the plugin authority.\nUpdating Update Delegate Plugin on Asset\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { updatePlugin } from '@metaplex-foundation/mpl-core'\n\nconst assetAddress = publicKey('11111111111111111111111111111111')\n\nconst newDelegate = publicKey('33333333333333333333333333333333')\n\nconst existingDelegate = publicKey('22222222222222222222222222222222')\n\nawait updatePlugin(umi, {\n\nasset: assetAddress,\n\nplugin: {\n\ntype: 'UpdateDelegate',\n\nadditionalDelegates: [existingDelegate, newDelegate], // Add or remove delegates\n\n},\n\n}).sendAndConfirm(umi)\n\nUpdating Update Delegate Plugin on Collection\nUpdating Update Delegate Plugin on Collection\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { updateCollectionPlugin } from '@metaplex-foundation/mpl-core'\n\nconst collectionAddress = publicKey('11111111111111111111111111111111')\n\nconst delegate1 = publicKey('22222222222222222222222222222222')\n\nconst delegate2 = publicKey('33333333333333333333333333333333')\n\nawait updateCollectionPlugin(umi, {\n\ncollection: collectionAddress,\n\nplugin: {\n\ntype: 'UpdateDelegate',\n\nadditionalDelegates: [delegate1, delegate2], // Updated delegates list\n\n},\n\n}).sendAndConfirm(umi)\n\nManaging Collection Membership as an Update Delegate\nThe UpdateDelegate plugin on a Collection grants authority to add and remove Assets from that Collection without the root update authority's signature. This is the primary pattern for programs and services that manage collection membership autonomously — for example, a game server that assigns Assets to guilds, or a launchpad that mints directly into a collection.\nRemove any Asset from the Collection — Collection UpdateDelegate alone is sufficient.\nAdd an Asset to the Collection — Collection UpdateDelegate plus authority over the Asset (as its update authority, or via the Asset's own UpdateDelegate plugin).\nIt is the Collection's UpdateDelegate plugin that controls membership, not the Asset's. A delegate on the Asset alone cannot add or remove it from a Collection — collection-side authority is required.\n\nAdding an Asset to a Collection as a Collection Update Delegate\nThe signer must be listed in the Collection's UpdateDelegate additionalDelegates array, and must also hold authority over the Asset — either as the Asset's update authority (e.g. the program created the Asset) or as a delegate listed in the Asset's UpdateDelegate plugin.\n\n1import { publicKey } from '@metaplex-foundation/umi'\n\n2import {\n\n3 update,\n\n4 fetchAsset,\n\n5 updateAuthority,\n\n6} from '@metaplex-foundation/mpl-core'\n\n7\n\n8const assetId = publicKey('11111111111111111111111111111111')\n\n9const collectionId = publicKey('22222222222222222222222222222222')\n\n10\n\n11const asset = await fetchAsset(umi, assetId)\n\n12\n\n13// umi.identity must be in the Collection's UpdateDelegate additionalDelegates\n\n14// AND hold the Asset's update authority (or be in the Asset's UpdateDelegate additionalDelegates)\n\n15await update(umi, {\n\n16 asset,\n\n17 newCollection: collectionId,\n\n18 newUpdateAuthority: updateAuthority('Collection', [collectionId]),\n\n19}).sendAndConfirm(umi)\n\n20\n\n21console.log('Asset added to collection')\n\n1use mpl_core::{instructions::UpdateV2Builder, types::UpdateAuthority};\n\n2use solana_sdk::{pubkey::Pubkey, signer::Signer};\n\n3\n\n4let asset = Pubkey::from_str(\"AssetAddressHere...\").unwrap();\n\n5let collection = Pubkey::from_str(\"CollectionAddressHere...\").unwrap();\n\n6\n\n7// Signer must be in the Collection's UpdateDelegate additionalDelegates\n\n8// AND hold the Asset's update authority (or be in its UpdateDelegate additionalDelegates)\n\n9let update_ix = UpdateV2Builder::new()\n\n10 .asset(asset)\n\n11 .new_collection(Some(collection))\n\n12 .payer(delegate.pubkey())\n\n13 .authority(Some(delegate.pubkey()))\n\n14 .new_update_authority(UpdateAuthority::Collection(collection))\n\n15 .instruction();\n\n16\n\n17println!(\"Asset added to collection\");\n\nRemoving an Asset from a Collection as a Collection Update Delegate\nThe signer only needs to be listed in the Collection's UpdateDelegate additionalDelegates array. Asset-level authority is not required to remove an Asset.\nFetch the asset and its current collection, then call update. The authority parameter identifies the Collection delegate explicitly.\n\n1import { publicKey } from '@metaplex-foundation/umi'\n\n2import {\n\n3 update,\n\n4 fetchAsset,\n\n5 fetchCollection,\n\n6 collectionAddress,\n\n7 updateAuthority,\n\n8} from '@metaplex-foundation/mpl-core'\n\n9\n\n10const assetId = publicKey('11111111111111111111111111111111')\n\n11\n\n12const asset = await fetchAsset(umi, assetId)\n\n13\n\n14const currentCollectionId = collectionAddress(asset)\n\n15if (!currentCollectionId) {\n\n16 throw new Error('Asset does not belong to a collection')\n\n17}\n\n18const collection = await fetchCollection(umi, currentCollectionId)\n\n19\n\n20// collectionDelegate only needs to be in the Collection's UpdateDelegate additionalDelegates\n\n21const collectionDelegate = umi.identity // replace with your delegate signer if different\n\n22await update(umi, {\n\n23 asset,\n\n24 collection,\n\n25 newUpdateAuthority: updateAuthority('Address', [umi.identity.publicKey]),\n\n26 authority: collectionDelegate,\n\n27}).sendAndConfirm(umi)\n\n28\n\n29console.log('Asset removed from collection')\n\n1use mpl_core::{instructions::UpdateV2Builder, types::UpdateAuthority};\n\n2use solana_sdk::{pubkey::Pubkey, signer::Signer};\n\n3\n\n4let asset = Pubkey::from_str(\"AssetAddressHere...\").unwrap();\n\n5let collection = Pubkey::from_str(\"CollectionAddressHere...\").unwrap();\n\n6let new_authority = Pubkey::from_str(\"NewAuthorityHere...\").unwrap();\n\n7\n\n8// Signer only needs to be in the Collection's UpdateDelegate additionalDelegates\n\n9let update_ix = UpdateV2Builder::new()\n\n10 .asset(asset)\n\n11 .collection(Some(collection))\n\n12 .payer(delegate.pubkey())\n\n13 .authority(Some(delegate.pubkey()))\n\n14 .new_update_authority(UpdateAuthority::Address(new_authority))\n\n15 .instruction();\n\n16\n\n17println!(\"Asset removed from collection\");\n\nCommon Errors\nAuthority mismatch\nOnly the update authority (or existing plugin authority) can add/modify the Update Delegate plugin.\nCannot modify root authority\nAdditional delegates cannot change the root update authority or modify the additional delegates list (except removing themselves).\nNotes\nAuthority Managed: update authority can add without owner signature\nAdditional delegates have almost full update permissions over the Asset or Collection they are delegated on\nA Collection UpdateDelegate can remove any Asset from the Collection, and add Assets it also has authority over\nDelegates cannot change the root update authority\nDelegates cannot modify the additional delegates list (except remove themselves)\nWorks on both Assets and Collections\nQuick Reference\nAsset Update Delegate Permissions\nActionAllowed?\nUpdate name/URI\n✅\n\nAdd plugins\n✅\n\nUpdate plugins\n✅\n\nRemove plugins\n✅\n\nChange root update authority\n❌\n\nModify additional delegates\n❌ (except self-removal)\n\nChange plugin authority\n❌\n\nCollection Update Delegate Permissions\nActionAllowed?\nRemove any Asset from the Collection\n✅\n\nAdd an Asset (you have authority over) to the Collection\n✅\n\nUpdate Collection metadata\n✅\n\nUpdate Collection plugins\n✅\n\nChange the Collection's root update authority\n❌\n\nModify the Collection's additional delegates\n❌ (except self-removal)\n\nFAQ\nWhat can additional delegates do?\nAlmost everything the update authority can do: update metadata, add/remove plugins, etc. They cannot change the root update authority, modify the additional delegates list, or change the Update Delegate plugin authority.\nCan additional delegates add more delegates?\nNo. Only the root update authority (or plugin authority) can add or remove additional delegates.\nHow do I remove myself as an additional delegate?\nAdditional delegates can remove themselves from the list by updating the plugin without their address in the additionalDelegates array.\nIs there a limit to additional delegates?\nThere's no hard limit, but more delegates increase account size and rent. Keep the list reasonable.\nDoes Update Delegate work on Collections?\nYes. Adding Update Delegate to a Collection allows delegates to update collection metadata and collection-level plugins.\nCan a Collection Update Delegate add or remove Assets from a Collection?\nYes. A delegate listed in the Collection's UpdateDelegate plugin can remove any Asset from the Collection, and can add Assets they have authority over — either as the Asset's update authority (e.g. the delegate created the Asset) or as a delegate listed in the Asset's own UpdateDelegate plugin. See Managing Collection Membership as an Update Delegate.\nDoes the Collection UpdateDelegate need authority over individual Assets to remove them?\nNo. Collection-level delegate authority is sufficient to remove any Asset from the Collection. Asset-level authority is only required when adding an Asset (since the Asset must also accept the change).\nRelated Plugins\nAttributes - Store on-chain data that delegates can update\nImmutableMetadata - Make metadata unchangeable (overrides delegates)\nAddBlocker - Prevent delegates from adding new plugins\nGlossary\nTermDefinition\nUpdate Delegate\nAuthority Managed plugin for granting update permissions\n\nAdditional Delegates\nExtra addresses with update permissions\n\nAuthority Managed\nPlugin type controlled by update authority\n\nRoot Update Authority\nThe primary update authority of the Asset/Collection","tokens":3188,"crawled_at":1791194695427}
+{"id":10421,"url":"https://gov.uniswap.org/t/temp-check-protocol-fee-expansion-three-more-chains/26108","domain":"gov.uniswap.org","chapter":"governance_daos","title":"[Temp Check] Protocol Fee Expansion: Three More Chains - Temperature Check - Uniswap Governance","text":"[Temp Check] Protocol Fee Expansion: Three More Chains\n\nTemperature Check\n\neek637\n\nMay 16, 2026, 5:20pm\n\n1\n\nThis proposal continues the protocol fee rollout, following proposals #93, #94, and #95. It uses the expedited governance process approved in UNIfication, where fee parameter update proposals can bypass the RFC stage and go directly to a five-day Snapshot followed by an onchain vote.\n\nSince protocol fees went live on Ethereum mainnet in late December, the rollout has extended to nine additional chains (Arbitrum, Base, OP Mainnet, Soneium, X Layer, Worldchain, and Zora). The burn system is working as designed, with fees accumulating in TokenJars across chains. From there, searchers claim them in exchange for burning UNI by bridging it back to mainnet and sending it to the burn address.\n\nThis proposal:\n\nExtends the infrastructure for collecting and burning protocol fees to BNB Chain and Polygon\n\nEnables v2 and v3 protocol fees on these chains\n\nCompletes Celo’s fee activation through a corrected cross-chain governance path, which was approved in a previous proposal but did not execute due to a configuration error\n\nImplementation Details\n\nFees on each chain will be routed to the TokenJar on that respective chain. UNI burned on these chains is bridged back to Ethereum mainnet and sent to 0xdead.\n\nCelo uses the same architecture as other OP-stack chains. On BNB and Polygon, we make use of Wormhole’s Native Token Transfer (NTT) mechanism for multichain token management. This post will be updated early the week of May 18, 2026 with links to the repository containing these contracts and a full description of our implementation.\n\nProtocol fee levels are the same on all other chains where fees are live, see breakdown here.\n\nProposal Spec\n\nIf passed, this proposal will execute three actions: one each for Celo, BNB Chain, and Polygon. Each action contains multiple inner calls.\n\nCelo\n\nThis action sets the fee collector of UniswapV2Factory to TokenJar, transfers ownership of UniswapV2Factory and PoolManager to Optimism CrossChainAccount, and transfers ownership of UniswapV3Factory to V3OpenFeeAdapter.\n\nRELEVANT ADDRESSES:\n\nName\nNetwork\nAddress\nDescription\n\nV2_FACTORY\n\nCelo\n\n0x114A43DF6C5f54EBB8A9d70Cd1951D3dD68004c7\n\nUniswap V2 Factory\n\nV3_FACTORY\n\nCelo\n\n0xAfE208a311B21f13EF87E33A90049fC17A7acDEc\n\nUniswap V3 Factory\n\nV4_POOL_MANAGER\n\nCelo\n\n0x288dc841A52FCA2707c6947B3A777c5E56cd87BC\n\nUniswap V4 Pool Manager\n\nTOKEN_JAR\n\nCelo\n\n0x190c22c5085640D1cB60CeC88a4F736Acb59bb6B\n\nFee Collector\n\nV3_OPEN_FEE_ADAPTER\n\nCelo\n\n0xB9952C01830306ea2fAAe1505f6539BD260Bfc48\n\nUniswap V3 Fee Adapter\n\nUNISWAP_WORMHOLE_MESSAGE_RECEIVER\n\nCelo\n\n0x0Eb863541278308c3A64F8E908BC646e27BFD071\n\nGovernance Owned Wormhole Receiver\n\nCROSS_CHAIN_ACCOUNT\n\nCelo\n\n0x044aAF330d7fD6AE683EEc5c1C1d1fFf5196B6b7\n\nGovernance-owned OP Bridge Receiver\n\nWORMHOLE_SENDER\n\nEthereum\n\n0xf5F4496219F31CDCBa6130B5402873624585615a\n\nWormhole Sender\n\nWORMHOLE_SENDER.sendMessage(targets, values, datas, UNISWAP_WORMHOLE_MESSAGE_RECEIVER, CELO_CHAIN_ID)\n\nencodes:\n\nV2_FACTORY.setFeeTo(TOKEN_JAR)\n\nV2_FACTORY.setFeeToSetter(CROSS_CHAIN_ACCOUNT)\n\nV3_FACTORY.setOwner(V3_OPEN_FEE_ADAPTER)\n\nV4_POOL_MANAGER.transferOwnership(CROSS_CHAIN_ACCOUNT)\n\nBNB Chain\n\nThis action sets the fee collector of UniswapV2Factory to TokenJar and transfers ownership of UniswapV3Factory to V3OpenFeeAdapter.\n\nRELEVANT ADDRESSES:\n\nName\nNetwork\nAddress\nDescription\n\nV2_FACTORY\n\nBNB Chain\n\n0x8909Dc15e40173Ff4699343b6eB8132c65e18eC6\n\nUniswap V2 Factory\n\nV3_FACTORY\n\nBNB Chain\n\n0xdB1d10011AD0Ff90774D0C6Bb92e5C5c8b4461F7\n\nUniswap V3 Factory\n\nUNISWAP_WORMHOLE_MESSAGE_RECEIVER\n\nBNB Chain\n\n0x341c1511141022cf8eE20824Ae0fFA3491F1302b\n\nGovernance Owned Wormhole Receiver\n\nTOKEN_JAR\n\nBNB Chain\n\n0xc6Ae6373CEcc9e595A6C8b9fe581925a8c84f70A\n\nFee Collector\n\nV3_OPEN_FEE_ADAPTER\n\nBNB Chain\n\n0x3F07F08b45912dCd6691C5B9412975D5113B2910\n\nUniswap V3 Fee Adapter\n\nWORMHOLE_SENDER\n\nEthereum\n\n0xf5F4496219F31CDCBa6130B5402873624585615a\n\nWormhole Sender\n\nWORMHOLE_SENDER.sendMessage(targets, values, datas, UNISWAP_WORMHOLE_MESSAGE_RECEIVER, BNB_CHAIN_ID)\n\nencodes:\n\nV2_FACTORY.setFeeTo(TOKEN_JAR)\n\nV3_FACTORY.setOwner(V3_OPEN_FEE_ADAPTER)\n\nPolygon\n\nThis action sets the fee collector of UniswapV2Factory to TokenJar and transfers ownership of UniswapV3Factory to V3OpenFeeAdapter.\n\nRELEVANT ADDRESSES:\n\nName\nNetwork\nAddress\nDescription\n\nV2_FACTORY\n\nPolygon\n\n0x9e5A52f57b3038F1B8EeE45F28b3C1967e22799C\n\nUniswap V2 Factory\n\nV3_FACTORY\n\nPolygon\n\n0x1F98431c8aD98523631AE4a59f267346ea31F984\n\nUniswap V3 Factory\n\nETHEREUM_PROXY\n\nPolygon\n\n0x8a1B966aC46F42275860f905dbC75EfBfDC12374\n\nGovernance Owned FxChild Receiver\n\nTOKEN_JAR\n\nPolygon\n\n0xc6Ae6373CEcc9e595A6C8b9fe581925a8c84f70A\n\nFee Collector\n\nV3_OPEN_FEE_ADAPTER\n\nPolygon\n\n0x3F07F08b45912dCd6691C5B9412975D5113B2910\n\nUniswap V3 Fee Adapter\n\nPOLYGON_FX_ROOT\n\nEthereum\n\n0xfe5e5D361b2ad62c541bAb87C45a0B9B018389a2\n\nPolygon’s Sender (on Ethereum)\n\nPOLYGON_FX_ROOT.sendMessageToChild(ETHEREUM_PROXY, abi.encode(targets, datas, values))\n\nencodes:\n\nV2_FACTORY.setFeeTo(TOKEN_JAR)\n\nV3_FACTORY.setOwner(V3_OPEN_FEE_ADAPTER)\n\nAbel189\n\nMay 18, 2026, 1:51pm\n\n2\n\nThis seems like a coherent next step for Uniswap’s fee rollout strategy. Extending fee collection and UNI burn infrastructure gradually across additional chains makes sense given Uniswap’s increasingly multi-chain reality.\n\nI also appreciate the incremental approach rather than a one-shot activation everywhere at once. The main aspect worth monitoring over time is probably the growing cross-chain governance and messaging complexity (Wormhole, adapters, bridge infrastructure, etc.), especially as more chains are added.\n\nManugotsuka\n\nMay 20, 2026, 2:30pm\n\n3\n\nThe following reflects the views of L2BEAT’s governance team, composed of @kaereste and @Manugotsuka, and it’s based on their combined research, fact-checking, and ideation.\n\nWe voted FOR\n\nBefore voting, we asked our Research Team to independently verify the implementation, deployed contracts, and expected governance payloads associated with this proposal.\n\nOur Research Team reviewed prop-4 in the Uniswap protocol-fees repository PR #130 and pinned the review to commit 83df8d7f. They rebuilt the commit and compared the deployed runtime bytecode on Celo, BNB, and Polygon against the build artifacts. All 10 relevant contracts matched after accounting for compiler metadata and immutable slots, and the immutable values read on-chain matched the expected values from Constants.sol.\n\nThe team also reconstructed the three proposal action payloads and produced the expected keccak256(datas[i]) hashes that should match once the on-chain proposal is submitted:\n\nCelo: 0xda4f141e0d1d27bfc513573f5a8e8e6fefedad7b6769d6f5a037cc0fd706424d\n\nBNB: 0x12a4d5c2bf9d982394d1716a301919870b2d000ea866216c0fd83082ac617e92\n\nPolygon: 0x1bee6e3efc6611d85f0810c271daff29a6f9b9a38466993860138a699166b34f\n\nBased on the continuity with the previously approved framework, the unchanged fee structure, and the independent verification performed by our Research Team, we are comfortable supporting this proposal.\n\nWe also believe the protocol would benefit from a more comprehensive post-UNIfication report covering operational and economic metrics across deployed chains. As the fee framework continues to expand, providing delegates with clearer visibility into protocol revenue, burn activity, liquidity impact, and cross-chain operational performance would improve governance oversight and help inform future expansion proposals.\n\n4 Likes\n\nAxia\n\nMay 20, 2026, 9:42pm\n\n4\n\nVoted FOR this proposal to continue the protocol fee rollout by expanding fee collection and UNI burn infrastructure to Polygon and BNB Chain, while completing Celo’s activation through the corrected cross-chain governance path.\n\nThis is a logical continuation of UNIfication and the prior protocol fee expansion votes. The burn mechanism is live and working: fees accumulate in TokenJars across chains, searchers call release(), UNI is burned, and TokenJar assets are distributed. Since the first release on Dec. 29, 2025, the system has already produced meaningful burn activity across Ethereum, Base, Arbitrum, Unichain, and OP Mainnet.\n\nFor this vote, I also created an updated graphic to make the mechanism easier to understand. The first graphic explains the original protocol fee collection flow and first UNI burn. The new graphic summarizes verified burn counts from Dec. 29, 2025 through May 20, 2026, showing how the Firepit/Releaser system has continued operating across active chains.\n\nExpanding to Polygon and BNB Chain makes sense given Uniswap’s multi-chain footprint, while Celo should be completed because governance already approved its inclusion and the prior execution issue was a configuration problem rather than a policy rejection.\n\nAs more chains are added, delegates should continue monitoring cross-chain messaging complexity, burn activity, and protocol revenue by chain. But based on the continuity with the existing fee framework, unchanged fee levels, and the fact that the burn system is already operating as designed, Axia supports this proposal.\n\nFirst Burn\n\nTotal Burns\n\nSee more here: https://rikagoldberg.xyz/work-samples\n\n3 Likes\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[Temp Check] Protocol Fee Expansion: Eight More Chains and Remaining Mainnet v3 Pools\n\nTemperature Check\n\n7\n\n1247\n\nMarch 3, 2026\n\n[Temp Check] Protocol Fee Expansion: Robinhood Chain\n\nTemperature Check\n\n3\n\n984\n\nJuly 22, 2026\n\n[Temp Check] Protocol Fee Expansion: Arc\n\nTemperature Check\n\n5\n\n463\n\nOctober 1, 2026\n\nAxia Network Delegate Platform\n\nDelegation Pitch\n\n11\n\n333\n\nOctober 3, 2026\n\nUNIfication Proposal\n\nRequests for Comment\n\n47\n\n24766\n\nJune 29, 2026","tokens":2430,"crawled_at":1791194694792}
+{"id":10422,"url":"https://docs.sui.io/sui-stack/zklogin-integration/zklogin","domain":"docs.sui.io","chapter":"layer1_layer2","title":"zkLogin Technical Reference | Sui Documentation","text":"This page is the technical reference for zkLoginzkLoginA Sui primitive that allows you to send transactions using an OAuth credential.. For a conceptual overview, see zkLogin. For implementation steps, see the Integration Guide.\n\nOpenID providers​\n\nThe following table lists the OpenID providers that can support zkLoginzkLoginA Sui primitive that allows you to send transactions using an OAuth credential. or are currently being reviewed to determine whether they can support zkLogin.\n\nProviderCan support?DevnetDevnetFor developing and testing new features.TestnetTestnetStaging network for testing changes before production deployment.MainnetMainnetProduction network for live transactions and real-value assets.\nFacebook\nYes\nYes\nYes\nYes\n\nGoogle\nYes\nYes\nYes\nYes\n\nTwitch\nYes\nYes\nYes\nYes\n\nApple\nYes\nYes\nYes\nYes\n\nSlack\nYes\nYes\nNo\nNo\n\nKakao\nYes\nYes\nNo\nNo\n\nMicrosoft\nYes\nYes\nNo\nNo\n\nAWS (Tenant)*\nYes\nYes\nYes\nYes\n\nKarrier One\nYes\nYes\nYes\nYes\n\nCredenza3\nYes\nYes\nYes\nYes\n\nRedBull\nUnder review\nNo\nNo\nNo\n\nAmazon\nUnder review\nNo\nNo\nNo\n\nWeChat\nUnder review\nNo\nNo\nNo\n\nAuth0\nUnder review\nNo\nNo\nNo\n\nOkta\nUnder review\nNo\nNo\nNo\n\nSui supports AWS (Tenant) but the provider is enabled per tenant. Contact us for more information.\n\nEntities​\n\nThe zkLogin protocol involves three entities beyond the user:\n\nApplication frontend: The wallet or frontend that stores the ephemeral private key, directs the user through the OAuth login flow, and creates and signs zkLogin transactions.\n\nSalt service: A backend service that returns a consistent, unique salt for each user. See Salt management for strategies.\n\nProving service: A backend service that generates zero-knowledge proofs from the JWT, JWT randomness, user salt, and max epochEpochA period of time defined by the network.. The proof is submitted onchain with the ephemeral signature.\n\nTerminology​\n\nThe following terms come from the OpenID Connect specification.\n\nOpenID provider (OP)​\n\nAn OAuth 2.0 authorization server that authenticates an end-user and provides claims to a relying party. Identified by the iss field in the JWT payload. See the table of supported providers.\n\nRelying party (RP) or client​\n\nAn OAuth 2.0 client application that requires end-user authentication. Assigned by an OP when you register your application. Identified by the aud field in the JWT payload. This is your zkLogin-enabled wallet or application.\n\nSubject identifier (sub)​\n\nA locally unique identifier for the end user within the issuer. zkLogin uses sub as the key claim to derive the user's addressAddressA unique, anonymous identity on a blockchain network..\n\nJSON Web Key (JWK)​\n\nA JSON data structure representing an OP's public keys. A public endpoint (for example, https://www.googleapis.com/oauth2/v3/certs) provides the keys corresponding to each kid. In Sui, validators call JWK endpoints independently, and the latest JWKs for all supported providers are updated during protocol upgrades. Correctness is guaranteed by quorumQuorumA set of validators whose combined voting power is greater than 2/3 of the total. (2f+1) of validatorValidatorResponsible for executing tasks like staking, gas price references, and tallying rules. stake.\n\nJSON Web Token (JWT)​\n\nThe token returned in the redirect URI after the OAuth login flow (https://redirect.com?id_token=$JWT_TOKEN). A JWT contains a header, payload, and signature. The signature is an RSA signature verified against jwt_message = header + . + payload using the JWK identified by kid.\n\nHeader fields:\n\nNameExample ValueUsage\nalg\nRS256\nzkLogin only supports RS256 (RSA + SHA-256).\n\nkid\nc3afe7a9bda46bae6ef97e46c95cda48912e5979\nIdentifies the JWK that should be used to verify the JWT.\n\ntyp\nJWT\nzkLogin only supports JWT.\n\nPayload fields:\n\nNameExample ValueUsage\niss\nhttps://accounts.google.com\nUnique identifier for the OAuth provider.\n\naud\n575519200000-msop9ep45u2uo98hapqmngv8d8000000.apps.googleusercontent.com\nUnique identifier for the relying party (your app), assigned by the OAuth provider.\n\nnonce\nhTPpgF7XAKbW37rEUS6pEVZqmoI\nSet by the relying party. zkLogin requires this to be the hash of the ephemeral public key, expiry, and randomness.\n\nsub\n110463452167303000000\nUnique identifier for the user.\n\nFor zkLogin transactions, the iat and exp JWT timestamp claims are not used. Expiry is controlled by the nonce, which embeds max_epoch.\n\nKey claim​\n\nThe claim used to derive the address. zkLogin currently supports only sub because the OpenID specification mandates that providers do not change this identifier.\n\nNotations​\n\nSymbolDescription\n(eph_sk, eph_pk)\nEphemeral private and public key pair. Same signing mechanism as traditional transactions, but short-lived (one session). The ephemeral public key is used to compute the nonce.\n\nnonce\nToBase64URL(Poseidon_BN254([ext_eph_pk_bigint / 2^128, ext_eph_pk_bigint % 2^128, max_epoch, jwt_randomness]).to_bytes()[len - 20..]) where ext_eph_pk_bigint is the BigInt representation of ext_eph_pk.\n\next_eph_pk\nByte representation of the ephemeral public key: flag || eph_pk. Size varies by signature scheme (see Signatures).\n\nuser_salt\nA value that unlinks the OAuth identifier from the onchain address.\n\nmax_epoch\nThe epoch at which the ephemeral key expires (u64).\n\nkc_name\nKey claim name, for example sub.\n\nkc_value\nKey claim value, for example 110463452167303000000.\n\nhashBytesToField(str, maxLen)\nHashes an ASCII string to a BN254 field element using Poseidon hash.\n\nHow zkLogin works​\n\nThe protocol works in three stages:\n\nA JWT is a signed payload from an OAuth provider that includes a user-defined nonce. zkLogin uses the OpenID Connect flow by setting the nonce to a hash of the ephemeral public key, a randomness value, and an expiry epoch.\n\nThe wallet stores an ephemeral key pair. The ephemeral private key signs transactions for a short session. A Groth16 zero-knowledge proof generated from the JWT conceals sensitive fields.\n\nThe transactionTransactionA number of commands that execute on inputs to define the result of the transaction. is submitted onchain with the ephemeral signature and zero-knowledge proof. Validators verify both before executing.\n\nThe zkLogin address is derived from sub (user identifier), iss (provider), aud (application), and user_salt, not from a public key.\n\nStep 0: The Groth16 zkSNARK requires a common reference string (CRS). A ceremony generates the CRS, producing the proving key (for the proving service) and verifying key (for validators).\n\nSteps 1–3: An ephemeral key pair (eph_sk, eph_pk) is generated. The public key, expiry (max_epoch), and randomness (jwt_randomness) are embedded in the nonce. The user logs in with an OpenID provider, and the JWT appears in the redirect URL.\n\nSteps 4–5: The application sends the JWT to a salt service, which returns the unique user_salt based on iss, aud, and sub.\n\nSteps 6–7: The JWT, user salt, ephemeral public key, randomness, and key claim name (sub) are sent to the proving service. The proof confirms:\n\nThe nonce is derived correctly.\n\nThe key claim value matches the JWT.\n\nThe RSA signature from the provider is valid.\n\nThe address is consistent with the key claim and salt.\n\nStep 8: The application computes the user's address from iss, aud, sub, and user_salt.\n\nSteps 9–10: The transaction is signed with the ephemeral private key and submitted with the ephemeral signature, zero-knowledge proof, and other inputs. Validators verify the proof against the provider's JWKs (stored by consensusConsensusThe process by which the majority of nodes agree on the current state of the network) and the ephemeral signature.\n\nAddress definition​\n\nThe address is computed from:\n\nzk_login_flag = 0x05: domain separator for zkLogin addresses.\n\nkc_name_F = hashBytesToField(kc_name, maxKCNameLen): key claim name (for example, sub) mapped to a BN254 field element.\n\nkc_value_F = hashBytesToField(kc_value, maxKCValueLen): key claim value mapped to a field element.\n\naud_F = hashBytesToField(aud, maxAudValueLen): relying party identifier.\n\niss: OpenID provider identifier.\n\nuser_salt: value that unlinks the OAuth identifier from the address.\n\nThe final address:\n\naddr_seed = Poseidon_BN254(kc_name_F, kc_value_F, aud_F, Poseidon_BN254(user_salt))\nzk_login_address = Blake2b_256(zk_login_flag, iss_L, iss, addr_seed)\n\nAddress and session lifetime​\n\nThe address is permanent. It does not change or expire as long as sub, iss, aud, and user_salt remain the same.\n\nThe ephemeral key pair and max_epoch control how long a single login session can authorize transactions. When the epoch passes max_epoch, the user logs in again, generates a new ephemeral key pair and zero-knowledge proof, and continues using the same address.\n\nLogging in with a different OAuth provider or application produces a different address (different iss or aud). Using a different user_salt also produces a different address.\n\nCeremony​\n\nzkLogin uses Groth16 zkSNARKs for proof generation. Groth16 requires a computation-specific common reference string (CRS) generated through a trusted setup ceremony. The security model requires that at least one participant in the ceremony acted honestly, generated strong entropy, and discarded it.\n\nThe Sui zkLogin ceremony was a cryptographic multi-party computation (MPC) following the MMORPG protocol by Bowe, Gabizon, and Miers. It ran September 12–18, 2023, with 111 contributions (82 browser, 29 Docker) from participants with diverse backgrounds: Sui validators, cryptographers, Web3 experts, academics, and business leaders.\n\nClick to openCeremony detailsThe protocol proceeds in two phases:\n\nPhase 1 (circuit-agnostic): Adopted from the community-contributed perpetual powers of tau, specifically challenge #0081 (80 community contributions). The Drand random beacon at epoch #3298000 was applied to remove bias.\n\nPhase 2 (zkLogin-circuit-specific): 111 contributions. Participants could contribute through a browser (snarkjs) or Docker (Kobi's implementation), providing software diversity. The Drand random beacon at epoch #3320606 was applied to remove bias.\n\nThe zkLogin circuit and ceremony client code were open-sourced before the ceremony. An audit report on the circuit from zkSecurity was also published.\nAll intermediate files can be reproduced following instructions for phase 1 and phase 2. The final CRS and all transcripts are available in a public repository.\nThe resulting proving key is stored with the proving service. The verifying key was deployed as part of the validator software (protocol version 25 in release 1.10.1).\n\nSecurity and privacy​\n\nThe following analysis covers each zkLogin artifact and the consequences of loss or exposure.\n\nJWT​\n\nThe JWT's validity is scoped to the client ID (aud), preventing phishing attacks. A JWT obtained for a malicious application cannot be used for your app's zkLogin. The JWT is sent directly to the application frontend through the redirect URL.\n\nA leaked JWT can compromise user privacy (JWTs often contain usernames and emails) and, if a backend salt server uses JWTs for authentication, could be used to retrieve the user's salt.\n\nA JWT leak does not mean loss of funds as long as the ephemeral private key is safe.\n\nUser salt​\n\nThe salt is required for both zero-knowledge proof generation and address derivation. A leaked salt does not enable fund theft, but it allows an attacker to link the user's sub to their Sui address. The impact depends on whether the provider uses pairwise identifiers (for example, Facebook, which is unique per app, low risk) or public reusable identifiers (for example, Google, Twitch, which have a globally unique sub, higher privacy risk).\n\nLosing the salt means permanent loss of access to that zkLogin address.\n\nEphemeral private key​\n\nThe ephemeral key's lifespan is tied to max_epoch. If lost, generate a new key pair, complete a new OAuth login, and get a new zero-knowledge proof. If compromised, an attacker would also need the user salt and a valid zero-knowledge proof to moveMoveAn open source programming language used for all activity on Sui. funds.\n\nZero-knowledge proof​\n\nThe proof alone cannot create a valid transaction. An ephemeral signature over the transaction is also required.\n\nPrivacy​\n\nBy default, there is no link between the OAuth sub and the Sui address (this is the purpose of the salt). The JWT is not published onchain. The values revealed onchain are iss, aud, and kid (needed to compute the public input hash). Sensitive fields like sub are private inputs to the proof.\n\nThe proving service and salt service can link user identity (they see both the JWT and salt), but both services are stateless by design.\n\nOffchain signature verification​\n\nYou can verify a zkLogin signature over transaction data or a personal message using the following methods:\n\nSui TypeScript SDK: Use the SDK, which initializes a GraphQL client under the hood.\n\nGraphQL endpoint: Call https://sui-[network].mystenlabs.com/graphql directly. See the GraphQL documentation. Recommended if you do not want to run servers or handle JWK rotations.\n\nSui Keytool CLI (debug use):\n\nsui keytool zk-login-sig-verify --sig $ZKLOGIN_SIG --bytes $BYTES --intent-scope 3 --network devnet --curr-epoch 3\n\nSelf-hosted verifier: Use the zklogin-verifier for custom logic.\n\nFAQ​\n\nWhat providers is zkLogin compatible with?​\n\nzkLogin supports providers that implement OpenID Connect on top of OAuth 2.0. See the supported providers table. Additional providers are enabled through protocol upgrades.\n\nWhat are the circuit constraints?​\n\nGroth16 imposes length restrictions on several JWT fields, including aud (max 120 characters), iss, the JWT header, and payload. These limits were chosen after surveying JWTs from all supported providers.\n\nDoes zkLogin work on mobile?​\n\nYes. zkLogin is a protocol-level primitive, not a feature of a specific application or wallet.\n\nIs a new proof required for every transaction?​\n\nNo. A proof is valid until the ephemeral key pair expires (when the current epoch exceeds max_epoch). Cache and reuse the proof across the session.\n\nCan I convert a traditional wallet to a zkLogin wallet?​\n\nNo. zkLogin addresses are derived differently from private-key-based addresses.\n\nIf an OAuth account is compromised, are funds at risk?​\n\nNo. zkLogin is a two-factor system. An attacker who compromises the OAuth account still needs the salt to derive the address and sign transactions.\n\nIf I lose access to my OAuth account, do I lose access to the address?​\n\nYes. You must produce a current JWT to use zkLogin. If recovery from a lost OAuth account is a concern, use a Sui multisig wallet with a backup signer, even another zkLogin signer from a different provider (for example, a 1-of-2 multisigMultisigMulti-signature transactions that require multiple keys for authorization. with Google and Facebook).\n\nHow is zkLogin different from Web3Auth, Magic, or Privy?​\n\nOther social login solutions typically require one or more of: trusting a separate network to verify credentials (JWK oracle), trusting parties to manage persistent private keys (MPC, secure enclaves), or verifying JWTs or zero-knowledge proofs onchain (expensive). zkLogin avoids all three: validators agree on JWKs by consensus, no persistent private key exists, and zero-knowledge proofs are verified natively at the protocol level.\nRelated topics\n\nZkLogin\nzkLogin is a Sui primitive that lets users send transactions from a Sui address using an OAuth credential, without publicly linking the two.\nZkLogin Integration Guide\nStep-by-step guide to implement zkLogin in your application, covering ephemeral keys, JWT handling, salt management, zero-knowledge proofs, and signature assembly.\nSigning and Sending Transactions\nUnderstanding cryptographic keys, addresses, and signatures on Sui. Sui supports multiple cryptography algorithms and primitives with rapid switching between them.\nGraphQL for Sui RPC\nGraphQL is a public service for the Sui RPC that enables you to efficiently interact with the Sui network.\n\nOpenID providers\nEntities\nTerminologyOpenID provider (OP)\nRelying party (RP) or client\nSubject identifier (sub)\nJSON Web Key (JWK)\nJSON Web Token (JWT)\nKey claim\n\nNotations\nHow zkLogin works\nAddress definitionAddress and session lifetime\n\nCeremony\nSecurity and privacyJWT\nUser salt\nEphemeral private key\nZero-knowledge proof\nPrivacy\n\nOffchain signature verification\nFAQ\n\nWas this page helpful?","tokens":4087,"crawled_at":1791194695236}
+{"id":10423,"url":"https://docs.near.ai/api-reference/chat/create-chat-completion","domain":"docs.near.ai","chapter":"crypto_ai_depin","title":"Create chat completion - NEAR AI","text":"Create chat completion\n\ncurl --request POST \\\n--url https://cloud-api.near.ai/v1/chat/completions \\\n--header 'Authorization: Bearer <token>' \\\n--header 'Content-Type: application/json' \\\n--data '\n{\n\"messages\": [\n{\n\"role\": \"<string>\",\n\"content\": \"<string>\",\n\"name\": \"<string>\",\n\"tool_call_id\": \"<string>\",\n\"tool_calls\": [\n{\n\"function\": {\n\"arguments\": \"<string>\",\n\"name\": \"<string>\"\n},\n\"id\": \"<string>\",\n\"type\": \"<string>\",\n\"thought_signature\": \"<string>\"\n}\n]\n}\n],\n\"model\": \"<string>\",\n\"frequency_penalty\": 123,\n\"max_tokens\": 123,\n\"n\": 123,\n\"presence_penalty\": 123,\n\"stop\": \"<string>\",\n\"stream\": true,\n\"temperature\": 123,\n\"top_p\": 123\n}\n'\n\nimport requests\n\nurl = \"https://cloud-api.near.ai/v1/chat/completions\"\n\npayload = {\n\"messages\": [\n{\n\"role\": \"<string>\",\n\"content\": \"<string>\",\n\"name\": \"<string>\",\n\"tool_call_id\": \"<string>\",\n\"tool_calls\": [\n{\n\"function\": {\n\"arguments\": \"<string>\",\n\"name\": \"<string>\"\n},\n\"id\": \"<string>\",\n\"type\": \"<string>\",\n\"thought_signature\": \"<string>\"\n}\n]\n}\n],\n\"model\": \"<string>\",\n\"frequency_penalty\": 123,\n\"max_tokens\": 123,\n\"n\": 123,\n\"presence_penalty\": 123,\n\"stop\": \"<string>\",\n\"stream\": True,\n\"temperature\": 123,\n\"top_p\": 123\n}\nheaders = {\n\"Authorization\": \"Bearer <token>\",\n\"Content-Type\": \"application/json\"\n}\n\nresponse = requests.post(url, json=payload, headers=headers)\n\nprint(response.text)\n\nconst options = {\nmethod: 'POST',\nheaders: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},\nbody: JSON.stringify({\nmessages: [\n{\nrole: '<string>',\ncontent: '<string>',\nname: '<string>',\ntool_call_id: '<string>',\ntool_calls: [\n{\nfunction: {arguments: '<string>', name: '<string>'},\nid: '<string>',\ntype: '<string>',\nthought_signature: '<string>'\n}\n]\n}\n],\nmodel: '<string>',\nfrequency_penalty: 123,\nmax_tokens: 123,\nn: 123,\npresence_penalty: 123,\nstop: '<string>',\nstream: true,\ntemperature: 123,\ntop_p: 123\n})\n};\n\nfetch('https://cloud-api.near.ai/v1/chat/completions', options)\n.then(res => res.json())\n.then(res => console.log(res))\n.catch(err => console.error(err));\n\n<?php\n\n$curl = curl_init();\n\ncurl_setopt_array($curl, [\nCURLOPT_URL => \"https://cloud-api.near.ai/v1/chat/completions\",\nCURLOPT_RETURNTRANSFER => true,\nCURLOPT_ENCODING => \"\",\nCURLOPT_MAXREDIRS => 10,\nCURLOPT_TIMEOUT => 30,\nCURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,\nCURLOPT_CUSTOMREQUEST => \"POST\",\nCURLOPT_POSTFIELDS => json_encode([\n'messages' => [\n[\n'role' => '<string>',\n'content' => '<string>',\n'name' => '<string>',\n'tool_call_id' => '<string>',\n'tool_calls' => [\n[\n'function' => [\n'arguments' => '<string>',\n'name' => '<string>'\n],\n'id' => '<string>',\n'type' => '<string>',\n'thought_signature' => '<string>'\n]\n]\n]\n],\n'model' => '<string>',\n'frequency_penalty' => 123,\n'max_tokens' => 123,\n'n' => 123,\n'presence_penalty' => 123,\n'stop' => '<string>',\n'stream' => true,\n'temperature' => 123,\n'top_p' => 123\n]),\nCURLOPT_HTTPHEADER => [\n\"Authorization: Bearer <token>\",\n\"Content-Type: application/json\"\n],\n]);\n\n$response = curl_exec($curl);\n$err = curl_error($curl);\n\ncurl_close($curl);\n\nif ($err) {\necho \"cURL Error #:\" . $err;\n} else {\necho $response;\n}\n\npackage main\n\nimport (\n\"fmt\"\n\"strings\"\n\"net/http\"\n\"io\"\n)\n\nfunc main() {\n\nurl := \"https://cloud-api.near.ai/v1/chat/completions\"\n\npayload := strings.NewReader(\"{\\n \\\"messages\\\": [\\n {\\n \\\"role\\\": \\\"<string>\\\",\\n \\\"content\\\": \\\"<string>\\\",\\n \\\"name\\\": \\\"<string>\\\",\\n \\\"tool_call_id\\\": \\\"<string>\\\",\\n \\\"tool_calls\\\": [\\n {\\n \\\"function\\\": {\\n \\\"arguments\\\": \\\"<string>\\\",\\n \\\"name\\\": \\\"<string>\\\"\\n },\\n \\\"id\\\": \\\"<string>\\\",\\n \\\"type\\\": \\\"<string>\\\",\\n \\\"thought_signature\\\": \\\"<string>\\\"\\n }\\n ]\\n }\\n ],\\n \\\"model\\\": \\\"<string>\\\",\\n \\\"frequency_penalty\\\": 123,\\n \\\"max_tokens\\\": 123,\\n \\\"n\\\": 123,\\n \\\"presence_penalty\\\": 123,\\n \\\"stop\\\": \\\"<string>\\\",\\n \\\"stream\\\": true,\\n \\\"temperature\\\": 123,\\n \\\"top_p\\\": 123\\n}\")\n\nreq, _ := http.NewRequest(\"POST\", url, payload)\n\nreq.Header.Add(\"Authorization\", \"Bearer <token>\")\nreq.Header.Add(\"Content-Type\", \"application/json\")\n\nres, _ := http.DefaultClient.Do(req)\n\ndefer res.Body.Close()\nbody, _ := io.ReadAll(res.Body)\n\nfmt.Println(string(body))\n\n}\n\nHttpResponse<String> response = Unirest.post(\"https://cloud-api.near.ai/v1/chat/completions\")\n.header(\"Authorization\", \"Bearer <token>\")\n.header(\"Content-Type\", \"application/json\")\n.body(\"{\\n \\\"messages\\\": [\\n {\\n \\\"role\\\": \\\"<string>\\\",\\n \\\"content\\\": \\\"<string>\\\",\\n \\\"name\\\": \\\"<string>\\\",\\n \\\"tool_call_id\\\": \\\"<string>\\\",\\n \\\"tool_calls\\\": [\\n {\\n \\\"function\\\": {\\n \\\"arguments\\\": \\\"<string>\\\",\\n \\\"name\\\": \\\"<string>\\\"\\n },\\n \\\"id\\\": \\\"<string>\\\",\\n \\\"type\\\": \\\"<string>\\\",\\n \\\"thought_signature\\\": \\\"<string>\\\"\\n }\\n ]\\n }\\n ],\\n \\\"model\\\": \\\"<string>\\\",\\n \\\"frequency_penalty\\\": 123,\\n \\\"max_tokens\\\": 123,\\n \\\"n\\\": 123,\\n \\\"presence_penalty\\\": 123,\\n \\\"stop\\\": \\\"<string>\\\",\\n \\\"stream\\\": true,\\n \\\"temperature\\\": 123,\\n \\\"top_p\\\": 123\\n}\")\n.asString();\n\nrequire 'uri'\nrequire 'net/http'\n\nurl = URI(\"https://cloud-api.near.ai/v1/chat/completions\")\n\nhttp = Net::HTTP.new(url.host, url.port)\nhttp.use_ssl = true\n\nrequest = Net::HTTP::Post.new(url)\nrequest[\"Authorization\"] = 'Bearer <token>'\nrequest[\"Content-Type\"] = 'application/json'\nrequest.body = \"{\\n \\\"messages\\\": [\\n {\\n \\\"role\\\": \\\"<string>\\\",\\n \\\"content\\\": \\\"<string>\\\",\\n \\\"name\\\": \\\"<string>\\\",\\n \\\"tool_call_id\\\": \\\"<string>\\\",\\n \\\"tool_calls\\\": [\\n {\\n \\\"function\\\": {\\n \\\"arguments\\\": \\\"<string>\\\",\\n \\\"name\\\": \\\"<string>\\\"\\n },\\n \\\"id\\\": \\\"<string>\\\",\\n \\\"type\\\": \\\"<string>\\\",\\n \\\"thought_signature\\\": \\\"<string>\\\"\\n }\\n ]\\n }\\n ],\\n \\\"model\\\": \\\"<string>\\\",\\n \\\"frequency_penalty\\\": 123,\\n \\\"max_tokens\\\": 123,\\n \\\"n\\\": 123,\\n \\\"presence_penalty\\\": 123,\\n \\\"stop\\\": \\\"<string>\\\",\\n \\\"stream\\\": true,\\n \\\"temperature\\\": 123,\\n \\\"top_p\\\": 123\\n}\"\n\nresponse = http.request(request)\nputs response.read_body\n\n{\n\"choices\": [\n{\n\"index\": 123,\n\"message\": {\n\"role\": \"<string>\",\n\"content\": \"<string>\",\n\"name\": \"<string>\",\n\"tool_call_id\": \"<string>\",\n\"tool_calls\": [\n{\n\"function\": {\n\"arguments\": \"<string>\",\n\"name\": \"<string>\"\n},\n\"id\": \"<string>\",\n\"type\": \"<string>\",\n\"thought_signature\": \"<string>\"\n}\n]\n},\n\"finish_reason\": \"<string>\"\n}\n],\n\"created\": 123,\n\"id\": \"<string>\",\n\"model\": \"<string>\",\n\"object\": \"<string>\",\n\"usage\": {\n\"completion_tokens\": 123,\n\"prompt_tokens\": 123,\n\"total_tokens\": 123,\n\"completion_tokens_details\": {\n\"reasoning_tokens\": 123\n},\n\"prompt_tokens_details\": {\n\"cached_tokens\": 123\n}\n}\n}\n\n{\n\"error\": {\n\"message\": \"<string>\",\n\"type\": \"<string>\",\n\"code\": \"<string>\",\n\"param\": \"<string>\"\n}\n}\n\n{\n\"error\": {\n\"message\": \"<string>\",\n\"type\": \"<string>\",\n\"code\": \"<string>\",\n\"param\": \"<string>\"\n}\n}\n\n{\n\"error\": {\n\"message\": \"<string>\",\n\"type\": \"<string>\",\n\"code\": \"<string>\",\n\"param\": \"<string>\"\n}\n}\n\n{\n\"error\": {\n\"message\": \"<string>\",\n\"type\": \"<string>\",\n\"code\": \"<string>\",\n\"param\": \"<string>\"\n}\n}\n\n{\n\"error\": {\n\"message\": \"<string>\",\n\"type\": \"<string>\",\n\"code\": \"<string>\",\n\"param\": \"<string>\"\n}\n}\n\nPOST\n/\nv1\n/\nchat\n/\ncompletions\n\nCreate chat completion\n\ncurl --request POST \\\n--url https://cloud-api.near.ai/v1/chat/completions \\\n--header 'Authorization: Bearer <token>' \\\n--header 'Content-Type: application/json' \\\n--data '\n{\n\"messages\": [\n{\n\"role\": \"<string>\",\n\"content\": \"<string>\",\n\"name\": \"<string>\",\n\"tool_call_id\": \"<string>\",\n\"tool_calls\": [\n{\n\"function\": {\n\"arguments\": \"<string>\",\n\"name\": \"<string>\"\n},\n\"id\": \"<string>\",\n\"type\": \"<string>\",\n\"thought_signature\": \"<string>\"\n}\n]\n}\n],\n\"model\": \"<string>\",\n\"frequency_penalty\": 123,\n\"max_tokens\": 123,\n\"n\": 123,\n\"presence_penalty\": 123,\n\"stop\": \"<string>\",\n\"stream\": true,\n\"temperature\": 123,\n\"top_p\": 123\n}\n'\n\nimport requests\n\nurl = \"https://cloud-api.near.ai/v1/chat/completions\"\n\npayload = {\n\"messages\": [\n{\n\"role\": \"<string>\",\n\"content\": \"<string>\",\n\"name\": \"<string>\",\n\"tool_call_id\": \"<string>\",\n\"tool_calls\": [\n{\n\"function\": {\n\"arguments\": \"<string>\",\n\"name\": \"<string>\"\n},\n\"id\": \"<string>\",\n\"type\": \"<string>\",\n\"thought_signature\": \"<string>\"\n}\n]\n}\n],\n\"model\": \"<string>\",\n\"frequency_penalty\": 123,\n\"max_tokens\": 123,\n\"n\": 123,\n\"presence_penalty\": 123,\n\"stop\": \"<string>\",\n\"stream\": True,\n\"temperature\": 123,\n\"top_p\": 123\n}\nheaders = {\n\"Authorization\": \"Bearer <token>\",\n\"Content-Type\": \"application/json\"\n}\n\nresponse = requests.post(url, json=payload, headers=headers)\n\nprint(response.text)\n\nconst options = {\nmethod: 'POST',\nheaders: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},\nbody: JSON.stringify({\nmessages: [\n{\nrole: '<string>',\ncontent: '<string>',\nname: '<string>',\ntool_call_id: '<string>',\ntool_calls: [\n{\nfunction: {arguments: '<string>', name: '<string>'},\nid: '<string>',\ntype: '<string>',\nthought_signature: '<string>'\n}\n]\n}\n],\nmodel: '<string>',\nfrequency_penalty: 123,\nmax_tokens: 123,\nn: 123,\npresence_penalty: 123,\nstop: '<string>',\nstream: true,\ntemperature: 123,\ntop_p: 123\n})\n};\n\nfetch('https://cloud-api.near.ai/v1/chat/completions', options)\n.then(res => res.json())\n.then(res => console.log(res))\n.catch(err => console.error(err));\n\n<?php\n\n$curl = curl_init();\n\ncurl_setopt_array($curl, [\nCURLOPT_URL => \"https://cloud-api.near.ai/v1/chat/completions\",\nCURLOPT_RETURNTRANSFER => true,\nCURLOPT_ENCODING => \"\",\nCURLOPT_MAXREDIRS => 10,\nCURLOPT_TIMEOUT => 30,\nCURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,\nCURLOPT_CUSTOMREQUEST => \"POST\",\nCURLOPT_POSTFIELDS => json_encode([\n'messages' => [\n[\n'role' => '<string>',\n'content' => '<string>',\n'name' => '<string>',\n'tool_call_id' => '<string>',\n'tool_calls' => [\n[\n'function' => [\n'arguments' => '<string>',\n'name' => '<string>'\n],\n'id' => '<string>',\n'type' => '<string>',\n'thought_signature' => '<string>'\n]\n]\n]\n],\n'model' => '<string>',\n'frequency_penalty' => 123,\n'max_tokens' => 123,\n'n' => 123,\n'presence_penalty' => 123,\n'stop' => '<string>',\n'stream' => true,\n'temperature' => 123,\n'top_p' => 123\n]),\nCURLOPT_HTTPHEADER => [\n\"Authorization: Bearer <token>\",\n\"Content-Type: application/json\"\n],\n]);\n\n$response = curl_exec($curl);\n$err = curl_error($curl);\n\ncurl_close($curl);\n\nif ($err) {\necho \"cURL Error #:\" . $err;\n} else {\necho $response;\n}\n\npackage main\n\nimport (\n\"fmt\"\n\"strings\"\n\"net/http\"\n\"io\"\n)\n\nfunc main() {\n\nurl := \"https://cloud-api.near.ai/v1/chat/completions\"\n\npayload := strings.NewReader(\"{\\n \\\"messages\\\": [\\n {\\n \\\"role\\\": \\\"<string>\\\",\\n \\\"content\\\": \\\"<string>\\\",\\n \\\"name\\\": \\\"<string>\\\",\\n \\\"tool_call_id\\\": \\\"<string>\\\",\\n \\\"tool_calls\\\": [\\n {\\n \\\"function\\\": {\\n \\\"arguments\\\": \\\"<string>\\\",\\n \\\"name\\\": \\\"<string>\\\"\\n },\\n \\\"id\\\": \\\"<string>\\\",\\n \\\"type\\\": \\\"<string>\\\",\\n \\\"thought_signature\\\": \\\"<string>\\\"\\n }\\n ]\\n }\\n ],\\n \\\"model\\\": \\\"<string>\\\",\\n \\\"frequency_penalty\\\": 123,\\n \\\"max_tokens\\\": 123,\\n \\\"n\\\": 123,\\n \\\"presence_penalty\\\": 123,\\n \\\"stop\\\": \\\"<string>\\\",\\n \\\"stream\\\": true,\\n \\\"temperature\\\": 123,\\n \\\"top_p\\\": 123\\n}\")\n\nreq, _ := http.NewRequest(\"POST\", url, payload)\n\nreq.Header.Add(\"Authorization\", \"Bearer <token>\")\nreq.Header.Add(\"Content-Type\", \"application/json\")\n\nres, _ := http.DefaultClient.Do(req)\n\ndefer res.Body.Close()\nbody, _ := io.ReadAll(res.Body)\n\nfmt.Println(string(body))\n\n}\n\nHttpResponse<String> response = Unirest.post(\"https://cloud-api.near.ai/v1/chat/completions\")\n.header(\"Authorization\", \"Bearer <token>\")\n.header(\"Content-Type\", \"application/json\")\n.body(\"{\\n \\\"messages\\\": [\\n {\\n \\\"role\\\": \\\"<string>\\\",\\n \\\"content\\\": \\\"<string>\\\",\\n \\\"name\\\": \\\"<string>\\\",\\n \\\"tool_call_id\\\": \\\"<string>\\\",\\n \\\"tool_calls\\\": [\\n {\\n \\\"function\\\": {\\n \\\"arguments\\\": \\\"<string>\\\",\\n \\\"name\\\": \\\"<string>\\\"\\n },\\n \\\"id\\\": \\\"<string>\\\",\\n \\\"type\\\": \\\"<string>\\\",\\n \\\"thought_signature\\\": \\\"<string>\\\"\\n }\\n ]\\n }\\n ],\\n \\\"model\\\": \\\"<string>\\\",\\n \\\"frequency_penalty\\\": 123,\\n \\\"max_tokens\\\": 123,\\n \\\"n\\\": 123,\\n \\\"presence_penalty\\\": 123,\\n \\\"stop\\\": \\\"<string>\\\",\\n \\\"stream\\\": true,\\n \\\"temperature\\\": 123,\\n \\\"top_p\\\": 123\\n}\")\n.asString();\n\nrequire 'uri'\nrequire 'net/http'\n\nurl = URI(\"https://cloud-api.near.ai/v1/chat/completions\")\n\nhttp = Net::HTTP.new(url.host, url.port)\nhttp.use_ssl = true\n\nrequest = Net::HTTP::Post.new(url)\nrequest[\"Authorization\"] = 'Bearer <token>'\nrequest[\"Content-Type\"] = 'application/json'\nrequest.body = \"{\\n \\\"messages\\\": [\\n {\\n \\\"role\\\": \\\"<string>\\\",\\n \\\"content\\\": \\\"<string>\\\",\\n \\\"name\\\": \\\"<string>\\\",\\n \\\"tool_call_id\\\": \\\"<string>\\\",\\n \\\"tool_calls\\\": [\\n {\\n \\\"function\\\": {\\n \\\"arguments\\\": \\\"<string>\\\",\\n \\\"name\\\": \\\"<string>\\\"\\n },\\n \\\"id\\\": \\\"<string>\\\",\\n \\\"type\\\": \\\"<string>\\\",\\n \\\"thought_signature\\\": \\\"<string>\\\"\\n }\\n ]\\n }\\n ],\\n \\\"model\\\": \\\"<string>\\\",\\n \\\"frequency_penalty\\\": 123,\\n \\\"max_tokens\\\": 123,\\n \\\"n\\\": 123,\\n \\\"presence_penalty\\\": 123,\\n \\\"stop\\\": \\\"<string>\\\",\\n \\\"stream\\\": true,\\n \\\"temperature\\\": 123,\\n \\\"top_p\\\": 123\\n}\"\n\nresponse = http.request(request)\nputs response.read_body\n\n{\n\"choices\": [\n{\n\"index\": 123,\n\"message\": {\n\"role\": \"<string>\",\n\"content\": \"<string>\",\n\"name\": \"<string>\",\n\"tool_call_id\": \"<string>\",\n\"tool_calls\": [\n{\n\"function\": {\n\"arguments\": \"<string>\",\n\"name\": \"<string>\"\n},\n\"id\": \"<string>\",\n\"type\": \"<string>\",\n\"thought_signature\": \"<string>\"\n}\n]\n},\n\"finish_reason\": \"<string>\"\n}\n],\n\"created\": 123,\n\"id\": \"<string>\",\n\"model\": \"<string>\",\n\"object\": \"<string>\",\n\"usage\": {\n\"completion_tokens\": 123,\n\"prompt_tokens\": 123,\n\"total_tokens\": 123,\n\"completion_tokens_details\": {\n\"reasoning_tokens\": 123\n},\n\"prompt_tokens_details\": {\n\"cached_tokens\": 123\n}\n}\n}\n\n{\n\"error\": {\n\"message\": \"<string>\",\n\"type\": \"<string>\",\n\"code\": \"<string>\",\n\"param\": \"<string>\"\n}\n}\n\n{\n\"error\": {\n\"message\": \"<string>\",\n\"type\": \"<string>\",\n\"code\": \"<string>\",\n\"param\": \"<string>\"\n}\n}\n\n{\n\"error\": {\n\"message\": \"<string>\",\n\"type\": \"<string>\",\n\"code\": \"<string>\",\n\"param\": \"<string>\"\n}\n}\n\n{\n\"error\": {\n\"message\": \"<string>\",\n\"type\": \"<string>\",\n\"code\": \"<string>\",\n\"param\": \"<string>\"\n}\n}\n\n{\n\"error\": {\n\"message\": \"<string>\",\n\"type\": \"<string>\",\n\"code\": \"<string>\",\n\"param\": \"<string>\"\n}\n}\n\nAuthorizations\n\n​\n\nAuthorization\nstring\nheader\nrequired\n\nAPI key for programmatic access (Authorization: Bearer sk-<api_key>)\n\nBody\napplication/json\n\n​\n\nmessages\nobject[]\nrequired\n\nShow child attributes\n\n​\n\nmodel\nstring\nrequired\n\n​\n\nfrequency_penalty\nnumber<float> | null\n\n​\n\nmax_tokens\ninteger<int64> | null\n\n​\n\nn\ninteger<int64> | null\n\n​\n\npresence_penalty\nnumber<float> | null\n\n​\n\nstop\nstringstring[]stringstring[]\n\nOpenAI stop accepts either a single string or an array of strings.\n\n​\n\nstream\nboolean | null\n\n​\n\ntemperature\nnumber<float> | null\n\n​\n\ntop_p\nnumber<float> | null\n\n​\n\n{key}\nany\n\nResponse\n\nCompletion generated successfully\n\n​\n\nchoices\nobject[]\nrequired\n\nShow child attributes\n\n​\n\ncreated\ninteger<int64>\nrequired\n\n​\n\nid\nstring\nrequired\n\n​\n\nmodel\nstring\nrequired\n\n​\n\nobject\nstring\nrequired\n\n​\n\nusage\nobject\nrequired\n\nUsage for chat/completions endpoints.\nSerializes as prompt_tokens, completion_tokens, prompt_tokens_details, completion_tokens_details, total_tokens.\n\nShow child attributes\n\n​\n\n{key}\nany\n\nUnknown top-level fields from the provider (e.g. system_fingerprint, prompt_logprobs).\nRe-emitted when serializing so we do not drop them.","tokens":3727,"crawled_at":1791194698159}
+{"id":10424,"url":"https://a16zcrypto.com/team/abigail-johnson","domain":"a16zcrypto.com","chapter":"research","title":"Abigail Johnson - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nAbigail Johnson\n\nFeed\nFilter\n(1)\nclear filters\n\ncategory\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\nrecommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nauthor\n(1) all authors\n@x0rart\n1337 Skulls Sers\na16z crypto\na16z crypto editorial\na16z crypto policy & regulatory teams\na16z crypto Regulatory Team\nAaditya Shidham\nAaron Levie\nAaron Phillips\nAaron Schnider\nAbby Green\nAbdou Ndiaye\nAbhi Shelat\nAbhiram Kothapalli\nAbigail Johnson\nAdam Alter\nAdam Back\nAdam Bry\nAdam Grant\nAdam Ludwin\nAdam Martin\nAdam Thierer\nAdam Zuckerman\nAdela Tomsejova\nAdena Friedman\nAdena Hefets\nAdeniyi Abiodun\nAdina Fischer\nAdrian Cockcroft\nAdrian Fenty\nAdrienne Mayor\nAgostino Capponi\nAiden Slavin\nAileen Lee\nAisha Stephenson\nAJ Shankar\nAlan Knott-Craig\nAlan Schaaf\nAlana Benton\nAlbert Tang\nAlec Nielsen\nAlec Ross\nAlejandro Flores\nAlex Constantinople\nAlex Honnold\nAlex Hutchinson\nAlex Immerman\nAlex Kreitz\nAlex Kroeger\nAlex Le\nAlex Masmej\nAlex Morcos\nAlex Price\nAlex Pruden\nAlex Rampell\nAlex Roetter\nAlex Solomon\nAlex Spector\nAlex Stamos\nAlex Tabarrok\nAlexander (Sasha) Spiegelman\nAlexander Chia\nAlexander Zoppa\nAlexandra Chang\nAlexandria Lafci\nAlexis Lakes\nAlexis Madrigal\nAlexis Ohanian\nAli Ghodsi\nAli Yahya\nAlicia Barone\nAlin Tomescu\nAlisha Litman\nAlison Mangiero\nAlison Martin\nAllison Pickens\nAlyssa Del Bene\nAlyssa Torres\nAmanda Cantor\nAmanda Cassatt\nAmanda Catherine\nAmanda Mulay\nAmanda Tuminelli\nAmanda Tyler\nAmelia Salyers\nAmie Tyrrel\nAmir Shevat\nAmira Yahyaoui\nAmy Abernethy\nAmy Berliner\nAmy Bohutinsky\nAmy Choice\nAmy Cray\nAmy Gill\nAmy Hoemeke\nAmy Kalokerinos\nAmy Robertson\nAna Mostarac\nAna Susi\nAnatoly Yakovenko\nAndie Taylor\nAndisheh Tahriri\nAndre Iguodala\nAndrea Clarke Hall\nAndrea Feinberg\nAndrea Rallo\nAndrea Simon\nAndrea Vinkler\nAndreas Papadimitropoulos, Jr\nAndreessen Horowitz\nAndrew Allen\nAndrew Chen\nAndrew F. Read\nAndrew Green\nAndrew Hall\nAndrew Lakis\nAndrew Lewis-Pye\nAndrew Lo\nAndrew Mason\nAndrew McAfee\nAndrew Milson\nAndrew Omori\nAndrew Radin\nAndrew Rubin\nAndrew Savage\nAndrew Smith\nAndrew Tretyakov\nAndy Beal\nAndy Coravos\nAndy Golden\nAndy Hill\nAndy Milenius\nAndy Rachleff\nAndy Tran\nAndy Walshe\nAneel Lakhani\nAngela Schenone\nAngela Strange\nAngela Tran Kingyens\nAngelica Gehr\nAniket Kate\nAnil Sethi\nAnish Acharya\nAnn Winblad\nAnna Berces\nAnna Jablonski\nAnna Semenova\nAnna Van Meurs\nAnnaLee Saxenian\nAnne Brandes\nAnne Lee Skates\nAnne Lewandowski\nAnne Mitchell\nAnne Yip\nAnnie Collins\nAnnie Duke\nAnthony Albanese\nAnthony Atala\nAnthony Foxx\nAnthony Lee Zhang\nAntonio Viggiano\nAntwone Stigall\nAnu Hariharan\nApril Roth\nAri Emanuel\nAri Juels\nArianna Huffington\nArianna Simpson\nArik Kershenbaum\nArmon Dadgar\nArnie Goldberg\nArsho Avetian\nArthur Brooks\nArun Sundararajan\nAsh Ashutosh\nAsha Christian\nAshley McCollum\nAshley Stern\nAshton Carter\nAtif Mian\nAtul Butte\nAubree Pelaez\nAubrey de Grey\nAugusto Marietti\nAurora Petracca\nAusten Allred\nAustin Guzman\nAustin Marchese\nAustin Wilson\nAva Iravani\nAvery Segal\nAvinash Solanky\nAviv Zohar\nAye Moah\nAzeem Azhar\nBailey Flanigan\nBailey Richardson\nBalaji Srinivasan\nBarry McCarthy\nBart Dessaint\nBeau Cronin\nBeau Woods\nBecky Pferdehirt\nBen Buckwalter\nBen Fielding\nBen Fisch\nBen Gardner\nBen Gomez\nBen Horowitz\nBen Kaufman\nBen Leventhal\nBen Lovell\nBen Napier\nBen Portney\nBen Rubin\nBen Scharfstein\nBen Schecter\nBen Silbermann\nBen Uretsky\nBen Wu\nBenedict Evans\nBenedikt Büenz\nBenjamin Ebner\nBenjamin Hindman\nBenjamin Wittes\nBenjamin Wu\nBennett Carroccio\nBenny Pinkas\nBernard J. Tyson\nBernard Tyson\nBeth Newman\nBethany Coates\nBharat Ramamurti\nBharath Ramsundar\nBill Carr\nBill Frist\nBill Hinman\nBill Janeway\nBill Krause\nBill Macaitis\nBlake Kim\nBlake Masters\nBlake Saari\nBlayne Donnell\nBob Iger\nBob Langer\nBob Moore\nBob Muglia\nBob Sutton\nBob Swan\nBob Tinker\nBob Wachter\nBobby Franklin\nBobby Green\nBobby Kotick\nBobby Wagner\nBoris Sofman\nBoris Wertz\nBrad Feld\nBrad Kern\nBrad Peterson\nBram Cohen\nBrandon Ballinger\nBrandon Barros\nBrandon Cherry\nBrandon Millman\nBrenda Kopf\nBrent McIntosh\nBrett Browman\nBrett Falk\nBrett Hagler\nBrewster Kahle\nBrian Armstrong\nBrian Balfour\nBrian Brooks\nBrian Crnkovich\nBrian Curran\nBrian Grazer\nBrian Koppelman\nBrian McCullough\nBrian Quintenz\nBrian Wilkins\nBridget McDowell\nBrittany Lucas\nBrittney Burrows\nBrooke Sheresky\nBruce Friedrich\nBryan Caplan\nBryan Chiang\nBryan Cox\nBryan Crowley\nBryan Faust\nBryan Houser\nBryan Kim\nBryan Pellegrino\nCaitlin Glazebrook\nCaitlin Johnston\nCaitlin Roberson\nCal Turner Jr.\nCaleb Christian\nCameron Schuler\nCamila De Souza\nCarine Carmy\nCarissa Bilinski\nCarl Agnelli\nCarl Eschenbach\nCarl Narcisse\nCarl Pope\nCarlos Araya\nCarolina Gonzalez\nCaroline Friedman\nCaroline Goggins\nCaroline Horn\nCaroline Moon\nCarolyn Bertozzi\nCarra Wu\nCasey Graul\nCasey Neistat\nCasey Winters\nCassady Churchill\nCassie Faerber\nCecilia Marshall\nCeia Font\nChad Rigetti\nChandra Krintz\nCharles Goetz\nCharles Hubbard\nCharles Koch\nCharlie Keinath\nCharlie Warzel\nChattry Meas\nChelsea Komlo\nChelsea Padilla\nCheng Li\nChris Bennett\nChris Best\nChris Burniske\nChris Curran\nChris DeWolfe\nChris Dixon\nChris Granger\nChris Hauth\nChris Lyons\nChris Messina\nChris Milk\nChris Power\nChris Santa Maria\nChris Wanstrath\nChristian Cachin\nChristian Catalini\nChristian Crowley\nChristian Seifert\nChristina Hampp\nChristina Lopes\nChristina Mercando\nChristina Xu\nChristina Zeidan\nChristine Darden\nChristine Perham\nChristopher Giancarlo\nChristopher Lee\nChristopher Mims\nChristopher Nguyen\nChristopher Rippingham\nChristopher Schroeder\nChristy Hubbard\nCiamac Moallemi\nCindi Zhang\nCindy Tenner\nClaire Austin\nClaire Cain Miller\nClaire Kart\nClaudia Picanco\nClay Shirky\nClayton Christensen\nClayton Gardner\nClifford Woolf\nClint Delapaz\nColin Bryar\nColin Rom\nCollin McCune\nConner Lyons Brown\nConnie Chan\nConnie Guglielmo\nConnor McCarthy\nConnor Moyles\nCorban Bell\nCorey Hawkins\nCorey Waller\nCourtney Dettlinger\nCraig Naylor\nCraig Walker\nCristina Cordova\nCurt Funderburk\nCuy Sheffield\nD'Arcy Coolican\nDaejun Park\nDaisy Linden\nDaisy Wolf\nDaljeet Virdi\nDalton Turay\nDan Berkenstock\nDan Boneh\nDan Frommer\nDan Primack\nDan Romero\nDan Shapero\nDan Siroker\nDan Stein\nDan Warmenhoven\nDan Wendlandt\nDaniel Chao\nDaniel Chen\nDanielle Andrzejewski\nDanielle Clark\nDanielle Looymans\nDanielle Lussier\nDanielle Morrill\nDanielle Shea\nDanny Shader\nDaphne Koller\nDapper Dan\nDaren Matsuoka\nDarin Malter\nDarshan Shankar\nDas Rush\nDave Jagoda\nDave King\nDave Touretzky\nDavid Banks\nDavid Belden\nDavid Damato\nDavid Deming\nDavid George\nDavid Haber\nDavid Hollestelle\nDavid Kerr\nDavid Lee\nDavid Mack\nDavid Madden\nDavid Marcus\nDavid Olson\nDavid Oyelowo\nDavid Pierce\nDavid Reich\nDavid Rumsey\nDavid Schweikert\nDavid Sinclair\nDavid Sverdlov\nDavid Tse\nDavid Ulevitch\nDavid Weiden\nDawn Lepore\nDawn Nott\nDeborah Embaie\nDeena Elitreby\nDeepak Maram\nDenis Nazarov\nDenis Young\nDenise Gonzalez\nDerek Dolin\nDerek Thompson\nDerrick Harris\nDevin Finzer\nDevon Zuegel\nDiana Peña\nDiane Greene\nDick Costolo\nDieter Shirley\nDiishan Imira\nDiogo Monica\nDominic Shine\nDominique Reliford\nDon Duet\nDon Faul\nDorris O'Brien\nDoug Ducey\nDoug Folden\nDoug McCracken\nDouglas Argueta\nDozie Uche\nDrew Coffman\nDylan Field\nDylan Rhodes\nEd Felten\nEd Lynch\nEddie Lim\nEddy Lazzarin\nEdith Zimmerman\nEdward Perkins\nEdwin Poston\nEfrat Noy\nEhud Shapiro\nEileen Burbidge\nEileen Wu\nElad Gil\nElaine Fuchs\nElaine Shi\nElena Burger\nEli Dourado\nElisa Leonhardt\nEliza Oak\nElizabeth Gunn\nElizabeth Harkavy\nElizabeth May\nElizabeth Ocken\nElizabeth Stark\nElizabeth Weil\nEllen Tunoa\nEmile Petrone\nEmilio Torres\nEmily Graff\nEmily Hinsch\nEmily Keir\nEmily Oster\nEmily Westerhold\nEmma Janaskie\nEric Budish\nEric Dai\nEric Ries\nEric Thomas\nEric Topol\nEric Wu\nErica Schecter\nErik Brynjolfsson\nErik Kiser\nErik Torenberg\nErika Bracken\nErika Herrera\nErika Louie\nErin Grody Kingsley\nErin Murphy\nErin Tice\nErin Tonnar\nErin Winkler\nErtem Nusret Tas\nEsther Shinn\nEthan Bueno de Mesquita\nEthan Ferreira\nEthan Zuckerman\nEuan Ashley\nEugene Volokh\nEugene Wei\nEugenia Yee\nEula Takahashi\nEva Sakkas\nEvan Burfield\nEvan Osnos\nEvangelos Simoudis\nEzra Klein\nF. Gary Gray\nFabiola Godinez\nFabrizio Zilibotti\nFahad Saleh\nFarid Jiandani\nFei-Fei Li\nFelix Do\nFEWOCIOUS\nFiona Kennedy\nFiona Murray\nFlashrekt\nFlora Oliveira\nFlori Del Valle\nFlorian Leibert\nFoteini Baldimtsi\nFrancesca Gino\nFrank Chen\nFrank Wilczek\nFred Benenson\nFred Ehrsam\nFred Upton\nFred Wilson\nFreda Lewis-Hall\nFrederic Kerrest\nFuture Editorial\nGabby Dizon\nGabby Reece\nGabriel Otte\nGabriel Vasquez\nGaetan Barthelemy\nGarrett Biel\nGary Ang\nGary Reedy\nGary Wolf\nGaurav Banga\nGaurav Dhillon\nGaut\nGayle Tzemach Lemmon\nGeoffrey Woo\nGeorg Fuchsbauer\nGeorg Petschnigg\nGeorge Church\nGeorge Danezis\nGeorge Fraser\nGeraldine Chan\nGérard Cachon\nGerard Ryle\nGerri Elliott\nGerry Tsoukalas\nGia Scinto\nGil Elbaz\nGil Shafir\nGina Moon\nGina Neff\nGina Yocom\nGinger Liau\nGokul Rajaram\nGoldie Chang\nGrace Ellis\nGraham Allison\nGrant Gregory\nGrant Jordan\nGrant LaFontaine\nGrant Rabenn\nGray Kinsella\nGreg Bowman\nGreg Clayman\nGreg Linares\nGreg Loehmann\nGreg Lynn\nGreg Solano\nGreg Truesdell\nGreg Waldon\nGregory Allen\nGregory Mundis\nGretchen Bush\nGretchen McCulloch\nGuido Appenzeller\nGustav Söderström\nGustavo Garcia\nGuy Goren\nGuy Raz\nGuy Wuollet\nHaley Van Dyck\nHanna Aziz\nHannah Frankl\nHanne Winarsky\nHaoyuan Li\nHarmit Malik\nHarry Grieve\nHarry Shum\nHarry Wright\nHatim Shafique\nHayden Adams\nHeather Gwynn\nHeather Podesta\nHedi Samar\nHelen Stoddard\nHelen Su\nHemant Mohapatra\nHendrik Pretorius\nHenri Kor\nHerb Lin\nHerman Narula\nHilmar Pétursson\nHoang Nguyen\nHoward Wu\nIan Dutra\nIan Shannon\nIan Sharp\nIce Cube\nIlan Zechory\nIllia Polosukhin\nIlyas Khan\nIma Christian\nIman Abuzeid\nInsiya Lokhandwala\nIon Stoica\nIrvin Chan\nIsa Guardalabene\nIsaiah Lott\nIsh Verduzco\nIsil Dillig\nIstván András Seres\nIttai Abraham\nIttay Eyal\nIva Messy\nIvan Linscott\nIvor Horn\nJ.D. Moriarty\nJack Donahoe\nJack Soslow\nJackie McQuiston\nJackson David\nJacob Westphal\nJacquelyn Melinek\nJad Esber\nJad Naous\nJade Lai\nJade Raymond\nJae Gnazzo\nJai Ramaswamy\nJaimie Buss\nJak Kennedy\nJake Auchincloss\nJakob Uszkoreit\nJamal Mohammed\nJames Beshara\nJames Currier\nJames da Costa\nJames Gwertzman\nJames J. Collins\nJames Kissell\nJames L. Madara\nJames Loftus\nJames Rathmell\nJames Rogers\nJames Watters\nJames Wu\nJames Zou\nJamie Brandon\nJamie McGurk\nJamie Sullivan\nJamilla Hemeid\nJana Odehnal\nJane Doe\nJane Lippencott\nJane Suh\nJanelle De Los Santos\nJared Bricklin\nJared Furutani\nJared Georgakopoulos\nJared Polis\nJared Smith\nJase Wilson\nJason Franklin\nJason Liu\nJason Mayden\nJason Milionis\nJason Mitchell\nJason Mok\nJason Rosenthal\nJason Warner\nJason Yanowitz\nJay Bradner\nJay Conte\nJay Drain\nJay Komarneni\nJay Rughani\nJean Reilly\nJeanne Tsan\nJeff Amico\nJeff Benson\nJeff Clark\nJeff Cordova\nJeff Glueck\nJeff Hawkins\nJeff Jones\nJeff Jordan\nJeff Lawson\nJeff Lu\nJeff Nagashima\nJeff Stump\nJeff Weiner\nJeffrey Immelt\nJeffrey Kaditz\nJeffrey Katzenberg\nJeffrey Kindler\nJeffrey Low\nJeffrey Silverstein\nJeffrey Zirlin\nJen Bulawsky\nJen Kha\nJenna Walsh\nJenna Zucker\nJennifer 8. Lee\nJennifer Doudna\nJennifer Kodner\nJennifer Konde\nJennifer Li\nJennifer Mumford\nJennifer Tejada\nJennifer Young\nJenny Cieplak\nJens Ernstberger\nJensen Harris\nJeremy Clark\nJeremy England\nJeremy Zhang\nJesse Holmes\nJesse Pollak\nJesse Walden\nJessica Childs\nJessica Hansen\nJessica Keeler\nJessica Patton\nJessica Verrilli\nJewel Pi\nJez Humble\nJi Kim\nJianying Luo\nJim Gilliam\nJimmy Chen\nJimmy Soni\nJing Wang\nJing Zou\nJJ Yu\nJoachim Neu\nJodi Lynn\nJodie Lutkenhaus\nJoe Gebbia\nJoe Grundfest\nJoe Montana\nJoe Morrissey\nJoe Schmidt\nJoe Sullivan\nJoel de la Garza\nJoel Mokyr\nJoel Monegro\nJoel Spolsky\nJoey Burleson\nJohn China\nJohn Collison\nJohn Fawcett\nJohn Garcia\nJohn Gedmark\nJohn Hennessy\nJohn Koelliker\nJohn M. Jack\nJohn Markoff\nJohn Menna\nJohn O’Farrell\nJohn Riccitiello\nJohn Smesko\nJohn Stanfield\nJohn Thompson\nJohn William Hatfield\nJonah Peretti\nJonathan Bush\nJonathan Dotan\nJonathan Downey\nJonathan Lai\nJonathan Lim\nJonathan Lusthaus\nJonathan Weissman\nJonathan Wong\nJordan Mazer\nJordan Stankowski\nJorge Conde\nJorge Gomez\nJose Guardado\nJoseph Bonneau\nJoseph Okpaku\nJoseph Spisak\nJosh Arnold\nJosh Bloom\nJosh Kim\nJosh Williams\nJoshua Browder\nJoshua Gans\nJoshua Grimm\nJoshua Hix\nJoshua Levin\nJoshua Lu\nJoshua Schank\nJoshua Soto\nJosie Ma\nJoyce Park\nJR Rivers\nJT Evans\nJuan Benet\nJudene Small\nJudy Savitskaya\nJudy Smith\nJulia Grace\nJulia Kirby\nJulie Bornstein\nJulie Farnham\nJulie Johnson\nJulie Samuels\nJulie Yoo\nJuliet Grier\nJuliet Nyatta\nJuliette Morton\nJulius Zhang\nJustin Bailey\nJustin Bethune\nJustin Blau\nJustin Cunningham\nJustin Gregorius\nJustin Kahl\nJustin Kan\nJustin Larkin\nJustin Paine\nJustin Pettit\nJustin Roberts\nJustin Simcock\nJustin Thaler\nJustine Moore\nJutta Steiner\nJyoti Bansal\nJZ Young\nKabir Gill\nKabir Laroia\nKais Khimji\nKamala Harris\nKaren Dunn\nKaren Wooley\nKarina Sobieski\nKarl Floersch\nkarma (Daniel Reynaud)\nKarmacoma\nKarthik Rau\nKartik Nayak\nKate Darling\nKate Dellolio\nKate Kerames\nKatherine Boyle\nKatherine Minarik\nKatherine Rundell\nKatherine Schoebel\nKathryn McKinley\nKathy Liu\nKathy Yang\nKatia Ameri\nKatie Baynes\nKatie Haun\nKatie Hemmerling\nKaty DeWitt-Drew\nKaty Nelson\nKayvon Tehranian\nKeener Barnhorst\nKeller Medlin\nKeller Rinaudo\nKelly Cannon\nKelsey Chaplinsky\nKelsey Mellard\nKen Chong\nKen Coleman\nKen Kocienda\nKerry Ganim\nKesha Cash\nKevin Chou\nKevin Chu\nKevin Dulsky\nKevin Kelly\nKevin McKinley\nKevin Nishioka\nKevin O'Kane\nKevin Rose\nKevin Tan\nKevin Wu\nKevin Zollman\nKidSuper\nKieran Snyder\nKierston Gittens\nKiki Mavridis\nKim Enright\nKim Malone Scott\nKim Milosevich\nKim Stevenson\nKim Zetter\nKimberly Tan\nKindra Mason\nKira Poskanzer\nKira Song\nKirstin Arbide\nKirt McMaster\nKofi Ampadu\nKouki Harasaki\nKrista Anderson-Copperman\nKristen Fortney\nKristen Johansson\nKristen Kee\nKristin Sauchak\nKristin Thayer\nKristina Graci-deLuna\nKristina Shen\nKristine Lipscomb\nKristo Käärmann\nKrisztina Holly\nKunal Bahl\nKunle Olukotun\nKurt House\nKyle Russell\nLaird Hamilton\nLatasha\nLaura Arrillaga-Andreessen\nLaura Baller\nLaura Behrens Wu\nLaura Deming\nLaura Gravley\nLaura Johnson\nLaura Shores\nLaura Weidman Powers\nLauren Berson\nLauren Illovsky\nLauren Murrow\nLauren Richardson\nLauren Spragge\nLaurene Powell Jobs\nLawrence Levy\nLawrence Summers\nLeah Cassidy\nLee Kleinman\nLee Lefkowitz\nLeeAnn Caballero\nLeila Hay\nLeila Janah\nLenny Rachitsky\nLeslie Jaw\nLeslie Vosshall\nLester Chen\nLi Fan\nLi Fei-Fei\nLi Jin\nLiang Wu\nLilian King\nLily Liu\nLina Sergie Attar\nLinda Banuelos\nLinda Xie\nLinden Tibbets\nLing Ren\nLinlin Li\nLinxin Wen\nLioba Heimbach\nLisa Hawke\nLisa Lambert\nLisa Orr\nLisa Reilly\nLisa Rosano\nLizzy Anderson\nLJ Erwin\nLloyd Dean\nLoretta Sanchez\nLori Potter\nLuca Prosperi\nLuca Zanolini\nLuis Martinez\nLuis von Ahn\nLuke Wroblewski\nLydia Green\nLynda Gibson\nLynn Rudolph\nMadan Nagaldinne\nMaddison Masaeli\nMadeline Lancaster\nMaggie Hsu\nMaggie Leung\nMaggie Romero\nMahad Abedin\nMahesh Iyer\nMahesh Vellanki\nMahimna Kelkar\nMakiri Duckett\nMalinka Walaliyadde\nMallesh M. Pai\nMalloy Evans\nManas Punhani\nManny Luna\nMarc Andreessen\nMarc Andrusko\nMarc Benioff\nMarc Levinson\nMarci Barbera\nMarco Reuter\nMargaret Jen\nMargit Wennmachers\nMaria LaMagna Morales\nMarian Garvin\nMarianne Winkler\nMariano Sorgente\nMaricarmen Alvarez\nMariel Goldenstein\nMarigold Vu\nMarina Kusserow\nMario Gabriele\nMario Linares\nMarissa Bramlett\nMark Cranney\nMark Leslie\nMark McAndrew\nMark McClusky\nMárk Melczer\nMark Moore\nMark Regan\nMark Sendak\nMarkos Georghiades\nMarkus Covert\nMarkus Funk\nMartha Lane Fox\nMartin Casado\nMartin Fischer\nMarty Makary\nMarvin Ammori\nMarvin Zamora\nMary Pat Jordan\nMary-Catherine Lader\nMaryam Bahrani\nMason Hall\nMatei Zaharia\nMatt Abrahams\nMatt Billmann\nMatt Bornstein\nMatt Clifford\nMatt Flannery\nMatt Fleming\nMatt Gleason\nMatt Kaeberlein\nMatt Levine\nMatt Levy\nMatt Oberhardt\nMatt Shortal\nMatt Spence\nMatt Weinberg\nMatthew Colford\nMatthew Green\nMatthew Haughey\nMatthew McCullough\nMatthew Mills\nMatthew Olsen\nMatthew Rutter\nMatthew Stein\nMatthieu Hafemeister\nMaureen Lara\nMax Kesten\nMax Krohn\nMax Levchin\nMax Polyak\nMax Resnick\nMax Ventilla\nMaya Rahkonen\nMcPherson Moore\nMeaghan Hardy\nMeg Whitman\nMegan Holston-Alexander\nMegan Kristalyn\nMehdi Hasan\nMehul Mehta\nMel Williams\nMelanie Galang\nMelissa Liao\nMelissa Minor\nMelissa Wasser\nMellody Hobson\nMelody Latronico\nMeredith Donahue\nMia Gonzalez\nMia Mandich\nMicah Johnson\nMichael Beckerman\nMichael Blau\nMichael Brandt\nMichael Chan\nMichael Copeland\nMichael Dearing\nMichael Dell\nMichael Franklin\nMichael Garcia\nMichael J. Casey\nMichael J. Freedman\nMichael Killam\nMichael King\nMichael Lee\nMichael Leiter\nMichael Morell\nMichael Ostrovsky\nMichael Ovitz\nMichael Paulus\nMichael Raynor\nMichael Reed\nMichael Snyder\nMichael Temkin\nMichael Wee\nMichael Zhu\nMichel Del Buono\nMichel Feaster\nMichèle Flournoy\nMichele Griffin\nMichele Korver\nMichele Law\nMichelle Ervin\nMichelle Kelso\nMichelle Kung\nMichelle Mundy\nMichelle Shin\nMichelle Ufford\nMichelle Volz\nMichelle Wilson\nMichelle Winn\nMichelle You\nMike Curtis\nMike Haydon\nMike Hearn\nMike Jones\nMike Kasperzak\nMike Kelly\nMike King\nMike Lempres\nMike Manning\nMike Maples jr\nMike Masnick\nMike Matchett\nMike Paulus\nMike Sandwick\nMikeal Rogers\nMikey Dickerson\nMiles Jennings\nMilijana Curic\nMiller Whitehouse-Levine\nMinerva Munoz\nMinnie Ingersoll\nMinsun Pak\nMintu Turakhia\nMiranda Christ\nMo Shaikh\nMohammad Akbarpour\nMohsen Malayeri\nMolly Grace\nMonique McCambridge\nMorgan Beller\nMorgan Bender\nMurat Pak\nMuriel Bowser\nMurray Shanahan\nMy Pham\nNadia Asparouhova\nNadia Eghbal\nNaftali Harris\nNaithan Jones\nNanjira Sambuli\nNaomi Metzger\nNashid Braswell\nNassim Eddequiouaq\nNat Barling\nNatacha Crooks\nNatalia Carrera\nNatalie Bucher\nNatalie Taumoepeau\nNate Chang\nNate Lau\nNathalie Balaban\nNathan McCauley\nNathan Yoon\nNathaniel Gleicher\nNathaniel Popper\nNav Singh\nNazanin Daneshvar\nNeel Maitra\nNeha Narula\nNelson Perla-Ward\nNeveen Bader\nNicholas Christakis\nNicholas Pacilio\nNick Babaian\nNick McKeown\nNick Quah\nNick Tomaino\nNicki Locker\nNicole Conner\nNicole Forsgren\nNicole Irvin\nNicole Neuman\nNicole Stanners\nNiels Provos\nNigel Robinson\nNikhil Krishnan\nNina Suthers\nNir Eyal\nNitasha Tiku\nNitin Natarajan\nNitya Subramanian\nNkiru Balonwu\nNoah Citron\nNoah Feldman\nNoah Levine\nNoah Smith\nNoam Nisan\nNoemi Glaeser\nO’Shea Jackson Jr.\nOlaf Carlson-Wee\nOleg Rogynskyy\nOliver Hsu\nOlivia Moore\nOlivia Webb\nOmri Weinstein\nOoshma Garg\nOprah Winfrey\nOrion Hindawi\nOscar Menjivar\nP.J. Hasleton\nPablo Montagnes\nPacky McCormick\nPak\nPalmer Luckey\nPamela Anderson\nPamon Forouhar\nParag Khanna\nParijat Talkad\nParker Brown\nParker Conrad\nPatrice Peck\nPatrick Byrne\nPatrick Collison\nPatrick Conway\nPatrick McCorry\nPatrick McHenry\nPatrick O’Grady\nPatrick Rivera\nPatrick Sutton\nPaul Cafiero\nPaul Daugherty\nPaul Davison\nPaul Krugman\nPaul Vigna\nPaula Long\nPenny Pritzker\nPerri Chilton\nPete Buttigieg\nPeter Blackwood\nPeter Buisseret\nPeter Chan\nPeter Donnelly\nPeter Johnson\nPeter Lauten\nPeter Leeson\nPeter Levine\nPeter Ludwig\nPeter Rubin\nPeter Thiel\nPeter Wang\nPetra Garrett\nPhil Daian\nPhil Hathaway\nPhil Wong\nPhong Nguyen\nPorter Smith\npplpleasr\nPranav Garimidi\nPrasad Akella\nPrat Moghe\nPreethi Kasireddy\npunk6529\nPurnima Padmanabhan\nPyrs Carvolth\nQasar Younis\nQuang Dao\nQuinten Burgunder\nQuintus Kilbourn\nRachael Horwitz\nRachel Goslins\nRachel Jenkins\nRachel Kalmar\nRachel McIntyre\nRachel Steiner\nRahul Iyer\nRahul Vohra\nRajeev Singh\nRajeev Venkayya\nRam Palaniappan\nRamana Jonnala\nRati Gelashvili\nRaul Vazquez\nRavi Parimi\nRay Dalio\nRaymond Carreira\nRebecca Lewis\nRebecca Rettig\nReed Hastings\nRefik Anadol\nRegina Benjamin\nRenato Valdés Olmos\nReshma Saujani\nReshma Sohoni\nRex Salisbury\nRich Ezekiel\nRichard Green\nRichard Menger\nRichard Rosenblatt\nRick Young\nRidhima Ahuja\nRiyaz Faizullabhoy\nRob Goodman\nRob McElhenney\nRob Pardo\nRob Rhinehart\nRobbie Petersen\nRobbie Peterson\nRobert Alexander\nRobert Cottrell\nRobert Hackett\nRobert Kolker\nRobert Leshner\nRobert McNeely\nRobert Moreno\nRobert Siegel\nRobert Stromberg\nRobert Weber\nRobin Casey\nRobin Guo\nRobin Weisman\nRod Johnson\nRodrigo Ibarra Lopez\nRodrigo Pacheco\nRoger Dickey\nRoger Wattenhofer\nRoham Gharegozlou\nRohini Mukand\nRohit Bansal\nRoman Mars\nRoman Stanek\nRon Gill\nRon Lavi\nRon Rothblum\nRonald Evans\nRonnie Harris\nRosa Davila\nRosalind Rattan\nRose Legarda\nRoss Andersen\nRoss Shuel\nRostin Behnam\nRuben Gallego\nRuben Smith\nRuss Altman\nRuss Heddleston\nRuss Roberts\nRussell Davies\nRyan Allen\nRyan Caldbeck\nRyan Conde\nRyan Holloway\nRyan Hoover\nRyan McEntush\nRyan Petersen\nRyan Prescott\nRyan Sandler\nRyan Spoon\nRyan Tseng\nRyan Walsh\nRyan Ward\nRyan Wyatt\nSaar Tochner\nSachin Jain\nSafi Bahcall\nSagar Dhawan\nSaku Panditharatne\nSalem Vance\nSam Blackshear\nSam Broner\nSam Gerstenzang\nSam Ragsdale\nSam Thompson\nSam Williams\nSam Yam\nSamantha Gelt\nSamantha Langford\nSamantha Ludwig\nSamson Wu\nSamuel Arbesman\nSamuel Hammond\nSandra Samayoa\nSandy Jen\nSankaet Pathak\nSantiago Rodriguez\nSara Boesen\nSarah Fazal\nSarah Hamburg\nSarah Lumbard\nSarah Mascardo\nSarah Meiklejohn\nSarah Porter\nSarah Rebello\nSarah Wang\nSasha Stiles\nSatish Talluri\nSaurabh Ladha\nSavannah Cherry\nScott Clark\nScott Duke Kominers\nScott Gottlieb\nScott Hassan\nScott Kupor\nScott Rubin\nScott Shenker\nScott Tyler\nScott Walker\nScott Weiss\nSean Duffy\nSean Neville\nSebastian Oddo\nSeema Amble\nSeemay Chou\nSep Kamvar\nSergiu Pasca\nSeth Lobree\nSeth Sivak\nSeth Sternberg\nShai Bernstein\nShai Kopeld\nShaka Senghor\nShakil Khan\nShan Sinha\nShana Fisher\nShane Mac\nShane Parrish\nShangda Xu\nShannon (Stubo) Brayton\nShannon Barbour\nShannon Kelly\nShannon Schiltz\nShannon Snow\nShari Doherty\nSharon Chang\nShawn Conway\nSheela Krothapalli\nShellye Archambeau\nSherie James\nSherriAnn Cole\nShishir Mehrotra\nShonda Rhimes\nSid Gorham\nSigne Pierce\nSimon Denny\nSiqi Chen\nSonal Chokshi\nSophie Song\nSoubhik Deb\nSpencer Dinwiddie\nSpencer Howard\nSpencer Rascoff\nSreeram Kannan\nSreevidya Kasturil\nSri Kosuri\nSriram Krishnan\nSrivatsan Sridhar\nStacey Cunningham\nStacey Merrick\nStacia Murray\nStacy Brown-Philpot\nStacy D'Amico\nStacy Warner\nStefan McDonough\nSten Tamkivi\nStephane Bancel\nStephanie Anyanwu\nStephanie Cohen\nStephanie Doppelt\nStephanie Smith\nStephanie Watkins\nStephanie Zinn\nStephen Armanios\nStephen Wink\nStephenie Zhang\nSteve Buress\nSteve Cadigan\nSteve Cheney\nSteve Harvey\nSteve Kaczynski\nSteve McDermid\nSteve Smith\nSteve Zhao\nSteven Adair\nSteven Ebert\nSteven Johnson\nSteven Levy\nSteven Sinofsky\nStewart Butterfield\nStina Ehrensvärd\nStuart Luman\nStuart Russell\nSudip Chakrabarti\nSue Hager\nSuhail Doshi\nSukhinder Singh Cassidy\nSumeet Singh\nSumit Shah\nSungMo Park\nSunil Chokshi\nSurya Ganguli\nSusan B. Wilde\nSusan Mernit\nSusan Rice\nSusannah Fox\nSydney Paul\nTaavet Hinrikus\nTaggart Matthiesen\nTamzen Brewis\nTana Billingsley\nTarek Mansour\nTarun Chitra\nTauri Laws Phillips\nTawny Holguin\nTaylor McFadden\nTed Not Lasso\nTed Sarandos\nTed Ullyot\nTerell Sterling\nTerence Carroll\nTeresa Carlson\nTerry Angelos\nTerry Brown\nThan Nguyen\nThanh Nguyen\nThe 2015 Academic Roundtable Sessions\nThe TxO team\nTheresa DeMichele\nTheresa Dilley\nTheresa Fisher\nTheresa Walz\nTheresia Gouw\nThibaut Scholasch\nThomas Gjerde\nThomas Juenger\nThomas Long\nThomas Rando\nTiffany Vo\nTiffany Zhong\nTim Beiko\nTim O'Reilly\nTim Roughgarden\nTim Schafer\nTim Sullivan\nTimmu Tõke\nTina Anderson\nTina Bhatnagar\nTina Ferguson\nTina Wie\ntinawie\nTing Ni\nTobi Lütke\nTodd Cranney\nTodd Lutwak\nTodd McKinnon\nTodd Park\nTodd Young\nTolga Dizdarer\nTom Butta\nTom Coates\nTom Davenport\nTom Ellis\nTom Hammer\nTom Hofmann\nTom Lehman\nTom Mitchell\nTom Preston-Werner\nTom Rikert\nTom Standage\nTomicah Tillemann\nTony Blair\nTony Blinken\nTori Landrum\nTracy Chou\nTracy Young\nTren Griffin\nTrent Mayol\nTrevor Bedford\nTristan Handy\nTristan Walker\nTroy Kirwin\nTugce Erten\nTurner Novak\nTushar Garg\nTyler Cowen\nTyler Wilson\nTyson Clark\nUma Valeti\nUsman Azam\nUzi Dutta\nValentina Marzorati\nValeria Nikolaenko\nValerie Arboleda\nVan Jones\nVan Le-Gray\nVanessa Kropf\nVas Narasimhan\nVaughn Ferguson\nVenkat Mocherla\nVicente De Baca\nVickie Casillas-Smith\nVictor Liang\nVictor Shoup\nVictoria Butcher\nVijay Balasubramaniyan\nVijay Kedar\nVijay Pande\nVineeta Agarwala\nVinod Khosla\nVirginia Postrel\nVishal Amin\nVitalik Buterin\nVivian Brooks\nVoices Onchain\nW. Brian Arthur\nWahab Owolabi\nWei Luo\nWendy Drpic\nWerner Gerola\nWes Taylor\nWhitney Owens\nWill Brown\nWill Wong\nWillem Mulder\nWilliam Gifford\nWilliam Mougayar\nWing Cheng\nXian Zhang\nXiang-Dong Fu\nXingchen Zhou\nYannai A. Gonczarowski\nYehuda Lindell\nYevgeniy Dodis\nYinuo Zhang\nYogi Roth\nYohei Ishii\nYoko Li\nYoni Levy\nYoram Novick\nYuichi Kurosawa\nYujin Chung\nYun Fan\nYung Yung Sheung\nYuval Efron\nYuval Harari\nZac Bookman\nZach Abrams\nZach Cohen\nZach Dicker\nZach Haigney\nZachary Chen\nZachary Gray\nZack Weiner\nZahabiya Gabaji\nZak Doric\nZal Bilimoria\nZane Lackey\nZeta Avarikioti\nZeya Yang\nZooko Wilcox\nZoran Basich\n\nclear all Abigail Johnson\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n12.04.25 / Abigail Johnson and Anthony Albanese\nFidelity CEO on stablecoins, Bitcoin, and innovation bets\nEvery traditional financial institution faces the same dilemma: evolve or fall behind, build or buy. But when safety, predictability, and trust is paramount, how do traditional finance companies innovate? How do they place their innovation bets, and decide what to explore and not to explore? Fidelity Chairman and CEO Abigail P. Johnson shares an inside...\n\ncompany building\nFounders Summits\nTradFi\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":6894,"crawled_at":1791194702588}
+{"id":10425,"url":"https://gov.uniswap.org/t/rfc-stable-application-for-canonical-uniswap-v3-deployment/26080","domain":"gov.uniswap.org","chapter":"governance_daos","title":"[RFC] Stable Application for Canonical Uniswap V3 Deployment - Uncategorized - Uniswap Governance","text":"[RFC] Stable Application for Canonical Uniswap V3 Deployment\n\nUncategorized\n\neduardo-protofire\n\nApril 8, 2026, 10:57pm\n\n1\n\nProposal Summary\n\nThis proposal formally requests that Stable be recognized as a canonical chain within the Uniswap V3 deployment framework. The intent is to acknowledge the already-deployed Uniswap V3 contract suite on Stable, with Stable Swap (swap.stable.xyz) serving as a standalone, actively maintained frontend that routes trades through this deployment. By doing so, the Uniswap DAO would extend canonical coverage to a USDT-native, high-throughput Layer 1 purpose-built for stablecoin payments, while requiring no additional technical work beyond updating the canonical deployments registry.\n\nProposal Stakeholders\n\nProposer: Protofire / website: https://protofire.io / X (Twitter) handle: https://x.com/protofire\n\nDeployer: Protofire\n\nBridge Provider: LayerZero (https://layerzero.network)\n\nAbout Stable\n\nStable is a high-throughput, EVM-compatible Layer 1 “StableChain” purpose-built for USDT and stablecoin settlement. It treats USDT as a native gas asset, enabling gasless transfers, ultra-low fees, and sub-second finality for dollar-denominated transactions.\n\nDesigned as institutional-grade infrastructure, Stable combines predictable performance, regulatory alignment, and dedicated blockspace to support real-world payments, remittances, and high-volume institutional flows. The network targets 10,000+ TPS and provides confidential transfer capabilities tailored to institutional use cases.\n\nKey Attributes\n\nUSDT-native design: USDT as gas, gas-free transfers, and real-dollar settlement optimized for stablecoin flows.\n\nHigh throughput & low latency: Engineered for high-frequency volume with sub-second finality and a roadmap towards 10,000+ TPS.\n\nInstitutional-grade infrastructure: Focus on compliance, predictable performance, dedicated blockspace, and confidential transfers for enterprises, fintechs, and payment providers.\n\nEVM-compatible: Solidity and Ethereum tooling work out-of-the-box, easing Uniswap V3 deployment and integration with existing DeFi infrastructure.\n\nBacked by major ecosystem players: Supported by Bitfinex, Tether, and additional strategic investors, Stable conducted a pre-deposit campaign capped at $1.325 billion.\n\nTarget Audience\n\nStable is targeting:\n\nPayment and remittance providers seeking predictable, low-cost USDT rails for cross-border payments and merchant settlement.\n\nFintechs, neobanks, and PSPs that require compliant, enterprise-grade infrastructure with dedicated blockspace, confidential transfers, and integration-friendly tooling.\n\nDeFi-native users and builders who want to deploy and trade stablecoin-centric strategies (delta-neutral, basis trades, stablecoin LPs) on a chain optimized for USDT liquidity.\n\nEveryday users and merchants who want “cash-like” USDT payments (gasless, sub-second settlement, single-currency UX) without juggling volatile gas tokens.\n\nBridge\n\nLayerZero — https://layerzero.network\n\nSender (Ethereum) — 0x079fbb55a84f68601A15684e6677Ac078C127e75\n\nReceiver (Stable) — 0x505556e173fCDFC0f40e489F341d544C90ac6e6D\n\nLayerZero provides the cross-chain messaging and bridging infrastructure connecting Stable with Ethereum and other Uniswap-relevant ecosystems, enabling secure movement of assets and messages between canonical Uniswap deployments and Stable. This allows liquidity providers and integrators to bridge assets and orchestrate multi-chain strategies while routing trades through the canonical Uniswap V3 deployment on Stable.\n\nBenefits to Uniswap\n\nBy formally recognizing Stable as a canonical Uniswap V3 deployment, the Uniswap DAO gains exposure to a USDT-native, payments-centric Layer 1 that is explicitly designed to scale global stablecoin usage. This deployment can attract new liquidity from payment rails, fintechs, and institutions building on Stable, while preserving Uniswap’s familiar EVM-based integration surface. The combination of gasless USDT transfers, sub-second settlement, and high throughput creates an ideal environment for deep, capital-efficient stablecoin liquidity, reinforcing Uniswap’s position as the default exchange infrastructure for the emerging “stablecoin economy” and extending the protocol’s reach into real-world payments use cases.\n\nStable DEX Environment\n\nStable is being designed first and foremost as rails for real-world money movement, with USDT as the native unit of account and gas asset. Within that context, the DEX layer is expected to support not just retail trading, but institutional-grade DeFi integrations and tokenized yield products that require deep, reliable, and composable liquidity.\n\nStable Swap is the canonical Uniswap deployment on Stable and the default venue for spot liquidity. Its primary role is to act as the base liquidity and routing layer for the ecosystem, with a design focus on:\n\nInstitutional-grade DeFi integrations\n\nStable Swap provides a standardized, battle-tested AMM foundation that institutions, fintechs, and payment-adjacent applications can integrate against with confidence. Predictable execution, transparent pricing, and composability make it suitable for higher-value flows and regulated counterparties.\n\nTokenized yield products and vaults\n\nStable Swap is intended to underpin tokenized yield strategies (e.g., yield-bearing USDT derivatives, vault tokens, structured products) that rely on continuous on-chain liquidity for issuance, redemption, and secondary market trading.\n\nOther DEX deployments on Stable are purpose-built to complement, rather than replace, Stable Swap:\n\nCurve\n\nCurve focuses on tightly-pegged asset swaps, particularly stable-to-stable and yield-bearing stable assets. Its role is to offer ultra-low-slippage execution for specialized pools that benefit from amplification, while composability with Stable Swap enables efficient routing and arbitrage.\n\nSettleX\n\nSettleX targets specialized settlement workflows and advanced execution primitives. It is optimized for bespoke trading and settlement use cases rather than serving as a general-purpose liquidity hub.\n\nFrontend\n\nThis deployment is a standalone instance of Uniswap V3, exposed through a dedicated frontend called Stable Swap, with active maintenance and long-term support from Protofire and the Stable ecosystem. The UI is designed to be the default Uniswap experience on Stable, integrating seamlessly with wallets and payment flows on the chain.\n\nimage2174×1330 125 KB\n\nThe production frontend is live at: https://swap.stable.xyz\n\nSmart Contracts\n\nBelow is a table with all contract addresses.\n\nContract Name\nAddress\n\nv3 Core Factory\n\n0x88F0a512eF09175D456bc9547f914f48C013E4aA\n\nMulticall 2\n\n0x208099D6E8a107aD485CD1374A6EC5Abd98c7F11\n\nProxy Admin\n\n0x51D1E70B8cAbDF4F3aB056475802AB1687b3EA23\n\nTick Lens\n\n0x8dF0D1614aae99352045c62d24d54E72b38111ec\n\nNFT Descriptor Library V1.3.0\n\n0xF7815833076D83161414A46c4E993dC8f22A7ADd\n\nNonfungible Token Position Descriptor V1.3.0\n\n0x7Cf5987951E48ADf235cc9194bCdc708Eb692D82\n\nDescriptor Proxy\n\n0xcd2cD0E139eC5581138E18C6DBB189c53efBAE95\n\nNonfungible Token Position Manager\n\n0x3BdC3437405f7D801b6036532713fc1F179136a6\n\nv3 Migrator\n\n0x2C5f4275F1a278BF328D56CB9db304e915DE3082\n\nv3 Staker\n\n0xA32e3E127FF46db40ab3c4775be97ED760AD7178\n\nQuoter V2\n\n0xb070179E7032CdA868b53e6C1742F80c9e940d1A\n\nSwap Router02\n\n0x32eaf9B5d5F2CD7361c5012890C943D7de84C22a\n\nV2 Core Factory\n\n0x25D2d657F539F2bB16eC82773cBE5ee49ddD3c69\n\nUniswap V2 Router02\n\n0xa571dc7c4f2369F1cA24D3a7E8a35c07Ff52bfC0\n\nPermit2\n\n0x000000000022D473030F116dDEE9F6B43aC78BA3\n\nUniversal Router\n\n0x5Be52b52f3d1dbC324d2959637471a4208626144\n\nTimeline\n\nThis deployment is already live, fully operational, and actively maintained: the core Uniswap V3 contracts are deployed on Stable, routing through the Stable Swap frontend, with bridge connectivity via LayerZero and an ongoing commitment from Protofire and ecosystem partners to sustain and grow usage over time.\n\n1 Like\n\npennblockchain\n\nApril 24, 2026, 8:09pm\n\n2\n\nWe agree with making Stable canonical. That being said, we feel a lot of the metrics backing this are missing from the proposal. We were wondering if there were any KPIs of this canonical proposal, past achievements, or metrics of its current deployment?\n\nAbdullahUmar\n\nApril 30, 2026, 5:08pm\n\n3\n\nAlthough the latest UC term has concluded, the deployment efforts pertaining to the Stable deployment began in Q4 of last year. We are therefore concluding that process now.\n\nThis proposal has successfully completed the approval period, canonicalizing the associated contracts as the official deployments on Stable. The contracts are verified, and ownership of the factory contracts have been successfully transferred to Uniswap governacne. The UC will update registries in accordance with this approval.\n\n1 Like\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[RFC] Flow Application for Canonical Uniswap V3 Deployment\n\nUncategorized\n\n1\n\n258\n\nNovember 14, 2025\n\n[RFC] Lens Chain Application for Canonical Uniswap V3 Deployment\n\nRequests for Comment\n\n1\n\n256\n\nAugust 27, 2025\n\n[RFC] Apply canonical Uniswap V3 deployment on World Chain\n\nRequests for Comment\n\n5\n\n571\n\nOctober 9, 2024\n\nProposal to deploy Uniswap V3 on Plasma\n\nRequests for Comment\n\n1\n\n1061\n\nSeptember 23, 2025\n\nZERO Application for Canonical Uniswap V3 Deployment\n\nUncategorized\n\n1\n\n347\n\nNovember 21, 2024","tokens":2344,"crawled_at":1791194712569}
+{"id":10426,"url":"https://docs.sui.io/sui-stack/mvr/move-registry","domain":"docs.sui.io","chapter":"layer1_layer2","title":"What is the Move Registry? | Sui Documentation","text":"MoveMoveAn open source programming language used for all activity on Sui. Registry (MVR, pronounced mover) provides a uniform naming service for interacting and building with packagesPackageSmart contracts on Sui. from the Sui ecosystem. You can reference packages by their names, and MVR resolves the package addressAddressA unique, anonymous identity on a blockchain network. for you, regardless of network.\n\nYou can access the front end of the Move Registry online at https://www.moveregistry.com/apps.\n\nUse MVR to:\n\nReference both packages and types by name in programmable transaction blocksProgrammable transaction blocksDefine all user transactions on Sui. (PTBs).\n\nDepend on other packages when developing with Move.\n\nAdditionally, MVR can help you manage package versioning. With MVR, you call a specific version of a package without having to resolve the addresses yourself. You also do not need to worry about the package being updated, because if you use a name without a specified version, MVR automatically defaults to the latest version available.\n\ninfo\nMVR default service currently supports MainnetMainnetProduction network for live transactions and real-value assets. and TestnetTestnetStaging network for testing changes before production deployment. networks.\n\nDesign​\n\nPackageInfo registration: Exists independently on each network.\n\nMVR registration: A single source of truth located on Mainnet.\n\nThe following diagram shows the MVR design at a high level.\n\nPackageInfo objects​\n\nThe first step when publishing a package is to register its metadata objectObjectThe basic unit of storage on Sui.. This metadata object serves as a key source of information for:\n\nLocating the source code across different versions of the package.\n\n(Future) Providing text-based metadata (title, description, tags) for the package, which the MVR search engine can use.\n\nThis metadata object can be reused when authorizing any package upgrades to supply source information for the new version. Sui indexers can index the metadata as it cannot be stored within another object.\n\nSee Managing Package Metadata for examples of working with PackageInfo objects.\n\nMVR name​\n\nA MVR name consists of a SuiNS name and a package name, in the format <suins_name>/<pkg_name>. For example, if your SuiNS name is myname.sui, and your package name is mypackage, the MVR name can be @myname/mypackage or myname.sui/mypackage.\n\nThe MVR standard supports an optional /<version> that allows you to specify which onchain version to resolve to. For example, if your MVR name is @myname/mypackage and there are multiple versions of the package, you can specify @myname/mypackage/2 to use version 2.\n\nMVR registration​\n\nMVR registration is separate from the PackageInfo registration process. This separation is necessary because the PackageInfo object acts as both the source of truth for package metadata and a proof of package ownership, whereas MVR registers applications that MVR tooling can resolve.\n\nTo register a package:\n\nUsing your SuiNS name, register an application.\n\nBased on the network, associate the application name with a PackageInfo object:\n\nMainnet: Associate the application name with a complete PackageInfo object, which provides the full metadata and ownership proof.\n\nOther networks: Associate the application name with the PackageInfo object ID, acting as a pointer without ensuring a full mapping.\n\ninfo\nThe registry that stores name resolution for MVR exists only on Mainnet.\n\nSee Managing MVR Names for examples of MVR registration.\n\nDevelopment status​\n\nMVR is currently in beta.\n\nSource code​\n\nThe open source code for MVR is located within both the Sui and MVR repositories on GitHub.\n\nThe MVR repository houses the MVR-CLI and MVR web app code.\n\nSui repository houses the MVR GraphQL code.\n\nThe TypeScript SDK repository houses the MVR plugin for Sui TypeScript SDK and MVR static tool.\n\nRelated topics\n\nManaging Package Metadata\nCreate and manage PackageInfo objects, add source code information, and configure reverse resolution for your Move packages in the Move Registry.\nManaging MVR Names\nCreate applications, set metadata, and attach packages to MVR names across Mainnet and other networks using the Move Registry.\n\nDesign\nPackageInfo objects\nMVR name\nMVR registration\nDevelopment statusSource code\n\nWas this page helpful?","tokens":1085,"crawled_at":1791194716685}
+{"id":10427,"url":"https://docs.ethena.fi/overview/how-usde-works","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"How USDe Works | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nHow USDe Maintains Its Intended Peg\nUSDe derives its relative peg stability from holding a diversified portfolio of backing assets and hedging the price-change risk of any volatile holdings. Volatile assets, such as spot crypto, tokenized equities, and tokenised commodities, are paired with corresponding short futures positions in approximately the same notional size, so that movements in the value of the spot asset are generally offset by movements in the value of the hedge.\nStable assets held within the portfolio - liquid stablecoins and short-duration real-world assets - already hold a stable dollar value and require no hedge. The combined position is a delta-neutral backing whose synthetic dollar value remains relatively stable across most market conditions.\nThis delta-neutral construction is what allows USDe to be backed by productive assets while maintaining a relatively stable value with reference to the dollar.\nsUSDe\nsUSDe is the staked form of USDe and the protocol's dollar savings asset. By staking USDe, holders are eligible to receive incentive reward distributions. As rewards accrue to the staking contract, the USDe value of sUSDe increases over time, with no further action required by the holder. sUSDe accrues only positive or flat rewards - periods of negative protocol revenue are absorbed by the Reserve Fund, during which period no incentive rewards would typically be paid.\nMinting Example\n\nA whitelisted user provides ~$100 of USDT and receives ~100 newly-minted USDe atomically in return less the gas & execution costs to execute the hedge.\n\nSlippage & execution fees are included in the price when minting & redeeming. Ethena earns no profit from the minting or redeeming of USDe.\n\nThe protocol opens a corresponding short perpetual position for the approximate same notional dollar value on a derivatives exchange.\n\nThe backing assets are transferred directly to an \"Off Exchange Settlement\" solution. Backing assets remain onchain and custodied by off exchange service providers to minimize counterparty risk.\n\nEthena delegates, but never transfers custody of, backing assets to derivatives exchanges to margin the short perpetual hedging positions.\n\nLast updated 2 months ago\nWas this helpful?","tokens":583,"crawled_at":1791194716708}
+{"id":10428,"url":"https://docs.ethena.fi/backing-assets/liquid-stablecoins","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Liquid Stablecoins | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nThe protocol holds a portion of its backing in liquid, fiat-referenced stablecoins - such as USDC, USDT, and USDtb - that already maintain a stable dollar value using fiat (and equivalent) reserves and therefore do not require a derivatives hedge.\nLiquid stablecoins serve several functions in the backing portfolio. They support the protocol's ability to manage on-demand redemptions, allowing whitelisted counterparties to redeem USDe without the protocol needing to unwind hedged positions in order to source liquidity.\nLiquid stablecoins also act as a safeguard during periods when perpetual funding rates and futures basis are suboptimal, allowing the protocol to reduce hedged exposure while preserving stable backing.\nThe allocation to liquid stablecoins is dynamic. It is increased or decreased in response to redemption patterns, market conditions, and the relative attractiveness of other backing strategies. Depending on where they are held, certain liquid stablecoins may earn rewards - for example, rewards available on USDC - which can contribute to overall protocol revenue.\n\nLast updated 3 months ago\nWas this helpful?","tokens":307,"crawled_at":1791194736254}
+{"id":10429,"url":"https://docs.sui.io/sui-stack/mvr/managing-package-info","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Managing Package Metadata | Sui Documentation","text":"caution\nThe TypeScript examples assume that you use the MVR plugin for the Sui TypeScript SDK. The Sui CLI examples do not use the MVR plugin.\n\nCreate a new PackageInfo objectObjectThe basic unit of storage on Sui.​\n\nYou should create a PackageInfo object for your packagePackageSmart contracts on Sui. when you first deploy it, once for each network. You can then treat the object as the source of truth for metadata of your package.\n\nThe following example works for both MainnetMainnetProduction network for live transactions and real-value assets. and TestnetTestnetStaging network for testing changes before production deployment..\n\nTypeScript\nSui CLI\nconst transaction = new Transaction();\n// ... (other code, could also include a `transaction.publish()`\n// call to publish and register in one step.)\n\n/// Pass in the UpgradeCap\nconst packageInfo = transaction.moveCall({\ntarget: `@mvr/metadata::package_info::new`,\narguments: [transaction.object('<Your UpgradeCap (by value or object id)>')],\n});\n\n// Also create the visual representation of the \"info\" object.\n// You can also call `@mvr/metadata::display::new` instead,\n// that allows customizing the colors of your metadata object.\nconst display = transaction.moveCall({\ntarget: `@mvr/metadata::display::default`,\narguments: [\ntransaction.pure.string('<Add a name to easily identify your package. This is not your MVR name.>') // Example: core\n],\n});\n\n// Set the display object to the info object.\ntransaction.moveCall({\ntarget: `@mvr/metadata::package_info::set_display`,\narguments: [transaction.object(packageInfo), display],\n});\n\n// Set the default for the packageInfo, which enables reverse resolution for that network\n// See details in reverse resolution section\ntransaction.moveCall({\ntarget: \"@mvr/metadata::package_info::set_metadata\",\narguments: [\ntransaction.object(packageInfo),\ntransaction.pure.string(\"default\"),\ntransaction.pure.string(\"<MVR name>\"), // Example: @suins/core or suins.sui/core\n],\n});\n\n// Optionally unset the metadata for the packageInfo\n// transaction.moveCall({\n// target: \"@mvr/metadata::package_info::unset_metadata\",\n// arguments: [\n// transaction.object(packageInfo),\n// transaction.pure.string(\"default\"),\n// ],\n// });\n\n// transfer the `PackageInfo` object to a safe address.\ntransaction.moveCall({\ntarget: `@mvr/metadata::package_info::transfer`,\narguments: [transaction.object(packageInfo), transaction.pure.address('<Your safe address>')],\n});\n\n// .. you can do any other actions, like setting the source code info, in the same PTB.\n\nsui client ptb \\\n--move-call @mvr/metadata::package_info::new @<Upgrade cap id or value> --assign packageinfo \\\n--move-call @mvr/metadata::display::default \\\"sample\\\" --assign display \\\n--move-call @mvr/metadata::package_info::set_display packageinfo display \\\n--move-call @mvr/metadata::package_info::set_metadata packageinfo \\\"default\\\" \\\"<MVR name>\\\" \\\n--move-call sui::tx_context::sender --assign sender \\\n--move-call @mvr/metadata::package_info::transfer packageinfo sender\n\nReverse resolution​\n\nReverse resolution allows you to look up the human-readable name (like @suins/core or suins.sui/core) associated with a given package ID, regardless of which version of the package you have. This is useful for identifying and verifying packages onchain, especially when working with tools or interfaces that reference package IDs directly.\n\nTo accomplish this you can add a default on a PackageInfo object (see previous example), but it needs to match what that MVR name points to in order to resolve.\n\nExample of reverse resolution:\n\ncurl --location 'https://mainnet.mvr.mystenlabs.com/v1/reverse-resolution/bulk' \\\n--header 'Content-Type: application/json' \\\n--data '{\n\"package_ids\": [\n\"0x2c8d603bc51326b8c13cef9dd07031a408a48dddb541963357661df5d3204809\",\n\"0x00c2f85e07181b90c140b15c5ce27d863f93c4d9159d2a4e7bdaeb40e286d6f5\"\n]\n}'\n\nOutput:\n\n{\n\"resolution\": {\n\"0x00c2f85e07181b90c140b15c5ce27d863f93c4d9159d2a4e7bdaeb40e286d6f5\": {\n\"name\": \"@suins/core\"\n},\n\"0x2c8d603bc51326b8c13cef9dd07031a408a48dddb541963357661df5d3204809\": {\n\"name\": \"@deepbook/core\"\n}\n}\n}\n\nAdd source code information​\n\nYou can add source code information on your PackageInfo object using the following setup.\n\nTo update the source for a version, first call @mvr/metadata::package_info::unset_git_versioning to remove the existing information.\n\nTypeScript\nSui CLI\nconst transaction = new Transaction();\n// adding source code info:\n\n// 1. Create the `GitInfo` object.\nconst git = transaction.moveCall({\ntarget: `@mvr/metadata::git::new`,\narguments: [\ntransaction.pure.string('<Your git repository, for example `https://github.com/mystenlabs/mvr`>'),\ntransaction.pure.string('<Your git subdirectory, for example `packages/mvr`>'),\ntransaction.pure.string('<Your git commit hash or tag, for example `636d22d6bc4195afec9a1c0a8563b61fc813acfc`>'),\n],\n});\n\ntransaction.moveCall({\ntarget: `@mvr/metadata::package_info::set_git_versioning`,\narguments: [\ntransaction.object(`<Your PackageInfo object>`),\ntransaction.pure.u64(`<The version number for the given source code (for example 1)>`),\ngit,\n],\n});\n\nsui client ptb --move-call @mvr/metadata::git::new \\\n\"\\\"<Your git repository, for example https://github.com/mystenlabs/mvr>\\\"\" \\\n\\\"<Your git subdirectory, for example packages/mvr>\\\" \\\n\\\"<Your git commit hash or tag, for example 636d22d6bc4195afec9a1c0a8563b61fc813acfc>\\\" --assign git \\\n--move-call @mvr/metadata::package_info::set_git_versioning @<Your PackageInfo object> \\\n<The version number for the given source code (for example 1)> git\n\nRemove or update source code information​\n\nTypeScript\nSui CLI\nconst transaction = new Transaction();\n\ntransaction.moveCall({\ntarget: `@mvr/metadata::package_info::unset_git_versioning`,\narguments: [\ntransaction.object(`<Your PackageInfo object>`),\ntransaction.pure.u64(`<The version number for the given source code (for example 1)>`),\n],\n});\n// .. you could then follow the previous steps to add the new source code info for that version.\n\nsui client ptb \\\n--move-call @mvr/metadata::package_info::unset_git_versioning @<Your PackageInfo object> <Version number>\n\nTransferTransferChanging the owner of an asset. the PackageInfo object​\n\nYou can transfer the PackageInfo object to another addressAddressA unique, anonymous identity on a blockchain network. (or object) by the following setup. If you want to build custom access control for your object, you can utilize a transfer to object workflow (see Transfer to Object on the Sui documentation site for more information).\n\nPackageInfo does not allow public transfers, to ensure that the object is always indexable (wrapping could hurt the discoverability of the object).\n\nRelated topics\n\nTransfer to Object\nOn Sui, you can transfer objects to objects in the same way you can transfer objects to addresses.\n\nTypeScript\nSui CLI\nconst transaction = new Transaction();\n\n// transfer the `PackageInfo` object to a safe address.\ntransaction.moveCall({\ntarget: `@mvr/metadata::package_info::transfer`,\narguments: [transaction.object(packageInfo), transaction.pure.address('<Your safe address>')],\n});\n\nsui client ptb --transfer-objects \"[@<packageInfo>]\" @<Your safe address>\n\nCreate a new PackageInfo object\nReverse resolution\nAdd source code information\nRemove or update source code information\nTransfer the PackageInfo object\n\nWas this page helpful?","tokens":1836,"crawled_at":1791194737617}
+{"id":10430,"url":"https://gov.uniswap.org/t/tally-is-shutting-down-option-to-maintain-the-existing-interface-no-contract-changes/26082","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Tally Is Shutting Down — Option to Maintain the Existing Interface (No Contract Changes) - Requests for Comment - Uniswap Governance","text":"Tally Is Shutting Down — Option to Maintain the Existing Interface (No Contract Changes)\n\nRequests for Comment\n\nDavidLen\n\nApril 13, 2026, 6:05pm\n\n1\n\nHi delegates and community members,\n\nI’m David Len. My team and I built and maintained the governance Discourse layer used by Aave and 10+ DAOs. Given Tally’s shutdown, we’re exploring a path to keep a familiar governance interface available for DAOs that rely on it.\n\nProposal We are prepared to host and maintain Tally Zero — Tally’s open-source governance client — preserving the existing frontend experience without requiring contract changes or migrations. No relearning of the platform.\n\nWhat this means\n\nContinued access to a familiar governance UI\n\nNo changes to existing governance contracts\n\nMinimal disruption to current delegate workflows\n\nSustainability & security\n\nWe have operated governance infrastructure across 10+ DAOs on a lean model\n\nWe are pursuing grant funding to cover audit costs and will publish a transparent cost structure before any DAO commits to anything\n\nWhy we’re working on this\n\nExisting DAO governance flows depend on accessible interfaces\n\nSignal request (non-binding) If your DAO would consider using a maintained version of Tally Zero, a simple reply or indication of interest helps us quantify demand. This costs you nothing and keeps the governance running without disruption.\n\nHappy to share more details or walk through the architecture.\n\n— David Len\n\n1 Like\n\nSem_pre\n\nApril 20, 2026, 1:03pm\n\n2\n\nThe interface continuity question is the right one to solve first. What’s less visible is the analytics layer that sat on top of Tally — delegate tracking, participation history, governance health signals. That’s the gap that opens up alongside the UI question. Happy to share what we’re seeing across the DAOs we track if it’s useful context for the proposal.\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[RFC] - Supporting Tally’s Continued Development and Enhancements for Uniswap DAO Governance\n\nRequests for Comment\n\n44\n\n1718\n\nDecember 17, 2024\n\nTally Uniswap Communication thread\n\nService Providers\n\n14\n\n787\n\nApril 3, 2026\n\nDhive - governance data tooling\n\nGovernance-Meta\n\n2\n\n204\n\nOctober 14, 2024\n\n[RFC] - Deploy a DeepDAO Pro Dashboard for Uniswap\n\nUncategorized\n\n6\n\n302\n\nJanuary 30, 2025\n\nDeepDAO Pro: A Breakthrough in DAO Analytics\n\nUncategorized\n\n1\n\n239\n\nMay 27, 2025","tokens":593,"crawled_at":1791194749593}
+{"id":10431,"url":"https://www.getfoundry.sh/cast/token-approvals","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Token Approvals – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nToken Approvals\n\nAn ERC-20 allowance authorizes a spender to use tokens owned by your account. You can set it with cast erc20 approve, or sign an ERC-2612 permit with cast erc20 permit when the token supports that extension. erc20 is an alias for erc20-token.\n\nA permit signature authorizes an allowance change. It does not transfer tokens, deposit into a vault, or change the allowance until someone submits it to the token contract.\n\nBefore you start\n\nSet TOKEN, SPENDER, and RPC_URL for the token, the contract that will spend it, and its chain. Set AMOUNT in the token's smallest unit. Set DEADLINE to an absolute Unix timestamp in seconds; it is the last time the permit may be submitted, not an expiry for the resulting allowance. The examples use PRIVATE_KEY for the token owner and RELAYER_PRIVATE_KEY for a relayer. You can instead select a keystore with --account or use the wallet options in Sending transactions.\n\nApprove with a transaction\n\nYou can use ordinary approval even when a token supports permits:\n\n$ cast erc20 approve \"$TOKEN\" \"$SPENDER\" \"$AMOUNT\" --private-key \"$PRIVATE_KEY\" --rpc-url \"$RPC_URL\"\n\nThis sends a transaction and sets the allowance directly.\n\nSign a permit for an integration\n\nGenerate a signature and calldata without broadcasting:\n\n$ cast erc20 permit \"$TOKEN\" \"$SPENDER\" \"$AMOUNT\" --deadline \"$DEADLINE\" \\\n--private-key \"$PRIVATE_KEY\" --rpc-url \"$RPC_URL\" --json > permit.json\n\nThe signing wallet is the owner. Cast reads nonces(owner) from the token and constructs the standard ERC-2612 Permit message. You do not supply the transaction nonce as the permit nonce.\n\nWithout --json, stdout contains a 65-byte signature encoded as hex in r || s || v order. JSON output uses the Foundry envelope: .data contains token, owner, spender, decimal strings for value, nonce, and deadline, plus signature, calldata, and typed_data.\n\nAn integration can use the signature in its permit-and-action transaction. Alternatively, a relayer can submit the calldata directly to the token:\n\n$ cast send \"$TOKEN\" --data \"$(jq -r '.data.calldata' permit.json)\" \\\n--private-key \"$RELAYER_PRIVATE_KEY\" --rpc-url \"$RPC_URL\"\n\nThe relayer pays the transaction fee. The permit still authorizes only the spender and amount you signed. After the permit is accepted, its nonce is consumed and the same signature cannot be used again. Another permit submitted for that owner before yours may make your signature stale.\n\nBroadcast from the signing wallet\n\nTo sign and submit the permit in one command, add --broadcast:\n\n$ cast erc20 permit \"$TOKEN\" \"$SPENDER\" \"$AMOUNT\" --deadline \"$DEADLINE\" \\\n--private-key \"$PRIVATE_KEY\" --rpc-url \"$RPC_URL\" --broadcast\n\nThis prints the transaction receipt. Add --async to print the transaction hash without waiting for the receipt. Broadcasting a permit and then sending a separate deposit still takes two transactions.\n\nVerify the allowance\n\nAfter the permit transaction is confirmed, query the resulting allowance:\n\n$ cast erc20 allowance \"$TOKEN\" \"$OWNER\" \"$SPENDER\" --rpc-url \"$RPC_URL\"\n\nDomain discovery and compatibility\n\nCast uses EIP-5267 eip712Domain() when the token exposes it, including optional domain fields and salt. It rejects unsupported domain extensions. Otherwise it constructs the common domain using name(), version \"1\", the RPC chain ID, and the token address.\n\nIf the token uses a different domain name or version, supply --domain-name or --domain-version. Cast checks the constructed domain against the token's DOMAIN_SEPARATOR() before asking the wallet to sign. A mismatch is an error; an override does not bypass verification. A discovered chain ID or verifying contract must also match the RPC chain or token address when present.\n\nThis command supports standard ERC-2612 permits. DAI-style permits and Uniswap Permit2 use different signing formats and are not supported by this helper.\n\nPermits and vault deposits\n\nFor an ERC-4626 deposit, the vault spends your underlying asset. A direct deposit therefore needs an allowance on that asset with the vault as spender. The vault's own permit, if implemented, approves spending vault shares and does not approve the underlying asset.\n\nRouter or bundler integrations may require a different spender and can combine permit submission with a deposit in one transaction. Use the integration's specified spender and transaction format. This command produces a standard permit; it does not build a Morpho or other protocol's bundled deposit transaction.\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":1142,"crawled_at":1791194751285}
+{"id":10432,"url":"https://docs.ethena.fi/protocol-overview/rewards-mechanism","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Rewards Mechanism | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nContext\nUsers are able to accrue fully discretionary incentive rewards by staking their USDe and receiving sUSDe atomically in return.\n\nOnce users stake their USDe for sUSDe, they begin to accrue rewards, to the extent provided, without any further action or cost. USDe that is staked is not rehypothecated in any way to generate returns.\n\nOverview\nThe amount of sUSDe a user receives is determined by how much USDe was transferred as well as when it was transferred. Ethena's sUSDe utilizes a reward-bearing \"Token Vault\" mechanism, the same as Rocketpool's rETH or Binance's WBETH.\nThe protocol does not rehypothecate, lend out, or otherwise utilize deposited USDe for any purpose. There is no need for any such action, as the USDe backing mechanic inherently creates value in the system.\nThis mechanism simply enables Ethena to provide rewards to ecosystem participants without users having to do any action to \"earn\" it. The USDe value of sUSDe grows on its own. When a user unstakes his or her USDe, the user receives an amount of USDe equal to the initial amount staked plus their share of rewards deposited in the staking contract as rewards while that user's USDe was staked, as reflected in the USDe value increase of sUSDe.\nImportant Notes\n\nThe amount of sUSDe you receive when you stake USDe is likely to be less in number, but valued at the equivalent amount of USDe. This is a result of the \"Token Vault\" mechanism and the ratio defined below in the worked example.\n\nThe value of USDe will remain worth the market trading price of USDe while sUSDe will grow in USDe value as the protocol (via a subsidiary of the Ethena Foundation) deposits discretionary rewards in the staking contract.\n\nIf the protocol were to suffer a loss due to funding or another reason, Ethena's Reserve Fund is intended to bear the cost, rather than the staking contract.\n\nsUSDe can only accrue positive or flat rewards while staking USDe; periods of negative protocol revenue are not passed on to sUSDe. During such periods, no discretionary rewards will be provided.\n\nCalculation & Worked Example\nsUSDe:USDe ratio = (total sUSDe supply) / (total USDe staked + total protocol revenue deposited in USDe terms)@c\n\nsUSDe Rewards Mechanism\nThe Ethena Foundation, via a subsidiary, calculates APY weekly as part of internal accounting when distributing rewards to the StakingRewardsDistributor contract.\nTo prevent lumpy distributions which people can arbitrage, and because its not currently feasible for Ethena to distribute more frequently than weekly, sUSDe rewards are distributed the week after the period to which they relate, in multiple smaller payments throughout the week. In that period, the USDe supply can increase or decrease, as can the % of USDe supply staked.\nThis can cause distortions between the APY published, and a number that's just based on the most recent 8 hourly payment to sUSDe, as seen on some data aggregator sites.\nEthena's APY is also annualized with weekly compounding reflecting the compounding interval users actually experience.\n\nLast updated 2 months ago\nWas this helpful?","tokens":797,"crawled_at":1791195621486}
+{"id":10433,"url":"https://docs.sui.io/operators/validator","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Sui Validators | Sui Documentation","text":"Sui uses a delegated proof-of-stakeDPoSConsensus mechanism used by Sui. model where validators process transactions and maintain network consensusConsensusThe process by which the majority of nodes agree on the current state of the network. These guides cover validatorValidatorResponsible for executing tasks like staking, gas price references, and tallying rules. configuration, committee management, rewards, and operational best practices.\n\nDeployment and Configuration\nLearn how to set up, configure, and manage a Sui validator node.\n→\nManagement\nLearn the processes you need to perform to ensure your validator nodes are always optimized.\n→\nTools\nUse the Sui CLI to interact with a full node's validator commands.\n→\nRewards\nLearn how Sui calculates and distributes validator and staker rewards.\n→\nAlert Reference\nA collection of the Prometheus Alertmanager rules that trigger alerts and warnings on Validator and Full nodes.\n→","tokens":233,"crawled_at":1791194758303}
+{"id":10434,"url":"https://www.metaplex.com/docs/smart-contracts/core/plugins/attribute","domain":"www.metaplex.com","chapter":"docs","title":"Attribute Plugin | Metaplex Core","text":"The Attributes Plugin stores key-value pairs directly on-chain within Core Assets or Collections. Perfect for game stats, traits, and any data that on-chain programs need to read.\nWhat You'll Learn\nAdd on-chain attributes to Assets and Collections\nStore and update key-value pairs\nRead attributes from on-chain programs\nUse cases: game stats, traits, access levels\n\nSummary\nThe Attributes Plugin is an Authority Managed plugin that stores key-value string pairs on-chain. Unlike off-chain metadata, these attributes are readable by Solana programs and indexed by DAS.\nStore any string key-value pairs on-chain\nReadable by on-chain programs via CPI\nAutomatically indexed by DAS for fast queries\nMutable by the update authority\nOut of Scope\nOff-chain metadata attributes (stored in JSON at URI), complex data types (only strings supported), and immutable attributes (all attributes are mutable).\nQuick Start\nJump to: Add to Asset · Update Attributes\nAdd the Attributes plugin: addPlugin(umi, { asset, plugin: { type: 'Attributes', attributeList: [...] } })\nEach attribute is a { key: string, value: string } pair\nUpdate anytime with updatePlugin()\nQuery via DAS or fetch on-chain\nOn-Chain vs Off-Chain Attributes\nFeatureOn-Chain (this plugin)Off-Chain (JSON metadata)\nStorage location\nSolana account\nArweave/IPFS\n\nReadable by programs\n✅ Yes (CPI)\n❌ No\n\nIndexed by DAS\n✅ Yes\n✅ Yes\n\nMutable\n✅ Yes\nDepends on storage\n\nCost\nRent (recoverable)\nUpload cost (one-time)\n\nBest for\nDynamic data, game stats\nStatic traits, images\n\nUse on-chain attributes when programs need to read the data or it changes frequently.\n\nUse off-chain metadata for static traits and image references.\n\nCommon Use Cases\nGame character stats: Health, XP, level, class - data that changes during gameplay\nAccess control: Tier, role, permissions - data programs check for authorization\nDynamic traits: Evolving NFTs where traits change based on actions\nStaking state: Track staking status, rewards earned, time staked\nAchievement tracking: Badges, milestones, completion status\nRental/lending: Track rental periods, borrower info, return dates\nWorks With\n\nMPL Core Asset\n✅\n\nMPL Core Collection\n✅\n\nArguments\nArgValue\nattributeList\nArray<{key: string, value: string}>\n\nAttributeList\nThe attribute list consists of an Array[] then an object of key-value pairs {key: \"value\"} string value pairs.\nAttributeList\n\nconst attributeList = [\n\n{ key: 'key0', value: 'value0' },\n\n{ key: 'key1', value: 'value1' },\n\n]\n\nAdding the Attributes Plugin to an Asset\nAdding a Attribute Plugin to an MPL Core Asset\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { addPlugin } from '@metaplex-foundation/mpl-core'\n\nconst asset = publicKey('11111111111111111111111111111111')\n\nawait addPlugin(umi, {\n\nasset: asset.publicKey,\n\nplugin: {\n\ntype: 'Attributes',\n\nattributeList: [\n\n{ key: 'key0', value: 'value0' },\n\n{ key: 'key1', value: 'value1' },\n\n],\n\n},\n\n}).sendAndConfirm(umi)\n\nUpdating the Attributes Plugin on an Asset\nUpdating the Attributes Plugin on an Asset\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { updatePlugin } from '@metaplex-foundation/mpl-core'\n\nconst assetAddress = publicKey('11111111111111111111111111111111')\n\nawait updatePlugin(umi, {\n\nasset: assetAddress,\n\nplugin: {\n\ntype: 'Attributes',\n\nattributeList: [\n\n{ key: 'key0', value: 'value0' },\n\n{ key: 'key1', value: 'value1' },\n\n],\n\n},\n\n}).sendAndConfirm(umi)\n\nCommon Errors\nAuthority mismatch\nOnly the plugin authority (usually update authority) can add or update attributes. Verify you're signing with the correct keypair.\nString too long\nAttribute keys and values are limited in size. Keep them concise.\nNotes\nAuthority Managed: update authority can add/update without owner signature\nAll values are strings - convert numbers/booleans as needed\nUpdating replaces the entire attribute list (no partial updates)\nAttributes increase account size and rent cost\nDAS indexes attributes for fast queries\nQuick Reference\nMinimum Code\nminimal-attributes.ts\nimport { addPlugin } from '@metaplex-foundation/mpl-core'\n\nawait addPlugin(umi, {\n\nasset: assetAddress,\n\nplugin: {\n\ntype: 'Attributes',\n\nattributeList: [\n\n{ key: 'level', value: '5' },\n\n{ key: 'class', value: 'warrior' },\n\n],\n\n},\n\n}).sendAndConfirm(umi)\n\nCommon Attribute Patterns\nUse CaseExample Keys\nGame character\nlevel, health, xp, class\n\nAccess control\ntier, access_level, role\n\nTraits\nbackground, eyes, rarity\n\nState\nstaked, listed, locked\n\nFAQ\nWhat's the difference between on-chain attributes and off-chain metadata attributes?\nOn-chain attributes (this plugin) are stored on Solana and readable by programs. Off-chain attributes (in JSON at URI) are stored on Arweave/IPFS and only readable by clients.\nCan on-chain programs read these attributes?\nYes. Use CPI to fetch the Asset account and deserialize the Attributes plugin data.\nAre attributes indexed by DAS?\nYes. DAS automatically indexes attribute key-value pairs for fast queries.\nCan I store numbers or booleans?\nValues are strings only. Convert as needed: { key: 'level', value: '5' }, { key: 'active', value: 'true' }.\nHow do I update a single attribute?\nYou can't update individual attributes. Fetch the current list, modify it, and update with the full new list.\nWhat's the size limit for attributes?\nThere's no hard limit, but larger attribute lists increase rent cost. Keep data concise.\nCan the owner update attributes?\nNo. The Attributes plugin is Authority Managed, so only the update authority can modify it (not the owner).\nRelated Plugins\nUpdate Delegate - Grant others permission to update attributes\nImmutableMetadata - Lock name/URI (attributes remain mutable)\nAddBlocker - Prevent adding new plugins\nGlossary\nTermDefinition\nAttributes Plugin\nAuthority Managed plugin storing on-chain key-value pairs\n\nattributeList\nArray of { key, value } objects\n\nAuthority Managed\nPlugin type controlled by update authority\n\nOn-chain Data\nData stored directly in Solana account (readable by programs)\n\nDAS\nDigital Asset Standard API that indexes attributes","tokens":1505,"crawled_at":1791194786036}
+{"id":10435,"url":"https://www.getfoundry.sh/cast/wallet-operations","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Wallet operations – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nWallet operations\n\nCast provides wallet utilities for key generation, signing, and verification.\n\nCreating wallets\n\n$ cast wallet new\n\n$ cast wallet new --number 5\n\n$ cast wallet derive \"abandon abandon ... about\"\n\n$ cast wallet private-key \"abandon abandon ... about\" 2\n\nKeystore management\n\nCreate a keystore\n$ cast wallet import my-key --interactive\n\nEnter your private key when prompted, then set a password.\n\nList keystores\n$ cast wallet list\n\nGet address from keystore\n$ cast wallet address --keystore ~/.foundry/keystores/my-key\n\nSigning messages\n\n$ cast wallet sign \"Hello, Ethereum!\" --private-key $KEY\n\n$ cast wallet sign \"Hello, Ethereum!\" --keystore ~/.foundry/keystores/my-key\n\n$ cast wallet sign \"Hello, Ethereum!\" --browser\n\n$ cast wallet sign --no-hash $HASH --private-key $KEY\n\nEIP-712 typed data\n\nSign structured data according to EIP-712:\n\n$ cast wallet sign --data '{\n\"types\": {\n\"EIP712Domain\": [\n{\"name\": \"name\", \"type\": \"string\"},\n{\"name\": \"version\", \"type\": \"string\"},\n{\"name\": \"chainId\", \"type\": \"uint256\"}\n],\n\"Mail\": [\n{\"name\": \"from\", \"type\": \"address\"},\n{\"name\": \"to\", \"type\": \"address\"},\n{\"name\": \"contents\", \"type\": \"string\"}\n]\n},\n\"primaryType\": \"Mail\",\n\"domain\": {\n\"name\": \"Ether Mail\",\n\"version\": \"1\",\n\"chainId\": 1\n},\n\"message\": {\n\"from\": \"0xCD2a3d9F938E13CD947Ec05AbC7FE734Df8DD826\",\n\"to\": \"0xbBbBBBBbbBBBbbbBbbBbbbbBBbBbbbbBbBbbBBbB\",\n\"contents\": \"Hello, Bob!\"\n}\n}' --private-key $KEY\n\nUse --browser instead of a private-key option to sign the typed data with an injected browser wallet. Browser wallets support personal-message and EIP-712 signing, but not raw-hash signing with --no-hash.\n\nVerifying signatures\n\n$ cast wallet verify --address $SIGNER \"Hello, Ethereum!\" $SIGNATURE\n\nEIP-7702 account delegation\n\nUse cast wallet sign-auth to create a signed authorization that delegates an EOA's execution to a contract implementation. The authorization can be submitted by the authority or a separate broadcaster.\n\nSee EIP-7702 account delegation for signing, nonce selection, broadcasting, verification, and clearing instructions.\n\nVanity addresses\n\nGenerate addresses matching a pattern:\n\n$ cast wallet vanity --starts-with dead\n\n$ cast wallet vanity --ends-with beef\n\n$ cast wallet vanity --starts-with 00 --ends-with 00\n\nAddress utilities\n\n$ cast to-check-sum-address 0xd8da6bf26964af9d7eed9e03e53415d37aa96045\n\n$ cast compute-address $DEPLOYER --nonce 5\n\n$ cast create2 --starts-with 00 --init-code $BYTECODE --deployer $FACTORY\n\nHardware wallets\n\n$ cast wallet list --ledger\n\n$ cast wallet list --trezor\n\n$ cast wallet sign \"Hello\" --ledger\n\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":669,"crawled_at":1791194768918}
+{"id":10436,"url":"https://docs.ethena.fi/protocol-overview/governance","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Governance | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nRather than a flat governance structure wherein every protocol-level decision is put to a vote for participation by all governance tokenholders, the vast majority of decisions (other than those which the committees deem outside the scope of their remit) are delegated to the relevant committees described in this section. Each committee will have a clearly defined and siloed role within the broader governance framework and ecosystem.\nThe primary role of $ENA governance tokenholders is initially to appoint committee members on a rotating basis; however, governance going forward will be a generally iterative process where all stakeholders will adapt and tweak the system on a collective basis to move towards an efficient system that enables an appropriate balance between efficient and informed decision-making and enabling stakeholders in the community to have adequate input where it makes sense.\nWhy Govern by Committee?\nDue to the design of Ethena (e.g., the necessity for off-chain infrastructure), fully on-chain governance is not a practical or viable option at present. The Committee approach reflects prioritizing practicality while adding external checks and balances to that off-chain infrastructure and governance environment.\nIn this framework, $ENA governance tokenholders are able to delegate everyday decision-making with respect to key aspects of the ecosystem to sophisticated, expert-level stakeholders - most of whom provide advisory and similar services to other projects and protocols in the industry - while retaining transparency during the process. In addition, the vetting process is put in place to reduce the risk of future Committee members being appointed who are ill-equipped to understand, analyze, and implement these initiatives and decisions.\nLinks\nForum\nSnapshot Voting\n\nLast updated 1 month ago\nWas this helpful?","tokens":487,"crawled_at":1791194774831}
+{"id":10437,"url":"https://docs.sui.io/operators/validator/validator-tasks","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Validator Node Management | Sui Documentation","text":"As a validatorValidatorResponsible for executing tasks like staking, gas price references, and tallying rules. on Sui, there are some processes you need to perform to ensure your nodes are always optimized.\n\nStorage management​\n\nBy default, all sui-node related data is stored under /opt/sui/db/, as specified in the sui-node configuration file.\n\n$ cat /opt/sui/config/validator.yaml | grep db-path\n\ndb-path: /opt/sui/db/authorities_db\ndb-path: /opt/sui/db/consensus_db\n\nEnsure that you have an appropriately sized disk mounted for the database to write to.\n\nTo check the size of the local sui-node databases:\n\n$ du -sh /opt/sui/db/\n$ du -sh /opt/sui/db/authorities_db\n$ du -sh /opt/sui/db/consensus_db\n\nTo delete the local sui-node databases:\n\n$ sudo systemctl stop sui-node\n$ sudo rm -rf /opt/sui/db/authorities_db /opt/sui/db/consensus_db\n\nKey management​\n\nThe following keys are used by sui-node:\n\nKeySchemePurpose\nprotocol.key\nbls12381\nTransactions\n\naccount.key\ned25519\nControls assets for staking\n\nnetwork.key\ned25519\nState sync\n\nworker.key\ned25519\nConsensusConsensusThe process by which the majority of nodes agree on the current state of the network (to be migrated)\n\nThese are configured in the sui-node configuration file.\n\nMetrics​\n\nsui-node exposes metrics through a local HTTP interface. You can scrape these for use in a central monitoring system, or view them directly from the node.\n\nView all metrics:\n\n$ curl -s http://localhost:9184/metrics\n\nSearch for a particular metric:\n\n$ curl http://localhost:9184/metrics | grep <METRIC>\n\nsui-node also pushes metrics to a central Sui metrics proxy.\n\nLogs​\n\nLogs are controlled using the RUST_LOG environment variable.\n\nYou can optionally set the RUST_LOG_JSON=1 environment variable to enable logging in JSON structured format.\n\nDepending on your deployment method, you configure these in the following places:\n\nAnsible\n\nNative systemd\n\nDocker Compose\n\nTo view and follow the sui-node logs:\n\n$ journalctl -u sui-node -f\n\nTo search for a particular match:\n\n$ journalctl -u sui-node -g <SEARCH_TERM>\n\nIf you are using Docker Compose, look at the examples in the README.\n\nYou can change the logging configuration while a node is running using the admin interface.\n\nTo view the currently configured logging values:\n\n$ curl localhost:1337/logging\n\nTo change the currently configured logging values:\n\n$ curl localhost:1337/logging -d \"info\"\n\nDashboards​\n\nPublic dashboard for network-wide visibility:\n\nSui Testnet Validators\n\nSoftware updates​\n\nWhen you need to update the sui-node software, use the following process. Follow the relevant Systemd or Docker Compose run book depending on your deployment type. You most likely do not want to restart with a clean database.\n\nSystemd\n\nDocker Compose\n\nState sync​\n\nCheckpointsCheckpointCreated after transaction execution to provide a certified record of chain history. in Sui contain the permanent history of the network. They are comparable to blocks in other blockchains with one key difference: they lag instead of lead. All transactions are final and executed before being included in a checkpoint.\n\nThese checkpoints synchronize between validators and full nodes through a dedicated peer-to-peer state sync interface.\n\nInter-validator state sync is always permitted, but you can use controls to limit which full nodes can sync from a specific validator.\n\nThe default and recommended max-concurrent-connections: 0 configuration does not affect inter-validator state sync, but restricts all full nodes from syncing. The sui-node configuration can be modified to allow a known full nodeFull nodeResponsible for validating blockchain activity. to sync from a validator:\n\np2p-config:\nanemo-config:\nmax-concurrent-connections: 0\nseed-peers:\n- address: <multiaddr> # The p2p address of the full node\npeer-id: <peer-id> # hex encoded network public key of the node\n- address: ... # another permitted peer\npeer-id: ...\n\nChain operations​\n\nYou execute the following chain operations using the sui CLI. This binary is built and provided as a release similar to sui-node, for example:\n\n$ wget https://releases.sui.io/$SUI_SHA/sui\n$ chmod +x sui\n\n$ curl https://releases.sui.io/$SUI_SHA/sui -o sui\n$ chmod +x sui\n\nEnsure that the sui binary release/version matches that of the deployed network, as this is often required.\n\nUpdating onchain metadata​\n\nYou can leverage the validator tool to perform a majority of the following tasks.\n\nAn active or pending validator can update its onchain metadata by submitting a transactionTransactionA number of commands that execute on inputs to define the result of the transaction.. Some metadata changes take effect immediately, including:\n\nName\n\nDescription\n\nImage URL\n\nProject URL\n\nOther metadata (keys, addressesAddressA unique, anonymous identity on a blockchain network., and so on) only come into effect at the next epochEpochA period of time defined by the network..\n\nTo update metadata, a validator makes a MoveCall transaction that interacts with the system objectObjectThe basic unit of storage on Sui.. For example:\n\nTo update name to new_validator_name, use the Sui Client CLI to call sui_system::update_validator_name:\n\ntip\nBeginning with the Sui v1.24.1 release, the --gas-budget option is no longer required for CLI commands.\n\n$ sui client call --package 0x3 --module sui_system --function update_validator_name --args 0x5 \\\"new_validator_name\\\" --gas-budget 10000\n\nTo update the p2p address starting from next epoch to /ip4/192.168.1.1, use the Sui Client CLI to call sui_system::update_validator_next_epoch_p2p_address:\n\n$ sui client call --package 0x3 --module sui_system --function update_validator_next_epoch_p2p_address --args 0x5 \"[4, 192, 168, 1, 1]\" --gas-budget 10000\n\nSee the full list of metadata update functions.\n\nOperation CapOperation CapAllows a validator to authorize another account to perform certain actions on its behalf.​\n\nTo avoid touching account keys too often and to allow storing them offline, you can delegate the operation ability to another address. This address can then update the reference gasGasThe computational cost of execution and object storage for a transaction. price and tallying rule on behalf of the validator.\n\nWhen you create a validator, the system creates a UnverifiedValidatorOperationCap and transfers it to the validator address. The holder of this Cap object (short for Capability) can therefore perform operational actions for this validator. To authorize another address to conduct these operations, transferTransferChanging the owner of an asset. the object to another address that you control.\n\nYou can perform the transfer using Sui Client CLI: sui client transfer.\n\nTo rotate the delegatee address or revoke the authorization, the current holder of Cap transfers it to another address. If keys are compromised or lost, the validator can create a new Cap object to invalidate the existing one.\n\nCall sui_system::rotate_operation_cap to do this:\n\n$ sui client call --package 0x3 --module sui_system --function rotate_operation_cap --args 0x5 --gas-budget 10000\n\nBy default, the new Cap object transfers to the validator address, and you can then transfer it to the new delegatee address. At this point, the old Cap becomes invalid and no longer represents eligibility.\n\nTo get the current valid Cap object's ID of a validator, use the Sui Client CLI sui client objects command after setting the holder as the active address.\n\ntip\nStrengthen operation-capability delegation with these practices:\n\nDelegate with least privilege. Hand the operation cap only to the address that needs it for a specific task, and keep account keys offline and uninvolved in routine operations.\n\nRevoke after the task completes. Once a delegated task is done, rotate the cap with sui_system::rotate_operation_cap to invalidate the old one, and rotate immediately if a delegatee key is lost or compromised.\n\nKeep an audit trail. Record who held each cap, when you delegated it, and when you revoked it, so you can review operational actions after the fact.\n\nRoll out security fixes confidentially. Apply urgent fixes through the private security fixes process rather than disclosing them publicly before validators have patched.\n\nSee Security Best Practices for the canonical operator guidance.\n\nUpdating the gas price survey quote​\n\nTo update the gas price survey quote of a validator, which the network uses to calculate the reference gas price at the end of the epoch, the sender needs to hold a valid UnverifiedValidatorOperationCap. The sender can be the validator itself or a trusted delegatee.\n\nCall sui_system::request_set_gas_price:\n\n$ sui client call --package 0x3 --module sui_system --function request_set_gas_price --args 0x5 {cap_object_id} {new_gas_price} --gas-budget 10000\n\nReporting/un-reporting validators​\n\nTo report a validator or undo an existing report, the sender needs to hold a valid UnverifiedValidatorOperationCap. The sender can be the validator itself or a trusted delegatee.\n\nCall sui_system::report_validator/undo_report_validator:\n\n$ sui client call --package 0x3 --module sui_system --function report_validator/undo_report_validator --args 0x5 {cap_object_id} {reportee_address} --gas-budget 10000\n\nAfter 2f + 1 other validators by voting power report a validator, the network slashes their staking rewards.\n\nJoining the validator set​\n\nTo join the validator set, you need to first sign up as a validator candidate by calling sui_system::request_add_validator_candidate with your metadata and initial configs:\n\n$ sui client call --package 0x3 --module sui_system --function request_add_validator_candidate --args 0x5 {protocol_pubkey_bytes} {network_pubkey_bytes} {worker_pubkey_bytes} {proof_of_possession} {name} {description} {image_url} {project_url} {net_address} {p2p_address} {primary_address} {worker_address} {gas_price} {commission_rate} --gas-budget 10000\n\nAfter an address becomes a validator candidate, any address (including the candidate address itself) can start staking with the candidate's staking pool. After a candidate's staking pool accumulates at least sui_system::MIN_VALIDATOR_JOINING_STAKE amount of stake, the candidate can call sui_system::request_add_validator to officially join the next epoch's active validator set:\n\n$ sui client call --package 0x3 --module sui_system --function request_add_validator --args 0x5 --gas-budget 10000000\n\nLeaving the validator set​\n\nTo leave the validator set starting next epoch, the sender needs to be an active validator in the current epoch and should call sui_system::request_remove_validator:\n\n$ sui client call --package 0x3 --module sui_system --function request_remove_validator --args 0x5 --gas-budget 10000\n\nAfter the validator is removed at the next epoch change, the staking pool becomes inactive and you can only withdraw stakes from an inactive pool.\n\nPrivate security fixes​\n\nThere might be instances where urgent security fixes need to roll out before public announcement (issues affecting liveness, invariants such as SUI supply, governance, and so on). To avoid active exploitation, Mysten Labs releases signed security binaries incorporating such fixes with a delay in publishing the source code until a large percentage of validators have patched the vulnerability.\n\nThis release process is different, and you should expect that announcements of the directory for such binaries arrive out of band.\nView the public key used to verify these binaries.\n\nA script is also available that downloads all the necessary signed binaries and Docker artifacts incorporating the security fixes.\n\nUsage: ./download_private.sh <commit-sha>\n\nYou can also download and verify specific binaries that might not be included by the above script using the download_and_verify_private_binary.sh script.\n\nUsage: ./download_and_verify_private_binary.sh <commit-sha> <binary-name>\n\nRelated topics\n\nValidator Deployment and Configuration\nLearn how to set up, configure, and manage a Sui validator node.\nSecurity Best Practices\nOverview of security best practices on Sui.\n\nStorage management\nKey management\nMetrics\nLogs\nDashboards\nSoftware updates\nState sync\nChain operationsUpdating onchain metadata\nOperation Cap\nUpdating the gas price survey quote\nReporting/un-reporting validators\nJoining the validator set\nLeaving the validator set\n\nPrivate security fixes\n\nWas this page helpful?","tokens":3088,"crawled_at":1791194779514}
+{"id":10438,"url":"https://www.getfoundry.sh/anvil/rpc-methods","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"RPC method reference – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nRPC method reference\n\nAnvil serves the standard Ethereum JSON-RPC API together with a custom anvil_* and evm_* namespace for manipulating the node at runtime. This page is the complete reference for every custom method. For workflow-oriented examples, see Custom methods, Mining and transaction pool, and State management.\n\nCall any method with cast rpc. The examples below assume a local node on the default endpoint; pass --rpc-url otherwise:\n\n$ cast rpc anvil_nodeInfo --rpc-url http://127.0.0.1:8545\n\nMany methods accept alias names for Ganache (evm_*), Hardhat (hardhat_*), and Tenderly (tenderly_*) compatibility. Each entry lists its aliases; aliased names behave identically. Numeric parameters accept 0x-prefixed hex quantities and decimal numbers unless noted, but decimal number literals only work up to u64::MAX (about 1.8e19); pass larger amounts as hex quantities or quoted decimal strings.\n\nAccount impersonation\n\nanvil_impersonateAccount\n\nAllows sending transactions from an address without its private key. Alias: hardhat_impersonateAccount.\n\nParameters: address — the account to impersonate.\n\nImpersonate an account\n$ cast rpc anvil_impersonateAccount $ADDRESS\n\nSend transactions from the impersonated account with --unlocked:\n\nSend as impersonated account\n$ cast send $CONTRACT \"transfer(address,uint256)\" $TO $AMOUNT --from $ADDRESS --unlocked\n\nanvil_stopImpersonatingAccount\n\nStops impersonating an account previously set with anvil_impersonateAccount. Alias: hardhat_stopImpersonatingAccount.\n\nParameters: address — the account to stop impersonating.\n\nStop impersonating\n$ cast rpc anvil_stopImpersonatingAccount $ADDRESS\n\nanvil_autoImpersonateAccount\n\nEnables or disables impersonation of every account, so any sender can be used without a key. Alias: hardhat_autoImpersonateAccount. Equivalent to starting Anvil with --auto-impersonate.\n\nParameters: enabled — true to impersonate all accounts, false to disable.\n\nEnable auto-impersonation\n$ cast rpc anvil_autoImpersonateAccount true\n\nanvil_impersonateSignature\n\nRegisters a signature/address pair that overrides the ecrecover precompile: recovering the given 65-byte signature returns the given address. Useful together with impersonation when contracts verify signatures.\n\nParameters: a single two-element array [signature, address] — the 65-byte signature as hex and the address ecrecover should return for it.\n\nFake an ecrecover result\n$ cast rpc anvil_impersonateSignature \"[\\\"$SIGNATURE\\\", \\\"$ADDRESS\\\"]\"\n\nMining\n\nanvil_getAutomine\n\nReturns true if automatic mining is enabled. Alias: hardhat_getAutomine. No parameters.\n\nCheck automine\n$ cast rpc anvil_getAutomine\n\nanvil_setAutomine\n\nEnables or disables automatic mining of a new block with each new transaction. Alias: evm_setAutomine.\n\nParameters: enabled — true for instant mining, false to stop instant mining.\n\nDisable automatic mining\n$ cast rpc anvil_setAutomine false\n\nanvil_setIntervalMining\n\nSwitches to interval mining with the given interval in seconds. Passing 0 disables mining entirely. Alias: evm_setIntervalMining.\n\nParameters: seconds — mining interval.\n\nMine every 12 seconds\n$ cast rpc anvil_setIntervalMining 12\n\nanvil_getIntervalMining\n\nReturns the current mining interval in seconds, or null if interval mining is not active. No parameters.\n\nCheck mining interval\n$ cast rpc anvil_getIntervalMining\n\nanvil_mine\n\nMines a series of blocks. Alias: hardhat_mine.\n\nParameters (both optional): blocks — number of blocks to mine (default 1), interval — seconds between the timestamps of the mined blocks. The interval applies only to blocks mined by this call.\n\nMine 10 blocks with 12s spacing\n$ cast rpc anvil_mine 10 12\n\nevm_mine\n\nMines a single block (or several, with options), regardless of the configured mining mode. Always returns \"0x0\".\n\nParameters (optional): either a timestamp for the mined block, or an options object {\"timestamp\": ..., \"blocks\": ...} to mine a fixed number of blocks. The options object requires the timestamp key (null keeps the current clock), and a timestamp must not be lower than the previous block's timestamp.\n\nMine one block\n$ cast rpc evm_mine\n\nMine 5 blocks\n$ cast rpc evm_mine \"{\\\"timestamp\\\": $TIMESTAMP, \\\"blocks\\\": 5}\"\n\nanvil_mine_detailed\n\nBehaves exactly like evm_mine but returns the mined blocks with full transaction objects; transactions with return data carry an additional output field, and failed transactions also a revertReason field. Alias: evm_mine_detailed.\n\nParameters (optional): same as evm_mine.\n\nMine and return block data\n$ cast rpc anvil_mine_detailed\n\nTime\n\nanvil_setTime\n\nSets the node's internal clock to the given Unix timestamp and returns the number of seconds between the previous clock time and the new one, clamped to 0 when moving backwards. Values above 1e12 are interpreted as milliseconds. Alias: evm_setTime.\n\nParameters: timestamp — Unix timestamp in seconds (or milliseconds).\n\nJump to a specific time\n$ cast rpc anvil_setTime 1700000000\n\nanvil_increaseTime\n\nJumps forward in time by the given number of seconds and returns the node's total accumulated clock offset in seconds. Alias: evm_increaseTime.\n\nParameters: seconds — amount of time to advance.\n\nAdvance time by one hour\n$ cast rpc anvil_increaseTime 3600\n\nanvil_setNextBlockTimestamp\n\nSets the exact timestamp of the next mined block. Fails if the timestamp is lower than the previous block's timestamp. Alias: evm_setNextBlockTimestamp.\n\nParameters: timestamp — Unix timestamp in seconds for the next block.\n\nPin the next block's timestamp\n$ cast rpc anvil_setNextBlockTimestamp $TIMESTAMP\n\nanvil_setBlockTimestampInterval\n\nSets a fixed timestamp interval: every new block's timestamp is computed as the previous block's timestamp plus the interval. Unlike the anvil_mine interval, this applies to all future blocks until removed.\n\nParameters: seconds — timestamp interval.\n\nAdvance timestamps by 12s per block\n$ cast rpc anvil_setBlockTimestampInterval 12\n\nanvil_removeBlockTimestampInterval\n\nRemoves a timestamp interval set with anvil_setBlockTimestampInterval. Returns true if an interval existed. No parameters.\n\nRemove the timestamp interval\n$ cast rpc anvil_removeBlockTimestampInterval\n\nanvil_getGenesisTime\n\nReturns the genesis block timestamp in Unix seconds. Anvil also serves this value through its Beacon API genesis endpoint. No parameters.\n\nGet the genesis timestamp\n$ cast rpc anvil_getGenesisTime\n\nState snapshots\n\nanvil_snapshot\n\nSnapshots the state of the blockchain at the current block and returns the snapshot ID. Alias: evm_snapshot. No parameters.\n\nCreate snapshot\n$ cast rpc anvil_snapshot\n\nanvil_revert\n\nReverts the chain to a previous snapshot and returns true on success. Reverting consumes the snapshot: the same ID cannot be used again. Alias: evm_revert.\n\nParameters: id — snapshot ID returned by anvil_snapshot.\n\nRevert to snapshot\n$ cast rpc anvil_revert $SNAPSHOT_ID\n\nState dump and load\n\nThe --dump-state, --load-state, and --state CLI flags cover the same functionality at startup and shutdown; the RPC forms work on a running node.\n\nanvil_dumpState\n\nSerializes the current chain state, including accounts, contract code, storage, and blocks, into a gzip-compressed hex-encoded blob that can later be loaded with anvil_loadState. Alias: hardhat_dumpState.\n\nParameters (optional): preserveHistoricalStates — true to include historical states in the dump (default false).\n\nDump chain state\n$ cast rpc anvil_dumpState\n\nanvil_loadState\n\nMerges a state blob previously produced by anvil_dumpState into the current chain, overwriting any conflicting accounts or storage, and returns true on success. Alias: hardhat_loadState.\n\nParameters: state — hex-encoded state blob.\n\nLoad chain state\n$ cast rpc anvil_loadState $STATE\n\nFork management\n\nanvil_reset\n\nResets the chain. Without parameters this resets to a fresh, empty in-memory state and disables any active fork. With a forking object it resets onto the given fork; omit jsonRpcUrl to re-fork the current fork URL at a different block. Alias: hardhat_reset.\n\nParameters (optional): {\"forking\": {\"jsonRpcUrl\": ..., \"blockNumber\": ...}} — both fields optional.\n\nReset to a fresh empty state\n$ cast rpc anvil_reset\n\nFork mainnet at a block\n$ cast rpc anvil_reset '{\"forking\": {\"jsonRpcUrl\": \"https://ethereum.reth.rs/rpc\", \"blockNumber\": 18000000}}'\n\nReset the current fork to a block\n$ cast rpc anvil_reset '{\"forking\": {\"blockNumber\": 18000000}}'\n\nanvil_setRpcUrl\n\nUpdates the RPC endpoint used by the active fork. Later anvil_reset calls also use the new URL.\n\nParameters: url — the new fork RPC endpoint.\n\nSwitch the fork endpoint\n$ cast rpc anvil_setRpcUrl $RPC_URL\n\nReorgs and rollbacks\n\nanvil_reorg\n\nReorgs the chain: rewinds by depth blocks and mines new blocks back to the same height, optionally including supplied transactions in the replacement blocks. The depth must not exceed the current chain height.\n\nParameters: depth — number of blocks to reorg, tx_block_pairs — array of [transaction, blockIndex] pairs, where transaction is a raw signed transaction hex string or a transaction request object and blockIndex (0-based, less than depth) selects the replacement block that includes it. Pass [] for empty replacement blocks.\n\nReorg the last 5 blocks\n$ cast rpc anvil_reorg 5 '[]'\n\nReorg 3 blocks and include a transfer in the first new block\n$ cast rpc anvil_reorg 3 '[[{\"from\": \"0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266\", \"to\": \"0x70997970C51812dc3A010C7d01b50e0d17dc79C8\", \"value\": \"0xde0b6b3a7640000\"}, 0]]'\n\nanvil_rollback\n\nRolls the chain back by the given number of blocks without mining replacements, shortening the chain. The depth must not exceed the current chain height.\n\nParameters (optional): depth — number of blocks to remove (default 1).\n\nDrop the last 3 blocks\n$ cast rpc anvil_rollback 3\n\nAccount state\n\nanvil_setBalance\n\nSets the ETH balance of an account. Aliases: hardhat_setBalance, tenderly_setBalance.\n\nParameters: address, balance — new balance in wei.\n\nSet balance to 1 ETH\n$ cast rpc anvil_setBalance $ADDRESS 0xDE0B6B3A7640000\n\nanvil_addBalance\n\nAdds the given amount to an account's ETH balance. Aliases: hardhat_addBalance, tenderly_addBalance.\n\nParameters: address, amount — wei to add.\n\nAdd 1 ETH\n$ cast rpc anvil_addBalance $ADDRESS 0xDE0B6B3A7640000\n\nanvil_setCode\n\nSets the bytecode of an account. Alias: hardhat_setCode.\n\nParameters: address, code — deployed bytecode as hex.\n\nSet contract code\n$ cast rpc anvil_setCode $ADDRESS $BYTECODE\n\nanvil_setNonce\n\nSets the nonce of an account. Aliases: hardhat_setNonce, evm_setAccountNonce.\n\nParameters: address, nonce.\n\nSet account nonce\n$ cast rpc anvil_setNonce $ADDRESS 0x10\n\nanvil_setStorageAt\n\nWrites a single storage slot of an account and returns true. Alias: hardhat_setStorageAt.\n\nParameters: address, slot — storage slot, value — 32-byte value.\n\nWrite a storage slot\n$ cast rpc anvil_setStorageAt $ADDRESS $SLOT $VALUE\n\nToken balances and allowances\n\nanvil_dealERC20\n\nSets the ERC-20 token balance of an account by discovering and overwriting the token's balance storage slot. Fails with an error if no slot can be found, which can happen for tokens with nonstandard balance accounting. Aliases: anvil_setERC20Balance, hardhat_dealERC20. On Tempo nodes, TIP-20 tokens are written through the native TIP-20 path instead (see Foundry on Tempo).\n\nParameters: address — account whose balance is set, token — ERC-20 token contract, balance — absolute balance to write.\n\nSet an ERC-20 balance\n$ cast rpc anvil_dealERC20 $ADDRESS $TOKEN 0xDE0B6B3A7640000\n\nanvil_setERC20Allowance\n\nSets an ERC-20 allowance by discovering and overwriting the token's allowance storage slot.\n\nParameters: owner, spender, token — ERC-20 token contract, amount — allowance to write.\n\nSet an ERC-20 allowance\n$ cast rpc anvil_setERC20Allowance $OWNER $SPENDER $TOKEN 0xDE0B6B3A7640000\n\nTransaction pool\n\nanvil_dropTransaction\n\nRemoves a transaction from the pool. Returns the hash if the transaction was pending, otherwise null. Alias: hardhat_dropTransaction.\n\nParameters: hash — transaction hash.\n\nDrop a pending transaction\n$ cast rpc anvil_dropTransaction $TX_HASH\n\nanvil_dropAllTransactions\n\nRemoves all transactions from the pool. Alias: hardhat_dropAllTransactions. No parameters.\n\nClear the pool\n$ cast rpc anvil_dropAllTransactions\n\nanvil_removePoolTransactions\n\nRemoves all pool transactions sent by the given address.\n\nParameters: address — sender whose transactions are removed.\n\nDrop all transactions from a sender\n$ cast rpc anvil_removePoolTransactions $SENDER\n\nChain and block configuration\n\nanvil_setChainId\n\nSets the chain ID of the running node.\n\nParameters: chainId.\n\nChange the chain ID\n$ cast rpc anvil_setChainId 31338\n\nanvil_setCoinbase\n\nSets the coinbase (block beneficiary) address used for subsequent blocks. Alias: hardhat_setCoinbase.\n\nParameters: address.\n\nSet the coinbase\n$ cast rpc anvil_setCoinbase $ADDRESS\n\nanvil_setBlockGasLimit\n\nSets the gas limit for subsequent blocks and returns true. Alias: evm_setBlockGasLimit.\n\nParameters: gasLimit.\n\nSet the block gas limit\n$ cast rpc anvil_setBlockGasLimit 0x1C9C380\n\nanvil_setNextBlockBaseFeePerGas\n\nSets the base fee of the next block. Only supported when EIP-1559 is active; returns an error otherwise. Alias: hardhat_setNextBlockBaseFeePerGas.\n\nParameters: baseFee — base fee in wei.\n\nSet the next base fee\n$ cast rpc anvil_setNextBlockBaseFeePerGas 0x5F5E100\n\nanvil_setMinGasPrice\n\nSets the minimum gas price for the node. Only supported on legacy (pre-EIP-1559) chains; returns an error when EIP-1559 is active. Alias: hardhat_setMinGasPrice.\n\nParameters: gasPrice — minimum gas price in wei.\n\nSet the minimum gas price\n$ cast rpc anvil_setMinGasPrice 0x4A817C800\n\nanvil_setNextBlockPrevRandao\n\nSets the prevrandao value of the next block. This is a one-shot override: it applies to the next mined block only.\n\nParameters: prevrandao — 32-byte value.\n\nOverride the next prevrandao\n$ cast rpc anvil_setNextBlockPrevRandao $VALUE\n\nanvil_setLoggingEnabled\n\nEnables or disables the node's logging. Alias: hardhat_setLoggingEnabled.\n\nParameters: enabled.\n\nSilence node logs\n$ cast rpc anvil_setLoggingEnabled false\n\nNode information\n\nanvil_nodeInfo\n\nReturns the node's runtime configuration: current block number, timestamp, and hash, hardfork, transaction ordering, environment (base fee, chain ID, gas limit, gas price), and fork configuration. No parameters.\n\nInspect the node\n$ cast rpc anvil_nodeInfo\n\nanvil_metadata\n\nReturns instance metadata: client version, chain ID, latest block hash and number, instance ID, forked network details, and the list of active state snapshots. Alias: hardhat_metadata. No parameters.\n\nGet instance metadata\n$ cast rpc anvil_metadata\n\nBlobs\n\nanvil_getBlobByHash\n\nReturns the EIP-4844 blob for a given blob versioned hash, or null if unknown.\n\nParameters: versionedHash — blob versioned hash.\n\nFetch a blob by versioned hash\n$ cast rpc anvil_getBlobByHash $VERSIONED_HASH\n\nanvil_getBlobsByTransactionHash\n\nReturns all blobs of a blob transaction, or null if the transaction is unknown or carries no blobs.\n\nParameters: hash — transaction hash.\n\nFetch blobs for a transaction\n$ cast rpc anvil_getBlobsByTransactionHash $TX_HASH\n\nTempo methods\n\nThese methods apply to Anvil's Tempo mode (anvil --network tempo). Except for anvil_classifyTransaction, they return an error on non-Tempo nodes.\n\nanvil_dealTIP20\n\nSets a TIP-20 token balance by writing directly into native TIP-20 storage. See Foundry on Tempo for details on how this differs from anvil_dealERC20.\n\nParameters: address — account whose balance is set, token — TIP-20 token contract, balance — absolute balance to write.\n\nSet a TIP-20 balance\n$ cast rpc anvil_dealTIP20 $RECIPIENT $TIP20_TOKEN 0x56BC75E2D63100000\n\nanvil_setFeeToken\n\nSets the fee token for a user address, so its transactions pay gas in that TIP-20 token.\n\nParameters: user, token — TIP-20 fee token.\n\nSet a user's fee token\n$ cast rpc anvil_setFeeToken $ADDRESS $FEE_TOKEN\n\nanvil_setValidatorFeeToken\n\nSets the fee token for a validator address.\n\nParameters: validator, token — TIP-20 fee token.\n\nSet a validator's fee token\n$ cast rpc anvil_setValidatorFeeToken $VALIDATOR $FEE_TOKEN\n\nanvil_setFeeAmmLiquidity\n\nMints FeeAMM liquidity for a user-token/validator-token pair, so fee conversion between the two tokens can succeed locally.\n\nParameters: userToken, validatorToken, amount — liquidity to mint.\n\nMint FeeAMM liquidity\n$ cast rpc anvil_setFeeAmmLiquidity $USER_TOKEN $VALIDATOR_TOKEN 0x56BC75E2D63100000\n\nanvil_classifyTransaction\n\nClassifies a raw signed transaction with the Tempo T5 payment-lane classifier and returns {\"lane\": ..., \"payment\": ..., \"reason\": ...}. Works on any node: outside Tempo mode (or before the T5 hardfork) every transaction classifies into the general lane with a matching reason.\n\nParameters: rawTransaction — raw signed transaction as hex.\n\nClassify a raw transaction\n$ cast rpc anvil_classifyTransaction $RAW_TX\n\neth_signRawTransaction\n\nSigns a sender-signed Tempo transaction as the node's fee payer (sponsor) and returns the fully signed raw transaction without broadcasting it. This is the sign-only mode of the Tempo fee payer service contract, so cast send --sponsor-url and the Tempo SDK relay transport can point directly at Anvil; raw transactions submitted to eth_sendRawTransaction with the sponsorship placeholder are sponsored automatically instead. The sponsor account defaults to the last dev account and is configurable with Anvil's --tempo.fee-payer option; it selects the fee token when the sender left it open and must not equal the transaction sender. See the sponsorship guide for the end-to-end flow.\n\nParameters: rawTransaction — sender-signed Tempo transaction as hex, carrying the fee payer signature placeholder.\n\nSponsor-sign a raw transaction\n$ cast rpc eth_signRawTransaction $RAW_TX\n\nNonstandard eth_ methods\n\nAnvil also serves a number of eth_ methods beyond the standard Ethereum JSON-RPC specification.\n\neth_callBundle\n\nSimulates a bundle of raw signed transactions on top of a given block, Flashbots style, and returns per-transaction results together with bundle totals such as gas fees and coinbase payments.\n\nParameters: a bundle object with txs — array of raw signed transactions, blockNumber — block the bundle is valid for, and stateBlockNumber — block number or tag to base the simulation state on; optionally timestamp, gasLimit, difficulty, baseFee, and coinbase.\n\nSimulate a bundle\n$ cast rpc eth_callBundle \"{\\\"txs\\\": [\\\"$RAW_TX\\\"], \\\"blockNumber\\\": \\\"$BLOCK_NUMBER\\\", \\\"stateBlockNumber\\\": \\\"latest\\\"}\"\n\neth_callMany\n\nSimulates a sequence of transaction bundles on top of each other and returns the call results for each bundle.\n\nParameters: bundles — array of {\"transactions\": [...], \"blockOverride\": ...} objects; optionally a state context {\"blockNumber\": ..., \"transactionIndex\": ...} and a state override object.\n\nSimulate two dependent calls\n$ cast rpc eth_callMany '[{\"transactions\": [{\"from\": \"0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266\", \"to\": \"0x70997970C51812dc3A010C7d01b50e0d17dc79C8\", \"value\": \"0xde0b6b3a7640000\"}, {\"from\": \"0x70997970C51812dc3A010C7d01b50e0d17dc79C8\", \"to\": \"0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266\", \"value\": \"0xde0b6b3a7640000\"}]}]'\n\neth_sendUnsignedTransaction\n\nExecutes a transaction from any sender regardless of signature status, without requiring impersonation to be enabled.\n\nParameters: transaction — a transaction request object including from.\n\nSend without a signature\n$ cast rpc eth_sendUnsignedTransaction \"{\\\"from\\\": \\\"$FROM\\\", \\\"to\\\": \\\"$TO\\\", \\\"value\\\": \\\"0x1\\\"}\"\n\neth_getTransactionBySenderAndNonce\n\nReturns the full transaction for a sender and nonce, checking pending pool transactions first and then mined blocks, or null if not found.\n\nParameters: sender, nonce.\n\nLook up a transaction by sender and nonce\n$ cast rpc eth_getTransactionBySenderAndNonce $ADDRESS 5\n\nOther extensions\n\nAnvil additionally serves these nonstandard eth_ extensions, largely mirroring geth and reth:\n\nMethodDescription\neth_baseFee\nReturns the base fee of the next block.\n\neth_pendingTransactions\nReturns the transactions currently pending in the pool.\n\neth_fillTransaction\nFills in defaults (nonce, gas, fees) for a transaction request and returns the raw unsigned transaction and its fields.\n\neth_resend\nResends a pending transaction with an updated gas price or gas limit.\n\neth_getHeaderByHash, eth_getHeaderByNumber\nReturn a block header by hash or number.\n\neth_getAccountInfo\nReturns an account's balance, nonce, and code in a single call.\n\neth_getStorageValues\nReturns storage values for multiple accounts and slots in a single call.\n\neth_getBlockAccessList, eth_getBlockAccessListByBlockHash, eth_getBlockAccessListByBlockNumber, eth_getBlockAccessListRaw\nReturn the EIP-7928 block access list for a block as JSON, or RLP for the raw variant. Anvil records the list for every Amsterdam block it mines; pre-Amsterdam blocks return null, and when forking, blocks below the fork block are answered by the upstream node.\n\neth_sendTransactionSync, eth_sendRawTransactionSync\nSend a transaction and wait for its receipt in a single call; the raw variant accepts an optional timeout in milliseconds.\n\neth_sendRawTransactionConditional\nAccepts a raw transaction with conditional-inclusion options; Anvil accepts the options but does not enforce the conditions.\n\nAnvil also implements the txpool_*, debug_*, trace_*, and ots_* (Otterscan) namespaces, plus erigon_getHeaderByNumber for Otterscan compatibility. See Mining and transaction pool for the txpool_* methods.\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":5418,"crawled_at":1791194786833}
+{"id":10439,"url":"https://docs.ethena.fi/backing-assets/real-world-assets-rwa","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Real World Assets (RWA) | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nReal-world assets (RWAs) are tokenised representations of off-chain financial assets. They hold a relatively stable dollar value and generate yield without requiring a derivatives hedge, which makes them a natural component of the protocol's backing portfolio.\nEthena's RWA exposure has historically centred on tokenised short-duration government debt.\nThe protocol is extending this exposure into high-liquidity real-world assets beyond treasury bills - including tokenised, liquid fixed income and credit instruments selected for low volatility, relatively strong liquidity and settlement terms, and their ability to be exited at predictable values.\nRWAs serve two purposes in the backing portfolio. They preserve a stable dollar value, contributing to the stability of USDe backing, and they generate rewards from off-chain markets whose returns are largely uncorrelated with crypto market cycles.\nEligible RWA products, issuers, and exposure limits are approved subject to governance and Risk Committee review, with particular attention to liquidity under stress, credit quality, and legal structure of the assets.\n\nLast updated 3 months ago\nWas this helpful?","tokens":314,"crawled_at":1791194794028}
+{"id":10440,"url":"https://docs.sui.io/operators/validator/alerts","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Sui Validator Alert Reference | Sui Documentation","text":"When running a Sui ValidatorValidatorResponsible for executing tasks like staking, gas price references, and tallying rules. or full nodeFull nodeResponsible for validating blockchain activity., it is recommended to monitor the health of the nodes and set up alerts on problems.\nBesides alerting on crashes and other common issues, you might also want to configure alerting based on the following example rules.\n\nThe following sections cover the alert queries, but the details are meant to be customized to suit your infrastructure.\n\nHigh-priority health alerts​\n\nThese alerts should receive the most immediate attention from you or your team.\n\nCrash loop​\n\nKeyValue\nName\nCrash loop\n\nSummary\nNode is crash looping\n\nDuration\nRecommended to trigger after 15m\n\nmax without(version) (uptime) < 60 or absent(uptime)\n\nNode is not staying up longer than 60s. Possible reasons:\n\nBinary version too old.\n\nIncorrect configuration.\n\nSoftware bug.\n\nPlease notify Sui community on Discord if this cannot be resolved on your own.\n\nConsensusConsensusThe process by which the majority of nodes agree on the current state of the network proposals failure​\n\nKeyValue\nName\nConsensus proposals failure\n\nSummary\nConsensus block proposal rate is low\n\nDuration\nRecommended to trigger after 1h\n\nsum without(force) (rate(consensus_proposed_blocks[5m])) < 1.0\n\nValidators with a slow consensus proposal rate can hurt network latency and throughput.\nIt is usually due to network, disk or CPU performance issues.\n\nCheckpointCheckpointCreated after transaction execution to provide a certified record of chain history. execution rate is low​\n\nKeyValue\nName\nCheckpoint execution rate is low\n\nSummary\nValidator is not executing checkpoints quickly enough\n\nDuration\nRecommended to trigger after 1h\n\nrate(last_executed_checkpoint[5m]) < 1.0\n\nValidators and full nodes with slow checkpoint execution will not have up-to-date information from the network.\nIt is usually due to network, disk or CPU performance issues.\n\nSafe mode during reconfiguration​\n\nKeyValue\nName\nSafe mode during reconfiguration\n\nSummary\nValidator or full node failed to advance the epochEpochA period of time defined by the network. and entered safe mode\n\nDuration\nRecommended to trigger after 15m\n\nis_safe_mode > 0.5\n\nUsually this issue is outside the control of validator or full node operators.\nPlease notify Sui community on Discord when this is observed.\n\nNon-urgent and warning alerts​\n\nAll alerts are important, but the following alerts and warnings can be addressed within the normal node maintenance workflow.\n\nSystem invariant violations​\n\nKeyValue\nName\nSystem invariant violations\n\nSummary\nThe node reports an invariant violation\n\nDuration\nRecommended to trigger after 15m\n\nsystem_invariant_violations > 0\n\nUsually this issue is outside the control of validator or full node operators.\nPlease notify Sui community on Discord when this is observed.\n\nHigh-priority health alertsCrash loop\nConsensus proposals failure\nCheckpoint execution rate is low\nSafe mode during reconfiguration\n\nNon-urgent and warning alertsSystem invariant violations\n\nWas this page helpful?","tokens":778,"crawled_at":1791194800405}
+{"id":10441,"url":"https://docs.ethena.fi/overview/ethena-whitelabel","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Ethena Whitelabel | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nEthena Whitelabel is a stablecoin-as-a-service offering that lets partners launch and operate their own branded stablecoins on top of Ethena's infrastructure. The partner designs the product, controls distribution, and captures the economics within their own ecosystem. Ethena provides the issuance, backing operations, custody, reserve management, and integrations.\nThe opportunity for partners is significant. Stablecoins have become one of the clearest examples of product–market fit in crypto, and every major ecosystem - exchanges, chains, applications, and institutions - increasingly has reason to capture the value flowing through its own dollar-denominated economy. Ethena Whitelabel allows a partner to do this in weeks rather than years, without building issuance infrastructure, onboarding custodians, negotiating exchange integrations, or assembling a reserve management operation from scratch.\nWhat partners receive:\nAccess to the Ethena Ecosystem\nFrom day one, a partner stablecoin sits inside one of the largest dollar networks in CeFi and DeFi, with established distribution into leading exchanges, custodians, and on-chain venues. Partners inherit Ethena's existing relationships rather than negotiating each integration individually.\nIssuance from a trusted operator\nPartners launch with the team behind one of the largest dollar assets in crypto and a multi-billion-dollar issuance track record. The same operational discipline that has supported Ethena's own issuance is applied to partner stablecoins.\nDynamic backing asset allocation\nPartner stablecoins can be backed by USDe or USDtb - a stablecoin issued by Anchorage Digital Bank in a GENIUS-compliant manner and backed by fiat USD and BlackRock's BUIDL - and other approved stablecoins. The mix can be tailored to the partner's risk preferences, target reward profile, and regulatory requirements, and the allocation can be adjusted dynamically as conditions evolve.\nTailored deployment\nPartners can launch quickly from a templated offering, or customise the product to fit specific ecosystem mechanics and use cases - for example, embedding the stablecoin into transaction-fee subsidies, margin systems, or treasury operations within their network.\nUnified liquidity\nPartner stablecoins benefit from deep secondary liquidity through USDe, allowing onboarded users to enter and exit the partner asset against one of the most liquid dollar-denominated assets on chain.\nClient dashboard\nPartners retain real-time visibility and control over their stablecoin through a dedicated client dashboard, covering supply, backing composition, reserve activity, and operational status.\nLive deployments\nSeveral partner stablecoins are already in production on Ethena Whitelabel:\n\njupUSD - a Solana-native stablecoin launched with Jupiter, backed by USDtb and USDC at launch and integrated across the Jupiter ecosystem.\n\nUSDm - launched by MegaETH, backed by USDtb and USDC at launch, and designed to subsidise sequencer fees and stabilise transaction costs across the MegaETH network.\n\nsuiUSDe - launched on Sui, backed by USDe and USDC, created to power Sui's DeFi ecosystem.\n\nSecurity and transparency\nWhitelabel deployments use the same audited contracts and operational infrastructure as Ethena's own products. The protocol's smart contracts have been audited by Zellic, Quantstamp, Spearbit, and Cantina, and have been the subject of public audit through Code4rena. Backing assets are held under the same institutional custody and reserve verification arrangements described in the Off-Exchange Custody section.\n\nPartners interested in launching a stablecoin on Ethena Whitelabel can request a demo at whitelabel.ethena.fi.\n\nLast updated 2 months ago\nWas this helpful?","tokens":958,"crawled_at":1791194813118}
+{"id":10442,"url":"https://a16zcrypto.com/posts/article/nassim-eddequiouaq-and-riyaz-faizullabhoy","domain":"a16zcrypto.com","chapter":"research","title":"Nassim Eddequiouaq and Riyaz Faizullabhoy - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nNassim Eddequiouaq and Riyaz Faizullabhoy\nAnthony Albanese\n10.11.21\n\nTags & Share Tags\nannouncements\nannouncements & news\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nEvery day, it feels like the web3 community gets closer to fulfilling the promise of a new kind of internet that, as my partner Chris Dixon recently put it, is “owned by the builders and users, orchestrated with tokens.” As this space goes mainstream and attracts more users—and scrutiny—so does the need to ensure deeper trust and confidence in the products and services being built on decentralized protocols. Central to this effort is security; if we are to build and scale the internet of value, people need confidence that their assets are protected.\n\nCrypto is growing and adapting so quickly that it’s difficult for even the most technically-savvy founders to ensure they’re following the latest security best practices. We began searching for a world-class security leader to consult with the projects in our portfolio and help our own operations scale in a crypto-native way, and were doubly fortunate to find a pair of them instead. I’m pleased to announce that Nassim Eddequiouaq and Riyaz Faizullabhoy are joining a16z Crypto this week as our Chief Information Security Officer (CISO) and Chief Technology Officer (CTO), respectively.\n\nNassim and Riyaz are phenomenal engineering and security leaders with a proven track record in blockchain and infrastructure, and are passionate about working to advance the entire crypto ecosystem. They’ve worked together for years across multiple companies to build world-class security systems in complex regulatory environments, and as part of our operating team, will closely consult with the projects in a16z Crypto’s portfolio to apply rigorous security measures and technical guidance.\n\nBefore joining a16z Crypto, Nassim and Riyaz co-created the crypto custody infrastructure for the Novi (fka Calibra) wallet at Facebook. Together, they served as engineering and technical leads for many aspects of the project to enable its vision of safely and securely bringing crypto to billions of new users.\n\nNassim and Riyaz were first introduced to crypto during their time at Anchorage (where we first got to know them), an institutional digital asset custodian, where Riyaz was a founding engineer and Nassim joined shortly thereafter. While they were both initially skeptical about the blockchain space, the technical challenge of securing private keys in a large distributed infrastructure was compelling to them. They quickly realized the potential and power of blockchain across many applications and use cases. The security-first product they helped build has convinced institutions and regulators alike that the ecosystem is headed in the right direction.\n\nPrior to getting involved with blockchain technologies, Nassim and Riyaz met on the security team at Docker, a container platform for building, running, and managing applications. At Docker, they worked on securing application provenance, authentication systems, and designed and shipped the secure OS used in Docker Desktop.\n\nTheir passion for web3 is contagious, and I know that applying their knowledge across the projects in our portfolio will do wonders for the entire space. Welcome, Riyaz and Nassim!\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nCharts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":1513,"crawled_at":1791194849183}
+{"id":10443,"url":"https://docs.sui.io/operators/data-management","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Data Indexing and Archives | Sui Documentation","text":"A full nodeFull nodeResponsible for validating blockchain activity. keeps only as much history as its pruning settings allow. Full history lives outside the node: archival indexers ingest every checkpointCheckpointCreated after transaction execution to provide a certified record of chain history. as the network produces it and write it to long-term storage. This section covers configuring pruning on your node, the archival stores that hold full history, and running indexers that turn checkpoint data into queryable databases.\n\nWhat data management options are available for Sui nodes?​\n\nPruning: A full node deletes old objectObjectThe basic unit of storage on Sui. versions and old checkpoints, including their transactions, effects, and events, from its local database after a retention window you configure.\n\nArchival stores: Archival indexers write the full chain history to long-term storage, independently of any full node's pruning. sui-checkpoint-blob-indexer writes checkpoint blobs to an object store (S3 or GCS), and sui-kvstore-alt writes checkpoints, transactions, effects, events, and objects to Bigtable, which the Archival Service serves over gRPCgRPC APIReplaces JSON-RPC on full nodes for data access.. Mysten Labs runs public instances of both; see Available Data Stores.\n\nIndexing: An indexer reads checkpoints from a full node or a checkpoint store and writes the data your application needs into a database you can query. The general-purpose indexer backs GraphQL RPCGraphQL RPCA lightweight GraphQL RPC service., and you can build a custom indexer for your own schema.\n\nHow do I manage disk usage on a Sui full node?​\n\nConfigure pruning in the authority-store-pruning-config section of your node configuration. num-epochs-to-retain sets how many epochs of old object versions the node keeps, and num-epochs-to-retain-for-checkpoints sets how many epochs of checkpoints, transactions, effects, and events it keeps. See Managing Data for recommended values.\n\nPruning does not depend on any archive. The node does not wait for data to be archived before pruning it, and it does not serve pruned data from an archive.\n\nWhat is the difference between archival and pruned data?​\n\nPruned data is deleted from the node's local database, and the node no longer serves it.\n\nArchived data is the complete checkpoint history held in an archival storeArchival StoreA long-term storage system that holds checkpoint-indexed Sui data.. Archival indexers write each checkpoint when the network produces it, not when a node prunes it, so the archive is complete regardless of how any individual node is configured.\n\nWhere to go for each need:\n\nHistorical reads: Query the Archival Service or an indexer.\n\nCatching up after falling behind: A full node can fetch missing checkpoints from a checkpoint store when its peers have already pruned them. See Archives.\n\nStarting a new node: Restore from a snapshot.\n\nData Management\nA high-level description of data management on the Sui network that you can use to optimize your Sui full node configuration.\n→\nAvailable Data Stores\nReference for all Sui Foundation-managed checkpoint stores, snapshot buckets, and archival endpoints available for Sui Mainnet and Testnet, including retention policies, credential requirements, and recommended use cases.\n→\nGraphQL and General-Purpose Indexer\nSetup instructions for running the indexer, consistent store, and GraphQL in production.\n→\nRunning a Remote Store\nSetup instructions for running the checkpoint blob indexer to populate a remote store with protobuf checkpoint blobs.\n→\nRunning the Archival Store and Service\nSetup instructions for running the archival indexer, Bigtable store, and gRPC service in production.\n→\nArchive Data\nThe archive is a historical record of all transactions on Sui. Enable archiving on your Full nodes as a best practice.\n→\n\nWhat data management options are available for Sui nodes?\nHow do I manage disk usage on a Sui full node?\nWhat is the difference between archival and pruned data?\n\nWas this page helpful?","tokens":1010,"crawled_at":1791194851786}
+{"id":10444,"url":"https://gov.uniswap.org/t/tax-year-2025-duni-tax-return-draft/26081","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Tax Year 2025 DUNI Tax Return [DRAFT] - Service Providers - Uniswap Governance","text":"Tax Year 2025 DUNI Tax Return [DRAFT]\n\nService Providers\n\nCowrie-Justin\n\nApril 10, 2026, 11:30pm\n\n1\n\nHello,\n\nAttached is a draft of the Tax Year 2025 U.S. Corporation Income Tax Return for DUNI. Prior to filing the return, Cowrie – Administrator Services provides a copy of the draft return to allow the community to comment and to answer any questions.\n\nWe plan on filing this return prior to the deadline and to make payments of any tax outstanding by Wednesday, April 15, 2026. While the IRS allows for an extension – the extension is simply a filing extension and does not impact the timing of any payments. As the information is complete and the return is ready to be filed, there is no need to extend the filing period.\n\nA few other important items:\n\n· DUNI has elected to be taxed as a corporation, so the proper tax return filing is Form 1120, U.S. Corporation Income Tax Return.\n\n· This return was prepared for DUNI by Cowrie - Administrator Services and will be signed by David Kerr as a member of the DUNA.\n\n· The return should be reviewed in conjunction with the Q4 and Year End 2025 Financial Statements and Tax Update, which contains the financial statements and important information about revenue and expense recognition, among other items.\n\n· Any payments you received from DUNI during 2025, regardless of the form (i.e., tokens or USD), should be reported as income on your personal tax return. Apart from reporting those payments, the corporate tax return does not impact your personal tax return, nor does it create any personal tax obligations for you.\n\nThank you,\n\nJustin\n\n3 Likes\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nCowrie – Administrator Services DUNI Tax Update\n\nService Providers\n\n0\n\n121\n\nFebruary 25, 2026\n\n[GOVERNANCE PROPOSAL] - Establish Uniswap Governance as “DUNI,” a Wyoming DUNA\n\nRequests for Comment\n\n18\n\n7932\n\nAugust 29, 2025\n\nUniswap Foundation 990 filing\n\nGovernance-Meta\n\n0\n\n194\n\nDecember 23, 2025\n\nTaxation, taxes\n\nUncategorized\n\n8\n\n2615\n\nMay 6, 2021\n\n\"Fee Switch\" Pilot Update & Vote\n\nRequests for Comment\n\n43\n\n23343\n\nMarch 17, 2023","tokens":522,"crawled_at":1791194854645}
+{"id":10445,"url":"https://docs.ethena.fi/overview/off-exchange-custody","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Off Exchange Custody | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nThe single largest historical risk to a synthetic-dollar protocol is the custody of its backing assets. The collapse of FTX in 2022 demonstrated, at scale, that holding assets on a centralised derivatives exchange exposes those assets to the operational, solvency, and legal risk of the exchange itself.\nA protocol that places backing directly on exchange wallets - even with the best counterparties - accepts that any exchange-level failure could lock or impair those assets and, with them, the backing of the protocol's liabilities.\nEthena's hedging operations depend on access to centralised derivatives venues, which provide the deepest and most liquid markets for the perpetual and deliverable futures used to hedge USDe backing. The protocol's custody architecture is designed to allow this access without taking on the exchange-level custody risk that has historically accompanied it.\nOff-Exchange Settlement\nEthena holds its backing assets with a small set of regulated, institutional-grade custody providers - Copper, Ceffu, Kraken and Anchorage Digital - through arrangements collectively referred to as Off-Exchange Settlement (OES).\nThe defining mechanic of OES is the separation of custody from margining. Backing assets remain in custody with the OES provider at all times. To support a hedging position at a centralised exchange, the OES provider delegates - but does not transfer - a notional value of those assets to the exchange as margin collateral.\nThe exchange recognises the delegated value for margining purposes but cannot withdraw the underlying assets. Settlement of profit and loss between exchange and custodian occurs on frequent cycles - and any payments owed by the exchange to the protocol are settled into custody at each cycle.\nThis architecture produces a set of properties that materially change the protocol's exposure to centralised exchanges.\nBenefits when accessing centralised exchanges\nBankruptcy remoteness from the exchange\nBacking assets are never held on, or owned by, the exchange. In the event of an exchange failure, the protocol's backing is not part of the exchange's estate, is not subject to its bankruptcy proceedings, and is not expected to be locked alongside other user funds. The protocol retains control of the underlying assets and is positioned to continue supporting mint and redeem activity for USDe.\nExchange-posted collateral at the custodian\nUnder OES arrangements, the exchange is required to post collateral with the custodian to support each settlement cycle. This collateral, together with the delegation structure, is designed so that PnL owed to the protocol can be settled into custody without depending on a unilateral payment from the exchange. The protocol's claim does not rest on the exchange's willingness or operational ability to send funds.\nShort and bounded exposure windows\nPnL settlement on frequent - generally daily - cycles bounds the value at risk to the exchange to the amount accumulated since the last settlement. Long, open-ended credit exposure to exchanges is replaced with a series of short, settled positions.\nSeparation of incentives\nCustody and execution are performed by separate institutions with separate ownership, regulation, and commercial incentives. An exchange cannot redirect, restrict, or rehypothecate backing assets, because it does not hold them. A custodian is not permitted to use protocol assets for any purpose other than the agreed custodial function. The protocol benefits from each party's specialisation in its own role.\nProtocol-controlled deposits and withdrawals\nEthena, not the exchange, controls the instructions to deposit assets into and withdraw assets from the OES arrangement. The protocol's internal system can scale hedging exposure up or down, move assets between custodians and exchanges, or recall assets to the minting contract to support redemption activity.\nCustodian redundancy\nThe protocol uses multiple OES providers in parallel rather than concentrating on a single custodian. Redundancy across custodians limits the impact of any single-provider operational issue and supports the protocol's ability to continue operating across stress events\nOn-chain verifiability and attestations\nWhere supported by the custodian, OES wallets can be exposed on-chain so that the existence and control of backing assets can be independently verified. Where assets are held in omnibus arrangements that preclude direct on-chain visibility, the custodial partners publish periodic attestations - at minimum monthly - confirming the value of backing held within their solutions. Together these enable users to verify, on an ongoing basis, that the backing of USDe exists and is under the protocol's control.\nHow OES supports a diversified backing portfolio\nThe same custody architecture supports the protocol's broader backing strategy as it diversifies across crypto basis trades, non-crypto basis trades, on-chain and institutional lending, and real-world assets.\nFor any strategy involving delegation of assets to a third-party venue - whether a centralised crypto exchange, or an institutional lending counterparty - the same principles apply: assets remain in segregated custody, delegation is structured to preserve the protocol's claim, and exposure to any single venue is bounded by settlement cycles and posted collateral.\nOES is the foundation that allows the protocol to operate hedging and strategies at scale across the deepest available venues while keeping the backing of USDe outside the operational and solvency perimeter of any single counterparty.\nCurrent custodial attestations and addresses for in-scope backing assets are published in the Custodian Attestations section.\n\nLast updated 3 months ago\nWas this helpful?","tokens":1464,"crawled_at":1791194864395}
+{"id":10446,"url":"https://a16zcrypto.com/posts/article/miles-jennings","domain":"a16zcrypto.com","chapter":"research","title":"Miles Jennings - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nMiles Jennings\nAnthony Albanese\n09.02.21\n\nTags & Share Tags\nannouncements\nannouncements & news\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nI first got to know Miles when I joined a16z and needed a go-to lawyer for all things crypto. As we searched to find a lawyer who truly understood crypto and the legal framework within which it operates, it became clear very quickly that there was no one better than Miles. He advised us and our portfolio companies and projects on a wide range of issues, always bringing a degree of understanding of the space that is hard to find. Our portfolio projects loved working with him and would reach out to him time and time again. Before long, it became clear that the only thing better than working with Miles as outside counsel would be working with Miles in-house.\n\nThat’s why I’m so pleased to announce that Miles has joined the a16z Crypto team as our General Counsel. This is a critically important role to support our portfolio companies and projects as the crypto industry quickly matures and as we further scale our platform and invest in projects at the vanguard of crypto.\n\nMiles was most recently a partner at Latham & Watkins, where he focused on working with startups and investors in heavily regulated sectors including life sciences and, most importantly, crypto. He has been the go-to, trusted advisor for countless startups and crypto projects, guiding them from incorporation through financings, acquisitions, token offerings, and governance matters.\n\nMiles’ experience within the sector stretches back to 2017, when he first began working with ConsenSys, a firm client, and he quickly became one of the most sought-after legal minds working in crypto. During his time at Latham, he co-chaired its global blockchain and cryptocurrency task force, which was composed of over 80 lawyers around the globe. In addition, he worked regularly with almost every venture firm operating in crypto, designing several of the investment structures they use today, and he was counsel to dozens of startups in the sector, including Aave, Bitwise, Avalanche, Element, Idle, Connext, 3Box, and Aztec. Miles was also an editor of Latham’s Global Fintech & Payments blog and has published several articles relating to legal matters relevant to crypto startups.\n\nIn our experience working in crypto, we’ve observed that the builders in this space prize experienced subject matter experts who share their values, set the bar for excellence high, are intellectually curious, and are open-minded and creative. This is particularly valuable in lawyers, as I know so well. This is exactly the kind of partner Miles has proven to be to the crypto community and we felt that, given the right platform, his impact in this space could be even bigger and more profound. I’m so excited for the teams we work with to get to know him.\n\nWelcome, Miles!\n\n###\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nCharts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":1409,"crawled_at":1791194867670}
+{"id":10447,"url":"https://docs.near.ai/cloud/guides/openai-compatibility","domain":"docs.near.ai","chapter":"crypto_ai_depin","title":"OpenAI Compatibility - NEAR AI","text":"NEAR AI Cloud implements the OpenAI-compatible inference surfaces documented below. You can use the official OpenAI client libraries for Python and JavaScript/TypeScript by changing the base URL and API key. Features that require provider-side storage or tool execution are intentionally limited; each section describes the supported contract.\n​\n\nConfiguration\n\nTo use the OpenAI SDKs with NEAR AI Cloud, you simply need to override the base_url and provide your NEAR AI api_key.\n​\n\nBase URL\n\nUse the NEAR AI Cloud Gateway base URL:\n\nhttps://cloud-api.near.ai/v1\n\n​\n\nAPI Key\n\nYou can generate your API key in the NEAR AI Cloud Dashboard.\n​\n\nRequest IDs\n\nGateway responses from https://cloud-api.near.ai/v1 include an X-Request-Id response header. Support may ask you for this value when debugging a request.\nX-Request-Id is opaque support/debugging metadata; it is not W3C traceparent or distributed trace context. If you send your own X-Request-Id, use a non-sensitive UUID value. X-Request-Id values must not contain secrets or PII. X-Org-Id and X-Workspace-Id are internal tenant headers; public clients cannot set or override them.\n​\n\nUsage Examples\n\nPython\n\nJavaScript/TypeScript\n\n​\n\nPython SDK\nFirst, install the OpenAI Python library:\n\npip install openai\n\nThen, initialize the client with NEAR AI configuration:\n\nfrom openai import OpenAI\n\nclient = OpenAI(\nbase_url=\"https://cloud-api.near.ai/v1\",\napi_key=\"YOUR_NEAR_AI_API_KEY\",\n)\n\nresponse = client.chat.completions.create(\nmodel=\"zai-org/GLM-5.1-FP8\",\nmessages=[\n{\"role\": \"system\", \"content\": \"You are a helpful assistant.\"},\n{\"role\": \"user\", \"content\": \"Explain quantum computing in simple terms.\"}\n],\ntemperature=0.7,\nmax_tokens=500\n)\n\nprint(response.choices[0].message.content)\n\n​\n\nAsync Usage\n\nimport asyncio\nfrom openai import AsyncOpenAI\n\nclient = AsyncOpenAI(\nbase_url=\"https://cloud-api.near.ai/v1\",\napi_key=\"YOUR_NEAR_AI_API_KEY\",\n)\n\nasync def main():\nstream = await client.chat.completions.create(\nmodel=\"zai-org/GLM-5.1-FP8\",\nmessages=[{\"role\": \"user\", \"content\": \"Tell me a story about space.\"}],\nstream=True,\n)\n\nasync for chunk in stream:\nif chunk.choices[0].delta.content is not None:\nprint(chunk.choices[0].delta.content, end=\"\")\n\nasyncio.run(main())\n\n​\n\nNode.js / TypeScript SDK\nFirst, install the OpenAI Node.js library:\n\nnpm install openai\n\nThen, initialize the client with NEAR AI configuration:\n\nimport OpenAI from 'openai';\n\nconst openai = new OpenAI({\nbaseURL: 'https://cloud-api.near.ai/v1',\napiKey: 'YOUR_NEAR_AI_API_KEY',\n});\n\nasync function main() {\nconst completion = await openai.chat.completions.create({\nmessages: [{ role: 'user', content: 'What is the capital of France?' }],\nmodel: 'zai-org/GLM-5.1-FP8',\n});\n\nconsole.log(completion.choices[0].message.content);\n}\n\nmain();\n\n​\n\nStreaming Example\n\nimport OpenAI from 'openai';\n\nconst openai = new OpenAI({\nbaseURL: 'https://cloud-api.near.ai/v1',\napiKey: 'YOUR_NEAR_AI_API_KEY',\n});\n\nasync function main() {\nconst stream = await openai.chat.completions.create({\nmodel: 'zai-org/GLM-5.1-FP8',\nmessages: [{ role: 'user', content: 'Write a haiku about coding.' }],\nstream: true,\n});\n\nfor await (const chunk of stream) {\nprocess.stdout.write(chunk.choices[0]?.delta?.content || '');\n}\n}\n\nmain();\n\n​\n\nSupported Features\n\nNEAR AI Cloud supports the following core OpenAI API features:\n\nChat Completions (/v1/chat/completions) - Including tool calling, structured outputs, and reasoning\n\nCompletions (/v1/completions) - Legacy text completions\n\nModels List (/v1/models)\n\nEmbeddings (/v1/embeddings) - See Beyond Chat\n\nImages (/v1/images/generations, /v1/images/edits) - See Beyond Chat\n\nAudio Transcription (/v1/audio/transcriptions) - See Beyond Chat\n\nResponses (/v1/responses) - Stateless, store: false inference with client-managed history and custom functions; see Stateless Responses\n\nStreaming (Server-Sent Events)\n\nNEAR AI Cloud also provides non-OpenAI extensions:\n\nReranking (/v1/rerank) - Score documents against a query\n\nPrivacy classification (/v1/privacy/classify) - Detect personally identifiable information through the gateway\n\nPrivacy redaction (/v1/privacy/redact) - Gateway-only endpoint for redacting personally identifiable information\n\nAttestation & Signatures (/v1/attestation/report, /v1/signature/{chat_id}) - See Verification\n\n​\n\nStateless Responses\n\nThe Responses API preserves the OpenAI Responses input, output, and streaming shapes without storing conversation or response history. Set store: false or omit it, and include any prior context in each new request.\nPython\n\nJavaScript/TypeScript\n\nfrom openai import OpenAI\n\nclient = OpenAI(\nbase_url=\"https://cloud-api.near.ai/v1\",\napi_key=\"YOUR_NEAR_AI_API_KEY\",\n)\n\nresponse = client.responses.create(\nmodel=\"z-ai/glm-5.2\",\ninput=\"Explain confidential inference in one sentence.\",\nstore=False,\n)\n\nprint(response.output_text)\n\nimport OpenAI from 'openai';\n\nconst openai = new OpenAI({\nbaseURL: 'https://cloud-api.near.ai/v1',\napiKey: 'YOUR_NEAR_AI_API_KEY',\n});\n\nasync function main() {\nconst response = await openai.responses.create({\nmodel: 'z-ai/glm-5.2',\ninput: 'Explain confidential inference in one sentence.',\nstore: false,\n});\n\nconsole.log(response.output_text);\n}\n\nmain();\n\nSee Stateless Responses for caller-managed multi-turn history, custom function replay, retired endpoints, and unsupported server-executed tools.\n​\n\nEnvironment Variables\n\nAlternatively, you can set the environment variables to avoid hardcoding credentials in your code:\n\nexport OPENAI_BASE_URL=\"https://cloud-api.near.ai/v1\"\nexport OPENAI_API_KEY=\"your-near-ai-key\"\n\nThen you can initialize the client without arguments:\n\n# Python\nclient = OpenAI()\n\n// JavaScript\nconst openai = new OpenAI();","tokens":1421,"crawled_at":1791194872767}
+{"id":10448,"url":"https://docs.sui.io/operators/data-management/indexer-stack-setup","domain":"docs.sui.io","chapter":"layer1_layer2","title":"GraphQL and General-Purpose Indexer | Sui Documentation","text":"The GraphQL and sui-indexer-alt (Indexer) stack are part of the Sui data access infrastructure. The stack provides access to onchain data through a high-performance GraphQL service backed by a scalable and general-purpose indexerGeneral-purpose IndexerA performant and scalable implementation of the custom indexing framework.. This stack is optimized for developers who need flexible queries, structured output, and historical access to data (with configurable retention) across the Sui network.\n\nGraphQL is ideal for applications that require rich query patterns over structured data, such as fetching owned objects, transactionTransactionA number of commands that execute on inputs to define the result of the transaction. history, specific onchain attributes, and more. The GraphQL service runs on top of a Postgres-compatible database that is updated by different Indexer pipelines in parallel.\n\nThe General-purpose Indexer includes configurable checkpointCheckpointCreated after transaction execution to provide a certified record of chain history.-based pipelines that extract data from the Sui remote checkpoint store and full nodes. The pipelines write processed data to a database optimized for GraphQL query access.\n\nTogether, the GraphQL service and Indexer offer a modular and production-ready data stack for builders, wallet developers, explorers, and indexer/data providers.\n\ninfo\nJSON-RPC is disabled on Sui Foundation MainnetMainnetProduction network for live transactions and real-value assets. full nodes. The shutoff took effect the week of July 27, 2026. Sui Foundation plans full decommission, including code removal, for mid-October 2026. If your application still calls JSON-RPC, migrate to gRPC or GraphQL RPC now. For a method mapping, decision criteria, and the remaining timeline, see the JSON-RPC Migration Guide.\n\nSee RPC and Data Providers for providers that serve gRPCgRPC APIReplaces JSON-RPC on full nodes for data access. and GraphQL RPCGraphQL RPCA lightweight GraphQL RPC service. endpoints. Contact a provider directly to request access. If your provider does not yet support these interfaces, ask them to enable support, or reach the Sui Foundation team on Discord, Telegram, or Slack for help.\n\ninfo\nRefer to Access Sui Data for an overview of options to access Sui network data.\n\nSee Sui Data Access for more information on how the stack serves application queries.\n\nProduction fullnode endpoints​\n\nThe https://fullnode.mainnet.sui.io:443, https://fullnode.testnet.sui.io:443, and https://fullnode.devnet.sui.io:443 endpoints are public-good services for testing only. They are not intended for a production indexer or GraphQL stack. For every fullnode URL in this guide, use a production-grade gRPCgRPC APIReplaces JSON-RPC on full nodes for data access. endpoint from an RPC provider with sufficient capacity and retention for your workload.\n\nRequester Pays checkpointCheckpointCreated after transaction execution to provide a certified record of chain history. buckets​\n\nThe full-retention MainnetMainnetProduction network for live transactions and real-value assets. and TestnetTestnetStaging network for testing changes before production deployment. Google Cloud Storage (GCS) checkpoint buckets are Requester Pays enabled. For the full list of available checkpoint stores, snapshot endpoints, and their retention policies, see Available Data Stores. Before running a production backfill or recovery, configure Google credentials that can charge an enabled billing project:\n\n$ export GOOGLE_APPLICATION_CREDENTIALS=/path/to/gcp-credentials.json\n$ export GOOGLE_CLOUD_PROJECT=your-billing-project\n\nWorkload Identity or another supported Google credential source can replace the credential file. Every --remote-store-gcs command must also include the x-goog-user-project header. See Google Cloud's Use Requester Pays documentation for billing and IAM requirements.\n\nIndexer setup​\n\nThe indexer consists of multiple pipelines that each read, transform, and write checkpoint data to various Postgres tables. Multiple instances of the indexer can run in parallel, each configured by its own TOML file.\n\nHardware requirements​\n\nCPU: 2 cores per instance\n\nMemory: 4GB per instance\n\nInternally at Mysten Labs, indexer instances use 8 CPUs and 16 GiB of memory for backfill, and scale down to 0.5 CPU and 1 GiB of memory for normal operation at network tip.\n\nStorage requirements​\n\nThe general-purpose indexerGeneral-purpose IndexerA performant and scalable implementation of the custom indexing framework. writes to a Postgres database. The storage footprint estimations outlined below are based on the network as of early 2026, and might fluctuate in relation to network growth. These numbers should be seen as directional rather than exact figures.\n\nThe bulk of the storage is consumed by obj_versions at 8.2 TB. A pruning strategy is in development.\n\nThe unpruned tx_balance_changes table adds another 1.2 TB.\n\nA 30-day retention adds 1.8 TB on top, while a 90-day retention contributes up to an additional 3.1 TB.\n\n30-day retention:\n\nTableHeap (GB)Idx (GB)\ntx_affected_objects\n64–70\n276–397\n\ntx_calls\n27–30\n239–366\n\nev_struct_inst\n15–19\n174–267\n\ntx_affected_addresses\n17–18\n63–92\n\nev_emit_mod\n8–9\n54–85\n\ntx_digests\n8\n21–25\n\ntx_kinds\n5\n14–16\n\ncp_sequence_numbers\n10\n5\n\nTOTAL\n426–430\n1,822–1,836\n\n90-day retention:\n\nTableHeap (GB)Idx (GB)\ntx_affected_objects\n188–202\n580–752\n\ntx_calls\n82–87\n560–715\n\nev_struct_inst\n45–50\n432–531\n\ntx_affected_addresses\n50–54\n151–183\n\nev_emit_mod\n22–24\n129–167\n\ntx_digests\n24–26\n45–55\n\ntx_kinds\n15–16\n30–36\n\ncp_sequence_numbers\n10\n5\n\nTOTAL\n698–779\n2,430–3,165\n\nRun sui-indexer-alt​\n\nRun production ingestion in 2 phases: backfill from the full-retention Requester Pays GCS bucket, then stop the backfill process and restart from the saved watermarks with fullnode gRPC for steady state. Run 1 indexer process for each configuration file and assign every co-located process a unique metrics addressAddressA unique, anonymous identity on a blockchain network..\n\nPhase 1: backfill​\n\nUnprunable pipelines must start at genesis:\n\n$ sui-indexer-alt indexer \\\n--config <CONFIG_FILE> \\\n--database-url <DATABASE_URL> \\\n--remote-store-gcs <REMOTE_STORE_GCS_BUCKET> \\\n--remote-store-header \"x-goog-user-project:${GOOGLE_CLOUD_PROJECT}\" \\\n--metrics-address <UNIQUE_METRICS_ADDRESS>\n\nPrunable pipelines can start at a checkpoint based on their retention period:\n\n$ sui-indexer-alt indexer \\\n--config <CONFIG_FILE> \\\n--database-url <DATABASE_URL> \\\n--remote-store-gcs <REMOTE_STORE_GCS_BUCKET> \\\n--remote-store-header \"x-goog-user-project:${GOOGLE_CLOUD_PROJECT}\" \\\n--first-checkpoint <CHECKPOINT_NUMBER> \\\n--metrics-address <UNIQUE_METRICS_ADDRESS>\n\nFor prunable pipelines, calculate the first-checkpoint based on your retention period:\n\n30-day retention: Start from checkpoint current_checkpoint - 10368000\n\n90-day retention: Start from checkpoint current_checkpoint - 31104000\n\nCLI parameterDescription\n<CONFIG_FILE>\nPath to indexer configuration file.\n\n<DATABASE_URL>\nPostgres database connection string.\n\n<REMOTE_STORE_GCS_BUCKET>\nFull-retention GCS bucket name. Use mysten-mainnet-checkpoints-use4 for Mainnet or mysten-testnet-checkpoints-use4 for Testnet.\n\n<CHECKPOINT_NUMBER>\nFor prunable pipelines only, the checkpoint at which indexing starts.\n\n<UNIQUE_METRICS_ADDRESS>\nPrometheus bind address unique to this process, for example 127.0.0.1:9184.\n\nExamples​\n\nUnprunable pipeline from genesis:\n\n$ sui-indexer-alt indexer \\\n--config unpruned.toml \\\n--database-url postgres://username:password@localhost:5432/database \\\n--remote-store-gcs mysten-mainnet-checkpoints-use4 \\\n--remote-store-header \"x-goog-user-project:${GOOGLE_CLOUD_PROJECT}\" \\\n--metrics-address 127.0.0.1:9184\n\nPrunable pipeline with 30-day retention (assuming current checkpoint is 100,000,000):\n\n$ sui-indexer-alt indexer \\\n--config events.toml \\\n--database-url postgres://username:password@localhost:5432/database \\\n--remote-store-gcs mysten-mainnet-checkpoints-use4 \\\n--remote-store-header \"x-goog-user-project:${GOOGLE_CLOUD_PROJECT}\" \\\n--first-checkpoint 89632000 \\\n--metrics-address 127.0.0.1:9187\n\nPhase 2: steady state​\n\nAfter a backfill process reaches the network tip, stop it and restart the same configuration against a production-grade fullnode gRPC endpoint from an RPC provider. Existing pipelines resume from their committed watermarks. Use --rpc-api-url for polling and --streaming-url for low-latency checkpoint streaming:\n\n$ export FULLNODE_GRPC_URL=https://your-rpc-provider.example:443\n\n$ sui-indexer-alt indexer \\\n--config events.toml \\\n--database-url postgres://username:password@localhost:5432/database \\\n--rpc-api-url \"$FULLNODE_GRPC_URL\" \\\n--streaming-url \"$FULLNODE_GRPC_URL\" \\\n--metrics-address 127.0.0.1:9187\n\nIf recovery requires checkpoints outside the fullnode's retention, stop the process, recover from the GCS bucket, and then switch back to fullnode gRPC.\n\ninfo\nFor checkpoint ingestion, the public https://checkpoints.mainnet.sui.io and https://checkpoints.testnet.sui.io stores are for testing only. Do not use them for production backfill, recovery, fallback, or steady state. See Checkpoint Data Sources for the source matrix.\n\nRun config recommendations​\n\nUse the TOML files below; they are grouped by pipeline speed. All pipelines in an instance are limited by the slowest pipeline in that instance so these files each contain pipelines that run at approximately the same speed.\n\nYou can include an optional [ingestion] section in each TOML file to tune checkpoint ingestion. The min-cohort-boundary setting controls how the indexer groups pipelines into ingestion cohorts based on their distance from the tip. The default is 25000 checkpoints. A higher value prevents nearly caught-up pipelines from being fragmented into many small cohorts. You do not need to set this for most deployments.\n\n[ingestion]\nmin-cohort-boundary = 25000\n\ninfo\nThe example configurations linked below use a fixed concurrency of 20 for simplicity, but this leads to longer backfill times.\nWhen backfilling a pipeline, consider setting the ingest-concurrency to a higher initial concurrency, such as { kind = \"adaptive\", initial = 200, min = 50, max = 2000 }. The indexer automatically adjusts concurrency based on current load and performance.\nOnce caught up to network tip, you can manually set the max concurrency to a lower value. Mysten-internal indexers are capped at 20.\n\nConfig TOMLTypeDescriptionPipelinesBackfill timeData retentionStart checkpoint\nevents.toml\nPrunable\nLightweight event tables.\nev_emit_mod\nev_struct_inst\n\n1-2 days\nConfigurable (for example, 30 or 90 days)\nBased on retention period\n\nClick to openevents.tomlexamples/prod-config/indexer/events.toml\n[pruner]\nretention = 31104000\n\n[pipeline.ev_emit_mod.pruner]\n\n[pipeline.ev_struct_inst.pruner]\n\nobj_versions.toml\nUnprunable\nObjectObjectThe basic unit of storage on Sui. versions table containing complete object version to checkpoint mappings.\nobj_versions\n10-14 days\nMust retain all data\nGenesis (checkpoint 0)\n\nClick to openobj_versions.tomlexamples/prod-config/indexer/obj_versions.toml\n[ingestion]\ningest-concurrency = { kind = \"fixed\", value = 20 }\n\n[committer]\nwrite-concurrency = 10\n\n# obj_versions pipeline pruning not yet supported\n\n[pipeline.obj_versions]\n\ntx_affected_addresses.toml\nPrunable\nMidweight transactionTransactionA number of commands that execute on inputs to define the result of the transaction. table.\ntx_affected_addresses\n1-2 days\nConfigurable (for example, 30 or 90 days)\nBased on retention period\n\nClick to opentx_affected_addresses.tomlexamples/prod-config/indexer/tx_affected_addresses.toml\n[ingestion]\ningest-concurrency = { kind = \"fixed\", value = 20 }\n\n[committer]\nwrite-concurrency = 10\n\n[pruner]\nretention = 31104000\n\n[pipeline.tx_affected_addresses.pruner]\n\ntx_affected_objects.toml\nPrunable\nMidweight transaction table.\ntx_affected_objects\n1-2 days\nConfigurable (for example, 30 or 90 days)\nBased on retention period\n\nClick to opentx_affected_objects.tomlexamples/prod-config/indexer/tx_affected_objects.toml\n[committer]\nwrite-concurrency = 20\n\n[pruner]\nretention = 31104000\n\n[pipeline.tx_affected_objects.pruner]\n\ntx_calls.toml\nPrunable\nMidweight transaction table.\ntx_calls\n1-2 days\nConfigurable (for example, 30 or 90 days)\nBased on retention period\n\nClick to opentx_calls.tomlexamples/prod-config/indexer/tx_calls.toml\n[committer]\nwrite-concurrency = 10\n\n[pruner]\nretention = 31104000\n\n[pipeline.tx_calls.pruner]\n\ntx_kinds.toml\nPrunable\nMidweight transaction table.\ntx_kinds\n1-2 days\nConfigurable (for example, 30 or 90 days)\nBased on retention period\n\nClick to opentx_kinds.tomlexamples/prod-config/indexer/tx_kinds.toml\n[pruner]\nretention = 31104000\n\n[pipeline.tx_kinds.pruner]\n\nunpruned.toml\nUnprunable\nFoundational reference data that other queries depend on.\ncp_sequence_numbers\nkv_epoch_ends\nkv_epoch_starts\nkv_feature_flags\nkv_packages\nkv_protocol_configs\nsum_displays\ntx_balance_changes\ntx_digests\n\n2-4 days\nMust retain all data\nGenesis (checkpoint 0)\n\nClick to openunpruned.tomlexamples/prod-config/indexer/unpruned.toml\n[ingestion]\ningest-concurrency = { kind = \"fixed\", value = 20 }\n\n[pipeline.cp_sequence_numbers]\n\n[pipeline.kv_epoch_ends]\n\n[pipeline.kv_epoch_starts]\n\n[pipeline.kv_feature_flags]\n\n[pipeline.kv_packages]\n\n[pipeline.kv_protocol_configs]\n\n[pipeline.sum_displays]\n\n[pipeline.tx_balance_changes]\n\n[pipeline.tx_digests]\n\nConsistent store setup​\n\nThe consistent store maintains live ownership and balance indexes in its own RocksDB database and exposes checkpoint-consistent reads over gRPC. It does not use the Postgres DATABASE_URL and does not replace the General-purpose Indexer. Keep its database path on persistent local SSD storage.\n\nAll 4 pipelines run in 1 process. Their watermarks are independent from the Postgres indexer's watermarks, and throughput is limited by the slowest consistent-store pipeline.\n\nHardware requirements​\n\nCPU: 8 cores\n\nMemory: 32GB\n\nRestore from a formal snapshot​\n\nWithout a restore, a new consistent store must process checkpoints from genesis. For production, restore the latest formal snapshot into an empty RocksDB path before starting the service.\n\nThe restore command reads from two distinct sources:\n\nExactly 1 formal snapshot source, such as --http, --gcs, --azure, --s3, or --local.\n\nA required --remote-store-url. The restorer uses this store to map the snapshot epochEpochA period of time defined by the network. to its ending checkpoint and fetch that checkpoint; it is not the post-restore catch-up source.\n\nMainnet and Testnet restores can use https://checkpoints.mainnet.sui.io or https://checkpoints.testnet.sui.io for --remote-store-url, respectively.\n\n$ export CONSISTENT_STORE_PATH=/path/to/consistent-store\n$ mkdir -p \"$(dirname \"$CONSISTENT_STORE_PATH\")\"\n\n$ sui-indexer-alt-consistent-store restore \\\n--database-path \"$CONSISTENT_STORE_PATH\" \\\n--http https://formal-snapshot.mainnet.sui.io \\\n--remote-store-url https://checkpoints.mainnet.sui.io \\\n--object-file-concurrency 5 \\\n--pipeline address_balances \\\n--pipeline balances \\\n--pipeline object_by_owner \\\n--pipeline object_by_type \\\n--config consistent-store.toml \\\n--metrics-address 127.0.0.1:9186\n\nCLI parameterDescription\n--database-path\nEmpty path where the RocksDB database is created.\n\n--http, --gcs, --azure, --s3, or --local\nFormal snapshot source. Specify exactly one. See managed snapshots.\n\n--remote-store-url\nPublic HTTPS checkpoint store used to read the epoch mapping and selected end-of-epoch checkpoint during restore.\n\n--object-file-concurrency\nNumber of formal-snapshot object files to download concurrently.\n\n--pipeline\nRuntime pipeline name to restore. Repeat once for each required pipeline.\n\n--config\nConsistent-store TOML configuration. Only its RocksDB settings are used during restore.\n\nEach --pipeline is required because restore materializes only explicitly selected pipelines. Let the command exit successfully before starting run.\n\nUse the latest formal snapshot so the public HTTPS checkpoint store still retains its end-of-epoch checkpoint. If that checkpoint is no longer available, restore cannot complete and you must choose a newer formal snapshot.\n\nRun and catch up with fullnode gRPC​\n\nAfter restore completes, start the combined consistent-store indexer and gRPC service. The polling client catches up after the restored watermark, and streaming supplies new checkpoints at the network tip. Use a production-grade fullnode endpoint from an RPC provider:\n\n$ export FULLNODE_GRPC_URL=https://your-rpc-provider.example:443\n\n$ sui-indexer-alt-consistent-store run \\\n--database-path \"$CONSISTENT_STORE_PATH\" \\\n--rpc-api-url \"$FULLNODE_GRPC_URL\" \\\n--streaming-url \"$FULLNODE_GRPC_URL\" \\\n--rpc-listen-address 127.0.0.1:7001 \\\n--metrics-address 127.0.0.1:9186 \\\n--config consistent-store.toml\n\nWait for the service to report SERVING and for every pipeline watermark to approach the network tip before routing GraphQL traffic to it. Only 1 process can open a given RocksDB path. Back up the RocksDB path separately from Postgres, and stop the consistent-store process before taking a filesystem-level copy.\n\nIf a successfully restored watermark is older than the fullnode's retention window, use GCS for the catch-up phase:\n\n$ sui-indexer-alt-consistent-store run \\\n--database-path \"$CONSISTENT_STORE_PATH\" \\\n--remote-store-gcs mysten-mainnet-checkpoints-use4 \\\n--remote-store-header \"x-goog-user-project:${GOOGLE_CLOUD_PROJECT}\" \\\n--rpc-listen-address 127.0.0.1:7001 \\\n--metrics-address 127.0.0.1:9186 \\\n--config consistent-store.toml\n\nDo not route traffic to this temporary catch-up process. After it reaches the network tip, stop it and restart with fullnode gRPC.\n\nTo build a consistent store without a formal snapshot, run from an empty path against the full-retention GCS bucket and process from checkpoint 0. Do not set --first-checkpoint to a later checkpoint, because doing so produces incomplete ownership and balance state.\n\nFor Testnet, use https://formal-snapshot.testnet.sui.io, https://checkpoints.testnet.sui.io, and a production-grade Testnet fullnode endpoint from an RPC provider. Use the mysten-testnet-checkpoints-use4 bucket when GCS catch-up is necessary. Keep every source on the same network and use a separate RocksDB path per network.\n\nRun config recommendations​\n\nThe CLI runtime pipeline names use underscores, while the corresponding TOML keys use hyphens:\n\nRuntime pipeline (--pipeline)TOML keyDescription\naddress_balances\naddress-balances\nAddress balance accumulator state.\n\nbalances\nbalances\nCoin balance state.\n\nobject_by_owner\nobject-by-owner\nLive objects indexed by owner.\n\nobject_by_type\nobject-by-type\nLive objects indexed by type.\n\nA formal-snapshot restore of all pipelines typically takes 1–2 hours. All pipeline state must be retained.\n\nClick to openconsistent-store.tomlexamples/prod-config/consistent_store.toml\n[ingestion]\ningest-concurrency = { kind = \"fixed\", value = 20 }\n\n[pipeline.address-balances]\n\n[pipeline.balances]\n\n[pipeline.object-by-owner]\n\n[pipeline.object-by-type]\n\nGraphQL RPCGraphQL RPCA lightweight GraphQL RPC service. server setup​\n\nGraphQL RPC server reads data from the general-purpose indexer's database (Postgres), the consistent store, and the archival service.\n\nPrerequisites\n\nEnsure that all unprunable indexer pipelines (obj_versions.toml and unpruned.toml) have fully caught up to the network tip before starting the GraphQL RPC server. The GraphQL service only operates normally once these pipelines are complete.\n\nHardware requirements​\n\nCPU: 2 cores per instance\n\nMemory: 4GB per instance\n\nScale the number of nodes based on the desired read throughput requirements of your client applications.\n\nGraphQL RPC server dependencies​\n\nThe GraphQL RPC server relies on multiple backend services to fulfill different types of queries:\n\nArchival serviceArchival ServiceA gRPC API layer that exposes access to this store. (--ledger-grpc-url) provides historical data for most queries involving checkpoints, objects, and transactions.\n\nConsistent store (--consistent-store-url) serves live data for queries related to current object and balance ownership.\n\nPostgres database (--database-url) is the primary store for most queries, except for direct object and transaction lookups handled by the Archival service.\n\nFullnode gRPC (--fullnode-rpc-url) powers transaction simulation and execution.\n\nSet the appropriate service URLs in your run command based on the query types your GraphQL RPC server needs to support.\n\nRun sui-indexer-alt-graphql​\n\ninfo\nIf you use the Sui Foundation-hosted public good archival service on Testnet or Mainnet, you might encounter performance issues. The team plans to address these before the GraphQL RPC and Archival Service reach general availability.\n\nUse the following command to run a GraphQL RPC server node:\n\n$ sui-indexer-alt-graphql rpc \\\n--config <PATH_TO_GRAPHQL_CONFIG_FILE> \\\n--indexer-config <PATH_TO_INDEXER_CONFIG_FILE_1> \\\n--indexer-config <PATH_TO_INDEXER_CONFIG_FILE_2> \\\n--indexer-config <PATH_TO_INDEXER_CONFIG_FILE_3> \\\n--ledger-grpc-url <LEDGER_GRPC_URL> \\\n--consistent-store-url <CONSISTENT_STORE_URL> \\\n--database-url <DATABASE_URL> \\\n--fullnode-rpc-url <FULLNODE_GRPC_URL> \\\n--rpc-listen-address <RPC_LISTEN_ADDRESS> \\\n--metrics-address <METRICS_ADDRESS>\n\nMultiple --indexer-config parameters can be provided, one for each general-purpose indexer instance.\n\nCLI parameterDescription\nPATH_TO_GRAPHQL_CONFIG_FILE\nPath to the optional GraphQL RPC server configuration file.\n\nPATH_TO_INDEXER_CONFIG_FILE\nPath to a General-purpose Indexer configuration file; repeat for each group of pipelines.\n\nLEDGER_GRPC_URL\nArchival Service LedgerService gRPC URL.\n\nCONSISTENT_STORE_URL\nConsistent store gRPC URL. Use http:// unless you explicitly configured its TLS listener.\n\nDATABASE_URL\nPostgres database connection string.\n\nFULLNODE_GRPC_URL\nProduction-grade fullnode gRPC URL from an RPC provider, used for transaction simulation and execution.\n\nRPC_LISTEN_ADDRESS\nGraphQL bind address, for example 127.0.0.1:7000.\n\nMETRICS_ADDRESS\nPrometheus bind address unique to this process, for example 127.0.0.1:9185.\n\nExample:\n\n$ export FULLNODE_GRPC_URL=https://your-rpc-provider.example:443\n\n$ sui-indexer-alt-graphql rpc \\\n--config graphql.toml \\\n--indexer-config events.toml \\\n--indexer-config obj_versions.toml \\\n--indexer-config tx_affected_addresses.toml \\\n--indexer-config tx_affected_objects.toml \\\n--indexer-config tx_calls.toml \\\n--indexer-config tx_kinds.toml \\\n--indexer-config unpruned.toml \\\n--ledger-grpc-url https://archive.mainnet.sui.io:443 \\\n--consistent-store-url http://127.0.0.1:7001 \\\n--database-url postgres://username:password@localhost:5432/database \\\n--fullnode-rpc-url \"$FULLNODE_GRPC_URL\" \\\n--rpc-listen-address 127.0.0.1:7000 \\\n--metrics-address 127.0.0.1:9185\n\nWith these addresses, GraphQL is available at http://127.0.0.1:7000/graphql, its health check is at http://127.0.0.1:7000/health, and Prometheus metrics are at http://127.0.0.1:9185/metrics. Assign a different metrics address to every co-located indexer process; all 3 binaries otherwise default to port 9184.\n\nGenerating configuration​\n\nYou can run the GraphQL RPC server without a configuration file, which uses default values. To customize settings, generate a configuration file using the following command and edit it as needed:\n\n$ sui-indexer-alt-graphql generate-config > <PATH_TO_GRAPHQL_CONFIG_FILE>\n\nThis produces output similar to the following:\n\nClick to opengraphql.tomlexamples/prod-config/graphql.toml\n[limits]\nmutation-timeout-ms = 74000\nquery-timeout-ms = 40000\nmax-query-depth = 20\nmax-query-nodes = 300\nmax-output-nodes = 1000000\nmax-tx-payload-size = 174763\nmax-query-payload-size = 5000\ndefault-page-size = 20\nmax-page-size = 50\nmax-multi-get-size = 200\npage-size-override-fx-object-changes = 1024\npage-size-override-packages = 200\nmax-type-argument-depth = 16\nmax-type-argument-width = 32\nmax-type-nodes = 256\nmax-move-value-depth = 128\nmax-move-value-bound = 1048576\nmax-display-field-depth = 10\nmax-display-output-size = 1048576\nmax-disassembled-module-size = 1048576\n\n[health]\nmax-checkpoint-lag-ms = 300000\n\n[name-service]\npackage-address = \"0xd22b24490e0bae52676651b4f56660a5ff8022a2576e0089f79b3c88d44e08f0\"\nregistry-id = \"0xe64cd9db9f829c6cc405d9790bd71567ae07259855f4fba6f02c84f52298c106\"\nreverse-registry-id = \"0x2fd099e17a292d2bc541df474f9fafa595653848cbabb2d7a4656ec786a1969f\"\n\n[watermark]\nwatermark-polling-interval-ms = 500\n\n[zklogin]\nenv = \"Prod\"\nmax-epoch-upper-bound-delta = 30\n\nIndexer/GraphQL Postgres-compatible database setup​\n\nBoth the indexer and GraphQL server require a Postgres-compatible database shared between them.\n\nThese GraphQL request throughputs were tested against the following recommended specs:\n\n500 requests per second when the indexer is backfilling from genesis or running a restore\n\n1000 requests per second when the indexer is indexing from the network tip (~4.25 checkpoints per second)\n\nAlloyDB Omni​\n\nAlloyDB Omni recommends 8GB RAM per vCPU. See the AlloyDB Omni hardware requirements for details. Allocating less than this results in the database closing indexer and GraphQL connections during load testing.\n\nHardware requirements​\n\nCPU: 6 cores\n\nMemory: 48GB\n\nVanilla Postgres​\n\nYou can also use a standard Postgres installation.\n\nHardware requirements​\n\nCPU: 6 cores\n\nMemory: 48GB\n\nWatermark debugging​\n\nThe indexer tracks progress for each pipeline using watermark records in the watermarks table. Each record stores the last successfully processed checkpoint for that pipeline. Use these queries to diagnose indexer health:\n\nCheck pipeline progress​\n\nQuery the watermarks table to see the current checkpoint for each pipeline:\n\nSELECT pipeline, checkpoint_hi_inclusive, epoch_hi_inclusive\nFROM watermarks\nORDER BY pipeline;\n\nIf a pipeline's checkpoint_hi_inclusive is significantly behind the network tip, that pipeline is lagging. Compare against the current network checkpoint (visible on SuiVision or through curl -s http://localhost:9184/metrics | grep watermark_checkpoint). The watermark_checkpoint metric tracks each pipeline's current position; watermark_checkpoint_in_db shows the last position persisted to the database.\n\nIf you also run the GraphQL RPC server, its health endpoint (for example, http://localhost:7000/health) reports lag broken down by data source and pipeline.\n\nDiagnose a stalled pipeline​\n\nA stalled watermark is the starting point for most indexer investigations. Narrow the cause to one of three categories before taking action:\n\nCheckpoints not being downloaded (upstream): The ingestion layer cannot fetch new checkpoints from the data source. Check network connectivity to your gRPC endpoint or GCS bucket. Verify the fullnode or checkpoint store is healthy and serving the expected checkpoint range. The ingested_checkpoint_timestamp_lag Prometheus metric shows how far behind the ingestion layer is.\n\nPipeline processing error: The pipeline fetched checkpoints but fails to transform or process them. Check the indexer logs filtered by the pipeline name for error messages. Common causes include schema mismatches after a protocol upgrade or unexpected data in a specific checkpoint.\n\nCommits not going through (downstream): The pipeline processed checkpoints but cannot write results to the database. Check Postgres connectivity, disk space, and lock contention. Long-running autovacuum on the pipeline's target table can block writes. Query pg_stat_activity for active vacuum processes on that table.\n\nThe cp_sequence_numbers pipeline​\n\nThe cp_sequence_numbers pipeline maps checkpoint sequence numbers to their transaction ranges. The GraphQL RPC server depends on this pipeline to translate checkpoint-based queries into transaction lookups. If this pipeline is missing or lagging:\n\nGraphQL queries that filter by checkpoint range return incomplete or empty results.\n\nThe GraphQL server logs warnings about missing checkpoint data.\n\nTo fix, ensure cp_sequence_numbers is included in your indexer's pipeline list. If you did not include it during initial setup, follow the adding a new pipeline procedure to add it.\n\nIndexer troubleshooting​\n\nThe following table lists common starting points for investigation. Most symptoms can result from multiple confounding factors, so treat these as initial hypotheses rather than definitive diagnoses.\n\nSymptomCommon causeSuggested mitigation\nAll pipelines stalled at the same checkpoint\nPostgres connection lost or disk full\nCheck Postgres connectivity and disk space. Restart the indexer after fixing.\n\nOne pipeline lagging, others current\nPipeline-specific error (schema mismatch, data issue)\nCheck indexer logs for that pipeline. If corrupted, re-index from a checkpoint.\n\nGraphQL returns empty results for valid queries\ncp_sequence_numbers pipeline missing or lagging\nAdd the pipeline or wait for it to catch up.\n\nWatermark not advancing after restart\nPipeline resuming from its last committed watermark, which is expected behavior\nInvestigate using the three categories above (upstream, processing, downstream). Only delete the watermark record as a last resort (see re-indexing).\n\nPostgres table bloat after enabling pruning\nDead rows accumulating faster than autovacuum\nApply the autovacuum tuning settings.\n\nAdding a new pipeline​\n\nAdding a new pipeline to an existing indexer currently requires these steps:\n\nStart a new pipeline in its own indexer instance, optionally with the --first-checkpoint <checkpoint> flag set if you want to start from a checkpoint after genesis.\n\nThe --first-checkpoint flag is only respected if no watermark record exists for the pipeline (the pipeline has not run before). You must manually remove the watermark record if you want to run the pipeline with a different value of --first-checkpoint, or it is ignored.\n\nAfter the new pipeline catches up to the tip of the network, you can optionally merge it into another indexer instance.\n\nRe-indexing from a different checkpoint​\n\nOnce the pipeline starts indexing data and the indexer starts recording watermarks, future runs of the pipeline ignore the --first-checkpoint flag and always resume from the last recorded checkpoint.\n\nTo restart and index from a different initial checkpoint, delete the watermark record for that pipeline. Delete the existing data for that pipeline as well to avoid any data inconsistencies.\n\nUse the following template for the general-purpose indexer to write to Postgres.\n\nBEGIN;\n\n-- One statement per pipeline to re-index\nTRUNCATE TABLE ev_emit_mod;\n\nDELETE FROM watermarks\nWHERE pipeline IN (\n-- List all pipelines to re-index\n'ev_emit_mod'\n);\n\nSELECT * FROM WATERMARKS; -- Verify that the watermark record(s) have been deleted\n\n-- Verify that the tables have been cleared\n\nCOMMIT;\n\nReducing indexer pipeline table and index bloat​\n\nBloat occurs when dead rows from deletes accumulate faster than autovacuum can reclaim them. This happens in two cases:\n\nYou enable pruning on a previously unpruned pipeline.\n\nYou reduce the retention period on an already-pruned pipeline.\n\nMysten Labs uses the following autovacuum settings for a 32-vCPU, 256 GiB Postgres instance. Adjust these proportionally for your setup:\n\nParameterValue\nautovacuum_max_workers\n8\n\nautovacuum_vacuum_cost_limit\n8000\n\nautovacuum_vacuum_scale_factor\n0.01\n\nmaintenance_work_mem\n13GB\n\nmax_parallel_maintenance_workers\n4\n\nWhile autovacuum enables reusing dead rows for future inserts, it does not return reclaimed disk space to the operating system. The on-disk footprint remains until you compact tables and indexes using one of the following tools:\n\nToolTypeACCESS EXCLUSIVE lockingSchedulableLink\nVACUUM FULL\nBuilt-in\nEntire operation\nNo\nPostgreSQL VACUUM documentation\n\npg_repack\nExtension\nBriefly during initial and final step\nNo\npg_repack documentation\n\npg_squeeze\nExtension\nBriefly during final step\nYes\npg_squeeze on GitHub\n\nRelated topics\n\nData Access Interfaces\nOverview of the types of data access mechanisms available in Sui.\ngRPC\nUse the Sui Full Node gRPC API for high-performance, type-safe blockchain data access with Protocol Buffers serialization.\nGraphQL for Sui RPC\nLearn the core concepts for working with GraphQL on Sui RPC, including request headers, query composition with variables and fragments, pagination strategies, query scope, service limits, and the components of the GraphQL and General-purpose Indexer stack.\nJSON-RPC Migration Guide\nChoose between gRPC and GraphQL RPC when migrating from the deprecated JSON-RPC API. Includes a method mapping, decision criteria, and common migration gotchas.\n\nProduction fullnode endpoints\nRequester Pays checkpoint buckets\nIndexer setupRun sui-indexer-alt\nRun config recommendations\n\nConsistent store setupRestore from a formal snapshot\nRun and catch up with fullnode gRPC\nRun config recommendations\n\nGraphQL RPC server setupGraphQL RPC server dependencies\nRun sui-indexer-alt-graphql\nGenerating configuration\n\nIndexer/GraphQL Postgres-compatible database setupAlloyDB Omni\nVanilla Postgres\n\nWatermark debuggingCheck pipeline progress\nDiagnose a stalled pipeline\nThe cp_sequence_numbers pipeline\nIndexer troubleshooting\n\nAdding a new pipeline\nRe-indexing from a different checkpoint\nReducing indexer pipeline table and index bloat\n\nWas this page helpful?","tokens":8324,"crawled_at":1791194874043}
+{"id":10449,"url":"https://gov.uniswap.org/t/tally-uniswap-communication-thread/25133","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Tally Uniswap Communication thread - Service Providers - Uniswap Governance","text":"Tally Uniswap Communication thread\n\nService Providers\n\ndennisonb\n\nJanuary 6, 2025, 3:11pm\n\n1\n\nHappy New Year!\n\nDennison from Tally.xyz here. This will be our official thread that we will use to update the Uniswap DAO about our roadmap, milestones, and goals for the Uniswap DAO as laid out in the Tally Service Agreement Proposal.\n\nThis thread can be used to ask questions, suggest features, and generally communicate with Tally in a central spot. This thread ideally should not be used for support requests as we have set up Intercom to help track support requests and issues.\n\nKey info:\n\nTally API Status + Uptime: https://status.tally.xyz/\n\nTo report bugs, the official communication channel is Intercom. This tool will allow us to more effectively track support times and organize our incident response.\n\nIntercom can be found in the lower right-hand side of the Tally website.\n\nTally Intercom Support Request1920×1308 155 KB\n\nAccountability\n\nQuarterly report\n\nDetailing key achievements, including uptime metrics, notes from Community Calls, support metrics, as well as enhancements to the Uniswap DAO’s governance on Tally.\n\nTally usage\n\nWe will continue to track the number of proposals and % of votes per proposal made on Tally and report on those to the DAO.\n\nRoadmap feature usage and requests\n\nAs we roll out new features, we will track usage of those features as well as maintain a forum thread in Uniswap where folks can offer feature suggestions.\n\n(We’ve already requested the foundation create a Service Providers Thread where we can report.)\n\nMonthly office hours\n\nAn open feedback session for Uniswap DAO contributors to suggest new features and contribute to our roadmap. We’re going to ask the foundation if this could go before or after the community call, but we’re open.\n\nUptime and availability\n\nSystem uptime: 99% monthly uptime, ensuring the system is accessible with minimal disruptions.\n\nScheduled downtime: Maximum of 2% monthly allowance for scheduled maintenance, communicated in advance.\n\nResponse and resolution time\n\nFor the response time to count, the report needs to be made through Intercom so we can properly track resolution time. (Obviously, you can still reach out via Telegram.)\n\nIncident response time: Initial response within 4 hours for high-priority incidents (e.g., outages) during work hours in the United States, and 24 hours for incidents outside of working hours and low-priority issues.\n\nResolution time: Resolution or workaround within 8 hours for high-priority incidents (e.g., outages) during working hours in the United States, and 24 hours for incidents outside of working hours.\n\nMaintenance and support\n\nBug resolution: Resolution of non-critical bugs within 5 business days and critical bugs within 1 business day. For bugs that are not possible to resolve in this time frame, a post-mortem analysis will be shared with the DAO following resolution.\n\nRegular maintenance updates: Regular monthly maintenance updates, including minor upgrades, patches, and performance improvements.\n\nTally Feature Roadmap (Q1/Q2)\n\nHere is a list of features Tally is working on for its Q1/Q2 roadmap. We’re excited to bring these services and features to the Uniswap Community. We will be holding regular office hours to speak with community members about other features or needs they have.\n\nUniStaker: We will operate a UniStaker interface, and if staking passes, we will work with the community to make it a success.\n\nGasless Voting: The previous gasless voting service in Uniswap (Uni.vote) has shut down. We will operate a gas-free voting relayer for the Uniswap DAO. This would allow delegates and voters to participate in Uniswap without spending their own ETH. We will reach out to the foundation and UAC about steps to fund the relayer. This service would be operated as part of the service agreement but requires regularly topping up with ETH to cover relayer gas. Learn more about Tally Relay.\n\nForum Bot: The Tally Forum Bot connects to the forum and updates the community automatically on changes in proposal statuses.\n\nOptimistic Governance: We expect to have Optimistic Governance support by the end of Q2. This has been a frequent request by members and delegates of the Uniswap DAO community. This tool can be used for creating more efficient working groups and communities by allowing proposals to pass optimistically while leaving the DAO the ability to veto a proposal. The DAO can start considering where they might want to implement this new Tally feature.\n\nIntegrating the UAC onto Tally: While we plan to tackle the body of this feature in Q3/Q4, we will start integration in Q2 with some early features supporting the UAC on the Uniswap DAO page.\n\nAs members and participants in Uniswap since the inception of the DAO, we are really excited to get started on what is shaping up to be a very exciting 2025!\n\nhands.png293×100 31 KB\n\n7 Likes\n\nUniswap Accountability Committee (UAC): Season 3 Report\n\ndennisonb\n\nJanuary 9, 2025, 5:13pm\n\n2\n\nUpdate: For Support requests, we can also accept support inbound at: support@tally.xyz\n\nWe monitor this quarter to see which tool is more effective.\n\n2 Likes\n\ndennisonb\n\nJanuary 16, 2025, 8:51pm\n\n3\n\n1781×900 32.2 KB\n\nUniswap DAO members have spent over $300k in gas fees participating in the DAO.\n\nBut no more! The Relayer for Gasless Delegation and Voting is live. So token holder and delegates can delegate and vote at no cost to themselves.\n\nUsers can see this when they go to delegate or vote. The minimum threshold (spam prevention) for using this features is 10UNI.\n\n4 Likes\n\nDoo_StableLab\n\nJanuary 17, 2025, 1:17pm\n\n4\n\nExcited to try it in next votings!\n\nkfx\n\nFebruary 14, 2025, 10:23am\n\n5\n\nJust for the record, I’ve been in talks with Dennison about getting Tally’s support for a checkbox that would indicate agreement to the Uniswap DAO Principles (and a link to the principles and place where the delegate has disclosed their conflicts of interest).\n\nSupport would be much appreciated, as that would allow to include agreeing to the principles as requisite for delegate rewards program, treasury delegation program, etc.\n\n4 Likes\n\ndennisonb\n\nMarch 27, 2025, 5:53pm\n\n6\n\nYeah it’s definitely in our list!\n\ndennisonb\n\nApril 2, 2025, 2:34pm\n\n7\n\nTally Q1 2025 Update:\n\nHello folks! It’s been the first quarter of the Tally <> Uniswap service agreement and want to share our updates.\n\nWe’ve held monthly office hours (I see you @Sinkas !) where we have had a chance to speak with delegates about our work. Generally the session has been free flowing and lots of freeform discussion around governance, Uniswap, features on Tally and crypto in general. If it wasn’t so early in the day EST time, I’d say it would be a great time to grab a beer and hang out!\n\nProduct Improvements:\n\nUniChain Support is live on Tally!\n\nThis wasn’t planned on our roadmap but with UniChain going live we moved quickly to support it on Launch. This means people can now deploy DAOs and connect them to Tally to operate them. For future quarters we’re thinking about what sort of tooling we could build to make the process of launching even simpler for teams.\n\nhttps://x.com/tallyxyz/status/1901676876374196434\n\nTally Unichain4096×4096 254 KB\n\nGasless Voting + (also delegation)\n\ngasless900×455 41.3 KB\n\nWe turned on this feature this quarter and we’ve gotten good feedback that people enjoy the feature.\n\nPreliminary analysis suggests that this feature has been a big success. Looking at Etherscan we can see that there have been about 194 votes cast via signature (the method the relayer users) in the past quarter. Prior to turning on Tally Gasless voting, the next most recent vote via signature was over two years prior. Huge uptake!\n\nWe’re working on coming up with a better way to track this kind of usage, so hopefully next quarter we’ll be able to show a bit more of a detailed breakdown across voting types.\n\nSocial Layer Analytics (Tallylitics)\n\nhttp://www.tallylitics.xyz/public/dashboard/f518fef1-a977-4590-a95d-82c4eb04e08e\n\n(ping me if it doesn’t load- I can prepare a PDF version)\n\nThis dashboard allows the DAO to explore the off chain social layer of the Uniswap DAO. It tracks forum participants, media, token price, proposals and more. We’ll be expanding this as we get feedback over the next couple quarters. Let us know if there are any ideas about what else we can be tracking. Some feedback we’ve gotten is tracking telegram, adding he ability to set custom date ranges and more. Currently we’re unsure of whether or not we will integrate it with the main Tally product, but thats something we’re considering as well.\n\nScreenshot 2025-03-28 at 11.23.33 AM1976×586 246 KB\n\nUniStaker\n\nWhile staking isn’t live yet in Uniswap we have worked on an updated advanced staking interface for when it goes live. Some features that will be built into our advanced staking interface:\n\nUsers can have multiple staked positions\n\nEach position can have its own delegate\n\nThis opens up the usage of UniStaker as tool for partial delegation as well, and excited additional feature.\n\nScreenshot 2025-04-02 at 10.27.42 AM2010×1186 180 KB\n\nTally Analytics:\n\nLive Dashboard for Q1 2025 (Highlight: $138m transferred on Tally!), some interesting trends have emerged, a high level of (most likely) programatic spam voting is visible on the last three proposals. Perhaps airdrop farming from participants hopeful of some sort of future airdrop.\n\nScreenshot 2025-03-28 at 11.28.29 AM1586×506 36.9 KB\n\nExplore the Tally reporting docs metabase:\n\nhttps://tally.metabaseapp.com/public/dashboard/660d3c49-e8cd-47a8-bd07-de6a273eb35e\n\nWe’re working on a better way to break down reporting data regarding our metrics, we are going to prioritize this for Q2.\n\nSystem stats for the Quarter (no downtime!)\n\nhttps://status.tally.xyz/\n\nSupport:\n\nWe had two issues we worked on this quarter:\n\nCorrect quorum reporting for Uniswap to include only ‘Yes’ votes (Resolved same day it was reported)\n\nDelegate reported some instances of failed voting transactions (Transient error we could not reproduce)\n\nCommunity Call Summaries:\n\nJanuary\n\nFebruary\n\nMarch\n\nIn general, we are reconsidering community call summaries. The feedback from delegates in office hours has been this is not a very helpful or useful for the community. The foundation already does a good job making them available on the forum and there isn’t a demand for a transcribed version.\n\nLooking forward:\n\nIn Q2 we are re-evaluating some of our deliverables based on feedback we’ve received this quarter. We haven’t made a decision yet but we are considering some alternatives to Optimistic Governance (for example, more robust safe Multisig support, and security sprint in light of the recent SAFE hack). In general we expect the roadmap as detailed in this forum thread will be a bit flexible to remain nimble and responsive to DAO needs. But we will keep the community informed!\n\nThank you everyone!\n\n3 Likes\n\nkpk\n\nApril 10, 2025, 8:24am\n\n8\n\nThank you @dennisonb for the update! The Social Layer Analytics dashboard provides valuable insights that could greatly inform future iterations of programs assessing delegate engagement and their contributions to the DAO.\n\ncliffton\n\nJune 30, 2025, 7:25am\n\n9\n\nTally Q2 2025 Update:\n\nHello everyone! Taking over these updates from @dennison moving forward - by way of a quick intro, Cliff here, and I recently joined Tally as Head of Strategy, and was previously leading governance in Arbitrum and dYdX.\n\nQ2 of the Tally <> Uniswap service agreement has officially concluded, and we wanted to share our updates.\n\nSeatbelt Integration\n\nOur headline in Q2 is the successful launch of Seatbelt inside Tally’s Uniswap proposal pages! Seatbelt is the security-simulation framework co-developed by Uniswap Labs and ScopeLift that runs:\n\na full Tenderly replay of every live proposal,\n\nchecks contract verification,\n\ndecodes calldata,\n\nruns Slither static-analysis, and\n\nproduces a human-readable report.\n\nSince June 21, 2025 every Uniswap proposal on Tally now carries a “Security Report” tab that exposes this information directly in the UI, and is archived in the Uniswap Foundation fork of the seatbelt repository. The integration draws on the original Uniswap Labs specification and ScopeLift’s technical blueprint for cross-DAO simulations.\n\n1340×1400 233 KB\n\nIn practice, delegates no longer need to open GitHub or Tenderly to understand what a proposal will do; the full state-diff, external-call trace, and any Slither warnings are visible alongside the “Discussion” and “Transactions” panels before a vote is cast.\n\nRead the in-depth announcement here!\n\nAnalytics\n\nThe public Tallylitics dashboard and the Tally Analytics metabase dashboard shows that forum engagement declined slightly in Q2, which could be attributed to a lighter on-chain calendar.\n\nRoughly the same number of unique posters contributed as in Q1, and the 2 most-visited discussion threads centred on the DUNA wrapper and fee-switch design.\n\nInternal analytics from our Metabase dashboard register nine new proposals and 815 unique voting wallets between 1 April and 30 June, a single-digit percentage dip from Q1 that tracks the broader market’s quieter spring. Signature or gas-relayed ballots continue to represent about one-fifth of all votes, suggesting that UX improvements made earlier in the year have retained users.\n\nOn the reliability front, Tally recorded a 100 % application and API availability for the period, and a 99.984% uptime for custom domains. Specifically,\n\nThe Tally API experienced issues for 3 seconds on Jun 12, 2025 at 08:10pm CEST due to a severe Google Cloud outage, and\n\nCustom Domains were down on 2 occasions - the first on April 29, 2025 for 13 minutes, and the second on Jun 2, 2025 for 6 minutes. The Uniswap DAO, Uniswap Foundation, and the Uniswap Accountability Committee (UAC) did not surface any issues during these outages.\n\nUAC page\n\nWe started building out the UAC page to increase visibility on Tally in Q2, but got feedback during the process that we should find a way to do it in a more privacy preserving way. At the moment, we’ve paused work on it while we reassess next steps forward.\n\nMonthly Office Hours\n\nCommunity engagement through live calls has not met expectations, and attendance has averaged fewer than ten participants. As flagged by @dennison in the Q1 update, the feedback from delegates in office hours has been that this is not very helpful or useful for the community. The foundation already does a good job making them available on the forum and there isn’t a demand for a transcribed version.\n\nTo ensure responsiveness without imposing on delegates’ calendars, we will instead commit to a first reply within 2 business days to any question posted in the Tally Uniswap Communication Thread. If the UAC or wider DAO still prefers monthly calls we are, of course, happy to continue hosting them.\n\nLooking ahead - Q3 and Q4\n\nLooking ahead to the second half of 2025 we are likely going to be working 2 streams of work, and will work closely with the UF and UAC on priority setting.\n\nExtending Seatbelt support for L2 transactions.\n\nSupporting the DUNA and fee switch implementations.\n\nDuring July we will solicit priorities from the Foundation, the UAC, and top delegates, and the resulting Q3-Q4 roadmap, with concrete milestones will be posted in this same thread.\n\nAs always, we welcome feedback and stand ready to iterate!\n\n–\n\nAs a cool callout, Tally shipped clarity.tally.xyz, a free regulatory-intelligence hub that tracks the CLARITY Act and other U.S. rule-makings in real time to help Uniswap contributors stay ahead of the policy curve. We’d love for the Uniswap community to have try this AI tool out, and are looking forward to getting feedback on whether this is useful, and how we can improve this moving forward!\n\n2 Likes\n\nSEEDGov\n\nJune 30, 2025, 5:43pm\n\n10\n\nGreat contribution with Tallylitics!\n\nWe have a few questions about it:\n\nHow do you define or evaluate the concept of “Forum Post Quality”? Since post quality is inherently subjective, we’re curious to understand how you’ve automated its assessment in an objective way.\n\nAnd related to that, in the “Users” section, how do you establish or measure all the listed attributes—such as quality, relevance, logical reasoning, constructiveness, persuasiveness, etc.? These are also quite subjective concepts, so we’re interested in learning what criteria or methodology you used to quantify and score them.\n\ncliffton\n\nJuly 8, 2025, 3:51am\n\n11\n\nThank you for the question and sorry for the late reply here!\n\nOn Forum Post Quality\n\nFor each forum thread, Tallylitics combines 3 objective signals into a single Post Quality score.\n\nEngagement: Unique views, likes, and reply depth captured at 30- and 90-day marks to gauge whether interest is sustained.\n\nSignal-to-action: A thread gains additional weight if the discussion advances to an offchain vote on Snapshot, and subsequently an onchain proposal on Tally. Progression in the governance lifecycle is a key indicator of initial forum post quality.\n\nAdjustments for recency bias - This keeps newer or still-active conversations from being crowded out by older, marquee forum threads. These inputs are pure counts taken from Discourse, Snapshot, and on-chain data, and no manual judgment enters the calculation.\n\nOn Users\n\nUser scores are primarily determined based on the quality of the users���s post(s). This is essentially the median post quality across everything that user has written, from likes, views, replies, replies from proposal author, time between last posted comment and post creation date, etc. These are all available through the Discourse API, which the metabase query reads from.\n\nOther factors include:\n\nFrequency of quality replies\n\nFrequency of creating new posts\n\nProposal creation on Snapshot and Tally\n\nWe agree that quality, relevance, logical reasoning, constructiveness, persuasiveness are all ultimately subjective, and are happy to work with @SEEDGov refine the weightings to better represent these metrics to the DAO.\n\ncliffton\n\nOctober 8, 2025, 2:03am\n\n12\n\nTally Q3 2025 Update\n\nHello everyone! Q3 of the Tally <> Uniswap service agreement has concluded a week ago, and we’re excited to share our progress.\n\nDUNA Tooling – Tally’s Q3 Headline\n\nOur primary focus this quarter has been gathering feedback from the Uniswap Foundation, the Uniswap Accountability Committee (UAC), and Cowrie LLC, on scope requirements and build dedicated DUNA tooling on Tally. We expect this feature to launch in early Q4 2025. Here’s a preview of what’s to come.\n\nDUNA-homepage1366×1453 105 KB\n\nDUNA-requirement-checklist1366×1453 185 KB\n\nDUNA-financial-reports1366×1453 103 KB\n\nThe DUNA integration will provide an intuitive entry point for anyone reviewing Uniswap’s governance on Tally to understand [DUNI](https://www.uniswapfoundation.org/duni) and access all relevant materials in one place. We believe this sets an important precedent for decentralized organizations, and we anticipate many other DAOs will follow Uniswap’s lead in adopting this legal framework.\n\nWe’re eager to update the community on the official launch shortly and are honored to support Uniswap in this groundbreaking governance evolution.\n\nSunsetting Tallylitics\n\nAfter evaluating community engagement and feedback, we’ve made the decision to discontinue maintenance of the Tallylitics dashboard. Adoption has been lower than anticipated, and we want to focus our resources where they can deliver the most value to the DAO.\n\nMoving forward, we will work closely with the Uniswap Foundation and the UAC to identify and prioritize other governance initiatives where Tally can meaningfully contribute.\n\nLooking Ahead\n\nAs we enter Q4, our immediate priorities are:\n\nLaunching the DUNA tooling integration and gathering community feedback\n\nCollaborating with the Foundation and UAC to define the next phase of governance infrastructure needs\n\nContinuing our commitment to system reliability and responsiveness\n\nAs always, we welcome feedback and stand ready to iterate. We remain committed partners in Uniswap’s governance journey and look forward to the work ahead.\n\nThank you for your continued trust and collaboration!\n\ncliffton\n\nJanuary 12, 2026, 2:37pm\n\n13\n\nTally 2025 Year in Review & Q1 2026 Update\n\nHello Uniswap Community!\n\nAs we start out 2026 and close out a transformative 2025, I wanted to share a comprehensive look back at what we’ve built for the Uniswap DAO over the last year, and outline our strategic focus for Q1 2026 and beyond.\n\n2025 Year in Review: A Year of Legal Innovation and Protocol Evolution\n\n2025 was a year of strengthening governance infrastructure and lowering barriers to entry. The DAO executed major on-chain proposals with high consensus, often exceeding 95% approval. Tally was proud to provide the default interface and infrastructure that powered these critical decisions, ensuring transparency and accessibility for every delegate.\n\nHere are the key highlights from our work and the DAO’s achievements this year:\n\n1. Supporting DUNI education and accessibility to information\n\nIn August, the DAO made history by approving the “DUNI” structure (Wyoming Decentralized Unincorporated Nonprofit Association) with 99.99% support. This paved the way for limited liability protections and better regulatory compliance.\n\nOur primary focus in Q4’2025 was the refinement of the DUNI page, which now serves as a dedicated education and transparency hub. It answers critical questions: what exactly is DUNI, what are the benefits of this structure, and what does membership mean for a token holder? It also houses DUNI’s financial reports and corporate documents, ensuring that DUNI’s legal and operational documentation are accessible to all members in a compliant, easy-to-read format.\n\n2. Seatbelt Integration & Security\n\nA major shipping highlight for Tally in 2025 was the full integration of Seatbelt. Delegates can now view human-readable security reports, state differences, and simulation results directly on the proposal page before casting a vote. This has significantly streamlined the technical diligence process, a necessity as the DAO managed complex upgrades this year.\n\n3. Infrastructure for UniChain\n\nTally supported UniChain at launch, ensuring DAOs deployed on the network could be managed immediately.\n\nLooking Ahead: 2026 Strategy\n\nFor 2026, our roadmap is defined by 2 major pillars: maximizing the potential of Uniswap’s new Continuous Clearing Auction (CCA) protocol, and supporting UNIfication.\n\n1. Advocating for Continuous Clearing Auctions (CCA)\n\nSupporting CCA is a top priority for Tally in 2026. As a premier token sale platform, Tally is positioned to become the primary distribution engine for new protocols entering the ecosystem.\n\nWe are actively working with our deep pipeline of pre-token projects to advocate for CCA as the superior token sale mechanism. Our strategy is twofold:\n\nLaunch via CCA: Guide projects to launch their tokens using the fair, efficient price discovery of Continuous Clearing Auctions.\n\nSeed V4 Liquidity: Ensure that the liquidity generated from these sales is directly used to seed Uniswap v4 pools, creating immediate depth and utility for tokens launched through Tally.\n\nTo support this adoption, we are building key open-source resources for builders:\n\nCCA Indexer: An open-sourced indexer to help projects track and display auction data.\n\nCCA Simulator: A tool for projects to simulate how their respective sales would look under different parameters.\n\nWe will share links to both resources once they are ready to be deployed!\n\nUNIfication Support\n\nWe are exploring new ways to operationalize the UNIfication mandate with stakeholders like the Uniswap Foundation and the UAC.\n\nVisualizing the Burn: We are designing interfaces to visualize the UNI burn, making protocol revenue and token economics more tangible for the community. Here are some initial designs , and we will continue to work with the Uniswap Foundation and the UAC to iterate and deploy these in time.\n\nScreenshot 2026-01-12 at 3.38.40 PM1276×1012 78.6 KB\n\nScreenshot 2026-01-12 at 3.39.06 PM1288×1088 88.1 KB\n\nOptimistic Governance: We are researching how optimistic governance models can improve efficiency for adjusting fee parameters across all Uniswap v3 and v4 pools. This model will allow the DAO to remain agile in a competitive market without overwhelming the governance queue.\n\nConclusion\n\nUniswap continues to be a strategic partner that Tally is proud to build alongside. From pioneering the DUNI legal structure to launching V4, 2025 was a year of massive progress. We remain committed to shipping infrastructure that empowers the DAO and are incredibly excited to work together on maximizing Uniswap’s distribution in the year ahead.\n\n2 Likes\n\ndennisonb\n\nMarch 23, 2026, 2:57pm\n\n14\n\nHello folks,\n\nAs you may have heard Tally is shutting down. I wanted to quickly however inform the community that we have a continuation plan in place and we will be still be completing our enterprise agreement with Uniswap. We have spoken with the DUNI and DAO representatives and we will be sharing more in this week on the plan forward.\n\nThere will not be any interruption of service for the Uniswap community!\n\nDennison\n\n2 Likes\n\ndennisonb\n\nApril 3, 2026, 2:36pm\n\n15\n\nTally Q1 2026 Update\n\nHello Uniswap Community,\n\nWe wanted to share a brief update on our work this quarter.\n\nThis quarter, a major area of focus for Tally was supporting Continuous Clearing Auctions (CCA) and building open-source infrastructure to help teams adopt them more easily across the Uniswap ecosystem.\n\nWe have open sourced a CCA auction indexer built on Ponder that can be used to index CCA auctions across deployments. The system is designed to make it easy to add support for new networks and monitor the factory contracts of CCA launchers. The architecture is also extensible, with a path toward automatically discovering launcher contracts based on contract shape. Our goal here is to make it easier for teams building around CCA to access reliable auction data with minimal custom infrastructure.\n\nWe have also open sourced an example CCA frontend that teams can use as a high-quality starting point for auction interfaces. The intention is to provide something that is not just functional, but polished, high-fidelity, and ready to accelerate adoption for teams that want to launch with CCA.\n\nIn addition, we built and open sourced an unaudited contracts package for orchestration around permissionless auction launches. This includes infrastructure for workflows such as routing raised funds into Uniswap liquidity and streaming proceeds via Sablier to users and teams. Together, these tools are meant to give builders a stronger base for launching auctions with better operational structure and improved safety properties.\n\nOverall, this was a significant buildout for us, and we are excited to make these resources available to the broader Uniswap ecosystem.\n\nThis quarter we were a major supporter to the Uniswap CCA narrative, as we were building a protocol on top of it. We completed one successfull launch: IdOS which raised about $400,000 using our infrastructure and Uniswap CCA on Arbtirum.\n\nOn the application side, we continued to support Uniswap throughout the quarter with stable performance. We did not experience any notable outages or service disruptions, and everything operated smoothly.\n\nAt a higher level, we also want to share that Tally is currently undergoing a major restructuring and will be winding down as a company. That said, we have put a full continuity plan in place to complete our enterprise agreement with Uniswap without interruption.\n\nAs part of that plan, ScopeLift will take over ongoing support responsibilities for the remainder of the term. ScopeLift is a long-time Uniswap collaborator and a natural fit for this work given their deep experience supporting the Uniswap ecosystem. We have been working closely with the Uniswap Foundation governance team on this transition, and the plan is aligned so that service continues uninterrupted and everything works as expected through the rest of the year.\n\nWe’re grateful for the opportunity to support Uniswap, proud of what we shipped this quarter, and committed to ensuring a smooth transition.\n\nGithub Repo:\n\nhttps://github.com/withtally/Uniswap-CCA-Token-Launcher-Boilerplate\n\n1 Like\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[RFC] - Supporting Tally’s Continued Development and Enhancements for Uniswap DAO Governance\n\nRequests for Comment\n\n44\n\n1718\n\nDecember 17, 2024\n\nUniswap Council (UC): Season 4 Report\n\nGovernance-Meta\n\n0\n\n345\n\nMarch 25, 2026\n\nGovernance Weekly Recap\n\nGovernance-Meta\n\n21\n\n6566\n\nMay 26, 2023\n\nIgnas Delegate Platform\n\nDelegation Pitch\n\n41\n\n1284\n\nMay 25, 2026\n\nUniswap Governance Community Calls\n\nGovernance-Meta\n\n44\n\n2906\n\nMarch 9, 2026","tokens":7232,"crawled_at":1791194882602}
+{"id":10450,"url":"https://docs.ethena.fi/backing-assets/institutional-lending","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Institutional Lending | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nThe protocol also extends overcollateralised loans of stable assets to institutional counterparties through direct lending agreements and triparty collateralised arrangements.\nEthena already lends stablecoins from the backing of USDe into DeFi markets such as Aave and Morpho. This represents a natural extension of that existing activity - overcollateralised lending with only high-quality, immediately liquid collateral (BTC/ETH) and facing institutional counterparties that meet strict eligibility criteria.\nThe CeFi lending market has undergone a structural reset since the credit crisis of 2022–23, where failures of undercollateralised lenders like Genesis, Celsius, and BlockFi eroded trust across the industry. Since then, the market has recovered on a fundamentally different footing: overcollateralised, transparent, and with rigorous counterparty standards.\nCrypto-collateralised lending reached an all-time high in Q4 2025, with the composition of that leverage structurally healthier than during the previous cycle. Overcollateralised credit and transparent reporting have become the norm.\nEthena’s direct lending activity will sit firmly within this reformed landscape - facing only institutional counterparties, overcollateralised with high-quality liquid collateral, and subject to the independent oversight of the Risk Committee.\nUnder these arrangements, an institutional borrower receives a loan of stable assets and posts collateral worth more than the value borrowed. The collateral is held under arrangements designed to protect the protocol's claim - including the use of qualified custodians and triparty structures in which an independent agent holds and administers the collateral. Ethena is establishing lending relationships with institutional-grade counterparties subject to the relevant agreements and Risk Committee approval.\nInstitutional lending captures borrowing demand from a set of counterparties whose activity is largely independent of crypto-native funding cycles, further diversifying the protocol's revenue base. Counterparty eligibility, collateral requirements, overcollateralisation ratios, and aggregate exposure limits are set subject to governance and Risk Committee review.\nLink to Maple & Anchorage Digital analysis\n\nLast updated 3 months ago\nWas this helpful?","tokens":601,"crawled_at":1791194883528}
+{"id":10451,"url":"https://a16zcrypto.com/posts/article/preserving-user-control-ai-agents","domain":"a16zcrypto.com","chapter":"research","title":"Agency by design: Preserving user control in a post-interface world - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nAgency by design: Preserving user control in a post-interface world\nChristian Crowley\n12.09.25\n\nTABLE OF CONTENTS\nWhat it means for founders What it means for founders\nDefining user agency\nAgent-permissioning frameworks\nIntent-centric infrastructure\nAuthenticated delegation standards\nVerifiable execution layers\nZero-knowledge agent frameworks\nMulti-agent coordination systems\nThe risk of fragmentation\nTags\nAI & crypto\nAI agents / agentic AI\ncompany building\nTradFi\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nFor decades, new layers of abstraction have defined how users interact with technology. Programming languages abstracted away machine code. The command line gave way to the graphical user interface, then to the mobile app and the API. Each shift abstracted more complexity away from the user — but left the human firmly in the loop.\n\nAgents represent a different level of abstraction: They don’t just abstract how tasks are done, they abstract who does them. In an agentic future, users will specify outcomes, not actions, and systems will determine how to achieve them. In crypto and fintech, agents can handle tasks like rebalancing portfolios autonomously, automating multi-step wallet transactions, and routing API calls across protocols — all triggered by a single natural language instruction. It’s the first major leap where the interface between human intent and machine execution becomes probabilistic rather than deterministic.\n\nIn other words, outcomes will start to depend on the agent’s interpretation of user intent, not a predefined sequence of commands. At the core, what changes is the user’s role: The user is no longer an operator, they’re an orchestrator. They set initial parameters, then step back as the system runs itself. The user’s role becomes supervisory, not interactive; unless they intervene, the default state is “on.” Agents take action on their behalf, often without additional prompts or approvals.\n\nWhen I was previously building a privacy-first AI company, I started thinking deeply about this shift — and now, in my go-to-market team role, I’m seeing founders across the ecosystem start to wrestle with the same questions, especially as agents become more prevalent in crypto systems. Crypto has always been about minimizing blind trust. Agentic systems don’t break that principle — they just raise the bar for how seriously we design for it.\n\nThis piece surveys what’s being built — a snapshot of today’s infrastructure. It also addresses why user control is so important to preserve at this layer of the stack, and the role crypto can play. I’ll also address how to design with intention at the agent layer, using emerging patterns to maintain agency, transparency, and trust. Better understanding how these approaches are converging is the first step in anticipating how they’ll reshape markets, user behavior, and business models — or even how they’ll impact your product.\n\nWhat it means for founders\n\nFor founders, product teams, and protocol designers, the rise of agentic systems is an opportunity to reimagine what user sovereignty looks like in a post-interface world. Sovereignty isn’t a UI feature — it’s a systems question. As execution shifts from user clicks to autonomous agent actions, design decisions at the agent layer will determine whether users stay in control or simply fade into the background. That means asking things like:\n\nAre agent defaults safe, reversible, and user-friendly?\n\nCan users verify what’s been done on their behalf?\n\nAre permissions composable, revocable, and enforced at the smart contract level?\n\nCan users simulate outcomes before approving?\n\nAre delegation and execution models interoperable across agents, protocols, and wallets?\n\nDo they incorporate shared standards or are they locked into custom, siloed formats?\n\nWe’ll dig into the context behind these questions below, but in short, they all point to the same question: How do we preserve trust and control when users no longer sit at the center of execution?\n\nDefining user agency\n\nUser agency means being able to set boundaries and verify what’s done on your behalf — even if you’re not the one clicking “sign.” It’s the functional expression of user sovereignty in a world where agents, not users, will increasingly drive execution.\n\nCrypto has the tools to preserve user agency in the shift to agents, but only if we rethink delegation, execution, and privacy at the systems level.\n\nTo level-set, today’s “onchain agents” are largely offchain programs that connect to blockchains via wallets, smart contracts, or account abstraction layers. They use large language models (e.g., GPT 4 or Claude) to plan and make decisions, then interact with blockchain infrastructure to execute them.\n\nThis offchain synthesis–onchain execution model enables powerful automation, but introduces new risks to user visibility and control. Over time, agents may evolve to operate more natively onchain, embedding more of that synthesis directly into decentralized systems. As this shift unfolds, the risks we face today will only deepen, and user agency will grow increasingly blurry.\n\nTwo pillars of crypto’s original promise are self-custody and transparency. But both rest on the assumption that the user is the one actively clicking “sign.” In an agent-driven paradigm, that model can start to break down. Agents can act before the user is even aware, and a single signature might authorize a series of downstream actions — some of which the user never explicitly reviewed.\n\nFor example, a wallet signature intended to approve one action might be reused by a delegated agent to execute others under broad permissions. A DAO governance delegate could cast votes based on a misinterpreted definition of “sustainability” embedded in its training dataset. Or you might delegate an agent to manage staking rewards — only to find your funds rerouted to an obscure yield vault you’ve never heard of. You didn’t sign that transaction — but you technically authorized it.\n\nThese aren’t edge cases. They’re realistic outcomes given how today’s agent systems are designed. A recent real-world example illustrates this risk: In March 2025, attackers who gained access to its control dashboard commandeered the AI trading bot AiXBT. The breach allowed them to queue deceptive commands that triggered the agent to transfer 55 ETH to an attacker’s address. The agent’s logic remained intact, but the compromise of its interface bypassed user intent entirely.\n\nAs users delegate more to agents, new risks emerge:\n\nAmbiguous inputs: Vague prompts or poorly scoped permissions can cause agents to operate on flawed assumptions.\n\nSilent failures: Agents can fail without feedback loops, leaving users unaware of what went wrong. Or if anything went wrong at all.\n\nCascading effects: A single approval might trigger a multi-step workflow the user didn’t fully intend or anticipate.\n\nIn these situations, agency becomes something users think they have when they don’t.\n\nAnd in some cases, the erosion of agency starts even earlier. Agents may come prepackaged with opaque default presets — permissions, connections, or logic the user never explicitly configured. When that happens, agency can begin to erode not just at the point of execution but at the point of distribution.\n\nReclaiming user agency\n\nIf interfaces disappear, preserving user control will require new approaches that evolve alongside crypto’s core values.\n\nWe’re still early, but across the ecosystem, teams are exploring new ways to delegate safely, maintain transparency, and protect data sovereignty, even as execution becomes more autonomous. Emerging patterns include:\n\nAgent permissioning frameworks\n\nIntent-based coordination\n\nPrivacy-preserving execution\n\nAuthenticated delegation standards\n\nZero-knowledge agent frameworks\n\nTogether, they offer a glimpse of how control and composability might coexist in an agentic future.\n\nThis list isn’t meant to be exhaustive — agent-layer technologies are evolving quickly, and new models continue to emerge. Instead, it offers a curated snapshot of patterns that show early promise in preserving user agency. Some of the systems and standards that follow were introduced a few years ago, while most are more recent — the goal is simply to illustrate the body of work this next wave is building on.\n\nAgent-permissioning frameworks\n\nOne of the clearest ways to preserve sovereignty is through scoped delegation. This entails giving users fine-grained control over what agents can do, under what conditions, and with which assets.\n\nSeveral teams are working on permissioning frameworks that embed constraint and accountability directly into the agent’s execution layer:\n\nMetaMask’s Delegation Toolkit (launched mid-2024; developer use now) provides infrastructure for account abstraction-based smart accounts, enabling developers to build wallets with scoped, recoverable permissions; gasless transactions; and zero-prompt user flows. In 2025, MetaMask expanded the toolkit with multichain smart account support and policy-based permissions, deepening its role as a standard for agent delegation\n\nCoinbase’s AgentKit combines Multi-Party Computation (MPC)-based key control, session-limited delegation, and account abstraction to support secure onchain agent actions. This embeds sovereignty directly into agent execution. Its successor, x402, launched in October 2025, extends these ideas into a full developer platform for agentic applications. (More on this in the closing section.)\n\nEIP-7702 extends these ideas at Ethereum’s base layer. Part of the Pectra upgrade, EIP-7702 lets externally owned accounts (EOAs) temporarily behave like smart contract wallets. In other words, an EOA — a standard Ethereum account controlled by a private key — can temporarily act more like a programmable smart contract. This unlocks native support for session keys and spending limits, strengthening agent permissioning without relying on custom wallet logic.\n\nBiconomy’s Delegated Authorization Network (DAN) introduces a programmable delegation layer for AI agents. Built on EigenLayer’s Actively Validated Services (AVS), it manages keys and enforces user-defined constraints through shared signing, where multiple parties must approve each action. (More on how AVS works in the section on verifiable execution.)\n\nLit Protocol’s Vincent Tool SDK (v3 released Dec 2023, v4 released Mar 2024) lets developers define the actions agents can take and policies that govern them, including spending caps, conditional logic, and multi-party consent triggers.\n\nAutonomys Network (formerly Autonomy Network) lets users define programmable “rails” for agent behavior, including gas caps, asset types, and destination allowlists and ensuring that actions stay within user-set boundaries.\n\nAvocado by Instadapp enables strategy delegation within user-defined scopes, such as “rebalance weekly” or “only interact with whitelisted protocols,” using smart contract wallets with modular authentication layers.\n\nFireblocks, Dynamic.xyz, and others apply MPC to key management as well. They split signing authority across services to constrain agent actions. By preventing any single agent or service from holding full custody of user keys, MPC enforces policies directly at the signing layer.\n\nCollectively, these frameworks show how giving users the ability to set clear boundaries up front helps protect their agency by design.\n\nIntent-centric infrastructure\n\nAs UX moves further away from direct user interaction, some teams are rethinking the transaction model entirely. One emerging approach is to shift from instruction-based systems (where the user approves every step) to intent-based architectures, where users (or agents) specify outcomes and the system determines how best to achieve them.\n\nNEAR’s Intents framework lets users define a desired outcome (e.g., “bridge tokens and stake”) without specifying how to do it. A decentralized network of solvers competes to fulfill that request efficiently. These solvers handle routing, execution, and optimization behind the scenes. This is live and gaining traction. According to DeFiLama, NEAR Intents have handled over $7 billion in cumulative DEX volume since its launch in Q4 2024.\n\nAnoma (Mainnet rollout 2025, early deployment phase) introduced a fully intent-based architecture. It uses a gossip protocol for decentralized intent discovery, where users broadcast intents into a shared coordination layer. Counterparties match and fulfill these intents through encrypted execution.\n\nParticle Network V2 introduced an “Intent Fusion Protocol” built into a zkWaaS (zero-knowledge wallet-as-a-service) stack. Users express goals via natural language or interface triggers, which solvers interpret and fulfill across chains.\n\nIn intent-centric systems, users define what they want, not how to get it. This abstraction empowers agents to determine the best path forward, often without a visible interface. While this can be powerful, it may also involve clearer user delegation, since the agent (or solver) becomes responsible for interpreting intent and executing on the user’s behalf.\n\nAuthenticated delegation standards\n\nAs agents gain more autonomy, it becomes unclear who is authorizing what — and when. Authenticated delegation frameworks make this possible by allowing users to grant scoped, verifiable permissions to agents, with auditability built in by design.\n\nWalletConnect Smart Sessions let users authorize agents to perform scoped actions — like executing trades or claiming rewards — within a defined session window. Users set parameters once, and agents act autonomously within that timeframe, reducing repetitive confirmations without losing user-defined limits.\n\nMIT’s Authenticated Delegation Framework extends OAuth 2.0 with agent-specific credentials. It creates cryptographically verifiable chains of authority that link a human user, a software agent, and the permissions granted, enabling granular, revocable, and auditable delegation across platforms.\n\nMIT’s Non-Authoritative Non-Repudiable Delegation Architecture (NANDA) explores how to create cryptographic chains of delegated authority without granting full control to any single agent. By enabling agents to act with provable, constrained intent, without assuming root privileges, models like NANDA could become a foundation for scalable, verifiable delegation in agent-driven systems.\n\nModel Context Protocol (MCP) proposes embedding agent metadata (e.g., intent, identity, delegation scope) directly into transaction payloads. Though still evolving, MCP offers a potential standard for preserving context and attribution across execution layers.\n\nThese approaches don’t just improve UX They embed user-centric features like consent, attribution, and revocation directly into open systems.\n\nVerifiable execution layers\n\nAs agents begin to act autonomously, visibility into what they’ve done — and whether they did it correctly — becomes more important. Without an auditable trail, user intent could be misrepresented, with agents driving unintended outcomes with opaque accountability.\n\nVerifiable execution systems introduce cryptographic, and incentive-aligned mechanisms, for validating agent behavior, even when execution happens off-chain.\n\nEigenCloud’s Actively Validated Services (AVS) provide a decentralized trust layer for verifying agent actions. Staked validators monitor and attest to the correctness of offchain execution, and can be slashed for dishonesty or inaction. This creates a cryptoeconomic accountability layer that extends beyond the base protocol.\n\nAVA Protocol (launched July 2024), built as an AVS on EigenLayer, focuses on verifiable AI agents. It enables models to log task execution on-chain, with slashing tied to execution quality and correctness.\n\nZero-knowledge (ZK) proofs can offer a powerful tool to verify that a computation was performed correctly without revealing its inputs or intermediate state. Aleo, zkSync, and others are exploring this technique to make offchain agent behavior auditable without sacrificing input privacy.\n\nThese approaches help turn agent behavior from a black box into a more transparent, auditable record. Giving users a clear view of what’s been done on their behalf is a helpful step toward preserving their agency.\n\nZero-knowledge agent frameworks\n\nWhile ZK proofs can help verify agent behavior, some companies go further, building full agent frameworks that operate natively in zero-knowledge environments. When agents handle sensitive inputs or must coordinate confidentially, transparency alone isn’t enough. Privacy needs to be designed in from the start. ZK technologies allow agents to prove what they’ve done — without revealing why or how.\n\nAleo’s ZK Agent Stack combines a custom zero-knowledge virtual machine with a privacy-preserving programming language (Leo), allowing agents to perform computations privately while still allowing for public verifiability.\n\nSeismic’s Encrypted Blockchain Architecture leverages secure hardware and encrypted state transitions to enable confidential agent workflows, with metadata revealed only to authorized parties.\n\nZK-based wallet integrations, including those developed by Particle Network and Lit Protocol, let agents interact with onchain applications without exposing session keys, user identities, or granular wallet histories.\n\nPrivacy must also protects users from passive surveillance that can occur from the agents acting on their behalf. These ZK-native systems let users retain sovereignty over sensitive inputs, without giving up automation or functionality.\n\nMulti-agent coordination systems\n\nAgents won’t operate in isolation. As agentic systems proliferate, coordination between them becomes inevitable and more sophisticated. We’ll need protocols that support agent-to-agent trust, governance, and composability.\n\nMulti-agent coordination systems offer ways for agents to discover, communicate with, and respond to one another.\n\nAt the protocol layer, Google’s Agent2Agent (A2A) Protocol defines a standardized communication layer. It includes primitives for agent discovery, task lifecycle management, streaming updates, and secure messaging. This enables reliable, interoperable agent-to-agent collaboration while preserving context, intent, and auditability across systems.\n\nRecent proposals like ERC-8004 (Trustless Agents) extend A2A with crypto-native trust models. These include things like reputation scores, stake-secured validation, and trusted execution environment (TEE) attestations. With these kinds of approaches, crypto can complement existing coordination standards with tools that preserve accountability and verifiability across agent ecosystems.\n\nAt the marketplace and infrastructure layer, Fetch.AI’s Agentverse is building a decentralized agent marketplace where DAOs can deploy agents to manage voting, liquidity, metagovernance, and resource allocation. Similarly, Bittensor supports a decentralized AI network where models (as agents) train across specialized subnets, coordinate through tokenized feedback loops, and compete for performance-based rewards.\n\nIn applied coordination systems, ElizaOS shows how investment DAOs can delegate capital management to autonomous agents. Their agents propose trades, rebalance portfolios, and execute on strategies within boundaries set by tokenholder governance. SingularityDAO offers a hybrid model, blending human and agent decision-making in DeFi portfolio management. AI agents handle execution around tactical portfolio management while human governance sets strategic intent.\n\nThese systems point to a future where agent-to-agent interaction becomes the norm — and where shared approaches ensure that agent-to-agent coordination doesn’t erode user intent, control, or autonomy.\n\nThe risk of fragmentation\n\nWhile each of these approaches shows promise, fragmentation will grow. That fragmentation will also span the entire agent stack, not just agent-to-agent coordination protocols. Teams are therefore designing custom formats for intents, delegation, and permissioning. These components may be powerful in isolation, but without shared design frameworks, agent systems risk becoming siloed — limiting interoperability and undermining user sovereignty across platforms.\n\nFor instance, an agent built on MetaMask’s Delegation Toolkit might not understand an intent broadcast by another agent built on a bespoke MPC wallet. Examples like this can create a patchwork of walled gardens, where agents speak only their own languages and dialects. This is precisely what open blockchain networks were designed to avoid.\n\nWork is already underway to address this, at least on Ethereum. EIP-8001 (Secure Intents) proposes a cryptographic standard for intent schemas. If widely adopted, it could give agents a shared language for delegation and coordination, preserving interoperability and user control as agent ecosystems expand.\n\n***\n\nThe shift is unfolding across real systems. Platforms like Coinbase x402 point toward what this future might look like: scoped, verifiable, and composable autonomy built directly into production systems. x402 gives agent policy-signing authority, MPC-secured key management, and verifiable onchain execution. Through Coinbase Bazaar, agents can autonomously discover and pay for services while every transaction remains visible and revocable by the user. These components translate abstract principles into live developer primitives. (For a live view of agent and service activity see x402scan.)\n\nRecent launches in crypto-adjacent ecosystems show how fast agent-driven execution is evolving: In AI-native ecosystems, OpenAI’s Operator Agent can already browse websites, fill out forms, and make purchases via a virtual browser — autonomously and with minimal user prompts. In payments, Visa’s Intelligent Commerce and Mastercard’s Agent Pay are issuing tokenized, agent-bound credentials for AI systems. Similar to some of the approaches above, these systems include scoped spending limits, programmable authentication flows, and audit trails.\n\nThese aren’t crypto-native systems, but they show that agent-first execution is already underway.\n\n***\n\nFor those building in crypto, there’s a real opportunity to lead the charge. Unlike legacy technologies, crypto has the primitives to embed user intent, delegation, and verification directly into architecture. Paired with shared frameworks for interoperability, these systems can support agent ecosystems that are composable, accountable to users, and user-controlled by default.\n\nWe’re early. But the choices builders make now will define how control, privacy, and consent are preserved in the agentic era. Crypto can make sure that agency stays where it belongs: with the user.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nYou should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investment-list/.\n\nThe content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures/ for additional important information.","tokens":6495,"crawled_at":1791194893237}
+{"id":10452,"url":"https://docs.sui.io/operators","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Node Operators | Sui Documentation","text":"Sui has several node types, each with a different role:\n\nFull nodeFull nodeResponsible for validating blockchain activity.: Stores the full chain state and serves read requests.\n\nValidatorValidatorResponsible for executing tasks like staking, gas price references, and tallying rules.: Participates in consensusConsensusThe process by which the majority of nodes agree on the current state of the network and produces certified transactionTransactionA number of commands that execute on inputs to define the result of the transaction. effects. Validators must meet staking and hardware requirements.\n\nBridge node: Supports cross-chain asset transfers between Sui and other networks.\n\nWhat does a node operator do?​\n\nRunning Sui infrastructure involves more than launching a binary. Operators are responsible for:\n\nConfiguring and starting nodes on supported hardware\n\nKeeping software up to date across network upgrades\n\nManaging chain data, snapshots, and archival storage\n\nMonitoring node health and setting up observability tooling\n\nHandling key management and operational security\n\nFrequently asked questions​\n\nWhat is the difference between a full node and a validator?​\n\nA full node stores chain state, answers queries, and submits transactions to validators. A validator participates in consensus to finalize transactions. Validators earn staking rewards and must meet additional operational and hardware requirements.\n\nHow do I keep my node in sync after a restart?​\n\nSui supports snapshots and archival data to help nodes catch up after downtime. The data management guides explain how to configure snapshot sources and restore from them.\n\nWhat monitoring should I set up for my node?​\n\nThe observability guide covers metrics endpoints, log configuration, and recommended alerting for production nodes.\n\nFind guides for running and managing Sui network infrastructure, including full nodes, validators, bridge nodes, data management, and exchange integration.\n\nNode Operators\nGuides for running and managing Sui network infrastructure, including full nodes, validators, bridge nodes, data management, and exchange integration.\n→\nGenesis\nGenesis refers to the initial state of the Sui blockchain at launch.\n→\nObservability\nSet up and manage logging, tracing, metrics, and observability for Sui validators and full nodes using structured logging and Prometheus.\n→\nDatabase Snapshots\nDatabase snapshots of the Sui network enable full node operators a way to bootstrap a full node without having to execute all the transactions that occurred after genesis.\n→\nFull Nodes\nIn this section\nConfiguration\nMonitoring\nUpdating\n\n→\nData Indexing and Archives\nIn this section\nData Management\nAvailable Data Stores\nGraphQL and General-Purpose Indexer\nRunning a Remote Store\nRunning the Archival Store and Service\nArchive Data\n\n→\nValidators\nIn this section\nDeployment and Configuration\nManagement\nTools\nRewards\nAlert Reference\n\n→\nExchange Integration\nGuidance for integrating SUI into a cryptocurrency exchange. Covers infrastructure, current APIs (gRPC and GraphQL), balance tracking, transactions, transfers, and staking.\n→\nBridge Node Configuration\nCorrect configuration of your node ensures optimal performance and valid metrics data.\n→\n\nWhat does a node operator do?\nFrequently asked questions\n\nWas this page helpful?","tokens":829,"crawled_at":1791194895602}
+{"id":10453,"url":"https://docs.sui.io/operators/genesis","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Genesis | Sui Documentation","text":"Genesis is the initial state of the Sui blockchain. To launch a network, the initial committee of validators collaborate by providing their validatorValidatorResponsible for executing tasks like staking, gas price references, and tallying rules. information (public keys, network addressesAddressA unique, anonymous identity on a blockchain network., and so on) to a shared workspace. After all of the initial validators have contributed their information, Sui generates the initial, unsigned genesis checkpointCheckpointCreated after transaction execution to provide a certified record of chain history. (checkpoint with sequence number 0) and each validator provides their signature. Sui aggregates these signatures to form a certificateCertificateThe mechanism proving a transaction was approved or certified. on the genesis checkpoint. Sui bundles this checkpoint, as well as the initial objects, together into a single genesis.blob file that is used to initialize the state when running the sui-node binary for both validators and full nodes.\n\nDownload genesis.blob​\n\nEach Sui network (MainnetMainnetProduction network for live transactions and real-value assets., TestnetTestnetStaging network for testing changes before production deployment., DevnetDevnetFor developing and testing new features.) has its own genesis.blob file. Download the file for your target network:\n\n# Replace <network> with mainnet, testnet, or devnet\n$ curl -fLO https://github.com/MystenLabs/sui-genesis/raw/main/<network>/genesis.blob\n\nPlace the file where your fullnode.yaml configuration points. The default template uses genesis-file-location: \"/opt/sui/config/genesis.blob\". Use an absolute path to avoid ambiguity. Relative paths resolve from the process working directory (the directory where you run sui-node), not from the directory containing fullnode.yaml.\n\nAll genesis files are hosted in the sui-genesis repository. See Sui Full Node Configuration for the complete setup steps.\n\nNetwork identity​\n\nThe genesis.blob file determines the network identity. The node derives a chain identifier from the genesis checkpoint digest and uses it to verify that peers, snapshots, and archive data belong to the same network. If you use the wrong genesis.blob for your target network, the node or related tooling (such as snapshot restore) fails with a chain identifier mismatch error. For example, sui-tool reports:\n\nGenesis file is for chain <X>, but formal snapshot download is configured for --network <Y>.\n\nA normal sui-node startup with a mismatched genesis file causes the node to reject peer connections and checkpoint data from the actual network. If the node's database was already initialized with the wrong genesis, the node asserts that the stored and configured checkpoint-0 digests match and refuses to start.\n\nTo fix a mismatch, download the correct genesis.blob for your target network using the command above. If the database was initialized with the wrong genesis, you must also delete the existing database and restore from a snapshot for the correct network before restarting.\n\nFile format​\n\nThe genesis.blob file is a BCS-serialized binary containing the genesis checkpoint, its certificate (aggregated validator signatures), and the initial onchain objects (system packagesPackageSmart contracts on Sui., the Sui framework, and validator staking objects). It is not human-readable. The node deserializes it at startup to initialize its state.\nRelated topics\n\nSui Full Node Configuration\nOperate a Sui full node to validate blockchain activities, like transactions, checkpoints, and epoch changes.\nDatabase Snapshots\nDatabase snapshots of the Sui network enable full node operators a way to bootstrap a full node without having to execute all the transactions that occurred after genesis.\n\nDownload genesis.blob\nNetwork identity\nFile format\n\nWas this page helpful?","tokens":968,"crawled_at":1791194916198}
+{"id":10454,"url":"https://www.getfoundry.sh/cast/tokenized-vaults","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Tokenized vaults – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nTokenized vaults\n\nCast provides typed commands for the complete synchronous base interface defined by ERC-4626. Use cast erc4626 or its cast vault alias to inspect exchange rates and limits, preview operations, and deposit, mint, withdraw, or redeem without writing ABI signatures by hand.\n\nThe commands accept integer amounts in the underlying asset's or vault share's smallest unit. Use cast erc20-token decimals and cast parse-units when you need to convert human-readable amounts.\n\nCommand surface\n\nEach state-changing operation has a limit query and a preview query:\n\nOperationLimitPreviewTransaction\nDeposit an asset amount for a receiver\nmax-deposit\npreview-deposit\ndeposit\n\nMint a share amount for a receiver\nmax-mint\npreview-mint\nmint\n\nWithdraw an asset amount owned by an account\nmax-withdraw\npreview-withdraw\nwithdraw\n\nRedeem a share amount owned by an account\nmax-redeem\npreview-redeem\nredeem\n\nYou can also query the asset address, total-assets, or use convert-to-shares and convert-to-assets for caller-independent conversions.\n\nFor a combined view, info summarizes the vault and its exchange rate, position summarizes one owner's shares and exit limits, and check probes whether the synchronous read interface behaves as expected.\n\nThe vault contract is also the ERC-20 share token. Use cast erc20-token for inherited operations such as balance, allowance, approve, and transfer.\n\nInspect a vault\n\nSet the vault and RPC endpoint, then read its underlying asset and accounting state:\n\n$ export VAULT=0x...\n$ export RPC_URL=https://...\n$ cast erc4626 info $VAULT --rpc-url $RPC_URL\n$ cast erc4626 info $VAULT --human --rpc-url $RPC_URL\n$ cast erc4626 position $VAULT $OWNER --human --rpc-url $RPC_URL\n\ninfo reports vault and asset metadata, total assets and shares, and normalized conversions in both directions. position reports an owner's share balance, its asset equivalent, and the owner's current max-withdraw and max-redeem values. Text output uses exact integer amounts by default; pass --human to format them using the on-chain token decimals. JSON output always preserves each integer as raw and includes formatted when decimals are available.\n\nconvert-to-shares and convert-to-assets provide idealized, caller-independent conversions. Use the corresponding preview command when you are preparing a specific operation because previews account for the vault's operation-specific fees and rounding.\n\nDeposit assets\n\nAn ERC-4626 deposit pulls the underlying ERC-20 asset from the sender. Approve the vault to spend the asset before submitting the deposit:\n\n$ ASSET=$(cast erc4626 asset $VAULT --rpc-url $RPC_URL)\n$ cast erc4626 max-deposit $VAULT $RECEIVER --rpc-url $RPC_URL\n$ cast erc4626 preview-deposit $VAULT $ASSETS --rpc-url $RPC_URL\n$ cast erc20-token approve $ASSET $VAULT $ASSETS --rpc-url $RPC_URL --private-key $PRIVATE_KEY\n$ cast erc4626 deposit $VAULT $ASSETS $RECEIVER --rpc-url $RPC_URL --private-key $PRIVATE_KEY\n\nIf the underlying asset supports ERC-2612, you can also authorize spending with a permit signature. A permit on the vault itself approves its shares, not the underlying deposit asset.\n\nmint follows the same approval flow, but takes the exact number of shares to mint. Use preview-mint to calculate the assets the vault expects to pull.\n\nState-changing vault commands use the same signer, fee, hardware wallet, browser wallet, and Tempo options as cast send. See Sending transactions for those options.\n\nWithdraw assets\n\nChoose withdraw when you know the asset amount to receive, or redeem when you know the share amount to burn:\n\n$ cast erc4626 max-redeem $VAULT $OWNER --rpc-url $RPC_URL\n$ cast erc4626 preview-redeem $VAULT $SHARES --rpc-url $RPC_URL\n$ cast erc4626 redeem $VAULT $SHARES $RECEIVER $OWNER --rpc-url $RPC_URL --private-key $PRIVATE_KEY\n\nThe signing account must be OWNER or have sufficient allowance to spend the owner's vault shares. RECEIVER receives the withdrawn underlying assets.\n\nCompatibility and safety\n\nProbe a vault before relying on the synchronous read interface:\n\n$ cast erc4626 check $VAULT --account $OWNER --rpc-url $RPC_URL\n\ncheck makes only read calls. It verifies contract code, the base accounting, conversion, limit, and preview calls, inherited ERC-20 reads, and the underlying asset contract. It prints the full report and exits nonzero when a required check fails; warnings do not make the command fail. Omit --account to use the zero address for account-dependent probes.\n\nThis is a compatibility probe, not a compliance certificate. It does not invoke state-changing selectors or prove the standard's semantic requirements. Cast reports targeted warnings for compatibility cases it can identify:\n\nA zero max-deposit or max-mint may be a conservative limit rather than proof that the operation is permanently disabled.\n\nA zero max-withdraw or max-redeem for an owner with shares may reflect temporary liquidity, authorization, or integration constraints.\n\nThe ERC-7535 native-asset sentinel requires a payable, value-bearing call; the typed write commands currently encode ERC-20-style calldata only.\n\nPreview calls can revert by design for the corresponding asynchronous flow in ERC-7540. check treats these reverts as expected warnings only when the vault advertises the mandated ERC-165 interface ID for that flow; an unadvertised preview failure remains a failed check.\n\nThe transaction commands invoke the base ERC-4626 methods without minimum-output or maximum-input slippage fields. A preview can become stale before the transaction executes, so use a protocol router or a vault-specific extension such as ERC-5143 when the operation needs on-chain price bounds.\n\nAsynchronous ERC-7540 request and claim flows, ERC-7575 multi-asset vaults, native-value deposits, permit composition, and router-specific methods are outside this synchronous base interface. Use cast call or cast send with the project's ABI for those extensions.\n\nSee the cast erc4626 reference for the complete option list.\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":1521,"crawled_at":1791194920802}
+{"id":10455,"url":"https://docs.ethena.fi/overview/ena","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"ENA | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nENA is the governance token of the Ethena protocol. ENA is used to govern parameters of the protocol, including the composition of USDe backing, the introduction of new backing strategies, the future allocation of protocol revenue, and the membership and remit of the Risk Committee. ENA is available across Ethereum and a number of supported chains through LayerZero, with governance accessible wherever ENA is held.\nsENA\nsENA is the staked form of ENA. Holders deposit ENA into the staking contract and receive sENA, an ERC-20 token representing their position. The contract is implemented as an ERC-4626 wrapper, and unstaking is subject to a cooldown period before ENA can be withdrawn. Staking ENA into sENA signals long-term alignment with the protocol and is a route through which ENA holders participate in governance.\nGovernance\nEthena governance operates through the Ethena governance forum and on-chain voting, with proposals subject to discussion, Risk Committee review where relevant, and a vote of ENA holders. The Risk Committee is a standing body responsible for setting risk parameters across the protocol - including eligibility of backing assets, exposure limits, counterparty limits, and the activation conditions for mechanisms such as the Fee Switch - and its membership is itself subject to governance.\nThe combination of token-holder voting, an active Risk Committee, and implementation of approved parameters allows the protocol to operate a diversified and dynamic backing portfolio while keeping decision-making transparent and subject to ENA holder oversight.\n\nhttps://gov.ethenafoundation.com/\n\nLast updated 2 months ago\nWas this helpful?","tokens":440,"crawled_at":1791194922609}
+{"id":10456,"url":"https://docs.sui.io/operators/full-node","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Full Nodes | Sui Documentation","text":"Full nodes replicate the complete state of the Sui blockchain and serve RPC requests. These guides cover setting up a full nodeFull nodeResponsible for validating blockchain activity., configuring it for your infrastructure, and operational best practices.\n\nConfiguration\nOperate a Sui full node to validate blockchain activities, like transactions, checkpoints, and epoch changes.\n→\nMonitoring\nMonitor Sui node metrics to ensure the health and performance of your node.\n→\nUpdating\nUpdate your Sui full node to the latest version to remain in sync with the network.\n→","tokens":142,"crawled_at":1791194936075}
+{"id":10457,"url":"https://www.getfoundry.sh/anvil/custom-methods","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Custom methods – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nCustom methods\n\nAnvil exposes custom RPC methods beyond the standard Ethereum JSON-RPC API. These methods are useful for testing scenarios that require account impersonation, time manipulation, or mining control. This page covers the most common workflows; for every custom method with parameters and examples, see the complete RPC method reference.\n\nAccount impersonation\n\nImpersonate any account to send transactions without its private key:\n\nImpersonate an account\n$ cast rpc anvil_impersonateAccount $ADDRESS\n\nSend transaction as impersonated account\n$ cast send $CONTRACT \"transfer(address,uint256)\" $TO $AMOUNT --from $ADDRESS --unlocked\n\nStop impersonating\n$ cast rpc anvil_stopImpersonatingAccount $ADDRESS\n\nStart Anvil with auto-impersonation enabled:\n\nEnable auto-impersonation\n$ anvil --auto-impersonate\n\nMining control\n\nFor mining modes, transaction ordering, pool inspection, and deterministic automation patterns, see Mining and transaction pool.\n\nControl when blocks are mined:\n\nDisable automatic mining\n$ anvil --no-mining\n\nMine a single block\n$ cast rpc anvil_mine\n\nMine multiple blocks\n$ cast rpc anvil_mine 10\n\nSet block interval (seconds)\n$ anvil --block-time 12\n\nEnable interval mining via RPC\n$ cast rpc evm_setIntervalMining 12\n\nResume automatic mining\n$ cast rpc evm_setAutomine true\n\nTime manipulation\n\nControl the blockchain's perception of time:\n\nIncrease time by seconds\n$ cast rpc evm_increaseTime 3600\n\nSet next block timestamp\n$ cast rpc evm_setNextBlockTimestamp 1700000000\n\nMine block with new timestamp\n$ cast rpc evm_mine\n\nState snapshots\n\nCreate and restore chain state snapshots during a session:\n\nCreate snapshot\n$ cast rpc evm_snapshot\n\nRevert to snapshot\n$ cast rpc evm_revert $SNAPSHOT_ID\n\nSnapshots return an ID that you use to revert. Reverting removes the snapshot.\n\nBalance and code manipulation\n\nModify account state directly:\n\nSet account balance\n$ cast rpc anvil_setBalance $ADDRESS 0xDE0B6B3A7640000\n\nSet account nonce\n$ cast rpc anvil_setNonce $ADDRESS 0x10\n\nSet contract code\n$ cast rpc anvil_setCode $ADDRESS $BYTECODE\n\nSet storage slot\n$ cast rpc anvil_setStorageAt $ADDRESS $SLOT $VALUE\n\nChain configuration\n\nModify chain parameters at runtime:\n\nSet chain ID\n$ cast rpc anvil_setChainId 31337\n\nSet block gas limit\n$ cast rpc evm_setBlockGasLimit 0x1C9C380\n\nSet next block base fee\n$ cast rpc anvil_setNextBlockBaseFeePerGas 0x5F5E100\n\nTransaction pool\n\nInspect and manage pending transactions:\n\nGet pending transactions\n$ cast rpc txpool_content\n\nDrop a transaction\n$ cast rpc anvil_dropTransaction $TX_HASH\n\nDrop all pending transactions\n$ cast rpc anvil_dropAllTransactions\n\nTracing\n\nEnable execution traces for debugging:\n\nEnable trace printing\n$ anvil --print-traces\n\nEnable step tracing for debug_* methods\n$ anvil --steps-tracing\n\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":722,"crawled_at":1791194940589}
+{"id":10458,"url":"https://docs.sui.io/operators/full-node/updates","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Updating a Full Node | Sui Documentation","text":"Sui release process​\n\nEach Sui network is deployed on a consistent schedule. Extenuating circumstances might delay releases occasionally, but these delays are rare and communicated through official channels.\n\ndevnet: Deployed every week on Mondays.\n\ntestnet: Deployed every week on Tuesdays.\n\nmainnet: Deployed every two weeks on Wednesdays.\n\ninfo\nFor additional details, see each network's release schedule and configuration.\n\nWhenever Sui releases a new version, you must update your full nodeFull nodeResponsible for validating blockchain activity. with the release to ensure compatibility with the network it connects to. For example, if you use Sui TestnetTestnetStaging network for testing changes before production deployment. you should install the version of Sui running on Sui Testnet.\n\nAny release that contains a protocol change needs to be applied before the protocol upgrade takes place (when enough stake within the validatorValidatorResponsible for executing tasks like staking, gas price references, and tallying rules. set upgrades, the new protocol version is enacted in the next epochEpochA period of time defined by the network.).\nIf you do not update your full node, it cannot connect to the network after the protocol upgrade takes place.\n\nCommunication​\n\nReleases are announced on the Sui Discord server and the node-operators Google group.\n\nDiscord channels​\n\ndevnet: #devnet-updates\n\ntestnet: #tn-validator-announcements, #testnet-updates, and #node-announcements channels.\n\nmainnet: #mn-validator-announcements, #mainnet-updates, and #node-announcements channels.\n\nUpdate your full node​\n\nYou can track the latest version of Sui on the Sui Releases page on GitHub.\nThe schedule for each network is available in the Network Release Schedule page.\n\nIt is reasonable to have to shut down your full node to perform an update, whether that be a rolling restart in Kubernetes, or a systemctl stop on a Linux machine to replace the sui-node binary.\n\nSui release process\nCommunicationDiscord channels\n\nUpdate your full node\n\nWas this page helpful?","tokens":517,"crawled_at":1791194956344}
+{"id":10459,"url":"https://www.getfoundry.sh/anvil/forking","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Forking – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nForking\n\nAnvil can fork any EVM-compatible chain, allowing you to test against real-world state without deploying to a live network.\n\nBasic forking\n\n$ anvil --fork-url https://ethereum.reth.rs/rpc\n\nYou can also fork from a specific point in the chain's history:\n\n$ anvil --fork-url https://ethereum.reth.rs/rpc --fork-block-number 18000000\n\n$ anvil --fork-url https://ethereum.reth.rs/rpc --fork-transaction-hash $TX_HASH\n\nSkipping fork identity probes\n\nBy default, Anvil sends anvil_nodeInfo and, if it succeeds, anvil_metadata to detect whether the fork endpoint is another Anvil instance. Some public RPC gateways delay responses to these methods. You can skip both probes with --no-fork-node-info:\n\n$ anvil --fork-url $RPC_URL --no-fork-node-info\n\nThe flag requires --fork-url and treats the endpoint as a regular chain. Standard RPC requests for chain ID, blocks, and gas price still run, subject to your other fork options. Leave the probes enabled when you need Anvil to inherit another Anvil instance's network and hardfork metadata.\n\nSee the anvil reference for all fork options.\n\nChain configuration\n\nWhen forking, Anvil inherits the chain ID from the remote endpoint by default.\n\nOverride chain ID\n$ anvil --fork-url https://ethereum.reth.rs/rpc --chain-id 1337\n\nSpecify hardfork\n$ anvil --fork-url https://ethereum.reth.rs/rpc --hardfork cancun\n\nRate limiting\n\nRPC providers often rate-limit requests. Anvil handles this automatically but you can tune the behavior:\n\nSet compute units per second\n$ anvil --fork-url $RPC_URL --compute-units-per-second 100\n\nDisable rate limiting\n$ anvil --fork-url $RPC_URL --no-rate-limit\n\nSet retry count\n$ anvil --fork-url $RPC_URL --retries 10\n\nCaching\n\nAnvil caches forked state to disk at ~/.foundry/cache/rpc/<chain>/<block>/ to speed up subsequent runs.\n\nDisable storage caching\n$ anvil --fork-url $RPC_URL --no-storage-caching\n\nCustom headers\n\nSome RPC providers require authentication headers:\n\nAdd custom header\n$ anvil --fork-url $RPC_URL --fork-header \"Authorization: Bearer $TOKEN\"\n\nL2 support\n\nAnvil can fork L2 networks directly. The network family is inferred from the forked chain ID, so forking a network like Optimism needs no extra flags:\n\nFork Optimism\n$ anvil --fork-url https://mainnet.optimism.io\n\nEnable Celo features\n$ anvil --fork-url https://forno.celo.org --celo\n\nUse --network to select a network family explicitly. See\nNetwork configuration for selection and inference behavior,\nand the anvil reference for the values supported by\nyour installed binary.\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":656,"crawled_at":1791194957989}
+{"id":10460,"url":"https://www.metaplex.com/docs/smart-contracts/core/plugins/immutableMetadata","domain":"www.metaplex.com","chapter":"docs","title":"ImmutableMetadata Plugin | Metaplex Core","text":"The ImmutableMetadata Plugin permanently locks the name and URI of Assets or Collections. Once added, the metadata cannot be changed by anyone, ensuring permanent provenance.\nWhat You'll Learn\nMake Asset metadata immutable\nMake Collection metadata immutable\nUnderstand inheritance from Collections to Assets\nProtect NFT provenance permanently\n\nSummary\nThe ImmutableMetadata plugin is an Authority Managed plugin that prevents any changes to an Asset or Collection's name and URI. Once added, this protection is permanent.\nAuthority Managed (only update authority can add)\nMakes name and URI permanently unchangeable\nCannot be removed after addition\nCollection plugin affects all Assets in that Collection\nOut of Scope\nMaking other plugin data immutable (use authority None on those plugins), selective field immutability, and temporary locks.\nQuick Start\nJump to: Add to Asset · Add to Collection\nEnsure metadata (name, URI) is finalized\nAdd ImmutableMetadata plugin as update authority\nMetadata is now permanently locked\nWhen to Use ImmutableMetadata\nScenarioUse ImmutableMetadata?\nArt NFTs with permanent artwork\n✅ Yes\n\nGame items with evolving stats\n❌ No (need to update attributes)\n\nPrevent rug-pulls\n✅ Yes\n\nDynamic/evolving NFTs\n❌ No\n\nCertificates/credentials\n✅ Yes\n\nUse ImmutableMetadata for art, collectibles, and certificates where permanence is valued.\n\nDon't use for game items or dynamic NFTs that need updates.\n\nCommon Use Cases\nArt collectibles: Guarantee artwork and metadata will never change\nCertificates: Issue credentials that can't be altered\nProvenance protection: Prevent rug-pulls by locking metadata\nHistorical records: Preserve NFT data permanently\nBrand guarantees: Assure collectors the NFT's identity is fixed\nWorks With\n\nMPL Core Asset\n✅\n\nMPL Core Collection\n✅\n\nArguments\nThe ImmutableMetadata Plugin requires no arguments.\nAdding the immutableMetadata Plugin to an Asset code example\nAdding a Immutability Plugin to an MPL Core Asset\n\nimport {\n\naddPlugin,\n\n} from '@metaplex-foundation/mpl-core'\n\nawait addPlugin(umi, {\n\nasset: asset.publicKey,\n\nplugin: {\n\ntype: 'ImmutableMetadata',\n\n},\n\n}).sendAndConfirm(umi)\n\nAdding the immutableMetadata Plugin to a Collection code example\nAdd immutableMetadata Plugin to Collection\n\nimport {\n\naddCollectionPlugin,\n\n} from '@metaplex-foundation/mpl-core'\n\nawait addCollectionPlugin(umi, {\n\ncollection: collection.publicKey,\n\nplugin: {\n\ntype: 'ImmutableMetadata',\n\n},\n\n}).sendAndConfirm(umi)\n\nCommon Errors\nAuthority mismatch\nOnly the update authority can add the ImmutableMetadata plugin.\nCannot update metadata\nThe ImmutableMetadata plugin is active. The name and URI cannot be changed.\nNotes\nThis action is permanent and irreversible\nDouble-check name and URI before adding this plugin\nAdding to a Collection makes ALL Assets in that Collection immutable\nThe plugin has no arguments—just add it to lock metadata\nQuick Reference\nAffected Fields\nFieldLocked\nname\n✅\n\nuri\n✅\n\nOther metadata\n❌ (use other methods)\n\nInheritance Behavior\nAdded ToEffect\nAsset\nOnly that Asset's metadata is locked\n\nCollection\nCollection AND all Assets' metadata locked\n\nFAQ\nCan I undo adding ImmutableMetadata?\nNo. Once added, the ImmutableMetadata plugin cannot be removed. The metadata is permanently locked. This is by design for provenance guarantees.\nWhat exactly becomes immutable?\nThe Asset or Collection's name and uri fields. Other plugin data is not affected—use authority None on individual plugins to make their data immutable.\nIf I add this to a Collection, are existing Assets affected?\nYes. When ImmutableMetadata is on a Collection, all Assets in that Collection inherit the immutability. Their metadata cannot be changed.\nCan I add this during Asset creation?\nYes. You can add ImmutableMetadata during create() to ensure the metadata is locked from the start.\nWhy would I want immutable metadata?\nImmutable metadata provides permanent provenance—collectors know the NFT's name and associated metadata URI can never be changed, preventing rug-pulls where creators swap out artwork or descriptions.\nRelated Plugins\nAddBlocker - Prevent new plugins (complementary to ImmutableMetadata)\nAttributes - On-chain data (not locked by ImmutableMetadata)\nRoyalties - Set royalties before making immutable\nGlossary\nTermDefinition\nImmutable\nCannot be changed or modified\n\nMetadata\nThe name and URI associated with an Asset/Collection\n\nProvenance\nVerifiable record of authenticity and ownership\n\nURI\nLink to off-chain JSON metadata\n\nInheritance\nAssets automatically get Collection-level plugin effects","tokens":1137,"crawled_at":1791194988076}
+{"id":10461,"url":"https://www.getfoundry.sh/anvil/mining","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Mining and Transaction Pool – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nMining and Transaction Pool\n\nAnvil can mine immediately, on a fixed interval, both ways, or only when you request a block. Choose the mode that matches the behavior you need to test instead of relying on the default instant-mining behavior.\n\nChoose a mining mode\n\nModeStart commandBehavior\nInstant\nanvil\nMines when ready transactions enter the pool. This is the default.\n\nInterval\nanvil --block-time 12\nMines a block every 12 seconds and includes ready transactions.\n\nMixed\nanvil --block-time 12 --mixed-mining\nMines on the timer and when a ready transaction arrives.\n\nManual\nanvil --no-mining\nKeeps transactions pending until you explicitly mine.\n\nUse instant mining for fast application development. Use interval mining to model confirmation delays and block batching. Mixed mining is useful when you want immediate transaction feedback but also need time-based empty blocks. Manual mining gives a test runner or coding agent full control over transaction ordering, timestamps, and block boundaries.\n\n--no-mining conflicts with --block-time. Mixed mining requires --block-time.\n\nMine on demand\n\nStart Anvil in manual mode:\n\n$ anvil --no-mining\n\nSubmit transactions without waiting for a receipt. A normal cast send waits for the transaction to be mined, so use --async when the same shell still needs to trigger mining:\n\n$ cast send --async $TO --value 1ether \\\n--private-key $PRIVATE_KEY \\\n--rpc-url http://127.0.0.1:8545\n\nMine one block:\n\n$ cast rpc --rpc-url http://127.0.0.1:8545 anvil_mine\n\nMine ten blocks and advance timestamps by 12 seconds between each block:\n\n$ cast rpc --rpc-url http://127.0.0.1:8545 anvil_mine 10 12\n\nThe interval passed to anvil_mine applies only to that RPC call. Use anvil_setBlockTimestampInterval when later blocks should continue advancing by a fixed amount:\n\n$ cast rpc anvil_setBlockTimestampInterval 12\n$ cast rpc anvil_removeBlockTimestampInterval\n\nYou can also use evm_mine to mine a single block. Use anvil_mine_detailed when automation needs the mined block data in the RPC response.\n\nChange modes at runtime\n\nDisable or enable instant mining without restarting the node:\n\n$ cast rpc evm_setAutomine false\n$ cast rpc evm_setAutomine true\n\nSwitch to interval mining, or disable mining with a zero interval:\n\n$ cast rpc evm_setIntervalMining 12\n$ cast rpc evm_setIntervalMining 0\n\nInspect the current mode before changing it:\n\n$ cast rpc anvil_getAutomine\n$ cast rpc anvil_getIntervalMining\n\nThe getters only identify pure instant and interval modes. In mixed mode, anvil_getAutomine\nreturns false and anvil_getIntervalMining reports no interval.\n\nevm_setAutomine false only disables pure instant mining; it is a no-op in interval and mixed\nmodes. Enabling automine replaces any non-instant mode with instant mining.\nevm_setIntervalMining always replaces the current mode with interval mining, or disables mining\nwhen passed 0. None of these methods can restore mixed mode, so use startup flags when a\nlong-running node must stay in that mode.\n\nControl transaction selection\n\nAnvil orders executable pool transactions by fees by default. Use FIFO ordering when deterministic arrival order matters:\n\n$ anvil --no-mining --order fifo\n\nAccount nonces still constrain execution: a transaction with a future nonce remains queued until its predecessors are available.\n\nLimit the size of transaction-triggered instant-mining batches:\n\n$ anvil --max-transactions 100\n\nInterval mining drains the ready pool at each tick. If you need exact block boundaries, use manual mining and submit only the transactions intended for the next block.\n\nInspect the pending pool\n\nUse the txpool namespace instead of inferring pending state from logs:\n\n$ cast rpc txpool_status\n$ cast rpc txpool_inspect\n$ cast rpc txpool_content\n$ cast rpc txpool_contentFrom $SENDER\n\ntxpool_status reports hexadecimal pending and queued counts. txpool_inspect returns a compact sender-and-nonce summary, while txpool_content returns full transaction objects.\n\nRemove one pending transaction or clear the entire pool:\n\n$ cast rpc anvil_dropTransaction $TX_HASH\n$ cast rpc anvil_dropAllTransactions\n\nDropping a transaction can move later nonces from pending to queued. Re-read txpool_status after mutating the pool.\n\nMake automation deterministic\n\nBind explicitly and write startup information to a file when another process launches Anvil:\n\n$ anvil \\\n--host 127.0.0.1 \\\n--port 8545 \\\n--no-mining \\\n--order fifo \\\n--config-out .anvil/config.json\n\nWait for an RPC response rather than treating process creation as node readiness:\n\n$ cast chain-id --rpc-url http://127.0.0.1:8545\n\nQuery anvil_nodeInfo for structured runtime state, including the current block, hardfork, transaction order, environment, and fork configuration:\n\n$ cast rpc --rpc-url http://127.0.0.1:8545 anvil_nodeInfo\n\nFor a repeatable test step, use this sequence:\n\nStart a fresh node or restore a known state file.\n\nWait for RPC readiness and verify the chain ID.\n\nSubmit transactions with --async and record their hashes.\n\nInspect the pool and assert the expected pending and queued counts.\n\nMine the intended block or blocks.\n\nFetch receipts by hash and assert the resulting block numbers and state.\n\nAgents should prefer these RPC results over terminal-log scraping. Start Anvil with --json only when you also need structured process logs; JSON logs do not replace the chain and pool RPC APIs.\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":1365,"crawled_at":1791194975271}
+{"id":10462,"url":"https://gov.uniswap.org/t/uniswap-foundation-summary-fy-2025-financials/26068","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Uniswap Foundation: Summary FY’2025 Financials - Uncategorized - Uniswap Governance","text":"Uniswap Foundation: Summary FY’2025 Financials\n\nUncategorized\n\nnataliara\n\nMarch 31, 2026, 8:28pm\n\n1\n\nContinuing with our series of financial transparency updates to the community, the Uniswap Foundation is pleased to publish the unaudited summary financials for the year ended December 31, 2025.\n\nThis report reflects the Foundation’s financial position prior to the changes post approval of the UNIfication governance proposal on December 26, 2025, which represents an important structural evolution for the Uniswap ecosystem.\n\n2025 marked a defining year for the Uniswap ecosystem, with major protocol launches, governance developments, and ecosystem expansion that strengthened the foundation for long-term growth.\n\nDuring the year, the ecosystem achieved several key milestones:\n\nLaunch of Uniswap v4, introducing hooks and a programmable architecture that significantly expands the design space for on-chain liquidity\n\nLaunch of Unichain, extending the Uniswap ecosystem with dedicated infrastructure designed to support high-performance DeFi applications\n\nContinued expansion of the Uniswap developer ecosystem, with more than 1,500 builders onboarding to v4 and thousands of hooks initialized across the ecosystem\n\nAdditional funding approved for the Uniswap Foundation through the Uniswap Unleashed governance proposal, strengthening the Foundation’s ability to support ecosystem development\n\nFormation of the DUNI legal entity, approved by governance to support the evolving structural needs of the ecosystem\n\nPublication of the UNIfication proposal, outlining a framework to better align the ecosystem’s institutional and governance structures\n\nGovernance approval of UNIfication on December 26, 2025\n\nAlongside these ecosystem developments, the Foundation continued supporting the growth of the Uniswap ecosystem through grants, developer programs, governance infrastructure, research initiatives, and ecosystem partnerships.\n\nTo learn more about the Uniswap community’s accomplishments during the year, please refer to the Uniswap Foundation Ecosystem Impact Report: 2025.\n\nAssets on Hand and Projected Funds Usage\n\nOn December 31, 2025 we had $49.9 million in USD and stables, 15.1 million UNI, and 240 ETH, or $85.8 million market value in tokens in USD terms at December 31, 2025’s closing rate on hand. The fiat (USD) cash and stables on hand were to be used for grantmaking and operating activities with significant UNI reserves held for future runway needs, allowing for additional upside exposure. The expected runway was through January 2027* and was earmarked as follows.\n\nFor grant commitments and incentives, a total of $106.2 million was allocated towards grants: $87.5 million to be committed and $18.7 million was reserved for grants committed previously, to be disbursed. $26.3 million was to be used to fund operations expenses and employee token awards.\n\n*The projected spend will be updated in the Q1’2026 report post UNIfication proposal passing and subsequent organizational changes.\n\nimage888×850 75.8 KB\n\nQ4’2025 Grants Committed and Disbursed\n\nimage1192×728 29.9 KB\n\nimage1224×740 34.3 KB\n\nQ4’2025 Commitments:\n\nIn Q4’2025 the Foundation committed $5.8 million in new grants and disbursed $2.1 million in committed grants. FY’2025, the Foundation committed $26 million in new grants and disbursed $11 million in committed grants.\n\nimage1070×1004 142 KB\n\nQ4’2025 Disbursements:\n\nimage1074×1300 153 KB\n\nQ1’2025, Q2’2025 and Q3’2025 financials, including grant commitments and disbursements, and operating expenditures are available to view here, here and here.\n\nFY’2025 Summary of Activities\n\nIn Q4’2025, the Foundation accrued $3.2 million in operating expenses, excluding 0.11 million employee token awards in UNI. The Foundation also realized $0.5 million in Revenue: Dividends and Interest in Q4’2025.\n\nIn FY’2025, the Foundation accrued $9.7 million in operating expenses, excluding 0.45 million employee token awards in UNI. The Foundation also received UNI 20.3M (in UNI) - or $114M market value at December 31, 2025 - from the Uniswap Treasury via the Uniswap Unleashed Proposal. The Foundation also realized $1.7M in Interest Revenue on fiat holdings.\n\nimage888×608 69.3 KB\n\nimage898×420 24.8 KB\n\nimage1198×736 39 KB\n\n*Ops expenses exclude employee token awards\n\nPayroll expenses included salaries, benefits and taxes. Contract & professional fees included legal, accounting, technical audit, and consultant expenses. Office expenses included internal team events, such as offsites, software, transaction fees and other G&A. External events included conference and external event travel and attendance. Advertising & marketing included web design, agency fees, TLDR event hosting. Insurance: includes directors and officers insurance.\n\nIn the following financial update post, we will continue with Q1’2026 results, including grants commitments and disbursements, operating expenses and summary of financial position. 2024 unaudited financial summary is available here.\n\nnataliara\n\nApril 1, 2026, 10:00pm\n\n2\n\nHi all,\n\nImportant context on the figures above. Since this report covers a period before the UNIfication proposal passed, it does not incorporate any of the changes that resulted from it.\n\nThe 2025 financials posted are intended to be a snapshot in time, as we publish every quarter. In these posts, we have described our spending and our projected runway as it stands each quarter, which we consider to be best practice. Because this was prepared to reflect Q4 2025, it reflected the Foundation’s plans to continue growing staff and expanding grant impact as a standalone org (pre-UNIfication). Those plans have changed with UNIfication passing, and the numbers in the post are not representative of what the budget looks like going forward for Q1 2026 and beyond.\n\nOur full Q1 2026 financial summary will reflect post-UNIfication operations, budget, and scope. We’ll have that out by May 1, 2026.\n\nIn the meantime some context on what’s changed with UNIfication: most Foundation staff transitioned to Labs, which absorbed the majority of the work (protocol stewardship, ecosystem support, developer relations) that was previously handled under the Foundation. That’s the main driver behind the $26.3M opex number, which you’ll see significantly reduced in Q1 financial summaries. The vast majority of the remaining UF treasury will be allocated towards grants making and ecosystem growth activities.\n\nThe Foundation retains a small, dedicated team focused on grant programs. As outlined in the UNIfication proposal, the Foundation’s existing assets fund its remaining scope. As part of this, the Foundation does not plan to request additional funds from governance.\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nUniswap Foundation: Summary Q1’2025 Financials\n\nUncategorized\n\n4\n\n1405\n\nJune 4, 2025\n\nUniswap Foundation: Summary Q2’2025 Financials\n\nUncategorized\n\n0\n\n1381\n\nSeptember 16, 2025\n\nUniswap Foundation: Summary Q3’2025 Financials\n\nUncategorized\n\n2\n\n739\n\nDecember 2, 2025\n\nUniswap Foundation: Summary FY’2024 Financials\n\nUncategorized\n\n0\n\n880\n\nApril 23, 2025\n\nUniswap Foundation: Summary 2023 Financials\n\nUncategorized\n\n8\n\n1908\n\nOctober 14, 2024","tokens":1802,"crawled_at":1791194990474}
+{"id":10463,"url":"https://www.getfoundry.sh/config/compiler","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Compiler – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nCompiler\n\nConfigure how Foundry compiles your Solidity contracts, including version management, optimization, and output options.\n\nSolidity version\n\nBy default, Foundry auto-detects the required Solidity version from your contracts. To pin a specific version:\n\nfoundry.toml\n[profile.default]\nsolc_version = \"0.8.28\"\n\nDisable auto-detection if you want full control:\n\nfoundry.toml\n[profile.default]\nsolc_version = \"0.8.28\"\nauto_detect_solc = false\n\nEVM version\n\nSet the target EVM version for compilation. This affects which opcodes are available:\n\nfoundry.toml\n[profile.default]\nevm_version = \"cancun\"\n\nCommon values: paris, shanghai, cancun, prague (default).\n\nOptimizer settings\n\nEnable the optimizer and configure the number of runs:\n\nfoundry.toml\n[profile.default]\noptimizer = true\noptimizer_runs = 200\n\nLower runs (e.g., 1): Optimizes for deployment cost\n\nHigher runs (e.g., 1000000): Optimizes for runtime cost (frequent calls)\n\nFor production deployments, consider higher optimizer runs:\n\nfoundry.toml\n[profile.production]\noptimizer = true\noptimizer_runs = 1000000\n\nVia IR\n\nEnable the new IR-based compilation pipeline for better optimization:\n\nfoundry.toml\n[profile.default]\nvia_ir = true\n\nThis can produce more optimized bytecode but increases compilation time.\n\nRemappings\n\nMap import paths to actual file locations:\n\nfoundry.toml\n[profile.default]\nremappings = [\n\"@openzeppelin/=lib/openzeppelin-contracts/\",\n\"@uniswap/=node_modules/@uniswap/\",\n]\n\nFoundry auto-detects remappings from your lib folder by default. To disable:\n\nfoundry.toml\n[profile.default]\nauto_detect_remappings = false\n\nIgnoring warnings\n\nSuppress specific compiler warnings:\n\nfoundry.toml\n[profile.default]\nignored_error_codes = [\"license\", \"code-size\"]\n\nOr treat all warnings as errors:\n\nfoundry.toml\n[profile.default]\ndeny_warnings = true\n\nBytecode metadata\n\nControl the metadata hash appended to bytecode:\n\nfoundry.toml\n[profile.default]\nbytecode_hash = \"none\" # Options: ipfs, bzzr1, none\ncbor_metadata = false\n\nSetting bytecode_hash = \"none\" is useful for deterministic deployments.\n\nExtra output\n\nInclude additional compiler output in artifacts:\n\nfoundry.toml\n[profile.default]\nextra_output = [\"storageLayout\", \"metadata\"]\nextra_output_files = [\"ir\", \"irOptimized\"]\n\nExample configuration\n\nA complete compiler configuration for production:\n\nfoundry.toml\n[profile.default]\nsolc_version = \"0.8.28\"\nevm_version = \"cancun\"\noptimizer = true\noptimizer_runs = 200\nvia_ir = false\n\n[profile.production]\noptimizer_runs = 1000000\nvia_ir = true\nbytecode_hash = \"none\"\n\nFor the complete list of compiler options, see the Solidity Compiler Reference.\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":680,"crawled_at":1791194992445}
+{"id":10464,"url":"https://www.metaplex.com/docs/smart-contracts/core/plugins/permanent-transfer-delegate","domain":"www.metaplex.com","chapter":"docs","title":"Permanent Transfer Delegate | Metaplex Core","text":"The Permanent Transfer Delegate Plugin provides irrevocable transfer authority that persists forever. Unlike regular Transfer Delegate, this authority is never revoked and can transfer Assets repeatedly.\nWhat You'll Learn\nCreate Assets with permanent transfer capability\nEnable collection-wide transfer authority\nUse cases: games, subscriptions, automated systems\nUnderstand permanent vs regular transfer delegate\n\nSummary\nThe Permanent Transfer Delegate is a permanent plugin that can only be added at creation time. The delegate can transfer the Asset unlimited times without owner approval.\nCan only be added at Asset/Collection creation\nAuthority persists forever (never revoked)\nUses forceApprove - can transfer even when frozen\nCollection-level: allows transfer of any Asset in the Collection\nOut of Scope\nRegular transfer delegate (see Transfer Delegate), escrowless listings (use regular delegate), and Token Metadata transfer authority.\nQuick Start\nJump to: Create Asset\nAdd PermanentTransferDelegate plugin at Asset/Collection creation\nSet the authority to your program or delegate address\nThe delegate can transfer the Asset at any time, unlimited times\nPermanent vs Regular Transfer Delegate\nFeatureTransfer DelegatePermanent Transfer Delegate\nAdd after creation\n✅ Yes\n❌ Creation only\n\nAuthority persists on transfer\n❌ Revokes after 1 transfer\n✅ Persists forever\n\nMultiple transfers\n❌ One-time\n✅ Unlimited\n\nCan transfer frozen Assets\n❌ No\n✅ Yes (forceApprove)\n\nWorks with Collections\n❌ No\n✅ Yes\n\nChoose Transfer Delegate for one-time escrowless sales.\n\nChoose Permanent Transfer Delegate for games, rentals, or automated systems needing repeated transfers.\n\nCommon Use Cases\nGame mechanics: Transfer Assets when game events occur (losing battles, trading)\nRental returns: Automatically return rented NFTs to the owner\nSubscription management: Transfer tokens when subscriptions end or renew\nDAO treasury management: Allow DAOs to manage Asset distribution\nAutomated systems: Programs that need to move Assets without per-transfer approval\nWorks With\n\nMPL Core Asset\n✅\n\nMPL Core Collection\n✅\n\nBehaviours\nAsset: Allows transferring of the Asset using the delegated address.\nCollection: Allows transferring of any Asset in the collection using the collection authority. It does not transfer all at once.\nArguments\nArgValue\nfrozen\nbool\n\nCreating a MPL Core Asset with a Permanent Transfer Plugin\nCreating a MPL Core Asset with a Permanent Transfer Plugin\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { create } from '@metaplex-foundation/mpl-core'\n\nconst assetSigner = generateSigner(umi)\n\nconst delegate = publicKey('33333333333333333333333333333')\n\nawait create(umi, {\n\nasset: assetSigner,\n\nname: 'My Asset',\n\nuri: 'https://example.com/my-asset.json',\n\nplugins: [\n\n{\n\ntype: 'PermanentTransferDelegate',\n\nauthority: { type: 'Address', address: delegate },\n\n},\n\n],\n\n}).sendAndConfirm(umi)\n\nCommon Errors\nCannot add permanent plugin after creation\nPermanent plugins can only be added at Asset/Collection creation. You cannot add a Permanent Transfer Delegate to an existing Asset.\nAuthority mismatch\nOnly the plugin authority can transfer. Verify you're signing with the correct keypair.\nNotes\nOn creation only: Cannot be added after Asset/Collection exists\nForce approve: Can transfer even when frozen\nCollection behavior: Can transfer any Asset in the Collection individually\nPersists forever: Authority is never revoked\nUnlimited transfers: No limit on how many times the delegate can transfer\nFAQ\nWhat's the difference between Transfer Delegate and Permanent Transfer Delegate?\nRegular Transfer Delegate is revoked after one transfer. Permanent Transfer Delegate persists forever and can transfer unlimited times.\nCan Permanent Transfer Delegate transfer frozen Assets?\nYes. Permanent plugins use forceApprove, which overrides freeze rejections.\nCan I add this to an existing Asset?\nNo. Permanent plugins can only be added at Asset creation time. Use regular Transfer Delegate for existing Assets.\nHow does Collection-level Permanent Transfer Delegate work?\nThe delegate can transfer any individual Asset in the Collection, but not all at once. Each transfer is a separate transaction.\nRelated Plugins\nTransfer Delegate - One-time transfer authority\nPermanent Freeze Delegate - Permanent freeze authority\nPermanent Burn Delegate - Permanent burn authority\nGlossary\nTermDefinition\nPermanent Plugin\nPlugin that can only be added at creation and persists forever\n\nforceApprove\nValidation that overrides other plugin rejections\n\nCollection Transfer\nAbility to transfer any Asset in a Collection","tokens":1155,"crawled_at":1791195005702}
+{"id":10465,"url":"https://a16zcrypto.com/posts/tags/hr-people-practices","domain":"a16zcrypto.com","chapter":"research","title":"people practices & HR - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\npeople practices & HR\n\nFeed\nFILTERS\n(1)\nclear filters\n\ncategories\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\n(1) recommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nclear all people practices & HR\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n08.22.24 / Craig Naylor, Mehdi Hasan and Madan Nagaldinne\nHiring and retaining talent in web3\nIn this talk, Craig Naylor, Mehdi Hasan, and Madan Nagaldinne share strategies for hiring and retaining strong teams for web3 startups.\n\ncompany building\nCSX 2024 (London)\nhiring & recruiting\npeople practices & HR\nvideo\n\n08.22.24 / Aurora Petracca\nWhy startups should hire recruiters much sooner than they think\nHow early should you hire a recruiter? They should be among your first ten employees: An explanation of why, and how to find the right one\n\ncompany building\nhiring & recruiting\npeople practices & HR\n\n03.28.24 / Brian Armstrong and Chris Dixon\nLeading through uncertainty (with Coinbase CEO)\nCoinbase CEO Brian Armstrong speaks with a16z crypto founder Chris Dixon about FTX, crypto in politics, company building, and more.\n\ncompany building\nbusiness strategy\nfounder stories\nFounders Summits\npeople practices & HR\npodcast\n\n06.29.23 / Jeanne Tsan\nHow to set up people operations for web3 founders\nA talk on saving time, energy, and heartache while setting up hiring, human resources, and other people operations.\n\ncompany building\nCSX 2023\npeople practices & HR\nvideo\n\n06.29.23 / Craig Naylor and Mehdi Hasan\nHow to hire and scale in web3\nA deep dive on hiring in web3, with advice and frameworks for all founders – from defining your needs to building a talent brand people want to be part of.\n\ncompany building\nCSX 2023\nhiring & recruiting\npeople practices & HR\nvideo\n\n06.29.23 / Kristen Kee and Daisy Linden\nBuilding culture\nHow Coinbase & Uniswap build culture with Daisy Linden (Sr. Director, Employee Experience and Benefits, Coinbase) and Kristen Kee (VP of People, Uniswap Labs).\n\ncompany building\nCSX 2023\npeople practices & HR\nvideo\n\n03.01.23 / Tina Ferguson\nManaging Distributed Workforces\nTina Ferguson of a16z’s Tech Talent and People Practices team offers guidance on “Managing a Distributed Workforce.”\n\ncompany building\nCSX 2020\npeople practices & HR\nvideo\n\n12.02.22 / Brian Armstrong and Ben Horowitz\nBuilding and Overcoming the Hard Things\nA chat between Coinbase CEO Brian Armstrong; and a16z co-founder Ben Horowitz into management, company culture, and overcoming the hard things while innovating.\n\ncompany building\nDeFi\nfounder stories\npeople practices & HR\nvideo\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":1343,"crawled_at":1791195016928}
+{"id":10466,"url":"https://gov.uniswap.org/t/uniswap-council-uc-season-4-report/26064","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Uniswap Council (UC): Season 4 Report - Governance-Meta - Uniswap Governance","text":"Uniswap Council (UC): Season 4 Report\n\nGovernance-Meta\n\nAbdullahUmar\n\nMarch 25, 2026, 11:27pm\n\n1\n\nThis post provides additional operational and financial detail supporting the Season 5 Renewal Proposal. While the renewal proposal outlines the UC’s forward-looking mandate and budget request, the information below offers a deeper look into some of the UC’s activities throughout Season 4, covering deployments, incentive programs, entity oversight, governance analysis, and accounting.\n\nDelegates and tokenholders looking for further context on any of the items referenced in the renewal can find those details here. Newly proposed mandates such as treasury management, burn bounty, and grant graduation pipeline are solely outlined in the renewal post.\n\nUniswap Deployments and Incentives\n\nThe UC supports operational coordination related to Uniswap v3 deployments and incentive programs by serving as an administrative and execution layer for DAO-approved initiatives. This includes facilitating cross-chain deployment workflows in coordination with ecosystem partners like Oku and Protofire, maintaining canonical references such as the ENS subdomain and official contract registry, and supporting the disbursement of incentives associated with various chains. The below details are up-to-date as of EOY 2025, at the conclusion of Season 4.\n\nChain Growth\n\nSeason 4 saw a clear plateau in new chain deployments as Uniswap v3 has now expanded to most large L2s and EVM L1s.\n\nDeployments by season:\n\nSeason 2: 7\n\nSeason 3: 17\n\nSeason 4: 8\n\nApproved deployments during Season 4 organized by deployer:\n\nUniswap Labs\n\nMonad\n\nOku\n\nEtherLink\n\nNibiru\n\nLens\n\nPlasma\n\nXDC\n\nRedbelly\n\nProtofire\n\nFlow\n\nThe presiding approach with DAO-led v3 deployments has been one of expansion due to the relatively low downside with cross-chain growth, with the potential to establish Uniswap as the canonical DEX on the given chain. As it is difficult to ascertain which chains will, for certain, garner strong traction, it has been thus far beneficial for Uniswap to expand to as many chains as possible.\n\nFor example, there are multiple chains that Uniswap Labs has chosen not to deploy to, but they’ve been successful expansion opportunities for the protocol. Good examples include Gnosis, Plasma, BOB, and Abstract. Note that deployments completed by parties other than Labs most often reside on a third-party platform, with Oku.trade being the largest third-party venue at the moment.\n\nGnosis:\n\nTVL on Gnosis grew from $11.8M to $26.1M in 2025.\n\nAs of Q4 2025, Uniswap became the primary DEX on the chain, supplanting Balancer’s position after the protocol’s unfortunate exploit in November.\n\nWithout a DAO-led v3 deployment, Gnosis itself would have been in a precarious situation, and Uniswap would not have been able to capture the growth seen on the chain over the past 12 months despite end-of-year volatility.\n\nThe summed cost to the DAO for this deployment equates to $415k\n\n$250k in UNI incentives (passed August 2024)\n\n$105k for Oku integration and maintenance (passed August 2024)\n\n$60k for Oku maintenance (passed December 2025)\n\nUni TVL on Gnosis1181×396 19.9 KB\n\nPlasma:\n\nPlasma was of the first stablecoin-focused chains, launching late September, garnering very strong support from various DeFi partners, investors, and liquidity providers. The UC and Oku collaborated with the Plasma team to deploy Uni v3 on the chain and attain ~$800k worth of incentives.\n\nPrior to the October 10th liquidation cascade, and corresponding decline in the XPL token price, this deployment reached approximately $60M in TVL, similar to TVL on chains as large as Optimism. Since incentives concluded in late November, Plasma TVL had been at a relatively steady state around $25M through EOY, sitting as the second largest DEX on the chain—behind Fluid in TVL but ahead of both Balancer and Curve.\n\nThe summed cost to the DAO for this deployment equates to $0.\n\nPlasma paid Oku for the deployment and front-end integration directly.\n\nPlasma allocated $800k XPL in incentives, but Uniswap has not matched any of that.\n\nBOB:\n\nUniswap deployed on BOB in Q4 2024, immediately becoming the primary DEX.\n\nThe deployment held $42M in TVL at EOY and hit a maximum value of $130M in December 2024 as individuals were airdrop farming.\n\nSince Uniswap launched, it sustained its status as the largest DEX on the chain, and for some time, the largest DeFi protocol on BOB by TVL, ahead of lending markets.\n\nHowever, recent volume for the deployment was lackluster, sitting around $200k average daily volume between August-December 2025. This has become even more steep going into 2026.\n\nCompared to other BTC-focused chains like Rootstock, BOB’s overall activity started indicating significant weakness in LP and trader retention.\n\nThe DAO approved a total of $270k (includes Merkl costs) worth of incentives for BOB in late April ‘25, along with a $105k Oku rebate.\n\nNeither of these ended up being disbursed due to the decline in the chain’s activity and unclarity from the BOB team around sustaining growth. The UC maintained communications with their team throughout the year but didn’t attain enough confidence in their plan to allocate the DAO-approved incentives. All of the above funds associated with BOB have been returned to the DAO as of February 2026.\n\nHence, BOB serves as a key example of a chain that attained transitory success, driving significant fees and volume—but only for a limited period.\n\nAbstract:\n\nUniswap v3 & v2 were both deployed on Abstract in February 2025 and have fluctuated between $7M - $30M in TVL since launch, ending the year at ~$8M.\n\nThe deploying team was Protofire, but the primary front-end, as requested by the Abstract team, is present within the Abstract portal, giving users who utilize the chain for activities like streaming access to trading.\n\nThis deployment is an example of how chain-white-labeled front-ends, powered by Uniswap in the backend, can help Uniswap grow.\n\nAbstract Native Swap Interface (powered by Uni v3)1600×537 46.8 KB\n\nCost of Chain Expansion\n\nThere are, however, downsides to this broad stroke deployment strategy, primarily pertaining to management complexity introduced when turning on fee switches and expenditure of resources for incentives and integrations. This is an important point of reflection when it comes to v4 deployments going forward.\n\nThird parties, including Oku and Protofire, have their own economic incentive for conducting deployments, which offloads some of the burden from the DAO. The UC collaborates with these two teams to oversee deployment operations in an optimistic manner as to reduce broader governance overhead. Each chain tends to sign an agreement with a given deployer, and that deployer also maintains a front-end. Deployment and maintenance costs are directly tended to in an agreement between the target chain and the deployer. The UC only gets involved in the costs associated with deployments when they are subsidized by the DAO. As of EOY 2025, the UC has disbursed a total of $720,000 to Oku for implementation and maintenance for 7 chains, with Unichain deviating from customary costs due to a discount.\n\nOku integration and maintenance costs by chain307×177 2.28 KB\n\nOf these deployments, Blast and Taiko have now been deprecated due to lack of traction on both of the chains, but the DAO recently voted to renew maintenance payments for Gnosis, Linea, and Mantle, amounting to a total $180k expense over 12 months. Note that no new chains over the past season were subsidized by the DAO; the chains directly paid for these integrations.\n\nMoreover, multiple chains, without DAO subsidy, have decided to cease their contracts with Oku and Protofire. These include:\n\nOku\n\nPolygon zkEVM\n\nMoonbeam\n\nManta\n\nLisk\n\nMetal\n\nScroll\n\nProtofire\n\nInk\n\nCyber\n\nRedstone\n\nShape\n\nAccordingly, a total of 12 chains have been deprecated at EOY. Note that deprecation here means that the chains do not presently have a front-end for accessing the v3 contracts, but of course, the contracts are still usable. The UC will maintain the registry of official contracts on this forum post for continuity purposes. Deployments like Linea and Mantle have so far been deemed by governance as promising—due to potential catalysts like ecosystem-wide incentive programs and likely sustenance based on large capital backing—so it’s worth maintaining them to be prepared for future revitalization initiatives. However, some chains, like Polygon zkEVM and Blast, have clearly been abandoned and are not worth maintaining or reexploring.\n\nIn relation to fee switch complexities, additional Uniswap deployments multiply the DAO’s fee-governance surface area. Fees aren’t toggled “globally.” They are enabled at chain-specific factory endpoints and associated message passing complexities due to the utilization of various bridges and owner/aliasing models. For example:\n\nOP L2s: Governance actions are sent from Ethereum mainnet through the OP Stack L1CrossDomainMessenger and executed on the target chain by a CrossChainAccount contract, which forwards the call to the Uniswap contract.\n\nWormhole: Most alt-EVM L1s are deployed using Wormhole. Governance calldata is sent from Ethereum via a canonical UniswapWormholeMessageSender contract and executed on the destination chain by a Wormhole message receiver. This has been led mainly by Oku, used by Celo, Gnosis, Rootstock, Sei, Saga, etc.\n\nLayerZero: Proposals are transmitted through a LayerZero v1 endpoint and executed on the destination chain by an OmnichainGovernanceExecutor. This is currently only used for Avalanche. LZ is now moving towards their v2 architecture, so future LZ-based deployments may refer to v2 endpoints. This is potentially another source of complexity.\n\nzkSync and Elastic Chains: Governance actions are sent from Ethereum mainnet through zkSync’s canonical L1 MailboxFacet, which enqueues the call as a priority L1→L2 transaction via requestL2Transaction. The zkSync sequencer executes the message on the destination chain (zkSync Era or Elastic chains such as ZERO and Abstract), where the call is delivered to the target v3 factory contract with an L2 sender derived from the aliased L1 governance address.\n\nAxelar: Governance actions are sent from Ethereum mainnet through Axelar’s General Message Passing (GMP) framework, where calldata is relayed by the Axelar network and executed on the destination chain by an Axelar-connected executor or gateway contract, which then forwards the call to the Uniswap contracts on that chain. Flow and Filecoin Virtual Machine (FVM) deployments use this setup.\n\nArbitrum: Governance actions are executed through an aliased L2 owner derived from the Ethereum L1 timelock, with proposals forwarded from mainnet via createRetryableTicket on the Arbitrum Inbox, carrying the encoded Uniswap calldata for execution on L2.\n\nThe result of the above is a heavier operational burden and higher coordination overhead. It may be prudent to consider implementing optimistic governance for more easily managing fees.\n\nCorrespondingly, these considerations allude significantly towards how v4 expansion will function going forward. These initiatives have primarily been spearheaded by the Foundation/Labs at the moment, with growth focusing on larger chains like Unichain, mainnet, and Base. Complexity with sustaining a hook-driven ecosystem also requires mindful expansion. For example, how much more growth is possible on, say, Rootstock, if we deployed v4? Would it make a material difference relative to the existing v3 deployment? We are remaining mindful of such considerations, especially since Oku is nearing completion of their v4 infrastructure and will soon be able to support v4 on multiple chains. This process will require further strategic coordination since Oku’s ability to deploy v4 for production requires Foundation approval. This process is likely to remain in Labs’ discretion for now especially since they’ve passed fee activation on Labs-led v2/v3 deployments already.\n\nChain Incentives\n\nOver the past season, the UC has aimed to ensure that outright financial expenses pertaining to deployments were kept at a reasonable level. This strategy has been demonstrated throughout the course of 2025, contrasting notably from how the DAO approached chain incentives in 2024.\n\nChains that move forward with incentive deployments were first advised to match a portion of their future ask from Uniswap DAO with some of their own funds. This helps sift through which chains are worth focusing on to a deeper extent, potentially moving forward with an incentive-matching proposal.\n\nDuring Season 4, the DAO saw three incentive matching proposals that completed the Snapshot phase:\n\nJuly:\n\nEtherlink proposed a 2:1 match, requesting $150k from Uniswap, while matching $300k on their end, as part of their Apple Farm campaign. The proposal did not proceed to an onchain vote as it failed the Snapshot, with 61% No votes.\n\nIn August, Etherlink allocated $10,500 to the v3 deployment.\n\nEtherlink EOY TVL sat at ~$5M and was doing approximately $3M in volume daily since July.\n\nSeptember:\n\nRonin requested a 2:1 match from the DAO, with Ronin allocating $1M and Uniswap allocating $250k. This proposal passed the Snapshot phase with 55% For votes. The Ronin team decided not to move forward with an onchain vote until they get closer to the chain’s L2 migration—along with suggestions from the UC to more carefully consider matching terms so the onchain vote wouldn’t cut as close as the Snapshot vote. At the moment, there isn’t a plan to revisit these incentives.\n\nOctober:\n\nAs part of the go-to-market strategy, Plasma intended to allocate a total of $3-$5M worth of XPL incentive to the v3 deployment over the course of 6 months. The team ended up allocating approximately $800k between September 25 and November 20. The UC indicated matching a portion of the XPL incentives, allotting $250k from the UC’s discretionary budget. The DAO also indicated near unanimous support for allocating an additional $250k UNI from the treasury, summing the total match from Uniswap to $500k. Due to significant fluctuations in the UNI discretionary budget and quorum uncertainties, the Uniswap incentives were delayed, with the UC not finding it prudent to allocate capital to this deployment at the end of ‘25. Plasma also cut back heavily on their chain-wide incentives, in part due to a lack of co-incentives.\n\nPlasma demonstrated why Uniswap should be pursuing day-one deployments on high potential chains. Notably, on day two of launch, the v3 deployment facilitated $164M worth of volume, generating $540k in fees.\n\nHowever, since the UC discretionary budget has now been closed out, we will not be revisiting co-incentives for Plasma under the conditions of the previous Snapshot vote.\n\nFees from Uniswap v3 on Plasma1193×390 16.3 KB\n\nSaga:\n\nAlthough Saga’s incentive matching proposal took place during Season 3—and even though the proposal was rejected—their team allocated approximately $1.67M SAGA tokens to the v3 deployment between April and September. At EOY, Uniswap remained the main DEX on the chain and held $12M in TVL. May and June, the months with higher incentive allocations, saw between $20M - $40M in daily volume. Volume numbers fluctuated around $5M daily through July and November, tipping towards $1M in December.\n\nSaga paid Oku for the deployment and front-end integration directly.\n\nSaga has allocated $1.67M SAGA in incentives so far, but Uniswap has not matched any of those incentives.\n\nCelo:\n\nAs far as DAO-approved incentives go, solely the Celo incentives were disbursed during the past season, between April and October, amounting to a total of $250k UNI disbursed. These were supplemented by $500k worth of CELO incentives by the Stabila team. The majority of the incentives went towards blue-chip pools, with a minority allocation given to Celo-specific pairs that included tokens like cEUR, cREAL, cGHS, cCOP, and cUSO.\n\nChart1200×742 18.5 KB\n\nBy EOY, the Celo deployment held approximately $20M in TVL and had the majority DEX market share on the chain.\n\nUniswap paid Oku for the deployment and front-end integration for Celo to the tune of $105k.\n\nCelo has allocated $500k in incentives so far.\n\nUniswap has allocated $250k in incentives.\n\nOther Chains:\n\nOther chains have allocated smaller amounts of incentives, and they have been advised to hold off on any new incentive requests from Uniswap until they are willing to commit more resources to their deployment. Examples here include:\n\n~$15k from LightLink\n\n~$10k from Telos\n\n~$20k from Lens\n\nThe above three tested out incentives on Metrom as opposed to Merkl. They are currently not pursuing incentive matching.\n\nGoing forward, incentives administration, in the form that they have been conducted historically, will not be dealt with by the UC. This is both in response to the new organizational structure of the DUNI and the suboptimal results incentives produce in tougher markets.\n\nEntity Oversight and Information Liaison\n\nOver the past year, the UC has functioned as an information bridge between the DAO and the Uniswap Foundation, primarily through the Foundation Feedback Group (FFG). The FFG was explicitly designed to improve communication and accountability as a result of the Foundation’s renewal (Uniswap Unleashed).\n\nThe purpose of the FFG was not to direct the Foundation’s work but rather to provide a structured environment in which high-context information could be shared and translated into public updates for the DAO. The Foundation was able to discuss roadmap items, ongoing initiatives, and internal constraints. Meanwhile, the UC ensured that the broader community retained a clear, aggregated understanding of the Foundation’s progress without requiring the disclosure of competitively sensitive or legally constrained details. Additionally, the FFG allowed for bi-directional communications as the UC would source and consolidate community/DAO questions and feedback as garnered through surveying and community calls, which would then be shared with The Foundation for response.\n\nThis pattern of communication, Foundation briefing followed by distilled public reporting, has proved to be functional.\n\nIt balances two competing needs:\n\nThe DAO’s expectation of visibility and accountability.\n\nThe operational entities need to protect proprietary, strategic, or pre-announcement information.\n\nThe UC’s role was to moderate these sessions and provide feedback on various Foundation initiatives, maintaining a public record summarizing major directional themes. It created a dependable feedback channel without imposing friction on day-to-day execution.\n\nAs the ecosystem transitions into the next stage of organizational evolution with the emergence of DUNI and the formalization of Labs’ relationship to governance as a service provider, this liaison function remains important. Historically, Labs operated without formal reporting obligations to token holders. It is, after all, a private corporation, very different from the Foundation. Decisions were communicated publicly at their discretion. Products were released as they were deemed strategically fit. Under the service provider engagement with DUNI, this dynamic shifts. While Labs must preserve its ability to operate competitively, it is now entering into a structured, compensated relationship with Uniswap governance. That relationship necessarily introduces expectations around transparent reporting and mandate alignment that go beyond ad-hoc public announcements.\n\nWith the Foundation and Labs actively exploring how responsibilities and reporting practices will be consolidated, it would be premature to prescribe a fixed successor to the FFG at this time. Instead, the UC intends to remain in communication with the relevant teams as this transition unfolds, with the goal of identifying an appropriate mechanism for ongoing information exchange. The guiding objective remains consistent with prior seasons: preserving transparency and accountability at the DAO level without introducing friction or compromising the ability of operational entities to execute effectively.\n\nGovernance Logistics Details\n\nDuring Season 4, the UC conducted an analysis on the overall state of governance (Governance Logistics Improvements), instigated by the sudden loss of significant voting power among a cohort of well-known delegates. This initiative analyzed major structural pain points in Uniswap DAO governance, opening community dialogue about potential paths forward.\n\nCore Issues Analyzed\n\nExtremely high quorum threshold (~$280M / ~40M UNI at the time, ~6.66% of circulating supply)—the highest dollar-value quorum among major DAOs\n\nResulting low proposal throughput and frequent quorum failures\n\nSignificant concentration of influence among a very small number of large holders\n\nVoter fatigue and difficulty sustaining participation for routine matters\n\nSecurity vs. usability trade-off given the size of the treasury\n\nMain Directions Explored\n\nQuorum adjustment (increase, decrease, or leave unchanged) → UC expressed the current view that the costs and risks of changing quorum currently outweigh the benefits\n\nOptimistic Governance (Aragon-inspired model using privileged committees + community veto window) → Seen as the most promising near-to-medium-term structural improvement → Already partially implemented successfully for cross-chain deployments\n\nOther complementary mechanisms\n\nCommunity Process Facilitators (CPFs)\n\nExpanded Independent Delegate Votes (IDVs)\n\nStrategic treasury delegations\n\nOutcomes & Community Reception (as of end of Season 4 / early Season 5 transition)\n\nThe post received a broadly constructive reception from active delegates, community members, and other governance participants\n\nStrongest resonance appeared around:\n\nRecognition of the very high economic security provided by the current quorum (widely viewed as valuable)\n\nFrustration with repeated quorum failures on meaningful but non-controversial proposals\n\nInterest in optimistic governance as a practical way to reduce voter fatigue while preserving ultimate tokenholder control\n\nMany participants expressed a preference for exploring optimistic and economically driven models first before considering any direct quorum change\n\nSeveral commenters highlighted the need to carefully design veto thresholds and challenge mechanisms to avoid creating new attack vectors or new forms of centralization\n\nNo strong community push emerged to immediately lower the quorum threshold\n\nClear appetite for continued structured work on governance scalability\n\nThere has also been a significant change in the makeup of overall delegations. Adoption of DUNA has quelled many of the worries of larger token holders and delegates regarding actively participating in votes.\n\nAs Uniswap governance enters this new stage, maintaining a reliable view of governance risk has become increasingly important. The UC’s objective in this area is to provide neutral, data-informed visibility into emerging governance threats, power-concentration dynamics, operational risk factors that may impact governance integrity, etc.\n\nAccounting and Financials\n\nThe accounting details in this section are up-to-date as of end of February 2026, and assumes a UNI price of $4.00. Also note that all of the account balances, along with their respective inflows and outflows, are cumulative from the establishment of the UC.\n\nDuring the 2025 fiscal year, a total of 129,831,069 UNI left the timelock, of which 77.02% represented the burn executed by the UNIfication proposal. The remaining 22.98%, accounting for 29,831,069 UNI, represented outflows pertaining to expenses. Seven of the total outflows pertaining to the UC for program escrow or UC-related expenditures, amounting to 1.11% of the total 2025 expenses. Uniswap Foundation-led incentives and funding represented 93.56% of outflows, while 5.33% of the outflows were for DUNI-associated expenditures.\n\nTimelock Outflows in 2025749×320 9.86 KB\n\nSimilar to prior seasons, there exist multiple benefits of utilizing an intermediary escrow setup. It grants the DAO a customary venue for issuing treasury-based UNI upon the execution of an onchain vote. There are often questions around what entity a proposer should direct their capital towards, and the UC wallet helps create a structure for such an organization. The DAO can distinguish between the treasury as a whole and operating capital that has been approved for consumption by governance vote. Better accountability is also implemented when the UC is able to verify the completion of work prior to conducting disbursements. However, with the establishment of the DUNI, the intermediary nature of the UC-held funds poses legal and tax complexity. The UC is therefore taking a step back from an escrow model going into Season 5.\n\nThis season, the UC saw dollar-denominated inflows, totaling $0.89M, bringing the total UC inflow to $10.64M.\n\nUC Token Inflows for Season 41600×325 68.7 KB\n\nProgram Account Balances\n\n“Accounts” are effectively the prescribed balances associated with a particular program that the DAO has voted in. Accounts are considered “currently allocated” if their budget has been fully disbursed. There are a total of ten Accounts, only three of which have not been fully allocated as of end of February ‘26:\n\nIncentive Package\n\nOku v4\n\nTally Grant\n\nCurrently Allocated:\n\nDelegate Reward WG\n\nUC Payroll/Operations\n\nUniswap Ecosystem Incentives Initiative\n\nUniswap Treasury Working Group (UTWG)\n\nUniswap Growth Program\n\nForse Grant\n\nDelegate Compensation\n\nThe all funds associated with unallocated Accounts, as well as residual UNI surplus from allocated Accounts, have been sent back to the DUNI multisig, run by the Administrator & Ministerial Agent. Therefore, remaining funds allocated for the Incentive Package, Oku v4, and Tally Grant Accounts are to be processed by the DUNI multisig.\n\nCorrespondingly, the Discretionary Budget has also been terminated since associated funds were derived from a dollar-based surplus in the Incentive Package Account.\n\nIncentive Package Account\n\nFollowing the information from the incentive packages section, this Account is responsible for tracking three types of payments:\n\nIncentives for distribution\n\nDistribution partner integration cost\n\nFront-end integration cost\n\nimage1084×1026 113 KB\n\nThere are no payables pending for Merkl integrations, and the most recent $180k for Gnosis, Linea, and Mantle Deployments passed in this vote have been sent and processed by the Ministerial Agent.\n\nChain Incentive Notes\n\nSonic cut their incentives short after distributing 40% of the $500k that they promised. In turn, we also cut off our incentives at the 40% mark, allocating only $100k of the allotted $250k. As such, the Current Balance decreased by $150k, leaving a surplus.\n\nCelo incentives were fully allocated during Season 4.\n\nRemaining Blast and BSC Incentives were put on hold for better allocation opportunities in the future.\n\nNone of the BOB incentives were allocated.\n\nAll of the unallocated capital—285,471 UNI—from the above line items was returned to the DUNI. There is no present intention to allocate this capital for its initially intended purpose of incentive distribution.\n\nOku Uniswap v4\n\nDuring Season 4, a vote for Oku to deploy on Unichain, as well as developing and integrating a Uniswap v4 front end, was passed. In total, $340k was allocated for this.\n\nimage1224×466 41.2 KB\n\nOf the total budget, $90k has already been paid out, with $250k pending upon future completion. There is a deficit in this account due to UNI price falling, but we do not believe we need to request a rebalance for this amount, as it is the only account in a deficit, and other accounts are able to be pulled from to assist in payables here. Similarly, funds for this account—totaling 38,800 UNI—have been sent to the DUNI and will be processed by the Ministerial Agent.\n\nTally Grant\n\nThe DAO previously approved to fund Tally operations and development between Q1 2025 - Q4 2026, spreading a total $500k across 8 even disbursements. The UC has paid Tally at the start of each quarter based on their plan for the upcoming quarter, along with progress and upkeep status on the previous quarter.\n\nFive of the 8 $62.5k payments have so far been made out to Tally, with the last one—and potential future ones—being conducted by the Ministerial Agent. The UC transferred the Tally balance to the DUNI multisig in January.\n\nResetting with New Accounts\n\nGoing into Season 5, the UC will be requesting new budgets for upcoming programs since the UNI balance controlled by the UC presently sits at zero. All residual account balances have been fully sent to the DUNI.\n\n3 Likes\n\nUniswap Council (UC): Season 5 Renewal\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n404 DAO Delegate Platform\n\nDelegation Pitch\n\n39\n\n3283\n\nJanuary 13, 2026\n\nTané Delegate Platform\n\nDelegation Pitch\n\n59\n\n2404\n\nMarch 9, 2026\n\nGFX Labs - Delegate Communication Thread\n\nDelegation Pitch\n\n27\n\n1504\n\nDecember 8, 2025\n\nUniswap Deployments Accountability Committee [Update Thread]\n\nGovernance-Meta\n\n15\n\n4579\n\nApril 18, 2025\n\nAvantgarde Finance Delegate Platform\n\nDelegation Pitch\n\n32\n\n1063\n\nNovember 27, 2025","tokens":7335,"crawled_at":1791195017871}
+{"id":10467,"url":"https://docs.ethena.fi/backing-assets/protocol-revenue","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Protocol Revenue | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nEthena generates revenue from its backing assets. As the backing portfolio has diversified, so have the sources of that revenue, which now span several distinct and largely uncorrelated streams.\nProtocol revenue is generated from:\n\nFunding and basis spread. The funding and basis earned on delta-neutral basis trades, in crypto markets and, increasingly, in non-crypto markets such as tokenised commodities. Historically, the mismatch between demand and supply for leveraged exposure has resulted in a positive funding and basis return over time.\n\nLending revenue. The return earned on investments in overcollateralised loans of stable assets, supplied both into on-chain DeFi lending markets and to institutional counterparties.\n\nReal-world asset yield. The yield earned on tokenised real-world assets held as backing, including short-duration government debt and high-liquidity credit.\n\nLiquid stablecoin rewards. Rewards earned on liquid stablecoin holdings, depending on the asset and where it is held.\n\nThe central purpose of diversifying the backing portfolio is to diversify protocol revenue and risk. A model concentrated in a single strategy ties overall risk to a single set of market dynamics; spreading exposure across funding, lending, real-world assets, and stablecoin rewards reduces the likelihood of stress to the Ethena system resulting from revenue compression across all sources at the same time.\nEach stream responds to different drivers, so weakness in one can be offset by strength in others, producing a revenue base and risk profile designed to be more resilient across market cycles.\nPeriods of negative protocol revenue are designed to be borne by the Reserve Fund. See the Reserve Fund section below.\n\nLast updated 2 months ago\nWas this helpful?","tokens":467,"crawled_at":1791195025734}
+{"id":10468,"url":"https://gov.uniswap.org/t/extension-of-uniswap-incentive-campaign-infrastructure-univ3-univ4-merkle-router-oracles/26048","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Extension of Uniswap Incentive Campaign Infrastructure (UniV3 + UniV4 Merkle Router Oracles) - Requests for Comment - Uniswap Governance","text":"Extension of Uniswap Incentive Campaign Infrastructure (UniV3 + UniV4 Merkle Router Oracles)\n\nRequests for Comment\n\nGauntlet\n\nMarch 3, 2026, 12:51pm\n\n1\n\nSummary\n\nWith reference to the Unichain and Uniswap v4 Liquidity Incentive Proposal passed last year, this proposal requests approval to extend the infrastructure that powers the current Uniswap liquidity incentive programs.\n\nThe middleware contracts used to route and deploy incentives (Merkle Router Oracle contracts for UniV3 and UniV4) were originally deployed with a fixed end date of March 10, 2026, as the initial proposal was structured for a 12-month program.\n\nBecause these contracts have an immutable expiration timestamp, they cannot be extended. To continue running incentive campaigns beyond March 10, 2026, new versions of these middleware contracts have been deployed with a new expiration date of March 10, 2030.\n\nThis proposal requests governance approval to:\n\nRemove the expiring middleware contracts\n\nRegister the newly deployed contracts\n\nEnable campaign creation through the new contracts\n\nNo other components of the system are being modified.\n\nWhat Is Changing (and What Is Not)\n\nWhat is changing:\n\nThe Merkle Router Oracle contracts used to route incentive campaigns will be replaced with newly deployed versions.\n\nIncentive routing will move from the old contracts to the new ones.\n\nWhat is NOT changing:\n\nThe Aera vault remains the same.\n\nThe final incentive distribution contracts remain the same.\n\nIncentive budgets, token parameters, and governance structure, including DUNI’s ability to withdraw UNI from the Aera vault, remain unchanged.\n\nNo new permissions are introduced.\n\nThis is a backend infrastructure update required due to the fixed expiration of the original middleware contracts.\n\nWhy Governance Approval Is Required\n\nThe contracts being replaced are owned by the Uniswap timelock.\n\nBecause of this, updating them requires an on-chain governance proposal.\n\nThere is no way to modify the expiration date of the existing contracts. The only path forward is:\n\nDeploy new middleware contracts with a later expiration date.\n\nHave governance formally register them.\n\nTransition campaign routing to the new contracts.\n\nWithout this approval, once the current contracts expire on March 10, 2026, it will no longer be possible to create new incentive campaigns.\n\nNext Steps\n\nThe proposal will follow the standard Uniswap governance process.\n\nThe proposed process is:\n\nCollect feedback from the community on this forum post.\n\nSubmit a Snapshot vote to signal community approval for registering the new middleware contracts.\n\nIf the Snapshot vote passes, submit the corresponding on-chain governance proposal to execute the contract updates via the Uniswap timelock.\n\nBecause the existing middleware contracts expire on March 10, 2026 , and the governance process requires time to complete, there may be a brief period where new incentive campaigns cannot be created while the proposal progresses through Snapshot and the on-chain vote.\n\n1 Like\n\nAbdullahUmar\n\nMarch 9, 2026, 10:54pm\n\n2\n\nThanks for the proposal.\n\nFrom what I can tell, the technical one-year restriction with this UNI was meant to purposefully limit the duration of these incentives. Totally respect that the full allotment of incentives wasn’t used up entirely, which indicates cognizance around unfavorable market conditions, etc.\n\nHowever, further justification around this extension is warranted since the initial proposal indicated:\n\nIt would also be helpful to understand how much is left to be allocated from the Aera vault—either for Unichain, v4, or both. Presumably, $32M total has been allocated according to this post. Since UNI fluctuated a lot over the past year, my hunch is that the dollar amount is at a surplus from the initial request of ~$45M. Would be helpful to see more data on this.\n\nGiven that, what’s the new disbursement timeline since the proposed expiration date is 2030? Does this prolonged duration mean there will be an ask for more incentives soon?\n\nAnd who is the intended manager of these remaining incentives? Is optimization/decision-making conducted by Gauntlet, UF, or Labs?\n\nIf the rationale for utilizing the remaining incentives aligns with further v4 growth, especially with hooks or in observing v3 to v4 liquidity migration, continuation may make sense. But it’s much harder to justify Unichain incentives without a more clear strategy.\n\n1 Like\n\nkfx\n\nMarch 10, 2026, 8:26am\n\n3\n\nI will be voting against this proposal.\n\nIn plain language, what is being requested is for the DAO to allow Gauntlet to spend ~$10M with no publicly defined objectives, no clear deadline, and effectively no DAO oversight.\n\nI had abstained from commenting earlier, hoping that Gauntlet would provide more details — know they have been asked privately — but the proposal has now reached the Snapshot voting stage.\n\nFirst, the proposal is written in a disingenuous way, framing the change as a purely technical extension. In reality, approving it would allow incentive campaigns to continue beyond the original timeline and objectives.\n\nSecond, judging from the original proposal, the incentive campaign only had clearly stated goals for the first six months. The 12-month limit already extends beyond that. Time limits exist for a good reason. It may be prudent that the incentives were not spent in full! But that does not give Gauntlet a mandate to run them indefinitely.\n\nThe DAO should have a meaningful say in how these incentives are used. Historical performance of Gauntlet’s campaigns (not limited to Uniswap) should be considered as part of that discussion.\n\nThere are currently 2,662,156 UNI tokens in the Aera vault, which is more than $10M at current UNI prices. The proposal notes that “Uniswap Governance maintains the ability to claw back the remaining allocated funds.”\n\nManugotsuka\n\nMarch 10, 2026, 6:02pm\n\n4\n\nThe following reflects the views of L2BEAT’s governance team, composed of @kaereste and @Manugotsuka, and is based on our combined research, fact-checking, and discussion.\n\nFirst of all, we would like to thank Gauntlet for bringing this proposal forward and for their continued work supporting the Uniswap ecosystem.\n\nIt would be helpful to hear the Uniswap Foundation’s (@devinwalsh) perspective as the original program proposer to better understand whether this extension still aligns with the strategic goals that originally motivated these incentives.\n\nAt the moment, our main concern is that the extension of the incentive infrastructure is being proposed without sufficient clarity on the outcomes and lessons learned from the original program. Before supporting an extension, it would be helpful to better understand the performance of the incentives already distributed.\n\nWe would also appreciate more context around the remaining funds in the Aera Vault, the intended strategy for their use, and who will ultimately be responsible for managing these incentives.\n\nFor now, we are leaning against this proposal, but with additional clarity on these points, we are open to revisiting our position.\n\neek637\n\nMarch 10, 2026, 10:41pm\n\n5\n\nHi all - an update and additional context here:\n\nOver the last several months, incentive spending through this vault has been deliberately small. The Foundation has been making pool and budget recommendations since late last summer, with Gauntlet handling review and execution - a shift we previewed with the Foundation Feedback Group in September 2025. In practice, that’s meant running targeted experiments to win specific markets on v4 across specific chains, not broad-based campaigns.\n\nAfter discussing it with the Gauntlet team, we think the better move is to hold off on extending this program. Instead, we’d suggest future incentive campaigns come through as separate proposals - each tightly scoped to a specific opportunity with its own budget and goals, informed by what we’ve learned from these smaller experiments. We appreciate Gauntlet’s ongoing support throughout this program.\n\nWith that in mind, we’d recommend governance not move forward with this proposal. We’ve been in contact with Gauntlet and they’ll be cancelling the Snapshot.\n\n4 Likes\n\nAxia\n\nMarch 11, 2026, 2:32am\n\n6\n\nAppreciate the additional context. Will the remaining funds in the Aera vault be returned to the DAO’s treasury?\n\nSEEDGov\n\nMarch 11, 2026, 1:59pm\n\n7\n\nIf there are remaining assets previously allocated to incentives that were not used, we believe they should not be indirectly renewed by extending the contracts, as flagged by @kfx, but rather through a new proposal with clear scope, report on the intended impact and KPIs that allows the community to evaluate the impact of past incentives and decide whether a renewal is justified, as @eek637 just stated. In the meantime, we understand that the funds must be returned by @gauntlet to the DAO treasury.\n\nWe also agree with those who noted that a 4-year extension is excessive. Annual timelines exist to allow oversight and impact measurement; removing them would grant excessive discretion and reduce the DAO’s ability to supervise the use of its funds.\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[Governance Proposal] Uniswap Unleashed: Unichain and Uniswap v4 Liquidity Incentives\n\nRequests for Comment\n\n44\n\n10632\n\nApril 22, 2025\n\nUniswap Council (UC): Season 4 Report\n\nGovernance-Meta\n\n0\n\n345\n\nMarch 25, 2026\n\nTané Delegate Platform\n\nDelegation Pitch\n\n59\n\n2404\n\nMarch 9, 2026\n\nIgnas Delegate Platform\n\nDelegation Pitch\n\n41\n\n1284\n\nMay 25, 2026\n\n404 DAO Delegate Platform\n\nDelegation Pitch\n\n39\n\n3283\n\nJanuary 13, 2026","tokens":2403,"crawled_at":1791195035336}
+{"id":10469,"url":"https://docs.sui.io/getting-started/onboarding/get-address","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Create a Sui Address | Sui Documentation","text":"An addressAddressA unique, anonymous identity on a blockchain network. is a unique, anonymous identity on a blockchain network. On Sui, an address specifically represents a location onchain that can:\n\nHold and send tokens\n\nOwn objects like NFTs and Move packagesPackageSmart contracts on Sui.\n\nSubmit transactions and interact with smart contracts\n\nYou do not need to provide any personally identifying information to create an address. A single individual can create and own multiple addresses.\n\nEvery Sui address is a unique 32-byte identifier and appears in hexadecimal encoding with a 0x prefix, unless you refer to it by an alias. For example:\n\n0x02a212de6a9dfa3a69e22387acfbafbb1a9e591bd9d636e7895dcfc8de05f331\n\nA cryptographic hash function generates a public key from which every address derives. Each public key has a corresponding private key that accesses the address and the objects that it owns. An address and its associated key pair together is an account.\n\nLearn more about how a Sui address is derived and other cryptography related topics.\n\nObtain a Sui address​\n\ncaution\nIf you already have an address or created a new address in Configure a Sui Client, you can skip to Get SUI from Faucet to continue the onboarding steps.\n\nPrerequisites\n\nDownload and install Sui.\n\nConfigure your Sui client.\n\nBy default, when the Sui client runs for the first time, it prompts you to configure the client. This initial configuration generates a new Sui address, its key pair, and its associated secret recovery phrase.\n\nTo create a new Sui address outside of the initial client configuration, run:\n\n$ sui client new-address ed25519\n\nThis command specifies the key pair scheme to be of type ed25519.\n\nThe options are:\n\ned25519: Small key size and compact signatures.\n\nsecp256k1: Provides security through generating and verifying keys using ECDSA.\n\nsecp256r1: Uses randomly generated curves to generate keys.\n\nThe client will return your new addressAddressA unique, anonymous identity on a blockchain network. and 12-word recovery phrase:\n\nGenerated new key pair for address with scheme \"ed25519\" [0xb9c83a8b40d3263c9ba40d551514fbac1f8c12e98a4005a0dac072d3549c2442]\nSecret Recovery Phrase : [cap wheat many line human lazy few solid bored proud speed grocery]\n\nRecovery phrases​\n\nEvery Sui address has a recovery phrase. Recovery phrases are a series of 12 randomly generated words that you use to recover the address if you lose access to the address's key pair.\n\ndanger\nSui displays recovery phrases only once. The system does not store them anywhere automatically, and you cannot retrieve them if you do not save them yourself.\nStore recovery phrases securely and do not share them with anyone, as they provide access to any objects and tokens that an address owns.\n\nTo recover an address using the recovery phrase, use the command:\n\n$ sui keytool import '<RECOVERY_PHRASE>' <KEY_SCHEME>\n\nReplace '<RECOVERY_PHRASE>' with your 12-word recovery phrase. The entire recovery phrase must be enclosed in single quotation marks '. You must enter the words in the correct order.\n\nReplace <KEY_SCHEME> with the type of encryption used to originally create the address, such as ed25519.\n\nIf successful, the CLI restores your address and prints it in the CLI output.\n\nsui.keystore​\n\nSui stores a private key for every address in either the ~/.sui/sui_config/sui.keystore or %USERPROFILE/.sui/sui_config/sui.keystore file on macOS/Linux or Windows systems, respectively.\n\nThis file contains content similar to the following:\n\n[\n\"AK6q1/Yzz5qmTfHGLot4wkbRP5lP5NUQVDlf3FggLrKZ\",\n\"ADAWAFS+J9KcDjFmAiVI/e9ZluG0id9AnI6a7Bk5tH+G\",\n\"AJ42rQfCrPIfrQvzCgeHVDCcQZ4R1qAzKtob61VTw5k5\",\n\"AHoKrY7DDnUOq2RgP7gXLPa86bFfzqEMvmOs7TmHtST+\"\n]\n\nWhen you create a new address on your system, a new line is added to this file that consists of the address's private key. Make sure you do not expose this to anyone, as they can use it to get access to your account.\n\ndanger\nThe sui.keystore file is not the same as your machine's local keystore that contains passwords for websites, biometric data like fingerprints, or other authentication credentials. Your machine's local keystore cannot sign and submit transactions on Sui. Only addresses with their associated keys included in the sui.keystore file can sign and submit transactions.\n\nAddress aliases​\n\nAn alias is a human-readable name that you can use in place of a Sui address's full 32-byte hexadecimal string. You can use aliases anywhere you would use an address to make referencing the address easier in scripts and CLI commands.\n\nWhen you create an address, Sui assigns a random alias by default. You can view an address's current alias with the command:\n\n$ sui client addresses\n\nThe output includes the address, its alias, and an indication of which address is active if there are multiple local addresses available:\n\n╭───────────────────────┬────────────────────────────────────────────────────────────────────┬────────────────╮\n│ alias │ address │ active address │\n├───────────────────────┼────────────────────────────────────────────────────────────────────┼────────────────┤\n│ vigorous-spinel │ 0x6ebb36a3c1ab2124c082d93f60f518f70494b82d8d13c5aabb3abad6ec8cd82d │ * │\n╰───────────────────────┴────────────────────────────────────────────────────────────────────┴────────────────╯\n\nThen, to update the alias to something else, use the command:\n\n$ sui keytool update-alias <OLD-ALIAS> <NEW-ALIAS>\n\nYou can now use the alias in place of the address in commands, such as:\n\n$ sui client objects <NEW-ALIAS>\n\nView all local Sui addresses​\n\nThe active address is the address that the Sui client is currently using. This address owns any objects you create and transactions you submit, unless you specify otherwise with the --address flag in a command.\n\nTo view the current active address, use the command:\n\n$ sui client active-address\n\nTo view all addresses on your local machine, run:\n\n$ sui keytool list\n\nThis returns all addresses, along with their alias, public key, key scheme, and peer ID.\n\n╭────────────────────────────────────────────────────────────────────────────────────────────╮\n│ ╭─────────────────┬──────────────────────────────────────────────────────────────────────╮ │\n│ │ alias │ vigorous-spinel │ │\n│ │ suiAddress │ 0x6ebb36a3c1ab2124c082d93f60f518f70494b82d8d13c5aabb3abad6ec8cd82d │ │\n│ │ publicBase64Key │ AKDCajKN877Uc7o8NP2cQVJkSewhq1ZbWgw5LgpWVqbj │ │\n│ │ keyScheme │ ed25519 │ │\n│ │ flag │ 0 │ │\n│ │ peerId │ a0c26a328df3bed473ba3c34fd9c41526449ec21ab565b5a0c392e0a5656a6e3 │ │\n│ ╰─────────────────┴──────────────────────────────────────────────────────────────────────╯ │\n╰────────────────────────────────────────────────────────────────────────────────────────────╯\n\nFor more information about the keytool command, see the Sui Keytool CLI documentation.\n\nChange the active address​\n\nIf you want to switch to another address, first confirm which address is the active address and which addresses are available for you to switch to:\n\n$ sui client addresses\n\nThen, to switch to another address, use the command:\n\n$ sui client switch --address <ADDRESS>\n\nQuery information about an address​\n\nYou can use a Sui network explorer to find more information about an address, its token balances, and the objects it owns. Popular Sui explorers include:\n\nSuiVision\n\nSuiScan\n\ndanger\nData displayed on an explorer differs depending on which network you created your address on. If you've followed the Configure a Sui Client page previously, you are most likely using TestnetTestnetStaging network for testing changes before production deployment.. Be sure to select Testnet on the Sui explorer or use the dedicated URL, such as https://testnet.suivision.xyz/.\n\nFrom the CLI, you can view all objects an address owns with the command:\n\n$ sui client objects <ADDRESS>\n\nIf you do not provide an address, this command returns all objects owned by the active address.\n\nNext steps\n\nGet SUI from Faucet\n\nObtain SUI from a faucetFaucetA service that provides free Testnet tokens. to deploy packages on Testnet.\n\nHello, World!\n\nClone and build the \"Hello, World!\" project.\n\nObtain a Sui addressRecovery phrases\n\nsui.keystore\nAddress aliases\nView all local Sui addressesChange the active address\n\nQuery information about an address\n\nWas this page helpful?","tokens":2073,"crawled_at":1791195043994}
+{"id":10470,"url":"https://a16zcrypto.com/posts/article/hiring-in-web3-in-volatile-times","domain":"a16zcrypto.com","chapter":"research","title":"Hiring in web3: Principles for finding talent in volatile times","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nHiring in web3: Principles for finding talent in volatile times\nIan Dutra and Mehdi Hasan\n05.01.23\n\nTags & Share Tags\ncompany building\nhiring & recruiting\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nCrypto markets can be volatile – but crypto innovation follows an underlying order. Builders brought in when prices were high have stuck around, resulting in a steady flow of new ideas, code, and projects. A new generation of web3 startups is working on the next wave of advances, and many are actively hiring.\n\nMeanwhile, the tech talent landscape has shifted dramatically in recent months. Layoffs across all sectors, but especially in larger tech companies, have left hundreds of thousands of workers looking for new challenges and opportunities. And, as a result, web3 startups with cash on hand and an optimistic outlook are seeing a very different talent pool than they were a year ago. But how can companies set themselves up to make smart, well-timed hires in periods of volatility? No matter the season, hiring the right people at the right time is critical to growing a resilient team.\n\nIn this post, we go over a few principles and best practices for navigating this new talent landscape as a web3 startup. As former leaders at high-growth web2 and web3 organizations, we have seen a wide variety of scale, talent needs, and market fluctuations. So here are our thoughts on how teams can make the most of their headcount (and budget) as they transform the proverbial hiring abyss into a functional and efficient hiring funnel.\n\nDo the work up front\n\nHiring fast takes foresight. Without some thorough planning, it can take longer to fill a role that a team already (maybe even desperately) needs. A few principles for getting started:\n\nBe realistic about hiring needs. A full-time hire isn’t necessarily a cure-all, especially when teams aren’t sprinting through a bull run. Teams may want to consider starting with agencies, freelancers, or other contingent workers in order to be able to scale up and down as budget and workload ebbs and flows.\n\nWork backwards from business needs to define the role. If it isn’t clear whether to hire a senior individual contributor and a senior director, then take a moment to unpack the company’s needs. Some questions to ask: What will the person in this role do in their first week? What will they do in six months, or a year? And will they need to build a team? Or build out the nuts and bolts of their discipline?\n\nDefine responsibilities and map them to skill sets. Can one person do it all, or does the team need to make multiple hires? For example, a token economist (or mechanism designer) may have the analytical and economic acumen to create a token program but you may want to consider hiring a software engineer to deploy and maintain these models in production.\n\nAvoid over-hiring by staying focused on immediate needs, now and in the near future. Members of smaller teams often end up doing more than what’s outlined in their job descriptions – trends, technologies, and market conditions can move fast in web3. Focus can help organizations stay nimble and goal-oriented, while identifying obvious skill gaps and opportunities for growth.\n\nConsult an expert on unfamiliar skills. Small companies must make a lot of “first” hires – particularly in newer, more niche web3 roles that didn’t exist a few years ago. Hiring managers seeking out skill sets that they don’t have (whether that’s writing Solidity or managing NFT communities) might opt to find an external advisor.\n\nReconsider “web3 native” as a required skill. Many hiring managers are asking candidates to come in with web3 experience, a qualification that can limit teams to a select cohort of candidates (a small enough pool that challenges many companies, despite recent layoffs). Worst case, teams may be seeking people with a combination of skills that don’t actually exist. Instead, consider which roles are appropriate for deeply experienced web2 professionals, or enthusiastic new talent looking for challenging, career-defining experiences.\n\nThese are just a few best practices, but there are, of course, many more to keep in mind before you post that job description. It’s also okay if pieces of this process aren’t quite working — hiring managers should always debrief and make adjustments as they go.\n\nQuality, not quantity\n\nA year ago, many companies (in web3 and beyond) were breathlessly filling seats to keep pace with market pressures. Now the same companies are reducing headcount, or slowing their hiring. Teams looking to fill key roles might need to make some hard choices, and prioritize their hiring plans accordingly. When there are fewer roles to fill, hiring the right person is even more important.\n\nAt the same time, the talent pool has deepened, and excellent candidates that weren’t available last year may be interested in exploring new roles, opportunities, and risks. But despite the influx of talent, a good principle to keep in mind isn’t just finding the best of the best – but also finding people who are in it for the long run. If someone is willing to join a project in rockier times, they will stick around in good times, too.\n\nConnecting over closing\n\nAs recruiters, we sometimes like to think of ourselves as sales people (and we can be!) – so it’s easy to slip into the habit of treating the time between receiving and signing an offer like a hard sell. This mindset falls short when it focuses more on rattling off selling points of a company, and less on identifying a person’s unique needs, wants, and expectations. (Also: talent is a long game. You want to keep people, not just companies, centered because over time as your relationships deepen with the talent pool they will change jobs multiple times.)\n\nClosing actually starts from that first phone call, and lasts throughout the interview process by learning about a candidate. This is especially important in more volatile times as a focus on quality of connection will help close candidates faster (read: less time spent hiring) and result in less churn and attrition after employees join (read: less time spent backfilling). When big market shifts happen, you may even have to “re-close” a candidate, giving them a call to help them tease apart perception of media headlines from reality.\n\nClosing should focus on two areas in particular:\n\nProfessional fulfillment: What makes a candidate passionate? And what problems are they trying to solve? With so many smart, idea-driven candidates in web3, there’s plenty to talk about.\n\nWork-life balance: Every company likes to pitch stellar work-life balance to potential hires; but in reality, startups can come with longer hours, greater uncertainty, and a slew of tasks that fall outside of a candidate’s job description. How do candidates rank work-life balance among other benefits? And what can your company realistically deliver?\n\nAnd also include a few key considerations that are even more important in more volatile times:\n\nRisk appetite: Is the candidate bought into the space and opportunity? This will matter more than usual to ensure there aren’t too many distractions in the new hire’s journey. Take the time to connect them to the role: Why them? Why here? Why now?\n\nExperience with ups and downs: Has the candidate experienced a volatile market before? A candidate with less experience may need to hear how a company deals with market cycles: How do you do more with less, and focus on the work vs. external noise?\n\nBase pay vs. equity: Make sure candidates understand the nuances to their compensation packages. Candidates may rightfully scrutinize packages that include tokens or equity, which can shift with the market. How can you provide information and mental models that help the candidate apply these to different outcomes?\n\nThere are many ways to build trust throughout the interview process, and make the best possible impression on potential hires (get to know them, stay transparent about the hiring process, regularly communicate updates and expectations, and more). These insights can also paint a picture of why this role at this company at this time is the best fit. Not every offer will work out, but the right candidates will.\n\nFocus on the future state\n\nSpeaking generally, the earlier a company is in its journey, the more work there is to do to help candidates “see the future,” especially if a candidate is more easily swayed by brand recognition. What is the company looking to accomplish? How does this hire fit into that vision? In an industry where change and innovation move quickly, it’s key that leaders keep their candidates (and employees) focused on the problem they are solving.\n\nA prospective hire should be invested in the work a team is looking to do; they should also understand what success looks like, and what path the company is taking to be successful. Building in web3, for example, is dynamic and ever-changing — this can lead to a longer time focused on solving hard problems and being able to pivot quickly as the market evolves.\n\nOften (and especially in web3) this may require taking a step back and explaining a broader world view or ecosystem. Set the stage, and then dive into what matters: What needs to happen for there to be a successful exit here? Maybe a candidate would trade liquid compensation for more long-term incentives like equity. What does this growth story look like?\n\nTo truly paint this picture, meet candidates where they are. Do they truly grasp the mission of web3 and understand where this company fits in? Consider trying a mental model for mapping the company’s growth to their personal growth (how can their role grow with the company, long term).\n\n***\n\nAlthough every company, candidate, and hiring journey is unique, focusing on building a consistent process and hiring the right candidates will prevent churn in a time when teams need stability and precision the most. Being diligent when hiring is slow can be like building a muscle: The more teams practice, the stronger they’ll be when hiring speeds back up.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nCharts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":3213,"crawled_at":1791195047318}
+{"id":10471,"url":"https://gov.uniswap.org/t/uniswap-governance-community-calls/24530","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Uniswap Governance Community Calls - Governance-Meta - Uniswap Governance","text":"Uniswap Governance Community Calls\n\nGovernance-Meta\n\nAbdullahUmar\n\nSeptember 6, 2024, 11:48pm\n\n1\n\n1032×410 60.1 KB\n\nThe Uniswap DAO has seen a large influx of delegates and community participants over the past couple of months. DAO-led programs have also increased in quantity. Unfortunately, many of these proposals and conversations can get lost in the swath of forum posts, making it difficult to keep track of what’s important and timely. It also takes some time for new entrants to become familiar with the DAO’s existing initiatives. To increase clarity around monthly DAO occurrences, we are resuming governance community calls, now led by the Uniswap Accountability Committee (UAC).\n\nThese calls will be hosted using Google Meets on the second Tuesday of every month, from 10am – 11am Eastern Time. You may refer to this calendar to keep track of meeting dates and links.\n\nNote that these community calls are hosted by the DAO and are separate from the Uniswap Foundation’s calls.\n\nThis forum thread will provide updates and reminders regarding the monthly calls. We will be recording each of the meetings and tracking the attendance for delegates that are a part of the delegate reward program.\n\nIf you are ever interested in covering a particular proposal or discussion point regarding Uniswap governance in general, please feel free to reach out. Our team will collect a list of relevant topics for each call and contact authors of currently active proposals to ensure that they have a chance to directly interact with the community and fairly present their thoughts. The format of these calls will be a combination of quick, successive presentations from a couple of community members, followed by a live Q&A/discussion.\n\n16 Likes\n\nUniswap Treasury Working Group (UTWG) Interim Update\n\nAbdullahUmar\n\nSeptember 7, 2024, 12:10am\n\n2\n\nThe first meeting will take place on Tuesday, September 10, from 10:00 AM to 11:00 AM ET.\n\nIf you are a part of the of cycle 2 of delegate rewards, we are giving teams a “free” absence due to the short notice for this call. We still encourage all teams to attend and engage with other delegates.\n\nMost individuals with active discussions and proposals have already been contacted. If you have a topic that you feel is important to discuss, please send us a message.\n\nProspective itinerary:\n\nUAC Renewal and Accounts Rebalancing\n\nUpdate on New Incentive Distributions\n\nBase 2, 3, 4 bps fee-tiers (onchain vote)\n\nUTWG Status Update\n\nConclusion of Uniswap-Arbitrum LTIPP\n\nOpen Discussion: Experimentation with Temperature Checks\n\n11 Likes\n\nL2BEAT Delegate Platform\n\nAbdullahUmar\n\nSeptember 12, 2024, 6:26pm\n\n3\n\nIf you missed this week’s governance call, you may view the recording here.\n\nAnd the presentation can be seen here.\n\nFor those who attended, you participation has also been logged. Note that this meeting is exempt from delegate reward points. Starting from the next call, we will be counting attendance.\n\n10 Likes\n\nAbdullahUmar\n\nOctober 4, 2024, 7:22pm\n\n4\n\nThe next community call will take place on Tuesday, October 8, from 10:00 AM to 11:00 AM ET.\n\nIf you are a part of the of cycle 2 of delegate rewards, we will be tracking attendance and counting it towards your monthly rewards.\n\nIf you have a topic that you feel is important to discuss, please send us a message.\n\nTo keep track of meetings, check this calendar.\n\nProspective itinerary:\n\nIntroduction to the updated UAC team\n\nUniswap Arbitrum Grant Program (UAGP) Update\n\nFund for Delegate Legal Fees\n\nUpdate on Forse proposal\n\nDelegating UNI from the Treasury\n\nQuorum and Governance Attacks Discussion\n\nUniswap Treasury Working Group (UTWG) Stability Fund Update\n\nOnboarding Lisk and World Chain\n\n6 Likes\n\njengajojo\n\nOctober 7, 2024, 11:30am\n\n5\n\nThanks for the updates @AbdullahUmar Any chance that this or the future calls can be moved an hour later?\n\nAbdullahUmar\n\nOctober 7, 2024, 5:00pm\n\n6\n\nWe can bring this up tomorrow and see if delegates want alternating meeting times. There’s no perfect time, unfortunately. Like moving it up an hour makes it tougher for Asia-based delegates. Let’s see.\n\n2 Likes\n\nDoo_StableLab\n\nOctober 11, 2024, 4:33pm\n\n7\n\nIt is indeed tricky. For some DAOs, they had a system where delegates can write their comments after watching the recording for those can’t make it. They had to make comments within 3-7 days of recording being shared.\n\nAbdullahUmar\n\nOctober 17, 2024, 5:02am\n\n8\n\nIf you missed the October governance call, you can view the recording here.\n\nAnd the presentation can be seen here.\n\nDelegates that are a part of the current rewards initiative were asked to complete a Google Form to track attendance. Responses have been recorded and will be reflected in this month’s compensation.\n\nSince delegates have requested a survey regarding governance call timing, below are a handful of options for future calls. Meetings will still be held on the second Tuesday of each month to prevent more coordination complications. Feel free to select as many openings as you’d like.\n\n10am - 11am ET (current timing)\n\n11am - 12pm ET\n\n3pm - 4pm ET\n\n4pm - 5pm ET\n\n7pm - 8pm ET\n\n8pm - 9pm ET\n\n0\nvoters\n\n1 Like\n\nAbdullahUmar\n\nOctober 30, 2024, 2:33am\n\n9\n\nUpcoming Calls Update\n\nDue to its proximity to Uniday at DevCon, the November Community Call will be canceled.\n\nWe will resume the regular call schedule during the following month, which will take place on December 10th.\n\nAs per the above survey, we will not be changing the time for these calls—they will continue to be held on the second Tuesday of each month between 10am - 11am ET, unless stated otherwise.\n\n5 Likes\n\nAbdullahUmar\n\nDecember 6, 2024, 8:58pm\n\n10\n\nThe next community call will take place on Tuesday, December 10, from 10:00 AM to 11:00 AM ET.\n\nIf you are a part of the of cycle 2 of delegate rewards, we will be tracking attendance and counting it towards your monthly rewards.\n\nTo keep track of meetings, check this calendar.\n\nProspective itinerary:\n\nUniswap Accountability Committee Chains & Accounting Update\n\nCelo Deployment Proposal\n\nUniswap Ecosystem Incentives Initiative (UEII) Optimism Grant\n\nGauntlet’s LTIPP Evaluation for Arbitrum Incentives\n\nSEAL Safe Harbor Agreement\n\nUTWG Report Update\n\nUniswap DAO Principles Update\n\nA couple of topics are still pending but may be pushed to January. If you have a topic that you feel is important to discuss, please send us a message.\n\n2 Likes\n\nL2BEAT Delegate Platform\n\ndennisonb\n\nDecember 6, 2024, 10:33pm\n\n11\n\nQuick question- are we allowed to record the calls ourselves? Could we bring our own Otter.AI?\n\nAbdullahUmar\n\nDecember 6, 2024, 10:57pm\n\n12\n\nYeah, I don’t see why not. We’ll also be using a tool to take notes automatically, so if the community wants those, we can post them. Not sure if multiple AIs creates an issue.\n\nAbdullahUmar\n\nDecember 10, 2024, 6:40pm\n\n13\n\nYou can view the December community call here.\n\nAnd the presentation is accessible here.\n\nIf you are a part of the delegate incentives program and were on the call but missed the QR code, please dm me.\n\n2 Likes\n\nAbdullahUmar\n\nJanuary 13, 2025, 6:14pm\n\n14\n\nThe next community call will take place on tomorrow, Jan 14, from 10:00 AM to 11:00 AM ET.\n\nIf you are a part of the of cycle 2 of delegate rewards, we will be tracking attendance and counting it towards your monthly rewards.\n\nTo keep track of meetings, check this calendar.\n\nProspective itinerary:\n\nUniswap Accountability Committee Update\n\nUniswap Ecosystem Incentives Initiative (UEII) Optimism and zkSync Ignite Status\n\nGauntlet’s LTIPP Evaluation for Arbitrum Incentives\n\nUF Security Fund (Areta)\n\nReservoir + Protofire Update\n\nDeepDAO Pro Proposal\n\nTally Update\n\nUniswap Growth Update (AlphaGrowth)\n\nUniswap Tendering System Idea (SeedGov)\n\nAbdullahUmar\n\nJanuary 23, 2025, 2:26am\n\n15\n\nYou can view the January community call here.\n\nThe presentation is available here.\n\n2 Likes\n\ndrllau_LexDAO\n\nJanuary 23, 2025, 4:12am\n\n16\n\nmore followup and in-depth discussion of the procurement proposal by @SEEDGov (slide pg13)\n\nimage594×158 15 KB\n\nAbdullahUmar\n\nFebruary 10, 2025, 7:16pm\n\n17\n\nThe next community call will take place tomorrow, Feb 11, from 10:00 AM to 11:00 AM ET.\n\nIf you are a part of the of cycle 2 of delegate rewards, we will be tracking attendance and counting it towards your monthly rewards.\n\nTo keep track of meetings, check this calendar.\n\nUpdates for the following are planned:\n\nUniswap Accountability Committee (UAC)\n\nUniswap Ecosystem Incentives Initiative (UEII)\n\nUniswap Growth Program\n\nForse Analytics\n\nDelegate Rewards Cycle 3\n\n2 Likes\n\nAbdullahUmar\n\nMarch 4, 2025, 1:39am\n\n18\n\nYou may view the February 2025 community call here.\n\nThe slides are available here.\n\nAbdullahUmar\n\nMarch 10, 2025, 10:38pm\n\n19\n\nBelow is the agenda for tomorrow’s community call:\n\nUAC General Updates\n\nUniswap Unleashed Update (UF proposal)\n\nUniswap Ecosystem Incentives Initiative (UEII) Updates\n\nUniswap Growth Program\n\nSaga Incentive Proposal\n\nMetrom Incentive Distribution Introduction\n\nForse Update\n\nDelegate Rewards Cycle 3 Results\n\nTreasury Delegation RFC\n\nTo keep track of meetings, check this calendar.\n\nAbdullahUmar\n\nMarch 17, 2025, 8:52pm\n\n21\n\nHere is the March community call recording.\n\nThe presentation slides are accessible here.\n\n3 Likes\n\nnext page →\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[RFC]: Uniswap Community Calls\n\nGovernance-Meta\n\n21\n\n3965\n\nApril 9, 2024\n\nAnnouncement: unofficial Community Call - Thursday 12 Nov 17:00 UTC\n\nUncategorized\n\n15\n\n9717\n\nNovember 14, 2020\n\nGovernance Weekly Recap\n\nGovernance-Meta\n\n21\n\n6566\n\nMay 26, 2023\n\n[Announcement] Community Call 2 - Tuesday 24 Nov 16:00 UTC\n\nUncategorized\n\n7\n\n3981\n\nNovember 25, 2020\n\nUniswap Accountability Committee (UAC): Season 2 Report\n\nRequests for Comment\n\n11\n\n1175\n\nSeptember 23, 2024","tokens":2443,"crawled_at":1791195053195}
+{"id":10472,"url":"https://docs.sui.io/getting-started/onboarding/configure-sui-client","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Configure a Sui Client | Sui Documentation","text":"The Sui client configuration specifies which network to connect to and which addressAddressA unique, anonymous identity on a blockchain network. to send transactions. When you run sui client for the first time, it generates a key pair, writes a client.yaml file to your local config directory, and sets TestnetTestnetStaging network for testing changes before production deployment. as the active environment. You can switch networks, add custom RPC endpoints, and manage multiple environments using the sui client new-env and sui client switch subcommands.\n\nPrerequisites\nFirst, confirm that Sui has been installed successfully:\n$ sui --version\n\nIf this command returns sui not found, then Sui is not installed and you must follow the installation instructions.\n\nsui client​\n\nRun the Sui CLI with the command:\n\n$ sui client\n\ninfo\nIf a previous Sui installation stored a client.yaml file locally, you receive the sui client --help output in the console. You can delete the existing ~/.sui/sui_config/client.yaml file if you'd like to start fresh, or you can continue using the existing configuration.\n\nThe prompt asks if you want to create the client.yaml file, select Y or press enter. You can skip the prompt with sui client -y.\n\nNo sui config found in `~/.sui/sui_config/client.yaml`, create one [Y/n]?\n\nYou see the following output:\n\nGenerated new keypair ...\nsecret recovery phrase : [recovery phrase words are here]\nCreated \"~/.sui/sui_config/client.yaml\"\nSet active environment to testnet\n\ncaution\nStore recovery phrases securely and do not share them with anyone, as they provide access to any objects and tokens that an address owns.\nThe recovery phrase is not visible again once the CLI history disappears.\nLearn more about Sui addresses, key generation, and recovery phrases.\n\nHow do I switch between Sui Testnet, DevnetDevnetFor developing and testing new features., and MainnetMainnetProduction network for live transactions and real-value assets.?​\n\nUse sui client switch to change the active network environment:\n\n$ sui client switch --env testnet\n\nTo list all configured environments and see which one is currently active, run:\n\n$ sui client envs\n\nYou see output similar to:\n\nlocalnet => http://0.0.0.0:9000 (active)\ndevnet => https://fullnode.devnet.sui.io:443\ntestnet => https://fullnode.testnet.sui.io:443\nmainnet => https://fullnode.mainnet.sui.io:443\n\nTo add a new environment, use sui client new-env. For example, to add a custom RPC endpoint:\n\n$ sui client new-env --alias custom --rpc https://your-custom-rpc-url\n\nAfter adding the environment, switch to it with sui client switch --env custom.\n\nWhat is client.yaml and how do I edit it?​\n\nYour Sui client is now configured. By default, Sui stores this information in either the ~/.sui/sui_config/client.yaml file (macOS/Linux) or %USERPROFILE%\\.sui\\sui_config\\client.yaml file (Windows). You can store a client.yaml file in a different location, if preferred, and specify its location with the --client.config flag.\n\nThe client.yaml contains the configuration for connecting to different Sui networks (Testnet, Mainnet, Devnet, and LocalnetLocalnetLocal network you can run on your own machine for optimized development.), as well as your current active environment, which tells the CLI which network to use when you don't explicitly specify one.\n\nYou can modify your configuration using the sui client subcommands. See the output of sui client --help for more information.\n\nSui stores the key for the Sui address in a separate file, ~/.sui/sui_config/sui.keystore (macOS/Linux) or %USERPROFILE/.sui/sui_config/sui.keystore (Windows). Learn more about Sui addresses in Create a Sui Address.\n\nNext steps\n\nLearn More About Sui Addresses\n\nNow that you have created a Sui address, learn about address management, key pairs, and recovery phrase best practices.\n\nGet SUI from Faucet\n\nObtain SUI from a faucetFaucetA service that provides free Testnet tokens. to deploy packagesPackageSmart contracts on Sui. on Testnet.\n\nHello, World!\n\nClone the \"Hello, World!\" project.\n\nsui client\nHow do I switch between Sui Testnet, Devnet, and Mainnet?\nWhat is client.yaml and how do I edit it?\n\nWas this page helpful?","tokens":1044,"crawled_at":1791195064234}
+{"id":10473,"url":"https://docs.ethena.fi/protocol-overview/underlying-derivatives","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Underlying Derivatives | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nContext\nEthena utilizes derivatives positions to buttress the synthetic USD value of the backing assets in most market conditions. This is achieved by being \"delta neutral\" through the use of an offsetting short derivatives position to the natural long spot position from backing assets.\nIn the subsections below, we go into what each term refers to and the key differences:\n\nFutures vs Perpetuals\n\nInverse vs Linear Contracts\n\nBasis Spread\n\nOverview\n\nEthena trades derivatives across all major centralized exchanges that are supported by \"Off-Exchange Settlement\" providers.\n\nAt a high level, Ethena trades derivatives with a few motivations:\n\nEthena opens a short position when a user mints USDe.\n\nEthena closes a short position when a user redeems USDe.\n\nEthena closes/opens positions across exchanges to realize unrealized PnL.\n\nEthena algorithmically optimizes positions in the backing portfolio to account for risk.\n\nEthena algorithmically optimizes positions in the backing portfolio to account for the differences between the exchanges' derivative contract specifications & the capital efficiency available from each exchange.\n\nIt is important to note that not all exchanges offer the same derivatives contracts and there are often key differences between each. Ethena is also sensitive to the exchange-assigned backing assets value when using liquid staking Ethereum assets, such as stETH, to margin ETHUSD or ETHUSDT Perpetual positions.\n\nLast updated 1 year ago\nWas this helpful?","tokens":396,"crawled_at":1791195064557}
+{"id":10474,"url":"https://www.getfoundry.sh/cast/abi-encoding","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"ABI encoding – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nABI encoding\n\nCast encodes and decodes data according to the Ethereum ABI specification.\n\nEncoding calldata\n\nEncode a function call\n$ cast calldata \"transfer(address,uint256)\" 0xRecipient 1000000000000000000\n\nEncode with named function\n$ cast calldata \"approve(address spender, uint256 amount)\" $SPENDER $AMOUNT\n\nEncode constructor arguments\n$ cast abi-encode \"constructor(string,uint256)\" \"MyToken\" 1000000\n\nDecoding calldata\n\nDecode with known signature\n$ cast calldata-decode \"transfer(address,uint256)\" 0xa9059cbb000000000000000000000000...\n\nDecode using 4byte database\n$ cast 4byte-decode 0x1F1F897F676d00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003e7\n\n1) \"fulfillRandomness(bytes32,uint256)\"\n0x676d000000000000000000000000000000000000000000000000000000000000\n999\n\nLook up function selector\n$ cast 4byte 0xa9059cbb\n\nABI encoding primitives\n\nEncode raw ABI data\n$ cast abi-encode \"foo(uint256,address)\" 42 0xRecipient\n\nDecode ABI data\n$ cast decode-abi --input \"foo(uint256,address)\" 0x000000000000000000000000...\n\nDecode output data\n$ cast decode-abi \"balanceOf(address)(uint256)\" 0x0000000000000000000000000000000000000000000000000de0b6b3a7640000\n\nFunction selectors\n\nCompute function selector\n$ cast sig \"transfer(address,uint256)\"\n\nGet full signature from selector\n$ cast 4byte 0xa9059cbb\n\nCompute event topic\n$ cast sig-event \"Transfer(address indexed,address indexed,uint256)\"\n\nDecoding events\n\nDecode event data\n$ cast decode-event --sig \"ValueChanged(uint256 value)\" $DATA\n\nLook up event by topic\n$ cast 4byte-event 0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef\n\nWorking with types\n\nEncode bytes\n$ cast abi-encode \"foo(bytes)\" 0xdeadbeef\n\nEncode dynamic array\n$ cast abi-encode \"foo(uint256[])\" \"[1,2,3]\"\n\nEncode tuple\n$ cast abi-encode \"foo((uint256,address))\" \"(42,0xRecipient)\"\n\nEncode nested struct with array field\n$ cast abi-encode \"foo(((uint256)[],uint256))\" \"([(1)],123)\"\n\nDecode nested struct with array field\n$ ENCODED=$(cast abi-encode \"foo(((uint256)[],uint256))\" \"([(1)],123)\")\n$ cast decode-abi --input \"foo(((uint256)[],uint256))\" \"$ENCODED\"\n\nEncode string\n$ cast abi-encode \"foo(string)\" \"Hello, World!\"\n\nType conversions\n\nParse units (e.g., ether to wei)\n$ cast to-wei 1.5 ether\n\nFormat units (e.g., wei to ether)\n$ cast from-wei 1500000000000000000\n\nConvert to hex\n$ cast to-hex 255\n\nConvert from hex\n$ cast to-dec 0xff\n\nConvert to bytes32\n$ cast to-bytes32 \"Hello\"\n\nFormat bytes32 as string\n$ cast parse-bytes32-string 0x48656c6c6f000000000000000000000000000000000000000000000000000000\n\nHashing\n\nKeccak256 hash\n$ cast keccak \"Hello, World!\"\n\nHash raw bytes\n$ cast keccak 0xdeadbeef\n\nCompute storage slot for mapping\n$ cast index address 0xOwner 0\n\nInterface utilities\n\nGenerate interface from ABI\n$ cast interface ./out/Counter.sol/Counter.json\n\nGenerate interface from Etherscan\n$ cast interface 0xContractAddress --etherscan-api-key $KEY\n\nPretty print ABI\n$ forge inspect Counter abi\n\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":778,"crawled_at":1791195072622}
+{"id":10475,"url":"https://docs.ethena.fi/protocol-overview/underlying-derivatives/futures-vs-perpetuals","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Futures vs Perpetuals | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nFutures Contract\nA Futures Contract is a derivative instrument and is an agreement to buy or sell a commodity, currency or other instrument at a predetermined price at a specified time in the future. They are either physically or cash settled.\nMargin collateral is either be denominated in underlying cryptocurrencies, allowing traders to speculate on the future value of its products using only crypto collateral, or they can be denominated in USDT/USDC.\nPerpetual Contract\nIn contrast to traditional futures, Perpetual Contracts have no expiry date and include a concept called \"Funding\". \"Funding\" incentivizes traders to keep the price of the Perpetual Contract relatively in line with the underlying asset index of which the contract is marked against.\nIf the Perpetual Contract trades at a higher price than the index, traders that have long positions need to make funding payments to the traders having short positions. This funding payment will make the product less attractive to the long-position holders and more attractive to the short-position holders. This dynamic attempts to drive the perpetual price to trade in line with the price of the index. If the Perpetual Contract trades at a price lower than the index, the short position holders will have to pay the long position holders.\nRead more about \"Funding\": Bitmex Guide, Deribit Guide\nDifferences between Futures & Perpetual Contracts\nThe core differences between Perpetual and Futures can be summarized as follows:\n\nPerpetual contracts have no expiry or settlement.\n\nThe \"Funding\" mechanism is used to tether Perpetual contracts to their underlying spot index price. This is in contrast to a Futures contract which may trade at significantly different prices to their associated index until expiry where it is settled at a rate very similar to the index price.\n\nEach Perpetual contract has its own details including:\n\nIndex Price Source Components\n\nFunding Rate Mechanism\n\nLast updated 1 year ago\nWas this helpful?","tokens":520,"crawled_at":1791195083682}
+{"id":10476,"url":"https://docs.sui.io/getting-started/sui-for-solana","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Solana -> Sui | Sui Documentation","text":"The biggest difference between Sui and Solana development lies in the programming language. Sui uses MoveMoveAn open source programming language used for all activity on Sui., while Solana relies on Rust, typically paired with a development framework that simplifies app development and management. Anchor is the most popular Solana framework.\n\nTopicRust (Solana)Move (Sui)\nModel\nAccount-based model where all data is stored in accounts. Programs declare read/write accounts upfront. Everything is an account (programs, data, wallets).\nObjectObjectThe basic unit of storage on Sui. ownership inherent to Sui, objects are first class citizens and encompass everything owned on Sui.\n\nData storage\nData is stored in programs, stateless accounts that contain instructions.\nData is stored in Move objects.\n\nInheritance\nNo inheritance. Rust uses traits for shared behavior and composition over inheritance.\nNo interfaces, no polymorphism. However, Move has generics, like Type<T>.\n\nDynamic dispatch\nAllowed through trait objects, but not commonly used in Solana programs due to performance overhead.\nNot allowed\n\nAsset and token accessibility\nTokens stored in Program Derived AddressesAddressA unique, anonymous identity on a blockchain network. (PDAs). Access controlled through program logic and signer verification.\nAnyone can access shared objects. Owned objects can only be accessed by the object owner.\n\nAccess control\nSigner-based access control. Programs verify transactionTransactionA number of commands that execute on inputs to define the result of the transaction. signers and account ownership. PDAs enable program-controlled accounts.\nMostly capability based access control through owned objects. Identity and role-based access control is possible.\n\nContract upgrades\nPrograms can be marked as upgradeable or immutable at deployment. Upgrades replace the program binary but keep the same program ID.\nNew contracts must be layout-compatible with the old one. You need to consider versioning shared objects.\n\nMutate contract state\nSending transactions with instruction data. Programs process instructions and modify account data. Can use Anchor's IDL (Interface Definition Language) for type-safe client interaction.\nSending transaction through runtime programmable transaction block (PTBProgrammable transaction blocksDefine all user transactions on Sui.) construction.\n\nType safety\nStrongly typed at compile time with Rust's type system. Memory safety enforced by borrow checker.\nResource-oriented with linear types. Assets cannot be copied or dropped unless explicitly allowed. Strong type safety with Move Prover for formal verification.\n\nObject model​\n\nIn Move, everything is an object. Objects serve as the fundamental data storage unit on Sui, containing Move packagesPackageSmart contracts on Sui. (smart contracts), addresses, coins, NFTs, and all other onchain data.\n\nYou can think of objects as assets with inherent ownership properties like NFTs, but generalized across all blockchain data. Every object has ownership.\n\nOwnership​\n\nThere are some nuances to object ownership, but key types include:\n\nAddress-owned objects: These objects are owned by a single address. You can transferTransferChanging the owner of an asset. or receive these objects without interacting with a smart contract. For example, currency, NFTs, or tokens gating access to certain functions.\n\nShared objects: Publicly accessible objects that anyone can use. Mutating the data stored in these objects typically involves defining rules in the smart contract.\n\nFor all types of ownership on Sui, see Object Ownership.\n\nAccess control​\n\nOn Solana, access control is typically signer-based: programs verify transaction signers and account ownership, and Program Derived Addresses (PDAs) enable program-controlled accounts.\n\nBecause object ownership is inherent in Sui, access to contract functions is typically gated through capability objects.\n\nYou issue these objects to users, granting them the rights to call certain functions. Function calls fail if a user does not own the object a function expects.\n\nYou can still implement address-based checks. However, the recommendation is to use capability objects as much as possible for better security.\n\nYou can read more in The Move Book.\n\nIn this example, a new user can only be created by presenting an AdminCap object during the function call.\n\n/// Grants the owner the right to create new users in the system.\npublic struct AdminCap has key { id: UID }\n\n/// Creates a new user in the system. Requires the `AdminCap` capability to be\n/// passed as the first argument.\npublic fun new(_: &AdminCap, ctx: &mut TxContext): User {\nUser { id: object::new(ctx) }\n}\n\nMutating objects​\n\nIn Rust, data structures are stored in separate account structures that programs read from and write to. Programs are stateless and declare which accounts they'll access upfront. Mutating data involves signing a transaction with the appropriate account references, and the program verifies signer permissions through explicit checks.\n\nIn Move, the logic that mutates the data is defined in the contract, but the data is stored in Move objects.\n\nTo mutate the data, the owner of the objects calls the contract functions using a PTB. The protocol checks ownership at the protocol level, so transactions fail if the signer does not have access to the referenced objects.\n\nProgrammable transaction blocks​\n\nIn Rust, if you want to chain together results of multiple program calls, you typically need to create multiple sequential transactions or use Cross-Program Invocations (CPIs) within a program. CPIs allow programs to call other programs atomically within a single transaction, but they are limited to 4 levels deep and require careful account management. Client-side transaction chaining lacks atomicity guarantees because each transaction is independent and a failure in one does not revert the others.\n\nIn Move, PTBs solve this problem. PTBs give builders the ability to chain contract calls together with atomicity guarantees during runtime. A Sui PTB can have up to 1,024 different contract calls in it, or other actions. PTBs effectively provide a limited scripting language that is straightforward yet expressive, powerful, and secure.\n\nBuilders on Sui leverage PTBs to provide experiences that would otherwise be intractable. A good example is a DeFi aggregator that routes token swaps across multiple DeFi protocols with the best price. On Sui, the aggregator would use a single PTB with the guarantee that the transaction would execute at the displayed price or it would revert completely. The PTB is one of the most powerful Sui features. Experience shows builders who are most successful on Sui are the ones who learn to leverage this feature early and often, leaning into it rather than treating it just as a way to batch transactions.\n\nSee Building Programmable Transaction Blocks for the full guide on constructing PTBs with the TypeScript SDK, including moveCall, chaining results, and gasGasThe computational cost of execution and object storage for a transaction. management.\n\nMore comparison​\n\nTopicSolanaSui\nDigital signature algorithm\nEd25519\nEd25519, secp256k1, secp256r1\n\nConsensusConsensusThe process by which the majority of nodes agree on the current state of the network mechanism\nTower BFT (PoS variant) with Proof of History (PoH)\nDPoSDPoSConsensus mechanism used by Sui.\n\nVM and its languages\nSolana VM, Rust, C, C++\nMoveVM, Move Lang\n\nChain data structure\nBlocks with PoH ordering\nDAG\n\nCommon standards (coin, token, NFT, and so on)\nSPL Token, MPL Core, Token22\nCoin Standard, Closed-Loop TokenClosed-Loop TokenA token that can be used only for a specific service or authorized account.\n\nCoin names, name of the smallest unit\nSOL, Lamport\nSUI, MISTMISTThe smallest unit of SUI.\n\nAvailable frameworks for development\nAnchor framework, Solana CLI, native Rust tooling\nSui CLI\n\nL1 and L2\nEmerging but not widespread, mostly relies on fast L1 with parallel execution\nNo L2, relies on fast L1 with horizontal scaling\n\nGovernance\nOffchain governance through SIMD (Solana Improvement Documents)\nOnchain governance\n\nBridges\nSupported\nSupported\n\nNetwork security (stake required for control)\n66% of total stake (BFT requirement)\n66% of total stake\n\nSmart contract auditing\nRequires comprehensive auditing due to account model complexity, PDA patterns, and CPI vulnerabilities\nLess auditing required, language does some of the lifting (object model)\n\nPrivate transactions\nPublic by design\nPublic by design\n\nTVL (as of late 2025)\n~10 billion\n~2.6 billion\n\nImplementation languages for clients\nRust, TypeScript (web3.js, @solana/kit), Python, Go\nRust, TypeScript, Python\n\nEventing\nIndexed by program logs, requires custom parsing or indexer\nIndexed by sender, object ID, type, timestamp\n\nIndexing\nHigh level transaction data, requires custom indexers (Helius, Triton, Shyft)\nHigh level transaction data + objects, coins, GraphQL RPCGraphQL RPCA lightweight GraphQL RPC service. support\n\nOracles\nThird party\nThird party\n\nNetwork upgrade strategy\nFeature gates voted on by validators, activated when supermajority is reached\nProtocol flags and framework upgrades voted on by validators then enabled\n\nIDE\nVSCode (Rust Analyzer)\nVSCode (Move extension)\n\nTransaction lifecycle\nTransaction submitted to RPC, gossiped to leaders, included in block, voted on by validators using Tower BFT.\nThe client submits the transaction to a full nodeFull nodeResponsible for validating blockchain activity., which forwards it to a validatorValidatorResponsible for executing tasks like staking, gas price references, and tallying rules. through Transaction Driver. Validators vote on it, consensus commits it in a block, and every validator executes it against the same ordered state. Low latency.\n\nParallel execution\nSealevel runtime enables parallel execution when transactions don't overlap in account access. Accounts must be declared upfront for scheduling.\nTransactions that can be parallel are run in parallel.\n\nStorage fees, storage rebates\nRent-exempt accounts require minimum balance. No rent collection since 2021, no rebates.\nLow storage fees paid upfront, rebates on destroying objects to incentivize cleanup.\n\nContract immutability\nPrograms can be marked as upgradeable or immutable at deployment time.\nNative mutable and immutable support using upgrade capabilities as objects.\n\nContract upgrading\nNative, programs marked as upgradeable can be upgraded by the upgrade authority.\nNative, upgrade capability mediated.\n\nComposability\nCross-Program Invocations (CPIs) allow programs to call other programs within a transaction. Limited to 4 levels deep. Atomic within transaction boundaries.\nCall any number of functions within a single transaction using PTBs. Compose by taking output of one call and passing into another. Ensures atomic execution with up to 1,024 commands per PTB.\n\nToken royalties\nNot enforced directly. Enforced through protocols like MPL Core or extensions like Token22.\nEnforced by the chain through KioskKioskA decentralized system for commerce applications on Sui. and transfer policies.\n\nBlock time and finalityFinalityThe state in which a transaction is permanently recorded and cannot be revoked.\n~400ms block time, ~12-13 seconds for economic finality (before Alpenglow upgrade).\nSub-second finality for independent transactions, ~390ms with MysticetiMysticetiThe consensus protocol used on Sui. for shared objects.\n\nRelated topics\n\nMove Concepts\nMove is an open source language for writing safe packages to manipulate onchain objects.\nUpgrading Packages\nUpgrade a published Move package on Sui using the Sui CLI, understand layout-compatibility requirements, manage UpgradeCap and UpgradeTicket, and apply custom upgrade policies to control what changes are permitted.\nWhat is a PTB?\nProgrammable transaction blocks are a group of commands that complete a transaction on Sui.\nBuilding Transactions\nUsing the Sui TypeScript SDK, you can create programmable transaction blocks to perform multiple commands in a single transaction.\n\nObject model\nOwnership\nAccess control\nMutating objects\nProgrammable transaction blocks\nMore comparison\n\nWas this page helpful?","tokens":3055,"crawled_at":1791195088605}
+{"id":10477,"url":"https://www.getfoundry.sh/config/networks","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Network configuration – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nNetwork configuration\n\nFoundry can execute against several EVM network families from the same toolchain. Network selection\ncontrols execution rules such as transaction types, hardforks, precompiles, and trace decoding. It\nis separate from choosing an RPC URL or setting the numeric chain ID.\n\nSelect a network\n\nSet network in your project when local tests and scripts should use a non-default execution\nfamily:\n\nfoundry.toml\n[profile.default]\nnetwork = \"tempo\"\n\nUse --network to select a family for one command:\n\n$ forge test --network tempo\n$ forge script script/Deploy.s.sol --network optimism\n$ anvil --network monad\n\nThe available values depend on how the binary was built. ethereum and tempo are always\navailable. optimism and monad require their matching Cargo features; official Foundry release\nbuilds currently include both. Run the command with --help to see the values supported by your\ninstalled binary.\n\nFork inference\n\nWhen you use a live fork, Foundry normally infers the execution family from a known chain ID or\nfrom metadata exposed by an Anvil endpoint:\n\n$ forge test --fork-url $RPC_URL\n$ anvil --fork-url $RPC_URL\n\nYou do not need --network for a recognized network family. Select the network explicitly when the\nendpoint uses an unknown chain ID, does not expose enough metadata, or when you intentionally need\na specific execution family. Compatibility profiles exposed through separate switches, such as\nCelo, still require their switch. The selected execution profile must be compatible with the fork\nsource.\n\nOptional metadata methods are capability probes. A standard RPC endpoint can reject an Anvil-only\nmethod and still be a valid fork source; Foundry falls back to standard chain and block methods\nuntil an endpoint identifies itself as Anvil.\n\nSee Anvil forking for block pinning, caching, headers, and fork configuration.\n\nSelect a hardfork\n\nUse hardfork when you need deterministic semantics for a particular activation. A namespaced\nhardfork also selects its network family:\n\nfoundry.toml\n[profile.default]\nhardfork = \"optimism:holocene\"\n\nfoundry.toml\n[profile.default]\nhardfork = \"tempo:T6\"\n\nFor normal current behavior, prefer network or live fork inference. Pin a hardfork for historical\ntesting, compatibility checks, or regression coverage.\n\nCelo features\n\nCelo compatibility remains a separate switch rather than a network family:\n\nfoundry.toml\n[profile.default]\ncelo = true\n\n$ anvil --fork-url https://forno.celo.org --celo\n\nLegacy settings\n\nFoundry still accepts optimism = true, tempo = true, and monad = true for compatibility when\nthe corresponding family is available. New configuration should use the canonical network field.\n\nInspect the resolved project configuration with:\n\n$ forge config --json\n\nSee the network and\nhardfork reference entries for environment variables and\nfield details. For Tempo-specific workflows, see Foundry on Tempo.\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":747,"crawled_at":1791195090663}
+{"id":10478,"url":"https://blog.trailofbits.com/2016/02/17/apple-can-comply-with-the-fbi-court-order","domain":"blog.trailofbits.com","chapter":"security_audits","title":"Apple can comply with the FBI court order - The Trail of Bits Blog","text":"Page content\n\nEarlier today, a federal judge ordered Apple to comply with the FBI’s request for technical assistance in the recovery of the San Bernadino gunmen’s iPhone 5C. Since then, many have argued whether these requests from the FBI are technically feasible given the support for strong encryption on iOS devices. Based on my initial reading of the request and my knowledge of the iOS platform, I believe all of the FBI’s requests are technically feasible.\nThe FBI’s Request\nIn a search after the shooting, the FBI discovered an iPhone belonging to one of the attackers. The iPhone is the property of the San Bernardino County Department of Public Health where the attacker worked and the FBI has permission to search it. However, the FBI has been unable, so far, to guess the passcode to unlock it. In iOS devices, nearly all important files are encrypted with a combination of the phone passcode and a hardware key embedded in the device at manufacture time. If the FBI cannot guess the phone passcode, then they cannot recover any of the messages or photos from the phone.\nThere are a number of obstacles that stand in the way of guessing the passcode to an iPhone:\niOS may completely wipe the user’s data after too many incorrect PINs entries\nPINs must be entered by hand on the physical device, one at a time\niOS introduces a delay after every incorrect PIN entry\nAs a result, the FBI has made a request for technical assistance through a court order to Apple. As one might guess, their requests target each one of the above pain points. In their request, they have asked for the following:\n[Apple] will bypass or disable the auto-erase function whether or not it has been enabled;\n[Apple] will enable the FBI to submit passcodes to the SUBJECT DEVICE for testing electronically via the physical device port, Bluetooth, Wi-Fi, or other protocol available on the SUBJECT DEVICE; and\n[Apple] will ensure that when the FBI submits passcodes to the SUBJECT DEVICE, software running on the device will not purposefully introduce any additional delay between passcode attempts beyond what is incurred by Apple hardware.\nIn plain English, the FBI wants to ensure that it can make an unlimited number of PIN guesses, that it can make them as fast as the hardware will allow, and that they won’t have to pay an intern to hunch over the phone and type PIN codes one at a time for the next 20 years — they want to guess passcodes from an external device like a laptop or other peripheral.\nAs a remedy, the FBI has asked for Apple to perform the following actions on their behalf:\n[Provide] the FBI with a signed iPhone Software file, recovery bundle, or other Software Image File (“SIF”) that can be loaded onto the SUBJECT DEVICE. The SIF will load and run from Random Access Memory (“RAM”) and will not modify the iOS on the actual phone, the user data partition or system partition on the device’s flash memory. The SIF will be coded by Apple with a unique identifier of the phone so that the SIF would only load and execute on the SUBJECT DEVICE. The SIF will be loaded via Device Firmware Upgrade (“DFU”) mode, recovery mode, or other applicable mode available to the FBI. Once active on the SUBJECT DEVICE, the SIF will accomplish the three functions specified in paragraph 2. The SIF will be loaded on the SUBJECT DEVICE at either a government facility, or alternatively, at an Apple facility; if the latter, Apple shall provide the government with remote access to the SUBJECT DEVICE through a computer allowed the government to conduct passcode recovery analysis.\n\nAgain in plain English, the FBI wants Apple to create a special version of iOS that only works on the one iPhone they have recovered. This customized version of iOS (ahem FBiOS) will ignore passcode entry delays, will not erase the device after any number of incorrect attempts, and will allow the FBI to hook up an external device to facilitate guessing the passcode. The FBI will send Apple the recovered iPhone so that this customized version of iOS never physically leaves the Apple campus.\nAs many jailbreakers are familiar, firmware can be loaded via Device Firmware Upgrade (DFU) Mode. Once an iPhone enters DFU mode, it will accept a new firmware image over a USB cable. Before any firmware image is loaded by an iPhone, the device first checks whether the firmware has a valid signature from Apple. This signature check is why the FBI cannot load new software onto an iPhone on their own — the FBI does not have the secret keys that Apple uses to sign firmware.\nEnter the Secure Enclave\nEven with a customized version of iOS, the FBI has another obstacle in their path: the Secure Enclave (SE). The Secure Enclave is a separate computer inside the iPhone that brokers access to encryption keys for services like the Data Protection API (aka file encryption), Apple Pay, Keychain Services, and our Tidas authentication product. All devices with TouchID (or any devices with A7 or later A-series processors) have a Secure Enclave.\nWhen you enter a passcode on your iOS device, this passcode is “tangled” with a key embedded in the SE to unlock the phone. Think of this like the 2-key system used to launch a nuclear weapon: the passcode alone gets you nowhere. Therefore, you must cooperate with the SE to break the encryption. The SE keeps its own counter of incorrect passcode attempts and gets slower and slower at responding with each failed attempt, all the way up to 1 hour between requests. There is nothing that iOS can do about the SE: it is a separate computer outside of the iOS operating system that shares the same hardware enclosure as your phone.\nThe Hardware Key is stored in the Secure Enclave in A7 and newer devicesAs a result, even a customized version of iOS cannot influence the behavior of the Secure Enclave. It will delay passcode attempts whether or not that feature is turned on in iOS. Private keys cannot be read out of the Secure Enclave, ever, so the only choice you have is to play by its rules.\nPasscode delays are enforced by the Secure Enclave in A7 and newer devicesApple has gone to great lengths to ensure the Secure Enclave remains safe. Many consumers became familiar with these efforts after “Error 53” messages appeared due to 3rd party replacement or tampering with the TouchID sensor. iPhones are restricted to only work with a single TouchID sensor via device-level pairing. This security measure ensures that attackers cannot build a fraudulent TouchID sensor that brute-forces fingerprint authentication to gain access to the Secure Enclave.\nFor more information about the Secure Enclave and Passcodes, see pages 7 and 12 of the iOS Security Guide.\nThe Devil is in the Details\n“Why not simply update the firmware of the Secure Enclave too?” I initially speculated that the private data stored within the SE was erased on updates, but I now believe this is not true. Apple can update the SE firmware, it does not require the phone passcode, and it does not wipe user data on update. Apple can disable the passcode delay and disable auto erase with a firmware update to the SE. After all, Apple has updated the SE with increased delays between passcode attempts and no phones were wiped.\nIf the device lacks a Secure Enclave, then a single firmware update to iOS will be sufficient to disable passcode delays and auto erase. If the device does contain a Secure Enclave, then two firmware updates, one to iOS and one to the Secure Enclave, are required to disable these security features. The end result in either case is the same. After modification, the device is able to guess passcodes at the fastest speed the hardware supports.\nThe recovered iPhone is a model 5C. The iPhone 5C lacks TouchID and, therefore, lacks a Secure Enclave. The Secure Enclave is not a concern. Nearly all of the passcode protections are implemented in software by the iOS operating system and are replaceable by a single firmware update.\nThe End Result\nThere are still caveats in these older devices and a customized version of iOS will not immediately yield access to the phone passcode. Devices with A6 processors, such as the iPhone 5C, also contain a hardware key that cannot ever be read. This key is also “tangled” with the phone passcode to create the encryption key. However, there is nothing that stops iOS from querying this hardware key as fast as it can. Without the Secure Enclave to play gatekeeper, this means iOS can guess one passcode every 80ms.\nPasscodes can only be guessed once every 80ms with or without the Secure EnclaveEven though this 80ms limit is not ideal, it is a massive improvement from guessing only one passcode per hour with unmodified software. After the elimination of passcode delays, it will take a half hour to recover a 4-digit PIN, hours to recover a 6-digit PIN, or years to recover a 6-character alphanumeric password. It has not been reported whether the recovered iPhone uses a 4-digit PIN or a longer, more complicated alphanumeric passcode.\nFestina Lente\nApple has allegedly cooperated with law enforcement in the past by using a custom firmware image that bypassed the passcode lock screen. This simple UI hack was sufficient in earlier versions of iOS since most files were unencrypted. However, since iOS 8, it has become the default for nearly all applications to encrypt their data with a combination of the phone passcode and the hardware key. This change necessitates guessing the passcode and has led directly to this request for technical assistance from the FBI.\nI believe it is technically feasible for Apple to comply with all of the FBI’s requests in this case. On the iPhone 5C, the passcode delay and device erasure are implemented in software and Apple can add support for peripheral devices that facilitate PIN code entry. In order to limit the risk of abuse, Apple can lock the customized version of iOS to only work on the specific recovered iPhone and perform all recovery on their own, without sharing the firmware image with the FBI.\nFor more information, please listen to my interview with the Risky Business podcast.\nUpdate 1: Apple has issued a public response to the court order.\nUpdate 2: Software updates to the Secure Enclave are unlikely to erase user data. Please see the Secure Enclave section for further details.\nUpdate 3: Reframed “The Devil is in the Details” section and noted that Apple can equally subvert the security measures of the iPhone 5C and later devices that include the Secure Enclave via software updates.","tokens":2628,"crawled_at":1791195093092}
+{"id":10479,"url":"https://docs.ethena.fi/backing-custody-and-security/backing-asset-custody","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Backing Asset Custody | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nFollowing on from Collateral Custody & Security, both Ethena's onchain and offchain composite services interact & engage with \"Off-Exchange Settlement\" providers in a number of ways.\n\nEthena uses \"Off-Exchange Settlement\" providers such as, but not limited to, Copper and Ceffu.\n\nOverview\nGiven the peg stability mechanism of USDe, Ethena's \"Treasury Management\" system increases and decreases the sizes of delta hedging derivatives positions as users mint and redeem USDe. As the supply of USDe increases, the delta will change and more short derivative positions are entered into to eliminate backing asset price exposure, and vice versa when USDe supply shrinks.\nIn the process of minting & redeeming USDe, users transfer & request backing assets in exchange for/from USDe. In addition, given USDe's peg stability mechanism, Ethena needs to be able to:\n\nSafely & securely custody protocol backing assets.\n\nTransfer backing assets between smart contracts & users.\n\nDelegate/Undelegate backing assets between \"Off-Exchange Settlement\" providers and centralized exchanges.\n\nEthena also needs to be able to transfer rewards to the Staking Smart Contract & the \"Off-Exchange Settlement\" provider plays a role.\nExample Internal Workflows\nSome workflow examples to highlight how different components of the system interact with \"Off-Exchange Settlement\" providers:\n\nUpon a user successfully minting USDe, the transferred asset is transferred by the Minting smart contract directly to the \"Off-Exchange Settlement\" provider.\n\nUpon a user successfully minting USDe, the internal hedging system needs to open an additional short derivatives position to hedge the increased delta exposure of the newly transferred asset from the user. As such, the \"Off-Exchange Settlement\" provider is instructed to delegate funds to the exchange.\n\nUpon a user successfully redeeming USDe, the user receives protocol backing assets from the Minting smart contract in exchange for the redeemed USDe. The minting smart contract needs to be actively monitored and refilled with protocol backing assets from an \"Off-Exchange Settlement\" provider.\n\nUpon a user successfully redeeming USDe, the internal hedging system needs to close the corresponding short derivatives position as the protocol no longer needs to hedge the delta exposure of the assets transferred to the redeeming user.\n\nUpon the protocol earning revenue, the funds are undelegated from the \"Off-Exchange Settlement\" provider and used to mint USDe.\n\n\"Off-Exchange Settlement\" Provider Benefits\n\"Off-Exchange Settlement\" providers provide unique benefits critical to many aspects of the user experience:\n\nEthena is able to prove the existence and control of protocol funds onchain.\n\nProtocol backing assets remain onchain with solutions provided by regulated and trusted parties. These entities are non-US based.\n\nThis enables users to enjoy the benefits of the ability to verify the existence and control of assets onchain, while also enjoying the benefits of high governance & security protections used by institutional participants.\n\nEthena mitigates the risks of CeFi Exchange failure.\n\n\"Off-Exchange Settlement\" providers require exchanges to post collateral with the provider to ensure each settlement cycle can occur without friction. This combined with frequent PnL settlement cycles, Copper is daily, enables Ethena to enjoy the benefits of CeFi liquidity without risking protocol backing assets with an obscure entity.\n\nEthena controls the \"deposits\" and \"withdrawals\" of funds.\n\nEach CeFi Exchange has varying deposit & withdrawal processes and speeds of operation. This can leave users waiting hours or days to be able to withdraw their assets.\n\n\"Off-Exchange Settlement\" providers enable Ethena to, in all market conditions, delegate & undelegate assets to margin derivatives positions without having to wait for the exchange or an onchain transaction. Delegation/undelegation operations typically take seconds and are at no cost to the protocol.\n\nThis enables Ethena to offer on-demand mint/redeem USDe requests to eliminate the friction of users being able to on & off-ramp from USDe.\n\nEthena remains agnostic to providers through each step of the workflow.\n\nOptimally, the system would use as many high-quality providers as possible for each step of the workflow. This enables Ethena to mitigate many risks as well as encourages an ecosystem that benefits users & the protocol.\n\nIt is the intention to onboard with as many \"Off-Exchange Settlement\" providers as reasonable and to champion transparency & independent verification of assets features across the space.\n\nCustody FAQ\nNotion FAQ Link\n\nLast updated 2 months ago\nWas this helpful?","tokens":1197,"crawled_at":1791195107363}
+{"id":10480,"url":"https://www.getfoundry.sh/best-practices","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"Best Practices – foundry - Ethereum Development Framework","text":"Best Practices\n\nGuidelines for writing maintainable, secure, and efficient Foundry projects.\n\nBefore you ship\n\nRun forge test with -vvvv at least once\n\nRun forge lint and forge fmt --check\n\nVerify deployments with the exact compiler settings\n\nStore production keys in encrypted keystores or hardware wallets\n\nKeep .env files out of version control\n\nWriting contracts\n\nUse named imports\n\nImport only what you need to reduce compilation time and make dependencies explicit:\n\nimport {ERC20} from \"@openzeppelin/contracts/token/ERC20/ERC20.sol\";\nimport {Ownable} from \"@openzeppelin/contracts/access/Ownable.sol\";\n\nimport \"@openzeppelin/contracts/token/ERC20/ERC20.sol\";\n\nFormat with forge fmt\n\nUse the built-in formatter for consistent code style:\n\n$ forge fmt\n\nCheck formatting without modifying files:\n\n$ forge fmt --check\n\nConfigure formatting in foundry.toml:\n\nfoundry.toml\n[fmt]\nline_length = 120\ntab_width = 4\nbracket_spacing = true\n\nAvoid \"Stack too deep\" errors\n\nThe EVM limits access to the top 16 stack slots. When you hit this error, the fix is usually to restructure your code—group variables into structs, split large functions into smaller helpers, or use block scoping.\n\nSee the Stack Too Deep guide for causes, solutions, and when to use via-ir as a last resort.\n\nOrganize contract layout\n\nFollow a consistent ordering within contracts:\n\nType declarations (structs, enums)\n\nState variables\n\nEvents\n\nErrors\n\nModifiers\n\nConstructor\n\nExternal functions\n\nPublic functions\n\nInternal functions\n\nPrivate functions\n\nWriting tests\n\nNaming conventions\n\nUse descriptive names that explain behavior:\n\nPatternUsageExample\ntest_Description\nStandard tests\ntest_TransferUpdatesBalances\n\ntestFuzz_Description\nFuzz tests\ntestFuzz_TransferAnyAmount\n\ntest_RevertWhen_Condition\nRevert tests\ntest_RevertWhen_InsufficientBalance\n\ntest_RevertIf_Condition\nAlternative revert naming\ntest_RevertIf_NotOwner\n\nfunction test_TransferUpdatesBalances() public {\ntoken.transfer(bob, 100);\nassertEq(token.balanceOf(bob), 100);\n}\n\nfunction test_RevertWhen_TransferExceedsBalance() public {\nvm.expectRevert(Token.InsufficientBalance.selector);\ntoken.transfer(bob, type(uint256).max);\n}\n\nTest organization\n\nStructure test files to mirror your source files:\n\nToken.sol\n\nVault.sol\n\nGovernor.sol\n\nToken.t.sol\n\nVault.t.sol\n\nGovernor.t.sol\n\nGroup related tests in the same contract:\n\ntest/Token.t.sol\ncontract TokenTransferTest is Test {\nfunction test_TransferUpdatesBalances() public { }\nfunction test_TransferEmitsEvent() public { }\nfunction test_RevertWhen_InsufficientBalance() public { }\n}\n\ncontract TokenApprovalTest is Test {\nfunction test_ApproveUpdatesAllowance() public { }\nfunction test_TransferFromUsesAllowance() public { }\n}\n\nUse test harnesses\n\nCreate harness contracts to expose internal functions for testing:\n\nimport {Token} from \"../../src/Token.sol\";\n\ncontract TokenHarness is Token {\nfunction exposed_mint(address to, uint256 amount) external {\n_mint(to, amount);\n}\n\nfunction exposed_burn(address from, uint256 amount) external {\n_burn(from, amount);\n}\n}\n\nimport {TokenHarness} from \"./harnesses/TokenHarness.sol\";\n\ncontract TokenInternalTest is Test {\nTokenHarness token;\n\nfunction setUp() public {\ntoken = new TokenHarness();\n}\n\nfunction test_MintIncreasesSupply() public {\ntoken.exposed_mint(alice, 1000);\nassertEq(token.totalSupply(), 1000);\n}\n}\n\nPrefer bound() over assume()\n\nUse bound() to constrain fuzz inputs instead of vm.assume():\n\nfunction testFuzz_Transfer(uint256 amount) public {\namount = bound(amount, 1, token.balanceOf(alice));\ntoken.transfer(bob, amount);\n}\n\nfunction testFuzz_Transfer(uint256 amount) public {\nvm.assume(amount > 0 && amount <= token.balanceOf(alice));\ntoken.transfer(bob, amount);\n}\n\nvm.assume() discards invalid inputs, which can slow down fuzzing. bound() transforms inputs to valid ranges.\n\nWriting scripts\n\nSeparate concerns\n\nSplit complex deployments into focused scripts:\n\nDeployToken.s.sol\n\nDeployVault.s.sol\n\nConfigureVault.s.sol\n\nDeploy.s.solOrchestrates all deployments\n\nscript/Deploy.s.sol\nimport {DeployToken} from \"./DeployToken.s.sol\";\nimport {DeployVault} from \"./DeployVault.s.sol\";\n\ncontract DeployScript is Script {\nfunction run() public {\nDeployToken tokenDeployer = new DeployToken();\naddress token = tokenDeployer.run();\n\nDeployVault vaultDeployer = new DeployVault();\nvaultDeployer.run(token);\n}\n}\n\nUse environment variables for configuration\n\nNever hardcode addresses or keys in scripts:\n\nGood\nfunction run() public {\naddress admin = vm.envAddress(\"ADMIN_ADDRESS\");\nuint256 initialSupply = vm.envOr(\"INITIAL_SUPPLY\", uint256(1_000_000 ether));\n\nvm.startBroadcast();\nnew Token(admin, initialSupply);\nvm.stopBroadcast();\n}\n\nLog deployment information\n\nOutput addresses and transaction details for verification:\n\nfunction run() public {\nvm.startBroadcast();\n\nToken token = new Token();\nconsole.log(\"Token deployed at:\", address(token));\nconsole.log(\"Chain ID:\", block.chainid);\nconsole.log(\"Deployer:\", msg.sender);\n\nvm.stopBroadcast();\n}\n\nSecurity\n\nEnable the linter\n\nCatch common issues with forge lint:\n\n$ forge lint\n\nConfigure rules in foundry.toml:\n\nfoundry.toml\n[lint]\nseverity = \"warning\"\nexclude = [\"script/**\"]\n\nTest access control\n\nVerify that protected functions reject unauthorized callers:\n\nfunction test_RevertWhen_CallerNotOwner() public {\nvm.prank(attacker);\nvm.expectRevert(Ownable.OwnableUnauthorizedAccount.selector);\nvault.withdrawAll();\n}\n\nTest edge cases\n\nCover boundary conditions in your tests:\n\nfunction test_TransferZeroAmount() public {\ntoken.transfer(bob, 0);\nassertEq(token.balanceOf(bob), 0);\n}\n\nfunction test_TransferMaxAmount() public {\ndeal(address(token), alice, type(uint256).max);\nvm.prank(alice);\ntoken.transfer(bob, type(uint256).max);\n}\n\nKey management\n\nUse encrypted keystores\n\nStore keys encrypted, not as plaintext environment variables:\n\nCreate a keystore\n$ cast wallet import deployer --interactive\n\nUse the keystore\n$ forge script script/Deploy.s.sol --account deployer --broadcast --rpc-url https://ethereum.reth.rs/rpc\n\nUse hardware wallets for production\n\nFor mainnet deployments, use a hardware wallet:\n\n$ forge script script/Deploy.s.sol --ledger --broadcast --rpc-url https://ethereum.reth.rs/rpc\n\nSeparate development and production keys\n\nUse different keys for different environments:\n\nEnvironmentKey source\nLocal development\nAnvil default keys\n\nTestnets\nEncrypted keystore\n\nMainnet\nHardware wallet\n\nAnvil provides pre-funded accounts for local testing:\n\nStart Anvil\n$ anvil\n\nUse Anvil's first account\n$ forge script script/Deploy.s.sol --broadcast --rpc-url http://localhost:8545 --private-key 0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80\n\nProtect environment files\n\nKeep .env files out of version control:\n\n.env\n.env.*\n\nUse .env.example to document required variables:\n\n.env.example\n$ RPC_URL=\n$ ETHERSCAN_API_KEY=\n# Use `cast wallet import` instead of PRIVATE_KEY\n\nWas this helpful?\n\nSuggest changes on GitHub","tokens":1734,"crawled_at":1791195108608}
+{"id":10481,"url":"https://docs.sui.io/getting-started/onboarding/sui-install","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Install Sui | Sui Documentation","text":"Install the Sui CLI and verify it works. The CLI creates and manages addressAddressA unique, anonymous identity on a blockchain network. balances, builds and publishes smart contracts, and queries information from the network.\n\nLooking for something else?\nThis page covers installation only. For other common tasks:\n\nConfigure a Sui Client\n\nGet SUI from Faucet\n\nHello, World!\n\nSui Full Node\n\nData Access\n\nLinux\nmacOS\nWindows\n\nUbuntu 22.04 (Jammy Jellyfish) or newer\n\nmacOS Monterey or newer\n\nWindows 10 or 11\n\nQuick install​\n\nYou use the Sui CLI to interact with the Sui network, deploy packagesPackageSmart contracts on Sui., and manage assets. To install the Sui CLI, you can use suiup.\n\nsuiup is the most effective installation method, as it allows you to easily install and switch between different versions of not only the Sui CLI but also other Sui stack components like walrus and mvr.\n\nAlternative quick install instructions for Homebrew or Chocolately do not support installing other Sui stack components. You need to install other components through their individual binaries if you'd like to use them in the future.\n\ncaution\nInstallations using Homebrew or Chocolatey might take several minutes if you do not have any of the Sui prerequisites installed. Using suiup is often much faster and highly recommended.\n\nsuiup (recommended)\nHomebrew\nChocolatey\nFirst, install suiup:\n$ curl -sSfL \\\nhttps://raw.githubusercontent.com/Mystenlabs/suiup/main/install.sh \\\n| sh\n\nThen, install Sui:\n$ suiup install sui@testnet\n\nFor alternative installation methods, refer to the suiup repository.\ndanger\nInstalling Sui with suiup does not configure the client. To use sui commands, you must configure the Sui client.\nTo confirm that Sui installed correctly:\n\nOpen a terminal or console\n\nType sui --version and press Enter\n\nIf you receive a \"command not found\" error, verify the Sui binaries directory is in your PATH environment variable.\n\ninfo\nsuiup is the recommended installer. It supports version pinning and can install additional Sui stack components (walrus, mvr, move-analyzer). Use Homebrew only if you prefer to manage Sui through your system packagePackageSmart contracts on Sui. manager.\n\nYou must have Homebrew installed before running the following command:\n$ brew install sui\n\nTo confirm that Sui installed correctly:\n\nOpen a terminal or console\n\nType sui --version and press Enter\n\nIf you receive a \"command not found\" error, verify the Sui binaries directory is in your PATH environment variable.\n\ninfo\nsuiup is the recommended installer. It supports version pinning and can install additional Sui stack components (walrus, mvr, move-analyzer). Use Chocolatey only if you prefer to manage Sui through your system package manager.\n\nYou must have Chocolately installed before running the following command:\n$ choco install sui\n\nFind more versions of Sui for Windows on the Chocolatey community website.\nTo confirm that Sui installed correctly:\n\nOpen a terminal or console\n\nType sui --version and press Enter\n\nIf you receive a \"command not found\" error, verify the Sui binaries directory is in your PATH environment variable.\n\nThe quick install is suitable for most use cases. For those wanting more control over the installation process, you can install from source or install binaries.\n\nIf Sui is already installed from a previous development environment, be sure to upgrade to the latest version.\n\nVerify the installation​\n\nAfter installing, open a new terminal and run:\n\n$ sui --version\n\nIf the installation succeeded, the command prints the installed Sui version.\n\nLooking for a project to clone?\nBefore you can create and publish a smart contract, you must configure a Sui client and obtain SUI tokens.\nThen, you can create a \"Hello, World!\" example.\n\nInstallation details​\n\nsuiup installation details​\n\nRefer to the suiup repository's README for information regarding installation files and their locations.\n\nDefault configuration file​\n\nRegardless of whether you used suiup, Homebrew, or Chocolately, Sui stores a primary configuration in the ~/.sui/sui_config/client.yaml file. This file defines settings and preferences for your environment, such as:\n\nNetwork environment details for MainnetMainnetProduction network for live transactions and real-value assets., TestnetTestnetStaging network for testing changes before production deployment., DevnetDevnetFor developing and testing new features., and LocalnetLocalnetLocal network you can run on your own machine for optimized development. networks.\n\nActive environment, which specifies the network the CLI commands target.\n\nActive address, which specifies the Sui address the CLI uses for transactions and queries.\n\nKeystore location, which specifies where Sui stores your address' private keys.\n\nTroubleshooting​\n\nClick to opensui: command not found after installationOpen a new terminal window after installing. If the issue persists, verify that the shell can find the sui binary:\n$ command -v sui\n\nIf no path is printed, the install directory is not in your PATH. The default suiup install location is ~/.local/bin (see suiup README). Add export PATH=\"$HOME/.local/bin:$PATH\" to your shell profile (~/.bashrc, ~/.zshrc, or ~/.bash_profile), then restart your terminal.\n\nClick to openClient/server API version mismatchYour local Sui CLI version does not match the network you are targeting. Switch to the correct version with suiup:\n$ suiup install sui@testnet\n\nReplace testnet with mainnet or devnet as needed.\n\nClick to openHomebrew or Chocolatey installation is slowHomebrew and Chocolatey might compile dependencies from source if the package manager has not cached prebuilt binaries. This can take several minutes. For a faster installation, use suiup instead:\n$ curl -sSfL https://raw.githubusercontent.com/MystenLabs/suiup/main/install.sh | sh\n$ suiup install sui@testnet\n\nClick to openPermission denied during installationDo not use sudo to install Sui. The suiup installer writes to your home directory and does not require elevated privileges. If a previous installation used sudo, remove it first:\n$ sudo rm -f /usr/local/bin/sui\n\nThen reinstall with suiup.\n\nClick to openMultiple Sui versions installedIf you previously installed Sui through Homebrew, Cargo, or a manual binary and also have suiup, you might have conflicting versions. Check which binary is active:\n$ which sui\n$ sui --version\n\nRemove the older installation method and use suiup exclusively to manage versions. Run suiup install sui@<network> to switch between network-compatible versions.\n\nNext steps\n\nConfigure a Sui Client\n\nConfigure a Sui client to get a Sui address and connect to Testnet.\n\nGet SUI from Faucet\n\nObtain SUI from a faucetFaucetA service that provides free Testnet tokens. to deploy packages on Testnet.\n\nHello, World!\n\nClone the \"Hello, World!\" project.\n\nQuick installVerify the installation\n\nInstallation detailssuiup installation details\nDefault configuration file\n\nTroubleshooting\n\nWas this page helpful?","tokens":1745,"crawled_at":1791195113888}
+{"id":10482,"url":"https://blog.trailofbits.com/2026/09/18/auditing-in-the-age-of-good-enough-ai","domain":"blog.trailofbits.com","chapter":"security_audits","title":"Auditing in the age of (good enough) AI - The Trail of Bits Blog","text":"Page content\n\nSecurity firms have published numerous blog posts describing how they pointed their agent harness at a codebase and found dozens of bugs (we��re one of them). However, these posts tend to focus on agentic code review, which is just one aspect of how we use AI in our security reviews. We want to give a different perspective: before code review even starts, agents now allow us to build custom tooling and formal models that improve the quality and depth of our reviews.\nWe recently reviewed the Miden VM, a new zero-knowledge VM with its own custom assembly language and almost no developer tooling. To prepare, we spent six months having our agents build an LSP server, a decompiler, a static analysis engine, and a Lean model of the VM executor from scratch. These tools found real security issues, like an unvalidated prover-supplied input that would let a malicious prover forge Falcon signatures and steal funds from Miden account holders. Additionally, the Lean work produced 95 machine-checked correctness proofs, covering a large component of the Miden core library.\nAuditing the Miden zkVM\nIn late 2025, the Miden team came to us to have parts of their zero-knowledge VM reviewed before launch. Part of the review was scoped to cover the Miden core library, which contains a small set of cryptographic primitives written in a custom assembly language called Miden assembly (MASM). This made us genuinely excited, as it was right up our alley: a high-assurance project writing complex cryptographic code in a low-level custom assembly language that we had never seen before. At the same time, it also presented some unique challenges.\n\nFigure 1: The left image shows a MASM procedure computing the XOR of two 128-bit values (represented as 32-bit limbs). The right image shows the same procedure implemented using 32-bit x86 assembly code.\nTo start, the Miden VM implements a stack-machine architecture. This means that each instruction operates on values read from the stack, and the result of the instruction is then written back to the top of the stack. While conceptually simple, this makes code written in MASM challenging to review, since instruction inputs and outputs are read from the stack and are always implicit. Additionally, since the Miden VM is a completely new architecture, very little existed in terms of developer tooling like IDE support, Language Server Protocol (LSP) servers, and linters.\nWe knew that we had six months to prepare for the review, since the implementation was not yet feature complete, so we asked ourselves: “What could we spend our time and tokens on to make sure that the review would root out as many bugs as possible in the codebase?”\nBuilding all the tools!\nSince MASM lacked developer tooling, we started out by asking ourselves what kind of tools we would like to have available when the project started. We typically use VS Code to review code, and syntax highlighting and code navigation are essential for readability and being able to follow data flow throughout a codebase. We needed an LSP server and a corresponding VS Code extension for this, and within a few days we had Claude build a working prototype that provided most of the functionality we wanted: features like syntax highlighting, goto definition, finding code references, and displaying procedure docstrings on hover. With these fundamental features in place, we also decided to add more language-specific features like displaying inline instruction documentation, and stack effects for individual instructions.\n\nFigure 2: Annotating the code with inline stack effects and instruction documentation helps prevent the context switch required to look up instruction semantics elsewhere.\nHaving built the LSP server, we started thinking about other ways to provide high-level semantic information to support manual and agent-driven review. We thought it would be interesting to see if we could provide faithful decompilation for MASM procedures inside the VS Code UI, to help the reviewer quickly understand the high-level control flow and data flow of the procedures they were looking at. For MASM, this is a harder problem than it first appears. Stack machine lifting and decompilation is a well-studied problem, but decompiling hand-written MASM is still difficult for a number of reasons.\nMost procedures in the core library do not have declared signatures, which means that the number of inputs and outputs must be inferred from context.\n\nMASM procedures do not conform to a well-defined calling convention, and the net stack effect of such calls is generally impossible to determine statically. This means that all analysis failures propagate up the call chain.\n\nWhile-loops do not need to be stack neutral, which means that the while-loop condition may occupy a different stack slot in each iteration. This also makes it impossible to map instruction inputs to stack slots for subsequent instructions.\n\nDifferent branches in conditional statements may have different stack effects, which similarly makes stack tracking and signature inference challenging.\n\nThis meant that we could not expect to be able to decompile all MASM procedures if we also wanted the decompiled output to be correct. We therefore focused on decompiling a well-defined subset of MASM correctly. During the development of the decompiler, we alternated between using Claude for planning and development and Codex for code review. Whenever we had implemented a new feature, we had agents decompile a randomized set of procedures from the core library and compare the result to the original MASM to look for regressions. Any issues found were added as regression tests to be fixed by the model.\n\nFigure 3: The eqz procedure, which tests if a 256-bit integer (represented as eight 32-bit limbs) is equal to zero, together with the corresponding decompiled pseudocodeThe decompiler represented the single largest effort of the tooling development for this project, with over 100 AI-generated commits over multiple months. The main benefit of this work turned out to be the decompiler’s internal analysis frameworks and intermediate representation, which we could reuse for static analysis, rather than the full decompilation pipeline.\nWith the decompiler in place, we had access to an intermediate representation of each procedure, with instruction inputs and outputs populated as expressions. This allowed us to bring all the standard static analysis machinery (like data flow analysis) to bear on the problem of finding bugs in the MASM code. We used this to build a number of analysis passes over the intermediate representation, answering questions like the following:\nAre prover-supplied advice values1 like remainders and modular inverses properly validated?\n\nAre type constraints (e.g. an input being a 32-bit integer or a boolean) enforced?\n\nAre local variables initialized across all execution paths?\n\nOne way to explore these issues is abstract interpretation. The idea behind this technique is simple. Instead of running the program with real numbers, the analysis tracks the types of values that could be on the stack at each step, like “a 32-bit integer” or “unknown.” It walks through the code again and again until no new information is found. Since it always keeps track of every possible value (with a little extra room), it can never miss a real case. So if a check passes in the analysis, it is guaranteed to hold in every actual run of the program.\nWe used Claude and Codex to build a general abstract interpretation engine, and then implemented a number of concrete analysis passes on top of it, having the agents switch between development and code review as described above. We also decided to have the agents design and build command-line interfaces for both the decompiler and a new MASM linter to make the new tools available to agent-driven code-review workflows as well.\nFinding all the bugs!\nDuring the actual review, these analyses identified over 400 unique locations2 where type validation could be improved (all of them reachable from the public API of the library) as well as one high-severity finding.\n\nFigure 4: The remainder is read from the advice stack, but is not validated to ensure that it is a valid 64-bit integer.\nThe high-severity issue was due to an underconstrained advice value in the mod_12289 procedure, which reduces a 64-bit value modulo 12289, with a quotient and remainder provided as advice values by the prover. The quotient is checked to ensure that it is a valid 64-bit value (represented as two 32-bit limbs), but the remainder is never validated before it is passed to the 32-bit instruction u32overflowing_sub. By carefully varying the quotient and remainder to ensure they still satisfy the constraints imposed by the subtraction, we found that it was possible to have mod_12289 return a value that is not the correct remainder. A malicious prover could exploit this to forge Falcon signatures and drain any Miden account controlled by a Falcon key pair.\nBut what if there are no bugs?\nAll this work meant that we had a comprehensive set of tools to support both manual and agent-driven code review coming into the audit. However, we’d had a long time to think about other ways to support the manual review process, and we had more ideas that we wanted to test. For example, if the procedures in the core library were implemented correctly and did not contain bugs, would it be possible to prove this using a proof assistant like Lean?\nIt turns out that the Miden VM is very amenable to formal modeling, since the instruction set is small and most instructions are side-effect free. To formally model MASM, we started by implementing a minimal Miden VM executor in Lean, and had Claude build an automatic translator from MASM procedures to Lean. During the review, we had multiple agents working in parallel to prove correctness of as many procedures as possible across the library. Since the Lean kernel could validate that the generated proofs were correct, we only needed to manually audit the theorem statements to ensure that each theorem proved the right correctness property for the corresponding procedure. To ensure that the theorems were easy to review, we introduced Lean types for field elements and the integer types implemented in the core library. This meant that at a high level, most correctness properties could be expressed in the following form:\nIf the stack is given by [x1, x2, x3, ..., xn, ...] and we execute the procedure P, then P terminates and the stack is given by [P(x1, x2, x3, ..., xn), ...].\n\nFigure 5: High-level statement of correctness for the procedure P with n argumentsOur agent-driven formal modeling efforts resulted in 95 correctness proofs that covered all of the binary arithmetic components of the core library. This work also identified two subtle bugs that the existing unit test suite did not catch. The first was an edge case in the 64-bit right-rotation rotr, which behaved incorrectly on large inputs greater than the Goldilocks prime if the rotational shift was a multiple of 32. The second was an issue in the 256-bit multiplication wrapping_mul, which dropped caller-owned values from the stack before returning.\n\nFigure 6: Manual review identified that the correctness proof for the 64-bit rotr procedure required an additional assumption (that shift mod 32 ≠ 0) to allow the proof to go through.Why we couldn’t have done this two years ago\nThe tools we developed leading up to this engagement, and the Lean libraries and proofs generated during the review, are all side projects that we wouldn’t have been able to dedicate time or resources to just one or two years ago. Projects like these are often highly exploratory in nature, and the end results and potential payoff may be difficult to predict. In practice, this means that it is hard to sell clients on them in advance. However, over the last year, agents became good enough to carry non-essential projects like these with only light supervision, which completely changed the economics of which projects are worth pursuing. Today, a failed side project only costs tokens.\nWith Miden, the benefits of all this preparatory work were clear. The LSP server and static analysis engine improved our manual review coverage, strengthened agent-driven reviews, and identified real security issues in the codebase that could have led to millions of dollars in lost funds. The AI-generated Lean correctness proofs also improved assurance across a large and fundamental component of the library, allowing the team to continue building on it with confidence. The team has adopted the static analysis engine developed for the review, which means that our side project will now also help secure future updates to the Miden core library.\nOn a personal note, this has been one of the more interesting projects I have worked on during my years at Trail of Bits. If you find this type of work interesting, or if you are building something similar, get in touch. We want to hear about it!\nThese are precomputed inputs that are supplied via a separate advice stack by the prover, and need to be validated carefully. ↩︎\n\nMost of these findings were due to the fact that almost all procedures in the core library were part of the public API, which meant that third-party developers could call them without proper validation. ↩︎","tokens":3348,"crawled_at":1791195114254}
+{"id":10483,"url":"https://www.getfoundry.sh/config/ci","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"CI Integration – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nCI Integration\n\nRun Foundry tests in continuous integration to catch issues before merging.\n\nGitHub Actions\n\nBasic workflow\n\nCreate .github/workflows/test.yml:\n\n.github/workflows/test.yml\nname: Tests\n\non:\npush:\nbranches: [main]\npull_request:\n\njobs:\ntest:\nruns-on: ubuntu-latest\nsteps:\n- uses: actions/checkout@v4\nwith:\nsubmodules: recursive\n\n- name: Install Foundry\nuses: foundry-rs/foundry-toolchain@v1\n\n- name: Build\nrun: forge build\n\n- name: Run tests\nrun: forge test -vvv\n\nWith caching\n\nSpeed up CI by caching dependencies:\n\n.github/workflows/test.yml\nname: Tests\n\non:\npush:\nbranches: [main]\npull_request:\n\njobs:\ntest:\nruns-on: ubuntu-latest\nsteps:\n- uses: actions/checkout@v4\nwith:\nsubmodules: recursive\n\n- name: Install Foundry\nuses: foundry-rs/foundry-toolchain@v1\nwith:\ncache: true\n\n- name: Build\nrun: forge build\n\n- name: Run tests\nrun: forge test -vvv\n\nUsing a CI profile\n\nUse a dedicated profile for more thorough testing in CI:\n\n.github/workflows/test.yml\n- name: Run tests\nrun: forge test -vvv\nenv:\nFOUNDRY_PROFILE: ci\n\nWith the corresponding profile in foundry.toml:\n\nfoundry.toml\n[profile.ci]\nverbosity = 3\nfuzz = { runs = 10000 }\ninvariant = { runs = 1000 }\n\nFull workflow example\n\nA complete workflow with formatting, linting, build, and tests:\n\n.github/workflows/ci.yml\nname: CI\n\non:\npush:\nbranches: [main]\npull_request:\n\nenv:\nFOUNDRY_PROFILE: ci\n\njobs:\ncheck:\nruns-on: ubuntu-latest\nsteps:\n- uses: actions/checkout@v4\nwith:\nsubmodules: recursive\n\n- name: Install Foundry\nuses: foundry-rs/foundry-toolchain@v1\nwith:\ncache: true\n\n- name: Check formatting\nrun: forge fmt --check\n\n- name: Run linter\nrun: forge lint --deny warnings\n\n- name: Build\nrun: forge build\n\n- name: Run tests\nrun: forge test -vvv\n\n- name: Check gas snapshots\nrun: forge snapshot --check\n\nFork testing in CI\n\nFor tests that fork from a live network, provide an RPC URL:\n\n.github/workflows/test.yml\n- name: Run fork tests\nrun: forge test -vvv\nenv:\nETH_RPC_URL: ${{ secrets.ETH_RPC_URL }}\n\nSet ETH_RPC_URL in your repository secrets. Use your own RPC endpoint or a provider like Alchemy or Infura.\n\nConfigure the fork URL in foundry.toml:\n\nfoundry.toml\n[profile.ci]\neth_rpc_url = \"${ETH_RPC_URL}\"\n\nCoverage reports\n\nGenerate and upload coverage reports. See Code Coverage for profile configuration, source filters, LCOV versions, and per-test attribution:\n\n.github/workflows/coverage.yml\nname: Coverage\n\non:\npush:\nbranches: [main]\npull_request:\n\njobs:\ncoverage:\nruns-on: ubuntu-latest\nsteps:\n- uses: actions/checkout@v4\nwith:\nsubmodules: recursive\n\n- name: Install Foundry\nuses: foundry-rs/foundry-toolchain@v1\nwith:\ncache: true\n\n- name: Generate coverage report\nrun: forge coverage --report lcov\n\n- name: Upload to Codecov\nuses: codecov/codecov-action@v4\nwith:\nfiles: lcov.info\ntoken: ${{ secrets.CODECOV_TOKEN }}\n\nGitLab CI\n\n.gitlab-ci.yml\nimage: ghcr.io/foundry-rs/foundry:latest\n\nstages:\n- test\n\ntest:\nstage: test\nscript:\n- forge build\n- forge test -vvv\n\nCircleCI\n\n.circleci/config.yml\nversion: 2.1\n\njobs:\ntest:\ndocker:\n- image: ghcr.io/foundry-rs/foundry:latest\nsteps:\n- checkout\n- run:\nname: Install submodules\ncommand: git submodule update --init --recursive\n- run:\nname: Build\ncommand: forge build\n- run:\nname: Test\ncommand: forge test -vvv\n\nworkflows:\nmain:\njobs:\n- test\n\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":841,"crawled_at":1791195125989}
+{"id":10484,"url":"https://www.metaplex.com/docs/smart-contracts/core/plugins/permanent-freeze-delegate","domain":"www.metaplex.com","chapter":"docs","title":"Permanent Freeze Delegate | Metaplex Core","text":"The Permanent Freeze Delegate Plugin provides irrevocable freeze authority that persists across transfers. Use it for soulbound tokens, collection-wide freezing, and permanent lock mechanisms.\nWhat You'll Learn\nCreate Assets with permanent freeze capability\nFreeze entire Collections at once\nImplement soulbound (non-transferable) tokens\nUnderstand permanent vs regular freeze delegate\n\nSummary\nThe Permanent Freeze Delegate is a permanent plugin that can only be added at creation time. Unlike the regular Freeze Delegate, this authority persists forever and can freeze/thaw even after transfers.\nCan only be added at Asset/Collection creation\nAuthority persists across transfers (never revoked)\nUses forceApprove - can freeze even with other blocking plugins\nCollection-level freezing affects all Assets in the Collection\nOut of Scope\nRegular freeze delegate (see Freeze Delegate), temporary freezing, and Token Metadata freeze authority.\nQuick Start\nJump to: Create Asset · Create Collection · Update (Thaw)\nAdd PermanentFreezeDelegate plugin at Asset/Collection creation\nSet frozen: true for immediate freeze, or false to freeze later\nThe delegate can freeze/thaw at any time, even after transfers\nPermanent vs Regular Freeze Delegate\nFeatureFreeze DelegatePermanent Freeze Delegate\nAdd after creation\n✅ Yes\n❌ Creation only\n\nAuthority persists on transfer\n❌ Revokes\n✅ Persists\n\nWorks with Collections\n❌ No\n✅ Yes\n\nforceApprove\n❌ No\n✅ Yes\n\nSoulbound tokens\n❌ Limited\n✅ Best choice\n\nChoose Freeze Delegate for temporary, revocable freezing.\n\nChoose Permanent Freeze Delegate for permanent authority or collection-wide freezing.\n\nCommon Use Cases\nSoulbound tokens: Create non-transferable credentials, achievements, or memberships\nCollection-wide freeze: Freeze all Assets in a Collection with one plugin\nPermanent collateral: Lock Assets as collateral that survives ownership changes\nGame item permanence: Items that stay locked regardless of trades\nCompliance requirements: Assets that must remain frozen for regulatory reasons\nWorks With\n\nMPL Core Asset\n✅\n\nMPL Core Collection\n✅\n\nBehaviours\nAsset: Allows the delegated address to freeze and thaw the NFT at any time.\nCollection: Allows the collection authority to freeze and thaw the whole collection at once. It does not allow to freeze a single asset in the collection using this delegate.\nArguments\nArgValue\nfrozen\nbool\n\nCreating an Asset with a Permanent Freeze plugin\nThe following example shows how to create an Asset with a Permanent Freeze plugin.\nCreating an Asset with a Permanent Freeze plugin\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { create } from '@metaplex-foundation/mpl-core'\n\nconst assetSigner = generateSigner(umi)\n\nconst delegate = publicKey('33333333333333333333333333333')\n\nawait create(umi, {\n\nasset: assetSigner,\n\nname: 'My NFT',\n\nuri: 'https://example.com/my-asset.json',\n\nplugins: [\n\n{\n\ntype: 'PermanentFreezeDelegate',\n\nfrozen: true,\n\nauthority: { type: 'Address', address: delegate },\n\n},\n\n],\n\n}).sendAndConfirm(umi)\n\nUpdating the Permanent Freeze Delegate plugin on an Asset\nThe following example shows how to update the Permanent Freeze Delegate plugin on an Asset. Freeze or unfreeze it by setting the frozen argument to true or false respectively. It assumes that the signing wallet is the plugin authority.\nUpdating the Permanent Freeze Delegate plugin on an Asset\n\nimport { updatePlugin } from '@metaplex-foundation/mpl-core'\n\nconst updateAssetResponse = await updatePlugin(umi, {\n\nasset: asset.publicKey,\n\nplugin: {\n\ntype: \"PermanentFreezeDelegate\",\n\nfrozen: false,\n\n},\n\n}).sendAndConfirm(umi);\n\nCreating a Collection with a Permanent Freeze plugin\nThe following example shows how to create a collection with a Permanent Freeze plugin.\nCreating a Collection with a Permanent Freeze plugin\n\nimport { generateSigner } from '@metaplex-foundation/umi'\n\nimport { createCollection } from '@metaplex-foundation/mpl-core'\n\nconst collectionSigner = generateSigner(umi)\n\nawait createCollection(umi, {\n\ncollection: collectionSigner,\n\nname: \"Frozen Collection\",\n\nuri: \"https://example.com/my-collection.json\",\n\nplugins: [\n\n{\n\ntype: 'PermanentFreezeDelegate',\n\nfrozen: true,\n\nauthority: { type: \"UpdateAuthority\"}, // The update authority can unfreeze it\n\n},\n\n],\n\n}).sendAndConfirm(umi);\n\nUpdating a Collection with a Permanent Freeze plugin\nThe following example shows how to update the Permanent Freeze Delegate plugin on a Collection. Freeze or unfreeze it by setting the frozen argument to true or false respectively. It assumes that the signing wallet is the plugin authority.\nUpdating a Collection with a Permanent Freeze plugin\n\nimport { updateCollectionPlugin } from '@metaplex-foundation/mpl-core'\n\nconst updateCollectionResponse = await updateCollectionPlugin(umi, {\n\ncollection: collectionSigner.publicKey,\n\nplugin: {\n\ntype: \"PermanentFreezeDelegate\",\n\nfrozen: false,\n\n},\n\n}).sendAndConfirm(umi);\n\nCommon Errors\nCannot add permanent plugin after creation\nPermanent plugins can only be added at Asset/Collection creation. You cannot add a Permanent Freeze Delegate to an existing Asset.\nAuthority mismatch\nOnly the plugin authority can freeze/thaw. Verify you're signing with the correct keypair.\nNotes\nOn creation only: Cannot be added after Asset/Collection exists\nForce approve: Can freeze even with conflicting plugins\nCollection behavior: Freezes all Assets at once, not individually\nPersists forever: Authority is never revoked, even after transfers\nUse for soulbound tokens by setting frozen: true with authority None\nFAQ\nHow do I create a soulbound (non-transferable) token?\nCreate the Asset with PermanentFreezeDelegate, set frozen: true, and set authority to None. The Asset can never be unfrozen or transferred.\nWhat's the difference between Freeze Delegate and Permanent Freeze Delegate?\nRegular Freeze Delegate authority is revoked on transfer and only works on Assets. Permanent Freeze Delegate persists forever, works on Collections, and uses forceApprove.\nCan I freeze individual Assets in a Collection?\nNo. When Permanent Freeze Delegate is on a Collection, freezing affects all Assets at once. Use Asset-level Permanent Freeze Delegate for individual control.\nCan a permanently frozen Asset be burned?\nOnly if there's also a Permanent Burn Delegate. Regular Burn Delegate cannot burn frozen Assets, but Permanent Burn Delegate uses forceApprove.\nRelated Plugins\nFreeze Delegate - Revocable freeze for temporary locking\nPermanent Transfer Delegate - Permanent transfer authority\nPermanent Burn Delegate - Burn even frozen Assets\nGlossary\nTermDefinition\nPermanent Plugin\nPlugin that can only be added at creation and persists forever\n\nforceApprove\nValidation that overrides other plugin rejections\n\nSoulbound\nNon-transferable token permanently frozen to a wallet\n\nCollection Freeze\nFreezing all Assets in a Collection at once","tokens":1712,"crawled_at":1791195144382}
+{"id":10485,"url":"https://docs.ethena.fi/protocol-overview/reserve-fund","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Reserve Fund | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nThe Reserve Fund is a pool of assets held by the protocol as an additional margin of safety for USDe.\nThe Reserve Fund was funded with a portion of the revenue generated by the protocol during periods of high revenue, and retains a balance that continues to support the backing of USDe. The amount of protocol revenue directed to the Reserve Fund on an ongoing basis is subject to governance. The percentage of revenue allocated to the Reserve Fund is currently 0%, with 100% being directed to incentive rewards, promotional distributions, and distribution incentives.\nThe Reserve Fund serves as a buffer in conditions where protocol revenue would otherwise be negative. If, across the diversified backing assets, the cost of maintaining positions exceeds the revenue earned from funding, lending, real-world assets, and liquid stablecoin rewards, the Reserve Fund is designed to bear that cost. This is designed so that periods of negative revenue are absorbed by the Reserve Fund rather than impairing the core reserves.\nThe Reserve Fund can also be deployed to address shortfalls in backing arising from the risks described in the Risks section, helping the protocol maintain full backing through stressed conditions.\nThe current size of the Reserve Fund can be viewed on the Transparency dashboard.\n\nLast updated 2 months ago\nWas this helpful?","tokens":360,"crawled_at":1791195126774}
+{"id":10486,"url":"https://docs.sui.io/getting-started/examples","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Example Apps | Sui Documentation","text":"Each example below ships as a runnable repository with its own README. Clone the repository, publish the Move packagePackageSmart contracts on Sui. to TestnetTestnetStaging network for testing changes before production deployment., and run the app.\n\nIf you are new to Sui, start with \"Hello, World!\" to install the toolchain and publish your first package, then come back here.\n\nMoveMoveAn open source programming language used for all activity on Sui. patterns​\n\nExampleWhat it demonstratesSource\nCapability pattern\nGating privileged functions behind an AdminCap instead of hardcoded addressAddressA unique, anonymous identity on a blockchain network. checks.\nsui-move-bootcamp/C1\n\nDerived objects\nPredicting an objectObjectThe basic unit of storage on Sui. ID before creation, and looking up objects by key without an indexer.\nsui-move-bootcamp/C5\n\nScenario testing\nMulti-transactionTransactionA number of commands that execute on inputs to define the result of the transaction. Move tests with test_scenario, including access control and transaction effects.\nsui-move-bootcamp/G1\n\nFrontend apps​\n\nExampleWhat it demonstratesSource\ndApp Kit starter\nWallet connection, network switching, and owned-object queries in a React app.\nsui-move-bootcamp/E2\n\nNFT minting app\nA shared registry Move package plus a frontend that mints through a programmable transaction block.\nsui-move-bootcamp/F1\n\nPlinko\nOnchain randomness in a house-managed game, with sponsored transactionsSponsored transactionWhen one address pays the gas fee for a transaction submitted by another address. and a payout table.\nplinko-poc\n\nData and indexing​\n\nExampleWhat it demonstratesSource\nReal-time event indexer\nA gRPCgRPC APIReplaces JSON-RPC on full nodes for data access. checkpointCheckpointCreated after transaction execution to provide a certified record of chain history. subscription that decodes BCS event data into structured TypeScript fields.\nsui-move-bootcamp/K1\n\nTo add an indexer to your own service rather than run this one, see the custom indexer guide.\n\nCapture the flag challenges​\n\nThe CTF repository holds capture-the-flag challenges. Each one deploys a deliberately vulnerable contract to Testnet and asks you to exploit it.\n\nChallengeWhat it teaches\nLootbox\nWhy functions that consume sui::random must be entry rather than public.\n\nMerchant using USDC\nPassing exact Coin<T> amounts to Move functions with splitCoins.\n\nStaking with time-accumulation\nHow time-based access control breaks when the client controls accumulation.\n\nRelated topics\n\nHello, World!\nAn overview of the Sui onboarding steps, from installing Sui and configuring a client to creating an address, getting test tokens, and deploying your first Move package.\nBuild a Custom Indexer\nBuild a custom indexer using the `sui-indexer-alt-framework` module. The example indexer demonstrates a sequential pipeline that extracts transaction digests from Sui checkpoints and stores them in a local PostgreSQL database, the default example storage backend.\n\nMove patterns\nFrontend apps\nData and indexing\nCapture the flag challenges\n\nWas this page helpful?","tokens":776,"crawled_at":1791195138238}
+{"id":10487,"url":"https://www.getfoundry.sh/reference/chisel/chisel","domain":"www.getfoundry.sh","chapter":"developer_specs","title":"chisel – foundry - Ethereum Development Framework","text":"Was this helpful?\n\nGenerated from chisel --help; see CLI reference versions. Regenerate this page instead of editing it directly.\n\nchisel\n\nFast, utilitarian, and verbose Solidity REPL\n\n$ chisel --help\n\nUsage: chisel [OPTIONS] [COMMAND]\n\nCommands:\nlist List all cached sessions\nload Load a cached session\nview View the source of a cached session\nclear-cache Clear all cached chisel sessions from the cache directory\neval Simple evaluation of a command without entering the REPL\nhelp Print this message or the help of the given subcommand(s)\n\nOptions:\n-j, --threads <THREADS>\nNumber of threads to use. Specifying 0 defaults to the number of\nlogical cores\n\n[alias: --jobs]\n\n--profile <PROFILE>\nThe configuration profile to use\n\n-h, --help\nPrint help (see a summary with '-h')\n\n-V, --version\nPrint version\n\nDisplay options:\n-v, --verbosity...\nVerbosity level of the log messages.\n\nPass multiple times to increase the verbosity (e.g. -v, -vv, -vvv).\n\nDepending on the context the verbosity levels have different meanings.\n\nFor example, the verbosity levels of the EVM are:\n- 2 (-vv): Print logs for all tests.\n- 3 (-vvv): Print execution traces for failing tests.\n- 4 (-vvvv): Print execution traces for all tests, and setup traces\nfor failing tests.\n- 5 (-vvvvv): Print execution and setup traces for all tests,\nincluding storage changes and\nbacktraces with line numbers.\n\n-q, --quiet\nDo not print log messages\n\n--json\nFormat log messages as JSON\n\n--md\nFormat log messages as Markdown\n\n--color <COLOR>\nThe color of the log messages\n\nPossible values:\n- auto: Intelligently guess whether to use color output (default)\n- always: Force color output\n- never: Force disable color output\n\nREPL options:\n--prelude <PRELUDE>\nPath to a directory containing Solidity files to import, or path to a\nsingle Solidity file.\n\nThese files will be evaluated before the top-level of the REPL,\ntherefore functioning as a prelude\n\n--no-vm\nDisable the default `Vm` import.\n\nThe import is disabled by default if the Solc version is less than\n0.6.2.\n\n--ir-minimum\nEnable viaIR with minimum optimization\n\nThis can fix most of the \"stack too deep\" errors while resulting a\nrelatively accurate source map.\n\nCache options:\n--force\nClear the cache and artifacts folder and recompile\n\nBuild options:\n--no-cache\nDisable the cache\n\n--no-dynamic-test-linking\nDisable dynamic test linking\n\n--skip <SKIP>...\nSkip building files whose names contain the given filter.\n\n`test` and `script` are aliases for `.t.sol` and `.s.sol`.\n\nLinker options:\n--libraries <LIBRARIES>\nSet pre-linked libraries\n\n[env: DAPP_LIBRARIES=]\n\nCompiler options:\n--ignored-error-codes <ERROR_CODES>\nIgnore solc warnings by error code\n\n-D, --deny <LEVEL>\nA compiler error will be triggered at the specified diagnostic level.\n\nReplaces the deprecated `--deny-warnings` flag.\n\nPossible values: - `never`: Do not treat any diagnostics as errors. -\n`warnings`: Treat warnings as errors. - `notes`: Treat both, warnings\nand notes, as errors.\n\nPossible values:\n- never: Always exit with zero code\n- warnings: Exit with a non-zero code if any warnings are found\n- notes: Exit with a non-zero code if any notes or warnings are\nfound\n\n--no-auto-detect\nDo not auto-detect the `solc` version\n\n--use <SOLC_VERSION>\nSpecify the solc version, or a path to a local solc, to build with.\n\nValid values are in the format `x.y.z`, `solc:x.y.z` or\n`path/to/solc`.\n\n--offline\nDo not access the network.\n\nMissing solc versions will not be installed.\n\n--use-literal-content\nChanges compilation to only use literal content and not URLs\n\n--no-metadata\nDo not append any metadata to the bytecode.\n\nThis is equivalent to setting `bytecode_hash` to `none` and\n`cbor_metadata` to `false`.\n\n--ast\nIncludes the AST as JSON in the compiler output\n\n--evm-version <VERSION>\nThe target EVM version\n\n--optimize [<OPTIMIZE>]\nActivate the Solidity optimizer\n\n[possible values: true, false]\n\n--optimizer-runs <RUNS>\nThe number of runs specifies roughly how often each opcode of the\ndeployed code will be executed across the life-time of the contract.\nThis means it is a trade-off parameter between code size (deploy cost)\nand code execution cost (cost after deployment). An `optimizer_runs`\nparameter of `1` will produce short but expensive code. In contrast, a\nlarger `optimizer_runs` parameter will produce longer but more gas\nefficient code\n\n--via-ir\nUse the Yul intermediate representation compilation pipeline\n\n--via-ssa-cfg\nTurn on SSA CFG-based code generation via the IR (experimental).\n\nThis passes `--via-ssa-cfg` to solc. Implies `--via-ir`. Requires\n`--experimental` to be set (as of Solidity 0.8.35+). This is false by\ndefault.\n\n--experimental\nEnable Solidity's experimental mode.\n\nThis passes `--experimental` to solc, which is required by Solidity\n0.8.35+ for experimental features.\n\n--extra-output <SELECTOR>...\nExtra output to include in the contract's artifact.\n\nExample keys: evm.assembly, ewasm, ir, irOptimized, metadata\n\nFor a full description, see\n[https://docs.soliditylang.org/en/v0.8.13/using-the-compiler.html#input-description](https://docs.soliditylang.org/en/v0.8.13/using-the-compiler.html#input-description)\n\n--extra-output-files <SELECTOR>...\nExtra output to write to separate files.\n\nValid values: metadata, ir, irOptimized, ewasm, evm.assembly\n\nProject options:\n-o, --out <PATH>\nThe path to the contract artifacts folder\n\n--revert-strings <REVERT>\nRevert string configuration.\n\nPossible values are \"default\", \"strip\" (remove), \"debug\"\n(Solidity-generated revert strings) and \"verboseDebug\"\n\n--build-info\nGenerate build info files\n\n--build-info-path <PATH>\nOutput path to directory that build info files will be written to\n\n--root <PATH>\nThe project's root path.\n\nBy default root of the Git repository, if in one, or the current\nworking directory.\n\n-C, --contracts <PATH>\nThe contracts source directory\n\n-R, --remappings <REMAPPINGS>\nThe project's remappings\n\n--remappings-env <ENV>\nThe project's remappings from the environment\n\n--cache-path <PATH>\nThe path to the compiler cache\n\n--lib-paths <PATH>\nThe path to the library folder\n\n--hardhat\nUse the Hardhat-style project layout.\n\nThis is the same as using: `--contracts contracts --lib-paths\nnode_modules`.\n\n[alias: --hh]\n\n--config-path <FILE>\nPath to the config file\n\nEVM options:\n-r, --rpc-url <URL>\nThe RPC endpoint\n\n[alias: --fork-url]\n\n-k, --insecure\nAllow insecure RPC connections (accept invalid HTTPS certificates).\n\nWhen the provider's inner runtime transport variant is HTTP, this\nconfigures the reqwest client to accept invalid certificates.\n\n--rpc-timeout <RPC_TIMEOUT>\nTimeout for the RPC request in seconds.\n\nThe specified timeout will be used to override the default timeout for\nRPC requests.\n\nDefault value: 45\n\n[env: ETH_RPC_TIMEOUT=]\n\n--no-proxy\nDisable automatic proxy detection.\n\nUse this in sandboxed environments (e.g., Cursor IDE sandbox, macOS\nApp Sandbox) where system proxy detection causes crashes. When\nenabled, HTTP_PROXY/HTTPS_PROXY environment variables and system proxy\nsettings will be ignored.\n\n--compute-units-per-second <CUPS>\nSets the number of assumed available compute units per second for this\nprovider.\n\ndefault value: 330\n\nSee also\n[https://docs.alchemy.com/reference/compute-units#what-are-cups-compute-units-per-second](https://docs.alchemy.com/reference/compute-units#what-are-cups-compute-units-per-second)\n\n--no-rpc-rate-limit\nDisables rate limiting for this node's provider.\n\nSee also\n[https://docs.alchemy.com/reference/compute-units#what-are-cups-compute-units-per-second](https://docs.alchemy.com/reference/compute-units#what-are-cups-compute-units-per-second)\n\n[alias: --no-rate-limit]\n\n--fork-block-number <BLOCK>\nFetch state from a specific block number over a remote endpoint.\n\nSee --rpc-url.\n\n--fork-retries <RETRIES>\nNumber of retries.\n\nSee --rpc-url.\n\n--fork-retry-backoff <BACKOFF>\nInitial retry backoff on encountering errors.\n\nSee --rpc-url.\n\n--no-storage-caching\nExplicitly disables the use of RPC caching.\n\nAll storage slots are read entirely from the endpoint.\n\nThis flag overrides the project's configuration file.\n\nSee --rpc-url.\n\n--initial-balance <BALANCE>\nThe initial balance of deployed test contracts\n\n--sender <ADDRESS>\nThe address which will be executing tests/scripts\n\n--ffi\nEnable the FFI cheatcode\n\n--live-logs\nWhether to show `console.log` outputs in realtime during script/test\nexecution\n\n--always-use-create-2-factory\nUse the create 2 factory in all cases including tests and\nnon-broadcasting scripts\n\n--create2-deployer <ADDRESS>\nThe CREATE2 deployer address to use, this will override the one in the\nconfig\n\nExecutor environment config:\n--code-size-limit <CODE_SIZE>\nEIP-170: Contract code size limit in bytes. Useful to increase this\nbecause of tests. By default, it is 0x6000 (~25kb)\n\n--chain <CHAIN>\nThe chain name or EIP-155 chain ID\n\n[alias: --chain-id]\n\n--gas-price <GAS_PRICE>\nThe gas price\n\n--block-base-fee-per-gas <FEE>\nThe base fee in a block\n\n[alias: --base-fee]\n\n--tx-origin <ADDRESS>\nThe transaction origin\n\n--block-coinbase <ADDRESS>\nThe coinbase of the block\n\n--block-timestamp <TIMESTAMP>\nThe timestamp of the block\n\n--block-number <BLOCK>\nThe block number\n\n--block-difficulty <DIFFICULTY>\nThe block difficulty\n\n--block-prevrandao <PREVRANDAO>\nThe block prevrandao value. NOTE: Before merge this field was mix_hash\n\n--block-gas-limit <BLOCK_GAS_LIMIT>\nThe block gas limit\n\n[alias: --gas-limit]\n\n--memory-limit <MEMORY_LIMIT>\nThe memory limit per EVM execution in bytes. If this limit is\nexceeded, a `MemoryLimitOOG` result is thrown.\n\nThe default is 128MiB.\n\n--disable-block-gas-limit\nWhether to disable the block gas limit checks\n\n[aliases: --no-block-gas-limit, --no-gas-limit]\n\n--enable-tx-gas-limit\nWhether to enable tx gas limit checks as imposed by Osaka (EIP-7825)\n\n[alias: --tx-gas-limit]\n\n--isolate\nWhether to enable isolation of calls. In isolation mode all top-level\ncalls are executed as a separate transaction in a separate EVM\ncontext, enabling more precise gas accounting and transaction state\nchanges\n\n--no-isolate\nWhether to disable isolation of calls\n\nNetworks:\n-n, --network <NETWORK>\nEnable a specific network family\n\n[possible values: ethereum, tempo]\n\n--celo\nEnable Celo network features\n\nWas this helpful?\n\nSuggest changes on GitHubLast updated: 29/09/2026, 10:21","tokens":2566,"crawled_at":1791195143397}
+{"id":10488,"url":"https://www.metaplex.com/docs/smart-contracts/core/plugins/permanent-burn-delegate","domain":"www.metaplex.com","chapter":"docs","title":"Permanent Burn Delegate | Metaplex Core","text":"The Permanent Burn Delegate Plugin provides irrevocable burn authority that persists forever. The delegate can burn Assets even when frozen, making it ideal for games and subscription services.\nWhat You'll Learn\nCreate Assets with permanent burn capability\nEnable collection-wide burn authority\nBurn frozen Assets (forceApprove behavior)\nUse cases: games, subscriptions, automated cleanup\n\nSummary\nThe Permanent Burn Delegate is a permanent plugin that can only be added at creation time. The delegate can burn the Asset at any time, even when the Asset is frozen.\nCan only be added at Asset/Collection creation\nAuthority persists forever (never revoked)\nUses forceApprove - can burn even when frozen\nCollection-level: allows burning any Asset in the Collection\nOut of Scope\nRegular burn delegate (see Burn Delegate), conditional burns, and Token Metadata burn authority.\nQuick Start\nJump to: Create Asset\nAdd PermanentBurnDelegate plugin at Asset/Collection creation\nSet the authority to your program or delegate address\nThe delegate can burn the Asset at any time, even if frozen\nPermanent vs Regular Burn Delegate\nFeatureBurn DelegatePermanent Burn Delegate\nAdd after creation\n✅ Yes\n❌ Creation only\n\nAuthority persists on transfer\n❌ Revokes\n✅ Persists forever\n\nCan burn frozen Assets\n❌ No\n✅ Yes (forceApprove)\n\nWorks with Collections\n❌ No\n✅ Yes\n\nEmergency destruction\n❌ Limited\n✅ Best choice\n\nChoose Burn Delegate for user-revocable burn permissions.\n\nChoose Permanent Burn Delegate for games, emergency destruction, or automated cleanup.\n\nCommon Use Cases\nGame mechanics: Destroy Assets when items are consumed, lost, or destroyed in-game\nSubscription expiration: Auto-burn expired subscription tokens even if frozen\nEmergency destruction: Remove compromised or unwanted Assets regardless of state\nCrafting systems: Burn ingredient NFTs when crafting (even if locked)\nTime-limited assets: Automatically destroy expired content\nCompliance: Remove Assets that violate terms, even if owner tries to freeze them\nWorks With\n\nMPL Core Asset\n✅\n\nMPL Core Collection\n✅\n\nBehaviours\nAsset: Allows burning of the Asset using the delegated address.\nCollection: Allows burning of any Asset in the collection using the collection authority. It does not burn all at once.\nArguments\nThe Permanent Burn Plugin doesn't contain any arguments to pass in.\nCreating an Asset with a Permanent Burn Plugin\nCreating an Asset with a Permanent Freeze plugin\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { create } from '@metaplex-foundation/mpl-core'\n\nconst assetSigner = generateSigner(umi)\n\nconst delegate = publicKey('33333333333333333333333333333')\n\nawait create(umi, {\n\nasset: assetSigner,\n\nname: 'My Asset',\n\nuri: 'https://example.com/my-asset.json',\n\nplugins: [\n\n{\n\ntype: 'PermanentBurnDelegate',\n\nauthority: { type: 'Address', address: delegate },\n\n},\n\n],\n\n}).sendAndConfirm(umi)\n\nCommon Errors\nCannot add permanent plugin after creation\nPermanent plugins can only be added at Asset/Collection creation. You cannot add a Permanent Burn Delegate to an existing Asset.\nAuthority mismatch\nOnly the plugin authority can burn. Verify you're signing with the correct keypair.\nNotes\nOn creation only: Cannot be added after Asset/Collection exists\nForce approve: Can burn even when frozen\nCollection behavior: Can burn any Asset in the Collection individually\nPersists forever: Authority is never revoked\nIrreversible: Burned Assets cannot be recovered\nFAQ\nWhat's the difference between Burn Delegate and Permanent Burn Delegate?\nRegular Burn Delegate cannot burn frozen Assets and is revoked on transfer. Permanent Burn Delegate can burn frozen Assets (forceApprove) and persists forever.\nCan Permanent Burn Delegate burn frozen Assets?\nYes. Permanent plugins use forceApprove, which overrides freeze rejections. This is useful for game mechanics where items must be destroyable.\nCan I add this to an existing Asset?\nNo. Permanent plugins can only be added at Asset creation time. Use regular Burn Delegate for existing Assets.\nHow does Collection-level Permanent Burn Delegate work?\nThe delegate can burn any individual Asset in the Collection, but not all at once. Each burn is a separate transaction.\nIs this safe to use?\nUse with caution. The delegate can burn Assets at any time without owner approval. Only assign to trusted programs or addresses.\nRelated Plugins\nBurn Delegate - Revocable burn authority\nPermanent Freeze Delegate - Permanent freeze authority\nPermanent Transfer Delegate - Permanent transfer authority\nGlossary\nTermDefinition\nPermanent Plugin\nPlugin that can only be added at creation and persists forever\n\nforceApprove\nValidation that overrides other plugin rejections\n\nCollection Burn\nAbility to burn any Asset in a Collection","tokens":1187,"crawled_at":1791195181864}
+{"id":10489,"url":"https://gov.uniswap.org/t/discretionary-budget-thread/25704","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Discretionary Budget Thread - Governance-Meta - Uniswap Governance","text":"Discretionary Budget Thread\n\nGovernance-Meta\n\nAbdullahUmar\n\nJuly 4, 2025, 3:24pm\n\n1\n\nDiscretionary Budget Thread\n\nAuthors: Uniswap Accountability Committee (UAC)\n\nAs per delegates’ request, we are publishing this forum thread as a way to disclose the status of any discretionary spending from the UAC budget. For context, the DAO voted to grant discretionary capabilities to the UAC for allocating capital towards high-impact initiatives. This budget provides the UAC with the necessary flexibility during extenuating and time-sensitive initiatives, as the customary budget requests require a 4-week or longer governance process, and time-limited or holiday-aligned deals may fall through.\n\nThis thread will be updated at the start of every month, reporting the expenditure—or lack thereof—from the previous month. Each update will include:\n\nThe current balance\n\nAdjusted balance (accommodating for UNI price fluctuation)\n\nThe corresponding surplus/deficit of the “Incentive Package Budget” Account. This Account holds UNI that is intended to be utilized for incentivizing pools on target chains, along with the associated distribution costs, like payments to Merkl.\n\nThe discretionary budget was instituted in December 2024.\n\nMechanism\n\nTo set limits on spending, the UAC will only be able to draw capital from the surplus while the surplus is at least 50% higher than the Current Balance.\n\nThis leaves a minimum 33.3% buffer for the price to decline and not cut into the payables associated with the balance.\n\nOnly incentive programs with $250k worth of funds or less can be used discretionarily.\n\nAll 5 of the UAC members have to agree that a sourced deal is “high-value.” Otherwise, without unanimous agreement, discretionary funding cannot be allocated.\n\n3 Likes\n\nGrow Uniswap on Plasma\n\nAbdullahUmar\n\nJuly 4, 2025, 3:28pm\n\n2\n\nUpdate: Jun 30, 2025\n\nNone of the discretionary budget was utilized during the month of June.\n\nBelow is the status of the Incentive Package Budget Account at month close.\n\n1086×1028 113 KB\n\nThe current balance stands at $890k, which is the total amount of yet-to-be-allocated incentives. Based on a UNI price of $7.13, this Account is at a surplus of $1,064,762, making the total current adjusted balance $1,954,762.\n\nAs it currently stands, 1.5x the current balance equates to $1,335,000. Therefore, the discretionary budget as of June 30th is $619,762. If the dollar value of the UNI in this account falls below $1,335,000, the discretionary budget cannot be utilized.\n\n3 Likes\n\nAbdullahUmar\n\nAugust 12, 2025, 8:15pm\n\n3\n\nUpdate: Jul 31, 2025\n\nNone of the discretionary budget was utilized during the month of July.\n\nBelow is the status of the Incentive Package Budget Account at month close.\n\n1086×1026 113 KB\n\nThe current balance stands at $890k, which is the total amount of yet-to-be-allocated incentives. Based on a UNI price of $9.06, this Account is at a surplus of $1,593,891, making the total current adjusted balance $2,483,891.\n\nAs it currently stands, 1.5x the current balance equates to $1,335,000. Therefore, the discretionary budget as of July 31st is $1,148,891. If the dollar value of the UNI in this account falls below $1,335,000, the discretionary budget cannot be utilized.\n\n1 Like\n\nAbdullahUmar\n\nSeptember 20, 2025, 1:08am\n\n4\n\nUpdate: Aug 31, 2025\n\nNone of the discretionary budget was utilized during the month of August.\n\nBelow is the status of the Incentive Package Budget Account at month close.\n\n1136×1076 178 KB\n\nThe current balance stands at $890k, which is the total amount of yet-to-be-allocated incentives. Based on a UNI price of $9.41, this Account is at a surplus of $1,689,847, making the total current adjusted balance $2,579,847.\n\nAs it currently stands, 1.5x the current balance equates to $1,335,000. Therefore, the discretionary budget as of August 31st is $1,244,847. If the dollar value of the UNI in this account falls below $1,335,000, the discretionary budget cannot be utilized.\n\n1 Like\n\nTané Delegate Platform\n\nAbdullahUmar\n\nOctober 8, 2025, 3:56am\n\n5\n\nUpdate: Sep 30, 2025\n\nNone of the discretionary budget was utilized during the month of September, but the UAC has indicated its intent to eventually allocate $250k UNI from this budget for Plasma incentives. Once the allocation materializes, we will adjust the associated accounts and provide an update in this thread. The Plasma allocation was voted by all 5 of the UAC members as prudent. The full proposal is viewable here.\n\nBelow is the status of the Incentive Package Budget Account at month close.\n\n1030×960 247 KB\n\nThe current balance stands at $890k, which represents the total amount of yet-to-be-allocated incentives. Based on a UNI price of $7.50, this Account is at a surplus of $1,166,201, bringing the total current adjusted balance to $2,056,201.\n\nAs it currently stands, 1.5× the current balance equates to $1,335,000. Therefore, the discretionary budget as of September 30th is $721,201. If the dollar value of the UNI in this account falls below $1,335,000, the discretionary budget cannot be utilized.\n\n4 Likes\n\nAbdullahUmar\n\nNovember 11, 2025, 12:04am\n\n6\n\nUpdate: Oct 31, 2025\n\nNone of the discretionary budget was utilized during the month of October.\n\nThe Celo incentives concluded last month. Since we budgeted the allocation in dollar terms, there was surplus UNI from the incentives wallet that we returned to our main wallet. This led to an inflow of ~14,195 UNI. Therefore, the current balance in UNI terms has increased, while the USD balance stays constant at $890k, adding 14k UNI of surplus.\n\nPlasma incentives have not yet been allocated. The tentative allocation timeline is late November. This allows more flexibility managing the budget due to October’s UNI price decline.\n\nBelow is the status of the Incentive Package Budget Account at month close.\n\n1084×1026 113 KB\n\nThe current balance stands at $890k, which represents the total amount of yet-to-be-allocated incentives. Based on a UNI price of $5.75, this Account is at a surplus of $768,046, bringing the total current adjusted balance to $1,658,046.\n\nAs it currently stands, 1.5× the current balance equates to $1,335,000. Therefore, the discretionary budget as of October 31st is $323,046. If the dollar value of the UNI in this account falls below $1,335,000, the discretionary budget cannot be utilized.\n\n1 Like\n\nUniswap Governance Community Calls\n\nAbdullahUmar\n\nDecember 9, 2025, 12:04pm\n\n7\n\nUpdate: Nov 30, 2025\n\nNone of the discretionary budget was utilized during the month of November.\n\nAfter an internal UAC vote, we have decided not allocate incentives towards the Plasma incentives this month. The surplus amount passes the necessary threshold (as seen below), however, the margin of safety is presently quite low. With only $297,094 in the surplus, we feel more comfortable allocating UNI on Plasma once this margin strengthens.\n\nThe Plasma team has also paused their side of the incentives for now, after allocating ~$800k. We will monitor incentive timing actively and coordinate with Plasma accordingly.\n\nBelow is the status of the Incentive Package Budget Account at month close.\n\n1086×1032 113 KB\n\nThe current balance stands at $890k, which represents the total amount of yet-to-be-allocated incentives. Based on a UNI price of $5.66, this Account is at a surplus of $742,094, bringing the total current adjusted balance to $1,632,094.\n\nAs it currently stands, 1.5× the current balance equates to $1,335,000. Therefore, the discretionary budget as of November 30th is $297,094. If the dollar value of the UNI in this account falls below $1,335,000, the discretionary budget cannot be utilized.\n\n2 Likes\n\nUniswap Ecosystems Incentives Initiative (UEII) Update Thread\n\nUniswap Council (UC): Season 4 Report\n\nAbdullahUmar\n\nJanuary 19, 2026, 5:00pm\n\n8\n\nUpdate: Dec 31, 2025\n\nNone of the discretionary budget was utilized during the month of December.\n\nBelow is the status of the Incentive Package Budget Account at month close.\n\n1088×1030 113 KB\n\nThe current balance stands at $1.07M, which represents the total amount of yet-to-be-allocated incentives. Based on a UNI price of $5.65, this Account is at a surplus of $754,785, bringing the total current adjusted balance to $1,824,785.\n\nAs it currently stands, 1.5× the current balance equates to $1,605,000. Therefore, the discretionary budget as of December 31st is $219,785. If the dollar value of the UNI in this account falls below $1,605,000, the discretionary budget cannot be utilized.\n\nThe total balance in December increased by 34,615 UNI ($180,000) for disbursing the Oku maintenance payments for Gnosis, Mantle, and Linea.\n\n2 Likes\n\nAbdullahUmar\n\nFebruary 9, 2026, 11:29pm\n\n9\n\nUpdate: Jan 31, 2026\n\nNone of the discretionary budget was utilized during the month of January. A single outflow of 37,500 UNI was completed to facilitate payment for Oku from Proposal 92.\n\nBelow is the status of the Incentive Package Budget Account at month close.\n\n749×698 17.6 KB\n\nThe current balance stands at $890k, which represents the total amount of yet-to-be-allocated incentives. Based on a UNI price of $3.95, this Account is at a surplus of $237,609, bringing the total current adjusted balance to $1,127,609.\n\nAs it currently stands, 1.5× the current balance equates to $1,335,000. Therefore, the discretionary budget as of January 31st is $0, as the dollar value of the UNI held in this account is below the required threshold. Until the account exceeds $1,335,000, the discretionary budget cannot be utilized.\n\n2 Likes\n\nAbdullahUmar\n\nMarch 9, 2026, 9:30pm\n\n11\n\nUpdate: Feb 28, 2026\n\nAt the end of February, the UAC closed out the Incentive Package Budget account, along with all other accounts. By extension, the discretionary budget is no longer active. This decision stems from a general reorganization of some of the UAC’s historical mandates, namely, the operational responsibility for disbursing incentives across various chains. Due to emergent tax and legal complexities post-DUNI adoption, the UAC, in its subsequent seasons, does not intend to act as the entity responsible for disbursing cross-chain incentives—at least not in the manner that has been conducted historically.\n\nThe remaining account balance at the end of Feb amounted to 285,471 UNI, or $1,141,883 (@ UNI = $4). This capital was fully returned to the DUNI’s multisig, operated by the Ministerial Agent and Administrator. The UAC operations and incentive multisigs therefore hold zero UNI at the moment.\n\n1 Like\n\nUniswap Governance Community Calls\n\n[RFC] Deploy Uniswap V3 on Gensyn\n\nUniswap Council (UC): Season 4 Report\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[RFC] Discretionary Budget from UAC for Co-Incentive Campaigns\n\nRequests for Comment\n\n12\n\n491\n\nDecember 24, 2024\n\nRevocation of Uniswap Growth's Discretionary Budget for Co-Incentive Campaigns\n\nRequests for Comment\n\n7\n\n698\n\nApril 22, 2025\n\nUniswap Accountability Committee (UAC): Season 3 Report\n\nRequests for Comment\n\n9\n\n1053\n\nMay 6, 2025\n\nUniswap Accountability Committee (UAC): Season 2 Report\n\nRequests for Comment\n\n11\n\n1175\n\nSeptember 23, 2024\n\nUniswap Deployments Accountability Committee [Update Thread]\n\nGovernance-Meta\n\n15\n\n4579\n\nApril 18, 2025","tokens":2799,"crawled_at":1791195185144}
+{"id":10490,"url":"https://docs.ethena.fi/protocol-overview/peg-arbitrage-mechanism","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Peg Arbitrage Mechanism | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nThere is one presently available trade strategy available to users to profit from a price dislocation of USDe in external markets from what it is actually worth:\nCross Market Arbitrage: purchasing or selling USDe into the protocol mint & redeem contract when USDe price has diverged from $1.\nTrade Strategies\nIt's important to keep in mind:\n\nUSDe is backed strictly by the protocol backing assets.\n\nUSDe is able to be minted & redeemed on demand by authorized, whitelisted users. This means that at any time, approved users are able to ramp in & out.\n\nabout 0.50% of backing assets are typically held in stablecoin form and available in the Minting Smart Contract to enable on-demand redemptions. This balance is systematically replenished from the 4% of the backing assets of USDe held in stablecoins that are readily available from multiple custodians.\n\nThe value & amount of USDe's underlying backing is generally unaffected by any dislocations or rapid movements of price across any Centralized/Decentralized Spot Market, AMM Protocols, etc., though fluctuations in those markets may cause temporary dislocations in the secondary market price of USDe as the market's \"reference assets\" for the target peg.\n\nThe value of the reserve underpinning USDe is generally unaffected by the removal of liquidity in volatile markets.\n\n1. Cross Market Arbitrage\nThis strategy enables any user approved to mint/redeem to profit from the difference between the price/amount users' are able to mint/redeem USDe with Ethena & the value of USDe in an external market. An external market includes all centralized & decentralized spot markets such as \"USDe/USDC\" and AMM Protocols such as Uniswap or Curve.\nIf USDe is worth LESS in an external market than from Ethena directly, a user could:\n\nBuy 1x USDe at 0.95 from Curve using USDT.\n\nRedeem 1x USDe at 1.00 from Ethena receiving USDT.\n\nProfit.\n\nIf USDe is worth MORE in an external market than from Ethena Labs, a user could:\n\nMint USDe using USDT from Ethena.\n\nSell the USDe in the Curve pool for > 1.00 for USDT.\n\nProfit.\n\nLast updated 2 years ago\nWas this helpful?","tokens":550,"crawled_at":1791195188446}
+{"id":10491,"url":"https://www.metaplex.com/docs/smart-contracts/core/plugins/verified-creators","domain":"www.metaplex.com","chapter":"docs","title":"Verified Creator Plugin | Metaplex Core","text":"The Verified Creators Plugin stores a list of verified creator signatures on Assets or Collections. Prove creatorship publicly without affecting royalty distribution.\nWhat You'll Learn\nAdd verified creators to Assets and Collections\nVerify creator signatures\nRemove creators from the list\nUnderstand the verification workflow\n\nSummary\nThe Verified Creators plugin is an Authority Managed plugin that stores creator addresses with verification status. Unlike Token Metadata, these creators are NOT used for royalty distribution (use the Royalties plugin for that).\nUpdate authority adds unverified creators\nCreators verify themselves by signing\nVerified creators must unverify before removal\nAssets inherit creators from their Collection\nOut of Scope\nRoyalty distribution (use Royalties plugin), Token Metadata creator arrays, and automatic verification.\nQuick Start\nJump to: Add to Asset · Add Creator · Remove Creator\nAdd the Verified Creators plugin with initial creators\nCreators verify themselves using updatePlugin\nTo remove: creator unverifies, then update authority removes\nVerified Creators vs Autograph\nFeatureVerified CreatorsAutograph\nWho can add\nUpdate authority only\nAnyone (after enabled)\n\nPurpose\nProve creatorship\nCollectible signatures\n\nVerification\nCreators verify themselves\nNo verification needed\n\nRemoval\nMust unverify first\nOwner can remove anytime\n\nUsed for royalties\n❌ No\n❌ No\n\nUse Verified Creators for proving authentic creatorship.\n\nUse Autograph for collectible signatures from fans/celebrities.\n\nCommon Use Cases\nTeam attribution: Designer, developer, and founder each verify their involvement\nCo-creator proof: Multiple artists verify collaboration on a piece\nBrand verification: Official brand accounts verify partnership\nAuthenticity proof: Original creator verifies they created the Asset\nHistorical record: Document who was involved in creating a Collection The update authority can:\nAdd the plugin.\nAdd unverified creators to the creators array.\nCan remove unverified creators. To remove verified creators they must unverify themselves first.\nCan verify themselves. To verify a creator the updatePlugin instruction has to be signed by the public key that was added by the update authority to the creators array.\nWorks With\n\nMPL Core Asset\n✅\n\nMPL Core Collection\n✅\n\nArguments\nThe verifiedCreator Plugin requires the following arguments in a VerifiedCreatorsSignature Array:\nArgValue\naddress\npublicKey\n\nmessage\nstring\n\nAssets inherit the Creators array from the Collection.\n\nAdding the autograph Plugin to an Asset code example\nAdding a verified Creators Plugin to an MPL Core Asset\n\nThis snippet assumes that the umi identity is the update authority of the asset.\nimport {\n\naddPlugin,\n\n} from '@metaplex-foundation/mpl-core'\n\nawait addPlugin(umi, {\n\nasset: asset.publicKey,\n\nplugin: {\n\ntype: 'VerifiedCreators',\n\nsignatures: [\n\n{\n\naddress: umi.identity.publicKey,\n\nverified: true,\n\n},\n\n},\n\n}).sendAndConfirm(umi)\n\nAdding a different Creator to an Asset code example\nAdding a different Creator to an MPL Core Asset\n\nThis snippet assumes that the umi identity is the update authority of the asset to add a unverified Creator.\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { updatePlugin, fetchAsset } from '@metaplex-foundation/mpl-core'\n\nconst asset = await fetchAsset(umi, assetAddress.publicKey, {\n\nskipDerivePlugins: false,\n\n})\n\nconst publicKeyToAdd = publicKey(\"abc...\")\n\n// The new autograph that you want to add\n\nconst newCreator = {\n\naddress: publicKeyToAdd,\n\nverified: false,\n\n}\n\n// Add the new autograph to the existing signatures array\n\nconst updatedCreators = [...asset.verifiedCreators.signatures, newCreator]\n\nawait updatePlugin(umi, {\n\nasset: asset.publicKey,\n\nplugin: {\n\ntype: 'VerifiedCreators',\n\nsignatures: updatedCreators,\n\n},\n\nauthority: umi.identity,\n\n}).sendAndConfirm(umi)\n\nAfter adding the unverified Creator they can verify themselves using the updatePlugin function again. This snippet assumes that the umi identity is the Creator.\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { updatePlugin, fetchAsset } from '@metaplex-foundation/mpl-core'\n\nconst asset = await fetchAsset(umi, assetAddress.publicKey, {\n\nskipDerivePlugins: false,\n\n})\n\nconst publicKeyToVerify = publicKey(\"abc...\")\n\n// The creator that you want to verify\n\nconst updatedCreators = asset.verifiedCreators.signatures.map(creator => {\n\nif (creator.address === publicKeyToVerify) {\n\nreturn { ...creator, verified: true };\n\n}\n\nreturn creator;\n\n});\n\nawait updatePlugin(umi, {\n\nasset: asset.publicKey,\n\nplugin: {\n\ntype: 'VerifiedCreators',\n\nsignatures: updatedCreators,\n\n},\n\nauthority: umi.identity,\n\n}).sendAndConfirm(umi)\n\nRemoving a Creator from an Asset code example\nRemoving a Creator from an MPL Core Asset\n\nOnly the update authority can remove creators. To remove the creator it has to be verified:false or the update authority itself. Therefore the update will be done in two steps. If you are able to sign with the update authority and the creator at the same time this could be done in one transaction combining both instructions.\nSet verified:false This snippet assumes that umi.identity is the creator that you want to remove\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { updatePlugin, fetchAsset } from '@metaplex-foundation/mpl-core'\n\nconst asset = await fetchAsset(umi, assetAddress.publicKey, {\n\nskipDerivePlugins: false,\n\n})\n\n// The Publickey of the creator that you want to remove\n\nconst publicKeyToRemove = publicKey(\"abc...\")\n\nconst modifiedCreators = signatures.map(signature =>\n\nsignature.address === creator.publicKey\n\n? { ...signature, verified: false }\n\n: signature\n\n);\n\nawait updatePlugin(umi, {\n\nasset: asset.publicKey,\n\nplugin: {\n\ntype: 'VerifiedCreators',\n\nsignatures: modifiedCreators,\n\n},\n\nauthority: umi.identity, // Should be the creator\n\n}).sendAndConfirm(umi)\n\nremove the creator This snippet assumes that umi.identity is the update authority\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { updatePlugin, fetchAsset } from '@metaplex-foundation/mpl-core'\n\nconst asset = await fetchAsset(umi, assetAddress.publicKey, {\n\nskipDerivePlugins: false,\n\n})\n\n// The Publickey of the creator that you want to remove\n\nconst publicKeyToRemove = publicKey(\"abc...\")\n\nconst creatorsToKeep = asset.verifiedCreators.signatures.filter(\n\n(creator) => creator.address !== publicKeyToRemove\n\n);\n\nawait updatePlugin(umi, {\n\nasset: asset.publicKey,\n\nplugin: {\n\ntype: 'VerifiedCreators',\n\nsignatures: creatorsToKeep,\n\n},\n\nauthority: umi.identity, // Should be the update authority\n\n}).sendAndConfirm(umi)\n\nAdding the verified Creators Plugin to a Collection code example\nAdd verified Creators Plugin to Collection\n\nThis snippet assumes that the umi.identity is the update authority\nimport { addCollectionPlugin } from '@metaplex-foundation/mpl-core'\n\nawait addCollectionPlugin(umi, {\n\ncollection: collection.publicKey,\n\nplugin: {\n\ntype: 'VerifiedCreators',\n\nsignatures: [\n\n{\n\naddress: umi.identity.publicKey,\n\nverified: true,\n\n},\n\n},\n\n}).sendAndConfirm(umi)\n\nCommon Errors\nAuthority mismatch\nOnly the update authority can add the plugin or add new creators. Only the creator themselves can verify their own signature.\nCreator already verified\nThe creator has already verified themselves. No action needed.\nCannot remove verified creator\nA verified creator must unverify themselves before the update authority can remove them.\nNotes\nVerified Creators are NOT used for royalty distribution (use Royalties plugin)\nCreators must verify themselves—update authority cannot verify on their behalf\nA creator must unverify before they can be removed\nAssets inherit the creators array from their Collection\nQuick Reference\nVerification Workflow\nStepActionWho\n1\nAdd unverified creator\nUpdate Authority\n\n2\nVerify creator\nCreator signs\n\n3\nUnverify (optional)\nCreator signs\n\n4\nRemove (optional)\nUpdate Authority\n\nPermission Matrix\nActionUpdate AuthorityCreator\nAdd plugin\n✅\n❌\n\nAdd unverified creator\n✅\n❌\n\nVerify creator\n❌\n✅ (self only)\n\nUnverify creator\n❌\n✅ (self only)\n\nRemove unverified creator\n✅\n❌\n\nFAQ\nHow is this different from the Token Metadata creator array?\nIn Token Metadata, the creator array was used for royalty distribution. In Core, Verified Creators is purely for proof of creatorship - use the Royalties plugin for royalty distribution.\nCan the update authority verify a creator?\nNo. Each creator must verify themselves by signing the transaction. This ensures authentic proof of creatorship.\nWhy can't I remove a verified creator?\nTo remove a verified creator, they must first unverify themselves. This prevents unauthorized removal of verified creators.\nDo Assets automatically get the Collection's verified creators?\nYes. Assets inherit the creators array from their Collection. Individual Assets can also have their own Verified Creators plugin with different creators.\nCan I use this for co-creator attribution?\nYes. This is a common use case—multiple creators (designer, developer, artist) can all verify their involvement in creating an Asset or Collection.\nGlossary\nTermDefinition\nVerified Creator\nCreator who has signed to confirm their involvement\n\nUnverified Creator\nCreator added by update authority but not yet confirmed\n\nVerification\nCreator signing to prove authentic creatorship\n\nRoyalties Plugin\nSeparate plugin for royalty distribution (not this one)\n\nCreator Array\nList of addresses associated with an Asset/Collection\n\nRelated Plugins\nAutograph - Collectible signatures from anyone (fans, celebrities)\nRoyalties - Set royalty distribution (separate from verified creators)\nImmutableMetadata - Lock metadata permanently","tokens":2409,"crawled_at":1791195220759}
+{"id":10492,"url":"https://gov.uniswap.org/t/temp-check-protocol-fee-expansion-eight-more-chains-and-remaining-mainnet-v3-pools/26035","domain":"gov.uniswap.org","chapter":"governance_daos","title":"[Temp Check] Protocol Fee Expansion: Eight More Chains and Remaining Mainnet v3 Pools - Temperature Check - Uniswap Governance","text":"[Temp Check] Protocol Fee Expansion: Eight More Chains and Remaining Mainnet v3 Pools\n\nTemperature Check\n\nhaydenadams\n\nFebruary 18, 2026, 8:35pm\n\n1\n\nThis is the first proposal to use the new governance process approved in UNIfication. The new process only applies to fee parameter updates, where proposals can bypass the RFC stage and go directly to a five-day Snapshot followed by an onchain vote. This allows for faster updates to protocol fees, while retaining the security of onchain governance.\n\nSnapshot vote here: https://snapshot.org/#/s:uniswapgovernance.eth/proposal/0x0242a914c60945d25873d2a98c6abd9f69cb889c6616e27f3c0ab759f9e8d783\n\nSince UNIfication went live in late December we have been monitoring protocol fees, which were rolled out gradually to ensure protocol health. This started with v2 and select v3 pools on Ethereum mainnet. This rollout has gone well, with market-adjusted TVL up on Ethereum mainnet since December. The burn system is working as expected, permissionlessly converting fees in many different tokens into UNI burns.\n\nNow, we propose to:\n\nExpand protocol fees on v2 and v3 to Arbitrum, Base, Celo, OP Mainnet, Soneium, X Layer, Worldchain, and Zora\n\nEnable protocol fees on all v3 pools via a new tier-based v3OpenFeeAdapter on mainnet and the above L2s\n\nImplementation Details\n\nExpand protocol fees to L2s and burn UNI on mainnet\n\nThis proposal introduces v2 and v3 protocol fees on eight chains. Fees on each chain will be routed to the TokenJar on that respective chain.\n\nUNI burned on L2s doesn’t stay on L2s - it is bridged back to mainnet and sent to 0xdead. This uses the same infrastructure used for burning Unichain sequencer fees (OptimismBridgedResourceFirepit for OP Stack chains, and ArbitrumBridgedResourceFirepit for Arbitrum).\n\nEnable fees on all v3 pools\n\nThe current v3FeeAdapter manages protocol fees pool by pool and governance maintains a list of individual pools and their fee levels. Today, those pools account for a significant majority of v3 volume on Ethereum mainnet.\n\nv3OpenFeeAdapter replaces this with a tier-based system. Protocol fees are set uniformly across all pools sharing the same LP fee tier. For example, all 1bps LP fee pools could have protocol fees set to 25%. Any pool automatically gets the default protocol fee for its tier, no governance action is needed. This means if this proposal passes, protocol fees will be active on every v3 pool. Governance retains the ability to override fees on individual pools.\n\nProposal Spec\n\nPre-proposal - complete before onchain vote:\n\n/// For each L2:\n\n/// Deploy the TokenJar\n\nTokenJar tokenJar = new TokenJar{salt: SALT_TOKEN_JAR}();\n\n/// Deploy the chain-specific Releaser\n\n/// OP Stack (Optimism, Base, Zora, Worldchain, etc.):\n\nOptimismBridgedResourceFirepit releaser = new OptimismBridgedResourceFirepit{salt: SALT_RELEASER}(RESOURCE, THRESHOLD, address(tokenJar));\n\n/// Arbitrum:\n\nArbitrumBridgedResourceFirepit releaser = new ArbitrumBridgedResourceFirepit{salt: SALT_RELEASER}(RESOURCE, L1_RESOURCE, THRESHOLD, address(tokenJar));\n\n/// Set the releaser on the TokenJar (must be before ownership transfer)\n\ntokenJar.setReleaser(address(releaser));\n\n/// Set the thresholdSetter on the Releaser (must be before ownership transfer)\n\nreleaser.setThresholdSetter(TIMELOCK_ALIAS);\n\n/// Transfer ownership of the TokenJar and Releaser to governance\n\ntokenJar.transferOwnership(TIMELOCK_ALIAS);\n\nreleaser.transferOwnership(TIMELOCK_ALIAS);\n\n/// For each L2 and Mainnet:\n\n/// Deploy the V3OpenFeeAdapter\n\nV3OpenFeeAdapter v3OpenFeeAdapter = new V3OpenFeeAdapter{salt: SALT_FEE_ADAPTER}(address(V3_FACTORY), address(tokenJar));\n\n/// Set the feeSetter (must be before ownership transfer)\n\nv3OpenFeeAdapter.setFeeSetter(TIMELOCK_ALIAS); // L2\n\nv3OpenFeeAdapter.setFeeSetter(TIMELOCK); // Mainnet\n\n/// Transfer ownership to governance\n\nv3OpenFeeAdapter.transferOwnership(TIMELOCK_ALIAS); // L2\n\nv3OpenFeeAdapter.transferOwnership(TIMELOCK); // Mainnet\n\n/// For Mainnet only:\n\n/// Deploy the Firepit (mainnet-only releaser, burns directly)\n\nFirepit releaser = new Firepit{salt: SALT_RELEASER}(RESOURCE, THRESHOLD, address(tokenJar));\n\n/// Set the releaser on the TokenJar (must be before ownership transfer)\n\ntokenJar.setReleaser(address(releaser));\n\n/// Set the thresholdSetter on the Releaser (must be before ownership transfer)\n\nreleaser.setThresholdSetter(TIMELOCK);\n\n/// Transfer ownership of the TokenJar and Releaser to governance\n\ntokenJar.transferOwnership(TIMELOCK);\n\nreleaser.transferOwnership(TIMELOCK);\n\nIn this proposal, if passed:\n\n/// For each L2:\n\n/// Set the owner of the V3 Factory to the V3OpenFeeAdapter\n\nV3_FACTORY.setOwner(address(v3OpenFeeAdapter));\n\n/// Set the recipient of V2 protocol fees to the TokenJar\n\nV2_FACTORY.setFeeTo(address(tokenJar));\n\n/// For Mainnet:\n\n/// Transfer V3 Factory ownership through the V3OpenFeeAdapter\n\nv3OpenFeeAdapter.setFactoryOwner(address(v3OpenFeeAdapter));\n\nGovernance Process\n\nPlease note that because of GovernorBravo’s limit of 10 actions per proposal, there will be two separate onchain votes posted in parallel. One proposal will include the change to mainnet’s fee controller and turn on fees on Base, OP Mainnet, and Arbitrum, the other will turn on fees on Celo, Soneium, Worldchain, X Layer, and Zora.\n\n7 Likes\n\n[Temp Check] Activate v4 Protocol Fees\n\nArana Digital Delegate Platform\n\nSEEDGov Delegate Platform\n\nManugotsuka\n\nFebruary 23, 2026, 5:19pm\n\n2\n\nThe following reflects the views of L2BEAT’s governance team, composed of @kaereste and @Manugotsuka, and it’s based on their combined research, fact-checking, and ideation.\n\nWe voted FOR.\n\nWe view it as a natural continuation of the UNIfication framework approved in December, extending the existing fee collection and UNI burn architecture to additional chains and replacing the curated v3 allowlist with a universal adapter. Fee parameters remain unchanged. Before voting, we asked our research team to validate the full implementation, including contract behavior and burn mechanics.\n\nFor a detailed technical breakdown of what was verified, what remains unpublished, and the associated risks, please see the full analysis below. This review was conducted by the L2BEAT Research Team as part of the independent technical due diligence we require before voting on proposals of this scope.\n\nWhat happened in December\n\nProposal #93 “UNIfication” passed in December 2025. It burned 100M UNI, turned on protocol fees for V2 and V3 on Ethereum mainnet, and approved a 40M UNI growth budget for Uniswap Labs over two years. In return, Labs eliminated all interface, wallet, and API fees.\n\nUNIfication deployed three new contracts:\n\nTokenJar - an immutable sink that collects fee tokens from pools. Only a designated releaser can withdraw.\n\nFirepit - the releaser on mainnet. A searcher pays a fixed UNI amount (4,000 UNI), receives the accumulated fee tokens, and the UNI paid gets burnt, transferred to 0xdead .\n\nV3FeeAdapter - a Merkle-proof-based adapter that acts as the V3 Factory owner and sets protocol fees only on pools included in a curated allowlist (roughly 80-95% of mainnet volume).\n\nWhat’s being proposed now\n\nThe Temp Check - authored by Hayden Adams - does two things:\n\n1. Expand protocol fees to eight L2s: Arbitrum, Base, Celo, OP Mainnet, Soneium, Worldchain, X Layer, and Zora. Both V2 and V3 pools are on each chain.\n\n2. Replace the curated Merkle adapter with an open one. The new V3OpenFeeAdapter drops the allowlist entirely. Every V3 pool inherits a protocol fee by default. Governance can exempt individual pools, but the default is fees on.\n\nDue to GovernorBravo’s 10-action limit, execution splits into two parallel proposals:\n\nProposal A: Mainnet V3OpenFeeAdapter + Base, OP Mainnet, Arbitrum\n\nProposal B: Celo, Soneium, Worldchain, X Layer, Zora\n\nHow the money flows (and burns)\n\nThe fee collection and burn architecture extends the mainnet system to L2s with chain-specific bridging:\n\nPools (v2/v3) on each chain\n│\n▼\nTokenJar ─── Immutable fee sink. Holds all collected tokens.\n│\n▼\nReleaser ─── Searcher pays UNI threshold, receives fee tokens.\n│\n├─ Ethereum: Firepit ─── UNI sent to 0xdead directly\n├─ OP Stack: OptimismBridgedResourceFirepit ─── bridges UNI to L1 0xdead\n└─ Arbitrum: ArbitrumBridgedResourceFirepit ─── bridges UNI to L1 0xdead\n\nThe protocol never converts fee tokens into UNI. Instead, it relies on a searcher auction: fee tokens accumulate in the TokenJar until a searcher decides the pot is worth more than the fixed UNI cost. The searcher pays 4,000 UNI (mainnet) or 2,000 UNI (L2s), receives all accumulated tokens, and the UNI is burned. The design avoids DEX routing, slippage management, and oracle dependency - burn frequency depends entirely on searcher competition and accumulated value.\n\nOn L2s, UNI doesn’t burn locally. It bridges to Ethereum L1 first, via L2StandardBridge on OP Stack chains, via L2GatewayRouter on Arbitrum - and once the withdrawal finalises, it is burnt by transfer to the 0xdead address.\n\nThe V3OpenFeeAdapter: from allowlist to all pools\n\nThe old adapter required a Merkle proof to set fees on a pool - governance curated the list, targeting pools where Uniswap held 90%+ market share to minimize LP attrition risk. The new adapter inverts the default:\n\nMerkle-based (current)\nOpen adapter (proposed)\n\nNew pools\n\nNo fee unless added to Merkle tree\n\nFee on - inherits tier default\n\nOpt-out\n\nNot in the tree = no fee\n\nOnly via governance poolOverride to zero\n\nCoverage\n\n~80-95% of volume\n\n100% of V3 pools\n\nThe adapter resolves fees through a three-level waterfall: pool-specific override, then fee-tier default, then global default. A ZERO_FEE_SENTINEL (value 255) distinguishes “not configured” from “explicitly exempt.” Anyone can call triggerFeeUpdate() to apply the current fee to any pool - no governance action required.\n\nFee parameters are identical to December’s UNIfication. No increase:\n\nLP Fee Tier\nProtocol Take\nEffective Protocol Fee\n\n0.01%\n\n1/4 of LP fees\n\n~0.0025%\n\n0.05%\n\n1/4 of LP fees\n\n~0.0125%\n\n0.30%\n\n1/6 of LP fees\n\n~0.05%\n\n1.00%\n\n1/6 of LP fees\n\n~0.167%\n\nRisks\n\nThe shift from allowlist to universal bets that Uniswap’s network effects hold across the full pool spectrum - not just popular pairs. The risk is economic and reversible (governance can exempt pools), not a security concern.\n\nWhat we verified\n\nWe reviewed the source code on the protocol-fees repository (main branch, no pinned commit hash provided)\n\nTokenJar: Immutable fee sink, onlyReleaser withdrawal - confirmed.\n\nFirepit: Constructor hardcodes RESOURCE_RECIPIENT = address(0xdead) - confirmed.\n\nOptimismBridgedResourceFirepit: Two-stage collect-then-bridge via L2StandardBridge.withdrawTo() to L1 0xdead - confirmed. Covers Base, OP Mainnet, Soneium, Worldchain, Zora.\n\nArbitrumBridgedResourceFirepit: Same pattern via L2GatewayRouter.outboundTransfer() - confirmed.\n\nV3OpenFeeAdapter: Permissionless waterfall fee resolution with sentinel for explicit zero - confirmed.\n\nFee parameters: Packed values (0x44, 0x66) match original UNIfication deployer - confirmed.\n\nOwnership: All contracts transfer ownership to UNI Timelock (L1) or its L2 alias (0x2BAD...46CD) - confirmed for OP Stack and Arbitrum.\n\nContracts are immutable (no proxy pattern), but governance retains control: it can swap the releaser on any TokenJar (redirecting fee flow), adjust release thresholds, set per-pool fee overrides, and transfer V3 Factory ownership to a future adapter.\n\nWhat we could not verify\n\nSeveral elements remain unpublished ahead of the on-chain vote:\n\nCelo and X Layer have no public implementation. No custom releasers, no deployment scripts, and no bridge contracts were found in the public repo. We cannot assess how UNI gets burned on these chains.\n\nNo on-chain proposal scripts are published. The Snapshot body contains pseudocode for Proposals A and B, but the actual FeeExpansionProposal scripts couldn’t be found in the repo. Exact calldata cannot be independently verified.\n\nAudit scope is unclear. OpenZeppelin and Spearbit audited the original UNIfication contracts. Whether the new V3OpenFeeAdapter and L2-specific deployments fall within that audit scope - or require a separate review - has not been confirmed (?).\n\nBridged UNI addresses for three chains are TBD. Soneium, Worldchain, and Zora don’t yet have confirmed UNI token addresses in the deployment parameters.\n\nTakeaway\n\nProposal A extends existing rates to new chains without increasing them. The universal fee adapter is a policy shift - from opt-in to opt-out - it’s an economic risk, not a security one.\n\nProposal B (Celo, Soneium, Worldchain, X Layer, Zora) covers chains whose bridge and burn path cannot be verified from public sources. Until the Celo and X Layer releaser contracts are published, delegates cannot confirm how - or whether - UNI gets burned on those chains.\n\nMy recommendation: The direction is sound for both proposals: extending proven fee infrastructure to new chains at unchanged rates.\n\nProposal A (Mainnet V3OpenFeeAdapter + Base, OP Mainnet, Arbitrum) - supportable at Temp Check. Implementation is verifiable from public source code.\n\nProposal B (Celo, Soneium, Worldchain, X Layer, Zora) - supportable at Temp Check, but the on-chain vote should be conditional on the missing pieces being published first.\n\nBefore the on-chain vote, delegates should require the proposer to publish:\n\nOn-chain proposal calldata for both Proposals A and B\n\nCelo and X Layer bridge/releaser contracts\n\nDeployment scripts with a pinned commit hash\n\nConfirmation of audit coverage for the new contracts\n\n3 Likes\n\neek637\n\nFebruary 26, 2026, 4:55pm\n\n3\n\nHey @Manugotsuka nice analysis, thank you! Proposal 95 was just posted with links to the deployed fee infra contracts. There’s an outstanding PR on the fee contract repo that notes them as well, I’ll get that merged.\n\n1 Like\n\ncp0x\n\nMarch 2, 2026, 6:39pm\n\n4\n\nClarification on V3OpenFeeAdapter Address in Onchain Execution\n\nWhile reviewing the calldata for Function 4 in the onchain proposal, I noticed that the address being passed to:\n\nV3FeeAdapter.setFactoryOwner(address)\n\nis:\n\n0xf2371551Fe3937Db7c750f4DfABe5c2fFFdcBf5A\n\nHowever, in the proposal description and documentation, the mainnet V3OpenFeeAdapter is listed as:\n\n0x3e40DB80450f025b01E45c58b0aF763C7A29a8bd\n\nCould the team clarify why a different address is being used in the execution payload compared to the one referenced in the proposal specification?\n\nThanks in advance for the clarification.\n\n1 Like\n\neek637\n\nMarch 3, 2026, 12:08am\n\n5\n\nThe correct address is 0xf2371551Fe3937Db7c750f4DfABe5c2fFFdcBf5A. The only difference between the contracts is a global default fee setting. There’s a getter function for that parameter (defaultFee()) so you can confirm on Etherscan. More info on fee resolution can be found here. Thanks for your diligence!\n\ncp0x\n\nMarch 3, 2026, 1:30pm\n\n6\n\nThanks for clarification.\n\nAm I correct in assuming this is a typo in the text? Was this an accident or was the address changed for some reason?\n\nAnd there is a second question already connected with the second vote - why is the part on the execution of Sela included in both the first and the second part?\n\neek637\n\nMarch 3, 2026, 4:18pm\n\n7\n\nyeah typo in the text. in prepping for the proposal, the first contract deployment went out without the default fee configured. that deployment was added to docs and description. the default fee being set to 0 was discovered on review and a new contract was deployed. the testing scripts were update with the new address, the description was not.\n\nAssuming your second question is about Celo:\n\ncelo started as an alt L1 and we used wormhole as the messaging bridge for governance\n\ncelo transitioned to a op-stack L2, and per recs from Bridge Evaluation Committee we should use native bridges for L2s (see appendix 4 here)\n\nvote 1 migrates celo’s contract ownership from wormhole to a CrossChainAccount; future messages will be passed through the op-stack’s canonical messaging bridge\n\nvote 2 passes a message through that bridge to turn on v2 and v3 fees\n\nLMK if you have any more questions.\n\nManugotsuka\n\nMarch 3, 2026, 6:41pm\n\n8\n\nThe following reflects the views of L2BEAT’s governance team, composed of @kaereste and @Manugotsuka, and it’s based on their combined research, fact-checking, and ideation.\n\nWe voted FOR the fee expansion in Votes 1 and 2.\n\nFollowing our previous support at the Temperature Check stage, we are extending that position to the on-chain stage as well. These votes implement the UNIfication framework without changing fee parameters and represent execution of previously approved direction.\n\nAhead of the Temperature Check, we requested a full technical review from the L2BEAT Research Team. That analysis, which informed our initial position, is available here, and our vote today remains consistent with those findings.\n\n1 Like\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[Temp Check] Protocol Fee Expansion: Three More Chains\n\nTemperature Check\n\n3\n\n667\n\nMay 20, 2026\n\nConsensus Check - Enable 1bp Fee Tier on UniswapV3 Optimism(L2)\n\nConsensus Check\n\n1\n\n3936\n\nJune 24, 2022\n\nUNIfication Proposal\n\nRequests for Comment\n\n47\n\n24766\n\nJune 29, 2026\n\nMaking Protocol Fees Operational\n\nRequests for Comment\n\n35\n\n22004\n\nMay 14, 2024\n\nPGov Delegate Platform\n\nDelegation Pitch\n\n73\n\n6457\n\nSeptember 27, 2026","tokens":4340,"crawled_at":1791195203587}
+{"id":10493,"url":"https://docs.ethena.fi/technical-design/staking-usde","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Staking USDe | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nStaking is controlled by the StakedUSDe smart contract. Stakers can interact with it directly or through the Ethena dApp UI.\n\nWhen staking, a user transfers USDe into the contract and receives sUSDE (staked USDe) in return, another ERC20 token.\n\nOver time, additional USDe is transferred in as rewards.\n\nWhen unstaking, staked USDe is burned in exchange for a proportionate USDe amount based on the total amount of sUSDe outstanding vis-a-vis total USDe in the smart contract.\n\nUsers will receive the principal amount of USDe staked as well as their proportionate share of the deposited rewards upon unstaking.\n\nThe acquisition of sUSDe is not offered to persons with their habitual residence or registered office in the European Union or the European Economic Area.\n\nThe StakedUSDe smart contract implements the ERC4626 Token Vault standard for composability. This popular standard is widely used for onchain reward-accruing; thus, it is expected that other user interfaces beyond the Ethena dApp may likely support USDe staking in the future. Various deposit and redeem functions are exposed, enabling staking with or without a slippage threshold, and with or without an ERC2612 Permit signature authorizing the transfer of USDe.\nThere is no minimum staking period. If a user stakes and unstakes in consecutive blocks, they would receive their share of any increase in vested USDe value in the contract that has occurred in that ~12-second period. Because reward payments into the contract occur every 8 hours and linearly vest over 8 hours, there are never any sudden spikes in the vested USDe value, which prevents sandwich attacks where an informed staker stakes before and unstakes after payment at the expense of all other stakers.\n\nStakers should never lose USDe by staking. USDe transfers of rewards can only be positive or flat into the StakedUSDe contract. As such, the USDe value of stUSDe can only increase or stay flat over time.\n\nStaking rewards accrual is related to the protocol's generated revenue from staking Ethereum & earning the funding and basis spread from the delta hedging derivatives position. While protocol generated revenue should remain fairly stable unless there is a slashing event, the funding and basis spread income from delta hedging derivatives will vary considerably (even day to day). In some periods, no rewards may be paid to stakers if the funding + basis spread yield is negative and it is greater than or equal to the income generated via the staked Ethereum. In this situation, when no rewards are transferred to the StakedUSDe smart contract, the Ethena reserve fund will support the underlying protocol backing.\nQuick Answers\nQ: Do I have to stake USDe to receive rewards?\nYes. You have to stake your USDe with Ethena to receive incentive rewards. USDe is a synthetic dollar that does not earn rewards.\nQ: Why is there a cooldown period during launch?\nThere is a cooldown from requesting to unstake sUSDe to receiving USDe in return. Users must first request their USDe be unstaked wherein their USDe will be placed in the USDeSilo smart contract. Once the cooldown period has elapsed, users will be able to withdraw their USDe from the USDeSilo smart contract.\nQ: Am I able to sell the sUSDe prior to the cooldown?\nYes, you are able to do so if external markets exist. Note, however, that neither the Ethena Foundation nor Ethena Labs is planning to actively procure or facilitate creation of any such markets, and there can therefore be no guarantee that such market will exist.\nQ: Is it possible that I owe the protocol while staked?\nNo. Rewards can only be positive or zero.\nQ: What are staking rewards paid in?\nThe rewards are transferred to the staking contract in the form of USDe.\n\nLast updated 2 months ago\nWas this helpful?","tokens":969,"crawled_at":1791195221450}
+{"id":10494,"url":"https://gov.uniswap.org/t/kpk-delegate-platform/21773","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Kpk Delegate Platform - Delegation Pitch - Uniswap Governance","text":"Kpk Delegate Platform\n\nDelegation Pitch\n\nkpk\n\nAugust 9, 2023, 6:26pm\n\n1\n\nContact & Delegation Address Information\n\nDelegate Address: governance.karpatkey.eth (0x8787FC2De4De95c53e5E3a4e5459247D9773ea52)\n\nEmail: governance@karpatkey.com\n\nWebsite: https://kpk.io/\n\nTwitter: https://x.com/kpk_io\n\nIntroduction\n\nkpk is a DeFi-native organisation specialising in professional treasury development through industry-leading research and tooling since 2020. We’ve been working with GnosisDAO, Balancer, ENS, CoW Protocol, and Lido to diversify their treasuries into sustainable portfolios of DeFi investments designed to support the DAOs in their missions.\n\nWhat do you want to see happen in Uniswap governance over the next year?\n\nFurther initiatives to strengthen Uniswap’s status as the leading decentralised exchange across numerous chains and for a wide array of assets, aiming to expand cross-chain deployments and stimulate protocol development. This will empower Uniswap to credibly compete with centralised exchanges as a preferred platform for professional trading.\n\nCareful, thoughtful, and inclusive progress in the discussions around the Fee Switch and other value-accrual design mechanisms, as a means to reach long-term sustainability without compromising growth and adoption.\n\nFurther initiatives to foster a competitive, vibrant, and diverse ecosystem of teams contributing to the protocol to avoid single point of failure dependences and foster innovation.\n\nWith the first steps being laid out with the creation of the Uniswap Foundation, we expect more initiatives like the Uniswap Agora and other tooling/processes geared towards improving the governance process and ultimately increasing participation rate and high-value discussion and action.\n\nReasons for wanting to be a delegate:\n\nUniswap validated product-market fit for highly decentralised financial infrastructures and ultimately led the way in the evolution and growth of DeFi. As a champion of Ethereum principles around neutrality and trust minimisation, it is now essential to evolve beyond its core team and push for community-driven growth, development, and self-sustainability.\n\nA robust and progressive governance system will be essential moving forward, giving community members more opportunity to become involved and influence the protocol ecosystem, whether directly or indirectly. We’ve been advocates of delegated voting in DAO governance as a viable solution to improve the legitimacy, inclusivity, and effectiveness of decision-making processes. However, the efficacy of this system is highly dependent on having domain experts actively involved as delegates. They transform the delegation process into a dynamic ecosystem where insights are not just shared but are also meticulously examined and thoughtfully applied. It fosters a symbiotic relationship between all stakeholders, optimising the quality of collective decisions and reinforcing the democratic underpinnings of DAOs.\n\nAs DAO treasury developers and contributors to some of the most reputable DeFi protocols in our industry, we believe that our team has the knowledge, trust, and alignment to meaningfully contribute to Uniswap’s growth moving forward. Check out our values to understand a bit more about our guiding and decision-making principles.\n\nSkills and areas of expertise:\n\nOur past work has led us to develop internal infrastructure for automatic on-chain treasury execution and risk management, which ultimately generated objective knowledge across DeFi protocols and hands-on user experience. kpk’s governance team taps our network of engineers, DeFi strategists, data/financial/quant analysts, and accountants for subject matter expertise.\n\nWe’re also advocates of DAO alliances through treasury swaps as a means of reaching a more resilient DeFi ecosystem through treasury diversification and better value alignment as the ecosystem matures.\n\nPast contributions to Uniswap ecosystem and/or demonstrated protocol knowledge:\n\nWe’ve historically deployed a combined $62.91M worth of LP positions in both Uniswap V2 and V3:\n\nUniV2 Positions (GnosisDAO): https://etherscan.io/token/0xd6f3768e62ef92a9798e5a8cedd2b78907cecef9?a=0x849d52316331967b6ff1198e5e32a0eb168d039d;\n\nUniV3 Positions (GnosisDAO): https://etherscan.io/token/0xc36442b4a4522e871399cd717abdd847ab11fe88?a=0x849d52316331967b6ff1198e5e32a0eb168d039d; and\n\nUniV3 Positions (Balancer): https://etherscan.io/token/0xc36442b4a4522e871399cd717abdd847ab11fe88?a=0x0efccbb9e2c09ea29551879bd9da32362b32fc89.\n\nThis ultimately led us to develop internal models to optimise our liquidity ranges, resulting in increased capital efficiency and earnings. On the other hand, we’ve provided market depth on less popular pools, which ultimately contributed to the platform’s liquidity and diversity while simultaneously capitalising on unique opportunities for attractive returns.\n\nDisclosure of Conflicts of Interest:\n\nNo conflicts of interest other than the aforementioned contributions to competing DEXes—although we rather see it as an opportunity—as we can leverage our connections to promote strategic synergies moving forward.\n\n7 Likes\n\nDelegation of UNI to Active but Underrepresented Delegates Application Thread\n\nUniswap Delegate Reward Application Thread\n\nGLI -- Treasury Delegation Round 2 Applications\n\nkpk\n\nAugust 9, 2023, 6:27pm\n\n2\n\nProposal: ARB Distribution Proposal Poll\n\nVote: Combined Liquidity Incentives and MMA Infrastructure Development\n\nSummary: We appreciate the collaboration between the complementary Gauntlet and Gamma Strategies proposals and, considering the Architectural Reccomendations in the recent bridge assessment, it is appropriate to support the MMA Infrastructure Development proposal.\n\nProposal: Uniswap v3 on Base\n\nVote: Yes\n\nSummary: We support this deployment. We agree with the cross-chain vision Uniswap and the benefits outlined in the proposal. We find no issues with the deployment on Base and believe this should be supported.\n\nProposal: Uniswap v3 on Linea\n\nVote: Yes\n\nSummary: We support this deployment. We agree with the cross-chain vision Uniswap and find no outstanding issues with this L2 deployment.\n\nProposal: [Temperature Check] Migrate the Celo Uniswap V3 Factory Contract owner from Optics to Wormhole\n\nVote: Yes\n\nSummary: We support this Temp Check. Uniswap Bridge Assessment Committee’s approved Wormhole in their June Report. The decision to migrate to Wormhole is prudent considering that Optics is not on a path for approval.\n\n4 Likes\n\nkpk\n\nAugust 29, 2023, 7:58pm\n\n3\n\nVoting Actions - August 21-26th\n\nProposal: Migrate the Celo Uniswap V3 Factory Contract owner from Optics to Wormhole\n\nVote: For\n\nReasoning: We supported this proposal during the temp check phase and continue to support the migration from Optics to Wormhole. Our initial reasoning for support can be found here.\n\nProposal: Fund Combined Liquidity Incentivization Program\n\nVote: For\n\nReasoning: We supported this during the RFC phase and continue to support this joint proposal from Gauntlet and Gamma Strategies. Our reply to the initial forum discussion can be found here, and our formal reasoning is stated above on this delegate platform.\n\n2 Likes\n\nkpk\n\nSeptember 27, 2023, 8:03pm\n\n4\n\nVoting Actions - September 4 – 8th\n\nProposal: [Temperature Check] Deploy Friendly Fork of Uniswap V3; ZERO Protocol on Polygon zkEVM\n\nVote: Abstain\n\nReasoning: We have abstained to evaluate the possible effects of this proposal further. We would like to see more clarity around the long-term effects of this proposal. As other delegates have mentioned, there is concern that this approval would be tacit support by Uniswap governance for all future actions and outcomes from this friendly fork and possibly assuming reputational risk for the protocol.\n\n1 Like\n\nkpk\n\nSeptember 27, 2023, 8:06pm\n\n5\n\nVoting Actions - September 25 – 29th\n\nProposal: Deploy Friendly Fork of Uniswap V3; ZERO Protocol on Polygon zkEVM\n\nVote: Yae\n\nReasoning: After considering this topic further in the Governance Proposal phase, we agree that collaboration in the proliferation of the Uniswap protocol while aligning with the parent protocol through a “friendly fork” would have positive outcomes for both Zero and Uniswap.\n\n3 Likes\n\nkpk\n\nOctober 13, 2023, 6:23pm\n\n6\n\nVoting Actions - October 2nd – 6th\n\nProposal: Deploy Uniswap V3 on Filecoin Virtual Machine (FVM)\n\nVote: Yae\n\nReasoning: We support this proposal as it brings an interesting use case for Uniswap. The concept of monetising data and creating a market for selling/swapping data storage tokens has been in discussion for a long time, and being early at a chain that enables it gives Uniswap a competitive edge.\n\nProposal: [Temp Check]: Complete initial funding of the UF\n\nVote: Yae\n\nReasoning: Although this is a large funding request from the Uniswap Foundation (UF), it fulfils Grants and Operational needs over several years. Further, we feel that the Uniswap Foundation has been candid in fielding public Q&A, and transparent with budget and spending allocations presented in the request. We have confidence in the UF and support this request to deploy the second tranche of the funding.\n\n3 Likes\n\nkpk\n\nNovember 2, 2023, 7:06pm\n\n7\n\nVoting Actions - October 9th – 13th\n\nProposal: Complete initial funding of the Uniswap Foundation\n\nVote: Yae\n\nReasoning: This continues our support expressed in the temp check. The proposal emphasizes the importance of Uniswap as critical infrastructure for decentralized finance (DeFi), and it ensures the Uniswap Foundation has the necessary resources to actively work on building and supporting a robust ecosystem to enable the Uniswap Protocol to continue its growth, innovation, and contribution to the DeFi ecosystem.\n\n2 Likes\n\nkpk\n\nNovember 11, 2023, 10:14am\n\n8\n\nVoting Actions - October 23rd – 27th\n\nProposal: Temperature Check - [Issue a Visa Card with Uniswap Logo ]\n\nVote: Abstain\n\nReasoning: With the logo and trademark belonging to Uniswap Labs, we do not feel this is an appropriate question for a DAO vote and have chosen to abstain.\n\nProposal: [Temperature Check]: Invest in Ekubo Protocol\n\nVote: No Change\n\nReasoning: We don’t support this proposal in the current state. The ask of 2.5 million UNI is too high for the terms presented. However, we recognize that there’s potential for Ekubo to contribute significantly to Uniswap with their knowledge of Starknet and Cairo. We would support a restructured proposal with a lower request and milestones.\n\n1 Like\n\nkpk\n\nNovember 11, 2023, 10:16am\n\n9\n\nVoting Actions - October 30rd – November 3rd\n\nProposal: Deploy Uniswap V3 on Scroll\n\nVote: Yae\n\nReasoning: We support this proposal for Uniswap to officially recognize Scroll’s mainnet deployment of Uniswap V3. The deployment on Scroll, a zk-rollup and native zkEVM scaling solution, follows over 1.8 million transactions already processed on its testnets.\n\nRecognizing this deployment as canonical is a move to expand the user base and capture the zkEVM market, which is essential as the Ethereum ecosystem evolves. This move positions Uniswap as an early adopter in a rapidly growing market, potentially increasing its platform’s utility and value.\n\n1 Like\n\nkpk\n\nNovember 11, 2023, 10:25am\n\n10\n\nVoting Actions - November 5th – 10th\n\nProposal: [Temperature Check]: Delegation of UNI to Active but Underrepresented Delegates\n\nVote: Yae\n\nReasoning: We wholly support governance initatives that increase the ability for smaller delegates to have a louder voice in the Uniswap DAO. We have posed questions in an earlier discussion, and we are glad to see this moving forward.\n\nkpk\n\nJanuary 17, 2024, 6:31am\n\n11\n\nVoting Actions 2024 - January 8th – 12th\n\nProposal: [Temperature Check] Deploy Uniswap v3 on Rootstock (Bitcoin Sidechain)\n\nVote: Yes\n\nReasoning: We support the TEMP CHECK to add Uniswap to Roosktock, as we see it well positioned to bring DeFi elements closer to Bitcoin. The sidechain’s willingness to allocate $3 million for bootstrapping liquidity is also a sign of commitment, and the current deployment already shows some traction. Other positive points are the wormhole bridge and Oku’s deployments, indicating that this part of the infrastructure is already in place.\n\nProposal: [Temperature Check] Lower Onchain Proposal Threshold\n\nVote: Lower PT from 2.5M UNI to 1M UNI\n\nReasoning: We support the threshold reduction as it will enable more delegates to act as the bridge from the community to the DAO. This amount required is still high enough to prevent spamming, and it will likely increase engagement on the forum with a new set of proposals and ideas.\n\n2 Likes\n\nkpk\n\nFebruary 12, 2024, 10:04pm\n\n12\n\nVoting Actions 2024: January 15th – 19th\n\nProposal: Uniswap Deployments Accountability Committee Competition\n\nVote: 25% for Juanbug (PGov), 25% for Doo_StableLab [StableLab], 25% for Abdullah (Michigan Blockchain), 25% for 0xpibblez (Blockworks Research)\n\nReasoning: All of the candidates available are of high quality, and any would serve the committee well. Given the close race, we have decided to select only four. We have selected to re-elect @juanbug and @Doo_StableLab because they carry forward continuity from the inaugural committee. At the same time, the addition of @AbdullahUmar and @0xpibblez bring in new talent that we feel will confidently foster new protocol relationships and deployment efforts.\n\n3 Likes\n\nkpk\n\nFebruary 12, 2024, 10:05pm\n\n13\n\nVoting Actions 2024: January 29th – February 2nd\n\nNote: This week saw ten proposals for onboarding packages. Although we support provisioning for onboarding, this process needed to be more convenient and efficient. As stated in the forum discussion, we feel this would be better addressed by delegates first deciding on the total cost for the onboarding program, which has overhead expenses outside of the onboarding packages themselves, and then having a committee suggest incentive packages bested suited for each chain based on specific data-driven criterias.\n\nProposal: [Temp] Uni Onboarding Package - Scroll\n\nVote: 500k\n\nReasoning: Scroll is a chain gaining momentum, with an increase in TVL and with other blue-chip DeFi protocols on board. We support 500k, so there is room for more incentives if the DAO chooses.\n\nProposal: [Temp] Uni Onboarding Package - Polygon zkEVM\n\nVote: Against\n\nReasoning: Given the other options, we don’t think this chain is a priority, as it has a low TVL despite being in the market for almost a year now.\n\nProposal: [Temp] Uni Onboarding Package - zkSync\n\nVote: 750k\n\nReasoning: zkSync ERA is a chain with a consistently sticky TVL, and the competition is strong. We choose 750k for incentives on this chain, as we believe Uniswap will need to be more aggressive there.\n\nProposal: [Temp] Uni Onboarding Package - Blast\n\nVote: Against\n\nReasoning: The mainnet still needs to be deployed. We can reassess the need/amount to incentivize when it is live.\n\nProposal: [Temp] Uni Onboarding Package - Linea\n\nVote: 750k\n\nReasoning: Since launch, Linea has had a positive growth trend on its TVL. There is no dominant DEX there yet, so Uniswap has the opportunity to establish itself there, and we chose a higher amount to help with this objective.\n\nProposal: [Temp] Uni Onboarding Package - Base\n\nVote: 750k\n\nReasoning: Base was able to keep the TVL it acquired at its launch. Uniswap will face competition and should have a higher value to incentivize liquidity and sustain user growth.\n\nProposal: [Temp] Uni Onboarding Package - Taiko\n\nVote: Against\n\nReasoning: The mainnet still needs to be deployed. We can reassess the need/amount to incentivize when it is live.\n\nProposal: [Temp] Uni Onboarding Package - Moonbeam\n\nVote: 500k\n\nReasoning: Moonbeam is the EVM entrance to Polkadot. A Uniswap presence will bring us closer to a market that has yet to be addressed.\n\nProposal: [Temp] Uni Onboarding Package - BSC\n\nVote: 750k\n\nReasoning: BSC has a different type of user, which is heavily connected to Binance. It makes sense to introduce a strong Uniswap presence there to reach a new target group.\n\nProposal: [Temp] Uni Onboarding Package - Mantle\n\nVote: 500k\n\nReasoning: Mantle is a steady growth trajectory chain with no clear dominant DEX. Uniswap should invest in its presence there, and we believe 500k in incentives is a good start for this goal.\n\n2 Likes\n\nkpk\n\nMarch 2, 2024, 8:05pm\n\n14\n\nVoting Actions 2024: February 5th – February 9th\n\nProposal: [Temp Check] Deploy Uniswap v3 on Zora\n\nVote: Yes\n\nReasoning: We support the deployment of Uniswap on Ethereum’s L2s, and Zora will provide incentives for Uniswap to do so. The timing is good, and being on the chain since the start helps bootstrap initial liquidity.\n\nkpk\n\nMarch 2, 2024, 8:44pm\n\n15\n\nVoting Actions 2024: February 19th – February 23rd\n\nProposal: Delegation of UNI to Active but Underrepresented Delegates\n\nVote: YAE\n\nReasoning: We wholly support governance initiatives that increase the ability of smaller delegates to have a louder voice in the Uniswap DAO. See our support in the temp check phase here.\n\nProposal: Lower Onchain Proposal Threshold\n\nVote: YAE\n\nReasoning: It makes sense to have a lower number to foster more delegate activities and to enable more proposals to be presented to the DAO. We support this, as the number is still high enough to prevent spam or low-quality proposals.\n\nProposal: Deploy Uniswap V3 on Rootstock\n\nVote: YAE\n\nReasoning: We supported the TEMP CHECK, and the reasoning remains the same.\n\nProposal: Deploy Uniswap V3 on Zora\n\nVote: YAE\n\nReasoning: We are continuing our support from the Temp Check phase.\n\nProposal: Deploy Uniswap V2 on all chains with V3\n\nVote: YAE\n\nReasoning: V2 should be deployed on all chains, as it will help protocols with an additional AMM option from an official Uniswap deployment. We understand that the combination of v2 and v3 is powerful, and we support this proposal.\n\nProposal: Uniswap Revitalization and Growth Proposal\n\nVote: YAE\n\nReasoning: We support the proposal and believe the incentives will help drive adoption on the chains where Uniswap has room to grow.\n\n2 Likes\n\nkpk\n\nApril 8, 2024, 8:13pm\n\n16\n\nVoting Actions 2024 - March 4th – March 8th\n\nProposal: Uniswap V3 Fees: Factory Owner Amendment\n\nVote: Reject amendment\n\nReasoning: We have voted against this proposal because, at the current time, we do not believe that the DAO should make concessions in security for flexibility at this level. We expressed our support for the proposal to Activate Uniswap Protocol Governance, which we would like to see moved forward without this amendment.\n\nkpk\n\nApril 8, 2024, 9:17pm\n\n17\n\nVoting Actions 2024 - March 25th – March 29th\n\nProposal: [Temp Check] Mobilizing the Uniswap Treasury\n\nVote: For\n\nReasoning: This is a timely initiative, and we support this proposal. Treasury diversification is one pillar that helps the organization better plan its future and ensure that it is prepared for adversarial market conditions and karpatkey is thrilled to present any insights needed based on our work with other DAOs.\n\nkpk\n\nApril 15, 2024, 7:44pm\n\n18\n\nVoting Actions 2024 - April 1st – April 5th\n\nProposal: [Temp Check] Onboard Uniswap to Sei\n\nVote: Incentivize $500k\n\nReasoning: We support Uniswap’s onboarding on Sei with a 500k USD incentive package. Sei is a promising chain, and having an official deployment at the v2 launch will help consolidate our position as the leading DEX on that chain. The Sei Foundation will also incentivize this deployment, which highlights Uniswap’s attractiveness to newer blockchains.\n\n1 Like\n\nkpk\n\nApril 23, 2024, 2:38pm\n\n19\n\nVoting Actions 2024 - April 8 – April 12th\n\nProposal: Update Uni v3/v2 Deployment Process (March 2024)\n\nVote: Update the process\n\nReasoning: We support this update on the deployment process, as it makes it more efficient.\n\nProposal: [Temp Check] Uniswap Onboarding Package - Manta\n\nVote: For\n\nReasoning: We support this proposal to add Manta Pacific to the v3 deployments record and grant Manta an Onboarding Package. This deployment will have reduced costs as Mant already supports the Oku front end.\n\nkpk\n\nApril 30, 2024, 8:29am\n\n20\n\nVoting Actions 2024 - April 15th – April 19th\n\nProposal: Uniswap Treasury Working Group (UTWG) Election\n\nVote: 25% for Franklin DAO, 25% for GFX Labs, 25% for JoJo, 25% for 404 DAO\n\nReasoning: We recognize that all applications are strong ones, and our vote reflects our positioning to not interfere on the results, as we applied for the position.\n\n1 Like\n\nnext page →\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nSEEDGov Delegate Platform\n\nDelegation Pitch\n\n76\n\n3514\n\nMay 5, 2026\n\nIgnas Delegate Platform\n\nDelegation Pitch\n\n41\n\n1284\n\nMay 25, 2026\n\nAtiselsts.eth Delegate Platform\n\nDelegation Pitch\n\n32\n\n4670\n\nJuly 9, 2026\n\nKeyrock Delegate Platform\n\nDelegation Pitch\n\n26\n\n5237\n\nMarch 20, 2025\n\nPGov Delegate Platform\n\nDelegation Pitch\n\n73\n\n6457\n\nSeptember 27, 2026","tokens":5212,"crawled_at":1791195223158}
+{"id":10495,"url":"https://a16zcrypto.com/posts/podcast/antimemetics-memes-ideas-spread-community-crypto-beyond","domain":"a16zcrypto.com","chapter":"research","title":"The antimemetics (and memetics) of making ideas happen -- in crypto and beyond - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nThe antimemetics (and memetics) of making ideas happen -- in crypto and beyond\nSonal Chokshi and Nadia Asparouhova\n08.06.25\n\nTags & Share Tags\ncompany building\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nIdeas, memes, and vibes are some of the most important drivers of modern technology adoption, marketing, and much more — and have been much-covered by everyone from Darwin to Dawkins to Girard to many others. Yet the topic of antimemetics — self-censoring (vs. self-propagating) ideas — whether something fringe, forgotten, or forbidden — haven’t been studied as much, especially in the context of modern networks.\n\nSo in this special book-launch episode, we cover the important concept of antimemetics (and memetics) — focusing on:\n\nwhere and how ideas take off in groups, whether in online chats or other high-shared context communities;\n\nhow ideas not just spread but are contained, or mutate in strange ways;\n\nwhy packaging ideas matters; and\n\nwhat we can all do to move ideas to action.\n\nWhere do bureacracy, institutions, and protocols come in? What about tacit knowledge that lies in these communities, how (or do) we make it explicit? What roles — from truth tellers to champions to individual nodes in networks — can and do people play in making something go from mere commentary to reality? After all, ideas — or ideas as viruses — are how movements happen, how innovation happens, how things change… or don’t ever change despite being discussed all the time.\n\nOur expert guest in this special book episode (following in our long tradition of sharing what we’re reading) is Nadia Asparouhova, the author of the new book, Antimemetics: Why Some Ideas Resist Spreading; she is also the author of the book Working in Public: The Making and Maintenance of Open Source Software. a16z crypto’s Sonal Chokshi — who previously hosted Nadia’s book-launch episode for the a16z Podcast and almost a decade before that on the changing culture of open source — interviews Nadia on these themes, how they connect, and why they matter for the crypto industry and beyond. We also dig into some critiques — and opportunities for builders — too, including what happens to the public commons; network propagation including across networks; reality distortion fields; hidden knowledge; and cultural stagnation vs. cultural abundance. All this and more in this episode of web3 with a16z!\n\nshownotes/ links\n\nThe dark forest theory of the internet, Yancey Strickler\n\nThe extended internet universe, Venkatesh Rao\n\nThe dark forest and the cozy web, Maggie Appleton\n\nDangerous Protocols, Nadia Asparouhova\n\nIdea machines, Nadia Asparouhova\n\nThe tyranny of ideas, Nadia Asparouhova\n\nGoing critical, Kevin Simler\n\nfull transcript\n\nSonal: Hi, everyone. Welcome to this week’s episode of the a16z Crypto Podcast, I’m Sonal, and I’m so excited to introduce one of our special reading-book episodes. It’s been a really long time since we’ve done a book launch episode (I used to do them all the time in the a16z Podcast) — and it’s very fitting because, we’re a culture of readers; we recently published our annual summer reading list; we also publish one in winter — It’s a tradition my team started here years ago , and, it’s because we’re a culture of readers, as mentioned; but also because books and ideas are a way to shape and-and adapt our thinking into what we also make and build.\n\nAnd that is actually going to be the theme of today’s episode — which is all about ideas, how they spread, how they don’t spread. And then what to do to move ideas to action.\n\nAnd so joining as our special guest, we have researcher and writer, Nadia Asparouhova — formerly Nadia Eghbal (only I’m mentioning her former name because she was on the podcast under that name). And her writing has appeared everywhere, but most notably, she’s the author of Working in Public: The Making and Maintenance of Open Source Software — which is very fitting for this audience and theme. I actually did the very first episode on that book, which was published by Stripe Press, with Nadia a number of years ago; and then, more recently, she’s written a book called Antimemetics: Why Some Ideas Resist Spreading. And her work has been supported by Emergent Ventures; Ford Foundation (actually, Ford Foundation supported her original research into the culture and communities of open source); Schmidt Futures; Ethereum Foundation, where she also contributed to the Summer of Protocols — and has written about protocols, and more.\n\nSo, welcome Nadia, and welcome back to the podcast for the third time, in like a decade!\n\nNadia: <chuckles> Thanks for having me back!\n\nSonal: I’m so excited about your new book — honestly, I’m not just saying this because I’m pretty critical about books these days; I was just telling my colleagues recently that I actually don’t even like nonfiction books anymore, because: I just think they’re terrible… Most of them should have been an article. They’re not interesting. They’re stuffed with stupid anecdotes. Like I’m just over nonfiction mostly; I’d rather read fiction at this point.\n\nAnd, your book truly — I actually added it to our best-of recommendations list this year — is just remarkable. I absolutely love it. And I’m truly not just saying that, I think you know me well enough to know that.\n\nNadia: <laughs> Tha-yeah, I think I have similar sentiments about nonfiction and fiction books; I mostly read fiction these days… So if I had to write a nonfiction book, which I felt like I had to do — I think I’m drawn to topics that I feel like no one else is looking at. Or that, you know, there’s some folk knowledge or understanding of how a thing works, but then that the way that it works is not more broadly understood.\n\nThat’s definitely what drew me to open source software, even though I didn’t have a background in it at all at the time. <Sonal: yup> And, yeah, I think there is some anti-memetic quality to a lot of… problems around maintenance and infrastructure, where we’re all sort of relying on these things, but; and using them — and we know that they’re important, but somehow can’t seem to pay enough attention to them, <Sonal: Yes!> even though we should be.\n\nSonal: So this is a wonderful throughline to even connect the episodes we’ve done together, is: You talked a lot about how open source, it’s remarkable how there’s entire very important systems that even hospitals rely on, and only one or two people are maintaining it just to make that concrete. And, in this book, there’s a funny anecdote you mentioned (which I think is really funny): You talk about how Disneyland has these bright things — and then against the background, there’s this don’t-look kind of green shade that hides all the maintenance and the invisible infrastructure? ‘Cuz like they don’t want you to see it, but it’s hiding in plain sight.\n\nNadia: Yeah, it’s a paint color called “go away green”.\n\nSonal: I love it. I’m also obsessed with colors — and I have- you know we’ll talk about this offline, as an, as an aesthetic property —\n\nBut it’s a great example of what you’re talking about: about kind of this thing that you can forget things that are hiding in plain sight and that are very important, but yet somehow our minds won’t capture them.\n\nI think we should start with you now just defining “anti-memetic”. Like I didn’t even know what that word really meant until I read your book. Just what does that even mean?\n\nNadia: Sure! So “anti-memes” are self-censoring ideas — so, that’s in contrast to memes, which are self-propagating ideas. They’re ideas that we can’t seem to hold onto in our minds — even though we find them interesting and compelling in the moment. So it’s not that the idea is boring or uninteresting; it’s like, you know, if you’re directly engaging with it, you think, oh, this is really important and I should remember it — and then somehow it just seems to fade from your memory.\n\nAnd that, that sort of anti-memetic property can happen on both an individual level — so, things like cognitive biases or motives, difficult truths that we just don’t really want to admit to ourselves. But then it also happens on a collective level — so things like taboos, where everyone knows that a thing is true, but for some reason you can’t say it out loud.\n\nSonal: Mm, interesting. And when we talk about memes, you describe examples of like symbols, customs, and rituals, all as things that can spread memetically. So those things spread memetically, not anti-memetically?\n\nNadia: Yah, I think in both cases for memes and anti-memes — even though the term “anti-meme” was coined you know in the last decade or two — but I think the-the dynamics of both memes and anti-memes have been around for forever, right. So yeah:\n\nMemes have passed through aphorisms, rituals, norms — you know shaking people’s hands, popular sayings, things like that — those are all examples of memes that have existed looong before the internet existed. <Sonal: Absolutely>\n\nAnd then similarly with anti-memes, there are you know taboos; whisper networks; sacred knowledge that you know requires some sort of, yah, religious ritual sort of <yah> to unearth or something. You know like all these things have also existed for a really long time, before we had the internet; but I think recent dynamics and changes in how the social web is evolving has just made this concept of anti-memes more prominent.\n\nSonal: Would you say that fringe movements also qualify as anti-memes?\n\nNadia: Yeah I think the ideas that are contained in those movements can be anti-memetic — If we are looking at sort of like, how are they spreading more broadly. It’s like okay, they’re being confined to a group of people that are particularly primed to engage with it, and look at it; but it can’t seem to spread beyond that smaller group. <mhm> And so I talk a lot about group chats in the book.\n\nAnd yeah, group chats are, in a sense you can see as kind of like fringe groups in their own right, right — it’s like these small segments and balkanized kind of groups. And sometimes ideas can spread very rapidly within a small group, <Sonal: mhm> but then not jump to a broader network.\n\nSonal: Got it. Now, well, it’s funny because, yah — I’d say group chats… one of the things I took away from your book is: They’re not, they’re not actually necessarily fringe; they might actually now be the core… body of where discourse is happening. Like they’re-they’re actually maybe the center now — because the public square, the so-called common, shared, singular space is kind of fracturing. I don’t know if that’s what your thesis is, but when I read your book, that was one of my takeaways…\n\nNadia: Yeah, it’s sort of like a “centerless center”, <mm!> I guess I would say, um that exists in parallel to… you know, I think one of the points I did want to drive home with this book was that it’s not that group chats have replaced the public feeds — we still have public feeds — and these two dynamic- these two modes of information spread continue <mhm> to work in tandem with each other.\n\nSonal: Yes, yes; I agree. And that was actually a very key idea I took away from your book too, is that these things need each other — the public internet, the private groups, even the discourse… If you think about media as an example (quote-“mainstream media”) you even make the observation that a lot of these groups need the public media in order to talk about those things in their private media, etc., etc.\n\nNadia: It’s almost like yah the information ecosystem has expanded now, it’s not that one has replaced the other.\n\nSonal: Yes, totally.\n\nThe other definition, though, which I thought was very vibrant and interesting <chuckles> — and probably the very first time I’ve ever seen this word defined, ever! — is the word “vibes”…\n\nAnd you actually say in your book that “vibes” combine the qualities of both memes and anti-memes. And I’d love to hear you, like, expand on that — and actually, it’s probably quite literally, indefinable, which to your point, is maybe the point — but how would you define them, cuz crypto is all about the vibes.\n\nNadia: So I talk a lot about the interplay between memes and anti-memes in both the you know the private and public web — and one of the places that I talk about that is this concept of vibes, which has become more of a thing let’s say in the last five-ish years <yah> that anti-memes have also become more popular.\n\nAnd a “vibe” is, I would think of it as: an anti-memetic idea that is wrapped in memetic wrapping paper <chuckles>… or something like that. <Sonal: I love that!> <both chuckle>\n\nSo it’s able to sort of spread through the public web or spread through public channels — but you don’t really know what the- what the thing is, and that’s kind of the point.\n\nLike we all kind of agree, we’re not going to look too closely at it, but we’re giving it this thin veneer of meme, just enough that we can continue to pass it around without ever actually looking what’s, what is the present inside the gift wrap. <Sonal: That is… so good!>\n\nAnd I think, again, all these ideas sound new, and trendy, and internet-y — but I actually think all these things have existed for a long time. And so, I think the concept of a vibe has… it’s encoded in a lot of our own language where we use a word without really knowing what the thing is: So I talk about examples like “community”, or “love”, or “mentorship” — These are also, in a sense, kind of vibes on their own, right; it’s really, really hard to define what love actually is. <Sonal: Yes!> It’s really hard to define what community actually is.\n\nAnd that’s kind of the point. Like we don’t want to get so specific with it that it can be sort of measured or exploited… and so we all kind of agree that you know, this word love is a stand in for some concept/ vibe/ feeling. And we’re kind of just going use it to pass the idea around, right.\n\nSonal: Yes! And to be clear though, there is still a thing — like even if we can’t quite define it when you say love, -<Nadia: yes!> when you say community — it’s not like anything can be community and anything can be love. Like we kind of still know what the “it” is, even though we can’t define it quite precisely.\n\nNadia: Yes. Yes.\n\nSonal: Yah, totally.\n\nYour book talks a lot about group chats, and that was one of the phenomena you talk about; but: Loosely speaking, we’re talking about small communities that form around a shared interest or high-shared context. Basically, it’s just a metaphor also for just any small group <Nadia: yes!> — or community that has a shared interest.\n\nYah. Which is why I think it’s very relevant to this audience, for the record. Because I think otherwise people think group chats, and they’re like well I’m not in a lot of group chats.\n\nNadia: It is funny, I’ve had a number of people who’ve read the book already be like “I feel kind of sad because I’m not in group chats” <Sonal: oh; laughs> I’m like, but you’re in a lot of small communities — if they think about it in a different way, it’s like actually everyone’s in them.\n\nSonal: Exactly; that’s how I think about it. So this leads me to my next question, Nadia (this is a perfect segue actually) — So the reason I care about this, and I think why our audience should care about this — is this is very much related to how ideas propagate, what doesn’t –\n\nThis is very top of mind for people, not just in the crypto community, but anyone for crypto and beyond, for all the whole builders. So that’s really what I’m very interested in: Which is, like, how these ideas spread, what makes them happen, what makes them work.\n\nActually, and I also want to add another point about vibes — and it connects to why this whole podcast and this topic matters, and why your book matters: Like, vibes actually can move economies. I don’t know if you’ve read Kyla Scanlon’s book, In This Economy, she has a whole chapter dedicated to kind of measuring vibes, informally. And you know that memetic and anti-memetic things can actually generate physical value.\n\nBecause one takeaway is: Are all these just conversations? Like we should maybe give a little bit more of the thesis — but one of the big themes, which we’ve seen, and you observe and outline this in your book, along with Kevin Simler and a few other people — is how a lot of these conversations are happening in group chats. Like, do you want to kind of quickly share your thesis on that more specifically? And then I’ll- I have a follow-up question for you around that.\n\nNadia: Yah. I’ve been saying that memes and anti-memes have been around for a long time. And if you look at sort of the history of how memes became household word — it- the term was popularized by Richard Dawkins in his book in the 1970s. But it didn’t really become internet-relevant until the let’s say 2000s, 2010s — where this concept of a self-propagating idea became just much more visible in how people were using the internet, and how information was passing around.\n\nAnd so similarly, I think something happened with anti-memes in the late 2010s let’s say — where, things just got a little bit too public; sharing ideas on the internet started to become a little bit more of a liability at times when things got too popular. <Sonal: yah> And so you see people sort of reflexively starting to burrow down; starting to reserve their most cherished and interesting ideas for smaller groups, for more high-context settings.\n\nAnd so that’s where you start seeing this like bifurcation happening where: We’re continuing to use our public social feeds; but then slowly, imperceptibly, more and more people are starting to use group chats, people are using newsletters — just looking for more semi-private spaces to share their ideas.\n\nAnd that’s where we kind of got to in the last five-ish years or so. And I think it’s interesting because group chats didn’t have this moment of an explosion: There was no like “group-chat moment” where everything took off — in the way that you could say you know Instagram, or Twitter, or Facebook had these like defining moments. Because it’s just you know, because these things happen on messaging apps. <chuckles> And definitely COVID helped increase the adoption of group chats — but these big trends are happening and no one can even see or perceive what-what is going on because it’s by definition not happening in public.\n\nSonal: Exactly, yeah. Eugene has also made this point (and he’s I think written about this too), where, that we’re not really meant to have large public squares. And that if you think about what public squares have historically been used for, they’re actually used for things like mass punishment, like you know flogging, you know tar and feathering, hangings. <Nadia: hm>\n\nAnd I don’t know if you have any thoughts on… — You-you do make the point in the book that it’s important to not abandon the public spaces; but I also wonder if you have any thoughts on the evolution of the public space, before we move into a little bit more of these private/ smaller groups.\n\nNadia: Yeah, I think that’s broadly right. I think what’s changed is just our expectations of what we think the public square should be or what it should do for us. <Sonal: Ah!… Yes> I do think that you know that, that sort of globalization influence/ Pollyanna-ish optimism of the late 2000s (when we saw the advent of the consumer web) — that was also sort of like the early open source kind of culture of just you know: “more public is great, and we should embrace that”. I think that, we’ve seen that play out now, and… yeah, maybe it’s not not great in the way that we expected it to be.\n\nThat doesn’t mean that we should just do away with it entirely — I still think it’s useful, sometimes you need to broadcast to a much broader audience — I mean, it is the (hehe) information superhighway.\n\nBut maybe it’s a way for us to get from destination to destination: Ideas can fly through these public channels to jump around from one place to another. It’s still a useful mode of transportation; it’s just maybe that’s not the place where nuance happens. And that’s okay.\n\nSonal: That’s- I’m so glad you brought that up. I would love to hear you more explicitly connect where you see the parallels between what you saw happen in the changing culture of open source.\n\nNadia: Yah; in some ways, I think Working in Public was a precursor to this book. I’ve thought about this book as you know “Working in Private” basically as the compliment to <Sonal: mm!…mhm… totally!> the first book.\n\nBut the thesis in Working in Public was that there’s this widespread belief that open source is all about you know widespread collaboration among lots and lots of open source developers — and we have this sort of like happy, bucolic kind of view of what it means to make open source software on the internet.\n\nAnd… what had sort of kicked off my interest in that was actually going and talking to open source developers and realizing that wasn’t the case, that there is actually a lot of nuance in different projects and how they’re structured: They’re not all always big communities. Some of the ones that we assume are big communities are actually just a couple of developers that are kind of toiling away, on their own.\n\nAnd so there’s something that needs to be added to the conversation about open source culture there <Sonal: yup> — it’s like, you know, they’re not all just Linux-sized projects: Some of them are kind of more like hobby/ hobbyist-type groups and clubs. Some of them are just one developer who’s working across tons and tons of different projects, and kind of like broadcasting that out to the group. And all of those are open source projects, but they’re just open source projects in different ways.\n\nIt required looking back a little bit on what were the original promises of open source and what we think it is (I still think a lot of this rhetoric continues to persist today, even though we should really be moving beyond it at this point) — “highly, highly public and collaborative” is not always what it’s cracked up to be in practice. A lot of times quote-unquote “collaboration” can look like people filing lots of open issues, or bugs, or feature requests. And, they think that they’re contributing to an open source project; they’re actually just adding a lot of support burden to maybe like a single developer who does not have the time to go through all this stuff in their spare time. <chuckles> Even if it’s a widely used project.\n\nSo, yeah, we-we hide behind this idea of like the public web as being this ultimate good — and, I think we’ve already sort of moved past that in like the broader social-web kind of context — but I still see it live on in a lot of places in open source, and I think, I think it’s just not realistic.\n\nSonal: I’m so glad you brought that up, because it actually does fit what we see in a lot of decentralized autonomous organizations.\n\nLike, there is this thing that it’s like “everyone’s open and sharing and its community” — but there’s a lot that our team has obviously written; and we have a wonderful researcher who’s at Stanford, and he’s a political science professor (Andy Hall) who studies decentralized governance in great, great detail — including in real-world systems, online, and DAOs in various forms.\n\nAnd, it’s very interesting because it parallels what you described and what you saw in the cultures of open source. ‘Cause really, Working in Public (and you even say this in this book) was also hinting at like why classic democracy may not work in its current form. And, that’s something similar to what people saw in DAOs — like in their initial wave of DAOs — like hey, this isn’t working.\n\nSo what we’re finding is people are doing these like laboratories of governance, like “living labs” of governance with DAOs, where they’re iterating and finding new models. And so one of our partners (Miles Jennings) wrote this series called “Machiavelli for DAOs” which leans in to the *reality* of people’s kind of self-interested motives — not in this happy, collaborative open source feel only — to actually better incentivize competition, empower rivals, and using non-token-based voting to like fix decentralized governance.\n\n<Nadia: hm> So it’s very similar to what you saw — I’ll send you the series, I think you’d find it really interesting <Nadia: yah I’m curious> Yah! As I was reading, as I was reading your book, I feel like you kind of imply, at multiple points, that we need to be realistic what people’s motives are… And so, that’s basically what his series is about, like just kind of leaning into that.\n\nBut the other thing which you didn’t mention just now (when talking about the link to open source) is not just about like the size of the project — and like you know big/ small, collaborative/ not — but also the clash of the old guard and new guard. Which I wonder if there’s something memetic and antimemetic about that too.\n\nNadia: Yah, the old guard/ new guard dynamics… So I mentioned that part of why I was drawn to open source in the first place was realizing there are these “truths” about <chuckles> how open source culture works that were really widely understood by a lot of developers who were deeply in it <Sonal: yup!> — but then somehow it did not make the jump to even broader software-developer culture (much less tech, much less the world).\n\nAnd, when you dig into a little bit of, you know, why is that happening — why is this information not spreading beyond the people who are like in it and experiencing it themselves? — There is definitely (and I think this dynamic is true in a lot of other communities, not just open source), but yah, old guard/ new guard dynamic, where it’s not even a always like a specific people trying to suppress things, but also just there is just a common wisdom about how open source works.\n\nAnd it’s to the benefit of the network that this idea continues to persist. <Sonal: yes> — because it’s- you know, we don’t want to talk about open source in a negative way, of it’s meant to be this poster child of democracy and poster child of what the internet could be, right. But then it gets in the way of like who ends up suffering in the end: It’s like people who can’t get support for their projects, or who are struggling under the burden of high support volume or whatever — and they’re going completely unseen because, because no one really wants to see the truth that is like right in front of them.\n\nSo yeah, I think there’s some anti-memetic quality around these like uncomfortable hidden truths that are right there for the taking — if you just go and ask people about their experiences. <both chuckle> <Sonal: Yah!>\n\nBut for, yah why do we suppress them; it’s again, kind of going back to how consequential it is to the rest of the network: What would it mean if open source turned out to not be the poster child we expected it to be?\n\nAnd, at the time when I- I published Working in Public in 2020; and that was, I think, during a time where it still felt a little bit strange to talk about that as a parable for the social web more broadly — <yup> and I was sort of trying to talk about it in a somewhat sanitized way in that, in that book. But I think that’s sort of what we saw happen more broadly.\n\nAnd all these promises that we had about sharing information more freely online, turned out to not be true. But it doesn’t mean that it’s not worth striving for. It doesn’t mean that democracy is not worth striving for. It just means let’s be realistic about what we’re looking at <Sonal: Exactly> — and then from there, we can build upon it to figure out how to- how to achieve the goals and the values that we still think are really important.\n\nSonal: That’s exactly why I brought up the Machiavellian DAOs — it’s literally just leaning into the reality, like let’s just face these truths; and then you can actually build and address.\n\nAnd, and I love that you connected the dots there, Nadia — because it also connects a throughline from your past few books, our past podcasts together — but also things that are really relevant to our audience.\n\nNow, one of the other things you propose in the book: You specifically use a phrase “sediment” — that you’re kind of almost, like, chewing up the idea… you have a great analogy, water-filtration analogy actually that you should share (‘cause it’s your analogy) — but I think it’s a wonderful way of kind of crystallizing this way to kind of pre-filter almost? Before you like masticate, like chew on the thing in a bigger group/ public discourse.\n\nNadia: <chuckles> Hm, I like the chewing metaphor.\n\nSonal: That came from my therapist; <Nadia: yup> I’ll talk about that in a moment. <both laugh>\n\nNadia: It’s a, yeah! I talk about networks — so any network where information is spreading through it — as these sort of sediment filters: If you think about a physical filter for purifying water, you can put like gravel in it, you can put stones in, you can put sand… and then you pour the water in and then it can like slooowly drip down to the bottom… and then your water is theoretically somewhat cleaner. And there’s-there’s something like that that happens with how information kind of drips through a network.\n\nAnd, group chats are a version of this, where you’re sort of workshopping, and then it’s slowly slowly seeping out to a broader network. But in the course of that happening, it’s being refined and tested – ‘cuz you know something we haven’t talked about yet is maybe sort of like on Why do anti-memes not spread easily, even though they are so interesting to us in the moment?\n\nPart of it is that they’re perceived to be highly consequential, right? <Sonal: yah> And so if I spread this too easily, there’s a potential hit that I might take to my own reputation, or it might harm my network. This is, you know if you think about taboos as a type of anti-meme, if you say the taboo out loud, that can make you look really bad; and maybe worse, maybe it doesn’t make you look bad and everyone just gets really excited about it (and now you’ve introduced this you know info hazard to a broader network).\n\nSo, I think it’s useful to have some sort of filtration system — and that’s sort of what networks naturally are, right?\n\nAnd if we think about it in terms of adjusting the porousness of that- that kind of sediment filter: Is it passing through very fine sand or is it passing through big rocky pebbles? Some networks let more ideas through, and some networks are a little bit more tightly held.\n\nAnd, I make the argument in the book that even taboos, I don’t think are innately good or bad, right; we can all think of examples of taboos that are really good that we don’t say them out loud. <chuckles> And then there’s also taboos where it’s like, I wish I could say that out loud! But it’s more of this spectrum of, you know, having to constantly… consider, you know: Are we letting too many ideas in or are we suppressing too many ideas; sometimes we are holding things a little bit too tightly, sometimes we’re being a little bit too loose with it. Both of those have consequences <mm> in different directions.\n\nSonal: I love that, and to build on your very sophisticated filtration metaphor, I will bring up the masticating one — which I did for the record steal from my therapist <Nadia chuckles> — ‘cause she describes it as a little bit like the job of someone who’s like a mediator helping you think about things and reflect on tough things: is to kind of pre-chew it, like masticate it the way a mama bird pre-chews the food before feeding it to a baby before their digestion fully develops.\n\nSo there is kind of like a combination of filtration and kind of “chewing it up” — iterating on it (as you say in your book) — before you really can… you know refine and have the thing that you’re talking about; which may or may not spread. And we will get to the question of why some things don’t spread.\n\nBut before we do, I also have this question for you — because one thing I wasn’t fully satisfied with, was: Are we also in an era with group chats where people are just commenting and not making things? Like they’re not really acting, and they’re just chewing on things, and filtering, and recycling, and… I don’t know, I’d love to hear your thoughts on this because I’m entirely sure you wrestled with this too while writing the book.\n\nNadia: I think, part of why I wrote this book was because I was grappling with that myself. I think a lot of people had this experience in somewhere around 2020-ish, where everyone starts hunkering down, and you know, a lot of people are withdrawing from public/ super-highly public social interactions.\n\nAnd… you get to this state where you’re just like, oh I’m comfortable and I’m cozy: I’ve got my little group chats, I can talk to my friends, I don’t need to interact with the you know public stage; that feels really good for a little bit. And then after a while, you’re just sort of like — yeah, exactly as you’re saying — Am I just commenting?\n\nYou know I used to be more participatory; I used to like put things into the commons so that other people could benefit from them. I’ve noticed this even with my own writing: Like I write less frequently and more long form, but I don’t write as often as I used to…and I don’t publish things in public as much as I used to — Because I just share them with my friends now, and that’s good enough for me. And I think I started feeling uncomfortable with this of like, is this the future? That doesn’t feel right for me. <Sonal: Right!> That feels like kind of a bummer.\n\nAnd I think a lot of the discourse about where the social web is going, sometimes seems to imply that this is a good thing. As if, we… found a way to put a band-aid solution on here; and we just aren’t as public as we used to be, and that’s fine. And I’m just, I’m just sort of dissatisfied with that answer. <Sonal: yes>\n\nAnd I think part of why I wanted to write this book was not to frame it as — there was, first there was the highly public social web; then we withdrew into the private web, and now everyone is happy — that’s not the end of the story.\n\nI think there are uh two big critiques I have of sort of the group chat era.\n\nSonal: Ooh, I want to hear those. <chuckles>\n\nNadia: <chuckles> Well yeah, the chapter about sort of this “memetic Galapagos” that I talk about, where, there’s this false sense of security that we have about only keeping our ideas in these smaller, more private spaces — because we think they’re protected somehow from memetic contagion.\n\nAnd I draw this analogy to you know the COVID pods that everyone had, where it’s like okay I’m just going to hang out with my 10 friends, and you know we’re going to avoid getting any other sort of contagion — but that doesn’t actually work in practice if you’re say, living in a city, <Sonal: yup> because people still interact with other humans just by nature of being around them.\n\nAnd so similarly with group chats, it’s not that you are only spending time in your group chat and not consuming any other information or ideas outside of that. <Sonal: Right> People take stuff… — what do we all talk about in group chats; we’re always sharing links, talking about things that are happening on Twitter or whatever happening in the news — so you are introducing these memetic contagions in very highly compressed, high-trust, high-context settings.\n\nAnd, just like how the Galapagos leads to greater species biodiversity — because you have these little islands; and within each island, a species can evolve much more rapidly; and also in really strange, mutated ways — that’s sort of what’s happening with ideas… Where ideas are actually getting stranger and stranger because they are in these segmented group chats. Because you’re in a small setting where your friend now introduces an idea and you go, oh! that sounds pretty reasonable.\n\nAnd then the speed at which those ideas can get warped in a smaller setting, it just happens much more rapidly than something on the public feed. <yah>\n\nSo, that’s one of my critiques about the group chat era, is that it’s not actually as cozy and safe as we think it is.\n\nSonal: Okay, so that’s one of the critiques. What was your second critique?\n\nNadia: Second critique is just, if we take the idea of being comfortable in our group chats to their most logical conclusion — What happens to the public commons?\n\nAnd… <Sonal: exactly> You know, I mentioned that at least for myself, I feel much less of a need to keep putting my ideas out in public because I get the same sort of satisfaction from smaller settings (group chats, newsletters, whatever). And I think a lot of people are experiencing something like that. But. And so, does that mean that the most… nuanced or thoughtful types of ideas — instead of putting them out in public, we’re just sort of holding them private? —\n\nAnd then what does the public commons look like? It’s kind of just left to people who are willing to play the super memetic game, or are you know doing things to kind of juice up their audience; that’s kind of a sad future to be in.\n\nAnd so part of even writing this book — this was something I’d sat on for a couple of years and, felt like a little bit self-indulgent; you know <yah!> I had my own doubts; every writer does about everything, you know, something that they write — And part of it was me trying to force myself to say, no, you should keep putting things out there, even when it makes you uncomfortable, even when you feel like you don’t necessarily have to… Because, yeah, we all have some kind of responsibility to do that.\n\nAnd so, I try not to overly moralize in one direction or the other of… <chuckles> But I at least want us to look at the phenomenon of what is happening today. And try to offer some inroads into, okay: if this is the way the world works, how can we make meaning out of it? I didn’t want it to feel like we’re just in a hostile environment and now, you know, just hunker down and pray you don’t get hit by a memetic crossfire.\n\nSonal: That was a fantastic summary, Nadia, and I did, for the record, see that come through in the book. In fact I found it very satisfying because you didn’t, you weren’t self-indulgent. And frankly, as an editor, I’ll tell you, I find too much writing — particularly in the crypto space early on (I think it’s improved quite a bit in the last few years) — but, it can be very self-indulgent. <Nadia: Thanks!> You also said something that really stuck out to me, which is that (I’m quoting you): “What I finally come to understand is that how we think directly influences how we act. Though this may sound obvious, it is not widely believed in practice.”\n\nAnd then later on in the book, you come full circle and talk about how one of the only ways we can change — ‘cause this moves to how we actually move beyond just discourse, and into moving ideas to action — is to actually change how we like control our attention and what we direct our attention towards.\n\nAnd we’ll talk more about the solutions, but I really thought that that is the key thing. Cuz you’ve written a lot about ideas: You wrote about idea machines. You wrote about other idea essays… It’s also about how to actually *change* things, which I’m glad that that was one of your impetuses for writing the book.\n\nBefore we go more into some of the action and some of the other observations you had, I do want to pick up on a couple of things you just said —\n\nSo one is, you describe the “super memetic game”. I think that’s so funny because that is what’s kind of happening in a lot of the public-square discourse. Kevin Kwok, I’ve heard him describe this (to me personally, at least) as like “cult building” — where everyone is just kind of building cults; and that’s creating a very different kind of online discourse. (I also have not found a lot of joy on these big public-square type social networks any longer because of that phenomenon.)\n\nSo I think that’s a very good way of putting it: That the super memetic game is also cult building.\n\nNadia: I haven’t heard Kevin talk about the cult-building, but I would definitely agree with at least the way that you’ve- you’ve framed it.\n\nYeah! I think cult building is definitely another way to think about it… And just briefly to summarize what “super memes” are: I describe them as ideas that are highly consequential, and spread very rapidly.\n\nSo, if memes are sort of these, you know, quick mental sugar… you know you consume a meme, you pass it on, and you kind of forget about it.\n\nSonal: Yes. Simple sugar <chuckles>\n\nNadia: Simple sugar, right?\n\nAnd anti-memes are kind of this like high-fiber, dense thing, where it’s like you chew on it for a really really long time, and you don’t spread it.\n\nSuper memes kind of combine the most dangerous of both of these qualities <Sonal: mm> where: it is both a dense idea, but also one that is spreading around — or a highly consequential idea.\n\nAnd so, the category of things that I would put into super memes are- often has some sort of apocalyptic quality to them, which means they really demand our attention — So things like the climate crisis or population decline, or existential risk from AI. It feels really really highly consequential and these are types of things that speak to our personal value systems, so they feel really important to spread: Some horrible crisis is going to happen in the medium-term future, and I need to do something about it. And that can marshal a lot of attention very quickly around it — and it can also attract a lot of talent and resources.\n\nAnd so you have these entire ecosystems that are forming around all these different super memes. (I go a little bit into a brief history of super memes in the book.) But, war was kind of the main super meme that everyone rallied around. <Sonal: yup> And there was one war at a time, and everyone who was expected to kind of drop everything they’re doing, redirecting their resources/ time/ attention towards that effort. And then then we kind of moved to having more like culture wars — but there was still sort of like a main culture war that was happening, and again, that’s sort of like where everyone’s mindshare was going. But right now it feels like that has even further fragmented into you can kind of like make your own super meme.\n\nAnd I think it does come from this innate desire for all of us to- you know, we have individual drives, things that we want to do; but then there’s also a drive to dedicate yourself to a cause that’s bigger than yourself. And that-that’s sort of what drives us to find super memes to pledge our lives to, right <yup>.\n\nBut right now there are so many different super memes floating around that we almost have like a marketplace of them: and it’s, you know, are you a climate person? Are you a fertility crisis person or whatever?\n\nSonal: Nuclear energy… or <Nadia: nuclear energy, yah!> Yah!\n\nYeah, no, exactly.\n\nI do also want to hear any of the critiques that you may have even heard on testing out, iterating on this thesis — like what ARE some of the critiques that you’ve heard of like, you know, the anti-memetic theory and the work that you put into this.\n\nNadia: I think a question that has come up (that I’ve heard come up) from a few people… is around sort of like: Where does the anti-memetic quality lie…? Is it in the idea itself? Or is it in the network that it’s being passed through? <Sonal: I love that question! ooh!>\n\nAnd yeah, I probably don’t flesh it out as much as I could have in this book. But, we talked about vibes, right — it’s like an anti-memetic idea could be made memetic if it’s packaged differently; the way that you frame an idea could be received very differently by people depending on how you talk about it. I think the idea of you know eat a healthy diet or something or exercise, like, you can package that very differently for a group of 22-year-olds versus people who are you know maybe older and dealing with chronic health issues and want to exercise for different reasons.\n\nThere’s different ways to package ideas, and that caused them to spread in different ways; and so — is it that the core idea is anti-memetic or is it that it’s just anti-memetic relative to the network that it’s in?\n\nI think there are things that we can do to make ideas more or less anti-memetic. You know we talked about the-the “go away green” paint that Disneyland has <Sonal: yes> — and I do spend some time talking about, about that of: How do you make ideas more obscure? How do you bring them more into the foreground?\n\nBut I think like ultimately, my interest lies more with the context that an idea is situated in, and, and with the network. Because I think to really understand like why is an idea being resisted, or why is it not spreading beyond like each node in the network, you really have to understand that broader context. So I think that’s probably more of where the anti-memetic power lies.\n\nSonal: So, it is in the network in your mind.\n\nNadia: I think so, yeah.\n\nSonal: And actually just to respond to… you did say very specifically in the book, quote-“Even though the core concept is roughly the same in both circumstances, changing how its message can help it spread more easily through different networks.”\n\nAnd I immediately thought of — just to give an analogy that relates/ connects to our audience — of *stablecoins*, which is kind of a hot topic right now in the crypto industry, fintech, and beyond; there’s been a lot of activity around it lately.\n\nAnd it’s fascinating ‘cause the ideas have been around for a very long time; they’ve gone through multiple iterations and forms. And, the value prop is very different for institutions, as it is for small businesses, as it is for like a Stripe, as it is for like a builder, as it is for just someone who’s crypto-degen… Like, it’s like the same core concept, but it, to your point, is packaged very differently.\n\nBut the other point you make — which I want to also just pause on — is that the same idea might be memetic within certain networks, but anti-memetic and others. Do you want to talk about that a little bit?\n\nNadia: Yeah I think maybe conspiracy theories are an example of this. <Sonal: mm!> Where, for some reason, an idea that seems sort of like fringy or you know just questionable could really take hold of a very specific network, based on how receptive they are to… to that idea — but then it doesn’t necessarily jump outside of that group, right? <yah>\n\nAnd I think the difference between a conspiracy theory versus an idea that was just sort of ahead of its time is: Can it make the leap out of that one network (where it like spreads very memetically), can it make the leap to other networks? Can it continue to spread on its own? Can it make it to super-public social feeds?\n\nSo yah, you can think of less extreme examples of that — but yah, if an idea can be very memetic within a certain network, but, anti-memetic if it just can’t spread beyond that.\n\nSonal: I wonder if NFTs fit this. Because I wondered when I was reading that line, it immediately struck me like in a way, NFTs became memetic — like they kind of jumped across networks and they hopped and they caught the imagination of many, many people more broadly… Like people almost thought like, it’s interesting: is culture the way that crypto adopts more broadly?; <Nadia: mm> we thought it’d be the other way around, or something else. And then they just took a different form: like the same idea that can be memetic within certain networks and then anti-memetic in others.\n\nNadia: Yeah, I mean crypto more broadly has gone through these waves, right — the booms and the bust cycles are themselves sort of when you’re in sort of like a quieter cycle, I hear a lot of people in crypto saying, that it’s nice because all those sort of grifters and self-interested people went away; and now it’s just the people who are here are the people who really, really want to be here. <Sonal: Exactly> And from the public- the outside view, people will declare crypto dead, or they’ll say oh it’s over now — and we’ve seen that happen over and over again, right, <yes!> where it’s like it’s just cyclical. And so it just means it kind of gets obscured from broader view, but it’s still alive in a smaller group, and then it’ll kind of bubble up and escape that group again.\n\nSonal: Yes! I love that you said that, this is very much our group’s thesis — like Chris Dixon and Eddy Lazzarin wrote a post called the “Crypto Price-Innovation Cycle” like in mid-2020 (it’s something they’d been thinking for even longer than that) – And, all of us who’ve been in the space for a long time, all-it’s exactly like you said, they view the space as evolving in cycles: And it kind of alternates between these periods of high activity or quote-“memetic times”; and like crypto “winters”, where, it’s anti-memetic to the world, but there’s still activity happening in these smaller or bigger pockets that are not like legible to the rest of the world.\n\nAnd- and it’s exactly as you said, Nadia: Some of it is a flurry of activity — like assets, prices, and the speculative activity — that then leads to new interests; and social media activity, it leads to more people getting involved, contributing to new ideas, open source code, leading to new projects, and startups getting creative — and then leading to product launches that actually inspire people.\n\nAnd then of course, if it burns out, then there is this group of people (like you observed too), that then are sticking around and still building. And with each cycle — and we’ve seen like three or four now maybe, maybe five? — but it’s like really interesting because they show the data to like how each wave brings in new people, and then that group stays to build. So it’s like a very iterative thing.\n\nAnd I’m so glad you brought that up because it’s very relevant to how ideas propagate (which I do want to talk more about) — before we do, I have some critiques too —\n\nNadia: That would actually be very fun to talk about.\n\nSonal: Yeah!\n\nSo one is, you describe the “balkanization of the internet” — But basically, if you think about these group chats (or community containers, whatever we want to call it): Is there kind of a homogeneity that happens?\n\nBecause on one hand, you argue that you’re actually seeing ecosystem diversity — your “memetic Galapagos” actually — but at the same time is it also creating this kind of high- homogeneity within group (in the in-group part), where people are just really not being truly infected with new ideas.\n\nIt’s almost like, are they all thinking the same — thinking they’re different? <chuckles> <Nadia chuckles, yah> Or like I don’t know how you would characterize this; I’m curious for your thoughts (because I for instance left a lot of them because I couldn’t take it).\n\nNadia: This is where we air our grievances about group chats. <laughs>\n\nSonal: Yes, exactly.\n\nNadia: Similarly, you know, I-I’ve noticed this dynamic as well. I’m sure there is a really great project here for someone to dig into, of just like all the different types of dynamics in people’s group chats. (I’m sure someone has already started to study this, but.) You know, there’s some group chats I really cherish because it’s just me and some of my longtime friends, and it feels like no one is trying to push an idea or anything like that. You’re just hanging out, right, you’re hanging out in this quiet space.\n\nBut then there’s also group chats that are formed around a specific purpose or idea that is bringing them together.\n\nThere’s also these sort of higher-volume group chats… Like I feel like the dynamics in a 5-person group chat are really different from the dynamics in like a 100-person group chats.\n\nAnd then you end up in this weird uncanny space where — yeah, I think I felt uncomfortable in a lot of these more, let’s call them like “impersonal group chats” I guess — where the speed of message is just super super high volume; and, I think about sort of how does information spread in a very small group chat in these sort of like larger ones versus out in the public…\n\nAnd then there is this strong sense of like groupthink being reinforced very intensely in some of these medium- to large-size group chats. <Sonal: yes!> Where it’s like, you’re kind of all there to agree with each other or to boost an idea… you’re, but critiques are not really welcome. (Or, it’s not my vibe, so I don’t really participate very much in them.) But that’s sort of my own experience with it, or how I feel about it.\n\nI *do* want to be careful not to overly moralize <Sonal: of course> any one dynamic or another. Because I think these are also just features of how the internet works now. And, it’s good to know that it exists.\n\nSonal: Right. And I agree with you; I mean you pointed out yourself, networks are made of people. And these are just groups of people interacting. So we’re going to have the same dynamics.\n\nThat’s actually one of the things I also wanted to bring up: And that at least in medium, larger ones (maybe not personal ones; they’re also about work and professional engagement) — there’s also I think, this phenomenon that where people can be a bit performative? And we tend to believe… — this is, I think, the mistake a lot of people make when they think of smaller or self- organic communities, or bottom-up communities, or people who around shared interests — they almost act like hierarchy doesn’t matter. <chuckles> <Nadia chuckles> And it’s like actually it’s still there, and it may even be more- it might be worse in some ways, because you’re not even being explicit about it anymore. Like there can be a very clear hierarchy, like some dominant people; and then you have these other people —\n\nBecause here’s what I-: My experience, Nadia, has been that there’s a conversation that happens in the group chat. And now there’s like a shadow conversation that’s below the group chat, <Nadia chuckles> where people are side messaging and one on one, “I don’t actually really agree with that person”. And it’s like these group dynamics are actually being exaggerated in a funny way, by the very container of the chat.\n\nI don’t know if you’ve noticed this, too. <Nadia: yes!> — it’s almost like they’re performative for like the-the big honcho in the group, and then they’re privately like grumbling about it to each other; it’s like so funny.\n\nNadia: Yeah, I’m sure there’s some axiom for this at this point – “For every group chat exists, there’s also like a side group chat.”\n\nSonal: “An anti- chat” <laughs; yah exactly!>\n\nNadia: “And if you don’t know that the group chat exists, then you’re the person that’s being excluded from that group chat.”\n\nSonal: That’s exactly right…! Yes. Maybe we’ll call it Nadia’s-Nadia’s Law or something. <laughs>\n\nNadia: Someone else has coined this.\n\nSonal: Yeah, we don’t want to put your name on it. <both laugh>\n\nNadia: But yeah, it’s sort of like like a small-town kind of fallacy as well — of well we tend to idolize the idea of like, oh wouldn’t it be so nice if I lived in a small town; and everything would be so peaceful here.\n\nBut anyone who’s lived in a small town can also attest to like gossip flies around like crazy; everyone is up in each other’s business, <yah> — because it’s much smaller and everyone knows everyone. So, it’s not really quite as nice and bucolic as it might seem. <yah>\n\nIn some ways, living in a city can enable you to be a lot more faceless and-and reinvent yourself constantly. <yes> So, yeah, I think similarly here, there’s trade-offs to both group chats and public social feeds.\n\nSonal: Of course! <Nadia: yah> Two more quick critiques —\n\nOne is (I don’t know if you’ve noticed this too), I would add: Kind of an untethered proportionality… So this is kind of like, what I would almost call like voodoo math, or “group chat math”, <chuckles> which is: There’s this funny thing — and I’ve seen this particularly in people who talk about media a lot; because I’ve obviously, you know, been building a direct media operation for many years now — and it’s funny, because the data and scale that people talk about is so untethered from reality.\n\nSo, I have like one or two people who will tell me like ohmygod, this person has a massive newsletter — and you worked at Substack, you know you worked at GitHub — and I’m kind of like, they have like 300 followers on that newsletter. <chuckles> And you act like it’s like thousands of people. Or ohmygod, this person has a massive media empire; and it’s like you know 20 subscribers to this Q&A (or whatever it is).\n\nAnd I kind of chuckle about it, and I think it’s because there’s this almost… When you spend ALL your time in group chats — without the balance of the public square and other data to tether you a little bit to reality — I wonder if there’s kind of like this opposite thing of an anchoring heuristic that happens, where: It’s almost like instead of being anchored to a certain number, you’re actually disproportionately… you’re unmoored and unanchored to numbers. I don’t know if you’ve noticed this, it might just be me.\n\nNadia: I definitely noticed this when I joined Substack. I actually had this huge moment of coming to reality or something �� ‘cause this is during a time where there was you know a lot of contention and conflict between what people (other people) would call like tech versus the media. Right? <Sonal: Yes, yes. I remember that well> … It was a time! Yes. And I got to see a lot of that happening, you know I had a front seat because I was working at Substack at the time;\n\nAnd I remember coming into it being like, you know, what is my idea of — exactly as you said <chuckles> right, I was one of those people — what was my idea of a big newsletter, someone with a big following? Because we were still trying to acquire new writers to the platform and stuff. And so trying to think through like what- who is considered big. And I came quickly to realize that my idea of what I considered “big” within the world of tech was…\n\nSonal: Is not big. Exactly.\n\nNadia: Is not that big! <Exactly!> I didn’t even realize how big <yes!> the New York media ecosystem was. <oh!> All these writers that were getting, that had… When I was trying to think of, like, who are the biggest tech accounts I know or something, to me these people were titans; they were drops in the bucket!\n\nI came away from it very humbled, where I was just like, <yahh!> ohmygosh, I had no idea this whole world exists <totally!> I feel like this country bumpkin, sorry <chuckles>.\n\nSonal: Oh I feel happy you’re telling me this though, because sometimes I feel like a crazy person, maybe I’m — later we’ll talk about the truth tellers and champions; but sometimes I feel like not just a truth teller, but a Cassandra, <both chuckle> to use the Greek mythology, where I’m like this person who’s saying, this is happening and no one’s really hearing, do you even hear it? — So I’m kind of glad to hear you say this, Nadia.\n\nNadia: I think maybe you’ve noticed it as well, because you do have more exposure to sort of like art world and media world outside of just, yah (the world that we occupy).\n\nSonal: Well, the example that comes to mind for me is — like, I’m a big fan of Slate Star Codex/ slash Astral Codex, Scott Alexander’s writing… But it’s funny, ‘cause he wrote a post where he publicly revealed this (which is why I say this) — He’s like oh, I had this piece that went viral at like 500,000 views or something.\n\nAnd I’m like, what?! I had pieces at Wired that, it had 12 million views in a day. Like, what are you even talking about virality? And that’s why when people attack Fox News (or whatever media outlet people are talking about) — it’s like crazy how massive these numbers are.\n\nAnd so… Anyway, I’m glad to hear you say that about this kind of data-proportion effect, because it really do feel like there’s this weird distortion that happens.\n\nBut I do want to also say on the flip side: Maybe that isn’t the point. Because it can also just be like, maybe you just need to reach the right people, or maybe to interact with these ideas — these anti-memetic ideas, especially — you just need to be with the group in that quote-“cozy web” (that you and Venkat describe) to-to … you maybe only need to reach those people.\n\nNadia: That’s the thing; in a weird way, I think it almost doesn’t really… <Sonal: matter!> matter <Sonal: yah> if in your world… Again, like I think all these dynamics are reflected in non-internet examples as well.\n\nSo like, back to your hometown — gosh, there’s this tweet from years and years ago that still lives rent free in my brain, of someone asking, growing up, who was the richest person that you knew or something? <yah> — And if you If you then move to a city or something, and you have a different perspective, you think back, and you’re just like wow, that was like the biggest kahuna in town <yah!> that I could think of <Sonal chuckles> is like this…\n\nAnd it’s like, it’s all relative, but it doesn’t really matter in the end, right, like I think relevance is super highly context dependent. And so if that person is the biggest person in your world, that’s okay, um.\n\nSonal: Exactly. Well, particularly if that’s who you listen to. And that’s all kind of that matters, if we’re talking about —\n\nNadia: Yeah, engagement is what matters, right?\n\nSonal: Exactly; or persuasion — like, why ideas spread and some don’t — like, if it has quote-“impact,” to use the word you use in the book, then that’s maybe how you measure that. And that’s all that matters.\n\nOkay! So the last kind of critique/ open question is on the other theme that you don’t really explicitly say in the book, but it’s kind of underneath the surface, is: You talk about like, these things are happening in the dark forest —\n\nYour book is published by the Dark Forest Collective by Yancey Strickler… And you actually talked about the dark forest (analogy) in the previous book, Working in Public (We also talked about it in our previous podcast; I’m a big fan of “The Three-Body Problem” trilogy, read all three books, and the fanfic book after that). And just for listeners who don’t know the dark forest analogy:\n\nYou know, it’s kind of this idea that, playing on the Fermi Paradox, that we live in space, in this completely dark forest invisible to other civilizations. And when you make yourself visible you can actually… be destroyed. Because then you’re no longer in that dark forest. It’s a very gross oversimplification, but —\n\nAnyway. The question that comes up for me as another critique/ slash opportunity is: There’s a lot of knowledge buried in these group chats — in these communities, and towns, and islands in the Galapagos archipelago — that’s not made visible to one another. And that’s not even made visible to any other machines/ readable. And so there’s this huge like, what is tacit versus made explicit?\n\nNadia: It’s kind of… I think it feels like a shame for those of us, including myself, who grew up – remember in the early internet days, and where everything was indexed and searchable? It feels kind of sad to be like oh, but now a lot of that is not easy to find — I think that’s true (for what it’s worth) even beyond the group chat context; I mean, yeah, there’s a lot of even just highly public social content that is no longer indexed or easily searchable <Sonal: yahh> — especially with the move to video and things like that.\n\nI try to take — and this this ties into the critiques I think that people have right now about whether our culture is stagnating; or you know are there any good ideas left, or are we just watching the same Marvel remakes on repeat over and over again — I actually, I think I have a, I tend towards a more optimistic view of it of:\n\nYeah, we’re losing probably a lot of tacit knowledge — partly because it’s not being you know indexed or searchable in easy ways — but also just because a lot of is happening in these dark spaces.\n\nBut on the flip side, it’s almost like, it’s partly because there are SO many ideas now floating around. And you’re almost… in this position of, being fattened by like all these — like I think the bar has actually been raised quite a bit in a weird way for culture. <Yes> And yes, if you look at the lowest common-denominator forms of what people are consuming, maybe that paints a bleaker picture — but if you grew up in a small town (I grew up in the suburbs), it’s like you’re deprived of culture, you’re in a culture desert, right, and you couldn’t access it in any other way. And think a lot of actually — I have some hunch that a lot of internet-y people came from these culture deserts, and they turned to their computers to like find what they were looking for.\n\nBut now there’s like, there’s so much more available… it doesn’t really matter where you geographically are, <Sonal: yes!> you can consume so much more interesting stuff.\n\nSo, yah, maybe it’s getting hard to make sense of it all — but even if someone were able to organize all that information, make it available, would we even have time to consume it all.\n\nI feel actually fairly optimistic, that the quality of ideas that we have access to has probably never been better… It’s just — and this is where it comes down for me a little bit down to like, well, what do you want to choose to pay attention to: If you are spending all day scrolling on really stupid videos, and then you’re complaining about you know like where is the culture; well, that’s kind of on you, I feel like. <Sonal: Exactly> It’s like you can choose to spend your time focusing on the things that you’re actually interested in, or consuming and stuff you’re interested in…\n\nI don’t think it’s quite as easy as saying, this is just a personal-responsibility problem. But, I think the information is at least available to us. And then the conversation should be about how do we get more people to pay attention to the things that are… high-fiber ideas versus yah the mental sugar.\n\nSonal: Yah, to use your di-diet analogy, in terms of complex and simple carbs <Nadia: Yah complex and simple- > Yeah, yah exactly. And you’re right, like the higher-fiber things digest better, they stay in your system better, that you chew on them more.\n\nThe simple things are kind of quick-hits, flash floods! ‘Cause like, let’s go to the question — you’ve been talking about it throughout this podcast, but if you were to summarize, why *don’t* ideas spread? — You know, you talk about this phenomenon where some things can be just a flash in the pan… but then they don’t really take off, or carry on? You even talk later in the book about phenomena *not* taking off that should — to be able to propagate an idea and really see it through its conclusion. (Because I want to shift into talking a little bit more about solutions and opportunities.)\n\nNadia: Well I think ideas don’t spread in the anti-memetic sense because they’re perceived to be super consequential. But it sounds like you’re yah maybe asking a little bit more about like, why – why don’t we make progress on ideas?\n\nSonal: Yeah, that’s actually the question — but is it only that it’s super consequential, Nadia, because that was one of the prongs I thought… But when I read your book, I read it more as: There’s also just some things we just don’t seem to see, period. Even if they’re not that consequential. I mean, tell me if I’m wrong, but that was also my interpretation.\n\nNadia: Yeah, I think that’s true. I mean, I talk about this in the context of bureaucracies:\n\nSo, Richard Dawkins, when he talks about memes — he has this also this idea of “memeplexes”, <yup> which are just sort of like a cluster of memes, right. So, you can think about like a political ideology or religion as sort of like a cluster of a lot of different memes that form this bigger thing —\n\nAnd so there’s like a version of that for anti-memes, where you have like an “anti-memeplex” that <Sonal: it’s bureaucracy> that I think, yah, looks a little bit like a bureaucracy.\n\nIt’s like, yah, a bunch of smaller anti-memes that have conspired to make you *not* look at the thing. And so, yeah — like healthcare-healthcare reform might be an example of this; or journal publishing and scientific research or — you know there’s a lot of these systems where you’re just like ugh, it feels bad, but I can’t seem to look at it or make sense of it or anything like that.\n\nAnd so yeah: Why can’t we seem to make progress on some of these ideas that really resist being looked at?\n\nSonal: Got it. It really is a question, not just of why these things don’t spread, but why don’t they take off — so how would you summarize *that* portion of the book and thesis.\n\nNadia: Yeah I think, a lot of this comes down to where do we allocate our attention…\n\nIt’s nice to talk about networks in this very sort of abstract way — but like really, when you drill down, what is the network made up of? It’s made up of individual people, individual nodes in the network. And so to really understand, like, why something doesn’t take off a network, you have to kind of go node to node <yes> and say, like why does it not spread from one person to another.\n\nAnd when you’re really, really zooming in, then it’s: Where is someone choosing to allocate their attention? Are they avoiding looking at something because they’re afraid they perceive it to be really high consequence for themselves or for their network? So these are all these different levers I think that you can start to-to point to.\n\nAnd then I think there’s, on — zooming back up to the network level — there’s also this question of like: How do we collectively remember things, right: So there’s like the individual question of like, as an individual, how do you choose to remember or forget something? But then on a collective level, how do we- there’s also this question of: We know that we want to remember something as a group, how do we remember them?\n\nAnd this is where I think institution building ends up becoming very important. Where, you know we need to write things down; having formal rituals to (or processes) to sort of like resurface things into our memory… And, yeah, like how do you make it possible for someone to sort of pick up the work and-and can continue on with it. And this is where I talked about this role of champions, and you know, for most people, if they’re looking at some really… you know tangled up problem, most people are going to look away from it. And maybe that’s fine. But there’s going to be someone out there where they look at it and they go oh, that’s an interesting problem; like I want to spend some time on that, right. And so just really encouraging people to lean into that.\n\nBut, yah; as we think about sort of like collective remembrance, then it’s… as someone is working an idea, and as they step down or as they rotate out, how are they sort of preserving that knowledge for the next person.\n\nSonal: Exactly! <crosstalk> That’s exactly what actually prompted the question about tacit versus explicit.\n\nBecause, when you talk about like you know college campuses, like as a great example of a place where ideas can quickly spread, but then kids age out: like they only are in campus for four years. And so they’re booted out of the system, essentially. And then this next batch comes in. And-and that’s only one example.\n\nAnd I don’t know if you have a concrete idea here, because of all the work you did in the open source world — Like is it documentation? Is that how people make the tacit explicit?\n\nI come from — you know, <Nadia: yah> my earlier career (as you know), was at Xerox PARC — and they were pioneers in the first knowledge base systems, because they were trying to scale both knowledge across enterprises. This is back in the day when companies would be around for 100 years, but people would generationally age out — and then they would also try to scale expertise; so like someone senior (like a senior copy person) could help a more junior technician in the field without sending out expensive people every time.\n\nSo there’s like a lot of interest in knowledge-work documentation and making tacit knowledge systems explicit, etc. — like do you have any thoughts on how to do that, like concretely?\n\nNadia: Yeah it’s a, unsolved… as you’re pointing to, <yah> there’s an entire industry around trying to solve this problem <totally> so I don’t- I have no magic bullets here, for sure.\n\nBut we definitely saw these dynamics in open source projects. <yup> There’s this, you know, so many examples of a maintainer that has sort of just gone M.I.A. on a- on an open source project, and it’s still critically used; maybe there’s some security update that needs to be pushed through, and the maintainer is just sort of like nowhere to be found. That- that presents a problem. <Sonal: yah>\n\nThis question of successorship, right, like, how do you transfer a project to someone else?\n\nThere’s also examples in the opposite direction where someone comes on and says, hey like I want to help with this project — and the maintainer is maybe overburdened, or just not thinking about it that much, <yup> and they hand them the keys to the castle. And then that turns out to be a malicious actor who then does things you know that aren’t great to the project.\n\nSo you know it’s hard to think about sort of like what is the right way to do it.\n\nI’m always a fan of documentation because I like writing, and I like writing things down. So, yes, documentation is great. But the reality also is, a lot of people don’t read documentation — and so, <Sonal: exactly> write it in a way that if you’re too detailed, and it’s too complex, and people just kind of tune it out. And so, how do you give people just-enough information <Sonal: mhm> that they act on it?\n\nSo, yah, I think documentation is great, but not the only answer… Like, it’s unsatisfying, but it’s like personal relationships: It’s like, someone that you really trust — or maybe someone who has just learned by observing you on, in this case, an open source project — where it feels like okay, I can hand this off to that person.\n\nThat might just feel better and be more successful than someone who’s kind of like, I read all the docs! — but doesn’t really know how something works in practice.\n\nSonal: Totally!… Well, the example that comes to mind for me (and I actually did this interview a number of years ago on this podcast), was with Tim Beiko at the Ethereum Foundation. <Nadia: Oh, yay!> Yeah, love him. <Nadia: Love Tim>\n\nAnd he was talking about how they do the community calls…And he does such a lovely job of like, basically this decentralized coordination across many different entities (you know because they have this multi-client diversity in the ecosystem, that there’s a key value for them). And then how do you kind of coordinate?\n\nAnd it goes exactly to what you said: It’s a lot of the human stuff, like, just talking about it. Like, people aren’t going to read the notes and talk about it. So, you know they have these community calls, every week, every month (I can’t remember); but like, they pull off massive feats of coordination — like The Merge — using those practices.\n\nSo I don’t think it’s (to your point), I think you’re right to be optimistic that these solutions will come about because people are already doing this at a scale — without a center. Like, it’s a centerless network, to use your analogy in the book.\n\nNadia: Yes, definitely.\n\nSonal: The other question I had for you on- along this theme of problem/ solutions, what to do, is in the chapter on the memetic Galapagos — I’ve actually been to the Galapagos multiple times… <Nadia: Oh wow!> it’s one of my favorite (favorite!) places in the world. It’s like a dream spot for me because I was obsessed (still kind of am), with Darwin’s theory of evolution, how it came about, just everything about it.\n\nAnd, it’s interesting because one of the things you talk about in the book — you already talked about this on the podcast, like, you talked earlier about how isolated environments lead to “greater speciation and biodiversity” (which was obviously famously discovered by Charles Darwin’s study of finches across Galapagos Islands) —\n\nYou then talk about how group chats are like social islands; ideas evolve even more rapidly in a private online environments: “They’re tested, iterated upon, and refined” (I’m quoting you) “with little outside influence to temper the process as they adapt to the unique dynamics of their members, much like Darwin’s finches” —\n\nYou also then talk about like, that you know, many people are probably part of many different group chats/ slash communities. And therefore quote-“Perfectly capable of crosspollinating ideas that are being incubated in these highly concentrated environments.” And you gave a funny analogy: It’s like spending one’s days moving between several poorly ventilated rooms instead of walking around all day in the fresh air.\n\nSo, it’s the conditions for idea viruses to grow and mutate.\n\nBut then… I wonder how much they actually do spread *across* these islands / slash group chats / slash communities. Like, what-what have you seen or what do you think about them actually spreading, and truly connecting across these networks?\n\nNadia: I think some of the context in which I was thinking about ideas mutating and taking on these sort of strange qualities they might not have otherwise — One of the examples I mentioned in the book was this plot to kill a standing governor. Which kind of emerged from a lot of disgruntled people being trapped in these sort of, metaphorically, poorly ventilated rooms: Where they’re airing their grievances. <yah> And then those grievances start to feed into each other, and they start to bubble up, and then it turns into a real life plot to kidnap and kill a governor; which was thankfully foiled.\n\nSo in that case, it’s not really so much about how much is it hopping from one place to another — but more of how is it fermenting <yah> in this contained environment. <yah> You know to your point earlier about just this reality distortion that happens <mhm> when you don’t have something else grounding you, that starts to feel like the new reality and it feels like it makes sense.\n\nSo yeah; I think it’s maybe slightly separate from the idea of <yah> like hopping from one place to <got it> another; I don’t know that I can pin down the exact-exact details of how something is spreading or not spreading.\n\nSonal: But are they supposed to connect… and are people like crosspollinating these ideas?\n\nNadia: Yeah! I think — beyond the context of sort of ideas mutating, getting very weird very quickly — this goes back to sort of group chats as a sediment filter for bubbling up into, into our wider feeds.\n\nAnd I talk a little bit about these dynamics as well of ideas that, or people, or books, whatever, that can feel really taboo and that you can’t talk about in a public setting. But people can talk about in like these smaller, smaller groups.\n\nFor a while, it’s not clear whether any other small groups are talking about it, or whether it’s just you and the people that you know. And, there’s sort of this — yah, testing of-of ideas that has to happen at some point, where it’s like the blobs start merging together, all the different groups start merging together. <Sonal: yes>\n\nAnd so it’s like, you know, is this safe to talk about with a totally different group? Oh, it is; okay, that means like *that* is also marked safe, right. But sometimes it happens where you share an idea with a broader group <chuckles> — and I can think of many examples <chuckles> of this happening in social media, right, where someone says something out loud, and then it turns out, oh, you should not have said that; like please, put that back <yah> — And so then you’re failing the test, right?\n\nBut yeah, I think the smaller groups can feel like a safer place to sort of test something out before it, yah, it jumps to the next group. And then if it keeps jumping, then you start to see these social scenes form. And then eventually sort of a taboo can make its way into mainstream discourse.\n\nSonal: Yeah and maybe it doesn’t even have to connect because I think sometimes these things just kind of boil…– maybe just not accidentally; I mean, we haven’t studied the topologies and-and spread in these networks super scientifically — but like, just in the zeitgeist: You see like when a movement that boils up, and then it kind of recedes, and then there’s almost a backlash that can happen (backlash, <mhm> and counter backlash, and backlash to the backlash). And it’s just, I just kind of wonder if it’s also like a zeitgeist shift, like a general vibe-shift that happens:\n\nMaybe a time has ripened — I don’t know how to quantify this, ‘cause it’s such a loosey-goosey concept — It’s just kind of like: an idea has had its time; it’s flashed, it’s spread memetically; the anti-memetic thing is kind of sitting across all these different islands… and even if they don’t connect to one another, at a certain point in the future (even though we can’t concretely quantify it), it does feel like some things can happen in the zeitgeist without connecting and crosspollinating.\n\nAnd it’s quite funny because I mentioned I went to the Galapagos multiple times: When you go from island to island, they make you wash your feet, so the sediment, like the sand doesn’t spread from island to island <Nadia: oh wow>… Yah! And that is kind of funny that you use a sediment analogy in the book, because the filtration — I mean, they’re trying to keep the biodiversity very pure and clean for you know ecological and tourism and other reasons — But when you go island to island, like you can’t crosspollinate. They will be so careful.\n\nAnd granted, it’s an analogy in your book <chuckles> I’m not trying to make it literal <laughs> — but it’s funny, because that really struck me as one of the unique things about: When you have biodiversity, you kind of have to maybe not crosspollinate it to let it just be what it is… To protect this very thing you’re talking about, this anti-memetic quality — maybe they don’t really need to crosspollinate (at least in the ways that we conventionally think they do).\n\nI don’t know — it’s a Dark Forest-related thing too, actually. <Nadia: Yeah, I think there’s something there…>\n\nSo okay. What I want to do now is just talk specifically about some technology solutions, opportunities… I also want to talk about specific roles you outline in the book — Let’s talk at an individual level, and then let’s talk at a kind of broader substrate level — like the Dark Forest/ macro level.\n\nBut at the individual level, you talk about three different entities in your book (not all in the same section):\n\nOne is the role of the “truth teller”;\n\nThe second is a role of a “champion”.\n\nAnd then throughout the book, you talk about “nodes” and “gatekeepers”, kind of interchangeably, and essentially us as individuals are nodes in these networks…\n\nAnd so I’d love you to tell me a little bit more about what those roles are, why they matter.\n\nNadia: Sure! Let’s start with the nodes or the gatekeepers, since that’s sort of the most general- generalized role — I know we touched on this a little bit earlier in this conversation, but yeah,\n\nI think ideas are often talked about sort of — like, even what we were just talking about now, sort of like — how do they come onto the scene? How do they spread through a network? <Sonal: yah!> We’re looking at this like very high network level…\n\nAnd so I spend some time, and in particular, in the chapter about attention, just zooming all the way in to say okay, well, how are these ideas actually spreading from node to node or person to person? And a lot of that being, I think a function of where someone is allocating their attention; But also, these dynamics around… It’s not just that ideas go viral or they don’t go viral — I think that’s a very flattened way to think about the spread of an idea. Because as we all know, there are plenty of good ideas these days that people are intentionally not wanting to go viral or not sharing with their broader networks — So why is that.\n\nAnd, and I use a couple different examples taken from epidemiology just to think about: Okay, it’s possible for someone to you know be infected by an idea, but choose to not spread it to their other connections for some reason; they just kind of hold on to it for a little bit. Someone can be presented with an idea and it just completely bounces off of them, just you know, not infected by it at all.\n\nAlso, the symptomatic periods of do <Sonal: yesss> does an idea pass right through you? Do you sit on it for a really really long time? All these things can sort of add a lot more nuance and complexity to whether an idea is simply going viral or not — which I think just assumes that oh I receive it, I pass it on, and you know just give me the next idea; it’s like an assembly line or something — like that’s not really how ideas spread.\n\nSo that’s some of the context around the idea of people being these nodes in a network.\n\nAnd then I particularly hone in on two… two roles that I think are particularly influential in a network — and that’s the role of the truth teller, and of the champion:\n\nThe truth teller is someone who can sort of shake a network out of its collective suppression of an idea. And so the you know simplest metaphor for this is the child who says you know “the emperor has no clothes”, right. Everyone standing in the town square in the parade knows that the emperor has no clothes, <Sonal: right!> but no one can say it out loud. And the only person who says it is this small child who can kind of blurt it out. And then everyone goes oh, gosh, you’re right! You know how did I not see that? <yes>\n\nSo I try to drill a little bit into the dynamics of what makes someone a truth teller, and I think fundamentally, it’s someone who has (is perceived at least) to have no skin in the game or no agenda <Sonal: agenda, yah, exactly> Right, it has to be someone who stands out a little bit as an outsider. And everyone can kind of trust that person because they say oh, well, you know, this person just waltzed in and said it’s okay.\n\nAnd I think this is fundamentally where a lot of religious leaders or figures can-can play a role because a lot of anti-memetic knowledge is treated as sacred — because it’s really difficult to unearth, whether from a group or from yourself in your own psychology. And so we can trust someone where we can go to a confessional booth and tell a priest our deepest darkest secret, and that person can kind of hold it for us right; you can have like a soothsayer or an oracle who’s like saying these things out loud, that’s no one else can be trusted to say, but it’s okay if they say it.\n\nAnd then in a secular context — and this is also true for a lot of how consulting works, frankly, in large corporations — where the employees and the people that work there can’t say something that might be- that everyone knows is true, <Sonal: yes> but you can pay someone to come in from the outside and deliver the same truth in a nicely packaged report. And then everyone goes, oh! yes, of course. This is the… you know; and it makes it okay to talk about. <yes>\n\nSo we have these sort of like interesting rituals that we’ve developed in many different contexts to welcome this role of a truth teller or recognize it. But I think it’s really important that we have truth tellers — because without them, we end up in this state of like, high-highly suppressing a lot of truths that we really need to be acknowledging as a group. And you need you need that role of someone to shake you out of it.\n\nAnd then the last one is the champion, which <Sonal: the champion! yup> yup, which we’ve talked about already a bit.\n\nSonal: Yah but go ahead and restate it because I think it’s useful in this taxonomy.\n\nNadia: So I think a truth teller is someone who’s sort of shaking us out of this collective mode of-of suppression – you know, we might temporarily look at the truth and then it all fades away, right. So if you think about the consultant delivering the report:\n\nEveryone reads the report (maybe); and then they go, oh, this is very interesting insight. It’s possible that when the consultant goes away… nothing ever gets acted upon; it’s like oh that was a nice moment where we all acknowledged the truth, and then we all forgot about it and moved on with our lives. <Sonal: totally!>\n\nSo what you need is someone who is a champion. And the champion is someone who is taking it upon themselves to make sure that we don’t forget this truth that we all temporarily looked at, right — ‘cause that’s the problem with anti-memes, is we can look at it and then it kind of fades from our memory —\n\nSo, again, just using those consulting examples: You know, maybe there’s someone who works at the company who is finally like yes, this is the moment! I needed to have some outside source of truth to force this to become a priority for everyone else who works in the company. And so now they have their — you know McKinsey report or whatever — and they can go around saying like hey, we spent all this time doing this- doing this project to point towards these truths, and this consultant has told us that these things are true; what are we going to do about it? But it needs to be someone on the inside who is really making sure that those changes are being implemented.\n\nAnd so — and this is I think, fundamentally how a lot of politics gets done, right, — because <Sonal: yes> the political machine is large and complex; there are an infinite number of issues that someone could be focusing on. And, all of that has to kind of be pushed through a system that is fairly limited in scope in terms of the amount of attention that can be allocated towards all these different issues that are competing for politicians’ time. This is why we have lobbyists; you can pay someone to go and make this their issue and make sure <yes> that it is put in front of, in front of a legislator to make sure it gets on-into a certain bill, or that a certain policy is passed.\n\nHow do politics actually get done? It- they get done because someone took the time to make this one very niche thing their problem, and <exactly> to make sure that everyone knew about it. I think sometimes people look at this and they go, oh that’s very trivializing; there are other issues that are more important than this. But I think it can also be really empowering because if you don’t like the issues that are being put on table, like you can be the person to be the champion for whatever you care about.\n\nSonal: That was a super helpful taxonomy ‘cause, I want this section to be more concrete. And that’s so relevant to each of us as individual; anyone can play all those roles.\n\nSo, a couple of quick probing questions:\n\nDoes the truth teller have to be external — or can they come internally from the network.\n\nNadia: Just sort of my first reaction is like, I think it does always have to be someone… not maybe not literally external, but perceived as having no agenda. <Sonal: exactly; yah yah>\n\nSo again, like a religious leader might be a very integrated part of a community — but there’s something that’s understood that like spiritual matters are a little bit separate from the other matters. Yeah, they can be trusted, they can be known — it’s not like it has to be a completely random person — but there has to be a sense that, like, we’ve all agreed that this person is somehow… stands apart a little bit.\n\nLike court judges also can kind of be perceived as having this role <yup> of like oh you know you’re- you’re somehow more fair and objective in perceiving this than the rest of us.\n\nSonal: Totally.\n\nAnd on the internal champ or the champion, not internal champions — I was thinking of internal champions in the context of sales and sales processes <Nadia chuckles> like; there’s always like, we talk about enterprise sales, any sales process, government, procurement, whatever it is, there’s always an internal champion —\n\nBut the flip side of that is sometimes the internal champion can also be kind of siloed. Like they’re a one-person department of X technology, so that the idea doesn’t get absorbed into the org or the target that you’re trying to persuade. So that person can also be set to the side.\n\nSo, the question around champions, is: The champion is just someone who carries the idea forward, or has some expertise in your framework. Is there like a particular hierarchy?…\n\nNadia: I don’t even think they necessarily need to have expert-… Or expertise can be learned in many cases on the fly; it’s like when I think of like, when I think of what is the most important quality for a champion to have, it’s just perseverance. <Sonal: Ah, Interesting> Just make this your thing and spend all the time you need to…\n\nSonal: Keep pounding at it. Yah, yah, that’s how you get the idea to take off, <right> to spread. Yah.\n\nNadia: Yah. Because the problem is fundamentally that people keep forgetting and not looking.\n\nIf you’re just being annoying and tapping people on the shoulder all the time, like that in itself is a service, right.\n\nSonal: And then the last question on the taxonomy —\n\nIf we are each individual nodes… It was interesting to me that you said “gatekeeper”. Like, what do you mean by that word, that each node is like a gatekeeper: Is it that we’re a gatekeeper of our attention, of information, of ourselves, of our curation of our filters and feeds? <mm>\n\nLike, what is the gatekeeper in this context?\n\nNadia: I think we’re a gatekeeper of whatever ideas we’re allowing to pass through us — <Sonal: yes…yes> and then flow on to someone else. Right?\n\nYou know, sometimes you encounter some sort of clickbait or rage bait, and I try to catch myself in those moments and go, okay, but am I doing exactly what the thing wants me to do — but maybe I just don’t because that’s…it’s… that would be the expected behavior, right.\n\nSonal: Yeahhh. And I think you even mentioned in the book that people are starting to do that on their own anyway, just because they’re becoming more familiar with this internet vocabulary of like how things work.\n\nNadia: Yeah! …I think we’re all developing a little bit of a better immunity, right, to the things that you might have shared unthinkingly 10 years ago, now you look and they’re like, uh I don’t need to share that right? <Sonal: Yeah, totally>\n\nSo that’s a good thing. We’re slowly developing maybe some immunity to these things. And I’m sure virus — ideas as viruses! — will continue to find ways to mutate and escape our whatever immunity that we’ve developed.\n\nSonal: I did wonder too if you need another role — which is kind of not like a town crier, but like the person who goes between places, and kind of calls out interesting things. <chuckles> Like in-in Hindu mythology, there’s like a-a character who does this — and it’s really interesting just from a storytelling perspective — and I feel like a lot of mythologies have this kind of person… Not like an oracle; but someone who just kind of walks around, and propagates info; almost like a storyteller-narrator?\n\nAnd the reason I was thinking of this because in crypto, a lot of venture capitalists who got into crypto h- all told me (and this is like a decade ago), that they were all at some dinner talking to Wences Cezares — I never met this person, but he was a founder of Lemon and a few other companies — and, basically, he was the one who kind of infected their mind (in a good way) with the crypto-virus idea.\n\nAs a spark — because it was still kind of anti-memetic in that time. And, I kind of wonder if there’s that kind of a role missing here: like a town crier type of person, or a walker of the roadwalker/ traveler? I don’t know <chuckles>; I was just, I don’t know if you’ve thought about it at all…\n\nNadia: Yeah, yeah, definitely — it’s like the person that is almost like a clearinghouse for ideas or something, but just like constantly sort of rapid-fire <yes> sending things out to different people. And I definitely can think of specific people that are like this <exac> in my own networks, who are just constant generous source of ideas, or just really good at infecting: Either-either they’re sort of like spewing out tons of things, or they’re so trusted that when they do share something, people really listen.\n\nIf I were writing a book about mimetics I would probably include that role… so that’s definitely a role. But yah, if <Sonal: This book is a book about anti-memetics, so you’re not, yah!> — but that’s definitely a very useful role, though.\n\nSonal: Quick question, where do you see the role of protocols? Because in your book, you actually talk about protocols — you even contributed an essay to the “Summer of Protocol” series that the Ethereum Foundation had funded, and that Venkat collaborated on as well; and he’s also a mutual friend of ours.\n\nI don’t know if you know this, Nadia, he was at Xerox when I was at PARC.\n\nNadia: Ohmygosh! I didn’t put that together… yah!\n\nSonal: Yah… So he and I first met in like 2006 or 5, something crazy. <Nadia: Wowww> Isn’t that crazy? I know. <Nadia: Yeah that’s totally–> I’m extremely fond of him and have huge respect for him;\n\nBut anyway, before you even answer the question, how would you define a protocol?\n\nNadia: As the term implies, I spent a summer thinking about protocols <Sonal chuckles> and writing this essay <chuckles> — so I spent a lot of time trying to get to a definition of protocols that I was happy with.\n\nAnd so in that essay, I define protocols as: “procedural systems of social control that simplify communication between actors”. They can help produce a number of decisions that need to be made. And they resist- some being managed by any one central place. They kind of like run on their own in a strange way.\n\nSonal: That’s fantastic. And it’s actually not that dissimilar from the technical protocol — in terms of communication between systems; < you know Nadia: mm> without a human in the loop necessarily — it’s not that different.\n\nIt’s funny, because Hayden at Uniswap, and I were at our Founder Summit last year, along with Colm Delaine, who’s CFDA fashion-award winning KidSuper — and so the three of us were talking because Colm was like, “What the heck is a protocol? Why do you guys all call everything a protocol? Why can’t you just call it X?” And Hayden’s like, “Uh-uh, how do I even define a protocol?” And I’m like “It’s just a way for systems to communicate.” And it’s like, <Nadia: yah!> you can automate it.\n\nSo where do you see the role of protocols in this, discussion?\n\nNadia: Yeah, I think if we’re thinking about the role of attention in how attention shapes which ideas we pay attention to or not <yeh> — protocols serve this function that can be pretty useful, where they can abstract our attention away — free us up to think about other things, right.\n\nSo sort of like automation for the mind <Sonal: oh, there we go!> where it’s like, okay, we have a, yes, a very clear way of: okay, when this thing happens, like here are the list of steps that we follow — and so, therefore, we don’t have to spend time thinking about it.\n\nThe-the piece I wrote for Summer Protocols was actually about sort of like the dangerous side of it (it was called “Dangerous Protocols”) and says like, yes, that’s great when you can sort of automate process and be running in the background — but there’s that sort of like, you know, the fantasia/ the Mickey Mouse thing <yah>, where suddenly you have too many protocols running and what if they start to get a little bit out of control? What if you want actually, do want to revise a protocol?\n\nWe’re not paying attention to a protocol by nature of what a protocol is — Sometimes we can start to become overrun by these processes that we increasingly feel like we don’t have control over. <yah> And that’s sort of like the bureaucracy problem too. <Sonal: exactly> Somehow all of this was constructed from scratch somewhere, but now it has become so complex and unwieldy, and somehow it really resists us being- us-us looking at it. And so now it has become very difficult to revise or even evaluate.\n\nAnd so I think that, that is an issue that can happen with-with protocols. But fundamentally, on the flip side, protocols are really important — just to have the ability to automate things that we don’t want to can- keep spending our attention on over and over again.\n\nSonal: That’s fabulous. I’m gonna do these last two as just lightning-rounds –\n\nDo you have any quick takeaways or thoughts for people in marketing?\n\nOne of the things I think about here is — like a lot of listeners to this podcast, people in crypto, people beyond — are very curious about how to package ideas: They know how to do things (at least) how to do things memetically.\n\nDo you have any thoughts on taking something from anti-memetic to memetic? One thing you already mentioned was packaging, which I loved.\n\nNadia: Yeah, I think it’s- it kind of centers around the packaging question. <mhm> I mean, the role of marketing is arguably taking things that are <chuckles> anti-memetic <Sonal: yup> and making them memetic. <Sonal: exactly!> So that is kind of the entire function of it.\n\nI would also suggest thinking about the opposite direction of taking things that are memetic and making them more anti-memetic — <Sonal: Interesting!> Maybe that’s the role of a… a PR and comms, and sometimes.\n\nSonal: Yeah, to hide things, let people forget things. That’s interesting.\n\nNadia: Yeah, you have the power to make things more obvious — but also the power to make things fade away.\n\nOne of the dynamics I do touch on in the book is that sometimes when we think about hiding an idea, we think of it in these very like, obvious sort of tamped-down ways: We make something forbidden, we put it behind a paywall, or we you know ‘ve forbidden access.\n\nAnd then sometimes that can actually hype up an idea even more, which can be a good thing if that’s what you’re going for — where it’s like oh this is a secret private exclusive event, and then everyone wants to know what the event is right? But making something truly anti-memetic can also mean making it, it can be more effective where you’re just kind of making something forgettable, and unremarkable — and just let it sort of like fade into the background. And, sometimes I think our egos can get in the way of that where it’s like well, if no one’s paying attention to the thing, I still want credit for like making the thing forgettable. But, a-a lot of anti-memetic work can be very thankless in that way.\n\nSonal: This ties to our earlier discussion about cycles in crypto — about how those anti-cyclical times were kind of quiet incubation periods, are very anti-memetic. And, you want that. You want that protected space to kind of do that.\n\nAnd it’s funny, because the other example: People in crypto marketing always talk about like keeping things with the kind of a degen vibe <Nadia: mm> or like making it nerd-snipey and not like over-explaining things, because you kind of want there to be this vibe that… — Not that it’s exclusive, because obviously the industry wants to grow, expand — But there’s always this tension: I mean, you’ve definitely seen this in communities where there’s like an early phase of adopters, and then a new phase, and a later phase; and there’s always a little bit of keeping some things intentionally anti-memetic.\n\nSo I love what you said that you can go the other direction. I think that’s actually super interesting and relevant to our listeners.\n\nNadia: It’s true for- in open source for sure, as well. Where it’s sometimes maintainers are trying to — not actively discourage contributors, but just there should be a little bit of a bar where it’s… you know if you make it too easy for everyone to kind of waltz in, then it gets overrun — so you kind of want, yeah, just a little bit of a “if you know you know”, vibe.\n\nSonal: No, totally. Exactly.\n\nSo then the last lightning-round actually on that very note about open source is: You have any like kind of bottom-lines for community management?\n\nAgain: What you’re talking about is group chats — but they can be just any communities… — It’s a kind of a big question to ask, but like, if you had one takeaway for people who are community managers; or people trying to nurture these kinds of communities, what would you want to tell them?\n\nNadia: Yeah one-one thought that comes to mind is that group chats have come with their own sorts of pitfalls that need to be actively managed.\n\nThere’s a feeling that a- creating a small group, a small community can feel like higher quality — but sometimes they come with their own strange dynamics around… Small does not equal better. <Sonal: yah> Ideas can kind of mutate in these strange and rapid ways: Not just the dynamics between people in a group; but also just sort of like what is sort of the idea-products that are like coming out of those conversations. Those can also kind of spin out of control in sort of unwieldy ways.\n\nAnd I think every community manager probably has experiences and knows this, but — yeah, just that still- active norms still need to be enforced and managed in those spaces to prevent them from getting out of control.\n\nSonal: Oh okay, great.\n\nOkay. So last minutes, let’s now take it back up — so we just talked about the individual level, these specific roles, the truth teller, the champion; the individual as node in the network, and also gatekeeper… — now let’s go macro and talk about the dark forest.\n\nAnd… do you have like a network topology… When you think of this, is the analogy/ the visualization — Is it just a bunch of islands, like the Galapagos, like an archipelago?\n\nWhen we talk about these communities and small, high-context spaces, is it like planets; like in the dark forest analogy, where it’s just a bunch of planets in the universe invisible to each other, but very rich in their own spaces?\n\nIs it houses? A city, a town? What-what metaphors <Nadia: hmm> apply in your mind.\n\nNadia: Yah.\n\nI found I’ve had a few different images come to mind — they’re all related, but probably all slightly imperfect — and actually, when, so when Yancey, who founded this Dark Forest Collective label that published this book… <Sonal: And also the co-founder of Kickstarter, yeah> Yes! — So he was the one had sort of, like, connected this idea of like dark forest to what was happening on the web in his essay, which came out in 2019:\n\nWhere he’s talking about yeah the public social landscape has become too hostile; and now everyone’s kind of withdrawing to these smaller, smaller settings. There was a slew of related essays and riffs on that idea that came out around the same time: So, Venkatesh Rao was writing about the “cozy web” — yah the idea that yah, we’re again, just sort of like burrowing down with our smaller groups — And then Maggie Appleton, who’s a designer, actually published this really nice visual of how she had sort of envisioned the cozywe-:\n\nShe had a nice graphic around this, and it looks, looks like-like geological layers of the earth or something, where it’s <Sonal: Oh! Interesting> burrowing down, deeper and deeper down. So that’s maybe one one way of thinking from the surface level all the way down to the bottom.\n\nI think as I’ve- yah as I’ve thought about it, it looks something like this highway — you know the information superhighway — of our very public social feeds. And then there’s like little exits you can get off at that are the-the smaller towns and things. Or… the early internet era was about building the highly public squares, and now we’ve finally managed to construct these, you know, smaller houses <Sonal: yes> where you can peel off and go have conversations.\n\nLike it’s kind of crazy to think about… I mean, really, what I think has happened when we take this sort of doom-and-gloom out of it — is that we built this incredibly… public place for everyone. And now we need to build some little like private <yes!> – private houses so that we can also continue to be in this online universe.\n\nBut also, like it’s just like wild to me that it’s only very recently that we’ve been able to have a private conversation online in the way that we are now able to today. So yeah; they’re not- these are all maybe similar kinds of metaphors, but those are some of the visuals that come to mind for me.\n\nSonal: That was super helpful, Nadia. And I- it’s so interesting, because it seems like it’s playing out in physical spaces, too, you know; people talk about maybe it’s a flash in the pan that living in megacities is the way —\n\nLike, we may live in a mega city, but our neighborhood is now really the container (however a person defines it): Whether it’s a community, a church, a physical geographical neighborhood, an online neighborhood… Like, we’re all kind of quote- “returning to smaller, high-context spaces” (to use your phrase) which is the whole theme of your book, whether it’s a group chat, whatever it’s called, interest group.\n\nSo then the other phrase you used in the book — and you said in the podcast a couple of times, too, <Nadia: chuckles> which really landed for me — was a “centerless network of networks”. And that I love… because when you think of the dark forest analogy, there isn’t a center of the universe —\n\nYou know, there’s like galaxies, there’s ecosystems, there’s planets. They can be in the same galaxy, they can be in different galaxies, there’s black holes that can suck you in (to use your supermemetic analogy). So I do think the dark forest is the right analogy…\n\nBut as a crypto person, I was very drawn to what you said about a “centerlessnetwork of networks”, because of course, I think of decentralization — which is obviously a big, big theme in crypto.\n\nAnd, the other context for how it connects to our audience is that if you think of blockchains as a substrate — you know, or a technology that has those properties (decentralized, permissionless, etc.) — then crypto can be defined as a coordination machine that can connect all the dots, without having to connect all the dots. (If that makes sense; going back to this whole Galapagos, like, you can wash your feet between islands and whatnot.)\n\nSo; anyway, it’s just funny because Chris Dixon used to talk about how the web is broken — he wrote a book, “Read Write Own.” And one of the things he talked about early on (when we were talking about Medium back in the days), how the social web is broken, and that we need some layer to kind of connect it — and lately, the theme seems to be really about crypto as kind of like a coordination machine… Especially because a big theme of his book is about how networks are destiny.\n\nAnd you basically say the same thing in your book: I feel like you’re basically saying that the network you are is who you are. That was at least a takeaway for me — is like the network you spend your time in is kind of destiny; it’s who you are, because what you’re thinking about is what you’re acting on, and being.\n\nNadia: I really… I wanted people to come away feeling like they can do something, or they know how to act in the world rather than…<sighs> Gosh, so much of what is being written about the world today is very defeatist, right; it’s very like, you know, “everything is crazy and just try to hold on and survive” or something. And I just find that to be such a depressing way to see- at least, let’s try to come up with something more positive.\n\nSonal: Yeah and I like that you’re not normative about it, which is also great.\n\nNadia: Yeah, yeah. Without being too like pounding-the-pulpit about it, the reason why I focus so much on attention — and that there’s one chapter that’s really about attention, and — yes, you know there’s a type of person where you can kind of roll your eyes and say, yes yes I know, attention is important, attention economies; blah, blah, blah —\n\nBut if you look at kind of what’s happening, lyou still can’t say it enough. Because I think people are still allocating their attention in poor ways, and then <Sonal: yes> sort of saying, well, why does the world feel so bad? And I really- I think sometimes attention can feel like this tug-of-war struggle where it’s like someone else is always trying to grab your attention and trying to snatch it back and whatever. And I think a lot of conversation is just around that of like: you know, malicious actors are trying to steal your attention, and you need to just grab it and hold- But then like we don’t have enough conversation around, well what do I do when I have all this attention.\n\nSonal: Yeah, exactly. I don’t want to be treated… I hate the nanny-stating of like I’m a person without agency. <Nadia: yah!> Like I have choice…yah\n\nNadia: Yeah. And I think that changes the conversation where it’s not just about preserving your attention for attention’s sake — But if people have goals that they’re really excited about, you will make the time, <that’s abso> you will find the attention when you’re absorbed in something that you’re really excited to do.\n\nAnd so I really want to challenge people to think about: What is it that you actually want to do with all this attention that you have?\n\nBut then for them to also believe that, like, it’s possible to, if you don’t like the reality that you’re seeing, you know, there are things you can do to make your reality better.\n\nSonal: Well, and on the builder note, you have a choice now. <Nadia: Yah> you know there’s other social networks, there’s no longer only the one public town square that we had in the first phase of the web… And it’s a wonderful note, I think, for us to end on: Because it’s such a positive, optimistic, pro-person <chuckles> view of networks as destiny — like we’re not just victims of this; we get to choose, like how we curate and be in our networks and our spaces. I love that, Nadia. Thank you so much for joining this episode — that’s Anti-memetics: Why Some Ideas Resist Spreading.\n\nNadia: Thanks for having me!","tokens":28625,"crawled_at":1791195231167}
+{"id":10496,"url":"https://docs.ethena.fi/technical-design/overview","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Overview | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nEthena's solution has both Onchain and Offchain composite components & services.\nThe Onchain components include the smart contracts that enable the minting, redeeming, staking, and unstaking of USDe.\nThe Offchain components include services that manage the delta hedging positions with respect to deposited backing assets.\n\nIn order to access the centralized liquidity, explicit trade-offs need to be made for onchain trust assumptions which are detailed in this section.\nEthena Labs Github\nethena-labsGitHub\nYou can read more in the following sections:\n\nMinting USDe\n\nStaking USDe\n\nBacking Asset Custody\n\nHedging System\n\nLast updated 1 year ago\nWas this helpful?","tokens":189,"crawled_at":1791195240512}
+{"id":10497,"url":"https://docs.sui.io/getting-started/tooling","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Developer Tools | Sui Documentation","text":"Browse the tools available for developing on Sui. Each tool includes a description, installation command, and link to its source.\n\ncaution\nTools tagged as Community are maintained by third-party developers. Mysten Labs, Sui Foundation, and Walrus Foundation do not guarantee their functionality, security, or compatibility with the latest platform updates.\n\nFundamentals​\nsuiup\nInstaller and version manager for the Sui toolchain. Installs and manages sui, mvr, move-analyzer, walrus, and other Sui binaries.\n\ncurl -sSfL https://raw.githubusercontent.com/MystenLabs/suiup/main/install.sh | sh\n\nSui CLI\nThe core Sui command-line interface. Includes sui move, sui client, sui replay, and other subcommands.\nsuiup is the recommended installer. Also available through brew install sui or install from source with Cargo.\n\nsuiup install sui@testnet or suiup install sui@mainnet\n\nPlay Move\nMove web IDE for quick experimentation without any downloads.\n\nSui Devstack\nBoot a local Sui stack with Walrus, Seal, DeepBook, and faucets from a single TypeScript config. Publishes packages, funds accounts, and generates typed bindings.\n\npnpm create @mysten-incubation/devstack-app@latest my-app\n\nWriting MoveMoveAn open source programming language used for all activity on Sui.​\nIDEs, editor extensions, and language tools for writing Move smart contracts.\nMove Analyzer\nMove Language Server providing code completion, go-to-definition, hover information, and diagnostics.\nVS Code extension: mysten.move\n\nsuiup install move-analyzer\n\nPrettier Move Plugin\nOfficial Move code formatter using a Prettier plugin backed by tree-sitter.\nVS Code extension: mysten.prettier-move\n\nnpm i -D prettier @mysten/prettier-plugin-move\n\nTree Sitter Move\nTree-sitter grammar for the Move language, enabling syntax highlighting and code analysis in supported editors.\n\nMove Registry CLI (MVR)\nOn-chain package manager for Sui with human-readable names, versioning, and dependency resolution.\nUsage: mvr add @deepbook/core, mvr resolve. Integrates with sui move build.\n\nsuiup install mvr\n\nMove Registry\nWeb portal for the Move Registry. Browse, search, and manage Move packages.\nProvides package analytics, name registration, and deployment management.\n\nCommunity\nIntelliJ Sui Move Language Plugin\nIntelliJ-based plugin for Move on Sui development.\n\nCommunity\nEmacs move-mode\nEmacs major-mode for editing smart contracts written in the Move programming language.\n\nCommunity\nMove.vim\nVim syntax highlighting that supports the Move 2024 edition.\n\nCommunity\nZed Move Extension\nMove language support for the Zed editor.\n\nCommunity\nBitsLab IDE\nOnline Move code editor that requires no configuration. Supports Move syntax highlighting and interacting with Sui.\n\nCommunity\nChainIDE\nCloud-powered Move development platform for Sui.\n\nCommunity\nSui Extension (zktx.io)\nVS Code extension for compiling, deploying, and testing Sui smart contracts directly within the editor.\n\nCommunity\nSui TUI\nTerminal UI tool for Sui.\n\ncargo install suitui\n\nBuilding apps​\nFrontend toolkits, wallet integration, authentication, and app scaffolding.\n@mysten/create-dapp\nCLI tool for creating Sui apps.\n\nSui dApp Kit\nReact components, hooks, and utilities for building apps on Sui.\n\nSuiLink\nSecurely link wallet addresses from different blockchains to a Sui wallet address. Receive a soulbound NFT as proof of ownership.\n\nSAGAT\nMultisig wallet management platform for proposing, signing, and managing multi-party transactions.\nIncludes API backend, React frontend, and TypeScript SDK.\n\nSelf-host (Bun + TypeScript + PostgreSQL)\n\n@mysten/signers\nThe Sui KMS Signers package provides a set of tools for securely signing transactions using Key Management Services (KMS) like AWS KMS and GCP KMS.\n\nnpm i @mysten/signers\n\nYubiSui\nCreate a Sui wallet inside a YubiKey and sign Sui transactions with it.\n\nCommunity\nSui dApp Starter\nFull-stack boilerplate for scaffolding Sui projects with React.\n\nTypeScriptCommunity\nhuman.tech Wallet Protocol (WaaP) SDK\nWhite label embedded wallets with social login, biometrics and gas sponsorship. One account works across apps, and also signs on Solana and EVM.\nNon-custodial. Keys are reconstructed in secure hardware, the user keeps ownership and can export at any time. Policies are enforced before a signature exists, and WaaP Squid Mode adds decentralized signing across the Ika network.\n\nnpm install @human.tech/waap-sdk\n\nCommunity\nSuiet Wallet Kit\nReact toolkit for apps to interact with all wallet types in Sui easily.\n\nCommunity\n@suiware/kit\nOpinionated React components and hooks for Sui apps.\n\nCommunity\nSui Suitcase (Polymedia)\nSui utilities for TypeScript, Node, and React.\n\nCommunity\nSui dApp Scaffold (Bucket Protocol)\nFrontend scaffold for a decentralized app on Sui.\n\nCommunity\nWormhole Kit (zktx.io)\nReact library that enables instant integration of Wormhole into your app.\n\nCommunity\ncreate-dubhe (Dubhe Engine)\nCreate a new Dubhe project on Sui.\n\nCommunity\nsui-dapp-kit-theme-creator\nBuild custom Sui dApp Kit themes.\n\nCommunity\nPTB Studio\nVisual Programmable Transaction Block builder.\n\nzkLoginzkLoginA Sui primitive that allows you to send transactions using an OAuth credential.​\nTools and demos for integrating zkLogin authentication into your app.\nCommunity\nuseSuiZkLogin\nReact hook and functions for seamless zkLogin integration on Sui.\n\nCommunity\nReact ZK Login Kit\nReady-to-use component with hook for sign-in and sign-transaction.\n\nCommunity\nzkLogin Demo (Polymedia)\nDemo implementation of zkLogin.\n\nCommunity\nzkLogin Demo (jovicheng)\nDemo implementation of Sui zkLogin.\n\nCommunity\nzkWallet Demo (ronanyeah)\nDemo implementation of a Sui zk wallet.\n\nTesting and debugging​\nTools for unit testing, replaying transactions, and debugging Move execution locally.\nsui replay\nLocally re-executes any past on-chain transaction and compares effects.\nUsage: sui replay --digest <TX_DIGEST>. Use --trace for debugger input.\n\nMove Trace Debugger\nStep-through debugger for Move execution traces with variable inspection and breakpoints.\nWorks on traces from sui move test --trace-execution and sui replay --trace.VS Code extension: mysten.move-trace-debug\n\nObject Display V2 Templates\nBuild and preview Display templates for on-chain objects.\n\nCommunity\nSuiBase\nCreate workdirs, each defining a distinct development environment targeting a network.\n\nCommunity\nSentio Debugger\nShows the trace of a transaction. Mainnet only.\n\nFaucets​\nObtain testing tokens for TestnetTestnetStaging network for testing changes before production deployment. deployment.\nSui Faucet\nRequest Testnet or Devnet SUI tokens for development and testing.\n\nCommunity\nN1 Stake Faucet\nCommunity-provided faucet for obtaining Testnet SUI tokens.\n\nCommunity\nSuiLearn Faucet\nCommunity-provided faucet for obtaining Testnet SUI tokens.\n\nSecurity and auditing​\nFormal verification, source verification, linting, and phishing protection.\nCommunity\nSui Prover\nProver for doing formal verification of Move on Sui code.\n\nCommunity\nPackage Source Code Verification\nVerify your package source code on Suiscan, powered by WELLDONE Studio and Blockberry.\n\nCommunity\nSuiSecBlockList\nBlock malicious websites and packages. Identify and hide phishing objects.\n\nCommunity\nGuardians\nPhishing website protection for Sui.\n\nCommunity\nHoneyPotDetectionOnSui\nDetect honeypot scams on Sui.\n\nCommunity\nSui RPC Proxy\nMonitor and analyze the network requests made by wallet applications and Sui apps.\n\nData and indexing​\nIndexers, data APIs, and analytics services for querying on-chain state.\nSui GraphQL RPC\nRich data query interface for Sui.\nMainnet: https://graphql.mainnet.sui.io/graphql, Testnet: https://graphql.testnet.sui.io/graphql, Devnet: https://graphql.devnet.sui.io/graphql\n\nCommunity\nZettaBlock\nGenerate custom GraphQL or REST APIs from SQL queries and incorporate private off-chain data.\n\nCommunity\nSentio Indexer\nTransform raw indexed data into meaningful queryable data by writing custom processor logic.\n\nCommunity\nBlockVision\nPre-built APIs for Sui indexed data including tokens, NFTs, and DeFi.\n\nCommunity\nBlockberry (Suiscan)\nAPI providing endpoints for significant entities on Sui, including NFTs, domains, collections, coins, and market data.\n\nCommunity\nSpace and Time (SxT)\nVerifiable compute layer for AI and blockchain. Decentralized data warehouse with sub-second ZK proof.\n\nCommunity\nBirdeye Data Services\nCrypto market data APIs on Sui.\n\nCommunity\nIndexer.xyz (TradePort)\nToolkit for accessing NFT data and integrating trading functionality on Sui.\n\nCommunity\nDubhe Indexer (Dubhe Engine)\nAutomatic indexing of all events based on Dubhe Engine configuration files.\n\nCommunity\nSurflux\nDeveloper infrastructure for Sui. Build production-ready apps with APIs, indexing, and real-time data streams.\n\nCommunity\nIndexer Generator\nCode generator that creates an indexer for all events in a given smart contract. Uses TypeScript and Prisma.\n\nCommunity\nOKLink\nExplorer and data APIs for Sui.\n\nExplorers​\nBlock explorers and network monitoring dashboards.\nCommunity\nSuiVision\nData analytics covering transactions, wallets, staking, and validators.\n\nCommunity\nSuiscan\nExplorer and analytics platform for Sui.\n\nCommunity\nPolymedia Explorer\nCommunity fork of the discontinued Sui Explorer from Mysten Labs. Available to build locally or use online.\n\nCommunity\nLocal Sui Explorer\nSui Explorer for your localnet.\n\nCommunity\nSuimon\nCommand-line tool providing detailed dashboards for monitoring the Sui network.\n\nCommunity\nRPC Tools (Polymedia)\nWeb app that helps users find the fastest RPC endpoint for their location.\n\nCommunity\ndevxplorer\nDeveloper-focused explorer built on GraphQL. Works with local and custom RPCs, focusing on transactions, effects, objects, events, packages, and types.\n\nCommunity\nSui Data Stack Explorer\nAI-native explorer with smart routing across gRPC, GraphQL, and Archival Service. Includes a Pulse checkpoint feed and an object Time Machine for historical inspection.\n\nOracles​\nPrice feeds and off-chain data delivery for on-chain contracts.\nCommunity\nPyth Network\nOracle protocol that connects the owners of market data to applications on multiple blockchains including Sui.\n\nCommunity\nSupra Oracles\nOracle protocol providing reliable data feeds through pull and push models.\n\nCommunity\nSwitchboard\nData feed customization and management for Sui.\n\nAI​\nAutonomous agents, verifiable inference, and TEE infrastructure.\nCommunity\nTalus\nBuild autonomous digital economy powered by Sui.\n\nCommunity\nAtoma\nDeveloper-focused infrastructure for private, verifiable, and customized AI experiences.\n\nCommunity\nEliza\nFramework for building autonomous agents.\n\nCommunity\nSui Pilot\nClaude Code plugin that bundles Sui ecosystem docs, a Move LSP bridge, and formal verification tooling into a doc-first development agent.\n\nCommunity\nLocal Sui MCP Server\nLocal MCP server exposing 29 agent-callable tools for querying Sui via gRPC, GraphQL, and Archival Service with automatic transport routing.\n\nTypeScriptCommunity\nWaaP CLI\nAgent payments from a headless wallet, with spend caps the AI agent cannot raise. Scoped, expiring grants let it transact autonomously on Sui, Solana and EVM.\nThe agent holds no key. Every request passes a policy gate server-side before a signature exists, so a prompt-injected agent has nothing to reach for. Grants are bound by recipient, chain, a cumulative spend ceiling and an expiry. Agentic pay-per-use without a browser or a human in the loop for each transaction.\n\nnpm install -g @human.tech/waap-cli\n\nSui stack tooling​\nTooling for other pieces of the Sui stack, including Walrus, Seal, and NautilusNautilusSecure and verifiable off-chain computation on Sui..\nWalrus CLI\nCLI for interacting with the Walrus platform for configuration, orchestration, and environment setup.\n\nsuiup install walrus\n\nWalrus site-builder\nCLI tool that lets you create, edit, and publish Walrus Sites.\n\nsuiup install site-builder\n\nSeal CLI\nCommand-line interface for Seal encryption and access control.\n\nCommunity\nNautilus Ops\nOperations tooling for Nautilus.\n\nCommunity\nNautilus TypeScript\nTypeScript utilities for Nautilus.\n\nMarlin Oyster and Nautilus\nTrusted execution environment (TEE) infrastructure for AI and blockchain workloads on Sui.\n\nSDKs​\nSDKs for building on Sui, grouped by language. Use the filter bar to search by language name.\nTypeScript​\nTypeScript\nSui TypeScript SDK\nModular library of tools for interacting with Sui, maintained by Mysten Labs.\n\nTypeScript\nEnoki TypeScript SDK\nTypeScript SDK for Enoki.\n\nTypeScript\nEnoki Connect SDK\nTypeScript SDK for Enoki Connect integration.\n\nTypeScript\nSeal SDK\nTypeScript SDK for Seal, providing encryption and access control on Sui.\n\nTypeScript\nzkSend SDK\nTypeScript SDK for sending assets through zkSend on Sui.\n\nTypeScript\nDeepBookV3 SDK\nTypeScript SDK for integrating with DeepBook V3.\n\nTypeScript\nSlush Wallet SDK\nTypeScript SDK for integrating Slush Wallet into your app.\n\nTypeScript\nKiosk SDK\nTypeScript SDK for building with Sui Kiosk, the decentralized commerce primitive.\n\nTypeScript\nWalrus SDK\nTypeScript SDK for integrating with Walrus decentralized storage.\n\nTypeScript\nPAS TypeScript SDK\nProgrammable Asset Standard TypeScript package.\n\nTypeScript\nSui Wallet Standard\nStandard TypeScript utilities for implementing wallets and libraries based on the Wallet Standard.\n\nTypeScript\nBCS TypeScript\nBinary Canonical Serialization library for TypeScript.\n\nTypeScript\nCodegen\nCode generation utilities for the Sui TypeScript SDK.\n\nTypeScript\nPayment Kit\nSDK for handling payments on Sui.\n\nTypeScriptCommunity\nSui Kit (Scallop)\nToolkit for interacting with the Sui network in TypeScript.\n\nTypeScriptCommunity\nSui Client Gen (Kuna Labs)\nGenerate TypeScript SDKs for Sui Move smart contracts. Works with source code and on-chain packages, no IDLs or ABIs required.\n\nTypeScriptCommunity\nTypeMove (Sentio)\nGenerate TypeScript bindings for Sui contracts.\n\nTypeScriptCommunity\nCoinMeta (Polymedia)\nLibrary for fetching coin metadata for Sui coins.\n\nTypeScriptCommunity\nDubhe Client\nMulti-platform client supporting browsers, Node.js, and game engines for interacting with Sui Move contracts.\n\nTypeScriptCommunity\nDubhe Client BCS Decoding\nAutomatic parsing of BCS types based on contract metadata with automatic conversion formatting.\n\nTypeScriptCommunity\ndApp Kit (Vue)\nSui dApp Kit for the Vue framework.\n\nRust​\nRust\nSui Rust SDK\nRust SDK for interacting with Sui. Supports gRPC and GraphQL.\n\nRust\nWalrus Rust SDK\nRust SDK for interacting with Walrus.\n\nRust\nLegacy Sui Rust SDK\nLegacy Rust crate providing the wallet and client configuration used by the Sui CLI. Use the current Sui Rust SDK for new integrations.\n\nRust\nRust External Signers\nRust-based external signer implementations for Sui.\n\nRustCommunity\nBCS Rust\nBCS serialization and deserialization in Rust.\n\nPython​\nPython\nPysui\nPython SDK for interacting with Sui.\n\nGo​\nGoCommunity\nSui Go SDK (SuiVision)\nGolang SDK to interact with Sui.\n\nGoCommunity\nSui Go SDK (Pattonkan)\nGolang SDK with PTB and devInspect support.\n\nKotlin​\nKotlinCommunity\nSui Kotlin SDK (Ksui)\nKotlin Multiplatform SDK for integrating with Sui.\n\nKotlinCommunity\nBCS Kotlin\nBCS serialization and deserialization in Kotlin.\n\nSwift​\nSwiftCommunity\nSuiKit\nSwift SDK natively designed for developing on Sui.\n\nSwiftCommunity\nBCS Swift\nBCS serialization and deserialization in Swift.\n\nDart​\nDartCommunity\nSui Dart SDK\nA cross-platform Dart SDK to interact with Sui.\n\nDartCommunity\nBCS Dart\nBCS serialization and deserialization in Dart.\n\nC# and Unity​\nC#Community\nSui Unity SDK (OpenDive)\nFully featured Unity SDK with offline transaction building.\n\nC#Community\nBCS Unity\nBCS serialization and deserialization in Unity C#.\n\nDeFi protocol SDKs​\nThese SDKs are built and maintained by their respective protocol teams for integrating with specific DeFi protocols on Sui.\nTypeScriptCommunity\nNAVI Protocol SDK\nTypeScript SDK for interacting with NAVI Protocol on Sui.\n\nTypeScriptCommunity\nBucket Protocol SDK\nTypeScript SDK for interacting with Bucket Protocol.\n\nTypeScriptCommunity\nSuilend SDK\nTypeScript SDK for interacting with the Suilend program.\n\nTypeScriptCommunity\nScallop SDK\nTypeScript SDK for interacting with the Scallop lending protocol on Sui.\n\nTypeScriptCommunity\nCetus CLMM SDK\nSDK for integration with Cetus-CLMM on Sui.\n\nTypeScriptCommunity\nAftermath SDK\nTypeScript SDK for interacting with Aftermath Protocol.\n\nTypeScriptCommunity\nFlowX SDK\nTypeScript SDK for interacting with FlowX protocols.\n\nTypeScriptCommunity\n7k Aggregator SDK\nTypeScript SDK for interacting with 7k Aggregator protocol.\nThe GitHub repository is archived. The npm package @7kprotocol/sdk-ts is still published.\n\nAPIs​\nSui gRPC API\ngRPC API definitions and protocol buffers for Sui.\n\nEnoki API\nREST API for zkLogin and sponsored transactions.\n\nMisc​\nOpenZeppelin Contracts for Sui\nAudited libraries including deterministic arithmetic, decimal scaling, and ownership-transfer wrappers.\n\nMinting Server\nA scalable system architecture that processes multiple Sui transactions in parallel using a producer-consumer worker scheme.\n\nDocker Sui Node Image\nOfficial Docker image for running a Sui node.\n\nCommunity\nSui Terraform Modules\nAll-in-one solution for deploying, monitoring, and managing Sui infrastructure.\n\nCommunity\nSui Tears (Interest Protocol)\nOpen source, production-ready Sui Move library for new and experienced developers.\n\nCommunity\nSui Codec\nEncoding solution for Sui.\n\nCommunity\nSkipList (Cetus)\nA skip list implementation in Move on Sui.\n\nCommunity\nIntegerMate (Cetus)\nMove module providing signed integer and integer math functions.\n\nCommunity\nCetus CLMM Contracts\nOpen source Cetus CLMM DEX contracts.\n\nCommunity\nSuiDouble Metadata\nMove library and tools to store, retrieve, and manage primitive data as chunks in a vector without dependencies.\n\nCommunity\nSuiGPT Decompiler\nUses generative AI to convert Move bytecode back to source code.\n\nCommunity\nRevela\nDecompile Sui smart contracts to recover Move source code.\n\nCommunity\nSui Token CLI\nRust-based CLI tool and RPC service for generating and verifying Sui token smart contracts.\n\nCommunity\nDubhe Engine (Obelisk Labs)\nOpen source toolchain for building intent-centric worlds with Move applications.\n\nCommunity\nDubhe CLI (Dubhe Engine)\nCLI for building and managing apps built on Dubhe Engine in Sui.\n\nSui Protocol Config\nTransaction limits and protocol configuration values for Sui.\n\nCommunity\nPolymedia Commando\nCommand-line tools for Sui airdrops, data gathering from RPCs and indexers, and more.\n\nsui-tool\nInternal diagnostic utility for Sui network operations.\n\nRelated topics\n\nInstall Sui\nInstall the Sui CLI using suiup, Homebrew, or Chocolatey, verify the installation, and learn about available toolchain components including walrus and mvr.\nSui CLI\nSui provides command line tools to interact with the network, its features, and the Move programming language. Individual command groups and utilities are referred to as Sui Client CLI, Sui Keytool CLI, Sui Move CLI, Sui Completion CLI, and Sui Validator CLI.\nMove Analyzer VS Code Extension\nThe Move extension provides language support features like code navigation, completion, and diagnostics for Move source code.\nSagat\nSagat is a multisig management platform designed for managing Sui multisig wallets.\n\nFundamentals\nWriting Move\nBuilding appszkLogin\n\nTesting and debuggingFaucets\n\nSecurity and auditing\nData and indexing\nExplorers\nOracles\nAI\nSui stack tooling\nSDKsTypeScript\nRust\nPython\nGo\nKotlin\nSwift\nDart\nC# and Unity\nDeFi protocol SDKs\n\nAPIs\nMisc\n\nWas this page helpful?","tokens":4888,"crawled_at":1791195250907}
+{"id":10498,"url":"https://docs.ethena.fi/backing-custody-and-security/overview","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Overview | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\n\n\"Backing Custody\" refers to where protocol backing assets are held.\n\nTo access centralized exchange liquidity, Ethena must provide backing assets to support the delta hedging derivative positions that act as the peg stability mechanism.\nEthena holds all backing assets with \"Off-Exchange Settlement\" solutions. These providers both custody deposited assets as well as enable Ethena to delegate/undelegate assets to/from centralized exchanges without ever transferring the assets to the exchanges.\n\"Off-Exchange Settlement\" providers enable Ethena to settle the outstanding PnL of Ethena's derivatives positions frequently. This enables Ethena to mitigate potential impact in the event of an exchange failure between settlement cycles.\nMost importantly, Ethena depositing backing assets assets with an \"Off-Exchange Settlement\" provider does not transfer beneficial title over the assets to the provider or exchange partners. In the event of an agreed exchange failure, Ethena should be able to delegate funds to another exchange to support hedging requirements.\n\"Off-Exchange Settlement\" providers such as Copper, Ceffu, and Fireblocks have long been used by institutional participants in the space to ameliorate this exact risk.\nTransparency\nEthena strongly believes in users' ability to independently verify the existence and control of the protocol backing as well as the hedging derivatives positions.\n\nAll \"Off-Exchange Settlement\" providers may enable the provision of onchain wallet addresses so users can validate the existence of the protocol backing assets; however, as some backing assets are held in omnibus accounts with other assets, this might not be feasible.\n\nPeriodic attestations (at least monthly) by custodial partners of backing asset value held within institutional custodial solutions will be published to provide transparency where addresses are not able to be provided.\n\nEthena is actively exploring tools to help publicly prove & enable users to independently verify the existence of hedging derivatives positions.\n\nApproach to Decentralization\nThere are a variety of trade-offs to consider when evaluating the degree to which the protocol relies on maximally decentralized solutions.\nThe core mission of creating a stablecoin equivalent that is not reliant on banking infrastructure has to date required either:\n\nCapital inefficient overcollateralized \"loans\" onchain.\n\nUnstable algorithmic designs.\n\nUnscalable delta-neutral designs that are fully reliant on decentralized exchanges.\n\nIn order to address the shortcomings of prior delta-neutral peg mechanism designs it is necessary to interact with centralized liquidity venues where open interest and trading volume on derivatives are >25x larger than onchain liquidity venues.\nHowever, doing so introduces new custodial risks with exchanges. How does Ethena address this?\nThe focus is generally on leveraging solutions for the most important qualities of decentralized exchanges, namely:\n\nHolding of assets outside opaque centralized servers.\n\nFully auditable and transparent.\n\nPermissionless and programmatic withdrawal.\n\nThe use of \"Off-Exchange Settlement\" providers largely addresses these qualities & enables Ethena to create a synthetic dollar that can meaningfully scale without being overly reliant upon a single source of liquidity, a single custodian of funds, etc.\n\nLast updated 1 year ago\nWas this helpful?","tokens":874,"crawled_at":1791195260860}
+{"id":10499,"url":"https://www.metaplex.com/docs/smart-contracts/core/external-plugins/overview","domain":"www.metaplex.com","chapter":"docs","title":"External Plugins | Metaplex Core","text":"External Plugins connect Core Assets to external programs for advanced functionality. Use Oracle plugins for custom validation logic and AppData plugins for storing arbitrary data that third-party apps can read and write.\nWhat You'll Learn\nUnderstand External Plugin architecture (Adapters + Plugins)\nConfigure lifecycle checks (create, transfer, update, burn)\nSet up data authorities for secure data storage\nChoose between Oracle and AppData plugins\n\nSummary\nExternal Plugins extend Core Assets with external program functionality. They consist of two parts: a Plugin Adapter attached to the Asset/Collection, and an External Plugin (Oracle account or AppData storage) that provides data and validations.\nAuthority Managed plugins (update authority controls)\nSupport lifecycle validation: approve, reject, or listen\nData Authority controls who can write plugin data\nWorks with Assets and Collections\nOut of Scope\nBuilt-in plugins (see Plugins Overview), creating Oracle programs (see Oracle guide), and Token Metadata extensions.\nQuick Start\nJump to: Oracle Plugin · AppData Plugin · Adding External Plugins\nChoose plugin type: Oracle (validation) or AppData (data storage)\nCreate/deploy the external account (Oracle) or configure data authority (AppData)\nAdd the plugin adapter to your Asset or Collection\nWhat are External Plugins?\nExternal Plugins are Authority Managed, consisting of 2 parts, the Adapter, and the Plugin. A Plugin Adapter is assigned to the Assets/Collection and allows data and validations to be passed from an External Plugin. The External Plugin provides data and validations for the Plugin Adapter.\nLifecycle Checks\nEach External Plugin comes with the ability to assign lifecycle checks to Lifecycle Events influencing the behavior of the lifecycle event that is trying to take place. The lifecycle checks available are:\nCreate\nTransfer\nUpdate\nBurn Each of the lifecycle events can be assigned with the following checks:\nCan Listen\nCan Reject\nCan Approve\nCan Listen\nA web3 type webhook that alerts the plugin that a lifecycle event has taken place. This is useful for tracking data or performing another task based on an event that's taken place.\nCan Reject\nThe plugin has the ability to reject a lifecycle events action.\nCan Approve\nThe plugin has the ability to approve a lifecycle event.\nData Authority\nAn External Plugin may have a data area in which projects can securely store data to that particular plugin. The Data Authority of an External Plugin is the only authority allowed to write to the External Plugin's data section. The Update Authority of the plugin does not have permission unless they are also the Data Authority.\nPlugins\nOracle Plugin\nThe Oracle Plugin is designed for simplicity in a web 2.0-3.0 workflow. The Oracle Plugin can access onchain Oracle accounts external from the MPL Core Asset that can reject the use of lifecycle events set by the authority. The external Oracle Account can also be updated at any time to change the authorization behavior of the lifecycle events, making for a dynamic experience. You can read more about the Oracle Plugin on the Oracle Plugin page.\nAppData Plugin\nThe AppData Plugin provides secure, partitioned data storage on Assets. Each AppData plugin has a Data Authority that exclusively controls writes to that data section. Useful for third-party apps storing user data, game state, or application-specific metadata. You can read more about the AppData Plugin on the AppData Plugin page.\nExternal Plugins vs Built-in Plugins\nFeatureExternal PluginsBuilt-in Plugins\nData storage\nExternal account or on-asset\nOn-asset only\n\nCustom validation\n✅ Full control\n❌ Predefined behavior\n\nDynamic updates\n✅ Update external account\n✅ Update plugin\n\nComplexity\nHigher (external program)\nLower (built-in)\n\nUse case\nCustom logic, third-party apps\nStandard NFT functionality\n\nFAQ\nWhen should I use External Plugins vs Built-in Plugins?\nUse External Plugins when you need custom validation logic (Oracle) or third-party data storage (AppData). Use built-in plugins for standard NFT functionality like freezing, royalties, or attributes.\nCan External Plugins reject transfers?\nYes. Oracle plugins can reject lifecycle events (create, transfer, update, burn) based on external account state. This enables time-based restrictions, price-based rules, or any custom logic.\nWho can write to AppData?\nOnly the Data Authority can write to an AppData plugin. This is separate from the plugin authority and provides secure, partitioned storage for third-party applications.\nCan I have multiple External Plugins on one Asset?\nYes. You can add multiple Oracle or AppData plugins to a single Asset, each with different configurations and authorities.\nAre External Plugins indexed by DAS?\nYes. AppData with JSON or MsgPack schemas is automatically indexed by DAS for easy querying.\nGlossary\nTermDefinition\nPlugin Adapter\nOn-chain component attached to Asset that connects to external plugin\n\nExternal Plugin\nExternal account (Oracle) or data storage (AppData) providing functionality\n\nLifecycle Check\nValidation that can approve, reject, or listen to events\n\nData Authority\nAddress with exclusive write permission to AppData\n\nOracle Account\nExternal account storing validation results\n\nRelated Pages\nOracle Plugin - Custom validation logic\nAppData Plugin - Third-party data storage\nAdding External Plugins - Code examples\nBuilt-in Plugins - Standard plugin functionality","tokens":1358,"crawled_at":1791195264083}
+{"id":10500,"url":"https://blog.trailofbits.com/2026/10/02/sequencehash-multihashing-for-the-rest-of-us","domain":"blog.trailofbits.com","chapter":"security_audits","title":"SequenceHash: multihashing for the rest of us - The Trail of Bits Blog","text":"Page content\n\nMultihashing is one of those cryptographic tasks that’s easy not to think about too much. This is unfortunate, because multihashing is a common stumbling point when cryptographers try to use hashes.\nAs part of our goal to “fix software, not bugs,” Trail of Bits is introducing SequenceHash and its sister function SequenceMAC, a pair of related hash constructions that bring secure multihashing to developers using hash functions other than Keccak. We hope SequenceHash and SequenceMAC will help cryptographers avoid attacks that take advantage of ambiguous input encodings. The specification is open source, and is now a part of the Community Cryptography Specification Project (C2SP).\nSequenceHash and SequenceMAC behave similarly to NIST’s TupleHash, but have the advantage of not being tied to a single hash function. They also don’t require developers to implement fiddly computations that aren’t byte-aligned. Instead, SequenceHash and SequenceMAC work out of the box with nearly any secure cryptographic hash function you care to use, including SHA256/384/512, BLAKE, and RIPEMD. SequenceMAC supports keys 32 bytes or longer (up to the ridiculous limit of 2128 −1 bytes).\n(It’s worth noting: SequenceHash and SequenceMAC rely on the security of the underlying hash for their own security. SequenceHash and SequenceMAC can’t magically make MD4 or SHA0 secure again. For the purposes of this document, it’s assumed that you have chosen a reasonable hash function like SHA256, not CRC32.)\nTo make SequenceHash and SequenceMAC easy to use, we’re releasing three initial implementations of SequenceHash and SequenceMAC: one each in Rust, Go, and Python. We’re also releasing a large set of test vectors that cover multiple hash functions and include intermediate values to help developers debug and verify their implementations.\nWait, “multihashing”?\nYeah, it’s a weird term, but the idea is pretty simple. “Multihashing” means “hashing a bunch of values together.” If you’ve ever read a cryptography paper, and there’s a step that says something like “compute the shared authenticator N=Hash(X, Y, Z, A, B),” that’s multihashing. You need to create a hash that incorporates the inputs X, Y, Z, A, and B. Unfortunately, the simple “solution” of concatenating the inputs and hashing the result can lead to serious security problems.\nFor example, consider what happens when you hash three inputs using “raw” SHA256:\nimport hashlib\n\nhasher = hashlib.new('sha256')\nhasher.update(b'Test 0')\nhasher.update(b'Test 1')\nhasher.update(b'Test 2')\nprint(hasher.hexdigest())\nhasher = hashlib.new('sha256')\nhasher.update(b'Test 0Test 1')\nhasher.update(b'Test 2')\nprint(hasher.hexdigest())\nhasher = hashlib.new('sha256')\nhasher.update(b'Test 0')\nhasher.update(b'')\nhasher.update(b'Test 1Test 2')\nprint(hasher.hexdigest())\nThis produces the following output:\n4fce0a9940a42b5c9d1bcbfc9a6ddd6de20d731d584a0acf5bda6de86483641c\n4fce0a9940a42b5c9d1bcbfc9a6ddd6de20d731d584a0acf5bda6de86483641c\n4fce0a9940a42b5c9d1bcbfc9a6ddd6de20d731d584a0acf5bda6de86483641c\nEven though inputs are fed in through separate calls, they’re not separated from the perspective of the hash function—under the hood, the inputs are just concatenated.\nAs with many things in cryptography, multihashing is harder than you think. That’s a big problem because multihashing is a critical component of one of the most important tools in zero-knowledge proofs: the Fiat-Shamir transform. When you get multihashing wrong, you introduce the risk of forgeries into your zero-knowledge proofs. Given that zero-knowledge proofs play a major role in cryptocurrency nowadays, that sort of mistake is sometimes measured in millions of dollars.\nBut Fiat-Shamir transforms aren’t the only place where you might want to use multihashing. It’s not uncommon to need to hash a collection of related objects, where both the objects and the collection are variable in size. Think of authenticating the files in an archive, grouping multiple cryptocurrency transactions into a single hash, or hashing something as “simple” as somebody’s name.\nMultihashing is also used when generating cryptographic commitments to values. In some protocols, one party must perform calculations using secret values, only to reveal them to other parties for later verification. Often, this is done by hashing the secret value along with a random “blinding” value and broadcasting the result to other parties as the commitment. If the boundary between the secret value and the blinding value isn’t clear, a “commitment” can sometimes be opened several different ways.\nUnfortunately, nobody seems to have landed on a consistent, standard solution to this problem. Instead, across the open-source ecosystem and in our private audits, we find developers solving the problem in wildly different ways. Some of these solutions are insecure, like using separator characters that can also appear in the inputs. Others encode their data in a way that makes their separators unambiguous, but the encoding is unnecessarily complex and introduces subtle timing risks. Think of stuff like Base64-encoding byte strings and separating the results with dollar signs. We often see situations where some hash inputs are length-encoded, but not all. It’s the wild west out there.\nThere are tools specific to Fiat-Shamir transforms, like Merlin and our own decree, but they don’t work so well for general multihashing.\nThe most widely known standard for multihashing is TupleHash, defined in NIST SP 800-185. To be clear, TupleHash is great. It solves the multihashing problem in a straightforward way (length-prefix encoding), and it handles inputs of effectively unlimited size (if you’re regularly hashing more than 22040 −1 bits of input, Trail of Bits wants to party with you and your disrespect for physics). As a bonus, it naturally operates as an XOF. If TupleHash is available for you, it’s a great tool.\nTupleHash has a downside, though: it’s only defined to work with Keccak, the function that underpins SHA3. If you replace Keccak with another hash function, several of the important security features (like length-extension resistance) can go away. If you don’t have a Keccak implementation handy, you’re out of luck. Given that SHA3 and Keccak adoption have been pretty lackluster over the last decade, that leaves a lot of cryptographers out in the cold. This is especially true in the government contracting sector, where CNSA 2.0 has mandated SHA384 and SHA512 for nearly everything.\nThis is a problem that cries out for a standardized solution. It calls for a complete specification. It begs for ready-to-use implementations available in multiple languages.\nEnter SequenceHash\nSequenceHash is a hash-agnostic multihashing construct, similar to the way HMAC is a hash-agnostic MAC construct. You can use SequenceHash with your favorite hash functions, including the entire SHA2 family, BLAKE, RIPEMD, and more.\nWhat does SequenceHash offer?\nSequenceHash offers four key features that prevent your hashed values from being mixed, extended, or replayed across contexts.\nUnambiguous input encoding\nGiven two inputs (𝐴, 𝐵), you are guaranteed that there is no other sequence of inputs (𝐼1,…,𝐼𝑡), for any length 𝑡, that will result in the same input to the underlying hash function.\nIn other words, the values you hash are guaranteed to be “semantically distinct.” There’s no chance of playing games with the beginnings and endings of inputs, and there’s no opportunity to mix up parts of 𝐴 with 𝐵 or vice versa.\nSequenceHash helps cryptographers follow the Horton principle: you are hashing what you mean, and meaning what you hash.\nLength-extension prevention\nSeveral popular hash functions, including SHA256 and SHA512, are vulnerable to length extension attacks. If Alice has a secret value 𝐴 and sends 𝐻(𝐴) to Bob, then Bob can craft a value 𝐵 such that he can compute 𝐻(𝐴||𝐵), even though he doesn’t know 𝐴.\nSequenceHash doesn’t have that issue. It uses a double-hash construction that prevents Bob from learning the information he needs to compute 𝐻(𝐴||𝐵).\nBuilt-in customization strings\nIf you’re developing cryptographic protocols, it’s often important to bind hashed values to a particular step in the protocol, or to a specific instance of the protocol, in order to prevent replay attacks or other problems related to reusing values.\nSequenceHash makes this easy with built-in customization strings. Assuming you’re using a good hash function, applying SequenceHash or SequenceMAC to the same inputs with different customization strings will lead to unrelated outputs, allowing you to easily and predictably bind your hashes to particular uses. If you don’t need a customization string, don’t worry. They’re completely optional.\nAs an added bonus, the customization strings are incorporated only into the outer layer of the double-hash construction. If you need to hash the same value with multiple customization strings, the inner hash can be reused!\nMAC mode\nOne final cool feature of SequenceHash is that it has a keyed mode, SequenceMAC. SequenceMAC is structurally similar to HMAC, and offers the same features as SequenceHash: unambiguous encoding, customization strings, and length-extension protection. It also incorporates metadata about the key and customization strings to prevent the key pseudocollision issues present in HMAC.\nHow does SequenceHash work?\nLike TupleHash, SequenceHash uses length encoding to unambiguously encode its inputs. However, SequenceHash uses a simplified encoding. Instead of writing the number of bits to be hashed as a variable-length integer, SequenceHash encodes the number of bytes into a fixed-length, 128-bit integer. SequenceHash uses a length-suffix encoding for inputs. Like the length-prefix encoding system used by TupleHash, length-suffix encoding is unambiguous; however, suffix encoding allows implementers to develop streaming APIs when they need to support hashing data with length that isn’t known ahead of time.\nWe chose a 128-bit length encoding for simplicity of implementation on 32- and 64-bit systems (padding with zeroes is easy), and because a 2128 −1 byte limit exceeds all practical considerations for the time being and the foreseeable future. Two of the most popular hash functions in use today, SHA256 and SHA512, limit their inputs to 261 and 2125 bytes, respectively, meaning that a 2128 −1-byte limit exceeds the specified limits of the most popular underlying hash functions, anyway. If you’re pushing the edges of SequenceHash, you’ve already blown past the limits of SHA256 and SHA512.\nWe use byte counts for simplicity. Nearly all hashing today is performed in software on strings of 8-, 16-, 32-, or 64-bit values. Systems using non-byte-length strings are very rare nowadays, and we believe it should be up to implementers of such systems to provide their own byte padding if they want to use SequenceHash.\nLike HMAC, SequenceHash uses a double-hash construction to prevent length extension attacks. This structure also allows us to support a keyed variant, SequenceMAC, which accepts keys up to 2128 −1 bytes in length.\nOne downside of the original HMAC construction is that it’s subject to what are known as “key pseudocollisions.” HMAC keys can be any length, but if they’re longer than a certain cutoff value (that depends on the hash), they get hashed before use. This means that every “long” key has a “short” representation that produces the exact same outputs. If you’re careful about specifying and enforcing key lengths in protocols, you can guard against this sort of problem, but if you’re not careful, somebody could present two versions of the “same” key in different contexts, allowing them to engage in shenanigans.\nAnother form of key pseudocollision is key extension. As far as HMAC is concerned, the 8-bit key 0xff is the same as the 16-bit key 0xff00 and the 128-bit key 0xff000000000000000000000000000000. Appending zeroes to a key doesn’t actually change it (unless it goes beyond the length cutoff, at least). This sort of pseudocollision is a bit more insidious, because it’s the sort of thing that can show up accidentally; it’s not hard to imagine unintentionally passing a 128-bit key instead of a 256-bit key, or incorrectly setting a length indicator somewhere.\nThe keyed variant of SequenceHash, SequenceMAC, incorporates key lengths into a header block that is part of the hash. As a result, HMAC-style long-key pseudocollisions are hard to find: if a key needs to be preprocessed by hashing, supplying the hash of the raw key is not the same as supplying the raw key. Trailing zeroes in a SequenceMAC key are semantically significant.\nSequenceHash and SequenceMAC support customization strings for domain separation, similar to TupleHash’s customization strings. Customization strings can be up to 2128 −1 bytes in length, and they’re only integrated into the outer hash function, allowing developers to derive multiple hashes from the same set of inputs without rehashing everything.\nHow do I use it?\nGlad you asked! We already have three implementations available: Rust, Go, and Python. We also have a specification available as part of the C2SP, with test vectors available in case you want to write your own implementation.\nThe main feature that distinguishes the SequenceHash API from other APIs is that all updates to SequenceHash and SequenceMAC objects are atomic. That is, each time you write a value to a hashing object, it will be added to the hash as an independent, length-encoded object.\nWe have worked to make sure that the SequenceHash and SequenceMAC APIs are similar, but not identical, to the standard APIs for each language. The Go cryptographic library’s hash.Hash interface incorporates the io.Writer interface, which guarantees that writing two values in sequence is the same as writing their concatenation. The Python hash library makes similar guarantees for the PEP 247 update function.\nLet’s see what happens when we hash our example values above using SequenceHash:\nimport sequencehash\n\nhasher = sequencehash.SequenceHash.new('sha256')\nhasher.add(b'Test 0')\nhasher.add(b'Test 1')\nhasher.add(b'Test 2')\nprint(hasher.result().hex())\nhasher = sequencehash.SequenceHash.new('sha256')\nhasher.add(b'Test 0Test 1Test 2')\nprint(hasher.result().hex())\nhasher = sequencehash.SequenceHash.new('sha256')\nhasher.add(b'Test 0')\nhasher.add(b'Test 1Test 2')\nprint(hasher.result().hex())\nWe get the following output:\n6eea7264b266d35bd5e483ef042189d2cebe51f9e8b764b90b0f9c82185de7ca\n1469d91e90c1d9c6189f576822e900f5cc8c3cdbd2ec51256df649d37c1688f7\n1800a2188e126c79dac8f7cf7e38a66e3f797654c15a5e49248a94d4e99bcaae\nThe three outputs are all unrelated. That’s because each of the inputs is length-encoded, meaning that feeding Test 0 and Test 1 into consecutive calls to SequenceHash is not the same as feeding Test 0Test 1 into a single call.\nWe can also try hashing identical inputs with different customization strings:\nimport sequencehash\n\nhasher = sequencehash.SequenceHash.new('sha256')\nhasher.add(b'Test 0')\nprint(hasher.result_with_customizer(b'CUST 0').hex())\n\nhasher = sequencehash.SequenceHash.new('sha256')\nhasher.add(b'Test 0')\nprint(hasher.result_with_customizer(b'CUST 1').hex())\n\nhasher = sequencehash.SequenceHash.new('sha256')\nhasher.add(b'Test 0')\nprint(hasher.result_with_customizer(b'CUST 2').hex())\nAgain, we have three unrelated outputs:\n3e54b5cd60ef78773dcf14c5f65ed593726a981f2c80045db7fac03015cc07ad\n3c5b12ea6952714fed499796a743b103de97575fc938aab7d154cc6c605984a9\n706af798b32b12c9f508c16c3411b594227f79936a3cc521e6e1f362b1ef3a38\nSounds cool. What about SequenceMAC?\nSequenceMAC works like SequenceHash, but with a 32-byte or longer key. As with SequenceHash, we can see that shifting the boundaries between our inputs leads to different results:\nimport sequencehash\n\nKEY = bytes.fromhex(\"c5d6670f20adad622292a404dc5496cd6692fee636b5935a18451c985b7277bc9cacbc26e5473f85cfc6a64e96d0b98e7b9b604eaebc8899971e1a97dc3caa3a\")\n\nhasher = sequencehash.SequenceMAC.new(KEY, digestmod='sha256')\nhasher.add(b'Test 0')\nhasher.add(b'Test 1')\nprint(hasher.result().hex())\n\nhasher = sequencehash.SequenceMAC.new(KEY, digestmod='sha256')\nhasher.add(b'Test 0Test 1')\nprint(hasher.result().hex())\n\nhasher = sequencehash.SequenceMAC.new(KEY, digestmod='sha256')\nhasher.add(b'Test 0')\nhasher.add(b'')\nhasher.add(b'Test 1')\nprint(hasher.result().hex())\nThis gives us the following output:\n9a24e4209dad98d2e1f1eecd62aa2908234f1eed2963395292fd9718129fe258\n4e4b71b8bb7b2c80e9f9ca89cb8bff43cd77cc5b530fc5f163069e5dda2876cb\n6faf7818842f5a208dc306afe83ed7bea5b3fadc2a617c2208e836709f925889\nChanging the key, or using result_with_customizer with different customization values, will also provide different outputs.\nSome notes on key size\nOne important point is that SequenceMAC has a minimum key size of 32 bytes (256 bits). Coupled with a good 256-bit hash function, this corresponds to about a 128-bit security level against forgery attacks. As with HMAC, key sizes should generally be at least as long as the output of the hash.\nAdditionally, while SequenceMAC supports keys up to 2128 −1 bytes in length, it’s important to remember that “longer key” is not the same as “higher security.” The underlying hash function and the key-preprocessing step (which hashes keys longer than the underlying hash function’s block size) impose a hard cap on the total security SequenceMAC can provide. Using keys longer than the length of the hash output is generally not a good idea.\nFor hash functions with outputs smaller than 256 bits (such as SHA224 or RIPEMD160), the security level should be equal to about half the hash length (112 bits for SHA224 and 80 bits for RIPEMD160), which does not match the security of the minimum key size. While SequenceMAC can be used with such hash functions, the SequenceMAC specification only prohibits short keys and strongly discourages the use of hash functions with short outputs.\nWhat about extensible output functions (XOFs)?\nExcellent question! We don’t have an answer yet!\nWe haven’t specified SequenceXOF, but it’s definitely something we’re thinking about. Right now, XOFs aren’t as widely used as hashes, so the APIs are a little less stable. We want to proceed carefully to ensure we cover all the relevant use cases.\nWhat if I want to write my own implementation?\nWe love to see high-quality implementations! There are many languages where someone might find SequenceHash and SequenceMAC useful, and there are certainly ways to customize the current APIs to better fit your needs!\nFirst, check out the specification. The document is kinda long, but the structure is straightforward. If you’ve implemented HMAC before, SequenceHash and SequenceMAC will feel like fancy versions of that.\nSecond, if your target language is similar to Rust, Go, or Python, consider porting over our initial implementations. We’ve tried to keep these implementations as clean as we can, so they’re easy to audit and other cryptographers can learn from them.\nFinally, whatever you do, don’t forget to check your implementation against the test vectors. The test vectors aren’t simple known-answer tests, either: they include intermediate values that can be used to help debug and validate your implementation.\nSome minor caveats\nSequenceHash provides for a specific set of needs: customization and domain separation, preventing length extension attacks where applicable, and—most importantly—ensuring that your inputs don’t get mixed together in a dangerous way. It’s a tool, not a panacea.\nYou still need to make sure you’re hashing the right inputs. Being able to decode a value doesn’t mean that two pieces of software will encode that value in the same way, and that can lead to compatibility issues among different servers, clients, and libraries. JSON and XML, for instance, don’t always guarantee field orderings. Even for strings, it’s important to make sure you’re using a consistent encoding method (“all the world is ASCII” isn’t true and never has been).\nIn the case of Fiat-Shamir transforms, you still have to be careful about including all your inputs. Schnorr proofs should always include the group descriptor (whether as individual values or named parameter sets), the generator element, etc. When the output is supposed to be interpreted as an integer modulo some other value, it’s also important to make sure that you select a hash with an output large enough to avoid modulo bias. Cryptography is subtle; there are always intricacies to consider.\nStill, as long as you’re careful to keep your inputs consistent and include all your values, SequenceHash and SequenceMAC make it easy to ensure nobody can pretend your inputs mean something other than what they’re supposed to mean.\nThe specification is live at C2SP, and our Rust, Go, and Python implementations are ready to use today, with test vectors available if you want to write your own. Try it out and let us know what you think!","tokens":5248,"crawled_at":1791195272360}
+{"id":10501,"url":"https://docs.sui.io/references/cli","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Sui CLI | Sui Documentation","text":"Sui provides a command line interface (CLI) tool to interact with the Sui network, its features, and the MoveMoveAn open source programming language used for all activity on Sui. programming language. The complete suite of tools is called the Sui CLI, with commands grouped together by feature. Each group of commands is commonly referred to by its top-level command or utility: Sui Client CLI, Sui Keytool CLI, Sui Move CLI, Sui Completion CLI, and Sui ValidatorValidatorResponsible for executing tasks like staking, gas price references, and tallying rules. CLI.\n\nCheck Sui CLI installation​\n\nBefore you can use the Sui CLI, you must install it. To check if the CLI exists on your system, open a terminal or console and type the following command:\n\n$ sui --version\n\nIf the terminal or console responds with a version number, you already have the Sui CLI installed.\n\nIf the command is not found, follow the instructions in Install Sui to get the Sui CLI on your system.\n\nUpdate CLI​\n\nThe recommended way to manage Sui CLI installations and versions is through suiup: https://github.com/MystenLabs/suiup.\n\ninfo\nThe tracing feature is important because it adds Move test coverage and debugger support in the Sui CLI. Unless you enable it, you cannot use these two features.\n\nSui CLI commands​\n\nThere are a number of top-level commands available. Use the help flag for the commands that are not documented yet. For example, sui validator --help.\n\nSui Client CLI: Use the sui client commands to interact with the Sui network.\n\nSui Client PTB CLI: Use the sui client ptb command to build and execute PTBsProgrammable transaction blocksDefine all user transactions on Sui..\n\nSui Completion CLI: Use the sui completion command to generate shell completion scripts.\n\nSui External Keys CLI: Use the sui external-keys commands to manage keys on external hardware signers (Ledger, YubiKey).\n\nSui Keytool CLI: Use the sui keytool commands to access cryptography utilities.\n\nSui Move CLI: Use the sui move commands to work with the Move programming language.\n\nSui Replay CLI: Use the sui replay command to replay a transactionTransactionA number of commands that execute on inputs to define the result of the transaction. and generate transaction traces for the Move Debugger and trace analysis tools.\n\nSui Validator CLI: Use the sui validator commands to access tools useful for Sui validators.\n\nRelated topics\n\nInstall Sui\nInstall the Sui CLI using suiup, Homebrew, or Chocolatey, verify the installation, and learn about available toolchain components including walrus and mvr.\nSui Client CLI\nThe Sui Client CLI provides command-level access to interact with the Sui network.\nSui Client PTB CLI\nThe Sui Client PTB CLI enables a user to construct a PTB and execute it from the command line or a file.\nSui CLI Completions\nGenerate shell completion scripts for the Sui CLI.\n\nUpdate CLI\nSui CLI commands\n\nWas this page helpful?","tokens":729,"crawled_at":1791195273346}
+{"id":10502,"url":"https://launch.solana.com/products/private-channels","domain":"launch.solana.com","chapter":"developer_specs","title":"Private Channels - Private execution infrastructure for Solana.","text":"Public liquidity. Private execution.\nThe private execution infrastructure for internet capital markets.\nDownload Brochure\n\nWhy Private Channels\nFull operational sovereignty and high performance.\n\nPrivacy\nNo public mempool, no front-running, no data leakage. You control who participates, what rules apply, and how data is accessed.\n\nAutonomy\nFull control over validation, ordering, and network governance. You can configure your own rules and policies.\n\nPerformance\nMeet availability and latency requirements with any network and hardware configuration.\n\nRisk\nOrganization-specific risk management, security standards, and compliance frameworks.\n\nHow it works\n\nMainnet\n$100B+ liquidity\n\nUser Wallet7xKp...4mNq\n\nAvailable Actions\n\nWithdraw\n\nDeposit\n\nApplication Layer\nPrivate\nTransactions by default are configured to be completely private.\n\nInstant\nUp to thousands of transactions per second. 100ms settlement batches.\n\nYour Rules\nSet access controls, rate limits, compliance requirements.\n\nZero Fees\nNo set per-transaction costs inside the channel.\n\nStart building\n\nGithub\nBrochure","tokens":271,"crawled_at":1791195278884}
+{"id":10503,"url":"https://docs.ethena.fi/technical-design/key-trust-assumptions","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Key Trust Assumptions | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nWhile the Ethena protocol attempts to minimize trust assumptions across all areas of the infrastructure, certain trust assumptions need to exist in order to access centralized liquidity and enable the scaling of the underlying product.\nAs the protocol develops further, there are specific plans to gradually reduce trust assumptions on certain entities.\nSummary of Major Trust Assumptions\n\nThe user initially needs to trust that the hedging system will execute the appropriate hedge for the backing assets provided upon issuance of USDe. However, this can easily be verified by the issuance of USDe vs assets transferred, alongside the existence of read APIs to both custody wallets and the exchange APIs that are transparently displayed on the Ethena dashboards.\n\nThe USDe holder makes a trust assumption that the various OES providers will undertake their roles diligently and without major errors with regard to custody of the underlying backing. To date, none of the custodial providers which hold the assets have ever lost users' funds compared to $7bn of hacks on DeFi smart contracts.\n\nThe GATEKEEPER_ROLE is responsible for pausing the mint and redeem function, as well as adding new whitelisted custodial addresses that backing assets assets on mint are transferred to. This role is time-locked to ensure an extensive time period exists before such a sensitive change is able to be made.\n\nThe DEFAULT_ADMIN_ROLE, granted exclusively to the protocol multisig, will act seldomly and only in the best interest of the protocol. This multi-sig wallet requires 7 signatures to sign or transact, both from internal and external stakeholders, with keys geographically distributed and controlled by distinct individuals both within and outside of the Ethena Labs team.\n\nThe GATEKEEPER_ROLE and Multi-Sig Safety Layer\n\nThe GATEKEEPER_ROLE is used in the system in order to accelerate response times in the case of an issue. Gatekeepers can only disable minting and redeeming or remove the corresponding minting and redeeming roles from individual addresses. Gatekeepers cannot re-enable minting and redeeming nor take any other action. This role is distributed both within the Ethena Labs organization and among external stakeholders including market makers and exchanges.\n\nThe time-locked multi-sig ensures that privileged roles cannot be abused by the Ethena Labs team with keys distributed outside of the core contributor team and 7 day time-locks for any change to core functions.\n\nMint & Redeem Privileged Roles\nEthenaMinting.sol\nDEFAULT_ADMIN_ROLE\n\nCan set the maxMintPerBlock.\n\nCan set the maxRedeemPerBlock.\n\nCan add and remove supported assets.\n\nCan add and remove custodian wallets.\n\nCan add and remove addresses from other roles and perform all actions restricted by other roles.\n\nMINTER_ROLE\n\nCan mint USDe from assets, within 5% of 3rd party oracle pricing provided by Pyth and Redstone.\n\nCan transfer any asset in the minting contract to any custodian wallets.\n\nREDEEMER_ROLE\n\nCan redeem USDe for assets, within 5% of 3rd party oracle pricing.\n\nGATEKEEPER_ROLE\n\nCan disable minting and redeeming.\n\nCan remove the MINTER_ROLE or REDEEMER_ROLE from an address.\n\nUSDe.sol\nOwner\n\ncan set minter\n\nminter\n\na single address, the only address that can mint USDe. It cannot be set to the same address as owner. Set to EthenaMinting and only modifiable in case a new minting contract needs to be deployed to preserve protocol.\n\nStaking Contract Privileged Roles\nowner/DEFAULT_ADMIN_ROLE\n\nCan add and remove addresses from other roles. This should be the role of the Gatekeeper according to documentation.\n\nCan redistribute sUSDe from wallets with the FULL_RESTRICTED_STAKER_ROLE to any unrestricted address.\n\nREWARDER_ROLE\n\nCan add protocol-generated yield vested USDe to the contract via transferInRewards().\n\nLast updated 1 year ago\nWas this helpful?","tokens":987,"crawled_at":1791195281236}
+{"id":10504,"url":"https://www.metaplex.com/docs/smart-contracts/core/external-plugins/app-data","domain":"www.metaplex.com","chapter":"docs","title":"AppData Plugin | Metaplex Core","text":"The AppData Plugin provides secure, partitioned data storage on Core Assets. Third-party applications can store and read arbitrary data (JSON, MsgPack, or binary) with exclusive write access controlled by a Data Authority.\nWhat You'll Learn\nAdd AppData to Assets and Collections\nConfigure Data Authorities for secure writes\nChoose data schemas (JSON, MsgPack, Binary)\nRead and write data from on-chain and off-chain\n\nSummary\nThe AppData plugin stores arbitrary data on Assets with controlled write access. Only the Data Authority can write to the plugin's data section, enabling secure third-party integrations.\nStore JSON, MsgPack, or Binary data\nData Authority has exclusive write permission\nAutomatically indexed by DAS (JSON/MsgPack)\nLinkedAppData variant for collection-wide writes\nOut of Scope\nOracle validation (see Oracle Plugin), on-chain attributes (see Attributes Plugin), and off-chain metadata storage.\nQuick Start\nJump to: Add to Asset · Write Data · Read Data\nAdd AppData plugin with a Data Authority address\nChoose schema: JSON, MsgPack, or Binary\nWrite data using writeData() (must sign as Data Authority)\nRead data via DAS or direct account fetch\nWhat is an AppData Plugin?\nThe AppData external plugin stores and contains arbitrary data that can be written to by the dataAuthority. Note this is different then the overall plugin authority stored in the ExternalRegistryRecord as it cannot update/revoke authority or change other metadata for the plugin. Think of AppData as like a partition data area of an Asset that only a certain authority can change and write to. This is useful for 3rd party sites/apps to store data needed to execute certain functionality within their product/app.\nWorks With\n\nMPL Core Asset\n✅\n\nMPL Core Collection*\n✅\n\n* MPL Core Collections can also work with the LinkedAppData Plugin.\n\nWhat is a LinkedAppData Plugin?\nThe LinkedAppData plugin is built for Collections. It allows you to add a single plugin adapter on the collection which will allow you to write to any Asset in the collection.\nArguments\nArgValue\ndataAuthority\nPluginAuthority\n\nschema\nExternalPluginAdapterSchema\n\ndataAuthority\nAttributeList\n\nconst dataAuthority = {\n\ntype: 'Address',\n\naddress: publicKey('11111111111111111111111111111111'),\n\n}\n\nschema\nThe schema determines the type of data that is being stored within the AppData plugin. All schemas will be indexed by DAS.\nArgDAS SupportedStored as\nBinary (Raw Data)\n✅\nbase64\n\nJson\n✅\njson\n\nMsgPack\n✅\njson\n\nWhen indexing the data if there was an error reading the JSON or MsgPack schema then it will be saved as binary.\n\nWriting data to the `AppData` plugin\n\nimport { ExternalPluginAdapterSchema } from '@metaplex-foundation/mpl-core'\n\n// Chose from Binary, Json or MsgPack\n\nconst schema = ExternalPluginAdapterSchema.Json\n\nAdding the AppData Plugin to an Asset\nAdding a Attribute Plugin to an MPL Core Asset\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { addPlugin, ExternalPluginAdapterSchema } from '@metaplex-foundation/mpl-core'\n\nconst assetSigner = generateSigner(umi);\n\nconst dataAuthority = publicKey('11111111111111111111111111111111')\n\nawait create(umi, {\n\nasset: asset.publicKey,\n\nname: \"My Asset\",\n\nuri: \"https://example.com/my-assets.json\"\n\nplugins: [\n\n{\n\ntype: 'AppData',\n\ndataAuthority,\n\nschema: ExternalPluginAdapterSchema.Json,\n\n},\n\n],\n\n}).sendAndConfirm(umi)\n\n// Alternatively you could add the plugin to an existing Asset\n\nawait addPlugin(umi, {\n\nasset,\n\nplugin: {\n\ntype: 'AppData',\n\ndataAuthority,\n\nschema: ExternalPluginAdapterSchema.Json,\n\n},\n\n})\n\nWriting Data to the AppData Plugin\nOnly the dataAuthority address can write data to the AppData plugin. To write data to the AppData plugin we will use a writeData() helper which takes the following args.\nArgValue\nkey\n{ type: string, dataAuthority: publicKey}\n\nauthority\nsigner\n\ndata\ndata in the format you wish to store\n\nasset\npublicKey\n\nSerializing JSON\nSerializing JSON\n\nconst json = {\n\ntimeStamp: Date.now(),\n\nmessage: 'Hello, World!',\n\n}\n\nconst data = new TextEncoder().encode(JSON.stringify(json))\n\nSerializing MsgPack\nSerializing MsgPack\n\n// This implementation uses `msgpack-lite` for serialization\n\nconst json = {\n\ntimeStamp: Date.now(),\n\nmessage: 'Hello, World!',\n\n}\n\nconst data = msgpack.encode(json)\n\nSerializing Binary\nAs binary can store arbitrary data it's up to you to decide on how you are going to serialize and deserialize the data.\nSerializing Binary\n\n// The below example is just creating bytes that are considered `true` or `false`.\n\nconst data = new Uint8Array([1, 0, 0, 1, 0])\n\nWriting Data\nAdding a Attribute Plugin to an MPL Core Asset\n\nawait writeData(umi, {\n\nkey: {\n\ntype: 'AppData',\n\ndataAuthority,\n\n},\n\nauthority: dataAuthoritySigner,\n\ndata: data,\n\nasset: asset.publicKey,\n\n}).sendAndConfirm(umi)\n\nReading Data from the AppData Plugin\nData can be both read on chain programs and external sources pulling account data.\nFetch the Raw Data\nThe first step to deserializing the data stored in an AppData plugin is to fetch the raw data and check the schema field which dictates the format in which the data is stored before serialization.\nFetching `AppData` Raw Data\n\nconst assetId = publicKey('11111111111111111111111111111111')\n\nconst dataAuthority = publicKey('33333333333333333333333333333333')\n\nconst asset = await fetchAsset(umi, assetId)\n\nlet appDataPlugin = asset.appDatas?.filter(\n\n(appData) => (appData.authority.address = dataAuthority)\n\n)\n\nlet data\n\nlet schema\n\n// Check if `AppData` plugin with the given authority exists\n\nif (appDataPlugin && appDataPlugin.length > 0) {\n\n// Save plugin data to `data`\n\ndata = appDataPlugin[0].data\n\n// Save plugin schema to `schema`\n\nschema = appDataPlugin[0].schema\n\n}\n\nDeserialization\nNow that you have the data you'll need to deserialize the data depending on the schema you chose to write the data with to the AppData plugins.\nDeserialize JSON Schema\nDeserializing JSON\n\n// Due to the JS SDK, the deserialization for the MsgPack schema is automatic and deserialized\n\n// data can be accessed at the RAW location example above.\n\nDeserialize MsgPack Schema\nDeserializing MsgPack\n\n// Due to the JS SDK, the deserialization for the MsgPack schema is automatic and deserialized\n\n// data can be accessed at the RAW location example above.\n\nDeserialize Binary Schema\nBecause the Binary schema is arbitrary data then deserialization will be dependent on the serialization you used.\nDeserializing Binary\n\n// As the binary data is arbitrary you will need to include your own deserializer to\n\n// parse the data into a usable format your app/website will understand.\n\nCommon Errors\nAuthority mismatch\nOnly the Data Authority can write data. Verify you're signing with the correct keypair.\nData too large\nThe data exceeds account size limits. Consider compressing or splitting data across multiple plugins.\nInvalid schema\nThe data doesn't match the declared schema. Ensure JSON is valid or MsgPack is properly encoded.\nNotes\nData Authority is separate from plugin authority\nChoose JSON or MsgPack for DAS indexing\nBinary schema for custom serialization formats\nLinkedAppData allows writing to any Asset in a Collection\nQuick Reference\nSchema Comparison\nSchemaDAS IndexedBest For\nJSON\n✅ As JSON\nHuman-readable, web apps\n\nMsgPack\n✅ As JSON\nCompact, typed data\n\nBinary\n✅ As base64\nCustom formats, max efficiency\n\nAppData vs Attributes Plugin\nFeatureAppDataAttributes\nWrite permission\nData Authority only\nUpdate Authority\n\nData format\nAny (JSON, MsgPack, Binary)\nKey-value strings\n\nThird-party friendly\n✅ Yes\n❌ Requires update authority\n\nDAS indexing\n✅ Yes\n✅ Yes\n\nFAQ\nWhat's the difference between AppData and the Attributes plugin?\nAttributes stores key-value strings controlled by the update authority. AppData stores arbitrary data controlled by a separate Data Authority, making it ideal for third-party applications.\nCan I have multiple AppData plugins on one Asset?\nYes. Each AppData plugin can have a different Data Authority, allowing multiple third-party apps to store data on the same Asset.\nHow do I update existing AppData?\nCall writeData() with the new data. This replaces the existing data entirely—there's no partial update.\nIs AppData indexed by DAS?\nYes. JSON and MsgPack schemas are automatically deserialized and indexed. Binary is stored as base64.\nWhat is LinkedAppData?\nLinkedAppData is added to a Collection and allows the Data Authority to write to any Asset in that Collection without adding AppData to each Asset individually.\nGlossary\nTermDefinition\nAppData\nExternal plugin for storing arbitrary data on Assets\n\nData Authority\nAddress with exclusive write permission\n\nLinkedAppData\nCollection-level variant for writing to any Asset\n\nSchema\nData format: JSON, MsgPack, or Binary\n\nwriteData()\nFunction to write data to AppData plugin\n\nRelated Pages\nExternal Plugins Overview - Understanding external plugins\nOracle Plugin - Validation instead of data storage\nAttributes Plugin - Built-in key-value storage\nOn-chain Ticketing Guide - AppData example","tokens":2245,"crawled_at":1791195301974}
+{"id":10505,"url":"https://solana.com/docs/tools/private-channels","domain":"solana.com","chapter":"developer_specs","title":"Private Channels | Solana","text":"Solana Documentation\nPrivate Channels\n\nPrivate Channels has not been security audited and is not recommended for\nproduction use with real funds without a thorough security review.\n\nPrivate Channels is an enterprise layer for internet capital markets on\nSolana. It provides a configurable app-layer for private, instant, zero-fee\ntransfers inside payment channels: users deposit SPL tokens into an on-chain\nescrow program, transact off-chain through a gateway, and settle back to Mainnet\nvia a Sparse Merkle Tree proof, giving app developers instant, zero-fee, private\ntransfers without leaving the Solana ecosystem.\n\nResources\n\nProduct page\n\nGitHub\n\nBrochure\n\nWhy Private Channels?\n\nInstant transfers: off-chain throughput beyond Solana's native TPS;\ntransfers confirm when the sequencer processes them, not when a block confirms\n\nZero per-transfer fees: no gas cost on individual channel transfers; users\npay only for on-chain deposits and withdrawals\n\nPrivacy: transfers between channel participants are not recorded on Solana\nMainnet\n\nPermissioned access: RBAC with JWT authentication lets you control who can\nsend and receive\n\nMainnet settlement: funds are always redeemable to Solana via a Sparse\nMerkle Tree exclusion proof, which the escrow program enforces on-chain\n\nSee the Overview for the full\narchitecture, data flow diagram, and security model.\n\nQuick Start\n\nimport { getDepositInstructionAsync } from \"../private-channel-escrow-program/clients/typescript/src/generated\";\n\nconst depositIx = await getDepositInstructionAsync({\n\npayer: payerSigner,\n\nuser: userSigner,\n\ninstance: instancePda,\n\nmint: mintAddress,\n\nuserAta: userAtaAddress,\n\namount: 1_000_000n, // 1 USDC\n\nrecipient: null\n\n});\n\n// send via your preferred Solana client\n\nTypeScript clients are generated from the IDL; see Installation. For Token-2022\nmints, pass tokenProgram: TOKEN_2022_PROGRAM_ADDRESS explicitly, since it\ndefaults to the standard SPL Token Program.\n\nFull Quickstart -\nenvironment setup and client generation\n\nOverview - architecture and data\nflow\n\nUse Cases\n\nInstitutional bilateral payments - banks and institutions that need\nhigh-volume, private USDC flows without every transfer appearing on-chain\n\nHigh-frequency app-layer transfers - gaming, loyalty, and consumer apps\nthat need sub-second, zero-fee transfers at scale beyond native Solana TPS\n\nPrivacy-preserving token flows - any use case where counterparty and\namount privacy is a product requirement\n\nWhen to use native SPL transfers instead\n\nNext Steps\n\nInstallation\nSet up your environment and generate TypeScript clients.\n\nDeposit\nMake your first deposit into the escrow.\n\nOverview\nUnderstand the architecture and data flow.\n\nInstructions\nFull instruction reference for all programs.\n\nCommunity & Support\n\nQuestions? Ask on Solana Stack Exchange\n(use the solana tag)\n\nIssues? Report on\nGitHub Issues\n\nBuilt and maintained by the Solana Foundation. Licensed\nunder the MIT License.\n\nIs this page helpful?\n\nNext\n\nOverview\n\nTable of Contents\n\nResourcesWhy Private Channels?Quick StartUse CasesNext StepsCommunity & Support\n\nEdit Page","tokens":772,"crawled_at":1791195301146}
+{"id":10506,"url":"https://gov.uniswap.org/t/arana-digital-delegate-platform/23971","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Arana Digital Delegate Platform - Delegation Pitch - Uniswap Governance","text":"Arana Digital Delegate Platform\n\nDelegation Pitch\n\nAranaDigital\n\nMay 20, 2024, 6:30pm\n\n1\n\nArana Digital Delegate Platform\n\nDelegate address: 0x0579A616689f7ed748dC07692A3F150D44b0CA09\n\nDelegate ENS Address: aranadigital.eth\n\nForum Username: @AranaDigital & @AbdullahUmar\n\nTwitter: @aranaventures\n\nVoting Activity: Boardroom\n\nHistorical Discussion Activity: https://gov.uniswap.org/u/abdullahumar/activity\n\nEmail: arana.governance@gmail.com\n\nAbout\n\nWe are a team experienced in DAO governance, operations, growth and research. Our members are deeply steeped in the crypto space and have multiple years of participation in protocol governance.\n\nWith delegation history for DEXs, money markets, L2s, liquid staking protocols, and stablecoins, our team is acclimated with a breadth of sectors. We also bring a diversity of work experience to DAOs–our members have consulted for companies like Immutable and dYdX, worked at crypto investment and trading firms, set up various validator nodes, and run educational events for universities.\n\nCore Values\n\nDiligence: We thoroughly investigate each proposal, engaging with other delegates and service providers to gather diverse perspectives and insights prior to making a decision.\n\nTransparency: We openly share information about decisions and their rationales, providing clear and accessible updates, and ensuring that all processes are effective to the community.\n\nInnovation + Sustainability: We champion initiatives that will both allow the DAO and its underlying protocol to sustain its advantages, all the while continuously looking to iron out flaws and introduce efficiencies.\n\nPast Contributions to Uniswap:\n\nOur members have been active participants in the Uniswap DAO for the past 4 years. History with the DAO allows us to make informed voting decisions. During our tenure, we’ve maintained an excellent voting record, passed numerous proposals, and collaborated with multiple other delegates, the Foundation, and adjacent teams associated with Uniswap.\n\nA core aspect of our contribution has been around facilitating Uniswap growth and expansion:\n\nLaunched v3 on Avalanche\n\nLaunched v3 on Moonbeam\n\nLaunched v3 on Filecoin Virtual Machine\n\nLaunched v3 on Base\n\nLaunched v3 on Scroll\n\nLaunched v3 on Rootstock\n\nLaunched v3 on Sei\n\nOur members have also been strong advocates of robust governance practices and financial decision making:\n\nLowered Proposal Threshold\n\nMobilizing the Uniswap Treasury\n\nUpdating Uni v3/v2 Deployment Process\n\nUniswap Accountability Committee (UAC): Season 2 Report and S3 Renewal\n\nUniswap Growth Program\n\nUniswap Treasury Report\n\nDelegate Rewards Cycle 2, Cycle 3\n\nEstablish Uniswap v4 Licensing Process\n\nUniswap Accountability Committee (UAC): Season 3 Report and S4 Renewal\n\n@AbdullahUmar is serving on/has served on multiple working groups:\n\nUniswap Arbitrum Delegate Program\n\nUniswap Accountability Committee\n\nUniswap Delegate Reward WG\n\nUniswap Treasury Working Group\n\nWe have also been active forum participants for various topics, including delegate comp, fee switch, fee architecture, and post BSL expiration gov process\n\nHere’s some content creation regarding important governance topics to educate the broader community\n\nPolitics of Crypto Governance\n\nThe Post License Expiration Future of Uniswap\n\nAvalanche v3 Deployment\n\nNomad Hack’s Impact on Uniswap Deployments\n\nArana hopes to continue delivering on its members’ previous commitments to the Uniswap DAO going forward, abiding by transparent communication & thoughtful decision making, all with the intention of bettering Uniswap as a whole.\n\nConflict of Interest:\n\nWe are actively involved as delegates and contributors in multiple other DAOs. Arana also has an investment arm focused on allocating to small caps digital assets. Any relevant conflicts of interest will be publicized when needed.\n\n4 Likes\n\nUniswap Delegate Reward Application Thread\n\nGLI -- Treasury Delegation Round 2 Applications\n\nUniswap Delegate Reward Initiative - Cycle 3 Application and Results\n\nUniswap Delegate Reward Initiative - Cycle 4 Application and Results\n\nUniswap Delegate Reward Initiative - Cycle 2 Application\n\nAranaDigital\n\nJuly 3, 2024, 6:42am\n\n2\n\nApril Voting Update\n\n[Temp Check] Onboard Uniswap to Sei\n\nVote: Incentivize $500k\n\nType: Snapshot\n\nOur team decided to bring this proposal to the DAO for the following reasons:\n\nThe $500k amount was chosen since it was the healthy middle option–enough to compete amongst the number of DEXs launching on the new EVM. Plus, this amount nearly matched Sei Foundation’s $400k POL commitment for the first running quarter.\n\nUpdate Uni v3/v2 Deployment Process (March 2024)\n\nVote: Update Process\n\nType: Snapshot\n\nWe authored this proposal in order to help increase the efficiency of deployments. One can argue that a general precedent has been set for these deployments and editing the text record isn’t like a security concern or the like. It’s for text keeping and organization. And the uniswap timelock via a gov vote can always revoke the committee’s oversight over the subdomain, which makes this proposal effective at delivering operational efficiency.\n\n[Temp Check] Uniswap Onboarding Package - Manta\n\nVote: For\n\nType: Snapshot\n\nThis proposal was put forth AFTER the integration with Oku was complete, along with the deployment of all of the relevant v3 contracts. It is therefore a no brainer to vote For this proposal. The lackluster DEX environment on Manta also primes Uniswap to overtake its market share via the $250k worth of incentives.\n\nOnboarding Package Bundle\n\nVote: For\n\nType: Onchain\n\nThis proposal continues to incentivize LPs on new EVM deployments for Uni v3. In order to attain market share and prioritize protocol growth, we voted For this proposal, especially since Sei and Moonbeam also contributed POL on their ends, partly matching our incentive allocations.\n\nUpdate Uni v3/v2 Deployment Process (March 2024)\n\nVote: For\n\nType: Onchain\n\nPlease see the above reasoning from the snapshot related to this proposal.\n\nUniswap Treasury Working Group (UTWG) Election\n\nVote: 25% for Steakhouse, GFX, Karpatkey, and Avantgarde\n\nType: Snapshot\n\nSteakhouse, KPT, and Avantgarde have extensive experience with other DAOs’ treasury management programs–and GFX has been involved in treasury-based programs in DAOs like Arbiturm and Maker. All these teams have strong background in this subject matter and therefore get an even distribution of our votes.\n\nDeFi Education Fund Temp Check\n\nVote: For\n\nType: Snapshot\n\nThe legal terrain is a tough one to navigate, and it’s seldom top of mind for builders in the space until the community faces some sort of calamity. It’s therefore vital to fund groups that have the connections and competency to effectively court the ears of politicians and regulatory bodies. There has been some confusion around why this magnitude of funding is required–but that’s simply because we fail to understand the overhead costs associated with activities like litigation. We find the ask to be fair and in alignment with the previous donation that the DAO gave out a few years ago. Although, we would like to see more updates, something that the DEF has promised this time.\n\nDeFi Education Fund Temp Check- Options\n\nVote: Fund 1 million UNI (Original)\n\nType: Snapshot\n\nAs stated in the previous post, the 1M ask seems to be reasonable, and the proposed vesting setup makes the accountability aspect even stronger. Voting for a different option would also mean contradicting our previous vote.\n\nMobilizing the Uniswap Treasury\n\nVote: For\n\nType: Onchain\n\nOur team co-authored this proposal and therefore voted for it:\n\n“The Uniswap DAO’s treasury, containing assets worth nearly ~$6B, predominantly in $UNI tokens, faces challenges due to its single-asset composition and the lack of a plan for productive utilization.\n\nTo address the treasury’s volatility and underutilization, we propose forming the Uniswap Treasury Working Group (UTWG) to explore treasury management strategies aimed at achieving sustainability and growth for the DAO. The UTWG will examine various treasury plans for Uniswap DAO based on 8 weeks of research and interviews with various entities and individuals familiar with treasury management and adjacent subject matters.”\n\nMay Voting Update\n\n[Temp Check] Uniswap Delegate Reward -3 Months-Cycle 1\n\nVote: For\n\nType: Snapshot\n\nThe above comments from earlier summarize our opinions. We believe that this pilot program is a step in the right direction for the DAO’s incentive alignment with delegates.\n\n[Temp Check] Onboard Uniswap to Redstone\n\nVote: Deploy without incentives\n\nType: Snapshot\n\nWe helped the Redstone team bring this proposal to the DAO. All the contracts were deployed and a front-end was set up posting the RFC. Therefore, it’s a no brainer to consider this deployment canonical. But the chain does not have enough traction nor liquidity to justify incentives yet. Plus, no matching was proposed by Redstone to warrant reciprocity.\n\nDeFi Education Fund\n\nVote: For\n\nType: Onchain\n\nAs stated in our Snapshot justification above, we admire the crucial work that the DEF conducted over the past handful of years. We therefore endorsed the 1M UNI spend. In our conversations with the DEF, they explained how much more costly legal fees are than us delegates expect. This is certainly not our domain of expertise, so we are taking the word of those who have more experience in this subject matter. The following also gave us confidence in the DEF’s alignment with the DAO:\n\n“It is important to us that DEF remains aligned with the DeFi community and our supporters over the long term. Upon passage, 500k $UNI tokens will be transferred to DEF’s on-chain Coinbase $UNI wallet, and 500k will be locked up in a streaming contract that will “vest” linearly over 12 months. Governance can vote to stop the streaming of the remaining tokens at any time.\n\nWe will hold half of any tokens we receive for at least 12 months from the date we receive them, and we will pre-disclose all sales plans in writing.”\n\nUniswap Delegate Reward- 3 Months Cycle 1\n\nVote: For\n\nType: Onchain\n\nPlease see the related Snapshot vote above for our justification–which remains unchanged between the Snapshot and onchain vote.\n\nJune Voting Update\n\nUniswap Arbitrum LTIPP Matching\n\nVote: (1st) $500k, (2nd) $250k, (3rd) $750k, (4th) $1m, (5th) Do not fund\n\nType: Snapshot\n\nWe voted to allocate a sufficient amount of capital as matching the Arbitrum DAO’s LTIPP allocation. Our work on the UADP has shown us that the Arbitrum ecosystem has strong respect for Uniswap, and this is empirically supported by the data. Uniswap currently has the largest market share by volume and TVL–and it’s not even close.\n\n1380×770 130 KB\n\nIn order to sustain a healthy relationship with the Arbitrum DAO in the long run, we vied to allocate either 500k or 250k worth of incentives to this program. This would supplement the previous liquidity mining initiative that Gauntlet has been running for the past three quarters. Although, this time around, they are altering their methodology: “Unlike the previous Arbitrum LM campaign, which relied on a simulation-based framework to identify pools with the greatest boosts to price execution under different liquidity scenarios, this program employs a predictive model that reallocates a fixed budget towards pools with the highest response to incentives, ensuring dynamic and efficient allocation.” Our team is For this type of experimentation and therefore would endorse incentives over no incentives–but do hope for a medium-sized allocation as opposed to an exorbitant one.\n\nUniswap Arbitrum LTIPP Matching\n\nVote: For\n\nType: Onchain\n\nWe voted for $500k and $250k as our primary options during the Snapshot. Although we helped bring this proposal forth, we do believe that a more conservative amount of capital should have been allocated to LTIPP matching–ideally $500k being the cap. However, as we stated, in the event that we have to choose between no incentives and a larger amount of incentives, we would select the larger amount of incentives. That’s why we voted For the $750k allotment. This generally sends a strong message to the Arbitrum DAO regarding our continued interest and support for the L2’s ecosystem. Future incentive and grant programs could therefore be easier to attain from the Arbitrum ecosystem if we pass this proposal.\n\n4 Likes\n\nMichigan Blockchain Delegate Platform\n\nAranaDigital\n\nAugust 1, 2024, 5:36am\n\n3\n\nJuly Voting Update\n\nUniswap Onboarding Package - Gnosis Chain\n\nVote: $250k\n\nType: Snapshot\n\nOur team voted to allocate $250k worth of $UNI towards Gnosis Chain incentives. This is a strong starting point for an initial round of incentives. The current DEX market dominance on Gnosis is led by Balancer, which in our opinion, means there’s a clear market opportunity for a more capital efficient, concentrated liquidity AMM to capture market share. Simply introducing Uniswap to Gnosis should increase the TVL of v3 pools off the bat. This deployment has technically been live for over a year now, but there hasn’t been a UI for LPs and swappers to interact with the protocol. Utilizing Oku as the FE should resolve this disparity.\n\nA large package over $500k is likely not the best idea since there doesn’t seem to be fierce competition to dominate the market from day-one. This is usually the case with newly-launched EVMs–and Gnosis has been around for some time. Hence, the liquidity incentives here are primarily for initially drawing liquidity away from Balancer and Gyroscope. This initial jolt of incentives ideally leads to sticky liquidity in v3 pools. Plus, the overall volume on Gnosis Chain is less than that of other target chains that attained $250k worth of incentives. In a single day, for example, Gnosis will direct ~$3M of volume, while Scroll $30M, and Linea will do $40M. Therefore, the addressable market from a volume perspective is also comparatively smaller than that of other chains. This does mean that the introduction of Uniswap will increase the trading appetite on Gnosis, thereby expanding the market on the basis of volume.\n\nTreasury Delegation Round 2 Ideas Thread\n\nAranaDigital\n\nAugust 30, 2024, 10:01pm\n\n4\n\nAugust Voting Update\n\n[TEMP CHECK] Uniswap Onboarding Package - OKX Chain\n\nVote: Against\n\nType: Snapshot\n\nWe voted against instituting incentives for this deployment due to concerns surrounding liquidity. The incentive package itself would make up a large portion of the overall TVL on the chain. Although the DAO has offered incentives to chains with low TVL, many of them have had other catalysts to justify the spending. We don’t see an explicit one here.\n\n[Temp Check] Forse Analytics for Uniswap Revitalization and Growth Program\n\nVote: 33.3% for Base, 33.3% for Blast, 33.3% for Scroll\n\nType: Snapshot\n\nWe selected some of the chains with less activity for the reasons below–along with Base:\n\nWe’d also like to highlight our concerns around overlap between the retroactive analysis that Gauntlet will be conducting on the LTIPP and what Forse will be analyzing. There were no incentives from the URGP for Arbitrum.\n\nOnboarding Package for Gnosis Chain\n\nVote: For\n\nType: Onchain\n\nOur reasoning for the onchain vote remains the same as our decision from the temp check:\n\nOur team voted to allocate $250k worth of $UNI to Gnosis Chain incentives, positioning Uniswap to capture market share from Balancer, the current DEX leader on the chain. A larger incentive package is unnecessary given the relatively low competition and smaller trading volume on Gnosis compared to other chains. The primary goal is to draw liquidity away from Balancer and Gyroscope.\n\n[TEMP CHECK]- Revised - Uniswap Onboarding Package - OKX Chain\n\nVote: For\n\nType: Snapshot\n\nWe voted against instituting incentives for this deployment due to concerns surrounding liquidity in the precious temp check–but are of the belief that if any v3 deployment is approved of by the DAO, it should have a plan to incorporate a front-end. Hence, subsidizing the Oku integration makes sense. The matter around TVL deficiency is well-addressed here. It demonstrates buy-in from the OKX team, which could open doors for collaboration in the future. This deployment, however, should first demonstrate success in driving organic volume first. If there are other catalysts that arise for OKX chain in the future, we can also revisit incentives.\n\n[Temp Check] Activate 2, 3, 4 bps fee tiers on Uniswap v3 on Base / [REDO: Temp Check] Activate 2, 3, 4 bps fee tiers on Uniswap v3 on Base\n\nVote: For (both)\n\nType: Snapshot\n\nIt would be an interesting experiment to see if adding additional lower fee tiers would materially enable Uniswap to capture volume from Aerodrome. Uniswap is still doing well, and it’s largely the case that Aerodrome itself is doing better than it historically has. Incentives are a large contributor to this success. Uniswap has stopped providing incentives to Base pools as of July 25. There doesn’t seem to be a material difference in volume post-incentives, at least at first glance. We’d need a more in-depth analysis to say for sure. It would also be interesting to see what the data show if incentives were to be normalized–unsure how difficult that is to do.\n\nLowering fee tiers will invariably lead to Aerodrome doing the same. So the risk of shifting liquidity, and hence fragmentation, along with a race to very ~no fees isn’t to be ignored. We are concerned regarding how much time this “experiment” will take to play out, especially with v4’s release being imminent. But if this fee addition can be put into effect soon, it could provide interesting data leading up to v4’s release.\n\nDeploy Uniswap v3 on X Layer\n\nVote: For\n\nType: Onchain\n\nSame as the temp check, we are For onboarding Uniswap v3 to X Layer by subsidizing the Oku integration. We also appreciate the liquidity commitment by the OKX team.\n\n[Temp Check] Uniswap Delegate Reward Initiative - Cycle 2\n\nVote: Yes\n\nType: Snapshot\n\nThe first cycle of delegate rewards has further formalized contributions from active delegates. One point of feedback from the DAO was that newer and smaller delegates have an unfair disadvantage when it comes to attaining rewards. To help reduce this barrier of entry, this round introduced a more relaxed set of requirements, while simultaneously giving a marginal benefit to older delegates who have been contributing for a longer period of time. This setup incentivizes older delegates to be on top of their game since the penalty for missing a vote is quite high–and it allows for newer delegates to make their way into the top 15 eligible delegates with a higher degree of feasibility.\n\nUniswap Delegate Reward Initiative - Cycle 2\n\nVote: For\n\nType: Onchain\n\nSame reasoning as the temp check–please see above.\n\nAranaDigital\n\nOctober 1, 2024, 1:23am\n\n5\n\nSeptember Voting Update\n\n[Temp Check] - Ethereum Foundation Attackathon Sponsorship\n\nVote: Abstain\n\nType: Snapshot\n\nWe voted to abstain from this proposal partly because we wanted to see if other DAOs would be moving forward with Attackathon grants. It feels more appropriate if various DAO committed smaller chunks of capital as opposed to a few committing large amounts. The Arbitrum onchain vote, for instance, has yet to conclude. Our hesitancy in supporting this proposal largely comes from the current allocation that the DAO has made to donations.\n\n471×364 19.2 KB\n\nMore UNI has been issued towards donations that protocols incentives, WG comp, and delegate incentives combined. This ratio should ideally decrease over time, and donations should be carefully considered prior to the DAO loosely committing to public goods funding. The DEF expenditure of $10M from earlier this year, in our eyes, should be the only donation we give out. If the commitment for the Attackathon were smaller, we’d be more inclined. Plus, if more Eth dapps were on board, the proposal would truly feel like a collective effort, as opposed to asking a small number of DAOs for hundreds of thousands of dollars.\n\nUAC Renewal S3\n\nVote: Renew UAC\n\nType: Snapshot\n\nThe UAC has played a critical role in ensuring a structured process for the deployment of v3 on various EVM environments. It also helps deploy and custody assets for various working groups and programs. This operational function is important for any DAO to have, so we are voting For this renewal.\n\nApproved Budgets Rebalancing\n\nVote: Approved Rebalance\n\nType: Snapshot\n\nIn order to effectively cover the liabilities of the DAO, it is important to denominate program and working group accounts in terms of dollars—not the native token. The risk here is a spiral where the sell pressure from the issued UNI leads to more and more rebalancing. However, we believe that the allotment for rebalancing is negligible enough relative to the circulating supply to prevent any price spirals.\n\nUniswap Delegate Race Tiebreaker\n\nVote: (1st) Tane, (2nd) Both (create an extra 16th spot), (3rd) Argonaut\n\nType: Snapshot\n\nThe primary issue with this vote was the fact that two applicants went through two rounds of tie-breakers before Tane was finally selected. Argonaut claimed that the process was unclear—which it was to an extent. It will be important to reduce any subjectivity in future votes. This particular scenario was a rare instance where both candidates voted on the same proposal, but Argonaut did so earlier. However, it was a part of the same vote, therefore, Argonaut should not be favored over Tane. There’s no point in rewarding someone for voting earlier, in most cases. As a result, the forum activity was considered to be the third tie-breaker, which was not effectively communicated to the DAO. However, this method has been used before, so if we had to choose a candidate, it would be Tane here.\n\nProposal to active 2, 3, 4 bps fee-tiers on Base\n\nVote: For\n\nType: Onchain\n\nAs per our reasoning for the snapshot, we are voting For this proposal. The optionality for undercutting fees as a competitive measure seems like an interesting experiment. A primary concern is still the degree of incentives that Aerodrome has, which will eventually subside, and Uniswap will likely become more competitive again. Hence, we are viewing this more as an experiment.\n\nUniswap Accountability S3 Renewal and Rebalance\n\nVote: For\n\nType: Onchain\n\nAs per the above snapshot reasoning, we are in favor of this proposal. It is important for the DAO to cover its liabilities in dollar terms, and the continuation of the UAC is important for effective operational execution of incentives, multi-chain deployments, and escrow/accountability for DAO-led teams and programs.\n\nForse Analytics for Uniswap Revitalization and Growth Program\n\nVote: For\n\nType: Onchain\n\nSomeone has to conduct a retrospective analysis of the URGP. It is a critical step in moving forward with future incentive programs. We also elected to analyze protocols exclusively in the URGP and not the LTIPP:\n\nOur team had some concerns about overlap between the retrospective analysis that would be completed by Gauntlet for the Arb LTIPP and the analysis that Forse would provide for the same protocol. StableLab communicated with Gauntlet to split the work around Arbitrum, so we are comfortable with supporting this analysis now.\n\nAranaDigital\n\nNovember 1, 2024, 2:01am\n\n6\n\nOctober Voting Update\n\nUniswap Accountability Committee S3 Elections\n\nVote: 25% Alex, Alice, Doo, Jojo\n\nType: Snapshot\n\nWe decided to split our votes evenly across the above four candidates based on our previous relationships with them and our observations regarding their work with DAOs and DeFi protocols. Our team has had the pleasure of working with Alex, Alice, and Doo on the UTWG. We also chose Jojo since he’s demonstrated his value to the DAO via the UAGP.\n\n[TEMP CHECK] - Onboarding Package for Lisk\n\nVote: For\n\nType: Snapshot\n\nWe voted in favor of this proposal. ​The main play with Lisk is getting a strong foothold early on in their ecosystem. Lisk had their L1 to OP L2 transition recently so many dapps have yet to launch, and Uniswap is one of the first ones there. Much of the non native token liquidity is coming in now as more users are onboarded, along with commitments from other dapps. This is all occurring in Q4. Yes, this deployment is not one where we enter a more mature and competitive market—we’re simply trying to be first. The $1M in usdc, usdt, LSK, and weth from Lisk would make uni the go to place for trading on the chain. Estimating the value of a deployment can be tricky especially when the chain isn’t immediately drawing a large amount of social attention on launch. Celo is a unique example here. The chain took a long time to mature, but since Uniswap was early there, it got a foothold, and now it’s a top deployment for Uniswap\n\nUniswap Growth Program Trial\n\nVote: In Support\n\nType: Snapshot\n\nThe DAO has been engaged with BD work for the past year. These initiatives primarily hinge around deployments of Uniswap v3 on a variety of EVM environments. Although the UAC has been intimately involved with walking the target chains through the governance process, establishing connections with relevant front-ends, and negotiating a proper onboarding package, there are two aspects that are left unmet: outbound BD and marketing. Most of the deals that the UAC addresses are inbound. Various sources either approach the team or are directed to the UAC; however, the UAC is not actively involved in finding deals—that’s where AG comes in. Using their CRM, they’ve set up a pipeline that’ll help facilitate the outreach to every new EVM that goes live or is looking to go live. Those deals will then be funneled to the UAC. On the end of this pipeline, once a deployment is officiated or when a package is voted in, AG will also market those deals to the broader community, ideally pulling in more volume and TVL, thereby increasing the effect of the campaigns. This role is especially important since the UF nor Labs market DAO-approved programs from onboarding packages or new chain deployments.\n\n[TEMP CHECK] - Tally Uniswap Proposal\n\nVote: For\n\nType: Snapshot\n\nAs the usage data show, and as the above comments have illustrated, Tally is the go-to voting platform for many—our team is no exception. We will therefore be supporting this proposal. The pricing also seems to be fair since Tally will not only be taking care of rudimentary voting processes and functionalities, but they’ll also be involved in the development of various governance-related products such as optimistic voting. Plus, they’ve shown their ability to nicely blend UI/UX details with backend smart contracts. This will be interesting to see play out if the UniStaker setup is followed through with, for instance. Quarterly reports and custody of funds with the UAC act as a bonus precaution with this proposal as well.\n\n[Updated] Forse Analytics for Uniswap Revitalization and Growth Program\n\nVote: For\n\nType: Onchain\n\nAs per our vote on the previous onchain vote, we also voted For this proposal. We are happy with the alterations made to amended terms.\n\nUniswap Growth Program Trial\n\nVote: For\n\nType: Onchain\n\nAs per our reasoning with the snapshot vote for this proposal, we also voted For it in the onchain stage.\n\nAranaDigital\n\nDecember 1, 2024, 12:04am\n\n7\n\nNovember Voting Update\n\n[TEMP CHECK] - Tally Uniswap Proposal\n\nVote: For\n\nType: Snapshot\n\nAs the usage data show, and as the above comments have illustrated, Tally is the go-to voting platform for many—our team is no exception. We will therefore be supporting this proposal. The pricing also seems to be fair since Tally will not only be taking care of rudimentary voting processes and functionalities, but they’ll also be involved in the development of various governance-related products such as optimistic voting. Plus, they’ve shown their ability to nicely blend UI/UX details with backend smart contracts. This will be interesting to see play out if the UniStaker setup is followed through with, for instance. Quarterly reports and custody of funds with the UAC act as a bonus precaution with this proposal as well.\n\nSupporting Tally’s Development and Enhancements for Uniswap DAO Governance\n\nVote: For\n\nType: Onchain\n\nAs per our reasoning during the Snapshot phase, we voted in favor of this proposal. Some numbers have been thrown around regarding the per proposal cost for Tally (i.e. divide the $500k program cost by the number of proposals Uniswap has executed). We don’t think this is a reasonable approach to pricing. There are auxiliary features beyond the mere ability to vote that Tally aids with. Providing a strong front-end that easily allows users to put up proposals, and in the future, enable delegates to interact with smart contracts like the Unistaker should not be priced on a per proposal basis. The mentioned are just a few features that integrate with Tally. The UAC will monitor the effectiveness of the program as well. If the value being provided does not match the costs, we will inform the DAO. We will also rely on delegate feedback regarding Tally’s periodic reports to see if the sentiment around this initiative remains positive.\n\n1 Like\n\nAranaDigital\n\nJanuary 1, 2025, 5:12am\n\n8\n\nDecember Voting Update\n\n[TEMP CHECK] Uniswap DAO Principles\n\nVote: For\n\nType: Snapshot\n\nGenerally agreed principles selected by the DAO are important for setting social standards and overall decorum among governance stakeholders. These should be continually revisited and adjusted to accommodate for changes in the DAO’s landscape—but the current points seem to be quite ubiquitous regardless of changes to the ecosystem or DAO. It’s important to note that most aspects continued in the proposal are hard to enforce. That’s why the focus of these principles will likely be for participation in DAO initiatives. These principles will determine whether or not including particular groups and individuals into delegate reward and treasury-based delegation programs, along with elections for working groups, is a wise choice. Those who violate DAO-set rules would be less likely to participate in these. At the end of the day, the outcome here is not to pursue legal action against violators, nor should that be the goal. Actors in a DAO should be able to act according to their will, but a lack of decorum may come at a social cost.\n\n[Temp Check] - Adopt The SEAL Safe Harbor Agreement\n\nVote: For\n\nType: Snapshot\n\nAlthough the Uniswap v3 contracts have been audited multiple times, battle tested over the past couple of years, it’s prudent to keep security top of mind. The tricky aspect is the numerous deployments that now exist. There are over 25 official deployments, and therefore, over 25 v3 factory contracts to be aware of—which of course includes the associated periphery addresses and factory owners. This leads to increased attack surface area. Having a system to incentivize whitehats to ensure safe recovery of potentially compromised funds related to these contracts and/or identify the nature of malicious attacks is important.\n\n[TEMP CHECK] Scale Uniswap Liquidity on Celo\n\nVote: For\n\nType: Snapshot\n\nCelo was one of the first v3 instances. Due to a first mover advantage, Uniswap has attained a solid lead ahead of competing DEXs in terms of market share. The commitments that Stabila and Celo have made over the past year are significant. We are voting in favor of this proposal as it further deepens our relationship with Celo as they make their transition to an OP L2. Their team has signaled interest in furthering their incentive program over the coming year, and in order to support their commitment, allocating the DAO’s funds to magnifying the campaign seems prudent. Much of this is about sustaining our market lead so that Celo does not begin incentivizing competitors.\n\n[TEMP CHECK] Metal L2: Bridging TradFi and DeFi Through Uniswap V3\n\nVote: Abstain\n\nType: Snapshot\n\nWe abstained on this proposal because we believe that an avenue for a potential collaboration should be left open with Metal, but in the current state of the chain, it is not yet ready to receive the $250k allocation. Sure, the expense ratio currently is about 2:1 ($520k:$250k), but we’d like to see more traction from Metal before the DAO commits funds to its growth. Metal has also conducted deals with Velodrome and Ionic, but from our understanding, those proposals have not committed capital to Metal.\n\nDiscretionary Budget from UAC for Co-Incentive Campaigns\n\nVote: Allow UAC Surplus\n\nType: Snapshot\n\nThere are various instances where deals need to be conducted with target chains and other partners. Many times when negotiations are taken through a 4+ week DAO process, the negotiating terms are less favorable as the speed for execution is lackluster and partners are publicly disclosing potential deals that would not bring favorability with other partners. In traditional businesses, most of these deals are done behind closed doors. This setup would effectively make the negotiation and deal execution part more private—but prioritize transparency in a retrospective manner. We are therefore voting For this.\n\nIncentive Package for Sonic (Formerly Fantom)\n\nVote: 250k incentive match\n\nType: Snapshot\n\nWe voted in favor of the 250k 2:1 match. Out of all the features, the fee sharing mechanism (FeeM), where 90% of the fees generated by apps are shared back to that app, creates the most interesting avenue for a partnership between Sonic and Uni DAO. A revenue model for Uni DAO would be established as a result of this deployment. This would be the first instance that the DAO would be making operating income. Furthering our relationship with ecosystems that have such symbiotic mechanisms is important. The Sonic ecosystem has also seen active community engagement through various airdrop programs, such as the Sonic Points and Sonic Gems initiatives, which reward both users and developers. We are in talks with the Merkl team regarding how Uniswap DAO can take advantage of these incentives. Marketing will be important for this, along with a potential match of capital from the DAO.\n\nAranaDigital\n\nJanuary 31, 2025, 11:46pm\n\n9\n\nJanuary 2025 Voting Update\n\nIncentive Package for Sonic\n\nVote: For\n\nType: Onchain\n\nIn correspondence with our vote in favor of this proposal during the Snapshot vote, we are voting For it during the onchain phase. The 2:1 ratio in terms of incentives is reasonable for Sonic, especially since it has had a decent amount of eyes and mindshare going into launch.\n\nScale Uniswap Liquidity on Celo\n\nVote: For\n\nType: Onchain\n\nIn correspondence with our vote in favor of this proposal during the Snapshot vote, we are voting For it during the onchain phase. Celo has been one of the earliest deployments and is also on the canonical Uniswap.org front-end. This should also help facilitate further adoption from users. And for more sophisticated individuals, the Oku integration will be a plus for them, especially for FXS-type tokens.\n\nUniswap DAO Principles\n\nVote: For\n\nType: Onchain\n\nIn correspondence with our vote in favor of this proposal during the Snapshot vote, we are voting For it during the onchain phase. A general set of principles is good for holding individuals accountable, especially with programs like delegate incentives.\n\nGovernance Proposal - Adopt The SEAL Safe Harbor Agreement\n\nVote: For\n\nType: Onchain\n\nIn correspondence with our vote in favor of this proposal during the Snapshot vote, we are voting For it during the onchain phase. We believe that this is a right step towards taking protective measures against potential exploits.\n\nAranaDigital\n\nMarch 4, 2025, 1:23am\n\n10\n\nFebruary 2025 Voting Update\n\n[Temp Check] Uniswap Delegate Reward Initiative - Cycle 3\n\nVote: For\n\nType: Snapshot\n\nIn line with our positions from the previous two cycles, we have voted in favor of this proposal. Making sure that delegate compensation criteria are well-designed is not an easy feat as it introduces multiple subjective variables, often those that are difficult to implement without an extensive amount of overhead, both in terms of analysis and coordination. We are therefore content with the current setup where delegates are selected primarily based on their participation history. Such a measure is more objective. This round increased the weight on voting %, which we think is apt. Additional metrics like proposal creation and community call attendance are marginally useful but can add up when competing with other delegates for a spot in this program. The time between execution of a proposal and a delegate’s justification for that proposal is a good addition in this cycle that improves timely contribution. However, there remains the contention around alignment. Most delegates including us do not have a large economic stake in the UNI tokens. A vesting setup could help reduce related issues. Perhaps a setup where there’s a baseline level of UNI that a delegate can opt in for could align incentives better—otherwise they attain a larger sum but paid later.\n\nAranaDigital\n\nMarch 10, 2025, 1:03am\n\n11\n\nMarch 2025 Voting Update\n\n[Temp Check] Uniswap Unleashed\n\nVote: Abstain\n\nType: Snapshot\n\n[Temp Check] Unichain and Uniswap v4 Liquidity Incentives\n\nVote: For\n\nType: Snapshot\n\nCombined Rational:\n\nReflecting on this proposal, we find ourselves holding two key positions: the UF needs to be funded, yet that funding must be met with structured oversight due to potential execution risk. Cutting or drastically reducing UF’s funding doesn’t seem to yield a net-positive outcome, especially given the evolving landscape of Uniswap itself. Uniswap v4 transitions the protocol from a baseline infrastructure into a platform, and Unichain represents an even larger shift as an independent L2. A formal steward is needed to guide these changes. We voted in favor of the incentives proposal with Gauntlet realizing that the adoption of a general purpose L2 and a platform contingent on builders, v4, needs incentives. The landscape is simply too competitive. Gauntlet is a strong choice for the first iteration of the program, but we would prefer working more closely with hooks teams for incentive management in the future. Some RFP structure would be ideal. We will reevaluate this stance come the next tranche of incentives funding. The timelock’s clawback capabilities with the Aera vaults is a good touch.\n\nBeyond Uniswap’s own developments, broader regulatory shifts—most notably, the anticipated adoption of DUNA—could finally unlock direct revenue streams for token holders, marking a pivotal moment where the DAO can engage in more active treasury management. For too long, the DAO has been sidelined, while Labs has been the primary beneficiary of Uniswap’s success. That dynamic is set to change. But the key question remains: with all these moving pieces, can the UF effectively execute its mandates?\n\nThis leads to a larger governance challenge: ensuring that UF’s funding is spent in a way that directly benefits the DAO and token holders. The UF, as a 501(c)(4), is legally mandated to prioritize DeFi broadly, not Uniswap specifically. This distinction introduces a risk that some initiatives, such as the proposed $4.5M allocation for CFMs, could end up benefiting the broader DeFi ecosystem without yielding proportional gains for Uniswap. While political engagement is a key advantage of UF’s legal status—evidenced by their efforts in regulatory advocacy—there needs to be a mechanism ensuring that DAO funds are used prudently.\n\nA potential solution is a formalized contract between the DAO and UF, enforcing clear KPIs and accountability measures. However, the DAO currently lacks the legal structure to enter into such agreements. This may change with the implementation of DUNA, but in the interim, alternative safeguards are necessary. One option is electing a dedicated oversight board, composed of industry experts and Uniswap delegates, to ensure strategic alignment. Another is structuring UF’s funding request in multiple tranches, similar to the initial 2022-2023 funding approach, to enable more iterative and disciplined capital allocation. A clawback mechanism could also be introduced, allowing the DAO to reclaim a portion of funds if performance metrics aren’t met.\n\nTo those ends, while we are excited to see the prospects surrounding core contributors, incubator programs, etc, we believe that the introduction of v4 and Unichain add too much new surface area for there not to be an interim review at the end of the year. This would make this funding ask contingent on explicit KPIs with clawback capabilities from the DAO. Due to this missing piece, we voted abstain from the funding proposal itself.\n\nUniswap Delegate Reward Initiative - Cycle 3\n\nVote: For\n\nType: Onchain\n\nIn line with our reasoning from the temp check phase, we decided to vote in favor of this proposal due to the benefit it has provided the DAO in terms of cultivating a stronger and more active set of delegates. It’ll be important to continue monitoring how beneficial the behavior as a result of this program remains and how it can be continually iterated upon.\n\nAranaDigital\n\nMarch 21, 2025, 10:35pm\n\n12\n\nUnichain and Uniswap v4 Liquidity Incentives\n\nVote: For\n\nType: Onchain\n\nUnichain and v4 will require incentives due to the competitive nature of DEXs and L2s alike. Uniswap is losing market share in the DEX space, and migrating liquidity to a new platform won’t be easy. We like the clawback present in the proposal so funds can be halted or recouped if the first handful of months are not executed in a desired manner. All the other reasons behind our support are substantiated in the above rationale regarding the Snapshot vote.\n\nUniswap Unleashed\n\nVote: Abstain\n\nType: Onchain\n\nAs per our above rationale, we abstained on this proposal because amendments around the tranched setup for funding were not included. Nor was there an addition of a clawback setup, like there is for the liquidity incentives proposal. We still believe that funding the UF is important, but there should be more concrete implementations around upholding proper execution of the stated programs. Directionally in support.\n\n[Temp Check] Saga Uniswap v3 Liquidity Incentives\n\nVote: For\n\nType: Snapshot\n\nThis incentives deal has been the most favorable one for the DAO to take on a purely cost ratio basis. The Saga team offered around $700k per month (given constant token price), while UNI would only have to commit $250k. Some have argued that there is risk related to Saga itself, which are fair concerns. However, Saga has promised to make the Uniswap deployment the canonical DEX on their chain/chainlets, allowing for us to attain direct support of the Saga Foundation. The same cannot be said for most alternative L1s/L2s. There aren’t native DEXs to compete with since Uniswap has been one of the first deployed dapps. From the perspective of monopolizing the DEX market on Saga, this is a smart move.\n\n1 Like\n\nAranaDigital\n\nApril 7, 2025, 3:32am\n\n13\n\nApril 2025 Voting Update\n\n[Temp Check] Treasury Delegation Round 2\n\nVote: For\n\nType: Snapshot\n\nGenerally, we are in favor of this initiative and see it as a net benefit regardless of the drawbacks. Although the nature of Staker may significantly alter the delegation landscape, the details of how that’ll transpire are still unpredictable. The structure for Staker should be designed to funnel voting power towards those who contribute to Uniswap actively and meaningfully—and not just to name-brand entities.\n\nAnother aspect that we have a preference towards is using different metrics/methods to select the delegates who receive delegation:\n\nIn sum, although there are aspects of the program that can be refined, we are in favor of continuing treasury delegation under the current state without Staker being active, and the presence of expiring delegation is something we’d like to see implemented via this program.\n\nAranaDigital\n\nApril 11, 2025, 12:35am\n\n14\n\n[TEMP CHECK] BoB Uniswap v3 Incentives Package\n\nVote: For\n\nType: Snapshot\n\nBOB is one of the most prominent L2s with a Uniswap deployment and has seen considerable growth in the past couple of months. They have also made a clear commitment to utilize Uniswap, via Oku, as their canonical front-end, which is seldom the case with new L2s who are most often adamant about incentivizing the growth of native DEXs. As far as getting exposure to BTC-fi, BOB is a great way for Uniswap to do so. Access to the growth of emerging protocols like Babylon, for example, can be done via BOB. In fact, it’s likely that some of the Babylon incentives may also flow to Uni v3 pools on BOB soon. Plus, the expense ratio in terms of what the BOB team is committing and what Uniswap is committing is near 1, thereby making this a financially prudent allocation. We are therefore voting in favor of this proposal.\n\n[TEMP CHECK] Establish Uniswap v4 Licensing Process\n\nVote: For\n\nType: Snapshot\n\nIn order to conduct any expansions on the v4 front, there needs to be a process for granting license exemptions to entities selected by the DAO. Choosing UF as the initial group for a blanket exemption makes sense. And granting writing capabilities to UAC, like is the case with v3 and v2, is also prudent.\n\nAranaDigital\n\nApril 17, 2025, 11:32pm\n\n15\n\nBoB Uniswap v3 Incentives Package\n\nVote: For\n\nType: Onchain\n\nAs per our Snapshot vote, we voted in favor of passing the onboarding package for BOB due to the following reasons—\n\nBOB’s commitment to making Uniswap the canonical DEX on their chain.\n\nCommitting to at least a 1:1 match between Uni DAO’s allocation and their incentive allocation.\n\nHigh level of existing adoption for Uni v3 on their chain relative to other chains.\n\nUniswap’s increased exposure to the intersection of BTC & DeFi.\n\nAranaDigital\n\nApril 24, 2025, 10:10pm\n\n16\n\nUAC Renewal S4\n\nVote: For\n\nType: Snapshot\n\nIn order to continue sustaining and growing a handful of the DAO’s operations for the coming year, we believe that it’s prudent to renew the UAC for a Season 4. The team has over time become the go-to operational entity for the DAO, partaking in growth initiatives, incentive distribution, escrow of funds, and overseeing cross-chain deployments.\n\nApproved Budgets Rebalancing (S4)\n\nVote: For\n\nType: Snapshot\n\nSince the UAC does not have the ability to sell any of the UNI for USD at the present time, all of the accounting must be conducted in terms of UNI, even though most of the stated budgets are dollar-denominated. In order to balance between not underpaying or overpaying working groups and grantees—as well as incentive distributions—it’s best-practice to top up needed balances. The budgets are all technically liabilities to entities that have requested the UNI, but until certain milestones are met and verified by the UAC, the UNI present in the UAC multisigs are effectively an extension of the treasury.\n\n[Temp Check/Revised] Treasury Delegation Round 2\n\nVote: For\n\nType: Snapshot\n\nIt seems the DAO has come to a general consensus around this proposal, where a transient delegation from the treasury makes sense to sustain meeting quorum during onchain proposals, as well as allowing entities to post votes by meeting the proposal threshold. Unistaker likely won’t be active until the end of the year. The timeline for reviewing the treasury delegation at a sooner date than initially proposed should somewhat align with the launch of Unistaker, at which point, in an ideal world, organic delegations become the resounding norm and treasury delegations are slowly phased out. If tokens from the treasury are to be delegated at all, it should ideally be a very exclusive program—not as broad as the present one.\n\nEstablish Uniswap v4 Licensing Process\n\nVote: For\n\nType: Onchain\n\nAs per our Snapshot vote, we have voted in favor of this proposal because it sets the foundation for allowing the DAO to begin initializing v4 deployments on alternative EVMs.\n\n1 Like\n\nvfsawesnhribc\n\nApril 26, 2025, 5:38pm\n\n17\n\nNice and thanks for post in forums\n\nAranaDigital\n\nMay 9, 2025, 8:05pm\n\n18\n\nMay 2025 Voting Update\n\n[TEMP CHECK] Scaling V4 and Supporting Unichain\n\nVote: For\n\nType: Snapshot\n\nOku has proven itself to be a strong partner of the DAO, helping expand v3’s presence across 20+ EVM environments. They’ve also managed to create a self-sustaining business after having attained an initial grant from the UF. The Oku brand is largely conflated with the Uniswap brand at this point, and the target chains that we collaborate with have vouched for Oku’s product.\n\nThe incorporation of the blanket license exemption also seems like a prudent operational addition:\n\nOku must work in the confines of the DAO-approved deployment process, and they will only be compensated if they do so. We therefore don’t take issue with extending them a license exemption.\n\nUAC Renewal S4\n\nVote: For\n\nType: Onchain\n\nAs per our vote in favor of this proposal during the Snapshot phase due to the critical role that the UAC plays in Uni DAO operations, we are voting in favor during the onchain phase as well.\n\nApproved Budgets Rebalancing (S4)\n\nVote: For\n\nType: Onchain\n\nAs per our vote in favor of this proposal during the Snapshot phase due to the importance of effectively accounting for the DAO’s liabilities, we are voting in favor during the onchain phase.\n\n[Temp Check] Analytics Hub for Uniswap’s Revitalization and Growth Program\n\nVote: For\n\nType: Snapshot\n\nFour Chains for Analytics Hub for Uniswap’s Revitalization and Growth Program\n\nVote: Unichain, zkSync\n\nType: Snapshot\n\nCombined rationale for the above two:\n\nWe voted in favor of this proposal because we believe the analytics for zkSync and Unichain are uniquely valuable given the structure and intent behind their incentive campaigns. Most of the results out of these in-depth analytics are extrapolatable, so we don’t have to analyze each campaign with high levels of detail. For example, the distribution of UNI incentives on Manta likely follow a very similar dispersion and result pattern to the incentives on Mantle. Hence, analyzing one of these chains often gives similar insights. What’s more valuable for similar incentive campaigns is a more simple dashboard that may be sufficiently provided via a Dune dashboard or by leveraging Oku data APIs. Forse’s product is unique in that it provides in-depth analytics, which is most valuable in certain scenarios. Another chain that I just wouldn’t bother analyzing is Polygon zkEVM since their team has basically deprecated the product.\n\nThe more in-depth type of analytics that Forse offers are most useful for campaigns like the Unichain one, which is being actively managed by Gauntlet. This would be similar to the analysis done on the Arbitrum LTIPP by Forse. zkSync is also interesting because we saw two tranches of this take place. The first tranche was voted in by Uni DAO and dispersed via Merkl in 2024. Then, in Q1 2025, an additional tranche of incentives were allocated to zkSync via the Ignite program, which leveraged OpenBlock Labs’ insights for incentive distribution.\n\nSince many of the early 2024 campaigns were also lacking matching by the target chain, the impact of them is clearly not as robust as we would have hoped. In order for a campaign to do well, it’s best if the UNI allocation is matched by the target chain—and if the pool selection for incentives is conducted as a collaborative process between Uni and the target chain. Further collaboration on incentive distribution as well as matching of those incentives makes campaigns more robust. Buy-in from multiple parties aligns goals, and this is the model that the UAC has started focusing on more keenly. The best examples of this are BOB and Celo—these incentives are actively being deployed over the coming six months. Once they conclude, it would be nice for Forse to analyze these programs.\n\nScaling V4 and Supporting Unichain\n\nVote: For\n\nType: Onchain\n\nWith our position remaining the same as the Snapshot vote, we voted in favor of this proposal. It was good to see the amended Additional Use Grant text during the onchain phase, making the license exemption component more palatable, especially with those who had concerns around the commercial usage aspect of the exemption. We believe the current state of the proposal is favorable for the operational aspect of scaling v4, something that Oku has evidently delivered on with the v3 side.\n\nUniswap Accountability Committee S4 Elections\n\nVote: Even Split Across All Candidates\n\nType: Snapshot\n\nIn order to reduce any degree of bias since Abdullah is currently a part of the UAC, we are in effect abstaining on this proposal by splitting our voting power evenly across each applicant.\n\nAranaDigital\n\nJune 13, 2025, 6:40am\n\n19\n\nJune 2025 Voting Update\n\nScaling V4 and Supporting Unichain (Version 2)\n\nVote: For\n\nType: Onchain\n\nWe voted in favor of this proposal due to the same reasoning as we did in its original version.\n\nTrial run a Technical Advisory Board (TAB)\n\nVote: Against\n\nType: Snapshot\n\nWhile we are not necessarily opposed to the idea of a technical team that is tasked with not only reviewing proposals but also educating delegates on important technical issues, we believe that this proposal can be made more robust. There is presently a lack of clear directives that the TAB will ontake. It would be more compelling to present specific types of educational topics and proposal instances that would require input from the TAB. 2/30 of the last proposals that passed are of less technical criticality as they target either the uniswap.eth ENS domain for text-based alterations—or for sending UNI to the UAC wallet or to the UF. It also doesn’t seem entirely prudent to create a specific facilitator role for the TAB when entities like the UAC are in place and have the ability to facilitate such an initiative under their present purview and funding. This would help the DAO save some capital.\n\nUniswap Unichain - USDS and sUSDS Co-Incentives Growth Management Plan\n\nVote: For\n\nType: Snapshot\n\nWe appreciate the longer-term approach, tranched into various TVL-based milestones for this proposal, contingent in part on stickiness of capital over a 90-day period. Although the process may be a bit cumbersome, the DAO signing off via a monthly Snapshots for incentive deployments is likely okay. We’re happy as a delegate to partake in this more active decision making process but are also fine with a team like the UAC conducting the month-to-month verification, subsequently reporting them to the DAO. The ratio of incentives allocated by Uni DAO and Sky does seem to be slightly tilted—in the sense that we would personally prefer seeing the ratio of Sky:Uni incentives a bit higher than it currently stands. Recent DAO co-incentives have trended more towards higher ratios. However, those are more focused on cross-chain deployments. Potential additional incentives from partner hooks could help increase this ratio. Hence, our main objective will be observing closely the nature of the partnerships Sky is able to bring in with hooks and other protocols. The yield for sUSDS could therefore be higher than 4.5%. If month-to-month we are able to see strong TVL growth, as well as good collaborations/incentive additions from hook partners, then this program would be considered successful. It’s helpful that the incentives are tranched so the DAO is able to continually evaluate these variables.\n\nAranaDigital\n\nJuly 22, 2025, 4:49am\n\n20\n\nJuly 2025 Voting Update\n\n[TEMP CHECK] - Etherlink Co-incentives Proposal\n\nVote: For\n\nType: Snapshot\n\nSince the Tezos ecosystem is well-capitalized and is supporting Etherlink, we believe that this arrangement could prove beneficial for both parties. The overall ask is not very high, and the 2:1 ratio proposed is satisfactory. Etherlink’s Apple Farm incentives program initially allocated a batch of capital to Uniswap v3, and as this proposal states, they intend to add onto that with the second tranche of Apple Farm incentives. They have also indicated that Uniswap v3 will become one of the two main DEXs on the chain, serving as the go-to hub for volatile assets. New launch partners’ tokens are intended to be deposited on Uniswap. If these attain high volume, there could be nice fees generated here. Overall, we believe the capital allocation here is worthwhile.\n\nnext page →\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nAtiselsts.eth Delegate Platform\n\nDelegation Pitch\n\n32\n\n4670\n\nJuly 9, 2026\n\nCuria Delegate Platform\n\nDelegation Pitch\n\n53\n\n2386\n\nJuly 23, 2026\n\nArgonaut Delegate Platform\n\nDelegation Pitch\n\n63\n\n1821\n\nJuly 11, 2026\n\nSEEDGov Delegate Platform\n\nDelegation Pitch\n\n76\n\n3514\n\nMay 5, 2026\n\nTané Delegate Platform\n\nDelegation Pitch\n\n59\n\n2404\n\nMarch 9, 2026","tokens":14206,"crawled_at":1791195308482}
+{"id":10507,"url":"https://docs.sui.io/references/cli/move","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Sui Move CLI | Sui Documentation","text":"The Sui CLI move command provides several commands for working with MoveMoveAn open source programming language used for all activity on Sui. source code. A typical usage of sui move is to compile and test the Move code, or to generate a new Move project by using sui move new project_name, which creates the needed directories and the Move.toml file.\n\nCheck Sui CLI installation​\n\nBefore you can use the Sui CLI, you must install it. To check if the CLI exists on your system, open a terminal or console and type the following command:\n\n$ sui --version\n\nIf the terminal or console responds with a version number, you already have the Sui CLI installed.\n\nIf the command is not found, follow the instructions in Install Sui to get the Sui CLI on your system.\n\nCommands​\n\n$ sui move --help\n\nTool to build and test Move applications\n\nUsage: sui move [OPTIONS] <COMMAND>\n\nCommands:\nbuild\ncoverage Inspect test coverage for this package. A previous test run with the `--coverage`\nflag must have previously been run\ndisassemble\nformat\nlint Run the Move linter on this package\nmigrate Migrate to Move 2024 for the package at `path`. If no path is provided defaults\nto current directory\nnew Create a new Move package with name `name` at `path`. If `path` is not provided\nthe package will be created in the directory `name`\ntest Run Move unit tests in this package\nsummary Generate a serialized summary of a Move package (e.g., functions, structs,\nannotations, etc.)\nupdate-deps Re-pin the dependencies of this package\nhelp Print this message or the help of the given subcommand(s)\n\nOptions:\n-p, --path <PACKAGE_PATH>\nPath to a package which the command should be run with respect to\n--client.config <CONFIG>\nSets the file storing the state of our user accounts (an empty one will be created if\nmissing)\n--client.env <ENV>\nThe Sui environment to use. This must be present in the current config file\n-y, --yes\nCreate a new sui config without prompting if none exists\n--test\nCompile in 'test' mode and include the code in the 'tests' directory\n--doc\nGenerate documentation for packages\n--disassemble\nSave disassembly for generated bytecode along with bytecode maps (source maps for\ndisassembled bytecode)\n--install-dir <INSTALL_DIR>\nInstallation directory for compiled artifacts. Defaults to current directory\n--force\nForce recompilation of all packages\n--allow-dirty\nAllow building, even if some cached git dependencies in `~/.move` are modified\n--default-move-flavor <DEFAULT_FLAVOR>\nDefault flavor for move compilation, if not specified in the package's config\n--default-move-edition <DEFAULT_EDITION>\nDefault edition for move compilation, if not specified in the package's config\n--silence-warnings\nIf set, ignore any compiler warnings\n--warnings-are-errors\nIf set, warnings become errors\n--json-errors\nIf set, reports errors at JSON\n--no-lint\nIf `true`, disable linters\n-q, --quiet\nDisplay less output\n--lint\nIf `true`, enables extra linters\n--mode <MODE>\nArbitrary mode -- this will be used to enable or filter user-defined `#[mode(<MODE>)]`\nannotations during compilation\n-e, --build-env <ENVIRONMENT>\nEnvironment to use for building packages\n--pubfile-path <PUBFILE_PATH>\nPath to ephemeral publication file. When provided, uses ephemeral addresses for\ncompilation instead of addresses from the lock file\n-h, --help\nPrint help\n-V, --version\nPrint version\n\nExamples​\n\nThe following examples demonstrate some of the most often used commands.\n\nCreate a new Move project​\n\nTo create a new Move project that automatically adds the necessary dependencies in a Move.toml file, run sui move new [<PROJECT-NAME>].\n\n$ sui move new smart_contract_test\n\n$ ls -l smart_contract_test\n\nMove.toml\nsources\ntests\n\nDisplay the contents of Move.toml file.\n\n$ cat smart_contract_test/Move.toml\n\n[package]\nname = \"smart_contract_test\"\nedition = \"2024\"\n\n[dependencies]\n\nBuild a Move project​\n\nUse sui move build at the root of your Move project to build the packagePackageSmart contracts on Sui..\n\n$ sui move build\n\nINCLUDING DEPENDENCY Sui\nINCLUDING DEPENDENCY MoveStdlib\nBUILDING smart_contract_test\n\nRun tests in a Move project​\n\nUse sui move test to run the tests in a Move package.\n\n$ sui move test\n\nINCLUDING DEPENDENCY Sui\nINCLUDING DEPENDENCY MoveStdlib\nBUILDING smart_contract_test\nRunning Move unit tests\nTest result: OK. Total tests: 0; passed: 0; failed: 0\n\nLint a Move project​\n\nUse sui move lint to run the Move linter on a package and check for potential issues. The linter runs both generic Move lints and Sui-specific objectObjectThe basic unit of storage on Sui.-model lints.\n\n$ sui move lint\n\nGet test coverage for a moduleModuleA component of a Move package that defines interaction with on-chain objects.​\n\nThis example uses first_package Move package.\n\nTo get a summary of the test coverage, you must first run the sui move test --coverage command, and then the sui move coverage summary --test to get a summary of the test coverage in the example project.\n\n$ sui move test --coverage\n\nINCLUDING DEPENDENCY Sui\nINCLUDING DEPENDENCY MoveStdlib\nBUILDING first_package\nRunning Move unit tests\n[ PASS ] 0x0::example::test_module_init\n[ PASS ] 0x0::example::test_sword_transactions\nTest result: OK. Total tests: 2; passed: 2; failed: 0\n\n$ sui move coverage summary --test\n+-------------------------+\n| Move Coverage Summary |\n+-------------------------+\nModule 0000000000000000000000000000000000000000000000000000000000000000::example\n>>> % Module coverage: 92.81\n+-------------------------+\n| % Move Coverage: 92.81 |\n+-------------------------+\n\nHelp​\n\nEach command has its own help section. For example:\n\n$ sui move build --help\n\nUsage: sui move build [OPTIONS]\n\nOptions:\n-p, --path <PACKAGE_PATH>\nPath to a package which the command should be run with respect to\n--with-unpublished-dependencies\nInclude the contents of packages in dependencies that haven't been published (only\nrelevant when dumping bytecode as base64)\n--dump-bytecode-as-base64\nDump the compiled bytecode as base64-encoded strings in a JSON object, together with the\ndigest and list of dependencies [aliases: dump]\n--no-tree-shaking\nBy default, the CLI will drop any unused dependencies from the output and makes calls to\nthe RPC. This flag disables that behavior and avoids any RPC calls, keeping all\ndependencies in the output (the dependency list). This is useful for offline compilation.\nOnly to be used with `--dump-bytecode-as-base64`\n--generate-struct-layouts\nIf true, generate struct layout schemas for all struct types passed into `entry` functions\ndeclared by modules in this package These layout schemas can be consumed by clients (e.g.,\nthe TypeScript SDK) to enable serialization/deserialization of transaction arguments and\nevents\n--test\nCompile in 'test' mode and include the code in the 'tests' directory\n--doc\nGenerate documentation for packages\n--disassemble\nSave disassembly for generated bytecode along with bytecode maps (source maps for\ndisassembled bytecode)\n--install-dir <INSTALL_DIR>\nInstallation directory for compiled artifacts. Defaults to current directory\n--force\nForce recompilation of all packages\n--allow-dirty\nAllow building, even if some cached git dependencies in `~/.move` are modified\n--default-move-flavor <DEFAULT_FLAVOR>\nDefault flavor for move compilation, if not specified in the package's config\n--default-move-edition <DEFAULT_EDITION>\nDefault edition for move compilation, if not specified in the package's config\n--silence-warnings\nIf set, ignore any compiler warnings\n--warnings-are-errors\nIf set, warnings become errors\n--json-errors\nIf set, reports errors at JSON\n--no-lint\nIf `true`, disable linters\n-q, --quiet\nDisplay less output\n--lint\nIf `true`, enables extra linters\n--mode <MODE>\nArbitrary mode -- this will be used to enable or filter user-defined `#[mode(<MODE>)]`\nannotations during compilation\n-e, --build-env <ENVIRONMENT>\nEnvironment to use for building packages\n--pubfile-path <PUBFILE_PATH>\nPath to ephemeral publication file. When provided, uses ephemeral addresses for\ncompilation instead of addresses from the lock file\n-h, --help\nPrint help\n-V, --version\nPrint version\n\nRelated topics\n\nInstall Sui\nInstall the Sui CLI using suiup, Homebrew, or Chocolatey, verify the installation, and learn about available toolchain components including walrus and mvr.\n\nCommands\nExamplesCreate a new Move project\nBuild a Move project\nRun tests in a Move project\nLint a Move project\nGet test coverage for a module\n\nHelp\n\nWas this page helpful?","tokens":2115,"crawled_at":1791195315246}
+{"id":10508,"url":"https://solana.com/docs/intro/installation/dependencies","domain":"solana.com","chapter":"developer_specs","title":"Install the dependencies necessary to develop with Solana | Solana","text":"Solana DocumentationLocal development\nInstall Dependencies\n\nInstall each dependency separately when you need a specific version or when the\nquick installation does not complete successfully.\nFollow the sections in order for a new environment, or go directly to the tool\nyou need to install or troubleshoot.\n\nPrerequisites\n\nInstall Rust\nDevelopers build Solana programs using the Rust\nprogramming language.\n\nInstall Rust using rustup by\nentering the following command in your terminal:\n\nTerminal\n\n$ curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y\n\nAfter a successful installation you will see the following message:\n\nReload your PATH environment variable to include\nCargo's bin directory:\n\nTerminal\n\n$ . \"$HOME/.cargo/env\"\n\nVerify that the installation was successful.\n\nTerminal\n\n$ rustc --version\n\nThe command prints the installed Rust version, for example:\nrustc x.y.z (...)\n\nInstall Solana CLI\nThe Solana CLI provides all the tools required to build and deploy Solana\nprograms.\n\nInstall the Solana CLI tool suite by using the official install command:\n\nTerminal\n\n$ sh -c \"$(curl -sSfL https://release.anza.xyz/stable/install)\"\n\nYou can replace stable with a specific Agave release tag or with the beta\nor edge release channel.\n\nMake the Solana CLI available in your current terminal.\n\nThe installer updates your shell configuration and prints the command required\nto update the current session. The command is typically:\n\nTerminal\n\n$ export PATH=\"$HOME/.local/share/solana/install/active_release/bin:$PATH\"\n\nIf solana is still unavailable, restart your terminal. To confirm which shell\nconfiguration file the installer updated, check your current shell:\n\nTerminal\n\n$ echo $SHELL\n\nIf the output contains /bash, restart the terminal or run\nsource ~/.bashrc.\n\nIf the output contains /zsh, restart the terminal or run source ~/.zshrc.\n\nVerify that the installation succeeded:\n\nTerminal\n\n$ solana --version\n\nThe command prints the installed Solana CLI version, for example:\nsolana-cli x.y.z (..., client:Agave)\n\nYou can view all available versions on the\nAgave GitHub repository. Agave is\nthe validator client from Anza, formerly known as\nSolana Labs validator client.\n\nTo update the Solana CLI later, run:\n\nTerminal\n\n$ agave-install update\n\nInstall Anchor CLI\nAnchor is a framework for developing Solana\nprograms. The Anchor framework leverages Rust macros to simplify the process of\nwriting Solana programs.\nPrerequisites\nNode.js and a JavaScript package manager are required only when you select a\nTypeScript test template such as Mocha or Jest. The default LiteSVM test\ntemplate runs in Rust and does not require Node.js tooling.\n\nInstallation\nYou can install the Anchor CLI and tooling in two ways:\n\nAnchor Version Manager (AVM) — Recommended installation method\n\nWithout AVM — Install directly from GitHub\n\nThe Anchor Version Manager (AVM) allows you to install and manage different\nAnchor versions on your system and easily update Anchor versions in the future.\nTo install Anchor using AVM, follow the steps below:\n\nInstall AVM with the following command:\n\nTerminal\n\n$ curl -sSfL https://raw.githubusercontent.com/otter-sec/anchor/master/avm/install | sh\n\nConfirm that AVM installed successfully:\n\nTerminal\n\n$ avm --version\n\nInstall Anchor CLI using AVM:\n\nTo install the latest version:\n\nTerminal\n\n$ avm install latest\n\n$ avm use latest\n\nTo install a specific version, specify the version number:\n\nTerminal\n\n$ avm install 1.1.2\n\n$ avm use 1.1.2\n\nWhen installing the Anchor CLI on Linux or WSL, you may encounter this error:\nerror: could not exec the linker cc = note: Permission denied (os error 13)\n\nIf you see this error message, follow these steps:\n\nInstall the dependencies listed in the\nLinux section at the top of this\npage.\n\nRetry installing the Anchor CLI.\n\nVerify that the installation succeeded, by checking the Anchor CLI version:\n\nTerminal\n\n$ anchor --version\n\nThe command prints the active Anchor CLI version, for example:\nanchor-cli 1.1.2\n\nRun avm use to select the Anchor CLI version for your system.\n\nIf you installed the latest version, run avm use latest.\n\nIf you installed version 1.1.2, run avm use 1.1.2.\n\nInstall Surfpool CLI\nSurfpool is a tool for local development and an improved\nreplacement for solana-test-validator.\n\nInstall Surfpool with the following command:\n\nTerminal\n\n$ curl --proto '=https' --tlsv1.2 -sSfL https://run.surfpool.run/ | bash\n\nVerify that the installation was successful by checking the Surfpool CLI\nversion:\n\nTerminal\n\n$ surfpool --version\n\nThe command prints the installed Surfpool CLI version, for example:\nsurfpool x.y.z\n\nIs this page helpful?\n\nPrevious\n\nProduction Readiness\nNext\n\nSolana CLI Basics\n\nTable of Contents\n\nPrerequisitesInstall RustInstall Solana CLIInstall Anchor CLIPrerequisitesInstallationInstall Surfpool CLI\n\nEdit Page","tokens":1205,"crawled_at":1791195319233}
+{"id":10509,"url":"https://www.metaplex.com/docs/smart-contracts/core/external-plugins/adding-external-plugins","domain":"www.metaplex.com","chapter":"docs","title":"Adding External Plugins | Metaplex Core","text":"This guide shows how to add External Plugins (Oracle, AppData) to Core Assets and Collections. Add at creation time or to existing Assets/Collections.\nWhat You'll Learn\nAdd external plugins during Asset/Collection creation\nAdd external plugins to existing Assets/Collections\nConfigure Oracle lifecycle checks\nSet up AppData with data authorities\n\nSummary\nAdd external plugins using create() with the plugins array, or addPlugin() for existing Assets. Collections use createCollection() and addCollectionPlugin().\nAdd at creation: include in plugins array\nAdd to existing: use addPlugin() / addCollectionPlugin()\nRequires update authority signature\nConfigure lifecycle checks for Oracle plugins\nOut of Scope\nRemoving external plugins (see Removing External Plugins), updating plugin data, and built-in plugins (see Adding Plugins).\nQuick Start\nJump to: Create Asset with Plugin · Add to Existing Asset · Create Collection with Plugin\nPrepare your Oracle account or AppData configuration\nAdd plugin at creation or via addPlugin()\nConfigure lifecycle checks (Oracle) or data authority (AppData)\nAssets\nCreating a Core Asset with an External Plugin\nCreating a Core Asset with an External Plugin\n\nimport { generateSigner } from '@metaplex-foundation/umi'\n\nimport { create, CheckResult } from '@metaplex-foundation/mpl-core'\n\nconst assetSigner = publicKey('11111111111111111111111111111111')\n\nconst oracleAccount = publicKey('22222222222222222222222222222222')\n\nawait create(umi, {\n\nasset: assetSigner,\n\nname: 'My Asset',\n\nuri: 'https://example.com/my-asset.json',\n\nplugins: [\n\n{\n\ntype: 'Oracle',\n\nresultsOffset: {\n\ntype: 'Anchor',\n\n},\n\nlifecycleChecks: {\n\nupdate: [CheckResult.CAN_REJECT],\n\n},\n\nbaseAddress: oracleAccount,\n\n},\n\n],\n\n}).sendAndConfirm(umi)\n\nAdding a External Plugin to a Core Asset\nAdding a Plugin with an assigned authority\n\nuse mpl_core::{\n\ninstructions::AddExternalPluginAdapterV1Builder,\n\ntypes::{\n\nExternalCheckResult, ExternalPluginAdapterInitInfo, HookableLifecycleEvent,\n\nOracleInitInfo, ValidationResultsOffset,\n\n},\n\n};\n\nuse solana_client::nonblocking::rpc_client;\n\nuse solana_sdk::{pubkey::Pubkey, signature::Keypair, signer::Signer, transaction::Transaction};\n\nuse std::str::FromStr;\n\npub async fn add_oracle_plugin_to_asset() {\n\nlet rpc_client = rpc_client::RpcClient::new(\"https://api.devnet.solana.com\".to_string());\n\nlet authority = Keypair::new();\n\nlet asset = Pubkey::from_str(\"11111111111111111111111111111111\").unwrap();\n\nlet oracle_plugin = Pubkey::from_str(\"22222222222222222222222222222222\").unwrap();\n\nlet add_oracle_plugin_to_asset_ix = AddExternalPluginAdapterV1Builder::new()\n\n.asset(asset)\n\n.payer(authority.pubkey())\n\n.init_info(ExternalPluginAdapterInitInfo::Oracle(OracleInitInfo {\n\nbase_address: oracle_plugin,\n\nresults_offset: Some(ValidationResultsOffset::Anchor),\n\nlifecycle_checks: vec![(\n\nHookableLifecycleEvent::Transfer,\n\nExternalCheckResult { flags: 4 },\n\n)],\n\nbase_address_config: None,\n\ninit_plugin_authority: None,\n\n}))\n\n.instruction();\n\nlet signers = vec![&authority];\n\nlet last_blockhash = rpc_client.get_latest_blockhash().await.unwrap();\n\nlet add_oracle_plugin_to_asset_tx = Transaction::new_signed_with_payer(\n\n&[add_oracle_plugin_to_asset_ix],\n\nSome(&authority.pubkey()),\n\n&signers,\n\nlast_blockhash,\n\n);\n\nlet res = rpc_client\n\n.send_and_confirm_transaction(&add_oracle_plugin_to_asset_tx)\n\n.await\n\n.unwrap();\n\nprintln!(\"Signature: {:?}\", res)\n\n}\n\nCollections\nCreating a Core Collection with an External Plugin\nAdding a External Plugin to a Core Collection\n\nimport { generateSigner, publicKey } from '@metaplex-foundation/umi'\n\nimport { createCollection, CheckResult } from '@metaplex-foundation/mpl-core'\n\nconst collectionSigner = generateSigner(umi)\n\nconst oracleAccount = publicKey('22222222222222222222222222222222')\n\nawait createCollection(umi, {\n\ncollection: collectionSigner,\n\nname: 'My Collection',\n\nuri: 'https://example.com/my-collection.json',\n\nplugins: [\n\n{\n\ntype: 'Oracle',\n\nresultsOffset: {\n\ntype: 'Anchor',\n\n},\n\nlifecycleChecks: {\n\nupdate: [CheckResult.CAN_REJECT],\n\n},\n\nbaseAddress: oracleAccount,\n\n},\n\n,\n\n],\n\n}).sendAndConfirm(umi)\n\nAdding a External Plugin to a Collection\nBurning an Assets\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { addCollectionPlugin, CheckResult } from '@metaplex-foundation/mpl-core'\n\nconst collection = publicKey('11111111111111111111111111111111')\n\nconst oracleAccount = publicKey('22222222222222222222222222222222')\n\nawait addCollectionPlugin(umi, {\n\ncollection: collection,\n\nplugin: {\n\ntype: 'Oracle',\n\nresultsOffset: {\n\ntype: 'Anchor',\n\n},\n\nlifecycleChecks: {\n\nupdate: [CheckResult.CAN_REJECT],\n\n},\n\nbaseAddress: oracleAccount,\n\n},\n\n}).sendAndConfirm(umi)\n\nCommon Errors\nAuthority mismatch\nOnly the update authority can add external plugins. Verify you're signing with the correct keypair.\nPlugin already exists\nAn external plugin with the same key already exists. Remove it first or update it instead.\nInvalid Oracle account\nThe Oracle base address is invalid or the account doesn't exist.\nNotes\nExternal plugins are Authority Managed (update authority controls)\nOracle plugins require an existing Oracle account\nAppData plugins need a Data Authority for write permissions\nCollection plugins don't automatically apply to existing Assets\nFAQ\nCan I add multiple external plugins to one Asset?\nYes. You can add multiple Oracle and/or AppData plugins to a single Asset.\nDo I need to create the Oracle account first?\nYes. The Oracle account must exist before adding an Oracle plugin adapter.\nWhat's the difference between adding at creation vs adding later?\nNo functional difference. Adding at creation is more efficient (one transaction). Adding later requires a separate transaction.\nRelated Operations\nRemoving External Plugins - Remove external plugins\nExternal Plugins Overview - Understanding external plugins\nOracle Plugin - Oracle configuration details\nAppData Plugin - AppData configuration details","tokens":1482,"crawled_at":1791195337896}
+{"id":10510,"url":"https://docs.sui.io/references/ptb-commands","domain":"docs.sui.io","chapter":"layer1_layer2","title":"PTB Commands | Sui Documentation","text":"The following sections describe each PTBProgrammable transaction blocksDefine all user transactions on Sui. command. Command signatures shown are conceptual MoveMoveAn open source programming language used for all activity on Sui. representations, as these operations cannot always be expressed as standard Move functions.\n\nTransferObjects​\n\nForm: TransferObjects(ObjectArgs, AddressArg)\n\nSends one or more objects to a specified addressAddressA unique, anonymous identity on a blockchain network..\n\nObjectArgs: [Argument]: Vector of objects, any type. Taken by value.\n\nAddressArg: Argument: Target address from Pure input or result. Taken by value.\n\nReturns: Empty result vector.\n\nSignature: (vector<forall T: key + store. T>, address): ()\n\nSplitCoins​\n\nForm: SplitCoins(CoinArg, AmountArgs)\n\nSplits off one or more coins from a single coin.\n\nCoinArg: Argument: Coin of type sui::coin::Coin<T> (any coin type). Taken by mutable reference.\n\nAmountArgs: [Argument]: u64 values for split amounts. Taken by value (copied).\n\nReturns: Vector of coins sui::coin::Coin<T> matching the number of amounts.\n\nSignature: <T: key + store>(coin: &mut sui::coin::Coin<T>, amounts: vector<u64>): vector<sui::coin::Coin<T>>\n\nMergeCoins​\n\nForm: MergeCoins(CoinArg, ToMergeArgs)\n\nMerges multiple coins into a single coin.\n\nCoinArg: Argument: Target coin of type sui::coin::Coin<T> (any coin type). Taken by mutable reference.\n\nToMergeArgs: [Argument]: Coins of type sui::coin::Coin<T> to merge. Taken by value (moved).\n\nReturns: Empty result vector.\n\nSignature: <T: key + store>(coin: &mut sui::coin::Coin<T>, to_merge: vector<sui::coin::Coin<T>>): ()\n\nMakeMoveVec​\n\nForm: MakeMoveVec(VecTypeOption, Args)\n\nCreates a vector (potentially empty) of Move values.\n\nVecTypeOption: Option<TypeTag>: Optional type specifier for elements. Must be specified for non-objectObjectThe basic unit of storage on Sui. types or empty vectors.\n\nArgs: [Argument]: Vector elements (any type). Taken by value (copied if T: copy, moved otherwise).\n\nReturns: Single result of type vector<T>. Elements cannot be accessed individually using NestedResult; use the entire vector or access elements inside Move code through MoveCall.\n\nSignature: (T...): vector<T>\n\nMoveCall​\n\nForm: MoveCall(Package, Module, Function, TypeArgs, Args)\n\nInvokes an entry or public Move function in a published packagePackageSmart contracts on Sui..\n\nPackage: ObjectID: Object ID of the package.\n\nModule: String: ModuleModuleA component of a Move package that defines interaction with on-chain objects. name.\n\nFunction: String: Function name.\n\nTypeArgs: [TypeTag]: Type arguments satisfying the function's type parameters.\n\nArgs: [Argument]: Arguments matching the function's signature.\n\nReturns: Dynamic number of results based on the function signature.\n\nUnlike other commands, argument usage and result count depend on the Move function being called.\n\nPublish​\n\nForm: Publish(ModuleBytes, TransitiveDependencies)\n\nCreates a new package and calls the init function of each module.\n\nModuleBytes: [[u8]]: Bytes of modules being published (each [u8] is one module).\n\nTransitiveDependencies: [ObjectID]: Object IDs of package dependencies for version selection.\n\nReturns: Single result of type sui::package::UpgradeCap for the newly published package.\n\nAfter verification, the init function of each module is called in the same order as the module byte vector.\n\nUpgrade​\n\nForm: Upgrade(ModuleBytes, TransitiveDependencies, Package, UpgradeTicket)\n\nUpgrades an existing package. No init functions are called for upgraded modules.\n\nModuleBytes: [[u8]]: Bytes of upgraded modules.\n\nTransitiveDependencies: [ObjectID]: Object IDs of package dependencies.\n\nPackage: ObjectID: Object ID of the package being upgraded (must exist and be latest version).\n\nUpgradeTicket: sui::package::UpgradeTicket: Upgrade ticket generated from sui::package::UpgradeCap. Taken by value (moved).\n\nReturns: Single result of type sui::package::UpgradeReceipt providing proof of upgrade.\n\nFor more details on upgrades, see Upgrading Packages.\nRelated topics\n\nUpgrading Packages\nUpgrade a published Move package on Sui using the Sui CLI, understand layout-compatibility requirements, manage UpgradeCap and UpgradeTicket, and apply custom upgrade policies to control what changes are permitted.","tokens":1075,"crawled_at":1791195339382}
+{"id":10511,"url":"https://gov.uniswap.org/t/onboarding-package-for-manta-pacific/23442","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Onboarding Package for Manta Pacific - Requests for Comment - Uniswap Governance","text":"Onboarding Package for Manta Pacific\n\nRequests for Comment\n\nGFXlabs\n\nMarch 24, 2024, 7:04pm\n\n1\n\nOnboarding Package for Manta Pacific\n\nTLDR: This proposal adds Manta Pacific to the v3 deployments record and grants Manta an Onboarding Package, which includes $250k of UNI incentives for three months on three key markets and Angle Merkl’s integration of Manta. Separate from this proposal, Manta has arranged for Oku to support Manta, and the contracts have been deployed.\n\nAbout Manta Pacific\n\nManta Network is the modular blockchain for zero-knowledge (ZK) applications. Manta Pacific is the modular L2 ecosystem for EVM-native ZK applications and dApps that want to deliver the lowest cost and best experience for users.\n\nLeveraging Manta’s Universal Circuits to enable ZK-as-a-Service and Celestia’s data availability for modularity to deliver low gas fees, Manta Pacific offers the perfect environment for ZK-enabled applications.\n\nManta Network was created by a team of experienced founders from prestigious institutions, including Harvard, MIT, and Algorand. Manta Network has received investments from many of the top web3 investment funds, including Binance Labs and Polychain Capital. It has grown through participation in the best web3 accelerators, including Alliance DAO and Berkeley Blockchain Xcelerator. Manta is the first Modular L2 with Celestia DA and one of the largest OP Stack chains with zkEVM in its future roadmap. Manta Pacific will achieve data scalability and reduce gas fees by incorporating Celestia’s modular DA.\n\nLearn more about Manta: link\n\nimage1168×373 45.7 KB\n\nToday, Manta’s total value locked is ~$2 billion, which makes it the fourth largest chain Layer 2 by TVL, according to L2beats. Notably, it’s only behind Arbitrum, Optimism, and Blast, ahead of several other modern L2 EVM chains.\n\nDeFi\n\nHaving launched six months ago, Manta has a rapidly growing DeFi ecosystem. The chain’s core DeFi protocol is Layer Bank, a borrow/lend protocol with $390M in TVL. Manta’s top DEX is QuickSwap v3 (an Algebra DEX), which has $9M in TVL and a weekly volume of $25M. Also, the second largest DEX on Manta is Aperture Swap, which is a Uniswap v3 fork with $7M in TVL.\n\nimage792×292 34.3 KB\n\nRoll out plan\n\nWith Manta still in its early stages, Uniswap has the opportunity to grab the majority of its market share without spending considerable capital. We propose directing the requested UNI incentives to the following markets:\n\nWETH/STONE 0.05% - 40%\n\nWETH/USDC 0.05% - 40%\n\nUSDC/USDT 0.01% - 20%\n\nOku has already completed integrating the contracts with its infrastructure. If the proposal passes, we will coordinate with the Manta team, Angle Merkl, and the Accountability Committee to set up the incentives as soon as possible. As of now, we’re shooting to be live the week of April 8th. In the meantime, anyone from the ecosystem who would like the contract details can find them below, or if they want access to the staging deployment for Manta on Oku, they can contact the Oku team.\n\nDeployment Details\n\nGFX Labs deployed the standard Uniswap v3 contracts and the associated peripheral contracts on Manta Pacific. The crosschain account handles the deployment’s ownership via Manta’s messaging system.\n\nv3CoreFactoryAddress: 0x06D830e15081f65923674268121FF57Cc54e4e23\n\nUniversal router: 0x42Bff1f6b647462fcD8c28a488Be9C9988830ef6\n\nnonfungibleTokenPositionManagerAddress: 0xA4F2Db71348697C65A64a146F709C73030C2ebcD\n\nPermit2: 0x83986Ff655A54ee061F6B7F476B92f4Fed111B93\n\nproxyAdminAddress: 0x48f809e2E3c4bc17D74CDb14726F710A86079c75\n\ntickLensAddress: 0xC94Fb2D13587b0b5af78094933490B35E004eAbE\n\nnftDescriptorLibraryAddressV1_3_0: 0xa09dF22EF7c77b10Fd0E60E6B814501dD7edd60c\n\nnonfungibleTokenPositionDescriptorAddressV1_3_0: 0xb17673D9B67330aa7f62206d123661eD729ACB2C\n\ndescriptorProxyAddress: 0xA767CA625981EB0Ff45E19ef443Dc8869ab901BF\n\nv3StakerAddress: 0x9F28881077B8026dE188811D868560aeA981185f\n\nswapRouter02: 0x94AA89D2fAB79D4D2B301848748806f6209D60F1\n\ncrossChainAccount: 0x683553d74D9779955a15d57D208234C956B6Eae6\n\nCost\n\n$250k in UNI for three months of incentives\n\n€20k for Angle Merkl\n\nTwo things are worth noting. First, Oku is not included in the costs of this proposal because Manta already arranged for Oku to deploy and integrate the Uniswap v3 contracts. Second, the Accountability Committee already has more than enough UNI in its possession to cover the potential costs of this proposal, thanks to the recent rise in UNI’s price. If this proposal advances to an onchain vote, it will not include a UNI transfer; instead, the existing funds with the committee will be used.\n\nTimeline\n\nBelow is the proposed timeline for delegates’ consideration. The timeline is an estimate and may be extended during the process as more time is required.\n\nContracts deployed (completed)\n\nRequest for Comment (RFC) ends March 31th\n\nTemperature check April 1st-5th\n\nThe onchain vote review period starts on April 6th\n\nOnchain voting opens on April 8th\n\n5 Likes\n\nparkienator\n\nMarch 25, 2024, 9:43am\n\n2\n\nis Manta matching the incentives to the listed pools?\n\nexisting protocols such as Quickswap seem to be receiving boosted apy from $manta incentives, and it would be nice for Uniswap pools to get some boost to the yield to bootstrap liquidity / awareness\n\n1 Like\n\nkfx\n\nMarch 25, 2024, 11:56am\n\n3\n\nSupport! There is no reason not to incentivize Manta, as opposed to the other chains we have voted to incentivize.\n\nOne potential concern arises again regarding evaluation and follow-up. Let’s say that three months have passed. The Manta chain returns and expresses interest in another round of incentives. What happens then, and how does the DAO assess whether the program has been successful?\n\nDoo_StableLab\n\nMarch 27, 2024, 12:10am\n\n4\n\nI do think those L2s committing resources to also support Uniswap would be beneficial. If there are difficulties, it’s fair for the community to explore different approaches\n\n1 Like\n\njengajojo\n\nMarch 27, 2024, 12:36pm\n\n5\n\nthanks for the proposal @GFXlabs I second the comments made earlier on matching incentives.\n\nI also wonder if there is a maintainence cost associated with this deployment?\n\nBased on your experience with deployments on other networks, do you have any idea on what will be the expected TVL that uniswap can capture from these incentives?\n\nmcd-aperture\n\nMarch 29, 2024, 9:49pm\n\n6\n\nAperture Finance could also transfer the ownership of its UniV3 deployment (called ApertureSwap) to Uniswap.\n\nHaving ownership over this UniV3 deployment is not a priority for Aperture (which is more focussed on using solvers to help LPs).\n\nThis would port over ~$11M in TVL to Uniswap immediately\n\nAperture, while 2nd in TVL, is #1 in volume on Manta due to the superior LP tooling and LP UX (source: Geckoterminal)\n\nThis would also prevent Aperture, which is the primary interface for capital efficient LPs on Manta, from having to support both the Uniswap version and ApertureSwap version of the UniV3 contract.\n\nThis would also prevent liquidity fragmentation\n\nAperture can post a formal submission but we wanted to mention this here first.\n\n5 Likes\n\nGFXlabs\n\nMarch 29, 2024, 10:10pm\n\n7\n\nHi everyone,\n\nThanks for the support thus far. We’re in talks with Manta about matching the incentives and other avenues for Manta to show support in addition to covering Oku’s costs. We should have more information in the coming days.\n\nQuestions\n\nThis proposal, in line with the Uniswap Revitalization and Growth proposal, only addresses getting the new Manta deployment up and running. If, after three months, Manta would like additional incentives, that would need to be in a subsequent proposal. As a delegate, we would judge that proposal by reviewing the effectiveness of the initial incentives requested to indicate the further effectiveness of incentives and consider what incentives Manta would also contribute at that time.\n\nThe maintenance of this deployment is the same as any other. The only difference is that Manta has worked directly with Oku to ensure support rather than asking the DAO to do so.\n\n$250k in allotted UNI to dedicate to kicking off the liquidity incentivization on Manta for 3 months across 3-5 key pools would hopefully garner $5m in liquidity, assuming a reward rate of 20%.\n\n1 Like\n\nwhile1\n\nMarch 29, 2024, 10:39pm\n\n8\n\nAdding more detail to @mcd-aperture’s comments above. The existing deployment of Aperture’s smart contract is a clean fork of Uniswap V3’s. With its current state:\n\nNo.1 Volume on Manta chain (oftentimes twice the volume of QuickSwap, which is the No.1 DEX in TVL on Manta chain).\n\nCumulative of $852M trading volume.\n\nTVL of $11.08M.\n\nAnd Aperture as the leading protocol in Intent & Liquidity management space, it has helped to rebalance $1.3B worth of liquidity for LPs. And it is on track to rebalance more than $5B worth of liquidity annually. This is equivalent to:\n\nrebalance roughly all Ethereum TVL ($2.80B based on DeFiLlama) twice\n\nrebalance all Arbitrum TVL ($287M based on DeFiLlama) 17 times.\n\nIt does not make sense to create another deployment of Uniswap V3 if Aperture is happy with transferring the ownership to Uniswap and working with Uniswap to benefit both Uni stakers and Aperture’s community. As a matter of fact, deploying another Uniswap V3 would further fragment the liquidity and hurt both Manta and Uniswap community.\n\nIn addition, Aperture already has $MANTA grants secured to help attract liquidity. With the introduction of Aperture’s recent points campaign, it would help boost up the liquidity even further.\n\nAll in all, I do not think it makes sense to create another deployment. The collaboration between Uniswap and Aperture would bring way more benefits to all.\n\n3 Likes\n\nUserisky\n\nMarch 29, 2024, 11:10pm\n\n9\n\nSeems like a win-win. This proposal can stay as it is with the exception of deploying new V3 contracts. However it would still require work from OKU: OKU can verify that the existing deployed manta uniswap V3 contracts are a clean fork/deployment, before integrating it into this proposal.\n\nwhile1\n\nMarch 29, 2024, 11:37pm\n\n10\n\nThanks for your thoughts on this.\n\nI don’t think Oku’s work is needed here. Aperture has done audit before going live on Manta, which verified the current deployment is a clean fork of Uniswap V3.\n\nBecause the nature of collaboration here: Aperture is transferring an existing fork with significant TVL & volume to Uniswap DAO, I would imagine there could be other nuances and details to be discussed by the community first before proceeding.\n\nIt may be better to create a different thread with more details from Aperture’s end. For instance:\n\nwhat are the current $MANTA grants allocated to Aperture that is available for liquidity incentive\n\nwhat are the commitments that Aperture is willing to spend for liquidity incentive\n\nwhat would be needed (or great to have) from Uniswap DAO to help bootstrap liquidity even further\n\nwhat are the cost of running and maintaining Uniswap V3 peripheral infrastructure and would there be grants to help offset these\n\netc.\n\nBased on the context above, in my humble opinion, it is a different set of discussion than what the current thread is intended for.\n\n1 Like\n\nGFXlabs\n\nMarch 29, 2024, 11:56pm\n\n11\n\nWe’ll get in touch with the Aperture team and circle back to the forums once we have info to share. Pending review and due diligence, if Aperture is willing to transfer control of the factory contract, it is probably the best path forward.\n\n1 Like\n\nJl_Defiedge\n\nApril 1, 2024, 10:34pm\n\n12\n\nAbsolutely! This proposal seems like a strategic move to incorporate Manta Pacific into Uniswap’s ecosystem. Including Manta’s modular ZK solutions, backed by its impressive TVL and growing DeFi ecosystem, could significantly enhance Uniswap’s scalability and reach. The proposed UNI incentives and integration with Angle Merkl further solidify this partnership, paving the way for mutual growth and innovation.\n\nI look forward to seeing its positive impact on Manta Pacific and Uniswap.\n\nGFXlabs\n\nApril 13, 2024, 12:16am\n\n13\n\nOver the last several days, we have been in touch with the Aperture team, Manta team, and several Uniswap delegates, discussing the opportunity to migrate the ApertureSwap deployment to become an official Uniswap deployment. We appreciate the Aperture team’s contributions to the Uniswap ecosystem and the opportunity extended here. It is the first time such an opportunity has presented itself. Unfortunately, after deliberating and discussing with everyone, we do not believe it is the best path forward for Uniswap to adopt the deployment. Instead, it should stick with precedent and continue the regular deployment process.\n\nGFX Labs would like to thank the delegates who took the time to consider the opportunity.\n\nUpdate: The Temperature Check is live. Voting ends Wednesday evening.\n\nThe following are the proposed pools for the program, but they can be amended for the onchain vote.\n\nETH/STONE 0.05% - 30%\n\nETH/USDC 0.05% - 40%\n\nUSDC/USDT 0.01% - 10%\n\nMANTA/USDC 0.30% - 20%\n\nThe Manta team has committed to providing incentives alongside the Uniswap DAO and plans to solidify their exact plans once this Temperature Check is successful and prior to the onchain vote.\n\nL2BEAT Delegate Platform\n\nSinkas\n\nApril 17, 2024, 1:41pm\n\n14\n\nThe below response reflects the views of L2BEAT’s governance team, composed of @kaereste and @Sinkas, and it’s based on the combined research, fact-checking, and ideation of the two.\n\nWe’re generally supportive of Uniswap deployments on Ethereum L2s and as such we’ll be voting in favor of adding Manta to the v3 deployment records and including an onboarding package.\n\nandelma33\n\nFebruary 27, 2026, 10:44am\n\n15\n\nI am raising this discussion to alert the DAO to the ongoing situation regarding Aperture Finance.\n\nOn January 26, 2026, Aperture Finance suffered a major exploit (approx. $3.6M lost). Security reports (including BlockSec) confirmed the vulnerability was an arbitrary-call capability in their smart contracts, allowing attackers to drain assets using transferFrom calls on existing user approvals.\n\nCurrent Issues for Uniswap LPs:\n\n30+ Days of Ghosting: The Aperture team has been completely silent since the exploit. No post-mortem has been shared, and no recovery plan has been proposed to the users who provided liquidity to Uniswap via their tool.\n\nTornado Cash Activity: On-chain data confirms that the exploited funds (1,200+ ETH) are currently being laundered through Tornado Cash, with no attempt from the team to negotiate with the hacker or secure the remaining funds.\n\nRecent Security Banner: A banner recently appeared on aperture.finance advising users to revoke all approvals. This proves the team still has frontend access but chooses to remain silent regarding the $3.6M loss.\n\nAperture has been a featured partner for Uniswap V3/V4 automation and was part of several ecosystem discussions. To protect the integrity of the Uniswap ecosystem, I propose:\n\nOfficial Warning: Request Uniswap Labs to add a high-risk warning to the Uniswap Interface for any interactions involving Aperture Finance contracts.\n\nAudit Review: We need a community-led review to ensure no other “Intent-based” solvers using similar logic are putting Uniswap LPs at risk.\n\nVC Accountability: We call on ecosystem investors who backed Aperture (such as Binance Labs/YZi, Krypital, etc.) to provide a statement on the status of the project.\n\nUniswap’s strength relies on the safety of its LP ecosystem. We cannot let automated management tools “ghost” the community after a major security failure.\n\n1 Like\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\n[RFC] Deploy Uniswap v3 on Mantle Network\n\nRequests for Comment\n\n1\n\n1064\n\nJuly 3, 2024\n\nUniswap Revitalization and Growth\n\nRequests for Comment\n\n75\n\n10905\n\nJuly 15, 2024\n\nWintermute Delegate Platform\n\nDelegation Pitch\n\n57\n\n8351\n\nMay 25, 2026\n\nKeyrock Delegate Platform\n\nDelegation Pitch\n\n26\n\n5237\n\nMarch 20, 2025\n\nKpk Delegate Platform\n\nDelegation Pitch\n\n64\n\n7501\n\nMarch 2, 2026","tokens":4004,"crawled_at":1791195347031}
+{"id":10512,"url":"https://www.metaplex.com/docs/smart-contracts/core/external-plugins/removing-external-plugins","domain":"www.metaplex.com","chapter":"docs","title":"Removing External Plugins | Metaplex Core","text":"This guide shows how to remove External Plugins from Core Assets and Collections. Remove Oracle or AppData plugins when they're no longer needed.\nWhat You'll Learn\nRemove external plugins from Assets\nRemove external plugins from Collections\nUnderstand authority requirements\nRecover rent from removed plugins\n\nSummary\nRemove external plugins using removePlugin() for Assets or removeCollectionPlugin() for Collections. Only the plugin authority can remove external plugins.\nSpecify the plugin type and base address\nPlugin data is deleted\nRent is recovered\nRequires plugin authority signature\nOut of Scope\nAdding external plugins (see Adding External Plugins), updating plugin data, and removing built-in plugins (see Removing Plugins).\nQuick Start\nJump to: Remove from Asset · Remove from Collection\nIdentify the plugin type and base address to remove\nCall removePlugin() with the plugin key\nPlugin is removed immediately, rent recovered\nRemove from Asset\nRemove External Plugin from Asset\n\nTo remove the External Plugin Adapter from an Asset you'll need to use the removePlugin() function.\nimport {publicKey } from '@metaplex-foundation/umi'\n\nimport { removePlugin, CheckResult } from '@metaplex-foundation/mpl-core'\n\nconst asset = publicKey('1111111111111111111111111111111')\n\nconst oracleAccount = publicKey('2222222222222222222222222222222')\n\nawait removePlugin(umi, {\n\nasset,\n\nplugin: {\n\ntype: 'Oracle',\n\nbaseAddress: oracleAccount,\n\n},\n\n})\n\nRemove from Collection\nRemove External Plugin from Collection\n\nTo remove the External Plugin Adapter from a Collection you'll need to use the removeCollectionPlugin() function.\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { removeCollectionPlugin, CheckResult } from '@metaplex-foundation/mpl-core'\n\nconst collection = publicKey('1111111111111111111111111111111')\n\nconst oracleAccount = publicKey('2222222222222222222222222222222')\n\nremoveCollectionPlugin(umi, {\n\ncollection,\n\nplugin: {\n\ntype: 'Oracle',\n\nbaseAddress: publicKey(oracleAccount),\n\n},\n\n})\n\nCommon Errors\nAuthority mismatch\nOnly the plugin authority can remove external plugins. Verify you're signing with the correct keypair.\nPlugin not found\nNo external plugin with the specified key exists on this Asset/Collection.\nNotes\nRemoving a plugin deletes all its data\nRent is recovered and returned to the payer\nOnly the plugin authority can remove (usually update authority)\nThe external Oracle/AppData account is NOT deleted—only the adapter\nFAQ\nDoes removing an Oracle plugin delete the Oracle account?\nNo. Only the plugin adapter on the Asset is removed. The external Oracle account remains and can be reused.\nCan I recover AppData before removing?\nYes. Read the AppData using fetchAsset() before removing the plugin if you need to preserve the data.\nWhat happens to the rent?\nThe rent from the plugin adapter is recovered and returned to the transaction payer.\nRelated Operations\nAdding External Plugins - Add external plugins\nExternal Plugins Overview - Understanding external plugins\nRemoving Plugins - Remove built-in plugins","tokens":764,"crawled_at":1791195357002}
+{"id":10513,"url":"https://docs.sui.io/references/awesome-sui-gaming","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Awesome Sui Gaming | Sui Documentation","text":"info\nVisit the Awesome Sui Gaming repo on GitHub for the source content of these pages.\n\nI. Core Architecture & Programming​\n\nTechnologyDescriptionVideo Game Utilization\nSui Move Language\nA Rust-based smart contract language focusing on safety, correctness, and asset centricity, designed specifically for Sui's objectObjectThe basic unit of storage on Sui. model.\nEnables highly secure and bug-resistant logic for handling game-critical assets, currencies, and ownership rules.\n\nObject-Centric Model\nAll digital assets, from currencies to player inventories to game state, are represented as independent, first class Objects with globally unique IDs, rather than being stored within contract mappings.\nAllows for dynamic object updates and parallel transactionTransactionA number of commands that execute on inputs to define the result of the transaction. processing (speed) for uncorrelated transactions.\n\nParallel Execution\nSui processes independent transactions (e.g., Player A mints an NFT while Player B transfers an item) simultaneously, using its object centric data model.\nEnsures near instant transaction finalityFinalityThe state in which a transaction is permanently recorded and cannot be revoked. and high throughput (TPS), crucial for real time or fast paced game experiences.\n\nProgrammable Transaction Blocks (PTBs)\nAllows developers to bundle up to 1,024 different smart contract calls into a single, atomic, and safe transaction.\nEnables complex, multi step actions (e.g., \"Use Item A to upgrade Item B, pay a fee, and earn an achievement\") to execute reliably as one single operation.\n\nII. Advanced Trust, Privacy & Data Storage​\n\nTechnologyDescriptionVideo Game Utilization\nNautilus\nA system for confidential, verifiable offchain computation using Trusted Execution Environments (TEEs).\nSecure Game Logic: Hosts hidden or high cost game logic (e.g., fog of war, secret auction bids, complex pathfinding) offchain while providing cryptographic proof of fair execution onchain.\n\nSeal\nA decentralized secrets management service offering robust encryption and onchain access control policies.\nGated Content/Quests: Encrypts mission data, item drops, or exclusive story content, which is only decrypted and revealed to a player upon meeting onchain conditions (e.g., owning a specific NFT or completing a task).\n\nWalrus\nA decentralized storage and data availability protocol optimized for storing large, unstructured data files (\"blobs\").\nDecentralized Game Assets: Stores all large game assets (high resolution NFT imagery, 3D models, rich video trailers, patch files) in a decentralized, tamper proof manner, rather than on a centralized server.\n\nIII. Asset & Economy Features​\n\nTechnologyDescriptionVideo Game Utilization\nDynamic NFTs (Mutable Assets)\nAssets where the metadata and attributes can change on chain over time without needing to mint a new token.\nA character's weapon can level up, a pet can evolve, or armor can gain stats based on in game actions, all reflected immediately on chain.\n\nComposability / Nested Assets\nThe ability for one object to own another object (dynamic fields), creating complex hierarchies.\nA player's Character NFT can hold (own) a Backpack NFT, which in turn holds Item NFTs (weapons, potions).\n\nKiosk\nA decentralized, on chain system for commerce and asset trading.\nProvides a ready made, secure foundation for building in game marketplaces, shops, and peer to peer trading features.\n\nSoulbound Assets\nAssets that are created with a policy preventing their transferTransferChanging the owner of an asset. or sale to another addressAddressA unique, anonymous identity on a blockchain network..\nUsed for non tradeable achievements, story progression markers, quest items, or in game licenses.\n\nSui Object Display Standard\nA standard for defining how on chain assets should be visually represented in different apps and interfaces.\nEnsures a consistent display (image, name, description) for in game items across the game, wallets, and external marketplaces.\n\nDeepBook\nA native, on chain central limit order book (CLOB).\nProvides an efficient foundation for creating stable and liquid in game currency exchanges or token swaps.\n\nIV. User Experience (UX) & Onboarding​\n\nTechnologyDescriptionVideo Game Utilization\nzkLogin (Account Abstraction)\nA Zero Knowledge Proof (ZKP) system that allows users to create and log into a Sui wallet using familiar Web2 credentials (e.g., Google or Facebook).\nRemoves the friction of seed phrases and complex wallet setup, enabling a seamless, Web2 like onboarding process for mainstream gamers.\n\nSponsored Transactions\nThe ability for a developer or a designated entity to pay the gasGasThe computational cost of execution and object storage for a transaction. fees for an end user's transactions (via Enoki or similar services).\nAllows games to be truly \"free to start\" by covering the gas costs for initial players, removing the barrier of buying SUI tokens.\n\nSuiNS / MVR\nSui Name Service (SuiNS) provides a human-readable, decentralized identity (sui.id) that replaces complex wallet addresses. Multi-Venue Resolution (MVR) ensures this single identity is consistently recognized and linked across various applications and smart contracts.\nEnables gamers to use a simple, memorable username (e.g., GamerTag.sui) as their universal profile, friend identifier, and wallet address, creating a seamless and unified digital identity across all Sui-based games.\n\nV. Development Tooling Partnerships​\n\nPartnership/SDKDescriptionVideo Game Utilization\nVenly Gaming SDK\nA comprehensive SDK for Web3 features that integrates with popular game engines like Unreal Engine and Unity.\nSimplifies the implementation of wallet integration, NFT management, and marketplace features directly within existing game development workflows.\n\nBeamable\nA powerful LiveOps and game backend platform that offers a Sui integration in its Marketplace.\nProvides a robust backend environment, enabling developers to build, manage, and scale games with integrated Sui functionality for asset and economy management.\n\nVI. Core Mysten Tools and SDKs​\n\nTool / SDKDescriptionCore Use for Development\nSui CLI\nThe Command-Line Interface client that provides command-level access to the Sui network. It is used for low-level interactions like publishing MoveMoveAn open source programming language used for all activity on Sui. smart contracts, getting object information, executing transactions, and managing addresses.\nEssential for local development, contract deployment, and administrative tasks in a command-line environment.\n\nWalrus CLI / API\nWalrus is an application management platform designed for platform engineering teams to manage application configuration, infrastructure orchestration, and environment setup. The CLI/API allows developers to interact with the Walrus server for these purposes.\nUsed by game services or platform teams to manage the underlying infrastructure and deployment environments, separating concerns from application developers.\n\nSeal TS SDK\nA TypeScript SDK for interacting with the Walrus/Seal platform to manage application resources and configurations.\nAllows game services to programmatically manage their deployment and configuration via TypeScript.\n\nSui TS SDK\nThe core TypeScript SDK (@mysten/sui) providing all the low-level functionality needed to interact with the Sui ecosystem. It offers utility classes and functions for signing transactions and interacting with the Sui JSON RPC API.\nThe primary library for any client or service written in TypeScript/JavaScript that needs to read data or submit transactions to Sui.\n\nBCS TS SDK\nTypeScript SDK for Binary Canonical Serialization (BCS). BCS is the serialization format used to represent the state of the Sui blockchain, guaranteeing a one-to-one correspondence between in-memory values and byte representations.\nUsed for low-level data serialization/deserialization of Move objects, transactions, and events, particularly when building custom tools or working closely with raw transaction data.\n\nDapp Kit TS SDK\nA collection of React hooks, components, and utilities (@mysten/dapp-kit) that make building Sui dApps straightforward. Key features include query hooks for RPC calls, automatic wallet state management, and support for all Sui wallets.\nAccelerates frontend development by providing pre-built components and hooks for wallet connection and querying blockchain data in React-based game clients or web portals.\n\nKiosk TS SDK\nTools for interacting with the Sui KioskKioskA decentralized system for commerce applications on Sui. standard, a decentralized system for commerce applications. Kiosks are shared objects that store assets and allow for listing them for sale while enabling creator-defined transfer policies (like royalty enforcement).\nCrucial for in-game item trading and marketplace integration, ensuring assets are managed securely and creator policies are enforced on-chain.\n\nPayment Kit TS SDK\nThis SDK would simplify the creation and execution of transactions related to sending and receiving tokens (SUI or other assets) within the game.\nSimplifies the implementation of in-game purchases, transfers, and token management flows.\n\nWalrus TS SDK\nThe official toolkit for building web or backend applications in TypeScript that need to interact with Walrus's decentralized storage. It includes tools like the Upload Relay for optimized data uploads and native support for Quilt (for small file efficiency).\nUsed for off-chain data storage (e.g., game assets, user profiles) where reliability, user ownership via their wallet, and optimized uploads are required.\n\nzkSend TS SDK\nThe SDK provides the functionality to create your own zkSend Claim Links. This primitive allows for sending any publicly transferrable asset via a link, leveraging zero-knowledge proofs for simpler transfers.\nEnables streamlined asset distribution and onboarding by letting developers or users send SUI or NFTs with a simple link, simplifying the recipient's claiming process.\n\nEnoki TS SDK\nIntegrates Enoki, an embedded wallet service, into dApps. It allows users to get a Sui address based on their Web 2.0 authentication (e.g., Google, Apple, Twitch), without needing to install a separate crypto wallet.\nDrastically simplifies onboarding by letting users sign in with their Web2 credentials and perform on-chain transactions without managing cryptographic keys.\n\nEnoki Connect TS SDK\nThe connector packagePackageSmart contracts on Sui. that enables a consistent way to handle signing transactions for Enoki wallets using the wallet-standard. It works in conjunction with dapp-kit to allow Enoki wallets to sign and execute transactions.\nConnects Enoki's embedded wallet logic with the standard Sui wallet interfaces, ensuring compatibility with existing dApp tooling.\n\nMove Version Registry (MVR - pronounced “Mover”)\nMove Version Registry (MVR), pronounced \"mover,\" is a uniform naming service. It allows packages and types to be referenced by human-readable names in transactions and development, and also helps manage package versioning.\nImproves developer experience by using names instead of complex addresses and helps manage smart contract upgrades/versions.\n\nNautilus reference\nA framework for secure and verifiable off-chain computation on Sui, enabling developers to delegate sensitive or resource-intensive tasks to a Trusted Execution Environment (TEE) like AWS Nitro Enclaves.\nCritical for complex and private game logic that is too resource-intensive or requires data privacy (e.g., complex AI agents, fraud prevention, secure private computations) while maintaining on-chain verification.\n\nAdditional Notes:​\n\nTo learn more visit:\n\nSui Documentation\n\nGaming on Sui | Sui Documentation\n\nI. Core Architecture & Programming\nII. Advanced Trust, Privacy & Data Storage\nIII. Asset & Economy Features\nIV. User Experience (UX) & Onboarding\nV. Development Tooling Partnerships\nVI. Core Mysten Tools and SDKs\nAdditional Notes:\n\nWas this page helpful?","tokens":3003,"crawled_at":1791195360256}
+{"id":10514,"url":"https://a16zcrypto.com/posts/article/achieving-crypto-privacy-and-regulatory-compliance","domain":"a16zcrypto.com","chapter":"research","title":"Achieving Crypto Privacy and Regulatory Compliance - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nAchieving Crypto Privacy and Regulatory Compliance\nJoseph Burleson, Michele Korver, and Dan Boneh\n11.15.22\n\nTags & Share Tags\ncompliance & illicit finance\npolicy & regulation\nsecurity\nzero knowledge & succinct proof systems\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nEditor’s note: Below is a shorter summary of the paper “Privacy-Protecting Regulatory Solutions Using Zero-Knowledge Proofs” in blog post form. Download the full paper, or read the text here.\n\nThe development and regulation of web3 – an evolution of the internet powered by crypto – must achieve two goals that are often in tension. Goal 1: Preserve consumer privacy, despite the default transparent nature of blockchains. Goal 2: Reduce the risk of illicit finance in the interest of national security. We believe these ends are simultaneously achievable.\n\nWeb3 cannot achieve its full potential unless blockchains support private transactions. If interacting with a blockchain means exposing sensitive financial information, such as salaries, payments for medical treatments, and payments to suppliers, people will be reluctant to use these systems. Ultimately, the question is how to enable people to use privacy-enhancing web3 technologies (good), while discouraging bad actors from abusing those same technologies (bad).\n\nEarly attempts leave the market wanting. The U.S. Department of the Treasury’s Office of Foreign Assets Control’s (OFAC) recent enforcement action against Tornado Cash underscores the predicament. In August, OFAC sanctioned wallet and smart contract addresses associated with Tornado Cash, a popular privacy-preserving service for Ethereum, in response to more than $7 billion worth of virtual currency laundered through the service since 2019. Notably, the laundered transactions included over $455 million stolen by the Lazarus Group, a Democratic People’s Republic of Korea (DPRK) state-sponsored hacking group.\n\nWhile Tornado Cash had some technical controls in place to guard against illicit financial activity, those controls failed to prevent significant volumes of illicit funds from running through the service. As a result, we consider here whether more comprehensive controls could be more effective.\n\nZero knowledge proofs, a cryptographic innovation that enables auditable security without undermining secret-keeping, is one solution to reconcile consumer privacy and regulatory compliance. At its core, a zero-knowledge proof is a way for one party, called a “prover,” to convince another party, a “verifier,” that a certain statement is true, while revealing nothing about the underlying data that makes the statement true. Zero knowledge proofs are powerful tools for preventing the abuse of privacy-preserving web3 protocols.\n\nFurther, a combination of three approaches using zero knowledge proofs may offer better safeguards. First, deposit screening, or checking wallets that are attempting to deposit funds against blocklists and allowlists. Next, withdrawal screening, or checking wallets that are attempting to withdraw funds against blocklists and allowlists. Finally, selective de-anonymization, a feature that would provide federal regulators or law enforcement access to transaction details. While none of these approaches alone is a silver bullet, taken together they may improve the ability to detect, deter, and disrupt illicit financial activity and prevent the use of privacy protocols by sanctioned state actors, all while preserving privacy for good actors.\n\nBelow we offer a high-level overview of the available options. A more comprehensive and in-depth discussion of the regulatory issues at hand and the nuances of each technological approach is available in our full paper, which you can find here.\n\nDeposit screening\n\nThe first approach involves screening wallets to prevent deposits of assets coming from sanctioned entities connected with exploits, hacks, or certain other illicit activity. This could involve government-hosted blocklists as well as on-chain oracle services, or data feeds, provided by blockchain analysis firms. A privacy protocol’s smart contracts would “call” the relevant blocklist contracts before accepting funds into one of its pools, and deposit requests would fail if the funds are from a blocked address. One could also couple this with an “allowlist” approach, making it easier for funds to be deposited from addresses that received funds from regulated financial intermediaries, such as cryptocurrency exchanges, as shown in the graphic below. Deposit screening is a good first step, but is incomplete in isolation, as we discuss more fully in our paper beginning on page 11.\n\nWithdrawal screening\n\nWithdrawal screening is similar to deposit screening, except instead of checking the wallets of inbound funds against blocklists, the cross-referencing happens just before withdrawal. Funds originating from flagged wallets would remain frozen, unable to be withdrawn. Fear of losing proceeds acts as a deterrent to would-be launderers. Withdrawal screening can address some of the shortcomings of deposit screening. For example, since privacy-preserving protocols more effectively anonymize their sources the longer they hold funds, blocklists may be updated during the intervening time period, making it more likely that sanctioned property will be identified and frozen. But, there are challenges associated with both types of screening, as our paper details on page 14.\n\nSelective de-anonymization\n\nSelective de-anonymization is a third approach that could be incorporated in order to address practical challenges associated with privacy-protecting protocols. The method comes in two flavors: voluntary and involuntary.\n\nVoluntary selective de-anonymization\n\nVoluntary selective de-anonymization allows people to reveal the details of transactions to selected or designated parties. The option can be useful for people who believe they were erroneously added to a sanctions list. The method offers a way for them to reclaim frozen funds. But the approach may reduce the effectiveness of withdrawal screening as a deterrent since bad actors could withdraw funds merely by de-anonymizing their transactions. In these scenarios, however, illicit users would receive no benefit at all from having used the privacy-enhancing service. Our paper treats the option in greater depth starting on page 14.\n\nInvoluntary selective de-anonymization\n\nInvoluntary selective de-anonymization is the nuclear option. The approach would provide the government with the ability to track and trace illicit proceeds upon presentation of a valid warrant or court order. The challenges associated with this approach are manifold: Who will maintain the private keys that unlock traceability? How will key-keepers ensure keys can’t be stolen or abused? These questions come up in every discussion of key escrow, which is what involuntary selective de-anonymization is. This solution is perennially unpopular and rife with operational challenges – the idea of a “back door.” Nonetheless, in the interest of comprehensiveness, we present the idea here as an option that may be considered. See page 15 in our paper for a richer discussion of the approach.\n\nConclusion\n\nWhile not opining on the appropriateness of implementing restrictions at the protocol layer of the web3 tech stack, we do believe that mitigating measures could apply at the app or client level of software frontends. Developers should have a full understanding of the available tools that might limit exploitive use by cybercriminals and state actors who threaten national security, thereby exposing such protocols to potential regulatory action, as experienced by Tornado Cash. Taken together, the measures discussed here – deposit screening, withdrawal screening, and selective de-anonymization – could help mitigate national security concerns and protect consumer privacy in web3.\n\nDownload the full paper, or read it here.\n\n***\n\nEditor: Robert Hackett\n\n***\n\nJoseph Burleson is an associate general counsel at a16z crypto, where he advises the firm and its portfolio companies on legal, governance, and decentralization matters.\n\nMichele Korver is the head of regulatory at a16z crypto. She previously served as FinCEN’s Chief Digital Currency Advisor, DOJ’s Digital Currency Counsel, and as an Assistant United States Attorney.\n\nDan Boneh is a senior research advisor at a16z crypto. He is a professor of computer science at Stanford University, where he heads its Applied Cryptography Group; co-directs the Stanford Center for Blockchain Research; and co-directs the Stanford Computer Security Lab.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nCharts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":2846,"crawled_at":1791195370287}
+{"id":10515,"url":"https://docs.ethena.fi/protocol-overview/scenario-analysis","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Scenario Analysis | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nGiven USDe's underlying peg stability mechanism is for the protocol to be long spot assets & short a derivatives position, a common question has been:\n\"How does a change in the price of BTC affect the underlying backing composition?\"\nThis is a great question in that it allows discussion in more detail about the composition of assets in the Ethena backing in different BTC price scenarios.\nOverview\nGiven the protocol utilizes both inverse coin-margined and linear usd-margined contracts as well as trades across multiple exchanges, there are differences in how Ethena settles outstanding PnL. These differences stem from:\n\nEach exchange's contract specifications, margining, and risk systems being subtly different.\n\nInverse coin-margined contracts typically recording & settling PnL in base currency (eg BTC for BTCUSD Perpetual contracts) terms while linear contracts typically recording & settling in USDT (eg for ETHUSDT Perpetual contracts).\n\nThis brings up an important subject of \"unrealized\" and \"realized\" PnL.\n\n\"Unrealized PnL\" refers to when an existing position has incurred a profit or loss (difference between the average position price & the mark price of the contract), but the position has not yet been fully or partially closed. In essence, for example, the position has an outstanding profit/loss denominated in BTC or USDT, but this has not been received or paid from or to the portfolio's collateral balance.\n\n\"Realized PnL\" refers to when a part or all of a position has been closed and has received or paid the PNL to/from the collateral balance.\n\nWhat this means is that Ethena typically receives/pays profit/loss in BTC or USDT depending upon the exchange and margin type of the positions the protocol is trading.\n\nA change in the price of BTC does NOT mean the portfolio is immediately buying/selling collateral to meet unrealized PnL moment by moment.\n\nAs a result, this means that the portfolio at times has balances owed to it or owes in BTC or USDT terms. The ~USD value of the backing assets underpinning the synthetic dollar remains constant.\n\nThe protocol expects to be able to naturally \"realize\" \"unrealized PnL\" by:\n\nClosing existing positions when redeem USDe requests are received.\n\nPeriodically rolling hedging positions between exchanges as it suits the risk & return framework.\n\nScenarios\nBTC Price Decreases\nIn this scenario, the price of BTC decreases from when the positions were opened upon minting USDe. This means the portfolio's derivatives positions have unrealized profits across both inverse coin-margined & linear margined positions. These unrealized profits are denominated in BTC & USDT. Ethena has not sold or reduced the amount of backing assets the protocol is holding.\nThere is no significant drag to the portfolio's yield or risk by holding a small proportion of the portfolio in unrealized BTC or USDT terms.\nBelow are two examples demonstrating the impact of differing price scenarios upon inverse & linear contract margined positions. You'll notice the portfolio is able to either purely hold BTC to margin positions or is able to hold a proportion in the \"Settlement Currency\" (the motivations will be discussed further down).\n\nLinear Margined Positions\n\nInverse Margined Positions\n\nYou'll notice as the price of BTC continues to fall, a greater proportion of the protocol's backing assets value resides in the unrealized profit of the hedging position.\n\nIt's important to keep in mind the portfolio is automatically rebalanced by Ethena and the extreme, edge-case price scenarios are designed to demonstrate if rapid movements were to occur and the Ethena system were not to intervene.\nBTC Price Increases\nIn this scenario, the price of BTC increases from when the positions were opened upon minting USDe. This means the portfolio's derivatives positions have unrealized losses across both inverse/coin-m & linear margined positions. These unrealized losses are denominated in BTC & USDT. Ethena has not sold or reduced the amount of backing assets the protocol is holding.\nThere is no significant drag to the portfolio's yield or risk by holding a small proportion of the portfolio in unrealized ETH or USDT terms.\n\nIt is important to note that the loss on the derivatives positions is perfectly offset by the gain in the value of the spot assets in normal market conditions. The ~USD collateral underpinning USDe generally remains constant in those environments.\n\nOne difference between the price of BTC increasing vs decreasing is that Ethena across many exchanges needs to be able to meet the unrealized loss with the \"Settlement Currency\" asset of the contract. The \"Settlement Currency\" asset of the contract is the asset in which PnL is settled. For example, for BTCUSDT Perpetual positions, PnL is settled in USDT. As such Ethena is able to:\n\nMaintain a balance of the \"Settlement Currency\" in the portfolio to meet this requirement.\n\n\"Borrow\" the balance from the exchange, at a reasonable variable interest rate, until the debt is extinguished (by acquiring the \"Settlement Currency\").\n\nBelow are two examples demonstrating the impact of differing price scenarios upon inverse & linear contract margined positions.\n\nLinear Margined Positions\n\nInverse Margined Positions\n\nYou'll notice as the price of BTC increases, a greater proportion of the protocol backing value resides in the spot Staked Ethereum asset with the unrealized loss in BTC or USDT terms growing.\n\nIt's important to keep in mind the portfolio is actively managed by Ethena & the extreme price scenarios are designed to demonstrate if rapid movements were to occur & Ethena were not to intervene. This is not a realistic assumption in reality.\n\nScenario Consequences to the Portfolio\nAs you'll notice from the scenarios the examples above, there is benefit for the Ethena system to manage the composition of the portfolio as the BTC price changes. This management does not need to occur every 5/10/20% difference in price as the implications are related to economic efficiency rather than stability.\nThe natural mint & redeem USDe flow in combination with automated rebalancing ensures even in the most volatile markets the cost to the portfolio will be minimal & offset by the revenue generated.\nFurther Notes\nGiven Ethena utilizes both inverse/coin & linear margined contracts, a question has been: \"What proportion of the portfolio is in USDT under different rapid price movements?\"\nWith the intention to keep this brief, you'll notice in the image below the scenarios wherein the portfolios has greater USDT exposure.\nGiven the protocol uses both inverse coin-margined contracts as well as linear usd-margined contracts, the proportion very much depends upon how much of the portfolio is hedged with either. As a protocol, we have a firm bias towards using inverse contracts. This is primarily a risk-related decision given it removes the reliance on USDT as well as because of its capital efficiency.\nIt's also important to note that the portfolio is actively managed & when the price of the underlying asset changes significantly, there is a greater likelihood that the positions will have already been rolled to realize the \"unrealized PnL\".\n\nLast updated 1 year ago\nWas this helpful?","tokens":1832,"crawled_at":1791195382901}
+{"id":10516,"url":"https://a16zcrypto.com/posts/tags/compliance-illicit-finance","domain":"a16zcrypto.com","chapter":"research","title":"compliance & illicit finance - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\ncompliance & illicit finance\n\nFeed\nFILTERS\n(1)\nclear filters\n\ncategories\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\n(1) recommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nclear all compliance & illicit finance\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n06.11.25 / Katherine Minarik, Emily Westerhold and Robert Hackett\nDebanking exposed\nImagine waking up one day to find your bank account frozen. No warning. No explanation. No recourse.\nThis is not a thought experiment. It’s a real situation. And it’s happened not just to crypto companies and their founders, but to ordinary people who are just trying to live their lives.\n\npolicy & regulation\ncompliance & illicit finance\ndebanking\nDeFi\n\n10.14.24 / Michele Korver and Jai Ramaswamy\nCrime and crypto: Concrete steps to address money laundering\nHow policymakers can implement measures that will help catching bad actors and reign in illicit financial activity in crypto\n\npolicy & regulation\ncompliance & illicit finance\ngovernment agencies\nop-eds\n\n11.15.22 / Joseph Burleson, Michele Korver and Dan Boneh\nAchieving Crypto Privacy and Regulatory Compliance\nPotential solutions for preserving privacy and mitigating illicit finance in web3 using zero knowledge proof technology for supporting private transactions.\n\npolicy & regulation\ncompliance & illicit finance\nsecurity\nzero knowledge & succinct proof systems\n\n08.18.22 / Michele Korver, Jai Ramaswamy and Sonal Chokshi\nCrypto Regulations, Illicit Finance, Privacy and Beyond\nEPISODE SUMMARY with @michelekorver @jai_ramaswamy @smc90 We tease apart the facts vs buzz around recent news — Tornado Cash sanctions, and arrest of a suspected developer — including what’s novel and what’s not, as well as broader backdrop. But we also share an evergreen explainer that goes well beyond recent events, to help crypto founders...\n\ncompany building\ncompliance & illicit finance\ngovernment agencies\npodcast\nregulatory know-how\nzero knowledge & succinct proof systems\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":1201,"crawled_at":1791195392290}
+{"id":10517,"url":"https://solana.com/podcasts/validated-with-austin-federa","domain":"solana.com","chapter":"developer_specs","title":"Validated | Podcasts | Solana Media","text":"All Podcasts\n\nValidated\nValidated is where the big ideas in web3 get unpacked. Austin Federa sits down with founders, developers, researchers, and ecosystem leaders to talk about the technology, the systems, and the long-term vision behind blockchain — beyond the market noise.\nDeep Technical Dives: From staking and MEV to DeFi protocols — get into the real mechanics of how it all works\nEcosystem Spotlights: How teams are building on Solana and pushing the boundaries of what's possible onchain\nIdeas Over Prices: This show is about technology, innovation, and where things are headed — not trading tips\nBuilders & Thinkers: Hear directly from the people writing the code and shaping the future of web3\n\nHosted by\nAFAustin Federa\n\nSubscribe & Listen\nApple PodcastsSpotifyRSS\n\nNew episodes weekly\n\nLatest Episode\nBuilding the Bitcoin Equivalent for AI Inference Compute with David and Daniil Liberman (Gonka)\n\n0:000:00\n\nAll Episodes(12+)\n45:05\n\nSeptember 22, 2026Building the Bitcoin Equivalent for AI Inference Compute with David and Daniil Liberman (Gonka)\nIn this episode, Austin chats with David and Daniil Liberman of Gonka about the case for using crypto to build a permissionless, meritocratic AI compute network focused on inference rather than decentralized training. They argue that centralized AI infrastructure is rapidly concentrating both revenue and compute, and contrast Bitcoin’s immutable, open rules with corporate systems whose promises can change. With Bitcoin as their north star, Gonka’s protocol aims to verify inference outputs and validate the underlying hardware to guard against fraud, censorship, and model substitution, using proof-of-work-like measurements of real, always-on hardware rather than proof-of-stake incentives.\n\n00:00 - Why Crypto for AI\n03:10 - Inference Over Training\n\n05:02 - Bitcoin as Compute Incentives\n\n07:21 - OpenRouter Critiques\n\n11:36 - Open Source and Safety\n\n18:51 - How Gonka Works\n\n20:14 - Verifiable Inference Proof\n\n24:22 - Privacy and Encryption\n\n29:07 - Decentralized Training Roadmap\n\n34:16 - Keeping Frontier Labs Honest\n\n42:44 - More on Why Bitcoin Provides an Ideal Compute Model\n\n44:23 - Where to Learn More\n\nHosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.\n\n29:36\n\nAugust 25, 2026What are Intents Actually Solving? with Declan Hannon (Aurora Labs)\nIn this episode, Austin chats with Declan from Aurora Labs about building on NEAR’s Intents architecture. Declan explains why intents go beyond “a better bridge UI\" and how Aurora Intents actually work, enabling one-click cross-chain journeys. They discuss how the protocol helps create liquidity, adoption metrics (over $21B lifetime volume, about $1B monthly), and use cases across wallets, neobanks, payments, RWAs, and more. The conversation also explores inherent cross-chain risks, as highlighted by a Litecoin reorg double-spend incident, and the need for insurance-like protections for onchain products.\n0:00 - Aurora Intents Overview\n02:57 - Intents vs Bridges\n05:21- Solver Network Explained\n06:23 - Aurora Intents’ Behind the Scenes Flow\n07:43 - Liquidity and Market Making\n08:55 - Real World Use Cases\n11:25 - Confidential Intents\n16:11 - Intents’ Speed Tradeoffs and Risks\n17:30 - Litecoin Incident Earlier This Year\n19:51 - Liability and Insurance\n26:08 - Future Verticals for Intents\n28:36 - Where to Learn More\n\nHosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.\n\n45:19\n\nAugust 14, 2026OUT OF SCOPE Ep. 2: Anything But Crypto with David Hoffman\nIn this episode, Austin and Tori join David Hoffman (Bankless) to talk about \"anything but crypto.\" Their conversation spans longevity and mind-uploading, the challenges of changing opinions in public, and how modern media incentives distort nuanced ideas. They also discuss social media, the future of long-form content, AI risk and alignment, what it means to “win” the AI race, regulatory uncertainty, and ... yes, David's ideas around fitness.\n00:00 - Welcome and intro\n01:46 - How Do You Want to Live?\n06:17 - Changing Your Mind as a Public Figure\n09:35 - Media Distortion Effects\n14:34 - Quality of Content vs Virality\n16:33 - Yudkowsky and AI Doom\n24:58 - Base Models' Values\n27:55 - China and AI's Moral Core\n30:01 - What Winning the AI Race Means\n36:46 - Why CLARITY Stalled\n41:47 - Hypertrophy and Longevity\n44:23 - Conclusion\n\nHosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.\n\n1:12:03\n\nJune 26, 2026OUT OF SCOPE, Ep. 1: Hot Takes Roundtable with Tori Pastore (Soup) and Austin Campbell (Zero Knowledge)\nAnd now for something (almost) completely different.\nWelcome to Out of Scope, a new sub-series where Austin and Tori Pastore (aka Birb Bernake) riff with guests on hot takes from the frontiers of tech, finance, policy, and whatever else is the flavor of the week In this debut episode, they sit down with Austin Campbell to discuss... quite a few things: running stablecoin reserves, repealing the 17th Amendment, why banks resemble cartels, insider trading, market structure, why regulators should be paid more and held to higher standards, modernizing the BSA, and—most importantly—a definitive ranking of video conferencing tools.\n00:00 - Introducing Tori\n01:24 - Chinese Peptides Explained\n02:45 - GLP 1 Hype Cycle\n05:40 - Peptides and Food Science\n10:49 - Enter Austin Campbell\n16:11- Stablecoin Reserve Rules\n20:35 - Gold Doom Scenarios\n22:59 - Banks' Payment Monopoly\n34:38 - AI Lobbying and EA critiques\n38:20 - Prediction Markets Incentives\n43:59 - Fixing Regulator Accountability\n47:39 - Prediction Markets\n48:47 - Market Manipulation Debate\n59:54 - Perps Versus Futures\n01:02:51 - Assassination Markets Debate\n01:06:21 - Austin's Magic Wand Reforms\n01:10:40 - Blooper Reel\n\nHosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.\n\n44:07\n\nJune 12, 2026Why Crypto Fails without Privacy with Mert Mumtaz (Helius)\nIn this episode, Austin chats with Mert about why privacy is becoming essential for crypto and on-chain finance. They discuss how ZK-based privacy works via shielded pools, commitments, proofs, and nullifiers, contrasting it with Monero’s probabilistic obfuscation. Mert explains Zcash’s renewed adoption through improved usability, macro and regulatory shifts, and fairer historical distribution. He argues privacy layers fail when they lack tangible benefits, and outlines a new fully on-chain, composable, atomic privacy protocol for Solana built with Light Protocol’s compression approach, including permissionless and enterprise “zones” with configurable compliance features and reduced MEV via encrypted swaps.\n00:00 - Why Privacy Matters\n03:05 - Zcash And ZK Origins\n06:26 - How Shielded Pools Work\n09:56 - Why Zcash Broke Out\n15:52 - Why Privacy Layers Fail\n19:47 - Solana Privacy Protocol\n22:57 - Composability Breakthrough\n25:51 - Go-To-Market Plan\n30:50 - Compliance And Zones\n32:40 - Onchain Versus Off Chain\n34:58 - Zcash And Solana’s Future\n40:29 - Bitcoin Privacy And Quantum\n43:48 - Closing And Where To Find\n\nHosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.\n\n42:59\n\nJune 2, 2026Why Privacy Tech Is Having Its Moment with Seth for Privacy (Cake Wallet)\nIn this episode, Austin chats with Seth (Cake Wallet) about why privacy is gaining traction after years of being niche, tracing Seth’s entry through Monero and other privacy-preserving products. They compare Zcash’s seemingly influencer-driven pump with Monero’s quieter but rising real-world usage, discuss Cake Wallet’s UX-driven approach (including enforced auto-shielding for Zcash), and debate how criminal adoption can actually validate that privacy tools work in adversarial settings while emphasizing legitimate use cases and storytelling. They explore why app-layer privacy on major L1s has weak adoption versus privacy-native L1s, the importance of defaults, and what’s next for privacy in DeFi and stablecoins.\n00:00 - Seth’s Personal and Professional Privacy Journey\n05:53 - Zcash vs Monero Adoption\n09:51 - Crime Compliance and Privacy Ethics\n15:25 - Why Privacy-Preserving Wallet UX Has Lagged\n20:49 - Privacy L1s vs. App-Layer Privacy\n27:30 - What’s Next Private DeFi\n30:07 - Why Monero Has Survived CEX Delistings\n32:35 - Privacy in the Age of AI Surveillance\n41:51 - Conclusion\n\nHosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.\n\n44:44\n\nMay 5, 2026Solana Mobile's Vision Beyond Seeker with Emmett Hollyer (Solana Mobile)\nIn this episode, Austin chats with Emmett Hollyer about the evolution and future of Solana Mobile. They reflect on how the successes and missteps of the Saga phone informed the more refined Seeker, with a focus on improvements in design, pricing, and usability. Emmett discusses scaling production to meet over 100,000 preorders, strategies for attracting developers, and the rationale behind launching a token to align incentives across the ecosystem. The conversation also explores plans to expand beyond in-house devices through partnerships with Android manufacturers, positioning Solana Mobile as a broader crypto platform rather than just a hardware company.\n\nHosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.\n\n42:09\n\nApril 21, 2026Crypto's Market Making Arms Race with Rahul Jain (Ellipsis Labs)\nIn this episode, Austin chats with Rahul Jain (Head of Trading at Ellipsis Labs) to explore the evolution of market making in crypto. Rahul discusses what gives crypto market makers an edge, why being early matters, and how crypto has created new challenges around MEV, transaction landing, and execution. They explore the future prospects of prop AMMs, perps, MCP, and what it will take for on-chain finance to scale beyond crypto-native users and compete with traditional markets.\n\nHosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.\n\n1:12:26\n\nApril 11, 2026The Constellation Debate Part 2, with Brennan Watt (Anza)\nIn this episode, Austin sits down with Brennan to unpack Constellation, Solana’s latest market structure proposal, and what it could mean for the network’s future. The conversation centers on Brennan’s perspective on why Solana’s current leader-based design creates challenges around transaction ordering, predictability, and censorship resistance, and how Constellation aims to address those issues through a new multi-proposer framework. They explore the trade-offs between latency, complexity, and fairness, debate whether the proposal strikes the right balance for traders and validators, and discuss how it fits into Solana’s broader roadmap.\n\nHosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.\n\n1:26:49\n\nApril 9, 2026The Constellation Debate, Part 1 with Ben Coverston (Temporal)\nIn this first part in a series of debates on Constellation (Anza's MCP proposal), Austin chats with Ben from Temporal. The conversation focuses on Ben’s measured critical perspective, highlighting his concerns around the proposal’s trade-offs, including added complexity, potential unintended effects on market structure, and whether alternative approaches could achieve similar gains in censorship resistance and throughput. They dig into the proposal’s underlying motivation, debate whether current limitations in Solana’s architecture are being correctly diagnosed, and explore what these design decisions could mean for the next generation of on-chain trading and market infrastructure.\n\nHosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.\n\n52:28\n\nMarch 24, 2026MegaETH Mainnet and the Real-Time ZK Endgame w/ Lei Yang\nIn this episode, we sit down with the team behind MegaETH to discuss the launch of their mainnet and the vision for a new generation of high-performance Layer 2 blockchains. We explore how MegaETH is pushing block times into the millisecond range, what that means for onchain markets, and why ultra-low latency could fundamentally change blockspace auctions and transaction ordering. The conversation also covers token utility, sequencer incentives, fraud proof security, and why the long-term endgame for rollups is real-time ZK proving. We also dive into the practical challenges of building high-performance crypto infrastructure — from co-location and distributed RPC networks to designing an ecosystem that can actually take advantage of that speed.\n\nTo learn more about MegaETH, check out:\nhttps://www.megaeth.com/\nhttps://rabbithole.megaeth.com/\n\nHosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.\n\n36:58\n\nMarch 6, 2026How Shelby Makes Decentralized Storage Faster and Cheaper w/ Pranav Raval\nIn this episode, Austin chats with Pranav Raval (Aptos Labs) about Shelby, a new decentralized storage protocol designed to address the performance and cost limitations of earlier decentralized storage systems. The conversation dives into Shelby’s architecture and market opportunities. Unlike previous systems that rely on unreliable “spare capacity” nodes, Shelby uses professionally operated data centers, erasure coding for reliability, and incentives for fast data retrieval. This design enables new use cases beyond simple file storage, including verifiable advertising analytics, IP-protected generative media, AI data marketplaces, and distributed AI inference at the network edge. Pranav explains how Shelby can position itself as infrastructure for data-intensive applications—especially those driven by AI—while offering an alternative to the expensive egress fees and regional data silos of traditional cloud providers.\n\nHosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.","tokens":3604,"crawled_at":1791195393381}
+{"id":10518,"url":"https://blog.trailofbits.com/2026/09/25/dont-let-tees-break-your-mpc","domain":"blog.trailofbits.com","chapter":"security_audits","title":"Don't let TEEs break your MPC - The Trail of Bits Blog","text":"Page content\n\nThreshold signature schemes, a form of multi-party computation (MPC) that lets a set of parties sign together without any one of them holding the key, are increasingly deployed inside trusted execution environments (TEEs). The combination is intended to amplify security for sensitive computations: MPC distributes trust across multiple independent parties, while TEEs root trust in the hardware manufacturer and its attestation infrastructure. But subtle issues can arise when running an MPC protocol inside a TEE without accounting for the untrusted host: for example, a malicious host could roll back the filesystem state after a threshold signer deletes a used pre-signature, causing the signer to reuse their nonce share and disclose their private key share.\nSo is this combination worth it? Provided you treat the TEE as a defense-in-depth layer rather than a substitute for a sound protocol, the answer is yes. This blog post discusses what TEE attestation can and can’t fix in MPC deployments, explores the pitfalls we see most often in audits, and covers best practices, such as incorporating strong attestation processes and binding them to the MPC parties’ identities.\nMPC: Security that depends on participant behavior\nBefore diving into how TEEs and MPC interact, we need to understand what MPC means and what security guarantees it offers. MPC is a cryptographic technique that allows multiple parties to jointly compute a function over their private inputs without revealing those inputs to each other.\nThe security of MPC protocols depends critically on assumptions about participant behavior. The cryptographic literature uses two primary security models:\nSemi-honest (honest-but-curious) security: In this model, all participants follow the protocol exactly as specified, but they may try to learn additional information from the messages they receive during the protocol execution. Participants can try to learn more than they should, but they don’t deviate from the protocol specification.\nMalicious security: This stronger model assumes participants may deviate arbitrarily from the protocol. A malicious participant might send incorrectly computed values, use wrong inputs, abort the protocol at strategic moments, and behave in ways designed to compromise security or learn private information.\nThis distinction is important in the context of TEEs. If a TEE attestation can cryptographically guarantee that all parties are running the correct protocol implementation, it effectively elevates semi-honest protocols to provide malicious security guarantees (at least against certain classes of attacks, as we’ll discuss later). But before delving into the details, let’s discuss how TEEs work.\nTEEs: Three core security guarantees\nTEEs are secure areas within a processor that provide hardware-based protection for code and data, even from privileged software like operating systems or hypervisors. TEEs offer three core security guarantees:\nConfidentiality: Data and code are encrypted in memory and accessible only from within the TEE. This ensures that even privileged system software cannot inspect the contents of the secure computation.\nIntegrity: The data and code are protected from tampering. Any attempt to modify the TEE’s memory or execution state from outside should be detected.\nAttestation: Remote parties can cryptographically verify what code is running in the TEE. This allows external verifiers to gain assurance about the computation being performed and the legitimacy of the TEE without trusting the host system.\nThis last property is particularly crucial for building distributed systems with TEEs.\nHow TEE attestation works\nThe attestation mechanism is at the heart of TEE security. When a TEE is manufactured, it’s provisioned with a private key and a corresponding certificate that chains back to a root certificate held by a trust anchor (typically the manufacturer).\nWhen an attestation is requested, the TEE takes measurements (cryptographic hashes of the TEE software, configuration, and hardware state). These measurements are bundled into a “quote” (a manifest of these cryptographic hashes), which the TEE then signs with its private key.\nTo verify these attestations, a number of checks need to be performed. However, the checks necessary in the verification process aren’t uniformly defined and are somewhat vendor-specific. For instance, Intel’s TDX documentation states:\nTD Quote Verification is the process by which a TD Quote is verified in a remote attestation flow. This verification can be done by any party and the checks performed are defined by this party.\n\nThis places significant responsibility on developers, who might not fully understand what checks are required to ensure the security of the TEE deployment.\nAt a minimum, a proper verification process requires:\nVerifying the quote signature\nVerifying the certificate chain back to the trusted root\nVerifying the actual measurements against known-good values (often stored in binary transparency logs)\nThis means deploying TEE-based systems involves not just cryptographic verification but also reproducible builds and binary transparency infrastructure. The measurements in the attestation quote are simply hashes; they don’t inherently indicate whether the code is correct or malicious. To verify that the TEE is running the intended software, what is required is a trusted source of reference measurements. Reproducible builds ensure that anyone can compile the same source code and arrive at identical binaries (and thus identical measurements). Binary transparency logs provide a tamper-evident record of what measurements correspond to what software versions, allowing verifiers to check that the TEE is running legitimate, audited code rather than a compromised variant. This piece is often overlooked in TEE deployments.\nThe trust model clash\nHere’s where things get interesting. Multi-party computation is fundamentally about distributing trust among multiple participants. No single party should be able to compromise the computation. TEEs, in contrast, centralize trust in the hardware manufacturer that controls the root certificate.\nAnother important threat model shift to consider is the fundamental inversion of traditional security assumptions in TEEs. Historically, we trusted the host operating system and built our security models on that foundation. TEEs flip this on its head: they’re virtualized environments where the guest (the code running inside the TEE) is trusted, but the host system is explicitly considered untrusted and potentially malicious.\nThis shift creates new attack surfaces that didn’t exist in traditional computing models. While the TEE protects the guest environment from the host, the host still controls critical operations like I/O, memory management, and CPU scheduling. The host can deny service, manipulate timing, or attempt rollback attacks, leading to subtle breaks of MPC protocols.\n\nFigure 1: Decentralized vs. centralized trust model shift\nWhat TEEs can (and can’t) fix in MPC deployments\nCombining these technologies can be beneficial, but one must be careful about the security claims that can be made. The security gains are real only if the TEE implementation is sound and the attestation process verifies the right properties. When TEEs attest to incomplete measurements or fail to verify critical components, the attestation provides false assurance. The actual security posture may even be weakened by the added complexity.\nIn an attempt to narrow down what TEEs can fix in MPC implementations, we’ve identified the common categories of MPC issues we frequently encounter in security audits:\nAmbiguous encoding in hash functions (e.g., “YOLO” is not a valid hash construction)\nMisbehaving participants\nMissing parameters in Fiat-Shamir transforms (e.g., Coordinated disclosure of vulnerabilities affecting Girault, Bulletproofs, and PlonK)\nMissing input validation (e.g., Breaking the shared key in threshold signature schemes)\nSide-channel attacks\nProtocol-level issues (e.g., Friends don’t let friends reuse IVs)\nArguably, if TEEs were perfectly secure, they could effectively mitigate the first four categories. When attestation and measurement processes are correctly implemented, each party gains cryptographic assurance about what code the other parties are running. This is powerful: if a party can verify that all other participants are running the exact protocol implementation expected (with no modifications or protocol deviations), then they know other participants will follow the protocol correctly and won’t misbehave by sending malformed messages. Essentially, correct attestation eliminates entire classes of implementation vulnerabilities by ensuring protocol compliance on both the sender and receiver sides. However, perfect security doesn’t exist in practice. Real-world TEE implementations have vulnerabilities, attestation processes can be incomplete or incorrectly verified, and the adversarial host environment introduces attack surfaces that are not traditional to MPC deployments.\nA cautionary tale: Rollback attacks with threshold signatures in TEEs\nConsider threshold signature schemes, which often use pre-signature optimizations. In Schnorr or ECDSA threshold signatures, participants can precompute nonce commitments independently of the message, speeding up the online signing phase. These precomputed nonce commitments are called pre-signatures, and the reuse of a pre-signature value by a participant leads to the leak of their private share (akin to how nonce reuse in traditional Schnorr and ECDSA signatures leads to private key recovery).\nIt might be tempting to run such an MPC protocol inside a TEE enclave to mitigate these types of attacks. But subtle issues can arise. In some implementations, signers store pre-signatures to disk and delete them after use (to limit the possibility of reuse). If that application were deployed to a TEE in a trust model where the host is potentially malicious, the host could roll back the filesystem state after the signer deletes a pre-signature file. When the TEE later fetches the pre-signature contained in that file, the signer essentially reuses their nonce share, which leads to a disclosure of the private key share. This is also discussed in the blog post A trail of flipping bits.\nCommon TEE pitfalls\nBeyond the rollback issue, several other pitfalls frequently appear:\nIncomplete attestation measurements: The security of TEE attestation hinges on measuring the right things. An attestation quote contains hashes of code and data, but project developers determine what gets measured and what gets excluded. If critical components aren’t included in the measurements, an attacker can modify those components without detection. This is particularly risky because the attestation appears cryptographically valid, but it’s attesting to an incomplete picture of the execution environment. For example, installing tools in an enclave from remote sources at runtime (e.g., using curl) pulls in code that was never measured; an attacker gaining access to that source can substitute their own and gain code execution inside the enclave.\nA real-world example demonstrates this risk: a vulnerability in Meta’s WhatsApp Private Inference revealed that the attestation process didn’t include certain configuration files, enabling an attacker to inject malicious shared libraries with the LD_PRELOAD environment variable, potentially compromising the TEE while maintaining a valid attestation quote.\nMissing verifications: The attestation process requires multiple verification steps, each critical to the security guarantee. Verifiers must check the quote signature, validate the certificate chain back to the manufacturer’s root certificate, confirm that the measurements match expected values, etc. Skipping any of these steps breaks the security model. Because verification procedures vary across TEE vendors and aren’t always well-documented, implementations sometimes omit crucial checks.\nLack of hardening: A TEE protects whatever runs inside it, including components that may not be needed. Redundant kernel drivers, overly permissive kernel config flags, stray ACPI table entries, unnecessary systemd services and timers, and weak entropy sources all increase the attack surface inside the trust boundary. Trim the image down to what the project requires, harden what remains, and measure it. For platform-specific guidance, see our notes on the AWS Nitro Enclaves attack surface.\nData availability and backups: Enclaves have limited persistent storage, so backups and recovery data typically live outside the trust boundary. Authenticated encryption provides confidentiality and integrity but not freshness, so a malicious host can serve a stale backup to force a rollback, as discussed earlier in our threshold signature example. More concretely, one recurring failure is a guest trusting attacker-controlled metadata that lives on disk: the disclosure of several vulnerabilities in LUKS2 disk encryption for confidential VMs shows that a malleable, unvalidated LUKS2 header lets an attacker with disk write access swap in a null cipher, leaving the guest reading and writing secrets on an effectively unencrypted volume.\nSide-channel and physical attacks: Because the untrusted host controls the TEE’s execution environment, it can perform various side-channel attacks to extract information about the guest’s computation. These can leak sensitive information and break a TEE’s confidentiality guarantees. Similarly, researchers regularly publish physical attacks on TEE hardware. For example, the recent “TEE fail” attack allows an attacker to break the security guarantees of Intel TDX and AMD SEV-SNP by using a memory interposition device that lets them physically inspect all memory traffic inside a DDR5 server. The more recent DDRop attack goes even further: an interposer costing under $200 silently drops DDR5 writes, so the processor keeps reading stale data that still decrypts correctly, breaking the integrity of Intel TDX, Scalable SGX, and AMD SEV-SNP. Memory encryption without freshness fails the same way disk state does in the rollback example above.\nCentralization risks: When MPC aims to distribute trust but TEEs centralize it in the manufacturer and its attestation infrastructure, the security goals of the protocol may be undermined. If all parties in an MPC protocol run their TEE nodes on the same TEE vendor’s hardware or if they use the same cloud provider, trust becomes centralized in that provider (for example, by way of the attestation chaining back to that vendor-operated root of trust).\nInsecure defaults: Be aware of some of the limitations that vendor-provided verification tools have. For example, Intel tools allow known-vulnerable firmware versions to pass the remote attestation process for one year after public disclosure. Users might want to implement their own security version number validation on top of the defaults to enforce stricter deadlines.\nBest practices for combining TEEs and MPC\nIf you’re building systems that combine these technologies, consider these recommendations:\nImplement strong attestation processes: Bind attestations to the identities of MPC parties and verify them comprehensively. This means not just checking that an attestation is valid but also confirming that the specific party you expect to be running the code is actually the one presenting the attestation.\nTerminate peer-to-peer communications inside TEEs: This provides end-to-end protection for party communications. By establishing TLS or other encrypted channels directly between TEEs (with endpoints inside the secure enclaves), you prevent the untrusted host from observing or tampering with protocol messages.\nPerform comprehensive verification of the attestation and measurements: Refer to your specific TEE vendor’s documentation for the necessary checks to be performed, and ensure every verification step is implemented correctly, tested, and reviewed.\nWrite constant-time code: This helps prevent timing side-channel attacks. Even within a TEE, timing variations in your cryptographic operations can leak information to a host performing careful measurements. Use constant-time implementations for all security-critical operations processing secrets.\nConsult vendor-specific guidance: Each TEE platform has unique characteristics, limitations, and recommended practices. Vendor documentation often includes details about platform-specific threats. Stay current with security advisories and updates, as TEE security is an active research area with new vulnerabilities regularly discovered. Follow best practices documentation, like our guidance for AWS Nitro Enclaves.\nUse multiple TEE vendors: For defense in depth, consider running MPC protocols on TEEs from different manufacturers (and/or cloud providers) to avoid centralizing trust in a single vendor. While admittedly challenging in practice since it requires additional operational complexity, this diversity can be essential for high-security applications where trust distribution is critical.\nLayered trust beats either layer alone\nCombining MPC and TEEs is not automatic security, but when done correctly, it represents a defense-in-depth strategy that’s stronger than either technology alone. TEEs can effectively mitigate several categories of MPC vulnerabilities by cryptographically guaranteeing correct protocol execution. Meanwhile, MPC’s distributed trust model reduces the impact of TEE manufacturer centralization and may provide security even if individual TEE instances are compromised.\nHowever, this benefit only materializes when both layers are correctly implemented. New vulnerabilities can emerge from their interaction, as we saw with the rollback attack example. Successful deployment requires following established best practices, implementing thorough attestation verification, and carefully reviewing the implementation and deployment procedure.\nThe intersection of these technologies represents the cutting edge of secure computation, but only if we approach it with a clear understanding of the tradeoffs involved. If you’re deploying MPC on TEEs, our cryptography team reviews these exact systems, so get in touch!","tokens":4582,"crawled_at":1791195403827}
+{"id":10519,"url":"https://docs.ethena.fi/technical-design/minting-usde","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Minting USDe | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\n\"Minting\" USDe refers to the creation of new synthetic dollars. \"Redeeming\" USDe is the reversal process, of exchanging synthetic dollars for the assets that collateralize them.\nThe methods of minting vary depending on the type of stablecoin/synthetic dollar. Here we will explore the novel Ethena synthetic dollar minting process.\n\nThe Ethena synthetic dollar minting system encompasses the following design principles:\n\nHow does it work?\n\nUsers request a price from the Ethena Pricing API.\n\nUsers can generate a signed EIP712 order and optionally submit it to Ethena's minting server.\n\nNote: at this stage, users have complete control over their assets - they have the freedom to create, hold, and sign the price at their discretion. The approval to transfer assets only happens when the user willingly signs the order.\n\nOnce the signed order is received, Ethena's server checks that the user has the required asset balance and signed approvals and that the dynamic hedging server can currently handle the order. Part of this involves communicating with the OES solution to prepare for the incoming mint or redemption request.\n\nNote: Ethena does have the ability to reject an order based on these conditions. However, even in this centralized part of the process, the protocol could never alter the contents of the signed order due to the immutability of blockchain cryptographic signatures. This design ensures that the user's order - the backing asset, its size, any included slippage, and the synthetic dollars to be minted - remains as the user intended.\n\nThe order is sent to the blockchain with the atomic mint function called when these checks are passed. As above both the transfer of the user's assets and the minted synthetic dollars happen in a single transaction.\n\nUpon success the hedging system actions the mint events to ensure the delta neutrality of the protocol's overall backing. Read more about these concepts in the Hedging SystemandBacking Asset Custodysections.\n\nBy blending centralized and decentralized elements in this way, Ethena achieves a relatively high level of trustlessness. Users always retain control over their assets prior to mint and their orders will be processed exactly as specified. And while Ethena has some control over order acceptance, the blockchain's transparency and cryptographic guarantees mean users can confidently engage with the protocol, knowing their transactions are secure and unalterable.\nSlippage\nSlippage occurs when the price at which a trade is executed differs from the expected price, usually due to market volatility or trade size.\nEthena has designed its minting process to minimize slippage for users. Before submitting a minting transaction, users receive a \"price\" from the Ethena Pricing API that includes a predefined slippage range. The user then signs this price, confirming their acceptance of the potential variation within the specified range.\nWhen the transaction is executed, the smart contract logic ensures that the final minting settlement price falls within the signed slippage range. This approach provides users with a level of certainty about the price they will receive and makes the transaction predictable.\nSlippage management is a key part of Ethena's minting design strategy, aiming to provide users with a more stable and transparent transaction experience.\nAudit\nThe Ethena Minting Contracts are regularly audited. See the section for up-to-date information.\n\nQuick Answers\nQ: Am I only able to get USDe via minting USDe with Ethena?\nNo, you can acquire USDe initially via decentralized protocols such as Curve and Uniswap as well as buy & sell USDe on Centralized Exchanges such as Binance, OKX and Bybit.\n\nLast updated 1 year ago\nWas this helpful?","tokens":960,"crawled_at":1791195403841}
+{"id":10520,"url":"https://a16zcrypto.com/posts/article/privacy-protecting-regulatory-solutions-using-zero-knowledge-proofs-full-paper","domain":"a16zcrypto.com","chapter":"research","title":"Privacy-Protecting Regulatory Solutions - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nPrivacy-Protecting Regulatory Solutions Using Zero-Knowledge Proofs: Full Paper\nJoseph Burleson, Michele Korver, and Dan Boneh\n11.15.22\n\nTABLE OF CONTENTS\nIntroduction Introduction\nBackground\nApplicable Regulatory Regimes\nKYC Standards and Transaction Monitoring\nSanctions\nOptimizing Privacy Protocols to Mitigate Illicit Finance Risk\nThe Tornado Cash Example\nDeposit Screening\nWithdrawal Screening\nSelective De-anonymization\nConclusion\nEndnotes\nTags\nmental models & frameworks\npolicy & regulation\nsecurity\nzero knowledge & succinct proof systems\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nEditor’s note: Below is the full text of the paper “Privacy-Protecting Regulatory Solutions Using Zero-Knowledge Proofs”. Download the PDF, or read the shorter summary blog post here.\n\nIntroduction\n\nOf all the utility that programmable blockchains offer – security, predictability, interoperability, and autonomous economies, among others – as of today, the most widely used blockchains do not offer privacy. This remains a key impediment to their widespread adoption. Although not all crypto tokens are solely – or even principally – financial instruments, and can be used for a variety of purposes within the growing web3 ecosystem, blockchain users do transact with each other on blockchains using digital assets. The current architectures of most existing blockchains rely on transaction transparency to promote trust, but this default transparency and lack of privacy increases the risk of consumer harm by permitting other blockchain users to view the transaction history and holdings of any wallet holder. The pseudonymity characteristic of blockchains is the principal protection against bad actors, but it is easily overcome. Modern blockchain analytics practices have shown that heuristic analysis of user interactions can be used to pierce this privacy, and anyone who transacts with a wallet holder can effectively see their entire financial profile. Consequently, although it provides a net benefit in tracing illicit financial activity, transaction transparency makes users of blockchain technologies particularly vulnerable to fraud, social engineering, and theft of assets by bad actors, as well as the inchoate harm caused by revealing sensitive financial data to third parties.\n\nThe transparent nature of public ledgers on blockchains stands in stark contrast to the default privacy of the traditional financial system, which arises from the recording of transactions on private ledgers maintained by financial intermediaries, supported by statutory rights to financial privacy and human controls on access to sensitive financial information. Indeed, regulations and guidance promulgated by the Department of the Treasury’s (Treasury) Office of Foreign Assets Control (OFAC), responsible for the U.S. financial sanctions regime, and the Financial Crimes Enforcement Network (FinCEN), responsible for U.S. anti-money laundering regulations and supervision, along with their enabling statutes, have been designed to compel transparency to overcome the inherent opacity of the traditional financial system and the privacy it affords. The recordkeeping and reporting requirements arising from these statutes require financial intermediaries to maintain and disclose information to the government (as well as take other actions such as blocking access to assets) in order to support law enforcement investigations, stop terrorist financing, and advance national security policies, among other things. Importantly, these measures create exceptions to protected privacy rights and represent a balance – albeit an imperfect one – between privacy rights and compliance requirements.\n\nNone of these protections – neither the practical privacy protections afforded by the inherent opacity of private ledgers, nor the explicit legal recognition of rights to financial privacy – exists with respect to users on public blockchains. Moreover, attempts to import measures (such as customer identification and due diligence, colloquially known as “know your customer” or “KYC” requirements) risk undermining even the minimum levels of privacy afforded by pseudonymity, by creating “honeypots” of information that attract malicious attacks and insider threats. While compromise of such information causes consumer harm in the traditional financial system, it dangerously exacerbates the already heightened risk of theft, fraud, and even physical harm that exists as a result of full financial transparency.\n\nWhile there are newer, more narrowly adopted layer-1 blockchains that primarily focus on privacy, for those blockchains that are not inherently private, users have to rely on a host of smart contract protocols and layer-2 blockchains that anonymize transaction data, many of which use zero-knowledge proofs, privacy-preserving cryptographic techniques, to achieve anonymity. These protocols and blockchains have commonly been derided as having solely nefarious purposes (including by being labeled “mixers”), and while it is irrefutable that a portion of their volume has ties to hacks and other illicit purposes,1 there is undeniable value in advancing privacy-preserving technology for lawful purposes. In fact, such technologies could permit legitimate consumers to benefit from a level of financial privacy and consumer protection beyond what is enjoyed by consumers of traditional financial services. The same solutions that maximize privacy, however, may frustrate the government’s ability to pursue investigations, combat illicit financial activity, or recover stolen assets in furtherance of law enforcement and national security goals. Does this mean that blockchain technology necessarily forces a choice between compliance to detect, prevent, and disrupt illicit financial activity, on the one hand, and privacy and consumer protection on the other hand?\n\nThis paper argues emphatically that the answer is no. Resolution of this tension using modern cryptographic techniques – unlike existing frameworks that rely on human controls – is not necessarily a zero-sum game. Reconciling the privacy needs of users and the informational and national security needs of regulators and law enforcement is both possible and necessary. This paper proposes potential use cases for zero-knowledge proofs in blockchain protocols that can achieve both sets of goals. First, we describe the basics of zero-knowledge proof technology, followed by an overview of relevant legal and regulatory regimes that may apply. Then, using Tornado Cash as an example, we lay out a number of high-level solutions that developers and policymakers might consider.\n\nIn writing this, the authors affirm the important premise, “regulate apps, not protocols.”2 In the United States, it’s common practice for the application layer to perform sanctions screening using geo-fencing techniques and restricting user access through a variety of measures. While these restrictions are helpful, they are not fail-safe, and bad actors may nonetheless circumvent such controls. As a result, certain privacy-preserving technologies that may be susceptible to use by sanctioned parties have chosen to include restrictions at the protocol level to address national security concerns. The authors don’t take the stance that all privacy-preserving technologies should make the same decision; developers should have the freedom to choose whether or not they want to adopt protocol-level restrictions to protect against use by illicit actors and potential regulatory liability. For those that choose to adopt protections, we simply offer up potential alternatives to consider which may make these solutions more effective, while also limiting the potential for them to be used for censorship.\n\nBackground\n\nAchieving Privacy Using Zero-Knowledge Proofs\n\nIt is unlikely that blockchain technology will achieve mainstream adoption without ensuring privacy. For example, when it comes to financial infrastructure, potential users of blockchain-based payments systems may be highly reluctant to use these systems if their salaries or other sensitive financial information, including payments for services such as medical treatments, are publicly viewable. The same can be said for social networking services, decentralized lending protocols, philanthropic platforms, and any other use case where users value the privacy of their information.\n\nThe data corroborates that position. The 30-day moving average of cryptocurrency market value received by on-chain privacy-preserving services or protocols reached $52 million as of April 29, 2022, up nearly 200% over the preceding 12 months.3 For context, many privacy-preserving protocols use algorithmic cryptography to facilitate one blockchain address depositing digital assets into a pool of similar fungible assets, followed by another blockchain address controlled by the same user withdrawing the same number and type of assets from that pool, effectively breaking the chain of custody and inhibiting the traceability of transactions. Certain of those protocols and some layer-2 blockchains use algorithms known as zero-knowledge proofs to anonymize transactions without exposing sensitive user information to the chain.\n\nZero-knowledge proofs enable private transactions on a public blockchain. At its core, a zero-knowledge proof is a way for one party, called a “prover,” to convince another party, a “verifier,” that a certain statement is true, while revealing nothing about the underlying data that makes the statement true. For example, the prover can prove knowledge of the solution to a Sudoku puzzle without revealing anything about the solution. More interestingly, a person can prove they are old enough to buy alcohol or vote, without revealing the name and date of birth printed on their driver’s license. (Technically, they would prove in zero knowledge that they have government-signed documents, and that their date of birth on these documents establish the requisite age of the person.) The proof convinces the verifier that this fact is true, without revealing any other information.4\n\nOne can build a variety of privacy mechanisms using zero knowledge tools. For instance, Alice can send funds to a service that keeps transaction details private, and the service gives Alice a receipt for her deposit. The service, as well as the public, learns that Alice sent funds. At a later time, when Alice wants to withdraw the funds from the service, she constructs a zero-knowledge proof that she has a valid receipt, and that she has not yet withdrawn the funds associated with that receipt. The proof reveals nothing about Alice’s identity, but convinces the service that it is interacting with someone who is eligible to withdraw those funds. Here, the zero-knowledge proof is used to convince the service that the withdrawal claim is valid, while keeping the identity of the withdrawer private.\n\nCritically, zero-knowledge proofs protect privacy by permitting selective disclosure of the information necessary to assess policy compliance, without exposing all of the underlying information. Zero-knowledge proofs can enable varying degrees of privacy, including complete privacy where no one can track a transaction, or privacy from everyone except for a few specific parties. While there are a number of lawful reasons why people may need strong privacy protection, these technologies can also be a magnet for bad actors. Just as overall usage of privacy-preserving protocols peaked in 2022, so did the relative proportion of value received from illicit sources, with illicit blockchain addresses accounting for approximately 23% of all funds sent to such protocols this year through Q2. Nearly all of that illicit activity originated from sanctioned entities or consisted of stolen funds.5 Despite the privacy-preserving technology utilized by these protocols, blockchain analytics firms, like Chainalysis and TRM Labs, are sometimes able to track illicit funds flowing through these protocols where they do not have sufficient volumes to mask the activity, or where the volumes they do have are not sufficiently diverse.6 Further, even when illicit actors exploit privacy-protecting technology, they still face challenges taking their assets off-chain, as fiat on-ramps and off-ramps are in most instances considered financial institutions in major financial centers and other jurisdictions across the globe, and thus subject to AML/CFT requirements.7 However, implementation and enforcement of these requirements globally is uneven at best, and non-existent in some jurisdictions, offering a favorable climate for illicit actors to exchange digital assets for fiat currency. As a result, although privacy-preserving protocols are critical to keeping legitimate user information private, they do create vulnerabilities within blockchain ecosystems for illicit actors to exploit. Compliance with international legal and regulatory regimes is complex, to be sure, but a standardized and regulatory-compliant implementation of zero-knowledge proofs in decentralized blockchain protocols can address some key vulnerabilities while at the same time benefitting web3 participants.\n\nApplicable Regulatory Regimes\n\nUnderstanding how zero-knowledge proofs can overcome the apparent binary choice between compliance and privacy requires an appreciation of the particular jurisdictional regulatory requirements that relate to combating illicit financial activity. In the U.S., regulations most likely to affect privacy-preserving protocols can be categorized into two primary legal regimes: (A) under the series of federal statutes and regulations commonly known as the Bank Secrecy Act (BSA) – (i) Customer identification program and customer due diligence requirements (commonly referred to as “Know Your Customer” or “KYC” standards) and (ii) transaction monitoring as well as other recordkeeping and reporting requirements;8 and (B) under Presidential wartime and national emergency powers – U.S. sanctions programs.9 Web3 market participants must address the legal requirements of both regimes in order to minimize any risk of enforcement for non-compliance and to mitigate against the illicit use of protocols and platforms. Further, any failure to comply may result in severe consequences, including civil penalties and criminal prosecution.10\n\nThe BSA requires certain financial institutions and other related entities to comply with a number of monitoring, recordkeeping, and reporting obligations. The purpose of these obligations is to assist FinCEN, OFAC, and law enforcement agencies with the identification, prevention, and prosecution of money laundering, terrorist financing, and fraud activity, as well as the identification and blocking of assets in the U.S. financial system belonging to sanctioned parties pursuant to national security and foreign policy goals. Full compliance under the BSA and sanctions regimes create a clear and auditable paper trail of illicit activity for regulators and law enforcement to follow and is critical to their successful enforcement.11\n\nBSA-covered or obliged entities include traditional financial institutions such as banks, as well as money services businesses (MSBs) such as currency dealers, exchangers, and money transmitters, among others.12 FinCEN has further clarified that individuals and entities which issue, administer, or exchange Convertible Virtual Currency (CVC), or value that substitutes for currency, are considered MSBs as well, and therefore subject to all of the applicable compliance obligations under the BSA.13 Depending on the facts and circumstances of a mixing service’s operation or business model, a mixer could be deemed an MSB and subject to the registration and compliance requirements of the BSA. This is because certain mixing services can enable value that substitutes for currency to move from wallets within the platform to wallets outside of the platform.14 In contrast, privacy-preserving decentralized blockchains likely do not involve money transmission. As FinCEN explicitly states in its most recent guidance, issued in 2019, non-custodial, self-executing code or software alone, even if performing mixing functions, will not at present trigger BSA obligations:\n\nAn anonymizing software provider is not a money transmitter. FinCEN regulations exempt from the definition of money transmitter those persons providing “the delivery, communication, or network access services used by a money transmitter to support money transmission services.” [31 CFR § 1010.100(ff)(5)(ii)]. This is because suppliers of tools (communications, hardware, or software) that may be utilized in money transmission, like anonymizing software, are engaged in trade and not money transmission.15\n\nThe application of sanctions compliance requirements is a bit less clear. The sanctions regimes administered by OFAC apply to all U.S. persons, both individuals and entities, wherever they reside, and require them to identify, block, and segregate transactions involving property of sanctioned parties. Although OFAC has stated that sanctions regimes do not apply to the publication of software and privacy-preserving technologies per se,16 the failure to implement measures to prevent sanctioned parties from abusing these technologies – as discussed in further detail below – risks responses from OFAC that could undermine such technologies’ viability, such as recently was the case with Tornado Cash.17\n\nKYC Standards and Transaction Monitoring\n\nThose individuals or entities whose business models are classified as MSBs must fulfill certain information collection and transaction monitoring requirements in order to meet their obligations under the BSA. MSBs are required to obtain KYC information from persons that use their services to conduct transactions, in order to verify the identity of such persons.18 At a minimum, MSBs must obtain a user’s name, address, and tax identification number as part of the KYC process.19\n\nPost-onboarding, MSBs must also monitor transactions conducted through their platforms and report any suspicious activity that might signal illegal conduct by filing Suspicious Activity Reports (SARs). The BSA requires MSBs to file a SAR within 30 days if they know of or suspect that a transaction on their platform may involve illegal activity, provided that such transaction involves the transfer of at least $2,000 in the aggregate. In order to incentivize timely filing, the proper filing of a SAR with respect to a transaction will shield the MSB from all civil liability related to that transaction.20\n\nWhile the BSA also imposes other recordkeeping and reporting requirements on MSBs such as the filing of Currency Transaction Reports (CTR) , this requirement currently does not apply to digital assets and is not immediately relevant for present purposes.21\n\nSanctions\n\nFinCEN has full authority to administer the BSA, promulgate rules thereunder, and bring enforcement actions against those in violation of the BSA, but OFAC has a much broader jurisdictional mandate. Most economic sanctions come from authority delegated to the President in the International Emergency Economic Powers Act (IEEPA) and the National Emergencies Act (NEA).22 Thus, sanctions are a wartime and national security-related power enacted via Executive Order. OFAC oversees all financial transactions in the U.S. and may sanction any individual, entity, or country that poses a threat to national security. As a result, if an OFAC-designated person or entity has an interest in any transaction processed through or property held by any U.S. person or entity, including but not limited to BSA-obliged entities such as MSBs and banks, the U.S. person or entity would be required to (i) block (freeze) the prohibited transaction, and any accounts or property related to the specified person, and/or (ii) place any funds received in connection with such transaction into a segregated, blocked account, and (iii) file certain reports with OFAC. In either case, no U.S. person or entity may process such transaction and/or release such funds until OFAC removes the individual or entity in question from the sanctions list, the applicable sanctions program is rescinded, or OFAC explicitly authorizes the release of withheld funds through the granting of a license.23\n\nFor sanctions relating to cryptocurrency transactions, the authority generally comes from EO 13694 which focused on “significant malicious cyber-enabled activities.”24 Individuals who violate economic sanctions may face civil or criminal penalties.25 It should be noted that the administrative, or civil, liability standard for sanctions violations is strict liability, meaning that one can be held liable for sending or receiving a transaction or failing to block property associated with a sanctioned person, entity, or country, even if there was no intention to do so.26 This effectively imposes a due diligence requirement to inquire as to the source of funds when engaging in financial or business activities. Criminal liability, on the other hand, requires a showing of willfulness – that the person violating sanctions meant to do so. Criminal prosecutions for sanctions violations are brought by the Department of Justice under IEEPA or money laundering statutes codified in Title 18 of the U.S. Code.27 The important takeaway, however, regarding sanctions liability and OFAC compliance requirements is that these obligations apply to all persons and entities in the U.S. or doing business in the U.S. and are not tied to whether or not the person or entity is BSA covered.\n\nOptimizing Privacy Protocols to Mitigate Illicit Finance Risk\n\nThe potential for privacy enhancements afforded by zero-knowledge proofs stands in tension with the aforementioned regulatory framework. The technology’s ability to shield transaction details means it may not readily lend itself to fulsome compliance with regulations such as BSA requirements – though it remains an open question whether and to what extent smart contracts and code are subject to the requirements under the regulations described. As mentioned above, in its 2019 guidance, FinCEN explicitly exempts software code from the BSA’s scope, and thus a truly decentralized protocol with no individual or group behind its operation is not required to – nor is it even clear how it could – collect and retain KYC information or file SARs on users. Similarly, the enabling statutes and cybersecurity executive order which would govern the imposition of any sanctions refers to “property and interests in property” of targeted individuals and entities, which suggests that software and computer code is itself outside the scope of sanctions.28 And recent guidance from OFACseems to indicate that publication of software is not itself a sanctionable activity.29 However, in light of OFAC’s designation of certain smart contract addresses associated with Tornado Cash, this conclusion is far from clear.\n\nNevertheless, zero-knowledge proofs can be designed to mitigate some risks of exposure to illicit financial activity and economic sanctions liability through privacy-enhancing protocols, including mitigation of the very national security risks that OFAC sanctions seek to address. In particular, there are several measures that privacy-focused protocols could implement to better manage these risks, without undermining their effectiveness. Three feasible measures are summarized below, each of which is evaluated in the context of the privacy-protecting protocol Tornado Cash.\n\nThe Tornado Cash Example\n\nOne way of demonstrating the potential for zero-knowledge proofs to overcome the current binary choice between potential liability under existing sanctions regimes raised by privacy-enhancing technologies is through the lens of Tornado Cash – the privacy-enhancing protocol recently sanctioned by OFAC. Tornado Cash is a protocol deployed on the Ethereum blockchain that seeks to anonymize user assets in order to protect their privacy. Anyone could send funds from their Ethereum address to the Tornado Cash smart contracts, and those funds would remain deposited in the contracts until the owner chose to withdraw them. Typically, users would wait anywhere from several weeks, to months, or even years before withdrawing, as the intervening time period (during which other users deposit and withdraw funds) can increase or decrease the effectiveness of Tornado Cash’s privacy-preserving features. Upon withdrawal, the protocol utilized zero-knowledge proof technology to transfer the funds to a new Ethereum address, breaking the link between the address from which the funds were initially deposited into Tornado and the new address to which the funds were later withdrawn from Tornado.30 The Tornado Cash protocol is immutable, trustless, and fully-automated.31 The anonymity provided by Tornado Cash depended upon multiple users simultaneously employing the service to break the connection between wallet addresses used for deposits and withdrawals. In addition, users maintained a certificate that only they could reveal which proved ownership of the deposited tokens. Consistent with the recent uptick in illicit mixer usage, the Tornado Cash platform was similarly and frequently used to launder stolen funds. For example, in the hack of the Ronin bridge in April 2022, approximately $600 million was stolen from the bridge and transferred to an Ethereum address owned by the attacker. A few days later, the hackers moved some of the stolen funds into Tornado Cash.32 On August 8, 2022, OFAC designated, among other things, the website tornado.cash and several Ethereum addresses associated with the service, many of which were smart contract addresses without an identifiable key holder.33 In the public announcement accompanying the designation, Treasury pointed to over $7 billion in illicit proceeds laundered through Tornado Cash, including $455 million laundered by the North Korean state-sponsored hacking syndicate known as the Lazarus Group, and significant sums associated with the Harmony Bridge34 and Nomad Heists.35 Although users engaged in a significant amount of legitimate transaction activity through Tornado Cash, Treasury made the choice to take action against the protocol and its smart contracts despite considerable collateral impacts on innocent third parties, including preventing non-sanctioned individuals from withdrawing fully legitimate funds deposited using the protocol. This issue arises from the decentralized and non-custodial nature of Tornado Cash, which makes it difficult to identify an organization or individual responsible for its activities. As a result, applying traditional sanctions enforcement techniques and blocking property interests in this context can pose technical legal challenges. Although such protocols are sometimes cast solely as attempts to circumvent regulatory requirements, from a cybersecurity perspective, the technical architecture of Tornado Cash can also represent the robust privacy-preserving technology necessary to deter unauthorized third parties and malicious actors from obtaining sensitive information of individuals and businesses who operate on-chain. This approach is preferred and may be technologically far superior to the traditional operational controls restricting access to information that more centralized custodial systems impose, and that have proven increasingly vulnerable to malicious attacks and insider threats.\n\nIn its press release accompanying the OFAC designation, Treasury indicated that “[d]espite public assurances otherwise, Tornado Cash has repeatedly failed to impose effective controls designed to stop it from laundering funds for malicious cyber actors . . . .”36 In fact, and as described in more detail below, Tornado Cash did have some technical controls in place to guard against the platform’s use for illicit financial activity. The question is – were there more effective technical controls, such as ones leveraging zero-knowledge proofs, that Tornado Cash could have implemented and that would have persuaded Treasury not to take the actions that it did? Let’s consider those zero-knowledge proof solutions, including some which Tornado Cash implemented, and others that might improve effectiveness. While none of these approaches alone is a silver bullet, taken together they may improve the ability to detect, deter, and disrupt illicit financial activity and the use of privacy protocols by sanctioned state actors. These are: (i) deposit screening – checking wallets making inbound transactions against blocklists and allowlists; (ii) withdrawal screening – checking wallets that are requesting returned funds against blocklists and allowlists; and (iii) selective de-anonymization – a feature that would provide federal regulators and law enforcement with access to transaction information.\n\nDeposit Screening\n\nDigital assets native to the Ethereum blockchain or bridged onto it from another chain can be swapped for ETH and deposited in Tornado Cash in an attempt to preserve the privacy of users’ transactions. To prevent deposits of assets coming from sanctioned persons or wallets connected with exploits or hacks, Tornado Cash used deposit screening that relied on a “blocklist” of designated addresses. The additional use of an “allowlist,” however, could be used to address national security concerns while also minimizing risks to lawful users of the protocol, as further outlined below.\n\nBlocklisting\n\nTornado Cash’s deposit screening enabled it to restrict automatically who can use the protocol by blocking any proposed deposits from addresses that are sanctioned or otherwise blocked by the U.S. government. Tornado Cash accomplished this by utilizing a blockchain analysis firm’s on-chain oracle service for testing whether an address is currently designated on economic or trade embargo lists (or “blocklists”) from various entities, including the U.S., E.U., or U.N.37 Tornado Cash’s smart contracts would “call” the analytics firm’s contract before accepting funds into one of its pools.38 A deposit request would fail if the funds are from one of the blocked addresses included on the analytic firm’s Specially Designated Nationals (SDN) list.\n\nWhile deposit screening using blocklists is a good first step, there are several practical problems with this mechanism. First, when cybercriminals steal funds from a victim, they can immediately move the funds into Tornado Cash before the victim even realizes that the funds are gone, and certainly before an analytics firm has flagged the funds as stolen or on the SDN list in their software. Second, in the event that the cybercriminal’s address is placed on the SDN list prior to depositing in Tornado Cash, the thief could simply transfer the funds to a new address, and immediately deposit the funds into Tornado Cash from that new address, before the new address is added to the sanctions list. Sophisticated hacking syndicates, like the DPRK’s Lazarus Group, use these techniques quite effectively to avoid detection. But, blockchain analytics firms attempt to overcome this limitation by using change address analysis and heuristics to identify non-designated wallets that are also controlled by designated groups.39 Lastly, relying on a non-governmental entity as the arbiter of truth with respect to who or what is on a sanctions list could result in accuracy issues that would be difficult to identify and rectify. For instance, an analytics firm could mistakenly include an address on its blocklist, and it is unclear whether the owner of such an address would have any recourse to have the mistake fixed (unlike in the case of traditional financial institutions which can field complaints from their customers). There is also the problem of which sanctions list gets added, since all sanctions represent policy decisions of the issuing government.\n\nAllowlisting\n\nIn order to reduce the risk that an analytics firm or government entity could use blocklisting to unfairly censor law-abiding users, privacy-preserving protocols might consider a more robust form of deposit screening that also relies on an “allowlist” of wallet addresses to which deposit screening restrictions would not apply. That allowlist would consist of wallet addresses associated with regulated financial intermediaries – such as fiat on-ramps like Coinbase – that conduct comprehensive KYC screening as part of their onboarding processes, thereby obviating the need for the privacy-preserving protocol to screen those addresses, as depicted below.\n\nThis approach would allow a user to deposit funds in a privacy-protecting protocol only if the deposit address (i) is not on the applicable analytics firm’s SDN list (i.e., the address is not on a blocklist) or (ii) received said funds from a regulated financial intermediary (i.e., the address is on the allowlist). That allowlist could be managed and updated over time by the decentralized autonomous organization (DAO) that controls the protocol or could be sourced from an on-chain oracle of addresses associated with regulated financial intermediaries (similar to the blocklist oracle operated by Chainalysis). Certain privacy-preserving technologies could take this concept a step further by bridging their protocol directly to regulated financial intermediaries, allowing users to deposit funds directly from those intermediaries into the protocol, without needing to transfer the funds to a separate wallet address first.\n\nUtilizing both a blocklist and an allowlist as part of the deposit screening process has several distinct advantages over a blocklist-only approach. First, a lawful user that is either erroneously or maliciously added to a blocklist would be able to avoid censorship so long as they utilized a regulated financial intermediary to deposit their funds into the protocol. And since most unlawful actors should not be able to establish an account with a regulated financial intermediary, they could not take advantage of the allowlist and would remain subject to censorship, thereby addressing national security concerns. Additionally, an allowlist approach would improve privacy for the customers of all regulated financial intermediaries, as it would guarantee their ability to enjoy the benefits of privacy-preserving protocols without fear of censorship.\n\nUltimately, while deposit screening would facilitate Tornado Cash’s obligations to block prohibited transactions, for other privacy service providers that may be deemed an MSB and subject to the BSA, or for individuals or entities that may be required to perform a sanctions-related risk assessment of business activities, it would not improve those entities’ transaction monitoring capabilities for risk assessment purposes.40 Deposit screening is a good first step, but it is unlikely to reduce illicit finance use of the protocol completely.\n\nWithdrawal Screening\n\nFor those wallet addresses that aren’t included on an allowlist as outlined above, one additional approach to deposit screening would be to check the oracles on withdrawal and block any proposed withdrawals by sanctioned addresses or addresses that have been identified as associated with illegal activity. For example, suppose an illicit actor sends funds to Tornado Cash from an address immediately following a hack. At the time of the deposit, the address is not on the allowlist and has not been identified as being associated with stolen funds or sanctioned individuals or entities, and the deposit is successfully completed. However, if the illicit actor attempts to withdraw the funds at a later time, and during the intervening time period the address is flagged as being associated with stolen funds or on a sanctions list, then the withdrawal request will fail. The funds will remain frozen, and the thief will not be able to withdraw them. This approach has multiple benefits. First, it prevents the thief from laundering the funds with the Tornado Cash protocol. Second, Tornado Cash’s implementation of a withdrawal checkpoint acts as a deterrent and should make it clear to nefarious actors that if they send stolen funds to Tornado Cash, those funds could be frozen by the smart contracts indefinitely, preventing them from accessing the fruits of their illicit activity. Such a deterrent would only affect cybercriminals and not impact law-abiding users of Tornado Cash. Indeed, given the deposit time period characteristic discussed above, and the likelihood that illicit actors would park funds in Tornado Cash for longer time periods in order to most effectively anonymize their source, this withdrawal screening feature would be very useful in its ability to screen against continually updating Treasury sanctions lists.\n\nAlthough withdrawal screening can address many of the shortcomings of deposit screening, like deposit screening it does little to address any necessary risk assessments.41 In addition, it would perpetuate Tornado Cash’s reliance on blockchain analytics firms’ faithful operation of sanctions oracles. Further, as with deposit screening, there is also the problem of government censorship – only in the case of withdrawal screening, a government’s misuse of the sanctions list could result in a user losing its funds.\n\nSelective De-anonymization\n\nSelective de-anonymization is a third approach to meeting potential regulatory requirements, and it comes in two flavors: voluntary and involuntary.\n\nVoluntary Selective De-anonymization\n\nThrough its deposit receipt function, Tornado Cash implemented a form of voluntary selective de-anonymization, which provides a person who believes that they were erroneously added to a sanctions list the option to de-anonymize the details of their transaction to selected or designated parties.42 If a similar voluntary de-anonymization function was instead coupled with withdrawal screening of wallet addresses not on an allowlist, a user could opt to de-anonymize their transaction, and the Tornado contract responsible for withdrawals would remove any block in place as a result of the withdrawal screening process described above. As a result, a user would receive its funds, but the user would not have received the benefits of Tornado’s privacy-preserving technology, as its withdrawal address would clearly be linked on-chain to its deposit address. Voluntary de-anonymization would enable protocols like Tornado Cash to address certain shortcomings of withdrawal screening (e.g., innocent users would not be at risk of getting their funds frozen), but it would also reduce the effectiveness of withdrawal screening as a deterrent because bad actors would then be able to withdraw their funds from Tornado by merely de-anonymizing their transaction. In that scenario, illicit users would receive no benefit at all from having used the privacy-enhancing service.\n\nInvoluntary Selective De-anonymization\n\nInvoluntary selective de-anonymization is an additional measure that could be integrated into Tornado Cash’s smart contracts to provide the government with the ability to track and trace illicit proceeds. While the applicability of BSA requirements to non-custodial web3 services is not likely, the traceability associated with blockchain protocols represents one key control to preventing illicit financial activity more broadly, including by sanctioned parties. Involuntary selective de-anonymization represents a powerful tool for maintaining traceability for authorized purposes while protecting privacy against malicious actors and unauthorized third parties. The key question is, who maintains the private key to unlock traceability?\n\nOne solution may involve providing a private key to a neutral gatekeeper-type organization or similar trusted entity, and another private key to government authorities. Both keys would need to be used to de-anonymize a deposit-and-withdrawal transaction that did not originate from a wallet address on the allowlist, and the details of such a transaction would only be revealed to the law enforcement agency that requested such de-anonymization. The role of the gatekeeper organization would be to resist de-anonymization without law enforcement first obtaining and presenting a valid warrant or court order for the de-anonymization. This would not only enable law enforcement to identify the source address that provided the funds used for any Tornado Cash withdrawal, thereby allowing the government to carry out its enforcement and national security mandate, but it would also alleviate the government from the burden of holding the keys, which would be suboptimal for both the government and Tornado Cash’s users.\n\nThere are several challenges associated with this approach. First, it is not clear which entities would have access to the private keys. No known gatekeeper organization in operation today is set up to manage such a process. Further, there are numerous jurisdictional issues. Will every country – even repressive regimes – have its own private keys, providing them access to transaction data? If so, how does one ensure that such regimes do not de-anonymize transactions of U.S. citizens? Also, how would the gatekeeper organization and government authorities manage their keys to ensure that they cannot be stolen? These questions are not new. They come up in every discussion of key escrow, which is what involuntary selective de-anonymization is. This solution is perennially unpopular and rife with operational challenges – the idea of a “back door.” It is nonetheless an option that developers could consider in order to satisfy regulatory requirements or to mitigate against the use of platforms for illicit purposes.\n\nOne possible solution to the foregoing challenges would be to allow a user, during withdrawal, to choose which public key they want to use to encrypt the address.43 The Tornado Cash contract might have multiple law enforcement public keys, say one public key for each country. During withdrawal, the user can choose which public key to encrypt with based on its local jurisdiction. The user may need to provide evidence of its jurisdiction, and that would determine which public key it uses for encryption. That evidence could be hidden under the zero-knowledge proof, so that no one other than the relevant government agency will learn the jurisdiction of the withdrawal.44 In theory, this would address the issue of repressive regimes having access to a transaction’s secret key, but it does not address the possibility that a malicious government could require the keyholders to provide their private keys under the guise of a bona fide – but bad faith – legal process.\n\nFor those BSA-obligated entities, selective de-anonymization would have the benefit of retaining the regulatory feasibility of withdrawal screening, including the ability to conduct OFAC-mandated sanctions screening, as well as the ability to collect KYC information and transaction data, and potentially file SARs. Moreover, the involuntary selective de-anonymization method outlined above could be modified such that the two keyholders would only have private keys for information specifically required to be collected, retained, and reported under the BSA (e.g., KYC information and SARs), and could only present those keys to FinCEN and OFAC, or to law enforcement upon service of valid legal process. That approach would help to ensure the privacy of users’ data, while allowing government agencies to meet their regulatory mandates.\n\nConclusion\n\nIn order for web3 technologies to flourish in the United States, the development of privacy-protecting regulatory solutions is crucial. In formulating these approaches, zero-knowledge proofs can supply a powerful tool for keeping cybercriminals and adversarial state actors from using blockchain technology for illicit purposes while still protecting the privacy of users’ personal information, data, and financial activities. Depending on the operational and economic model and regulatory compliance obligations for a given protocol or platform, use of zero-knowledge proofs could enable deposit screening, withdrawal screening, and selective de-anonymization to meet those obligations and better protect the ecosystem from illicit use and prevent harm to the security of the U.S. and other nations. The diversity of activity in the blockchain space may require developers and founders to consider multiple approaches, including those posed in this paper, in addressing illicit finance risk.\n\nReiterating the previously discussed principle that protocols should not be regulated and that developers must have total freedom to choose whether or not they want to adopt protocol-level restrictions to alleviate these important risks, it is the authors’ hope that these ideas will spark creative discussion, further research, and development around the possibilities of zero-knowledge proofs among builders and policymakers alike.\n\nDownload the full paper, or read the summary blog post here.\n\n***\n\nEndnotes\n\n1 See Crypto Mixer Usage Reaches All-time Highs in 2022, With Nation State Actors and Cybercriminals Contributing Significant Volume, Chainalysis (July 14, 2022), https://blog.chainalysis.com/reports/cryptocurrency-mixers; see also U.S. Treasury Sanctions Widely Used Crypto Mixer Tornado Cash, TRM Labs (Aug. 8, 2022), https://www.trmlabs.com/post/u-s-treasury-sanctions-widely-used-crypto-mixer-tornado-cash.\n\n2 Miles Jennings, Regulate web3 Apps, Not Protocols, a16z Crypto (Sept. 29, 2022), https://a16zcrypto.com/web3-regulation-apps-not-protocols/.\n\n3 See Chainalysis, supra note 1.\n\n4 The way a prover accomplishes this is by first encoding the statement to be proved as a series of polynomials (the sum of a series of algebraic terms) that are identically zero if and only if the statement is true. This encoding – often called the “arithmetization” of the statement – is the magical step that makes zero-knowledge proofs possible. The prover then convinces the verifier that the polynomials are indeed identically zero.\n\n5 See Chainalysis, supra note 1.\n\n6 See North Korea’s Lazarus Group moves funds through Tornado Cash, TRM Labs (Apr. 28, 2022), https://www.trmlabs.com/post/north-koreas-lazarus-group-moves-funds-through-tornado-cash.\n\n7 “AML” is anti-money laundering, and “CFT” is countering the financing of terrorism. See Fin. Crimes Enf’t Network, History of Anti-Money Laundering Laws, https://www.fincen.gov/history-anti-money-laundering-laws.\n\n8 31 U.S.C. § 5311 et seq.\n\n9 See U.S. Dep’t of the Treasury, Office of Foreign Assets Control (OFAC) – Sanctions Program and Information, https://home.treasury.gov/policy-issues/office-of-foreign-assets-control-sanctions-programs-and-information.\n\n10 For example, in 2021, the alleged operator of Bitcoin Fog, a mixing service, was arrested and charged with money laundering, operating an unlicensed money transmitting business, and money transmission without a license in the District of Columbia. See Press Release, U.S. Dep’t of Justice, Individual Arrested and Charged with Operating Notorious Darknet Cryptocurrency “Mixer” (Apr. 28, 2021), https://www.justice.gov/opa/pr/individual-arrested-and-charged-operating-notorious-darknet-cryptocurrency-mixer.\n\n11 31 U.S.C. § 5311.\n\n12 Definitions Relating to, and Registration of, Money Services Businesses, 64 Fed. Reg. 45438 (Aug. 1999), https://www.govinfo.gov/content/pkg/FR-1999-08-20/pdf/FR-1999-08-20.pdf.\n\n13 Fin. Crimes Enf’t Network, Application of FinCEN’s Regulations to Persons Administering, Exchanging, or Using Virtual Currencies, FIN-2013-G001 (Mar. 18, 2013), https://www.fincen.gov/sites/default/files/shared/FIN-2013-G001.pdf.\n\n14 Money transmission involves the transmission of funds, CVC, or value that substitutes for currency to another location or person by any means. See Fin. Crimes Enf’t Network, Application of FinCEN’s Regulations to Certain Business Models Involving Convertible Virtual Currencies, FIN-2019-G001 (May 9, 2019), https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20Guidance%20CVC%20FINAL%20508.pdf.\n\n15 Id. at 20, 23-24.\n\n16 Frequently Asked Questions, U.S. Dep’t of the Treasury’s Off. of Foreign Assets Control (“OFAC”), No. 1076, https://home.treasury.gov/policy-issues/financial-sanctions/faqs/1076 (“While engaging in any transaction with Tornado Cash or its blocked property or interests in property is prohibited for U.S. persons, interacting with open-source code itself, in a way that does not involve a prohibited transaction with Tornado Cash, is not prohibited. For example, U.S. persons would not be prohibited by U.S. sanctions regulations from copying the open-source code and making it available online for others to view…”).\n\n17 Press Release, U.S. Dep’t of the Treasury, U.S. Treasury Sanctions Notorious Virtual Currency Mixer Tornado Cash (Aug. 8, 2022), https://home.treasury.gov/news/press-releases/jy0916.\n\n18 Alexandra D. Comolli & Michele R. Korver, Surfing the First Wave of Cryptocurrency Money Laundering, 69 DOJ J. FED. L. & PRAC. 3 (2021).\n\n19 31 CFR § 1010.410.\n\n20 31 CFR § 1022.320(a)(1); 31 U.S.C. § 5318(g)(3).\n\n21 CTRs require reporting of cash or coin transactions over $10,000 conducted by, or on behalf of, one person, as well as multiple currency transactions that aggregate to over $10,000 in a single day. They do not apply to digital assets currently, although there is a pending rule that could expand CTR-like requirements to CVC transactions meeting certain criteria. See 31 CFR § 1010.311; see also Fin. Crimes Enf’t Network, Notice to Customers: A CTR Reference Guide, https://www.fincen.gov/sites/default/files/shared/CTRPamphlet.pdf.\n\n22 See 50 U.S.C. § 1702(a); Nina M. Hart, Enforcement of Economic Sanctions: An Overview, Congressional Research Service Reports (Mar. 18, 2022), https://crsreports.congress.gov/product/pdf/IF/IF12063.\n\n23 Fed. Fin. Institutions Examination Council, Bank Secrecy Act (BSA)/Anti-Money Laundering (AML) Examination Manual (2021), https://bsaaml.ffiec.gov/manual/OfficeOfForeignAssetsControl/01.\n\n24 See OFAC Cyber-Related Sanctions Frequently Asked Questions, Nos. 444, 445, and 447, https://home.treasury.gov/policy-issues/financial-sanctions/faqs/topic/1546. Sanctions involving cryptocurrency may also come from country-specific executive orders, such as those addressing Russia, Iran, or North Korea.\n\n25 See 31 CFR Apx. A to Pt. 501; 50 U.S.C. § 1705.\n\n26 Civil liability arises without having knowledge or reason to know one was engaging in a sanctions violation.\n\n27 See, e.g., 18 U.S.C. §§ 1956, 1957, and 1960.\n\n28 See OFAC, Sanctions Compliance Guidance for the Virtual Currency Industry (Oct. 15, 2021) (stating that sanctions compliance programs and risk assessments apply to “companies”), https://home.treasury.gov/system/files/126/virtual_currency_guidance_brochure.pdf [hereinafter: “OFAC Guidance”]; but see Frequently Asked Questions, OFAC, No. 445, https://home.treasury.gov/policy-issues/financial-sanctions/faqs/topic/1546,(stating “[a]s a general matter, U.S. persons, including firms that facilitate or engage in online commerce, are responsible for ensuring that they do not engage in unauthorized transactions or dealings with persons named on any of OFAC’s sanctions lists or operate in jurisdictions targeted by comprehensive sanctions programs. Such persons, including technology companies, should develop a tailored, risk-based compliance program, which may include sanctions list screening or other appropriate measures.”).\n\n29 Frequently Asked Questions, OFAC, No. 1076, https://home.treasury.gov/policy-issues/financial-sanctions/faqs/1076.\n\n30 See generally Tornado Cash, https://tornado.cash (2022).\n\n31 A new version of Tornado Cash, called Nova, supports direct account-to-account transfers without having to first withdraw funds from Tornado. See generally Tornado Cash Nova, https://nova.tornadocash.eth.link (2022).\n\n32 Tim Hakki, Nearly $7M of Hacked Ronin Funds Sent to Privacy Mixer Tornado Cash, Decrypt (Apr. 4, 2022), https://decrypt.co/96811/nearly-7m-hacked-ronin-funds-sent-privacy-mixer-tornado-cash.\n\n33 See OFAC Cyber-Related Sanctions Frequently Asked Questions, Nos. 1076 and 1095, https://home.treasury.gov/policy-issues/financial-sanctions/faqs/topic/1546.\n\n34 See Elizabeth Howcroft et al., U.S. Crypto Firm Harmony Hit by $100 Million Heist, Reuters (June 24, 2022), https://www.reuters.com/technology/us-crypto-firm-harmony-hit-by-100-million-heist-2022-06-24.\n\n35 See Elizabeth Howcroft, U.S. Crypto Firm Nomad Hit by $190 Million Theft, Reuters (Aug. 3, 2022), https://www.reuters.com/technology/us-crypto-firm-nomad-hit-by-190-million-theft-2022-08-02.\n\n36 See supra note 17.\n\n37 See Chainalysis oracle for sanctions screening, Chainalysis, https://go.chainalysis.com/chainalysis-oracle-docs.html.\n\n38 Jeff Benson, Ethereum Privacy Tool Tornado Cash Says It Uses Chainalysis to Block Sanctioned Wallets, Decrypt (Apr. 15, 2022), https://decrypt.co/97984/ethereum-privacytool-Tornado-cash-uses-chainalysis-block-sanctioned-wallets.\n\n39 See Brian Armstrong & Vitalik Buterin Discuss Decentralization, Privacy, and More, Coinbase: Around the Block, at 35:00 (Aug. 30, 2022) (available on Spotify), https://open.spotify.com/episode/2vzctO7qgvYqGLKbnMnqha?si=X3eu221IRvGIJn3kd4tWFA&nd=1; see, e.g., Ben Fisch, Configurable Privacy Case Study: Partitioned Privacy Pools, Espresso Systems (Sept. 11, 2022), https://www.espressosys.com/blog/configurable-privacy-case-study-partitioned-privacy-pools.\n\n40 See OFAC Guidance at 12-16 (outlining risk assessment obligations).\n\n41 Id.\n\n42 See generally Tornado Cash, Tornado.cash compliance, Medium (June 3, 2020), https://tornado-cash.medium.com/tornado-cash-compliance-9abbf254a370.\n\n43 The newer Tornado Nova protocol supports private transfers while the funds are in the Tornado system. In this case, the “address” encrypted under the law enforcement public key must be the entire chain of transactions that led to the funds currently being withdrawn – more data than just a single address.\n\n44 See Fisch, supra note 39.\n\n***\n\nAcknowledgements: With thanks to Jai Ramaswamy and Miles Jennings for their feedback and contributions to the concepts in the piece, including Miles’s “allowlist” proposal. Thanks also to David Sverdlov who helped put this together.\n\n***\n\nEditor: Robert Hackett\n\n***\n\nJoseph Burleson is an associate general counsel at a16z crypto, where he advises the firm and its portfolio companies on legal, governance, and decentralization matters.\n\nMichele Korver is the head of regulatory at a16z crypto. She previously served as FinCEN’s Chief Digital Currency Advisor, DOJ’s Digital Currency Counsel, and as an Assistant United States Attorney.\n\nDan Boneh is a senior research advisor at a16z crypto. He is a professor of computer science at Stanford University, where he heads its Applied Cryptography Group; co-directs the Stanford Center for Blockchain Research; and co-directs the Stanford Computer Security Lab.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nCharts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":14468,"crawled_at":1791195411330}
+{"id":10521,"url":"https://solana.com/podcasts/validated-with-austin-federa/episodes/out-of-scope-ep-2-anything-but-crypto-with-david-hoffman-7psglyc","domain":"solana.com","chapter":"developer_specs","title":"OUT OF SCOPE Ep. 2: Anything But Crypto with David Hoffman | Validated | Solana Media","text":"Back to Validated\n\nValidatedAugust 14, 2026·45:19\nOUT OF SCOPE Ep. 2: Anything But Crypto with David Hoffman\nIn this episode, Austin and Tori join David Hoffman (Bankless) to talk about \"anything but crypto.\" Their conversation spans longevity and mind-uploading, the challenges of changing opinions in public, and how modern media incentives distort nuanced ideas. They also discuss social media, the future of long-form content, AI risk and alignment, what it means to “win” the AI race, regulatory uncertainty, and ... yes, David's ideas around fitness.\n\n00:00 - Welcome and intro\n\n01:46 - How Do You Want to Live?\n\n06:17 - Changing Your Mind as a Public Figure\n\n09:35 - Media Distortion Effects\n\n14:34 - Quality of Content vs Virality\n\n16:33 - Yudkowsky and AI Doom\n\n24:58 - Base Models' Values\n\n27:55 - China and AI's Moral Core\n\n30:01 - What Winning the AI Race Means\n\n36:46 - Why CLARITY Stalled\n\n41:47 - Hypertrophy and Longevity\n\n44:23 - Conclusion\n\nHosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.\n\nAF\nAustin Federa\n\nOUT OF SCOPE Ep. 2: Anything But Crypto with David Hoffman\n\n0:000:00\n\nShare this episode\n\nSubscribe & Listen\nApple PodcastsSpotifyRSS\n\nPrevious Episode\nOUT OF SCOPE, Ep. 1: Hot Takes Roundtable with Tori Pastore (Soup) and Austin Campbell (Zero Knowledge)\nNext Episode\nWhat are Intents Actually Solving? with Declan Hannon (Aurora Labs)\n\nMore from Validated\n45:05\n\nSeptember 22, 2026Building the Bitcoin Equivalent for AI Inference Compute with David and Daniil Liberman (Gonka)\nIn this episode, Austin chats with David and Daniil Liberman of Gonka about the case for using crypto to build a permissionless, meritocratic AI compute network focused on inference rather than decentralized training. They argue that centralized AI infrastructure is rapidly concentrating both revenue and compute, and contrast Bitcoin’s immutable, open rules with corporate systems whose promises can change. With Bitcoin as their north star, Gonka’s protocol aims to verify inference outputs and validate the underlying hardware to guard against fraud, censorship, and model substitution, using proof-of-work-like measurements of real, always-on hardware rather than proof-of-stake incentives.\n\n00:00 - Why Crypto for AI\n03:10 - Inference Over Training\n\n05:02 - Bitcoin as Compute Incentives\n\n07:21 - OpenRouter Critiques\n\n11:36 - Open Source and Safety\n\n18:51 - How Gonka Works\n\n20:14 - Verifiable Inference Proof\n\n24:22 - Privacy and Encryption\n\n29:07 - Decentralized Training Roadmap\n\n34:16 - Keeping Frontier Labs Honest\n\n42:44 - More on Why Bitcoin Provides an Ideal Compute Model\n\n44:23 - Where to Learn More\n\nHosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.\n\n29:36\n\nAugust 25, 2026What are Intents Actually Solving? with Declan Hannon (Aurora Labs)\nIn this episode, Austin chats with Declan from Aurora Labs about building on NEAR’s Intents architecture. Declan explains why intents go beyond “a better bridge UI\" and how Aurora Intents actually work, enabling one-click cross-chain journeys. They discuss how the protocol helps create liquidity, adoption metrics (over $21B lifetime volume, about $1B monthly), and use cases across wallets, neobanks, payments, RWAs, and more. The conversation also explores inherent cross-chain risks, as highlighted by a Litecoin reorg double-spend incident, and the need for insurance-like protections for onchain products.\n0:00 - Aurora Intents Overview\n02:57 - Intents vs Bridges\n05:21- Solver Network Explained\n06:23 - Aurora Intents’ Behind the Scenes Flow\n07:43 - Liquidity and Market Making\n08:55 - Real World Use Cases\n11:25 - Confidential Intents\n16:11 - Intents’ Speed Tradeoffs and Risks\n17:30 - Litecoin Incident Earlier This Year\n19:51 - Liability and Insurance\n26:08 - Future Verticals for Intents\n28:36 - Where to Learn More\n\nHosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.\n\n1:12:03\n\nJune 26, 2026OUT OF SCOPE, Ep. 1: Hot Takes Roundtable with Tori Pastore (Soup) and Austin Campbell (Zero Knowledge)\nAnd now for something (almost) completely different.\nWelcome to Out of Scope, a new sub-series where Austin and Tori Pastore (aka Birb Bernake) riff with guests on hot takes from the frontiers of tech, finance, policy, and whatever else is the flavor of the week In this debut episode, they sit down with Austin Campbell to discuss... quite a few things: running stablecoin reserves, repealing the 17th Amendment, why banks resemble cartels, insider trading, market structure, why regulators should be paid more and held to higher standards, modernizing the BSA, and—most importantly—a definitive ranking of video conferencing tools.\n00:00 - Introducing Tori\n01:24 - Chinese Peptides Explained\n02:45 - GLP 1 Hype Cycle\n05:40 - Peptides and Food Science\n10:49 - Enter Austin Campbell\n16:11- Stablecoin Reserve Rules\n20:35 - Gold Doom Scenarios\n22:59 - Banks' Payment Monopoly\n34:38 - AI Lobbying and EA critiques\n38:20 - Prediction Markets Incentives\n43:59 - Fixing Regulator Accountability\n47:39 - Prediction Markets\n48:47 - Market Manipulation Debate\n59:54 - Perps Versus Futures\n01:02:51 - Assassination Markets Debate\n01:06:21 - Austin's Magic Wand Reforms\n01:10:40 - Blooper Reel\n\nHosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.\n\nView all episodes from Validated","tokens":1401,"crawled_at":1791195411446}
+{"id":10522,"url":"https://blog.trailofbits.com/2025/06/17/unexpected-security-footguns-in-gos-parsers","domain":"blog.trailofbits.com","chapter":"security_audits","title":"Unexpected security footguns in Go's parsers - The Trail of Bits Blog","text":"Page content\n\nIn Go applications, parsing untrusted data creates a dangerous attack surface that’s routinely exploited in the wild. During our security assessments, we’ve repeatedly exploited unexpected behaviors in Go’s JSON, XML, and YAML parsers to bypass authentication, circumvent authorization controls, and exfiltrate sensitive data from production systems.\nThese aren’t theoretical issues—they’ve led to documented vulnerabilities like CVE-2020-16250 (a Hashicorp Vault authentication bypass found by Google’s Project Zero) and numerous high-impact findings in our client engagements.\nThis post contextualizes these unexpected parser behaviors through three attack scenarios that every security engineer and Go developer should understand:\n(Un)Marshaling unexpected data: How Go parsers can expose data that developers intended to be private\nParser differentials: How discrepancies between parsers enable attackers to bypass security controls when multiple services parse the same input\nData format confusion: How parsers process cross-format payloads with surprising and exploitable results\nWe’ll demonstrate each attack scenario with real-world examples and conclude with concrete recommendations for configuring these parsers more securely, including strategies to compensate for security gaps in Go’s standard library.\nBelow is a summary of the surprising behaviors we’ll examine, with indicators showing their security status:\n🟢 Green: Secure by default\n🟠 Orange: Insecure by default but configurable\n🔴 Red: Insecure by default with no secure configuration options\nJSONJSON v2XMLYAML\njson:\"-,…\"\nYES (bad design)\nYES (bad design)\nYES (bad design)\nYES (bad design)\n\njson:“omitempty”\nYES (expected)\nYES (expected)\nYES (expected)\nYES (expected)\n\nDuplicate keys\nYES (last)\nNO\nYES (last)\nNO\n\nCase insensitivity\nYES\nNO\nNO\nNO\n\nUnknown keys\nYES (mitigable)\nYES (mitigable)\nYES\nYES (mitigable)\n\nGarbage leading data\nNO\nNO\nYES\nNO\n\nGarbage trailing data\nYES (with Decoder)\nNO\nYES\nNO\n\nParsing in Go\nLet’s examine how Go parses JSON, XML, and YAML. Go’s standard library provides JSON and XML parsers but not a YAML parser, for which there are several third-party alternatives. For our analysis, we’ll focus on:\nencoding/json version go1.24.1\nencoding/xml version go1.24.1\nyaml.v3 version 3.0.1 (the most popular third-party Go YAML library)\nWe’ll use JSON in our following examples, but all three parsers have APIs equivalent to the ones we’ll see.\nAt their core, these parsers provide two primary functions:\nMarshal (serialize): Converts Go structs into their respective format strings\nUnmarshal (deserialize): Converts format strings back into Go structs\n\nGo uses struct field tags to allow customization of how parsers should handle individual fields. These tags consist of:\nA key name for serialization/deserialization\nOptional comma-separated directives that modify behavior (e.g., the omitempty tag option tells the JSON serializer not to include the field in the JSON output string if it is empty)\ntype User struct {\nUsername string `json:\"username_json_key,omitempty\"`\nPassword string `json:\"password\"`\nIsAdmin bool `json:\"is_admin\"`\n}\nTo unmarshal a JSON string into the User structure shown above, we must use the username_json_key key for the Username field, password for the Password field, and is_admin for the IsAdmin field.\nu := User{}\n_ = json.Unmarshal([]byte(`{\n\"username_json_key\": \"jofra\",\n\"password\": \"qwerty123!\",\n\"is_admin\": \"false\"\n}`), &u)\nfmt.Printf(\"Result: %#v\\n\", u)\n// Result: User{Username:\"jofra\", Password:\"qwerty123!\", IsAdmin:false}\nThese parsers also offer stream-based alternatives that operate on io.Reader interfaces rather than byte slices. This API is ideal for parsing streaming data such as HTTP request bodies, making it a preferred choice in HTTP request handling.\n\nAttack scenario 1: (Un)Marshaling unexpected data\nSometimes, you need to limit which fields of a structure can be marshaled or unmarshaled.\nLet’s consider a simple example in which a back-end server has an HTTP handler for creating users and another for retrieving that user after authentication.\nWhen creating a user, you may not want the user to be able to set the IsAdmin field (i.e., unmarshal that field from the user input).\n\nSimilarly, when fetching the user, you may not want the user to return the user’s Password or other secret values.\n\nHow can we instruct the parsers not to marshal or unmarshal a field?\nFields without a tag\nLet’s first see what happens if you don’t set a JSON tag.\ntype User struct {\nUsername string\n}\nIn this case, you can unmarshal the Username field with its name, as shown below.\n_ = json.Unmarshal([]byte(`{\"Username\": \"jofra\"}`), &u)\n// Result: User{Username:\"jofra\"}\nThis is well documented, and most Go devs are aware of it. Let’s look at another example:\ntype User struct {\nUsername string `json:\"username,omitempty\"`\nPassword string `json:\"password,omitempty\"`\nIsAdmin bool\n}\nIs it evident that the IsAdmin field above would be unmarshaled? A less senior or distracted developer could assume it would not and introduce a security vulnerability.\nIf you’d like to scan your codebase for this pattern, where some but not all fields have a JSON, XML, or YAML tag, you can use the following Semgrep rule. This rule is not on the our collection of rules exposed on the Semgrep registry because, depending on the codebase, it is likely to produce many false positives.\nrules:\n- id: unmarshaling-tag-in-only-some-fields\nmessage: >-\nType $T1 has fields with json/yml/xml tags on some but not other fields. This field can still be (un)marshaled using its name. To prevent a field from being (un)marshaled, use the - tag.\nlanguages: [go]\nseverity: WARNING\npatterns:\n- pattern-inside: |\ntype $T1 struct {\n...\n$_ $_ `$TAG`\n...\n}\n# This regex attempts to remove some false positives such as structs declared inside structs\n- pattern-regex: >-\n^[ \\t]+[A-Z]+[a-zA-Z0-9]*[ \\t]+[a-zA-Z0-9]+[^{`\\n\\r]*$\n- metavariable-regex:\nmetavariable: $TAG\nregex: >-\n.*(json|yaml|xml):\"[^,-]\nMisusing the - tag\nTo tell the parser not to (un)marshal a specific field, we must add the special - JSON tag!\ntype User struct {\nUsername string `json:\"username,omitempty\"`\nPassword string `json:\"password,omitempty\"`\nIsAdmin bool `json:\"-,omitempty\"`\n}\nLet’s try it!\n_ = json.Unmarshal([]byte(`{\"-\": true}`), &u)\n// Result: main.User{Username:\"\", Password:\"\", IsAdmin:true}\nOh, whoops, we were still able to set the IsAdmin field. We copy-pasted the ,omitempty part by mistake, which caused the parser to look for the - key in the provided JSON input. I searched for this pattern on the top 1,000 Go repositories by stars on GitHub and, among a few others, I found and reported these two results, which are now fixed:\nFlipt exposes the ClientID field on an OIDC configuration as the - field (fixed in #3658)\nlangchaingo exposes the MaxTokens field as the - field (fixed in #1163)\nWhile this behavior is error prone with minimal benefits (having the ability to name a field -), it is documented in the JSON package documentation:\nAs a special case, if the field tag is “-”, the field is always omitted. Note that a field with name “-” can still be generated using the tag “-,”.\n\nThe XML and YAML parsers operate similarly, with one key difference: the XML parser treats the <-> tag as invalid. To resolve this, we must prefix the - symbol with an XML namespace, such as <A:->.\n\nOk, ok, let’s do it right this time.\ntype User struct {\nUsername string `json:\"username,omitempty\"`\nPassword string `json:\"password,omitempty\"`\nIsAdmin bool `json:\"-\"`\n}\nFinally! Now, there is no way for the IsAdmin field to be unmarshaled.\nBut I hear you ask: How can these misconfigurations lead to security vulnerabilities? The most common way is, like in our example, using -,... as the JSON tag for a field such as IsAdmin–a field the user should not control. This is a hard bug to detect with unit tests because unless you have an explicit test that unmarshals an input with the - key and detects if any field was written to, you won’t detect it. You need your IDE or an external tool to detect it.\n\nWe created a public Semgrep rule to help you find similar issues in your codebases. Try it with semgrep -c r/trailofbits.go.unmarshal_tag_is_dash.unmarshal-tag-is-dash!\nMisusing omitempty\nAnother very simple misconfiguration we’ve found before was a developer mistakenly setting the field name to omitempty.\ntype User struct {\nUsername string `json:\"omitempty\"`\n}\nu := User{}\n_ = json.Unmarshal([]byte(`{\"omitempty\": \"a_user\"}`), &u)\n// Result: User{Username:\"a_user\"}\nIf you set the JSON tag to omitempty, the parser will use omitempty as the field’s name (as expected). Of course, some developers have tried to use this to set the omitempty option in the field while keeping the default name. I searched the top 1,000 Go repositories for this pattern and found these results:\nGitea exposes the Args field of the TranslatableMessage structure with the omitempty key (fixed in #33663)\nKustomize exposes the Replacements field of the plugin structure with the omitempty key (fixed in #5877)\nBtcd exposes the MaxFeeRate field of the TestMempoolAcceptCmd structure with the omitempty key\nEvcc exposes the Message field of the Measurements structure with the omitempty key\nIn these cases, the developer often wanted to set the tag to json:\",omitempty\", which would keep the default name, and add the omitempty tag option.\nContrary to the previous example, this one is unlikely to have a security impact and should be easy to detect with tests because any attempt to serialize or deserialize input with the expected field name will fail. However, as we can see, it still shows up even in popular open-source repositories. We created a public Semgrep rule to help you find similar issues in your codebases. Try it with semgrep -c r/trailofbits.go.unmarshal_tag_is_omitempty.unmarshal-tag-is-omitempty!\nAttack scenario 2: Parser differentials\nWhat can happen if you parse the same input with different JSON parsers and they disagree on the result? More specifically, which behaviors in Go parsers allow attackers to trigger these discrepancies “reliably”?\nAs an example, let’s use the following application using a microservice architecture with:\nA Proxy Service that receives all user requests\nAn Authorization Service called by the Proxy Service to determine if the user has sufficient permission to complete their request\nMultiple business logic services called by the Proxy Service to perform the business logic\nIn this first flow, a regular, non-admin user attempts to perform a UserAction, an action they are allowed to perform.\n\nIn this second flow, the same regular user attempts to perform an AdminAction, an action they are forbidden to perform.\n\nFinally, the following flow is because the services disagree on the action the user is trying to perform.\n\nThe Authorization Service, written in a different programming language or using a non-default Go parser, will parse UserAction and grant the user permission to perform the operation, while the Proxy Service, using Go’s default parser, will parse AdminAction and proxy it to the incorrect service. The remaining question is: Which payloads can we use to achieve this behavior?\nThis is a common architecture we’ve seen multiple times during our audits, and against which we’ve found authentication bypasses because of the problems we’ll describe below. Other examples exist, but most follow the same pattern: the component that does security checks and the component that performs the actions differ in their view of the input data. Here are some of those examples in a variety of scenarios:\nCVE-2017-12635: Authorization bypass in Apache CouchDB caused by JSON parser differentials (very similar to our example above)\nMacOS sandbox escape caused by XML parser differentials (2020)\n0-click Zoom RCE caused by XML parser differentials in XMPP (2022)\nGitLab SAML auth bypass caused by XML parser differentials (2025)\nDuplicate fields\nThe first differential attack vector we’ll explore is duplicate keys. What happens when your JSON input has the same key twice? It depends on the parser!\nIn Go, the JSON parser will always take the last one. There is no way to prevent this behavior.\n_ = json.Unmarshal([]byte(`{\n\"action\": \"Action1\",\n\"action\": \"Action2\"\n}`), &a)\n// Result: ActionRequest{Action:\"Action2\"}\nThis is the default behavior of most parsers. However, as shown in the JSON interoperability vulnerabilities blog post from Bishop Fox, seven out of the 49 parsers tested take the first key:\nGo: jsonparser and gojay\nC++: rapidjson\nJava: json-iterator\nElixir: Jason and Poison\nErlang: jsone\nNone of these are the most common JSON parsers in their corresponding languages, even though some are common alternatives.\nSo, if our Proxy Service uses the Go JSON parser and the Authorization Service uses one of these parsers, we get our discrepancy, as shown in the figure below.\n\nThe XML parser has the same behavior, while the YAML parser returns an error on duplicate fields—the secure default we think all of these parsers should implement.\n\nWhile not ideal, at least this behavior is consistent with the most commonly used JSON and XML parsers. Let’s now take a look at a much worse behavior that will almost always get you a discrepancy between Go’s default parser and any other parser.\nCase insensitive key matching\nGo’s JSON parser parses field names case-insensitively. Whether you write action action, ACTION, or aCtIoN, the parser treats them as identical!\n_ = json.Unmarshal([]byte(`{\n\"aCtIoN\": \"Action2\"\n}`), &a)\n// Result: ActionRequest{Action:\"Action2\"}\nThis is documented but is very unintuitive, there’s no way to disable it, and almost no other parser has this behavior.\nTo make this worse, as we saw above, you can have duplicate fields, and the latter one is still chosen, eVeN wHeN tHe cAsInG dOeS nOt mAtCh.\n_ = json.Unmarshal([]byte(`{\n\"action\": \"Action1\",\n\"aCtIoN\": \"Action2\"\n}`), &a)\n// Result: ActionRequest{Action:\"Action2\"}\nThis is against the documentation, which says:\n“To unmarshal JSON into a struct, Unmarshal matches incoming object keys to the keys used by Marshal (either the struct field name or its tag), preferring an exact match but also accepting a case-insensitive match.”\n\nYou can even use Unicode characters! In the example below, we’re using ſ (the unicode character named Latin small letter long s) as an s, and K (the unicode character for the Kelvin sign) as a k. From our testing of the JSON library code that does the comparison, only these two unicode characters match ASCII characters.\ntype ActionRequest struct {\nAction string `json:\"aktions\"`\n}\na := ActionRequest{}\n_ = json.Unmarshal([]byte(`\n{\n\"aktions\": \"Action1\",\n\"aKtionſ\": \"Action2\"\n}\n`), &a)\nfmt.Printf(\"Result: %#v\\n\", a)\n// Result: main.ActionRequest{Action:\"Action2\"}\nApplying it to our running attack scenario, this is how the attack would look like:\n\nIn our opinion, this is the most critical pitfall of Go’s JSON parser because it differs from the default parsers for JavaScript, Python, Rust, Ruby, Java, and all other parsers we tested. This has led to many high-impact security vulnerabilities, including ones we’ve found during our audits.\nAs a final blow, there’s no way to disable this behavior, even though people have complained about this behavior leading to security vulnerabilities since at least 2016.\nThis only affects the JSON parser. The XML and YAML parsers use exact matches.\n\nIf you are interested in other kinds of JSON parsing differentials between many parsers, we recommend these two blog posts:\nParsing JSON is a Minefield by Nicolas Seriot\nJSON Interoperability Vulnerabilities by Bishop Fox\nAttack scenario 3: Data format confusion\nFor the final attack scenario, let’s see what happens if you parse a JSON file with the XML parser or use any other format with the incorrect parser.\nAs an example, let’s use CVE-2020-16250, an Hashicorp Vault bypass in its AWS IAM authentication method. This bug was found by Google’s Project Zero team, and a detailed analysis can be found in their “Enter the Vault: Authentication Issues in HashiCorp Vault” blog post if you are interested. We won’t go through all the details in this post, but in summary, this is how the normal Hashicorp Vault AWS IAM authentication flow works:\nAn AWS resource (e.g., an AWS Lambda function) presigns a GetCallerIdentity request.\nThe AWS resource sends it to the Vault Server.\nThe Vault Server builds that requests and sends it to the AWS Security Token Service (STS).\nAWS STS verifies the signature.\nOn success, AWS STS returns the associated role’s identity in an XML document.\nThe Vault Server parses the XML, extracts the identity, and, if that AWS role should have access to the requested secrets, it returns them.\nThe AWS resource can now use the secret to, for example, authenticate against a database.\n\nWhat Google’s Project Zero team found was that an attacker could control too much in step 2, including controlling all headers of the request that Vault builds in step 3. In particular, by setting the Accept header to application/json, AWS STS would now return a JSON document in step 5 instead of the expected XML document. As a result, the Vault Server would parse a JSON document with Go’s XML parser. Because the XML parser is very lenient and parses anything that looks like XML in between lots of other “garbage” data, this was sufficient for a full authentication bypass when combined with partial control of the JSON response.\n\nLet’s look at three different behaviors that make parsing files with the wrong Go parser possible and build a polyglot that can be parsed with Go’s JSON, XML, and YAML parsers and return a different result for each.\nUnknown keys\nBy default, the JSON, XML, and YAML parsers don’t prevent unknown fields—properties in the incoming data that don’t match any fields in the target struct.\n\nLeading garbage data\nOf the three parsers, only the XML parser accepts leading garbage data.\n\nTrailing garbage data\nAgain, only the XML parser accepts arbitrary trailing garbage data.\n\nThe exception is using the parsers’ Decoder API with streaming data, in which case the JSON parser accepts garbage trailing data. This an open issue for which a fix is not planned.\n\nConstructing a polyglot\nHow can we combine all the behaviors we’ve seen so far that build a polyglot that:\nCan be parsed by Go’s JSON, XML, and YAML parsers\nReturns a different result for each\nA very useful piece of information is that JSON is a subset of YAML:\nEvery JSON file is also a valid YAML file\n\nWith this in mind, we can build the following polyglot:\n\nThe JSON parser can parse the polyglot because the input is valid JSON, it ignores unknown keys, and it allows duplicate keys. It takes the Action_2 value because its field matching is case-insensitive and it takes the value of the last match.\nThe YAML parser can parse the polyglot because the input is valid JSON (and every JSON file is also a valid YAML file), and it ignores unknown keys. It takes the Action_1 value because, contrary to the JSON parser, it does exact field name matches.\nFinally, the XML parser can parse the polyglot because it ignores all surrounding data and just looks for XML-looking data, which, in this polyglot, we hid in a JSON value. As a result, it takes Action_3.\nThe polyglot we’ve constructed is a powerful starting payload when exploiting these data format confusion attacks similar to the HashiCorp Vault bypass we explored above (CVE-2020-16250).\nMitigations\nHow can we minimize these risks and make JSON parsing more strict? We’d like to:\nPrevent parsing of unknown keys in JSON, XML, and YAML\nPrevent parsing of duplicate keys in JSON and XML\nPrevent case insensitive key matches in JSON (this one is especially important!)\nPrevent leading garbage data in XML\nPrevent trailing garbage data in JSON and XML\nUnfortunately, JSON only offers one option to make its parsing stricter: DisallowUnknownFields. As the name implies, this option disallows unknown fields in the input JSON. YAML supports the same functionality with the KnownFields(true) function, and while there was a proposal to implement the same for XML, it was rejected.\nTo prevent the remaining insecure defaults, we must create a custom “hacky” solution. The next code block shows the strictJSONParse function, an attempt to make JSON parsing stricter, which has several limitations:\nBad performance: It requires parsing JSON input twice, making it significantly slower.\nIncomplete detection: Some edge cases remain undetected, as detailed in the function comments.\nPoor adoption potential: Since these security measures aren’t built into libraries as secure defaults or configurable options, widespread adoption is unlikely.\nStill, if you detect a vulnerability in your codebase, perhaps this imperfect solution can help you plug a hole while you find a more permanent solution.\n// DetectCaseInsensitiveKeyCollisions checks if the JSON data contains keys\n// that differ only by letter case. This helps prevent subtle bugs where two\n// different key spellings might refer to the same data.\nfunc DetectCaseInsensitiveKeyCollisions(data []byte) error {\n// Create a map to hold the decoded JSON data and attempt to parse the JSON\n// data. This keeps keys with different letter casing.\nvar res map[string]interface{}\nif err := json.NewDecoder(bytes.NewReader(data)).Decode(&res); err != nil {\nreturn err\n}\n\nseenKeys := make([]string, 0, len(res))\n\n// Iterate through all keys in the parsed JSON and detect duplicates\nfor newKey := range res {\nfor _, existingKey := range seenKeys {\nif strings.EqualFold(existingKey, newKey) {\n// Return an error when a case-insensitive duplicate is found\nreturn fmt.Errorf(\"case-insensitive duplicate keys detected:\n%q and %q\", existingKey, newKey)\n}\n}\nseenKeys = append(seenKeys, newKey)\n}\nreturn nil\n}\n\n// Provides a stricter JSON parsing with additional validation:\n// 1. Rejects unknown fields not in the target struct\n// 2. Detects case-insensitive key collisions\n// 3. Ensures complete parsing with no trailing content\n// strictJSONParse does not:\n// - Ensure that there are no duplicate keys with the same casing\n// - Ensure that the casing in the input matches the expected casing\n// in the target struct\nfunc strictJSONParse(jsonData []byte, target interface{}) error {\ndecoder := json.NewDecoder(bytes.NewReader(jsonData))\n\n// 1. Disallow unknown fields\ndecoder.DisallowUnknownFields()\n\n// 2. Disallow duplicate keys with different casing\nerr := DetectCaseInsensitiveKeyCollisions(jsonData)\nif err != nil {\nreturn fmt.Errorf(\"strictJSONParse: %w\", err)\n}\n\n// Decode the JSON into the provided struct\nerr = decoder.Decode(target)\nif err != nil {\nreturn fmt.Errorf(\"strictJSONParse: %w\", err)\n}\n\n// 3. Ensure there's no trailing data after the JSON object\ntoken, err := decoder.Token()\nif err != io.EOF {\nreturn fmt.Errorf(\"strictJSONParse: unexpected trailing data after\nJSON: token: %v, err: %v\", token, err)\n}\n\nreturn nil\n}\nJSONv2\nTo be widely adopted and solve the problem at a large scale, this functionality needs to be implemented at the library level and enabled by default. This is where JSON v2 comes in. It is currently only a proposal, but a lot of work has gone into it already, and it will hopefully be released soon. It improves on JSON v1 in many ways, including:\nDisallowing duplicate names: “(…) in v2 a JSON object with duplicate names results in an error. The jsontext.AllowDuplicateNames option controls this behavior difference.”\nDoing case-sensitive matching: “(…) v2 matches fields using an exact, case-sensitive match. The MatchCaseInsensitiveNames and jsonv1.MatchCaseSensitiveDelimiter options control this behavior difference.”\nIt includes a RejectUnknownMembers option, even though it is not enable by default (equivalent to DisallowUnknownFields).\nIt includes a UnmarshalRead function to process data from an io.Reader, verifying that an EOF is found, disallowing trailing garbage data.\nWhile this proposal addresses many of the issues discussed in this blog post, these challenges will persist within the Go ecosystem as widespread adoption takes time. The proposal needs formal acceptance, after which developers must integrate it into all existing JSON-parsing Go code. Until then, these vulnerabilities will continue to pose risks.\nKey takeaways for developers\nImplement strict parsing by default. Use DisallowUnknownFields for JSON, KnownFields(true) for YAML. Unfortunately, this is all you can do directly with the Go parser APIs.\n\nMaintain consistency across boundaries. When input in processed in multiple services, ensure consistent parsing behavior by always using the same parser or implement additional validation layers, such as the strictJSONParse function shown above.\n\nWatch for JSON v2. Keep an eye on the development of Go’s JSON v2 library, which addresses many of these issues with safer defaults for JSON.\n\nLeverage static analysis. Use the Semgrep rules we’ve provided to detect a few vulnerable patterns in your codebase, particularly the misuse of the - tag and omitempty fields. Try them with semgrep -c r/trailofbits.go.unmarshal_tag_is_dash.unmarshal-tag-is-dash and semgrep -c r/trailofbits.go.unmarshal_tag_is_omitempty.unmarshal-tag-is-omitempty!\n\nWhile we’ve provided mitigations and detection strategies, the long-term solution requires fundamental changes to how these parsers operate. Until parser libraries adopt secure defaults, developers must remain vigilant.","tokens":6374,"crawled_at":1791195421816}
+{"id":10523,"url":"https://docs.ethena.fi/technical-design/minting-usde/mint-and-redeem-contract-v2","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Mint and Redeem Contract V2 | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nOverview\nEthena upgraded the Mint and Redeem Contract from the first version to the second version on the 8th of July 2024 at approximately 10am UTC.\nEthena gathered feedback from all key stakeholders, requested buy-in, and scheduled the deployment at a date & time that was optimal for whitelisted API users. This upgrade represented a breaking change to existing whitelisted users' trading systems.\n\nBoth versions of the contract were written by the same engineering team and have both successfully passed Audit.\nThe updates to the Mint and Redeem Contract were principally motivated by:\n\nImprovements to the protocol's security and continuing to reduce potential risk surfaces.\n\nAdding features requested by existing and potential users to support new workflows.\n\nIntroducing additional controls around specific risk configurations.\n\nAction Items for API Users\nFunctionally for existing whitelisted API users, the changes were quite minor and not a large engineering lift for whitelisted users.\n\nReview the Mint and Redeem Contract V2 between the existing & second versions of the Mint & Redeem Contract.\n\nPrepare required updates to your trading system to accommodate the second version of the contract, including:\n\nUpdating your connection URL to either https://public.api.ethena.fi or https://private.api.ethena.fi from https://api.ethena.fi.\n\nYou must provide an IP address to be whitelisted if you wish to use the private.api.ethena.fi connection URL. There is no difference in priority, performance, or rate limits between the two connection URLs.\n\nEnsuring new approvals are added to your whitelisted addresses given the new Mint and Redeem Smart Contract.\n\nUpdating to use the new Minting Contract ABI.\n\nThe [POST] /order submission remains the same, except for the following changes:\n\nrfq_id is no longer required in the [POST] /order parameters. Instead, it must be included inside the signed object body object as order_id. This is because the rfq id is now stored onchain, and thus requires you to sign it.\n\nFor EIP-1271 users, you must add the signature_type parameter with the value EIP1271 to the [POST] /order request. The default is EIP712 so the former is only required if you're using EIP-1271.\n\nurl = {ethena_url}order?signature={signature_hex}&signature_type=EIP1271\n\nSupporting the new error_code value 27 that enables you to perform a hot upgrade if you would like during the deployment. If you receive this code from V1 then it is time to begin minting/redeeming with your V2 client.\n\nDuring deployment, prepare for approximately 15 minutes of downtime.\n\nThe Ethena Labs team will proactively confirm to users if the deployment has been successful.\n\nAPI users will be required to meet the new API specifications & requirements to be able to mint & redeem directly with Ethena.\n\nIn the event of an unsuccessful launch, Ethena Labs will:\n\nCommunicate proactively with all API users.\n\nImmediately roll back to V1 of the Mint & Redeem Smart Contract enabling the existing V1 systems to continue functioning without change.\n\nCoordinate another deployment date in the future for all API users.\n\nOnly the USDT/USDe pair will be available for minting and redeeming for the initial V2 rollout. Other pairs are available at the protocol's discretion.\n\nChanges\nOverview\n\nChange\n\nDescription\n\nOperation / Outcome\n\nDistinct Asset Mint/Redeem Max Per Block Limits\n\nImplements asset-specific block-by-block minting and redeeming limits for stablecoins versus assets/LSTs, with a global cap.\n\nLimits can be adjusted using the Ethena Dev multi-sig.\n\nEIP-1271 Smart Contract Signing\n\nAdopts EIP-1271 standards to verify signatures, enabling smart contracts to recognize and accept collateral.\n\nMarket Maker Smart Contract implementing the https://eips.ethereum.org/EIPS/eip-1271 Interface can partake in this type of Minting via adding a parameter to the [POST] /order request.\n\nOnchain API User Whitelisting\n\nIntroduces multi-sig whitelist for benefactors and a self serve beneficiary whitelist directly within the Mint and Redeem Contract.\n\nBenefactor addresses are onboarded via Ethena Dev multi-sig; beneficiaries are assigned by benefactors.\n\nMandate Delta Limit Between Stables & USDe\n\nSets a mandated delta limit in bps for price divergence between stablecoins and USDe in specific cases, mainly to protect protocol from blackswan events like stablecoin collateral de-pegging events or private key compromise.\n\nThe value of the limit is configurable via the Ethena Dev multi-sig.\n\nIf MINT and the normalised amount of USDe minted is greater than the collateral received, the stable limit check is applied.\n\nIf REDEEM and the normalised amount of USDe is less than the amount of collateral returned, the stable limit check is applied.\n\nGas Optimizations\n\nUses Solidity structs to optimize gas usage and rearranges declaration for efficiency.\nImplements optimized gas usage through efficient memory management of variables like order_type, and expiry.\n\nMints and Redeems occur normally but with less ETH burned by minters and redeemers over time.\n\nRFQ ID on chain\n\nEnables further reconciliation between the quoted RFQ ID from the Ethena trading system and the actual mints and redeems.\n\nIncluded in the V2 Market Maker client program. Must now be part of EIP-712 an EIP-1271 signed order payloads for [POST] /order requests.\n\nAES cipher encryption\n\nImplemented advanced key encoding mechanisms using AES encryption and a rigorous key ceremony protocol involving multiple participants and secure storage methods.\n\nOperations no longer rely upon AWS secrets. The secure process startup and interaction with the cryptographical of the system is strictly managed and executed by authorized Ethena Labs personnel only.\n\nDetails\nThe section below is not an exhaustive list of the aforementioned changes but rather expands on particular areas of interest. Please reach out if you have any questions or feedback.\nDistinct Asset Mint/Redeem Max Per Block Limits\nEthena is now able to set specific direct Mint/Redeem global limits per ETH block by:\n\nAsset\n\nGroups of Assets, such as Stablecoins and LSTs\n\nThis enables greater specificity around which assets whitelisted users are able to directly mint & redeem directly with Ethena.\n\nAll block limits are measured in USDe terms. The global block limit can never be surpassed regardless of the individual USDe limits, per asset, per block.\n\nMandate Delta Limit Between Stables & USDe\nThis feature introduces an additional validation to check such that it is not possible to directly mint or redeem with Ethena if the divergence in price between USDe and USDT/USDC exceeds a defined limit in an adverse way to the protocol. The limit is defined via the field stablesDeltaLimitwith a default of zero.\n\nThe Distinct Asset Mint/Redeem Max Per Block Limits feature in combination with the Mandate Delta Limit between Stables & USDe feature means, that when only stablecoin minting is enabled, a theoretical compromise of the Mint and Redeem Contract private keys can NOT lead to protocol losses.\n\nThis unique pairing removes the risk surface that would enable an attacker to ever possibly be able to mint or redeem USDe at an unfavorable price to the protocol.\n\nEIP-1271 Smart Contracts Signing\nWith the adoption of EIP-1271 standards, this enables Smart Contracts to directly (after having been whitelisted) mint and redeem with Ethena via our API.\nIf using an EIP-1271, then the signature_type parameter, with the value EIP1271, must be added to the [POST] /order request.\n\nOnchain API User Whitelisting\nEthena is moving from offchain to onchain whitelisting of users able to interact with the API. Newly requested addresses to be whitelisted will be added by a request from the Ethena Dev multi-sig.\nWhitelisted users now have the autonomy to whitelist their beneficiaries via the following smart contract function invocation:\n\nfunction setApprovedBeneficiary(address beneficiary, bool status)\n\nIf the benefactor and the beneficiary are the same, there is NO need to whitelist the beneficiary onchain beforehand.\n\nHot (Graceful) Upgrade on Deployment\nAn Error Code has been added to the API specification to notify when the migration has successfully occurred.\nUsers are able to use this response, returned by [POST] /orders, to automatically swap trading systems to meet the requirements of the second version of the Mint and Redeem Contract. In the event of an unsuccessful deployment, users could also use this to swap their settings back to the original version 1.\nExample of error_code == 27\n\n{\n\"error_name\":\"Incorrect USDe minter. Switch Minting API\",\n\"error_code\":\"27\"\n}\n\nLast updated 1 year ago\nWas this helpful?","tokens":2192,"crawled_at":1791195424120}
+{"id":10524,"url":"https://www.metaplex.com/docs/smart-contracts/core/external-plugins/oracle","domain":"www.metaplex.com","chapter":"docs","title":"Oracle Plugin | Metaplex Core","text":"The Oracle Plugin connects Core Assets to external Oracle accounts for custom validation logic. Reject transfers, burns, or updates based on time, price, ownership, or any custom rule you implement.\nWhat You'll Learn\nCreate Oracle accounts for validation\nConfigure lifecycle checks (reject transfers, updates, burns)\nUse PDA-based Oracle addressing\nDeploy time-based and condition-based restrictions\n\nSummary\nThe Oracle Plugin validates lifecycle events against external Oracle accounts. The Oracle account stores validation results that the Core program reads to approve or reject operations.\nCan reject create, transfer, burn, and update events\nOracle account is external to the Asset (you control it)\nDynamic: update the Oracle account to change behavior\nSupports PDA derivation for per-asset or per-owner oracles\nOut of Scope\nAppData storage (see AppData Plugin), built-in freeze behavior (see Freeze Delegate), and off-chain oracles.\nQuick Start\nJump to: Oracle Account Structure · Create with Oracle · Add to Asset · Default Oracles\nDeploy an Oracle account with validation rules\nAdd Oracle plugin adapter to Asset/Collection\nConfigure lifecycle checks (which events to validate)\nUpdate Oracle account to change validation behavior dynamically\nWhat is an Oracle Plugin?\nAn Oracle Plugin is an onchain account that is created by the authority externally from the MPL Core Asset or Collection. If an Asset or Collection has an Oracle Adapter enabled and an Oracle Account assigned to it the Oracle Account will be loaded by the MPL Core program for validations against lifecycle events. The Oracle Plugin stores data relating to 4 lifecycle events of create, transfer, burn, and update and can be configured to perform a Reject validation. The ability to update and change the Oracle Account provides a powerful and interactive lifecycle experience.\nWorks With\n\nMPL Core Asset\n✅\n\nMPL Core Collection\n✅\n\nAllowed Validations\nThe following validation results can be returned from the Oracle Account to the Oracle Plugin.\n\nCan Approve\n❌\n\nCan Reject\n✅\n\nCan Pass\n❌\n\nOn Chain Oracle Account Structure\nThe Oracle Account should have the following onchain account structure.\nOn Chain Account Struct of Oracle Account\n\n#[account]\n\npub struct Validation {\n\npub validation: OracleValidation,\n\n}\n\nimpl Validation {\n\npub fn size() -> usize {\n\n8 // anchor discriminator\n\n+ 5 // validation\n\n}\n\n}\n\npub enum OracleValidation {\n\nUninitialized,\n\nV1 {\n\ncreate: ExternalValidationResult,\n\ntransfer: ExternalValidationResult,\n\nburn: ExternalValidationResult,\n\nupdate: ExternalValidationResult,\n\n},\n\n}\n\npub enum ExternalValidationResult {\n\nApproved,\n\nRejected,\n\nPass,\n\n}\n\nOracle Account Offset\nThe account structure will differ slightly between account frameworks (Anchor, Shank, etc.) due to the discriminator sizes needed for accounts:\nIf the OracleValidation struct is located at the beginning of the data section for the Oracle account, then choose NoOffset for the ValidationResultsOffset.\nIf the Oracle account only contains the OracleValidation struct but is managed by an Anchor program, select Anchor for ValidationResultsOffset so that the struct can be located after the Anchor account discriminator.\nIf the OracleValidation struct is located at some other offset in the Oracle account, use the Custom offset.\nresultsOffset / result_offset\n\nconst resultsOffset: ValidationResultsOffset =\n\n| { type: 'NoOffset' }\n\n| { type: 'Anchor' }\n\n| { type: 'Custom'; offset: bigint };\n\nUpdating the Oracle Account\nBecause the Oracle Account is created and maintained by the creator/developer the OracleValidation struct can be updated at anytime allowing lifecycles to be dynamic.\nThe Oracle Adapter\nThe Oracle Adapter accepts the following arguments and data.\nOn Chain Struct\npub struct Oracle {\n\n/// The address of the oracle, or if using the `pda` option,\n\n/// a program ID from which to derive a PDA.\n\npub base_address: Pubkey,\n\n/// Optional account specification (PDA derived from `base_address` or other\n\n/// available account specifications). Note that even when this\n\n/// configuration is used there is still only one\n\n/// Oracle account specified by the adapter.\n\npub base_address_config: Option<ExtraAccount>,\n\n/// Validation results offset in the Oracle account.\n\n/// Default is `ValidationResultsOffset::NoOffset`\n\npub results_offset: ValidationResultsOffset,\n\n}\n\nDeclaring the PDA of an Oracle Plugin\nThe default behavior of the Oracle Plugin Adapter is to supply the adapter with a static base_address which the adapter can then read from and provide the resulting validation results. If you wish to get more dynamic with the Oracle Plugin Adapter you can pass in your program_id as the base_address and then an ExtraAccount, which can be used to derive one or more PDAs pointing to Oracle Account addresses. This allows the Oracle Adapter to access data from multiple derived Oracle Accounts. Note that there are other advanced non-PDA specifications also available when using ExtraAccount.\nList of ExtraAccounts Options\nAn example of an extra account that is the same for all assets in a collection is the PreconfiguredCollection PDA, which uses the collection's Pubkey to derive the Oracle account. An example of more dynamic extra account is the PreconfiguredOwner PDA, which uses the owner pubkey to derive the Oracle account.\npub enum ExtraAccount {\n\n/// Program-based PDA with seeds \\[\"mpl-core\"\\]\n\nPreconfiguredProgram {\n\n/// Account is a signer\n\nis_signer: bool,\n\n/// Account is writable.\n\nis_writable: bool,\n\n},\n\n/// Collection-based PDA with seeds \\[\"mpl-core\", collection_pubkey\\]\n\nPreconfiguredCollection {\n\n/// Account is a signer\n\nis_signer: bool,\n\n/// Account is writable.\n\nis_writable: bool,\n\n},\n\n/// Owner-based PDA with seeds \\[\"mpl-core\", owner_pubkey\\]\n\nPreconfiguredOwner {\n\n/// Account is a signer\n\nis_signer: bool,\n\n/// Account is writable.\n\nis_writable: bool,\n\n},\n\n/// Recipient-based PDA with seeds \\[\"mpl-core\", recipient_pubkey\\]\n\n/// If the lifecycle event has no recipient the derivation will fail.\n\nPreconfiguredRecipient {\n\n/// Account is a signer\n\nis_signer: bool,\n\n/// Account is writable.\n\nis_writable: bool,\n\n},\n\n/// Asset-based PDA with seeds \\[\"mpl-core\", asset_pubkey\\]\n\nPreconfiguredAsset {\n\n/// Account is a signer\n\nis_signer: bool,\n\n/// Account is writable.\n\nis_writable: bool,\n\n},\n\n/// PDA based on user-specified seeds.\n\nCustomPda {\n\n/// Seeds used to derive the PDA.\n\nseeds: Vec<Seed>,\n\n/// Program ID if not the base address/program ID for the external plugin.\n\ncustom_program_id: Option<Pubkey>,\n\n/// Account is a signer\n\nis_signer: bool,\n\n/// Account is writable.\n\nis_writable: bool,\n\n},\n\n/// Directly-specified address.\n\nAddress {\n\n/// Address.\n\naddress: Pubkey,\n\n/// Account is a signer\n\nis_signer: bool,\n\n/// Account is writable.\n\nis_writable: bool,\n\n},\n\n}\n\nCreating and Adding Oracle Plugins\nCreating an Asset with the Oracle Plugin\nCreate a MPL Core Asset with an Oracle Plugin\n\nimport { generateSigner, publicKey } from '@metaplex-foundation/umi'\n\nimport {\n\ncreate,\n\nCheckResult\n\n} from '@metaplex-foundation/mpl-core'\n\nconst collectionSigner = generateSigner(umi)\n\nconst oracleAccount = publicKey('11111111111111111111111111111111')\n\nconst asset = await create(umi, {\n\n... CreateAssetArgs,\n\nplugins: [\n\n{\n\ntype: 'Oracle',\n\nresultsOffset: {\n\ntype: 'Anchor',\n\n},\n\nbaseAddress: oracleAccount,\n\nlifecycleChecks: {\n\nupdate: [CheckResult.CAN_REJECT],\n\n},\n\nbaseAddressConfig: undefined,\n\n},\n\n],\n\n});.sendAndConfirm(umi)\n\nAdding an Oracle Plugin to An Asset\nAdding an Oracle Plugin to a Collection\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { addPlugin, CheckResult } from '@metaplex-foundation/mpl-core'\n\nconst asset = publicKey('11111111111111111111111111111111')\n\nconst oracleAccount = publicKey('22222222222222222222222222222222')\n\naddPlugin(umi, {\n\nasset,\n\nplugin: {\n\ntype: 'Oracle',\n\nresultsOffset: {\n\ntype: 'Anchor',\n\n},\n\nlifecycleChecks: {\n\ncreate: [CheckResult.CAN_REJECT],\n\n},\n\nbaseAddress: oracleAccount,\n\n},\n\n})\n\nCreating a Collection with an Oracle Plugin\nCreating a Collection with an Oracle Plugin\n\nimport { generateSigner, publicKey } from '@metaplex-foundation/umi'\n\nimport {\n\ncreate,\n\nCheckResult\n\n} from '@metaplex-foundation/mpl-core'\n\nconst collectionSigner = generateSigner(umi)\n\nconst oracleAccount = publicKey('11111111111111111111111111111111')\n\nconst collection = await createCollection(umi, {\n\n... CreateCollectionArgs,\n\nplugins: [\n\n{\n\ntype: 'Oracle',\n\nresultsOffset: {\n\ntype: 'Anchor',\n\n},\n\nbaseAddress: oracleAccount,\n\nlifecycleChecks: {\n\nupdate: [CheckResult.CAN_REJECT],\n\n},\n\nbaseAddressConfig: undefined,\n\n},\n\n],\n\n});.sendAndConfirm(umi)\n\nAdding an Oracle Plugin to a Collection\nAdding an Oracle Plugin to a Collection\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nimport { addCollectionPlugin, CheckResult } from '@metaplex-foundation/mpl-core'\n\nconst collection = publicKey('11111111111111111111111111111111')\n\nconst oracleAccount = publicKey('22222222222222222222222222222222')\n\nawait addCollectionPlugin(umi, {\n\ncollection: collection,\n\nplugin: {\n\ntype: 'Oracle',\n\nresultsOffset: {\n\ntype: 'Anchor',\n\n},\n\nlifecycleChecks: {\n\nupdate: [CheckResult.CAN_REJECT],\n\n},\n\nbaseAddress: oracleAccount,\n\n},\n\n}).sendAndConfirm(umi)\n\nDefault Oracles deployed by Metaplex\nIn some rare cases like Soulbound NFT it might be useful to have Oracles that always Deny or Approve a lifecycle event. For those the following Oracles have been deployed and can be used by anyone:\nTransfer Oracle: Always denies transferring. AwPRxL5f6GDVajyE1bBcfSWdQT58nWMoS36A1uFtpCZY\nUpdate Oracle: Always denies updating. 6cKyMV4toCVCEtvh6Sh5RQ1fevynvBDByaQP4ufz1Zj6\nCreate Oracle: Always denies creating. 2GhRFi9RhqmtEFWCwrAHC61Lti3jEKuCKPcZTfuujaGr\nExample Usage/Ideas\nExample 1\nAssets to be not transferable during the hours of noon-midnight UTC.\nCreate onchain Oracle Plugin in a program of your choice.\nAdd the Oracle Plugin Adapter to an Asset or Collection specifying the lifecycle events you wish to have rejection validation over.\nYou write a cron that writes and updates to your Oracle Plugin at noon and midnight flipping a bit validation from true/false/true.\nExample 2\nAssets can only be updated if the floor price is above $10 and the asset has attribute “red hat”.\nCreate onchain Oracle Plugin in a program of your choice.\nAdd the Oracle Plugin Adapter to Asset specifying the lifecycle events you wish to have rejection validation over.\nDev writes Anchor program that can write to the Oracle Account that derive the same PRECONFIGURED_ASSET accounts\nDev writes web2 script that watches prices on a marketplace, AND with known hashlist of Assets with the 'Red Hat' trait red updates and writes to the relevant Oracle Accounts.\nCommon Errors\nOracle validation failed\nThe Oracle account returned a rejection. Check your Oracle account state and validation logic.\nOracle account not found\nThe Oracle account address is invalid or doesn't exist. Verify the base address and any PDA derivation.\nInvalid results offset\nThe ValidationResultsOffset doesn't match your Oracle account structure. Use Anchor for Anchor programs, NoOffset for raw accounts.\nNotes\nOracle accounts are external. You deploy and maintain them\nValidation is read-only: Core reads the Oracle, doesn't write to it\nUse cron jobs or event listeners to update Oracle state dynamically\nPDA derivation allows per-asset, per-owner, or per-collection oracles\nFAQ\nCan Oracle plugins approve transfers, or only reject?\nOracle plugins can only reject or pass. They cannot force-approve transfers that other plugins reject.\nHow do I create time-based transfer restrictions?\nDeploy an Oracle account and use a cron job to update the validation result at specific times. See Example 1 above.\nCan I use one Oracle for multiple Assets?\nYes. Use a static base address for a single Oracle, or use PDA derivation with PreconfiguredCollection for collection-wide validation.\nWhat's the difference between Oracle and Freeze Delegate?\nFreeze Delegate is built-in and binary (frozen/unfrozen). Oracle allows custom logic—time-based, price-based, or any condition you implement.\nDo I need to write a Solana program for Oracle?\nYes. The Oracle account must be a Solana account with the correct structure. You can use Anchor or native Rust. See the Oracle Plugin Example guide.\nGlossary\nTermDefinition\nOracle Account\nExternal Solana account storing validation results\n\nOracle Adapter\nPlugin component attached to Asset referencing the Oracle\n\nValidationResultsOffset\nByte offset to locate validation data in Oracle account\n\nExtraAccount\nPDA derivation configuration for dynamic Oracle addressing\n\nLifecycle Check\nConfiguration specifying which events the Oracle validates\n\nRelated Pages\nExternal Plugins Overview - Understanding external plugins\nAppData Plugin - Data storage instead of validation\nOracle Plugin Example - Complete implementation guide\nFreeze Delegate - Built-in freeze alternative","tokens":3230,"crawled_at":1791195462433}
+{"id":10525,"url":"https://docs.ethena.fi/technical-design/use-of-oracles","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Use of Oracles | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nOverview\n\"Oracles\" typically refer to price feeds a protocol utilizes to perform key business logic and functions. Ethena utilizes price feeds from various sources given the importance of real-time data to trading & risk workflows which exist offchain.\nThe system is split between onchain and offchain components.\nPrice Feeds & Ethena's Offchain Systems\nEthena relies on price feeds in order to price the mint and redeem USDe requests per the available derivatives market liquidity as well as manage the risk of derivatives positions. Real-time data feeds indicate not only where the system delegates protocol assets, but the various risk profiles between the exchanges.\nWith this in mind, it's critically important that Ethena has access to & is constantly consuming real-time price feeds, especially from where it matters most; the exchanges where the system holds derivatives positions due to their margin requirements.\nEthena consumes real-time pricing information from three primary sources:\n\nCeFi Exchanges such as Binance, Bybit, Okx, Deribit, Bitmex and Bitget.\n\nPyth.\n\nRedstone\n\nThis real-time data is used extensively throughout the system to apply business logic, but to also ensure the integrity of all actions.\nIn that way, the system relies heavily upon CeFi Exchange price feeds, given the volume-weighted importance of their traded instruments, and also upon Pyth and Redstone to validate internal pricing throughout the system and before every single mint and redeem USDe request is accepted by Ethena. This ensures thorough checks for any inconsistency and protect the protocol from manipulation that might be occurring from one/multiple sources.\nEthena is constantly working to provide the resilience and integrity of price sources and evaluating other low latency offchain pricing services.\n\nLast updated 1 year ago\nWas this helpful?","tokens":487,"crawled_at":1791195443421}
+{"id":10526,"url":"https://blog.trailofbits.com/categories/tool-release","domain":"blog.trailofbits.com","chapter":"security_audits","title":"tool-release - The Trail of Bits Blog","text":"In April we released Mewt, our open-source mutation-testing engine that finds the gaps in your test suite. Today we’re expanding it with support for DAML, the language Canton Network applications are written in.\nWe built gosentry, a fuzzing-oriented fork of the Go toolchain that keeps the standard fuzzing workflow while using a stronger stack underneath.\nWe added LibAFL support to Ruzzy, our coverage-guided fuzzer for pure Ruby code and Ruby C extensions. This gives Ruby developers and security researchers access to a more advanced and actively maintained fuzzing engine without changing how they write their fuzzing harnesses.\nTrailmark turns source code into a security-analysis graph, powering eight Claude Code skills for blast radius, taint propagation, and mutation test triage.\nWe’re releasing CoBRA, an open-source tool that simplifies the full range of Mixed Boolean-Arithmetic (MBA) expressions used in the wild.\nToday, we’re announcing MuTON and mewt, two new mutation testing tools optimized for agentic use.\nWe released a Claude plugin that uses LLMs to annotate code with dimensional types and mechanically detect mismatches, achieving 93% recall versus 50% for baseline prompts when tested against real audit findings.\nWe’re open-sourcing mquire, a tool that analyzes Linux memory dumps without requiring any external debug information.\nWe’re releasing go-panikint, a modified Go compiler that turns silent integer overflows into explicit panics. We used it to find a live integer overflow in the Cosmos SDK’s RPC pagination logic, showing how this approach eliminates a major blind spot for anyone fuzzing Go projects.\nOur new tool mrva is a terminal-first tool for running CodeQL multi-repository variant analysis locally,allowing users to download pre-built databases, analyze them with custom queries, and view results directly in the terminal.\nWe’re releasing Slither-MCP, a new tool that augments LLMs with Slither’s unmatched static analysis engine.\nChecksec Anywhere consolidates fragmented binary security analysis tools into a browser-based platform that analyzes ELF, PE, and Mach-O formats locally without compromising privacy or performance.\nWe’ve added a pickle file scanner to Fickling that uses an allowlist approach to protect AI/ML environments from malicious pickle files that could compromise models or infrastructure.\nNow that DARPA’s AI Cyber Challenge (AIxCC) has officially ended, we can finally make Buttercup, our CRS (Cyber Reasoning System), open source!\nToday we’re announcing the beta release of mcp-context-protector, a security wrapper for LLM apps using the Model Context Protocol (MCP). It defends against the line jumping attacks documented earlier in this blog series, such as prompt injection via tool descriptions and ANSI terminal escape codes.\nVendetect is our new open-source tool for detecting copied and vendored code between repositories. It uses semantic fingerprinting to identify similar code even when variable names change or comments disappear. More importantly, unlike academic plagiarism detectors, it understands version control history, helping you trace vendored code back to its exact source commit.\nDeptective, our new open-source tool, automatically finds the packages needed to install software dependencies. It does so not based on the software’s self-reported requirements, but by observing what the software needs at runtime.\nThe Fiat-Shamir transform is an important building block in zero-knowledge proofs (ZKPs) and multi-party computation (MPC). It allows zero-knowledge proofs based on interactive protocols to be made non-interactive. Essentially, it turns conversations into documents. This ability is at the core of powerful technologies like SNARKs and STARKs. Useful stuff! But the Fiat-Shamir […]\nTrail of Bits is excited to introduce Ruzzy, a coverage-guided fuzzer for pure Ruby code and Ruby C extensions. Fuzzing helps find bugs in software that processes untrusted input. In pure Ruby, these bugs may result in unexpected exceptions that could lead to denial of service, and in Ruby C extensions, they […]\nToday, we’re releasing SARIF Explorer, the VSCode extension that we developed to streamline how we triage static analysis results. We make heavy use of static analysis tools during our audits, but the process of triaging them was always a pain. We designed SARIF Explorer to provide an intuitive UI inside VSCode, with […]\nToday, we’re releasing weAudit, the collaborative code-reviewing tool that we use during our security audits. With weAudit, we review code more efficiently by taking notes and tracking bugs in a codebase directly inside VSCode, reducing our reliance on external tools, ensuring we never lose track of bugs we find, and enabling us […]\nToday, Trail of Bits is publishing Attacknet, a new tool that addresses the limitations of traditional runtime verification tools, built in collaboration with the Ethereum Foundation. Attacknet is intended to augment the EF’s current test methods by subjecting their execution and consensus clients to some of the most challenging network conditions […]\nOriginally published May 20, 2021 This blog post introduces Dylint, a tool for loading Rust linting rules (or “lints”) from dynamic libraries. Dylint makes it easy for developers to maintain their own personal lint collections. Previously, the simplest way to write a new Rust lint was to fork Clippy, Rust’s […]","tokens":1358,"crawled_at":1791195454585}
+{"id":10527,"url":"https://docs.sui.io/getting-started/dev-cheat-sheet","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Developer Cheat Sheet | Sui Documentation","text":"Quick reference on best practices for Sui Network developers.\n\nMoveMoveAn open source programming language used for all activity on Sui.​\n\nBest practices for writing Move smart contracts on Sui.\n\nGeneral​\n\nRead the Code Quality Checklist for best practices in Move development.\n\nFollow the Move conventions for consistent naming and coding style.\n\nUse vector-backed collections (vector, VecSet, VecMap, PriorityQueue) with a known maximum size of 1000 items or fewer.\n\nUse dynamic field-backed collections (Table, Bag, ObjectBag, ObjectTable, LinkedTable) for any collection that allows third-party addition, larger collections, and collections of unknown size.\n\nMove objects have a maximum size of 250KB. Any attempt to create a larger objectObjectThe basic unit of storage on Sui. causes an aborted transactionTransactionA number of commands that execute on inputs to define the result of the transaction.. Ensure that your objects do not have an ever-growing vector-backed collection.\n\nIf your function f needs a payment in, for example, SUI from the caller, use fun f(payment: Coin<SUI>) not fun f(payment: &mut Coin<SUI>, amount: u64). This is safer for callers; they know exactly how much they are paying, and do not need to trust f to extract the right amount.\n\nUse the capability pattern for access control instead of addressAddressA unique, anonymous identity on a blockchain network. checks. Define capability objects like AdminCap or MintCap with the key ability, require them as function parameters for privileged operations, transferTransferChanging the owner of an asset. them to delegate access, and destroy them to revoke access. This is more composable than tx_context::sender() checks because other modulesModuleA component of a Move package that defines interaction with on-chain objects. can hold and pass capabilities on a user's behalf.\n\nComposability​\n\nUse Sui Object Display to customize how your objects appear in wallets, apps, and explorers.\n\nAvoid self-transfers. When possible, return the object from the current function so that it can be used in a different command in a programmable transaction block.\n\nPackagePackageSmart contracts on Sui. upgrades​\n\nRead about package upgrades before publishing your package.\n\nPackages are immutable, so any published package can be called forever. Use object versioning to prevent older versions from being called.\n\nIf you upgrade a package P1 to P2, other packages and clients that depend on P1 will continue using P1. They do not auto-update to P2. Both dependent packages and client code must be explicitly updated to point at P2.\n\nPackages that expect to be extended by dependent packages can avoid breaking their extensions with each upgrade by providing a standard (unchanging) interface that all versions conform to. See the message sending across a bridge example from Wormhole. Extension packages that produce outbound messages can use prepare_message from any version of the Wormhole package to produce a MessageTicket while client code that sends the message must pass that MessageTicket into publish_message in the latest version of the package.\n\npublic function signatures cannot be deleted or changed, but public(package) functions can. Use public(package) or private visibility liberally unless you are exposing library functions that will live forever.\n\nIt is not possible to delete struct types, change their definition, or add new abilities through an upgrade. Introduce new types carefully because they live forever.\n\nTesting​\n\nUse the sui::test_scenario module to mimic multi-transaction, multi-sender test scenarios.\n\nUse the std::unit_test module for assert_eq! and assert_ref_eq! macros and the destroy function for cleaning up objects in tests.\n\nUse the std::debug module for debug printing through print.\n\nUse sui move test --coverage to compute code coverage information for your tests, and sui move coverage source --module <name> to see uncovered lines highlighted in red. Push coverage all the way to 100% if feasible.\n\nUse sui move lint to run the Move linter on your package and catch common issues and anti-patterns before publishing.\n\nApps​\n\nFor optimal performance and data consistency, submit writes and reads to the same full nodeFull nodeResponsible for validating blockchain activity.. In the TS SDK, use the wallet's signTransactionBlock API, then submit the transaction through a call to execute_transactionBlock on your app's full node instead of using the wallet's signAndExecuteTransactionBlock API. This ensures read-after-write consistency. Reads from your app's full node reflect writes from the transaction right away instead of waiting for a checkpointCheckpointCreated after transaction execution to provide a certified record of chain history..\n\nImplement a local cache for frequently read data rather than over-fetching from the full node.\n\nWhenever possible, use programmable transaction blocksProgrammable transaction blocksDefine all user transactions on Sui. to compose existing onchain functionality rather than publishing new smart contract code. Programmable transaction blocks allow large-scale batching and heterogeneous composition, driving already-low gasGasThe computational cost of execution and object storage for a transaction. fees down even further.\n\nLeave gas budget, gas price, and coin selection to the wallet. This gives wallets more flexibility, and the wallet is responsible for dry running a transaction to ensure it does not fail.\n\nSigning​\n\nDo not sign two concurrent transactions that touch the same mutable owned object. Either use independent owned objects, combine related operations into one PTB, or wait for one transaction to conclude before sending the next one.\n\nAny sui client command that crafts a transaction (for example, sui client publish or sui client call) can accept the --serialize-output flag to output a base64 transaction for signing.\n\nSui supports several signature schemes for transaction signing, including native multisigMultisigMulti-signature transactions that require multiple keys for authorization..\n\nzkLoginzkLoginA Sui primitive that allows you to send transactions using an OAuth credential.​\n\nCall the proving service as sparingly as possible. Design your app flows such that you call the proving service only when the user is about to perform a real transaction.\n\nBeware of how you cache the ephemeral private key. Treat the private key as highly sensitive data, such as a password. If an unexpired ephemeral private key and its corresponding ZK proof are leaked, an attacker can steal the user's assets.\n\nRelated topics\n\nMove Best Practices\nRecommended Move best practices for Sui development.\nBuilding Transactions\nUsing the Sui TypeScript SDK, you can create programmable transaction blocks to perform multiple commands in a single transaction.\nUpgrading Packages\nUpgrade a published Move package on Sui using the Sui CLI, understand layout-compatibility requirements, manage UpgradeCap and UpgradeTicket, and apply custom upgrade policies to control what changes are permitted.\nExecuteTransaction\n\nMoveGeneral\nComposability\nPackage upgrades\nTesting\n\nApps\nSigning\nzkLogin\n\nWas this page helpful?","tokens":1795,"crawled_at":1791195458569}
+{"id":10528,"url":"https://docs.ethena.fi/video-guides/how-to-un-lock-positions","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"How to [Un]lock positions | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nUsers in permitted jurisdictions can lock & unlock positions with Ethena via the UI.\nUsing the UI, the locking & unlocking positions user workflow is:\n\nThe user requests to lock/unlock positions via the dApp interface by clicking \"Lock\"/\"Unlock\", which pops up their selected wallet to sign the requested transaction.\n\nAfter the user signs the transaction with their wallet, the transaction is submit to the blockchain, if successful, the cooldown period starts.\n\nOnce the cooldown period ends, the user now needs to click on \"Withdraw\" and sign a second transaction.\n\nUpon successful confirmation of the transaction, the user receives unlocked tokens.\n\nImportant to Note\n\nThere is a cooldown period of 7 days after unlocking USDe, USDe will be available to withdraw after that period.\n\nThere is a cooldown period of 7 days after unlocking sENA, sENA will be available to withdraw after that period. This is in addition to the 7 day sENA unstaking cooldown.\n\nThere is a cooldown period of 21 days after unlocking LP tokens, these LP tokens will be available to withdraw after that period. Some LP tokens have no cooldown and can be withdrawn immediately.\n\nLast updated 2 months ago\nWas this helpful?","tokens":323,"crawled_at":1791195463842}
+{"id":10529,"url":"https://www.youtube.com/@solana","domain":"www.youtube.com","chapter":"developer_specs","title":"Solana - YouTube","text":"Solana\n@solana\n•95.6k subscribers•2.2k videos\nThe high performance network powering internet capital markets, payments, and crypto applications. Subscribe for updates, video podcast episodes, developer guides, event highlights and more. The high performance network powering internet capital markets, payments, and crypto applications. Subscribe for updates, video podcast episodes, developer guides, event highlights and more. solana.comand 5 more links\n\nHome\n\nVideos\n\nShorts\n\nLive\n\nPodcasts\n\nPlaylists\n\nPosts\n\nSearch\n\nSolana Stories\n\nPlay all\n\nStories about the founders and people who make the Solana community what it is today.\n\n1:09\n\nSolana Stories: Comic-Con meets Wall Street\nSolana\n778 9 days ago\n\n2:14\n\nSolana Stories: We Bought A Bank\nSolana\n1.1k 2 mo ago\n\n2:12\n\nSolana Stories: Crypto Never Sleeps\nSolana\n390 2 mo ago\n\n2:11\n\nSolana Stories: The Agents Are Here\nSolana\n1.1k 4 mo ago\n\n1:36\n\nSolana Stories: The First Touchpoint\nSolana\n317 4 mo ago\n\n2:08\n\nSolana Stories: The Founder\nSolana\n508 5 mo ago\n\nSolana Accelerate USA 2026\n\nPlay all\n\n21:53\n\nAccelerate USA 2026: Anatoly Yakovenko\nSolana\n1.7k 4 mo ago\n\n13:45\n\nAccelerate USA 2026: MoonPay's Ivan Soto-Wright\nSolana\n1.7k 4 mo ago\n\n13:02\n\nAccelerate USA 2026: Sen. Bernie Moreno\nSolana\n244 4 mo ago\n\n14:19\n\nAccelerate USA 2026: Arjun Sethi\nSolana\n1.7k 4 mo ago\n\n7:33\n\nAccelerate USA 2026: Jito's Lucas Bruder\nSolana\n190 4 mo ago\n\n10:46\n\nAccelerate USA 2026: Building the Future of Agentic Payments with Google Cloud\nSolana\n292 4 mo ago\n\nAccelerate APAC 2026\n\nPlay all\n\n3:56\n\nAccelerate APAC 2026: Welcome to Solana Accelerate APAC\nSolana\n833 7 mo ago\n\n2:07\n\nAccelerate APAC 2026: Opening\nSolana\n220 7 mo ago\n\n21:24\n\nAccelerate APAC 2026: Opening Fireside\nSolana\n165 7 mo ago\n\n9:47\n\nAccelerate APAC 2026: Partnering to Build Next-Gen Financial Infrastructure For Onchain Assets\nSolana\n114 7 mo ago\n\n23:58\n\nAccelerate APAC 2026: ETF from East to West\nSolana\n91 7 mo ago\n\n7:00\n\nAccelerate APAC 2026: Bridging The Gap\nSolana\n61 7 mo ago\n\nSolana Breakpoint 2025\n\n199 videos\n\nBreakpoint 2025: All Talks\nSolana Playlist\nView full playlist\n\n19 videos\n\nBreakpoint 2025: Lock In Stage | Day 1\nSolana Playlist\nView full playlist\n\n37 videos\n\nBreakpoint 2025: Absolute Cinema Stage | Day 1\nSolana Playlist\nView full playlist\n\n41 videos\n\nBreakpoint 2025: Absolute Cinema Stage | Day 2\nSolana Playlist\nView full playlist\n\n27 videos\n\nBreakpoint 2025: Lock In Stage | Day 2\nSolana Playlist\nView full playlist\n\n44 videos\n\nBreakpoint 2025: Absolute Cinema Stage | Day 3\nSolana Playlist\nView full playlist\n\nWhy We Ship\n\nPlay all\n\n2:58\n\nWhy We Ship: Beezie\nSolana\n932 1 mo ago\n\n2:47\n\nWhy We Ship: DoubleZero & Malbec Labs\nSolana\n700 2 mo ago\n\n1:55\n\nWhy We Ship: GolfN\nSolana\n351 3 mo ago\n\n2:36\n\nWhy We Ship: Kled\nSolana\n328 5 mo ago\n\n2:03\n\nWhy We Ship: DFlow\nSolana\n264 5 mo ago\n\n2:48\n\nWhy We Ship: Decal\nSolana\n559 5 mo ago\n\nDePIN on Solana\n\nPlay all\n\n2:20\n\nDePIN on Solana: Dawn Internet's Decentralized Broadband Network with Andrena CEO Neil Chatterjee\nSolana\n2.7k 1 yr ago\n\n3:22\n\nDePIN on Solana: Render's Decentralized Compute Network with Jules Urbach and Trevor Harries-Jones\nSolana\n1.3k 1 yr ago\n\n1:34\n\nDePIN on Solana: Gradient's Edge Node Compute Network with co-founder Yuan Gao\nSolana\n1.4k 1 yr ago\n\n2:11\n\nDePIN on Solana: Dabba Wireless Network in India with cofounders Shubhendu Sharma & Karam Lakshman\nSolana\n855 1 yr ago\n\n2:29\n\nDePIN on Solana: Jambo's $99 Crypto Phone Expanding Financial Inclusion ft. CEO James Zhang\nSolana\n1.2k 1 yr ago\n\n2:07\n\nDePIN on Solana: Cudis Wearable AI Smart Ring with Founder Edison Chen\nSolana\n1.2k 1 yr ago\n\nSolana Developer Bootcamp 2026\n\nPlay all\n\n5:11:42\n\nSolana Developer Bootcamp 2026: Learn Blockchain and Full-Stack Crypto Development [Full Course]\nSolana\n40k 5 mo ago","tokens":942,"crawled_at":1791195475236}
+{"id":10530,"url":"https://docs.sui.io/develop/transactions/ptbs/building-ptb","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Building Transactions | Sui Documentation","text":"This guide explores creating a programmable transaction block (PTB) on Sui using the TypeScript SDK and the Sui CLI.\n\nThis example constructs a PTBProgrammable transaction blocksDefine all user transactions on Sui. to send SUI tokens. First, import the Transaction class, and construct it:\n\nimport { Transaction } from '@mysten/sui/transactions';\n\nconst tx = new Transaction();\n\nUsing this, you can then add transactions to the PTB:\n\n// Send 100 MIST to the recipient's address balance. tx.balance() draws from the\n// sender's coin objects and address balance, so you do not select coins yourself.\ntx.moveCall({\ntarget: '0x2::balance::send_funds',\ntypeArguments: ['0x2::sui::SUI'],\narguments: [tx.balance({ balance: 100n }), tx.pure.address('0xSomeSuiAddress')],\n});\n\nA balance transferTransferChanging the owner of an asset. creates no new objects for the recipient to manage. When the recipient needs a Coin<T> objectObjectThe basic unit of storage on Sui. instead, such as a payment a downstream MoveMoveAn open source programming language used for all activity on Sui. call consumes, use tx.coin() with transferObjects:\n\ntx.transferObjects([tx.coin({ balance: 100n })], '0xSomeSuiAddress');\n\nYou can attach multiple transactionTransactionA number of commands that execute on inputs to define the result of the transaction. commands of the same type to a PTB. For example, to get a list of transfers, and iterate over them to transfer coins to each:\n\ninterface Transfer {\nto: string;\namount: number;\n}\n\n// Procure a list of some Sui transfers to make:\nconst transfers: Transfer[] = getTransfers();\n\nconst tx = new Transaction();\n\n// tx.coin() sources each amount for you, so there is no split step to manage.\ntransfers.forEach((transfer) => {\ntx.transferObjects([tx.coin({ balance: BigInt(transfer.amount) })], transfer.to);\n});\n\nAfter you define the transaction, directly execute it with a Sui client and KeyPair using client.signAndExecuteTransaction.\n\nclient.signAndExecuteTransaction({ signer: keypair, transaction: tx });\n\nBuild PTBs with the CLI​\n\nUse sui client ptb to build and execute PTBs from the command line. Prefer sui client ptb for examples that build transactions, including basic transfers and coin operations, because it exposes the same PTB commands used by SDKs.\n\nThe following CLI PTB splits 500,000,000 MISTMISTThe smallest unit of SUI. from the gasGasThe computational cost of execution and object storage for a transaction. coin and transfers the new coin to eloquent-amber:\n\n$ sui client ptb \\\n--split-coins gas \"[500000000]\" \\\n--assign coin \\\n--transfer-objects \"[coin]\" eloquent-amber \\\n--gas-budget 5000000\n\nUse --preview to inspect the PTB commands without executing them, --dry-run to simulate execution, and --summary for concise output after execution. For more examples, see Sui Client PTB CLI.\n\nConstructing inputs​\n\nInputs are how you provide external values to PTBs, for example, an amount of SUI to transfer, an object to pass into a Move call, or a shared object.\n\nDefine inputs in two ways:\n\nFor objects: Use the tx.object(objectId) function to construct an input that contains an object reference.\n\nFor pure values: Use the tx.pure(type, value) function to construct an input for a non-object input.\n\nIf value is a Uint8Array, the function treats it as raw bytes and uses it directly: tx.pure(SomeUint8Array).\n\nOtherwise, the function generates the BCS serialization layout for the value.\n\nThe new version provides a more intuitive syntax, for example: tx.pure.u64(100), tx.pure.string('SomeString'), tx.pure.address('0xSomeSuiAddress'), tx.pure.vector('bool', [true, false]).\n\nLearn more about inputs.\n\nPassing transaction results as arguments​\n\nYou can use the result of a transaction command as an argument in subsequent transaction commands. Each transaction command method on the transaction builder returns a reference to the transaction result.\n\n// Split a coin object off of the gas object:\nconst [coin] = tx.splitCoins(tx.gas, [tx.pure.u64(100)]);\n// Transfer the resulting coin object:\ntx.transferObjects([coin], tx.pure.address(address));\n\nWhen a transaction command returns multiple results, you can access the result at a specific index either using destructuring or array indexes.\n\n// Destructuring (preferred, as it gives you logical local names):\nconst [nft1, nft2] = tx.moveCall({ target: '0x2::nft::mint_many' });\ntx.transferObjects([nft1, nft2], tx.pure.address(address));\n\n// Array indexes:\nconst mintMany = tx.moveCall({ target: '0x2::nft::mint_many' });\ntx.transferObjects([mintMany[0], mintMany[1]], tx.pure.address(address));\n\nUse the gas coin​\n\nFor most transactions, reach for tx.coin() and tx.balance() rather than the gas coin. They are the recommended way to source tokens, and they draw from coin objects and addressAddressA unique, anonymous identity on a blockchain network. balances without you selecting either.\n\ntx.gas still matters when you want the gas coin specifically, and it is valid as input for any argument.\n\ntx.gas is available whichever way the transaction pays for gas. When you supply coin objects, the protocol smashes them into a single gas coin. When you pass an empty array to setGasPayment([]) to draw gas from an address balance, the protocol materializes a synthetic gas coin from the sender's or sponsor's balance. tx.gas refers to that coin in either case, so building against it does not force client-side coin or balance resolution. That matters for offline building, where an unresolved tx.coin() or tx.balance() intent would need a balance lookup.\n\nYou can borrow the gas coin by reference freely: add to it with mergeCoins, split from it with splitCoins, or pass it to a Move function with moveCall. Consuming it by value is restricted to 2 commands:\n\ntransferObjects, to send the whole remaining balance to another address.\n\nsui::coin::send_funds, to deposit it into an address balance.\n\nAny other by-value use fails with InvalidGasCoinUsage.\n\nYou can also split from and transfer other coins in your wallet using their object ID. For example,\n\nconst otherCoin = tx.object('0xCoinObjectId');\n// splitCoins returns an array of coins, so destructure the first result.\nconst [coin] = tx.splitCoins(otherCoin, [tx.pure.u64(100)]);\ntx.transferObjects([coin], address);\n\nGet PTB bytes​\n\nIf you need the PTB bytes, instead of signing or executing the PTB, you can use the build method on the transaction builder itself.\n\ntip\nYou might need to explicitly call setSender() on the PTB to ensure that the sender field is populated. This is normally done by the signer before signing the transaction, but will not be done automatically if you're building the PTB bytes yourself.\n\nconst tx = new Transaction();\n\n// ... add some transactions...\n\nawait tx.build({ client });\n\nIn most cases, building requires a client to resolve input values such as object versions and coin selection. If you have PTB bytes, you can also convert them back into a Transaction class:\n\nconst bytes = getTransactionBytesFromSomewhere();\nconst tx = Transaction.from(bytes);\n\nBuilding offline​\n\nTo build a PTB offline, with no client available, define all input values and gas configuration yourself. For pure values, provide a Uint8Array, which the transaction uses directly. For objects, construct the reference explicitly.\n\n// For pure values:\ntx.pure(pureValueAsBytes);\n\n// For owned or immutable objects, supply the exact version and digest:\ntx.objectRef({ objectId, version, digest });\n\n// For shared and party objects, initialSharedVersion is stable:\ntx.sharedObjectRef({ objectId, initialSharedVersion, mutable });\n\nEvery offline build must also set the sender, gas price, gas budget, and gas payment. When the transaction uses no owned objects for gas or inputs, such as when setGasPayment([]) draws gas from an address balance, set a ValidDuring expiration as well.\n\nYou can then omit the client argument when calling build on the transaction. If any required data is missing, build throws an error.\n\nGas configuration​\n\nThe transaction builder comes with default behavior for all gas logic, including automatically setting the gas price, budget, and selecting coins to be used as gas. This behavior can be customized.\n\nGas price​\n\nBy default, the SDK sets the gas price to the reference gas price of the network. You can also explicitly set the gas price of the PTB by calling setGasPrice on the transaction builder:\n\ntx.setGasPrice(gasPrice);\n\nBudget​\n\nBy default, the SDK automatically derives the gas budget by executing a dry-run of the PTB beforehand. The SDK then uses the dry run gas consumption to determine a balance for the transaction. You can override this behavior by explicitly setting a gas budget for the transaction using the setGasBudget on the transaction builder.\n\ninfo\nSet the gas budget in MIST, not SUI. 1 SUI is 1,000,000,000 MIST, so tx.setGasBudget(50_000_000) caps the transaction at 0.05 SUI. Take the gas price of the PTB into account when choosing a value.\n\ntx.setGasBudget(gasBudgetAmount);\n\nGas payment​\n\nBy default, the SDK automatically determines the gas payment. It selects all coins at the provided address that are not used as inputs in the PTB.\n\nThe SDK merges the list of coins used as gas payment down into a single gas coin before executing the PTB, and deletes all but 1 of the gas objects. The gas coin at the 0-index is the coin that all others are merged into.\n\n// NOTE: You need to ensure that the coins do not overlap with any\n// of the input objects for the PTB.\ntx.setGasPayment([coin1, coin2]);\n\nGas coins should be objects containing the coin's { objectId: string, version: string | number, digest: string }.\n\nApp and wallet integration​\n\nThe Wallet StandardWallet StandardA cross-chain standard that defines how apps can interact with wallets. interface now supports the Transaction kind directly. All signTransaction and signAndExecuteTransaction calls from apps into wallets must provide a Transaction class. You can then serialize this PTB class and send it to your wallet for execution.\n\nTo serialize a PTB for sending to a wallet, Sui recommends using the tx.serialize() function, which returns an opaque string representation of the PTB that can be passed from the Wallet Standard app context to your wallet. You can then convert this back into a Transaction using Transaction.from().\n\ntip\nYou should not build the PTB from bytes in the app code. Using serialize instead of build allows you to build the PTB bytes within the wallet itself. This allows the wallet to perform gas logic and coin selection as needed.\n\n// Within an app\nconst tx = new Transaction();\nwallet.signTransaction({ transaction: tx });\n\n// Your Wallet Standard code:\nfunction handleSignTransaction(input) {\nsendToWalletContext({ transaction: input.transaction.serialize() });\n}\n\n// Within your wallet context:\nfunction handleSignRequest(input) {\nconst userTx = Transaction.from(input.transaction);\n}\n\nSponsored PTBs​\n\nThe PTB builder can support sponsored PTBs by using the onlyTransactionKind flag when building the PTB.\n\nconst tx = new Transaction();\n// ... add some transactions...\n\nconst kindBytes = await tx.build({ client, onlyTransactionKind: true });\n\n// Construct a sponsored transaction from the kind bytes:\nconst sponsoredTx = Transaction.fromKind(kindBytes);\n\n// You can now set the sponsored transaction data that is required:\nsponsoredTx.setSender(sender);\nsponsoredTx.setGasOwner(sponsor);\nsponsoredTx.setGasPayment(sponsorCoins);\n\nLearn more about sponsored transactions.\n\nRust SDK example​\n\nYou can also build PTBs using the Sui Rust SDK. The following example demonstrates creating a ProgrammableTransactionBuilder, adding pure value and shared object inputs, and calling a Move function with type arguments:\n\nuse move_core_types::{identifier::Identifier, language_storage::TypeTag};\nuse sui_types::{\nbase_types::ObjectID,\nprogrammable_transaction_builder::ProgrammableTransactionBuilder,\ntransaction::{Argument, CallArg, ObjectArg, SharedObjectMutability},\n};\n\nlet mut ptb = ProgrammableTransactionBuilder::new();\n\n// Pass a pure value\nlet amount = ptb.pure(1000u64)?;\n\n// Pass a shared object\nlet shared_obj = ptb.obj(ObjectArg::SharedObject {\nid: ObjectID::from_hex_literal(\"0x...\")?,\ninitial_shared_version: 1.into(),\nmutability: SharedObjectMutability::Mutable,\n})?;\n\n// Call a generic function with type arguments\nptb.programmable_move_call(\nObjectID::from_hex_literal(\"0xPACKAGE\")?,\nIdentifier::new(\"module\")?,\nIdentifier::new(\"function\")?,\nvec![TypeTag::U64], // type arguments (generics)\nvec![shared_obj, amount], // runtime arguments\n);\n\nPassing type arguments​\n\nGeneric Move functions require type parameters. Specify them as a Vec<TypeTag> in Rust or as string type tags in TypeScript:\n\ntx.moveCall({\ntarget: '0xPACKAGE::module::generic_function',\ntypeArguments: ['0x2::coin::Coin<0x2::sui::SUI>'],\narguments: [tx.object('0x...')],\n});\n\nTroubleshooting PTB errors​\n\nErrorCauseFix\nHTTP 504 (Gateway Timeout)\nRPC node overloaded or unresponsive.\nRetry with a different RPC endpoint or after a delay.\n\nMoveAbort in effects\nOnchain logic failed (assertion, type mismatch).\nCheck the abort code against the Move moduleModuleA component of a Move package that defines interaction with on-chain objects. source.\n\nInsufficientGas\nGas budget too low for the computation.\nIncrease setGasBudget() or use dry-run to estimate.\n\nwaitForTransaction​\n\nReads are served from indexed state, which trails execution. After you submit a transaction, use waitForTransaction before you query its effects. This prevents race conditions where querying immediately after submission returns no results.\n\nPass the execution result directly. signAndExecuteTransaction returns a discriminated union of Transaction and FailedTransaction, so the digest is not on the result itself.\n\nconst result = await client.signAndExecuteTransaction({ transaction: tx, signer: keypair });\n\nawait client.waitForTransaction({ result });\n\nconst transaction = result.Transaction ?? result.FailedTransaction;\nconst txn = await client.getTransaction({\ndigest: transaction.digest,\ninclude: { effects: true },\n});\n\nFor end-to-end recipes covering sponsored transactionsSponsored transactionWhen one address pays the gas fee for a transaction submitted by another address., kioskKioskA decentralized system for commerce applications on Sui. operations, coin selection, and multi-recipient transfers, see the PTB Cookbook.\nRelated topics\n\nWhat is a PTB?\nProgrammable transaction blocks are a group of commands that complete a transaction on Sui.\nSui Client PTB CLI\nThe Sui Client PTB CLI enables a user to construct a PTB and execute it from the command line or a file.\nUsing Address Balances\nAddress balances introduce a canonical balance system for fungible assets tied to Sui addresses. Learn how to send, withdraw, and query address balances.\nSigning and Sending Transactions\nUnderstanding cryptographic keys, addresses, and signatures on Sui. Sui supports multiple cryptography algorithms and primitives with rapid switching between them.\n\nBuild PTBs with the CLI\nConstructing inputs\nPassing transaction results as arguments\nUse the gas coin\nGet PTB bytes\nBuilding offline\nGas configurationGas price\nBudget\nGas payment\nApp and wallet integration\n\nSponsored PTBs\nRust SDK examplePassing type arguments\n\nTroubleshooting PTB errorswaitForTransaction\n\nWas this page helpful?","tokens":3841,"crawled_at":1791195481191}
+{"id":10531,"url":"https://docs.sui.io/develop/write-move","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Writing Move Packages | Sui Documentation","text":"MoveMoveAn open source programming language used for all activity on Sui. is the smart contract language of the Sui blockchain. You write Move code organized into packagesPackageSmart contracts on Sui., which are the deployable units on Sui. Each package contains one or more modulesModuleA component of a Move package that defines interaction with on-chain objects., and each module defines types, functions, and logic that run onchain.\n\nWhat is a Move package?​\n\nA Move package is a directory with a Move.toml manifest file and a sources/ folder containing .move source files. The manifest declares the package name and edition. The source files define the modules that make up the package.\n\nA minimal package structure looks like this:\n\nmy_package/\n├── Move.toml\n└── sources/\n└── my_module.move\n\nCreate a new package with the Sui CLI:\n\nsui move new my_package\n\nA minimal Move.toml is all you need to get started:\n\n[package]\nname = \"my_package\"\nedition = \"2024\"\n\nWhat does a Move module look like?​\n\nA Move module declares a module name, imports dependencies, defines types, and implements functions. The following example defines a simple counter objectObjectThe basic unit of storage on Sui.:\n\nmodule my_package::counter;\n\nuse sui::event;\n\npublic struct Counter has key {\nid: UID,\nvalue: u64,\n}\n\npublic struct CounterIncremented has copy, drop {\nvalue: u64,\n}\n\nfun init(ctx: &mut TxContext) {\nlet counter = Counter {\nid: object::new(ctx),\nvalue: 0,\n};\ntransfer::transfer(counter, ctx.sender());\n}\n\npublic fun increment(counter: &mut Counter) {\ncounter.value = counter.value + 1;\nevent::emit(CounterIncremented { value: counter.value });\n}\n\nThis module uses Move 2024 syntax: the module label declaration (module my_package::counter;), method-style calls (ctx.sender() instead of tx_context::sender(ctx)), and direct field access. The Counter type has the key ability, which makes it a Sui object. The init function runs once at package publication and creates the initial counter.\n\nWhat are Move Packages?\nSui uses Move through three constructs. They are packages, modules, and objects.\n→\nMove Concepts\nMove is an open source language for writing safe packages to manipulate onchain objects.\n→\nMove Syntax Fundamentals\nA comprehensive reference for Move language syntax fundamentals, covering modules, types, structs, abilities, functions, generics, control flow, and more.\n→\nMove Best Practices\nRecommended Move best practices for Sui development.\n→\nMove Book\n↗\n\nWhat is a Move package?\nWhat does a Move module look like?\n\nWas this page helpful?","tokens":638,"crawled_at":1791195506032}
+{"id":10532,"url":"https://a16zcrypto.com/posts/article/personal-physical-security","domain":"a16zcrypto.com","chapter":"research","title":"Personal and physical security for founders, operators, and investors - a16z crypto","text":"Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nPersonal and physical security for founders, operators, and investors\nCarl Agnelli\n04.30.25\n\nTags & Share Tags\ncompany building\ncrypto basics\nsecurity\nsecurity best practices\n\nImagine your family being abducted from home, or being forced into a car at gunpoint, or having your finger amputated while your captors demand a ransom payment. These examples are distressing — gruesome, in some cases — but they’re not hypothetical. They’ve actually happened — and are happening — to people in crypto.\n\nI want to share practical lessons that can help keep you — crypto founders, operators, and investors — safe in an increasingly dangerous world. I’m going to go through two areas that are central to your safety. First, daily habits. And second, crypto industry-specific violent crime. But I’ll start with some general principles and a couple of illustrative stories.\n\nWhy take the time to talk about this? Founders, operators, and engineers are focused on building their companies. Investors are busy managing their portfolios. But if you’re not thinking about security — personal, physical security — none of that matters. And it’s not just about your safety. It’s about your teams. Your families. Your work. Security has to be part of your operating system.\n\nI’ve spent the last 35 years in the world of security. Twenty-five of those were in the U.S. Secret Service, where I served in many roles, including protecting every living U.S. president during that time. I’ve protected foreign heads of state (even the ones I disagreed with). The rule was simple: No one dies on U.S. soil.\n\nBut the Secret Service isn’t just about protection. It’s the only agency in the U.S. government with a dual mission: protection and investigations. Some of the best cyber investigators in the world start there. I worked global, transnational investigations, surveilled people, and was surveilled myself. You learn a lot of tradecraft doing that. You also become a student of people. You learn how to read them, spot tells, and identify threats before they happen.\n\nFoundational principles for personal security\n\nLet’s start with a few guiding ideas:\n\nAvoid conflict whenever possible. If someone’s acting strangely, move away. Switch train cars. Cross the street. Don’t be prideful. Your ego won’t save you.\n\nTrust your instincts. That uncomfortable feeling you get? It’s not random. It’s your autonomic nervous system warning you — rising heart rate, shallow breathing, perspiration. That’s your body trying to keep you alive. Listen to it.\n\nExpect the unexpected. We call them Murphy moments. When things go bad, they usually go bad fast. You can’t predict every scenario, but you can rehearse mentally. “What if?” is your best defense.\n\nInvest in your safety. We’ll spend two hours reading Amazon reviews before buying a water bottle. Spend five minutes learning how to secure your home when you’re away.\n\nSituational awareness: Living in the ‘yellow’\n\nIn the Secret Service, we used a color-coded system to describe how attentive people, aka targets (that’s you), are when they’re in public:\n\nWhite: Unaware, distracted — like walking with earbuds in. Vulnerable.\n\nYellow: Relaxed awareness. Alert but not paranoid. This is where you should live.\n\nOrange: Heightened alertness — used in active threat situations.\n\nBlack: Panic, paralysis. You don’t want to be here.\n\nIn the Secret Service, we talked a lot about something called “leaning into the yellow.” It means maintaining a relaxed state of awareness. Train yourself to stay in the yellow. You’re not paranoid, you’re just paying attention.\n\nMaybe you notice someone talking to themselves on a train. Or someone in a heavy coat on a 90-degree day. You don’t panic, but you do move. You don’t want to be in the white — tuned out with both earbuds in, buried in your phone. And you definitely don’t want to be in the black — frozen in panic.\n\nStay in the yellow.\n\nLearning the hard way: Two personal security stories\n\nLoose lips in public\n\nLast year, I was in Miami for Formula One. After the event, I went to a bar, not to party, just to grab a burger and a Diet Coke. I was sitting at a table, minding my own business, when I noticed a guy a few feet away. He was with three women, clearly enjoying himself, and clearly a little drunk.\n\nHe was loud. Charming, maybe, in a collegiate sort of way. But more importantly, he was talking. A lot. Within the first minute of listening — not intentionally, just by sitting nearby — I learned his first name. A minute after that, I got his last name. The women were talking about ancestry. He mentioned his Irish roots, someone joked about spelling, and he corrected them. Full name. Easy.\n\nHe was wearing a polo with his company logo embroidered on it. A racing team. He also mentioned his job out loud: what he did, who he worked for. Now I had his employer and his title.\n\nThen came the birthday. One of the women was celebrating hers, and he chimed in that his had just passed. She asked, “What day?” He told her. “You don’t look 50,” one of them said, teasing him. “Come on, I look great for 50,” he replied. That’s how I got his full date of birth: month, day, and year. I hadn’t even been served my burger yet.\n\nThe talk turned to where they were staying. The guy casually dropped that they were all in the same hotel. Then they started talking about the view from their rooms. One woman could see the pool, another could see the street. This guy then added, “We’re all on the 18th floor, right?” They laughed about being neighbors. Someone asked what room he was in. He said it, just like that.\n\nAt this point, I had a dossier on this person without ever speaking to him:\n\nFull name\n\nEmployer and job function\n\nDate of birth\n\nHotel\n\nFloor\n\nRoom number\n\nAll it would have taken was a confident walk to the front desk and a little social engineering: “Hey, I locked myself out of Room XXX, I left my ID upstairs, you can call my cell if you need to verify, etc.” If I were someone with bad intentions, I could have easily gotten a key. Best- case scenario, I clean out his room. Worst case, he comes back while I’m inside.\n\nNow, multiply that by a hundred. What if I were targeting someone? What if I had followed him from a public speaking event, or an industry conference, or simply searched for him online because he’s known in the crypto space? All that info he gave away for free — that’s exactly how people get compromised.\n\nHe was just trying to impress some people at a bar. But he gave up every security answer most companies would ever ask for. Date of birth, name, place of employment, room number. The kind of stuff that makes you incredibly vulnerable.\n\nThe moral of the story? Assume someone like me is always listening. Only I’m not the one you need to worry about — because unlike me the people who are listening could be out to get you. They’re listening, and they’re looking for their next easy mark. Don’t let it be you.\n\nCarl goes to a hockey game\n\nI don’t want to pick just on this random, drunk stranger in Miami. Let me tell you a story about when I ignored everything I knew about personal security.\n\nI went with friends to a Bruins playoff game in New Jersey. I was wearing a brand-new Bruins jersey over my work clothes — permitted gun holstered underneath. We were loud, having fun, probably saying a few things we shouldn’t have. The Bruins won. After the game, I was walking through the parking lot doing the Conor McGregor strut before that was even a thing.\n\nI looked around and realized: My friends were gone. I was in a sea of Devils fans, all in red. They were staring me down. I should go back to the arena, I thought.\n\nI didn’t. I kept walking.\n\nOne guy — taking off his red jersey, angry — starts coming toward me. He’s looking around, scanning, just like we used to do in the Secret Service before taking action. He’s checking for cops and exits. I knew the signs. I saw every one of them. And yet I ignored them.\n\nThis person walked right up to me and punched me in the face. I hit the ground. He broke my nose. I was rolling around with him, worried he’d get my gun, worried his friends would stomp me. I remember thinking: “This is how it ends? In a parking lot in East Rutherford, New Jersey?”\n\nThen, out of nowhere, my buddies showed up. Bodies flew. They pulled me out. I was bleeding. My nose was a mess. And they asked, “How the hell did this happen to you, of all people?”\n\nSimple. I put myself in a bad situation and ignored every single sign. The lesson is that it can happen to anyone — even someone who should know better.\n\nEveryday habits to stay safe\n\nA lot of the habits that keep you safe aren’t glamorous. It’s not tactical gear or Secret Service motorcades. It’s basic, boring habits. If you get them right, you will keep way safer than most people.\n\nHere’s what I mean.\n\nDon’t walk alone after drinking. If you do, tell someone your plan. This one’s so simple, but people mess it up constantly. You go out. You have a couple drinks. When it’s time to leave, you ghost your group and walk home. Happens all the time. If you’re going to drink, fine — but make sure someone knows where you’re going, how you’re getting there, and when to expect you. Text a friend. Share your location. Use your phone’s location-sharing features or a special app that helps track and share these details. Do whatever it takes.\n\nCarry non-lethal deterrents — but they only work if they’re in your hand. For example, get yourself a flashlight with a strobe function. That’s a real deterrent — but only if you’re holding it when you need it. The same goes for pepper spray. If it’s buried in your bag, it’s no good. You need to have it out and ready, and you need to know how to use it. Walking alone at night? Carry that deterrent in your hand.\n\nMinimize distractions. If I had bad intentions, I could rob half the people I ride the train with in New York. Earbuds in, screen-gazing, bags wide open. Completely zoned out. That’s the white zone — total lack of awareness. You need to “stay in the yellow.” One earbud out. Head up. Pay attention. Just looking like someone who’s paying attention will already make you harder to target than most people out there.\n\nTry the Bond app for non-emergencies. There’s a big gap on the spectrum between “just feeling scared” and calling 911. That’s where Bond comes in. You’re in a ride-share and the driver or shared passenger feels off? You’re walking home and something doesn’t feel right? Open the app, and within seconds you’re on the phone with a real person trained in conflict de-escalation. You can have them accompany you en route silently. They’ll stay on the line with you. They can track your route. They can even call emergency services if needed. It’s a game-changer, and I push it to everyone we work with. There may be other services like this, but this is the one I use.\n\nPractice stairwell drills — know your exits. When I check into a hotel, I don’t just throw my bag down and relax. I find the emergency stairwell, and I walk it. Why? Because in a fire, or a real emergency, elevators are out, and panic sets in. You don’t want to discover that the stairwell exits somewhere you didn’t expect — or worse, that the door doesn’t open. We do it on planes all the time — hear where exits are, see the markers — why don’t we do this in other spaces where we’re spending even more time? I’ve been caught in those situations before. Don’t assume. Know your exits.\n\nEstablish fallback plans — where to meet if separated. Here’s one that saved me once. I was at a crowded Orioles game with my daughter. She was younger then, and she wanted ice cream. We walked to get it, and I turned around — and she was gone. Forty thousand people in the stadium. Panic sets in fast. But before we’d gone out, I had told her, “If we ever get separated, meet me at the statue.” Sure enough, that’s where she was — sitting with her little stuffed bear. You should have the same kind of plan anytime, anywhere you’re out with friends or family. “If something goes sideways, meet here.” It’s that simple.\n\nCheck mirrors in hotel rooms. This one’s a little more niche, but it’s a real concern. I always check mirrors when I travel — especially abroad. You take a pen or something sharp, press it to the glass. If there’s a gap between the tip and the reflection, you’re good. If there’s no gap? You might be looking at a two-way mirror. I’ve had this happen. Twice. Both in high-risk countries. If that mirror’s sketchy, ask for a new room.\n\nLeave something you’ll need in the hotel safe. Have you ever left a passport or a wallet in a hotel safe when you’re checking out? People do this all the time. You check out in a rush and forget it. So here’s my trick to help prevent that: I put something in the safe that I know I’ll absolutely need to leave — like one of my shoes. Next morning, I’m getting dressed, I’ve only got one shoe, and boom — I remember the safe.\n\nThese aren’t complex tactics. They’re just smart habits. And if you do them consistently, you’re going to be ten steps ahead of most people.\n\nCrypto-specific threats\n\nThose everyday habits are practices everyone should follow. But let’s not sugarcoat it: If you’re in crypto, you’re a target. Founders. Engineers. Early employees. If someone thinks you might have access to digital assets — or even just influence over a protocol — they may come for you. And these aren’t petty criminals. The people doing this are often organized and sophisticated. In many cases, they’re violent.\n\nThis isn’t theoretical. It’s an ever–present threat that you need to be aware of.\n\nThese aren’t random muggings — they’re calculated, brutal operations\n\nNot long ago, a crypto founder was robbed at gunpoint in the UK (where gun crime is rare). The attackers didn’t stumble on him. They knew what they were doing. They tracked him, studied him, and then they struck.\n\nAnother case was a cofounder at a crypto wallet company. He and his wife were surveilled. The attackers followed them, waited for the right moment, then kidnapped them. They took the founder to a separate location, cut off one of his fingers, and sent a video of the mutilation back to his cofounder as proof that they were serious. That’s beyond robbery — it’s terror.\n\nThere was another case in Toronto, involving the CEO of an international crypto asset platform company. The night after the U.S. election — when Bitcoin prices jumped — he was grabbed off the street. The attackers had watched his daily movements and planned it out. In the end, he gave them a million dollars in crypto.\n\nAnd these are just some of the examples on record. There are many more you’ll never hear about.\n\nIt doesn’t just happen to famous people\n\nIt’s not always CEOs or protocol founders who get targeted. Sometimes, attackers come for someone who just ran their mouth online.\n\nThere was a kid in Portland — young, not famous, not well-protected. But he liked to brag on Twitter. Talked about how much crypto he had, what he was buying, where he was going. A crew in Florida saw the posts, flew across the country, kidnapped him, took everything, tied him to a fence post, and left.\n\nHe wasn’t even on anyone’s radar until then. He made himself a target just by being loud.\n\nWhy crypto is uniquely vulnerable\n\nSo why is this happening?\n\nFirst, perception. Everyone thinks if you work in crypto, you’re rich. Whether it’s true doesn’t matter — criminals believe it. That’s enough.\n\nSecond, when you’re part of an early stage startup, you may be lacking infrastructure. Most early startups don’t yet have security teams, so you’re probably walking around without protection. You may be moving millions of dollars and building protocols, but still living like you’re in college. That’s a problem.\n\nThird, the criminals don’t really understand crypto. They don’t know that wallets can be traced, or that funds might be frozen. They just think that if they get your keys, they win.\n\nAnd fourth — this is the big one — there’s no “undo” button. If the criminals get your seed phrase, a quorum of keys to your multisig, or passwords and access to your hardware wallet? That’s it. Game over. There’s no one to call. No hotline. No fraud department.\n\nThese attacks don’t happen overnight. There’s a process behind how these criminals operate:\n\nThey identify a target. Usually from public channels — podcasts, social media, conferences, even party guest lists.\n\nThey build a profile. They start scraping everything: your name, your habits, your digital footprint. Who you live with. Who you work with.\n\nThey use people around you. Housekeepers. Contractors. Rideshare drivers. Anyone who can get close.\n\nThey study your routine. This is called “pattern of life” surveillance. The time you leave the house. Which route you walk. Where you eat. When you’re alone.\n\nThey pick a place. Usually your home, because they know the layout. They can control the environment. And it buys them time.\n\nThis kind of operation takes effort. But that’s exactly why it’s detectable — if you’re paying attention.\n\nWhat you can do\n\nSet up a secondary wallet: Some of you probably know this dramatic irony: You spend years building bulletproof encryption, and some guy hits you with a $5 wrench and demands your seed phrase.\n\nHere’s the hard truth: If someone grabs you, encryption won’t save you. Your air-gapped laptop won’t save you. The multisig you set up? That’s great until someone clobbers you.\n\nThat’s why I tell every founder I work with: Set up a secondary wallet. Make it real. Put funds in it. Give it a transaction history. Make it look like it’s the one. If something goes bad, that’s what you hand over. Not the real vault. Just enough to be convincing.\n\nHow much should be in it? That’s up to you. Ten percent? Five percent? Whatever feels painful enough to be believable — but not catastrophic.\n\nBecause if someone’s spent weeks planning your abduction, they’re not leaving empty-handed. But if they get something, they’re more likely to walk. They want to get out as badly as you do. You don’t want to be in a standoff. You want to give them what they came for and quickly end it.\n\nAnd if they know — or even suspect — you’ve got more? That’s when it gets worse.\n\nDelete your online presence: You don’t need to be paranoid — but you do need to be private. We recommend using a service like DeleteMe to reduce your digital footprint. When buying property, use a trust. Don’t give attackers a map.\n\nInstall home security cameras and motion lights. You don’t need to spend tens of thousands of dollars. A basic setup — motion light and a Ring camera on the front and back doors — will do wonders. No one should be able to walk up to your house without tripping something. A motion light buys you time. A camera gives you awareness. If someone is casing your place and sees that setup, there’s a good chance they move on to someone else. Most people will pick between easy and hard targets. This is basic hygiene. If you’re in crypto, you should have this already.\n\nSeparate your funds. Use different platforms. Don’t link everything. Too many people keep all their holdings in one place. Worse, they use the same email, the same device, or the same recovery protocol across multiple accounts. That’s a recipe for disaster. If someone gets access to one, and they can draw a straight line to the rest, you’re done. Break up the connections. Use different services. Vary the wallets, platforms, devices — everything. The harder it is to draw a map connecting the routes, the safer you are.\n\nPractice the “what if” game. This one’s hugely beneficial. I do it constantly. I’ll walk into a restaurant and think, “What if someone walked in with a gun right now? Where do I go? What can I use?” If I’m on a plane, I play out, “What if something breaks bad?” In the Secret Service, we trained this way all the time. Visualization is the drill. Ask yourself: “What if someone came through that door right now? What’s my first move? Where’s cover? Where’s concealment? Can I get out?” You never want to be thinking through this stuff for the first time when it’s actually happening.\n\nKnow your exits. Walk the stairwells. Pack a “go chair.” Hotels are chaotic during emergencies. Fire alarms go off, and people are out there in bathrobes, barefoot, holding laptops, panicking. Don’t be that person. In every hotel I stay at, I find the emergency stairwell right after check-in and I walk it. I do this not just to see where it is, but to see where it actually goes. Does it open on your floor? Does it go out to the street? You’d be surprised how many don’t. I also pack a “go chair.” I set out sweats and sneakers — easy to throw on fast. If the alarm goes off in the middle of the night, I’m out the door in 30 seconds, fully dressed, not fumbling around like I’ve never done this before.\n\nDon’t rely on your phone to reconnect. Have a separation plan. Phones die. Batteries don’t charge. Coverage drops. Connectivity comes and goes, especially in disasters. You can’t rely on your phone as your only lifeline. If you’re out with someone — partner, team, friends — you need a separation plan. Say it out loud before you go out: “If things get weird, if we lose each other, meet me here.” Doesn’t have to be complicated. As I mentioned, I did it with my daughter when she was three years old at a baseball stadium, and it reunited us. If a three-year-old can do it, you can too. Make a plan, every time.\n\n***\n\nIf you’re ever grabbed, it’s too late to wish you’d thought about this stuff. That’s why situational awareness matters. Your best defense is prevention. Stay in the yellow. Adopt good habits. Prepare.\n\n***\n\nCarl Agnelli is head of security for a16z crypto, where he oversees physical security and safety operations for a16z crypto employees, facilities, and events globally. Prior to joining a16z, Carl served as the Director of Security at Citigroup. Before that, he spent 25 years as a special agent in the United States Secret Service. Most notably, as a special agent in Washington, DC, he conducted security operations around the world while also serving on the personal protective details of Presidents Bill Clinton and George W. Bush. Carl also served as the Special Agent in Charge of a northeast Field Division, where he oversaw security measures at large scale events for the President of the United States and visiting Foreign Heads of State.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nThe content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":6241,"crawled_at":1791195514033}
+{"id":10533,"url":"https://gov.uniswap.org/t/public-forum-to-wallet-link-verification/25965","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Public Forum to Wallet Link Verification - Delegation Pitch - Uniswap Governance","text":"Public Forum to Wallet Link Verification\n\nDelegation Pitch\n\nCuria\n\nDecember 17, 2025, 3:43am\n\n1\n\nPublic Forum to Wallet Link Verification\n\nThis thread provides an open verification tool for linking your forum account to your wallet address. It serves as a public utility for integrating onchain governance with forum activity and is available for anyone to use or adopt this on their own platform.\n\nInstructions:\n\nConnect your wallet to your delegate wallet on https://uniswap.curiahub.xyz\n\nLink your forum account by entering your forum name.\n\nSign a verification message to confirm your identity with your forum handle.\n\nPost the generated signature text:\n\nCopy the message.\n\nGo to the forum and post the generated signature text under this thread.\n\nReturn to https://uniswap.curiahub.xyz to complete the verification process\n\nEveryone is welcome to use this thread for their forum-to-wallet verification needs.\n\n2 Likes\n\nUniswap Delegate Dashboard by CuriaLab\n\nCuria\n\nDecember 17, 2025, 4:25am\n\n2\n\nVerifying my forum identity for uniswap governance\n\naddr: 0x17296956b4E07Ff8931E4ff4eA06709FaB70b879\n\nsig: 0xbaa75cac3ddbc91c9ad733466b910a1ac7c92e6b4ce072b5554462711bbecfe064b5a3373a65761648408f6e22973ebec18cb13617fbfc196109bc2af5eb033b1b\n\n#uniswapgovernance #Curia\n\nTane\n\nDecember 17, 2025, 9:22am\n\n3\n\nVerifying my forum identity for uniswap governance\n\naddr: 0xB79294D00848a3A4C00c22D9367F19B4280689D7\n\nsig: 0x01514bfb1da2ab4642b4d434413e00197e9467637cc0ff5ed8006743284d81f22db83c446af844bdc1dc70c13575f6a663356ff2cd856ac3dc971f2baae77ab51b\n\n#uniswapgovernance #Tane\n\n1 Like\n\ncodeknight\n\nDecember 17, 2025, 4:34pm\n\n4\n\nVerifying my forum identity for uniswap governance\n\naddr: 0xb2010b3B9e1d60933df001a30bC2A8fc523B2241\n\nsig: 0x4960a9f37a35c9778657863f6f9614162f23baec91c6907a3831228675704f5c6ebfe91a0f0d9e05afc663d3392a3d1ddfd33faba171b2a30488c325dfa966151c\n\n#uniswapgovernance #codeknight\n\n1 Like\n\nDAOplomats.eth\n\nJanuary 21, 2026, 6:10pm\n\n7\n\nVerifying my forum identity for uniswap governance\n\naddr: 0xc5547B4907418C2EC0C2A95beC6fEE8354657759\n\nsig: 0xa5ee25a07a7d1b31d4b16498cee682d5d894b66f4e9983c534c8058b76162bc03de62f40a53594cf1d09ee6061b4e9c8c408ca6ad27ef4c1bdbce8a6ee53842b1c\n\n#uniswapgovernance #DAOplomats.eth\n\nmust479\n\nJanuary 25, 2026, 7:47pm\n\n8\n\nVerifying my forum identity for uniswap governance\n\naddr: 0x2D815240A61731c75Fa01b2793E1D3eD09F289d0\n\nsig: 0xc242959468df171ca24a7c94d3e3900807a452fa24be652ec70e1d72c9410f852e7f6a279292c29d74d70167a708acd157bf83b2dece18c656aeff0aa41276341b\n\n#uniswapgovernance #Must479\n\nmust479\n\nJanuary 25, 2026, 7:50pm\n\n9\n\nVerifying my forum identity for uniswap governance\n\naddr: 0x2D815240A61731c75Fa01b2793E1D3eD09F289d0\n\nsig: 0xe6e1f2bbefcb669fd344817b391988e5cc557aa13f8f6abae469eeecae8e78f751ef1e6be7d0e2b2d4915b3ca7cf202c8b69c9714fcc0ffec27e0ee42d0814171b\n\n#uniswapgovernance #must479\n\nblockful\n\nFebruary 3, 2026, 1:48pm\n\n10\n\nVerifying my forum identity for uniswap governance\n\naddr: 0x1F3D3A7A9c548bE39539b39D7400302753E20591\n\nsig: 0xf8a9aa7dd2cca32ab8c98d5377905b61c610f24afe14be4ec44b70649bc8e1de7fd3c8a92ba70f23c95107ed66d5d4fee919b2c3a46da384968621abee22b3a51cb34847c106b000a1696982652e5b1e4186dcaea9eadba1c4f81c739ac2ff5f2876696f5ceb8a9b25087336570844e69e049b6da8a8e2e25462d6d1874f30a90e1b\n\n#uniswapgovernance #blockful\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nDelegate UNiswap votes to me\n\nDelegation Pitch\n\n0\n\n2354\n\nApril 1, 2022\n\nUniswap Governance Forum Banner\n\nUncategorized\n\n0\n\n3250\n\nSeptember 21, 2020\n\nCommunity Governance Process\n\nGovernance-Meta\n\n30\n\n58333\n\nApril 7, 2023\n\nOfficial Uniswap v3 Deployments List\n\nGovernance-Meta\n\n10\n\n4366\n\nDecember 17, 2025\n\nUniswap Delegate Dashboard by CuriaLab\n\nRequests for Comment\n\n0\n\n419\n\nDecember 17, 2025","tokens":931,"crawled_at":1791195520358}
+{"id":10534,"url":"https://docs.sui.io/develop/write-move/package-overview","domain":"docs.sui.io","chapter":"layer1_layer2","title":"What are Move Packages? | Sui Documentation","text":"MoveMoveAn open source programming language used for all activity on Sui. is the smart contract language Sui uses to define onchain logic. Move is platform-agnostic, enabling shared libraries, tooling, and developer communities across blockchains with different data and execution models.\n\nSui uses Move through three constructs: packagesPackageSmart contracts on Sui., modulesModuleA component of a Move package that defines interaction with on-chain objects., and objects.\n\nA Move package is a set of Move bytecode published to the Sui network. Packages are immutable. You can upgrade a package, but upgrading creates a new onchain version while leaving all prior versions intact. Once published, other packages can import and use a package's modules, and anyone can inspect its contents or trace its logic using a Sui Explorer.\n\nA Move module defines a package's interaction with onchain objects. Each module name is unique within its package.\n\nA Move objectObjectThe basic unit of storage on Sui. is typed data governed by a Move module. Each object is a struct with fields that can contain primitive types such as integers and addressesAddressA unique, anonymous identity on a blockchain network., other objects, or non-object structs.\n\nPackages are immutable​\n\nAfter you publish a package object to a network, it lives there permanently. You cannot directly change the code of an onchain package. Once published, other packages can import and use the modules it provides.\n\nIf developers could modify onchain packages after publication, downstream behavior could change in unexpected ways. For example, a developer fixing an overlooked bug could unintentionally change the execution of every dependent package.\n\nMaking packages immutable​\n\nYou can call the Move function sui::package::make_immutable to destroy a package's UpgradeCap and make the package permanently immutable. This eliminates single-key risk but also prevents all future bug fixes and feature additions.\n\nFor a more flexible approach, use custom upgrade policies to protect UpgradeCap access without giving up the ability to upgrade.\n\nUpgrading packages​\n\nAlthough you cannot edit a published package directly, you can upgrade it. Upgrading creates a new package object onchain, leaving the original intact. This lets you add features or fix issues without breaking existing dependencies.\n\nSee Upgrading packages for details on the process.\n\nUsing the Sui Client CLI​\n\nThe Sui Client CLI provides an approachable way to publish and upgrade packages. See the package management\nguide for information on creating and working with Move packages.\n\nIf the CLI's active address owns the UpgradeCap for a package, you can use the upgrade command to perform an upgrade. This workflow is convenient when you're starting development or iterating quickly. However, protecting package upgrades with a single private key poses security risks:\n\nThe entity owning that key might make changes that are in their own interests but not the interests of the broader community.\n\nUpgrades might happen without enough time for packagePackageSmart contracts on Sui. users to consult on the change or stop using the package if they disagree.\n\nThe key might get lost.\n\nRelated topics\n\nCustom Upgrade Policies\nCustom upgrade policies are used to upgrade live packages while addressing the security risks of single key ownership upgrades.\nUpgrading Packages\nUpgrade a published Move package on Sui using the Sui CLI, understand layout-compatibility requirements, manage UpgradeCap and UpgradeTicket, and apply custom upgrade policies to control what changes are permitted.\nSui Client CLI\nThe Sui Client CLI provides command-level access to interact with the Sui network.\nMove Package Management\nLearn how to use the Move package manager system.\n\nPackages are immutableMaking packages immutable\n\nUpgrading packages\nUsing the Sui Client CLI\n\nWas this page helpful?","tokens":977,"crawled_at":1791195530298}
+{"id":10535,"url":"https://gov.uniswap.org/t/governance-proposal-supporting-the-defi-education-fund/23631","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Governance Proposal - Supporting the DeFi Education Fund - Requests for Comment - Uniswap Governance","text":"Governance Proposal - Supporting the DeFi Education Fund\n\nRequests for Comment\n\nmillerDEF\n\nApril 12, 2024, 3:09pm\n\n1\n\nGovernance Proposal (technical implementation explainer doc)\n\nUpdated Proposal & Temperature Check\n\nWe’ve updated the proposal (below) to incorporate the feedback and thoughts we received on the prior version. Thank you to everyone who helped us make this proposal better. Significant changes:\n\nToken Smart Contract Streaming: DEF would receive 500k tokens upon passage of this proposal and 500k would be locked up in a streaming contract that would “vest” linearly over 12 months. Governance could vote to stop the streaming of the remaining tokens at any time. We are looking into the best way to implement this idea and will update the forum thread with confirmed details once we have them.\n\nCommunity Transparency and Engagement: The DEF team will host monthly community calls that Uniswap community members can join to hear updates on our work, learn about high priority policy and regulatory developers, and have questions answered. We’ll also keep a thread on the Uniswap governance forum up to date with our monthly updates.\n\nGFX has initiated a temperature check on this updated proposal. Thank you all!\n\nOverview\n\nSince its founding via a timely Uniswap Governance governance proposal in 2021, the DeFi Education Fund (DEF) has fought to advance and protect the potential of DeFi in the public policy sphere. The threat that misguided policies and overreaching regulators pose to DeFi has never been clearer. This proposal is to provide DEF with one million UNI tokens in two tranches to support them in fulfilling their mission.\n\nSee our CLO Amanda Tuminelli discuss our recent work on Unchained this morning.\n\nDeFi promises to revolutionize how people engage in economic activities. In particular, the openly accessible and decentralized characteristics of DeFi protocols means that anyone with an internet connection and a wallet can participate in the global economy in a way that would not be possible without DeFi. To do so, DeFi upends the structure of traditional financial services and related policy making approaches. That upending has brought with it intense interest, suspicion, and hostility from entrenched interests and regulatory bodies around the world.\n\nDEF has defended DeFi from legislative threats that would require DeFi developers to implement protocol access restrictions or requirements designed for CeFi businesses; regulatory proposals that would mandate centralization if finalized; and in the courts against overzealous regulators. In late March, we sued the SEC over its policy on airdrops and its campaign of regulation by enforcement that is crippling DeFi and crypto development and participation in the United States.\n\nOver the last few years, DeFi’s policy challenges have become more real, more imminent, and more numerous. For example, in the U.S. alone, there are at least half a dozen bills actively under consideration in Congress and two rulemakings pending finalization that would effectively prohibit DeFi development. Luckily, public policy education and advocacy has borne—and can continue to bear—fruit for DeFi.\n\nWithout doubt, building a public policy environment welcoming of DeFi and decentralized governance will be a long and arduous struggle, but we know that Uniswap Governance shares our commitment to winning that debate—and it is winnable—so that the benefits of DeFi can be felt and enjoyed by as many people as possible, as quickly as possible.\n\nDEF is eager to continue leading the fight on behalf of DeFi. With additional resources, we can build out our team:\n\nsuper charge our impact litigation efforts to reshape the legal landscape to DeFi and DAOs’ benefit;\n\nexpand our outreach to legislators and double down on our educational efforts;\n\nmore vigorously challenge the regulatory onslaught targeting DeFi; and\n\nenhance our ability to engage in state-level debates and jurisdictions outside of the United States.\n\nIf DeFi development and DAOs are to have a future in the United States, we need to double down on our advocacy efforts to protect DeFi from the myriad policy risks it faces while proactively laying the foundation for longterm policy solutions favorable to DeFi and DAOs. We stand ready and able to do so with the community’s backing and appreciate your consideration.\n\nRationale\n\nDeFi’s policy challenges are immense and interest in DeFi has only grown since the DEF got to work in 2021. Following the collapse of FTX and with the return of the bull market, there is acute interest in DeFi on Capitol Hill and state legislatures, as well as inside federal and state government agencies. Providing meaningful educational outreach about DAOs and DeFi to lawmakers while also assisting in the legal defense of decentralized organizations is a role not played by anyone else in the US.\n\nAt this time, DAOs and DeFi protocols face several potentially catastrophic threats: a live IRS proposal would mandate the creation of intermediaries to conduct tax reporting (i.e., ban on disintermediated systems) and a live SEC rulemaking would define anyone loosely related to a DeFi protocol—including the underlying chain’s miners/validators—to be national securities exchanges like the New York Stock Exchange. Moreover, bills written to regulate CeFi often inadvertently capture DeFi protocols and subject them to compliance obligations designed for CeFi businesses.\n\nIf DeFi development and DAOs are to have a future in the United States, we need to double down on our advocacy efforts to protect DeFi from these myriad policy risks while laying the foundation for longterm proactive policy solutions favorable to DeFi and DAOs. There is a reason TradFi businesses collectively spend over $1 billion per year on U.S. lobbying and policy efforts: it works, and we’re making it work for DeFi.\n\nDEF focuses specifically on fighting for policy outcomes favorable to decentralized finance developers and users on the ground in Washington, DC. A summary of our past work, which has included defending DAOs in court, as well as providing comment and consultation to regulators to avoid burdensome rules and regulations in the US and around the world, below. This proposal would expand our budget so that we can expand our legislative, regulatory, and legal advocacy and education efforts on behalf of DeFi and DAO developers and users.\n\nIf DeFi development and DAOs are to have a future in the United States, we need to double down on our advocacy efforts to protect DeFi from policy risks while proactively laying the foundation for longterm policy solutions favorable to DeFi and DAOs. We stand ready and able to do so with the community’s backing, and we appreciate your consideration.\n\nTeam, Social, & Contacts\n\nTeam: Miller Whitehouse-Levine , Amanda Tuminelli , Max Bernstein , and Lizandro Peiper\n\nBoard: Marc Boiron, Jake Chervinsky, and Rebecca Rettig (all elected by Uniswap Governance in '21)\n\nWeekly updates on policy developments and activities\n\n12 Month Estimated Budget (current burn)\n\nHistorical financial information (annual and monthly)\n\nX\n\nContact - Please reach out to discuss!\n\nEmail: miller@defieducationfund.org\n\nTelegram: @millwl\n\nTwitter: @fund_defi\n\nConclusion\n\nThe DeFi Education Fund is a nonprofit organization with a demonstrated history of being in the trenches fighting for DAOs and decentralized finance. Whether looking to provide legal assistance when DAOs and their members are targeted, providing educational resources, or fighting for policy changes, the DeFi Education Fund is the only major crypto advocate that focuses solely on decentralized web3.\n\nFAQs\n\nWhy are you raising money now if you have about two years of runway at your current burn?\n\nWe are seeking Uniswap Governance’s further support now for three primary reasons.\n\nFirst, we need a good sense of our longer term funding in order to expand our efforts and take on the long term projects that our work often requires, which can play out over several years. For example, our legal challenge of the patent covering oracle tech that is being used against DAOs will likely take a total of at least two years from start to finish. Our lawsuit against the SEC will probably last several years. If we did not have a good expectation of being able to operate two years after starting those efforts, we would not have been able to take them on at all. In addition, because we hold tokens long term, we are exposed to crypto market price fluctuations.\n\nSecond, unexpected, ad hoc projects that we are well-positioned to take on in defense of DeFi can be extremely expensive. For example, we expect the challenge to the oracle patent to cost nearly $500,000 over its entire course. A legal challenge to proposed rules that would de facto ban DeFi in the United States would cost well over $1m. We have no ability to predict with certainty when and if those expenditures will be necessary, and without a sense of our longer term funding situation, we can’t take on those types of unexpected, but critical, projects while also expanding our day to day efforts and team.\n\nDeFi needs more dedicated advocates working on its behalf. With a larger budget, we can hire more people.\n\nWhen and how would you plan on selling this proposal’s tokens?\n\nIt is important to us that DEF remains aligned with the DeFi community and our supporters over the long term. Upon passage, 500k $UNI tokens would be transferred to DEF’s on-chain Coinbase $UNI wallet, and 500k would be locked up in a streaming contract that would “vest” linearly over 12 months. Governance could vote to stop the streaming of the remaining tokens at any time.\n\nWe will hold half of any tokens we receive for at least 12 months from the date we receive them, and we will pre-disclose all sales plans in writing.\n\nHow are you going to keep Uniswap Governance up to date on your activities?\n\nThe DEF team will host monthly community calls that Uniswap community members can join to hear updates on our work, learn about high priority policy and regulatory developers, and have questions answered. We’ll also keep a thread on the Uniswap governance forum up to date with our monthly updates.\n\nWhat about the tokens from the 2021 proposal?\n\nWe received our initial grant of one million $UNI tokens from the Uniswap Governance in July 2021 and sold half of the tokens shortly thereafter. In February 2024, we began selling portions of the other half of the tokens according to an 18 month written sales plan. We will sell in July 2025 the last of the UNI tokens we received in July 2021.\n\nWhy are you asking us for money and not other DAOs?\n\nWe are, and we will definitely continue to “pass around the hat”! We seek Uni governance’s continued support as a community that is building for the long term. Uniswap Governance took a massive “leap of faith” in generously funding an organization that did not yet exist to do work that would benefit every DeFi project and DAO. We hope that our track record of work has proven valuable to DeFi projects and users such that Uni governance and other projects’ governance will continue to contribute to our work going forward.\n\nACCOMPLISHMENTS\n\nLegal Advocacy\n\nSEC v. Kraken - In February 2024, we submitted an amicus brief explaining the various incorrect and often inconsistent legal positions the SEC employs in its attempts to justify its position that digital asset transactions are securities transactions.\n\nVan Loon v. Treasury - In November 2023, we filed another amicus brief related to the Tornado Cash sanctions in the U.S. Court of Appeals for the Fifth Circuit. We argued that the use of privacy-protecting technology is normal and not inherently illicit and that Office of Foreign Asset Control (OFAC) exceeded its statutory authority in issuing sanctions that included purely domestic transactions.\n\nHarper v. Internal Revenue Service - In October 2023, we filed an amicus brief in a case involving a challenge to a “John Doe” summons the IRS sent to Coinbase that resulted in the collection of information (including information revealing on-chain wallet addresses) about 14,355 Americans (none of whom were accused of any wrongdoing prior to the summons) over a three-year period. Our brief explained the sweeping Fourth Amendment implications of indiscriminately collecting digital asset transaction information and how doing so is more revealing than in the context of TradFi.\n\nSEC v. Coinbase - In August 2023, we filed an amicus brief in the U.S. District Court for the Southern District of New York in support of Coinbase. We explained how wallets and staking actually work and supported Coinbase’s arguments that it is not a broker through its wallet software, nor did it offer securities through its staking program.\n\nCoin Center v. Treasury - In June 2023, we filed an amicus brief in support of a challenge to OFAC’s sanctioning of Tornado Cash smart contracts. plaintiffs’ motion for summary judgment ag. In October 2022, Coin Center and several individuals sued Treasury, challenging OFAC’s designation of Tornado Cash smart contracts. The plaintiffs argued that doing so exceeded the Treasury’s authority, and violated the Administrative Procedure Act (APA) and the First Amendment. Our brief supported arguments that the sanctions were beyond the Treasury Department’s statutory authority and violated the Administrative Procedure Act, made the point that Tornado Cash is an important privacy-protection tool, and argued that the sanctions designations made no sense when considering the realities of the technology at issue.\n\nVan Loon v. Treasury - In April 2023, we submitted our first brief related to Treasury’s sanctioning of Tornado Cash smart contracts. In addition to Treasury’s lack of statutory basis for the actions, We argued that the downstream implications of sanctioning a software protocol will lead to not only a weakening of the digital asset industry, but will also seriously jeopardize law-abiding Americans’ financial privacy.\n\nCFTC v. Ooki DAO - In late 2022, the Commodity Futures Trading Commission (CFTC) served Ooki DAO, alleging it is “illegally offering leveraged and margined retail commodity transactions in digital assets” without a Futures Commission Merchant designation or a Bank Secrecy Act (BSA) program. The CFTC served “Ooki DAO” via a help chat box with a contemporaneous notice posted on a website purportedly affiliated with Ooki DAO. We filed a brief in the case explaining: “First, the Commission has named Ooki DAO as a defendant in this action, asserting that Ooki DAO is an “unincorporated association comprised of Ooki Token holders.” But nothing about the structure of a DAO inherently dictates that result. In many cases, DAOs lack any central organization or management, and many DAO token holders often lack coordination or common objectives. As a result, DAOs will often not be “associations” of any kind, and therefore will not be proper defendants in an enforcement action brought under the Commodity Exchange Act (“CEA”), which requires that a defendant be a “person” (defined to include “associations”). The Commission has not yet alleged facts sufficient to establish that Ooki DAO is an association, so its attempt to serve Ooki DAO here is premature.”\n\nCombatting crypto patent trolls: In September 2023, we took action to protect DeFi and crypto from invalid patent infringement claims. We filed a petition with the U.S. Patent and Trademark Office seeking to initiate an inter partes review and cancellation of all claims in a patent owned by True Return Systems LLC. TRS is a patent troll who first tried to sell the patent as an NFT, and when that didn’t work, sued both MakerDAO and Compound Protocol in federal court for alleged infringement of U.S. Patent No. 10,025,797. Our petition argued that the technology that TRS purported to patent was not in fact TRS’s invention, but was instead very similar to oracle technology that had been in development and use for years prior to the patent.\n\nRegulatory Advocacy\n\nIn January 2024, we urged the Department of the Treasury to reconsider its proposed rule to classify crypto “mixing” transactions to be a “primary money laundering concern” subject to enhanced reporting requirements. Among the issues we commented on is the proposal’s all-encompassing definition of “mixing,” which would capture almost all crypto transactions and designate them to be “high risk.”\n\nIn January 2024, we submitted our thoughts on a Consumer Financial Protection Bureau (CFPB) proposed rulemaking that could expand the CFPB’s supervisory authority to capture self-hosted wallets. We argued that the rulemaking should not move forward as it would further scramble the Federal government’s already-convoluted regulatory treatment of DeFi and crypto-related activities.\n\nIn November 2023, we filed a comment letter regarding the Treasury Department’s proposed “broker” rulemaking. The proposed rule would introduce a brand new category of broker called a “digital asset middleman,” a new term that is essentially limitless in scope and creates brokers out of thin air in DeFi and, as we argue, runs contrary to the statute and legislative history. Furthermore, we argued that the proposal violates the Fourth Amendment’s prohibition on warrantless searches and seizures of a person’s papers and effects because individuals do not voluntarily turn over their personal data to “digital asset middlemen” who themselves neither collect nor have any legitimate business reason to collect that information. For a plain language review of our issues with the rulemaking, read: “Congress Gets the Runaround From Regulators, Again.”\n\nIn October 2023, we responded to France’s Autorité de Marchés Financiers (AMF) concerning their DeFi regulatory discussion paper. Our comment letter addressed many topics including permissionless blockchain protocols, legal enforceability of smart contracts, off-chain elements, etc. Importantly, we addressed the legal liability of smart contract developers, arguing that smart contracts’ code is open-source for anyone to audit and make informed decisions. Furthermore, we argued that open-source code is a form of expression as it conveys ideas for societal change and demands protection. We also argued against the AMF’s proposal to create a government-run certification regime for smart contracts.\n\nIn September 2023, we responded to a request for comment from the Senate Finance Committee regarding the taxation of digital assets. In our submission, we recommended Congress: 1) Revise Section 6050I so that it does not “deputize recipients of digital assets to collect and report information about their payers;” 2) Do not tax staking rewards until a sale or other disposition; 3) Do not apply wash sale rules to taxpayers who utilize digital assets as a form of currency; and 4) explicitly extend the application of section 1058’s nonrecognition rule to “loans” of actively traded fungible tokens.\n\nIn June 2023, we submitted a response to a consultation from HM Revenue and Customs, the United Kingdom’s tax, payments, and customs authority, regarding “the taxation of DeFi involving the lending and staking of cryptoassets.” At a high-level, our submission noted that any changes to the tax regime that concern DeFi must: be flexible to account for future innovation; exhibit clarity and simplicity to promote compliance by minimizing the burden on taxpayers; and align with the underlying economic substance of a typical DeFi transaction.\n\nIn June 2023, we submitted a response to Banque of France’s Autorité de Contrôle Prudentiel et de Résolution (ACPR) regarding their discussion paper: “Decentralised’ or ‘Disintermediated’ Finance: What Regulatory Response?” Our primary arguments included that ACPR should not directly regulate miners and validators by establishing standards for public blockchains; a policy that would “force centralization” would eliminate the core innovations of public blockchains; and a framework for smart contract certification would require centralization and the inappropriate regulation of speech.\n\nIn June 2023, we filed our third comment letter on the SEC’s proposed “exchange” rulemaking. Our brief made two primary arguments: first, the proposal improperly reads and misapplies the Exchange Act and exceeds the SEC’s statutory authority and mandate under the Act; and second, the SEC has flatly failed to comply with numerous procedural and statutory rulemaking requirements.\n\nIn August 2022, the DEF filed a response to the U.S. Treasury Department’s request for comment on innovation in digital assets. In our response, we explained how DeFi protocols have the potential to benefit consumers, investors, and businesses in the United States and around the world by creating accessible financial infrastructure usable by any individual with an internet connection.\n\nIn June 2022, we responded to Abu Dhabi’s DeFi consultation, in which we expressed our view that decentralization and disintermediation serve important societal objectives and that forcing the reintroduction of intermediation via legal obligations is a misguided approach to DeFi that would undermine its core potential and innovation.\n\nIn June 2022, In our second letter on the SEC’s exchange rulemaking, we argued that the proposed rule represents an improperly static regulatory response to a dynamic innovation and therefore needs to be reconsidered in total.\n\nIn May 2022, we commented on the SEC’s “dealer” rulemaking, which could not only subject large DeFi market participants to the threat of arbitrary SEC enforcement actions but also, potentially, capture liquidity pools themselves as so-called “dealers” under the securities laws. But how would it do so? In what way? The SEC did not say when it proposed the rule nor when it later finalized the rule in early 2024, which we expect to see challenged in court. .\n\nIn April 2022, we submitted the first of three comment letters on the SEC’s “exchange” rulemaking, which would de facto ban DeFi protocols in the United States. We argued that the Proposal’s expanded definition of an “exchange” is so broad that it could be interpreted to cover DeFi market participants, yet the rule didn’t specify which or why—it didn’t even mention “crypto,” “DeFi,” or “digital assets” once. In January 2023 in response to these concerns, the SEC released 167 pages of additional information explaining that the proposal does apply to DeFi and crypto, which we also responded to.\n\nIn April 2022, we submitted a comment letter to the Organization for Economic Co-operation and Development (OECD) on its proposed framework for tax reporting in the digital asset ecosystem. Broadly, when it comes to DeFi, the proposal fits squarely in the “how do we apply existing regulations and tactics to innovative systems” camp. This concept would force the creation of intermediaries where they do not exist for tax reporting purposes, a concept that the Treasury Department is now attempting to enshrine in the United States (see November 2023 comment letter on the IRS’s proposed “broker” rulemaking).\n\nLegislative Advocacy\n\nThe past year has yielded some fruit in the industry’s push for crypto-specific legislation, but legislation is still a few years out, in our view. In July, The House Agriculture Committee and the House Financial Services Committee (HFSC) voted, with bipartisan support, to advance the Financial Innovation Technology for the 21st Century Act, a bill that would create a regulatory framework for crypto in the U.S. That same month, the HFSC advanced a bill to establish a federal regulatory regime for stablecoins.\n\nMore recently, the House Committee on Energy and Commerce passed the Deploying American Blockchains Act (by a 46-0 margin), which would direct the chief of the Department of Commerce “to promote the competitiveness of the United States related to the deployment, use, application, and competitiveness of blockchain technology or other distributed ledger technology.” While these bills are not perfect, we’re pleased that Congress has taken a serious approach to these matters.\n\nThere’s another factor that gives us hope for the long-term chances of good legislation passing both chambers. And that is the willingness of Congressional offices and policymakers to engage with DEF and learn about the foundational aspects of the technology. We do “DeFi Demos” on Capitol Hill and advocate for policies welcoming of DeFi and DAOs. We explain why we believe in DeFi and why government officials and elected representatives should be just as curious as we are as to how this technology can improve the lives of their constituents. Away from sensational media headlines and televised hearings, one can see that a better, more open future for DeFi is developing.\n\nSpecifically, we’ve provided a perspective from DeFi’s corner on the following federal legislation:\n\nH.R. 1122, CBDC Anti-Surveillance State Act\n\nH.R. 1177/S. 427, Financial Freedom Act of 2023\n\nH.R. 1414. Keep Innovation in America Act\n\nH.R. 1747: Blockchain Regulatory Certainty Act\n\nH.R. 2670, National Defense Authorization Act for Fiscal Year 2024, including provisions related to Amendment 44\n\nH.R. 2743/S. 293, Fair Access to Banking Act\n\nH.R. 2891/S. 1323, Secure and Fair Enforcement (SAFE) Banking Act of 2023\n\nH.R. 2969/S. 1340, Financial technology Protection Act of 2023\n\nH.R. 3572, Securities Clarity Act\n\nH.R. 4664, Making appropriations for financial services and general government for the fiscal year ending September 30, 2024, and for other purposes\n\nH.R. 4763, Financial Innovation and Technology for the 21st Century Act\n\nH.R. 4766, Clarity for Payment Stablecoins Act of 2023\n\nH.R. 4841, Keep Your Coins Act of 2023\n\nH.R. 5403, CBDC Anti-Surveillance State Act\n\nH.R. 5741, Uniform Treatment of Custodial Assets Act\n\nH.R. 6307, Creating Legal Accountability for Rogue Innovators and Technology (CLARITY) Act of 2023\n\nH.R. 6322, End Financing for Hamas and State Sponsors of Terrorism Act\n\nH.R. 6572, Deploying American Blockchains Act of 2023\n\nS. 661, Crypto-Asset Environmental Transparency Act of 2023\n\nS. 695, A bill to repeal the provisions of the Infrastructure Investment and Jobs Act that impose new information reporting requirements with respect to digital asset transfers\n\nS. 1357, Responsible Digital Asset Advertising Act of 2023\n\nS. 2226, National Defense Authorization Act for Fiscal Year 2024, including provisions related to Senate Amendment 326 and Senate Amendment 1087 to Senate Amendment 935\n\nS. 2281, Lummis-Gillibrand Responsible Financial Innovation Act\n\nS. 2355, Crypto-Asset National Security Enhancement and Enforcement Act of 2023\n\nS. 2597, Digital Consumer Protection Commission Act of 2023\n\nS. 2669, Digital Asset Anti-Money Laundering Act of 2023\n\nS. 3087, Proving Reserves Of Others Funds (PROOF) Act\n\nS. 3441, Terrorist Financing Prevention Act of 2023\n\n[media work continued in next post…]\n\n10 Likes\n\nRFC - Options for Supporting DeFi Education Fund\n\n[RFC] Donate to Roman Storm & Alexey Pertsev’s legal defense fund\n\n[RFC] Donate to Roman Storm & Alexey Pertsev’s legal defense fund\n\nmillerDEF\n\nApril 12, 2024, 3:11pm\n\n2\n\n[…continued]\n\nVoice for DeFi: Selected Op-Eds\n\nBankless: “You Can Protect DeFi”\n\nFortune: “You’ve got a friend in me: How amicus briefs are helping the crypto industry win over the courts”\n\nCoinDesk: Congress Gets the Runaround From Regulators, Again\n\nCoinDesk: When Did Privacy Become a Bad Word?\n\nBlockworks: Crypto rights are fundamental American rights\n\nFortune: The SEC’s campaign to define ‘exchange’ should concern every American—even those without ties to crypto\n\nBlockworks: Don’t Drive Crypto Into the EU’s Open Arms\n\nThe American Conservative: The Wrong Lesson from the Fall of FTX\n\nCoinDesk: Why Ex-SEC Official John Reed Stark Is Wrong About Crypto\n\nCoinTelegraph: CBDCs will lead to absolute government control\n\nFortune: A ‘kitchen sink’ approach won’t work if the 118th Congress wants to fix its DeFi problem\n\nProviding DeFi’s Perspective in the Media\n\nThe Defiant: Crypto Advocates See Coinbase’s SEC Hearing as a “Step Forward”\n\nA spokesperson from the DeFi Education Fund (DEF), a DeFi-focused research and advocacy group, told The Defiant the hearing was “a step forward.” “On wallets and staking, the court rightly noted the paucity of factual allegations in the SEC’s complaint, and we were happy to hear that our amicus brief on these issues was useful in the court’s understanding of them,” the spokesperson said.\n\nDL News: Coinbase lashes out against regulator’s bid to ‘grab jurisdiction’ over crypto — and it’s not the SEC\n\n“Regulatory agencies — the CFPB included — are trying to grab jurisdiction in a way that creates statutory contradictions,” Miller Whitehouse-Levine, CEO of the DeFi Education Fund, told DL News.\n\nCointelegraph: A taxing obligation: Is crypto reporting ‘impossible’ under US law?\n\n“At the moment, it is literally not possible to comply with the reporting requirement,” Miller Whitehouse-Levine, CEO at the DeFi Education Fund, told Cointelegraph. What’s needed instead for the 60 million Americans who own digital assets today are “fit-for-purpose tax provisions” that basically regard crypto as a different sort of case.\n\nLaw360: USPTO To Review Blockchain IP Used To ‘Troll’ Crypto Firms\n\nThe challenge has been led by the DeFi Education Fund, a crypto advocacy group that says that the technology the patent covers predates the patent itself and has called True Return Systems a “patent troll” that threatens to force anyone using oracle systems to pay. On the same day in 2022, True Return Systems brought two suits against what amount to technology programs, arguing that they were infringing on the True Return Systems patent.\n\nBankless Podcast: The US Government is Trying to Kill Crypto\n\nWe need to stop the US from killing crypto. The new IRS proposals could effectively destroy DeFi and other crypto use cases. The good news? We can change this. 5 minutes is all it takes to leave a comment and get the interpretation delayed. In this episode, we bring on Miller Whitehouse-Levine of the DeFi Education Fund and tax lawyer Jason Schwartz to discuss the proposed rules and their catastrophic implications.\n\nLaw360: Crypto Group Urges 1st Circ. To Revive IRS Doc Seizure Suit\n\nA New Hampshire federal court failed to understand the distinctive features of cryptocurrency technology when it determined that the seizure, issued by John Doe summons, did not violate James Harper’s Fourth Amendment right to privacy, DeFi Education Fund argued in an amicus brief. DeFi is a research group that advocates for the benefits of decentralized finance, including cryptocurrency.\n\nDecrypt: Taxes Targeting DeFi Would be ‘Awfully Challenging’: Coinbase VP\n\nToday, Washington, D.C. nonprofit Defi Education Fund said on Twitter that “the proposed ‘broker’ rulemaking… must be stopped” because it would raise “serious tax policy and privacy concerns.”\n\nCointelegraph: Crypto advocates file amicus brief to address users’ Fourth Amendment privacy rights\n\nCryptocurrency advocacy group the DeFi Education Fund (DEF) has urged a United States court to consider the unique aspects of blockchain technology when evaluating the privacy rights of cryptocurrency users under the Fourth Amendment of the U.S. Constitution.\n\nLaw360: DeFi Org Asks USPTO To Review Blockchain IP Held By ‘Troll’\n\nCrypto advocacy group the DeFi Education Fund has asked the U.S. Patent and Trademark Office on Monday to take a look at a patent held by a firm it said is “trolling” decentralized finance entities with lawsuits over a blockchain system the group claims is “indistinguishable” from solutions that came before it.\n\nLaw360: CFTC Enforcement Cases May Force DeFi To Comply Or Leave\n\nThe DeFi Education Fund advocacy group said in a statement to Law360 that the CFTC enforcement actions “completely reject” the New York court’s finding…“The CFTC’s enforcement actions yesterday completely reject the court’s decision in Risley v. Uniswap Labs, which found that it ‘defies logic’ to hold the developer of a DeFi protocol liable for a third party’s potential misuse of that software,” the DeFi Education Fund said.\n\nDL News: The Guidance: A peak into lobbyists’ agenda\n\nWhile the stablecoin and market structure bills are front of mind, for the DeFi Education Fund, Senator Elisabeth Warren and Senator Roger Marshall’s bill on anti-money laundering provisions for digital assets is the priority…“What they propose to essentially do is make miners and validators financial intermediaries for regulatory purposes or software developers,” Miller Whitehouse-Levine, CEO of the Fund, told DL News. “So it’s highly problematic and certainly would kill the industry in the United States.\" But Whitehouse-Levine is hopeful because “everyone’s objective is the same, it’s just a matter of accomplishing how this objective is going to work.”\n\nBloomberg: Treasury Aims to Snag Tax Cheats With Crypto Broker Proposal\n\n“Today’s proposal from the IRS is confusing, self-refuting, and misguided,” said Miller Whitehouse-Levine, chief executive officer of the DeFi Education Fund.\n\nThe Wall Street Journal: U.S. Tackles Crypto Tax Mess\n\n“It attempts to apply regulatory frameworks predicated on the existence of intermediaries where they don’t exist.”\n\nReuters: Biden administration unveils new crypto tax reporting rules\n\nMiller Whitehouse-Levine, CEO of the DeFi Education Fund, a lobbying group focused on decentralized finance, said the proposed approach would neither make filing taxes easier nor improve tax compliance.\n\nCoinDesk: U.S. Senator Lummis, Crypto Lobbyists Urge Court to Dismiss SEC’s Coinbase Lawsuit\n\nIn total, lobby organizations including the Blockchain Association, Crypto Council for Innovation, Chamber of Digital Commerce, DeFi Education Fund, Chamber of Progress, Consumer Technology Association, venture firms like Andreessen Horowitz and Paradigm and half a dozen academics filed a total of six briefs, not including the Senator’s.\n\nBlockworks: DeFi Education Fund seeks FOIA amid SEC inaction on securities dispute\n\nThe DeFi Education Fund recently utilized the Freedom of Information Act to file a request for additional information regarding the Securities and Exchange Commission’s decision not to provide clarity on the classification of syndicated loans as securities.\n\nPOLITICO: What’s that cloud look like? To Chopra, stability risk\n\n“He previously tweeted about being pro-innovation and wanting to keep development of this industry onshore,” DeFi Education Fund CEO Miller Whitehouse-Levine told MM. “Given the contents of the bill, I do think his position has apparently changed.”\n\nThe Block: Senate bill would tighten money laundering and sanctions rules for DeFi\n\nThe bill would “effectively ban DeFi development in the country,” argued Miller Whitehouse-Levine, CEO of the DeFi Education Fund, in a statement decrying the legislation. “Unfortunately, this approach is not only a disproportionate response to the illicit use of DeFi but also risks undermining US law enforcement’s existing insight and reach into peer-to-peer crypto activity,” Whitehouse-Levine said.\n\nBlockworks: SEC’s proposed exchange definition would cause ‘de facto expatriation’ of DeFi companies\n\n“The upshot of this technological reality is that holding DeFi protocols to the requirements of the regulatory regimes governing national securities exchanges and ATSs would result in their de facto expatriation from the United States. DeFi is rapidly gaining trading market share in crypto assets, especially after recent and high-profile fraud and compliance issues at leading centralized and intermediated non-U.S. crypto asset exchanges,” the DeFi Education Fund (DEF) wrote in a 47-page response letter.\n\nCoinDesk: U.S. SEC Out-of-Bounds in Dragging DeFi Into Proposed Exchange Rule, Industry Says\n\n“The proposal would operate as a blanket de facto banishment of DeFi from the United States,” the DeFi Education Fund, a lobbying group, wrote in its comment letter. “The actions and words of the commission and agency personnel have created great confusion.”\n\nThe Capitol Account: Talking `Impact’ Litigation; SEC Officials on Hotseat in House; Stepping up Merger Scrutiny; Banks Bash SEC Custody Plan\n\nAmanda Tuminelli, who is the new chief legal officer at the DeFi Education Fund, thinks there is probably a better way to get answers – in court. Her role at the decentralized finance advocacy group is to spearhead “impact litigation” designed to bring more clarity about the rules digital assets need to follow. And even though she’s only been on the job since March, Tuminelli already has a few targets in mind. (SEC Chair Gary Gensler may want to watch out.)\n\nAxios: U.S. Treasury looks at DeFi and crime\n\n“Those frameworks were developed based on how the global economy worked in the 1970s, and are predicated on the assumption that transactions must occur through custodial financial intermediaries,” DeFi Education Fund CEO Miller Whitehouse-Levine said in a statement.\n\nPOLITICO: DeFi’s turn in the barrel\n\n“DeFi protocols function in a different way than traditional finance, and trying to apply existing AML/CFT rules, isn’t going to accomplish AML/CFT objectives,” DeFi Education Fund policy director Miller Whitehouse-Levine told MM.\n\nBlockworks: Treasury Review Acknowledges Traditional Finance, Not DeFi, Preferred by Criminals\n\n“While the assessment does, at times, demonstrate a sophisticated understanding of the DeFi landscape, it evidences a tension between the idea that decentralization is irrelevant in determining compliance obligations under existing AML/CFT controls and the idea that decentralized protocols are a novel tool unanticipated by existing frameworks,” Miller Whitehouse-Levine, CEO of the DeFi Education Fund, said in an email.\n\nThe Defiant: Gensler Refuses To Call Ether A Security At Congressional Hearing\n\nMiller Whitehouse-Levine, who heads the DeFi Education Fund crypto advocacy group, said Gensler’s appearance “underscores the thesis that [he] has made the policy choice to try and ban crypto in this country.”\n\nThe Defiant: “Everybody” Should be Concerned About the SEC’s Proposed Rule Change for DeFi\n\n“Everybody and their mother,” should be concerned, Whitehouse-Levine said in an interview. Validators of blockchain transactions, members of DAOs, and open source developers, are potentially liable, he said. The DeFi Education Fund is a research firm which advocates for DeFi with policy-makers.\n\nCapitol Account: Grading Gensler: Advocates Assess SEC Chief Two Years In\n\nTop line: F- [grade]. Chair Gensler has morphed the SEC from being the gold standard of financial regulators – an agency that protects American investors and the primacy of its capital markets by adapting its statutorily-authorized regulations to innovative technologies – to being an agency that actively engages in merit-based policymaking. That approach is undermining the SEC’s pursuit of its mission and its credibility already. And in turn, it risks doing lasting damage to the agency and the markets it oversees.\n\nThe Block: Fighting a digital dollar becomes new conservative crypto cause to champion\n\n“A CBDC’s potential for misuse is quite potent. It could severely encroach on Americans’ right to financial privacy and enable an unprecedented degree of control over individuals’ private transactions,” Whitehouse-Levine said. “Protecting the right to financial privacy is a non-partisan issue.”\n\nReuters: Wall St watchdog shortens time-frame for stock trades, proposes new investment adviser rules\n\nHowever Miller Whitehouse-Levine, policy director at DeFi Education Fund, described Gensler’s position as an attempt to cut off digital assets from the traditional financial system. “This should end any doubt that ‘come in and register’ is a fig leaf for the SEC usurping Congress to block crypto in the U.S.,” he said.\n\nNew York Times Dealbook: Investors Await a Momentous Inflation Report\n\nThe left-right divisions run deep. Despite a shared sense of urgency, the gulf between party leaders on the details of any approach to crypto regulation is wide, said Miller Whitehouse-Levine, policy director of the DeFi Education Fund, a crypto lobbying group. “It’ll be a lot of work to get consensus,” he said, and he doesn’t foresee legislation passing any time soon.\n\nCapitol Account: Calling SEC Investor Rule Discriminatory, House Republicans Plot Fresh Push to Open Up PE and Hedge Funds to the Masses\n\nHere’s a response from Miller Whitehouse-Levine, the DeFi Education Fund’s policy director: “The blog post is mistitled. The potential (further) broad decline in digital asset prices, the potential composition of custodial stablecoin reserves, and the potential mass use of a digital asset for payments are not DeFi issues.”\n\nCointelegraph: Blockchain privacy groups urge new US Congress to protect privacy rights\n\nAt the time of writing, the letter had 36 signatories, including industry players such as the Blockchain Association, DeFi Education Fund, Ledger, Nillion Network, Protocol Labs and Proton.\n\nCapitol Account: Crypto Turf Fight: a Progressive Attack on CFTC’s Behnam Gets Personal – and Ugly\n\nAs the head of the DeFi Education Fund, Miller Whitehouse-Levine often notes that he spends much of his time explaining to confused lawmakers what his industry does. Toward that end, the group isn’t wasting any time getting its education efforts going with the new Congress. Today, it sent a letter to every senator and House member that included a “DeFi FAQ,” and encourages them to pass legislation that recognizes the benefits of decentralized finance. You can read the note here.\n\nTIME: A Crypto Reckoning Isn’t Coming Yet\n\nBut Miller Whitehouse-Levine, policy director of The DeFi Education Fund, told TIME in a phone interview two weeks ago that “I don’t think this hearing is indicative of momentum behind the DCCPA. If anything, I think it has added much more to think about in the next few months.”\n\nThe Block: Crypto industry protests against Treasury’s proposed tax reporting regulation\n\nThe Defi Education Fund said earlier this month in its letter that the proposal stretches the definition of a broker beyond its constitutional limits and that the Treasury is essentially creating a new kind of broker called a “digital asset middleman.” The proposed regulations’ definition of ‘digital asset middleman’ is vague to the point of being unintelligible,” Miller Whitehouse-Levine and Amanda Tuminelli — CEO and chief legal officer of advocacy group the DeFi Education Fund respectively — wrote in a letter to the IRS.\n\nFortune: The obscure DAO at the center of a case that could determine the future of crypto\n\n“These are questions of fairness and liability that are generally handled via state law,” said Miller Whitehouse-Levine, policy director at DeFi Education Fund.\n\nThe Lexcon Crypto Show: Was the CFTC right to sue Ooki Dao? Hear from Miller Whitehouse-Levine of DEF\n\nMiller Whitehouse-Levine of the DeFi Education Fund joins Andrew in the studio today to discuss the latest news and activity of the DEF.\n\nThe ReFi DeFi Podcast: The DeFi Education Fund\n\nIt’s clear that US regulators are shining a spotlight on DeFi. It’s essential that we have a group that is dedicated to educating policymakers and shaping the future of DeFi. In this episode, we had the honor to speak to Miller Whitehouse-Levine, Policy Director at the DEF.\n\nThe New York Times’ Dealbook: Warning Signs Multiply Ahead of Pivotal Fed Interest Rates Meeting\n\nThe issue has sparked a feud among crypto insiders. “Decentralization is a spectrum, and where the line is drawn between centralized and decentralized is a policy choice that Congress will eventually have to make,” said Miller Whitehouse-Levine of the DeFi Education Fund.\n\nThe Capitol Account: DeFi Advocate Talks Hacks, Fraud and How His Industry Can Revolutionize Finance\n\nThis week we chatted with Miller Whitehouse-Levine, the policy director of the DeFi Education Fund. An early crypto enthusiast, he may have one of the hardest jobs in Washington: explaining to confused lawmakers and regulators what decentralized finance is – and why they shouldn’t be afraid of it.\n\nDecrypt: CFTC Sues a DAO, Raising Legal Questions for DeFi Founders and Users\n\nIn an emailed statement to Decrypt, the DeFi Education Fund called the lawsuit against Ooki DAO an “unprecedented action [that] seeks to create novel policy in response to novel issues, all via an enforcement action.”\n\n[end]\n\n6 Likes\n\nDoo_StableLab\n\nApril 12, 2024, 6:07pm\n\n3\n\nAs much as the proposal is understandable and unpopular for us to do vote against it, we will be voting against this proposal in the current state once live. It’s been almost 2 years since DeFi Education Fund posted any updates on this forum despite taking such a significant amount (which was also one million $UNI as they shared).\n\nAlso even with this info, why is the team asking for $8 million? I believe to give the community more options, it should be a snapshot voting with ranges. It seems more justified to potentially support 2x or 3x of such cost but 8x seems excessive.\n\n6 Likes\n\nmillerDEF\n\nApril 12, 2024, 6:21pm\n\n4\n\nThank you for your feedback and thoughts. Here are weekly updates of what we’ve been working on since, which we can definitely also post to the forum going forward: https://defieducationfund.substack.com/.\n\nDoo_StableLab\n\nApril 12, 2024, 6:47pm\n\n5\n\nWe are aware of updates via other means such as Twitter. But it’s more of the team taking the grant and literally did not even think of communicating with the community for many years until now just to ask for more funding\n\n3 Likes\n\nDoo_StableLab\n\nApril 12, 2024, 6:52pm\n\n6\n\nOnce this passes but even if it’s not passed, We suggest the DEF to share with the Uniswap community (ideally via forum) twice per year how the DEF has been benefiting the Uniswap community. We know accountability and transparency are not part of the agreement and we as the community can’t enforce them. But we believe those steps would be beneficial\n\n2 Likes\n\nmillerDEF\n\nApril 12, 2024, 7:09pm\n\n7\n\nUnderstood. I’m glad other means have been working at least a bit, and I’m sorry that not regularly posting our updates directly in the forum gave off that impression because we do think about it and want folks to know what we’ve been up to so we’ll do that going forward.\n\n1 Like\n\nmillerDEF\n\nApril 12, 2024, 7:09pm\n\n8\n\nThat’s an excellent idea. We’ll do this going forward regardless of outcome here. Thank you\n\n1 Like\n\nDoo_StableLab\n\nApril 12, 2024, 8:03pm\n\n10\n\nThank you. That would be appreciated\n\n1 Like\n\nUserisky\n\nApril 12, 2024, 8:19pm\n\n11\n\nIt’s understandable to seek additional funds while the momentum is strong. The DeFi Education Fund has accomplished significant work since its inception with its initial funding. However, it has demonstrated through its actions over the past few years that it is a separate entity from the UNI DAO. Funding should be sourced from the broader crypto community.\n\nFeedback on DeFi Education Fund’s transparency:\n\nAs noted by @Doo_StableLab, there have been no updates in the forums for two years. Even the updates on the DeFi Education Fund’s website lack detail. It is essential to clearly outline expenditures and the run rate. Additionally, it does not create a good image that the 0x address of the initial DeFi Education funding is not publicly displayed in this proposal.\n\nFeedback on DeFi Education Fund’s Marketing:\n\nIf funds need to be raised, a stronger marketing campaign should be launched to engage the larger crypto ecosystem. One notable example is when the Judge in Coinbase’s case referred to the amicus brief as one of the best, calling it the “DeFi People” brief. Utilizing this name as a slogan could attract more support and donations. Merchandise such as T-shirts and hats could also be produced, or even rebranding to “DeFi People Fund”. Additionally, example can be taken from how Coinbase merchandise has ran its marketing campaign.\n\nFunding Amount:\n\nThe proposed amount is quite high. The UNI DAO has struggled to meet its basic funding needs, with no sustainable income. Selling UNI tokens negatively affects smaller airdrop recipients who have held or purchased more over the years. There has been a 50% drop in just the last weeks for those who believed the UNI DAO was moving towards sustainability through the fee switch, which now seems unlikely.\n\nSeek funding from large VC firms that have profited the most from buying seed rounds across the crypto ecosystem and have substantial cash reserves. Stand with the true DeFi people and secure funding from those who possess it.\n\n6 Likes\n\nlex-node\n\nApril 12, 2024, 9:15pm\n\n12\n\nYou guys know I support and respect you as lawyers, and you’ve done some great work, but AFAIK you have flagrantly broken almost every transparency and accountability promise made during the initial solicitation–which I and others predicted would happen. You even had technical assistance offers from projects like Tally to help remain transparent and accountable, and instead you went completely offchain and opaque and dumped UNI way faster than indicated.\n\n$30M is a lot of money and we don’t know how it was spent–I have to suppose it mainly benefited whiteshoe biglaw partners who mostly do not care about crypto\n\nYou also do not do a very good job looping in the interests of smaller non-blue-chip, non-a16z/Paradigm-backed projects and the broader legal community. I realize I’ve personally collaborated with you guys on a few things but overall it feels very opaque and like a small cabal of elite lawyers dominating all crypto legal discussions/decisions, mostly behind closed doors while using “politicians won’t talk to us if we collaborate more (outside our bubble)” as an excuse.\n\nThis is not how DAOs are supposed to work. You should create a more accountable & transparent structure for this funding round–not just based on promises this time, but with a real structure such as use of a DAO-adjacent multisig with some checks/balances on it as well as concrete commitments to loop in the broader cryptolaw community–and then I would happily support it as you have done some great work.\n\nEven if one accepts that spending another $8M in UNI tokens on legal is a great idea, there are much more effective ways to spend than paying biglaw partners $1k+ per hour to spill ink. For example, what massive legal safety benefits FOR THE ENTIRE ECOSYSTEM could $8M in funding to a decentralized front-end project deliver? We all know that ultimately, decentralization is the only protection against fickle regulators and governments.\n\nThe other thing is that if you’re going to throw millions of dollars at lawyers with little extrinsic oversight or transparency, at least give some thought to the governance. One board member is CEO of Polygon, another is GC of Polygon, and another is GC of Variant, which is heavily invested in Polygon–Polygon is a fine project, I have nothing against it, but how does this make sense as governance for an organization that is supposed to be for all of DeFi???\n\nP.S.–this post from Cobie is still the funniest take of all time on this subject: https://gov.uniswap.org/t/proposal-removal-of-established-cranial-follicles-fund/13314\n\n10 Likes\n\nmillerDEF\n\nApril 12, 2024, 9:27pm\n\n13\n\nThank you for your thoughts, Userisky. Agreed that our funding should be sourced from additional sources as our work is a public good, which we’re trying to source as well.\n\nHere’s a more detailed breakdown of everything we’ve spent to date. My bad: here’s the multisig to which the original tokens went. As noted, we began selling half of that grant in February of this year and will complete those sales in July of 2025.\n\nThe “DeFi People” comment has been the highlight of my year and the outcome on the SEC’s broker allegation is the most significant legal win in the US for DeFi to date, in my opinion. We’ve actually just “soft-launched” a merch store so agreed there.\n\nThanks again\n\n2 Likes\n\nmillerDEF\n\nApril 12, 2024, 9:36pm\n\n14\n\njust corrected the wrong link there*\n\npcfreak30\n\nApril 12, 2024, 10:36pm\n\n15\n\nHere is my 2C: https://twitter.com/pcfreak30/status/1778907493093040268\n\nTL;DR, if anything should be funded it should be on public goods and not capital hill. I get our lobby groups are trying to get warren/garry/biden to back off, and getting paid to do what they are best at, but the real solution is to stop the decentralization theatre and just put any money to actual decentralization efforts.\n\nAn example is the DeFi Collective.\n\nWe might need to have decent government regulation, but we need to be censorship-proof even more. The entire culture ethos started from BTC and saying frankly, screw the government, and ended up to now trying to bend over to make them happy.\n\nWe got wayy off track\n\nIm not active in uniswap, but I felt I needed to put my tiny voice in anyways.\n\n5 Likes\n\nkfx\n\nApril 13, 2024, 6:55am\n\n16\n\nGreat timing of your proposal and great work, judging from the references you provide! Appreciate your service.\n\nThat said, I will vote against this request. I think it’s fair to describe this funding request (and the previous one in 2021 too) as public goods funding, and my delegate profile clearly says that I don’t believe the Uniswap DAO should fund public goods. This is both due to neutrality issues, and because these days DEXes have relatively small profit margins, especially compared with L1/L2 projects.\n\nPerhaps it can be argued that Uniswap should fund this not as a public good, but because the protocol itself needs this kind of legal defense. But there are two problems with this. I agree that DeFi has the burden to defend itself, but the burden should be shared between all the leading DeFi protocols. Uniswap’s fair share may be high, but it’s not 100%. Moreover, the cost-efficiency of the plans are not clear. The DAO, especially delegates outside the US, don’t have the means to independently evaluate that.\n\n2 Likes\n\ndevinwalsh\n\nApril 16, 2024, 6:29pm\n\n17\n\nI am supportive of this proposal.\n\nThe DeFi Education Fund is the only crypto nonprofit which is focused exclusively on protecting DeFi and decentralized protocols more generally (as opposed to, for instance, protecting centralized exchanges).\n\nThey are a small yet prolific team on the front lines - they have not only defended the space but gone on the offensive in recent months.\n\nI’ve read through some of the critiques around communication and the funding ask more generally:\n\nAgree that the team could have provided more transparent communications directed to the Uniswap community specifically. I will note the team has regularly updated their Substack and Twitter however, so this seems more like an issue of mis-communication rather than a broader lack of transparency. Happy to work with the DEF to organize more regular (at least bi-annual as suggested by @Doo_StableLab above) community updates if this goes through.\n\nAs to broader funding, I don’t know there is a better anchor donor that Uniswap. The Uniswap Protocol is one of the largest targets in the space. It is at the same time one of the most used Protocols, and to the extent its growth or innovation is negatively impacted by misguided policies or antagonistic regulatory action, it negatively impacts not only Uniswap but the entire space. At the same time, Uniswap has one of the largest treasuries in the space. The DEF’s ask is ~0.2% of the Treasury. (While Uniswap would be an anchor, 8 other teams and 70+ other individuals have donated, so Uniswap is not the only donor)\n\nIf we want DeFi, and Uniswap, to survive, we need folks fighting for us. There may be areas to improve the proposal (for instance, more frequent and direct communication), but I think it would be a loss for us all to not support it on the whole.\n\n4 Likes\n\nDoo_StableLab\n\nApril 16, 2024, 6:39pm\n\n18\n\nDifferent perspectives are welcome but I think this is an example of why the community is asking for more transparency and accountability in the process. Most of requests that have been in the discussion in Uniswap governance are even less than 0.02% of the treasury. But even for those, a lot of discussions and process are needed. For example, we saw them in such as recent growth initiatives and now potential delegate reward program. So I think it’s reasonable that the community desires such changes this time\n\n3 Likes\n\ncharlus\n\nApril 16, 2024, 6:42pm\n\n19\n\nStrategic & high-impact works. Yes it is, ofc.\n\nDoo_StableLab\n\nApril 16, 2024, 6:55pm\n\n20\n\nWhich is also why giving the community different options (range of funding) seems reasonable\n\nUserisky\n\nApril 16, 2024, 11:31pm\n\n21\n\nThe DEF’s ask is ~0.2% of the Treasury.\n\nThat is one way to look at it. The other perspective is that the liquidity depth for UNI is very shallow. The total value locked (TVL) for all pairs is about $34 million for UNI, according to Uniswap.info. The bid side is even worse; if $7 million worth of UNI is market-sold, only $3 million USD would be received. In other words, the ask of this proposal represents 60% of on-chain liquidity, which is a significant request. Even if sold through off-chain market makers, it will have large impacts, either now or in the future.\n\nThis is why it’s very important to get the backbone of the protocol, i.e., liquidity providers, involved in governance. Everything done here is at their expense, from funding the Uniswap Foundation, Grants, liquidity provisions, fee switch, funding the DEF, and more.\n\nMore needs to be done to address the utility of UNI itself if we are to view ourselves as an open public good pocketbook.\n\nA few ideas in the past that were supposed to address this have gone silent/forgotten:\n\nUNI as an oracle token, by Vitalik\n\nhttps://gov.uniswap.org/t/uni-should-become-an-oracle-token/11988\n\nUNI as a base token pair/credit facility, by mjc716\n\nhttps://gov.uniswap.org/t/a-completely-new-uni-token-model-for-v4/21647\n\n3 Likes\n\nnext page →\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nGovernance Proposal 005 - DeFi Education Fund\n\nRequests for Comment\n\n32\n\n16235\n\nFebruary 19, 2022\n\nConsensus Check - UNI should fund a political defense organization for decentralized finance\n\nRequests for Comment\n\n105\n\n20223\n\nJune 17, 2021\n\nTemperature Check - Funding a Political Defense of DeFi\n\nTemperature Check\n\n56\n\n17227\n\nAugust 25, 2021\n\nConsensus Check - UNI should fund a political defense organization for decentralized finance (copy)\n\nConsensus Check\n\n24\n\n8626\n\nJune 16, 2021\n\nDemand for Transparency from DeFi Education Fund\n\nGovernance-Meta\n\n24\n\n8397\n\nNovember 19, 2021","tokens":14691,"crawled_at":1791195554178}
+{"id":10536,"url":"https://docs.sui.io/develop/manage-packages","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Managing Packages | Sui Documentation","text":"PackagePackageSmart contracts on Sui. management on Sui covers the tools and workflows for maintaining Move packages after initial development. This includes resolving dependencies, managing package addressesAddressA unique, anonymous identity on a blockchain network. across networks, and verifying that deployed packages match their published source code.\n\nPackage security\nAn upgradeable package's UpgradeCap controls all of its future behavior, so treat package management as a security-sensitive activity. Verify the exact package IDs of your dependencies, and deliberately choose between an immutable package and a custom upgrade policy rather than defaulting to single-key upgrade authority. See Security Best Practices for guidance.\n\nMove packages on Sui are immutable objects. Once published, a package's bytecode never changes. Upgrading a package publishes a new objectObjectThe basic unit of storage on Sui. at a new address and links it to the original through the upgrade chain. This means every version of your package coexists onchain, and any package can call any version.\n\nManaging packages correctly requires you to:\n\nTrack which package address corresponds to which network (DevnetDevnetFor developing and testing new features., TestnetTestnetStaging network for testing changes before production deployment., MainnetMainnetProduction network for live transactions and real-value assets.).\n\nPin dependency versions so your builds stay reproducible.\n\nDecide who controls upgrades and under what conditions.\n\nVerify that a deployed package matches its source code.\n\nWhat does the UpgradeCap control?​\n\nWhen you publish an upgradeable package, Sui returns an UpgradeCap object to the publisher. Whoever holds that object can upgrade the package. The UpgradeCap is the sole source of upgrade authority by default, so its ownership determines who controls the package's future behavior.\n\nYou have several options for handling the UpgradeCap:\n\nKeep it in a wallet. The simplest option. One key pair controls upgrades.\n\nTransferTransferChanging the owner of an asset. it to a multisigMultisigMulti-signature transactions that require multiple keys for authorization. address. Requires multiple signers to approve upgrades.\n\nWrap it in a custom upgrade policy. Lets you enforce on-chain rules such as time locks or governance votes before an upgrade proceeds.\n\nDestroy it. Makes the package permanently immutable. No further upgrades are possible.\n\nChoosing an upgrade policy is a one-time decision with long-term consequences. Consider your security model before publishing.\n\nMove Package Management\nLearn how to use the Move package manager system.\n→\nAddress Management (Legacy)\nLegacy documentation for the pre-v1.63 Move.lock-based address tracking system. For the current package system, see Move Package Management.\n→\nSource Verification\nVerify that a Move source package compiles to the bytecode of an onchain package using sui client verify-source.\n→\n\nWhat does the UpgradeCap control?\n\nWas this page helpful?","tokens":758,"crawled_at":1791195558524}
+{"id":10537,"url":"https://blog.trailofbits.com/","domain":"blog.trailofbits.com","chapter":"security_audits","title":"The Trail of Bits Blog","text":"We’re releasing SequenceHash and its sister function SequenceMAC, a pair of related hash constructions that bring secure multihashing to developers using hash functions other than Keccak.\nCombining threshold signature schemes with trusted execution environments (TEEs) can strengthen MPC deployments, as long as you treat the TEE as a defense-in-depth layer rather than a substitute for a sound protocol.\nSAML, the XML-based authentication protocol that birthed the SSO industry, is fundamentally flawed due to XML complexity, canonicalization issues, enveloped signatures, and design ossification, making it vulnerable to signature wrapping attacks and parser differentials that persist despite decades of awareness. Organizations should migrate to OpenID Connect (OIDC), which avoids these pitfalls through simpler JSON-based design, detached signatures, and agile evolution.\nBefore code review even starts, agents let us build custom tooling and formal models. Here’s how six months of building with AI agents helped us find real issues in our Miden zkVM audit.\n1Password’s benchmark misrepresents AI patching. We share real-world data on human and agent patch quality from our consulting work and Patch the Planet and release two agent skills for testing and reviewing security fixes.\nFermat’s margin was too narrow for his proof. Ours would have fit just fine, thanks to a wonderfully cursed Lean bug.\nYou can no longer assume a mere VM will contain a sufficiently advanced AI agent.\nWe found and reported a bug in Provenance Blockchain, a public proof-of-stake chain built on Cosmos SDK, that lets any user grant themselves admin control over marker accounts without holding a single token.\nSignal recently launched Automatic Key Verification, a feature that helps validate that your chats are secure without requiring direct safety number comparison. Trail of Bits built and operates one of the three auditors that make this system trustworthy.\nThis blog post details security risks to consider when integrating AWS Nitro Enclaves with AWS KMS.\nThis blog post identifies seven recurring failure patterns in application and hook code, including missing caller checks and accounting bugs that still satisfy the PoolManager’s settlement invariant.\nOver the first few weeks of Patch the Planet, our engineers found three techniques for using /goal, which hands Codex an open-ended objective and lets it work independently toward a success condition.\nWe’ve added a new chapter to our Testing Handbook: a comprehensive guide to security testing Rust programs.\nIn April we released Mewt, our open-source mutation-testing engine that finds the gaps in your test suite. Today we’re expanding it with support for DAML, the language Canton Network applications are written in.\nA Patch the Planet field report: GPT-5.5-Cyber built a bespoke zlib fuzzing campaign in a single day, work that once took skilled researchers weeks.\nWe added post-quantum cryptography support to pyca/cryptography, the eleventh most-downloaded Python package on PyPI, putting quantum-resistant ML-KEM and ML-DSA algorithms one pip install away for the entire Python ecosystem.\nPatch the Planet is our joint initiative with OpenAI to assist critical open-source software in the age of machine-speed vulnerability research.\nWe found hundreds of weak RSA and DSA keys with biased bits that we could quickly factor using a new polynomial-based cryptanalytic technique.\nWe recently bypassed ClawHub’s malicious skill detector, Cisco’s agent skill scanner, and all three of the scanners integrated into skills.sh.\nWe improved YAML anchor support in zizmor and tested it against 41,253 real-world GitHub Actions workflows from high-value open-source projects.\nWe built gosentry, a fuzzing-oriented fork of the Go toolchain that keeps the standard fuzzing workflow while using a stronger stack underneath.\nHere is a walkthrough of our solutions to two C/C++ security challenges from the new C/C++ chapter in the Testing Handbook: a Linux ping program with an inet_ntoa global buffer gotcha and command injection, and a Windows driver with registry type confusion bugs that can escalate from local DoS to a kernel write primitive.\nWe added LibAFL support to Ruzzy, our coverage-guided fuzzer for pure Ruby code and Ruby C extensions. This gives Ruby developers and security researchers access to a more advanced and actively maintained fuzzing engine without changing how they write their fuzzing harnesses.\nTrailmark turns source code into a security-analysis graph, powering eight Claude Code skills for blast radius, taint propagation, and mutation test triage.\nTrail of Bits discovered and exploited memory safety and logic vulnerabilities in Google’s Rust zero-knowledge proof code to forge a proof claiming better quantum circuit performance metrics than Google’s original results, demonstrating unique security risks in zkVM systems.","tokens":1226,"crawled_at":1791195558763}
+{"id":10538,"url":"https://a16zcrypto.com/posts/article/statement-of-digital-assets","domain":"a16zcrypto.com","chapter":"research","title":"On crypto financial reporting: The Statement of Digital Assets - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nOn crypto financial reporting: The Statement of Digital Assets\nEmily Westerhold\n10.03.24\n\nTags & Share Tags\ncompany building\nmental models & frameworks\ntech trends\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nIn an ideal world, every company holding digital assets would follow a standard reporting practice — allowing operators and investors to intuitively and transparently understand the liquid value of their assets.\n\nThis is the purpose of the new Statement of Digital Assets (SoDA), a standardized report that aims to provide a lasting and transparent bridge between accurate GAAP reporting of digital assets and the details from multiple wallets, centralized exchanges, and other cryptographically based ownership and/or custody arrangements. SoDA is designed to address many of the accounting nuances associated with businesses that interact with digital assets.\n\nThe need for SoDA\n\nTraditionally, this is what the balance sheet is for: to report what a business owns (assets), what it owes (liabilities) and what the ownership or equity in the business is. Unfortunately, existing reporting standards for businesses interacting with digital assets can make the balance sheet opaque. And current US GAAP (Generally Accepted Accounting Principles) reporting for recording digital assets “breaks” several core purposes of a balance sheet – primarily understanding and assessing liquidity. While the balance sheet should, in principle, tell the complete financial story for any entity, for those that hold and transact in digital assets, it does not.\n\nAnd the need for such clear reporting has only grown. The number of “crypto native” and traditional businesses that transact with digital assets has seen unprecedented growth. This adoption of a new asset class has necessitated an increased focus on accounting for tax reporting and operations management purposes. But IRS (The U.S. Internal Revenue Service) and FASB (the Financial Accounting Standards Board) rules continue to evolve, and the systems required to convert on-chain activity to the general ledger are developing in lockstep with the blockchains they monitor. But even with recent FASB (Financial Accounting Standards Board) changes for digital asset accounting, the guidance isn’t complete.\n\nFurther, recent FASB guidance requires fair market value reporting of select digital assets. But the new rules are not complete: They exclude NFTs (non-fungible tokens), native tokens (tokens created or issued by the reporting entity), select tokens representing real world assets (RWAs), and wrapped tokens. These excluded digital assets continue to be defined as indefinite-lived intangible assets that necessitates the valuation at the lower of cost or impaired value (“LOCOM” or “BV”) and can only be marked down, never marked to market. This range of treatments complicates balance sheet reporting, by reporting significantly different valuation methodologies alongside one another. Further complicating matters is the balance sheet reporting of stablecoins, essentially adding a third distinct type of digital asset that should be broken out in the same context. This is essentially comparing Cars (crypto @ FV) vs. Motorcycles (crypto @ LOCOM) vs. Boats (stablecoins).\n\nAt the highest level, this challenges the operation of digital asset-based businesses because questions persist regarding operating runway, tax liability, and fully understanding a companies’ digital asset treasury. It also makes it difficult to assess, and nearly impossible to report, a firm’s true liquidity to analysts, investors, regulators, and auditors.\n\nWhat SoDA does\n\nSoDA also helps calculate fair market value to provide a more rational sense of liquidity. Taken with a company’s fiat holdings and select other assets, SoDA presents a complete picture of a company’s digital asset liquidity. By reporting at the wallet/asset level and providing the corresponding FV and LOCOM, SoDA provides all the backup for the digital asset balance sheet entries in addition to providing better visibility into the aforementioned operating metrics.\n\nAdditionally, when it comes to investor reporting best practices, most investors expect some level of regular financial reporting in accordance with investor information rights reflected in their deal terms. Under the current guidance, evaluating the liquidity or operating runway of a company with material digital assets on the balance sheet can be difficult. SoDA is a tool that can help both operators and investors alike.\n\nThis project brought together many people across the industry who embraced the collaborative, open source crypto ethos to create our own “public benefit” best practice that was a grassroots effort — not something imposed or created by FASB. Sharing best practices with one another is something that comes naturally in the space, and creating clear reporting that anyone with a basic financial background can understand will move the industry forward. We started with the balance sheet because of a treasury’s importance to crypto-native businesses, but we’ll continue to work on additional sections, and have started thinking about how to include overall financial and operational best practices for crypto startups more broadly.\n\nCrypto companies should implement this standard in their financial reporting and operations. The bottom line: More transparency in financial statements leads to better business decisions.\n\nIf these tools work for you, please consider giving them your endorsement at sodafinance.xyz. By using and endorsing SoDA, you are joining a growing network of professionals committed to advancing transparency, accuracy and best practices in the rapidly evolving landscape of digital assets.\n\nread the whitepaper\n\n***\n\nEmily Westerhold is a partner on the crypto team, focused on finance and operations advisory. Before joining Andreessen Horowitz, she was most recently the CFO of VSCO, where she spent 7 years helping to build and scale the company and still serves on the board. Prior to VSCO, she worked in various finance and accounting roles and began her career at PwC.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investment-list/.\n\nCharts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures/ for additional important information.","tokens":2224,"crawled_at":1791195567182}
+{"id":10539,"url":"https://docs.sui.io/develop/accessing-data","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Accessing Data | Sui Documentation","text":"Data access on Sui is the process of reading onchain state, including transactions, checkpoints, objects, and events. Sui provides multiple interfaces for accessing this data, each optimized for different use cases.\n\nChoosing a data access method​\n\nMethodBest forLatencyHistorical depth\nGraphQL RPC\nFlexible queries, app backends, explorers\nLow\nCurrent state and recent history\n\ngRPC\nHigh-throughput streaming, real-time pipelines\nLowest\nCurrent state and recent history\n\nCustom indexing\nApplication-specific data models, analytics\nVaries\nFull history (you control retention)\n\nArchival Store\nHistorical lookups after full nodeFull nodeResponsible for validating blockchain activity. pruning\nHigher\nComplete history from genesis\n\nFor most applications, start with GraphQL RPC. If you need real-time streaming or higher throughput, use gRPC. If you need a custom data model or application-specific indexes, build a custom indexing pipeline. For historical data beyond what full nodes retain, use the Archival Store.\n\nYou can also subscribe to onchain activity through events, which MoveMoveAn open source programming language used for all activity on Sui. modulesModuleA component of a Move package that defines interaction with on-chain objects. emit during transactionTransactionA number of commands that execute on inputs to define the result of the transaction. execution. Authenticated events provide cryptographic proof of event origin for cross-system verification.\n\nFor a list of hosted RPC providers, see RPC Providers.\n\nData Access Interfaces\nOverview of the types of data access mechanisms available in Sui.\n→\nRPC and Data Providers\nThird-party providers offering Sui gRPC, GraphQL RPC, and Archival Store and Service endpoints.\n→\nJSON-RPC Migration Guide\nChoose between gRPC and GraphQL RPC when migrating from the deprecated JSON-RPC API. Includes a method mapping, decision criteria, and common migration gotchas.\n→\ngRPC\nIn this section\nWhat is gRPC?\nQuerying Data with gRPC\ngRPC Migration Cookbook\n\n→\nGraphQL\nIn this section\nGraphQL for Sui RPC\nQuerying Data with GraphQL RPC\nGraphQL Migration Cookbook\n\n→\nArchival Service\nIn this section\nWhat is Archival Store and Service?\nQuerying Historical Data with Archival Service\n\n→\nEmitting Events\nLearn how to define Move event structs, emit events from smart contracts, and process or query them using gRPC, the TypeScript SDK, or a custom indexer.\n→\nAuthenticated Events\nCryptographically verifiable Move events that can be verified by a light client without trusting any intermediary, suitable for trustless event consumption.\n→\nCustom Indexing Framework\nIn this section\nWhat Are Custom Indexers?\nIndexer Pipeline Architecture\nBuild a Custom Indexer\nIntegrate a Custom Indexer\nBring Your Own Store (BYOS)\nIntegrate Data Sources\n+ 1 more\n\n→\n\nChoosing a data access method\n\nWas this page helpful?","tokens":714,"crawled_at":1791195580753}
+{"id":10540,"url":"https://blog.trailofbits.com/2025/02/05/preventing-account-takeover-on-centralized-cryptocurrency-exchanges-in-2025","domain":"blog.trailofbits.com","chapter":"security_audits","title":"Preventing account takeover on centralized cryptocurrency exchanges in 2025 - The Trail of Bits Blog","text":"Page content\n\nThis blog post highlights key points from our new white paper Preventing Account Takeovers on Centralized Cryptocurrency Exchanges, which documents ATO-related attack vectors and defenses tailored to CEXes.\nImagine trying to log in to your centralized cryptocurrency exchange (CEX) account and your password and username just… don’t work. You try them again. Same problem. Your heart rate increases a little bit at this point, especially since you are using a password manager. Maybe a service outage is all that’s responsible (knock on wood), and your password will work again as soon as it’s fixed? But it is becoming increasingly likely that you’re the victim of an account takeover (ATO).\nCEXes’ choices dictate how (or if) the people who use them can secure their funds. Since account security features vary between platforms and are not always documented, the user might not know what to expect nor how to configure their account best for their personal threat model. Design choices like not supporting phishing-resistant multifactor authentication (MFA) methods like U2F hardware security keys, or not tracking user events in order to push in-app “was this you?” account lockdown prompts when anomalies happen invite the attacker in.\nOur white paper’s goal is to inform and enable CEXes to provide a secure-by-design platform for their users. Executives can get a high-level overview of the vulnerabilities and entities involved in user account takeover. We recommend a set of overlapping security controls that they can bring to team leads and technical product managers to check for and prioritize if not yet implemented. Security engineers and software engineers can also use our work as a reference for the risks of not integrating, maintaining, and documenting appropriate ATO mitigations.\nAccount takeover\nWhen the topic of fraud involving crypto comes up, our minds might jump to the FTX collapse, blackmail scams, romance scams, or maybe to social media posts advertising “investment opportunities.” ATO is another common type of fraud that happens due to security failures, even though financial institutions like CEXes that serve US customers must protect their users’ information from (among other harms) unauthorized access.\nIn an ATO, the attacker obtains access to someone else’s account, then locks the rightful account owner out by changing the access credentials. In 2023, the Sift Q3 Digital Trust and Safety Index disclosed an 808% year-over-year increase in reported takeovers of financial (including crypto) accounts, and the Sift Q3 2024 index reported a further increase in ATO across all industries since 2023.\nNot only has ATO become more common, not all platforms have sufficient logging and monitoring in place to be able to detect it when it occurs and alert users promptly. Fewer than half of the victims that Sift surveyed were notified that any data loss or breach had occurred. In addition to damaging user trust in the platform, if users are not quickly and appropriately notified (and steps to prevent further future abuse aren’t taken), ATO can be costly for victims. A 2016 RAND survey of consumer attitudes toward data breach notifications and loss of personal information included the grim statistic that 68% of their respondents had suffered a median financial loss of $864 if their financial information was compromised1.\nAttacker tactics and opportunities\nAttackers can gain initial access to user accounts through multiple vectors. In our whitepaper, we cover common weaknesses that CEX platforms must actively guard against.\nFor example, the user might have failed to use a strong password and a second factor. Maybe the attacker then can brute-force the user password or phish the user into giving up their credentials. But the user might, on the other hand, already leverage every available security feature the CEX provides. The platform might simply not provide appropriately implemented security controls that users need to keep their accounts and funds safe.\nSuppose the platform only supports less-secure second-factor options that aren’t phishing-resistant like SMS, mobile authenticator app, or email. If the user sends their MFA codes to their email account, the attacker could then compromise the email account to secondarily gain CEX account access. Or, if SMS is set as the target CEX account’s second authentication factor, the attacker can SIM swap the user’s phone to receive their second-factor code. Or, if a CEX password reset flow is exploitable, perhaps the attacker can leverage it to bypass needing the user’s second factor at all to achieve ATO.\nAvoiding terrible outcomes\nCEXes (just like any other type of service with people that rely on it) need to leverage strong, intertwined technical security mechanisms, processes, and documentation to defend themselves and their users. ATO not only poses a threat to accountholders’ financial safety, but also reduces public trust in the CEX in question and in cryptocurrency more broadly. At Trail of Bits, we believe that knowledge is our most fundamental defense against threats like ATO. Our whitepaper includes the following:\nDiscussion of common ATO attack methods\nSystem actors common to account takeover threat scenarios\nActionable steps that CEX platforms can take to enhance their systems’ security and to protect their users\nBasic personal security guidelines that CEXes can provide to their end users\nRead more in our full white paper.\nWant to learn more about how to use crypto safely, or how to secure your platform or dapp? We’d love to help.\n1Loss of user funds also might not be the immediate outcome. An attacker might take advantage of a security flaw in a CEX platform to exfiltrate credentials or valid session tokens to sell. Another attacker might buy datasets of credentials or identifiers on the darknet and attempt to validate them against multiple platforms, before reselling just the working entries. This could lead to some time elapsing from an initial account compromise to when attempts are actually made to buy something or to transfer funds using the stolen credentials.","tokens":1534,"crawled_at":1791195595985}
+{"id":10541,"url":"https://a16zcrypto.com/team/jeff-amico","domain":"a16zcrypto.com","chapter":"research","title":"Jeff Amico - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nJeff Amico\n\nFeed\nFilter\n(1)\nclear filters\n\ncategory\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\nrecommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nauthor\n(1) all authors\n@x0rart\n1337 Skulls Sers\na16z crypto\na16z crypto editorial\na16z crypto policy & regulatory teams\na16z crypto Regulatory Team\nAaditya Shidham\nAaron Levie\nAaron Phillips\nAaron Schnider\nAbby Green\nAbdou Ndiaye\nAbhi Shelat\nAbhiram Kothapalli\nAbigail Johnson\nAdam Alter\nAdam Back\nAdam Bry\nAdam Grant\nAdam Ludwin\nAdam Martin\nAdam Thierer\nAdam Zuckerman\nAdela Tomsejova\nAdena Friedman\nAdena Hefets\nAdeniyi Abiodun\nAdina Fischer\nAdrian Cockcroft\nAdrian Fenty\nAdrienne Mayor\nAgostino Capponi\nAiden Slavin\nAileen Lee\nAisha Stephenson\nAJ Shankar\nAlan Knott-Craig\nAlan Schaaf\nAlana Benton\nAlbert Tang\nAlec Nielsen\nAlec Ross\nAlejandro Flores\nAlex Constantinople\nAlex Honnold\nAlex Hutchinson\nAlex Immerman\nAlex Kreitz\nAlex Kroeger\nAlex Le\nAlex Masmej\nAlex Morcos\nAlex Price\nAlex Pruden\nAlex Rampell\nAlex Roetter\nAlex Solomon\nAlex Spector\nAlex Stamos\nAlex Tabarrok\nAlexander (Sasha) Spiegelman\nAlexander Chia\nAlexander Zoppa\nAlexandra Chang\nAlexandria Lafci\nAlexis Lakes\nAlexis Madrigal\nAlexis Ohanian\nAli Ghodsi\nAli Yahya\nAlicia Barone\nAlin Tomescu\nAlisha Litman\nAlison Mangiero\nAlison Martin\nAllison Pickens\nAlyssa Del Bene\nAlyssa Torres\nAmanda Cantor\nAmanda Cassatt\nAmanda Catherine\nAmanda Mulay\nAmanda Tuminelli\nAmanda Tyler\nAmelia Salyers\nAmie Tyrrel\nAmir Shevat\nAmira Yahyaoui\nAmy Abernethy\nAmy Berliner\nAmy Bohutinsky\nAmy Choice\nAmy Cray\nAmy Gill\nAmy Hoemeke\nAmy Kalokerinos\nAmy Robertson\nAna Mostarac\nAna Susi\nAnatoly Yakovenko\nAndie Taylor\nAndisheh Tahriri\nAndre Iguodala\nAndrea Clarke Hall\nAndrea Feinberg\nAndrea Rallo\nAndrea Simon\nAndrea Vinkler\nAndreas Papadimitropoulos, Jr\nAndreessen Horowitz\nAndrew Allen\nAndrew Chen\nAndrew F. Read\nAndrew Green\nAndrew Hall\nAndrew Lakis\nAndrew Lewis-Pye\nAndrew Lo\nAndrew Mason\nAndrew McAfee\nAndrew Milson\nAndrew Omori\nAndrew Radin\nAndrew Rubin\nAndrew Savage\nAndrew Smith\nAndrew Tretyakov\nAndy Beal\nAndy Coravos\nAndy Golden\nAndy Hill\nAndy Milenius\nAndy Rachleff\nAndy Tran\nAndy Walshe\nAneel Lakhani\nAngela Schenone\nAngela Strange\nAngela Tran Kingyens\nAngelica Gehr\nAniket Kate\nAnil Sethi\nAnish Acharya\nAnn Winblad\nAnna Berces\nAnna Jablonski\nAnna Semenova\nAnna Van Meurs\nAnnaLee Saxenian\nAnne Brandes\nAnne Lee Skates\nAnne Lewandowski\nAnne Mitchell\nAnne Yip\nAnnie Collins\nAnnie Duke\nAnthony Albanese\nAnthony Atala\nAnthony Foxx\nAnthony Lee Zhang\nAntonio Viggiano\nAntwone Stigall\nAnu Hariharan\nApril Roth\nAri Emanuel\nAri Juels\nArianna Huffington\nArianna Simpson\nArik Kershenbaum\nArmon Dadgar\nArnie Goldberg\nArsho Avetian\nArthur Brooks\nArun Sundararajan\nAsh Ashutosh\nAsha Christian\nAshley McCollum\nAshley Stern\nAshton Carter\nAtif Mian\nAtul Butte\nAubree Pelaez\nAubrey de Grey\nAugusto Marietti\nAurora Petracca\nAusten Allred\nAustin Guzman\nAustin Marchese\nAustin Wilson\nAva Iravani\nAvery Segal\nAvinash Solanky\nAviv Zohar\nAye Moah\nAzeem Azhar\nBailey Flanigan\nBailey Richardson\nBalaji Srinivasan\nBarry McCarthy\nBart Dessaint\nBeau Cronin\nBeau Woods\nBecky Pferdehirt\nBen Buckwalter\nBen Fielding\nBen Fisch\nBen Gardner\nBen Gomez\nBen Horowitz\nBen Kaufman\nBen Leventhal\nBen Lovell\nBen Napier\nBen Portney\nBen Rubin\nBen Scharfstein\nBen Schecter\nBen Silbermann\nBen Uretsky\nBen Wu\nBenedict Evans\nBenedikt Büenz\nBenjamin Ebner\nBenjamin Hindman\nBenjamin Wittes\nBenjamin Wu\nBennett Carroccio\nBenny Pinkas\nBernard J. Tyson\nBernard Tyson\nBeth Newman\nBethany Coates\nBharat Ramamurti\nBharath Ramsundar\nBill Carr\nBill Frist\nBill Hinman\nBill Janeway\nBill Krause\nBill Macaitis\nBlake Kim\nBlake Masters\nBlake Saari\nBlayne Donnell\nBob Iger\nBob Langer\nBob Moore\nBob Muglia\nBob Sutton\nBob Swan\nBob Tinker\nBob Wachter\nBobby Franklin\nBobby Green\nBobby Kotick\nBobby Wagner\nBoris Sofman\nBoris Wertz\nBrad Feld\nBrad Kern\nBrad Peterson\nBram Cohen\nBrandon Ballinger\nBrandon Barros\nBrandon Cherry\nBrandon Millman\nBrenda Kopf\nBrent McIntosh\nBrett Browman\nBrett Falk\nBrett Hagler\nBrewster Kahle\nBrian Armstrong\nBrian Balfour\nBrian Brooks\nBrian Crnkovich\nBrian Curran\nBrian Grazer\nBrian Koppelman\nBrian McCullough\nBrian Quintenz\nBrian Wilkins\nBridget McDowell\nBrittany Lucas\nBrittney Burrows\nBrooke Sheresky\nBruce Friedrich\nBryan Caplan\nBryan Chiang\nBryan Cox\nBryan Crowley\nBryan Faust\nBryan Houser\nBryan Kim\nBryan Pellegrino\nCaitlin Glazebrook\nCaitlin Johnston\nCaitlin Roberson\nCal Turner Jr.\nCaleb Christian\nCameron Schuler\nCamila De Souza\nCarine Carmy\nCarissa Bilinski\nCarl Agnelli\nCarl Eschenbach\nCarl Narcisse\nCarl Pope\nCarlos Araya\nCarolina Gonzalez\nCaroline Friedman\nCaroline Goggins\nCaroline Horn\nCaroline Moon\nCarolyn Bertozzi\nCarra Wu\nCasey Graul\nCasey Neistat\nCasey Winters\nCassady Churchill\nCassie Faerber\nCecilia Marshall\nCeia Font\nChad Rigetti\nChandra Krintz\nCharles Goetz\nCharles Hubbard\nCharles Koch\nCharlie Keinath\nCharlie Warzel\nChattry Meas\nChelsea Komlo\nChelsea Padilla\nCheng Li\nChris Bennett\nChris Best\nChris Burniske\nChris Curran\nChris DeWolfe\nChris Dixon\nChris Granger\nChris Hauth\nChris Lyons\nChris Messina\nChris Milk\nChris Power\nChris Santa Maria\nChris Wanstrath\nChristian Cachin\nChristian Catalini\nChristian Crowley\nChristian Seifert\nChristina Hampp\nChristina Lopes\nChristina Mercando\nChristina Xu\nChristina Zeidan\nChristine Darden\nChristine Perham\nChristopher Giancarlo\nChristopher Lee\nChristopher Mims\nChristopher Nguyen\nChristopher Rippingham\nChristopher Schroeder\nChristy Hubbard\nCiamac Moallemi\nCindi Zhang\nCindy Tenner\nClaire Austin\nClaire Cain Miller\nClaire Kart\nClaudia Picanco\nClay Shirky\nClayton Christensen\nClayton Gardner\nClifford Woolf\nClint Delapaz\nColin Bryar\nColin Rom\nCollin McCune\nConner Lyons Brown\nConnie Chan\nConnie Guglielmo\nConnor McCarthy\nConnor Moyles\nCorban Bell\nCorey Hawkins\nCorey Waller\nCourtney Dettlinger\nCraig Naylor\nCraig Walker\nCristina Cordova\nCurt Funderburk\nCuy Sheffield\nD'Arcy Coolican\nDaejun Park\nDaisy Linden\nDaisy Wolf\nDaljeet Virdi\nDalton Turay\nDan Berkenstock\nDan Boneh\nDan Frommer\nDan Primack\nDan Romero\nDan Shapero\nDan Siroker\nDan Stein\nDan Warmenhoven\nDan Wendlandt\nDaniel Chao\nDaniel Chen\nDanielle Andrzejewski\nDanielle Clark\nDanielle Looymans\nDanielle Lussier\nDanielle Morrill\nDanielle Shea\nDanny Shader\nDaphne Koller\nDapper Dan\nDaren Matsuoka\nDarin Malter\nDarshan Shankar\nDas Rush\nDave Jagoda\nDave King\nDave Touretzky\nDavid Banks\nDavid Belden\nDavid Damato\nDavid Deming\nDavid George\nDavid Haber\nDavid Hollestelle\nDavid Kerr\nDavid Lee\nDavid Mack\nDavid Madden\nDavid Marcus\nDavid Olson\nDavid Oyelowo\nDavid Pierce\nDavid Reich\nDavid Rumsey\nDavid Schweikert\nDavid Sinclair\nDavid Sverdlov\nDavid Tse\nDavid Ulevitch\nDavid Weiden\nDawn Lepore\nDawn Nott\nDeborah Embaie\nDeena Elitreby\nDeepak Maram\nDenis Nazarov\nDenis Young\nDenise Gonzalez\nDerek Dolin\nDerek Thompson\nDerrick Harris\nDevin Finzer\nDevon Zuegel\nDiana Peña\nDiane Greene\nDick Costolo\nDieter Shirley\nDiishan Imira\nDiogo Monica\nDominic Shine\nDominique Reliford\nDon Duet\nDon Faul\nDorris O'Brien\nDoug Ducey\nDoug Folden\nDoug McCracken\nDouglas Argueta\nDozie Uche\nDrew Coffman\nDylan Field\nDylan Rhodes\nEd Felten\nEd Lynch\nEddie Lim\nEddy Lazzarin\nEdith Zimmerman\nEdward Perkins\nEdwin Poston\nEfrat Noy\nEhud Shapiro\nEileen Burbidge\nEileen Wu\nElad Gil\nElaine Fuchs\nElaine Shi\nElena Burger\nEli Dourado\nElisa Leonhardt\nEliza Oak\nElizabeth Gunn\nElizabeth Harkavy\nElizabeth May\nElizabeth Ocken\nElizabeth Stark\nElizabeth Weil\nEllen Tunoa\nEmile Petrone\nEmilio Torres\nEmily Graff\nEmily Hinsch\nEmily Keir\nEmily Oster\nEmily Westerhold\nEmma Janaskie\nEric Budish\nEric Dai\nEric Ries\nEric Thomas\nEric Topol\nEric Wu\nErica Schecter\nErik Brynjolfsson\nErik Kiser\nErik Torenberg\nErika Bracken\nErika Herrera\nErika Louie\nErin Grody Kingsley\nErin Murphy\nErin Tice\nErin Tonnar\nErin Winkler\nErtem Nusret Tas\nEsther Shinn\nEthan Bueno de Mesquita\nEthan Ferreira\nEthan Zuckerman\nEuan Ashley\nEugene Volokh\nEugene Wei\nEugenia Yee\nEula Takahashi\nEva Sakkas\nEvan Burfield\nEvan Osnos\nEvangelos Simoudis\nEzra Klein\nF. Gary Gray\nFabiola Godinez\nFabrizio Zilibotti\nFahad Saleh\nFarid Jiandani\nFei-Fei Li\nFelix Do\nFEWOCIOUS\nFiona Kennedy\nFiona Murray\nFlashrekt\nFlora Oliveira\nFlori Del Valle\nFlorian Leibert\nFoteini Baldimtsi\nFrancesca Gino\nFrank Chen\nFrank Wilczek\nFred Benenson\nFred Ehrsam\nFred Upton\nFred Wilson\nFreda Lewis-Hall\nFrederic Kerrest\nFuture Editorial\nGabby Dizon\nGabby Reece\nGabriel Otte\nGabriel Vasquez\nGaetan Barthelemy\nGarrett Biel\nGary Ang\nGary Reedy\nGary Wolf\nGaurav Banga\nGaurav Dhillon\nGaut\nGayle Tzemach Lemmon\nGeoffrey Woo\nGeorg Fuchsbauer\nGeorg Petschnigg\nGeorge Church\nGeorge Danezis\nGeorge Fraser\nGeraldine Chan\nGérard Cachon\nGerard Ryle\nGerri Elliott\nGerry Tsoukalas\nGia Scinto\nGil Elbaz\nGil Shafir\nGina Moon\nGina Neff\nGina Yocom\nGinger Liau\nGokul Rajaram\nGoldie Chang\nGrace Ellis\nGraham Allison\nGrant Gregory\nGrant Jordan\nGrant LaFontaine\nGrant Rabenn\nGray Kinsella\nGreg Bowman\nGreg Clayman\nGreg Linares\nGreg Loehmann\nGreg Lynn\nGreg Solano\nGreg Truesdell\nGreg Waldon\nGregory Allen\nGregory Mundis\nGretchen Bush\nGretchen McCulloch\nGuido Appenzeller\nGustav Söderström\nGustavo Garcia\nGuy Goren\nGuy Raz\nGuy Wuollet\nHaley Van Dyck\nHanna Aziz\nHannah Frankl\nHanne Winarsky\nHaoyuan Li\nHarmit Malik\nHarry Grieve\nHarry Shum\nHarry Wright\nHatim Shafique\nHayden Adams\nHeather Gwynn\nHeather Podesta\nHedi Samar\nHelen Stoddard\nHelen Su\nHemant Mohapatra\nHendrik Pretorius\nHenri Kor\nHerb Lin\nHerman Narula\nHilmar Pétursson\nHoang Nguyen\nHoward Wu\nIan Dutra\nIan Shannon\nIan Sharp\nIce Cube\nIlan Zechory\nIllia Polosukhin\nIlyas Khan\nIma Christian\nIman Abuzeid\nInsiya Lokhandwala\nIon Stoica\nIrvin Chan\nIsa Guardalabene\nIsaiah Lott\nIsh Verduzco\nIsil Dillig\nIstván András Seres\nIttai Abraham\nIttay Eyal\nIva Messy\nIvan Linscott\nIvor Horn\nJ.D. Moriarty\nJack Donahoe\nJack Soslow\nJackie McQuiston\nJackson David\nJacob Westphal\nJacquelyn Melinek\nJad Esber\nJad Naous\nJade Lai\nJade Raymond\nJae Gnazzo\nJai Ramaswamy\nJaimie Buss\nJak Kennedy\nJake Auchincloss\nJakob Uszkoreit\nJamal Mohammed\nJames Beshara\nJames Currier\nJames da Costa\nJames Gwertzman\nJames J. Collins\nJames Kissell\nJames L. Madara\nJames Loftus\nJames Rathmell\nJames Rogers\nJames Watters\nJames Wu\nJames Zou\nJamie Brandon\nJamie McGurk\nJamie Sullivan\nJamilla Hemeid\nJana Odehnal\nJane Doe\nJane Lippencott\nJane Suh\nJanelle De Los Santos\nJared Bricklin\nJared Furutani\nJared Georgakopoulos\nJared Polis\nJared Smith\nJase Wilson\nJason Franklin\nJason Liu\nJason Mayden\nJason Milionis\nJason Mitchell\nJason Mok\nJason Rosenthal\nJason Warner\nJason Yanowitz\nJay Bradner\nJay Conte\nJay Drain\nJay Komarneni\nJay Rughani\nJean Reilly\nJeanne Tsan\nJeff Amico\nJeff Benson\nJeff Clark\nJeff Cordova\nJeff Glueck\nJeff Hawkins\nJeff Jones\nJeff Jordan\nJeff Lawson\nJeff Lu\nJeff Nagashima\nJeff Stump\nJeff Weiner\nJeffrey Immelt\nJeffrey Kaditz\nJeffrey Katzenberg\nJeffrey Kindler\nJeffrey Low\nJeffrey Silverstein\nJeffrey Zirlin\nJen Bulawsky\nJen Kha\nJenna Walsh\nJenna Zucker\nJennifer 8. Lee\nJennifer Doudna\nJennifer Kodner\nJennifer Konde\nJennifer Li\nJennifer Mumford\nJennifer Tejada\nJennifer Young\nJenny Cieplak\nJens Ernstberger\nJensen Harris\nJeremy Clark\nJeremy England\nJeremy Zhang\nJesse Holmes\nJesse Pollak\nJesse Walden\nJessica Childs\nJessica Hansen\nJessica Keeler\nJessica Patton\nJessica Verrilli\nJewel Pi\nJez Humble\nJi Kim\nJianying Luo\nJim Gilliam\nJimmy Chen\nJimmy Soni\nJing Wang\nJing Zou\nJJ Yu\nJoachim Neu\nJodi Lynn\nJodie Lutkenhaus\nJoe Gebbia\nJoe Grundfest\nJoe Montana\nJoe Morrissey\nJoe Schmidt\nJoe Sullivan\nJoel de la Garza\nJoel Mokyr\nJoel Monegro\nJoel Spolsky\nJoey Burleson\nJohn China\nJohn Collison\nJohn Fawcett\nJohn Garcia\nJohn Gedmark\nJohn Hennessy\nJohn Koelliker\nJohn M. Jack\nJohn Markoff\nJohn Menna\nJohn O’Farrell\nJohn Riccitiello\nJohn Smesko\nJohn Stanfield\nJohn Thompson\nJohn William Hatfield\nJonah Peretti\nJonathan Bush\nJonathan Dotan\nJonathan Downey\nJonathan Lai\nJonathan Lim\nJonathan Lusthaus\nJonathan Weissman\nJonathan Wong\nJordan Mazer\nJordan Stankowski\nJorge Conde\nJorge Gomez\nJose Guardado\nJoseph Bonneau\nJoseph Okpaku\nJoseph Spisak\nJosh Arnold\nJosh Bloom\nJosh Kim\nJosh Williams\nJoshua Browder\nJoshua Gans\nJoshua Grimm\nJoshua Hix\nJoshua Levin\nJoshua Lu\nJoshua Schank\nJoshua Soto\nJosie Ma\nJoyce Park\nJR Rivers\nJT Evans\nJuan Benet\nJudene Small\nJudy Savitskaya\nJudy Smith\nJulia Grace\nJulia Kirby\nJulie Bornstein\nJulie Farnham\nJulie Johnson\nJulie Samuels\nJulie Yoo\nJuliet Grier\nJuliet Nyatta\nJuliette Morton\nJulius Zhang\nJustin Bailey\nJustin Bethune\nJustin Blau\nJustin Cunningham\nJustin Gregorius\nJustin Kahl\nJustin Kan\nJustin Larkin\nJustin Paine\nJustin Pettit\nJustin Roberts\nJustin Simcock\nJustin Thaler\nJustine Moore\nJutta Steiner\nJyoti Bansal\nJZ Young\nKabir Gill\nKabir Laroia\nKais Khimji\nKamala Harris\nKaren Dunn\nKaren Wooley\nKarina Sobieski\nKarl Floersch\nkarma (Daniel Reynaud)\nKarmacoma\nKarthik Rau\nKartik Nayak\nKate Darling\nKate Dellolio\nKate Kerames\nKatherine Boyle\nKatherine Minarik\nKatherine Rundell\nKatherine Schoebel\nKathryn McKinley\nKathy Liu\nKathy Yang\nKatia Ameri\nKatie Baynes\nKatie Haun\nKatie Hemmerling\nKaty DeWitt-Drew\nKaty Nelson\nKayvon Tehranian\nKeener Barnhorst\nKeller Medlin\nKeller Rinaudo\nKelly Cannon\nKelsey Chaplinsky\nKelsey Mellard\nKen Chong\nKen Coleman\nKen Kocienda\nKerry Ganim\nKesha Cash\nKevin Chou\nKevin Chu\nKevin Dulsky\nKevin Kelly\nKevin McKinley\nKevin Nishioka\nKevin O'Kane\nKevin Rose\nKevin Tan\nKevin Wu\nKevin Zollman\nKidSuper\nKieran Snyder\nKierston Gittens\nKiki Mavridis\nKim Enright\nKim Malone Scott\nKim Milosevich\nKim Stevenson\nKim Zetter\nKimberly Tan\nKindra Mason\nKira Poskanzer\nKira Song\nKirstin Arbide\nKirt McMaster\nKofi Ampadu\nKouki Harasaki\nKrista Anderson-Copperman\nKristen Fortney\nKristen Johansson\nKristen Kee\nKristin Sauchak\nKristin Thayer\nKristina Graci-deLuna\nKristina Shen\nKristine Lipscomb\nKristo Käärmann\nKrisztina Holly\nKunal Bahl\nKunle Olukotun\nKurt House\nKyle Russell\nLaird Hamilton\nLatasha\nLaura Arrillaga-Andreessen\nLaura Baller\nLaura Behrens Wu\nLaura Deming\nLaura Gravley\nLaura Johnson\nLaura Shores\nLaura Weidman Powers\nLauren Berson\nLauren Illovsky\nLauren Murrow\nLauren Richardson\nLauren Spragge\nLaurene Powell Jobs\nLawrence Levy\nLawrence Summers\nLeah Cassidy\nLee Kleinman\nLee Lefkowitz\nLeeAnn Caballero\nLeila Hay\nLeila Janah\nLenny Rachitsky\nLeslie Jaw\nLeslie Vosshall\nLester Chen\nLi Fan\nLi Fei-Fei\nLi Jin\nLiang Wu\nLilian King\nLily Liu\nLina Sergie Attar\nLinda Banuelos\nLinda Xie\nLinden Tibbets\nLing Ren\nLinlin Li\nLinxin Wen\nLioba Heimbach\nLisa Hawke\nLisa Lambert\nLisa Orr\nLisa Reilly\nLisa Rosano\nLizzy Anderson\nLJ Erwin\nLloyd Dean\nLoretta Sanchez\nLori Potter\nLuca Prosperi\nLuca Zanolini\nLuis Martinez\nLuis von Ahn\nLuke Wroblewski\nLydia Green\nLynda Gibson\nLynn Rudolph\nMadan Nagaldinne\nMaddison Masaeli\nMadeline Lancaster\nMaggie Hsu\nMaggie Leung\nMaggie Romero\nMahad Abedin\nMahesh Iyer\nMahesh Vellanki\nMahimna Kelkar\nMakiri Duckett\nMalinka Walaliyadde\nMallesh M. Pai\nMalloy Evans\nManas Punhani\nManny Luna\nMarc Andreessen\nMarc Andrusko\nMarc Benioff\nMarc Levinson\nMarci Barbera\nMarco Reuter\nMargaret Jen\nMargit Wennmachers\nMaria LaMagna Morales\nMarian Garvin\nMarianne Winkler\nMariano Sorgente\nMaricarmen Alvarez\nMariel Goldenstein\nMarigold Vu\nMarina Kusserow\nMario Gabriele\nMario Linares\nMarissa Bramlett\nMark Cranney\nMark Leslie\nMark McAndrew\nMark McClusky\nMárk Melczer\nMark Moore\nMark Regan\nMark Sendak\nMarkos Georghiades\nMarkus Covert\nMarkus Funk\nMartha Lane Fox\nMartin Casado\nMartin Fischer\nMarty Makary\nMarvin Ammori\nMarvin Zamora\nMary Pat Jordan\nMary-Catherine Lader\nMaryam Bahrani\nMason Hall\nMatei Zaharia\nMatt Abrahams\nMatt Billmann\nMatt Bornstein\nMatt Clifford\nMatt Flannery\nMatt Fleming\nMatt Gleason\nMatt Kaeberlein\nMatt Levine\nMatt Levy\nMatt Oberhardt\nMatt Shortal\nMatt Spence\nMatt Weinberg\nMatthew Colford\nMatthew Green\nMatthew Haughey\nMatthew McCullough\nMatthew Mills\nMatthew Olsen\nMatthew Rutter\nMatthew Stein\nMatthieu Hafemeister\nMaureen Lara\nMax Kesten\nMax Krohn\nMax Levchin\nMax Polyak\nMax Resnick\nMax Ventilla\nMaya Rahkonen\nMcPherson Moore\nMeaghan Hardy\nMeg Whitman\nMegan Holston-Alexander\nMegan Kristalyn\nMehdi Hasan\nMehul Mehta\nMel Williams\nMelanie Galang\nMelissa Liao\nMelissa Minor\nMelissa Wasser\nMellody Hobson\nMelody Latronico\nMeredith Donahue\nMia Gonzalez\nMia Mandich\nMicah Johnson\nMichael Beckerman\nMichael Blau\nMichael Brandt\nMichael Chan\nMichael Copeland\nMichael Dearing\nMichael Dell\nMichael Franklin\nMichael Garcia\nMichael J. Casey\nMichael J. Freedman\nMichael Killam\nMichael King\nMichael Lee\nMichael Leiter\nMichael Morell\nMichael Ostrovsky\nMichael Ovitz\nMichael Paulus\nMichael Raynor\nMichael Reed\nMichael Snyder\nMichael Temkin\nMichael Wee\nMichael Zhu\nMichel Del Buono\nMichel Feaster\nMichèle Flournoy\nMichele Griffin\nMichele Korver\nMichele Law\nMichelle Ervin\nMichelle Kelso\nMichelle Kung\nMichelle Mundy\nMichelle Shin\nMichelle Ufford\nMichelle Volz\nMichelle Wilson\nMichelle Winn\nMichelle You\nMike Curtis\nMike Haydon\nMike Hearn\nMike Jones\nMike Kasperzak\nMike Kelly\nMike King\nMike Lempres\nMike Manning\nMike Maples jr\nMike Masnick\nMike Matchett\nMike Paulus\nMike Sandwick\nMikeal Rogers\nMikey Dickerson\nMiles Jennings\nMilijana Curic\nMiller Whitehouse-Levine\nMinerva Munoz\nMinnie Ingersoll\nMinsun Pak\nMintu Turakhia\nMiranda Christ\nMo Shaikh\nMohammad Akbarpour\nMohsen Malayeri\nMolly Grace\nMonique McCambridge\nMorgan Beller\nMorgan Bender\nMurat Pak\nMuriel Bowser\nMurray Shanahan\nMy Pham\nNadia Asparouhova\nNadia Eghbal\nNaftali Harris\nNaithan Jones\nNanjira Sambuli\nNaomi Metzger\nNashid Braswell\nNassim Eddequiouaq\nNat Barling\nNatacha Crooks\nNatalia Carrera\nNatalie Bucher\nNatalie Taumoepeau\nNate Chang\nNate Lau\nNathalie Balaban\nNathan McCauley\nNathan Yoon\nNathaniel Gleicher\nNathaniel Popper\nNav Singh\nNazanin Daneshvar\nNeel Maitra\nNeha Narula\nNelson Perla-Ward\nNeveen Bader\nNicholas Christakis\nNicholas Pacilio\nNick Babaian\nNick McKeown\nNick Quah\nNick Tomaino\nNicki Locker\nNicole Conner\nNicole Forsgren\nNicole Irvin\nNicole Neuman\nNicole Stanners\nNiels Provos\nNigel Robinson\nNikhil Krishnan\nNina Suthers\nNir Eyal\nNitasha Tiku\nNitin Natarajan\nNitya Subramanian\nNkiru Balonwu\nNoah Citron\nNoah Feldman\nNoah Levine\nNoah Smith\nNoam Nisan\nNoemi Glaeser\nO’Shea Jackson Jr.\nOlaf Carlson-Wee\nOleg Rogynskyy\nOliver Hsu\nOlivia Moore\nOlivia Webb\nOmri Weinstein\nOoshma Garg\nOprah Winfrey\nOrion Hindawi\nOscar Menjivar\nP.J. Hasleton\nPablo Montagnes\nPacky McCormick\nPak\nPalmer Luckey\nPamela Anderson\nPamon Forouhar\nParag Khanna\nParijat Talkad\nParker Brown\nParker Conrad\nPatrice Peck\nPatrick Byrne\nPatrick Collison\nPatrick Conway\nPatrick McCorry\nPatrick McHenry\nPatrick O’Grady\nPatrick Rivera\nPatrick Sutton\nPaul Cafiero\nPaul Daugherty\nPaul Davison\nPaul Krugman\nPaul Vigna\nPaula Long\nPenny Pritzker\nPerri Chilton\nPete Buttigieg\nPeter Blackwood\nPeter Buisseret\nPeter Chan\nPeter Donnelly\nPeter Johnson\nPeter Lauten\nPeter Leeson\nPeter Levine\nPeter Ludwig\nPeter Rubin\nPeter Thiel\nPeter Wang\nPetra Garrett\nPhil Daian\nPhil Hathaway\nPhil Wong\nPhong Nguyen\nPorter Smith\npplpleasr\nPranav Garimidi\nPrasad Akella\nPrat Moghe\nPreethi Kasireddy\npunk6529\nPurnima Padmanabhan\nPyrs Carvolth\nQasar Younis\nQuang Dao\nQuinten Burgunder\nQuintus Kilbourn\nRachael Horwitz\nRachel Goslins\nRachel Jenkins\nRachel Kalmar\nRachel McIntyre\nRachel Steiner\nRahul Iyer\nRahul Vohra\nRajeev Singh\nRajeev Venkayya\nRam Palaniappan\nRamana Jonnala\nRati Gelashvili\nRaul Vazquez\nRavi Parimi\nRay Dalio\nRaymond Carreira\nRebecca Lewis\nRebecca Rettig\nReed Hastings\nRefik Anadol\nRegina Benjamin\nRenato Valdés Olmos\nReshma Saujani\nReshma Sohoni\nRex Salisbury\nRich Ezekiel\nRichard Green\nRichard Menger\nRichard Rosenblatt\nRick Young\nRidhima Ahuja\nRiyaz Faizullabhoy\nRob Goodman\nRob McElhenney\nRob Pardo\nRob Rhinehart\nRobbie Petersen\nRobbie Peterson\nRobert Alexander\nRobert Cottrell\nRobert Hackett\nRobert Kolker\nRobert Leshner\nRobert McNeely\nRobert Moreno\nRobert Siegel\nRobert Stromberg\nRobert Weber\nRobin Casey\nRobin Guo\nRobin Weisman\nRod Johnson\nRodrigo Ibarra Lopez\nRodrigo Pacheco\nRoger Dickey\nRoger Wattenhofer\nRoham Gharegozlou\nRohini Mukand\nRohit Bansal\nRoman Mars\nRoman Stanek\nRon Gill\nRon Lavi\nRon Rothblum\nRonald Evans\nRonnie Harris\nRosa Davila\nRosalind Rattan\nRose Legarda\nRoss Andersen\nRoss Shuel\nRostin Behnam\nRuben Gallego\nRuben Smith\nRuss Altman\nRuss Heddleston\nRuss Roberts\nRussell Davies\nRyan Allen\nRyan Caldbeck\nRyan Conde\nRyan Holloway\nRyan Hoover\nRyan McEntush\nRyan Petersen\nRyan Prescott\nRyan Sandler\nRyan Spoon\nRyan Tseng\nRyan Walsh\nRyan Ward\nRyan Wyatt\nSaar Tochner\nSachin Jain\nSafi Bahcall\nSagar Dhawan\nSaku Panditharatne\nSalem Vance\nSam Blackshear\nSam Broner\nSam Gerstenzang\nSam Ragsdale\nSam Thompson\nSam Williams\nSam Yam\nSamantha Gelt\nSamantha Langford\nSamantha Ludwig\nSamson Wu\nSamuel Arbesman\nSamuel Hammond\nSandra Samayoa\nSandy Jen\nSankaet Pathak\nSantiago Rodriguez\nSara Boesen\nSarah Fazal\nSarah Hamburg\nSarah Lumbard\nSarah Mascardo\nSarah Meiklejohn\nSarah Porter\nSarah Rebello\nSarah Wang\nSasha Stiles\nSatish Talluri\nSaurabh Ladha\nSavannah Cherry\nScott Clark\nScott Duke Kominers\nScott Gottlieb\nScott Hassan\nScott Kupor\nScott Rubin\nScott Shenker\nScott Tyler\nScott Walker\nScott Weiss\nSean Duffy\nSean Neville\nSebastian Oddo\nSeema Amble\nSeemay Chou\nSep Kamvar\nSergiu Pasca\nSeth Lobree\nSeth Sivak\nSeth Sternberg\nShai Bernstein\nShai Kopeld\nShaka Senghor\nShakil Khan\nShan Sinha\nShana Fisher\nShane Mac\nShane Parrish\nShangda Xu\nShannon (Stubo) Brayton\nShannon Barbour\nShannon Kelly\nShannon Schiltz\nShannon Snow\nShari Doherty\nSharon Chang\nShawn Conway\nSheela Krothapalli\nShellye Archambeau\nSherie James\nSherriAnn Cole\nShishir Mehrotra\nShonda Rhimes\nSid Gorham\nSigne Pierce\nSimon Denny\nSiqi Chen\nSonal Chokshi\nSophie Song\nSoubhik Deb\nSpencer Dinwiddie\nSpencer Howard\nSpencer Rascoff\nSreeram Kannan\nSreevidya Kasturil\nSri Kosuri\nSriram Krishnan\nSrivatsan Sridhar\nStacey Cunningham\nStacey Merrick\nStacia Murray\nStacy Brown-Philpot\nStacy D'Amico\nStacy Warner\nStefan McDonough\nSten Tamkivi\nStephane Bancel\nStephanie Anyanwu\nStephanie Cohen\nStephanie Doppelt\nStephanie Smith\nStephanie Watkins\nStephanie Zinn\nStephen Armanios\nStephen Wink\nStephenie Zhang\nSteve Buress\nSteve Cadigan\nSteve Cheney\nSteve Harvey\nSteve Kaczynski\nSteve McDermid\nSteve Smith\nSteve Zhao\nSteven Adair\nSteven Ebert\nSteven Johnson\nSteven Levy\nSteven Sinofsky\nStewart Butterfield\nStina Ehrensvärd\nStuart Luman\nStuart Russell\nSudip Chakrabarti\nSue Hager\nSuhail Doshi\nSukhinder Singh Cassidy\nSumeet Singh\nSumit Shah\nSungMo Park\nSunil Chokshi\nSurya Ganguli\nSusan B. Wilde\nSusan Mernit\nSusan Rice\nSusannah Fox\nSydney Paul\nTaavet Hinrikus\nTaggart Matthiesen\nTamzen Brewis\nTana Billingsley\nTarek Mansour\nTarun Chitra\nTauri Laws Phillips\nTawny Holguin\nTaylor McFadden\nTed Not Lasso\nTed Sarandos\nTed Ullyot\nTerell Sterling\nTerence Carroll\nTeresa Carlson\nTerry Angelos\nTerry Brown\nThan Nguyen\nThanh Nguyen\nThe 2015 Academic Roundtable Sessions\nThe TxO team\nTheresa DeMichele\nTheresa Dilley\nTheresa Fisher\nTheresa Walz\nTheresia Gouw\nThibaut Scholasch\nThomas Gjerde\nThomas Juenger\nThomas Long\nThomas Rando\nTiffany Vo\nTiffany Zhong\nTim Beiko\nTim O'Reilly\nTim Roughgarden\nTim Schafer\nTim Sullivan\nTimmu Tõke\nTina Anderson\nTina Bhatnagar\nTina Ferguson\nTina Wie\ntinawie\nTing Ni\nTobi Lütke\nTodd Cranney\nTodd Lutwak\nTodd McKinnon\nTodd Park\nTodd Young\nTolga Dizdarer\nTom Butta\nTom Coates\nTom Davenport\nTom Ellis\nTom Hammer\nTom Hofmann\nTom Lehman\nTom Mitchell\nTom Preston-Werner\nTom Rikert\nTom Standage\nTomicah Tillemann\nTony Blair\nTony Blinken\nTori Landrum\nTracy Chou\nTracy Young\nTren Griffin\nTrent Mayol\nTrevor Bedford\nTristan Handy\nTristan Walker\nTroy Kirwin\nTugce Erten\nTurner Novak\nTushar Garg\nTyler Cowen\nTyler Wilson\nTyson Clark\nUma Valeti\nUsman Azam\nUzi Dutta\nValentina Marzorati\nValeria Nikolaenko\nValerie Arboleda\nVan Jones\nVan Le-Gray\nVanessa Kropf\nVas Narasimhan\nVaughn Ferguson\nVenkat Mocherla\nVicente De Baca\nVickie Casillas-Smith\nVictor Liang\nVictor Shoup\nVictoria Butcher\nVijay Balasubramaniyan\nVijay Kedar\nVijay Pande\nVineeta Agarwala\nVinod Khosla\nVirginia Postrel\nVishal Amin\nVitalik Buterin\nVivian Brooks\nVoices Onchain\nW. Brian Arthur\nWahab Owolabi\nWei Luo\nWendy Drpic\nWerner Gerola\nWes Taylor\nWhitney Owens\nWill Brown\nWill Wong\nWillem Mulder\nWilliam Gifford\nWilliam Mougayar\nWing Cheng\nXian Zhang\nXiang-Dong Fu\nXingchen Zhou\nYannai A. Gonczarowski\nYehuda Lindell\nYevgeniy Dodis\nYinuo Zhang\nYogi Roth\nYohei Ishii\nYoko Li\nYoni Levy\nYoram Novick\nYuichi Kurosawa\nYujin Chung\nYun Fan\nYung Yung Sheung\nYuval Efron\nYuval Harari\nZac Bookman\nZach Abrams\nZach Cohen\nZach Dicker\nZach Haigney\nZachary Chen\nZachary Gray\nZack Weiner\nZahabiya Gabaji\nZak Doric\nZal Bilimoria\nZane Lackey\nZeta Avarikioti\nZeya Yang\nZooko Wilcox\nZoran Basich\n\nclear all Jeff Amico\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n10.17.22 / Chris Dixon and Jeff Amico\nCrypto Startup School: relaunched and expanded\nWe’re thrilled to announce that we are relaunching Crypto Startup School and expanding it into a full accelerator program. We launched Crypto Startup School in February 2020 with the goal of helping builders get started on new web3 projects. Over seven weeks, we coached teams on the fundamentals of building a web3 startup from the...\n\nannouncements & news\nannouncements\nCrypto Startup Accelerator (CSX)\nCSX 2023\n\n08.24.22 / Jeff Amico, Maggie Hsu, Ed Lynch and Emily Westerhold\nTreasury Management: A Guide to Navigating Downturns\nWe share a framework for how conservative treasury management principles can help DAOs and startups to safely navigate periods of market uncertainty.\n\ncompany building\ncustody\nDAOs\ngovernance best practices\nplaybooks\nproduct-market fit\n\n08.25.21 / Jeff Amico\nOpen Sourcing Our Token Delegate Program\nOver the last year we’ve worked with dozens of delegates across a number of leading protocols. Here are some of the best practices that we’ve identified.\n\nannouncements & news\nannouncements\ngovernance\n\n02.04.21 / Jeff Amico\nOn Crypto Governance\nFor crypto startups, transitions towards community governance are complicated but ultimately necessary in order for the protocols to provide enduring value.\n\nannouncements & news\nannouncements\ngovernance\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":7107,"crawled_at":1791195598343}
+{"id":10542,"url":"https://docs.ethena.fi/protocol-overview/risks","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Risks | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nRisks of USDe as Synthetic Dollar\nEthena is committed to transparency. It is crucial to highlight the risks associated with USDe, the actions taken to mitigate these risks, as well as plans to further manage and ameliorate these risks.\nThis section will discuss the following risks:\n\nFunding Risk\n\nLiquidation Risk\n\nCustodial Risk\n\nExchange Failure Risk\n\nBacking Assets Risk\n\nStablecoin-Related Risk\n\nMargin Collateral Risk\n\nWe would greatly appreciate any feedback or information you would like to see to help the protocol be as transparent as possible. If you believe any risk has not been adequately surfaced please reach out in Discord and notify the contributors.\n\nLast updated 6 months ago\nWas this helpful?","tokens":202,"crawled_at":1791195599381}
+{"id":10543,"url":"https://blog.trailofbits.com/2026/09/21/saml-a-fractal-of-bad-design","domain":"blog.trailofbits.com","chapter":"security_audits","title":"SAML: A fractal of bad design - The Trail of Bits Blog","text":"Page content\n\nBorn out of academia and raised in corporate IT departments, the Security Assertion Markup Language (SAML) authentication protocol continues to be a staple in these organizations. However, it’s time for it to retire. With the rise of software-as-a-service (SaaS) companies in the late aughts, IT departments needed a way for users to authenticate to many new web services. SAML and the burgeoning single sign-on (SSO) industry fulfilled this need. However, SAML is being crushed under the weight of its own complexity. It’s time to deprecate it and move on to modern alternatives like OpenID Connect (OIDC). In this post, I will explore the design-by-committee origin of SAML, its progression through the ranks in academic and corporate environments, its slow disintegration at the hands of the security research community, and its (hopeful) deprecation in favor of newer protocols.\n\nSAML 101\nWhat’s insidious about SAML is that it really is mostly straightforward to understand, but it’s built on a foundation of sand, bone dust, and ash; it works … if you assume XML signature validation is reliable. But XML signature validation is deeply cursed, and is so complicated that most fielded SAML implementations are wrapping libxmlsec, a gnarly C codebase nobody reads.\n— Thomas Ptacek, 2023\n\nSAML and the birth of the SSO industry\nWikipedia tells me that “SAML is an XML-based markup language for security assertions.” It was created in 2002 by the Organization for the Advancement of Structured Information Standards (OASIS) Security Services Technical Committee (SSTC). Okay, we’re not off to a great start by modern standards. XML, despite having some redeeming qualities, is quite complex compared to newer alternatives like JSON, but we’ll get more into that later. Further, a committee of subcommittees having meetings is a recipe for “kitchen-sink” protocol design (e.g., waterfall methodology, big design up front, etc.). And sure enough, we’ve now jammed four (!) XML-based security protocols into one:\n… the following intellectual property was contributed to the SSTC:\nSecurity Services Markup Language (S2ML) from Netegrity\nAuthXML from Securant\nXML Trust Assertion Service Specification (X-TASS) from VeriSign\nInformation Technology Markup Language (ITML) from Jamcracker\n— SAML: History\n\nHowever, the desire for such a protocol was undeniable. As the internet shifted from Web 1.0 in the 90s to Web 2.0 in the early aughts, users and organizations needed an easy way to authenticate to many new web services. Academia was the biggest driver of this movement, although not the only one: Central Authentication Service (CAS) in 2002 at Yale, Shibboleth IdP in 2003 by Internet2, a consortium of research universities (including my alma mater), ADFS in 2003 by Microsoft, and simpleSAMLphp around 2007 by Uninett, a state-owned Norwegian company with close ties to academia. All these authentication projects eventually supported SAML in one way or another. Like ARPANET before it, universities were at the forefront of internet development and were the earliest consumers of web services. Once this base layer of protocol availability and nascent academic proving ground was established, the commercial industry took it and ran toward a multibillion dollar industry.\nThe SSO, identity, and authentication provider industry was also starting up in the early aughts, but really came to fruition a few years later: Ping Identity (2002), OneLogin (2009), Okta (2009), and Duo Security (2010). These companies were essentially built on the SAML protocol with the exception of Duo, who would introduce their first SSO product in 2015, which is where I come into the story. I worked on Duo’s first on-premises Access Gateway product (DAG), which was built on simpleSAMLphp and, obviously, the SAML protocol. It’s where I became intimately familiar with the SAML protocol and spent many years of my life digesting its lengthy specifications. I was there when Kelby Ludwig found the XML comment bypass, but we will get into various attacks and SAML deficiencies later. Suffice it to say, the SSO and authentication provider industry was booming, and much of it was built on the SAML protocol.\nA crack in the armor\nXML signature wrapping (XSW) attacks are the proverbial arrow to SAML’s heel. While there was earlier security research into both signature wrapping (2005, 2008, and 2009) and SAML (2008), I consider the godfather of it all to be “On Breaking SAML: Be Whoever You Want to Be” (2012). It tested theory against practice and resulted in an automated way to check for XSW attacks. This was our north star when implementing the DAG. It was the reason we chose simpleSAMLphp as our building block. PHP, especially at the time, was not exactly known for its security track record, but simpleSAMLphp’s spoke for itself. simpleSAMLphp was resilient to XSW at a time when nobody really knew what that was:\n\nsimpleSAMLphp’s security track record (credit: On Breaking SAML)\nDespite being front and center in this 2012 paper, XSW is still present today. If we know the bug class, then why can’t we fix it? But before we get into SAML’s flaws we first have to consider the shaky ground it was built upon: XML.\nXML is no slouch when it comes to a (lack of) security track record. These bug classes would have been more familiar to a developer in the 90s, but nonetheless are still present in XML today: XXE, entity expansion (“billion laughs”), DTD retrieval (SSRF), XPath/XQuery/XInclude/XSLT/CDATA injection, and more. A SAML library needs to handle all these bug classes before even getting to the actual SAML functionality.\nIn addition to security bug classes, there’s also the sheer complexity of XML when compared against something like JSON. In XML you have tags, elements, attributes, comments, namespaces, markup versus content, schemas, CDATA, DOCTYPEs, and more. In JSON, you essentially have keys, values, objects, and lists. Complexity is generally at odds with security, and this is one reason I consider SAML to be a fractal of bad design.\nA fractal of bad design\nSAML provides ample opportunity to learn about protocol design. In this section, I will cover five flaws that I consider to be fatal to the long-term viability of SAML as an authentication protocol. These flaws can also be used when designing new authentication protocols. That is, you can either sidestep the flaw, or take its inverse and attempt to bake that into the protocol.\nBuilt on XML\nAs mentioned above, SAML is built on XML, and XML is complex, but it’s not the committee’s fault. XML is what they had at the time, and it’s what people used. JSON was “discovered” in 2001, but this was right around the time the SAML committee was meeting, and they’d be unlikely to design an authentication protocol around an experimental new format. Especially when it caters to JavaScript and you write a lot of Java.\nOne could design a quantitative complexity measurement for XML versus JSON or SAML versus JWT/OIDC (e.g., spec/RFC word count, spec/RFC normative word count, etc.), but that would require a blog post or paper all to itself. In the interest of staying on topic, I will refrain from doing that here, and suffice to say that XML is significantly more complex than something like JSON.\nCanonicalization\nCanonicalization (C14N) is what you do when you want to take the wild mess that is XML, compute a hash of it, and get consistent results. In other words, if the SP and IdP cannot agree on a consistent representation of the XML data, then the bytes won’t line up, the signatures won’t match, and your authentication fails. However, this is easier said than done.\nCanonicalization bugs enabled Kelby’s XML comment bypass in 2018:\n\nXML canonicalization (credit: Identity Theft)\nCanonicalization is often a precursor to parser differential and/or “round-trip” bugs, which are what most modern SAML attacks use:\nCoordinated disclosure of XML round-trip vulnerabilities in Go’s standard library (2020)\nSecuring XML implementations across the web (2021)\nAbusing libxml2 quirks to bypass SAML authentication on GitHub Enterprise (2025)\nSign in as anyone: Bypassing SAML SSO authentication with parser differentials (2025)\nSAML roulette: the hacker always wins (2025)\nThe Fragile Lock: Novel Bypasses For SAML Authentication (2025)\nEnveloped signatures\nEnveloped signature concerns are a not-too-distant cousin of canonicalization. In short, if you’re trying to insert the signature into the data payload that you’re signing, you’re going to have a bad time. Let’s compare and contrast JWT and SAML in this way:\n\nJWT versus SAML signatures (credit: jwt.io and samltool.io)\nIn the JWT example above, the blue signature is detached from the JSON payload and delimited in the JWT with a period (“.”). In the SAML example, the Signature element is inserted (“enveloped”) in the Assertion element. The problem here is that it is very difficult to get a byte-for-byte, canonically equivalent representation of the data when you’re also modifying it! Even more so when you have a complex format like XML and complex canonicalization rules.\n“Kitchen-sink” design\nThis design deficiency essentially transposes to you aren’t gonna need it (YAGNI). It’s not an entirely fair characterization because the portions of the SAML specification that are used in the real-world have changed over the past 20 years (sorry, SOAP and artifact binding). However, the fact of the matter is that 99% of modern SAML implementations use a very similar data shape and subset of the specification. Any given SAML authentication you would encounter in the wild today probably avoids 90% of the specification. This adds significant complexity for largely unused features.\nIf I was adding SAML support to something new, I’d consider beyond all the standard SAML checks also rejecting any message that doesn’t have the same shape as what Okta, Onelogin, Google, or Shib generates.\n— Thomas Ptacek, 2021\n\nOssification\nSAML was designed in a different era for a different time and has not received necessary updates. These concerns will generally be of practical implication rather than theoretical. What I mean by ossification can roughly be enumerated as the following:\nOIDC assumes HTTP, whereas SAML is transport independent. Sure, SAML HTTP bindings exist and are most commonly used, but they are not required. This affords SAML a certain degree of flexibility, but also means that flexibility must be well defined, must be implemented somewhere, and can contain bugs. SAML came about at a time when HTTP + TLS was not yet the dominant backbone of web service communication, and it has never reconciled with this modern landscape. HTTPS allows OIDC to punt encrypted, trusted communication to the transport layer.\nOIDC generally assumes a connected network topology, whereas SAML does not. The most common OIDC flow (authorization code) assumes the OpenID Provider (OP) and Relying Party (RP) can communicate directly (OIDC OP/RP == SAML IdP/SP). Sure, OIDC implicit flow with form post exists, but it is very uncommon to see today. Further, SAML has artifact binding for direct communication, but it is also very uncommon. The point is that if the OP and RP can communicate directly then that relieves pressure off of the authentication response payload to contain all the information necessary to make an authentication and authorization decision. This reduces payload size and complexity. The OIDC OP and RP can instead exchange information in a backchannel.\nOIDC grew organically over the years, whereas SAML was largely designed up front. OIDC encompasses dozens of specifications and RFCs that grew organically over many years. These documents were generally created to solve a specific need rather than trying to anticipate all future needs and building that up front. This is akin to agile methodology versus waterfall, as described in the first section. Consider the following non-exhaustive timeline:OpenID Connect 1.0 specification published (2014)\nJOSE stack finalized for JW{S,E,K,A,T} via RFC 7515-7519 (2015)\nPKCE published via RFC 7636 (2015)\nPKCE for mobile/native apps published via RFC 8252 (2017)\nDevice authorization grant for IoT devices published via RFC 8628 (2019)\nDemonstrating proof of possession (DPoP) for MFA workflows published via RFC 9449 (2023)\nPKCE for SPAs published via RFC 10017 (2026)\n\nI find the historical circumstances interesting too. For example, SAML came of age in an era of VPNs and network segmentation, hence point (2) above. If the IdP or SP was behind a corporate firewall, and it couldn’t speak directly to the other end, then the whole rollout came to a halt and that vendor lost the sales deal. SAML needed to seamlessly account for this situation. Google’s BeyondCorp model and zero-trust architecture flipped this notion on its head in 2014. Additionally, SAML failed to anticipate the mobile, SPA, and IoT revolutions, and had no answers when these technologies arrived on the scene in the late aughts. Even though SAML is still widely adopted in corporate environments, these macroscopic events helped start the long, slow decline of the protocol. Agility and loose coupling enable rapid adaptation in ever-changing IT environments.\nAll roads lead to OIDC\nNo protocol is perfect, but in terms of a solution all roads lead to OIDC. As far as I can tell, the only deployment scenario where SAML had an advantage was networks where the SP and IdP cannot communicate directly. OIDC’s implicit flow with form post provides all the same ingredients. This is actually one of the cleanest migration plans I’ve seen available in the industry.\nSo what can I do if I’m a service provider (i.e., SP) and I’d like to integrate into the SSO ecosystem without SAML? Just support OIDC. Abandon SAML. Apparently Fly.io and Tailscale are already doing it:\nWe’ve managed to hold the line on OIDC so far. So has Tailscale. If Tailscale can hold the line, given who they’re selling to, I think most orgs can. Really, try to avoid doing SAML. Remember, as a vendor, you’re often competing with companies that don’t do real SSO integration at all.\n— Thomas Ptacek, 2024\n\nSo what can I do if I’m an identity or authentication provider (i.e., IdP) and I’d like to move off of SAML? Well, depending on your customer count, this may be a long road indeed. But you know how you eat an elephant? One bite at a time. This is a well-worn path in the industry: develop a deprecation plan, communicate it to customers, stop onboarding new customers to SAML integrations, provide existing SAML customers with equivalent OIDC configurations, set a sunset date, and get to work.\nSAML had a good 25 year run. It birthed the SSO industry, helped secure untold numbers of authentications, improved the UX of authenticating to dozens of web services, and created billions of dollars of economic impact. We should be thankful to the creators of the SAML protocol. It has provided us with a great case study in protocol design and evolution over a very dynamic period in the tech industry.\nIf you’d like to read more about historical analyses of security topics, then check out “Marshal madness: A brief history of Ruby deserialization exploits.”\nContact us if you’re interested in a protocol design audit or would like a review of your authentication system.","tokens":3836,"crawled_at":1791195616186}
+{"id":10544,"url":"https://www.metaplex.com/docs/smart-contracts/mpl-3643/getting-started","domain":"www.metaplex.com","chapter":"docs","title":"Getting Started — Prerequisites and First Steps | MPL-3643","text":"This page covers what you need in place before building on MPL-3643, which path to take, and the shape of the flows for launching a token, onboarding an investor, and executing a compliant transfer.\nMPL-3643 is live on Solana mainnet in early access — request alpha access to build with it.\nAudit status\nMPL-3643 has not been audited. Do not custody real assets without coordinating with Metaplex.\n\nSummary\nBuilding on MPL-3643 means composing a Token-2022 mint with Token ACL, the four MPL-3643 programs, and a KYC provider. The order in which you do it matters, because one step is irreversible.\nChoose Your Path\nThree audiences build against MPL-3643, and they need different things first.\nYou areYou want toYour flow below\nAn RWA issuer\nLaunch and administer a compliant token\nThe Shape of a Token Launch\n\nAn integrating developer\nMove MPL-3643 tokens from a wallet, venue, or app\nThe Shape of a Compliant Transfer\n\nA KYC provider\nMake investors eligible by issuing claims\nThe Shape of Investor Onboarding\n\nWhichever path you take, one fact drives everything else: every MPL-3643 token account is born frozen, and only a compliant wallet can thaw one.\nPrerequisites\nTooling\nRequirementVersionWhy\nNode.js\n20.18.0 or later\nRequired by the TypeScript SDK and generated clients\n\nSolana CLI\n2.1.0 or later\nDevnet interaction and key management\n\nA devnet RPC endpoint\n—\nMust support Token-2022\n\nRust integrators additionally need the Anchor and Solana toolchain versions the programs are built against.\nOn-Chain Prerequisites\nBefore any MPL-3643 instruction succeeds for your token, four things must be true.\nThe mint is Token-2022 with DefaultAccountState = Frozen. This extension cannot be added after the mint is created.\nFreeze authority is delegated to Token ACL, with permissionless thaw and permissionless freeze both enabled in the Token ACL config, and the config sealed so those settings cannot later be changed.\nYou hold a registry token-issuer role grant. This is what lets you create your own compliance, gate, and yield configs without a Metaplex co-signature.\nA trusted attestor covers every topic you require. The attestor you pin must be active and authorized for KYC plus every topic in your token's required set.\nTwo mint decisions cannot be revisited\nDefaultAccountState = Frozen and the transfer hook extension are both fixed when the mint is created. A mint without the hook can never gain per-transfer modules — no lockups, no volume caps, no blackout windows, no venue restrictions. Decide before you create the mint.\n\nThe Shape of a Token Launch\nLaunching a compliant token is a bootstrap sequence whose ordering is enforced by the programs.\nCreate the Token-2022 mint with DefaultAccountState = Frozen, plus the transfer hook extension if per-transfer modules will ever be needed.\nCreate the Token ACL config for the mint, enable both permissionless flags, and seal it.\nInitialize the gate config — requires the raw mint authority. This also creates the token's trust scope.\nAdd accepted KYC providers to the trust scope.\nInitialize lifecycle yield and recovery configs, if the token uses them — requires the raw mint authority.\nInitialize the compliance config. This is the authority-transfer boundary.\nInitialize the gate extra account meta lists, which reads the live compliance config and binds the gate.\nEnable and configure modules, then mint the initial supply through the Compliance Module's mint flow, which keeps holder accounting in sync.\nStep 6 is a one-way door\nCompliance initialization irreversibly moves the mint's MintTokens authority to the ComplianceConfig PDA. Every instruction requiring the raw mint authority — steps 3 and 5 — must run before it. There is no recovery path: a token launched without a trust scope cannot be given one later. The SDK sequences this for you; if you use the generated clients directly, you own the ordering.\n\nThe Shape of Investor Onboarding\nAn investor becomes eligible through four steps, starting from one off-chain verification.\nKYC off-chain. The provider verifies the investor's documents.\nAttestation. The passing result is recorded as a Solana Attestation Service attestation, or prepared as an attestor-signed Direct claim.\nClaim attach. The trusted attestor attaches a wallet-keyed Claim for each topic the token requires; a residency claim records the investor's ISO-3166 country code when the token enforces jurisdiction rules.\nThaw. Anyone submits thaw_permissionless; the Gate Program checks eligibility and Token ACL thaws the account.\nStep 3 happens once per trusted attestor — the party whose key attaches claims on-chain, typically the token issuer. The standard is designed to pair with reusable-KYC providers so an earlier verification can be shared, with the investor's consent, instead of repeated.\nThe Shape of a Compliant Transfer\nMoving an MPL-3643 token is a three-phase envelope, not a single instruction.\nPrepare — ensure the destination's Associated Token Account exists, thaw it, and resolve transfer hook accounts if the token has a hook.\nTransfer — a Token-2022 transfer_checked, with hook metas appended when applicable.\nFinalize — checkpoint yield for both parties if the token pays yield.\nDon't skip the prepare phase: a transfer to a recipient who has never held the token always fails, because their account is born frozen.\nOperational Responsibilities\nA compliant token is not fire-and-forget. Two background jobs keep it correct.\nJobWhat it doesConsequence of not running it\nRe-freeze cranker\nCalls freeze_permissionless on holders that fell out of compliance\nExpired-KYC holders keep trading indefinitely\n\nYield crank and checkpoint\nAdvances the global index and settles holder balances\nYield does not accrue and accounting drifts\n\nBoth are permissionless, so they can be issuer-operated, third-party, or incentivized.\nDecide Before You Build\nFour decisions shape everything downstream, and three of them cannot be changed later.\nDecisionReversible?Consequence\nTransfer hook enabled at mint creation\nNo\nDetermines whether per-transfer modules are ever possible\n\nDefaultAccountState = Frozen\nNo\nRequired; without it MPL-3643 cannot enforce anything\n\nPermanent delegate set to the recovery PDA\nNo\nDetermines whether forced recovery is ever possible\n\nWhich modules are enabled\nYes, mostly\nHolder cap and investor cap must be enabled before any supply exists\n\nNotes\nMPL-3643 tokens are Token-2022 mints. Integrations that hardcode the SPL Token program ID will not see them.\nHolder cap and investor cap must be enabled before any supply exists, and holder cap cannot be disabled once activated.\nUse canonical Associated Token Accounts everywhere. Non-canonical token accounts owned by the same wallet are not tracked by holder accounting and silently desynchronize caps and yield.\nWhether a configuration satisfies a given securities regime is a legal question for the issuer and their counsel. These pages describe what the programs enforce.\nMaintained by Metaplex Foundation. Last verified 2026-09-28.\nFAQ\nHow do I get access to MPL-3643?\nMPL-3643 is live on mainnet in early access. Request access. Alpha partners receive direct onboarding support.\nWhat do I need before launching an MPL-3643 token?\nA Token-2022 mint created with DefaultAccountState = Frozen, a sealed Token ACL config with both permissionless flags enabled, a registry token-issuer role grant, and a trusted attestor authorized for KYC plus every other topic your token will require (e.g., accreditation, sanctions screening).\nShould I use the SDK or the generated program clients?\nUse the SDK. It sequences the irreversible bootstrap ordering and routes each administrative action through the correct direct or gate-wrapped call. The generated clients are for integrators who need instruction-level control and are willing to own that ordering themselves.\nDo I need to run my own cranker?\nYou need one to exist. Nothing re-freezes a non-compliant holder automatically, so without a cranker a holder whose KYC expires keeps trading until someone calls freeze_permissionless. Crankers are permissionless, so it can be yours, a third party's, or an incentivized network.\nCan I add per-transfer rules to a token I already launched?\nNo. Per-transfer modules run inside a Token-2022 transfer hook, and Token-2022 extensions are fixed at mint creation. Launching without the hook permanently rules out lockups, volume caps, blackout windows, and venue restrictions.","tokens":2111,"crawled_at":1791195641729}
+{"id":10545,"url":"https://a16zcrypto.com/posts/article/treasury-management-guide","domain":"a16zcrypto.com","chapter":"research","title":"Treasury Management: A Guide to Navigating Downturns - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nTreasury Management: A Guide to Navigating Downturns\nJeff Amico, Maggie Hsu, Ed Lynch, and Emily Westerhold\n08.24.22\n\nTags & Share Tags\ncompany building\ncustody\nDAOs\ngovernance best practices\nplaybooks\nproduct-market fit\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nCrypto markets can be volatile. Over the past year, prices have swung wildly, only recently rebounding from a brisk “winter.” Up, down, sideways — it’s impossible to know which way the winds will blow. What people can control is, however, the way they prepare for such vicissitudes.\n\nTreasury management is the practice of stewarding a project’s resources over time. The goal is, generally, to ensure a going concern can remain a going concern — that it has enough cash on hand to continue operating. This might involve paying near-term expenses such as payroll and rent, or making longer term strategic investments, such as acquisitions and R&D. Regardless of the expenditure, treasury management should carefully consider and aim to achieve a projects’ core operating goals.\n\nTreasury management is a core function of any organization, but it is particularly relevant today given the uncertainty of present market conditions. From decentralized autonomous organizations, or “DAOs,” to traditional startups, teams are reckoning with a market environment featuring high inflation, low yields, and a tightening of financing options across both public and private markets. In light of this new normal, teams should place greater emphasis on conservative cash management principles in order to weather storms and emerge stronger on the other side of them.\n\nHere is a basic framework that teams can follow to do so.\n\n1. Calculate monthly cash burn\n\nThe first step is to develop a realistic financial model. In accounting terms, that means tracking projected inflows and outflows on a monthly basis (e.g., “net burn”). More plainly, it means calculating how much cash a given project is expected to spend each month, relative to how much it is expected to earn. This analysis should specify the component parts that drive both earning and spending. For example, the expense side should break out the cash-spend across key operating functions (engineering, business development, legal, etc.), as well as any expected non-operating outflows (financing costs, taxes, other one time payments, etc.). The revenue side should similarly break the inflows down into operating and non-operating categories. This will help determine their relative predictability over time.\n\nConservative assumptions will help ensure a project does not overestimate its runway. This is particularly true when projecting revenue. In a downturn, revenue is likely to fall — or at least growth may slow — as customers scale down their budgets or, worse, potentially go out of business. Even revenue assumed to be recurring or contractually committed may become more difficult to collect. While this sort of financial planning does not always apply to the many crypto projects and early stage ventures that have yet to make money, factoring in these probabilities can help projects plan more realistically for the longer term.\n\nShrewd financial planning is a routine exercise for traditional startups — and it’s increasingly relevant for DAOs as well. DAOs differ from traditional startups in many regards, including their organizational structures and degree of decentralized control. In many cases DAOs may be comprised of various unaffiliated entities who are working together toward some shared purpose and who receive budgets from the broader DAO. Traditional companies are, on the other hand, likelier to have cash on the balance sheet from various financing rounds. Nevertheless, as DAOs continue to evolve and take on more sophisticated operating structures, it is critical that they too have visibility into their overall financial health. This will ensure they can meet operating expenses as they come due, including contributor payments, incentive programs, and more. It will also provide transparency into the operating state of the organization, enabling better decision making. While teams like MakerDAO have led the way on this type of analysis to date, we expect this will eventually become table stakes for all successful DAOs in the future.\n\n2. Maintain operating expenses in cash\n\nOnce the rate of cash burn is determined, a project can begin developing an overall treasury management plan. The core objectives here are: capital preservation, liquidity, and income, in that order.\n\nPriority number one is to cover near-term operating expenses. It’s critical to optimize for the safety and accessibility of capital before exploring opportunities for yield. This typically means maintaining at least 12 months – ideally, 18 months – of operating expenses in a basic cash account (e.g., bank deposit or money market account) or, in the case of a DAO, in high-quality stablecoins. This capital will earn relatively little yield, but it will be available to meet near-term liabilities as they come due. Be conservative.\n\nIn addition to maintaining near-term expenses in cash, projects should also ensure they match assets and liabilities by currency. In other words, if liabilities are denominated in USD, then a corresponding amount of liquid assets should also be denominated in USD. This is particularly relevant for companies or DAOs who hold crypto assets but have expenses denominated in dollars. To avoid having to sell depreciated assets in a down market, teams should ensure they are regularly converting assets into the appropriate currency to cover ongoing operating expenses; of course, they must also ensure they’re conducting any asset sales in a manner that complies with applicable regulatory restrictions and has the appropriate legal wrappers in place to enable them to pay taxes, where applicable. Always have what you need on hand.\n\nApparently, diversification is fairly uncommon. A recent study from Chainalysis, a crypto tracking firm, shows that 85% of DAOs store their entire treasury in a single crypto asset — typically their native governance token. Among those who do hold stablecoins, the majority hold 10% or less of their reserves in stablecoins. While some DAOs have limited operating expenses, for those that do have material operations, it’s possible they may be forced to sell their native tokens at depressed prices to cover operating expenses, or cut back on core strategic initiatives. That would be suboptimal.\n\nSome projects may be reluctant to sell crypto for fiat currency or stablecoins out of a concern that it sends a negative signal to the market. These are project-specific decisions, and ones that depend on each project’s unique set of circumstances. They should always take account, however, of any regulatory and tax considerations.\n\nProjects can avoid negative outcomes — like having to sell native tokens in a down market, or cutting back on strategic initiatives — by maintaining a sufficient cash buffer. Managing cash appropriately ensures projects can cover expenses for potentially prolonged periods, which may be critical during a downturn where access to financing markets can be challenging. Planning ahead also allows projects to maintain focus on core operating goals, knowing their working capital remains safe from loss.\n\n3. Develop plan for additional capital\n\nFor companies holding cash in excess of their 12-to-18-month operating budget, it may make sense to explore opportunities for incremental yield. As with the working capital budget discussed in the previous section, this exercise should be informed by the project’s liquidity needs over time. The diagram below provides a high-level look at various products and when they might become appropriate to consider. In general, products offering greater yield become more appropriate as a project moves from operating cash (for meeting day-to-day needs) towards strategic cash (for pursuing growth and other opportunities).Each product has different risk, yield, and liquidity profiles. Before allocating among them, it’s useful to develop a basic plan to guide the overall approach.\n\nHere’s a template investment plan we often share with traditional portfolio companies — ones that fall in the left-hand column above — when discussing this topic. While some of these considerations may be inapplicable to earlier stage companies, DAOs, and other projects, they are nonetheless instructive for learning how companies with larger balance sheets think about managing cash.\n\nIn general, traditional companies allocate excess cash toward safe holdings. These include products such as money market instruments and investment-grade fixed income securities (rated BBB or higher). In a given portfolio, these companies typically diversify assets across maturities, credit quality, sectors, and issuers. For a sense of what this looks like, below is a breakdown of allocations among mid-to-late stage companies with up to $100 million in assets with Silicon Valley Bank.While we’ve seen some corporate treasurers take on additional risk in recent years, a more conservative strategy is often advisable. This is particularly true in the current rate environment, where yield is beginning to return to many traditional credit and banking products. For example, yields on certain money market instruments are beginning to approach 150 or 200 basis points in some cases, making them an attractive option for managing cash. A portfolio anchored around these types of assets is likely to be well-suited for many companies.\n\nMeanwhile, for DAOs managing on-chain treasuries, a variety of money market and fixed-income products have emerged in recent years that may be appropriate to consider. These include products such as Compound, Element Finance, and Goldfinch, among others. For longer-term cash, it may make sense to explore staking with high-quality protocols like Lido and others. As with more traditional products, however, it’s important to consider the risk, yield, and liquidity profiles of these options before allocating to them. It’s also important to evaluate any technical or operational risks that may arise when interacting with assets or protocols on-chain to ensure a project isn’t exposing assets to risk of loss.\n\n4. Build out operational capacity\n\nWith a strategy in place, it’s time to build out the various operational pieces needed to put the plan into action. For companies with more traditional treasury management plans, this includes finding a banking partner and an investment advisor, and putting in place internal processes to ensure proper custody, reporting, valuation, controls, tax, and audit requirements.\n\nProjects don’t have to figure everything out all on their own. The banking partner should be able to help provide investment vehicles that fit within a company’s investment policy. The banking partner may also be able to recommend more sophisticated investment advisors to help maximize returns within specified risk parameters. Always consult with an accounting firm or auditor on proper practices and procedures as they relate to accounting for investments and related earnings.\n\nFor DAOs or companies holding crypto, the diagram below lays out the key operational pieces that may be required as well as some of the leading options in each:At a minimum, a secure wallet setup is necessary to ensure assets are always safely custodied. This is particularly relevant any time assets are being deployed into other protocols or otherwise moving on-chain. Options range from traditional custodians such as Anchorage or Coinbase to decentralized or multi-sig options, like Entropy or Gnosis.\n\nBeyond custody, DAOs will typically also need some form of governance approval from tokenholders before executing a treasury management strategy. Tools like Snapshot and Tally can be used for voting, while forums like Discourse and Commonwealth can help facilitate community discussion.\n\nDAOs can also tap into the emerging suite of on-chain analytics products to monitor the state of their strategy over time, including Nansen, Dune and Flipside Crypto. Payroll and operations-related tools like Opolis, Coordinape, and Utopia can also be used to manage budgets and track spending over time.\n\nAnd finally, given the complexity of this task, it may be worthwhile to consult with firms who provide advisory services on this topic. These range from traditional advisors such as Silicon Valley Bank to more crypto-native firms such as Reverie, Alastor, Gauntlet, and Llama, among others. Teams should also make sure to conduct regulatory analysis of various strategies and engage outside counsel as appropriate.\n\n5. Monitor and make adjustments as necessary\n\nFinally, teams should actively monitor their cash positions and adjust their strategies as necessary. This requires updating burn projections to ensure cash is being managed properly. Teams should also regularly confirm that their strategies remain oriented around their core principles (capital preservation, liquidity, income). Doing so will ensure they do not take on unnecessary risk as their strategy evolves over time.\n\ntl;dr\n\nTreasury management is an integral part of any projects’ long-term success. To maximize the chances for success, both cash management and longer-term capital allocation should be both well defined and well executed. The goals are capital preservation, liquidity, and income, in precisely that order.\n\nUnder current economic conditions, it’s important to think critically about potential unforeseen business expenses that may arise outside of the course of normal operations. Once a project has a conservative estimate of the capital required to keep running, it should earmark an available cash balance equal to at least 12 months — or better, 18 months — of net cash outflows. Any remaining cash reserves can then be allocated according to a policy that should clearly define the relevant stakeholders, the specific roles of each stakeholder, the institutions involved in executing the strategy, and the reporting requirements associated with any holdings. After a strategy is put in place, the performance of holdings should be monitored and the suitability of the strategy periodically evaluated as it relates to the ever changing needs of a project.\n\nPreparation now prevents pain later on.\n\n***\n\nAcknowledgements: Special thanks to Silicon Valley Bank for allowing us to share a breakdown of investment policies among a subset of its asset management group’s clients.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nCharts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":4330,"crawled_at":1791195619807}
+{"id":10546,"url":"https://docs.ethena.fi/technical-design/hedging-system","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Hedging System | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nEthena's \"Hedging System\" is composed of a number of offchain application services that enable many critical aspects of the user experience, including:\n\nCalculating & publishing indicative prices for minting & redeeming USDe.\n\nReturning pricing to mint & redeem USDe requests.\n\nEnsuring the integrity of the system in real time.\n\nThe \"Hedging System\" ingests & interacts directly with the protocol's onchain smart contracts as well as the Ethereum blockchain.\n\nThe \"Hedging System\" is extremely risk-aware and has been designed in a manner wherein the preservation of protocol collateral is the most important consideration.\n\nResponsibilities\nAt a level lower of detail, the \"Hedging System\" performs the following functions (but is not limited to):\n\nIngests market data from CeFi Exchanges, \"Off-Exchange Settlement\" providers, Pyth and Redstone. This data includes order book updates, public trade information, as well as private portfolio, positions, orders, and trade information.\n\nNormalizes and validates the integrity of market data.\n\nCalculates the risk exposure of the portfolio relative to defined risk limits and goals.\n\nReconciles internal system information relating to the protocol's portfolio, positions, orders, and trade information with CeFi Exchanges & \"Off-Exchange Settlement\" providers.\n\nCalculates & publishes indicative prices for minting & redeeming USDe.\n\nIngests, validates, and publishes pricing for mint & redeem USDe requests.\n\nDetermines where to route & execute orders upon a successful mint & redeem USDe request. This incorporates information about fees, depth of liquidity, existing positions, and other funding + basis opportunities.\n\nIn real-time, validates all information & operations to ensure integrity relative to internal & external expectations.\n\nMonitors and alerts in regards to the availability of internal & external dependencies such as other internal services or CeFi Exchanges.\n\nOrchestrates the movement of backing assets between \"Off-Exchange Settlement\" providers and CeFi Exchanges.\n\nPublishes & alerts Ethena team members to real-time developments. Enabling immediate manual intervention in the event of inconsistency.\n\nPublishes & logs system data to different data stores. An example being the publication of trade data to a database.\n\nHedging FAQ\nNotion FAQ Link\n\nLast updated 1 year ago\nWas this helpful?","tokens":615,"crawled_at":1791195647194}
+{"id":10547,"url":"https://www.metaplex.com/docs/smart-contracts/mpl-3643","domain":"www.metaplex.com","chapter":"docs","title":"MPL-3643 — Permissioned Token Standard for RWAs on Solana | Metaplex","text":"MPL-3643 is a suite of onchain programs that enables the issuance, management, and transfer of permissioned tokens on Solana. It is the ERC-3643 equivalent for Solana, implemented through the mpl-permission programs. It ensures only users meeting pre-defined conditions can become token holders, making it ideal for digital assets that represent real-world value, like securities, real estate and private funds. Compliance is a layer above a standard Token-2022 token, not a new token type.\nMPL-3643 is live on Solana mainnet in early access — request alpha access to build with it.\nAudit status\nMPL-3643 has not been audited. Do not custody real assets without coordinating with Metaplex.\n\nSummary\nMPL-3643 is comprised of four Metaplex programs on top of Token-2022, Token ACL (sRFC 37), and the Solana Attestation Service so that an issuer can launch a permissioned token with eligibility rules that are enforced by onchain programs rather than by custom per-issuer code.\nStandard and implementation — MPL-3643 names the standard; mpl-permission names the code. The repository, npm packages, and Rust crates all use the mpl-permission prefix.\nStandard token, layered compliance — an MPL-3643 token is a Token-2022 mint, not a custom token program, so wallets, explorers, and DEXs integrate through their existing Token-2022 support. The degree of support depends on each venue's handling of the extensions a mint uses, such as transfer hooks, and its own policies for permissioned assets.\nFour programs — Identity Registry, Compliance Module, Gate, and Lifecycle Manager, each independently auditable.\nReusable verification — the standard is designed to pair with reusable-KYC providers: with the investor's consent, an existing verification is shared to a new issuer off-chain, so investors avoid repeating document collection while each issuer retains its own data custody, regulatory responsibility, and on-chain claims.\nEarly access — live on mainnet; request alpha access to build with it. See Status and availability.\nWho MPL-3643 Is For\nMPL-3643 serves four audiences, each with a different entry point. Start with Getting Started.\nAudienceWhat they do\nRWA issuers\nLaunch and administer a permissioned token — pre-conditions like jurisdictions, lockups\n\nIntegrating developers\nBuild wallets, venues, or apps that move MPL-3643 tokens\n\nKYC providers\nIssue attestations that make investors eligible\n\nWallet and venue integrators\nSurface frozen accounts, thaw flows, and rejection reasons to users\n\nWhat MPL-3643 Solves\nToken-2022, Token ACL, and the Solana Attestation Service already provide the primitives for permissioned tokens, but nothing assembles them into a compliance-first system. Every issuer of regulated tokens on Solana today writes that assembly from scratch.\nMPL-3643 supplies the missing pieces:\nA Gate program that implements the sRFC 37 gate interface by checking identity and compliance state.\nA registry that maps attestations to per-token requirements — \"for this token you need KYC plus accreditation from a trusted provider\".\nA configurable rule engine — holder caps, jurisdiction lists, lockups, volume limits — that enforces onchain without custom code per issuer.\nLifecycle infrastructure — vesting, corporate actions, and guardrailed recovery — tied to compliance state.\nMPL-3643 Architecture\nMPL-3643 is four Metaplex programs layered over three existing Solana components. Identity, compliance rules, and freeze authority are separate concerns in separate programs, so each can be audited and upgraded independently.\nidentity check\neligibility / re-freeze checks\nCPI\nreads live attestation\nfreeze / thaw\n\nmpl-permission TypeScript SDK\n\nToken profiles, one-call token launch\n\nIdentity Registry\n\nClaim, TrustedAttestor, TokenTrustScope\n\nCompliance Module\n\nBoundary and per-transfer rule modules\n\nLifecycle Manager\n\nYield, vesting, corporate actions, recovery\n\nGate Program\n\nImplements the sRFC 37 gate interface\n\nToken ACL (sRFC 37)\n\nHolds the mint freeze authority\n\nSolana Attestation Service\n\nLive KYC attestations\n\nToken-2022 Mint\n\nDefaultAccountState = Frozen\n\nReact Flow\nPress enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.\nPress enter or space to select an edge. You can then press delete to remove it or escape to cancel.\n\nDiagram description: The mpl-permission TypeScript SDK sits above three programs — Identity Registry, Compliance Module, and Lifecycle Manager. The Gate Program sits below the Compliance Module and calls into both the Identity Registry (identity verification) and the Compliance Module (hold-eligibility and re-freeze checks). Token ACL holds the mint's freeze authority and cross-program-invokes the Gate Program to decide every freeze and thaw; the Identity Registry reads live attestations from the Solana Attestation Service. Token ACL is the only component that calls Token-2022's freeze and thaw instructions on the mint, whose accounts are born frozen via DefaultAccountState.\nProgram Responsibilities\nEach MPL-3643 program owns exactly one concern.\nProgramOwns\nIdentity Registry\nClaims, trusted attestors, per-token trust scope\n\nCompliance Module\nOffering rules — holder caps, countries, lockups, volume, blackouts\n\nGate Program\nComposing identity + compliance into the two sRFC 37 entry points\n\nLifecycle Manager\nYield, vesting, corporate actions, guardrailed recovery\n\nCompliance Modules\nAn issuer composes per-token policy from a menu of compliance modules, enabling and configuring each independently. MPL-3643 is in active development, so the module set may change before release.\nModuleRule it enforces\nCountry\nAllow- or deny-lists holders by the country in their residency claim\n\nHolder cap\nCaps the total number of holders\n\nInvestor cap\nCaps the number of unique investors, counting linked wallets as one investor\n\nLockup\nTime-locks newly acquired tokens before they can be transferred\n\nAffiliate volume\nCaps transfer volume for designated holders\n\nBlackout\nHalts transfers during scheduled windows\n\nJurisdiction pair\nRestricts transfers between specific country pairs\n\nVenue\nRestricts trading to approved venues\n\nClaim Topics\nIdentity claims are organized by topic — the vocabulary of facts a trusted attestor can assert about a wallet. Topics defined today include KYC, AML, residency, accreditation, and sanctions screening, plus classification topics used internally by specific modules. Each token's trust policy names the topics it requires, and each trusted attestor is authorized per topic. The topic space is extensible: a new pass/fail eligibility label is a configuration change rather than a program change. As with the module set, the topics defined today may be refined before release.\nRoles of Metaplex and the Issuer\nMetaplex provides the infrastructure; the issuer sets the policy for its tokens.\nMetaplex provides the onchain infrastructure. Metaplex deploys and maintains the four programs that power MPL-3643 and curates the global trusted attestor list. MPL-3643 enforces the issuer's pre-conditions for users to hold their tokens.\nThe issuer is the policy operator. Each issuer creates their own ComplianceConfig, chooses which modules to enable, configures module parameters, selects which KYC providers to accept via a per-token trust scope, and controls the owner key. The issuer is responsible for the token itself and its compliance posture.\nMPL-3643 enforces configuration, it does not guarantee compliance\nThese pages describe what the programs enforce. Whether a given configuration satisfies applicable regulations is a question for the issuer and their legal counsel.\n\nERC-3643 to MPL-3643 Component Mapping\nMPL-3643 keeps ERC-3643's separation of concerns and substitutes Solana primitives for each Ethereum contract.\nERC-3643 componentMPL-3643 equivalent\nToken contract (ERC-20)\nToken-2022 mint wired to Token ACL (sRFC 37)\n\nIdentity Registry\nIdentity Registry program\n\nIdentity Registry Storage\nWallet-keyed Claim accounts in the Identity Registry\n\nONCHAINID\nWallet-keyed Claim accounts, backed by Solana Attestation Service attestations or attached directly by a trusted attestor\n\nTrusted Issuers Registry\nTrustedAttestor accounts in the Identity Registry\n\nClaim Topics Registry\nThe token trust scope's required topics, set per token\n\nCompliance Module\nCompliance Module program plus the sRFC 37 Gate Program\n\nAgent role\nowner / operator / agent roles via per-program RoleGrant PDAs\n\nThe one structural difference: ERC-3643 checks compliance inside the token's transfer(). Solana has no equivalent hook on a plain transfer, so MPL-3643 enforces eligibility at freeze and thaw time — accounts are born frozen and only a compliant wallet can thaw one. Some compliance modules — rules that must be evaluated on every transfer, such as lockups or volume limits — require per-transfer checks, and those are enforced through a Token-2022 transfer hook.\nHow MPL-3643 Differs from a Plain Token-2022 Mint\nMPL-3643 changes who may hold a token, not how the token itself moves.\nPlain Token-2022 mintMPL-3643 token\nToken account initial state\nThawed\nFrozen (DefaultAccountState = Frozen)\n\nFreeze authority\nIssuer key\nToken ACL MintConfig PDA\n\nMint authority\nIssuer key\nComplianceConfig PDA, after compliance initialization\n\nWho may thaw\nFreeze authority\nAnyone, permissionlessly — the Gate Program decides\n\nWho may hold\nAnyone\nWallets that pass the identity and hold-eligibility checks\n\nPer-transfer cost\nNone\nNone on boundary-only tokens; a transfer hook when opted in\n\nProtocol Fees\nMPL-3643 charges flat protocol fees, paid in SOL, at asset configuration, holder account activation, and distribution execution. Nothing is a percentage of value transferred, capital raised, or assets under management.\nInstructionSolana\nAsset configuration (once per configuration or amendment)\n0.063 SOL\n\nHolder account activation (once per holder)\n0.034 SOL\n\nDistribution execution (once per recipient)\n0.00085 SOL\n\nSee the Protocol Fees page for up-to-date information on all Metaplex protocol fees.\nQuick Reference\nPrograms\nProgramProgram namePurpose\nIdentity Registry\nmpl-permission-identity-registry\nClaims, trusted attestors, trust scopes\n\nCompliance Module\nmpl-permission-compliance\nBoundary and per-transfer rule enforcement\n\nGate Program\nmpl-permission-gate\nsRFC 37 gate for thaw and freeze decisions\n\nLifecycle Manager\nmpl-permission-lifecycle\nYield, vesting, corporate actions, recovery\n\nSDKs\nMPL-3643 ships with a unified TypeScript SDK (@metaplex-foundation/mpl-permission) and a Rust SDK (mpl-permission), each backed by generated low-level clients for the four programs. The SDKs are the primary interface and sequence the launch bootstrap ordering automatically. They are provided through alpha onboarding.\nExternal Dependencies\nDependencyRole in MPL-3643Status\nToken-2022\nThe mint and token accounts\nLive on mainnet\n\nToken ACL (sRFC 37)\nHolds the mint freeze authority; calls the Gate Program\nLive on mainnet and devnet; source audited\n\nSolana Attestation Service\nLive KYC and accreditation attestations\nLive on mainnet\n\nStatus and Availability\nMPL-3643 is live on mainnet in early access, pre-audit.\nEarly access on mainnet. The four programs are deployed on mainnet and operated with alpha partners (request alpha access).\nAudit. MPL-3643 will undergo a security audit. See Security for how Metaplex audits programs and how to report a vulnerability.\nToken ACL dependency. Token ACL (sRFC 37) is live and its source has been audited. MPL-3643 verifies the Token ACL deployment it binds to as part of release diligence.\nStability level. MPL-3643 is listed as Experimental on the Stability Index.\nNotes\nMPL-3643 tokens are Token-2022 mints, not legacy SPL Token mints. Integrations must use the Token-2022 program ID.\nBoundary-only tokens have no transfer hook, so post-thaw transfers carry no MPL-3643 compute cost. Per-transfer modules require opting into the Compliance Module's Token-2022 transfer hook, which cannot be added retroactively to an existing mint.\nOn-chain enforcement makes a small, fixed set of facts publicly readable, none containing direct identifiers: a wallet subject to jurisdiction rules holds a residency claim recording its ISO-3166 country code — the tradeoff for enforcing those rules autonomously, and the same choice ERC-3643's ONCHAINID makes; claims expose their topic, attestor, and expiry; and tokens that opt into an investor-count cap link wallets controlled by the same investor. Names, documents, and detailed KYC results stay off-chain, though the wallet-keyed records themselves are public and, like any public-chain data, can constitute personal data for an observer able to associate the wallet with its owner.\nCompliance initialization irreversibly transfers the mint's MintTokens authority to the ComplianceConfig PDA. Every instruction needing the raw mint authority must run before it.\nMaintained by Metaplex Foundation. Last verified 2026-09-28.\nFAQ\nWhat is MPL-3643?\nMPL-3643 is an on-chain standard for permissioned tokens on Solana, purpose built for RWAs like tokenized securities — the framework equivalent of ERC-3643, implemented through the mpl-permission program suite. It comprises four Metaplex programs — Identity Registry, Compliance Module, Gate, and Lifecycle Manager — on top of Token-2022, Token ACL (sRFC 37), and the Solana Attestation Service. Developer artifacts — the repository, npm packages, and Rust crates — use the mpl-permission prefix.\nIs MPL-3643 a new token program?\nNo. MPL-3643 tokens are standard Token-2022 mints, and compliance is a layer above the token rather than a replacement for it. Wallets, explorers, and DEXs integrate through their existing Token-2022 support; the degree of support depends on each venue's handling of the extensions a mint uses, such as transfer hooks, and its own policies for permissioned assets.\nHow is MPL-3643 related to ERC-3643?\nMPL-3643 is the Solana counterpart to ERC-3643, keeping the same architecture of separate identity, compliance, and token layers while building each layer from Solana primitives. Token-2022 provides the token, Token ACL and the Gate Program perform the role of ERC-3643's compliance callback, and wallet-keyed Claim accounts serve the role ONCHAINID plays on Ethereum. Claims can be backed by Solana Attestation Service attestations or attached directly by a trusted attestor. See the component mapping.\nDo users have to complete KYC once per token?\nEach offering makes its own admission decision. When the issuer needs access to the underlying KYC data, MPL-3643 is designed to pair with reusable-KYC providers: with the investor's consent, the original verification is shared with the new issuer off-chain, so the investor avoids re-uploading documents, while each issuer keeps its own data custody and regulatory responsibility. For issuances that do not need access to the underlying data, there is a simpler route of relying on a shared on-chain attestation, which means placing trust in the attestation provider that performed the verification. Names, documents, and detailed KYC results remain off-chain in either route: a shared on-chain attestation records only the passing verification outcome, and MPL-3643 records enforcement metadata such as the wallet, claim topics, attestors, and expiries. Because that metadata is wallet-keyed and public, it can still amount to personal data for anyone able to associate the wallet with its owner.\nDoes every MPL-3643 transfer cost extra compute?\nOnly when the issuer opts into per-transfer enforcement. Boundary-only tokens enforce compliance at thaw time and continuously through permissionless re-freeze, so post-thaw transfers are ordinary Token-2022 transfers. Tokens that enable the Compliance Module's transfer hook pay for a compliance evaluation on every transfer.\nCan an issuer seize or claw back tokens?\nOnly if the mint opts into recovery. A recovery-enabled mint sets the Token-2022 permanent delegate to a Lifecycle Manager program address that has no private key and can only sign through guardrailed recovery instructions — separate proposer and approver roles, a timelock, a bounded execution window, an on-chain audit trail, and a per-request target account and amount. Mints without a permanent delegate cannot be clawed back at all.\nIs MPL-3643 available on mainnet?\nYes. MPL-3643 is live on Solana mainnet in early access. Request alpha access to get started.\nGlossary\nTermDefinition\nAttestation\nA signed, on-chain credential issued by a KYC provider through the Solana Attestation Service.\n\nBoundary module\nA compliance rule evaluated when a wallet enters or leaves eligibility (thaw, re-freeze, mint, burn) rather than on each transfer.\n\nClaim\nA wallet-keyed Identity Registry account recording that a wallet holds a specific claim topic from a specific trusted attestor.\n\nClaim topic\nA numeric identifier for a kind of claim, such as KYC, accreditation, or holder role.\n\nCranker\nA permissionless caller that re-freezes accounts that have fallen out of compliance, or advances the yield index.\n\nGate Program\nThe MPL-3643 program that implements the sRFC 37 gate interface and answers every thaw and freeze decision.\n\nPer-transfer module\nA compliance rule evaluated inside the Token-2022 transfer hook on every transfer.\n\nRe-freeze\nPermissionlessly freezing an account that has fallen out of compliance after previously being thawed.\n\nsRFC 37\nThe Solana standard defining Token ACL and the gate program interface for permissionless freeze and thaw.\n\nToken ACL\nThe live Solana program that holds a mint's freeze authority and consults a gate program before freezing or thawing.\n\nTransfer envelope\nThe prepare, transfer, finalize sequence an integrator must follow to move an MPL-3643 token.\n\nTrust scope\nA per-token account naming which trusted attestors a token accepts and which claim topics it requires.\n\nTrusted attestor\nThe party whose key attaches claims on-chain — typically the token issuer — registered globally in the Identity Registry and authorized for specific claim topics. Distinct from the off-chain KYC provider that performs the verification.","tokens":4546,"crawled_at":1791195660348}
+{"id":10548,"url":"https://www.youtube.com/watch?v=EqnM9KtL-M8","domain":"www.youtube.com","chapter":"developer_specs","title":"Accelerate USA 2026: Arjun Sethi - YouTube","text":"Accelerate USA 2026: Arjun Sethi\n\n2x\n\nAccelerate USA 2026: Arjun Sethi\nSolana 1,708 views 4 months ago\n\nIf playback doesn't begin shortly, try restarting your device.\n\n•\n\nYou're signed out\nVideos that you watch may be added to the TV's watch history and influence TV recommendations. To avoid this, cancel and sign in to YouTube on your computer.\n\nUp next\n\nLive\nUpcoming\n\nPlay now\n\nShare\nInclude playlist\n\nAn error occurred while retrieving sharing information. Please try again later.\n\n0:03\n\n0:04 / 14:18\n\n•Watch full video\n\n12:07\nHuge: ”Blocking Voters Is Arbitrary, No Excuse Can Justify It” :Justice BhuyanTheRedMike137k • 3 hr agoLivePlaylist ()Mix (50+)20:34\nTRANSFORM 2026 Houston: How the Toyota Way Drives Product & Process Quality Improvements at the EdgeZEDEDA27 • 8 days agoLivePlaylist ()Mix (50+)9:47\nअजय राय को हटाकर मोना मिश्रा को लाने की इनसाइड स्टोरी । Navin KumarArticle19 India16k • 1 hr agoLivePlaylist ()Mix (50+)53:38\nSystem Design Concepts Course and Interview PrepfreeCodeCamp.org3.1m • 2 yr agoLivePlaylist ()Mix (50+)16:03\nIndia’s $12.5 Trillion Dream: The Growth Problem No One Is Talking About | Indian Express SpecialThe Indian Express172k • 2 days agoLivePlaylist ()Mix (50+)20:43\nThe Real Power Of Gyanesh Kumar | Why Modi-Shah Will Never Push The CEC To Resign | Akash BanerjeeThe Deshbhakt6.6m • 8 days agoLivePlaylist ()Mix (50+)31:43\nTRANSFORM 2026 Houston: AI at the Edge: Ready or Not?ZEDEDA31 • 8 days agoLivePlaylist ()Mix (50+)19:55\nHow Long Is Your LIFELINE? | Reality of Palmistry | Dhruv RatheeDhruv Rathee5.5m • 20 hr agoLivePlaylist ()Mix (50+)25:51\nLIVE PC में चला दिए मोदी-शाह के वीडियो, मच गया हड़कंप! | Shakti Singh Gohil | Share MarketIndian National Congress82k • 2 hr agoLivePlaylist ()Mix (50+)11:31\nPick One Idea and Go DeepY Combinator170k • 3 mo agoLivePlaylist ()Mix (50+)3:35:08\nn8n Tutorial – Zero to Hero CoursefreeCodeCamp.org1m • 9 mo agoLivePlaylist ()Mix (50+)12:41\nWhy is the BJP backing Gyanesh Kumar | Let Me Explainnewslaundry101k • 7 hr agoLivePlaylist ()Mix (50+)\n\nAccelerate USA 2026: Arjun Sethi\n\nSolana\n\nSolana\n\n95.6k subscribers\n\n1.7k views 4 months ago\n\n1,708 views • 11 May 2026\n\nDISCLAIMER\nThe content herein is provided for educational, informational, and entertainment purposes only, and does not constitute an offer to sell or a solicitation of an offer to buy any securities, options, futures, or other derivatives related to securities in any jurisdiction, nor should …...more\n\n...more\n\nHow this was made\nAuto-dubbed\nAudio tracks for some languages were automatically generated. Learn more\n\nChapters\n\nExpanding crypto offerings\n\nExpanding crypto offerings\n\n0:00\n\nExpanding crypto offerings\n\n0:00\n\nMarket demand for X stocks\n\nMarket demand for X stocks\n\n1:48\n\nMarket demand for X stocks\n\n1:48\n\nPermissionless innovation\n\nPermissionless innovation\n\n4:29\n\nPermissionless innovation\n\n4:29\n\nFuture of real-world assets\n\nFuture of real-world assets\n\n6:11\n\nFuture of real-world assets\n\n6:11\n\nInfrastructure and integration\n\nInfrastructure and integration\n\n7:51\n\nInfrastructure and integration\n\n7:51\n\nLong-term growth and outlook\n\nLong-term growth and outlook\n\n11:09\n\nLong-term growth and outlook\n\n11:09\n\nTranscript\n\nFollow along using the transcript.\n\nSolana\n\n95.6k subscribers\n\nVideos\n\nAbout\n\nTwitter\n\nDiscord\n\nReddit\n\nInstagram\n\nLinkedIn\n\nShow less\n\nAccelerate USA 2026: Arjun Sethi\n1,708 views1.7k views\n11 May 2026\n\nComments\n\nComments\n2\n\nTop\n\nShow featured comments\n\nNewest\n\nShow recent comments, including potential spam\n\nIn this video\n\nChapters\n\nThese chapters are auto-generated\n\nExpanding crypto offerings\n\nExpanding crypto offerings\n\n0:00\n\nExpanding crypto offerings\n\n0:00\n\nMarket demand for X stocks\n\nMarket demand for X stocks\n\n1:48\n\nMarket demand for X stocks\n\n1:48\n\nPermissionless innovation\n\nPermissionless innovation\n\n4:29\n\nPermissionless innovation\n\n4:29\n\nFuture of real-world assets\n\nFuture of real-world assets\n\n6:11\n\nFuture of real-world assets\n\n6:11\n\nInfrastructure and integration\n\nInfrastructure and integration\n\n7:51\n\nInfrastructure and integration\n\n7:51\n\nLong-term growth and outlook\n\nLong-term growth and outlook\n\n11:09\n\nLong-term growth and outlook\n\n11:09\n\nAccelerate USA 2026: Arjun Sethi\n\nSolana\n\nSolana\n\n4Likes\n1.7kViews\n11 May2026\n\nDISCLAIMER\nThe content herein is provided for educational, informational, and entertainment purposes only, and does not constitute an offer to sell or a solicitation of an offer to buy any securities, options, futures, or other derivatives related to securities in any jurisdiction, nor should not be relied upon as advice to buy, sell or hold any of the foregoing. This content is intended to be general in nature and is not specific to you, the user or anyone else. You should not make any decision, financial, investment, trading or otherwise, based on any of the information presented without undertaking independent due diligence and consultation with a professional advisor. Solana Foundation Foundation and its agents, advisors, council members, officers and employees (the “Foundation Parties”) make no representation or warranties, expressed or implied, as to the accuracy of the information herein and expressly disclaims any and all liability that may be based on such information or any errors or omissions therein. The Foundation Parties shall have no liability whatsoever, under contract, tort, trust or otherwise, to any person arising from or related to the content or any use of the information contained herein by you or any of your representatives. All opinions expressed herein are the speakers’ own personal opinions and do not reflect the opinions of any entities. …...more\n\n...more\nShow less\n\nHow this was made\nAuto-dubbed\nAudio tracks for some languages were automatically generated. Learn more\n\nChapters\n\nExpanding crypto offerings\n\nExpanding crypto offerings\n\n0:00\n\nExpanding crypto offerings\n\n0:00\n\nMarket demand for X stocks\n\nMarket demand for X stocks\n\n1:48\n\nMarket demand for X stocks\n\n1:48\n\nPermissionless innovation\n\nPermissionless innovation\n\n4:29\n\nPermissionless innovation\n\n4:29\n\nFuture of real-world assets\n\nFuture of real-world assets\n\n6:11\n\nFuture of real-world assets\n\n6:11\n\nTranscript\n\nFollow along using the transcript.\n\nSolana\n\n95.6k subscribers\n\nVideos\n\nAbout\n\nTwitter\n\nDiscord\n\nReddit\n\nInstagram\n\nLinkedIn\n\nTranscript\n\nNaN / NaN\n\n12:07\n\nNew\n\nHuge: ”Blocking Voters Is Arbitrary, No Excuse Can Justify It” :Justice Bhuyan\nTheRedMike\n\n137k 3 hr ago\n\n20:34\n\nTRANSFORM 2026 Houston: How the Toyota Way Drives Product & Process Quality Improvements at the Edge\nZEDEDA\n\n27 8 days ago\n\n9:47\n\nNew\n\nअजय राय को हटाकर मोना मिश्रा को लाने की इनसाइड स्टोरी । Navin Kumar\nArticle19 India\n\n16k 1 hr ago\n\n53:38\n\nSystem Design Concepts Course and Interview Prep\nfreeCodeCamp.org\n\n3.1m 2 yr ago\n\n16:03\n\nNew\n\nIndia’s $12.5 Trillion Dream: The Growth Problem No One Is Talking About | Indian Express Special\nThe Indian Express\n\n172k 2 days ago\n\n20:43\n\nThe Real Power Of Gyanesh Kumar | Why Modi-Shah Will Never Push The CEC To Resign | Akash Banerjee\nThe Deshbhakt\n\n6.6m 8 days ago\n\n31:43\n\nTRANSFORM 2026 Houston: AI at the Edge: Ready or Not?\nZEDEDA\n\n31 8 days ago\n\n19:55\n\nNew\n\nHow Long Is Your LIFELINE? | Reality of Palmistry | Dhruv Rathee\nDhruv Rathee\n\n5.5m 20 hr ago\n\n25:51\n\nNew\n\nLIVE PC में चला दिए मोदी-शाह के वीडियो, मच गया हड़कंप! | Shakti Singh Gohil | Share Market\nIndian National Congress\n\n82k 2 hr ago\n\n11:31\n\nPick One Idea and Go Deep\nY Combinator\n\n170k 3 mo ago\n\n3:35:08\n\nn8n Tutorial – Zero to Hero Course\nfreeCodeCamp.org\n\n1m 9 mo ago\n\n12:41\n\nNew\n\nWhy is the BJP backing Gyanesh Kumar | Let Me Explain\nnewslaundry\n\n101k 7 hr ago\n\n15:31\n\nNew\n\nUFC Fighter Accidentally Exposes a Huge Scam\nCoffeezilla\n\n6.8m 5 days ago\n\n19:48\n\nNew\n\nMarket Bottom, RBI Policy, Commodities And Financials: Rohit Srivastava's Full Outlook\nmoneycontrol\n\n4.7k 4 hr ago\n\n14:30\n\nNVIDIA Explained Like You're 5\nCrayon Capital\n\n918k 2 mo ago\n\n14:33\n\nNew\n\nWhat Institutions Want From Onchain Data, with William Lai of Allium\nSolana\n\n530 2 days ago\n\n21:53\n\nAccelerate USA 2026: Anatoly Yakovenko\nSolana\n\n1.7k 4 mo ago\n\n20:02\n\nNew\n\nHDFC Bank, Kotak & ICICI: Macquarie’s Suresh Ganapathy Reveals Top Banking Picks | Business News\nET Now\n\n1.8k 4 hr ago\n\n3:42\n\nNew\n\nAbhijit Dipke, SauravDas ने Jantar Mantar Protest पर Amit Shah, Modi सरकार को क्या चेतावनी दी?\nThe Lallantop\n\n201k 6 hr ago\n\n39:45\n\nNew\n\nदिल्ली आएंगे कॉकरोच, जंतर-मंतर पर आज भी ज़बरदस्त प्रदर्शन, सिब्बल हुए शामिल, राहुल की अपील\nRavish Kumar Official\n\n3m 1 day ago","tokens":2119,"crawled_at":1791195668480}
+{"id":10549,"url":"https://docs.ethena.fi/video-guides/how-to-buy-usde","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"How to Buy USDe | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\n\nUsing the UI, non-whitelisted users are able to exchange stablecoins for USDe by accessing external liquidity pools available:\n\nThe user requests to buy USDe via the dApp interface by selecting a stablecoin asset to exchange for USDe.\n\nThis transaction is routed using MEV protection through CowSwap to various onchain liquidity pools in exchange for USDe.\n\nThis abstracts away the complexity for all users allowing stablecoins as an input asset, and causes small imbalances in the onchain AMM pools which triggers an opportunity for market makers to proceed with the mint workflow outlined below.\n\nUsers may also exchange fiat for USDe using our partners Alchemy Pay and Transak.\nMinting USDe is the process of sending backing assets to the Ethena protocol in exchange for USDe. Redeeming USDe is the process of burning USDe in exchange for backing assets. Whitelisted users can mint or redeem USDe via our API or through the \"Mint\" tab in the app, which is only visible to whitelisted users.\n\nLast updated 1 year ago\nWas this helpful?","tokens":283,"crawled_at":1791195675884}
+{"id":10550,"url":"https://www.metaplex.com/docs/smart-contracts/bubblegum-v2/faq","domain":"www.metaplex.com","chapter":"docs","title":"FAQ - Bubblegum V2 - Metaplex","text":"Summary\nThis page answers the most common questions about Bubblegum V2 compressed NFTs, including costs, transaction errors, and differences from V1.\nFind required parameters for leaf-mutating instructions using getAssetWithProof\nResolve \"Transaction too large\" errors with truncateCanopy or Address Lookup Tables\nUnderstand tree costs and capacity before creating a tree\nBubblegum V2 is not backward-compatible with V1 trees or decompression\ncNFTs can inherit seller fee basis points from an MPL-Core collection's Royalties plugin\nWhat is Bubblegum V2?\nBubblegum V2 is a new iteration of the Bubblegum program that introduces several improvements and new features. It is part of the known Bubblegum program, but the instructions and data structures are different. With Bubblegum V2 cNFTs are grouped into collections using MPL-Core Collections instead of Metaplex Token Metadata Collections. It also introduces new features like freezing, thawing, and soulbound NFTs and additional features like:\nFreeze and Thaw Functionality: Project creators can now freeze and thaw cNFTs, providing greater control over their assets for various use cases such as preventing transfers during specific events or implementing vesting mechanics.\nMPL-Core Collections Integration: Bubblegum V2 NFTs can now be added to MPL-Core collections instead of being limited to token metadata collections, allowing for greater flexibility and integration with the broader Metaplex ecosystem.\nRoyalty Enforcement: Since Bubblegum V2 is using MPL-Core Collections, it is possible to enforce royalties on cNFTs e.g. using a ProgramDenyList.\nSoulbound NFTs: cNFTs can now be made soulbound (non-transferrable), permanently binding them to their owner's wallet. This is perfect for credentials, proof of attendance, identity verification, and more. It requires the PermanentFreezeDelegate plugin to be enabled on the collection.\nAllow Permanent Transfer: The permanent transfer delegate can now transfer the cNFT to a new owner without interaction of the leaf owner if the PermanentTransferDelegate plugin is enabled on the collection.\nHow do I find the arguments needed for operations such as transfer, delegate, burn, etc?\nWhenever we use an instruction that ends up replacing a leaf in the Bubblegum Tree — such as transfer, delegate, burn, etc. — the program requires a bunch of parameters that are used to ensure the current leaf is valid and can be updated. This is because the data of Compressed NFTs is not available inside onchain accounts and therefore additional parameters such as the Proof, the Leaf Index, the Nonce and more are required for the program to fill the pieces.\nAll of that information can be retrieved from the Metaplex DAS API using both the getAsset and the getAssetProof RPC methods. However, the RPC responses from these methods and the parameters expected by the instructions are not exactly the same and parsing from one to the other is not trivial.\nFortunately, our SDKs provide a helper method that will do all the heavy lifting for us, as we can see in the code examples below. It accepts the Asset ID of the Compressed NFT and returns a bunch of parameters that can be directly injected into instructions that replace the leaf — such as burn, transfer, update, etc.\nThat being said, if you ever needed to do that parsing yourself, here is a quick breakdown of the parameters expected by the instructions and how to retrieve them from the Metaplex DAS API. Here we will assume the result of the getAsset and getAssetProof RPC methods are accessible via the rpcAsset and rpcAssetProof variables respectively.\nLeaf Owner: Accessible via rpcAsset.ownership.owner.\nLeaf Delegate: Accessible via rpcAsset.ownership.delegate and should default to rpcAsset.ownership.owner when null.\nMerkle Tree: Accessible via rpcAsset.compression.tree or rpcAssetProof.tree_id.\nRoot: Accessible via rpcAssetProof.root.\nData Hash: Accessible via rpcAsset.compression.data_hash.\nCreator Hash: Accessible via rpcAsset.compression.creator_hash.\nNonce: Accessible via rpcAsset.compression.leaf_id.\nIndex: Accessible via rpcAssetProof.node_index - 2^max_depth where max_depth is the maximum depth of the tree and can be inferred from the length of the rpcAssetProof.proof array.\nProof: Accessible via rpcAssetProof.proof.\nMetadata: Currently needs to be reconstructed from various fields in the rpcAsset response.\nGet parameters for instructions that replace leaves\n\nThe Bubblegum Umi library provides a getAssetWithProof helper method that fits the description above. Here's an example of how to use it using the transfer instruction. Note that, in this case, we override the leafOwner parameter as it needs to be a Signer and assetWithProof gives us the owner as a Public Key.\nDepending on Canopy size it can make sense to use the truncateCanopy: true parameter of the getAssetWithProof helper. It fetches the tree config and truncates not required proofs. This will help if your transaction sizes grow too large.\nimport { getAssetWithProof, transfer } from '@metaplex-foundation/mpl-bubblegum'\n\nconst assetWithProof = await getAssetWithProof(umi, assetId,\n\n// { truncateCanopy: true } // optional to prune the proofs\n\n);\n\nawait transferV2(umi, {\n\n...assetWithProof,\n\nleafOwner: leafOwnerA, // As a signer.\n\nnewLeafOwner: leafOwnerB.publicKey,\n\n}).sendAndConfirm(umi);\n\nawait transferV2(umi, {\n\n...assetWithProof,\n\nleafOwner: leafOwnerA, // As a signer.\n\nnewLeafOwner: leafOwnerB.publicKey,\n\n}).sendAndConfirm(umi)\n\nHow to Resolve \"Transaction too large\" Errors\nWhen performing leaf-replacing operations like transfers or burns, you may encounter a \"Transaction too large\" error. To resolve this, consider the following solutions:\nUse the truncateCanopy option: Pass { truncateCanopy: true } to the getAssetWithProof function:\nconst assetWithProof = await getAssetWithProof(umi, assetId,\n\n{ truncateCanopy: true }\n\n);\n\nThis option retrieves the Merkle Tree configuration and optimizes the assetWithProof by removing unnecessary proofs based on the Canopy. While it adds an extra RPC call, it significantly reduces the transaction size.\n\nUtilize versioned transactions and Address Lookup Tables: Another approach is to implement versioned transactions and Address Lookup Tables. This method can help manage transaction size more effectively.\n\nBy applying these techniques, you can overcome transaction size limitations and successfully execute your operations.\nHow much does it cost to create a compressed NFT tree?\nTree costs depend on the configured depth and canopy. Here are some reference costs:\nTree CapacityDepthCanopyCost (SOL)Cost per cNFT\n16,384\n14\n8\n~0.34\n~0.00002\n\n1,048,576\n20\n13\n~8.50\n~0.00001\n\n16,777,216\n24\n15\n~26.12\n~0.000007\n\nThese costs are the one-time rent for the tree account. Once paid, minting cNFTs into the tree only costs transaction fees.\nWhat is the difference between Bubblegum V1 and V2?\nBubblegum V2 adds several new features compared to V1:\nFreeze/Thaw: Ability to freeze and thaw cNFTs via leaf delegates or permanent freeze delegates\nSoulbound NFTs: Make cNFTs non-transferable using the permanent freeze delegate\nMPL-Core Collections: Uses MPL-Core collections instead of Token Metadata collections\nRoyalty Enforcement: Enforced royalties via MPL-Core collection plugins\nPermanent Delegates: Permanent transfer, freeze, and burn delegates at the collection level\nLeafSchemaV2: New leaf format with collection hash, asset data hash, and flags\nV1 trees and V2 trees are not interchangeable. V2 trees require V2 instructions.\nDo I need a special RPC provider?\nYes. Compressed NFTs require an RPC provider that supports the Metaplex DAS API for indexing and fetching cNFT data. Not all RPCs support this extension. See the RPC Providers page for a list of compatible providers.\nCan I decompress a cNFT back to a regular NFT?\nDecompression is only available for Bubblegum V1 assets. Bubblegum V2 does not support decompression. V2 cNFTs remain compressed.\nHow many cNFTs can I store in one tree?\nThe maximum number of cNFTs is 2^maxDepth. A depth-14 tree holds 16,384 cNFTs, depth-20 holds ~1 million, depth-24 holds ~16 million, and depth-30 holds over 1 billion. See the tree capacity table for all options.\nCan a cNFT inherit royalties from its MPL-Core collection?\nYes. When minting into an MPL-Core collection that has the Royalties plugin, you can omit metadata.sellerFeeBasisPoints (or pass SELLER_FEE_BASIS_POINTS_INHERIT, 65535). The leaf stores that sentinel on-chain. DAS puts the collection-resolved rate on royalty.basis_points / creators for display, and the leaf sentinel on royalty.basis_points_raw / creators_raw (with royalty.inherited: true).\nRequirements:\nThe collection must have both the BubblegumV2 and Royalties plugins.\nmetadata.creators must be an empty array when using inherited seller fees.\nUsing getAssetWithProof:\nmetadata — mirrors DAS main / display fields (sellerFeeBasisPoints is the collection-resolved rate when inherited).\ncurrentMetadata — leaf-canonical MetadataArgsV2Args for write instructions (sentinel when inherited).\nsellerFeeBasisPointsRaw / creatorsRaw — optional leaf siblings; set when inherited / DAS provides _raw.\ninherited — sugar for inherit detection.\nrpcAsset — full DAS response (royalty.basis_points / creators for display).\nWhen calling updateMetadataV2, spread ...assetWithProof so currentMetadata is the leaf state. For instructions that take a leaf metadata arg, pass assetWithProof.currentMetadata.\nCollection management:\nA cNFT with inherited seller fees cannot be removed from its collection until you update to an explicit sellerFeeBasisPoints.\nMoving to another collection is allowed when the destination has the Royalties plugin.\nSee Reading Inherited Royalties for clients reading DAS, Minting — Inheriting royalties, Updating cNFTs, and Managing Collections for full examples.","tokens":2465,"crawled_at":1791195700215}
+{"id":10551,"url":"https://docs.ethena.fi/api-documentation/overview","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Overview | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nEthena’s API is used to mint and redeem USDe. In addition to the information on this page, interactive documentation is available here.\nWe offer the ability to stream indicative quotes, perform a formal RFQ and finally submitting of signed orders.\nOnly whitelisted users are able to successfully interact with the API interface. We recommend reaching out in our discord if you would like to be whitelisted.\nAddresses on Ethereum mainnet\nUSDe: 0x4c9EDD5852cd905f086C759E8383e09bff1E68B3\nEthena Mint and Redeem Smart Contract: 0xe3490297a08d6fC8Da46Edb7B6142E4F461b62D3\nThese addresses are the production USDe and minting contract. Care should be taken using them as real value will be transferred.\nMint & Redeem Smart Contract ABI\nServer location\nEthena's infrastructure is hosted on AWS Asia Pacific (Hong Kong) region, ap-east-1. Low latency with our infrastructure is necessary to algorithmically mint or redeem with Ethena as quotes are valid for limited time.\nConnection URLs\nWhitelisted users are able to use either https://public.api.ethena.fi\nSDKs\nThere are both Python and TypeScript SDKs available.\nApprovals Added to Whitelisted Addresses\nEnsure you have approved the Mint & Redeem Smart Contract for your whitelisted wallet addresses.\nPair Availability Endpoint\nThis endpoint returns the pairs available to directly mint & redeem with.\nNo parameters required\n\nOur response\nkey\nkey\nPossible values\nDescription\n\nmint\n\n[\"USDT/USDE\", \"USDC/USDE\"]\n\nThe available pairs to directly mint with.\n\nredeem\n\n[\"USDT/USDE\", \"USDC/USDE\"]\n\nExample request\nhttps://public.api.ethena.fi/asset-availability\nExample response\n\n{\n\"mint\": [\n\"USDC/USDE\",\n\"USDT/USDE\"\n],\n\"redeem\": [\n\"USDC/USDE\",\n\"USDT/USDE\"\n]\n}\n\nRFQ Request Endpoint\nCall the RFQ endpoint to receive a formal mint/redeem quote. Quotes are valid for 15 minutes upon us sending our response.\n\nYour request\nKey\nKey\nRequired\nPossible Values\nDescription\n\npair\n\ntrue\n\nUSDT/USDe, USDC/USDe\n\ncollateral/usde pairs we support\n\nside\n\ntrue\n\nmint,redeem\n\nsize\n\ntrue\n\n21.2918\n\nsize of asset you will send us. USDT for mint, USDe for redeem\n\nbenefactor\n\ntrue\n\n{benefactor_address}\n\nString of the ETH wallet address\n\nOur response\n\nKey\nPossible values\nDescription\n\nrfq_id\n\nRFQ-B7MT6QD2JKFFC\n\nUnique ID to be sent back to us when submitting order\n\npair\n\nUSDT/USDe, USDC/USDe\n\ncollateral/usde pairs we support\n\nside\n\nmint, redeem\n\nsize\n\ntrue1\n\nsize of asset you will send us. USDT for mint, USDe for redeem.\n\namount\n\n1552.2695\n\namount of asset you will receive, before gas. USDe for mint, USDT for redeem.\n\ncollateral_asset_address\n\n0xae7ab96520DE3A18E5e111B5EaAb095312D7fE84\n\nThe non-USDe asset in the transaction\n\nusde_address\n\n0x8191DC3053Fe4564c17694cB203663d3C07B8960\n\nAddress of USDe\n\ncollateral_amount\n\n1000000000000000000\n\nUse this value for EIP712 signature. For mints, this is the same as size but in 18 decimals. For redeems, this is amount minus gas converted to USDT in 18 decimals\n\nusde_amount\n\n1550198770000000000000\n\nUse this value for EIP712 signature. For redeems, this is the same as size but in 18 decimals. For mint, this is amount minus gas in 18 decimals\n\ngas\n\n2.070727513\n\nthe gas price of this tx in USD.\n\nExample mint RFQ request\nhttps://public.api.ethena.fi/rfq?pair=USDT%2FUSDe&side=MINT&size=100000&benefactor=0x0000000000000000000000000000000000000020\nResponse\n\n{\n\"amount\": \"99900.000\",\n\"collateral_amount\": \"100000000000\",\n\"collateral_asset_address\": \"0xdAC17F958D2ee523a2206206994597C13D831ec7\",\n\"gas\": \"32.490274776\",\n\"minting_contract_address\": \"0xe3490297a08d6fC8Da46Edb7B6142E4F461b62D3\",\n\"pair\": \"USDT/USDe\",\n\"rfq_id\": \"RFQ-P9Y4SVP5EZ8UW\",\n\"side\": \"MINT\",\n\"size\": \"100000\",\n\"usde_address\": \"0x4c9EDD5852cd905f086C759E8383e09bff1E68B3\",\n\"usde_amount\": \"99867509700000000000000\"\n}\n\nExample redeem RFQ request\nhttps://public.api.ethena.fi/rfq?pair=USDT%2FUSDe&side=REDEEM&size=100000&benefactor=0x0000000000000000000000000000000000000020\nResponse\n\n{\n\"amount\": \"99500.000\",\n\"collateral_amount\": \"100000000000\",\n\"collateral_asset_address\": \"0xdAC17F958D2ee523a2206206994597C13D831ec7\",\n\"gas\": \"30.890409055\",\n\"minting_contract_address\": \"0x8a39215693aaB95038727fB31EBe19ce18903885\",\n\"pair\": \"USDT/USDe\",\n\"rfq_id\": \"RFQ-Z0PHAGLVWZ0J5\",\n\"side\": \"MINT\",\n\"size\": \"100000\",\n\"usde_address\": \"0x2dFaF238B8255826A160432126E0BC5db20c33e9\",\n\"usde_amount\": \"99469109500000000000000\"\n}\n\nError Codes\n\nError Code\nHTTP Status Code\nMessage\n\n0\n\n400\n\nInvalid RFQ payload. Missing required fields.\n\n1\n\n400\n\nTemporarily unavailable\n\n2\n\n400\n\nCollateral asset not supported.\n\n3\n\n400\n\nPair is not supported.\n\n4\n\n400\n\nSide value is not supported.\n\n5\n\n400\n\nToo many significant figures for size value.\n\n6\n\n400\n\nSize can only include numbers.\n\n7\n\n400\n\nSize must be non zero and positive.\n\n8\n\n400\n\nSize must be enough to cover the incurred gas cost.\n\n9\n\n400\n\nSize exceeds Ethena set capacity per block.\n\n10\n\n400\n\nWallet address not whitelisted. Please contact Ethena.\n\n11\n\n400\n\nInsufficient collateral asset in wallet.\n\n12\n\n400\n\nInsufficient collateral asset approval for Ethena to transfer.\n\n13\n\n400\n\nInsufficient USDe balance in wallet.\n\n14\n\n400\n\nInsufficient USDe approval for Ethena to transfer.\n\n15\n\n400\n\nAsset currently not active\n\n16\n\n400\n\nType_ value is not supported.\n\nFees Endpoint\nCall the Fees endpoint to retrieve the fee schedule. The endpoint returns the applicable fees (in basis points) for each supported token.\nYour Request\nKey\nType\nRequired\nDescription\n\nbenefactor\n\nstring\n\nYes\n\nThe Ethereum wallet address to check fees for. Must be a valid checksummed address.\n\nOur Response\nKey\nType\nDescription\n\nbenefactor\n\nstring\n\nThe checksummed Ethereum address that was queried.\n\nfees\n\narray\n\nArray of fee objects for each supported token.\n\nfees[].token\n\nstring\n\nThe token symbol (e.g., \"USDT\", \"USDC\").\n\nfees[].fee_bps\n\nfloat\n\nThe fee in basis points (1 bps = 0.01%). NOTE: this field is deprecated and will be removed in a future release.\n\nfees[].mint_fee_bps\n\nfloat\n\nThe fee in basis points (1 bps = 0.01%).\n\nfees[].redeem_fee_bps\n\nfloat\n\nThe fee in basis points (1 bps = 0.01%).\n\nExample Request\n\nGET https://public.api.ethena.fi/fees?benefactor=0x0000000000000000000000000000000000000020\n\nExample Response\n\n{\n\"benefactor\": \"0x0000000000000000000000000000000000000020\",\n\"fees\": [\n{\n\"token\": \"USDT\",\n\"fee_bps\": 10.0,\n\"mint_fee_bps\": 10.0,\n\"redeem_fee_bps\": 10.0\n},\n{\n\"token\": \"USDC\",\n\"fee_bps\": 10,\n\"mint_fee_bps\": 10.0,\n\"redeem_fee_bps\": 10.0\n},\n{\n\"token\": \"DAI\",\n\"fee_bps\": 15,\n\"mint_fee_bps\": 15.0,\n\"redeem_fee_bps\": 10.0\n}\n]\n}\n\nFee Calculation\n\nFees are expressed in basis points (bps), where 1 bps = 0.01%\n\nFor example, a fee of 10 bps means a 0.10% fee will be applied\n\nDifferent tokens may have different fee rates\n\nError Codes\nError Code\nError Name\nHTTP Status\nDescription\n\n1\n\nTemporarily unavailable, please try again.\n\n400\n\nNo fee data is currently available, or there was an error retrieving fees. Please retry your request.\n\n29\n\nInvalid payload\n\n400\n\nThe benefactor parameter is missing or the provided address is not a valid Ethereum address.\n\nOrders Submission Endpoint\nAfter receiving the RFQ response, if you wish to execute the order as quoted, sign an EIP-712 signature using the usde_amount and collateral_amount values. Our system only accepts orders with matching values for the 2 fields, and if the order is submitted and received within 15 minutes of our previous RFQ response.\nThe order process has no interaction with the smart contracts as Ethena receives your orders, passes them through checks, then submits the order onchain.\nFor EIP-1271 users, you must add the signature_type parameter with the value EIP1271 to the request. The default is EIP712 so the former is only required if you're using EIP-1271.\nurl = {ethena_url}order?signature={signature_hex}&signature_type=EIP1271\nExample payload\nkey\n\nvalue\n\nDescription\n\nsignature\n\n0xf80a44c799d13f257fa25459a9e2d36dadfea48a78f699de3f09fc3009a0e92d63b51ce85003c95cd7f4b80c271659092b898192d83fcd0dc1e3aae7483d59931b\n\nResulting signature from signing the order\n\norder\n\nSee EIP712 signature ORDER_TYPE below\n\nThe order in plain json that they used to sign and create the signature\n\ncurl -d '{ \"order_id\": \"RFQ-N9Y9T2Z6MXFNS\", \"benefactor\": \"0x0000000000000000000000000000000000000020\", \"beneficiary\": \"0x0000000000000000000000000000000000000020\", \"collateral_amount\": \"8995495840000\", \"collateral_asset\": \"0xdAC17F958D2ee523a2206206994597C13D831ec7\", \"expiry\": 1764067729, \"nonce\": 1727791471438686, \"order_type\": \"MINT\", \"usde_amount\": \"8999996000000000000000000\" }' -H \"Content-Type: application/json\" -X POST \"https://public.api.ethena.fi/order?signature=0xd7c436757d3b7f6fc0c7a3adb2a68d7b48a4bbf08daff521629e0a081466e15f0b8a08bab0a67e90d9d2e0307e021b2530abea5c71b36ba21a2982a6f5d855e31c\"\n\nResponse\n\n{\n\"tx\":\"0xbf4d5dce0e482b7cfd3e0ac714a0bb1b67d2c777668048e257b7fd3e9fb68980\"\n}\n\nThe tx that went onchain\nhttps://etherscan.io/tx/0xbf4d5dce0e482b7cfd3e0ac714a0bb1b67d2c777668048e257b7fd3e9fb68980\nEIP712 signature ORDER_TYPE\nbytes32 private constant ORDER_TYPE = keccak256( \"Order(string order_id, uint8 order_type, uint256 expiry, uint256 nonce, address benefactor, address beneficiary, address collateral_asset, uint256 collateral_amount, uint256 usde_amount)\" );\nComment\n\norder key\n\nvalues\n\nNotes\n\norder_id\n\nRFQ-N9Y9T2Z6MXFNS\n\nUnique identifier returned in the RFQ endpoint response. This ID must be included when submitting the order.\n\norder_type\n\n0 or 1\n\n0 for mint, 1 for redeem\n\nexpiry\n\n1764067729\n\nUse an expiry of current time + 45s\n\nnonce\n\n256\n\nUse a unique int for each order. eg timestamp\n\nbenefactor\n\n0x0000000000000000000000000000000000000020\n\nAddress of signer. address where the asset is taken from (USDT for mint, USDe for redeem)\n\nbeneficiary\n\n0x0000000000000000000000000000000000000020\n\nAddress that receives funds. (USDe for mint, USDT for redeem).\n\ncollateral_asset\n\n0xdAC17F958D2ee523a2206206994597C13D831ec7\n\nUSDT address\n\ncollateral_amount\n\n8995495840000\n\nAmount of USDT in 18 decimals. Use the exact value provided in RFQ\n\nusde_amount\n\n8999996000000000000000000\n\nAmount of USDe in 18 decimals. Use the exact value provided in RFQ\n\nExample raw order (before signing)\n\n{\n\"order_id\": \"RFQ-N9Y9T2Z6MXFNS\"\n\"benefactor\":\"0x0000000000000000000000000000000000000020\",\n\"beneficiary\":\"0x0000000000000000000000000000000000000020\",\n\"collateral_amount\":\"8995495840000\",\n\"collateral_asset\":\"0xdAC17F958D2ee523a2206206994597C13D831ec7\",\n\"expiry\":1764067729,\n\"nonce\":1727791471438686,\n\"order_type\":\"MINT\",\n\"usde_amount\":\"8999996000000000000000000\"\n}\n\nOur response\nWe will either respond with a tx hash, where your order passed our checks and is sent to the blockchain or a failure message with a reason for failure.\nThe most common failure reasons include an invalid EIP-712 signature, submitting an order after the quote has expired or not having sufficient assets in your address for the mint or redeem.\nOne Order per RFQ\nEach RFQ is single-use. Once an RFQ id has been used to execute an order, it is consumed and cannot be reused — even if you re-sign the quote with a new nonce or expiry. Submitting a second order against a consumed RFQ is rejected with 409 Conflict (error code 37).\nError Codes\n\nError Code\nHTTP Status Code\nMessage\n\n1\n\n400\n\nTemporarily unavailable\n\n10\n\n400\n\nWallet address not whitelisted. Please contact Ethena.\n\n11\n\n400\n\nInsufficient collateral asset in wallet.\n\n12\n\n400\n\nInsufficient collateral asset approval for Ethena to transfer.\n\n13\n\n400\n\nInsufficient usde balance in wallet.\n\n14\n\n400\n\nInsufficient usde approval for Ethena to transfer.\n\n15\n\n400\n\nInvalid signature.\n\n16\n\n400\n\nOrder payload invalid or does not match RFQ.\n\n17\n\n400\n\nSize greater than available capacity for this block.\n\n18\n\n400\n\nRFQ expired.\n\n19\n\n400\n\nInvalid RFQ.\n\n20\n\n400\n\nPlease try again. The market moved too much.\n\n21\n\n400\n\nExecution request already being processed.\n\n22\n\n400\n\nAlready successfully executed this block.\n\n23\n\n400\n\nPresent time greater than order expiry. Execution not submitted to blockchain.\n\n24\n\n400\n\nDuplicate nonce\n\n25\n\n400\n\nBenefactor not whitelisted\n\n26\n\n400\n\nBeneficiary not whitelisted. User on-chain transaction required.\n\n27\n\n400\n\nIncorrect USDe minter. Switch Minting API\n\n28\n\n429\n\nBenefactor has reached throttle limit. Please wait until the limit resets or contact support for assistance.\n\n29\n\n400\n\nInvalid payload\n\n30\n\n400\n\nInvalid address\n\n31\n\n400\n\nFees not applicable\n\n32\n\n400\n\nSlippage is too high for delegate-signed order\n\n33\n\n400\n\nNo pricing source found for validating asset price with alternative source\n\n34\n\n400\n\nInsufficient minting contract balance\n\n35\n\n404\n\nOrder not found. Please verify the order ID is correct.\n\n36\n\n202\n\nOrder submitted but transaction not yet mined. Please wait and try again.\n\n37\n\n409\n\nThis RFQ has already been used to execute an order. Each RFQ is single-use — please request a new quote.\n\nOrder Confirmation Endpoint\nAfter submitting an order, you can check its execution status using the order confirmation endpoint. This is useful for:\n\nConfirming your order was executed on-chain\n\nChecking if a transaction is still pending\n\nUnderstanding why an order was rejected before execution\n\nYour request\nKey\nRequired\nPossible Values\nDescription\n\norder_id\n\ntrue\n\nRFQ-ABC123XYZ4567\n\nThe RFQ ID returned from the RFQ endpoint. Case-insensitive.\n\nNote: The order_id can be provided with or without the RFQ- prefix. Both RFQ-ABC123XYZ4567 and ABC123XYZ4567 are accepted and normalized to uppercase.\nExample request\nhttps://public.api.ethena.fi/order-confirmation?order_id=RFQ-ABC123XYZ4567\nOur response\nThe response varies based on the order status:\nStatus\nHTTP Code\nDescription\n\nexecuted\n\n200\n\nOrder was successfully executed on-chain\n\nreverted\n\n200\n\nOrder was submitted but reverted on-chain\n\npending\n\n202\n\nOrder submitted but transaction not yet mined\n\nrejected\n\n400\n\nOrder failed validation and was not submitted to blockchain\n\nnot_found\n\n404\n\nNo order found with this ID\n\nExample response: Executed order\n\n{\n\"order_id\": \"RFQ-ABC123XYZ4567\",\n\"tx_hash\": \"0xbf4d5dce0e482b7cfd3e0ac714a0bb1b67d2c777668048e257b7fd3e9fb68980\",\n\"status\": \"executed\",\n\"etherscan_link\": \"https://etherscan.io/tx/0xbf4d5dce0e482b7cfd3e0ac714a0bb1b67d2c777668048e257b7fd3e9fb68980\"\n}\n\nExample response: Pending order\n\n{\n\"error\": {\n\"error_name\": \"Order submitted but transaction not yet mined. Please wait and try again.\",\n\"error_code\": \"36\"\n},\n\"order_id\": \"RFQ-ABC123XYZ4567\",\n\"tx_hash\": \"0xbf4d5dce0e482b7cfd3e0ac714a0bb1b67d2c777668048e257b7fd3e9fb68980\",\n\"status\": \"pending\",\n\"etherscan_link\": \"https://etherscan.io/tx/0xbf4d5dce0e482b7cfd3e0ac714a0bb1b67d2c777668048e257b7fd3e9fb68980\"\n}\n\nExample response: Rejected order (failed validation)\n\n{\n\"error\": {\n\"error_name\": \"Insufficient collateral asset in wallet.\",\n\"error_code\": \"11\"\n},\n\"order_id\": \"RFQ-ABC123XYZ4567\",\n\"status\": \"rejected\"\n}\n\nExample response: Order not found\n\n{\n\"error\": {\n\"error_name\": \"Order not found. Please verify the order ID is correct.\",\n\"error_code\": \"35\"\n},\n\"order_id\": \"RFQ-NOTFOUND12345\",\n\"status\": \"not_found\"\n}\n\nExample response: Invalid order_id format\nHTTP Status: 400\n\n{\n\"error\": \"Order ID is malformed or incorrect. Expected format: RFQ-XXXXXXXXXXXXX\",\n\"order_id\": \"INVALID\"\n}\n\nError Codes\nError Code\nHTTP Status Code\nMessage\n\n1\n\n400\n\nTemporarily unavailable\n\n29\n\n400\n\nInvalid payload (missing order_id)\n\n35\n\n404\n\nOrder not found. Please verify the order ID is correct.\n\n36\n\n202\n\nOrder submitted but transaction not yet mined. Please wait and try again.\n\nRecommended Polling Strategy\nFor programmatic usage, we recommend:\n\nAfter submitting an order, wait 5-10 seconds before first poll\n\nPoll the endpoint every 5 seconds\n\nStop polling when status is executed, reverted, or rejected\n\nTimeout after 5 minutes if order remains pending\n\nLast updated 3 months ago\nWas this helpful?","tokens":3959,"crawled_at":1791195700506}
+{"id":10552,"url":"https://docs.sui.io/getting-started/sui-for-ethereum","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Ethereum -> Sui | Sui Documentation","text":"If you have worked with Ethereum Virtual Machine (EVM) before, the biggest difference when developing on Sui is the programming language. Sui uses MoveMoveAn open source programming language used for all activity on Sui. and EVM uses Solidity.\n\nTopicSolidityMove\nAccount vs objectObjectThe basic unit of storage on Sui.-centric models\nCustom ownership logic written within contracts typically using mappings. Only Ethereum coins are first class citizens with global APIs. All ownership APIs are contract specific.\nObject ownership inherent to Sui, objects are first class citizens and encompass everything owned on Sui.\n\nData storage\nData is stored in the smart contract.\nData is stored in Move objects.\n\nInheritance\nSupports multiple inheritance, including polymorphism.\nNo interfaces, no polymorphism. However, Move has generics, like Type<T>.\n\nDynamic dispatch\nAllowed\nNot allowed\n\nAsset/Token accessibility\nBound to smart contract.\nAnyone can access shared objects. Owned objects can only be accessed by object owner.\n\nAccess control\nIdentity/role-based access control through Ownable and AccessControl contract.\nMostly capability based access control through owned objects. Identity/role-based access control is possible.\n\nContract upgrades\nProxy contract forwards user transactions.\nNew contracts must be layout-compatible with the old one. Need to consider versioning shared objects.\n\nDevelopment environment\nHardhat, Foundry\nMove VSCode extension.\n\nMutate contract state\nSending transactions through compile time ABI interface.\nSending transactionTransactionA number of commands that execute on inputs to define the result of the transaction. through runtime programmable transaction block (PTBProgrammable transaction blocksDefine all user transactions on Sui.) construction.\n\nObject model​\n\nObjects store data in Move and everything in Move is an object. This includes the smart contracts (Move packagesPackageSmart contracts on Sui.), onchain addressesAddressA unique, anonymous identity on a blockchain network., coins, and NFTs.\n\nFor simplicity, you can think of objects as assets or NFTs. Objects have ownership.\n\nOwnership​\n\nThere are some nuances to object ownership, but key types include:\n\nAddress-owned objects: These objects are owned by a single address. You can transferTransferChanging the owner of an asset. or receive these objects without interacting with a smart contract. For example, currency, NFTs, or tokens gating access to certain functions.\n\nShared objects: Publicly accessible objects that anyone can use. Mutating the data stored in these objects typically involves defining rules in the smart contract.\n\nFor all types of ownership on Sui, see Object Ownership.\n\nAccess control​\n\nIdentity or role-based access control is widely used through OpenZeppelin's Ownable and AccessControl contracts in Solidity.\n\nBecause object ownership is inherent in Sui, access to contract functions is typically gated through capability objects.\n\nYou issue these objects to users, granting them the rights to call certain functions. Function calls fail if a user does not own the object a function expects.\n\nYou can still implement address-based checks. However, the recommendation is to use capability objects as much as possible for better security.\n\nYou can read more in The Move Book.\n\nIn this example, a new user can only be created by presenting an AdminCap object during the function call.\n\n/// Grants the owner the right to create new users in the system.\npublic struct AdminCap has key { id: UID }\n\n/// Creates a new user in the system. Requires the `AdminCap` capability to be\n/// passed as the first argument.\npublic fun new(_: &AdminCap, ctx: &mut TxContext): User {\nUser { id: object::new(ctx) }\n}\n\nMutating objects​\n\nIn Solidity, data structures such as Mapping are defined and stored in a contract. Mutating the data involves signing a transaction regardless of whether the signer owns the data or not.\n\nIn Move, the logic that mutates the data is defined in the contract, but the data is stored in Move objects.\n\nTo mutate the data, the owner of the objects calls the contract functions using a PTB. The protocol checks ownership at the protocol level, so transactions fail if the signer does not have access to the referenced objects.\n\nProgrammable transaction blocks​\n\nIn Solidity, if you want to chain together the results of multiple contract calls or calls across different contracts, you need a function in the smart contract that composes other function calls. The client side does not support chaining function calls with atomicity guarantees.\n\nIn Move, PTBs solve this problem. PTBs give builders the ability to chain contract calls together with atomicity guarantees during runtime. A Sui PTB can have up to 1,024 different contract calls in it, or other actions. PTBs effectively provide a limited scripting language that is straightforward yet expressive, powerful, and secure.\n\nBuilders on Sui leverage PTBs to provide experiences that would otherwise be intractable. A good example is a DeFi aggregator that routes token swaps across multiple DeFi protocols with the best price. On Sui, the aggregator would use a single PTB with the guarantee that the transaction would execute at the displayed price or it would revert completely. The PTB is one of the most powerful Sui features. Experience shows builders who are most successful on Sui are the ones who learn to leverage this feature early and often, leaning into it rather than treating it just as a way to batch transactions.\n\nSee Building Programmable Transaction Blocks for the full guide on constructing PTBs with the TypeScript SDK, including moveCall, chaining results, and gasGasThe computational cost of execution and object storage for a transaction. management.\n\nMore comparison​\n\nTopicSuiEthereum\nDigital signature algorithm\nEd25519, secp256k1, secp256r1\nsecp256k1\n\nConsensusConsensusThe process by which the majority of nodes agree on the current state of the network mechanism\nDPoSDPoSConsensus mechanism used by Sui.\nPoS\n\nVM and its languages\nMoveVM, Move Lang\nEVM, Solidity, Vyper\n\nChain data structure\nDAG\nBlocks\n\nCommon standards (coin, token, NFT, and so on)\nCurrency Standard, Closed-Loop TokenClosed-Loop TokenA token that can be used only for a specific service or authorized account.\nERC-20, ERC-721, ERC-1155\n\nCoin names, name of the smallest unit\nSUI, MISTMISTThe smallest unit of SUI.\nETH, Wei\n\nAvailable frameworks for development\nSui CLI\nFoundry, Hardhat\n\nL1/L2\nNo L2, relies on fast L1\nMany L2s\n\nGovernance\nOnchain governance\nEIP + Node Operator consensus\n\nBridges\nSupported\nSupported\n\nNetwork security (stake required for control)\n66% of total stake\n51% of total stake\n\nSmart contract auditing\nLess auditing required, language does some of the lifting (object model).\nSolidity provides less protection requiring greater auditing.\n\nPrivate transactions\nPublic by design.\nPublic by design. L2 and third party support private transactions.\n\nTVL\n~1 billion\n~46 billion\n\nImplementation languages for clients\nRust, TypeScript\nMany\n\nEventing\nIndexed by sender, object ID, type, timestamp.\nIndexed by topic.\n\nIndexing\nHigh level transaction data + objects, coins, and so on.\nHigh level transaction data.\n\nOracles\nThird party\nThird party\n\nNetwork upgrade strategy\nProtocol flags and framework upgrades are voted on by validators then enabled.\nEIPs + Hardforking, no onchain mechanism.\n\nIDE\nVSCode\nMany\n\nTransaction lifecycle\nThe client submits the transaction to a full nodeFull nodeResponsible for validating blockchain activity., which forwards it to a validatorValidatorResponsible for executing tasks like staking, gas price references, and tallying rules. through Transaction Driver. Validators vote on it, consensus commits it in a block, and every validator executes it against the same ordered state. Low latency.\nThe network gossips the transaction, verifies it, and adds it to the mempool. Validators select transactions from the mempool. A random validator proposes a block, and the other validators vote on it. After enough blocks pass, the network considers a transaction final. High latency, because finalityFinalityThe state in which a transaction is permanently recorded and cannot be revoked. depends on block height.\n\nParallel execution vs Ethereum serial execution, fast path\nTransactions that can be parallel are run in parallel.\nEvery transaction is sequentially run.\n\nStorage fees, storage rebates, storage accounts to pay for fees over time\nLow, rebates on destroying objects.\nHigh, no rebates.\n\nContract immutability\nNative mutable and immutable support using upgrade capabilities.\nNot native, requires auditing the Solidity code deployed. Can be discerned by some operation codes.\n\nContract upgrading\nNative, upgrade capability mediated.\nAchieved using proxy pattern to delegate calls. Upgrades change where calls are directed to.\n\nComposability\nCall any number of functions within a single transaction using PTBs. Compose by taking the output of one contract call and passing it into another. Ensures atomic execution.\nEach call is its own transaction that must be processed individually and serialized by the chain. Requires careful publishing to ensure execution. Not atomic.\n\nToken royalties\nEnforced by the chain.\nOnly enforceable by marketplaces.\n\nRelated topics\n\nUpgrading Packages\nUpgrade a published Move package on Sui using the Sui CLI, understand layout-compatibility requirements, manage UpgradeCap and UpgradeTicket, and apply custom upgrade policies to control what changes are permitted.\nWhat is a PTB?\nProgrammable transaction blocks are a group of commands that complete a transaction on Sui.\nBuilding Transactions\nUsing the Sui TypeScript SDK, you can create programmable transaction blocks to perform multiple commands in a single transaction.\nTypes of Object Ownership\n\nObject model\nOwnership\nAccess control\nMutating objects\nProgrammable transaction blocks\nMore comparison\n\nWas this page helpful?","tokens":2491,"crawled_at":1791195714944}
+{"id":10553,"url":"https://gov.uniswap.org/latest?no_definitions=true&page=2","domain":"gov.uniswap.org","chapter":"governance_daos","title":"Uniswap Governance - Uniswap is a fully decentralized protocol for automated liquidity provision on Ethereum.","text":"Topic\n\nReplies\nViews\nActivity\n\n404 DAO Delegate Platform\n\nDelegation Pitch\n\n39\n\n3283\n\nJanuary 13, 2026\n\nDelegate Platform: Ezekiel Ekondu — Community-First, Transparent & Long-Term Governance\n\nDelegation Pitch\n\n0\n\n101\n\nJanuary 12, 2026\n\nStableLab Delegate Platform\n\nDelegation Pitch\n\n103\n\n8892\n\nDecember 30, 2025\n\nGauntlet Delegate Platform\n\nDelegation Pitch\n\n41\n\n2415\n\nDecember 29, 2025\n\nUniswap Foundation 990 filing\n\nGovernance-Meta\n\n0\n\n194\n\nDecember 23, 2025\n\nStrategic Renewal for Support of Uniswap v3 Deployments\n\nRequests for Comment\n\n10\n\n975\n\nDecember 23, 2025\n\nProxy (prev Boardroom) Delegate Platform\n\nDelegation Pitch\n\n26\n\n827\n\nDecember 20, 2025\n\nFoundation Feedback Group (FFG) Thread\n\nGovernance-Meta\n\n20\n\n2282\n\nDecember 17, 2025\n\n[RFC] Deploy Uniswap V3 on XDC Network\n\nRequests for Comment\n\n3\n\n317\n\nDecember 17, 2025\n\n[RFC] - Deploy Uniswap V3 on Redbelly Network\n\nRequests for Comment\n\n2\n\n226\n\nDecember 17, 2025\n\nOfficial Uniswap v3 Deployments List\n\nGovernance-Meta\n\n10\n\n4366\n\nDecember 17, 2025\n\nUniswap Delegate Dashboard by CuriaLab\n\nRequests for Comment\n\n0\n\n419\n\nDecember 17, 2025\n\nUniswap Ecosystems Incentives Initiative (UEII) Update Thread\n\nGovernance-Meta\n\n29\n\n1854\n\nDecember 9, 2025\n\nGFX Labs - Delegate Communication Thread\n\nDelegation Pitch\n\n27\n\n1504\n\nDecember 8, 2025\n\nDhive Communication Thread\n\nGovernance-Meta\n\n11\n\n309\n\nDecember 4, 2025\n\nUniswap Delegate Rewards\n\nGovernance-Meta\n\n18\n\n1712\n\nDecember 3, 2025\n\nUniswap Foundation: Summary Q3’2025 Financials\n\nUncategorized\n\n2\n\n739\n\nDecember 2, 2025\n\nAvantgarde Finance Delegate Platform\n\nDelegation Pitch\n\n32\n\n1063\n\nNovember 27, 2025\n\nGrow Uniswap on Plasma\n\nRequests for Comment\n\n5\n\n809\n\nNovember 20, 2025\n\n[RFC] Flow Application for Canonical Uniswap V3 Deployment\n\nUncategorized\n\n1\n\n258\n\nNovember 14, 2025\n\nL2BEAT Delegate Platform\n\nDelegation Pitch\n\n21\n\n2920\n\nNovember 12, 2025\n\nUniswap Community Proposal Factory\n\nRequests for Comment\n\n13\n\n765\n\nNovember 11, 2025\n\n[RFC] Deploying Uniswap v3 on Ronin with Co-Incentives\n\nRequests for Comment\n\n1\n\n663\n\nNovember 10, 2025\n\nAudit of Uniswap Grants\n\nGovernance-Meta\n\n0\n\n138\n\nNovember 7, 2025\n\nBOR4 Delegate Platform\n\nDelegation Pitch\n\n0\n\n128\n\nNovember 1, 2025\n\nMichigan Blockchain Delegate Platform\n\nDelegation Pitch\n\n20\n\n2303\n\nOctober 17, 2025\n\nGLI -- Treasury Delegation Round 2 Applications\n\nGovernance-Meta\n\n15\n\n698\n\nOctober 6, 2025\n\n[RFC] Governance Logistics Improvements\n\nRequests for Comment\n\n39\n\n2257\n\nOctober 2, 2025\n\nScaling V4 and Supporting Unichain\n\nRequests for Comment\n\n52\n\n3333\n\nSeptember 29, 2025\n\nDonOfDAOs Delegate Platform\n\nDelegation Pitch\n\n3\n\n173\n\nSeptember 25, 2025\n\n← previous page\nnext page →","tokens":662,"crawled_at":1791195716982}
+{"id":10554,"url":"https://docs.ethena.fi/resources/faq","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"FAQ | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nOur FAQ aims to answer every question we've been asked on Ethena and USDe.\nLink to the full FAQ here.\nEthena FAQs | Notionethena on Notion\nGeneral Questions\nCan anyone mint/redeem USDe?\nAll addresses will need to be whitelisted by the Ethena Protocol after satisfying KYC/AML checks. US users are not able to access the application. Feel free to reach out in our Telegram or Discord for help onboarding.\nPeg Stability\nHow is stability supported?\nUSDe's peg stability is supported through the protocol immediately hedging the delta of protocol backing assets. This aims to protect the underlying backing supporting USDe from significant variance in \"USD\" equivalent value under volatile market conditions or price action.\nSecurity & Safety of Protocol Backing\nHow is protocol backing kept safe from hacks or exchange failures?\nProtocol backing is held solely in audited smart contracts as well as regulated & licensed custodians and MPC wallet providers. The custodian and MPC wallet provider partners have the highest possible security and are used by all institutional participants in the space. The use of custodians and MPC wallet providers also enables the system to custody funds off-exchange, but to still have funds available on the exchanges to collateralize the delta hedging derivatives positions. In the event of an exchange failure, the funds are NOT expected to be locked or party to the bankruptcy and Ethena should retain control to support all mint & redeem requests of USDe on demand.\nWhy doesn't the protocol just hold assets with the exchanges?\nHolding protocol backing with exchanges exposes the protocol to risks if an exchange were to limit/delay withdrawals or were to close suddenly like FTX. The ability to use off-exchange custody providers enables Ethena to enjoy the benefits of a disintermediation of incentives as well as the availability of backed assets to trade on the most liquid markets.\n\nRewards Explanation\nThe protocol shares rewards with certain users, how is that received?\nThe protocol-level revenue Ethena generates come from three different sources:\n\nStaked ETH yield\n\nPerpetual Futures Funding Rates or Expiry Futures Basis\n\nFixed rewards on Liquid Stables\n\nOn the backing asset side, staked Ethereum backing USDe will offer rewards that are currently around 3-4%. The delta hedged derivative positions offsetting the backing assets can also earn income on both perpetual futures funding rates and the basis on dated futures. Lastly, the rewards from liquid stables held by the protocol are in line with the TradFi risk free rate.\nBasis refers to the difference between the spot price of an asset and the price of the corresponding expiring futures contract. More on basis trades here.\nFunding Rates are periodic payments made to traders who are long or short depending on the difference between spot prices and perpetual contract markets. Consequently, traders will either pay or get funding based on open positions depending on demand for long or short positions. When the funding rate is positive, long positions pay shorts; when it is negative, short positions pay those long the contract. This mechanism ensures avoiding long-term divergence in the prices of the two markets.\nBoth dated futures basis and perpetual funding rates have, on average, returned a yield to the short side of c.6-7% over the last 3 years, leading to an excess return over staked Ethereum and liquid stables holdings.\nThese protocol level rewards are variable, transparent, sustainable, and partially distributed to users (net of revenue that accrues to the reserve fund) according to the staking mechanism.\nPerpetual Futures\nAren't perpetual futures funding rates volatile?\nPerpetual futures funding rates have two primary components: the interest rate and the premium. The venue determines how funding rates are calculated. Funding rates may exhibit sharp behavior during times of market volatility, they may go negative for significant periods but usually revert closer to zero or positive and display mean-reverting characteristics.\n\nHistorically, long positions have paid the funding rate to the short side, which on average are expected to provide Ethena with an excess return over rewards from ETH staking and liquid stables holdings. The table below summarizes the distribution of funding rates since inception. We can see that the mean for annualized open interest-weighted funding rates is 9.03% for ETH and 7.79% for BTC.\n\nHow does this affect the combined protocol yield?\nCombining the different income sources gives the system an excess return, which is broken down below for each perpetual future contract per quarter. Q3 2022 was the only quarter with a negative excess return on some exchanges thanks to an arbitrage opportunity related to the ETH Proof of Work token airdrop post-Merge.\n\nThere are \"Quick Answers\" available throughout the documentation as well.\nWe would love to answer any unanswered questions. Join us in Telegram & Discord.\n\nLast updated 1 month ago\nWas this helpful?","tokens":1280,"crawled_at":1791195719639}
+{"id":10555,"url":"https://a16zcrypto.com/posts/article/news-you-can-use-early-feb-2026","domain":"a16zcrypto.com","chapter":"research","title":"News you can use: Hot topics, fact checks, trends, industry moves - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nNews you can use: Hot topics, fact checks, trends, industry moves\na16z crypto editorial\n02.13.26\n\nTags & Share Tags\nannouncements & news\nTradFi\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nWe sift through the news so you don’t have to\n\nEditor’s note: In this regular news segment, we focus on the signal vs. the noise across various media sources — traditional media outlets, industry announcements, and debates online — to help you stay on top of what’s going on and why it matters. Be sure to also subscribe to our weekly newsletter if you haven’t already (or share it with others to subscribe!); and also check out the policy team’s regulatory updates as well.\n\nHot topics & fact checks\n\nAre non-financial use cases for crypto dead?\n\n“It’s fashionable right now to declare that ‘non-financial use cases of crypto are dead.’ Some people also claim that read write own has failed. These conclusions misunderstand both the thesis and the stage we’re in. We are clearly in the financial era of blockchains. But the core idea was never that every crypto application would emerge all at once, or that finance wouldn’t come first. The core idea was — and remains — that blockchains introduce a new primitive: the ability to coordinate people and capital at internet scale, with ownership embedded directly into the system. (And increasingly, to coordinate AI agents too.)” Chris Dixon’s article last week on the long game for crypto continues to garner discussion and debate.\n\nWhen you’re building networks and not just traditional companies/ businesses…\n\nResponding to a post on “why tokens can’t compound” — arguing crypto is about the power law of timing vs the power law of compounding — a16z crypto general partner Ali Yahya argues that the writer misses one of the most powerful drivers of exponential growth — network effects. He outlines what makes tokens valuable:\n\nThis ignores one of the most powerful drivers of exponential growth — network effects.\n\nHere’s what makes tokens valuable:\n\n1. A well designed protocol grows exponentially because of a flywheel between investors, infra providers, developers, and users.\n\n2. The protocol captures… https://t.co/ZI6gOKeUdm pic.twitter.com/PUM3qFjMCu\n\n— Ali Yahya (@alive_eth) February 8, 2026\n\nAnother key difference that a16z crypto CTO Eddy Lazzarin adds is that protocols have more flexibility than corporations:\n\nCorporations need to use fees or fundraises for growth\n\nProtocols can issue tokens, and can even use these to pay for their operating costs\n\n“The mint+burn dynamic decouples incoming fees from outgoing investment into the business investment (subject to inflation). Protocols can use fees to burn tokens (to limit inflation) and can separately mint new network tokens to reinvest in the business. These two functions can be completely decoupled.”\n\nNews & moves\n\nTradFi continues to embrace and adopt crypto… plus, a new bank this way comes\n\nBlackRock revealed this week that it was bringing its Treasury-backed digital token onto DeFi platform Uniswap, reflecting “a major vote of confidence in DeFi by one of the finance industry’s most influential firms” according to Fortune. This collaboration — which was in the works for over a year — between traditional finance and decentralized finance uses Uniswap’s market structure to power onchain trading for the BlackRock token, settled on Ethereum.\n\nErebor Bank, co-founded by Anduril co-founder and Oculus architect Palmer Luckey, received its national charter from the Office of the Comptroller of the Currency (OCC) last week, who shared that the approval reflects OCC’s “commitment to a dynamic and diverse financial system that remains innovative and relevant over time.” The bank plans to integrate blockchain technologies to settle transactions 24/7. It is also reported to be building products “designed for a clientele most banks don’t know how to serve” – including loans to finance AI/ GPU chips; underwriting for defense contractors, robotics firms, and other builders whose collateral “doesn’t fit neatly into traditional risk models”.\n\nLuckey spoke to us about why this bank last year, here.\n\nEarlier this year, the CFTC (Commodity Futures Trading Commission) had previously launched its Innovation Advisory Committee (renamed from the former Technology Advisory Committee) with the goal of gathering “expertise and recommendations on innovation in financial markets”. This week, the 35 committee members — including a16z crypto founding and managing partner Chris Dixon — were announced.\n\nLayerZero, which last week announced its new chain Zero “designed to meet the needs of Wall Street” (as reported by Fortune), announced several new traditional finance partners including Citadel, Intercontinental Exchange (the parent company of the New York Stock Exchange), and Ark’s Cathie Wood. Founder Bryan Pellegrino shared that this scaling for the massive needs of traditional finance is partly due to zero-knowledge proofs, “which allows different parties to verify information in a privacy-preserving method”.\n\nRead more on zero-knowledge VMs (and “Jolt Inside” Zero) here.\n\nCrypto around the world…\n\nThe first-ever World Crypto Forum took place this past week in Seoul, South Korea. The event organizers observe that “KRW-denominated crypto market stands as the world’s second largest, following only the U.S. dollar.” And even though “institutional investment in digital assets remains strictly prohibited in Korea”, with participation limited to individual investors, the market has grown to become the second largest globally — showing “the immense potential and growth capacity” of Korea’s digital asset industry.\n\nAnthony Albanese, COO at a16z crypto, and SungMo Park, Head of APAC go-to-market for a16zcrypto, closed out the event.\n\nSouth Korea’s Financial Services Commission is looking to set a 5% cap on corporate investments in cryptocurrencies, according to Seoul Economic Daily, as reported by The Block — corporations and professional investors would be permitted to allocate up to 5% of their equity capital annually to the top 20 cryptocurrencies by market capitalization.\n\nRead more about our Asia expansion, and our notes on go-to-market in APAC and Korea.\n\nStablecoins, stablecoins everywhere…\n\nThe Financial Times featured how the “The WhatsApp moment for money is here”, an article by a16z crypto’s Chris Dixon on how the internet made information global, and crypto is doing the same for money; you can also read a version on our website here.\n\nY Combinator announced last week that YC-funded startups can now choose to receive their funding in stablecoins, sharing that they believe stablecoins “are setting the stage for a new fintech renaissance and broader global access to financial services.” The further observed that “Sending money should be as easy as sending a text message. Stablecoins make that possible: cheap, fast, and global, using currencies people already trust.”\n\nSee also Chris Dixon on “The WhatsApp Moment for Money” (April 2025) and how “stablecoins are our first real shot at doing for money what email did for communication: make it open, instant, and borderless” here.\n\nCrypto powering AI…\n\nCoinbase announced agentic wallets this week, saying that it’s “the first wallet infrastructure built specifically for agents” — and built on the x402 protocol. Stripe also previewed how machine payments will work, allowing developers to directly charge agents. “The current financial system is tuned for humans,” observed Stripe product lead Jeff Weinstein, sharing that agents need: microtransactions, 24/7 global rails, controls (for human out of the loop), http native, low latency, and finality guarantees.\n\nRead more of our coverage on agentic commerce here, including why AI needs crypto — especially now: https://a16zcrypto.com/posts/article/ai-needs-crypto-now/\n\nBonus: Tools you can use\n\nBut what does the token actually do — does it control governance? have any claim on the treasury? receive protocol revenue via buybacks or dividends?\n\nDefiLlama recently released Token Rights, which provides a “clear, standardized view of what a token entitles holders to” including revenue, treasury, governance — as well as historical governance discussions around token rights and whether teams raised equity separately from the token.\n\n~a16z editorial\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nYou should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investment-list/.\n\nThe content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures/ for additional important information.","tokens":2871,"crawled_at":1791195725610}
+{"id":10556,"url":"https://docs.sui.io/develop/transactions/ptbs/prog-txn-blocks","domain":"docs.sui.io","chapter":"layer1_layer2","title":"What is a PTB? | Sui Documentation","text":"Local network prerequisite\nIf you connect to LocalnetLocalnetLocal network you can run on your own machine for optimized development., verify your local node is running first. See Connecting to a local network.\n\nTransactions on Sui are composed of groups of commands that execute on inputs to define the result of the transactionTransactionA number of commands that execute on inputs to define the result of the transaction.. Referred to as programmable transaction blocksProgrammable transaction blocksDefine all user transactions on Sui. (PTBs), these groups of commands define all user transactions on Sui. PTBs allow a user to call multiple MoveMoveAn open source programming language used for all activity on Sui. functions, manage their objects, and manage their coins in a single transaction without publishing a new Move packagePackageSmart contracts on Sui.. Designed with automation and transaction builders in mind, PTBs are a lightweight and flexible way of generating transactions.\n\nHowever, more intricate programming patterns, such as loops, are not supported. In such cases, you must publish a new Move package.\n\nThe individual transaction commands within a PTB execute in order. You can use the results from one transaction command in any subsequent transaction command within the PTB. The effects of each transaction command in the block, such as objectObjectThe basic unit of storage on Sui. modifications or transfers, are applied atomically at the end of the transaction. If one transaction command fails, the entire block fails and no effects from the commands are applied.\n\nA PTB can perform up to 1,024 unique operations in a single execution, whereas transactions on traditional blockchains would require 1,024 individual executions to accomplish the same result. This structure also results in cheaper gasGasThe computational cost of execution and object storage for a transaction. fees. The cost of facilitating individual transactions is always more than the cost of those same transactions blocked together in a PTB.\n\nTransaction components​\n\nThere are two parts of a PTB that are relevant to execution semantics. Other transaction information, such as the transaction sender or the gas limit, might be referenced but are out of scope. The structure of a PTB is:\n\n{\ninputs: [Input],\ncommands: [Command],\n}\n\nLooking closer at the two main components:\n\nThe inputs value is a vector of arguments, [Input]. These arguments are either objects or pure values that you can use in the commands. The objects are either owned by the sender or are shared or immutable objects. The pure values represent basic Move values, such as u64 or String values, which you can construct purely from their bytes. For historical reasons, Input is CallArg in the Rust implementation.\n\nThe commands value is a vector of commands, [Command]. The possible commands are:\n\ntx.splitCoins(coin, amounts): Creates new coins with the defined amounts, split from the provided coin. Returns the coins so that it can be used in subsequent transactions.\n\nExample: tx.splitCoins(tx.gas, [tx.pure.u64(100), tx.pure.u64(200)])\n\ntx.mergeCoins(destinationCoin, sourceCoins): Merges the sourceCoins into the destinationCoin.\n\nExample: tx.mergeCoins(tx.object(coin1), [tx.object(coin2), tx.object(coin3)])\n\ntx.transferObjects(objects, address): Transfers a list of objects to the specified addressAddressA unique, anonymous identity on a blockchain network..\n\nExample: tx.transferObjects([tx.object(thing1), tx.object(thing2)], tx.pure.address(myAddress))\n\ntx.moveCall({ target, arguments, typeArguments }): Executes a Move call. Returns whatever the Sui Move call returns.\n\nExample: tx.moveCall({ target: '0x2::devnet_nft::mint', arguments: [tx.pure.string(name), tx.pure.string(description), tx.pure.string(image)] })\n\ntx.makeMoveVec({ type, elements }): Constructs a vector of objects that can be passed into a moveCall. This is required as there's no other way to define a vector as an input.\n\nExample: tx.makeMoveVec({ elements: [tx.object(id1), tx.object(id2)] })\n\ntx.publish(modules, dependencies): Publishes a Move package. Returns the upgrade capability object.\n\ntx.upgrade(modules, dependencies, packageId: EXAMPLE_PACKAGE_ID, ticket): Upgrades an existing package. No init functions are called for upgraded modulesModuleA component of a Move package that defines interaction with on-chain objects..\n\nLearn more about each PTB command.\n\nInputs and results​\n\nInputs are the values that are provided to the PTB, and results are the values that are produced by the PTB commands. The inputs are either objects or basic Move values, and the results are arbitrary Move values, including objects. Inputs and results form the data flow through a PTB's execution.\n\nThey can be seen as populating an array of values. For inputs, there is a single array, but for results, there is an array for each individual transaction command, creating a 2D-array of result values. You can access these values by borrowing, mutably or immutably, by copying, if the type permits, or by moving, which takes the value out of the array without re-indexing.\n\nLearn more about inputs and results.\n\nArgument structure and usage​\n\nCommands take Argument values that specify which input or result to use. The runtime infers whether to pass the argument by reference or by value based on the command's expected type.\n\nThe Argument enum has 4 variants:\n\nInput(u16): References an input by its index. For example, with inputs [Object1, Object2, Pure1, Object3], use Input(0) for Object1 and Input(2) for Pure1.\n\nGasCoin: References the SUI coin used to pay for gas. When using address balance gas payment (empty gas payment list), GasCoin references a synthetic coin created from the sender or sponsor address balance. This is separate from other inputs because it has special restrictions:\n\n&mut or & usage anywhere.\n\nOnly by value through TransferObjects or sui::coin::send_funds\n\nIf you need an owned Coin<SUI> from the GasCoin, first use SplitCoins.\n\nNestedResult(u16, u16): References a result from a previous command. The first index specifies the command, the second specifies which result from that command. For example, if command 1 returns [Value1, Value2], use NestedResult(1, 0) for Value1 and NestedResult(1, 1) for Value2.\n\nResult(u16): Shorthand for NestedResult(i, 0), but only valid when the command at index i returns exactly 1 result. Use NestedResult for commands that return 0 or multiple results.\n\nExecution​\n\nFor the execution of PTBs, the input vector is populated by the input objects or pure value bytes. The transaction commands are then executed in order, and the results are stored in the result vector. Finally, the effects of the transaction are applied atomically.\n\nStart of execution​\n\nAt the beginning of execution, the PTB runtime loads the input objects into the input array. The network already verifies the objects, checking rules like existence and valid ownership. The pure value bytes are also loaded into the array but not validated until usage.\n\nThe most important consideration at this stage is the effects on the gas coin. At the beginning of execution, the system withdraws the maximum gas budget (in terms of SUI) from the gas coin. The system returns any unused gas to the gas coin at the end of execution, even if the coin has changed owners.\n\nObject consumption​\n\nAll objects created or returned by Move commands must either be consumed (destroyed, transferred, or used by another command) or explicitly dropped if the type has the drop ability.\n\nIn a PTB, if you create an object through a Move command and do not destroy, transferTransferChanging the owner of an asset., or use it in a subsequent command, the transaction fails with an error.\n\nPre-execution validation​\n\nWhen a transaction is signed, the network performs the following validations on specific commands:\n\nSplitCoins and MergeCoins: Verifies that the argument arrays (AmountArgs and ToMergeArgs) are non-empty.\n\nMakeMoveVec: Verifies that the type must be specified for an empty vector of Args.\n\nPublish: Verifies that the ModuleBytes are not empty.\n\nArgument usage rules​\n\nEach argument can be used by reference or by value. The usage is based on the type of the argument and the type signature of the command:\n\nIf the signature expects an &mut T, the runtime checks the argument has type T and it is then mutably borrowed.\n\nIf the signature expects an &T, the runtime checks the argument has type T and it is then immutably borrowed.\n\nIf the signature expects a T, the runtime verifies the argument has type T, then copies the value if T: copy or moves it otherwise. Objects are always moved because sui::object::UID does not have the copy ability.\n\nThe transaction fails if an argument is used in any form after being moved. There is no way to restore an argument to its position (its input or result index) after it is moved.\n\nIf an argument is copied but does not have the drop ability, then the last usage is inferred to be a move. As a result, if an argument has copy and does not have drop, the last usage must be by value. Otherwise, the transaction fails because a value without drop has not been used.\n\nBorrowing rules​\n\nBorrowing follows additional rules to ensure safe reference usage:\n\nMutable borrow: No other borrows can be outstanding. An overlapping mutable borrow could create dangling references.\n\nImmutable borrow: No mutable borrows can be outstanding. Multiple immutable borrows are allowed.\n\nMove: No borrows can be outstanding. Moving a borrowed value invalidates existing references.\n\nCopy: Allowed regardless of outstanding borrows.\n\nSpecial object handling​\n\nObject inputs have the type T of the underlying object. ObjectArg::Receiving inputs are the exception and have type sui::transfer::Receiving<T>. This wrapper indicates the object is owned by another object, not the sender. Call sui::transfer::receive with the parent object to unwrap it and prove ownership.\n\nShared objects have restrictions on by value usage to ensure they remain shared or are deleted by the end of the transaction:\n\nRead-only shared objects (marked as not mutable) cannot be used by value.\n\nShared objects cannot be transferred or frozen. These operations succeed during execution but cause the transaction to fail at the end.\n\nShared objects can be wrapped or converted to dynamic fields during execution, but must be re-shared or deleted before the transaction completes.\n\nMove call rules​\n\nPTBs can call any public function and any entry function, whether private (entry fun f()), or public(package) (public(package) entry fun f()). Non-entry private and public(package) functions cannot be called from PTBs. Note that in this way, there is no reason to add entry to a public function.\n\ninfo\nPreviously, entry functions had signature restrictions that limited their parameter and return types compared to public functions. These restrictions have been removed. entry functions can now have the same signature as any public function.\n\nReturn types:\nMove calls cannot return references (&T or &mut T).\n\nPrivate generics:\nSome framework functions have type parameters that can only be instantiated with types defined in the same module. Since PTBs are not modules, they cannot supply these types and therefore cannot call these functions directly. For example, certain sui::transfer functions like transfer and share_object require a type defined in the calling module, and as such cannot be called from a PTB. Instead, use the public_transfer and public_share_object variants.\n\nTxContext handling:\nTxContext parameters (&TxContext or &mut TxContext) are automatically injected by the runtime; callers do not supply them. TxContext can appear at any position in the parameter list, and a function can have multiple TxContext parameters as long as they are immutable (&TxContext). These parameters are not counted toward the user-supplied argument count for indexing purposes.\n\nNon-public entry function restrictions​\n\nA non-public entry function is a function declared with entry that is not public. It is either private (entry fun f()) or public(package) (public(package) entry fun f()). These functions can be called directly in PTBs but not from other packages.\n\nNon-public entry functions have a single restriction: their arguments cannot be in a \"hot\" clique (see below) when the function is called. This restriction ensures that arguments to non-public entry functions are not entangled with outstanding hot potato values that could force behavior after the function executes.\n\nHot potato values\n\nA value is a hot potato if its type has neither the drop nor the store ability. Hot potato values must be consumed (moved by value) before the transaction completes; they cannot be silently dropped or stored.\n\nCliques\n\nThe system tracks which values are entangled using cliques. As described above, the goal is to prevent hot potato values from forcing behavior outside of the call to the non-public entry function. The cliques provide a modeling of this \"entanglement\" by keeping a count of how many hot potato values are live and which values they have interacted with:\n\nEach PTB input starts in its own clique with a hot count of 0.\n\nWhen values are used together as arguments in a command, their cliques merge. The hot counts add together.\n\nHot potato return values from a command increment the merged clique's hot count.\n\nMoving (consuming) a hot potato decrements its clique's hot count.\n\nBefore a non-public entry call, the merged clique of its arguments must have a hot count of 0.\n\nA non-public entry function can consume hot potato values, but they must be the last hot values in their clique. The hot count check happens after arguments are consumed but before the function is verified.\n\nShared objects consumed by value\n\nConsuming a shared object by value permanently marks its clique as \"always hot.\" Since shared objects cannot be wrapped (they must be re-shared or deleted) consuming one by value is treated similarly to a hot potato that can never be resolved. A non-public entry function can receive a shared object by value directly, but it cannot receive a value whose clique previously interacted with a shared object consumed by value.\n\nExamples\n\nConsider the following module:\n\nmodule ex::m;\n\npublic struct HotPotato()\n\npublic fun hot<T>(x: &mut Coin<T>): HotPotato { ... }\n\nentry fun spend<T>(x: &mut Coin<T>) { ... }\n\npublic fun cool(h: HotPotato) { ... }\n\nIn this invalid PTB, the HotPotato from command 0 is still alive in the same clique as Input(0) when spend is called:\n\n// Invalid PTB\n// Input 0: Coin<SUI>\n// cliques: { Input(0) } => 0\n0: ex::m::hot(Input(0));\n// cliques: { Input(0), Result(0) } => 1\n1: ex::m::spend(Input(0)); // INVALID: Input(0)'s clique has count > 0\n2: ex::m::cool(Result(0));\n\nHowever, if the hot potato is consumed before calling spend, the clique's count drops to 0 and the call succeeds:\n\n// Valid PTB\n// Input 0: Coin<SUI>\n// cliques: { Input(0) } => 0\n0: ex::m::hot(Input(0));\n// cliques: { Input(0), Result(0) } => 1\n1: ex::m::cool(Result(0));\n// cliques: { Input(0) } => 0\n2: ex::m::spend(Input(0)); // Valid: Input(0)'s clique has count 0\n\nIn a flash loan scenario, entanglement extends transitively. Even if a value was not directly involved in the loan, being in the same clique as the loan's hot potato makes it ineligible for a non-public entry call:\n\nmodule flash::loan;\n\npublic struct Loan { amount: u64 }\n\npublic fun issue(bank: &mut Bank, amount: u64): (Balance<SUI>, Loan) { ERROR }\n\npublic fun repay(bank: &mut Bank, loan: Loan, repayment: Balance<SUI>) { ERROR }\n\n// Invalid PTB\n// Input 0: flash::loan::Bank, Input 1: u64\n// cliques: { Input(0) } => 0, { Input(1) } => 0\n0: flash::loan::issue(Input(0), Input(1))\n// cliques: { Input(0), Input(1), NestedResult(0,0), NestedResult(0,1) } => 1\n1: sui::coin::from_balance(NestedResult(0,0));\n// cliques: { Input(0), Input(1), NestedResult(0,1), Result(1) } => 1\n2: ex::m::spend(Result(1)); // INVALID: Result(1)'s clique has count > 0\n3: sui::coin::into_balance(Result(1));\n4: flash::loan::repay(Input(0), NestedResult(0,1), Result(3));\n\nEven though the Coin created in command 1 was not directly involved in the flash loan, it is part of a clique with the outstanding Loan hot potato (NestedResult(0,1)). Repaying the loan before calling spend would make the PTB valid.\n\nPure value type checking​\n\nPure values are not type checked until they are used. The first time a pure value appears as an argument expecting type T, the system checks that T is a valid pure type (see the Inputs section) and that the bytes deserialize to T. Each distinct type creates a separate typed copy of the bytes, so the same pure input can be used at multiple types as long as the bytes are valid for each. For example, you can use the same bytes as an ASCII string std::ascii::String and as a UTF-8 string std::string::String. Each typed copy is treated as its own input, so mutations affect only that type's value, not all values created from the same bytes.\n\nPublish and upgrade rules​\n\nBoth commands embed their module bytes and dependency IDs directly in the command structure, however, these are not PTB Argument values.\n\nPublish:\n\nReturns a single sui::package::UpgradeCap.\n\nAfter the package is staged, the runtime calls each module's init function (if present) in the order the modules are provided (in the vector of serialized bytes). init receives &mut TxContext and optionally a one-time witness. Additional init arguments are not yet supported but are planned.\n\nThe package is available to init functions during execution. It is staged before they run.\n\nUpgrade:\n\nTakes exactly one PTB argument: a sui::package::UpgradeTicket (by value).\n\nReturns a single sui::package::UpgradeReceipt.\n\nDoes not call init functions. Newly added modules in an upgrade cannot have init functions.\n\nThe module digest and package ID in the ticket must match exactly.\n\nThe upgrade policy (compatible, additive, dep-only) is enforced from the ticket.\n\nEnd of execution​\n\nAt the end of execution, the remaining values are checked and effects for the transaction are calculated.\n\nFor inputs:\n\nRemaining immutable or read only input objects are skipped (no modifications made).\n\nRemaining mutable input objects are returned to their original owners (shared remain shared, owned remain owned).\n\nRemaining pure input values are dropped (all permissible types have copy and drop).\n\nShared objects are only deleted or re-shared. Any other operation (wrap, transfer, freezing) results in an error.\n\nFor results:\n\nRemaining results with the drop ability are dropped.\n\nIf a value has copy but not drop, its last usage must have been by-value (treated as a move).\n\nOtherwise, an error is given for unused values without drop.\n\nFor gas:\n\nAny remaining SUI deducted from the gas coin at the beginning of execution is returned to the coin, even if the owner has changed. The maximum possible gas is deducted at the beginning of execution, and unused gas is returned at the end (all in SUI). Because the gas coin can only be taken by value with TransferObjects, it has not been wrapped or deleted.\n\nThe total effects (created, mutated, and deleted objects) are then passed out of the execution layer and applied by the Sui network.\n\nExecution example​\n\nBy following each command's execution, you can see how inputs flow through commands, how results accumulate, and how the final transaction effects are determined.\n\nSuppose you want to buy 2 items from a marketplace costing 100 MIST. You keep one item for yourself and send the other item plus the remaining coin to a friend at address 0x808.\n\n{\ninputs: [\nPure(/* @0x808 BCS bytes */ ...),\nObject(SharedObject { /* Marketplace shared object */ id: market_id, ... }),\nPure(/* 100u64 BCS bytes */ ...),\n]\ncommands: [\nSplitCoins(GasCoin, [Input(2)]),\nMoveCall(\"some_package\", \"some_marketplace\", \"buy_two\", [], [Input(1), NestedResult(0, 0)]),\nTransferObjects([GasCoin, NestedResult(1, 0)], Input(0)),\nMoveCall(\"sui\", \"tx_context\", \"sender\", [], []),\nTransferObjects([NestedResult(1, 1)], NestedResult(3, 0)),\n]\n}\n\nThe inputs include the friend's address, the marketplace object, and the coin split value. The commands split off the coin, call the marketplace function, send the gas coin and one object, grab your address (through sui::tx_context::sender), and send the remaining object to yourself.\n\nCommand 0: SplitCoins(GasCoin, [Input(2)])\n\nAccesses the gas coin by mutable reference and loads Input(2) as 100u64 (copied, not moved). Creates a new coin.\n\nStateValue\nGas coin balance\n499,900 MIST\n\nResult\n[Coin<SUI> { id: new_coin, value: 100 }]\n\nCommand 1: MoveCall(\"some_package\", \"some_marketplace\", \"buy_two\", ...)\n\nCalls buy_two(marketplace: &mut Marketplace, coin: Coin<SUI>, ctx: &mut TxContext): (Item, Item). Uses Input(1) by mutable reference (marketplace) and NestedResult(0, 0) by value (coin is moved and consumed).\n\nStateValue\nResults[0][0]\nmoved\n\nResult\n[Item { id: id1 }, Item { id: id2 }]\n\nCommand 2: TransferObjects([GasCoin, NestedResult(1, 0)], Input(0))\n\nTransfers the gas coin and first item to 0x808. Both objects are taken by value (moved).\n\nStateValue\nGas coin\nmoved\n\nResults[1][0]\nmoved\n\nResult\n[]\n\nCommand 3: MoveCall(\"sui\", \"tx_context\", \"sender\", [], [])\n\nCalls sender(ctx: &TxContext): address. Returns the sender's address.\n\nStateValue\nResult\n[sender_address]\n\nCommand 4: TransferObjects([NestedResult(1, 1)], NestedResult(3, 0))\n\nTransfers the second item to the sender. The item is moved by value; the address is copied by value.\n\nStateValue\nResults[1][1]\nmoved\n\nResult\n[]\n\nInitial state​\n\nGas Coin: Coin<SUI> { id: gas_coin, balance: 1_000_000u64 }\nInputs: [Pure(@0x808), Marketplace { id: market_id }, Pure(100u64)]\nResults: []\n\nAfter maximum gas budget of 500_000 is deducted:\n\nGas Coin: Coin<SUI> { id: gas_coin, balance: 500_000u64 }\n\nFinal state​\n\nGas Coin: _ (moved)\nInputs: [Pure(@0x808), Marketplace { id: market_id } (mutated), Pure(100u64)]\nResults: [\n[_],\n[_, _],\n[],\n[sender_address],\n[]\n]\n\nEnd of execution checks​\n\nInput objects: Gas coin moved. Marketplace remains shared (mutated).\n\nResults: All remaining values have drop ability (Pure inputs, sender's address). All other results moved.\n\nShared objects: Marketplace not moved, remains shared.\n\nTransaction effects:\n\nCoin split from gas (new_coin) does not appear (created and deleted in same transaction).\n\nGas coin and Item { id: id1 } transferred to 0x808. Remaining gas returned to gas coin despite owner change.\n\nItem { id: id2 } transferred to sender.\n\nMarketplace object returned as shared (mutated).\n\nRelated topics\n\nConnecting to a Local Network\nConnect to a Sui local network using the Sui CLI. Use local networks to test your applications and prepare for launching them on Devnet or Testnet.\nPTB Commands\nReference for all PTB commands — TransferObjects, SplitCoins, MergeCoins, MakeMoveVec, MoveCall, Publish, and Upgrade — including each command's form, arguments, return type, and conceptual Move signature.\nInputs and Results\n\nTransaction components\nInputs and results\nArgument structure and usage\nExecutionStart of execution\nObject consumption\nPre-execution validation\nArgument usage rules\nEnd of execution\n\nExecution example\n\nWas this page helpful?","tokens":5820,"crawled_at":1791195739441}
+{"id":10557,"url":"https://a16zcrypto.com/team/a16z-crypto","domain":"a16zcrypto.com","chapter":"research","title":"a16z crypto - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\na16z crypto\n\nFeed\nFilter\n(1)\nclear filters\n\ncategory\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\nrecommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nauthor\n(1) all authors\n@x0rart\n1337 Skulls Sers\na16z crypto\na16z crypto editorial\na16z crypto policy & regulatory teams\na16z crypto Regulatory Team\nAaditya Shidham\nAaron Levie\nAaron Phillips\nAaron Schnider\nAbby Green\nAbdou Ndiaye\nAbhi Shelat\nAbhiram Kothapalli\nAbigail Johnson\nAdam Alter\nAdam Back\nAdam Bry\nAdam Grant\nAdam Ludwin\nAdam Martin\nAdam Thierer\nAdam Zuckerman\nAdela Tomsejova\nAdena Friedman\nAdena Hefets\nAdeniyi Abiodun\nAdina Fischer\nAdrian Cockcroft\nAdrian Fenty\nAdrienne Mayor\nAgostino Capponi\nAiden Slavin\nAileen Lee\nAisha Stephenson\nAJ Shankar\nAlan Knott-Craig\nAlan Schaaf\nAlana Benton\nAlbert Tang\nAlec Nielsen\nAlec Ross\nAlejandro Flores\nAlex Constantinople\nAlex Honnold\nAlex Hutchinson\nAlex Immerman\nAlex Kreitz\nAlex Kroeger\nAlex Le\nAlex Masmej\nAlex Morcos\nAlex Price\nAlex Pruden\nAlex Rampell\nAlex Roetter\nAlex Solomon\nAlex Spector\nAlex Stamos\nAlex Tabarrok\nAlexander (Sasha) Spiegelman\nAlexander Chia\nAlexander Zoppa\nAlexandra Chang\nAlexandria Lafci\nAlexis Lakes\nAlexis Madrigal\nAlexis Ohanian\nAli Ghodsi\nAli Yahya\nAlicia Barone\nAlin Tomescu\nAlisha Litman\nAlison Mangiero\nAlison Martin\nAllison Pickens\nAlyssa Del Bene\nAlyssa Torres\nAmanda Cantor\nAmanda Cassatt\nAmanda Catherine\nAmanda Mulay\nAmanda Tuminelli\nAmanda Tyler\nAmelia Salyers\nAmie Tyrrel\nAmir Shevat\nAmira Yahyaoui\nAmy Abernethy\nAmy Berliner\nAmy Bohutinsky\nAmy Choice\nAmy Cray\nAmy Gill\nAmy Hoemeke\nAmy Kalokerinos\nAmy Robertson\nAna Mostarac\nAna Susi\nAnatoly Yakovenko\nAndie Taylor\nAndisheh Tahriri\nAndre Iguodala\nAndrea Clarke Hall\nAndrea Feinberg\nAndrea Rallo\nAndrea Simon\nAndrea Vinkler\nAndreas Papadimitropoulos, Jr\nAndreessen Horowitz\nAndrew Allen\nAndrew Chen\nAndrew F. Read\nAndrew Green\nAndrew Hall\nAndrew Lakis\nAndrew Lewis-Pye\nAndrew Lo\nAndrew Mason\nAndrew McAfee\nAndrew Milson\nAndrew Omori\nAndrew Radin\nAndrew Rubin\nAndrew Savage\nAndrew Smith\nAndrew Tretyakov\nAndy Beal\nAndy Coravos\nAndy Golden\nAndy Hill\nAndy Milenius\nAndy Rachleff\nAndy Tran\nAndy Walshe\nAneel Lakhani\nAngela Schenone\nAngela Strange\nAngela Tran Kingyens\nAngelica Gehr\nAniket Kate\nAnil Sethi\nAnish Acharya\nAnn Winblad\nAnna Berces\nAnna Jablonski\nAnna Semenova\nAnna Van Meurs\nAnnaLee Saxenian\nAnne Brandes\nAnne Lee Skates\nAnne Lewandowski\nAnne Mitchell\nAnne Yip\nAnnie Collins\nAnnie Duke\nAnthony Albanese\nAnthony Atala\nAnthony Foxx\nAnthony Lee Zhang\nAntonio Viggiano\nAntwone Stigall\nAnu Hariharan\nApril Roth\nAri Emanuel\nAri Juels\nArianna Huffington\nArianna Simpson\nArik Kershenbaum\nArmon Dadgar\nArnie Goldberg\nArsho Avetian\nArthur Brooks\nArun Sundararajan\nAsh Ashutosh\nAsha Christian\nAshley McCollum\nAshley Stern\nAshton Carter\nAtif Mian\nAtul Butte\nAubree Pelaez\nAubrey de Grey\nAugusto Marietti\nAurora Petracca\nAusten Allred\nAustin Guzman\nAustin Marchese\nAustin Wilson\nAva Iravani\nAvery Segal\nAvinash Solanky\nAviv Zohar\nAye Moah\nAzeem Azhar\nBailey Flanigan\nBailey Richardson\nBalaji Srinivasan\nBarry McCarthy\nBart Dessaint\nBeau Cronin\nBeau Woods\nBecky Pferdehirt\nBen Buckwalter\nBen Fielding\nBen Fisch\nBen Gardner\nBen Gomez\nBen Horowitz\nBen Kaufman\nBen Leventhal\nBen Lovell\nBen Napier\nBen Portney\nBen Rubin\nBen Scharfstein\nBen Schecter\nBen Silbermann\nBen Uretsky\nBen Wu\nBenedict Evans\nBenedikt Büenz\nBenjamin Ebner\nBenjamin Hindman\nBenjamin Wittes\nBenjamin Wu\nBennett Carroccio\nBenny Pinkas\nBernard J. Tyson\nBernard Tyson\nBeth Newman\nBethany Coates\nBharat Ramamurti\nBharath Ramsundar\nBill Carr\nBill Frist\nBill Hinman\nBill Janeway\nBill Krause\nBill Macaitis\nBlake Kim\nBlake Masters\nBlake Saari\nBlayne Donnell\nBob Iger\nBob Langer\nBob Moore\nBob Muglia\nBob Sutton\nBob Swan\nBob Tinker\nBob Wachter\nBobby Franklin\nBobby Green\nBobby Kotick\nBobby Wagner\nBoris Sofman\nBoris Wertz\nBrad Feld\nBrad Kern\nBrad Peterson\nBram Cohen\nBrandon Ballinger\nBrandon Barros\nBrandon Cherry\nBrandon Millman\nBrenda Kopf\nBrent McIntosh\nBrett Browman\nBrett Falk\nBrett Hagler\nBrewster Kahle\nBrian Armstrong\nBrian Balfour\nBrian Brooks\nBrian Crnkovich\nBrian Curran\nBrian Grazer\nBrian Koppelman\nBrian McCullough\nBrian Quintenz\nBrian Wilkins\nBridget McDowell\nBrittany Lucas\nBrittney Burrows\nBrooke Sheresky\nBruce Friedrich\nBryan Caplan\nBryan Chiang\nBryan Cox\nBryan Crowley\nBryan Faust\nBryan Houser\nBryan Kim\nBryan Pellegrino\nCaitlin Glazebrook\nCaitlin Johnston\nCaitlin Roberson\nCal Turner Jr.\nCaleb Christian\nCameron Schuler\nCamila De Souza\nCarine Carmy\nCarissa Bilinski\nCarl Agnelli\nCarl Eschenbach\nCarl Narcisse\nCarl Pope\nCarlos Araya\nCarolina Gonzalez\nCaroline Friedman\nCaroline Goggins\nCaroline Horn\nCaroline Moon\nCarolyn Bertozzi\nCarra Wu\nCasey Graul\nCasey Neistat\nCasey Winters\nCassady Churchill\nCassie Faerber\nCecilia Marshall\nCeia Font\nChad Rigetti\nChandra Krintz\nCharles Goetz\nCharles Hubbard\nCharles Koch\nCharlie Keinath\nCharlie Warzel\nChattry Meas\nChelsea Komlo\nChelsea Padilla\nCheng Li\nChris Bennett\nChris Best\nChris Burniske\nChris Curran\nChris DeWolfe\nChris Dixon\nChris Granger\nChris Hauth\nChris Lyons\nChris Messina\nChris Milk\nChris Power\nChris Santa Maria\nChris Wanstrath\nChristian Cachin\nChristian Catalini\nChristian Crowley\nChristian Seifert\nChristina Hampp\nChristina Lopes\nChristina Mercando\nChristina Xu\nChristina Zeidan\nChristine Darden\nChristine Perham\nChristopher Giancarlo\nChristopher Lee\nChristopher Mims\nChristopher Nguyen\nChristopher Rippingham\nChristopher Schroeder\nChristy Hubbard\nCiamac Moallemi\nCindi Zhang\nCindy Tenner\nClaire Austin\nClaire Cain Miller\nClaire Kart\nClaudia Picanco\nClay Shirky\nClayton Christensen\nClayton Gardner\nClifford Woolf\nClint Delapaz\nColin Bryar\nColin Rom\nCollin McCune\nConner Lyons Brown\nConnie Chan\nConnie Guglielmo\nConnor McCarthy\nConnor Moyles\nCorban Bell\nCorey Hawkins\nCorey Waller\nCourtney Dettlinger\nCraig Naylor\nCraig Walker\nCristina Cordova\nCurt Funderburk\nCuy Sheffield\nD'Arcy Coolican\nDaejun Park\nDaisy Linden\nDaisy Wolf\nDaljeet Virdi\nDalton Turay\nDan Berkenstock\nDan Boneh\nDan Frommer\nDan Primack\nDan Romero\nDan Shapero\nDan Siroker\nDan Stein\nDan Warmenhoven\nDan Wendlandt\nDaniel Chao\nDaniel Chen\nDanielle Andrzejewski\nDanielle Clark\nDanielle Looymans\nDanielle Lussier\nDanielle Morrill\nDanielle Shea\nDanny Shader\nDaphne Koller\nDapper Dan\nDaren Matsuoka\nDarin Malter\nDarshan Shankar\nDas Rush\nDave Jagoda\nDave King\nDave Touretzky\nDavid Banks\nDavid Belden\nDavid Damato\nDavid Deming\nDavid George\nDavid Haber\nDavid Hollestelle\nDavid Kerr\nDavid Lee\nDavid Mack\nDavid Madden\nDavid Marcus\nDavid Olson\nDavid Oyelowo\nDavid Pierce\nDavid Reich\nDavid Rumsey\nDavid Schweikert\nDavid Sinclair\nDavid Sverdlov\nDavid Tse\nDavid Ulevitch\nDavid Weiden\nDawn Lepore\nDawn Nott\nDeborah Embaie\nDeena Elitreby\nDeepak Maram\nDenis Nazarov\nDenis Young\nDenise Gonzalez\nDerek Dolin\nDerek Thompson\nDerrick Harris\nDevin Finzer\nDevon Zuegel\nDiana Peña\nDiane Greene\nDick Costolo\nDieter Shirley\nDiishan Imira\nDiogo Monica\nDominic Shine\nDominique Reliford\nDon Duet\nDon Faul\nDorris O'Brien\nDoug Ducey\nDoug Folden\nDoug McCracken\nDouglas Argueta\nDozie Uche\nDrew Coffman\nDylan Field\nDylan Rhodes\nEd Felten\nEd Lynch\nEddie Lim\nEddy Lazzarin\nEdith Zimmerman\nEdward Perkins\nEdwin Poston\nEfrat Noy\nEhud Shapiro\nEileen Burbidge\nEileen Wu\nElad Gil\nElaine Fuchs\nElaine Shi\nElena Burger\nEli Dourado\nElisa Leonhardt\nEliza Oak\nElizabeth Gunn\nElizabeth Harkavy\nElizabeth May\nElizabeth Ocken\nElizabeth Stark\nElizabeth Weil\nEllen Tunoa\nEmile Petrone\nEmilio Torres\nEmily Graff\nEmily Hinsch\nEmily Keir\nEmily Oster\nEmily Westerhold\nEmma Janaskie\nEric Budish\nEric Dai\nEric Ries\nEric Thomas\nEric Topol\nEric Wu\nErica Schecter\nErik Brynjolfsson\nErik Kiser\nErik Torenberg\nErika Bracken\nErika Herrera\nErika Louie\nErin Grody Kingsley\nErin Murphy\nErin Tice\nErin Tonnar\nErin Winkler\nErtem Nusret Tas\nEsther Shinn\nEthan Bueno de Mesquita\nEthan Ferreira\nEthan Zuckerman\nEuan Ashley\nEugene Volokh\nEugene Wei\nEugenia Yee\nEula Takahashi\nEva Sakkas\nEvan Burfield\nEvan Osnos\nEvangelos Simoudis\nEzra Klein\nF. Gary Gray\nFabiola Godinez\nFabrizio Zilibotti\nFahad Saleh\nFarid Jiandani\nFei-Fei Li\nFelix Do\nFEWOCIOUS\nFiona Kennedy\nFiona Murray\nFlashrekt\nFlora Oliveira\nFlori Del Valle\nFlorian Leibert\nFoteini Baldimtsi\nFrancesca Gino\nFrank Chen\nFrank Wilczek\nFred Benenson\nFred Ehrsam\nFred Upton\nFred Wilson\nFreda Lewis-Hall\nFrederic Kerrest\nFuture Editorial\nGabby Dizon\nGabby Reece\nGabriel Otte\nGabriel Vasquez\nGaetan Barthelemy\nGarrett Biel\nGary Ang\nGary Reedy\nGary Wolf\nGaurav Banga\nGaurav Dhillon\nGaut\nGayle Tzemach Lemmon\nGeoffrey Woo\nGeorg Fuchsbauer\nGeorg Petschnigg\nGeorge Church\nGeorge Danezis\nGeorge Fraser\nGeraldine Chan\nGérard Cachon\nGerard Ryle\nGerri Elliott\nGerry Tsoukalas\nGia Scinto\nGil Elbaz\nGil Shafir\nGina Moon\nGina Neff\nGina Yocom\nGinger Liau\nGokul Rajaram\nGoldie Chang\nGrace Ellis\nGraham Allison\nGrant Gregory\nGrant Jordan\nGrant LaFontaine\nGrant Rabenn\nGray Kinsella\nGreg Bowman\nGreg Clayman\nGreg Linares\nGreg Loehmann\nGreg Lynn\nGreg Solano\nGreg Truesdell\nGreg Waldon\nGregory Allen\nGregory Mundis\nGretchen Bush\nGretchen McCulloch\nGuido Appenzeller\nGustav Söderström\nGustavo Garcia\nGuy Goren\nGuy Raz\nGuy Wuollet\nHaley Van Dyck\nHanna Aziz\nHannah Frankl\nHanne Winarsky\nHaoyuan Li\nHarmit Malik\nHarry Grieve\nHarry Shum\nHarry Wright\nHatim Shafique\nHayden Adams\nHeather Gwynn\nHeather Podesta\nHedi Samar\nHelen Stoddard\nHelen Su\nHemant Mohapatra\nHendrik Pretorius\nHenri Kor\nHerb Lin\nHerman Narula\nHilmar Pétursson\nHoang Nguyen\nHoward Wu\nIan Dutra\nIan Shannon\nIan Sharp\nIce Cube\nIlan Zechory\nIllia Polosukhin\nIlyas Khan\nIma Christian\nIman Abuzeid\nInsiya Lokhandwala\nIon Stoica\nIrvin Chan\nIsa Guardalabene\nIsaiah Lott\nIsh Verduzco\nIsil Dillig\nIstván András Seres\nIttai Abraham\nIttay Eyal\nIva Messy\nIvan Linscott\nIvor Horn\nJ.D. Moriarty\nJack Donahoe\nJack Soslow\nJackie McQuiston\nJackson David\nJacob Westphal\nJacquelyn Melinek\nJad Esber\nJad Naous\nJade Lai\nJade Raymond\nJae Gnazzo\nJai Ramaswamy\nJaimie Buss\nJak Kennedy\nJake Auchincloss\nJakob Uszkoreit\nJamal Mohammed\nJames Beshara\nJames Currier\nJames da Costa\nJames Gwertzman\nJames J. Collins\nJames Kissell\nJames L. Madara\nJames Loftus\nJames Rathmell\nJames Rogers\nJames Watters\nJames Wu\nJames Zou\nJamie Brandon\nJamie McGurk\nJamie Sullivan\nJamilla Hemeid\nJana Odehnal\nJane Doe\nJane Lippencott\nJane Suh\nJanelle De Los Santos\nJared Bricklin\nJared Furutani\nJared Georgakopoulos\nJared Polis\nJared Smith\nJase Wilson\nJason Franklin\nJason Liu\nJason Mayden\nJason Milionis\nJason Mitchell\nJason Mok\nJason Rosenthal\nJason Warner\nJason Yanowitz\nJay Bradner\nJay Conte\nJay Drain\nJay Komarneni\nJay Rughani\nJean Reilly\nJeanne Tsan\nJeff Amico\nJeff Benson\nJeff Clark\nJeff Cordova\nJeff Glueck\nJeff Hawkins\nJeff Jones\nJeff Jordan\nJeff Lawson\nJeff Lu\nJeff Nagashima\nJeff Stump\nJeff Weiner\nJeffrey Immelt\nJeffrey Kaditz\nJeffrey Katzenberg\nJeffrey Kindler\nJeffrey Low\nJeffrey Silverstein\nJeffrey Zirlin\nJen Bulawsky\nJen Kha\nJenna Walsh\nJenna Zucker\nJennifer 8. Lee\nJennifer Doudna\nJennifer Kodner\nJennifer Konde\nJennifer Li\nJennifer Mumford\nJennifer Tejada\nJennifer Young\nJenny Cieplak\nJens Ernstberger\nJensen Harris\nJeremy Clark\nJeremy England\nJeremy Zhang\nJesse Holmes\nJesse Pollak\nJesse Walden\nJessica Childs\nJessica Hansen\nJessica Keeler\nJessica Patton\nJessica Verrilli\nJewel Pi\nJez Humble\nJi Kim\nJianying Luo\nJim Gilliam\nJimmy Chen\nJimmy Soni\nJing Wang\nJing Zou\nJJ Yu\nJoachim Neu\nJodi Lynn\nJodie Lutkenhaus\nJoe Gebbia\nJoe Grundfest\nJoe Montana\nJoe Morrissey\nJoe Schmidt\nJoe Sullivan\nJoel de la Garza\nJoel Mokyr\nJoel Monegro\nJoel Spolsky\nJoey Burleson\nJohn China\nJohn Collison\nJohn Fawcett\nJohn Garcia\nJohn Gedmark\nJohn Hennessy\nJohn Koelliker\nJohn M. Jack\nJohn Markoff\nJohn Menna\nJohn O’Farrell\nJohn Riccitiello\nJohn Smesko\nJohn Stanfield\nJohn Thompson\nJohn William Hatfield\nJonah Peretti\nJonathan Bush\nJonathan Dotan\nJonathan Downey\nJonathan Lai\nJonathan Lim\nJonathan Lusthaus\nJonathan Weissman\nJonathan Wong\nJordan Mazer\nJordan Stankowski\nJorge Conde\nJorge Gomez\nJose Guardado\nJoseph Bonneau\nJoseph Okpaku\nJoseph Spisak\nJosh Arnold\nJosh Bloom\nJosh Kim\nJosh Williams\nJoshua Browder\nJoshua Gans\nJoshua Grimm\nJoshua Hix\nJoshua Levin\nJoshua Lu\nJoshua Schank\nJoshua Soto\nJosie Ma\nJoyce Park\nJR Rivers\nJT Evans\nJuan Benet\nJudene Small\nJudy Savitskaya\nJudy Smith\nJulia Grace\nJulia Kirby\nJulie Bornstein\nJulie Farnham\nJulie Johnson\nJulie Samuels\nJulie Yoo\nJuliet Grier\nJuliet Nyatta\nJuliette Morton\nJulius Zhang\nJustin Bailey\nJustin Bethune\nJustin Blau\nJustin Cunningham\nJustin Gregorius\nJustin Kahl\nJustin Kan\nJustin Larkin\nJustin Paine\nJustin Pettit\nJustin Roberts\nJustin Simcock\nJustin Thaler\nJustine Moore\nJutta Steiner\nJyoti Bansal\nJZ Young\nKabir Gill\nKabir Laroia\nKais Khimji\nKamala Harris\nKaren Dunn\nKaren Wooley\nKarina Sobieski\nKarl Floersch\nkarma (Daniel Reynaud)\nKarmacoma\nKarthik Rau\nKartik Nayak\nKate Darling\nKate Dellolio\nKate Kerames\nKatherine Boyle\nKatherine Minarik\nKatherine Rundell\nKatherine Schoebel\nKathryn McKinley\nKathy Liu\nKathy Yang\nKatia Ameri\nKatie Baynes\nKatie Haun\nKatie Hemmerling\nKaty DeWitt-Drew\nKaty Nelson\nKayvon Tehranian\nKeener Barnhorst\nKeller Medlin\nKeller Rinaudo\nKelly Cannon\nKelsey Chaplinsky\nKelsey Mellard\nKen Chong\nKen Coleman\nKen Kocienda\nKerry Ganim\nKesha Cash\nKevin Chou\nKevin Chu\nKevin Dulsky\nKevin Kelly\nKevin McKinley\nKevin Nishioka\nKevin O'Kane\nKevin Rose\nKevin Tan\nKevin Wu\nKevin Zollman\nKidSuper\nKieran Snyder\nKierston Gittens\nKiki Mavridis\nKim Enright\nKim Malone Scott\nKim Milosevich\nKim Stevenson\nKim Zetter\nKimberly Tan\nKindra Mason\nKira Poskanzer\nKira Song\nKirstin Arbide\nKirt McMaster\nKofi Ampadu\nKouki Harasaki\nKrista Anderson-Copperman\nKristen Fortney\nKristen Johansson\nKristen Kee\nKristin Sauchak\nKristin Thayer\nKristina Graci-deLuna\nKristina Shen\nKristine Lipscomb\nKristo Käärmann\nKrisztina Holly\nKunal Bahl\nKunle Olukotun\nKurt House\nKyle Russell\nLaird Hamilton\nLatasha\nLaura Arrillaga-Andreessen\nLaura Baller\nLaura Behrens Wu\nLaura Deming\nLaura Gravley\nLaura Johnson\nLaura Shores\nLaura Weidman Powers\nLauren Berson\nLauren Illovsky\nLauren Murrow\nLauren Richardson\nLauren Spragge\nLaurene Powell Jobs\nLawrence Levy\nLawrence Summers\nLeah Cassidy\nLee Kleinman\nLee Lefkowitz\nLeeAnn Caballero\nLeila Hay\nLeila Janah\nLenny Rachitsky\nLeslie Jaw\nLeslie Vosshall\nLester Chen\nLi Fan\nLi Fei-Fei\nLi Jin\nLiang Wu\nLilian King\nLily Liu\nLina Sergie Attar\nLinda Banuelos\nLinda Xie\nLinden Tibbets\nLing Ren\nLinlin Li\nLinxin Wen\nLioba Heimbach\nLisa Hawke\nLisa Lambert\nLisa Orr\nLisa Reilly\nLisa Rosano\nLizzy Anderson\nLJ Erwin\nLloyd Dean\nLoretta Sanchez\nLori Potter\nLuca Prosperi\nLuca Zanolini\nLuis Martinez\nLuis von Ahn\nLuke Wroblewski\nLydia Green\nLynda Gibson\nLynn Rudolph\nMadan Nagaldinne\nMaddison Masaeli\nMadeline Lancaster\nMaggie Hsu\nMaggie Leung\nMaggie Romero\nMahad Abedin\nMahesh Iyer\nMahesh Vellanki\nMahimna Kelkar\nMakiri Duckett\nMalinka Walaliyadde\nMallesh M. Pai\nMalloy Evans\nManas Punhani\nManny Luna\nMarc Andreessen\nMarc Andrusko\nMarc Benioff\nMarc Levinson\nMarci Barbera\nMarco Reuter\nMargaret Jen\nMargit Wennmachers\nMaria LaMagna Morales\nMarian Garvin\nMarianne Winkler\nMariano Sorgente\nMaricarmen Alvarez\nMariel Goldenstein\nMarigold Vu\nMarina Kusserow\nMario Gabriele\nMario Linares\nMarissa Bramlett\nMark Cranney\nMark Leslie\nMark McAndrew\nMark McClusky\nMárk Melczer\nMark Moore\nMark Regan\nMark Sendak\nMarkos Georghiades\nMarkus Covert\nMarkus Funk\nMartha Lane Fox\nMartin Casado\nMartin Fischer\nMarty Makary\nMarvin Ammori\nMarvin Zamora\nMary Pat Jordan\nMary-Catherine Lader\nMaryam Bahrani\nMason Hall\nMatei Zaharia\nMatt Abrahams\nMatt Billmann\nMatt Bornstein\nMatt Clifford\nMatt Flannery\nMatt Fleming\nMatt Gleason\nMatt Kaeberlein\nMatt Levine\nMatt Levy\nMatt Oberhardt\nMatt Shortal\nMatt Spence\nMatt Weinberg\nMatthew Colford\nMatthew Green\nMatthew Haughey\nMatthew McCullough\nMatthew Mills\nMatthew Olsen\nMatthew Rutter\nMatthew Stein\nMatthieu Hafemeister\nMaureen Lara\nMax Kesten\nMax Krohn\nMax Levchin\nMax Polyak\nMax Resnick\nMax Ventilla\nMaya Rahkonen\nMcPherson Moore\nMeaghan Hardy\nMeg Whitman\nMegan Holston-Alexander\nMegan Kristalyn\nMehdi Hasan\nMehul Mehta\nMel Williams\nMelanie Galang\nMelissa Liao\nMelissa Minor\nMelissa Wasser\nMellody Hobson\nMelody Latronico\nMeredith Donahue\nMia Gonzalez\nMia Mandich\nMicah Johnson\nMichael Beckerman\nMichael Blau\nMichael Brandt\nMichael Chan\nMichael Copeland\nMichael Dearing\nMichael Dell\nMichael Franklin\nMichael Garcia\nMichael J. Casey\nMichael J. Freedman\nMichael Killam\nMichael King\nMichael Lee\nMichael Leiter\nMichael Morell\nMichael Ostrovsky\nMichael Ovitz\nMichael Paulus\nMichael Raynor\nMichael Reed\nMichael Snyder\nMichael Temkin\nMichael Wee\nMichael Zhu\nMichel Del Buono\nMichel Feaster\nMichèle Flournoy\nMichele Griffin\nMichele Korver\nMichele Law\nMichelle Ervin\nMichelle Kelso\nMichelle Kung\nMichelle Mundy\nMichelle Shin\nMichelle Ufford\nMichelle Volz\nMichelle Wilson\nMichelle Winn\nMichelle You\nMike Curtis\nMike Haydon\nMike Hearn\nMike Jones\nMike Kasperzak\nMike Kelly\nMike King\nMike Lempres\nMike Manning\nMike Maples jr\nMike Masnick\nMike Matchett\nMike Paulus\nMike Sandwick\nMikeal Rogers\nMikey Dickerson\nMiles Jennings\nMilijana Curic\nMiller Whitehouse-Levine\nMinerva Munoz\nMinnie Ingersoll\nMinsun Pak\nMintu Turakhia\nMiranda Christ\nMo Shaikh\nMohammad Akbarpour\nMohsen Malayeri\nMolly Grace\nMonique McCambridge\nMorgan Beller\nMorgan Bender\nMurat Pak\nMuriel Bowser\nMurray Shanahan\nMy Pham\nNadia Asparouhova\nNadia Eghbal\nNaftali Harris\nNaithan Jones\nNanjira Sambuli\nNaomi Metzger\nNashid Braswell\nNassim Eddequiouaq\nNat Barling\nNatacha Crooks\nNatalia Carrera\nNatalie Bucher\nNatalie Taumoepeau\nNate Chang\nNate Lau\nNathalie Balaban\nNathan McCauley\nNathan Yoon\nNathaniel Gleicher\nNathaniel Popper\nNav Singh\nNazanin Daneshvar\nNeel Maitra\nNeha Narula\nNelson Perla-Ward\nNeveen Bader\nNicholas Christakis\nNicholas Pacilio\nNick Babaian\nNick McKeown\nNick Quah\nNick Tomaino\nNicki Locker\nNicole Conner\nNicole Forsgren\nNicole Irvin\nNicole Neuman\nNicole Stanners\nNiels Provos\nNigel Robinson\nNikhil Krishnan\nNina Suthers\nNir Eyal\nNitasha Tiku\nNitin Natarajan\nNitya Subramanian\nNkiru Balonwu\nNoah Citron\nNoah Feldman\nNoah Levine\nNoah Smith\nNoam Nisan\nNoemi Glaeser\nO’Shea Jackson Jr.\nOlaf Carlson-Wee\nOleg Rogynskyy\nOliver Hsu\nOlivia Moore\nOlivia Webb\nOmri Weinstein\nOoshma Garg\nOprah Winfrey\nOrion Hindawi\nOscar Menjivar\nP.J. Hasleton\nPablo Montagnes\nPacky McCormick\nPak\nPalmer Luckey\nPamela Anderson\nPamon Forouhar\nParag Khanna\nParijat Talkad\nParker Brown\nParker Conrad\nPatrice Peck\nPatrick Byrne\nPatrick Collison\nPatrick Conway\nPatrick McCorry\nPatrick McHenry\nPatrick O’Grady\nPatrick Rivera\nPatrick Sutton\nPaul Cafiero\nPaul Daugherty\nPaul Davison\nPaul Krugman\nPaul Vigna\nPaula Long\nPenny Pritzker\nPerri Chilton\nPete Buttigieg\nPeter Blackwood\nPeter Buisseret\nPeter Chan\nPeter Donnelly\nPeter Johnson\nPeter Lauten\nPeter Leeson\nPeter Levine\nPeter Ludwig\nPeter Rubin\nPeter Thiel\nPeter Wang\nPetra Garrett\nPhil Daian\nPhil Hathaway\nPhil Wong\nPhong Nguyen\nPorter Smith\npplpleasr\nPranav Garimidi\nPrasad Akella\nPrat Moghe\nPreethi Kasireddy\npunk6529\nPurnima Padmanabhan\nPyrs Carvolth\nQasar Younis\nQuang Dao\nQuinten Burgunder\nQuintus Kilbourn\nRachael Horwitz\nRachel Goslins\nRachel Jenkins\nRachel Kalmar\nRachel McIntyre\nRachel Steiner\nRahul Iyer\nRahul Vohra\nRajeev Singh\nRajeev Venkayya\nRam Palaniappan\nRamana Jonnala\nRati Gelashvili\nRaul Vazquez\nRavi Parimi\nRay Dalio\nRaymond Carreira\nRebecca Lewis\nRebecca Rettig\nReed Hastings\nRefik Anadol\nRegina Benjamin\nRenato Valdés Olmos\nReshma Saujani\nReshma Sohoni\nRex Salisbury\nRich Ezekiel\nRichard Green\nRichard Menger\nRichard Rosenblatt\nRick Young\nRidhima Ahuja\nRiyaz Faizullabhoy\nRob Goodman\nRob McElhenney\nRob Pardo\nRob Rhinehart\nRobbie Petersen\nRobbie Peterson\nRobert Alexander\nRobert Cottrell\nRobert Hackett\nRobert Kolker\nRobert Leshner\nRobert McNeely\nRobert Moreno\nRobert Siegel\nRobert Stromberg\nRobert Weber\nRobin Casey\nRobin Guo\nRobin Weisman\nRod Johnson\nRodrigo Ibarra Lopez\nRodrigo Pacheco\nRoger Dickey\nRoger Wattenhofer\nRoham Gharegozlou\nRohini Mukand\nRohit Bansal\nRoman Mars\nRoman Stanek\nRon Gill\nRon Lavi\nRon Rothblum\nRonald Evans\nRonnie Harris\nRosa Davila\nRosalind Rattan\nRose Legarda\nRoss Andersen\nRoss Shuel\nRostin Behnam\nRuben Gallego\nRuben Smith\nRuss Altman\nRuss Heddleston\nRuss Roberts\nRussell Davies\nRyan Allen\nRyan Caldbeck\nRyan Conde\nRyan Holloway\nRyan Hoover\nRyan McEntush\nRyan Petersen\nRyan Prescott\nRyan Sandler\nRyan Spoon\nRyan Tseng\nRyan Walsh\nRyan Ward\nRyan Wyatt\nSaar Tochner\nSachin Jain\nSafi Bahcall\nSagar Dhawan\nSaku Panditharatne\nSalem Vance\nSam Blackshear\nSam Broner\nSam Gerstenzang\nSam Ragsdale\nSam Thompson\nSam Williams\nSam Yam\nSamantha Gelt\nSamantha Langford\nSamantha Ludwig\nSamson Wu\nSamuel Arbesman\nSamuel Hammond\nSandra Samayoa\nSandy Jen\nSankaet Pathak\nSantiago Rodriguez\nSara Boesen\nSarah Fazal\nSarah Hamburg\nSarah Lumbard\nSarah Mascardo\nSarah Meiklejohn\nSarah Porter\nSarah Rebello\nSarah Wang\nSasha Stiles\nSatish Talluri\nSaurabh Ladha\nSavannah Cherry\nScott Clark\nScott Duke Kominers\nScott Gottlieb\nScott Hassan\nScott Kupor\nScott Rubin\nScott Shenker\nScott Tyler\nScott Walker\nScott Weiss\nSean Duffy\nSean Neville\nSebastian Oddo\nSeema Amble\nSeemay Chou\nSep Kamvar\nSergiu Pasca\nSeth Lobree\nSeth Sivak\nSeth Sternberg\nShai Bernstein\nShai Kopeld\nShaka Senghor\nShakil Khan\nShan Sinha\nShana Fisher\nShane Mac\nShane Parrish\nShangda Xu\nShannon (Stubo) Brayton\nShannon Barbour\nShannon Kelly\nShannon Schiltz\nShannon Snow\nShari Doherty\nSharon Chang\nShawn Conway\nSheela Krothapalli\nShellye Archambeau\nSherie James\nSherriAnn Cole\nShishir Mehrotra\nShonda Rhimes\nSid Gorham\nSigne Pierce\nSimon Denny\nSiqi Chen\nSonal Chokshi\nSophie Song\nSoubhik Deb\nSpencer Dinwiddie\nSpencer Howard\nSpencer Rascoff\nSreeram Kannan\nSreevidya Kasturil\nSri Kosuri\nSriram Krishnan\nSrivatsan Sridhar\nStacey Cunningham\nStacey Merrick\nStacia Murray\nStacy Brown-Philpot\nStacy D'Amico\nStacy Warner\nStefan McDonough\nSten Tamkivi\nStephane Bancel\nStephanie Anyanwu\nStephanie Cohen\nStephanie Doppelt\nStephanie Smith\nStephanie Watkins\nStephanie Zinn\nStephen Armanios\nStephen Wink\nStephenie Zhang\nSteve Buress\nSteve Cadigan\nSteve Cheney\nSteve Harvey\nSteve Kaczynski\nSteve McDermid\nSteve Smith\nSteve Zhao\nSteven Adair\nSteven Ebert\nSteven Johnson\nSteven Levy\nSteven Sinofsky\nStewart Butterfield\nStina Ehrensvärd\nStuart Luman\nStuart Russell\nSudip Chakrabarti\nSue Hager\nSuhail Doshi\nSukhinder Singh Cassidy\nSumeet Singh\nSumit Shah\nSungMo Park\nSunil Chokshi\nSurya Ganguli\nSusan B. Wilde\nSusan Mernit\nSusan Rice\nSusannah Fox\nSydney Paul\nTaavet Hinrikus\nTaggart Matthiesen\nTamzen Brewis\nTana Billingsley\nTarek Mansour\nTarun Chitra\nTauri Laws Phillips\nTawny Holguin\nTaylor McFadden\nTed Not Lasso\nTed Sarandos\nTed Ullyot\nTerell Sterling\nTerence Carroll\nTeresa Carlson\nTerry Angelos\nTerry Brown\nThan Nguyen\nThanh Nguyen\nThe 2015 Academic Roundtable Sessions\nThe TxO team\nTheresa DeMichele\nTheresa Dilley\nTheresa Fisher\nTheresa Walz\nTheresia Gouw\nThibaut Scholasch\nThomas Gjerde\nThomas Juenger\nThomas Long\nThomas Rando\nTiffany Vo\nTiffany Zhong\nTim Beiko\nTim O'Reilly\nTim Roughgarden\nTim Schafer\nTim Sullivan\nTimmu Tõke\nTina Anderson\nTina Bhatnagar\nTina Ferguson\nTina Wie\ntinawie\nTing Ni\nTobi Lütke\nTodd Cranney\nTodd Lutwak\nTodd McKinnon\nTodd Park\nTodd Young\nTolga Dizdarer\nTom Butta\nTom Coates\nTom Davenport\nTom Ellis\nTom Hammer\nTom Hofmann\nTom Lehman\nTom Mitchell\nTom Preston-Werner\nTom Rikert\nTom Standage\nTomicah Tillemann\nTony Blair\nTony Blinken\nTori Landrum\nTracy Chou\nTracy Young\nTren Griffin\nTrent Mayol\nTrevor Bedford\nTristan Handy\nTristan Walker\nTroy Kirwin\nTugce Erten\nTurner Novak\nTushar Garg\nTyler Cowen\nTyler Wilson\nTyson Clark\nUma Valeti\nUsman Azam\nUzi Dutta\nValentina Marzorati\nValeria Nikolaenko\nValerie Arboleda\nVan Jones\nVan Le-Gray\nVanessa Kropf\nVas Narasimhan\nVaughn Ferguson\nVenkat Mocherla\nVicente De Baca\nVickie Casillas-Smith\nVictor Liang\nVictor Shoup\nVictoria Butcher\nVijay Balasubramaniyan\nVijay Kedar\nVijay Pande\nVineeta Agarwala\nVinod Khosla\nVirginia Postrel\nVishal Amin\nVitalik Buterin\nVivian Brooks\nVoices Onchain\nW. Brian Arthur\nWahab Owolabi\nWei Luo\nWendy Drpic\nWerner Gerola\nWes Taylor\nWhitney Owens\nWill Brown\nWill Wong\nWillem Mulder\nWilliam Gifford\nWilliam Mougayar\nWing Cheng\nXian Zhang\nXiang-Dong Fu\nXingchen Zhou\nYannai A. Gonczarowski\nYehuda Lindell\nYevgeniy Dodis\nYinuo Zhang\nYogi Roth\nYohei Ishii\nYoko Li\nYoni Levy\nYoram Novick\nYuichi Kurosawa\nYujin Chung\nYun Fan\nYung Yung Sheung\nYuval Efron\nYuval Harari\nZac Bookman\nZach Abrams\nZach Cohen\nZach Dicker\nZach Haigney\nZachary Chen\nZachary Gray\nZack Weiner\nZahabiya Gabaji\nZak Doric\nZal Bilimoria\nZane Lackey\nZeta Avarikioti\nZeya Yang\nZooko Wilcox\nZoran Basich\n\nclear all a16z crypto\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n10.09.24 / a16z crypto\nIntroducing Voices Onchain\nIntroducing the inaugural group of creators featured in Voices Onchain (VO): https://voicesonchain.com/. Voices Onchain highlights creators who have turned to blockchain technology to unlock new creative possibilities, build deeper connections with fans, and discover more ways to monetize their work. Explore their stories and help nominate (see form at bottom) more voices of artists and...\n\nannouncements & news\npolicy & regulation\nannouncements\n\n06.08.23 / a16z crypto\nCrypto Startup School 2023: Recap & Resources\nCrypto Startup School (CSS) is our early-stage accelerator, designed to foster growth in crypto startups through a variety of resources — including funding, mentorship, guidance from domain experts, and a network of fellow founders. The CSS 2023 program recently ended, culminating in a Demo Day event where the founders presented their projects to an audience...\n\nannouncements & news\nannouncements\nCrypto Startup Accelerator (CSX)\nCSX 2023\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":7019,"crawled_at":1791195748047}
+{"id":10558,"url":"https://www.metaplex.com/docs/smart-contracts/bubblegum-v2/sdk/javascript","domain":"www.metaplex.com","chapter":"docs","title":"JavaScript SDK - Bubblegum V2 - Metaplex","text":"The Bubblegum V2 JavaScript SDK (@metaplex-foundation/mpl-bubblegum) is the recommended TypeScript/JavaScript library for creating and managing compressed NFTs on Solana. Built on the Umi framework, it provides type-safe functions for all Bubblegum V2 operations and includes the DAS API plugin automatically.\nWhat You'll Learn\nThis SDK reference covers:\nSetting up Umi with the Bubblegum V2 plugin\nCreating merkle trees for storing cNFTs\nMinting, transferring, burning, and updating cNFTs\nDelegating, freezing, and verifying creators\nFetching cNFTs using the DAS API\nHandling transaction size limits and common errors\n\nSummary\nThe Bubblegum V2 JavaScript SDK wraps all MPL-Bubblegum V2 program instructions in a type-safe API and includes the DAS API plugin for reading cNFT data.\nInstall: npm install @metaplex-foundation/mpl-bubblegum @metaplex-foundation/umi-bundle-defaults\nRegister with Umi using .use(mplBubblegum()) — the DAS API plugin is included automatically\nUse getAssetWithProof before any write operation (transfer, burn, update, delegate, freeze, verify)\nApplies to Bubblegum V2 (MPL-Bubblegum 5.x) — not compatible with V1 trees\nQuick Start\nJump to: Setup · Create Tree · Mint · Transfer · Burn · Update · Delegate · Collections · Freeze · Verify Creators · Fetch · Errors · Quick Reference\nInstall dependencies: npm install @metaplex-foundation/mpl-bubblegum @metaplex-foundation/umi-bundle-defaults\nCreate a Umi instance with .use(mplBubblegum())\nCreate a Bubblegum tree with createTree\nMint cNFTs with mintV2; use getAssetWithProof before any subsequent write operation\nInstallation\nTerminal\nnpm install @metaplex-foundation/mpl-bubblegum @metaplex-foundation/umi-bundle-defaults\n\nTypeDoc API Reference\nFull generated API documentation for the SDK.\n\nnpm Package\nPackage on npmjs.com with version history.\n\nUmi Setup\nThe mplBubblegum plugin registers all Bubblegum V2 instructions and the DAS API plugin with your Umi instance.\nsetup.ts\nimport { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\nimport { mplBubblegum } from '@metaplex-foundation/mpl-bubblegum'\n\nimport { keypairIdentity } from '@metaplex-foundation/umi'\n\nconst umi = createUmi('https://api.devnet.solana.com')\n\n.use(mplBubblegum())\n\n.use(keypairIdentity(yourKeypair))\n\nCreate a Bubblegum Tree\ncreateTree allocates a new merkle tree on-chain and registers it as a Bubblegum V2 tree. Tree parameters are permanent — choose them carefully before creating.\ncreate-tree.ts\nimport { createTree } from '@metaplex-foundation/mpl-bubblegum'\n\nimport { generateSigner } from '@metaplex-foundation/umi'\n\nconst merkleTree = generateSigner(umi)\n\nawait createTree(umi, {\n\nmerkleTree,\n\nmaxDepth: 14, // tree holds 2^14 = 16,384 cNFTs\n\nmaxBufferSize: 64, // concurrent writes per block\n\ncanopyDepth: 10, // cached upper nodes (reduces proof size in txs)\n\npublic: false, // false = only tree creator/delegate can mint\n\n}).sendAndConfirm(umi)\n\nconsole.log('Tree address:', merkleTree.publicKey)\n\npublic: false means only the tree creator (or an approved tree delegate) can mint from the tree. Set public: true to allow anyone to mint. See Create Trees for tree size cost estimates.\n\nMint a Compressed NFT\nMint Without Collection\nmintV2 creates a new cNFT leaf in the specified tree.\nmint-cnft.ts\nimport { mintV2 } from '@metaplex-foundation/mpl-bubblegum'\n\nimport { none } from '@metaplex-foundation/umi'\n\nawait mintV2(umi, {\n\nleafOwner: umi.identity.publicKey,\n\nmerkleTree: merkleTree.publicKey,\n\nmetadata: {\n\nname: 'My Compressed NFT',\n\nuri: 'https://example.com/my-nft.json',\n\nsellerFeeBasisPoints: 500, // 5% royalty\n\ncollection: none(),\n\ncreators: [{ address: umi.identity.publicKey, verified: false, share: 100 }],\n\n},\n\n}).sendAndConfirm(umi)\n\nMint to a Collection\nPass a coreCollection to associate the cNFT with an MPL-Core collection. The collection must have the BubblegumV2 plugin enabled.\nmint-to-collection.ts\nimport { mintV2 } from '@metaplex-foundation/mpl-bubblegum'\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nawait mintV2(umi, {\n\nleafOwner: umi.identity.publicKey,\n\nmerkleTree: merkleTree.publicKey,\n\nmetadata: {\n\nname: 'My Collection cNFT',\n\nuri: 'https://example.com/my-nft.json',\n\nsellerFeeBasisPoints: 500,\n\ncollection: publicKey('YourCollectionAddressHere'),\n\ncreators: [{ address: umi.identity.publicKey, verified: false, share: 100 }],\n\n},\n\ncoreCollection: publicKey('YourCollectionAddressHere'),\n\n}).sendAndConfirm(umi)\n\nInherit royalties from the collection\nWhen coreCollection is set, the SDK's mintV2 helper defaults to inherited royalties if metadata.sellerFeeBasisPoints is omitted. The leaf stores SELLER_FEE_BASIS_POINTS_INHERIT (65535). The collection must have the Royalties plugin and metadata.creators must be empty.\n\n1import { createTreeV2, mintV2, mplBubblegum } from '@metaplex-foundation/mpl-bubblegum'\n\n2import { createCollection, mplCore, ruleSet } from '@metaplex-foundation/mpl-core'\n\n3import { generateSigner, some } from '@metaplex-foundation/umi'\n\n4import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n5\n\n6const umi = createUmi('https://api.devnet.solana.com')\n\n7 .use(mplBubblegum())\n\n8 .use(mplCore())\n\n9\n\n10const merkleTree = generateSigner(umi)\n\n11const collectionSigner = generateSigner(umi)\n\n12\n\n13await createTreeV2(umi, {\n\n14 merkleTree,\n\n15 maxDepth: 5,\n\n16 maxBufferSize: 8,\n\n17}).sendAndConfirm(umi)\n\n18\n\n19// The collection must include BubblegumV2 and Royalties plugins.\n\n20await createCollection(umi, {\n\n21 collection: collectionSigner,\n\n22 name: 'My Collection',\n\n23 uri: 'https://example.com/collection.json',\n\n24 plugins: [\n\n25 { type: 'BubblegumV2' },\n\n26 {\n\n27 type: 'Royalties',\n\n28 basisPoints: 500, // 5%\n\n29 creators: [{ address: umi.identity.publicKey, percentage: 100 }],\n\n30 ruleSet: ruleSet('None'),\n\n31 },\n\n32 ],\n\n33}).sendAndConfirm(umi)\n\n34\n\n35// sellerFeeBasisPoints is omitted — the SDK sends the inherit sentinel (65535).\n\n36await mintV2(umi, {\n\n37 collectionAuthority: umi.identity,\n\n38 leafOwner: umi.identity.publicKey,\n\n39 merkleTree: merkleTree.publicKey,\n\n40 coreCollection: collectionSigner.publicKey,\n\n41 metadata: {\n\n42 name: 'My NFT',\n\n43 uri: 'https://example.com/my-nft.json',\n\n44 collection: some(collectionSigner.publicKey),\n\n45 creators: [], // must be empty when inheriting royalties\n\n46 },\n\n47}).sendAndConfirm(umi)\n\n48\n\n49// cNFT minted with SELLER_FEE_BASIS_POINTS_INHERIT (65535) on the leaf\n\nSee Minting Compressed NFTs — Inheriting royalties for collection setup and constraints.\nGet Asset ID After Minting\nUse parseLeafFromMintV2Transaction to retrieve the leaf schema (including the asset ID) after a mint confirms.\nparse-mint.ts\nimport { mintV2, parseLeafFromMintV2Transaction } from '@metaplex-foundation/mpl-bubblegum'\n\nimport { none } from '@metaplex-foundation/umi'\n\nconst { signature } = await mintV2(umi, {\n\nleafOwner: umi.identity.publicKey,\n\nmerkleTree: merkleTree.publicKey,\n\nmetadata: {\n\nname: 'My Compressed NFT',\n\nuri: 'https://example.com/my-nft.json',\n\nsellerFeeBasisPoints: 500,\n\ncollection: none(),\n\ncreators: [],\n\n},\n\n}).sendAndConfirm(umi)\n\nconst leaf = await parseLeafFromMintV2Transaction(umi, signature)\n\nconsole.log('Asset ID:', leaf.id)\n\nconsole.log('Leaf index:', leaf.nonce)\n\nTransfer a Compressed NFT\ntransferV2 moves ownership of a cNFT to a new wallet. getAssetWithProof fetches all required proof parameters from the DAS API.\ntransfer.ts\nimport { getAssetWithProof, transferV2 } from '@metaplex-foundation/mpl-bubblegum'\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nconst assetWithProof = await getAssetWithProof(umi, assetId, { truncateCanopy: true })\n\nawait transferV2(umi, {\n\n...assetWithProof,\n\nleafOwner: umi.identity, // current owner as signer\n\nnewLeafOwner: publicKey('NewOwnerAddressHere'),\n\n}).sendAndConfirm(umi)\n\nBurn a Compressed NFT\nburnV2 permanently destroys a cNFT and removes its leaf from the tree.\nburn.ts\nimport { getAssetWithProof, burnV2 } from '@metaplex-foundation/mpl-bubblegum'\n\nconst assetWithProof = await getAssetWithProof(umi, assetId, { truncateCanopy: true })\n\nawait burnV2(umi, {\n\n...assetWithProof,\n\nleafOwner: umi.identity, // owner must sign\n\n}).sendAndConfirm(umi)\n\nUpdate a Compressed NFT\nupdateMetadataV2 modifies a cNFT's metadata. Update authority depends on whether the cNFT belongs to a collection — see Update cNFTs for authority rules.\nupdate.ts\nimport {\n\ngetAssetWithProof,\n\nupdateMetadataV2,\n\nUpdateArgsArgs,\n\n} from '@metaplex-foundation/mpl-bubblegum'\n\nimport { some, publicKey } from '@metaplex-foundation/umi'\n\nconst assetWithProof = await getAssetWithProof(umi, assetId, { truncateCanopy: true })\n\nconst updateArgs: UpdateArgsArgs = {\n\nname: some('Updated Name'),\n\nuri: some('https://example.com/updated.json'),\n\n}\n\n// Spread includes currentMetadata (leaf-canonical). Do not pass metadata here.\n\nawait updateMetadataV2(umi, {\n\n...assetWithProof,\n\nleafOwner: assetWithProof.leafOwner,\n\nupdateArgs,\n\ncoreCollection: publicKey('YourCollectionAddressHere'),\n\n}).sendAndConfirm(umi)\n\ngetAssetWithProof.metadata mirrors DAS main fields (resolved when inherited) and keeps type MetadataArgs. currentMetadata is leaf-canonical MetadataArgsV2Args for write instructions (sentinel 65535 when inherited). Optional siblings sellerFeeBasisPointsRaw / creatorsRaw and inherited mirror DAS _raw / inherit detection. Spread ...assetWithProof into writes — do not pass metadata as currentMetadata or as the leaf metadata arg on other instructions.\nDelegate a Compressed NFT\nA leaf delegate can transfer, burn, and freeze a cNFT on the owner's behalf. The delegate resets to the new owner after any transfer.\nApprove a Delegate\napprove-delegate.ts\nimport { getAssetWithProof, delegate } from '@metaplex-foundation/mpl-bubblegum'\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nconst assetWithProof = await getAssetWithProof(umi, assetId, { truncateCanopy: true })\n\nawait delegate(umi, {\n\n...assetWithProof,\n\nleafOwner: umi.identity,\n\npreviousLeafDelegate: umi.identity.publicKey, // current delegate (use owner if none)\n\nnewLeafDelegate: publicKey('DelegateAddressHere'),\n\n}).sendAndConfirm(umi)\n\nRevoke a Delegate\nSet the new delegate to the owner's own address.\nrevoke-delegate.ts\nimport { getAssetWithProof, delegate } from '@metaplex-foundation/mpl-bubblegum'\n\nconst assetWithProof = await getAssetWithProof(umi, assetId, { truncateCanopy: true })\n\nawait delegate(umi, {\n\n...assetWithProof,\n\nleafOwner: umi.identity,\n\npreviousLeafDelegate: currentDelegatePublicKey,\n\nnewLeafDelegate: umi.identity.publicKey, // revoke by delegating to self\n\n}).sendAndConfirm(umi)\n\nCollections\nsetCollectionV2 sets, changes, or removes the MPL-Core collection on a cNFT. See Managing Collections for full details.\nSet or Change a Collection\nset-collection.ts\nimport {\n\ngetAssetWithProof,\n\nsetCollectionV2,\n\n} from '@metaplex-foundation/mpl-bubblegum'\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nconst assetWithProof = await getAssetWithProof(umi, assetId, { truncateCanopy: true })\n\nawait setCollectionV2(umi, {\n\n...assetWithProof,\n\nmetadata: assetWithProof.currentMetadata,\n\nnewCollectionAuthority: newCollectionUpdateAuthority,\n\nnewCoreCollection: publicKey('NewCollectionAddressHere'),\n\n}).sendAndConfirm(umi)\n\nRemove a Collection\nremove-collection.ts\nimport { getAssetWithProof, setCollectionV2 } from '@metaplex-foundation/mpl-bubblegum'\n\nimport { unwrapOption } from '@metaplex-foundation/umi'\n\nconst assetWithProof = await getAssetWithProof(umi, assetId, { truncateCanopy: true })\n\nconst collection = unwrapOption(assetWithProof.currentMetadata.collection)\n\nawait setCollectionV2(umi, {\n\n...assetWithProof,\n\nmetadata: assetWithProof.currentMetadata,\n\nauthority: collectionAuthoritySigner,\n\ncoreCollection: collection!,\n\n}).sendAndConfirm(umi)\n\nFreeze and Thaw\nTwo freeze mechanisms are available. See Freeze cNFTs for the full breakdown of asset-level vs collection-level freeze.\nFreeze a cNFT (Leaf Delegate)\nfreeze.ts\nimport {\n\ngetAssetWithProof,\n\ndelegateAndFreezeV2,\n\n} from '@metaplex-foundation/mpl-bubblegum'\n\nimport { publicKey } from '@metaplex-foundation/umi'\n\nconst assetWithProof = await getAssetWithProof(umi, assetId, { truncateCanopy: true })\n\n// Delegates and freezes in one instruction\n\nawait delegateAndFreezeV2(umi, {\n\n...assetWithProof,\n\nleafOwner: umi.identity,\n\nnewLeafDelegate: publicKey('FreezeAuthorityAddressHere'),\n\n}).sendAndConfirm(umi)\n\nThaw a cNFT\nthaw.ts\nimport { getAssetWithProof, thawV2 } from '@metaplex-foundation/mpl-bubblegum'\n\nconst assetWithProof = await getAssetWithProof(umi, assetId, { truncateCanopy: true })\n\nawait thawV2(umi, {\n\n...assetWithProof,\n\nleafDelegate: umi.identity, // freeze authority must sign\n\n}).sendAndConfirm(umi)\n\nCreate a Soulbound cNFT\nA soulbound cNFT is permanently non-transferable. The collection must have the PermanentFreezeDelegate plugin enabled. See Freeze cNFTs for setup details.\nsoulbound.ts\nimport { getAssetWithProof, setNonTransferableV2 } from '@metaplex-foundation/mpl-bubblegum'\n\nconst assetWithProof = await getAssetWithProof(umi, assetId, { truncateCanopy: true })\n\nawait setNonTransferableV2(umi, {\n\n...assetWithProof,\n\n// permanent freeze delegate must sign\n\n}).sendAndConfirm(umi)\n\nsetNonTransferableV2 is irreversible. The cNFT cannot be made transferable again after this call.\n\nVerify Creators\nverifyCreatorV2 sets the verified flag on a creator entry. The creator being verified must sign the transaction. See Verify Creators for details.\nVerify a Creator\nverify-creator.ts\nimport {\n\ngetAssetWithProof,\n\nverifyCreatorV2,\n\n} from '@metaplex-foundation/mpl-bubblegum'\n\nconst assetWithProof = await getAssetWithProof(umi, assetId, { truncateCanopy: true })\n\nawait verifyCreatorV2(umi, {\n\n...assetWithProof,\n\nmetadata: assetWithProof.currentMetadata,\n\ncreator: umi.identity, // the creator being verified must sign\n\n}).sendAndConfirm(umi)\n\nUnverify a Creator\nunverify-creator.ts\nimport {\n\ngetAssetWithProof,\n\nunverifyCreatorV2,\n\n} from '@metaplex-foundation/mpl-bubblegum'\n\nconst assetWithProof = await getAssetWithProof(umi, assetId, { truncateCanopy: true })\n\nawait unverifyCreatorV2(umi, {\n\n...assetWithProof,\n\nmetadata: assetWithProof.currentMetadata,\n\ncreator: umi.identity,\n\n}).sendAndConfirm(umi)\n\nFetching cNFTs\nThe DAS API plugin is automatically registered by mplBubblegum(). See Fetch cNFTs for the full breakdown of available methods.\ngetAssetWithProof and inherited royalties\ngetAssetWithProof combines getAsset and getAssetProof into the parameter shape expected by write instructions.\nFieldPurpose\nmetadata\nMirrors DAS main fields (MetadataArgs): sellerFeeBasisPoints / creators from royalty.basis_points / creators (resolved when inherited). Use for reading / UI.\n\ncurrentMetadata\nLeaf-canonical MetadataArgsV2Args for write instructions and hashing (sentinel 65535 when inherited). Included when you spread ...assetWithProof.\n\nsellerFeeBasisPointsRaw / creatorsRaw\nOptional DAS-aligned leaf siblings (basis_points_raw / creators_raw). Set when DAS provides _raw / inherited SFBP; omitted otherwise (same as DAS).\n\ninherited\nSugar for inherit detection (rpcAsset.royalty.inherited / sentinel).\n\nrpcAsset\nFull DAS response. Same main / _raw split as above.\n\nupdateMetadataV2 names its existing-leaf argument currentMetadata (IDL). Spreading ...assetWithProof supplies it. Instructions that take a leaf metadata arg (setCollectionV2, verifyCreatorV2, …) should use assetWithProof.currentMetadata. Do not pass display metadata into those args.\nClients reading DAS directly should follow Reading Inherited Royalties.\nVersion requirements\ncurrentMetadata ships in @metaplex-foundation/mpl-bubblegum 5.1.0. The sellerFeeBasisPointsRaw, creatorsRaw, and inherited siblings are not published yet — they arrive with mpl-bubblegum#173. Until then, read the same values from rpcAsset.royalty.basis_points_raw, rpcAsset.creators_raw, and rpcAsset.royalty.inherited, which need @metaplex-foundation/digital-asset-standard-api ≥ 2.1.0.\n\n1import { dasApi } from '@metaplex-foundation/digital-asset-standard-api'\n\n2import { getAssetWithProof, mplBubblegum } from '@metaplex-foundation/mpl-bubblegum'\n\n3import { publicKey } from '@metaplex-foundation/umi'\n\n4import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n5\n\n6// getAssetWithProof calls getAsset and getAssetProof, so this needs a\n\n7// DAS-capable RPC. The public Solana endpoints do not serve DAS methods.\n\n8const umi = createUmi('YOUR_DAS_ENABLED_RPC_URL')\n\n9 .use(mplBubblegum())\n\n10 .use(dasApi())\n\n11\n\n12const assetId = publicKey('YOUR_ASSET_ID')\n\n13\n\n14const assetWithProof = await getAssetWithProof(umi, assetId, {\n\n15 truncateCanopy: true,\n\n16})\n\n17\n\n18// Reading: metadata mirrors DAS main / resolved fields\n\n19console.log(assetWithProof.metadata.sellerFeeBasisPoints) // e.g. 500 when inherited\n\n20console.log(assetWithProof.metadata.creators) // collection payees when inherited\n\n21console.log(assetWithProof.inherited) // true\n\n22\n\n23// Writes / hashing: currentMetadata is leaf-canonical (V2)\n\n24console.log(assetWithProof.currentMetadata.sellerFeeBasisPoints) // 65535 when inherited\n\n25console.log(assetWithProof.currentMetadata.creators) // usually []\n\n26\n\n27// Optional DAS-aligned _raw siblings (same leaf values)\n\n28console.log(assetWithProof.sellerFeeBasisPointsRaw) // 65535 when inherited\n\n29console.log(assetWithProof.creatorsRaw) // usually []\n\n30\n\n31// Explicit DAS raw + flag\n\n32console.log(assetWithProof.rpcAsset.royalty?.basis_points_raw) // 65535\n\n33console.log(assetWithProof.rpcAsset.creators_raw) // []\n\n34console.log(assetWithProof.rpcAsset.royalty?.inherited) // true\n\n35\n\n36// 500\n\n37// [{ address: '...', share: 100, verified: true }]\n\n38// true\n\n39// 65535\n\n40// []\n\n41// 65535\n\n42// []\n\n43// 65535\n\n44// []\n\n45// true\n\nFetch a Single cNFT\nfetch-asset.ts\nimport { publicKey } from '@metaplex-foundation/umi'\n\nconst asset = await umi.rpc.getAsset(assetId)\n\nconsole.log('Owner:', asset.ownership.owner)\n\nconsole.log('Name:', asset.content.metadata.name)\n\nFetch cNFTs by Owner\nfetch-by-owner.ts\nimport { publicKey } from '@metaplex-foundation/umi'\n\nconst result = await umi.rpc.getAssetsByOwner({\n\nowner: publicKey('OwnerAddressHere'),\n\n})\n\nconsole.log('cNFTs owned:', result.items.length)\n\nFetch cNFTs by Collection\nfetch-by-collection.ts\nimport { publicKey } from '@metaplex-foundation/umi'\n\nconst result = await umi.rpc.getAssetsByGroup({\n\ngroupKey: 'collection',\n\ngroupValue: publicKey('CollectionAddressHere'),\n\n})\n\nconsole.log('cNFTs in collection:', result.items.length)\n\nDerive Leaf Asset ID from Tree and Index\nfind-asset-id.ts\nimport { findLeafAssetIdPda } from '@metaplex-foundation/mpl-bubblegum'\n\nconst [assetId] = await findLeafAssetIdPda(umi, {\n\nmerkleTree: merkleTree.publicKey,\n\nleafIndex: 0,\n\n})\n\nTransaction Patterns\nHandling \"Transaction Too Large\" Errors\nMerkle proofs grow with tree depth. Pass truncateCanopy: true to getAssetWithProof to automatically remove proof nodes already cached in the canopy, reducing transaction size.\ntruncate-canopy.ts\nimport { getAssetWithProof } from '@metaplex-foundation/mpl-bubblegum'\n\n// truncateCanopy fetches tree config and removes redundant proof nodes\n\nconst assetWithProof = await getAssetWithProof(umi, assetId, { truncateCanopy: true })\n\nFor very deep trees where even a truncated proof exceeds the transaction limit, use versioned transactions with Address Lookup Tables.\nSend and Confirm\nsend-and-confirm.ts\nconst result = await mintV2(umi, { ... }).sendAndConfirm(umi)\n\nconsole.log('Signature:', result.signature)\n\nBuild Without Sending\nbuild-only.ts\nconst tx = await mintV2(umi, { ... }).buildAndSign(umi)\n\n// send later: await umi.rpc.sendTransaction(tx)\n\nCommon Errors\nTransaction too large\nThe merkle proof exceeds the 1232-byte transaction limit. Use { truncateCanopy: true } in getAssetWithProof, or implement versioned transactions with Address Lookup Tables.\nInvalid proof\nThe proof is stale — the tree was modified after you fetched the proof. Always call getAssetWithProof immediately before submitting a write transaction.\nLeaf already exists / Invalid leaf\nThe asset ID or leaf index is incorrect. Re-derive the asset ID using findLeafAssetIdPda or re-fetch via getAssetsByOwner.\nInvalidAuthority\nYou are not the owner, delegate, or required authority for this instruction. Verify the correct signer is set as leafOwner or leafDelegate.\nTree is full\nThe merkle tree has reached its maxDepth capacity (2^maxDepth leaves). Create a new tree to continue minting.\nAccount not found on DAS fetch\nYour RPC provider may not support the Metaplex DAS API. Switch to a compatible RPC provider.\nNotes\ngetAssetWithProof is required before nearly every write instruction. Always call it immediately before submitting to avoid stale proof errors.\nProofs fetched via DAS can become stale if the tree is modified between fetch and submit. High-concurrency scenarios should fetch and submit in the same atomic flow.\nsetNonTransferableV2 (soulbound) is irreversible. There is no way to restore transferability once set.\nDelegate authority resets to the new owner after any transferV2. The new owner must re-delegate if needed.\nThis SDK targets Bubblegum V2 (LeafSchemaV2). It is not compatible with Bubblegum V1 trees or the decompression workflow.\nCollections used with cNFTs must have the BubblegumV2 plugin enabled. Standard MPL-Core collections without this plugin cannot be used.\nQuick Reference\nBubblegum V2 Functions\nFunctionPurpose\ncreateTree\nCreate a new Bubblegum V2 merkle tree\n\nmintV2\nMint a new compressed NFT\n\ntransferV2\nTransfer cNFT ownership\n\nburnV2\nPermanently destroy a cNFT\n\nupdateMetadataV2\nUpdate cNFT metadata (name, URI, creators, royalties)\n\ndelegate\nApprove or revoke a leaf delegate\n\nsetTreeDelegate\nApprove or revoke a tree delegate\n\nsetCollectionV2\nSet, change, or remove an MPL-Core collection\n\nfreezeV2\nFreeze a cNFT (requires existing leaf delegate)\n\nthawV2\nThaw a frozen cNFT\n\ndelegateAndFreezeV2\nDelegate and freeze in a single instruction\n\nsetNonTransferableV2\nMake a cNFT permanently soulbound (irreversible)\n\nverifyCreatorV2\nSet verified flag on a creator entry\n\nunverifyCreatorV2\nRemove verified flag from a creator entry\n\ngetAssetWithProof\nFetch proof parameters; metadata for display, currentMetadata for writes; optional _raw siblings + inherited\n\nSELLER_FEE_BASIS_POINTS_INHERIT\nSentinel constant (65535) for royalties inherited from an MPL-Core collection\n\nfindLeafAssetIdPda\nDerive a cNFT asset ID from tree address and leaf index\n\nparseLeafFromMintV2Transaction\nExtract leaf schema (including asset ID) from a mint transaction\n\nMinimum Dependencies\npackage.json\n{\n\n\"dependencies\": {\n\n\"@metaplex-foundation/mpl-bubblegum\": \"^5.0.0\",\n\n\"@metaplex-foundation/umi\": \"^1.0.0\",\n\n\"@metaplex-foundation/umi-bundle-defaults\": \"^1.0.0\"\n\n}\n\n}\n\nProgram Addresses\nProgramAddress\nMPL-Bubblegum V2\nBGUMAp9Gq7iTEuizy4pqaxsTyUCBK68MDfK752saRPUY\n\nSPL Account Compression\ncmtDvXumGCrqC1Age74AVPhSRVXJMd8PJS91L8KbNCK\n\nSPL Noop\nnoopb9bkMVfRPU8AsbpTUg8AQkHtKwMYZiFUjNRtMmV\n\nTree Size Reference\nMax DepthCapacityApprox. Cost\n14\n16,384\n~0.34 SOL\n\n17\n131,072\n~1.1 SOL\n\n20\n1,048,576\n~8.5 SOL\n\n24\n16,777,216\n~130 SOL\n\n30\n1,073,741,824\n~2,000 SOL\n\nFAQ\nWhat is the Bubblegum V2 JavaScript SDK?\nThe Bubblegum V2 JavaScript SDK (@metaplex-foundation/mpl-bubblegum) is a TypeScript library for creating and managing compressed NFTs on Solana. Built on the Umi framework, it provides type-safe wrappers for all MPL-Bubblegum V2 program instructions and includes the DAS API plugin automatically.\nDo I need a special RPC provider to use this SDK?\nYes. Compressed NFTs require an RPC provider supporting the Metaplex DAS API to index and fetch cNFT data. Standard Solana RPCs do not support DAS. See the RPC Providers page for compatible options (Helius, Triton, Shyft, and others).\nHow do I get the asset ID of a cNFT after minting?\nUse parseLeafFromMintV2Transaction with the confirmed transaction signature. It decodes the mint transaction and returns the full leaf schema including leaf.id (the asset ID) and leaf.nonce (the leaf index).\nWhy do I get a \"Transaction too large\" error?\nMerkle proofs grow with tree depth. Pass { truncateCanopy: true } to getAssetWithProof to automatically remove proof nodes cached in the on-chain canopy. For very deep trees, use versioned transactions with Address Lookup Tables.\nCan I use this SDK with Bubblegum V1 trees?\nNo. This SDK targets Bubblegum V2 which uses LeafSchemaV2 and V2 merkle trees. Use the legacy Bubblegum SDK for V1 trees. V2 trees and V1 trees are not cross-compatible.\nWhat is getAssetWithProof and why do I need it?\ngetAssetWithProof is a helper that calls both getAsset and getAssetProof on the DAS API and parses the responses into the exact parameter shape expected by Bubblegum V2 write instructions. Almost every mutation instruction (transfer, burn, update, delegate, freeze, verify) requires these parameters. Always call it immediately before submitting to avoid stale proof errors.\nGlossary\nTermDefinition\nUmi\nMetaplex's framework for building Solana applications; handles wallet connections, RPC, and transaction building\n\nmplBubblegum\nThe Umi plugin that registers all Bubblegum V2 instructions and the DAS API plugin\n\ncNFT\nCompressed NFT — stored as a hashed leaf in an on-chain merkle tree instead of a dedicated account\n\nMerkle Tree\nOn-chain account storing hashed NFT data as leaves; created with createTree\n\nLeaf\nA single cNFT entry in the merkle tree, identified by its leaf index\n\nProof\nA list of sibling hashes enabling cryptographic verification that a leaf belongs to a tree\n\nCanopy\nCached upper nodes of the merkle tree stored on-chain to reduce required proof size in transactions\n\nLeafSchemaV2\nThe V2 leaf data structure containing id, owner, delegate, nonce, data hash, creator hash, collection hash, asset data hash, and flags\n\ngetAssetWithProof\nSDK helper that fetches and parses all DAS API data needed for write instructions\n\nDAS API\nDigital Asset Standard API — RPC extension for indexing and fetching cNFT data\n\nTreeConfig\nPDA derived from the merkle tree address storing Bubblegum tree configuration\n\nLeaf Delegate\nAccount authorized by the cNFT owner to transfer, burn, or freeze the cNFT\n\nTree Delegate\nAccount authorized by the tree creator to mint cNFTs from a private tree\n\nSoulbound\nA permanently non-transferable cNFT set via setNonTransferableV2 — irreversible","tokens":6583,"crawled_at":1791195750655}
+{"id":10559,"url":"https://blog.trailofbits.com/2024/12/09/35-more-semgrep-rules-infrastructure-supply-chain-and-ruby","domain":"blog.trailofbits.com","chapter":"security_audits","title":"35 more Semgrep rules: infrastructure, supply chain, and Ruby - The Trail of Bits Blog","text":"Page content\n\nWe are publishing another set of custom Semgrep rules, bringing our total number of public rules to 115. This blog post will briefly cover the new rules, then explore two Semgrep features in depth: regex mode (especially how it compares against generic mode), and HCL language support for technologies such as Terraform and Nomad. With these features, we can search for security vulnerabilities in more than just application code. This new release joins our existing collection of Semgrep rules, our public CodeQL queries, and our Testing Handbook as part of our long-term effort to share our technical expertise with the security community.\nSemgrep is a vast and capable tool, and it contains many nooks and crannies that can be exploited to get the most value possible out of a static analysis tool. Like our previous Semgrep rules release post, this post will highlight some interesting Semgrep functionality. Publicly releasing rules is a great start, but we feel that we can do even better by explaining why rules are written the way they are.\nFor this release, we focused on supply chain issues related to a lack of short-lived OIDC tokens in GitHub Actions; infrastructure concerns in Terraform code, Nomad jobs, and insecure database connections; and general application security concerns in Ruby code. Many of these Ruby rules were written during our recent Ruby Central (rubygems.org) audit. We will be publishing more information about this audit shortly.\nWithout further ado, here are our new rules:\nModeRule IDRule description\nRuby\naction-dispatch-insecure-ssl\nFound Rails application with insecure SSL setting.\n\nRuby\naction-mailer-insecure-tls\nFound ActionMailer SMTP configuration with insecure TLS setting. These settings do not require a successful, encrypted, verified TLS connection is made. Set enable_starttls: true and openssl_verify_mode to verify peer.\n\nRuby\nactive-record-encrypts-misorder\nFound an ActiveRecord value with encryption before serialization. The declaration of the serialized attribute should go before the encryption declaration.\n\nRuby\nactive-record-hardcoded-encryption-key\nFound hard-coded ActiveRecord encryption key.\n\nRuby\nglobal-timeout\nFound Timeout::timeout (or timeout) use. Setting a global timeout can cause an exception to be raised anywhere in the passed block of code. This precludes any possible clean up action typically associated with rescuing from exceptions. This can lead to denial-of-service, data integrity failure, and general availability concerns. Instead prefer to use the library’s built in timeout functionality, if it has any, to ensure processing happens as expected. If it does not have built in timeout functionality, then consider implementing it.\n\nRuby\nfaraday-disable-verification\nFound Faraday HTTP request disabling SSL/TLS verification.\n\nRuby\nruby-saml-skip-validation\nSAML response validation disabled for $KEY.\n\nRuby\nyaml-unsafe-load\nFound YAML call to unsafe_load. This can lead to deserialization bugs and RCE.\n\nRuby\nrails-cookie-attributes\nFound Rails cookie set with insecure attribute.\n\nRuby\nrails-cache-store-marshal\nFound Rails cache store configured to allow Marshaling. As of Rails 7.1 the default serializer is :marshal_7_1. If an attacker can inject data into the cache store (SSRF, etc.), then they can achieve code execution when the object is later deserialized. Consider using the :message_pack serializer or a custom serializer.\n\nRuby\njson-create-deserialization\nFound json_create class method. This implies custom JSON deserialization is occuring. This can lead to RCE and other deserialization-type bugs. Usage should be audited and, at least, fuzzed.\n\nRuby\ninsecure-rails-cookie-session-store\nFound Rails session cookie missing SameSite=Secure. As of Rails 7.2, session cookies default to SameSite=Lax.\n\nRuby\nrest-client-disable-verification\nFound RestClient HTTP request disabling SSL/TLS verification.\n\nRegex\npostgres-insecure-sslmode\nFound PostgreSQL connection string disabling SSL verification.\n\nRegex\nmongodb-insecure-transport\nFound insecure MongoDB connection, prefer TLS encrypted transport by setting the tls=true connection option and ensuring proper verification.\n\nRegex\nmysql-insecure-sslmode\nFound MySQL connection string disabling SSL verification.\n\nGeneric\namqp-unencrypted-transport\nFound unencrypted AMQP connection, prefer TLS encrypted amqps:// transport.\n\nGeneric\nredis-unencrypted-transport\nFound unencrypted Redis connection, prefer TLS encrypted rediss:// transport.\n\nGeneric\nnode-disable-certificate-validation\nSetting this environment variable disables TLS certificate validation. This makes TLS, and HTTPS by extension, insecure. The use of this environment variable is strongly discouraged.\n\nHCL\naws-oidc-role-policy-duplicate-condition\nFound AWS role policy for GitHub Actions with duplicate condition. This overrides previous conditions, and the last condition with the duplicated key “wins.” This likely breaks access controls and allows unauthorized access.\n\nHCL\naws-oidc-role-policy-missing-sub\nFound AWS role policy for GitHub Actions missing OIDC subject. This means any GitHub repository can assume this role in CI.\n\nHCL\nvault-hardcoded-token\nFound Terraform Vault instance with hard-coded token.\n\nHCL\nvault-skip-tls-verify\nFound Terraform Vault instance with TLS verification disabled.\n\nHCL\nroot-user\nFound Nomad task using root user.\n\nHCL\ndocker-hardcoded-password\nFound Nomad task using Docker auth with hard-coded password.\n\nHCL\ndocker-privileged-mode\nFound Nomad task using Docker containers in privileged mode.\n\nHCL\ntls-hostname-verification-disabled\nFound Nomad tls block with server hostname verification disabled.\n\nHCL\npodman-tls-verify-disabled\nFound Nomad task using Podman with registry TLS verification disabled.\n\nYAML\njfrog-hardcoded-credential\nFound long-term access key. Instead prefer JFrog temporary OIDC security credentials.\n\nYAML\naws-secret-key\nFound long-term access key. Instead prefer AWS role assumption and temporary OIDC security credentials.\n\nYAML\ngcp-credentials-json\nFound long-term access key. Instead prefer GCP workload identity federation and temporary OIDC security credentials.\n\nYAML\nrubygems-publish-key\nFound long-term access key. Instead prefer RubyGems trusted publishing and temporary OIDC security credentials.\n\nYAML\nvault-token\nFound long-term access key. Instead prefer Vault role assumption and temporary OIDC security credentials.\n\nYAML\npypi-publish-password\nFound long-term access key. Instead prefer PyPI trusted publishing and temporary OIDC security credentials.\n\nYAML\nazure-principal-secret\nFound long-term access key. Instead prefer Azure subscription ID and temporary OIDC security credentials.\n\nSemgrep isn’t just for programming languages\nThe first post in this series included perspectives on two lesser-known Semgrep features: generic mode and YAML support. This post introduces two additional considerations: regular expressions vs. generic mode and HashiCorp Configuration Language (HCL) support for infrastructure-as-code (IaC) security. We will continue the trend of bringing Semgrep to all forms of textual data.\nHeuristics: Regular expressions vs. generic-mode\nRegular expression patterns are another lesser-known feature of Semgrep. This is the so-called pattern-regex operator and regex language. But why would you want to use regular expressions in Semgrep rules? Doesn’t that defeat the purpose of static analysis tools like Semgrep? Why not simply use ripgrep or classic grep? Doesn’t generic mode obviate the need for regex mode?\nThe following heuristics will help you understand when to use regex mode. The more “yeses” you answer below, the more likely you should be using regex mode.\nHeuristic #1: Does the text you are looking for generally span a single line of code?\nDealing with multi-line whitespace in a regular expression is a pain. If you find yourself searching for multi-line patterns, and language-specific rules aren’t possible, then you will probably be best served by generic mode. So remember: when using regex mode, the text you’re searching for will almost always span a single line.\nHeuristic #2: Does this pattern exist in many languages or types of text files?\nThe beauty of Semgrep is that it’s a one-stop-shop for all things textual analysis. If the text you are searching for may exist in many languages, then it may be a good fit for regex mode. For example, consider URL parameters. If you’re searching for, say, sslmode=disable, then the following regular expression would be a good start: [?&]sslmode=(disable|allow|prefer). This is great because it will find this insecure URL parameter in any connection URI to any PostgreSQL library in any language. We don’t have to write separate rules for separate libraries and languages. It will also find this pattern in shell scripts, documentation, CI jobs, and more.\nHeuristic #3: Do you want to share your regular expressions with others?\nAgain, the beauty of Semgrep is that it consolidates the functionality of tools like ripgrep or classic grep under a single tool. ripgrep can be useful when you’re quickly iterating on regular expressions and searching through your code for patterns, but Semgrep rules really shine once it comes time to codify, test, and publish a regex. Your regex findings will exist next to your Python and Kubernetes findings, and you can track all of your findings and manage rules from a single location.\nHeuristic #4: Do you need to match specific characters or character classes?\nRegex mode and generic mode often serve similar needs. Our previous post discussed the advantages of generic mode, so when should you use regex mode? Regex mode is preferred over generic mode when you would like to match specific characters or character classes, or use other regular expression functionality such as alternation. For example, in the sslmode regular expression above, we search for sslmode prefixed by a character class with ? and &. These two prefixes give us additional confidence that what we find will in fact be a URL parameter. As far as we know, there is not an easy way to express this in generic mode. We can always use pattern-either, but this can get quite verbose for more complex expressions. On the other hand, generic mode’s primary advantage is that it supports the ellipsis operator (i.e., ...), which allows easily skipping non-matching elements and whitespace used in multi-line patterns.\nAs you can see, there are often multiple ways to approach searching for specific code patterns in Semgrep. The heuristics above provide a good baseline for when you may want to use regex mode. The more important consideration is that regex mode exists, and it’s a valuable tool in your toolbelt when searching through textual data.\nHCL support and IaC security\nInfrastructure as Code (IaC) has transformed cloud management. It brings faster deployments, improved consistency and repeatability, and better security through version-control environments that previously relied on manual configurations. By codifying infrastructure, organizations can seamlessly integrate these definitions with CI/CD pipelines thus enabling automated testing, deployment, and static analysis.\nHashiCorp Configuration Language (HCL) is foundational to many IaC tools, including Terraform, Nomad, and Consul. Recognizing the increasing importance of IaC, Semgrep introduced HCL support back in 2021. With dedicated HCL support, Semgrep now allows for a unified approach, bringing the same level of scrutiny to both application code and infrastructure configurations, ensuring they work together harmoniously within CI/CD pipelines.\nWe’ve learned that even the most straightforward Semgrep rules can uncover significant issues that continue to pose risks in 2024. Take, for example, the common practice of disabling TLS verification during development. If this configuration is inadvertently deployed, it could expose sensitive data. Here’s how easy it is to detect such vulnerabilities in Vault infrastructure with Semgrep:\nrules:\n- id: vault-skip-tls-verify\nmessage: |\nFound Terraform Vault instance with TLS verification disabled\nlanguages: [hcl]\nseverity: WARNING\npatterns:\n- pattern-inside: provider \"vault\" { ... }\n- pattern: skip_tls_verify = true\nFigure 1: Semgrep rule searching for disabled TLS verification (hcl/terraform/vault-skip-tls-verify.yaml)Another frequent misstep is hard-coding credentials—a security risk that Semgrep can easily catch:\nrules:\n- id: vault-hardcoded-token\nmessage: |\nFound Terraform Vault instance with hardcoded token\nlanguages: [hcl]\nseverity: WARNING\npatterns:\n- pattern-inside: provider \"vault\" { ... }\n- pattern: token = \"...\"\nFigure 2: Semgrep rule search for hardcoded Vault tokens (hcl/terraform/vault-hardcoded-token.yaml)By coupling this step with configuring your CI/CD pipelines to block PRs with unresolved Semgrep findings (one of our recommended practices), you can easily keep these issues out of production infrastructure.\nHCL’s structured nature also makes it particularly effective for detecting more complex patterns and ensuring that we keep false positives as low as possible. For instance, consider the following rule that identifies AWS role policies for GitHub Actions that are missing the OIDC subject—a critical misconfiguration that could allow any GitHub repository to assume the role in CI:\nrules:\n- id: aws-oidc-role-policy-missing-sub\nmessage: |\nFound AWS role policy for GitHub Actions missing OIDC subject. This\nmeans any GitHub repository can assume this role in CI.\nlanguages: [hcl]\nseverity: WARNING\npatterns:\n- pattern-inside: |\n{\n...\nStatement = [...]\n...\n}\n- pattern-inside: |\n{\n...,\n\"Action\": \"sts:AssumeRoleWithWebIdentity\",\n...\n}\n- pattern: |\n{\n...\n\"Condition\": {\n...\n\"StringEquals\": {\n...\n\"token.actions.githubusercontent.com:aud\": ...,\n...\n}\n...\n}\n...\n}\n- pattern-not: |\n{\n...\n\"Condition\": {\n...\n\"StringEquals\": {\n...\n\"token.actions.githubusercontent.com:sub\": ...,\n...\n\"token.actions.githubusercontent.com:aud\": ...,\n...\n}\n...\n}\n...\n}\n# Remain pattern-nots truncated to save space\nFigure 3: Semgrep rule searching for missing OIDC subjects (hcl/terraform/aws-oidc-role-policy-missing-sub.yaml)Role policies for GitHub Actions can be configured in many ways, and we can use pattern-inside and pattern-not to properly contextualize the pattern we are looking for (i.e., instances where the subject is not defined). This rule is a powerful example of how Semgrep can help enforce security policies and prevent configuration errors that could lead to serious vulnerabilities.\nText is the universal interface\nIf text is the universal interface, then Semgrep can help secure arbitrary interfaces, from bytes and strings to IaC, YAML, and more. Combining the power of Semgrep with regular expressions, generic mode, YAML, and IaC support allows us to go beyond just code in programming languages. As the industry moves everything toward “as-code” solutions, we need to be able to apply scalable tooling to domains like supply chain, CI/CD, and IaC.\nWith IaC, you can apply the same rigor of static analysis to your infrastructure as you do to your application code, catching issues early and avoiding costly mistakes in production—“shifting left,” as it were. Manual audits and dynamic scans against production environments are slow and do not scale well. We encourage you to try out our newly released Terraform and Nomad rules, explore Semgrep’s terraform rules, and consider incorporating them into your projects. To our knowledge, these are the first open-source Semgrep rules targeting Nomad—a fact we’re excited to share with the community, hoping to inspire others to build upon them.\nIf you’d like to read more about our work on Semgrep, we have used its capabilities in several ways, such as securing machine learning pipelines, discovering goroutine leaks, and securing Apollo GraphQL servers.\nContact us if you’re interested in custom Semgrep rules for your project!","tokens":3990,"crawled_at":1791195756065}
+{"id":10560,"url":"https://docs.sui.io/develop/objects","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Objects | Sui Documentation","text":"The Sui objectObjectThe basic unit of storage on Sui. model is the foundation of how Sui stores and manages on-chain state. Objects have unique IDs, owners, and types. Transactions consume and produce objects, and every object change is recorded on-chain.\n\nWhat is a Sui object?​\n\nOn Sui, the base unit of storage is an object. Unlike account-based blockchains where state lives in a single global store keyed by addressAddressA unique, anonymous identity on a blockchain network., Sui organizes state around individual objects. Each object has:\n\nA globally unique ID\n\nAn owner (an address, another object, or the network itself)\n\nA type defined by a Move packagePackageSmart contracts on Sui.\n\nA version that increments with each mutation\n\nMove packages are also objects. When you publish a Move package to Sui, the package becomes an immutable object stored onchain. The functions and types defined in that package are then available to other transactions.\n\nTransactions on Sui take objects as inputs and produce objects as outputs. When a transactionTransactionA number of commands that execute on inputs to define the result of the transaction. runs, it can read, mutate, transferTransferChanging the owner of an asset., or delete its input objects. The resulting objects become available for future transactions.\n\nObject ownership determines how a transaction can use an object. An address-owned object can only be used by transactions signed by the owner. A shared object can be used by any transaction, but requires consensusConsensusThe process by which the majority of nodes agree on the current state of the network to order concurrent access.\n\nThe following example shows a simple MoveMoveAn open source programming language used for all activity on Sui. struct that defines a custom object type:\n\npublic struct TodoList has key {\nid: UID,\nitems: vector<String>,\n}\n\nThe key ability marks this struct as a Sui object. The id field of type UID gives each instance a unique on-chain identifier. When you create a value of this type and transfer it to an address, it becomes an owned object on Sui.\n\nTypes of Object Ownership\nIn this section\nAddress-Owned Objects\nShared Objects\nImmutable Objects\nWrapped Objects\nParty Objects\n\n→\nDerived Objects\nDerived objects enable deterministic object addresses, Transfer-to-Object capabilities, guaranteed uniqueness, and native parallelization for building scalable composable systems on Sui.\n→\nDynamic Fields\nDynamic fields and dynamic object fields on Sui are added and removed dynamically, affect gas only when accessed, and store heterogeneous values.\n→\nVersioning\nSui versions every onchain object by (ID, version) pair using Lamport timestamps, with objects versioned either through the fastpath or through consensus depending on their ownership type.\n→\nOwned Compared With Shared\nThe same trustless swap service implemented 2 ways, once with address-owned objects and a custodian and once with a shared object, to show the trade-offs between the 2 ownership models.\n→\nObject Display\nIn this section\nWhat is Object Display?\nCreating Displays\nObject Display Templates\n\n→\nTransferring Objects\nIn this section\nCustom Transfer Rules\nTransfer Policies\nTransfer to Object\nSimulating References\n\n→\n\nWhat is a Sui object?\n\nWas this page helpful?","tokens":823,"crawled_at":1791195765653}
+{"id":10561,"url":"https://www.metaplex.com/docs/smart-contracts/bubblegum-v2","domain":"www.metaplex.com","chapter":"docs","title":"Bubblegum V2 - Compressed NFTs on Solana - Metaplex","text":"Summary\nBubblegum V2 (MPL-Bubblegum) is the Metaplex program for creating and managing compressed NFTs on Solana. It stores NFT data as hashed leaves in on-chain merkle trees, reducing minting costs by orders of magnitude compared to traditional NFTs.\nMint millions of cNFTs for a fraction of the cost of standard Solana NFTs (~0.00001 SOL per cNFT in large trees)\nNew in V2: freeze/thaw, soulbound NFTs, MPL-Core collections, royalty enforcement, permanent delegates\nRequires an RPC provider supporting the Metaplex DAS API for indexing and fetching cNFT data\nUses LeafSchemaV2 with V2 Merkle Trees — not backward-compatible with V1 trees\nBubblegum V2 is the latest iteration of the Metaplex Protocol program for creating and interacting with compressed NFTs (cNFTs) on Solana. Built for large-scale operations, Bubblegum V2 preserves all the benefits of the original Bubblegum while introducing powerful new features. Compressed NFTs make it possible to scale the creation of NFTs to new orders of magnitude by rethinking the way we store data onchain.\nPlease note that certain Bubblegum V2 instructions will require protocol fees. Please review the Protocol Fees page for up-to-date information.\n\nGetting Started\nFind the language or library of your choice and get started with compressed NFTs.\n\nAPI reference\nLooking for something specific? Have a peak at our API References and find your answer.\n\nEcosystem Compatibility\nAdoption in progress\nBubblegum V2 is a new standard and ecosystem adoption is ongoing. Wallets and marketplaces that support Bubblegum V1 cNFTs may not yet fully support V2. Verify compatibility with your target platforms before launching user-facing features that depend on wallet display or marketplace trading.\nIf you need broad wallet and marketplace support today, consider using MPL-Core instead — Core assets are widely supported across the Solana ecosystem.\n\nPlatformTypeRead / DisplayTransfer / Trade\nSolflare\nWallet\n✅ Supported\n❌ Not yet supported\n\nPhantom\nWallet\n✅ Supported\n❌ Not yet supported\n\nBackpack\nWallet\n✅ Supported\n❌ Not yet supported\n\nMagic Eden\nMarketplace\n❌ Not yet supported\n❌ Not yet supported\n\nTensor\nMarketplace\n❌ Not yet supported\n❌ Not yet supported\n\nWhat's New in Bubblegum V2\nBubblegum V2 builds on the foundation of the original Bubblegum program while introducing several powerful new features:\nFreeze and Thaw Functionality: Two types of freeze/thaw are available: 1) cNFT owners can delegate freeze authority to a leaf delegate for asset-level control, providing flexibility for various use cases such as preventing transfers during specific events or implementing vesting mechanics. 2) If the PermanentFreezeDelegate plugin is enabled on collection creation, project creators can freeze and thaw cNFTs via the permanent freeze delegate for collection-wide control\nMPL-Core Collections Integration: Bubblegum V2 NFTs can now be added to MPL-Core collections instead of being limited to token metadata collections, allowing for greater flexibility and integration with the broader Metaplex ecosystem.\nRoyalty Enforcement: Since Bubblegum V2 is using MPL-Core Collections, it is possible to enforce royalties on cNFTs e.g. using a ProgramDenyList.\nInherited Royalties: cNFTs minted into MPL-Core collections can store a sentinel seller fee basis points value (65535) on the leaf and inherit the collection's Royalties plugin configuration instead of duplicating basis points on every mint.\nSoulbound NFTs: cNFTs can now be made soulbound (non-transferrable), permanently binding them to their owner's wallet. This is perfect for credentials, proof of attendance, identity verification, and more. It requires the PermanentFreezeDelegate plugin to be enabled when creating the collection.\nAllow Permanent Transfer: The permanent transfer delegate can now transfer the cNFT to a new owner without interaction of the leaf owner if the PermanentTransferDelegate plugin is enabled on the collection.\nBurning by Authority: If the Collection has the PermanentBurnDelegate plugin enabled, the delegate could burn the NFT without the leaf owner's signature.\nAttributes: Attribute Data on collection level can be added using the MPL-Core attributes plugin.\nTo allow the above features to work, Bubblegum V2 introduces a new leaf schema (LeafSchemaV2). To learn more what leaves are used in Bubblegum V2, check out the following sections.\nLeafSchemaV2\nBubblegum V2 introduces a new leaf schema (LeafSchemaV2) which supports the additional features while maintaining backward compatibility. This new schema allows for:\nIntegration with MPL-Core collections instead of traditional token metadata\nSupporting freezing/thawing functionality\nEnabling soulbound capabilities Projects can choose to use the original leaf Schema by using Legacy Bubblegum or the new v2 schema with Bubblegum V2 depending on their requirements.\nTo use the new LeafSchemaV2, a V2 Merkle Tree has to be used that needs to be created using the createTreeV2 instruction. V1 Merkle Trees do not support the new leaf schema and V2 Merkle Trees are not compatible with V1 leaves.\nMerkle Trees, leaves and proofs\nCompressed NFTs only exist in the context of a Merkle Tree. We explain in a dedicated advanced guide what Merkle Trees are but, for the sake of this overview, you can think of a Merkle Tree as a collection of hashes that we call Leaves. Each Leaf is obtained by hashing the data of the compressed NFT.\nFor each Leaf in the Merkle Tree, one can provide a list of hashes — called a Proof — that enables anyone to verify that the given Leaf is part of that tree. Whenever a compressed NFT is updated or transferred, its associated Leaf will change and so will its Proof.\nHash\n\nRoot Node\n\nHash\n\nNode 1\n\nHash\n\nNode 2\n\nNode 3\n\nNode 4\n\nHash\n\nNode 5\n\nNode 6\n\nLeaf 1\n\nLeaf 2\n\nLeaf 3\n\nLeaf 4\n\nLeaf 5\n\nLeaf 6\n\nLeaf 7\n\nLeaf 8\n\nNFT Data\n\nLeaf 4\n\nNode 3\n\nNode 2\n\nProof\n\nReact Flow\nPress enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.\nPress enter or space to select an edge. You can then press delete to remove it or escape to cancel.\n\nAs such, Merkle Trees act as an onchain structure that allows anyone to verify a given compressed NFT exist. They do this without storing any NFT data which makes them so scalable.\nWhich brings us to an important question: where is the NFT data stored?\nMetaplex DAS API\nWhen we mint a new compressed NFT, its data is hashed and added as a new Leaf in a Merkle Tree. But there's more. Additionally, the entire NFT data is stored in the transaction that created the compressed NFT. Similarly, when a compressed NFT is updated, its updated data is, once again, saved on the transaction as a changelog. So, while there aren't any accounts keeping track of that data, one can look at all previous transactions in the ledger and find that information.\nStored in\nStored in\nStored in\n\nTransaction 1\n\nTransaction 2\n\nTransaction 3\n\nTransaction 4\n\nTransaction 5\n\n...\n\nInitial NFT Data\n\nNFT Data Changelog\n\nNFT Data Changelog\n\nReact Flow\nPress enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.\nPress enter or space to select an edge. You can then press delete to remove it or escape to cancel.\n\nCrawling through millions of transactions every time just to fetch the data of one NFT is admittedly not the best user experience. Therefore, compressed NFTs rely on some RPCs to index that information in real time to abstract this away from the end-user. We call the resulting RPC API, which enables fetching compressed NFTs, the Metaplex DAS API.\nNote that not all RPCs support the DAS API. As such, you may be interested in the \"Metaplex DAS API RPCs\" page to select an appropriate RPC when using compressed NFTs in your application.\nWe talk about this in more detail in our advanced \"Storing and indexing NFT data\" guide.\nFeatures\nEven though NFT data does not live inside accounts, it is still possible to execute a variety of operations on compressed NFTs. This is possible by requesting the current NFT data and ensuring its hashed Leaf is valid on the Merkle Tree. As such, the following operations can be performed on compressed NFTs:\nMint a cNFT with or without an associated collection.\nTransfer a cNFT.\nUpdate the data or collection of a cNFT.\nBurn a cNFT.\nDelegate a cNFT.\nVerify and unverify a cNFT collection.\nVerify and unverify the creators of a cNFT.\nFreeze and thaw a cNFT.\nMake a cNFT soulbound.\nQuick Reference\nItemValue\nProgram\nMPL-Bubblegum (BGUMAp9Gq7iTEuizy4pqaxsTyUCBK68MDfK752saRPUY)\n\nCompression Program\nMPL Account Compression (fork of SPL Account Compression)\n\nKey Accounts\nMerkle Tree Account (owned by Compression Program), TreeConfigV2 (PDA owned by Bubblegum)\n\nLeaf Schema\nLeafSchemaV2 (id, owner, delegate, nonce, data_hash, creator_hash, collection_hash, asset_data_hash, flags)\n\nJS SDK\n@metaplex-foundation/mpl-bubblegum (npm)\n\nRust Crate\nmpl-bubblegum (crates.io)\n\nSource\nGitHub\n\nNext steps\nNow that we know how compressed NFTs work at a high level and what's new in Bubblegum V2, we recommend checking out our Getting Started page which enumerates the various languages/frameworks that one can use to interact with compressed NFTs. Afterward, the various feature pages can be used to learn more about the specific operations that can be performed on cNFTs. Finally, advanced guides are also available to deepen your knowledge of cNFTs and Merkle Trees.\nFAQ\nWhat is Bubblegum V2?\nBubblegum V2 is the latest Metaplex program for creating and managing compressed NFTs (cNFTs) on Solana. It uses merkle trees to store NFT data at a fraction of the cost of traditional NFTs, while adding new features like freeze/thaw, soulbound NFTs, and MPL-Core collection integration.\nHow much does it cost to mint a compressed NFT?\nCosts depend on the merkle tree size. A tree holding ~1 million cNFTs costs approximately 8.5 SOL in rent, making each cNFT roughly 0.00001 SOL. A smaller tree of 16,384 cNFTs costs ~0.34 SOL. These costs are orders of magnitude cheaper than standard Solana NFTs (~0.0029 SOL per Core NFT).\nWhat is the difference between Bubblegum V1 and V2?\nBubblegum V2 introduces freeze/thaw functionality, soulbound (non-transferable) NFTs, MPL-Core collection integration, royalty enforcement, permanent delegates (transfer, freeze, burn), and a new LeafSchemaV2 with collection hash, asset data hash, and flags fields.\nDo I need a special RPC to use compressed NFTs?\nYes. Compressed NFTs require an RPC provider that supports the Metaplex DAS API for indexing and fetching cNFT data. Not all RPCs support this. See the RPC Providers page for a list of compatible providers.\nCan compressed NFTs be used in collections?\nYes. Bubblegum V2 uses MPL-Core collections to group cNFTs. Collections enable features like royalty enforcement, freeze delegates, and soulbound NFTs. The collection must have the BubblegumV2 plugin enabled.\nWhat is a merkle tree in the context of cNFTs?\nA merkle tree is an on-chain data structure that stores hashes (called leaves) of cNFT data. It enables cryptographic verification of NFT ownership and data integrity without storing the full NFT data in on-chain accounts, which is what makes cNFTs so cost-effective.\nGlossary\nTermDefinition\ncNFT\nCompressed NFT — an NFT stored as a hashed leaf in a merkle tree rather than in a dedicated on-chain account\n\nMerkle Tree\nA binary tree data structure where each leaf is a hash of data and each parent node is a hash of its children, enabling efficient cryptographic verification\n\nLeaf\nA leaf node in the merkle tree representing one compressed NFT's hashed data (LeafSchemaV2)\n\nProof\nA list of sibling hashes along the path from a leaf to the root, used to verify a cNFT exists in the tree\n\nCanopy\nCached upper nodes of the merkle tree stored on-chain to reduce proof sizes in transactions\n\nDAS API\nDigital Asset Standard API — an RPC extension for indexing and fetching compressed NFT data from transaction history\n\nLeafSchemaV2\nThe V2 data structure containing id, owner, delegate, nonce, data hash, creator hash, collection hash, asset data hash, and flags\n\nTreeConfig\nA PDA account derived from the merkle tree address that stores Bubblegum-specific configuration (creator, delegate, capacity, version)\n\nBubblegum Tree\nThe combination of a Merkle Tree account and its associated TreeConfigV2 PDA account\n\nSoulbound\nA non-transferable cNFT permanently bound to its owner's wallet, created via the permanent freeze delegate","tokens":3137,"crawled_at":1791195768982}
+{"id":10562,"url":"https://a16zcrypto.com/posts/article/investing-in-espresso","domain":"a16zcrypto.com","chapter":"research","title":"Investing in Espresso - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nInvesting in Espresso\nAli Yahya\n03.21.24\n\nTags & Share Tags\nannouncements\nannouncements & news\ninvestments\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nEthereum’s scalability end-game is all about rollups—potentially thousands or even millions of rollups, each one a mini-ecosystem or an application that is built on top of Ethereum’s bedrock of security. The ideas behind how this can work were first laid out by Vitalik a few years back in his now-famous rollup-centric roadmap post. Since then, other ecosystem players like zkSync, Optimism, and Polygon have extended that vision with roadmaps for Hyperchains, the Superchain, and Polygon’s AggLayer. For the first time, there is an illuminated path that Ethereum can follow to reach a scale that supports millions of applications and billions of users.\n\nThis plan, however, is not without its limitations. The biggest disadvantage of a rollup-centric future is the fragmentation of the Ethereum ecosystem. Today, on the Ethereum main chain, every application (i.e. smart contract) can seamlessly interact with every other application. In a world of millions of rollups, composability with applications will become harder. This is because each individual rollup is its own separate blockchain. They all share Ethereum’s security, but computation proceeds independently on each one. Each rollup is driven by what’s known as a “sequencer,” which today is a centralized party that performs all of the computation for a rollup on a server.\n\nToday, if an app on one rollup wants to interact with an app on another, it has to either go through the main Ethereum chain or a bridge. Both approaches are much slower and make it harder for developers to synchronize state across rollups (they are asynchronous solutions). In a better world, sequencers of different rollups would have a mechanism to cooperate with each other, giving developers and end-users a smoother, faster, and cheaper interoperability experience.\n\nThe Espresso Team\n\nBefore I tell you about Espresso Systems, I need to tell you about the people behind it. I have known Ben Fisch and Benedikt Bünz since before I joined a16z. It was early 2017, I was at Google Brain, and both Ben and Benedikt were Ph.D. students under Dan Boneh at Stanford, who I knew very well from my undergrad days. Thanks to Dan, we were all connected and were advising a new crypto company that would later go on to become Eco — which is now also an a16z crypto portfolio company. I remember being very inspired by both of their technical brilliance. For a brief moment, I was even tempted to pursue a Ph.D. in cryptography under Dan, as they were doing.\n\nWhat has always been most impressive to me about Ben in particular is his ability to think clearly at every level of abstraction—from the lowest-level cryptographic primitives, through every business and product consideration, and all the way to the broadest societal effects—for a new technology that he is building. I should have known it was inevitable for him to transition from his role in academia to that of a startup founder and CEO.\n\nAs it turned out, I did not go on to get a Ph.D. Instead, I left Google and joined a16z to become a venture capitalist, which is almost the same thing, right? Shortly thereafter, I met Jill Gunter through crypto circles, and while she was at Slow Ventures, we became fast friends. What has always been so impressive to me about Jill is her insane ability to think strategically. She has the sharpest intuitions about how the world works and how people are likely to operate within it. So, it was impossible to not take note when she joined Ben, Benedikt, and Charles Lu at Espresso in 2021.\n\nAlong the way, through his work at Espresso, I have also gotten to know Charles. He is technically brilliant, like everyone else at Espresso, and also worked with Dan at Stanford. But most importantly, he is the perfect complement to Ben, Benedikt, and Jill because of his excellent operational capabilities. Espresso wouldn’t be the organization that it is without Charles.\n\nLast year, as some of the limitations of Ethereum’s rollup-based roadmap became clear, Ben and team pitched us the most compelling solution to the fragmentation problem that we had heard.\n\nEspresso Systems\n\nEspresso is building a decentralized network that acts as a coordination mechanism for rollup sequencers. It is a marketplace in which sequencers can both sell their blockspace and participate in a mechanism that unifies transaction sequencing across rollups. With Espresso, rollups will be able to sell the right to build their blocks to proposers bidding for them in the network. Those proposers can also simultaneously bid on multiple rollup blocks to become shared proposers for more than one chain at once. This allows rollups to continue to evolve independently while also interoperating more seamlessly with other rollups.\n\nAt its core, crypto is a technology movement that builds tools for better human cooperation at a larger scale—especially when the cooperating parties mutually distrust one another. Espresso and Ethereum are the perfect embodiment of that ideal.\n\nWe’re very excited to be partnering with Ben, Benedikt, Jill, Charles and the Espresso team to help them bring to life a more seamless and interoperable future for Ethereum.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investment-list/.\n\nPast performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures/ for additional important information.","tokens":1988,"crawled_at":1791195779182}
+{"id":10563,"url":"https://www.metaplex.com/docs/smart-contracts/bubblegum-v2/sdk/rust","domain":"www.metaplex.com","chapter":"docs","title":"Rust SDK - MPL-Bubblegum V2 - Metaplex","text":"Summary\nThe MPL-Bubblegum V2 Rust SDK provides instruction builders for local scripts and CPI builders for on-chain programs interacting with compressed NFTs.\nInstall via Cargo: cargo add mpl-bubblegum\nUse Builder types for local scripts and CpiBuilder types for on-chain CPI\nFull instruction reference available on docs.rs\nMetaplex provides a Rust library that can be used to interact with the MPL-Bubblegum program. The Rust library can be used in Rust scripts/builds as well as onchain programs via CPI instructions.\nInstallation\nThe MPL-Bubblegum Rust SDK can be used in both scripts/desktop/mobile applications as well as with Solana onchain programs.\ncargo add mpl-bubblegum\n\ncrates.io\nGet started with our MPL-Bubblegum Rust crate.\n\ndocs.rs\nThe Rust SDK typedoc platform for MPL-Bubblegum.\n\nLocal Scripts\nFor local scripts, we recommend using the Builder versions of all the instructions listed. These builders abstract a lot of the work for you and return an instruction that can be added to a transaction.\nA list of all Bubblegum instructions can be found here: MPL-Bubblegum - Rust Instructions\nFor a more comprehensive guide on using Rust check out the Metaplex Rust SDKs Guide page.\nCreateTreeConfigBuilder - Example\nuse mpl_bubblegum::{instructions::CreateTreeConfigV2Builder, programs::{SPL_ACCOUNT_COMPRESSION_ID, SPL_NOOP_ID}};\n\nuse solana_client::{nonblocking::rpc_client, rpc_config::RpcSendTransactionConfig};\n\nuse solana_sdk::{commitment_config::CommitmentConfig, pubkey::Pubkey, signature::Keypair, signer::Signer, system_program, transaction::Transaction};\n\n#[tokio::main]\n\npub async fn create_tree(keypair: Keypair) {\n\nlet rpc_client = rpc_client::RpcClient::new(\"https://api.devnet.solana.com/\".to_string());\n\nlet payer = keypair;\n\nlet asset = Keypair::new();\n\nlet merkle_tree = Keypair::new();\n\nlet tree_config = Pubkey::find_program_address(\n\n&[\n\n&merkle_tree.pubkey().to_bytes(),\n\n],\n\n&mpl_bubblegum::ID,\n\n);\n\nlet create_tree_config_ix = CreateTreeConfigV2Builder::new()\n\n.merkle_tree(merkle_tree.pubkey())\n\n.tree_config(tree_config.0)\n\n.payer(payer.pubkey())\n\n.max_depth(20)\n\n.max_buffer_size(1024)\n\n.public(false)\n\n.instruction();\n\nlet signers = vec![&asset, &payer];\n\nlet last_blockhash = rpc_client.get_latest_blockhash().await;\n\nlet create_tree_config_tx = Transaction::new_signed_with_payer(\n\n&[create_tree_config_ix],\n\nSome(&payer.pubkey()),\n\n&signers,\n\nlast_blockhash.unwrap(),\n\n);\n\nlet res = rpc_client\n\n.send_transaction_with_config(&create_tree_config_tx, RpcSendTransactionConfig {\n\nskip_preflight: false,\n\npreflight_commitment: Some(CommitmentConfig::confirmed().commitment),\n\nencoding: None,\n\nmax_retries: None,\n\nmin_context_slot: None,\n\n})\n\n.await\n\n.unwrap();\n\nprintln!(\"Signature: {:?}\", res);\n\n}\n\nCPI (Cross Program Invocation)\nPerforming CPI instructions from your own programs can be achieved easily by using the CpiBuilder version of an instruction function that can be found for all instructions in the MPL-Bubblegum Rust crate.\nA list of all Bubblegum instructions can be found here: Metaplex Bubblegum - Rust Instructions\nFor a more comprehensive guide using Metaplex crates to create CPI instructions check out the How to CPI into a Metaplex Program guide page.\nCreateTreeConfigCpiBuilder - Example\nCreateTreeConfigV2CpiBuilder::new()\n\n.merkle_tree(context.accounts.merkle_tree)\n\n.tree_config(context.accounts.tree_config)\n\n.payer(context.accounts.payer)\n\n.tree_creator(context.accounts.tree_creator)\n\n.log_wrapper(SPL_NOOP_ID)\n\n.compression_program(context.accounts.compression_program)\n\n.system_program(context.accounts.system_program)\n\n.max_depth(20)\n\n.max_buffer_size(1024)\n\n.public(false)\n\n.invoke()","tokens":914,"crawled_at":1791195806268}
+{"id":10564,"url":"https://docs.sui.io/develop/objects/escrow-example","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Owned Compared With Shared Objects | Sui Documentation","text":"Choosing between address-owned and shared objects changes how a service is built, not just how it performs. This page implements the same trustless objectObjectThe basic unit of storage on Sui. swap 2 ways, once with addressAddressA unique, anonymous identity on a blockchain network.-owned objects and a custodian, and once with a shared object.\n\nBoth implementations use a locking primitive:\n\nmodule escrow::lock {\npublic fun lock<T: store>(obj: T, ctx: &mut TxContext): (Locked<T>, Key);\npublic fun unlock<T: store>(locked: Locked<T>, key: Key): T\n}\n\nAny T: store can be locked to get a Locked<T> and a corresponding Key. Unlocking consumes the key, so any tampering with the locked value is detectable by monitoring the key's ID.\n\nView the complete code on GitHub.\n\nFastpath: address-owned objects​\n\nClick to openowned.moveexamples/trading/contracts/escrow/sources/owned.move\n/// An escrow for atomic swap of objects using single-owner transactions that\n/// trusts a third party for liveness, but not safety.\n///\n/// Swap via Escrow proceeds in three phases:\n///\n/// 1. Both parties `lock` their objects, getting the `Locked` object and a\n/// `Key`. Each party can `unlock` their object, to preserve liveness if the\n/// other party stalls before completing the second stage.\n///\n/// 2. Both parties register an `Escrow` object with the custodian, this\n/// requires passing the locked object and its key. The key is consumed to\n/// unlock the object, but its ID is remembered so the custodian can ensure\n/// the right objects being swapped. The custodian is trusted to preserve\n/// liveness.\n///\n/// 3. The custodian swaps the locked objects as long as all conditions are met:\n///\n/// - The sender of one Escrow is the recipient of the other and vice versa.\n/// If this is not true, the custodian has incorrectly paired together this\n/// swap.\n///\n/// - The key of the desired object (`exchange_key`) matches the key the\n/// other object was locked with (`escrowed_key`) and vice versa.\n\n/// If this is not true, it means the wrong objects are being swapped,\n/// either because the custodian paired the wrong escrows together, or\n/// because one of the parties tampered with their object after locking it.\n///\n/// The key in question is the ID of the `Key` object that unlocked the\n/// `Locked` object that the respective objects resided in immediately\n/// before being sent to the custodian.\nmodule escrow::owned;\n\nuse escrow::lock::{Locked, Key};\n\n/// An object held in escrow\npublic struct Escrow<T: key + store> has key {\nid: UID,\n/// Owner of `escrowed`\nsender: address,\n/// Intended recipient\nrecipient: address,\n/// The ID of the key that opens the lock on the object sender wants\n/// from recipient.\nexchange_key: ID,\n/// The ID of the key that locked the escrowed object, before it was\n/// escrowed.\nescrowed_key: ID,\n/// The escrowed object.\nescrowed: T,\n}\n\n// === Error codes ===\n\n/// The `sender` and `recipient` of the two escrowed objects do not match\nconst EMismatchedSenderRecipient: u64 = 0;\n\n/// The `exchange_key` fields of the two escrowed objects do not match\nconst EMismatchedExchangeObject: u64 = 1;\n\n// === Public Functions ===\n\n/// `ctx.sender()` requests a swap with `recipient` of a locked\n/// object `locked` in exchange for an object referred to by `exchange_key`.\n/// The swap is performed by a third-party, `custodian`, that is trusted to\n/// maintain liveness, but not safety (the only actions they can perform are\n/// to successfully progress the swap).\n///\n/// `locked` will be unlocked with its corresponding `key` before being sent\n/// to the custodian, but the underlying object is still not accessible\n/// until after the swap has executed successfully, or the custodian returns\n/// the object.\n///\n/// `exchange_key` is the ID of a `Key` that unlocks the sender's desired\n/// object. Gating the swap on the key ensures that it will not succeed if\n/// the desired object is tampered with after the sender's object is held in\n/// escrow, because the recipient would have to consume the key to tamper\n/// with the object, and if they re-locked the object it would be protected\n/// by a different, incompatible key.\npublic fun create<T: key + store>(\nkey: Key,\nlocked: Locked<T>,\nexchange_key: ID,\nrecipient: address,\ncustodian: address,\nctx: &mut TxContext,\n) {\nlet escrow = Escrow {\nid: object::new(ctx),\nsender: ctx.sender(),\nrecipient,\nexchange_key,\nescrowed_key: object::id(&key),\nescrowed: locked.unlock(key),\n};\n\ntransfer::transfer(escrow, custodian);\n}\n\n/// Function for custodian (trusted third-party) to perform a swap between\n/// two parties. Fails if their senders and recipients do not match, or if\n/// their respective desired objects do not match.\npublic fun swap<T: key + store, U: key + store>(obj1: Escrow<T>, obj2: Escrow<U>) {\nlet Escrow {\nid: id1,\nsender: sender1,\nrecipient: recipient1,\nexchange_key: exchange_key1,\nescrowed_key: escrowed_key1,\nescrowed: escrowed1,\n} = obj1;\n\nlet Escrow {\nid: id2,\nsender: sender2,\nrecipient: recipient2,\nexchange_key: exchange_key2,\nescrowed_key: escrowed_key2,\nescrowed: escrowed2,\n} = obj2;\nid1.delete();\nid2.delete();\n\n// Make sure the sender and recipient match each other\nassert!(sender1 == recipient2, EMismatchedSenderRecipient);\nassert!(sender2 == recipient1, EMismatchedSenderRecipient);\n\n// Make sure the objects match each other and haven't been modified\n// (they remain locked).\nassert!(escrowed_key1 == exchange_key2, EMismatchedExchangeObject);\nassert!(escrowed_key2 == exchange_key1, EMismatchedExchangeObject);\n\n// Do the actual swap\ntransfer::public_transfer(escrowed1, recipient1);\ntransfer::public_transfer(escrowed2, recipient2);\n}\n\n/// The custodian can always return an escrowed object to its original\n/// owner.\npublic fun return_to_sender<T: key + store>(obj: Escrow<T>) {\nlet Escrow {\nid,\nsender,\nrecipient: _,\nexchange_key: _,\nescrowed_key: _,\nescrowed,\n} = obj;\nid.delete();\ntransfer::public_transfer(escrowed, sender);\n}\n\n// === Tests ===\n#[test_only]\nuse sui::coin::{Self, Coin};\n#[test_only]\nuse sui::sui::SUI;\n#[test_only]\nuse sui::test_scenario::{Self as ts, Scenario};\n\n#[test_only]\nuse escrow::lock;\n\n#[test_only]\nconst ALICE: address = @0xA;\n#[test_only]\nconst BOB: address = @0xB;\n#[test_only]\nconst CUSTODIAN: address = @0xC;\n#[test_only]\nconst DIANE: address = @0xD;\n\n#[test_only]\nfun test_coin(ts: &mut Scenario): Coin<SUI> {\ncoin::mint_for_testing<SUI>(42, ts::ctx(ts))\n}\n\n#[test]\nfun test_successful_swap() {\nlet mut ts = ts::begin(@0x0);\n\n// Alice locks the object they want to trade\nlet (i1, ik1) = {\nts.next_tx(ALICE);\nlet c = test_coin(&mut ts);\nlet cid = object::id(&c);\nlet (l, k) = lock::lock(c, ts.ctx());\nlet kid = object::id(&k);\ntransfer::public_transfer(l, ALICE);\ntransfer::public_transfer(k, ALICE);\n(cid, kid)\n};\n\n// Bob locks their object as well.\nlet (i2, ik2) = {\nts.next_tx(BOB);\nlet c = test_coin(&mut ts);\nlet cid = object::id(&c);\nlet (l, k) = lock::lock(c, ts.ctx());\nlet kid = object::id(&k);\ntransfer::public_transfer(l, BOB);\ntransfer::public_transfer(k, BOB);\n(cid, kid)\n};\n\n// Alice gives the custodian their object to hold in escrow.\n{\nts.next_tx(ALICE);\nlet k1: Key = ts.take_from_sender();\nlet l1: Locked<Coin<SUI>> = ts.take_from_sender();\ncreate(k1, l1, ik2, BOB, CUSTODIAN, ts.ctx());\n};\n\n// Bob does the same.\n{\nts.next_tx(BOB);\nlet k2: Key = ts.take_from_sender();\nlet l2: Locked<Coin<SUI>> = ts.take_from_sender();\ncreate(k2, l2, ik1, ALICE, CUSTODIAN, ts.ctx());\n};\n\n// The custodian makes the swap\n{\nts.next_tx(CUSTODIAN);\nswap<Coin<SUI>, Coin<SUI>>(\nts.take_from_sender(),\nts.take_from_sender(),\n);\n};\n\n// Commit effects from the swap\nts.next_tx(@0x0);\n\n// Alice gets the object from Bob\n{\nlet c: Coin<SUI> = ts.take_from_address_by_id(ALICE, i2);\nts::return_to_address(ALICE, c);\n};\n\n// Bob gets the object from Alice\n{\nlet c: Coin<SUI> = ts.take_from_address_by_id(BOB, i1);\nts::return_to_address(BOB, c);\n};\n\nts.end();\n}\n\n#[test]\n#[expected_failure(abort_code = EMismatchedSenderRecipient)]\nfun test_mismatch_sender() {\nlet mut ts = ts::begin(@0x0);\n\nlet ik1 = {\nts.next_tx(ALICE);\nlet c = test_coin(&mut ts);\nlet (l, k) = lock::lock(c, ts.ctx());\nlet kid = object::id(&k);\ntransfer::public_transfer(l, ALICE);\ntransfer::public_transfer(k, ALICE);\nkid\n};\n\nlet ik2 = {\nts.next_tx(BOB);\nlet c = test_coin(&mut ts);\nlet (l, k) = lock::lock(c, ts.ctx());\nlet kid = object::id(&k);\ntransfer::public_transfer(l, BOB);\ntransfer::public_transfer(k, BOB);\nkid\n};\n\n// Alice wants to trade with Bob.\n{\nts.next_tx(ALICE);\nlet k1: Key = ts.take_from_sender();\nlet l1: Locked<Coin<SUI>> = ts.take_from_sender();\ncreate(k1, l1, ik2, BOB, CUSTODIAN, ts.ctx());\n};\n\n// But Bob wants to trade with Diane.\n{\nts.next_tx(BOB);\nlet k2: Key = ts.take_from_sender();\nlet l2: Locked<Coin<SUI>> = ts.take_from_sender();\ncreate(k2, l2, ik1, DIANE, CUSTODIAN, ts.ctx());\n};\n\n// When the custodian tries to match up the swap, it will fail.\n{\nts.next_tx(CUSTODIAN);\nswap<Coin<SUI>, Coin<SUI>>(\nts.take_from_sender(),\nts.take_from_sender(),\n);\n};\n\nabort 1337\n}\n\n#[test]\n#[expected_failure(abort_code = EMismatchedExchangeObject)]\nfun test_mismatch_object() {\nlet mut ts = ts::begin(@0x0);\n\nlet ik1 = {\nts.next_tx(ALICE);\nlet c = test_coin(&mut ts);\nlet (l, k) = lock::lock(c, ts.ctx());\nlet kid = object::id(&k);\ntransfer::public_transfer(l, ALICE);\ntransfer::public_transfer(k, ALICE);\nkid\n};\n\n{\nts.next_tx(BOB);\nlet c = test_coin(&mut ts);\nlet (l, k) = lock::lock(c, ts.ctx());\ntransfer::public_transfer(l, BOB);\ntransfer::public_transfer(k, BOB);\n};\n\n// Alice wants to trade with Bob, but Alice has asked for an\n// object (via its `exchange_key`) that Bob has not put up for\n// the swap.\n{\nts.next_tx(ALICE);\nlet k1: Key = ts.take_from_sender();\nlet l1: Locked<Coin<SUI>> = ts.take_from_sender();\ncreate(k1, l1, ik1, BOB, CUSTODIAN, ts.ctx());\n};\n\n{\nts.next_tx(BOB);\nlet k2: Key = ts.take_from_sender();\nlet l2: Locked<Coin<SUI>> = ts.take_from_sender();\ncreate(k2, l2, ik1, ALICE, CUSTODIAN, ts.ctx());\n};\n\n// When the custodian tries to match up the swap, it will fail.\n{\nts.next_tx(CUSTODIAN);\nswap<Coin<SUI>, Coin<SUI>>(\nts.take_from_sender(),\nts.take_from_sender(),\n);\n};\n\nabort 1337\n}\n\n#[test]\n#[expected_failure(abort_code = EMismatchedExchangeObject)]\nfun test_object_tamper() {\nlet mut ts = ts::begin(@0x0);\n\n// Alice locks the object they want to trade\nlet ik1 = {\nts.next_tx(ALICE);\nlet c = test_coin(&mut ts);\nlet (l, k) = lock::lock(c, ts.ctx());\nlet kid = object::id(&k);\ntransfer::public_transfer(l, ALICE);\ntransfer::public_transfer(k, ALICE);\nkid\n};\n\n// Bob locks their object as well.\nlet ik2 = {\nts.next_tx(BOB);\nlet c = test_coin(&mut ts);\nlet (l, k) = lock::lock(c, ts.ctx());\nlet kid = object::id(&k);\ntransfer::public_transfer(l, BOB);\ntransfer::public_transfer(k, BOB);\nkid\n};\n\n// Alice gives the custodian their object to hold in escrow.\n{\nts.next_tx(ALICE);\nlet k1: Key = ts.take_from_sender();\nlet l1: Locked<Coin<SUI>> = ts.take_from_sender();\ncreate(k1, l1, ik2, BOB, CUSTODIAN, ts.ctx());\n};\n\n// Bob has a change of heart, so they unlock the object and tamper\n// with it.\n{\nts.next_tx(BOB);\nlet k: Key = ts.take_from_sender();\nlet l: Locked<Coin<SUI>> = ts.take_from_sender();\nlet mut c = lock::unlock(l, k);\n\nlet _dust = coin::split(&mut c, 1, ts.ctx());\nlet (l, k) = lock::lock(c, ts.ctx());\ncreate(k, l, ik1, ALICE, CUSTODIAN, ts.ctx());\n};\n\n// When the Custodian makes the swap, it detects Bob's nefarious\n// behaviour.\n{\nts.next_tx(CUSTODIAN);\nswap<Coin<SUI>, Coin<SUI>>(\nts.take_from_sender(),\nts.take_from_sender(),\n);\n};\n\nabort 1337\n}\n\n#[test]\nfun test_return_to_sender() {\nlet mut ts = ts::begin(@0x0);\n\n// Alice locks the object they want to trade\nlet cid = {\nts.next_tx(ALICE);\nlet c = test_coin(&mut ts);\nlet cid = object::id(&c);\nlet (l, k) = lock::lock(c, ts.ctx());\nlet i = object::id_from_address(@0x0);\ncreate(k, l, i, BOB, CUSTODIAN, ts.ctx());\ncid\n};\n\n// Custodian sends it back\n{\nts.next_tx(CUSTODIAN);\nreturn_to_sender<Coin<SUI>>(ts.take_from_sender());\n};\n\nts.next_tx(@0x0);\n\n// Alice can then access it.\n{\nlet c: Coin<SUI> = ts.take_from_address_by_id(ALICE, cid);\nts::return_to_address(ALICE, c)\n};\n\nts.end();\n}\n\nBoth parties begin by locking their objects. If either decides not to proceed, they unlock and exit.\n\nBoth parties then swap keys:\n\nA third-party custodian holds the objects and matches them when both arrive. The create function sends the Escrow request to the custodian, unlocking the offered object while recording the ID of the key it was locked with:\n\nexamples/trading/contracts/escrow/sources/owned.move\npublic fun create<T: key + store>(\nkey: Key,\nlocked: Locked<T>,\nexchange_key: ID,\nrecipient: address,\ncustodian: address,\nctx: &mut TxContext,\n) {\nlet escrow = Escrow {\nid: object::new(ctx),\nsender: ctx.sender(),\nrecipient,\nexchange_key,\nescrowed_key: object::id(&key),\nescrowed: locked.unlock(key),\n};\n\ntransfer::transfer(escrow, custodian);\n}\n\nEven though the custodian owns both objects, the only valid actions in MoveMoveAn open source programming language used for all activity on Sui. are to match them correctly or return them. The swap function verifies that senders and recipients match and that each party wants what the other is offering by comparing key IDs:\n\nexamples/trading/contracts/escrow/sources/owned.move\n/// Function for custodian (trusted third-party) to perform a swap between\n/// two parties. Fails if their senders and recipients do not match, or if\n/// their respective desired objects do not match.\npublic fun swap<T: key + store, U: key + store>(obj1: Escrow<T>, obj2: Escrow<U>) {\nlet Escrow {\nid: id1,\nsender: sender1,\nrecipient: recipient1,\nexchange_key: exchange_key1,\nescrowed_key: escrowed_key1,\nescrowed: escrowed1,\n} = obj1;\n\nlet Escrow {\nid: id2,\nsender: sender2,\nrecipient: recipient2,\nexchange_key: exchange_key2,\nescrowed_key: escrowed_key2,\nescrowed: escrowed2,\n} = obj2;\nid1.delete();\nid2.delete();\n\n// Make sure the sender and recipient match each other\nassert!(sender1 == recipient2, EMismatchedSenderRecipient);\nassert!(sender2 == recipient1, EMismatchedSenderRecipient);\n\n// Make sure the objects match each other and haven't been modified\n// (they remain locked).\nassert!(escrowed_key1 == exchange_key2, EMismatchedExchangeObject);\nassert!(escrowed_key2 == exchange_key1, EMismatchedExchangeObject);\n\n// Do the actual swap\ntransfer::public_transfer(escrowed1, recipient1);\ntransfer::public_transfer(escrowed2, recipient2);\n}\n\nConsensusConsensusThe process by which the majority of nodes agree on the current state of the network: shared object​\n\nClick to openshared.moveexamples/trading/contracts/escrow/sources/shared.move\n/// An escrow for atomic swap of objects using shared objects without a trusted\n/// third party.\n///\n/// The protocol consists of three phases:\n///\n/// 1. One party `lock`s their object, getting a `Locked` object and its `Key`.\n/// This party can `unlock` their object to preserve livness if the other\n/// party stalls before completing the second stage.\n///\n/// 2. The other party registers a publicly accessible, shared `Escrow` object.\n/// This effectively locks their object at a particular version as well,\n/// waiting for the first party to complete the swap. The second party is\n/// able to request their object is returned to them, to preserve liveness as\n/// well.\n///\n/// 3. The first party sends their locked object and its key to the shared\n/// `Escrow` object. This completes the swap, as long as all conditions are\n/// met:\n///\n/// - The sender of the swap transaction is the recipient of the `Escrow`.\n///\n/// - The key of the desired object (`exchange_key`) in the escrow matches\n/// the key supplied in the swap.\n///\n/// - The key supplied in the swap unlocks the `Locked<U>`.\nmodule escrow::shared;\n\nuse escrow::lock::{Locked, Key};\nuse sui::dynamic_object_field as dof;\nuse sui::event;\n\n/// The `name` of the DOF that holds the Escrowed object.\n/// Allows easy discoverability for the escrowed object.\npublic struct EscrowedObjectKey has copy, drop, store {}\n\n/// An object held in escrow\n///\n/// The escrowed object is added as a Dynamic Object Field so it can still be looked-up.\npublic struct Escrow<phantom T: key + store> has key, store {\nid: UID,\n/// Owner of `escrowed`\nsender: address,\n/// Intended recipient\nrecipient: address,\n/// ID of the key that opens the lock on the object sender wants from\n/// recipient.\nexchange_key: ID,\n}\n\n// === Error codes ===\n\n/// The `sender` and `recipient` of the two escrowed objects do not match\nconst EMismatchedSenderRecipient: u64 = 0;\n\n/// The `exchange_for` fields of the two escrowed objects do not match\nconst EMismatchedExchangeObject: u64 = 1;\n\n// === Public Functions ===\npublic fun create<T: key + store>(\nescrowed: T,\nexchange_key: ID,\nrecipient: address,\nctx: &mut TxContext,\n) {\nlet mut escrow = Escrow<T> {\nid: object::new(ctx),\nsender: ctx.sender(),\nrecipient,\nexchange_key,\n};\nevent::emit(EscrowCreated {\nescrow_id: object::id(&escrow),\nkey_id: exchange_key,\nsender: escrow.sender,\nrecipient,\nitem_id: object::id(&escrowed),\n});\n\ndof::add(&mut escrow.id, EscrowedObjectKey {}, escrowed);\n\ntransfer::public_share_object(escrow);\n}\n\n/// The `recipient` of the escrow can exchange `obj` with the escrowed item\npublic fun swap<T: key + store, U: key + store>(\nmut escrow: Escrow<T>,\nkey: Key,\nlocked: Locked<U>,\nctx: &TxContext,\n): T {\nlet escrowed = dof::remove<EscrowedObjectKey, T>(&mut escrow.id, EscrowedObjectKey {});\n\nlet Escrow {\nid,\nsender,\nrecipient,\nexchange_key,\n} = escrow;\n\nassert!(recipient == ctx.sender(), EMismatchedSenderRecipient);\nassert!(exchange_key == object::id(&key), EMismatchedExchangeObject);\n\n// Do the actual swap\ntransfer::public_transfer(locked.unlock(key), sender);\n\nevent::emit(EscrowSwapped {\nescrow_id: id.to_inner(),\n});\n\nid.delete();\n\nescrowed\n}\n\n/// The `creator` can cancel the escrow and get back the escrowed item\npublic fun return_to_sender<T: key + store>(mut escrow: Escrow<T>, ctx: &TxContext): T {\nevent::emit(EscrowCancelled {\nescrow_id: object::id(&escrow),\n});\n\nlet escrowed = dof::remove<EscrowedObjectKey, T>(&mut escrow.id, EscrowedObjectKey {});\n\nlet Escrow {\nid,\nsender,\nrecipient: _,\nexchange_key: _,\n} = escrow;\n\nassert!(sender == ctx.sender(), EMismatchedSenderRecipient);\nid.delete();\nescrowed\n}\n\n// === Events ===\npublic struct EscrowCreated has copy, drop {\n/// the ID of the escrow that was created\nescrow_id: ID,\n/// The ID of the `Key` that unlocks the requested object.\nkey_id: ID,\n/// The id of the sender who'll receive `T` upon swap\nsender: address,\n/// The (original) recipient of the escrowed object\nrecipient: address,\n/// The ID of the escrowed item\nitem_id: ID,\n}\n\npublic struct EscrowSwapped has copy, drop {\nescrow_id: ID,\n}\n\npublic struct EscrowCancelled has copy, drop {\nescrow_id: ID,\n}\n\n// === Tests ===\n#[test_only]\nuse sui::coin::{Self, Coin};\n#[test_only]\nuse sui::sui::SUI;\n#[test_only]\nuse sui::test_scenario::{Self as ts, Scenario};\n\n#[test_only]\nuse escrow::lock;\n\n#[test_only]\nconst ALICE: address = @0xA;\n#[test_only]\nconst BOB: address = @0xB;\n#[test_only]\nconst DIANE: address = @0xD;\n\n#[test_only]\nfun test_coin(ts: &mut Scenario): Coin<SUI> {\ncoin::mint_for_testing<SUI>(42, ts.ctx())\n}\n#[test]\nfun test_successful_swap() {\nlet mut ts = ts::begin(@0x0);\n\n// Bob locks the object they want to trade.\nlet (i2, ik2) = {\nts.next_tx(BOB);\nlet c = test_coin(&mut ts);\nlet cid = object::id(&c);\nlet (l, k) = lock::lock(c, ts.ctx());\nlet kid = object::id(&k);\ntransfer::public_transfer(l, BOB);\ntransfer::public_transfer(k, BOB);\n(cid, kid)\n};\n\n// Alice creates a public Escrow holding the object they are willing to\n// share, and the object they want from Bob\nlet i1 = {\nts.next_tx(ALICE);\nlet c = test_coin(&mut ts);\nlet cid = object::id(&c);\ncreate(c, ik2, BOB, ts.ctx());\ncid\n};\n\n// Bob responds by offering their object, and gets Alice's object in\n// return.\n{\nts.next_tx(BOB);\nlet escrow: Escrow<Coin<SUI>> = ts.take_shared();\nlet k2: Key = ts.take_from_sender();\nlet l2: Locked<Coin<SUI>> = ts.take_from_sender();\nlet c = escrow.swap(k2, l2, ts.ctx());\n\ntransfer::public_transfer(c, BOB);\n};\n// Commit effects from the swap\nts.next_tx(@0x0);\n\n// Alice gets the object from Bob\n{\nlet c: Coin<SUI> = ts.take_from_address_by_id(ALICE, i2);\nts::return_to_address(ALICE, c);\n};\n\n// Bob gets the object from Alice\n{\nlet c: Coin<SUI> = ts.take_from_address_by_id(BOB, i1);\nts::return_to_address(BOB, c);\n};\n\nts::end(ts);\n}\n\n#[test]\n#[expected_failure(abort_code = EMismatchedSenderRecipient)]\nfun test_mismatch_sender() {\nlet mut ts = ts::begin(@0x0);\n\nlet ik2 = {\nts.next_tx(DIANE);\nlet c = test_coin(&mut ts);\nlet (l, k) = lock::lock(c, ts.ctx());\nlet kid = object::id(&k);\ntransfer::public_transfer(l, DIANE);\ntransfer::public_transfer(k, DIANE);\nkid\n};\n\n// Alice wants to trade with Bob.\n{\nts.next_tx(ALICE);\nlet c = test_coin(&mut ts);\ncreate(c, ik2, BOB, ts.ctx());\n};\n\n// But Diane is the one who attempts the swap\n{\nts.next_tx(DIANE);\nlet escrow: Escrow<Coin<SUI>> = ts.take_shared();\nlet k2: Key = ts.take_from_sender();\nlet l2: Locked<Coin<SUI>> = ts.take_from_sender();\nlet c = escrow.swap(k2, l2, ts.ctx());\n\ntransfer::public_transfer(c, DIANE);\n};\n\nabort 1337\n}\n\n#[test]\n#[expected_failure(abort_code = EMismatchedExchangeObject)]\nfun test_mismatch_object() {\nlet mut ts = ts::begin(@0x0);\n\n{\nts.next_tx(BOB);\nlet c = test_coin(&mut ts);\nlet (l, k) = lock::lock(c, ts.ctx());\ntransfer::public_transfer(l, BOB);\ntransfer::public_transfer(k, BOB);\n};\n\n// Alice wants to trade with Bob, but Alice has asked for an object (via\n// its `exchange_key`) that Bob has not put up for the swap.\n{\nts.next_tx(ALICE);\nlet c = test_coin(&mut ts);\nlet cid = object::id(&c);\ncreate(c, cid, BOB, ts.ctx());\n};\n\n// When Bob tries to complete the swap, it will fail, because they\n// cannot meet Alice's requirements.\n{\nts.next_tx(BOB);\nlet escrow: Escrow<Coin<SUI>> = ts.take_shared();\nlet k2: Key = ts.take_from_sender();\nlet l2: Locked<Coin<SUI>> = ts.take_from_sender();\nlet c = escrow.swap(k2, l2, ts.ctx());\n\ntransfer::public_transfer(c, BOB);\n};\n\nabort 1337\n}\n\n#[test]\n#[expected_failure(abort_code = EMismatchedExchangeObject)]\nfun test_object_tamper() {\nlet mut ts = ts::begin(@0x0);\n\n// Bob locks their object.\nlet ik2 = {\nts.next_tx(BOB);\nlet c = test_coin(&mut ts);\nlet (l, k) = lock::lock(c, ts.ctx());\nlet kid = object::id(&k);\ntransfer::public_transfer(l, BOB);\ntransfer::public_transfer(k, BOB);\nkid\n};\n\n// Alice sets up the escrow\n{\nts.next_tx(ALICE);\nlet c = test_coin(&mut ts);\ncreate(c, ik2, BOB, ts.ctx());\n};\n\n// Bob has a change of heart, so they unlock the object and tamper with\n// it before initiating the swap, but it won't be possible for Bob to\n// hide their tampering.\n{\nts.next_tx(BOB);\nlet k: Key = ts.take_from_sender();\nlet l: Locked<Coin<SUI>> = ts.take_from_sender();\nlet mut c = lock::unlock(l, k);\n\nlet _dust = c.split(1, ts.ctx());\nlet (l, k) = lock::lock(c, ts.ctx());\nlet escrow: Escrow<Coin<SUI>> = ts.take_shared();\nlet c = escrow.swap(k, l, ts.ctx());\n\ntransfer::public_transfer(c, BOB);\n};\n\nabort 1337\n}\n\n#[test]\nfun test_return_to_sender() {\nlet mut ts = ts::begin(@0x0);\n\n// Alice puts up the object they want to trade\nlet cid = {\nts.next_tx(ALICE);\nlet c = test_coin(&mut ts);\nlet cid = object::id(&c);\nlet i = object::id_from_address(@0x0);\ncreate(c, i, BOB, ts.ctx());\ncid\n};\n\n// ...but has a change of heart and takes it back\n{\nts.next_tx(ALICE);\nlet escrow: Escrow<Coin<SUI>> = ts.take_shared();\nlet c = escrow.return_to_sender(ts.ctx());\n\ntransfer::public_transfer(c, ALICE);\n};\n\nts.next_tx(@0x0);\n\n// Alice can then access it.\n{\nlet c: Coin<SUI> = ts.take_from_address_by_id(ALICE, cid);\nts::return_to_address(ALICE, c)\n};\n\nts::end(ts);\n}\n\n#[test]\n#[expected_failure]\nfun test_return_to_sender_failed_swap() {\nlet mut ts = ts::begin(@0x0);\n\n// Bob locks their object.\nlet ik2 = {\nts.next_tx(BOB);\nlet c = test_coin(&mut ts);\nlet (l, k) = lock::lock(c, ts.ctx());\nlet kid = object::id(&k);\ntransfer::public_transfer(l, BOB);\ntransfer::public_transfer(k, BOB);\nkid\n};\n\n// Alice creates a public Escrow holding the object they are willing to\n// share, and the object they want from Bob\n{\nts.next_tx(ALICE);\nlet c = test_coin(&mut ts);\ncreate(c, ik2, BOB, ts.ctx());\n};\n\n// ...but then has a change of heart\n{\nts.next_tx(ALICE);\nlet escrow: Escrow<Coin<SUI>> = ts.take_shared();\nlet c = escrow.return_to_sender(ts.ctx());\ntransfer::public_transfer(c, ALICE);\n};\n\n// Bob's attempt to complete the swap will now fail.\n{\nts.next_tx(BOB);\nlet escrow: Escrow<Coin<SUI>> = ts.take_shared();\nlet k2: Key = ts.take_from_sender();\nlet l2: Locked<Coin<SUI>> = ts.take_from_sender();\nlet c = escrow.swap(k2, l2, ts.ctx());\n\ntransfer::public_transfer(c, BOB);\n};\n\nabort 1337\n}\n\nThe first party locks the object they want to swap:\n\nThe second party views the locked object and, if interested, creates a swap request that passes their object directly into a shared Escrow object. The request records the sender (who can reclaim if the swap doesn't complete) and the intended recipient:\n\nexamples/trading/contracts/escrow/sources/shared.move\npublic fun create<T: key + store>(\nescrowed: T,\nexchange_key: ID,\nrecipient: address,\nctx: &mut TxContext,\n) {\nlet mut escrow = Escrow<T> {\nid: object::new(ctx),\nsender: ctx.sender(),\nrecipient,\nexchange_key,\n};\nevent::emit(EscrowCreated {\nescrow_id: object::id(&escrow),\nkey_id: exchange_key,\nsender: escrow.sender,\nrecipient,\nitem_id: object::id(&escrowed),\n});\n\ndof::add(&mut escrow.id, EscrowedObjectKey {}, escrowed);\n\ntransfer::public_share_object(escrow);\n}\n\nThe intended recipient completes the swap by providing their locked object:\n\nexamples/trading/contracts/escrow/sources/shared.move\n/// The `recipient` of the escrow can exchange `obj` with the escrowed item\npublic fun swap<T: key + store, U: key + store>(\nmut escrow: Escrow<T>,\nkey: Key,\nlocked: Locked<U>,\nctx: &TxContext,\n): T {\nlet escrowed = dof::remove<EscrowedObjectKey, T>(&mut escrow.id, EscrowedObjectKey {});\n\nlet Escrow {\nid,\nsender,\nrecipient,\nexchange_key,\n} = escrow;\n\nassert!(recipient == ctx.sender(), EMismatchedSenderRecipient);\nassert!(exchange_key == object::id(&key), EMismatchedExchangeObject);\n\n// Do the actual swap\ntransfer::public_transfer(locked.unlock(key), sender);\n\nevent::emit(EscrowSwapped {\nescrow_id: id.to_inner(),\n});\n\nid.delete();\n\nescrowed\n}\n\nAlthough the Escrow object is shared and accessible by anyone, Move ensures only the original sender and intended recipient can interact with it. swap verifies the locked object matches what was requested, extracts the escrowed object, deletes the wrapper, and delivers both objects to their new owners.\nRelated topics\n\nAddress-Owned Objects\nAddress-owned objects are owned by a Sui 32-byte address, which can either be an account address or an object ID. Learn how to create and access these objects.\nShared Objects\nAnyone can access shared objects on the Sui network, so care must be taken to secure access, if needed.\n\nFastpath: address-owned objects\nConsensus: shared object\n\nWas this page helpful?","tokens":6745,"crawled_at":1791195790958}
+{"id":10565,"url":"https://a16zcrypto.com/posts/article/investing-in-eigenlayer","domain":"a16zcrypto.com","chapter":"research","title":"Investing in EigenLayer - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nInvesting in EigenLayer\nAli Yahya\n02.22.24\n\nTags & Share Tags\nannouncements\nannouncements & news\ninfrastructure\ninvestments\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nIt’s exceedingly rare to come across a founder with a vision and plan that has the potential to change everything. I have come to know EigenLayer founder Sreeram Kannan to be not only brilliant, but also fundamentally motivated by a vision of the future so crisp and compelling that it momentarily becomes real when you talk to him. Sreeram has what I like to call the Promethean flame; he is driven to bring a new technology to life first and foremost because of the future it will create.\n\nI first met Sreeram in 2019. At the time, he was still an associate professor at the University of Washington and getting started on his journey as an entrepreneur. Sreeram made a strong impression, and since then we’ve had many touchpoints through the years with both him and the world-class team that he has brought together. In 2022, Sreeram gave an eye-opening talk in our summer research fellowship about EigenLayer and EigenDA, and last year, he and Soubhik, EigenLayer’s head of protocol research, published a comprehensive overview of the Cryptoeconomics of Slashing on our blog.\n\nToday, it’s a pleasure to announce that we’re leading EigenLayer’s Series B. We’re excited to partner with Sreeram and the whole team on building a platform that unlocks a new dimension of open innovation on top of Ethereum.\n\nBackground\n\nIt’s difficult to appreciate the full breadth of EigenLayer without first zooming out: In the beginning, there was Bitcoin. It was the first example of an entire blockchain that was built for the purpose of a single application, which at the time was ostensibly payments, but since then has turned out to be more like digital gold—a store of value, albeit a volatile one.\n\nThe genius of Ethereum was to unbundle the monolithic, single-app Bitcoin approach by separating consensus from the application logic that is built on top. Ethereum makes it possible for developers to write their own applications—in the form of smart contracts—that leverage the blockchain’s pooled security and computational resources. This change alone unlocked a huge design space for open innovation which has led to almost everything we know and love about the space today. It means that people can now build decentralized applications without having to spin up their own blockchains.\n\nEthereum’s greater level of programmability has been a huge unlock for a whole set of applications. But, it’s not without limitations. It still mandates a lot about what you can and cannot do as a developer. For example, the code you write must be compatible with the Ethereum Virtual Machine (EVM), which will continue to be a great computational model for certain applications—those that are lightweight enough to fit within Ethereum’s block-size and gas limits—but not for others that might be heavier-weight or need specialized features.\n\nIn an ideal world, you as a developer should have almost complete freedom. If you need to, you should be able to build a decentralized service with code for any instruction set, your own consensus mechanism, your own data propagation algorithm, your own block time and gas limits, and even your own set of hardware requirements for validators (like GPUs or trusted execution environments). You would be able to do all of that without having to spin up your own blockchain network from scratch. Instead, you would be able to build on top of the already decentralized and secure validator set of the most secure programmable blockchain: Ethereum.\n\nEnter EigenLayer\n\nEigenLayer is a set of smart contracts on Ethereum that creates a two-sided marketplace for raw cryptoeconomic security: On the demand side, it allows creators of custom decentralized services to write code that effectively extends the functionality of Ethereum. And, on the supply side, validators participating in Ethereum consensus—if they happen to have the capacity and required hardware—can opt into running each of those decentralized services by restaking their ETH to them. The net result is that EigenLayer is a decentralized and market-based mechanism for extending Ethereum’s capabilities.\n\nThe implications of this are profound. We believe that, by further unbundling cryptoeconomic security from the EVM, EigenLayer has the potential to unlock 100x faster innovation on technologies like consensus mechanisms, novel virtual machines, decentralized oracles, bridges, and networks with specialized hardware in the same way that Ethereum unlocked 100x faster innovation at the application logic level by introducing smart contracts.\n\nWe’re very excited to partner with Sreeram and team to help them bring this vision to life.\n\n* * *\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nCharts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":1890,"crawled_at":1791195813942}
+{"id":10566,"url":"https://docs.sui.io/develop/objects/object-ownership","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Types of Object Ownership | Sui Documentation","text":"Every objectObjectThe basic unit of storage on Sui. has an owner that determines who can use it in transactions and whether the object is versioned on the fastpath or through consensusConsensusThe process by which the majority of nodes agree on the current state of the network. The ownership type you choose affects transactionTransactionA number of commands that execute on inputs to define the result of the transaction. latency, concurrency, and the security model your smart contract must enforce.\n\nOwnership typeAccess modelVersioning pathTypical latency\nAddress-owned\nA single addressAddressA unique, anonymous identity on a blockchain network. can use the object.\nFastpath\nLowest (no contention on the object)\n\nShared\nAny address can use the object, subject to MoveMoveAn open source programming language used for all activity on Sui. checks.\nConsensus\nHigher (consensus ordering required)\n\nImmutable\nAny address can read the object; no one can mutate it.\nFixed after it becomes immutable\nLowest (read-only, no versioning)\n\nWrapped\nOnly accessible through the object that wraps it.\nDepends on the wrapper\nDepends on the wrapper\n\nConsensus-address owned / party\nA single address owns the object, but the object is sequenced by consensus.\nConsensus\nHigher (consensus sequencing)\n\nChoosing an ownership type​\n\nChoose the ownership type based on your access pattern.\n\nUse address-owned objects when a single user owns and controls the object (for example, a user's NFT, a personal wallet, or a capability token). Only the owner can use an address-owned object, so there is no contention for it, and the sender names the version in the object reference rather than waiting for consensus to assign one.\n\nUse shared objects when multiple users need to read and write the same object (for example, a marketplace, a liquidity pool, or a game board). Shared objects go through consensus, which adds latency but enables concurrent access. Contention on a single shared object can reduce transaction throughput, so minimize the number of transactions that write to the same shared object in the same checkpointCheckpointCreated after transaction execution to provide a certified record of chain history. (Security Best Practices).\n\nUse immutable objects for data that never changes after creation (for example, published packagesPackageSmart contracts on Sui., configuration constants, or reference data). Immutable objects have no versioning overhead, and any number of transactions can read the same one concurrently.\n\nUse wrapped objects when an object should only be accessible through its parent (for example, a ticket inside an envelope, or inventory items inside a character). See Wrapped Objects for details.\n\nAddress-owned​\n\nUse address-owned objects when a single user owns and controls the object (for example, a user's NFT, a personal wallet, or a capability token). Only the owner can use an address-owned object, so there is no contention for it, and the sender names the version in the object reference rather than waiting for consensus to assign one.\n\nShared​\n\nUse shared objects when multiple users need to read and write the same object (for example, a marketplace, a liquidity pool, or a game board). Shared objects go through consensus, which adds latency but enables concurrent access. Contention on a single shared object can reduce transaction throughput, so minimize the number of transactions that write to the same shared object in the same checkpoint.\n\nImmutable​\n\nUse immutable objects for data that never changes after creation (for example, published packages, configuration constants, or reference data). Immutable objects have no versioning overhead, and any number of transactions can read the same one concurrently.\n\nWrapped​\n\nUse wrapped objects when an object should only be accessible through its parent (for example, a ticket inside an envelope, or inventory items inside a character). See Wrapped Objects for details.\n\nParty​\n\nUse party objects when you want single-address ownership but need to allow multiple inflight transactions against the same object without fastpath locks. Party objects are sequenced by consensus but owned by a single address.\n\nAPIs expose consensus-address-owned objects with a ConsensusAddressOwner owner variant. Party objects are the public Move-facing way to create this ownership form with sui::party::Party and sui::transfer::party_transfer or sui::transfer::public_party_transfer.\n\ncaution\nAnyone can submit a transaction that references a shared object. Shared-object access is not restricted by ownership, so secure it in Move with explicit authorization checks (such as a capability argument, a tx_context::sender() check, or validating object ownership). Do not assume that referencing a shared object implies the caller is authorized. See Access control.\n\nAddress-Owned Objects\nAddress-owned objects are owned by a Sui 32-byte address, which can either be an account address or an object ID. Learn how to create and access these objects.\n→\nShared Objects\nAnyone can access shared objects on the Sui network, so care must be taken to secure access, if needed.\n→\nImmutable Objects\nImmutable objects cannot be changed, transferred, or deleted. Immutable objects cannot have an owner and anyone can use them.\n→\nWrapped Objects\nWrapped objects are object data structures nested inside of another object data structure. Objects can be wrapped directly, through `Option`, or through `vector` fields.\n→\nParty Objects\nParty objects are owned by a specified party at the time of transfer and versioned by consensus. Learn how to create, transfer, and access these objects.\n→\n\nChoosing an ownership type\n\nWas this page helpful?","tokens":1423,"crawled_at":1791195816161}
+{"id":10567,"url":"https://www.metaplex.com/docs/smart-contracts/bubblegum-v2/create-trees","domain":"www.metaplex.com","chapter":"docs","title":"Creating Bubblegum Trees - Bubblegum V2 - Metaplex","text":"Summary\nCreating a Bubblegum Tree is the first step before minting compressed NFTs. This page covers how to create and fetch the two required on-chain accounts: the Merkle Tree account and the TreeConfigV2 PDA.\nCreate a Bubblegum Tree with configurable max depth, max buffer size, and canopy depth\nChoose tree parameters based on your project's cNFT capacity needs (16K to 1B+ cNFTs)\nFetch merkle tree and tree config account data after creation\nUnderstand the cost tradeoffs for different tree configurations\nIntroduction\nWhilst the data of Compressed NFTs is stored inside transactions and not onchain accounts, we still need some onchain accounts to keep track of the Merkle Tree and its configuration. As such, before we can start minting Compressed NFTs, we need to create two accounts:\nA Merkle Tree account. This account holds a generic Merkle Tree that can be used to verify the authenticity of any type of data. It is owned by the MPL Account Compression Program forked from the SPL Account Compression Program. In our case, we will use it to verify the authenticity of Compressed NFTs.\nA TreeConfigV2 account. This second account is a PDA derived from the address of the Merkle Tree account. It allows us to store additional configurations for the Merkle Tree that are specific to Compressed NFTs — e.g. the tree creator, the number of minted cNFTs, etc.\nWith these two accounts, we have everything we need to start minting Compressed NFTs. Note that, we will refer to Merkle Tree accounts with associated Tree Config accounts as Bubblegum Trees.\n\nMerkle Tree Account\n\nOwner: Account Compression Program\n\nPDA\n\nTree Config Account\n\nOwner: Bubblegum Program\n\nReact Flow\nPress enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.\nPress enter or space to select an edge. You can then press delete to remove it or escape to cancel.\n\nCreating a Bubblegum Tree\nLet's now see how one can create both of these accounts to create a Bubblegum Tree. Fortunately, our libraries make this process easy by providing a Create Tree operation that takes care of everything for us. This operation accepts a variety of parameters — most of them optional — that allow us to customize the Bubblegum Tree to our needs. The most important ones are:\nMerkle Tree: A newly generated signer that will be used to create the Merkle Tree account. The Merkle Tree account will then be accessible at this address.\nTree Creator: The address of the account that will be able to manage the Bubblegum Tree and mint Compressed NFTs.\nMax Depth and Max Buffer Size: The Max Depth parameter is used to compute the maximum number of leaves — and therefore Compressed NFTs — that the Merkle Tree can hold. This maximum is calculated by 2^maxDepth. The Max Buffer Size parameter indicates the minimum concurrency limit of the Merkle Tree. In other words, it defines how many changes can happen in the tree in parallel. These two parameters cannot be chosen arbitrarily and have to be selected from a predefined set of values as displayed in the table below.\nBelow is an interactive calculator to help you estimate tree creation costs. Enter the number of cNFTs you need, or use the advanced mode to fine-tune all tree parameters and see how they affect cost, proof size, and tree structure.\n\nHow many compressed NFTs do you need?\n\nClosest tree depth: 20 (holds up to 1,048,576 cNFTs)\nBubblegum requires a minimum canopy depth of 3 for this tree size. Only 17 proof accounts fit in a single transaction.\n\nMinimum cost\n0.3122 SOL\nCanopy 3 (Bubblegum minimum)\nCanopy depth3\nProof size17 nodes (544 bytes)\nCost per cNFT0.00000030 SOL\n\nBalanced\n7.61 SOL\nModerate canopy — good composability\nCanopy depth14\nProof size6 nodes (192 bytes)\nCost per cNFT0.00000725 SOL\n\nMaximum composability\n58.69 SOL\nFull canopy — smallest proof size\nCanopy depth17\nProof size3 nodes (96 bytes)\nCost per cNFT0.00005597 SOL\n\nCanopy (on-chain)Proof nodesLeaves (cNFTs)\n\nBelow are our recommended tree settings for compatibility within the Solana ecosystem.\nNumber of cNFTsTree DepthCanopy DepthConcurrency BufferTree CostCost per cNFT\n16,384\n14\n8\n64\n0.3358\n0.00002550\n\n65,536\n16\n10\n64\n0.7069\n0.00001579\n\n262,144\n18\n12\n64\n2.1042\n0.00001303\n\n1,048,576\n20\n13\n1024\n8.5012\n0.00001311\n\n16,777,216\n24\n15\n2048\n26.1201\n0.00000656\n\n67,108,864\n26\n17\n2048\n70.8213\n0.00000606\n\n1,073,741,824\n30\n17\n2048\n72.6468\n0.00000507\n\nThe max depths of trees are as follows:\n\nPublic: Whether or not the Bubblegum Tree should be public. If it is public, anyone will be able to mint Compressed NFTs from it. Otherwise, only the Tree Creator or the Tree Delegate (as discussed in Delegating cNFTs) will be able to mint Compressed NFTs.\nHere is how one can create a Bubblegum Tree using our libraries:\nCreate a Bubblegum Tree\n\nimport { generateSigner } from '@metaplex-foundation/umi'\n\nimport { createTreeV2 } from '@metaplex-foundation/mpl-bubblegum'\n\nconst merkleTree = generateSigner(umi)\n\nconst builder = await createTreeV2(umi, {\n\nmerkleTree,\n\nmaxBufferSize: 64,\n\nmaxDepth: 14,\n\n})\n\nawait builder.sendAndConfirm(umi)\n\nBy default, the Tree Creator is set to the Umi identity and the Public parameter is set to false. However, these parameters can be customized as shown in the example below.\nconst customTreeCreator = generateSigner(umi)\n\nconst builder = await createTreeV2(umi, {\n\n// ...\n\ntreeCreator: customTreeCreator,\n\npublic: true,\n\n})\n\nFetching a Bubblegum Tree\nSince a Bubblegum Tree is composed of two onchain accounts, let's see how to fetch either of them.\nFetching a Merkle Tree\nThe Merkle Tree account contains various information about the tree such as:\nThe Tree Header which stores the Max Depth, the Max Buffer Size, the Authority of the tree and the Creation Slot of when the tree was created.\nThe Tree itself which stores low-level information about the tree such as its Change Logs (or roots), its Sequence Number, etc. We talk more about Concurrent Merkle Trees in a dedicated page of this documentation.\nThe Canopy as discussed in the Merkle Tree Canopy page.\nHere is how one can fetch all of that data using our libraries:\nFetch a Merkle Tree\n\nimport {\n\nfetchMerkleTree,\n\n} from \"@metaplex-foundation/mpl-account-compression\";\n\nconst merkleTreeAccount = await fetchMerkleTree(umi, merkleTree)\n\nFetching a Tree Config\nThe Tree Config account contains data specific to Compressed NFTs. It stores:\nThe Tree Creator of the Bubblegum Tree.\nThe Tree Delegate of the Bubblegum Tree, if any. Otherwise, it is set to the Tree Creator.\nThe Total Capacity of the Bubblegum Tree which is the maximum number of cNFTs that can be minted from the tree.\nThe Number Minted which keeps track of the number of cNFTs minted into the tree. This value is important as it is used as a Nonce (\"number used once\") value for operations to ensure the Merkle tree leaves are unique. Thus, this nonce acts as a tree-scoped unique identifier of the asset.\nThe Is Public parameter which indicates whether or not anyone can mint cNFTs from the tree.\nIs Decompressible is only valid for Bubblegum V1.\nVersion is the version of the LeafSchema that can be used.\nHere is how one can fetch all of that data using our libraries:\nFetch a Tree Config\n\nimport { fetchTreeConfigFromSeeds } from '@metaplex-foundation/mpl-bubblegum';\n\nconst treeConfig = await fetchTreeConfigFromSeeds(umi, { merkleTree });\n\nNotes\nTree parameters (max depth, max buffer size, canopy depth) are immutable after creation. Choose carefully based on your project's needs.\nLarger trees cost more in rent but have a lower per-cNFT cost. See the recommended settings table above for cost estimates.\nThe Tree Creator is stored in the TreeConfigV2 account and can delegate minting authority to another account (see Delegating Trees).\nPublic trees allow anyone to mint. Private trees restrict minting to the Tree Creator or Tree Delegate.\nFAQ\nHow do I choose the right tree size for my project?\nUse the recommended settings table. For small projects or testing, a depth-14 tree holds 16,384 cNFTs at ~0.34 SOL. For large collections, a depth-20 tree holds 1 million cNFTs at ~8.5 SOL. For very large drops, depth-24+ trees hold millions to billions of cNFTs.\nCan I change the tree size after creation?\nNo. The max depth, max buffer size, and canopy depth are all fixed at creation time and cannot be modified. If you need different parameters, you must create a new tree.\nWhat is the relationship between max depth and tree capacity?\nThe maximum number of cNFTs a tree can hold is calculated as 2^maxDepth. For example, maxDepth=14 supports 16,384 cNFTs, maxDepth=20 supports 1,048,576, and maxDepth=30 supports over 1 billion.\nWhat does the max buffer size control?\nThe max buffer size determines the minimum concurrency limit — how many modifications can happen to the tree within the same Solana block. Higher values allow more parallel transactions (mints, transfers, burns) but increase the tree's rent cost.\nGlossary\nTermDefinition\nBubblegum Tree\nThe combination of a Merkle Tree account and its associated TreeConfigV2 PDA\n\nMerkle Tree Account\nThe on-chain account holding the merkle tree data, owned by the MPL Account Compression Program\n\nTreeConfigV2\nA PDA derived from the Merkle Tree address, storing Bubblegum-specific config (creator, delegate, capacity, mint count, public flag)\n\nMax Depth\nThe maximum depth of the merkle tree, determining capacity as 2^maxDepth\n\nMax Buffer Size\nThe number of change log entries stored, determining how many concurrent modifications the tree supports per block\n\nCanopy Depth\nThe number of upper tree levels cached on-chain, reducing proof sizes in transactions\n\nTree Creator\nThe account that created the tree and has authority to manage it and mint cNFTs\n\nTree Delegate\nAn account authorized by the Tree Creator to mint cNFTs on their behalf","tokens":2460,"crawled_at":1791195849695}
+{"id":10568,"url":"https://docs.sui.io/develop/objects/versioning","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Object Versioning | Sui Documentation","text":"Every objectObjectThe basic unit of storage on Sui. stored onchain is referenced by an ID and version. When a transactionTransactionA number of commands that execute on inputs to define the result of the transaction. modifies an object, it writes the new contents to an onchain reference with the same ID but a new version. Despite appearing multiple times in the store, only the latest version of an object is available to transactions. Only one transaction can modify an object at a given version, guaranteeing a linear history.\n\n(I, v0) => ...\n(I, v1) => ... # v0 < v1\n(I, v2) => ... # v1 < v2\n\nVersions are strictly increasing and (ID, version) pairs are never re-used. This allows node operators to prune old object versions from their stores, though they might also retain them to serve historical requests or help other nodes catch up.\n\nObject versioning paths​\n\nObjects on Sui are versioned either through the fastpath or through consensus. The choice affects object ownership options and has performance trade-offs.\n\nSui uses Lamport timestamps in its versioning algorithm. This guarantees versions are never re-used: a transaction sets the new version for all objects it touches to 1 + max(version of all input objects). For example, a transaction transferring object O at version 5 using gasGasThe computational cost of execution and object storage for a transaction. object G at version 3 updates both to version 1 + max(5, 3) = 6.\n\nFastpath objects​\n\ntip\nIt is recommended to use party objects rather than fastpath objects.\n\nFastpath objects can only be address-owned or immutable. The sender names the exact version to use, so these objects need no consensusConsensusThe process by which the majority of nodes agree on the current state of the network-assigned version and do not contend with other transactions for one.\n\nEvery fastpath transaction must use the object's current version as input and use the output version as the reference for the next transaction. If a fastpath object is frequently used by multiple senders, coordinate offchain access or use a consensus object instead.\n\nYou must reference fastpath transaction inputs at a specific ID and version. Validators reject conflicting transactions that require the same mutable owned object version. Immutable objects are also referenced at a specific version, but do not need to be locked because their contents never change. Their version identifies the point at which they became immutable.\n\nFastpath is a good fit for applications that are extremely sensitive to latency or gas costs, do not need complex multi-party transactions, or already rely on an offchain coordination service.\n\nConsensus objects​\n\nConsensus objects can be address-owned, owned by a party, or shared. Consensus sequences reads and writes on these objects and assigns their versions, which can raise latency when multiple transactions contend for an object, but you manage versions more easily, especially for frequently accessed or multi-party objects.\n\nTransactions accessing multiple consensus objects or particularly popular objects might see increased latency due to contention. The trade-off is flexibility: multiple addressesAddressA unique, anonymous identity on a blockchain network. can access the same object in a coordinated way without offchain coordination.\n\nYou reference shared transaction inputs by ID, the version the object was shared at, and a flag indicating whether it is accessed mutably. You don't specify the precise access version because consensus determines that during scheduling, one transaction's output version becomes the next transaction's input version. Immutably referenced shared objects participate in scheduling but don't increment the object's version.\n\nConsensus is a good fit for applications that require coordination between multiple parties.\n\nWrapped and dynamic field objects​\n\nWrapped objects are not accessible by their ID in the object store, you must access them through the object that wraps them. You do not need to supply a wrapped object's ID or version as transaction input. Validators refuse to sign transactions that specify wrapped objects directly as inputs.\n\nWrapped objects can be unwrapped, after which they are accessible by their ID again. An object retains its ID across all wrap and unwrap events. Lamport timestamp versioning ensures the version at unwrap is always greater than the version at wrap.\n\nDynamic fields behave similarly: they are only accessible through their parent object and do not need to be supplied as transaction inputs. However, unlike wrapped objects, if a transaction modifies a dynamic object field, its version is incremented in that transaction. Lamport versioning also ensures that when a field is removed and re-added with the same name, the new Field object's version is strictly greater than the deleted one's, so (ID, version) pairs are never reused.\n\nWhy does object versioning matter?​\n\nUnderstanding object versioning helps you design applications correctly and avoid common mistakes:\n\nAvoid stale version references. If your client code caches an object version and another transaction modifies that object before yours executes, validators reject your transaction. Always fetch the latest version before submitting.\n\nChoose the right versioning path. Fastpath reduces latency for single-owner workflows. Consensus handles multi-party coordination without requiring offchain locking.\n\nPrune safely. Because (ID, version) pairs are never reused, node operators can safely prune old versions without risking collision with future writes.\n\nReason about history. The strictly increasing version sequence gives every object a linear, auditable history. Archival nodes can serve any historical version to clients that need it.\n\nRelated topics\n\nOperator Guides\nGuides for operators on the Sui network. Whether you are running a full node for your app or operating as a validator on the Sui network, these guides help you set up your environment and operate your network.\nConsensus\nOverview of the Sui consensus mechanism.\nParty Objects\nParty objects are owned by a specified party at the time of transfer and versioned by consensus. Learn how to create, transfer, and access these objects.\nAddress-Owned Objects\nAddress-owned objects are owned by a Sui 32-byte address, which can either be an account address or an object ID. Learn how to create and access these objects.\n\nObject versioning paths\nFastpath objects\nConsensus objects\nWrapped and dynamic field objects\nWhy does object versioning matter?\n\nWas this page helpful?","tokens":1643,"crawled_at":1791195838495}
+{"id":10569,"url":"https://docs.ethena.fi/technical-design/key-addresses","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Key Addresses | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nCore Contracts\nMint and Redeem Contract V1: https://etherscan.io/address/0x2cc440b721d2cafd6d64908d6d8c4acc57f8afc3\nMint and Redeem Contract V2: https://etherscan.io/address/0xe3490297a08d6fC8Da46Edb7B6142E4F461b62D3\nStaking Contract: https://etherscan.io/address/0x9d39a5de30e57443bff2a8307a4256c8797a3497\nUSDe Token Contract: https://etherscan.io/address/0x4c9edd5852cd905f086c759e8383e09bff1e68b3\nsUSDe Token Contract: https://etherscan.io/address/0x9d39a5de30e57443bff2a8307a4256c8797a3497\nsUSDe Rewards Distributions:\nhttps://etherscan.io/advanced-filter?fadd=0x71e4f98e8f20c88112489de3dded4489802a3a87&tadd=0x9D39A5DE30e57443BfF2A8307A4256c8797A3497&qt=1\nUSDe to sUSDe Staking Rewards Distributor Contract: https://etherscan.io/address/0xf2fa332bd83149c66b09b45670bce64746c6b439#tokentxns\nENA Token Contract:\nhttps://etherscan.io/address/0x57e114B691Db790C35207b2e685D4A43181e6061\nsENA Token Contract:\nhttps://etherscan.io/token/0x8bE3460A480c80728a8C4D7a5D5303c85ba7B3b9\nsENA Token Contract:\nhttps://etherscan.io/address/0x8be3460a480c80728a8c4d7a5d5303c85ba7b3b9\nrsENA Token Contract:\nhttps://etherscan.io/address/0xc65433845ecd16688eda196497fa9130d6c47bd8\nUSDtb PSM Contract: https://etherscan.io/address/0x73E35C5c35A274E34AdE6EB13cC7f62aEE323728\nToken Contracts on Other Chains\nBeyond Ethereum mainnet, Ethena tokens are available on the following chains:\n\nTON\n\nAptos\n\nBerachain\n\nSolana\n\nMantle\n\nBlast\n\nArbitrum\n\nOptimism\n\nBase\n\nZircuit\n\nZKSync\n\nBNB\n\nLinea\n\nManta\n\nScroll\n\nFraxtal\n\nMode\n\nXLayer\n\nMetis\n\nKava\n\nMorph\n\nSwell\n\nWith the exceptions of Solana, ZKSync, and Zircuit, token addresses on all chains are identical, as summarized below:\n\nChain\nENA\nUSDe\nsUSDe\n\nMost L2s (Other Than As Indicated Below)\n\n0x58538e6A46E07434d7E7375Bc268D3cb839C0133\n\n0x5d3a1Ff2b6BAb83b63cd9AD0787074081a52ef34\n\n0x211Cc4DD073734dA055fbF44a2b4667d5E5fE5d2\n\nSolana\n\n72QvBVwpxqmheEPfaCwWSWqEFsUy3rhWt6JhQBMNTwD1\n\nDEkqHyPN7GMRJ5cArtQFAWefqbZb33Hyf6s5iCwjEonT\n\nEh6XEPhSwoLv5wFApukmnaVSHQ6sAnoD9BmgmwQoN2sN\n\nTON\n\nEQAFhZFZYye0llsl785OzOJG9QT6PXyYUdmiC4U95lBuHh1S\n\nEQAIb6KmdfdDR7CN1GBqVJuP25iCnLKCvBlJ07Evuu2dzP5f\n\nEQDQ5UUyPHrLcQJlPAczd_fjxn8SLrlNQwolBznxCdSlfQwr\n\n(tsUSDe on TON)\n\nTempo\n\n0x20c0000000000000000000002F52D5CC21A3207B\n\nOFT: 0xf8b6aa0cee4e1ad87ee259dab5e556eb62297d7f\n\n0x20C000000000000000000000Bd95bFB69fBE6Ce3\n\nOFT: 0x100c123770be9015321a9fcfa4ae3e77dcb2cf1a\n\nAptos\n\n0xf37a8864fe737eb8ec2c2931047047cbaed1beed3fb0e5b7c5526dafd3b9c2e9\n\n0xb30a694a344edee467d9f82330bbe7c3b89f440a1ecd2da1f3bca266560fce69\n\nZKSync\n\n0x686b311F82b407f0be842652a98e5619F64cC25F\n\n0x39Fe7a0DACcE31Bd90418e3e659fb0b5f0B3Db0d\n\n0xAD17Da2f6Ac76746EF261E835C50b2651ce36DA8\n\nZircuit\n\n0x813635891aA06bd55036bbd8f7d1A34aB3de9a0F\n\n0x5d3a1Ff2b6BAb83b63cd9AD0787074081a52ef34\n\n0x211Cc4DD073734dA055fbF44a2b4667d5E5fE5d2\n\nChain\nEthena LP Staking\nMultisig\n\nSolana\n\nhttps://app.squads.so/squads/EWZCJs2JRo3tMKgDt8FGx7MccD8sKv4QEcdsY9ZhVKZA\n\nAptos\n\nhttps://app.rimosafe.com/home?safe=0x84c7ac376914733149586b28acf837f3ef20eee7fe8e28a19e1a135ffca676b9\n\nBerachain\n\nhttps://safe.berachain.com/home?safe=berachain:0x093d3F4785149A3d2600cb10D63aFa14f9b09364\n\nMantle\n\nhttps://etherscan.io/address/0x8707f238936c12c309bfc2b9959c35828acfc512#code\n\nhttps://multisig.mantle.xyz/home?safe=mantle:0x799a2Cd46CBc7FB53949072257e6331054A060Bb\n\nBlast\n\nhttps://blast-safe.io/home?safe=blast:0x689272B1D2B2F37a0B3fe1f5Af0420C64f6cc9E3\n\nArbitrum\n\nhttps://app.safe.global/home?safe=arb1:0xc9647361742Eb964965B461C44Bdf5c4Bc3c406d\n\nOptimism\n\nhttps://app.safe.global/home?safe=oeth:0xc66bbBf821f2cfB3a85683acF0326EAC92C160Bd\n\nBase\n\nhttps://app.safe.global/home?safe=base:0xbC89D10EB486b6591583F218acB9545087dBF293\n\nZKSync\n\nhttps://app.safe.global/home?safe=zksync:0xa026e9a5e54E16349D7b594449f32901E02C609a\n\nBNB\n\nhttps://app.safe.global/home?safe=bnb%3A0xc9647361742Eb964965B461C44Bdf5c4Bc3c406d\n\nLinea\n\nhttps://safe.linea.build/home?safe=linea%3A0xE1B9B4c7D664126Bf4B6724deb59Eb5F8Aab9192\n\nManta\n\nhttps://safe.manta.network/home?safe=manta%3A0xA408Fd6724341B27F2e348faf9eCCEc04A2299EA\n\nScroll\n\nhttps://safe.scroll.xyz/settings/setup?safe=scr:0xAFAFc5D0DF6830052988c76DD8d0DfA7f5B8FfD6\n\nFraxtal\n\nhttps://safe.mainnet.frax.com/home?safe=fraxtal:0xc66bbBf821f2cfB3a85683acF0326EAC92C160Bd\n\nMode\n\nhttps://safe.optimism.io/home?safe=mode:0x273ceD5b9da8F5ba6E40C82c126898cB5307B2ea\n\nXLayer\n\nhttps://app.safe.global/home?safe=xlayer:0xce2f77841A8B974CE8e79157BccBECf17599f0E8\n\nMetis\n\nhttps://metissafe.tech/home?safe=metis-andromeda:0x795dB361ED5727F3f27dccde15b7D0d975fC94e0\n\nKava\n\nhttps://app.oryy.io/home?safe=kava:0x10E9219dD188D0f3af30824469Dc874A539733B6\n\nZircuit\n\nhttps://safe.zircuit.com/home?safe=zircuit-mainnet:0x07762C592e243D4aDD1648A7Ab4916D898780bae\n\nLiquidity Pool Contracts\nUSDC x USDe Curve Pool:\nhttps://curve.fi/#/ethereum/pools/factory-stable-ng-12/deposit\ncrvUSD x USDe Curve Pool:\nhttps://curve.fi/#/ethereum/pools/factory-stable-ng-11/deposit\n\nFRAX x USDe Curve Pool:\nhttps://curve.fi/#/ethereum/pools/factory-stable-ng-35/deposit\nmkUSD x USDe Curve Pool:\nhttps://curve.fi/#/ethereum/pools/factory-stable-ng-68/deposit\n\nDAI x USDe Curve Pool:\nhttps://curve.fi/#/ethereum/pools/factory-stable-ng-100/deposit\n\nFDUSD x USDe Curve Pool:\n\nhttps://curve.fi/#/ethereum/pools/factory-stable-ng-166/deposit\n\nsDAI x sUSDe Curve Pool:\nhttps://curve.fi/#/ethereum/pools/factory-stable-ng-102/deposit\nUSDT x USDe Uniswap v3 Pool:\nhttps://info.uniswap.org/#/pools/0x435664008f38b0650fbc1c9fc971d0a3bc2f1e47\nMultisig Wallets\nDev\nhttps://etherscan.io/address/0x3b0aaf6e6fcd4a7ceef8c92c32dfea9e64dc1862\n\n5/11 signers.\n\nOwner of Ethena's deployed mainnet smart contracts & able to modify contract parameters.\n\nsUSDe Payout Fund\nhttps://etherscan.io/address/0x71e4f98e8f20c88112489de3dded4489802a3a87\n\n3/11 signers.\n\nDistributes USDe to Staking Rewards Distributor.\n\nReserve Fund\nhttps://etherscan.io/address/0x2b5ab59163a6e93b4486f6055d33ca4a115dd4d5\n\n4/10 signers.\n\nProtocol's funds to be disbursed when net negative funding (or other impairment to USDe's backing) occurs.\n\nUSDe PSM Custodian\nhttps://etherscan.io/address/0xD7fCaDe52aFb60FbF0E1E5F72A683F43820f56A0\n\nCoinbase MPC custody. The same address is used on each chain where a PSM is deployed.\n\nHolds pre-minted USDe inventory supporting Peg Stability Module (PSM) contracts on chains beyond Ethereum mainnet, enabling 1:1 swaps between USDe and supported stablecoins.\n\nUSDe held at this address is not in circulation and is excluded from circulating supply. It enters circulation only when swapped out against an equivalent value of backing assets received.\n\nBacking assets held at this address are included in the protocol's backing, as they already back circulating USDe (i.e., USDe not held in the PSM).\n\nLast updated 16 days ago\nWas this helpful?","tokens":1710,"crawled_at":1791195849107}
+{"id":10570,"url":"https://docs.ethena.fi/video-guides/how-to-stake-usde","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"How to Stake USDe | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nThe information contained in the following video or on this website is not directed at persons with their habitual residence or registered office in the European Union, European Economic Area, or United Kingdom.\n\nUsers in permitted jurisdictions can stake & unstake USDe/sUSDe via the UI.\nUsing the UI, the staking & unstaking USDe/sUSDe user workflow is:\n\nThe user requests to stake/unstake USDe/sUSDe via the dApp interface by clicking \"Stake\"/\"Unstake\", which pops up their selected wallet to sign the requested transaction.\n\nAfter the user signs the transaction with their wallet, the transaction is submit to the blockchain.\n\nUpon successful confirmation of the transaction, the user receives sUSDe/USDe as their USDe/sUSDe is atomically swapped via autonomous smart contract.\n\nImportant to Note\n\nUsers do NOT need to do anything but hold sUSDe to accrue rewards.\n\nRewards aren’t earned directly by sUSDe holders; rather, they accumulate within the staking contract, which results in the \"value\" of sUSDe rising over time in USDe terms. Users are able to unstake their sUSDe at any time, at which point they receive an amount USDe reflecting the staked amount plus any increase from the time the user staked until unstaking.\n\nThe amount of sUSDe a user will receive when staking USDe will depend on the current value of sUSDe. At launch the value was 1 sUSDe = 1 USDe, and sUSDe is expected to slowly increase in value in USDe terms as protocol discretionary rewards are transferred into the Staking smart contract.\n\nThis is because sUSDe was implemented using a token vault mechanism to provide protocol level incentive rewards to permitted users. This mechanic is similar to Rocketpool's rETH.\n\nTherefore, while a staker might receive less sUSDe than USDe staked, the value of the sUSDe in USDe terms will always be equal to or greater than the USDe staked.\n\nsUSDe is subject to a cooldown period before USDe can be withdrawn. The cooldown is dynamic (currently between 1 and 7 days) depending on reserve conditions; the current parameters are set by governance.\n\nUsers can only receive a positive or zero rewards holding sUSDe. The value of sUSDe will NOT decline, even in periods where the protocol is earning negative income, as the protocol does not and cannot remove assets from the staking contract. Such periods are expected to be covered by the Reserve Fund, to be discussed later.\n\nLast updated 2 months ago\nWas this helpful?","tokens":634,"crawled_at":1791195872990}
+{"id":10571,"url":"https://forum.solana.com/t/protocol-todos-2024/927","domain":"forum.solana.com","chapter":"governance_daos","title":"Protocol TODOs 2024 - Research - Solana Developer Forums","text":"Protocol TODOs 2024\n\nResearch\n\naccounts-db,\neconomics\n\nripatel-jump\n\nJanuary 9, 2024, 9:31am\n\n1\n\nHere are three protocol changes that I consider important to improve reliability and performance of the Solana network and the Firedancer client. In other words: My Solana-land New Year’s resolution for 2024.\n\n(Software optimization is a game of whack-a-mole)\n\nExecutable Format Simplification\n\nPreparing an on-chain program for execution should be as simple as mapping bytecode and data into virtual machine memory. In reality, loading a typical user program often takes longer than actually executing it.\n\nThis is mostly owed to historical choices to allow the protocol to execute the outputs of clang / rustc directly. This was thought to feature better developer experience than requiring some post-processing step.\n\nWhat resulted was an error-prone and inefficient format.\n\nThe situation is best explained by Firedancer’s implementation:\n\nhttps://github.com/firedancer-io/firedancer/blob/main/src/ballet/sbpf/fd_sbpf_loader.c\n\nA 1200 line code footprint in this context is not only slow, but also complicates cross-client compatibility testing.\n\nDesigning a replacement binary format is a trivial exercise. It is mostly a social issue, as it will require approval from all contributors to the virtual machine and compiler toolchain.\n\nOnce the new format is implemented, the old format should be retired.\n\nMy preferred solution thus far is a one-time sweep over the account database that converts all existing deployed programs. Any VM bytecode would be kept strictly identical, such that immutability of program code is preserved.\n\nLimiting State Growth\n\nThe state size of the Solana network is gradually approaching a point where it is no longer practical to keep in DRAM. In fact, it is technically unbounded due to an overly simplistic storage cost model.\n\nOne obvious solution is to spilling over to accounts to cheaper storage such as NVMe. But unless done very carefully, would kill any prospect of greatly increasing network performance.\n\nSolana is DRAM-heavy for reasons that this Intel technical paper neatly summarizes: https://www.intel.com/content/www/us/en/developer/articles/technical/memory-performance-in-a-nutshell.html\n\nKeeping account state in-memory allows on-chain programs to access arbitrary account data with consistently low latency. More importantly, current generation x86 systems can achieve total memory bandwidth of hundreds of gigabytes per second.\n\nWhen operating in a storage environment with highly asymmetric latency and bandwidth, a blockchain runtime will certainly become limited by I/O capabilities unless fee models become aware of account locality.\n\nFor example, writing ten 1MB accounts 1 million times each is going to be significantly faster than writing (10^6)x10MB accounts once, even though both cases write 10TB of data. The former would operate at a bandwidth of ~hundreds GB/s via L3 cache, the latter at least 100x slower)\n\nWith the goal of staying in DRAM territory in mind, let’s instead take measures to reduce state growth rate.\n\nAn effective first step to improve cost modeling is to dynamically increase storage fees as free space decreases. Currently, storage fees are implemented via a “minimum account balance” that can be fully reclaimed.\n\nI don’t expect that it is possible to achieve negative state growth with this dynamic alone, though. At least, not until exceedingly high fees make the network unusable.\n\nWhich leads us to the next research item.\n\nGeneric Account Compression\n\nDid you know that 76% of Solana accounts have not been accessed in the last 6 months? (Credit to @andrewhong5297 for this data point)\n\nContinuing from the above, there is significant opportunity to reduce the in-memory set of accounts.\n\nHash trees have become the de-facto standard approach to provide large amounts of state to on-chain programs (commonly called “compression” within Solana). Compressed program data consists of just the root of a concurrently modifiable hash tree. The original data itself will no longer get replicated across the blockchain network and is stored separately by whoever chooses to (such as in a p2p torrent network). But it can be recovered as needed. Currently, each program would have to include logic for state compression separately.\n\n@toly has suggested to introduce compression generically by introducing a new storage class of compressed accounts. To reclaim DRAM, the runtime would periodically sweep the database for the oldest accounts and evict them if their balance drops below a dynamic minimum (determined using the aforementioned state growth limiting mechanic).\n\nTo avoid complexities with storage asymmetry, the transactions that attempt to access compressed accounts would fail. Users can decompress their accounts at any time be re-uploading all data fragments, along with a cryptographic proof that the data was not tampered with.\n\nThe main difficulties lie in client/wallet “RPC” infrastructure and choosing an appropriate storage solution. Failure to do so risks data loss. Storage networks like Filecoin and Arweave are of particular interest.\n\nClosing Thoughts\n\nPreliminary design work for all of the above is under way at the Solana Labs and Firedancer. I hope to publish detailed designs and technical proposals for all three items in the coming weeks. As always, I’d love to invite the wider community for discussion. I’m curious what you think.\n\n13 Likes\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nState growth problem - Accounts Lattice Hash\n\nSIMD\n\n0\n\n316\n\nJanuary 9, 2025\n\nGeneralized State Compression\n\nRFP\n\n3\n\n1216\n\nAugust 2, 2024\n\nFeature: Accounts Index on Disk (1.14.17)\n\nReleases\n\n114\n,\nfeature\n\n0\n\n2109\n\nMay 4, 2023\n\nsRFC 00002: Off-Chain Instruction Account Resolution\n\nsRFC\n\naccount-resolution\n,\ninterfaces\n,\nspl\n,\nanchor\n\n4\n\n1057\n\nApril 16, 2025\n\nsRFC 21 - Nested Account Resolution\n\nsRFC\n\naccount-resolution\n,\ninterfaces\n,\nprogram-interface\n,\ncpi\n\n0\n\n749\n\nJanuary 15, 2024","tokens":1500,"crawled_at":1791195873925}
+{"id":10572,"url":"https://blog.trailofbits.com/2024/10/01/securing-the-software-supply-chain-with-the-slsa-framework","domain":"blog.trailofbits.com","chapter":"security_audits","title":"Securing the software supply chain with the SLSA framework - The Trail of Bits Blog","text":"Page content\n\nSoftware supply chain security has been a hot topic since the Solarwinds breach back in 2020. Thanks to the Supply-chain Levels for Software Artifacts (SLSA) framework, the software industry is now at the threshold of sustainably solving many of the biggest challenges in securely building and distributing open-source software.\nSLSA is a security standard that helps a consumer verify the process by which an open-source software artifact was created. Its cornerstone is a provenance file, a document signed by a build platform attesting to how a binary, container image, or other file was generated from source code through a project-specific build pipeline. However, SLSA is a relatively new standard (version 1.0 was released in April 2023), and in order for its benefits to be fully realized, multiple parties need to adopt and implement it. In addition to the technical work involved, it will also take time to build awareness and drive demand for SLSA-compliant tooling.\nTo expedite adoption of SLSA, we’ve drafted PEP 740, a specification that adds support for SLSA provenance to PyPI and leverages the power of trusted publishing. However, there’s no need to wait for all of this work to be fully realized to realize the benefits of SLSA. Read on to learn how you can take advantage of existing SLSA support and help promote good supply chain security practices among your customers and vendors.\nOverview of SLSA\nSLSA 1.0 specifies three different levels of compliance, called SLSA Build Level 1, 2 and 3, that can be achieved through the publication of a suitable build provenance file. This file identifies the build platform itself (usually a hosted CI/CD platform, such as GitHub Actions or Google Cloud Build) and the configuration parameters used to generate the final build artifact. In the case of a GitHub Actions build, the provenance file will identify the workflow definition file, the repository and tag that were built, and any other applicable inputs, such as the ID of the pull request that triggered the build. Additionally, the platform should make a best-effort attempt to list all of the project’s direct and indirect dependencies.\nLevel 1 compliance provides visibility into the build process so that honest mistakes can be caught: the provenance file need only include the data described above and be published in an accessible location. Level 2 ensures the authenticity of the build provenance file. The key requirements are that the provenance file must be signed by the build platform, and the build must be run on dedicated infrastructure. At Level 3, additional build platform hardening prevents forgery of the provenance file. The build platform must prevent user-defined steps in the build process from accessing the signing key, and no two builds should be able to influence each other in any way, whether they run in series or in parallel.\nMost attacks against build and distribution processes will face substantial obstacles if the targeted project has reached SLSA Level 3 compliance. An attacker who compromises package upload credentials would still need to compromise the provenance signing key in order to forge a valid provenance file for their malicious binary or container image. If an attacker somehow tampered with the parameters to the build process, any changes would be reflected in the provenance file. (Starting at Build Level 2, the build parameters shown in the provenance must be read directly from the build platform, not provided separately by the entity invoking the build.) Moreover, if signed provenance is uploaded to a service with a public transparency log like Sigstore, any such attack would be conducted in the open with immediate visibility into each build that was altered.\nA growing list of build platforms have built-in support for SLSA, allowing projects to reach Level 3 by invoking pre-written build pipeline steps. From the consumer side, the slsa-verifier project provides configurable tooling to verify a published provenance file.\nThe final step: Integration into package ecosystems\nWith all this tooling already implemented, it seems like the benefits of SLSA are already within reach. But there’s one more piece to the puzzle: integration of this SLSA-compliant tooling into the package distribution tools developers use on a daily basis. This final step requires operational decisions that are in the purview of the package management system, not the SLSA framework itself. For example, how does a downstream user know which build platforms a project will use? When is a project permitted to switch build platforms between versions? Is it acceptable for some releases to have signed Level 3 provenance, but others to have only Level 1 provenance?\nIf these questions are left unanswered, some threats can slip through the cracks. Suppose an attacker steals package upload credentials for a project that normally provides signed Level 3 provenance files, then uploads an artifact with unsigned Level 1 provenance. How can consumers protect themselves in that scenario? The community would need to agree on a convention for handling SLSA level downgrades, preferably with automatic enforcement in package publishing and distribution tools.\nThese outstanding issues are the reason why the benefits of SLSA are not yet fully realized. The reference implementations of SLSA tooling lay the groundwork, but it is up to each package management system to operationalize the framework so that consumers do not have to manually resolve ambiguities.\nPEP 740 and provenance in PyPI\nNow would be a good time to highlight the in-progress PEP 740, a draft specification authored by Trail of Bits engineers William Woodruff and Facundo Tuesca to add support for SLSA provenance to PyPI. Thanks to the existing support for trusted publishing, each package’s build platform itself provides the trust mechanism for PyPI uploads through OIDC tokens issued to each build run. Provenance can piggyback on this process by using the same OIDC tokens to generate keyless signatures through Sigstore, then upload the provenance file to the registry along with the package. This design reduces the entire system’s attack surface so that a bad actor can only submit untrusted artifacts into PyPI by compromising the package source code, or by forging a GitHub OIDC token.\nTaking advantage of SLSA as a consumer\nDevelopment teams need not wait for PEP 740 and adoption of similar standards by other package managers to reap the benefits of SLSA incrementally. Some package managers already have built-in support for downloading and verifying signed provenance. With a little extra effort, slsa-verifier can be invoked independently in the case of software distribution tools that have not yet completed their integrations.\nAs of this writing, the package ecosystem with the most deeply integrated SLSA support is npm. Each package’s page on npmjs.com summarizes the latest version’s build provenance with a link to the relevant Sigstore transparency log. On the client side, the npm audit signatures command will automatically verify all available provenance for a project’s dependencies. This command’s output includes the number of packages with verified build attestation, but does not say which packages those are. Thus, the best way to leverage npm’s existing support is to run npm audit signatures on every build or dependency update and to manually review the dependency list if the number of packages with verified provenance unexpectedly decreases between builds.\nOther package managers do not yet automatically locate, download and verify provenance files and their signatures. Many SLSA-compliant projects host provenance in their release assets, and it is straightforward enough to script the process of downloading and verifying these files and their signatures. For projects with large numbers of dependencies, this manual setup does not scale well.\nOCI-compatible container registries allow image providers to upload provenance files as artifacts to the images, but there is no standardized way to designate the artifact as a provenance file and automate verification. Some registries, such as Google Artifact Registry, also use a vendor-specific interface for downloading provenance files.\nWe suggest prioritizing your SLSA verification work as follows.\nStart by configuring verification for container images. In practice, container image dependencies do not explode in number as quickly as software package dependencies, so verifying container dependencies can generate a lot of value quickly.\nImplement a SLSA checklist that must be completed for each new dependency distributed to your build system in a binary, container image, or other pre-built artifact. If the dependency publishes signed provenance, automate the process of obtaining and verifying the provenance file. Make sure that your build fails whenever provenance verification fails!\nInitiate a long-term workstream to add provenance verification to all existing dependencies. For projects with lots of dependencies, this step will take the most work. Set realistic target dates and work through your backlog at a reasonable pace.\nRequest SLSA provenance from your upstream vendors who do not already publish it. Make some noise about SLSA (politely, that is)! Let your partners know you are focused on supply chain security and are looking for providers who are too. If you have the resources, consider submitting your own pull requests to add SLSA compliance to your most critical dependencies.\nToward a secure software supply chain\nAs with many security problems, the ideal future state follows the “set it and forget it” pattern: ecosystems will deeply integrate build provenance so that package managers will work securely, or not at all, with no manual effort on consumers’ part. Until that day comes, SLSA-compliant projects should define their policies as clearly as possible so that users know exactly what to expect and when to reject an artifact. Specifically, if your project uses anything other than the official SLSA provenance generators, make sure consumers know which build platforms your project uses and how they can confirm that the signature is not just cryptographically correct, but comes from the correct source.\nLast but not least, if your project is SLSA compliant, include verification instructions in your documentation, and treat them as mandatory. Make sure your customers know that if they forget to verify your published provenance, they have skipped a critical step. Offering education to both software vendors and consumers is the key to reaching the critical mass of adoption that will solve supply chain security problems at scale.\nOur application security team can help your open-source project by auditing its build process, including build configuration, provenance distribution, and documentation, so that consumers can download and use your software with confidence. From the consumer’s side, our engineers can help you update your dependency management processes to gain the maximum value from vendors with existing SLSA support and prepare you as more organizations get on board. Contact us if you’re interested!","tokens":2801,"crawled_at":1791195897332}
+{"id":10573,"url":"https://docs.ethena.fi/resources/audits","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Audits | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nAt Ethena, the integrity of our smart contracts is paramount. We maintain this by conducting comprehensive audits, which help identify potential vulnerabilities, logical errors, or inefficiencies. These rigorous audits, carried out by industry experts, fortify our security and seek to increase trust in the platform.\nApproach to Audits\nEthena has undertaken a multi-phased audit program to ensure the highest level of security on the procotol.\nPhase 1: conducted initial audit with Zellic on the v1 of the protocol where no critical or high level vulnerabilities were found.\n\nPhase 2: architecture design review and economic risk factor analysis with Spearbit's Kurt Barry former Lead Engineer at MakerDAO\nPhase 3: phased audit with industry leading firms:\n\n-Quantstamp\n-Spearbit & Cantina\n\nPhase 4: independent audit with Pashov with individual experience of over 50 audits\nPhase 5: public audit with Code4rena\nPhase 6: economic and financial risk audit by Chaos Labs\nPhase 7: upcoming public bug bounty program with Immunefi\nReports\nZellic Audit on v1 of contracts\nOur initial audit on the first version of the contracts was performed by Zellic and was a success in that no critical, or high vulnerabilities were identified. The small and medium-level feedback and optimisations were reviewed and patched during the audit cycle.\n\nEthena x Zellic - Audit Report\nPDF · 395KB\n\nOpen\n\nQuantstamp Audit on v1 of contracts\nAttached is the audit report by Quantstamp completed on 18 Oct 2023. No critical or high level issues were identified.\n\nEthena x Quantstamp - Audit Report\nPDF · 887KB\n\nOpen\n\nSpearbit Audit on v1 of contracts\nAttached is the audit report by Speabit completed on 18 Oct 2023. No critical or high level issues were identified.\n\nSpearbit x Ethena - Audit Report\nPDF · 515KB\n\nOpen\n\nIndependent Audit by Pashov on v1 of contracts\nAttached is the audit report by Pashov completed on 22 Oct 2023. No critical or high level issues were identified.\n\nEthena x Pashov - Audit Report\nPDF · 217KB\n\nOpen\n\nPublic Code4rena Audit on v1 of contracts\nAttached is the audit report by Code4rena completed on 13 Nov 2023. No critical or high level issues were identified.\nEthena Labs Audit | Code4renaCode4rena | Keeping high severity bugs out of production\nIndependent Audit by Pashov on ENA and LP staking contracts\nAttached is the audit report by Pashov completed on December 22nd 2023.\n\nEthena-security-review (1).pdf\nPDF · 438KB\n\nOpen\n\nIndependent Audit by Pashov on V2 of contracts\nAttached is the audit report by Pashov completed on May 23th 2024.\n\nv2-audit.pdf\nPDF · 676KB\n\nOpen\n\nEconomics Audit and Risk Analysis by Chaos Labs on System Design\n\nChaos Labs - Ethena LST Market Risk Analysis\nPDF · 2MB\n\nOpen\n\nChaos Labs - Ethena Perpetual Assessment Report Final.pdf\nPDF · 5MB\n\nOpen\n\nChaos Labs - USDe On Chain Liquidity Assessment\nPDF · 2MB\n\nOpen\n\nIndependent Audit by Pashov on Staked ENA (sENA)\nAttached is the audit report by Pashov completed on 2 Sept 2024. No critical or high level issues were identified.\n\nEthena x Pashov - SENA Audit Report.pdf\nPDF · 936KB\n\nOpen\n\nQuantstamp Audit on USDTB\nAttached is the audit report by Quantstamp completed on 25 Oct 2024. No critical or high level issues were identified.\n\nEthena x Quantstamp - USTB.pdf\nPDF · 2MB\n\nOpen\n\nCyfrin Audit on USDTB\nAttached is the audit report by Cyfrin completed on 31 Oct 2024. No critical or high level issues were identified.\n\nEthena x Cyfrin - USTB.pdf\nPDF · 201KB\n\nOpen\n\nIndependent Audit by Pashov on USDTB\nAttached is the audit report by Pashov completed on 20 Oct 2024. No critical or high level issues were identified.\n\nEthena x Pashov - USTB.pdf\nPDF · 994KB\n\nOpen\n\nLast updated 1 year ago\nWas this helpful?","tokens":947,"crawled_at":1791195903591}
+{"id":10574,"url":"https://a16zcrypto.com/team/sriram-krishnan","domain":"a16zcrypto.com","chapter":"research","title":"Sriram Krishnan - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nSriram Krishnan\n\nFeed\nFilter\n(1)\nclear filters\n\ncategory\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\nrecommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nauthor\n(1) all authors\n@x0rart\n1337 Skulls Sers\na16z crypto\na16z crypto editorial\na16z crypto policy & regulatory teams\na16z crypto Regulatory Team\nAaditya Shidham\nAaron Levie\nAaron Phillips\nAaron Schnider\nAbby Green\nAbdou Ndiaye\nAbhi Shelat\nAbhiram Kothapalli\nAbigail Johnson\nAdam Alter\nAdam Back\nAdam Bry\nAdam Grant\nAdam Ludwin\nAdam Martin\nAdam Thierer\nAdam Zuckerman\nAdela Tomsejova\nAdena Friedman\nAdena Hefets\nAdeniyi Abiodun\nAdina Fischer\nAdrian Cockcroft\nAdrian Fenty\nAdrienne Mayor\nAgostino Capponi\nAiden Slavin\nAileen Lee\nAisha Stephenson\nAJ Shankar\nAlan Knott-Craig\nAlan Schaaf\nAlana Benton\nAlbert Tang\nAlec Nielsen\nAlec Ross\nAlejandro Flores\nAlex Constantinople\nAlex Honnold\nAlex Hutchinson\nAlex Immerman\nAlex Kreitz\nAlex Kroeger\nAlex Le\nAlex Masmej\nAlex Morcos\nAlex Price\nAlex Pruden\nAlex Rampell\nAlex Roetter\nAlex Solomon\nAlex Spector\nAlex Stamos\nAlex Tabarrok\nAlexander (Sasha) Spiegelman\nAlexander Chia\nAlexander Zoppa\nAlexandra Chang\nAlexandria Lafci\nAlexis Lakes\nAlexis Madrigal\nAlexis Ohanian\nAli Ghodsi\nAli Yahya\nAlicia Barone\nAlin Tomescu\nAlisha Litman\nAlison Mangiero\nAlison Martin\nAllison Pickens\nAlyssa Del Bene\nAlyssa Torres\nAmanda Cantor\nAmanda Cassatt\nAmanda Catherine\nAmanda Mulay\nAmanda Tuminelli\nAmanda Tyler\nAmelia Salyers\nAmie Tyrrel\nAmir Shevat\nAmira Yahyaoui\nAmy Abernethy\nAmy Berliner\nAmy Bohutinsky\nAmy Choice\nAmy Cray\nAmy Gill\nAmy Hoemeke\nAmy Kalokerinos\nAmy Robertson\nAna Mostarac\nAna Susi\nAnatoly Yakovenko\nAndie Taylor\nAndisheh Tahriri\nAndre Iguodala\nAndrea Clarke Hall\nAndrea Feinberg\nAndrea Rallo\nAndrea Simon\nAndrea Vinkler\nAndreas Papadimitropoulos, Jr\nAndreessen Horowitz\nAndrew Allen\nAndrew Chen\nAndrew F. Read\nAndrew Green\nAndrew Hall\nAndrew Lakis\nAndrew Lewis-Pye\nAndrew Lo\nAndrew Mason\nAndrew McAfee\nAndrew Milson\nAndrew Omori\nAndrew Radin\nAndrew Rubin\nAndrew Savage\nAndrew Smith\nAndrew Tretyakov\nAndy Beal\nAndy Coravos\nAndy Golden\nAndy Hill\nAndy Milenius\nAndy Rachleff\nAndy Tran\nAndy Walshe\nAneel Lakhani\nAngela Schenone\nAngela Strange\nAngela Tran Kingyens\nAngelica Gehr\nAniket Kate\nAnil Sethi\nAnish Acharya\nAnn Winblad\nAnna Berces\nAnna Jablonski\nAnna Semenova\nAnna Van Meurs\nAnnaLee Saxenian\nAnne Brandes\nAnne Lee Skates\nAnne Lewandowski\nAnne Mitchell\nAnne Yip\nAnnie Collins\nAnnie Duke\nAnthony Albanese\nAnthony Atala\nAnthony Foxx\nAnthony Lee Zhang\nAntonio Viggiano\nAntwone Stigall\nAnu Hariharan\nApril Roth\nAri Emanuel\nAri Juels\nArianna Huffington\nArianna Simpson\nArik Kershenbaum\nArmon Dadgar\nArnie Goldberg\nArsho Avetian\nArthur Brooks\nArun Sundararajan\nAsh Ashutosh\nAsha Christian\nAshley McCollum\nAshley Stern\nAshton Carter\nAtif Mian\nAtul Butte\nAubree Pelaez\nAubrey de Grey\nAugusto Marietti\nAurora Petracca\nAusten Allred\nAustin Guzman\nAustin Marchese\nAustin Wilson\nAva Iravani\nAvery Segal\nAvinash Solanky\nAviv Zohar\nAye Moah\nAzeem Azhar\nBailey Flanigan\nBailey Richardson\nBalaji Srinivasan\nBarry McCarthy\nBart Dessaint\nBeau Cronin\nBeau Woods\nBecky Pferdehirt\nBen Buckwalter\nBen Fielding\nBen Fisch\nBen Gardner\nBen Gomez\nBen Horowitz\nBen Kaufman\nBen Leventhal\nBen Lovell\nBen Napier\nBen Portney\nBen Rubin\nBen Scharfstein\nBen Schecter\nBen Silbermann\nBen Uretsky\nBen Wu\nBenedict Evans\nBenedikt Büenz\nBenjamin Ebner\nBenjamin Hindman\nBenjamin Wittes\nBenjamin Wu\nBennett Carroccio\nBenny Pinkas\nBernard J. Tyson\nBernard Tyson\nBeth Newman\nBethany Coates\nBharat Ramamurti\nBharath Ramsundar\nBill Carr\nBill Frist\nBill Hinman\nBill Janeway\nBill Krause\nBill Macaitis\nBlake Kim\nBlake Masters\nBlake Saari\nBlayne Donnell\nBob Iger\nBob Langer\nBob Moore\nBob Muglia\nBob Sutton\nBob Swan\nBob Tinker\nBob Wachter\nBobby Franklin\nBobby Green\nBobby Kotick\nBobby Wagner\nBoris Sofman\nBoris Wertz\nBrad Feld\nBrad Kern\nBrad Peterson\nBram Cohen\nBrandon Ballinger\nBrandon Barros\nBrandon Cherry\nBrandon Millman\nBrenda Kopf\nBrent McIntosh\nBrett Browman\nBrett Falk\nBrett Hagler\nBrewster Kahle\nBrian Armstrong\nBrian Balfour\nBrian Brooks\nBrian Crnkovich\nBrian Curran\nBrian Grazer\nBrian Koppelman\nBrian McCullough\nBrian Quintenz\nBrian Wilkins\nBridget McDowell\nBrittany Lucas\nBrittney Burrows\nBrooke Sheresky\nBruce Friedrich\nBryan Caplan\nBryan Chiang\nBryan Cox\nBryan Crowley\nBryan Faust\nBryan Houser\nBryan Kim\nBryan Pellegrino\nCaitlin Glazebrook\nCaitlin Johnston\nCaitlin Roberson\nCal Turner Jr.\nCaleb Christian\nCameron Schuler\nCamila De Souza\nCarine Carmy\nCarissa Bilinski\nCarl Agnelli\nCarl Eschenbach\nCarl Narcisse\nCarl Pope\nCarlos Araya\nCarolina Gonzalez\nCaroline Friedman\nCaroline Goggins\nCaroline Horn\nCaroline Moon\nCarolyn Bertozzi\nCarra Wu\nCasey Graul\nCasey Neistat\nCasey Winters\nCassady Churchill\nCassie Faerber\nCecilia Marshall\nCeia Font\nChad Rigetti\nChandra Krintz\nCharles Goetz\nCharles Hubbard\nCharles Koch\nCharlie Keinath\nCharlie Warzel\nChattry Meas\nChelsea Komlo\nChelsea Padilla\nCheng Li\nChris Bennett\nChris Best\nChris Burniske\nChris Curran\nChris DeWolfe\nChris Dixon\nChris Granger\nChris Hauth\nChris Lyons\nChris Messina\nChris Milk\nChris Power\nChris Santa Maria\nChris Wanstrath\nChristian Cachin\nChristian Catalini\nChristian Crowley\nChristian Seifert\nChristina Hampp\nChristina Lopes\nChristina Mercando\nChristina Xu\nChristina Zeidan\nChristine Darden\nChristine Perham\nChristopher Giancarlo\nChristopher Lee\nChristopher Mims\nChristopher Nguyen\nChristopher Rippingham\nChristopher Schroeder\nChristy Hubbard\nCiamac Moallemi\nCindi Zhang\nCindy Tenner\nClaire Austin\nClaire Cain Miller\nClaire Kart\nClaudia Picanco\nClay Shirky\nClayton Christensen\nClayton Gardner\nClifford Woolf\nClint Delapaz\nColin Bryar\nColin Rom\nCollin McCune\nConner Lyons Brown\nConnie Chan\nConnie Guglielmo\nConnor McCarthy\nConnor Moyles\nCorban Bell\nCorey Hawkins\nCorey Waller\nCourtney Dettlinger\nCraig Naylor\nCraig Walker\nCristina Cordova\nCurt Funderburk\nCuy Sheffield\nD'Arcy Coolican\nDaejun Park\nDaisy Linden\nDaisy Wolf\nDaljeet Virdi\nDalton Turay\nDan Berkenstock\nDan Boneh\nDan Frommer\nDan Primack\nDan Romero\nDan Shapero\nDan Siroker\nDan Stein\nDan Warmenhoven\nDan Wendlandt\nDaniel Chao\nDaniel Chen\nDanielle Andrzejewski\nDanielle Clark\nDanielle Looymans\nDanielle Lussier\nDanielle Morrill\nDanielle Shea\nDanny Shader\nDaphne Koller\nDapper Dan\nDaren Matsuoka\nDarin Malter\nDarshan Shankar\nDas Rush\nDave Jagoda\nDave King\nDave Touretzky\nDavid Banks\nDavid Belden\nDavid Damato\nDavid Deming\nDavid George\nDavid Haber\nDavid Hollestelle\nDavid Kerr\nDavid Lee\nDavid Mack\nDavid Madden\nDavid Marcus\nDavid Olson\nDavid Oyelowo\nDavid Pierce\nDavid Reich\nDavid Rumsey\nDavid Schweikert\nDavid Sinclair\nDavid Sverdlov\nDavid Tse\nDavid Ulevitch\nDavid Weiden\nDawn Lepore\nDawn Nott\nDeborah Embaie\nDeena Elitreby\nDeepak Maram\nDenis Nazarov\nDenis Young\nDenise Gonzalez\nDerek Dolin\nDerek Thompson\nDerrick Harris\nDevin Finzer\nDevon Zuegel\nDiana Peña\nDiane Greene\nDick Costolo\nDieter Shirley\nDiishan Imira\nDiogo Monica\nDominic Shine\nDominique Reliford\nDon Duet\nDon Faul\nDorris O'Brien\nDoug Ducey\nDoug Folden\nDoug McCracken\nDouglas Argueta\nDozie Uche\nDrew Coffman\nDylan Field\nDylan Rhodes\nEd Felten\nEd Lynch\nEddie Lim\nEddy Lazzarin\nEdith Zimmerman\nEdward Perkins\nEdwin Poston\nEfrat Noy\nEhud Shapiro\nEileen Burbidge\nEileen Wu\nElad Gil\nElaine Fuchs\nElaine Shi\nElena Burger\nEli Dourado\nElisa Leonhardt\nEliza Oak\nElizabeth Gunn\nElizabeth Harkavy\nElizabeth May\nElizabeth Ocken\nElizabeth Stark\nElizabeth Weil\nEllen Tunoa\nEmile Petrone\nEmilio Torres\nEmily Graff\nEmily Hinsch\nEmily Keir\nEmily Oster\nEmily Westerhold\nEmma Janaskie\nEric Budish\nEric Dai\nEric Ries\nEric Thomas\nEric Topol\nEric Wu\nErica Schecter\nErik Brynjolfsson\nErik Kiser\nErik Torenberg\nErika Bracken\nErika Herrera\nErika Louie\nErin Grody Kingsley\nErin Murphy\nErin Tice\nErin Tonnar\nErin Winkler\nErtem Nusret Tas\nEsther Shinn\nEthan Bueno de Mesquita\nEthan Ferreira\nEthan Zuckerman\nEuan Ashley\nEugene Volokh\nEugene Wei\nEugenia Yee\nEula Takahashi\nEva Sakkas\nEvan Burfield\nEvan Osnos\nEvangelos Simoudis\nEzra Klein\nF. Gary Gray\nFabiola Godinez\nFabrizio Zilibotti\nFahad Saleh\nFarid Jiandani\nFei-Fei Li\nFelix Do\nFEWOCIOUS\nFiona Kennedy\nFiona Murray\nFlashrekt\nFlora Oliveira\nFlori Del Valle\nFlorian Leibert\nFoteini Baldimtsi\nFrancesca Gino\nFrank Chen\nFrank Wilczek\nFred Benenson\nFred Ehrsam\nFred Upton\nFred Wilson\nFreda Lewis-Hall\nFrederic Kerrest\nFuture Editorial\nGabby Dizon\nGabby Reece\nGabriel Otte\nGabriel Vasquez\nGaetan Barthelemy\nGarrett Biel\nGary Ang\nGary Reedy\nGary Wolf\nGaurav Banga\nGaurav Dhillon\nGaut\nGayle Tzemach Lemmon\nGeoffrey Woo\nGeorg Fuchsbauer\nGeorg Petschnigg\nGeorge Church\nGeorge Danezis\nGeorge Fraser\nGeraldine Chan\nGérard Cachon\nGerard Ryle\nGerri Elliott\nGerry Tsoukalas\nGia Scinto\nGil Elbaz\nGil Shafir\nGina Moon\nGina Neff\nGina Yocom\nGinger Liau\nGokul Rajaram\nGoldie Chang\nGrace Ellis\nGraham Allison\nGrant Gregory\nGrant Jordan\nGrant LaFontaine\nGrant Rabenn\nGray Kinsella\nGreg Bowman\nGreg Clayman\nGreg Linares\nGreg Loehmann\nGreg Lynn\nGreg Solano\nGreg Truesdell\nGreg Waldon\nGregory Allen\nGregory Mundis\nGretchen Bush\nGretchen McCulloch\nGuido Appenzeller\nGustav Söderström\nGustavo Garcia\nGuy Goren\nGuy Raz\nGuy Wuollet\nHaley Van Dyck\nHanna Aziz\nHannah Frankl\nHanne Winarsky\nHaoyuan Li\nHarmit Malik\nHarry Grieve\nHarry Shum\nHarry Wright\nHatim Shafique\nHayden Adams\nHeather Gwynn\nHeather Podesta\nHedi Samar\nHelen Stoddard\nHelen Su\nHemant Mohapatra\nHendrik Pretorius\nHenri Kor\nHerb Lin\nHerman Narula\nHilmar Pétursson\nHoang Nguyen\nHoward Wu\nIan Dutra\nIan Shannon\nIan Sharp\nIce Cube\nIlan Zechory\nIllia Polosukhin\nIlyas Khan\nIma Christian\nIman Abuzeid\nInsiya Lokhandwala\nIon Stoica\nIrvin Chan\nIsa Guardalabene\nIsaiah Lott\nIsh Verduzco\nIsil Dillig\nIstván András Seres\nIttai Abraham\nIttay Eyal\nIva Messy\nIvan Linscott\nIvor Horn\nJ.D. Moriarty\nJack Donahoe\nJack Soslow\nJackie McQuiston\nJackson David\nJacob Westphal\nJacquelyn Melinek\nJad Esber\nJad Naous\nJade Lai\nJade Raymond\nJae Gnazzo\nJai Ramaswamy\nJaimie Buss\nJak Kennedy\nJake Auchincloss\nJakob Uszkoreit\nJamal Mohammed\nJames Beshara\nJames Currier\nJames da Costa\nJames Gwertzman\nJames J. Collins\nJames Kissell\nJames L. Madara\nJames Loftus\nJames Rathmell\nJames Rogers\nJames Watters\nJames Wu\nJames Zou\nJamie Brandon\nJamie McGurk\nJamie Sullivan\nJamilla Hemeid\nJana Odehnal\nJane Doe\nJane Lippencott\nJane Suh\nJanelle De Los Santos\nJared Bricklin\nJared Furutani\nJared Georgakopoulos\nJared Polis\nJared Smith\nJase Wilson\nJason Franklin\nJason Liu\nJason Mayden\nJason Milionis\nJason Mitchell\nJason Mok\nJason Rosenthal\nJason Warner\nJason Yanowitz\nJay Bradner\nJay Conte\nJay Drain\nJay Komarneni\nJay Rughani\nJean Reilly\nJeanne Tsan\nJeff Amico\nJeff Benson\nJeff Clark\nJeff Cordova\nJeff Glueck\nJeff Hawkins\nJeff Jones\nJeff Jordan\nJeff Lawson\nJeff Lu\nJeff Nagashima\nJeff Stump\nJeff Weiner\nJeffrey Immelt\nJeffrey Kaditz\nJeffrey Katzenberg\nJeffrey Kindler\nJeffrey Low\nJeffrey Silverstein\nJeffrey Zirlin\nJen Bulawsky\nJen Kha\nJenna Walsh\nJenna Zucker\nJennifer 8. Lee\nJennifer Doudna\nJennifer Kodner\nJennifer Konde\nJennifer Li\nJennifer Mumford\nJennifer Tejada\nJennifer Young\nJenny Cieplak\nJens Ernstberger\nJensen Harris\nJeremy Clark\nJeremy England\nJeremy Zhang\nJesse Holmes\nJesse Pollak\nJesse Walden\nJessica Childs\nJessica Hansen\nJessica Keeler\nJessica Patton\nJessica Verrilli\nJewel Pi\nJez Humble\nJi Kim\nJianying Luo\nJim Gilliam\nJimmy Chen\nJimmy Soni\nJing Wang\nJing Zou\nJJ Yu\nJoachim Neu\nJodi Lynn\nJodie Lutkenhaus\nJoe Gebbia\nJoe Grundfest\nJoe Montana\nJoe Morrissey\nJoe Schmidt\nJoe Sullivan\nJoel de la Garza\nJoel Mokyr\nJoel Monegro\nJoel Spolsky\nJoey Burleson\nJohn China\nJohn Collison\nJohn Fawcett\nJohn Garcia\nJohn Gedmark\nJohn Hennessy\nJohn Koelliker\nJohn M. Jack\nJohn Markoff\nJohn Menna\nJohn O’Farrell\nJohn Riccitiello\nJohn Smesko\nJohn Stanfield\nJohn Thompson\nJohn William Hatfield\nJonah Peretti\nJonathan Bush\nJonathan Dotan\nJonathan Downey\nJonathan Lai\nJonathan Lim\nJonathan Lusthaus\nJonathan Weissman\nJonathan Wong\nJordan Mazer\nJordan Stankowski\nJorge Conde\nJorge Gomez\nJose Guardado\nJoseph Bonneau\nJoseph Okpaku\nJoseph Spisak\nJosh Arnold\nJosh Bloom\nJosh Kim\nJosh Williams\nJoshua Browder\nJoshua Gans\nJoshua Grimm\nJoshua Hix\nJoshua Levin\nJoshua Lu\nJoshua Schank\nJoshua Soto\nJosie Ma\nJoyce Park\nJR Rivers\nJT Evans\nJuan Benet\nJudene Small\nJudy Savitskaya\nJudy Smith\nJulia Grace\nJulia Kirby\nJulie Bornstein\nJulie Farnham\nJulie Johnson\nJulie Samuels\nJulie Yoo\nJuliet Grier\nJuliet Nyatta\nJuliette Morton\nJulius Zhang\nJustin Bailey\nJustin Bethune\nJustin Blau\nJustin Cunningham\nJustin Gregorius\nJustin Kahl\nJustin Kan\nJustin Larkin\nJustin Paine\nJustin Pettit\nJustin Roberts\nJustin Simcock\nJustin Thaler\nJustine Moore\nJutta Steiner\nJyoti Bansal\nJZ Young\nKabir Gill\nKabir Laroia\nKais Khimji\nKamala Harris\nKaren Dunn\nKaren Wooley\nKarina Sobieski\nKarl Floersch\nkarma (Daniel Reynaud)\nKarmacoma\nKarthik Rau\nKartik Nayak\nKate Darling\nKate Dellolio\nKate Kerames\nKatherine Boyle\nKatherine Minarik\nKatherine Rundell\nKatherine Schoebel\nKathryn McKinley\nKathy Liu\nKathy Yang\nKatia Ameri\nKatie Baynes\nKatie Haun\nKatie Hemmerling\nKaty DeWitt-Drew\nKaty Nelson\nKayvon Tehranian\nKeener Barnhorst\nKeller Medlin\nKeller Rinaudo\nKelly Cannon\nKelsey Chaplinsky\nKelsey Mellard\nKen Chong\nKen Coleman\nKen Kocienda\nKerry Ganim\nKesha Cash\nKevin Chou\nKevin Chu\nKevin Dulsky\nKevin Kelly\nKevin McKinley\nKevin Nishioka\nKevin O'Kane\nKevin Rose\nKevin Tan\nKevin Wu\nKevin Zollman\nKidSuper\nKieran Snyder\nKierston Gittens\nKiki Mavridis\nKim Enright\nKim Malone Scott\nKim Milosevich\nKim Stevenson\nKim Zetter\nKimberly Tan\nKindra Mason\nKira Poskanzer\nKira Song\nKirstin Arbide\nKirt McMaster\nKofi Ampadu\nKouki Harasaki\nKrista Anderson-Copperman\nKristen Fortney\nKristen Johansson\nKristen Kee\nKristin Sauchak\nKristin Thayer\nKristina Graci-deLuna\nKristina Shen\nKristine Lipscomb\nKristo Käärmann\nKrisztina Holly\nKunal Bahl\nKunle Olukotun\nKurt House\nKyle Russell\nLaird Hamilton\nLatasha\nLaura Arrillaga-Andreessen\nLaura Baller\nLaura Behrens Wu\nLaura Deming\nLaura Gravley\nLaura Johnson\nLaura Shores\nLaura Weidman Powers\nLauren Berson\nLauren Illovsky\nLauren Murrow\nLauren Richardson\nLauren Spragge\nLaurene Powell Jobs\nLawrence Levy\nLawrence Summers\nLeah Cassidy\nLee Kleinman\nLee Lefkowitz\nLeeAnn Caballero\nLeila Hay\nLeila Janah\nLenny Rachitsky\nLeslie Jaw\nLeslie Vosshall\nLester Chen\nLi Fan\nLi Fei-Fei\nLi Jin\nLiang Wu\nLilian King\nLily Liu\nLina Sergie Attar\nLinda Banuelos\nLinda Xie\nLinden Tibbets\nLing Ren\nLinlin Li\nLinxin Wen\nLioba Heimbach\nLisa Hawke\nLisa Lambert\nLisa Orr\nLisa Reilly\nLisa Rosano\nLizzy Anderson\nLJ Erwin\nLloyd Dean\nLoretta Sanchez\nLori Potter\nLuca Prosperi\nLuca Zanolini\nLuis Martinez\nLuis von Ahn\nLuke Wroblewski\nLydia Green\nLynda Gibson\nLynn Rudolph\nMadan Nagaldinne\nMaddison Masaeli\nMadeline Lancaster\nMaggie Hsu\nMaggie Leung\nMaggie Romero\nMahad Abedin\nMahesh Iyer\nMahesh Vellanki\nMahimna Kelkar\nMakiri Duckett\nMalinka Walaliyadde\nMallesh M. Pai\nMalloy Evans\nManas Punhani\nManny Luna\nMarc Andreessen\nMarc Andrusko\nMarc Benioff\nMarc Levinson\nMarci Barbera\nMarco Reuter\nMargaret Jen\nMargit Wennmachers\nMaria LaMagna Morales\nMarian Garvin\nMarianne Winkler\nMariano Sorgente\nMaricarmen Alvarez\nMariel Goldenstein\nMarigold Vu\nMarina Kusserow\nMario Gabriele\nMario Linares\nMarissa Bramlett\nMark Cranney\nMark Leslie\nMark McAndrew\nMark McClusky\nMárk Melczer\nMark Moore\nMark Regan\nMark Sendak\nMarkos Georghiades\nMarkus Covert\nMarkus Funk\nMartha Lane Fox\nMartin Casado\nMartin Fischer\nMarty Makary\nMarvin Ammori\nMarvin Zamora\nMary Pat Jordan\nMary-Catherine Lader\nMaryam Bahrani\nMason Hall\nMatei Zaharia\nMatt Abrahams\nMatt Billmann\nMatt Bornstein\nMatt Clifford\nMatt Flannery\nMatt Fleming\nMatt Gleason\nMatt Kaeberlein\nMatt Levine\nMatt Levy\nMatt Oberhardt\nMatt Shortal\nMatt Spence\nMatt Weinberg\nMatthew Colford\nMatthew Green\nMatthew Haughey\nMatthew McCullough\nMatthew Mills\nMatthew Olsen\nMatthew Rutter\nMatthew Stein\nMatthieu Hafemeister\nMaureen Lara\nMax Kesten\nMax Krohn\nMax Levchin\nMax Polyak\nMax Resnick\nMax Ventilla\nMaya Rahkonen\nMcPherson Moore\nMeaghan Hardy\nMeg Whitman\nMegan Holston-Alexander\nMegan Kristalyn\nMehdi Hasan\nMehul Mehta\nMel Williams\nMelanie Galang\nMelissa Liao\nMelissa Minor\nMelissa Wasser\nMellody Hobson\nMelody Latronico\nMeredith Donahue\nMia Gonzalez\nMia Mandich\nMicah Johnson\nMichael Beckerman\nMichael Blau\nMichael Brandt\nMichael Chan\nMichael Copeland\nMichael Dearing\nMichael Dell\nMichael Franklin\nMichael Garcia\nMichael J. Casey\nMichael J. Freedman\nMichael Killam\nMichael King\nMichael Lee\nMichael Leiter\nMichael Morell\nMichael Ostrovsky\nMichael Ovitz\nMichael Paulus\nMichael Raynor\nMichael Reed\nMichael Snyder\nMichael Temkin\nMichael Wee\nMichael Zhu\nMichel Del Buono\nMichel Feaster\nMichèle Flournoy\nMichele Griffin\nMichele Korver\nMichele Law\nMichelle Ervin\nMichelle Kelso\nMichelle Kung\nMichelle Mundy\nMichelle Shin\nMichelle Ufford\nMichelle Volz\nMichelle Wilson\nMichelle Winn\nMichelle You\nMike Curtis\nMike Haydon\nMike Hearn\nMike Jones\nMike Kasperzak\nMike Kelly\nMike King\nMike Lempres\nMike Manning\nMike Maples jr\nMike Masnick\nMike Matchett\nMike Paulus\nMike Sandwick\nMikeal Rogers\nMikey Dickerson\nMiles Jennings\nMilijana Curic\nMiller Whitehouse-Levine\nMinerva Munoz\nMinnie Ingersoll\nMinsun Pak\nMintu Turakhia\nMiranda Christ\nMo Shaikh\nMohammad Akbarpour\nMohsen Malayeri\nMolly Grace\nMonique McCambridge\nMorgan Beller\nMorgan Bender\nMurat Pak\nMuriel Bowser\nMurray Shanahan\nMy Pham\nNadia Asparouhova\nNadia Eghbal\nNaftali Harris\nNaithan Jones\nNanjira Sambuli\nNaomi Metzger\nNashid Braswell\nNassim Eddequiouaq\nNat Barling\nNatacha Crooks\nNatalia Carrera\nNatalie Bucher\nNatalie Taumoepeau\nNate Chang\nNate Lau\nNathalie Balaban\nNathan McCauley\nNathan Yoon\nNathaniel Gleicher\nNathaniel Popper\nNav Singh\nNazanin Daneshvar\nNeel Maitra\nNeha Narula\nNelson Perla-Ward\nNeveen Bader\nNicholas Christakis\nNicholas Pacilio\nNick Babaian\nNick McKeown\nNick Quah\nNick Tomaino\nNicki Locker\nNicole Conner\nNicole Forsgren\nNicole Irvin\nNicole Neuman\nNicole Stanners\nNiels Provos\nNigel Robinson\nNikhil Krishnan\nNina Suthers\nNir Eyal\nNitasha Tiku\nNitin Natarajan\nNitya Subramanian\nNkiru Balonwu\nNoah Citron\nNoah Feldman\nNoah Levine\nNoah Smith\nNoam Nisan\nNoemi Glaeser\nO’Shea Jackson Jr.\nOlaf Carlson-Wee\nOleg Rogynskyy\nOliver Hsu\nOlivia Moore\nOlivia Webb\nOmri Weinstein\nOoshma Garg\nOprah Winfrey\nOrion Hindawi\nOscar Menjivar\nP.J. Hasleton\nPablo Montagnes\nPacky McCormick\nPak\nPalmer Luckey\nPamela Anderson\nPamon Forouhar\nParag Khanna\nParijat Talkad\nParker Brown\nParker Conrad\nPatrice Peck\nPatrick Byrne\nPatrick Collison\nPatrick Conway\nPatrick McCorry\nPatrick McHenry\nPatrick O’Grady\nPatrick Rivera\nPatrick Sutton\nPaul Cafiero\nPaul Daugherty\nPaul Davison\nPaul Krugman\nPaul Vigna\nPaula Long\nPenny Pritzker\nPerri Chilton\nPete Buttigieg\nPeter Blackwood\nPeter Buisseret\nPeter Chan\nPeter Donnelly\nPeter Johnson\nPeter Lauten\nPeter Leeson\nPeter Levine\nPeter Ludwig\nPeter Rubin\nPeter Thiel\nPeter Wang\nPetra Garrett\nPhil Daian\nPhil Hathaway\nPhil Wong\nPhong Nguyen\nPorter Smith\npplpleasr\nPranav Garimidi\nPrasad Akella\nPrat Moghe\nPreethi Kasireddy\npunk6529\nPurnima Padmanabhan\nPyrs Carvolth\nQasar Younis\nQuang Dao\nQuinten Burgunder\nQuintus Kilbourn\nRachael Horwitz\nRachel Goslins\nRachel Jenkins\nRachel Kalmar\nRachel McIntyre\nRachel Steiner\nRahul Iyer\nRahul Vohra\nRajeev Singh\nRajeev Venkayya\nRam Palaniappan\nRamana Jonnala\nRati Gelashvili\nRaul Vazquez\nRavi Parimi\nRay Dalio\nRaymond Carreira\nRebecca Lewis\nRebecca Rettig\nReed Hastings\nRefik Anadol\nRegina Benjamin\nRenato Valdés Olmos\nReshma Saujani\nReshma Sohoni\nRex Salisbury\nRich Ezekiel\nRichard Green\nRichard Menger\nRichard Rosenblatt\nRick Young\nRidhima Ahuja\nRiyaz Faizullabhoy\nRob Goodman\nRob McElhenney\nRob Pardo\nRob Rhinehart\nRobbie Petersen\nRobbie Peterson\nRobert Alexander\nRobert Cottrell\nRobert Hackett\nRobert Kolker\nRobert Leshner\nRobert McNeely\nRobert Moreno\nRobert Siegel\nRobert Stromberg\nRobert Weber\nRobin Casey\nRobin Guo\nRobin Weisman\nRod Johnson\nRodrigo Ibarra Lopez\nRodrigo Pacheco\nRoger Dickey\nRoger Wattenhofer\nRoham Gharegozlou\nRohini Mukand\nRohit Bansal\nRoman Mars\nRoman Stanek\nRon Gill\nRon Lavi\nRon Rothblum\nRonald Evans\nRonnie Harris\nRosa Davila\nRosalind Rattan\nRose Legarda\nRoss Andersen\nRoss Shuel\nRostin Behnam\nRuben Gallego\nRuben Smith\nRuss Altman\nRuss Heddleston\nRuss Roberts\nRussell Davies\nRyan Allen\nRyan Caldbeck\nRyan Conde\nRyan Holloway\nRyan Hoover\nRyan McEntush\nRyan Petersen\nRyan Prescott\nRyan Sandler\nRyan Spoon\nRyan Tseng\nRyan Walsh\nRyan Ward\nRyan Wyatt\nSaar Tochner\nSachin Jain\nSafi Bahcall\nSagar Dhawan\nSaku Panditharatne\nSalem Vance\nSam Blackshear\nSam Broner\nSam Gerstenzang\nSam Ragsdale\nSam Thompson\nSam Williams\nSam Yam\nSamantha Gelt\nSamantha Langford\nSamantha Ludwig\nSamson Wu\nSamuel Arbesman\nSamuel Hammond\nSandra Samayoa\nSandy Jen\nSankaet Pathak\nSantiago Rodriguez\nSara Boesen\nSarah Fazal\nSarah Hamburg\nSarah Lumbard\nSarah Mascardo\nSarah Meiklejohn\nSarah Porter\nSarah Rebello\nSarah Wang\nSasha Stiles\nSatish Talluri\nSaurabh Ladha\nSavannah Cherry\nScott Clark\nScott Duke Kominers\nScott Gottlieb\nScott Hassan\nScott Kupor\nScott Rubin\nScott Shenker\nScott Tyler\nScott Walker\nScott Weiss\nSean Duffy\nSean Neville\nSebastian Oddo\nSeema Amble\nSeemay Chou\nSep Kamvar\nSergiu Pasca\nSeth Lobree\nSeth Sivak\nSeth Sternberg\nShai Bernstein\nShai Kopeld\nShaka Senghor\nShakil Khan\nShan Sinha\nShana Fisher\nShane Mac\nShane Parrish\nShangda Xu\nShannon (Stubo) Brayton\nShannon Barbour\nShannon Kelly\nShannon Schiltz\nShannon Snow\nShari Doherty\nSharon Chang\nShawn Conway\nSheela Krothapalli\nShellye Archambeau\nSherie James\nSherriAnn Cole\nShishir Mehrotra\nShonda Rhimes\nSid Gorham\nSigne Pierce\nSimon Denny\nSiqi Chen\nSonal Chokshi\nSophie Song\nSoubhik Deb\nSpencer Dinwiddie\nSpencer Howard\nSpencer Rascoff\nSreeram Kannan\nSreevidya Kasturil\nSri Kosuri\nSriram Krishnan\nSrivatsan Sridhar\nStacey Cunningham\nStacey Merrick\nStacia Murray\nStacy Brown-Philpot\nStacy D'Amico\nStacy Warner\nStefan McDonough\nSten Tamkivi\nStephane Bancel\nStephanie Anyanwu\nStephanie Cohen\nStephanie Doppelt\nStephanie Smith\nStephanie Watkins\nStephanie Zinn\nStephen Armanios\nStephen Wink\nStephenie Zhang\nSteve Buress\nSteve Cadigan\nSteve Cheney\nSteve Harvey\nSteve Kaczynski\nSteve McDermid\nSteve Smith\nSteve Zhao\nSteven Adair\nSteven Ebert\nSteven Johnson\nSteven Levy\nSteven Sinofsky\nStewart Butterfield\nStina Ehrensvärd\nStuart Luman\nStuart Russell\nSudip Chakrabarti\nSue Hager\nSuhail Doshi\nSukhinder Singh Cassidy\nSumeet Singh\nSumit Shah\nSungMo Park\nSunil Chokshi\nSurya Ganguli\nSusan B. Wilde\nSusan Mernit\nSusan Rice\nSusannah Fox\nSydney Paul\nTaavet Hinrikus\nTaggart Matthiesen\nTamzen Brewis\nTana Billingsley\nTarek Mansour\nTarun Chitra\nTauri Laws Phillips\nTawny Holguin\nTaylor McFadden\nTed Not Lasso\nTed Sarandos\nTed Ullyot\nTerell Sterling\nTerence Carroll\nTeresa Carlson\nTerry Angelos\nTerry Brown\nThan Nguyen\nThanh Nguyen\nThe 2015 Academic Roundtable Sessions\nThe TxO team\nTheresa DeMichele\nTheresa Dilley\nTheresa Fisher\nTheresa Walz\nTheresia Gouw\nThibaut Scholasch\nThomas Gjerde\nThomas Juenger\nThomas Long\nThomas Rando\nTiffany Vo\nTiffany Zhong\nTim Beiko\nTim O'Reilly\nTim Roughgarden\nTim Schafer\nTim Sullivan\nTimmu Tõke\nTina Anderson\nTina Bhatnagar\nTina Ferguson\nTina Wie\ntinawie\nTing Ni\nTobi Lütke\nTodd Cranney\nTodd Lutwak\nTodd McKinnon\nTodd Park\nTodd Young\nTolga Dizdarer\nTom Butta\nTom Coates\nTom Davenport\nTom Ellis\nTom Hammer\nTom Hofmann\nTom Lehman\nTom Mitchell\nTom Preston-Werner\nTom Rikert\nTom Standage\nTomicah Tillemann\nTony Blair\nTony Blinken\nTori Landrum\nTracy Chou\nTracy Young\nTren Griffin\nTrent Mayol\nTrevor Bedford\nTristan Handy\nTristan Walker\nTroy Kirwin\nTugce Erten\nTurner Novak\nTushar Garg\nTyler Cowen\nTyler Wilson\nTyson Clark\nUma Valeti\nUsman Azam\nUzi Dutta\nValentina Marzorati\nValeria Nikolaenko\nValerie Arboleda\nVan Jones\nVan Le-Gray\nVanessa Kropf\nVas Narasimhan\nVaughn Ferguson\nVenkat Mocherla\nVicente De Baca\nVickie Casillas-Smith\nVictor Liang\nVictor Shoup\nVictoria Butcher\nVijay Balasubramaniyan\nVijay Kedar\nVijay Pande\nVineeta Agarwala\nVinod Khosla\nVirginia Postrel\nVishal Amin\nVitalik Buterin\nVivian Brooks\nVoices Onchain\nW. Brian Arthur\nWahab Owolabi\nWei Luo\nWendy Drpic\nWerner Gerola\nWes Taylor\nWhitney Owens\nWill Brown\nWill Wong\nWillem Mulder\nWilliam Gifford\nWilliam Mougayar\nWing Cheng\nXian Zhang\nXiang-Dong Fu\nXingchen Zhou\nYannai A. Gonczarowski\nYehuda Lindell\nYevgeniy Dodis\nYinuo Zhang\nYogi Roth\nYohei Ishii\nYoko Li\nYoni Levy\nYoram Novick\nYuichi Kurosawa\nYujin Chung\nYun Fan\nYung Yung Sheung\nYuval Efron\nYuval Harari\nZac Bookman\nZach Abrams\nZach Cohen\nZach Dicker\nZach Haigney\nZachary Chen\nZachary Gray\nZack Weiner\nZahabiya Gabaji\nZak Doric\nZal Bilimoria\nZane Lackey\nZeta Avarikioti\nZeya Yang\nZooko Wilcox\nZoran Basich\n\nclear all Sriram Krishnan\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n11.07.23 / Sriram Krishnan\nInvesting in Pimlico\nOne of crypto’s core promises is self-sovereignty over digital goods and assets. Despite this promise, developers building wallets or web3 applications and experiences have long been faced with a dilemma – deciding whether to prioritize UX or decentralization. When optimizing for UX, developers have typically leaned into custodial solutions, sacrificing self-sovereignty. Those prioritizing self-sovereignty and...\n\nannouncements & news\nannouncements\ninvestments\n\n09.06.23 / Sriram Krishnan\nInvesting in Story Protocol\nI grew up obsessed with movies, TV, and comics. Be it Batman, Superman, Star Trek, Harry Potter, or Lord of the Rings, like millions of others, they formed a major part of my childhood (and still do). When I got access to the internet, I would then discuss these with fans from all over the...\n\nannouncements & news\nannouncements\ninvestments\n\n05.12.23 / Sriram Krishnan\nConsumer products 101\na16z general partner Sriram Krishnan provides a framework for developing consumer products for any builder in the process of bringing their idea to life.\n\ncompany building\nCSX 2023\ndesign & user experience\nvideo\n\n05.12.23 / Brian Armstrong and Sriram Krishnan\nHow Brian Armstrong built Coinbase\nThe journey from coder to manager, the importance of building a community of power users for your product, and more.\n\ncompany building\nCSX 2023\nfounder stories\nvideo\n\n02.23.23 / Sriram Krishnan\nInvesting in Towns\nI’ve spent the majority of my career working on classic centralized web2 social platforms. One of the core appeals for joining a16z crypto was working with founders who are focused on building decentralized crypto native versions of the social platforms we have grown used to – but re-imagined from the ground up with letting creators...\n\nannouncements & news\nannouncements\ninvestments\n\n08.29.22 / Sriram Krishnan\nInvesting in PROOF\nWe are big believers in NFTs revolutionizing the future of the media, entertainment, and content creation spaces. It’s personally been thrilling to see how many different artists and creators, developers, and communities have found unique ways to use NFTs to build community/technology and interesting experiences on top. One of the most exciting examples is PROOF....\n\nannouncements & news\nannouncements\ninvestments\nNFTs\n\n08.13.22 / Sriram Krishnan\nStatus Traps: Learning from Web2 Social Networks\nCountering social networks’ tendency toward “social capital” inequality requires thinking like an economist and learning from the web2 days.\n\ncompany building\ndesign & user experience\nidentity & reputation\nsocial networks\nweb2 to web3\n\n01.24.22 / Sriram Krishnan\nInvesting in Prologue\nEnter Prologue, a unique company with an audacious vision: to help the best founders around the world level up and break through the noise.\n\nannouncements & news\nannouncements\ninvestments\n\n05.05.21 / Sriram Krishnan\nInvesting in Bitski\nBitski lets creators, brands, and platforms easily create, sell, and purchase NFTs — no crypto deep dive required.\n\nannouncements & news\nannouncements\ninvestments\nNFTs\nwallets\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":7542,"crawled_at":1791195904847}
+{"id":10575,"url":"https://blog.trailofbits.com/2023/05/23/trusted-publishing-a-new-benchmark-for-packaging-security","domain":"blog.trailofbits.com","chapter":"security_audits","title":"Trusted publishing: a new benchmark for packaging security - The Trail of Bits Blog","text":"Page content\n\nRead the official announcement on the PyPI blog as well!\nFor the past year, we’ve worked with the Python Package Index to add a new, more secure authentication method called “trusted publishing.” Trusted publishing eliminates the need for long-lived API tokens and passwords, reducing the risk of supply chain attacks and credential leaks while also streamlining release workflows. Critical packages on PyPI are already using trusted publishing to make their release processes more secure.\nIf you publish packages to PyPI, use the official PyPI documentation to set up trusted publishing for your projects today. The rest of this post will introduce the technical how and why of trusted publishing, as well as where we’d like to see similar techniques applied in the future.\nWe love to help expand trust in language ecosystems. Contact us if you’re involved in a packaging ecosystem (e.g., NPM, Go, Crates, etc) and want to adopt more of these techniques!\nTrusted publishing: a primer\nAt its core, trusted publishing is “just” another authentication mechanism. In that sense, it’s no different from passwords or long-lived API tokens: you present some kind of proof to the index that states your identity and expected privileges; the index verifies that proof and, if valid, allows you to perform the action associated with those privileges.\nWhat makes trusted publishing interesting is how it achieves that authentication without requiring a preexisting shared secret. Let’s get into it!\nOpenID Connect and “ambient” credentials\nTrusted publishing is built on top of OpenID Connect (OIDC), an open identity attestation and verification standard built on top of OAuth2. OIDC enables identity providers (IdPs) to produce publicly verifiable credentials that attest to a particular identity (like hamilcar@example.com) . These credentials are JSON Web Tokens (JWTs) under the hood, meaning that an identity under OIDC is the set of relevant claims in the JWT.\nTo drive that point home, here’s what a (slightly redacted) claim set might look like for a user identity presented by GitHub’s OIDC IdP:\n\n(In an actual JWT, this claim set would be accompanied by a digital signature proving its authenticity for a trusted signing key held by the IdP. Without that digital signature, we’d have no reason to trust the claims!)\nAnybody can be an IdP in an OpenID Connect scheme. Still, a large part of the practical value of OIDC is derived from interactions with large, presumed-to-be-trustworthy-and-well-secured IdPs. There’s value in proving ownership over things like GitHub and Google accounts, particularly for things like SSO and service federation.\nSo far, so good, but none of this is especially relevant to packaging indices like PyPI. PyPI could allow users to sign in with OIDC rather than passwords, but it’s unclear how that would make publishing workflows, particularly CI-based ones, any more convenient.\nWhat makes OIDC useful to package indices like PyPI is the observation that an OIDC identity doesn’t need to be a human: it can be a machine identifier, a source repository, or even a specific instance of a CI run. Moreover, it doesn’t need to be obtained through an interactive OAuth2 flow: it can be offered “ambiently” as an object or resource that only the identity (machine, etc.) can access.\nCI providers figured this out not too long ago: GitHub Actions added support for ambient OIDC credentials in late 2021, while GitLab added it just a few months ago. Here’s what retrieving one of those credentials looks like on GitHub Actions:\n\nAnd here’s what the (again, filtered) claim set for a GitHub Actions workflow run might look like:\n\nThis is a lot of context to work with: assuming that we trust the IdP and that the signature checks out, we can verify the identity down to the exact GitHub repository, the workflow that ran, the user that triggered the workflow, and so forth. Each of these can, in turn, become a constraint in an authentication system.\nTrust is everything\nTo recap: OpenID Connect gives us the context and machinery we need to verify proofs of identity (in the form of OIDC tokens) originating from an IdP. The identities in these proofs can be anything, including the identity of a GitHub Actions workflow in a particular repository.\nAny third-party service (like PyPI) can, in turn, accept OIDC tokens and determine a set of permissions based on them. Because OIDC tokens are cryptographically tied to a particular OIDC IdP’s public key, an attacker cannot spoof an OIDC token, even if they know the claims within it.\nBut wait a second: how do we get from an OIDC token containing an identity to a specific PyPI project? How do we know which PyPI project(s) should trust which OIDC identity or identities?\nThis is where a bit of trusted setup is required: a user (on PyPI) has to log in and configure the trust relationship between each project and the publishers (i.e., the OIDC identities) that are authorized to publish on behalf of the project.\nThis needs to be done only once, as with a normal API token. Unlike an API token, however, it only involves one party: the CI (and OIDC) provider doesn’t need to be given a token or any other secret material. Moreover, even the trusted setup part is composed of completely public information: it’s just the set of claim values that the user considers trustworthy for publishing purposes. For GitHub Actions publishing to PyPI, the trusted setup would include the following:\nThe GitHub user/repo slug\nThe filename of the GitHub Actions workflow that’s doing the publishing (e.g., release.yml)\nOptionally, the name of a GitHub Actions environment that the workflow uses (e.g., release)\nTogether, these states allow the relying party (e.g., PyPI) to accept OIDC tokens, confirm that they’re signed by a trusted identity provider (e.g., GitHub Actions), and then match the signed claims against one or more PyPI projects that have established trust in those claims.\nLook ma, no secrets\nAt this point, we have everything we need to allow an identity verified via OIDC to publish to PyPI. Here’s what that looks like in the GitHub case:\nA developer (or automation) triggers a GitHub Actions workflow to release to PyPI.\nThe normal build process (python -m build or similar) commences.\nAutomation retrieves an OIDC token for the current workflow run, attesting to the current workflow’s identity (user/repo, workflow name, environment, etc.) via GitHub Actions’ OIDC IdP.\nThat OIDC token is shot over to PyPI.\nIf valid, PyPI verifies it and exchanges it for a short-lived PyPI API token that’s scoped to just the PyPI projects that trust those token claims.\nPyPI returns the short-lived API token as a response to the OIDC token.\nThe workflow continues, performing a normal PyPI publish step (e.g., with twine) with the short-lived API token.\nFor 99% of package publishers, steps 3 through 7 are entirely implementation details: the official PyPA GitHub Action for publishing to PyPI encapsulates them, making the user-facing piece just this:\n\nWhy should I care?\nAt this point, you might reasonably think:\nI’m a competent engineer, and I already do everything right. My tokens are correctly scoped to the smallest permissions required, they’re stored as workflow (or per-environment) secrets, and I carefully audit my release workflows to ensure that all third-party code is trustworthy.\" – You, a competent engineer\n\nHere’s the thing: you’ve been doing everything right! Until now, the most secure way to authenticate to PyPI was to do the following:\nCreate a project-scoped API token.\nStore it as a (scoped) secret in your CI.\nAccess it carefully in a publishing workflow you’ve reviewed and established trust in.\nThis suffices for many use cases but also leaves a great deal to be desired from both the usability and security perspectives:\nUsability. Manually managing and creating API tokens is tedious, especially in scenarios where a single source repository hosts multiple PyPI packages: each needs its own separately scoped token, a unique secret name, and so forth. You and your fellow engineers have better ways to spend your time!\nPre-compromise security. Not all attackers are born equal: some are passive, some are active, some might be able to compromise only a specific step in your publishing process, and so forth. Reducing the power of (or outright eliminating) one of these attackers is useful, even when the mitigation involved doesn’t meaningfully impact other attackers. Unfortunately, doing so with long-lived tokens is difficult: a long-lived token is equally susceptible to any attacker who gets access for any time.\nPost-compromise recovery. Designing for security means attempting to thwart attackers and preparing for and mitigating the risk posed by a successful attacker. With long-lived credentials (either passwords or API tokens), this is slow, tedious, and error-prone: missing a single credential leaves a gap for the attacker to return. A better system wouldn’t have this problem to begin with.\nTrusted publishing addresses these problems and more:\nUsability. With a trusted publisher, no manual API token management is necessary: configuring the publisher is a one-time action for each project, including for projects that haven’t been created yet.\nThis avoids the annoying API token dance involved when publishing a brand new project and the game of “credential hot potato” that engineers play when trying to hand an API token to the party responsible for adding it to the CI’s secrets. No more Slack DMs with API tokens!\n\nPre-compromise security. Trusted publishing reduces the number of adversaries: an attacker with access to only some GitHub Actions environments or particular (non-permission) steps can’t mint the OIDC credential needed to use the trusted publisher. This is in marked contrast to a long-lived token stored in a GitHub Actions secret, where any step (and frequently any environment) can access the credential!\n\nPost-compromise recovery. Trusted publishing is fundamentally ephemeral: the credentials involved (both the OIDC and PyPI credentials) live for only a few minutes at a time, meaning that an attacker who loses access during post-compromise response is automatically sealed off without any human intervention. That means fewer manual steps and fewer possible human errors.\n\nSecurity and threat model considerations\nTrusted publishing is another way to securely authenticate to a package index. Like every security feature, it must be designed and implemented to a threat model. That threat model must justify trusted publishing’s existence, both for addressing attackers that previous authentication methods do not address and for new attack scenarios it exposes.\nExisting threats: account takeover and supply chain attacks\nAccount takeover (ATO) is a known problem in packaging ecosystems: an attacker who manages to compromise a legitimate user’s PyPI or GitHub account can upload malicious releases (or even override previous ones) without any outward indication of inauthenticity.\nIn the general case, ATO is an unsolvable problem: services like PyPI and GitHub can improve access to security features (and even mandate those features) but fundamentally cannot prevent a user from disclosing their credentials (e.g., via phishing), much less protect them from every piece of potentially vulnerable software they use.\nAt the same time, features like trusted publishing can reduce the scope of account takeover: a future in which package indices allow packages to opt in to only trusted publishing is one where an ATO on the package index itself doesn’t allow the attacker to upload malicious releases.\nSimilarly, “supply chain security” is all the rage these days: companies and hobbyists alike are taking a second look at out-of-control dependency trees and their frequently unaccountable and untraceable components.\nWithout trusted publishing, the status quo for GitHub Actions is that you trust every third-party action you execute: they can all read your configured secrets. This is extremely non-ideal and is one of the key attack models trusted publishing intends to secure against.\nNew threats: “account resurrection” and malicious committers\nTrusted publishing works because it’s tied to a notion of “trusted identity”: the trusted identity on the other side (e.g., on GitHub Actions) is a tuple of user/repo, workflow name, and an optional environment name.\nBut wait: what happens if a user changes their username and an attacker takes over their old username? We call this “account resurrection,” and it’s explicitly supported by most services: a username isn’t intended to be a permanent, stable identifier for the underlying identity.\nThis opens up an entirely new attack vector: a PyPI project that trusts hamilcar/cartago might suddenly begin trusting an attacker-controlled hamilcar/cartago, all because the original hamilcar is now hannibal (and the legitimate hamilcar/cartago is now hannibal/cartago).\nWe thought of this while designing trusted publishing for PyPI and worked with GitHub to add an additional claim that binds the OIDC token not just to the user, but also to their unique, stable user ID. This gives us the state we need to prevent resurrection attacks: even if an attacker manages to become hamilcar on GitHub, their underlying user ID will not change and PyPI will reject any identity tokens they present.\nTrusted publishing also reveals a new (potential) division in a project’s trust model: for any given project, do you trust every member of that project to also be a potential publisher? In many cases, the answer is yes: many projects have only one or two repository members, both of whom are also owners or otherwise privileged on the package index.\nIn some cases, however, the answer is no: many projects have dozens of low-activity or inactive members, not all of whom may be following best practices for securing their accounts. These members might not be removable because of community policy or because they need access for infrequent (but critical) project activities. These users should not necessarily receive the ability to publish releases to the packaging index just because they have the commit bit on the repository.\nThis is also a consideration we made while designing trusted publishing, and it’s why PyPI’s implementation supports an optional GitHub Actions environment: for communities where users who commit and users who publish do not wholly overlap, an environment can be used to impose additional workflow restrictions that are reflected (and subsequently honored by PyPI) in the OIDC token. A detailed example of this is given in PyPI’s own security model documentation.\nComing to a package index near you\nOur work on PyPI was funded by the incredible Google Open Source Security Team (GOSST), who we’ve also worked with to develop new tooling for the Python ecosystem’s overall security. In particular, we’d like to thank Dustin Ingram for tirelessly working alongside us and directing the overall pace and design of trusted publishing for PyPI.\nAt the moment, PyPI is the only package index offering trusted publishing that we’re aware of. That being said, nothing about trusted publishing is unique to Python or Python packaging: it could just as easily be adopted by Rust’s Crates, Ruby’s RubyGems, JavaScript’s NPM, or any other ecosystem where publishing from a third-party service is common (like GitHub Actions or GitLab’s CI/CD).\nIt’s our opinion that, much like Two-Factor Authentication in 2019, this kind of trusted publishing scheme will become instrumental to the security model of open-source packaging. We see it as a building block for all kinds of subsequent improvements, including being able to generate strong cryptographic proof that a PyPI release was built from a particular source artifact.\nIf you or your company are interested in this work, please get in touch with us! We have years of experience working on security features in open-source ecosystems and are always looking for more ways to contribute to critical open-source projects and services.","tokens":4028,"crawled_at":1791195916646}
+{"id":10576,"url":"https://a16zcrypto.com/posts/article/investing-in-pimlico","domain":"a16zcrypto.com","chapter":"research","title":"Investing in Pimlico - a16z crypto","text":"Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nInvesting in Pimlico\nSriram Krishnan\n11.07.23\n\nTags & Share Tags\nannouncements\nannouncements & news\ninvestments\n\nOne of crypto’s core promises is self-sovereignty over digital goods and assets. Despite this promise, developers building wallets or web3 applications and experiences have long been faced with a dilemma – deciding whether to prioritize UX or decentralization.\n\nWhen optimizing for UX, developers have typically leaned into custodial solutions, sacrificing self-sovereignty. Those prioritizing self-sovereignty and self-custody subsequently forced their users to manage 12 or 24-word seed phrases.\n\nIn 2019, the concept of account abstraction was introduced as the first step in a long series of solutions to enable flexible, secure self-custody. In 2021, ERC-4337 was proposed and quickly became the first Account Abstraction spec to gain real momentum, as it did not require changes to Ethereum’s consensus-layer. Among the authors of ERC-4337, including Ethereum co-founder Vitalik Buterin and several Ethereum core researchers, was Kristof Gazso.\n\nWhen we first met Kristof Gazso, buzz around account abstraction was picking up, and companies were beginning to form with the mission of supporting smart contract wallets of the future. Inspired by his talk on Account Abstraction at ETH Dubai, and recognizing the significance of his close ties to core Ethereum developers, we quickly realized that Kristof was a world-class developer, and someone we wanted to keep a very close eye on as account abstraction became an investable category.\n\nMonths later, Kristof founded Pimlico, a product suite to enable wallet developers to easily embed account abstraction functionality. Pimlico is designed to make crypto UX simpler and easier by offering services like gas fee sponsorship, payment with ERC-20 tokens, social recovery schemes, batched transactions, spending limits, and different account access levels.\n\nWith Pimlico just a few weeks old, Kristof participated in our Spring 2023 cohort of Crypto Startup School in Los Angeles. Within weeks, we were blown away by the velocity at which Kristof and team shipped product and closed significant, early partnerships for Pimlico. By the end of Crypto Startup School, we were convinced that no one was better equipped to build the supporting infrastructure for account abstraction than Kristof.\n\nToday, we’re proud to announce that we’ve led Pimlico’s Seed round and are thrilled to partner with them as they enable web3 deliver on its self-sovereignty promises with the ease and usability of web2.\n\nWe’re also excited to work with Kristof and the Pimlico team from our new office in London. If the name wasn’t enough of a clue, Pimlico is based in London and we are excited to work with fantastic entrepreneurs in the UK ecosystem with Kristof being a great example of one.\n\nWelcome, Pimlico!\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nThe content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":1355,"crawled_at":1791195935756}
+{"id":10577,"url":"https://docs.ethena.fi/resources/usde-mint-user-agreement","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"USDe Mint User Agreement | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nLast Updated: August 2025\n\nThis USDe Mint User Agreement (this “Agreement”) is a contract between you (“you” or a “ Mint User”) and Ethena BVI Limited (\"referred to as the “Company,” and “Ethena BVI”, “we,” or “us”). This Agreement applies to your use of Ethena BVI--related products and services (the “Services”) on the Company platform (the “Platform” or “Company”). The USDe Terms apply to your USDe and your status as a Mint User, as applicable, as defined in the USDe Terms. From and after the date set forth above, this Agreement shall govern your use of any Company products or Services.\nFor the avoidance of doubt, your access to the Services is contingent on your status as a Mint User, as defined herein.\nBy registering as a Mint User or using any of the Services, you agree that you have read, understood and accept all of the terms and conditions contained in this Agreement as well as the Privacy Policy, Cookie Policy, and other policies, and you acknowledge and agree that you will be bound by these agreements and policies.\nNote that this Agreement uses the term “Digital Currency” to refer to USDe or any other digital currencies, cryptocurrencies, virtual currencies, or digital assets. For the avoidance of doubt, where used herein, the term “funds” includes Digital Currency.\nPlease note that Section 20 contains an arbitration clause and collective or class action waiver. By agreeing to this Agreement, you agree to resolve all disputes, except as otherwise set forth in Section 20, through binding individual arbitration, which means that you waive any right to have the dispute decided by a judge or jury, and you waive any right to participate in collective action, whether that be a class action, class arbitration, or representative action.\nSection 21 of this Agreement governs how this Agreement may be changed over time; the date of the last update is set forth at the top of this Agreement.\n1. Eligibility; Limitations; Registration Process; Identity Verification\nEligibility; Limitations\nThe Platform and the Services are currently only available to users located in supported jurisdictions. In registering to use the Company Services as a Mint User on behalf of an entity, you represent and warrant that (i) such legal entity is duly organized and validly existing under the applicable laws of the jurisdiction of its organization; (ii) you are duly authorized by such legal entity to act on its behalf, and (iii) such organization (and any affiliate entity) must not have been previously suspended or removed from the Services or any other service or product offered by the Company or its affiliate entities.\nUse of certain Services may have further eligibility requirements that will need to be verified prior to you using such Services or from time to time in order to continue your use of the Services and may be subject to additional terms and conditions.\nBy using your status as a Mint User and the Services, you further represent and warrant that:\n\nyou are at least 18 years old and are not a Restricted Person, nor are you resident of a Restricted Territory (each as defined in Section 27 below).\n\nyou will not be using your status as a Mint User and Services for any illegal activity, including, but not limited to, illegal gambling, money laundering, fraud, blackmail, extortion, ransoming data, terrorism financing, other violent activities or any prohibited market practices, including, but not limited to, those listed in the USDe Terms and Conditions.\n\nYou also understand that there are additional representations and warranties made by you elsewhere in (or by reference in) this Agreement and that any misrepresentation by you is a violation of this Agreement.\nUsers in the United States are not eligible to become a Mint User. This restriction may be revisited from time to time taking into account relevant changes in law.\nWhen you register as a Mint User, you will be required to designate an administrator for your registration and provide a wallet address to be whitelisted. The Company may, in its discretion, enable functionality utilizing your status as a Mint User and some or all of the Services to other persons at your firm (e.g. your employees) (such persons, “Additional Users”). Such access is subject to the Company’s review and approval, and such Additional Users’ agreement to all of the terms hereof. To the extent that you choose to have Additional Users have access and control over the Mint User profile and relationship, you will have to designate those Additional Users and manage their access to your Mint User whitelisted wallets. By you requesting such access, you and all Additional Users automatically agree to this Agreement.\nIf the Company determines that you or any of your Additional Users have violated this Agreement, including, but not limited to, transacting with Blocked Addresses (as defined in the USDe Terms and Conditions) or engaging in Restricted Activities or Prohibited Transactions then the Company may be forced to terminate your status as a Mint User.\nNotwithstanding the foregoing, the Company may determine not to make the Services, in whole or in part, available in every market, either in its sole discretion or due to legal or regulatory requirements, depending on your location. We may also, without liability to you or any third party, refuse to let you register as a Mint User in the Company’s sole discretion.\nRegistration Process; Identity Verification\nWhen registering as a Mint User, you must provide current, complete, and accurate information for all required elements on the registration page or via any third-party service providers (e.g., KYC/KYB information collection and screening providers), including your full legal name and the legal name of your organization. You also agree to provide us, when registering as a Mint User and on an ongoing basis, any additional information we request for the purposes of identity verification and the detection of money laundering, terrorist financing, fraud, or any other financial crime. You permit us to keep a record of such information and authorize us to make the inquiries, whether directly or through third parties, that we consider necessary or desirable to verify your identity or protect you and/or us against fraud or other financial crime, and to take action we reasonably deem necessary based on the results of such inquiries. When we carry out these inquiries, you understand, acknowledge and agree that your personal information may be disclosed to credit reference and fraud prevention or financial crime agencies and that these agencies may respond to our inquiries in full.\nIn certain circumstances, we may require you to submit additional information about yourself or your business, provide records, and complete other verification steps (such process, \"Enhanced Due Diligence\").\nYou represent and warrant that all information provided to us pursuant to this Agreement is true, accurate and not misleading in any respect. If any such information changes, it is your obligation to update such information as soon as possible.\nFrom time to time we may be required to request further information or review or update existing information regarding your registration or your transactions to comply with applicable laws and regulation, and in some cases, payment network. Failure to provide such information, if requested by the Company, in a timely fashion may result in the suspension of your ability to use the Services (until you provide such information) or the termination of your status as a Mint User.\nWe reserve the right to maintain your registration information after you terminate your status as a Mint User for business and regulatory compliance purposes, subject to applicable laws and regulation.\n2. Services\nThe Company offers the following Services in connection with your status as a Mint User:\nThe Company provides USDe-related services, which are described more fully in Section 10 and in the USDe Terms. The USDe Terms are incorporated herein by reference.\n3. Custody\nThe Company does not provide any custody services with respect to USDe or any other assets. Additionally, for the avoidance of doubt, the Company is not a fiduciary, and the Company does not provide any trust or fiduciary services to any User in the course of such User visiting, accessing, or using the the Company website or services, including, for the avoidance of doubt, holding USDe.\nLegal title to the reserves associated with USDe are held by the Company, which administers the assets accordingly.\n4. No Investment Advice\nThe Company does not provide investment, tax, or legal advice, nor does the Company broker trades on your behalf. You should consult your legal or tax professional regarding your specific situation. The Company may provide educational information about USDe and other Digital Currency not supported by the Company. Information may include, but is not limited to, blog posts, articles, links to third-party content, news feeds, tutorials, and videos. The information provided on this website or any third-party sites does not constitute investment advice, financial advice, trading advice, or any other sort of advice, and you should not treat any of the website's content as such.\n5. Privacy\nWe are committed to protecting your personal information and helping you understand exactly how your personal information is being used. You should carefully read the Privacy Policy as it provides details on how your personal information is collected, stored, protected, and used.\n6. Communications\nBy entering into this Agreement, you agree to receive electronic communications and notifications in accordance with our E-Sign Consent Policy, as detailed in the USDe Terms.\nThis Agreement is provided to you and communicated in English. We will also communicate with you in English for all matters related to your use of the Services. Where we have provided you with a translation of the English language version of this Agreement or any information related to your status as a Mint User, you acknowledge and agree that such translation is provided for your convenience only and that the English language version of the Agreement will govern your use of the Services.\n7. Security of User Information\nYou are responsible for maintaining the confidentiality and security of all account names, User IDs, passwords, seed phrases, private keys, personal identification numbers (PINs) and other access codes that you use to access the Services. You are responsible for keeping your email address and all other access and User information up to date with us and for maintaining the confidentiality of your User information. You agree to (i) notify the Company immediately if you become aware of any unauthorized use of your registration as a Mint User, the Services, or any other breach of security regarding the Services or the Platform. We strongly advise you to enable all security features that are available to you (such as, by way of example, using hardware wallets to secure private keys); this offers you enhanced protection from possible malicious attacks. The Company will not be liable for any loss or damage arising from your failure to protect your registration information or private keys.\nWe shall not bear any liability for any damage or interruptions caused by any computer viruses, spyware, or other malware that may affect your computer or other equipment, or any phishing, spoofing, or other attack. We recommend the regular use of a reliable virus and malware screening and prevention software. If you question the authenticity of a communication purporting to be from the Company, you should contact a representative directly.\n8. Suspension & Closure\nWe may, without liability to you or any third party, suspend your status as a Mint User or terminate your status as a Mint User or suspend your use of one or more of the Services in accordance with the terms of this Agreement, as determined in our sole and absolute discretion. Such actions may be taken as a result of inactivity, failure to respond to customer support requests, failure to positively identify you, a court order, your violation of the terms of this Agreement or for other similar reasons. The Company may also temporarily suspend your status as a Mint User in the event that a technical problem causes system outage or the Company errors until the problem is resolved. For the avoidance of doubt, in the event your status as a Mint User is suspended or closed, you will no longer be able to access any of the Services.\nYou may terminate this Agreement at any time by terminating your status as a Mint User in accordance with this Agreement. In order to do so, you should contact the Company’s “Support Team” who will assist you in terminating your status as a Mint User. You may not terminate your status as a Mint User if the Company believes, in its sole discretion, that such termination is being performed in an effort to evade a court order or legal or regulatory investigation or to avoid paying any amounts otherwise due to the Company.\nUpon closure or suspension of your status as a Mint User, you authorize the Company to cancel or suspend pending transactions and forfeit all proprietary rights and claims against the Company in relation to any assets otherwise eligible for redemption.\nIn the event that you or the Company terminates this Agreement or your access to the Services, or cancels your status as a Mint User, you remain liable for all activity conducted on or with your status as a Mint User while it was active and for all amounts due hereunder.\n9. Fees\nThe Company may charge fees in connection with the Services, which will typically not represent fees for the Company’s own account and will constitute reimbursements for costs associated with transactions initiated by you, such as blockchain gas fees and execution fees. You agree to pay the fees shown to you, if any, or as separately agreed between you and the Company, when you enter into a transaction. Fees are generally disclosed prior to your confirmation of any transaction with the Company; we may change any of the fees that the Company charges at any time, with or without notice.\nThe applicable Digital Currency network may charge a fee in connection with blockchain transactions. You are responsible for all such fees.\n10. Applicable USDe Terms\nTo the extent that you utilize your status as a Mint User for any transaction or service involving USDe to which the Company is a counterparty, the USDe Terms shall apply to all such transactions and such agreement. Notwithstanding anything to the contrary set forth in this Agreement or otherwise, in the event of a conflict between any term set forth herein and any term set forth in the USDe Terms, (i) in connection with any USDe transaction, the terms of the USDe Terms shall control, and (ii) in respect of any other Digital Currency transaction, the terms of this Agreement shall control.\n11. Mobile Services\nTo the extent you access the Services through a mobile device, your wireless service carrier’s standard charges, data rates, and other fees may apply. In addition, downloading, installing, or using certain mobile applications may be prohibited or restricted by your carrier, and not all Services may work with all carriers or devices. By using mobile Services, you agree that we may communicate with you by SMS, MMS, text message, push notification, and/or other electronic means via your mobile device (“Mobile Messaging”) and that certain information about your usage of the Services may be communicated to us. In the event that you change or deactivate your mobile telephone number, you agree to promptly update your registration information to ensure that your messages are not sent to any person who might acquire your old number.\nYou may receive messages related to the Services or your status as a Mint User via Mobile Messaging. Message and data rates may apply. Reply STOP to any such Mobile Message to Cancel and unsubscribe. For help, please contact the Support Team.\nYou hereby confirm that with respect to any mobile phone number provided, you own the account corresponding to that mobile phone number or otherwise have the account holder’s permissions to use this service. By registering a mobile phone number you are agreeing to the specific terms set forth in this Section 11.\n12. Transaction Limits\nThe Company reserves the right to change the mint, redemption, transfer, and velocity limits as we deem necessary. We may establish individual or aggregate transaction limits on the size or number of mints, redemptions, transfers or other transactions that you initiate using your status as a Mint User during any specified time period.\n13. Right to Change/Remove Features or Suspend/Delay Transactions\nSubject to Section 17 of the USDe Terms, we reserve the right to change, suspend, or discontinue any aspect of the Services or the Platform at any time, including hours of operation or availability of any feature, without notice and without liability. We may, in our sole discretion, delay any transaction if we believe that such transaction is suspicious, may involve fraud or misconduct, violates applicable laws or payment network rules, or violates any term of this Agreement.\n14. Insufficient Funds\nIf you have insufficient funds in your whitelisted wallet associated with your status as a Mint User to complete a transaction, such transaction will not be completed.\n15. Refunds; Reversals\nOnce a transaction has been initiated (including, but not limited to, a Digital Currency Transfer), it cannot be reversed or refunded, except as set forth in this Agreement. You may have additional refund or chargeback rights under your agreement with the recipient of such funds, your financial institution, or applicable law. You should periodically review statements from your financial institution and any other service that you use to transact Digital Currency, which should reflect all applicable transactions made using the related transaction method.\n16. Taxes\nIt is your responsibility to determine what, if any, taxes apply to the payments you make or receive, and to collect, report, and remit the correct tax to the appropriate tax authority. the Company is not responsible for determining whether taxes apply to your transaction, or for collecting, reporting, or remitting any taxes arising from any transaction.\n17. Indemnification; Release\nYou agree to indemnify and hold the Company, its affiliates, and service providers, and each of their officers, directors, agents, joint venturers, employees, and representatives harmless from any claim or demand (including attorneys’ fees and any losses, fines, fees or penalties imposed by any regulatory authority) arising out of your breach of this Agreement, your violation of any law or regulation or your use of the Services.\nFor the purpose of this Section 17, the term “losses” means all net costs reasonably incurred by us or the other persons referred to in this Section which are the result of the matters set out in this Section 19 and which may relate to any claims, demands, causes of action, debt, cost, expense or other liability, including reasonable legal fees (without duplication).\nIf you have a dispute with one or more Users or third parties, you release the Company (and its affiliates and service providers, and each of their officers, directors, agents, joint ventures, employees and representatives) from all claims, demands, and damages (actual and consequential) of every kind and nature arising out of or in any way connected with such disputes.\n18. Limitation of Liability; No Warranty\nYOU EXPRESSLY UNDERSTAND AND AGREE THAT THE COMPANY AND OUR AFFILIATES AND SERVICE PROVIDERS, AND THEIR RESPECTIVE OFFICERS, DIRECTORS, AGENTS, JOINT VENTURERS, EMPLOYEES, AND REPRESENTATIVES WILLNOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY DAMAGES, OR DAMAGES FOR LOSS OF PROFITS INCLUDING BUT NOT LIMITED TO, DAMAGES FOR LOSS OF GOODWILL, USE, DATA, OR OTHER INTANGIBLE LOSSES (EVEN IF THE COMPANY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES),WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY, OR OTHERWISE, RESULTING FROM: (I) THE USE OR THE INABILITY TO USE THE SERVICES; (II) THE COST OF PROCUREMENT OF SUBSTITUTE GOODS AND SERVICES RESULTING FROM ANY GOODS, DATA, INFORMATION, OR SERVICES PURCHASED OR OBTAINED OR MESSAGES RECEIVED OR TRANSACTIONS ENTERED INTO THROUGH OR FROM THE SERVICES; (III) UNAUTHORIZED ACCESS TO OR ALTERATION OF YOUR TRANSMISSIONS OR DATA; OR (IV) ANY OTHER MATTER RELATING TO THE SERVICES.\nSOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF CERTAIN WARRANTIES OR THE LIMITATION OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES. ACCORDINGLY, SOME OF THE LIMITATIONS SET FORTH ABOVE MAY NOT APPLY TO YOU. IF ANY PROVISION OF THIS SECTION CANNOT BE GIVEN FULL EFFECT UNDER THE LAWS OF YOUR JURISDICTION, REVIEWING COURTS SHALL APPLY LOCAL LAW THAT MOST CLOSELY APPROXIMATES THE INTENDED ECONOMIC EFFECT OF SUCH PROVISION, INCLUDING AN ABSOLUTE WAIVER OF ALL CIVIL LIABILITY IN CONNECTION WITH THE SERVICES TO THE EXTENT PERMITTED BY LAW. IF YOU ARE DISSATISFIED WITH ANY PORTION OF THE SERVICES OR WITH THIS AGREEMENT, YOUR SOLE AND EXCLUSIVE REMEDY IS TO DISCONTINUE USE OF THE SERVICES AND TERMINATE YOUR STATUS AS A MINT USER.\nTHE SERVICES ARE PROVIDED \"AS IS\" AND WITHOUT ANY REPRESENTATION OR WARRANTY, WHETHER EXPRESS,IMPLIED OR STATUTORY. THE COMPANY, OUR AFFILIATES, AND OUR RESPECTIVE OFFICERS, DIRECTORS, AGENTS, JOINT VENTURERS, EMPLOYEES, AND SUPPLIERS SPECIFICALLY DISCLAIM ANY IMPLIED WARRANTIES OF TITLE,MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT. THE COMPANY MAKES NO WARRANTY THAT (I) THE SERVICES WILL MEET YOUR REQUIREMENTS, (II) THE SERVICES WILL BE UNINTERRUPTED, TIMELY, SECURE, OR ERROR-FREE, OR (III) THE QUALITY OF ANY PRODUCTS, SERVICES, INFORMATION, OR OTHER MATERIAL PURCHASED OR OBTAINED BY YOU WILL MEET YOUR EXPECTATIONS.\nThe Company will make reasonable efforts to ensure that requests for the Company transactions are processed in a timely manner, but the Company makes no representations or warranties regarding the amount of time needed to complete processing because the Services are dependent upon many factors outside of our control, such as delays in the banking system. or international mail service. Some jurisdictions do not allow the disclaimer of implied warranties, so the foregoing disclaimers may not apply to you. This Section gives you specific legal rights and you may also have other legal rights that vary from state to state.\n19. Right to Set Off\nThe Company may and is authorized, without prior notice and both before and after demand, to set off the whole or any part of your liabilities or other amounts payable to the Company, including but not limited to fees, whether such amounts are present or future, actual or contingent, or liquidated or unliquidated, against any sums held by the Company and owed to you, whether under this Agreement or any other agreement between the Company and you.\nFor the purpose of exercising its rights under this Section 21: (i) the Company is entitled to convert and/or exchange any Supported Digital Currency owned by you and held by the Company, and is authorized to effect any such conversions at the then prevailing exchange rate; and (ii) if your liability is contingent and/or unliquidated, then the Company may set off the amount it estimates in good faith will be the liquidated amount.\n20. Arbitration\nExcept for claims for injunctive or equitable relief or claims regarding intellectual property rights (which may be brought, in an individual capacity only, and not on a class-wide or representative basis, in the courts specified in Section 28 without the posting of a bond), any dispute between you and the Company related in any way to, or arising in any way from, our Services or this Agreement (“Dispute”) shall be finally settled on an individual, non-representative basis in binding arbitration shall be settled by arbitration in accordance with the BVI IAC Arbitration Rules, as modified by this Agreement, or in accordance with rules on which we may mutually agree in writing; provided, however, that to the extent a Dispute is within the scope of a small claims court’s jurisdiction, either you or the Company may commence an action in small claims court, in the county of your most recent physical address, to resolve the Dispute.\nAny arbitration will be conducted by a single, neutral arbitrator and shall take place in Road Town, Tortola, British Virgin Islands, unless we agree otherwise. The arbitrator may award any relief that a court of competent jurisdiction could award, including attorneys’ fees when authorized by law. The arbitral decision may be enforced in any court of competent jurisdiction. An arbitral decision is subject to very limited review by a court.\n21. Amendments\nThe Company may amend any portion of this Agreement at any time by posting the revised version of this Agreement with an updated revision date. The changes will become effective, and shall be deemed accepted by you, the first time you use the Services after the initial posting of the revised Agreement and shall apply on a going-forward basis with respect to transactions initiated after the posting date. In the event that you do not agree with any such modification, your sole and exclusive remedy is to terminate your use of the Services and terminate your status as a Mint User. You agree that we shall not be liable to you or any third party as a result of any losses suffered by any modification or amendment of this Agreement.\nIf the revised Agreement includes a material change, we will provide you with prior notice via our website and/or email before the material change becomes effective. For this purpose a “material change” means a significant change other than changes that (i) are to your benefit, (ii) are required to be made (a) to comply with applicable laws and/or regulations, (b) to comply with a payment network , or (c) as otherwise required by one of our regulators, (iii) relates to a new product or service made available to you, or (iv) to otherwise clarify an existing term.\n22. Assignment\nYou may not transfer or assign this Agreement or any rights or obligations hereunder, by operation of law or otherwise and any such attempted assignment shall be void. We reserve the right to freely assign this Agreement and the rights and obligations of this Agreement to any third party at any time without notice or consent. If you object to such transfer or assignment, you may stop using our Services and terminate this Agreement by contacting the Company’s Support Team and asking us to terminate your status as a Mint User.\n23. Change of Control\nIn the event that the Company is acquired by or merged with a third party entity, we reserve the right, in any of these circumstances, to transfer or assign the information we have collected from you as part of such merger, acquisition, sale, or other change of control.\n24. Survival; Force Majeure\nUpon termination of your status as a Mint User or this Agreement for any reason, all rights and obligations of the parties that by their nature are continuing will survive such termination.\nThe Company shall have no liability for any failure or delay resulting from any condition beyond our reasonable control, including but not limited to governmental action or acts of terrorism, pandemics, earthquake, fire, flood, or other acts of God, labor conditions, power failures, equipment failures, and Internet disturbances.\n25. Website; Third Party Content\nThe Company strives to provide accurate and reliable information and content on the Company website, but such information may not always be correct, complete, or up to date. The Company will update the information on the Company website as necessary to provide you with the most up to date information, but you should always independently verify such information. The Company website may also contain links to third party websites, applications, events or other materials (“Third Party Content”). Such information is provided for your convenience and links or references to Third Party Content do not constitute an endorsement by the Company of any products or services. The Company shall have no liability for any losses incurred as a result of actions taken in reliance on the information contained on the Company website or in any Third Party Content.\n26. Limited License; IP Rights\nWe grant you a limited, non-exclusive, non-sublicensable, and non-transferable license, subject to the terms and conditions of this Agreement, to access and use the Services solely for approved purposes as determined by the Company. Any other use of the Services or the Platform is expressly prohibited. the Company and its licensors reserve all rights in the Services and you agree that this Agreement does not grant you any rights in or licenses to the Services except for the limited license set forth above. Except as expressly authorized by the Company, you agree not to modify, reverse engineer, copy, frame, scrape, rent, lease, loan, sell, distribute, or create derivative works based on the Services or the Platform, in whole or in part. If you violate any portion of this Agreement, your permission to access and use the Services and your status as a Mint User may be terminated pursuant to this Agreement. \"USDe.money\", \"the Company\", and all logos related to the Services are either trademarks, or registered marks of the Company or its licensors. You may not copy, imitate, or use them without the Company's prior written consent. All right, title, and interest in and to the the Company website, any content thereon, the Services, and all technology and any content created or derived from any of the foregoing is the exclusive property of the Company and its licensors.\n27. Applicable Law; Legal Compliance\nYour use of the Services is subject to the laws, regulations, and rules of any applicable governmental or regulatory authority, including, without limitation, all applicable tax, anti-money laundering (“AML”) and counter-terrorist financing (“CTF”) provisions.\nYou unequivocally agree and understand that by registering as a Mint User and using the Services in any capacity, you will act in compliance with and be legally bound by this Agreement and all applicable laws and regulations (including, without limitation, those stated in this Section 27, where applicable). For the avoidance of doubt, continued use of your status as a Mint User and the Company’s obligations to you under this Agreement are conditional on your continued compliance at all times with this Agreement and all applicable laws and regulations. The Company’s AML and CTF procedures are guided by all applicable laws and regulations regarding AML and CTF. These standards are designed to prevent the use of the Services for money laundering or terrorist financing activities. We take compliance very seriously and it is our policy to take all necessary steps to prohibit fraudulent transactions, report suspicious activities, and actively engage in the prevention of money laundering and any related acts that facilitate money laundering, terrorist financing or any other financial crimes.\nYou agree, represent, and warrant that all funds transacted as a Mint User, or funds deposited by you with the Company in the future, are not the direct or indirect proceeds of any criminal or fraudulent activity.\nThe Services are subject to economic sanctions programs administered in the countries where we conduct business, including but not limited to those administered by the U.S. Department of Treasury’s Office of Foreign Assets Control (“OFAC”), pursuant to which we are prohibited from providing services or entering into relationships with certain individuals and institutions. By using the Services, you represent that your actions are not in violation of such sanctions programs. Without limiting the foregoing, you may not use the Services if (i) you are a resident, national or agent of a jurisdiction subject to comprehensive sanctions by OFAC (“Restricted Territories”), (ii) you are on the Table of Denial Orders, the Entity List, or the List of Specially Designated Nationals (“Restricted Persons”), or (iii) you intend to transact with any Restricted Territories or Restricted Persons. You further represent that you are not a citizen, resident, or organized in, the following jurisdictions (the “Prohibited Jurisdictions”): Abkhazia, Afghanistan, Angola, Belarus, Burundi, Central African Republic, Congo, Cuba, Crimea, Ethiopia, Guinea-Bissau, Iran, Ivory Coast (Cote D’Ivoire), Lebanon, Liberia, Libya, Mali, Burma (Myanmar), Nicaragua, North Korea, Northern Cyprus, Russia, Somalia, Somaliland, South Ossetia, South Sudan, Sudan, Syria, Ukraine (Donetsk and Luhansk regions), United States, Venezuela, Yemen, Zimbabwe.\nIn the event that we are required to block funds associated with your registration as a Mint User in accordance with a sanctions program, or other similar government sanctions programs, we may: (i) suspend your status as a Mint User; (ii) terminate your status as a Mint User; or (iii) return funds to the destination of their origin or to an account specified by authorities. In certain cases, taking one or more of these actions may result in a forfeiture of some or all of your assets held with the Company. We are not responsible for any losses, whether direct or indirect, that you may incur as a result of our complying with applicable law and regulations, the guidance or direction of any regulatory authority or government agency, or any writ of attachment, lien, levy, subpoena, warrant, or other legal order.\n28. Governing Law; Venue\nThe laws of the British Virgin Islands shall govern this Agreement. Except for those disputes that shall be resolved in arbitration or in small claims court, each party agrees to submit to the personal and exclusive jurisdiction of the courts located in the British Virgin Islands, provided that any claims or disputes shall be subject to the arbitration provisions set forth in Section 20. You agree with us that, if you are a consumer, the courts in the permitted region where you are resident will have non-exclusive jurisdiction.\n29. Entire Agreement\nThe failure of the Company to exercise or enforce any right or provision of the Agreement shall not constitute a waiver of such right or provision. If any provision of this Agreement shall be adjudged by any court of competent jurisdiction to be unenforceable or invalid, that provision shall be limited or eliminated to the minimum extent necessary so that this Agreement shall otherwise remain in full force and effect and remain enforceable between the parties, except as specified in Section 25. The headings and explanatory text are for reference purposes only and in no way define, limit, construe, or describe the scope or extent of such section. This Agreement, including any additional agreement incorporated by reference herein; the Company’s policies governing the Services referenced herein (including, without limitation, those set forth in the USDe Terms); the the Company Privacy Policy and the Cookie Policy constitute the entire agreement between you and the Company with respect to the use of the Services. This Agreement is not intended and shall not be construed to create any rights or remedies in any parties other than you and the Company and other the Company affiliates which each shall be a third-party beneficiary of this Agreement, and no other person shall assert any rights as a third-party beneficiary hereunder.\n30. User Support\nPlease contact our Support Team to report any violations of this Agreement or to ask any questions regarding this Agreement or the Services.\n\nLast updated 9 months ago\nWas this helpful?","tokens":9027,"crawled_at":1791195937239}
+{"id":10578,"url":"https://github.com/features/copilot","domain":"github.com","chapter":"developer_specs","title":"GitHub Copilot · Your AI coding agent · GitHub · GitHub","text":"GitHub CopilotCommand your craft\n\nYour AI accelerator for every workflow, from the editor to the enterprise.\nDownload for Windows (x64)\n\nSee plans & pricing\n\nAlready have Visual Studio Code? Open now\n\nCompanies powered by GitHub\n\nGo beyond one-size-fits-all\nChoose from leading LLMs optimized for speed, accuracy, or cost.\n\nUse your agents, your way\nUse GitHub Copilot, your own custom agents, or the third-party ones you already rely on.\n\nStay in your flow\nCopilot works where you do—in GitHub, your IDE, the CLI, project tools, chat apps, and custom MCP servers.\n\nManage agent-driven work from one place\n\nLaunch work from GitHub, track progress across multiple agents, review changes, and merge completed work—all from one desktop workspace built natively on GitHub.\n\nExplore the GitHub Copilot app\n\nMake your editor your most powerful accelerator\n\nCopilot in your editor does it all, from explaining concepts and completing code, to proposing edits and validating files with agent mode.\n\nExplore Copilot in the IDE\n\nShip faster with AI that work alongside you\n\nAssign tasks to agents like Copilot, Claude by Anthropic, and OpenAI Codex, and let them plan, explore, and execute work autonomously in the background.\n\nExplore Copilot cloud agent\n\nGrupo Boticário increases developer productivity by 94% with Copilot\nRead customer story\n\nKnowledgeTurn Copilot into a project expert\nScale knowledge and keep teams consistent by creating a shared source of truth that includes context from your docs and repositories.\nTry Copilot Spaces\n\nGovernanceManage agent usage with enterprise-grade controls\nTrack activity with detailed audit logs and enforce governance by managing agents from a single control plane.\nRead the docs\n\nSecuritySecure your 
MCP integrations\nControl which MCP servers developers can access from their IDEs, and use allow lists to prevent unauthorized access.\nRead the docs\n\nFree\n\nFor getting started with GitHub Copilot.\n$0USDper user / month\nGet startedOpen in VS Code\nWhat's included\n\n2,000 completions per month\nAccess to Haiku 4.5, GPT-5 mini, and more\nCopilot CLI\nCommunity Support\n\nNo credit card required. Verified students have access to the GitHub Copilot Student plan. Learn more\n\nPro\n\nFor everyday coding with agents in GitHub Copilot.\n$10USDper user / month\nGet started\nEverything in Free and:\n\nAccess to Cloud agent and code review1\nUnlimited code completion and next edit suggestions2\nAccess to 3rd party agents (Claude Code and Codex)\nModel selection\n$15 monthly total credits for Pro3\n\nPro+\n\nFor more complex development with premium models.\n$39USDper user / month\nGet started\nEverything in Pro and:\n\nAccess to premium models, including Opus\nAudit logs\n4x+ included usage than Pro\n$70 monthly total credits for Pro+3\n\nMax\n\nFor sustained, high-volume agent workflows with GitHub Copilot.\n$100USDper user / month\nGet started\nEverything in Pro+ and:\n\nPriority access to new models and features\n2.9x+ included usage than Pro+\n$200 monthly total credits for Max3\n\nBest value\n\nBusiness\n\nFor teams that want pooled credits and control.\n$19USDper user / month\nGet startedContact SalesWe're gradually enabling new sign-ups. If you're unable to sign up right now, please check back soon.\n\nWhat's included:\n\nUnlimited code completion and next edit\nAccess to cloud agent and code review1\nAccess to broad model catalog\nAccess to 3rd party agents\nAccess control, budget control, and governance\nIP indemnity and data privacy\nWeb-based support\n1,900 credits per user\n\nEnterprise\n\nFor org-wide rollout and larger pooled credits.\n$39USDper user / month\nGet startedContact salesWe're gradually enabling new sign-ups. If you're unable to sign up right now, please check back soon.\n\nEverything in Business and:\n\nPriority access to new models and features\n\n2,000 more credits per user\n\nBest value\n\nGitHub Copilot is available on your favorite platforms:\n\nGitHub\nVisual Studio\nVisual Studio Code\nXcode\nJetBrains\nNeovim\nEclipse IDE\nRaycast\n\nCompare all plan features\n\nChangelogPreview the latest features\nBe the first to explore what’s next for GitHub Copilot.\nSee previews\n\nBlogExplore the GitHub Blog\nDiscover the latest in software development with insights, best practices, and more.\nRead blog\n\nTrust CenterVisit the GitHub Copilot Trust Center\nGain peace of mind with our security, privacy, and responsible Al policies.\nGo to Trust Center\n\nFrequently Asked Questions\n\nGeneral\nWhat is GitHub Copilot?\nGitHub Copilot transforms the developer experience. Backed by the leaders in AI, GitHub Copilot provides contextualized assistance throughout the software development lifecycle, from inline suggestions and chat assistance in the IDE to code explanations and answers to docs in GitHub and more. With GitHub Copilot elevating their workflow, developers can focus on: value, innovation, and happiness.\nGitHub Copilot enables developers to focus more energy on problem solving and collaboration and spend less effort on the mundane and boilerplate. That’s why developers who use GitHub Copilot report up to 75% higher satisfaction with their jobs than those who don’t and are up to 55% more productive at writing code without sacrifice to quality, which all adds up to engaged developers shipping great software faster.\nGitHub Copilot integrates with leading editors, including Visual Studio Code, Visual Studio, JetBrains IDEs, and Neovim, and, unlike other AI coding assistants, is natively built into GitHub. Growing to millions of individual users and tens of thousands of business customers, GitHub Copilot is the world’s most widely adopted AI developer tool and the competitive advantage developers ask for by name.\n\nWho is eligible to access GitHub Copilot for free?\nGitHub Copilot Free is a new free pricing tier with limited functionality for individual developers. Users assigned a Copilot Business or Copilot Enterprise seat are not eligible for access. Users with access to Copilot Pro through a paid subscription, trial, or through an existing verified OSS, student, faculty, or MVP account may elect to use Free instead.\n\nWhat languages, IDEs, and platforms does GitHub Copilot support?\nGitHub Copilot is trained on all languages that appear in public repositories. For each language, the quality of suggestions you receive may depend on the volume and diversity of training data for that language. For example, JavaScript is well-represented in public repositories and is one of GitHub Copilot’s best supported languages. Languages with less representation in public repositories may produce fewer or less robust suggestions.\nGitHub Copilot is available as an extension in Visual Studio Code, Visual Studio, Vim, Neovim, the JetBrains suite of IDEs, and Azure Data Studio. Although inline suggestion functionality is available across all these extensions, chat functionality is currently available only in Visual Studio Code, JetBrains, and Visual Studio. GitHub Copilot is also supported in terminals through GitHub CLI and as a chat integration in Windows Terminal Canary. With the GitHub Copilot Enterprise plan, GitHub Copilot is natively integrated into GitHub.com. All plans are supported in GitHub Copilot in GitHub Mobile. GitHub Mobile for Copilot Pro and Copilot Business have access to Bing and public repository code search. Copilot Enterprise in GitHub Mobile gives you additional access to your organization's knowledge.\n\nDoes GitHub Copilot “copy/paste”?\nNo, GitHub Copilot generates suggestions using probabilistic determination.\nWhen thinking about intellectual property and open source issues, it is critical to understand how GitHub Copilot really works. The AI models that create GitHub Copilot’s suggestions may be trained on public code, but do not contain any code. When they generate a suggestion, they are not “copying and pasting” from any codebase.\n\nTo generate a code suggestion, the GitHub Copilot extension begins by examining the code in your editor—focusing on the lines just before and after your cursor, but also information including other files open in your editor and the URLs of repositories or file paths to identify relevant context. That information is sent to GitHub Copilot’s model, to make a probabilistic determination of what is likely to come next and generate suggestions.\n\nTo generate a suggestion for chat in the code editor, the GitHub Copilot extension creates a contextual prompt by combining your prompt with additional context including the code file open in your active document, your code selection, and general workspace information, such as frameworks, languages, and dependencies. That information is sent to GitHub Copilot’s model, to make a probabilistic determination of what is likely to come next and generate suggestions.\n\nTo generate a suggestion for chat on GitHub.com, such as providing an answer to a question from your chat prompt, GitHub Copilot creates a contextual prompt by combining your prompt with additional context including previous prompts, the open pages on GitHub.com as well as retrieved context from your codebase or Bing search. That information is sent to GitHub Copilot’s model, to make a probabilistic determination of what is likely to come next and generate suggestions.\n\nWhat are the differences between the GitHub Copilot Business, GitHub Copilot Enterprise, and GitHub Copilot Individual plans?\nGitHub Copilot has multiple offerings for organizations and an offering for individual developers. All the offerings include both inline suggestion and chat assistance. The primary differences between the organization offerings and the individual offering are license management, policy management, and IP indemnity.\nOrganizations can choose between GitHub Copilot Business and GitHub Copilot Enterprise. GitHub Copilot Business primarily features GitHub Copilot in the coding environment - that is the IDE, CLI and GitHub Mobile. GitHub Copilot Enterprise includes everything in GitHub Copilot Business. It also adds an additional layer of customization for organizations and integrates into GitHub.com as a chat interface to allow developers to converse with GitHub Copilot throughout the platform. GitHub Copilot Enterprise can index an organization’s codebase for a deeper understanding of the customer’s knowledge for more tailored suggestions and will offer customers access to fine-tuned custom, private models for inline suggestions.\nGitHub Copilot Individual is designed for individual developers, freelancers, students, educators, and open source maintainers. The plan includes all the features of GitHub Copilot Business except organizational license management, policy management, and IP indemnity.\n\nWhat data has GitHub Copilot been trained on?\nGitHub Copilot is powered by generative AI models developed by GitHub, OpenAI, and Microsoft. It has been trained on natural language text and source code from publicly available sources, including code in public repositories on GitHub. Starting on April 24, GitHub may also use interactions from users with a Copilot Free, Copilot Pro, and Copilot Pro+ subscription - including inputs, outputs, code snippets, and associated context - to train and improve our AI models unless they have opted out. This allows us to build more intelligent, context-aware coding assistance for a more diverse set of coding tasks based on real-world development patterns. Users were notified 30 days before the change went into effect and can opt out from allowing their data to be used for training in their GitHub account settings at any time.\n\nWhich plan includes GitHub Copilot Autofix?\nGitHub Copilot Autofix provides contextual explanations and code suggestions to help developers fix vulnerabilities in code, and is included in GitHub Advanced Security.\n\nWhat if I do not want GitHub Copilot?\nGitHub Copilot is entirely optional and requires you to opt in before gaining access. You can easily configure its usage directly in the editor, enabling or disabling it at any time. Additionally, you have control over which file types GitHub Copilot is active for.\n\nHow do I control access to GitHub Copilot in my company?\nAccess to Copilot Business and Enterprise is managed by your GitHub Administrator. They can control access to preview features, models, and set GitHub Copilot policies for your organization. Additionally, you can use your network firewall to explicitly allow access to Copilot Business and/or block access to Copilot Pro or Free. For more details, refer to the documentation.\n\nPlans & Pricing\nWhat are the differences between the Free, Pro, Pro+, Max, Business, and Enterprise plans?\nGitHub Copilot has multiple offerings for organizations and an offering for individual developers. All the offerings include both code completion and chat assistance. The primary differences between the organization offerings and the individual offering are license management, policy management, and IP indemnity.\nOrganizations can choose between GitHub Copilot Business and GitHub Copilot Enterprise. GitHub Copilot Business primarily features GitHub Copilot in the coding environment - that is the IDE, CLI and GitHub Mobile. GitHub Copilot Enterprise includes everything in GitHub Copilot Business. It also adds an additional layer of customization for organizations and integrates into GitHub.com as a chat interface to allow developers to converse with Copilot throughout the platform. GitHub Copilot Enterprise can index an organization’s codebase for a deeper understanding of the customer’s knowledge for more tailored suggestions and will offer customers access to fine-tuned custom, private models for code completion.\nGitHub Copilot Pro is designed for individual developers, freelancers, students, educators, and open source maintainers. The plan includes all the features of GitHub Copilot Business except organizational license management, policy management, and IP indemnity.\nGitHub Copilot Max is built for heavy Copilot usage, including sustained agent-driven workflows, and includes $100/month in GitHub AI Credits.\n\nHow can I upgrade my GitHub Copilot Free license to Copilot Pro?\nIf you're on the Free plan, you can upgrade to Pro through your Copilot settings page or directly on the Copilot marketing page.\n\nWhat is included in GitHub Copilot Free?\nCopilot Free includes 2,000 code completions per month and a limited monthly allowance of GitHub AI Credits for chat and agent features. Models are provided through auto model selection. Usage varies with the model and the number of tokens processed.\n\nWhich plan includes GitHub Copilot Autofix?\nGitHub Copilot Autofix provides contextual explanations and code suggestions to help developers fix vulnerabilities in code, and is included in GitHub Advanced Security and available to all public repositories.\n\nCan users in my organization use Copilot code reviews for their pull requests if they don’t have a Copilot license?\nOrganizations can now enable Copilot code review on all pull requests on github.com—including pull requests from users who are not assigned a Copilot license.\nThis allows you to extend the quality and rich analysis of Copilot code review to all pull requests, regardless of its author, giving you complete coverage and confidence that pull requests have been reviewed.\nTo enable this functionality, an enterprise/org admin must first have Copilot enabled and then enabled two policies.\nNote: This capability is not supported for Copilot code reviews in VS Code or other IDEs.\n\nHow does billing work for Copilot code review usage generated by users without a Copilot license?\nUsage from non-licensed users is billed directly to your organization as GitHub AI Credits. This flexible model allows you to get full review coverage on every PR without purchasing a full Copilot seat for non-development contributors who may not need Copilot.\nUsage from your existing licensed users continues to draw from their included monthly allowance as it does today. Beginning June 1, 2026, code review workflows also consume GitHub Actions minutes.\n\nIs Copilot code review usage from users without a Copilot license enabled by default? How do I control the cost?\nNo. This capability is off by default and gives the enterprise admin control to enable or disable. An admin must explicitly enable two separate policies to activate:\n‘GitHub AI Credits paid usage’ must be enabled to allow enterprises to be charged for GitHub AI Credits exceeding their included usage.\n\nA new Copilot code review policy (‘Allow members without a Copilot license to use Copilot code review in github.com’) must also be enabled.\n\nWe encourage admins to set up budgets to control spending on our metered products, especially customers who have not enabled the ‘Premium request paid usage’ policy in the past. You can track all premium request usage in your billing dashboard to monitor and control spending.\n\nWhat are GitHub AI Credits?\nGitHub AI Credits are how you pay for AI usage in GitHub Copilot. Every plan includes a monthly allowance: 1 AI credit = $0.01 USD.\nYou use credits when you chat with Copilot, work with agents, or use Copilot CLI, and Spaces. Code completions and next edit suggestions don't use credits. They remain unlimited with every paid plan.\nHow many credits an interaction uses depends on the model you choose and the complexity of the task. A quick question to a lightweight model costs a fraction of a credit. A longer agent session on a frontier model across many files costs more.\n\nWhat happens when I hit my usage limit?\n\nWhen you've used your monthly allowance, you have a few options:\nWait for your next cycle. Your included allowance resets every month.\n\nKeep working with paid usage. Set a dollar budget for additional usage and Copilot continues without interruption. Credits draw down at $0.01 each, so a $10 budget covers 1,000 credits.\n\nSwitch to a less expensive model. Lightweight models use fewer credits per interaction and stretch your remaining allowance further.\n\nOn GitHub Copilot Business and GitHub Copilot Enterprise, admins set usage limits and decide whether additional paid usage is allowed. If it isn't, Copilot pauses until the next cycle.\nYou can track your usage and reset date in your Copilot settings, with alerts at 75%, 90%, and 100% of any configured budget.\n\nPrivacy\nWhat personal data does GitHub Copilot process?\nGitHub Copilot processes personal data based on how Copilot is accessed and used: whether via GitHub.com, mobile app, extensions, or one of various IDE extensions, or through features like suggestions for the command line interface (CLI), IDE code completions, or personalized chat on GitHub.com. The types of personal data processed may include:\nUser Engagement Data: This includes pseudonymous identifiers captured on user interactions with Copilot, such as accepted or dismissed completions, error messages, system logs, and product usage metrics.\n\nPrompts: These are inputs for chat or code, along with context, sent to Copilot's AI to generate suggestions.\n\nSuggestions: These are the AI-generated code lines or chat responses provided to users based on their prompts.\n\nFeedback Data: This comprises real-time user feedback, including reactions (e.g., thumbs up/down) and optional comments, along with feedback from support tickets.\n\nDoes GitHub use Copilot Business or Enterprise data to train GitHub’s model?\nNo. GitHub does not use either Copilot Business or Enterprise data to train its models.\n\nHow does GitHub use the Copilot data from Business and Enterprise Subscribers?\nHow GitHub uses Copilot data depends on how the user accesses Copilot and for what purpose. Users can access GitHub Copilot through the web, extensions, mobile apps, computer terminal, and various IDEs (Integrated Development Environments). GitHub generally uses personal data to:\nDeliver, maintain, and update the services as per the customer's configuration and usage, to ensure personalized experiences and recommendations\n\nTroubleshoot, which involves preventing, detecting, resolving, and mitigating issues, including security incidents and product-related problems, by fixing software bugs and maintaining the online services' functionality and up-to-dateness\n\nEnhance user productivity, reliability, effectiveness, quality, privacy, accessibility, and security by keeping the service current and operational\n\nThese practices are outlined in GitHub’s Data Protection Agreement (DPA), which details our data handling commitments to our data controller customers. GitHub also uses certain personal data with customer authorization under the DPA, for the following purposes:\nBilling and account management\n\nTo comply with and resolve legal obligations\n\nFor abuse detection, prevention, and protection, virus scanning, and scanning to detect violations of terms of service\n\nTo generate summary reports for calculating employee commissions and partner incentives\n\nTo produce aggregated reports for internal use and strategic planning, covering areas like forecasting, revenue analysis, capacity planning, and product strategy.\n\nHow does GitHub use the Copilot data from Individual (Free/Pro/Pro+) Subscribers?\n\nGitHub uses the Copilot data from Individual subscribers for all the operational purposes described above for Business/Enterprise subscribers.\nIn addition, for Individual subscribers only: GitHub may use Copilot interaction data — including prompts (inputs), suggestions (outputs), and code snippets generated during Copilot sessions — to train and improve AI models. This training helps improve code suggestions for all Copilot users.\nIndividual subscribers can opt out of having their data used for AI model training at any time through https://github.com/settings/copilot/features. Opting out does not affect your access to Copilot features.\nFor details on GitHub's data processing activities as a controller, particularly for Copilot Free, Copilot Pro, and Copilot Pro customers, refer to the GitHub Terms of Service and the GitHub Privacy Statement.\n\nHow long does GitHub retain Copilot data for Business and Enterprise customers?\n\nIf and for how long GitHub’s retains Copilot data depends on how a Copilot user accesses Copilot and for what purpose. The default settings for Copilot Business and Enterprise Customers are as follows:\nAccess through IDE for Chat and Code Completions:\nPrompts and Suggestions: Not retained\n\nUser Engagement Data: Kept for two years.\n\nFeedback Data: Stored for as long as needed for its intended purpose.\n\nAll other GitHub Copilot access and use:\nPrompts and Suggestions: Retained for 28 days.\n\nUser Engagement Data: Kept for two years.\n\nFeedback Data: Stored for as long as needed for its intended purpose.\n\nWhy do some Copilot features retain prompts and suggestions?\nRetaining prompts and suggestions is necessary for chat on github.com, mobile, and CLI Copilot because those features’ effectiveness depends on using thread history to improve responses. The Copilot model requires access to previous interactions to deliver accurate and relevant suggestions.\n\nDoes GitHub Copilot support compliance with the GDPR and other data protection laws?\nYes. GitHub and customers can enter a Data Protection Agreement that supports compliance with the GDPR and similar legislation.\n\nDoes GitHub Copilot ever output personal data?\nWhile we've designed GitHub Copilot with privacy in mind, the expansive definition of personal data under legislation like the EU’s General Data Protection Regulation (GDPR) means we can't guarantee it will never output such data. The Large Language Model (LLM) powering GitHub Copilot was trained on public code and there were instances in our tests where the tool made suggestions resembling personal data. These suggestions were typically synthesized and not tied to real individuals.\n\nHow does Copilot allow users to access, alter or delete personal data?\nThese actions are available to Copilot users as described in the GitHub Privacy Statement.\n\nResponsible AI\nWhat are the intellectual property considerations when using GitHub Copilot?\nThe primary IP considerations for GitHub Copilot relate to copyright. The model that powers Copilot is trained on a broad collection of publicly accessible code, which may include copyrighted code, and Copilot’s suggestions (in rare instances) may resemble the code its model was trained on. Here’s some basic information you should know about these considerations:\nCopyright law permits the use of copyrighted works to train AI models: Countries around the world have provisions in their copyright laws that enable machines to learn, understand, extract patterns, and facts from copyrighted materials, including software code. For example, the European Union, Japan, and Singapore, have express provisions permitting machine learning to develop AI models. Other countries including Canada, India, and the United States also permit such training under their fair use/fair dealing provisions. GitHub Copilot’s AI model was trained with the use of code from GitHub’s public repositories—which are publicly accessible and within the scope of permissible copyright use.\nWhat about copyright risk in suggestions? In rare instances (less than 1% based on GitHub’s research), suggestions from GitHub may match examples of code used to train GitHub’s AI model. Again, Copilot does not “look up” or “copy and paste” code, but is instead using context from a user’s workspace to synthesize and generate a suggestion.\nOur experience shows that matching suggestions are most likely to occur in two situations: (i) when there is little or no context in the code editor for Copilot’s model to synthesize, or (ii) when a matching suggestion represents a common approach or method. If a code suggestion matches existing code, there is risk that using that suggestion could trigger claims of copyright infringement, which would depend on the amount and nature of code used, and the context of how the code is used. In many ways, this is the same risk that arises when using any code that a developer does not originate, such as copying code from an online source, or reusing code from a library. That is why responsible organizations and developers recommend that users employ code scanning policies to identify and evaluate potential matching code.\nIn Copilot, you can opt whether to allow Copilot to suggest code completions that match publicly available code on GitHub.com. For more information, see \"Configuring GitHub Copilot settings on GitHub.com\". If you have allowed suggestions that match public code, GitHub Copilot can provide you with details about the matching code when you accept such suggestions. Matching code does not necessarily mean copyright infringement, so it is ultimately up to the user to determine whether to use the suggestion, and what and who to attribute (along with other license compliance) in appropriate circumstances.\n\nDoes GitHub Copilot include a filtering mechanism to mitigate risk?\n\nYes, GitHub Copilot does include an optional code referencing filter to detect and suppress certain suggestions that match public code on GitHub.\nGitHub has created a duplication detection filter to detect and suppress suggestions that contain code segments over a certain length that match public code on GitHub. This filter can be enabled by the administrator for your enterprise and it can apply for all organizations within your enterprise, or the administrator can defer control to individual organizations.\n\nWith the filter enabled, Copilot checks code suggestions for matches or near-matches against public code on GitHub of 65 lexemes or more (on average,150 characters). If there is a match, the suggestion will not be shown to the user.\n\nIn addition to off-topic, harmful, and offensive output filters, GitHub Copilot also scans the outputs for vulnerable code.\n\nDoes GitHub Copilot include features to make it easier for users to identify potentially relevant open source licenses for matching suggestions?\nYes, GitHub Copilot is previewing a code referencing feature as an additional tool to assist users to find and review potentially relevant open source licenses. Code referencing is currently available in Visual Studio Code. This feature searches across public GitHub repositories for code that matches a Copilot suggestion. If there’s a match, users will find its information displayed in the Copilot console log, including where the match occurred, any applicable licenses, and a deep link to learn more. The deep link will take users to a navigable page on GitHub.com to browse examples of the code match and their repository licenses, and see how many repositories—including ones without licenses—that code appears in, as well as links to those repositories. Copilot users can review this information to determine whether the applicable suggestions are suitable for use, and whether additional measures may be necessary to use them.\n\nWho owns the suggestions provided by GitHub Copilot?\n\nWe don’t determine whether a suggestion is capable of being owned, but we are clear that GitHub does not claim ownership of a suggestion. Whether a suggestion generated by an AI model can be owned depends on many factors (e.g. the intellectual property law in the relevant country, the length of the suggestion, the extent that suggestion is considered ‘functional’ instead of expressive, etc).\nIf a suggestion is capable of being owned, our terms are clear: GitHub does not claim ownership.\n\nGitHub does not claim ownership of any suggestion. In certain cases, it is possible for Copilot to produce similar suggestions to different users. For example, two unrelated users both starting new files to code the quicksort algorithm in Java will likely get the same suggestion. The possibility of providing similar suggestions to multiple users is a common part of generative AI systems.\n\nCan GitHub Copilot introduce insecure code in its suggestions?\nPublic code may contain insecure coding patterns, bugs, or references to outdated APIs or idioms. When GitHub Copilot synthesizes code suggestions based on this data, it can also synthesize code that contains these undesirable patterns. Copilot has filters in place that either block or notify users of insecure code patterns that are detected in Copilot suggestions. These filters target the most common vulnerable coding patterns, including hardcoded credentials, SQL injections, and path injections. Additionally, in recent years we’ve provided tools such as GitHub Advanced Security, GitHub Actions, Dependabot, and CodeQL to open source projects to help improve code quality. Of course, you should always use GitHub Copilot together with good testing and code review practices and security tools, as well as your own judgment.\n\nIs GitHub Copilot intended to fully automate code generation and replace developers?\nNo. Copilot is a tool intended to make developers more efficient. It’s not intended to replace developers, who should continue to apply the same sorts of safeguards and diligence they would apply with regard to any third-party code of unknown origin.\nThe product is called “Copilot” not “Autopilot” and it’s not intended to generate code without oversight. You should use exactly the same sorts of safeguards and diligence with Copilot’s suggestions as you would use with any third-party code.\n\nIdentifying best practices for use of third party code is beyond the scope of this section. That said, whatever practices your organization currently uses – rigorous functionality testing, code scanning, security testing, etc. – you should continue these policies with Copilot’s suggestions. Moreover, you should make sure your code editor or editor does not automatically compile or run generated code before you review it.\n\nCan GitHub Copilot users simply use suggestions without concern?\nNot necessarily. GitHub Copilot users should align their use of Copilot with their respective risk tolerances.\nAs noted above, GitHub Copilot is not intended to replace developers, or their individual skill and judgment, and is not intended to fully automate the process of code development. The same risks that apply to the use of any third-party code apply to the use of Copilot’s suggestions.\n\nDepending on your particular use case, you should consider implementing the protections discussed above. It is your responsibility to assess what is appropriate for the situation and implement appropriate safeguards.\n\nYou’re entitled to IP indemnification from GitHub for the unmodified suggestions when Copilot’s filtering is enabled. If you do elect to enable this feature, the copyright responsibility is ours, not our customers. As part of our ongoing commitment to responsible AI, GitHub and Microsoft extends our IP indemnity and protection support to our customers who are empowering their teams with GitHub Copilot. See Microsoft's Copilot Copyright Commitment for more details.\n\nDoes GitHub Copilot support accessibility features?\nWe are conducting internal testing of GitHub Copilot’s ease of use by developers with disabilities and working to ensure that GitHub Copilot is accessible to all developers. Please feel free to share your feedback on GitHub Copilot accessibility in our feedback forum.\n\nDoes GitHub Copilot produce offensive outputs?\nGitHub Copilot includes filters to block offensive language in the prompts and to avoid synthesizing suggestions in sensitive contexts. We continue to work on improving the filter system to more intelligently detect and remove offensive outputs. If you see offensive outputs, please report them directly to copilot-safety@github.com so that we can improve our safeguards. GitHub takes this challenge very seriously and we are committed to addressing it.\n\nWill GitHub Copilot work as well using languages other than English?\nGiven public sources are predominantly in English, GitHub Copilot will likely work less well in scenarios where natural language prompts provided by the developer are not in English and/or are grammatically incorrect. Therefore, non-English speakers might experience a lower quality of service.\n\nGeneral\nWhat is GitHub Copilot?\nGitHub Copilot transforms the developer experience. Backed by the leaders in AI, GitHub Copilot provides contextualized assistance throughout the software development lifecycle, from inline suggestions and chat assistance in the IDE to code explanations and answers to docs in GitHub and more. With GitHub Copilot elevating their workflow, developers can focus on: value, innovation, and happiness.\nGitHub Copilot enables developers to focus more energy on problem solving and collaboration and spend less effort on the mundane and boilerplate. That’s why developers who use GitHub Copilot report up to 75% higher satisfaction with their jobs than those who don’t and are up to 55% more productive at writing code without sacrifice to quality, which all adds up to engaged developers shipping great software faster.\nGitHub Copilot integrates with leading editors, including Visual Studio Code, Visual Studio, JetBrains IDEs, and Neovim, and, unlike other AI coding assistants, is natively built into GitHub. Growing to millions of individual users and tens of thousands of business customers, GitHub Copilot is the world’s most widely adopted AI developer tool and the competitive advantage developers ask for by name.\n\nWho is eligible to access GitHub Copilot for free?\nGitHub Copilot Free is a new free pricing tier with limited functionality for individual developers. Users assigned a Copilot Business or Copilot Enterprise seat are not eligible for access. Users with access to Copilot Pro through a paid subscription, trial, or through an existing verified OSS, student, faculty, or MVP account may elect to use Free instead.\n\nWhat languages, IDEs, and platforms does GitHub Copilot support?\nGitHub Copilot is trained on all languages that appear in public repositories. For each language, the quality of suggestions you receive may depend on the volume and diversity of training data for that language. For example, JavaScript is well-represented in public repositories and is one of GitHub Copilot’s best supported languages. Languages with less representation in public repositories may produce fewer or less robust suggestions.\nGitHub Copilot is available as an extension in Visual Studio Code, Visual Studio, Vim, Neovim, the JetBrains suite of IDEs, and Azure Data Studio. Although inline suggestion functionality is available across all these extensions, chat functionality is currently available only in Visual Studio Code, JetBrains, and Visual Studio. GitHub Copilot is also supported in terminals through GitHub CLI and as a chat integration in Windows Terminal Canary. With the GitHub Copilot Enterprise plan, GitHub Copilot is natively integrated into GitHub.com. All plans are supported in GitHub Copilot in GitHub Mobile. GitHub Mobile for Copilot Pro and Copilot Business have access to Bing and public repository code search. Copilot Enterprise in GitHub Mobile gives you additional access to your organization's knowledge.\n\nDoes GitHub Copilot “copy/paste”?\nNo, GitHub Copilot generates suggestions using probabilistic determination.\nWhen thinking about intellectual property and open source issues, it is critical to understand how GitHub Copilot really works. The AI models that create GitHub Copilot’s suggestions may be trained on public code, but do not contain any code. When they generate a suggestion, they are not “copying and pasting” from any codebase.\n\nTo generate a code suggestion, the GitHub Copilot extension begins by examining the code in your editor—focusing on the lines just before and after your cursor, but also information including other files open in your editor and the URLs of repositories or file paths to identify relevant context. That information is sent to GitHub Copilot’s model, to make a probabilistic determination of what is likely to come next and generate suggestions.\n\nTo generate a suggestion for chat in the code editor, the GitHub Copilot extension creates a contextual prompt by combining your prompt with additional context including the code file open in your active document, your code selection, and general workspace information, such as frameworks, languages, and dependencies. That information is sent to GitHub Copilot’s model, to make a probabilistic determination of what is likely to come next and generate suggestions.\n\nTo generate a suggestion for chat on GitHub.com, such as providing an answer to a question from your chat prompt, GitHub Copilot creates a contextual prompt by combining your prompt with additional context including previous prompts, the open pages on GitHub.com as well as retrieved context from your codebase or Bing search. That information is sent to GitHub Copilot’s model, to make a probabilistic determination of what is likely to come next and generate suggestions.\n\nWhat are the differences between the GitHub Copilot Business, GitHub Copilot Enterprise, and GitHub Copilot Individual plans?\nGitHub Copilot has multiple offerings for organizations and an offering for individual developers. All the offerings include both inline suggestion and chat assistance. The primary differences between the organization offerings and the individual offering are license management, policy management, and IP indemnity.\nOrganizations can choose between GitHub Copilot Business and GitHub Copilot Enterprise. GitHub Copilot Business primarily features GitHub Copilot in the coding environment - that is the IDE, CLI and GitHub Mobile. GitHub Copilot Enterprise includes everything in GitHub Copilot Business. It also adds an additional layer of customization for organizations and integrates into GitHub.com as a chat interface to allow developers to converse with GitHub Copilot throughout the platform. GitHub Copilot Enterprise can index an organization’s codebase for a deeper understanding of the customer’s knowledge for more tailored suggestions and will offer customers access to fine-tuned custom, private models for inline suggestions.\nGitHub Copilot Individual is designed for individual developers, freelancers, students, educators, and open source maintainers. The plan includes all the features of GitHub Copilot Business except organizational license management, policy management, and IP indemnity.\n\nWhat data has GitHub Copilot been trained on?\nGitHub Copilot is powered by generative AI models developed by GitHub, OpenAI, and Microsoft. It has been trained on natural language text and source code from publicly available sources, including code in public repositories on GitHub. Starting on April 24, GitHub may also use interactions from users with a Copilot Free, Copilot Pro, and Copilot Pro+ subscription - including inputs, outputs, code snippets, and associated context - to train and improve our AI models unless they have opted out. This allows us to build more intelligent, context-aware coding assistance for a more diverse set of coding tasks based on real-world development patterns. Users were notified 30 days before the change went into effect and can opt out from allowing their data to be used for training in their GitHub account settings at any time.\n\nWhich plan includes GitHub Copilot Autofix?\nGitHub Copilot Autofix provides contextual explanations and code suggestions to help developers fix vulnerabilities in code, and is included in GitHub Advanced Security.\n\nWhat if I do not want GitHub Copilot?\nGitHub Copilot is entirely optional and requires you to opt in before gaining access. You can easily configure its usage directly in the editor, enabling or disabling it at any time. Additionally, you have control over which file types GitHub Copilot is active for.\n\nHow do I control access to GitHub Copilot in my company?\nAccess to Copilot Business and Enterprise is managed by your GitHub Administrator. They can control access to preview features, models, and set GitHub Copilot policies for your organization. Additionally, you can use your network firewall to explicitly allow access to Copilot Business and/or block access to Copilot Pro or Free. For more details, refer to the documentation.\n\nPlans & Pricing\nWhat are the differences between the Free, Pro, Pro+, Max, Business, and Enterprise plans?\nGitHub Copilot has multiple offerings for organizations and an offering for individual developers. All the offerings include both code completion and chat assistance. The primary differences between the organization offerings and the individual offering are license management, policy management, and IP indemnity.\nOrganizations can choose between GitHub Copilot Business and GitHub Copilot Enterprise. GitHub Copilot Business primarily features GitHub Copilot in the coding environment - that is the IDE, CLI and GitHub Mobile. GitHub Copilot Enterprise includes everything in GitHub Copilot Business. It also adds an additional layer of customization for organizations and integrates into GitHub.com as a chat interface to allow developers to converse with Copilot throughout the platform. GitHub Copilot Enterprise can index an organization’s codebase for a deeper understanding of the customer’s knowledge for more tailored suggestions and will offer customers access to fine-tuned custom, private models for code completion.\nGitHub Copilot Pro is designed for individual developers, freelancers, students, educators, and open source maintainers. The plan includes all the features of GitHub Copilot Business except organizational license management, policy management, and IP indemnity.\nGitHub Copilot Max is built for heavy Copilot usage, including sustained agent-driven workflows, and includes $100/month in GitHub AI Credits.\n\nHow can I upgrade my GitHub Copilot Free license to Copilot Pro?\nIf you're on the Free plan, you can upgrade to Pro through your Copilot settings page or directly on the Copilot marketing page.\n\nWhat is included in GitHub Copilot Free?\nCopilot Free includes 2,000 code completions per month and a limited monthly allowance of GitHub AI Credits for chat and agent features. Models are provided through auto model selection. Usage varies with the model and the number of tokens processed.\n\nWhich plan includes GitHub Copilot Autofix?\nGitHub Copilot Autofix provides contextual explanations and code suggestions to help developers fix vulnerabilities in code, and is included in GitHub Advanced Security and available to all public repositories.\n\nCan users in my organization use Copilot code reviews for their pull requests if they don’t have a Copilot license?\nOrganizations can now enable Copilot code review on all pull requests on github.com—including pull requests from users who are not assigned a Copilot license.\nThis allows you to extend the quality and rich analysis of Copilot code review to all pull requests, regardless of its author, giving you complete coverage and confidence that pull requests have been reviewed.\nTo enable this functionality, an enterprise/org admin must first have Copilot enabled and then enabled two policies.\nNote: This capability is not supported for Copilot code reviews in VS Code or other IDEs.\n\nHow does billing work for Copilot code review usage generated by users without a Copilot license?\nUsage from non-licensed users is billed directly to your organization as GitHub AI Credits. This flexible model allows you to get full review coverage on every PR without purchasing a full Copilot seat for non-development contributors who may not need Copilot.\nUsage from your existing licensed users continues to draw from their included monthly allowance as it does today. Beginning June 1, 2026, code review workflows also consume GitHub Actions minutes.\n\nIs Copilot code review usage from users without a Copilot license enabled by default? How do I control the cost?\nNo. This capability is off by default and gives the enterprise admin control to enable or disable. An admin must explicitly enable two separate policies to activate:\n‘GitHub AI Credits paid usage’ must be enabled to allow enterprises to be charged for GitHub AI Credits exceeding their included usage.\n\nA new Copilot code review policy (‘Allow members without a Copilot license to use Copilot code review in github.com’) must also be enabled.\n\nWe encourage admins to set up budgets to control spending on our metered products, especially customers who have not enabled the ‘Premium request paid usage’ policy in the past. You can track all premium request usage in your billing dashboard to monitor and control spending.\n\nWhat are GitHub AI Credits?\nGitHub AI Credits are how you pay for AI usage in GitHub Copilot. Every plan includes a monthly allowance: 1 AI credit = $0.01 USD.\nYou use credits when you chat with Copilot, work with agents, or use Copilot CLI, and Spaces. Code completions and next edit suggestions don't use credits. They remain unlimited with every paid plan.\nHow many credits an interaction uses depends on the model you choose and the complexity of the task. A quick question to a lightweight model costs a fraction of a credit. A longer agent session on a frontier model across many files costs more.\n\nWhat happens when I hit my usage limit?\n\nWhen you've used your monthly allowance, you have a few options:\nWait for your next cycle. Your included allowance resets every month.\n\nKeep working with paid usage. Set a dollar budget for additional usage and Copilot continues without interruption. Credits draw down at $0.01 each, so a $10 budget covers 1,000 credits.\n\nSwitch to a less expensive model. Lightweight models use fewer credits per interaction and stretch your remaining allowance further.\n\nOn GitHub Copilot Business and GitHub Copilot Enterprise, admins set usage limits and decide whether additional paid usage is allowed. If it isn't, Copilot pauses until the next cycle.\nYou can track your usage and reset date in your Copilot settings, with alerts at 75%, 90%, and 100% of any configured budget.\n\nPrivacy\nWhat personal data does GitHub Copilot process?\nGitHub Copilot processes personal data based on how Copilot is accessed and used: whether via GitHub.com, mobile app, extensions, or one of various IDE extensions, or through features like suggestions for the command line interface (CLI), IDE code completions, or personalized chat on GitHub.com. The types of personal data processed may include:\nUser Engagement Data: This includes pseudonymous identifiers captured on user interactions with Copilot, such as accepted or dismissed completions, error messages, system logs, and product usage metrics.\n\nPrompts: These are inputs for chat or code, along with context, sent to Copilot's AI to generate suggestions.\n\nSuggestions: These are the AI-generated code lines or chat responses provided to users based on their prompts.\n\nFeedback Data: This comprises real-time user feedback, including reactions (e.g., thumbs up/down) and optional comments, along with feedback from support tickets.\n\nDoes GitHub use Copilot Business or Enterprise data to train GitHub’s model?\nNo. GitHub does not use either Copilot Business or Enterprise data to train its models.\n\nHow does GitHub use the Copilot data from Business and Enterprise Subscribers?\nHow GitHub uses Copilot data depends on how the user accesses Copilot and for what purpose. Users can access GitHub Copilot through the web, extensions, mobile apps, computer terminal, and various IDEs (Integrated Development Environments). GitHub generally uses personal data to:\nDeliver, maintain, and update the services as per the customer's configuration and usage, to ensure personalized experiences and recommendations\n\nTroubleshoot, which involves preventing, detecting, resolving, and mitigating issues, including security incidents and product-related problems, by fixing software bugs and maintaining the online services' functionality and up-to-dateness\n\nEnhance user productivity, reliability, effectiveness, quality, privacy, accessibility, and security by keeping the service current and operational\n\nThese practices are outlined in GitHub’s Data Protection Agreement (DPA), which details our data handling commitments to our data controller customers. GitHub also uses certain personal data with customer authorization under the DPA, for the following purposes:\nBilling and account management\n\nTo comply with and resolve legal obligations\n\nFor abuse detection, prevention, and protection, virus scanning, and scanning to detect violations of terms of service\n\nTo generate summary reports for calculating employee commissions and partner incentives\n\nTo produce aggregated reports for internal use and strategic planning, covering areas like forecasting, revenue analysis, capacity planning, and product strategy.\n\nHow does GitHub use the Copilot data from Individual (Free/Pro/Pro+) Subscribers?\n\nGitHub uses the Copilot data from Individual subscribers for all the operational purposes described above for Business/Enterprise subscribers.\nIn addition, for Individual subscribers only: GitHub may use Copilot interaction data — including prompts (inputs), suggestions (outputs), and code snippets generated during Copilot sessions — to train and improve AI models. This training helps improve code suggestions for all Copilot users.\nIndividual subscribers can opt out of having their data used for AI model training at any time through https://github.com/settings/copilot/features. Opting out does not affect your access to Copilot features.\nFor details on GitHub's data processing activities as a controller, particularly for Copilot Free, Copilot Pro, and Copilot Pro customers, refer to the GitHub Terms of Service and the GitHub Privacy Statement.\n\nHow long does GitHub retain Copilot data for Business and Enterprise customers?\n\nIf and for how long GitHub’s retains Copilot data depends on how a Copilot user accesses Copilot and for what purpose. The default settings for Copilot Business and Enterprise Customers are as follows:\nAccess through IDE for Chat and Code Completions:\nPrompts and Suggestions: Not retained\n\nUser Engagement Data: Kept for two years.\n\nFeedback Data: Stored for as long as needed for its intended purpose.\n\nAll other GitHub Copilot access and use:\nPrompts and Suggestions: Retained for 28 days.\n\nUser Engagement Data: Kept for two years.\n\nFeedback Data: Stored for as long as needed for its intended purpose.\n\nWhy do some Copilot features retain prompts and suggestions?\nRetaining prompts and suggestions is necessary for chat on github.com, mobile, and CLI Copilot because those features’ effectiveness depends on using thread history to improve responses. The Copilot model requires access to previous interactions to deliver accurate and relevant suggestions.\n\nDoes GitHub Copilot support compliance with the GDPR and other data protection laws?\nYes. GitHub and customers can enter a Data Protection Agreement that supports compliance with the GDPR and similar legislation.\n\nDoes GitHub Copilot ever output personal data?\nWhile we've designed GitHub Copilot with privacy in mind, the expansive definition of personal data under legislation like the EU’s General Data Protection Regulation (GDPR) means we can't guarantee it will never output such data. The Large Language Model (LLM) powering GitHub Copilot was trained on public code and there were instances in our tests where the tool made suggestions resembling personal data. These suggestions were typically synthesized and not tied to real individuals.\n\nHow does Copilot allow users to access, alter or delete personal data?\nThese actions are available to Copilot users as described in the GitHub Privacy Statement.\n\nResponsible AI\nWhat are the intellectual property considerations when using GitHub Copilot?\nThe primary IP considerations for GitHub Copilot relate to copyright. The model that powers Copilot is trained on a broad collection of publicly accessible code, which may include copyrighted code, and Copilot’s suggestions (in rare instances) may resemble the code its model was trained on. Here’s some basic information you should know about these considerations:\nCopyright law permits the use of copyrighted works to train AI models: Countries around the world have provisions in their copyright laws that enable machines to learn, understand, extract patterns, and facts from copyrighted materials, including software code. For example, the European Union, Japan, and Singapore, have express provisions permitting machine learning to develop AI models. Other countries including Canada, India, and the United States also permit such training under their fair use/fair dealing provisions. GitHub Copilot’s AI model was trained with the use of code from GitHub’s public repositories—which are publicly accessible and within the scope of permissible copyright use.\nWhat about copyright risk in suggestions? In rare instances (less than 1% based on GitHub’s research), suggestions from GitHub may match examples of code used to train GitHub’s AI model. Again, Copilot does not “look up” or “copy and paste” code, but is instead using context from a user’s workspace to synthesize and generate a suggestion.\nOur experience shows that matching suggestions are most likely to occur in two situations: (i) when there is little or no context in the code editor for Copilot’s model to synthesize, or (ii) when a matching suggestion represents a common approach or method. If a code suggestion matches existing code, there is risk that using that suggestion could trigger claims of copyright infringement, which would depend on the amount and nature of code used, and the context of how the code is used. In many ways, this is the same risk that arises when using any code that a developer does not originate, such as copying code from an online source, or reusing code from a library. That is why responsible organizations and developers recommend that users employ code scanning policies to identify and evaluate potential matching code.\nIn Copilot, you can opt whether to allow Copilot to suggest code completions that match publicly available code on GitHub.com. For more information, see \"Configuring GitHub Copilot settings on GitHub.com\". If you have allowed suggestions that match public code, GitHub Copilot can provide you with details about the matching code when you accept such suggestions. Matching code does not necessarily mean copyright infringement, so it is ultimately up to the user to determine whether to use the suggestion, and what and who to attribute (along with other license compliance) in appropriate circumstances.\n\nDoes GitHub Copilot include a filtering mechanism to mitigate risk?\n\nYes, GitHub Copilot does include an optional code referencing filter to detect and suppress certain suggestions that match public code on GitHub.\nGitHub has created a duplication detection filter to detect and suppress suggestions that contain code segments over a certain length that match public code on GitHub. This filter can be enabled by the administrator for your enterprise and it can apply for all organizations within your enterprise, or the administrator can defer control to individual organizations.\n\nWith the filter enabled, Copilot checks code suggestions for matches or near-matches against public code on GitHub of 65 lexemes or more (on average,150 characters). If there is a match, the suggestion will not be shown to the user.\n\nIn addition to off-topic, harmful, and offensive output filters, GitHub Copilot also scans the outputs for vulnerable code.\n\nDoes GitHub Copilot include features to make it easier for users to identify potentially relevant open source licenses for matching suggestions?\nYes, GitHub Copilot is previewing a code referencing feature as an additional tool to assist users to find and review potentially relevant open source licenses. Code referencing is currently available in Visual Studio Code. This feature searches across public GitHub repositories for code that matches a Copilot suggestion. If there’s a match, users will find its information displayed in the Copilot console log, including where the match occurred, any applicable licenses, and a deep link to learn more. The deep link will take users to a navigable page on GitHub.com to browse examples of the code match and their repository licenses, and see how many repositories—including ones without licenses—that code appears in, as well as links to those repositories. Copilot users can review this information to determine whether the applicable suggestions are suitable for use, and whether additional measures may be necessary to use them.\n\nWho owns the suggestions provided by GitHub Copilot?\n\nWe don’t determine whether a suggestion is capable of being owned, but we are clear that GitHub does not claim ownership of a suggestion. Whether a suggestion generated by an AI model can be owned depends on many factors (e.g. the intellectual property law in the relevant country, the length of the suggestion, the extent that suggestion is considered ‘functional’ instead of expressive, etc).\nIf a suggestion is capable of being owned, our terms are clear: GitHub does not claim ownership.\n\nGitHub does not claim ownership of any suggestion. In certain cases, it is possible for Copilot to produce similar suggestions to different users. For example, two unrelated users both starting new files to code the quicksort algorithm in Java will likely get the same suggestion. The possibility of providing similar suggestions to multiple users is a common part of generative AI systems.\n\nCan GitHub Copilot introduce insecure code in its suggestions?\nPublic code may contain insecure coding patterns, bugs, or references to outdated APIs or idioms. When GitHub Copilot synthesizes code suggestions based on this data, it can also synthesize code that contains these undesirable patterns. Copilot has filters in place that either block or notify users of insecure code patterns that are detected in Copilot suggestions. These filters target the most common vulnerable coding patterns, including hardcoded credentials, SQL injections, and path injections. Additionally, in recent years we’ve provided tools such as GitHub Advanced Security, GitHub Actions, Dependabot, and CodeQL to open source projects to help improve code quality. Of course, you should always use GitHub Copilot together with good testing and code review practices and security tools, as well as your own judgment.\n\nIs GitHub Copilot intended to fully automate code generation and replace developers?\nNo. Copilot is a tool intended to make developers more efficient. It’s not intended to replace developers, who should continue to apply the same sorts of safeguards and diligence they would apply with regard to any third-party code of unknown origin.\nThe product is called “Copilot” not “Autopilot” and it’s not intended to generate code without oversight. You should use exactly the same sorts of safeguards and diligence with Copilot’s suggestions as you would use with any third-party code.\n\nIdentifying best practices for use of third party code is beyond the scope of this section. That said, whatever practices your organization currently uses – rigorous functionality testing, code scanning, security testing, etc. – you should continue these policies with Copilot’s suggestions. Moreover, you should make sure your code editor or editor does not automatically compile or run generated code before you review it.\n\nCan GitHub Copilot users simply use suggestions without concern?\nNot necessarily. GitHub Copilot users should align their use of Copilot with their respective risk tolerances.\nAs noted above, GitHub Copilot is not intended to replace developers, or their individual skill and judgment, and is not intended to fully automate the process of code development. The same risks that apply to the use of any third-party code apply to the use of Copilot’s suggestions.\n\nDepending on your particular use case, you should consider implementing the protections discussed above. It is your responsibility to assess what is appropriate for the situation and implement appropriate safeguards.\n\nYou’re entitled to IP indemnification from GitHub for the unmodified suggestions when Copilot’s filtering is enabled. If you do elect to enable this feature, the copyright responsibility is ours, not our customers. As part of our ongoing commitment to responsible AI, GitHub and Microsoft extends our IP indemnity and protection support to our customers who are empowering their teams with GitHub Copilot. See Microsoft's Copilot Copyright Commitment for more details.\n\nDoes GitHub Copilot support accessibility features?\nWe are conducting internal testing of GitHub Copilot’s ease of use by developers with disabilities and working to ensure that GitHub Copilot is accessible to all developers. Please feel free to share your feedback on GitHub Copilot accessibility in our feedback forum.\n\nDoes GitHub Copilot produce offensive outputs?\nGitHub Copilot includes filters to block offensive language in the prompts and to avoid synthesizing suggestions in sensitive contexts. We continue to work on improving the filter system to more intelligently detect and remove offensive outputs. If you see offensive outputs, please report them directly to copilot-safety@github.com so that we can improve our safeguards. GitHub takes this challenge very seriously and we are committed to addressing it.\n\nWill GitHub Copilot work as well using languages other than English?\nGiven public sources are predominantly in English, GitHub Copilot will likely work less well in scenarios where natural language prompts provided by the developer are not in English and/or are grammatically incorrect. Therefore, non-English speakers might experience a lower quality of service.\n\nCode review will incur Actions usage.\nResponse times may vary during periods of high usage. Requests may be subject to rate limiting.\nFlex allotments will vary over time.","tokens":15969,"crawled_at":1791195957685}
+{"id":10579,"url":"https://a16zcrypto.com/posts/article/introducing-the-nakamoto-challenge-addressing-the-toughest-problems-in-crypto","domain":"a16zcrypto.com","chapter":"research","title":"Introducing the Nakamoto Challenge: Addressing the Toughest Problems in Crypto - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nIntroducing the Nakamoto Challenge: Addressing the Toughest Problems in Crypto\nGuy Wuollet\n09.28.23\n\nTABLE OF CONTENTS\nThe Limits of Atomic Composability and Shared Sequencing The Limits of Atomic Composability and Shared Sequencing\nDePIN Verification\nJOLT + Lasso Problem\nCompliant Programmable Privacy\nOptimal LVR Mitigation\nDesigning the MEV Transaction Supply Chain\nLeveraging Blockchain For Deepfake Protection\nTags\nannouncements\nannouncements & news\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nWe’re fortunate to have a broad view across the crypto landscape and the opportunity to talk with the best builders, founders, and entrepreneurs. As a result, we hear about many interesting problems that the smartest people are working on. Some are problems that everyone has and are just too challenging to solve, and some are poorly documented and exist only as tribal knowledge.\n\nWe’ve made a list of hard problems and open questions that we believe can and should be solved to help unlock the future of crypto. Like important nodes in a tech tree, solving each problem below would unblock many builders and developers that create and support decentralized networks. In honor of the whitepaper author that started it all, we’re calling this the Nakamoto Challenge.\n\nLast week we announced that applications are open until October 20th for our next cohort of Crypto Startup School. We’re looking for founders who want to take big, bold swings in crypto and are hellbent on building something transformational. We don’t expect our Nakamoto Challenge to result in fully-formed solutions to these thorny problems, but we do want to activate the smartest entrepreneurs to propose and start building creative new paths to get there, which would advance the whole crypto ecosystem. The person or company with the best answer to each Nakamoto Challenge question will be fast-tracked to the interview stage of our Crypto Startup School application process.\n\nIf you have a compelling answer to one or more of our questions, please email them to us at cryptostartupschool@a16z.com.\n\nHappy hunting!\n\nThe Limits of Atomic Composability and Shared Sequencing\n\nProblem statement: Perhaps the most-talked-about path to scaling blockchains today is deploying many rollups on Ethereum. While this bootstraps security and decentralization, deploying many disconnected rollups on Ethereum will fracture composability. We believe atomic composability – the ability to send a transaction A that finalizes if, and only if, transaction B is finalized – is crucial.\n\nPlease describe the limits of composability between rollups on Ethereum. Ideally a solution would propose a formal model of rollups and an impossibility result.\n\nRelevant reading:\n\nShared Validity Sequencing\n\nThe Espresso Sequencer\n\nShared Sequencing: Defragmenting the L2 Rollup Ecosystem\n\nOptimism Superchain and Superchain Explainer\n\nzkSync Hyperchains and Hyperchains documentation\n\nRollups aren’t real\n\nDePIN Verification\n\nProblem Statement:\n\nDecentralized Physical Infrastructure Networks (DePIN) represent a class of blockchain applications dealing with physical infrastructure. Whereas smart contract platforms and payments can use classical consensus or validity proofs for trustless computation, DePIN projects often can’t due to scalability constraints and the oracle problem of verifying physical sensor data.\n\nCurrent hardware-based approaches to verification include embedding a public/private key pair at the time of manufacture, or building custom hardware with a secure element like a trusted execution environment. Unfortunately, embedding a key pair means that only devices manufactured by certain parties can join the network, adding a level of permissioning, and trusted execution environments both require application-specific hardware and are often vulnerable to hacks.\n\nAs existing software approaches like consensus and validity proofs aren’t feasible, and existing hardware approaches have significant downsides, we’re excited about new potential software-based approaches to verification. Some projects have explored the idea of random sampling as a measurement method to ensure that rational participants in a DePIN network are behaving in accordance with the protocol.\n\nThe early outline of a random sampling approach to verification usually involves the network generating measurement requests to each provider/validator on the network. If the measurement request is correctly served, the provider receives a larger reward, akin to a block reward. As long as the provider can’t distinguish between a measurement request and a normal request, they are incentivized to correctly respond to each request.\n\nWithout verification, many DePIN networks fall victim to three common incentive challenges:\n\nSelf dealing occurs when providers in a DePIN network request services from themselves and receive a block reward or service payment from the network. If providers receive a larger payment than users make — often the case because of early subsidies or block rewards — then it’s profitable to buy service from yourself as a service provider.\n\nContending with lazy providers who commit to serving client requests but simply don’t respond, or respond with lower quality of service than they committed to.\n\nA provider is willing to lose money to convince a client of a malicious response. Random sampling does the worst job addressing malicious providers as currently outlined, and does a much better job at ameliorating self dealing or laziness.\n\nPlease propose a generalized solution to verification for DePIN projects, or a specific solution for a sub-category of DePIN projects (DeWi, Decentralized Energy, Decentralized ridesharing/delivery, etc.)\n\nRelevant Reading:\n\nEngineering Filecoin’s economy\n\nOrchid Whitepaper\n\nHelium Whitepaper\n\nHelium Proof of Coverage\n\nNym whitepaper\n\nJOLT + Lasso Problem\n\nProblem Statement:\n\nSNARK virtual machines (VMs) enable highly-scalable decentralized computation, such as blockchains. Jolt is a new model for building SNARK VMs on top of Lasso, a fast lookup argument. We believe Jolt will be the most efficient way to build custom SNARK VMs in the near future. We released a sample implementation for Lasso earlier this year and are targeting a full release of Jolt later this year.\n\nThe efficiency of modern non-interactive proof systems are dependent on the efficiency of their polynomial commitment schemes. Lasso builds on a different lineage of SNARKs than the majority of those in production today. These sumcheck-based SNARKs depend on multilinear polynomial commitment schemes (PCS) rather than univariate. As a result, less analysis has been put into the efficiency properties (for both the prover and verifier) for multilinear polynomial commitment schemes. Section 2.2 of the Lasso paper briefly describes these different PCS.\n\nPlease expand on this section to provide a comprehensive analysis (theoretical and/or empirical) of 3-5 different polynomial commitment schemes and their cost in the context of verification for decentralized systems. We’re interested in both the cost profiles of the prover and verifier directly, as well as the cost of recursively verifying Jolt proofs within existing SNARK schemes, especially those with EVM-compatible verifiers.\n\nSpecifically, please detail:\n\nProver compute cost\n\nVerifier compute cost\n\nProof size\n\nRecursive verifier compute cost\n\nRecursive verifier proof size\n\nRelevant Reading:\n\nLasso Paper\n\nJolt Paper\n\nLasso Repo\n\nIntroducing Lasso and Jolt\n\nUnderstanding Lasso and Jolt\n\nCompliant Programmable Privacy\n\nProblem Statement:\n\nWhile most smart contracts and blockchains today are fully transparent, we deeply believe privacy is essential for fully realizing blockchain’s potential as a social coordination tool in building decentralized networks. It’s become apparent that privacy is increasingly complex, and that private smart contracts or payments protocols may need to factor in some KYC, compliance, or illicit finance and sanctions screening features to enable users in different jurisdictions to participate and to limit developer exposure to legal risk. Current approaches include deposit delays, and deposit and withdrawal screening. Existing approaches are made even more complicated by fully-programmable smart contract platforms, where any developer can deploy their own bridge.\n\nPlease provide suggested compliance solution(s) to address illicit finance mitigation for privacy-enabling and programmable smart contract platforms. A solution should eliminate legal and regulatory risks to the greatest extent possible, while maintaining privacy and trustlessness.\n\nRelevant Reading:\n\nAchieving Crypto Privacy and Regulatory Compliance\n\nPrivacy-Protecting Regulatory Solutions Using Zero-Knowledge Proofs: Full Paper\n\nDerecho: Privacy Pools with Proof-Carrying Disclosures\n\nPrivacy Pools\n\nBlockchain Privacy and Regulatory Compliance: Towards a Practical Equilibrium\n\nConfigurable Asset Privacy for Ethereum (CAPE)\n\nOptimal LVR Mitigation\n\nProblem Statement:\n\nLoss vs. rebalancing (aka LVR and pronounced ‘Lever’) was proposed in a 2022 paper as a way of modeling adverse selection costs borne by liquidity providers to constant function market maker decentralized exchanges (CFMM DEXs). Current work is focused on finding an optimal way to mitigate LVR in DEXs without using a price oracle.\n\nPlease describe the potential mitigations to LVR and argue why your proposed solution is better than all known alternatives.\n\nRelevant Reading:\n\nLoss vs. Rebalancing Paper\n\nLVR: Quantifying the Cost of Providing Liquidity to Automated Market Makers\n\nSBC ‘22 LVR Talk by Tim Roughgarden\n\nAutomated Market Making and Loss-Versus-Rebalancing\n\nDesigning the MEV Transaction Supply Chain\n\nProblem Statement:\n\nAssuming you could start from scratch, what is the optimal design of the miner extractable value (MEV) transaction supply chain? The process today is most naturally separated into distinct roles for searchers, builders, and proposers. What are the economic tradeoffs for maintaining these as separate roles versus having them consolidate? Are there new roles that would be beneficial to introduce? What are the optimal mechanisms to mediate how these different parties interact? Can the mechanisms mediating how the MEV supply chain functions be purely economic or are there components that require cryptographic solutions/trusted components?\n\nThe notion of what “optimal” means is intentionally left vague. Argue for what metrics are the most important when evaluating different mechanisms. Do we require strict collusion resistance between any groups of agents throughout the supply chain? Do we only require collusion resistance between agents at the same level of the supply chain? Is it enough that the mechanism’s properties hold in equilibrium or is it important that all parties have dominant strategies? On the other hand, what are lower bounds for how “optimal” the transaction supply chain can be? Are there certain conditions under which it is impossible to achieve all the “optimal” properties we might want?\n\nThis problem is left open to interpretation. Feel free to address any of the questions above or provide your own direction towards designing mechanisms for the transaction supply chain.\n\nRelevant Reading:\n\nCredible Auctions: A Trilemma\n\nFoundations of Transaction Fee Mechanism Design\n\nTransaction Fee Mechanism Design with Active Block Producers\n\nThe Centralizing Effects of Private Orderflow on PBS\n\nContingent Fees in Orderflow Auctions\n\nTime is Money: Strategic Timing Games in Proof-of-Stake Protocols\n\nThe Specter (and Spectra) of Miner Extractable Value\n\nWhy Enshrine Proposer Builder Separation\n\nThe Future of MEV is SUAVE\n\nInfinite Games\n\nLeveraging Blockchain For Deepfake Protection\n\nProblem Statement: The rise of deepfakes (synthetic videos, photos, or audio recordings produced by artificial intelligence) that can convincingly replace a person’s likeness and voice – leading to potential misuse in misinformation campaigns, fraud, and other malicious activities – has been a common topic of conversation recently. While various deepfake detection methods are being researched, the challenge remains in providing a verifiable and trustless way to ensure the authenticity of digital content.\n\nBlockchains and smart contracts present a promising avenue to counter this issue. By leveraging the immutable nature of blockchains and the automated execution of smart contracts, it’s possible to create a system that verifies and validates genuine content and differentiates it from tampered or deepfaked versions.\n\nYour task is to devise a system that can enable viewers or platforms to verify the authenticity of videos, voice recordings, or photos. This may include reputation systems (reward or penalize based on the validation result, e.g., rewarding creators for genuine content or flagging tampered content) or it may not. Consider the scalability, privacy, and efficiency of your proposed system, especially when large video files are involved. Your solution should minimize computational and storage overheads and should be feasible for widespread adoption.\n\nKey challenges include addressing the re-recording attack vector (if someone records a screen displaying a video, this secondary recording might bypass some naive authenticity checks) as well as allowing for legitimate changes (cropping, shortening videos).\n\nRelevant Reading:\n\nDeep Fake Generation and Detection: Issues, Challenges, and Solutions\n\nCombating Deepfake Videos Using Blockchain and Smart Contracts\n\nHow Blockchain Can Help Combat Disinformation\n\nWhy Decentralized CMS is the Future of Content Management for Web 3.0 and Beyond\n\nCombating Deepfakes: Multi-LSTM and Blockchain as Proof of Authenticity for Digital Media\n\nGeometrically robust video hashing based on ST-PCT for video copy detection\n\nSolving the Deepfake Problem: Proving the Authenticity of Digital Artifacts with Blockchain\n\nAcknowledgements: Thank you to Pranav Garimidi, Liz Harkavy, Michele Korver, Sam Ragsdale, and Tim Roughgarden for contributing challenge questions and to Jason Rosenthal, Daren Matsuoka, and Mike Manning for their help in making this a reality.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investment-list/.\n\nPast performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures/ for additional important information.","tokens":4217,"crawled_at":1791195963542}
+{"id":10580,"url":"https://docs.ethena.fi/resources/usde-terms-and-conditions","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"USDe Terms and Conditions | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nLast Updated: August 2025\n\nUsers who have completed Know-Your-Customer and Anti-Money Laundering checks, as well as other onboarding procedures, and are whitelisted with Ethena BVI Limited (“Ethena BVI”) are referred to herein as a “Mint User.” To the extent you have not completed the aforementioned checks or been whitelisted but hold USDe, these Terms still apply to your holding and use of USDe (hereinafter referred as “Holding User”). For the avoidance of doubt, Holding Users are not customers of Ethena BVI.\nBy obtaining and using USDe, you understand and expressly agree to these Terms, regardless of whether or not you are a customer of Ethena BVI, and you acknowledge that you have reviewed and understand each of the disclosures made in this section. Any provisions of these Terms that only apply to Mint Users or Holding Users will be specifically noted herein. Unless so noted, each Section of these Terms apply to both Mint Users and Holding Users, and any use of “you” or “your” refers to both Mint Users and Holding Users. The terms herein applicable to Mint Users are supplemental to the terms in the USDe Mint User Agreement.\nBy holding or using USDe, or using any of the USDe Services, you agree that you have read, understood and accept all of the terms and conditions contained in these Terms, as well as our Privacy Policy and Cookie Policy, and you acknowledge and agree that you will be bound by these terms and policies.\nSection 22 of these Terms governs how these Terms may be changed over time; the date of the last update is set forth at the top of these Terms.\n1. About USDe\nUSDe is a digital token issued by Ethena BVI. USDe issued by Ethena BVI is a form of stored value or prepaid access and does not represent a claim, participation interest, economic right, voting right, or other similar right associated with Ethena BVI or any of its affiliates.\nUSDe is backed by an amount of spot crypto assets, such as BTC, ETH, SOL, certain liquid staking tokens, certain stablecoins (such as USDC, USDT, and USDtb), and offsetting hedging positions on derivatives contracts the (“USDe Reserves”).\nUnaffiliated third parties, including the Ethena Foundation directly and via the Ethena Risk Committee, provide input on certain parameters associated with the USDe Reserves. The Ethena Foundation does not have any members, ultimate beneficial owners, or beneficiaries, and exists with the principal objects of supporting the Ethena Protocol and its architecture. No shareholders, employees, contractors, ultimate beneficial owners, or other party affiliated with Ethena BVI or its affiliates holds a position of ownership or control with respect to the Ethena Foundation.\nUSDe is not designed to intrinsically create returns for holders, increase in value, or otherwise accrue financial benefit to the USDe holder.\n2. Scope of USDe and Key Terms\nThe following only applies to Mint Users: As you have agreed to, and are subject to, the USDe Mint User Agreement, Ethena BVI makes available the following USDe-related Services (as defined in the USDe Mint User Agreement: (i) create USDe in exchange for accepted tokens from Ethena BVI, and (ii) redeem USDe for supported assets from Ethena BVI (collectively, the “USDe Services”). Your use of the USDe Services is subject to these Terms. Any of the USDe Services can be discontinued at any time in accordance with Section 14 of these USDe Terms.\nYou understand and agree that you may only utilize accepted assets to create USDe and redeem USDe directly with Ethena BVI to the extent that you are a Mint User.\nThe following only applies to Holding Users: You may not redeem USDe with Ethena BVI unless and until you are a Mint User who has cleared KYC/AML and other checks and have onboarded as a whitelisted customer with Ethena BVI. Eligibility for and requirements related to such process are set forth in the USDe Mint User Agreement.\nThe following applies to both Mint Users and Holding Users: Your use of USDe and USDe Services (as applicable), is subject to these Terms and Ethena BVI’s obligations hereunder are conditional on you complying with its provisions. You understand that any violation of these Terms may result in potential consequences, including the possible loss or forfeiture of assets tokenized for USDe.\nYou understand and agree that sending USDe to another address automatically transfers and assigns to the owner of that address, and any subsequent owner all rights and obligations of a Holding User to redeem USDe for approved assets so long as the Holder is or becomes a Mint User. For the avoidance of doubt, if a Holder is not a Mint User, not eligible to become a Mint User, or fails to do so, such Holding User is not entitled to redeem USDe with Ethena BVI.\nEthena BVI (or an affiliate designated by Ethena BVI) commits to redeem 1 USDe for the notional value relating to its pro rata portion of the USDe Reserves in supported digital assets, up to a maximum amount of 1 USD in notional value, subject to these Terms, applicable law, and any fees where applicable. While Ethena BVI may hold the USDe Reserves in interest-bearing accounts or other yield-generating instruments, you acknowledge that you are not entitled to any interest or other returns earned on such funds as either a Holding User or Mint User. USDe does not itself generate any interest or return for holders of USDe and only represents your right to redeem USDe as a Mint User, if you are one. If you are a Holding User, you do not have a right to redeem USDe with Ethena BVI.\n3. Applicable Laws and Regulations; AML and CTF\nYour holding and use of USDe, and any use of the USDe Services, is subject to the laws, regulations, and rules of any applicable governmental or regulatory authority, including, without limitation, all applicable tax, anti-money laundering (“AML”) and counter-terrorist financing (“CTF”) provisions and sanctions. You agree to act in compliance with and be legally bound by these Terms and all applicable laws and regulations. These Terms are conditional on your continued compliance at all times with these Terms and all applicable laws and regulations.\nEthena BVI is committed to complying with all applicable AML and CTF laws and regulations. These standards are designed to prevent the use of the USDe Services for money laundering, terrorist financing, fraudulent transactions, and any other illegal activities. Ethena BVI takes compliance very seriously and actively engages in measures to:\n• Prohibit fraudulent transactions;\n• Report suspicious activities;\n• Prevent money laundering, terrorist financing, and any related acts that facilitate financial crimes.Applicable laws require us to prevent Restricted Persons from holding USDe or using USDe Services. A Restricted Person means any person that is the subject or target of any sanctions, including a person that is:\n\nnamed in any Sanctions-related list maintained by the U.S. Department of State; the U.S. Department of Commerce, including the Bureau of Industry and Security’s Entity List and Denied Persons List; or the U.S. Department of the Treasury, including the OFAC Specially Designated Nationals and Blocked Persons List, the Sectoral Sanctions Identifications List, and the Foreign Sanctions Evaders List; or any similar list maintained by any other relevant governmental authority;\n\nlocated, organized or resident in a country, territory or geographical region which is itself the subject or target of any territory-wide Sanctions (a “Restricted Territory”) (currently, Cuba, Iran, Syria, North Korea, and the Ukraine regions of Crimea, Donetsk, and Luhansk); or\n\nowned or controlled by any such person or persons listed above.\n\n4. Eligibility; Limitations\nThe following applies to both Mint Users and Holding Users: USDe Services and support for USDe are currently only available to individuals and institutions (as applicable) located in supported jurisdictions.\nBy holding or using USDe, or accessing or using the USDe Services, you further represent and warrant that:\n\nyou are at least 18 years old, are not a Restricted Person, and are not holding USDe on behalf of a Restricted Person.\n\nyou will not be using USDe or the USDe Services (as applicable) for any illegal activity, including, but not limited to, illegal gambling, money laundering, fraud, blackmail, extortion, ransoming data, terrorism financing, other violent activities or any prohibited market practices, including, but not limited to, those listed under Sections 16 and 17.\n\nAdditionally, users in the United States are not eligible to become a Mint User. This restriction may be revisited from time to time taking into account relevant changes in law.\nYou also understand that there are additional representations and warranties made by you elsewhere in (or by reference in) these Terms and that any misrepresentation by you is a violation of these Terms.\nIf Ethena BVI suspects or determines that you or any of your authorized users or customers, as applicable, have violated these Terms, including, but not limited to, attempting to transact or transacting with Blocked Addresses (as defined in Section 11) or attempting to engage or engaging in Restricted Activities (as defined in Section 16) or Prohibited Transactions (as defined in Section 17), then Ethena BVI may be forced to terminate your status as a Mint User and you may forfeit any assets otherwise eligible for redemption.\nNotwithstanding the foregoing, Ethena BVI may determine not to make USDe or the USDe Services, in whole or in part, available in every market, either in its sole discretion or due to legal or regulatory requirements, depending on your location. We may also, without liability to you or any third party, refuse to let you register as a Mint User.\nThe following only applies to Mint Users: Use of certain USDe Services may have further eligibility requirements that will need to be verified prior to you using such USDe Services, or from time to time in order to continue your use of the USDe Services, and may be subject to additional terms and conditions.\n5. Support\nPlease contact Support to report any violations of these Terms or to ask any questions regarding these Terms or the USDe Services, as applicable.\n6. Copies, Wrappers, and Forks Not Supported\nThe following applies to both Mint Users and Holding Users: As a result of the decentralized and open source nature of USDe it is possible that a party unaffiliated with Ethena BVI could create an alternative, equivalent version of USDe either on one of the USDe supported blockchains or on an unsupported blockchain (a “copy”) that operate independently from USDe. Similarly, it is possible that a party unaffiliated with Ethena BVI may create an asset and purport that such asset is collateralized by or otherwise incorporates USDe into its design (a “wrapper”). Ethena BVI supports only USDe and is under no obligation to support any copies of USDe or wrappers and assumes no responsibility for any value that might be lost as a result of this lack of support of copies of USDe. No such copy or wrapper should be considered approved, sold, distributed, or promoted by Ethena BVI unless explicitly stated.\nAs a result of the decentralized and open source nature of the blockchains on which USDe is supported, it is possible that a party unaffiliated with Ethena BVI could create an alternative version of the blockchain (a “fork”). Note that in the event of a fork of one of the USDe supported blockchains, Ethena BVI may be forced to suspend all activities relating to USDe (including tokenizing assets for USDe, redeeming USDe for supported assets, or sending and receiving USDe) for an extended period of time until Ethena BVI has determined in its sole discretion that such functionality can be restored (“Downtime”). This Downtime will likely occur immediately upon a “fork”, potentially with little to no warning, and during this period of Downtime you will not be able to conduct various activities involving USDe. In the event of a fork of one of the USDe supported blockchains, Ethena BVI shall, in its sole discretion, determine which fork it will support, if any.\n7. USDe Supported Blockchains and Smart Contract Modifications\nUSDe operates on USDe supported blockchains. Ethena BVI does not have any ability or obligation to prevent or mitigate attacks or resolve any other issues that might arise with any USDe supported blockchain. Any such attacks or delays on any USDe supported blockchain might materially delay or prevent you from sending or receiving USDe, and Ethena BVI shall bear no responsibility for any losses that result from such issues.\nNote that in certain circumstances, including, but not limited to, a copy or fork of a USDe supported blockchain or the identification of a security issue with a USDe supported blockchain, Ethena BVI may be forced to suspend all activities relating to USDe (including tokenizing assets for USDe, redeeming USDe for assets, or sending and receiving USDe) for an extended period of time until such Downtime is over and USDe Services can be restored. This Downtime will likely occur immediately upon a copy or fork of any USDe supported blockchain, potentially with little to no warning, and during this period of Downtime you will not be able to conduct various activities involving USDe.\nEthena BVI reserves the right to migrate USDe to another blockchain or protocol in the future in its reasonable discretion. Upon Ethena BVI’s request, you agree to take any and all actions reasonably necessary to effectuate the migration of your USDe to another blockchain or protocol identified by Ethena BVI. Ethena BVI will not be responsible or liable for any damages, losses, costs, fines, penalties or expenses of whatever nature, whether or not reasonably foreseeable by the parties, which you may suffer, sustain or incur, arising out of or relating to your failure to effectuate such migration of your USDe to another blockchain or protocol identified by Ethena BVI.\n8. Privacy\nWe are committed to protecting your personal information and helping you understand exactly how your personal information is being used. You should carefully read the Ethena BVI Privacy Policy, as it provides details on how your personal information is collected, stored, protected, and used.\n9. Communications\nBy entering into these Terms, you agree to receive electronic communications and notifications.\nThese Terms are provided to you and communicated in English. We will also communicate with you in English for all matters related to USDe and your use of USDe Services. Where we have provided you with a translation of the English language version of these Terms, you agree that such translation is provided for your convenience only and that the English language version of these Terms govern your holding and use of USDe, and the USDe Services, as applicable.\n10. Limited License; IP Rights\nThe following only applies to Mint Users: We grant you a limited, non-exclusive, non-sublicensable, and non-transferable license, subject to the terms and conditions of these Terms, to access and use the USDe Services solely for approved purposes as determined by Ethena BVI. Any other use of the USDe Services is expressly prohibited. Ethena BVI and its licensors reserve all rights in the USDe Services and you agree that these Terms does not grant you any rights in or licenses to the USDe Services except for the limited license set forth above. Except as expressly authorized by Ethena BVI, you agree not to modify, reverse engineer, copy, frame, scrape, rent, lease, loan, sell, distribute, or create derivative works based on the USDe Services, in whole or in part. If you violate any portion of these Terms, your permission to access and use the USDe Services may be terminated pursuant to these Terms.\n\"ethena.fi\", \"Ethena BVI\", and all logos related to the USDe Services are either copyrights, trademarks, or registered marks of Ethena BVI or its licensors. Whether or not you are a Mint User, you may not copy, imitate, or use them without Ethena BVI's prior written consent. All right, title, and interest in and to the Ethena BVI website, any content thereon, the USDe Services, and all technology and any content created or derived from any of the foregoing is the exclusive property of Ethena BVI and its licensors.\n11. Risk Factors & Disclosures\nThe following list of risks associated with USDe and the USDe Services is not exhaustive.\nNo guarantee of price stability on Third Party Platforms\nEthena BVI does not guarantee that the value of one (1) USDe will always or ever equal 1 USD ($1) on any platform. Due to a variety of factors, the value of USDe on third-party platforms such as cryptocurrency exchange platforms could fluctuate above or below 1 USD ($1), and the risk factors highlighted at docs.ethena.fi (as well as presently unknown risk factors) may result in the USDe Reserves falling to less than 1 USD ($1) of notional value per USDe in circulation. Ethena BVI cannot control how third parties quote or value USDe, and Ethena BVI is not responsible for any losses or other issues that may result from fluctuations in the value of USDe.\nThird-parties\nEthena BVI does not control or endorse any products, services, or platforms offered by third parties using the USDe Services or supporting USDe. Third parties may elect to support USDe on their platforms without any authorization or approval by Ethena BVI. The availability of USDe on any third-party platform does not imply that such services are valid, legal, stable, or otherwise appropriate.\nEthena BVI is not liable for any losses, issues, or consequences that may arise from third-party transactions or the use of USDe on third-party platforms, including, but not limited to, (i) Failure to comply with applicable laws and regulations, including illegal transactions;(ii) The quality, delivery, or satisfaction of products and services facilitated by USDe Services; (iii) Technical errors, loss of access, or inability to recover USDe resulting from the use of third-party platforms.\nYou accept all consequences of sending USDe to third-party platforms or addresses, including the risk of loss or failure to recover your USDe. For the avoidance of doubt, Ethena BVI has no obligation to track, verify, or determine the provenance of USDe balances or transactions involving third-party platforms.\nYou accept all consequences of sending USDe\nUSDe transactions are not reversible. Once you send USDe to an address, you accept the risk that you may lose access to, and any claim on, that USDe indefinitely or permanently. For example, (i) an address may have been entered incorrectly and the true owner of the address may never be discovered, (ii) you may not have (or subsequently lose) the private key associated with such address, (iii) an address may belong to an entity that will not return the USDe, or (iv) an address belongs to an entity that may return the USDe but first requires action on your part, such as verification of your identity. For the avoidance of doubt, nothing in these Terms is intended to obligate Ethena BVI to track, verify or determine the provenance of USDe balances for Users, including any form of security interests claimed thereon.\nBlocked Addresses & Forfeited Funds\nEthena BVI reserves the right to “block” certain USDe addresses of Mint Users that it determines, in its sole discretion, may be associated with illegal activity or activity that otherwise violates these Terms (“Blocked Addresses”). In certain circumstances, Ethena BVI may deem it necessary to report such suspected illegal activity to applicable law enforcement agencies and you may forfeit any rights associated with your USDe, including the ability to redeem USDe for any permitted assets. Ethena BVI may also be required to surrender associated assets held in the USDe Reserve in the event it receives a legal order from a valid government authority requiring it to do so.\nSoftware protocols and operational challenges\nYou are aware of and accept the risk of operational challenges. Ethena BVI may experience sophisticated cyber-attacks, unexpected surges in activity or other operational or technical difficulties that may cause interruptions to the USDe Services. You understand that the USDe Services may experience operational issues that lead to delays, including delays in redeeming USDe. You agree to accept the risk of transaction failure resulting from unanticipated or heightened technical difficulties, including those resulting from sophisticated attacks. You agree not to hold Ethena BVI accountable for any related losses.\nCompliance\nYou are responsible for complying with applicable law. You agree that Ethena BVI is not responsible for determining whether or which laws may apply to your transactions, including tax laws. You are solely responsible for reporting and paying any taxes arising from your use of USDe or the USDe Services, including any accurate reporting of the tax or legal status of USDe in your jurisdiction.\nLegal treatment of USDe transfers\nThe regulatory status of USDe and blockchain technology is unclear or unsettled in many jurisdictions. It is difficult to predict how or whether regulatory agencies may apply existing regulation with respect to USDe, blockchain technology and its applications. Accordingly, it is not possible to determine whether a USDe transfer would be recognized under applicable law by a court or regulator.\nLegislative and regulatory changes\nLegislative and regulatory changes or actions at the international level may adversely affect the tokenization of assets into USDe, and the use, transfer, redemption and/or value of USDe.\nNo deposit insurance\nUSDe held in your wallet is not subject to deposit insurance protection, including, but not limited to, (i) where your country of residence is the United States, the Federal Deposit Insurance Corporation (FDIC) insurance or Securities Investor Protection Corporation protections (SIPC); or (ii) where your country of residence is outside of the United States, the United Kingdom Financial Services Compensation Scheme (FSCS) or equivalent scheme in your country of residence.\nClaim on funds\nOnly Mint Users can redeem USDe directly with Ethena BVI. For Mint Users, your ability to redeem with us for each USDe is conditional on (i) your possession of a corresponding amount of USDe associated with a Mint User, (ii) no violation of these Terms or your USDe Mint User Agreement, and (iii) no action, pending or otherwise, by a regulator, law enforcement or a court of competent jurisdiction that would restrict redemption.\nSending USDe to another address automatically transfers and assigns to that Holding User, and any subsequent Holding User, the right to redeem USDe with us so long as the Holding User is eligible to, and does, register as a Mint User (and thereby becomes a Mint User).\nEncumbrances\nDepending on the actions of the owners of USDe addresses before your receipt of USDe from another USDe address, it is possible that the transfer of USDe between USDe addresses could result in the USDe in your whitelisted wallet becoming subject to a lien or other form of security interest before redemption.\nOn-chain transactions irreversible\nWhen USDe is sent to a third-party USDe address, such transaction is completed on USDe supported blockchains. This means that such a transaction is irreversible and Ethena BVI does not have the ability to reverse or recall any transaction once initiated. You bear all responsibility for any losses that might be incurred as a result of sending USDe to an incorrect or unintended USDe address.\nAffiliate Activities\nYou understand and agree that individuals or entities affiliated with Ethena BVI may hold, purchase, sell, or otherwise engage in transactions using or involving USDe. You further understand and agree that such persons may engage in this activity for any reason, including but not limited to engaging in commercial transactions, promoting transaction activity that utilizes USDe, or otherwise supporting the use or adoption of USDe. This activity may involve selling USDe to other entities for provision to their end users. You understand and agree that no individual or entity, whether affiliated with Ethena BVI or otherwise, is under any obligation to engage in these activities, and they may be discontinued at any time.\n12. Fees; Authorization\nThe following only applies to Mint Users: Except as disclosed to you prior to completing a transaction as a Mint User, Ethena BVI will not charge you any fees for tokenizing assets for USDe, or receiving USDe. Any cost of executing a mint or redemption transaction is a cost reimbursement to cover friction such as blockchain gas fees or execution fees paid by Ethena BVI.\n13. Currency Conversion\nThe following only applies to Mint Users: All tokenizations of assets will be credited in USDe to your whitelisted wallet(s) based on a rate of one (1) USDe per 1 USD ($1) of notional value (measured in stablecoin value, i.e., 1 USDC, 1 USDT, or 1 USDtb, as the case may be, depending on the asset exchanged to mint USDe), less applicable fees and transaction costs associated with the transaction, including, for the avoidance of doubt, fees paid associated with the applicable blockchain consensus mechanism. Such value shall be calculated by Ethena BVI based on the asset in its sole discretion, with any transaction fees associated with the blockchain consensus mechanism determined by requirements of the underlying blockchain at the time the transaction is submitted by the Mint User.\n14. Right to Change/Remove Features or Suspend/Delay Transactions\nThe following only applies to Mint Users: We reserve the right to (i) change, suspend, or discontinue any aspect of the USDe Services at any time, including hours of operation or availability of any feature, without notice and without liability and (ii) decline to process any issuance or redemption without prior notice and may limit or suspend your use of one or more USDe Services at any time, in our sole discretion. Our rights under this paragraph are subject to our obligations under applicable law and licenses, including but not limited to our reasonable suspicion of inappropriate or illegal conduct. Suspension of your use of any of the USDe Services will not affect your rights and obligations pursuant to these Terms. We may, in our sole discretion, delay issuances or redemptions if we reasonably believe the transaction is suspicious, may involve fraud or misconduct, violates applicable laws, or violates the terms of these Terms.\n15. Transactions Irreversible\nThe following only applies to Mint Users: Once a transaction has been initiated, it cannot be reversed, as further described in Section 11 above and pursuant to the underlying blockchain consensus mechanism. Except as set forth in these Terms, all transactions processed through the USDe Services are nonrefundable.\n16. Restricted Activities\nIn connection with your holding or use of USDe, or the USDe Services (as applicable), you hereby agree that you will not:\n\nviolate (or assist any other party in violating) any applicable law, statute, ordinance, or regulation;\n\nintentionally try to defraud (or assist in the defrauding of) Ethena BVI or other Mint Users or Holding Users;\n\nprovide false, inaccurate, or misleading information;\n\ntake any action that interferes with, intercepts, or expropriates any system, data, or information;\n\npartake in any transaction involving the proceeds of illegal activity;\n\ntransmit or upload any virus, worm, or other malicious software or program;\n\nattempt to gain unauthorized access to the Ethena BVI website, or any related networks or systems;\n\nuse the USDe Services on behalf of any third party or otherwise act as an intermediary between Ethena BVI and any third parties;\n\ncollect any information from other Mint Users or Holding Users, including, without limitation, email addresses;\n\ndefame, harass, or violate the privacy or intellectual property rights of Ethena BVI or any Holding Users or Mint Users; or\n\nupload, display or transmit any messages, photos, videos or other media that contain illegal goods, violent, obscene or copyrighted images or materials (such activities, “Restricted Activities”).\n\n17. Prohibited Transactions\nUsing USDe or the USDe Services for transactions related to the following is prohibited, and Ethena BVI reserves the right to monitor and, if appropriate, block or otherwise prevent transactions that relate to:\n\nany Restricted Persons;\n\nweapons of any kind, including but not limited to firearms, ammunition, knives, explosives, or related accessories;\n\ncontrolled substances, including but not limited to narcotics, prescription drugs, steroids, or related paraphernalia or accessories, unless licensed and authorized by the jurisdiction in which the User is based as well as by the jurisdiction in which the transaction takes place;\n\ngambling activities including but not limited to sports betting, casino games, horse racing, dog racing, games that may be classified as gambling (i.e. poker), or other activities that facilitate any of the foregoing, unless licensed and authorized by the jurisdiction in which the User is based as well as by the jurisdiction in which the transaction takes place;\n\nmoney-laundering or terrorist financing;\n\nany sort of Ponzi scheme, pyramid scheme, or multi-level marketing program;\n\ngoods or services that infringe or violate any copyright, trademark, or proprietary rights under the laws of any jurisdiction;\n\ncredit repair services, or other services that may present consumer protection risks;\n\ncourt ordered payments, structured settlements, tax payments, or tax settlements;\n\nany unlicensed money transmitter activity;\n\nlayaway systems, or annuities;\n\ncounterfeit goods, including but not limited to fake or “novelty” IDs;\n\nwash trading, front-running, insider trading, market manipulation or other forms of market-based fraud or deceit;\n\npurchasing goods of any type from “Darknet” markets, or any other service or website that acts as a marketplace for illegal goods (even though such marketplace might also sell legal goods); or\n\nany other matters, goods, or services that from time to time we communicate to you that are unacceptable and which, for example, may be restricted by our and your bank or payment partners (such transactions, “Prohibited Transactions”).\n\nIn the event that Ethena BVI learns you are making any such Prohibited Transactions, Ethena BVI will consider you to be a violation of these Terms and may also suspend or terminate your status as a Mint User.\n18. Taxes\nThe following only applies to Mint Users: Ethena BVI will maintain a record of your transaction history pursuant to the terms of the USDe Mint User Agreement. This transaction history will include all transactions you complete with Ethena BVI including tokenizing assets for USDe and redeeming USDe for assets.\n19. Indemnification; Release\nThe following only applies to Mint Users: Section 22 of the USDe Mint User Agreement is hereby incorporated into these Terms by reference and shall apply in all respects to these Terms and your use of USDe Services and our products and services as contemplated herein.\nThe following only applies to Holding Users: You agree to indemnify and hold Ethena BVI, its affiliates, and service providers, and each of their officers, directors, agents, joint venturers, employees, and representatives harmless from any claim or demand (including attorneys’ fees and any losses, fines, fees or penalties imposed by any regulatory authority) arising out of your breach of these Terms, your violation of any law or regulation or your holding or use of USDe.\nFor the purpose of this Section 19, the term “losses” means all net costs reasonably incurred by us or the other persons referred to in this Section which are the result of the matters set out in this Section 19 and which may relate to any claims, demands, causes of action, debt, cost, expense or other liability, including reasonable legal fees (without duplication).\nIf you have a dispute with one or more Mint Users, Holding Users or third parties, you release Ethena BVI (and its affiliates and service providers, and each of their officers, directors, agents, joint ventures, employees and representatives) from all claims, demands, and damages (actual and consequential) of every kind and nature arising out of or in any way connected with such disputes.\n20. Limitation of Liability; No Warranty\nThe following only applies to Mint Users: Section 23 of the USDe Mint User Agreement is hereby incorporated into these Terms by reference and shall apply in all respects to these Terms and your use of USDe Services and our products and services as contemplated herein.\nThe following only applies to Holding Users: YOU EXPRESSLY UNDERSTAND AND AGREE THAT ETHENA BVI AND OUR AFFILIATES AND SERVICE PROVIDERS, AND THEIR RESPECTIVE OFFICERS, DIRECTORS, AGENTS, JOINT VENTURERS, EMPLOYEES, AND REPRESENTATIVES WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY DAMAGES, OR DAMAGES FOR LOSS OF PROFITS INCLUDING BUT NOT LIMITED TO, DAMAGES FOR LOSS OF GOODWILL, USE, DATA, OR OTHER INTANGIBLE LOSSES (EVEN IF ETHENA BVI HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES), WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY, OR OTHERWISE, RESULTING FROM: (I) THE USE OR THE INABILITY TO HOLD OR USE USDe; (II) THE COST OF PROCUREMENT OF SUBSTITUTE GOODS AND SERVICES RESULTING FROM ANY GOODS, DATA, INFORMATION, OR SERVICES PURCHASED OR OBTAINED OR MESSAGES RECEIVED OR TRANSACTIONS ENTERED INTO INVOLVING USDe; (III) UNAUTHORIZED ACCESS TO OR ALTERATION OF YOUR TRANSMISSIONS OR DATA; OR (IV) ANY OTHER MATTER INVOLVING USDe.\nSOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF CERTAIN WARRANTIES OR THE LIMITATION OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES. ACCORDINGLY, SOME OF THE LIMITATIONS SET FORTH ABOVE MAY NOT APPLY TO YOU. IF YOU ARE DISSATISFIED WITH USDe, YOUR SOLE AND EXCLUSIVE REMEDY IS TO DISCONTINUE HOLDING AND USE OF USDe.\nUSDe IS PROVIDED \"AS IS\" AND WITHOUT ANY REPRESENTATION OR WARRANTY, WHETHER EXPRESS, IMPLIED OR STATUTORY. ETHENA BVI, OUR AFFILIATES, AND OUR RESPECTIVE OFFICERS, DIRECTORS, AGENTS, JOINT VENTURERS,EMPLOYEES, AND SUPPLIERS SPECIFICALLY DISCLAIM ANY IMPLIED WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT. ETHENA BVI MAKES NO WARRANTY THAT (I) USDeWILL MEET YOUR REQUIREMENTS, (II) USDe WILL BE UNINTERRUPTED, TIMELY, SECURE, OR ERROR-FREE, OR (III) THE QUALITY OF ANY PRODUCTS, SERVICES, INFORMATION, OR OTHER MATERIAL PURCHASED OR OBTAINED BY YOU WILL MEET YOUR EXPECTATIONS.\n21. Force Majeure\nEthena BVI shall have no liability for any failure or delay resulting from any condition beyond our reasonable control, including but not limited to governmental action or acts of terrorism, earthquake, fire, flood, or other acts of God, labor conditions, power failures, equipment failures, and Internet disturbances.\n22. Amendments\nEthena BVI may amend any portion of these Terms at any time by posting the revised version of these Terms with an updated revision date. The changes will become effective, and shall be deemed accepted by you, the first time you access or use USDe or the USDe Services after the initial posting of the revised Terms and shall apply on a going-forward basis with respect to transactions initiated after the posting date. In the event that you do not agree with any such modification, your sole and exclusive remedy is to terminate your use of the USDe Services and terminate your status as a Mint User (if any). You agree that we shall not be liable to you or any third party as a result of any losses suffered by any modification or amendment of these Terms.\nIf the revised Terms include a material change, we will provide you with prior notice via our website and/or email before the material change becomes effective. For this purpose a “material change” means a significant change other than changes that (i) are to your benefit, (ii) are required to be made to comply with applicable laws and/or regulations or as otherwise required by one of our regulators, (iii) relates to a new product or service made available to you, or (iv) otherwise clarifies an existing term.\n23. Assignment and Third-Party Holders\nYou may not transfer or assign these Terms or any rights or obligations hereunder, by operation of law or otherwise and any such attempted assignment shall be void, subject to the following exception. Sending USDe to an address will automatically transfer and assign to that Holder, and any subsequent Holder, the right to redeem USDe for USD so long as the Holder is eligible to, and does, register as a Mint User.\nEach Holding User is subject to all terms of these Terms as if a user including, but not limited to, the requirements to not transact with Blocked Addresses and not engage in Restricted Activities or Prohibited Transactions.\nWe reserve the right to freely assign these Terms and the rights and obligations of these Terms to any third party at any time without notice or consent. If you object to such transfer or assignment, you may stop holding and using USDe; further if you are a Mint User, you may also stop using our USDe Services, and terminate these Terms by contacting Support and asking us to terminate your status as a Mint User.\n24. Survival\nUpon termination of these Terms (and termination of your status as a Mint User, if you are a Mint User), all rights and obligations of the parties that by their nature are continuing will survive such termination.\n25. Website; Third Party Content\nEthena BVI strives to provide accurate and reliable information and content on the Ethena BVI website, but such information may not always be correct, complete, or up to date. Ethena BVI will update the information on the Ethena BVI website as necessary to provide you with the most up to date information, but you should always independently verify such information. The Ethena BVI website may also contain links to third-party websites, applications, events or other materials (“Third Party Content”). Such information is provided for your convenience and links or references to Third Party Content do not constitute an endorsement by Ethena BVI of any products or services. Ethena BVI shall have no liability for any losses incurred as a result of actions taken in reliance on the information contained on the Ethena BVI website or in any Third Party Content.\n26. Governing Law; Venue\nThe laws of the British Virgin Islands shall govern these Terms. The courts of the British Virgin Islands shall have exclusive jurisdiction to settle any dispute arising out of, or connected with, these Terms.\n27. Entire Agreement\nThe following applies to both Mint Users and Holding Users: The failure of Ethena BVI to exercise or enforce any right or provision of these Terms shall not constitute a waiver of such right or provision. If any provision of these Terms shall be adjudged by any court of competent jurisdiction to be unenforceable or invalid, that provision shall be limited or eliminated to the minimum extent necessary so that these Terms shall otherwise remain in full force and effect and remain enforceable between the parties, except as specified in Section 27. Furthermore, if any portion of these Terms, whether in whole, or in part, shall be adjudged by any court of competent jurisdiction to be unenforceable or invalid against certain persons or categories of persons that are purportedly bound by these Terms, such portion of these Terms shall otherwise remain in full force and effect and remain enforceable as to any other persons bound by these terms. The headings and explanatory text are for reference purposes only and in no way define, limit, construe, or describe the scope or extent of such section. These Terms, the USDe Mint User Agreement, the General Terms of Service, and Ethena BVI’s policies governing the holding or use of USDe, the use of the USDe Services referenced herein, and the Privacy Policy t constitute the entire agreement between you and Ethena BVI with respect to the holding or use of USDe, and the use of the USDe Services. These Terms are not intended and shall not be construed to create any rights or remedies in any parties other than you and Ethena BVI and other Ethena BVI affiliates which each shall be a third-party beneficiary of these Terms, and no other person shall assert any rights as a third-party beneficiary hereunder.\nThe following only applies to Mint Users: Notwithstanding anything to the contrary set forth in these Terms or otherwise, in the event of a conflict between any term set forth herein and any term set forth in the USDe Mint User Agreement (i) in connection with any USDe transaction, the terms of these Terms shall control, and (ii) in respect of any other Digital Currency transaction, the terms of the USDe Mint User Agreement shall control.\n28. E-Sign Consent\nPlease be aware that your consent to the electronic delivery of disclosures is required to use any of the Services (as defined in the USDe Mint User Agreement). If you are unable or unwilling to provide such consent, you will not be able to become a Mint User. Once you are a Mint User you can rescind your consent to electronic delivery of disclosures at any time and receive paper communications as set forth below.\nThis E-Sign Consent applies to any and all communications and/or disclosures that Ethena BVI is legally required to provide to you in writing in connection with your status as a Mint User and any related products and services (“Communications”). This E-Sign Consent supplements and is to be construed in accordance with the terms and conditions contained in the USDe Mint User Agreement.\nWhen you use the Services, you agree that we may provide you with any Communications in electronic format, and that we may discontinue sending paper Communications to you, unless and until you withdraw your consent as described below. Your consent to receive electronic communications and transactions includes, but is not limited to:\n\nLegal and regulatory disclosures and communications associated with your registration or the Services;\n\nNotices or amendments relating to the USDe Mint, User Agreement, the Privacy Policy, the Cookie Policy or this E-Sign Consent;\n\nCommunications regarding any transactions; and\n\nResponses to claims filed in connection with your relationships with Ethena BVI as a Mint User.\n\nMethods of Communication\nAll Communications that we provide to you in electronic form will be provided by e-mail, by posting to the Ethena BVI website (USDe.money), or through other electronic communication such as mobile push notification or text message.\nHardware Requirements\nIn order to access, view, and retain electronic Communications that we make available to you, you must have the following software and hardware:\n\nA valid e-mail address.\n\nA computer or other device capable of accessing the internet with a current web browser that supports at least 128 bit encryption, such as Google Chrome, Apple® Safari, Microsoft® Internet Explorer, or Mozilla Firefox®. The browser must have cookies enabled.\n\nThe computer must also have a printer or disk drive to print or retain copies of this E-Sign Consent and any Communications.\n\nUpdating your Information\nIt is your responsibility to provide us with a true, accurate and complete e-mail address, your contact information, and other information related to this E-Sign Consent and your registration, keep such information up to date.\nWithdrawing Consent\nYou may withdraw your consent to receive electronic Communications at any time by sending us a written request by email. You understand that any withdrawal of your consent to receive electronic Communications will be effective only after Ethena BVI has had a reasonable period of time to process your withdrawal. You understand that withdrawing your consent to electronic Communications will likely result in the termination of your status as a Mint User.\nCommunications in Writing\nAll electronic Communications from us to you will be considered \"in writing\" and shall have the same meaning and effect as a paper Communication. You should print or download for your records a copy of this E-Sign Consent and any other Communication that is important to you. You acknowledge and agree that Communications are considered received by you within 24 hours of the time posted to the Ethena BVI website (USDe.money), or within 24 hours of the time emailed to you unless Ethena BVI receives notice that the email was not delivered.\nGeneral\nEthena BVI reserves the right, in our sole discretion, to cancel this electronic Communication service, or to terminate or change the terms and conditions on which Ethena BVI provides electronic Communications. Ethena BVI will provide you with notice of any such termination or change as required by law.\n\nLast updated 9 months ago\nWas this helpful?","tokens":11309,"crawled_at":1791195966125}
+{"id":10581,"url":"https://docs.sui.io/develop/publish-upgrade-packages","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Packages | Sui Documentation","text":"A Move packagePackageSmart contracts on Sui. on Sui includes one or more modulesModuleA component of a Move package that defines interaction with on-chain objects. that define the package's interaction with onchain objects. You develop the logic for those modules in MoveMoveAn open source programming language used for all activity on Sui., compile them into an objectObjectThe basic unit of storage on Sui., and publish that package object to a Sui network.\n\nPublish workflow​\n\nPublishing a package follows this sequence:\n\nWrite and test your Move code: Create a Move project with sui move new PROJECT_NAME, write your modules, and run tests with sui move test.\n\nConfigure your manifest: Verify that your Move.toml uses edition = \"2024\" and lists all dependencies. The Sui framework is resolved automatically and does not need an explicit entry in [dependencies]. See the Manifest Reference for the full syntax.\n\nBuild the package: Run sui move build to compile. Fix any errors before publishing.\n\nPublish to the network: Run sui client publish from the package root. The command compiles, creates a package object onchain, and returns the package ID. You need sufficient gasGasThe computational cost of execution and object storage for a transaction. in your active addressAddressA unique, anonymous identity on a blockchain network.. Use --dry-run to estimate gas cost before publishing.\n\nVerify publication: Use sui client verify-source from the package directory to confirm that the onchain bytecode matches your local source.\n\ncaution\nPublishing is irreversible. Once you publish a package, you cannot delete it from the network. You can upgrade the package if you retain the UpgradeCap, but the original version remains onchain. Store your UpgradeCap in a multisigMultisigMulti-signature transactions that require multiple keys for authorization. address or apply a custom upgrade policy for production packages (Security Best Practices).\n\nUpgrade packages​\n\nAfter publishing, you can deploy new versions of your package using sui client upgrade. Upgrades require the UpgradeCap object that was created during the initial publish. The upgrade policy determines which types of changes are allowed. See the upgrade-specific pages below for details on upgrade policies, compatibility rules, and multisig signing workflows.\n\nNetwork considerations​\n\nTestnetTestnetStaging network for testing changes before production deployment. and DevnetDevnetFor developing and testing new features.: Use these for development and testing. Testnet and Devnet addresses are separate from MainnetMainnetProduction network for live transactions and real-value assets., and packages published on one network do not exist on another.\n\nMainnet: Production deployments. Verify your tests, dependencies, and gas budget before publishing. Use --dry-run to simulate the transactionTransactionA number of commands that execute on inputs to define the result of the transaction. without committing it.\n\nPublishing\nCompile and publish a Move package to a Sui network using the Sui CLI, estimate gas costs with a dry run, verify onchain bytecode, and serialize publish transactions for multisig signing.\n→\nUpgrading\nUpgrade a published Move package on Sui using the Sui CLI, understand layout-compatibility requirements, manage UpgradeCap and UpgradeTicket, and apply custom upgrade policies to control what changes are permitted.\n→\nCustom Upgrade Policies\nCustom upgrade policies are used to upgrade live packages while addressing the security risks of single key ownership upgrades.\n→\nVersioning\nUnderstand how Sui assigns and increments package versions on publish and upgrade, how framework packages preserve their IDs across upgrades, and what package manifest version fields actually control.\n→\nDeploy with GitHub Actions\nBuild a production-safe CI/CD pipeline that tests every pull request, automates Testnet publishing, and gates Mainnet publishing and upgrades behind manual approval.\n→\n\nPublish workflow\nUpgrade packages\nNetwork considerations\n\nWas this page helpful?","tokens":1014,"crawled_at":1791195969307}
+{"id":10582,"url":"https://www.metaplex.com/docs/smart-contracts/bubblegum-v2/mint-cnfts","domain":"www.metaplex.com","chapter":"docs","title":"Minting Compressed NFTs - Bubblegum V2 - Metaplex","text":"Summary\nMinting compressed NFTs adds new cNFTs to a Bubblegum Tree using the mintV2 instruction. This page covers minting with and without MPL-Core collections, and retrieving the asset ID from mint transactions.\nMint cNFTs to a Bubblegum Tree using the mintV2 instruction\nMint directly into an MPL-Core collection with the BubblegumV2 plugin\nRetrieve the asset ID and leaf schema from the mint transaction\nConfigure metadata including name, URI, creators, and royalties\nInherit seller fee basis points from an MPL-Core collection's Royalties plugin\nIn the previous page, we saw that we need a Bubblegum Tree to mint Compressed NFTs, and we saw how to create one. Now, let's see how to mint compressed NFTs from a given Bubblegum Tree.\nThe Bubblegum program offers multiple minting instructions for the different leaf schema versions. Bubblegum V2 introduces a new minting instruction called mintV2 that is used to mint Compressed NFTs either to a given Collection or without a Collection.\nMinting without a Collection\nThe Bubblegum program provides the mintV2 instruction that enables us to mint Compressed NFTs from a Bubblegum Tree. If the Bubblegum Tree is public, anyone will be able to use this instruction. Otherwise, only the Tree Creator or the Tree Delegate will be able to do so.\nThe main parameters of the mintV2 instruction are:\nMerkle Tree: The Merkle Tree address from which the Compressed NFT will be minted.\nTree Creator Or Delegate: The authority allowed to mint from the Bubblegum Tree — this can either be the creator or the delegate of the tree. This authority must sign the transaction. In the case of a public tree, this parameter can be any authority, but must still be a signer.\nLeaf Owner: The owner of the Compressed NFT that will be minted. It defaults to the payer of the transaction.\nLeaf Delegate: A delegate authority allowed to manage the minted cNFT, if any. Otherwise, it is set to the Leaf Owner.\nCollection Authority: The authority allowed to manage the given Collection.\nCore Collection: The MPL-Core Collection NFT to which the Compressed NFT will be added.\nMetadata: The metadata of the Compressed NFT that will be minted. It contains information such as the Name of the NFT, its URI, its Collection, its Creators, etc. In Bubblegum V2 the metadata is using MetadataArgsV2 which excludes unneeded fields like uses and the verified flag for the collection.\nMint a Compressed NFT without a Collection\n\nimport { none } from '@metaplex-foundation/umi';\n\nimport { mintV2 } from '@metaplex-foundation/mpl-bubblegum';\n\nawait mintV2(umi, {\n\nleafOwner: umi.identity.publicKey,\n\nmerkleTree: merkleTree.publicKey,\n\nmetadata: {\n\nname: 'My NFT',\n\nuri: 'https://example.com/my-nft.json',\n\nsellerFeeBasisPoints: 550,\n\ncollection: none(),\n\ncreators: [],\n\n},\n\n}).sendAndConfirm(umi);\n\nMinting to a Collection\nWhile it is possible to set and verify a Collection for a Compressed NFT after it is minted, Bubblegum V2 allows you to mint a Compressed NFT directly to a given Collection. Bubblegum V2 uses MPL-Core Collections to group the compressed NFTs. The same mintV2 instruction is used for that. In addition to the parameters described above, you need to pass in the core collection and sign as collection authority or delegate:\nCore Collection: The mint address passed to the coreCollection parameter, pointing to the MPL-Core Collection NFT…\nCollection Authority: The authority allowed to manage the given Collection NFT. This can either be the update authority of the Collection NFT or a delegated collection authority. This authority must sign the transaction regardless of whether the Bubblegum Tree is public or not.\nNote that the Metadata parameter must contain the Collection Public Key.\nMint a Compressed NFT to a Collection\n\nimport { some } from '@metaplex-foundation/umi';\n\nimport { mintV2 } from '@metaplex-foundation/mpl-bubblegum';\n\nawait mintV2(umi, {\n\ncollectionAuthority: umi.identity,\n\nleafOwner: umi.identity.publicKey,\n\nmerkleTree: merkleTree.publicKey,\n\ncoreCollection: collectionSigner.publicKey,\n\nmetadata: {\n\nname: 'My NFT',\n\nuri: 'https://example.com/my-nft.json',\n\nsellerFeeBasisPoints: 550, // 5.5%\n\ncollection: some(collectionSigner.publicKey),\n\ncreators: [],\n\n},\n\n}).sendAndConfirm(umi);\n\nInheriting royalties from the collection\nWhen minting to an MPL-Core collection, you can store a sentinel seller fee basis points value on the leaf (65535, exported as SELLER_FEE_BASIS_POINTS_INHERIT / 0xffff) instead of copying the collection's royalty percentage into every cNFT. DAS puts the collection-resolved rate on royalty.basis_points / creators for display and the leaf sentinel on royalty.basis_points_raw / creators_raw (with royalty.inherited: true), while the on-chain leaf keeps the sentinel for hashing.\nClients that read DAS responses (wallets, marketplaces, indexers, and apps) should follow Reading Inherited Royalties.\nMarketplace / indexer compatibility\nUntil a marketplace's DAS provider supports inherited SFBP resolution, it may see creators: [] and basis_points: 65535 and skip royalty payouts. See the warning on Reading Inherited Royalties. For stronger guarantees, use collection Royalties plugin allow/deny lists so sales go through royalty-compliant venues.\n\nThe JavaScript SDK's mintV2 helper defaults to this behavior when coreCollection is provided and metadata.sellerFeeBasisPoints is omitted.\nRequirements:\nThe MPL-Core collection must have both the BubblegumV2 and Royalties plugins.\nmetadata.creators must be an empty array when using inherited seller fees. Creator splits come from the collection's Royalties plugin instead of leaf-level creators.\nInherited seller fees are only valid for cNFTs in a collection. Collectionless mints must use an explicit value between 0 and 10000.\n\n1import { createTreeV2, mintV2, mplBubblegum } from '@metaplex-foundation/mpl-bubblegum'\n\n2import { createCollection, mplCore, ruleSet } from '@metaplex-foundation/mpl-core'\n\n3import { generateSigner, some } from '@metaplex-foundation/umi'\n\n4import { createUmi } from '@metaplex-foundation/umi-bundle-defaults'\n\n5\n\n6const umi = createUmi('https://api.devnet.solana.com')\n\n7 .use(mplBubblegum())\n\n8 .use(mplCore())\n\n9\n\n10const merkleTree = generateSigner(umi)\n\n11const collectionSigner = generateSigner(umi)\n\n12\n\n13await createTreeV2(umi, {\n\n14 merkleTree,\n\n15 maxDepth: 5,\n\n16 maxBufferSize: 8,\n\n17}).sendAndConfirm(umi)\n\n18\n\n19// The collection must include BubblegumV2 and Royalties plugins.\n\n20await createCollection(umi, {\n\n21 collection: collectionSigner,\n\n22 name: 'My Collection',\n\n23 uri: 'https://example.com/collection.json',\n\n24 plugins: [\n\n25 { type: 'BubblegumV2' },\n\n26 {\n\n27 type: 'Royalties',\n\n28 basisPoints: 500, // 5%\n\n29 creators: [{ address: umi.identity.publicKey, percentage: 100 }],\n\n30 ruleSet: ruleSet('None'),\n\n31 },\n\n32 ],\n\n33}).sendAndConfirm(umi)\n\n34\n\n35// sellerFeeBasisPoints is omitted — the SDK sends the inherit sentinel (65535).\n\n36await mintV2(umi, {\n\n37 collectionAuthority: umi.identity,\n\n38 leafOwner: umi.identity.publicKey,\n\n39 merkleTree: merkleTree.publicKey,\n\n40 coreCollection: collectionSigner.publicKey,\n\n41 metadata: {\n\n42 name: 'My NFT',\n\n43 uri: 'https://example.com/my-nft.json',\n\n44 collection: some(collectionSigner.publicKey),\n\n45 creators: [], // must be empty when inheriting royalties\n\n46 },\n\n47}).sendAndConfirm(umi)\n\n48\n\n49// cNFT minted with SELLER_FEE_BASIS_POINTS_INHERIT (65535) on the leaf\n\nYou can still pass an explicit sellerFeeBasisPoints to override the collection default for a single mint.\nCollection removal\nA cNFT with inherited seller fees cannot be removed from its collection until the seller fee is updated to an explicit value. See Managing Collections and Updating Compressed NFTs.\n\nGet Asset ID and Leaf Schema from mint transaction\nYou can retrieve the leaf and determine the asset ID from the mintV2 transaction using the parseLeafFromMintV2Transaction helper. This function parses the Transaction, therefore you have to make sure that it has been finalized before calling parseLeafFromMintV2Transaction.\nTransaction finalization\nPlease make sure that the transaction has been finalized before calling parseLeafFromMintV2Transaction.\n\nGet leaf schema from mint transaction\n\nimport {\n\nmintV2,\n\nparseLeafFromMintV2Transaction,\n\n} from '@metaplex-foundation/mpl-bubblegum';\n\nconst { signature } = await mintV2(umi, {\n\n// ... see details above\n\n}).sendAndConfirm(umi);\n\nconst leaf = await parseLeafFromMintV2Transaction(umi, signature);\n\nconst assetId = leaf.id;\n\nNotes\nThe Bubblegum Tree must be created before minting. See Creating Trees.\nFor collection mints, the MPL-Core collection must have the BubblegumV2 plugin enabled.\nTo inherit royalties from a collection, the collection must also have the Royalties plugin and the leaf's creators array must be empty.\nThe collection authority must sign the transaction when minting to a collection, regardless of whether the tree is public or private.\nUse parseLeafFromMintV2Transaction only after the transaction is finalized, not just confirmed.\nFAQ\nHow do I mint a compressed NFT to a collection?\nUse the mintV2 instruction with the coreCollection parameter set to your MPL-Core collection address and provide the collectionAuthority signer. The collection must have the BubblegumV2 plugin enabled.\nHow do I get the asset ID after minting?\nUse the parseLeafFromMintV2Transaction helper after the transaction is finalized. It parses the transaction and returns the leaf schema including the asset ID via leaf.id.\nCan anyone mint from my tree?\nOnly if the tree was created with public: true. For private trees, only the Tree Creator or Tree Delegate can mint cNFTs.\nWhat metadata fields are required for minting?\nThe MetadataArgsV2 struct requires: name (string), uri (string pointing to JSON metadata), sellerFeeBasisPoints (0-10000, or omit when minting to a collection to inherit from its Royalties plugin), collection (public key or none), and creators (array of creator objects; must be empty when inheriting royalties).\nCan a cNFT inherit royalties from its MPL-Core collection?\nYes. When minting with coreCollection, omit metadata.sellerFeeBasisPoints and leave metadata.creators empty. The SDK stores SELLER_FEE_BASIS_POINTS_INHERIT (65535) on the leaf. The collection must have the Royalties plugin. See Inheriting royalties from the collection.\nGlossary\nTermDefinition\nmintV2\nThe Bubblegum V2 instruction for minting compressed NFTs, replacing the V1 mint instructions\n\nMetadataArgsV2\nThe metadata structure passed to mintV2, containing name, URI, royalties, collection, and creators\n\nSELLER_FEE_BASIS_POINTS_INHERIT\nSentinel value 65535 (0xffff) stored on-chain to indicate royalties are inherited from the MPL-Core collection\n\nCollection Authority\nThe signer authorized to manage the MPL-Core collection — required when minting to a collection\n\nBubblegumV2 Plugin\nAn MPL-Core collection plugin that enables Bubblegum V2 features (freeze, soulbound, royalties)\n\nAsset ID\nA PDA derived from the merkle tree address and leaf index, uniquely identifying a compressed NFT\n\nLeaf Schema\nThe data structure stored as a leaf in the merkle tree, containing the cNFT's hashed metadata and ownership info","tokens":2799,"crawled_at":1791195998121}
+{"id":10583,"url":"https://a16zcrypto.com/team/joshua-lu","domain":"a16zcrypto.com","chapter":"research","title":"Joshua Lu - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nJoshua Lu\n\nFeed\nFilter\n(1)\nclear filters\n\ncategory\nall categories\nannouncements & news\ncode & engineering\ncompany building\npolicy & regulation\nresearch\ntech trends\n\nformat\nall formats\narticles\nlisticles\npapers\npodcasts\nvideos\n\ntags\nrecommended tags\nAI & crypto\nJolt\nstablecoins\ntokens\nall tags\nall tags\nagentic commerce\nAI agents / agentic AI\nairdrops\nAMMs\nanatomy of a hack\nannouncements\nannual Big Ideas\napac\narts & culture\nauction design\nbanking\nBFT\nbitcoin\nblockchain\nbrand & marketing\nbusiness strategy\nchoosing infrastructure\nCLARITY Act\ncomment letters & amicus briefs\ncomms\ncommunity building\ncompensation\ncompliance & illicit finance\ncomposability\nconsensus\ncreator economy\ncrypto basics\nCrypto Startup Accelerator (CSX)\ncryptography\nCSX 2020\nCSX 2023\nCSX 2024 (London)\nCSX 2024 (NYC)\nCSX 2025 (SF)\ncustody\ncypherpunk\nDAGs\ndanksharding\nDAOs\ndata availability\ndata insights\ndebanking\ndecentralization\ndecentralization how-to\ndecentralized media & entertainment\nDeFi\nDePIN\nDeSci\ndesign & user experience\ndeveloper experience & tooling\nDUNA\neconomics\nEthereum\nFAQ\nFHE (fully homomorphic encryption)\nfield notes\nfinance\nFirst Principles series\nformal verification\nfoundations\nfounder stories\nFounders Summits\ngaming\ngas\nGenius Act\nglossaries & terminology\ngo-to-market\ngov\ngovernance\ngovernance best practices\ngovernment agencies\nguest posts\nHalmos\nhelios\nhiring & recruiting\nhistory\nhow innovation happens\nidentity & reputation\ninfrastructure\ninvestments\nIP\nlegal best practices\nlicensing\nlight clients\nlockups\nlongform\nlongreads\nLVR\nMachiavelli for DAOs series\nmachine learning\nmarketplaces\nmechanism design\nmental models & frameworks\nmetaverse\nmetrics & measures\nmev\nMPC (multi-party computation)\nmulti-client diversity\nnetwork effects\nnew year's resolutions\nnewsletters\nNFTs\noffline to online\nop-eds\nopen source\npartnerships & sales\nPCNs\npeople practices & HR\npermissionless\nperpetual futures\npitching investors\nplaybooks\npodcast\nprediction markets\npricing\nprivacy\nproduct-market fit\nprogramming\nprogressive decentralization\nproof of human\nproof of stake\nproof of work\nproposer-builder separation\nQ&As\nquantum computing & post-quantum crypto\nrandomness beacons\nregional innovation\nregulatory know-how\nregulatory updates\nrelease notes\nresearch\nrollups\nroundups\nroyalties\nrulemaking\nRWA tokenization\nscaling & throughput\nsecurity\nsecurity best practices\nslashing\nsmart contracts\nSNARKs\nsocial networks\nsolana\nSolidity\nstarter packs\nState of Crypto\nState of Crypto 2022\nState of Crypto 2023\nState of Crypto 2024\nstate of crypto 2025\ntalent\ntax policy\nTEEs (trusted execution environment)\nThe Merge series\ntoken business models\ntoken design\ntoken launch playbook\nTradFi\nUK\nVDFs\nvibecoding\nvideo\nVoices Onchain\nvoting\nVR\nwallets\nweb2 to web3\nwhat we're reading\nzero knowledge\nzero knowledge & succinct proof systems\n\nauthor\n(1) all authors\n@x0rart\n1337 Skulls Sers\na16z crypto\na16z crypto editorial\na16z crypto policy & regulatory teams\na16z crypto Regulatory Team\nAaditya Shidham\nAaron Levie\nAaron Phillips\nAaron Schnider\nAbby Green\nAbdou Ndiaye\nAbhi Shelat\nAbhiram Kothapalli\nAbigail Johnson\nAdam Alter\nAdam Back\nAdam Bry\nAdam Grant\nAdam Ludwin\nAdam Martin\nAdam Thierer\nAdam Zuckerman\nAdela Tomsejova\nAdena Friedman\nAdena Hefets\nAdeniyi Abiodun\nAdina Fischer\nAdrian Cockcroft\nAdrian Fenty\nAdrienne Mayor\nAgostino Capponi\nAiden Slavin\nAileen Lee\nAisha Stephenson\nAJ Shankar\nAlan Knott-Craig\nAlan Schaaf\nAlana Benton\nAlbert Tang\nAlec Nielsen\nAlec Ross\nAlejandro Flores\nAlex Constantinople\nAlex Honnold\nAlex Hutchinson\nAlex Immerman\nAlex Kreitz\nAlex Kroeger\nAlex Le\nAlex Masmej\nAlex Morcos\nAlex Price\nAlex Pruden\nAlex Rampell\nAlex Roetter\nAlex Solomon\nAlex Spector\nAlex Stamos\nAlex Tabarrok\nAlexander (Sasha) Spiegelman\nAlexander Chia\nAlexander Zoppa\nAlexandra Chang\nAlexandria Lafci\nAlexis Lakes\nAlexis Madrigal\nAlexis Ohanian\nAli Ghodsi\nAli Yahya\nAlicia Barone\nAlin Tomescu\nAlisha Litman\nAlison Mangiero\nAlison Martin\nAllison Pickens\nAlyssa Del Bene\nAlyssa Torres\nAmanda Cantor\nAmanda Cassatt\nAmanda Catherine\nAmanda Mulay\nAmanda Tuminelli\nAmanda Tyler\nAmelia Salyers\nAmie Tyrrel\nAmir Shevat\nAmira Yahyaoui\nAmy Abernethy\nAmy Berliner\nAmy Bohutinsky\nAmy Choice\nAmy Cray\nAmy Gill\nAmy Hoemeke\nAmy Kalokerinos\nAmy Robertson\nAna Mostarac\nAna Susi\nAnatoly Yakovenko\nAndie Taylor\nAndisheh Tahriri\nAndre Iguodala\nAndrea Clarke Hall\nAndrea Feinberg\nAndrea Rallo\nAndrea Simon\nAndrea Vinkler\nAndreas Papadimitropoulos, Jr\nAndreessen Horowitz\nAndrew Allen\nAndrew Chen\nAndrew F. Read\nAndrew Green\nAndrew Hall\nAndrew Lakis\nAndrew Lewis-Pye\nAndrew Lo\nAndrew Mason\nAndrew McAfee\nAndrew Milson\nAndrew Omori\nAndrew Radin\nAndrew Rubin\nAndrew Savage\nAndrew Smith\nAndrew Tretyakov\nAndy Beal\nAndy Coravos\nAndy Golden\nAndy Hill\nAndy Milenius\nAndy Rachleff\nAndy Tran\nAndy Walshe\nAneel Lakhani\nAngela Schenone\nAngela Strange\nAngela Tran Kingyens\nAngelica Gehr\nAniket Kate\nAnil Sethi\nAnish Acharya\nAnn Winblad\nAnna Berces\nAnna Jablonski\nAnna Semenova\nAnna Van Meurs\nAnnaLee Saxenian\nAnne Brandes\nAnne Lee Skates\nAnne Lewandowski\nAnne Mitchell\nAnne Yip\nAnnie Collins\nAnnie Duke\nAnthony Albanese\nAnthony Atala\nAnthony Foxx\nAnthony Lee Zhang\nAntonio Viggiano\nAntwone Stigall\nAnu Hariharan\nApril Roth\nAri Emanuel\nAri Juels\nArianna Huffington\nArianna Simpson\nArik Kershenbaum\nArmon Dadgar\nArnie Goldberg\nArsho Avetian\nArthur Brooks\nArun Sundararajan\nAsh Ashutosh\nAsha Christian\nAshley McCollum\nAshley Stern\nAshton Carter\nAtif Mian\nAtul Butte\nAubree Pelaez\nAubrey de Grey\nAugusto Marietti\nAurora Petracca\nAusten Allred\nAustin Guzman\nAustin Marchese\nAustin Wilson\nAva Iravani\nAvery Segal\nAvinash Solanky\nAviv Zohar\nAye Moah\nAzeem Azhar\nBailey Flanigan\nBailey Richardson\nBalaji Srinivasan\nBarry McCarthy\nBart Dessaint\nBeau Cronin\nBeau Woods\nBecky Pferdehirt\nBen Buckwalter\nBen Fielding\nBen Fisch\nBen Gardner\nBen Gomez\nBen Horowitz\nBen Kaufman\nBen Leventhal\nBen Lovell\nBen Napier\nBen Portney\nBen Rubin\nBen Scharfstein\nBen Schecter\nBen Silbermann\nBen Uretsky\nBen Wu\nBenedict Evans\nBenedikt Büenz\nBenjamin Ebner\nBenjamin Hindman\nBenjamin Wittes\nBenjamin Wu\nBennett Carroccio\nBenny Pinkas\nBernard J. Tyson\nBernard Tyson\nBeth Newman\nBethany Coates\nBharat Ramamurti\nBharath Ramsundar\nBill Carr\nBill Frist\nBill Hinman\nBill Janeway\nBill Krause\nBill Macaitis\nBlake Kim\nBlake Masters\nBlake Saari\nBlayne Donnell\nBob Iger\nBob Langer\nBob Moore\nBob Muglia\nBob Sutton\nBob Swan\nBob Tinker\nBob Wachter\nBobby Franklin\nBobby Green\nBobby Kotick\nBobby Wagner\nBoris Sofman\nBoris Wertz\nBrad Feld\nBrad Kern\nBrad Peterson\nBram Cohen\nBrandon Ballinger\nBrandon Barros\nBrandon Cherry\nBrandon Millman\nBrenda Kopf\nBrent McIntosh\nBrett Browman\nBrett Falk\nBrett Hagler\nBrewster Kahle\nBrian Armstrong\nBrian Balfour\nBrian Brooks\nBrian Crnkovich\nBrian Curran\nBrian Grazer\nBrian Koppelman\nBrian McCullough\nBrian Quintenz\nBrian Wilkins\nBridget McDowell\nBrittany Lucas\nBrittney Burrows\nBrooke Sheresky\nBruce Friedrich\nBryan Caplan\nBryan Chiang\nBryan Cox\nBryan Crowley\nBryan Faust\nBryan Houser\nBryan Kim\nBryan Pellegrino\nCaitlin Glazebrook\nCaitlin Johnston\nCaitlin Roberson\nCal Turner Jr.\nCaleb Christian\nCameron Schuler\nCamila De Souza\nCarine Carmy\nCarissa Bilinski\nCarl Agnelli\nCarl Eschenbach\nCarl Narcisse\nCarl Pope\nCarlos Araya\nCarolina Gonzalez\nCaroline Friedman\nCaroline Goggins\nCaroline Horn\nCaroline Moon\nCarolyn Bertozzi\nCarra Wu\nCasey Graul\nCasey Neistat\nCasey Winters\nCassady Churchill\nCassie Faerber\nCecilia Marshall\nCeia Font\nChad Rigetti\nChandra Krintz\nCharles Goetz\nCharles Hubbard\nCharles Koch\nCharlie Keinath\nCharlie Warzel\nChattry Meas\nChelsea Komlo\nChelsea Padilla\nCheng Li\nChris Bennett\nChris Best\nChris Burniske\nChris Curran\nChris DeWolfe\nChris Dixon\nChris Granger\nChris Hauth\nChris Lyons\nChris Messina\nChris Milk\nChris Power\nChris Santa Maria\nChris Wanstrath\nChristian Cachin\nChristian Catalini\nChristian Crowley\nChristian Seifert\nChristina Hampp\nChristina Lopes\nChristina Mercando\nChristina Xu\nChristina Zeidan\nChristine Darden\nChristine Perham\nChristopher Giancarlo\nChristopher Lee\nChristopher Mims\nChristopher Nguyen\nChristopher Rippingham\nChristopher Schroeder\nChristy Hubbard\nCiamac Moallemi\nCindi Zhang\nCindy Tenner\nClaire Austin\nClaire Cain Miller\nClaire Kart\nClaudia Picanco\nClay Shirky\nClayton Christensen\nClayton Gardner\nClifford Woolf\nClint Delapaz\nColin Bryar\nColin Rom\nCollin McCune\nConner Lyons Brown\nConnie Chan\nConnie Guglielmo\nConnor McCarthy\nConnor Moyles\nCorban Bell\nCorey Hawkins\nCorey Waller\nCourtney Dettlinger\nCraig Naylor\nCraig Walker\nCristina Cordova\nCurt Funderburk\nCuy Sheffield\nD'Arcy Coolican\nDaejun Park\nDaisy Linden\nDaisy Wolf\nDaljeet Virdi\nDalton Turay\nDan Berkenstock\nDan Boneh\nDan Frommer\nDan Primack\nDan Romero\nDan Shapero\nDan Siroker\nDan Stein\nDan Warmenhoven\nDan Wendlandt\nDaniel Chao\nDaniel Chen\nDanielle Andrzejewski\nDanielle Clark\nDanielle Looymans\nDanielle Lussier\nDanielle Morrill\nDanielle Shea\nDanny Shader\nDaphne Koller\nDapper Dan\nDaren Matsuoka\nDarin Malter\nDarshan Shankar\nDas Rush\nDave Jagoda\nDave King\nDave Touretzky\nDavid Banks\nDavid Belden\nDavid Damato\nDavid Deming\nDavid George\nDavid Haber\nDavid Hollestelle\nDavid Kerr\nDavid Lee\nDavid Mack\nDavid Madden\nDavid Marcus\nDavid Olson\nDavid Oyelowo\nDavid Pierce\nDavid Reich\nDavid Rumsey\nDavid Schweikert\nDavid Sinclair\nDavid Sverdlov\nDavid Tse\nDavid Ulevitch\nDavid Weiden\nDawn Lepore\nDawn Nott\nDeborah Embaie\nDeena Elitreby\nDeepak Maram\nDenis Nazarov\nDenis Young\nDenise Gonzalez\nDerek Dolin\nDerek Thompson\nDerrick Harris\nDevin Finzer\nDevon Zuegel\nDiana Peña\nDiane Greene\nDick Costolo\nDieter Shirley\nDiishan Imira\nDiogo Monica\nDominic Shine\nDominique Reliford\nDon Duet\nDon Faul\nDorris O'Brien\nDoug Ducey\nDoug Folden\nDoug McCracken\nDouglas Argueta\nDozie Uche\nDrew Coffman\nDylan Field\nDylan Rhodes\nEd Felten\nEd Lynch\nEddie Lim\nEddy Lazzarin\nEdith Zimmerman\nEdward Perkins\nEdwin Poston\nEfrat Noy\nEhud Shapiro\nEileen Burbidge\nEileen Wu\nElad Gil\nElaine Fuchs\nElaine Shi\nElena Burger\nEli Dourado\nElisa Leonhardt\nEliza Oak\nElizabeth Gunn\nElizabeth Harkavy\nElizabeth May\nElizabeth Ocken\nElizabeth Stark\nElizabeth Weil\nEllen Tunoa\nEmile Petrone\nEmilio Torres\nEmily Graff\nEmily Hinsch\nEmily Keir\nEmily Oster\nEmily Westerhold\nEmma Janaskie\nEric Budish\nEric Dai\nEric Ries\nEric Thomas\nEric Topol\nEric Wu\nErica Schecter\nErik Brynjolfsson\nErik Kiser\nErik Torenberg\nErika Bracken\nErika Herrera\nErika Louie\nErin Grody Kingsley\nErin Murphy\nErin Tice\nErin Tonnar\nErin Winkler\nErtem Nusret Tas\nEsther Shinn\nEthan Bueno de Mesquita\nEthan Ferreira\nEthan Zuckerman\nEuan Ashley\nEugene Volokh\nEugene Wei\nEugenia Yee\nEula Takahashi\nEva Sakkas\nEvan Burfield\nEvan Osnos\nEvangelos Simoudis\nEzra Klein\nF. Gary Gray\nFabiola Godinez\nFabrizio Zilibotti\nFahad Saleh\nFarid Jiandani\nFei-Fei Li\nFelix Do\nFEWOCIOUS\nFiona Kennedy\nFiona Murray\nFlashrekt\nFlora Oliveira\nFlori Del Valle\nFlorian Leibert\nFoteini Baldimtsi\nFrancesca Gino\nFrank Chen\nFrank Wilczek\nFred Benenson\nFred Ehrsam\nFred Upton\nFred Wilson\nFreda Lewis-Hall\nFrederic Kerrest\nFuture Editorial\nGabby Dizon\nGabby Reece\nGabriel Otte\nGabriel Vasquez\nGaetan Barthelemy\nGarrett Biel\nGary Ang\nGary Reedy\nGary Wolf\nGaurav Banga\nGaurav Dhillon\nGaut\nGayle Tzemach Lemmon\nGeoffrey Woo\nGeorg Fuchsbauer\nGeorg Petschnigg\nGeorge Church\nGeorge Danezis\nGeorge Fraser\nGeraldine Chan\nGérard Cachon\nGerard Ryle\nGerri Elliott\nGerry Tsoukalas\nGia Scinto\nGil Elbaz\nGil Shafir\nGina Moon\nGina Neff\nGina Yocom\nGinger Liau\nGokul Rajaram\nGoldie Chang\nGrace Ellis\nGraham Allison\nGrant Gregory\nGrant Jordan\nGrant LaFontaine\nGrant Rabenn\nGray Kinsella\nGreg Bowman\nGreg Clayman\nGreg Linares\nGreg Loehmann\nGreg Lynn\nGreg Solano\nGreg Truesdell\nGreg Waldon\nGregory Allen\nGregory Mundis\nGretchen Bush\nGretchen McCulloch\nGuido Appenzeller\nGustav Söderström\nGustavo Garcia\nGuy Goren\nGuy Raz\nGuy Wuollet\nHaley Van Dyck\nHanna Aziz\nHannah Frankl\nHanne Winarsky\nHaoyuan Li\nHarmit Malik\nHarry Grieve\nHarry Shum\nHarry Wright\nHatim Shafique\nHayden Adams\nHeather Gwynn\nHeather Podesta\nHedi Samar\nHelen Stoddard\nHelen Su\nHemant Mohapatra\nHendrik Pretorius\nHenri Kor\nHerb Lin\nHerman Narula\nHilmar Pétursson\nHoang Nguyen\nHoward Wu\nIan Dutra\nIan Shannon\nIan Sharp\nIce Cube\nIlan Zechory\nIllia Polosukhin\nIlyas Khan\nIma Christian\nIman Abuzeid\nInsiya Lokhandwala\nIon Stoica\nIrvin Chan\nIsa Guardalabene\nIsaiah Lott\nIsh Verduzco\nIsil Dillig\nIstván András Seres\nIttai Abraham\nIttay Eyal\nIva Messy\nIvan Linscott\nIvor Horn\nJ.D. Moriarty\nJack Donahoe\nJack Soslow\nJackie McQuiston\nJackson David\nJacob Westphal\nJacquelyn Melinek\nJad Esber\nJad Naous\nJade Lai\nJade Raymond\nJae Gnazzo\nJai Ramaswamy\nJaimie Buss\nJak Kennedy\nJake Auchincloss\nJakob Uszkoreit\nJamal Mohammed\nJames Beshara\nJames Currier\nJames da Costa\nJames Gwertzman\nJames J. Collins\nJames Kissell\nJames L. Madara\nJames Loftus\nJames Rathmell\nJames Rogers\nJames Watters\nJames Wu\nJames Zou\nJamie Brandon\nJamie McGurk\nJamie Sullivan\nJamilla Hemeid\nJana Odehnal\nJane Doe\nJane Lippencott\nJane Suh\nJanelle De Los Santos\nJared Bricklin\nJared Furutani\nJared Georgakopoulos\nJared Polis\nJared Smith\nJase Wilson\nJason Franklin\nJason Liu\nJason Mayden\nJason Milionis\nJason Mitchell\nJason Mok\nJason Rosenthal\nJason Warner\nJason Yanowitz\nJay Bradner\nJay Conte\nJay Drain\nJay Komarneni\nJay Rughani\nJean Reilly\nJeanne Tsan\nJeff Amico\nJeff Benson\nJeff Clark\nJeff Cordova\nJeff Glueck\nJeff Hawkins\nJeff Jones\nJeff Jordan\nJeff Lawson\nJeff Lu\nJeff Nagashima\nJeff Stump\nJeff Weiner\nJeffrey Immelt\nJeffrey Kaditz\nJeffrey Katzenberg\nJeffrey Kindler\nJeffrey Low\nJeffrey Silverstein\nJeffrey Zirlin\nJen Bulawsky\nJen Kha\nJenna Walsh\nJenna Zucker\nJennifer 8. Lee\nJennifer Doudna\nJennifer Kodner\nJennifer Konde\nJennifer Li\nJennifer Mumford\nJennifer Tejada\nJennifer Young\nJenny Cieplak\nJens Ernstberger\nJensen Harris\nJeremy Clark\nJeremy England\nJeremy Zhang\nJesse Holmes\nJesse Pollak\nJesse Walden\nJessica Childs\nJessica Hansen\nJessica Keeler\nJessica Patton\nJessica Verrilli\nJewel Pi\nJez Humble\nJi Kim\nJianying Luo\nJim Gilliam\nJimmy Chen\nJimmy Soni\nJing Wang\nJing Zou\nJJ Yu\nJoachim Neu\nJodi Lynn\nJodie Lutkenhaus\nJoe Gebbia\nJoe Grundfest\nJoe Montana\nJoe Morrissey\nJoe Schmidt\nJoe Sullivan\nJoel de la Garza\nJoel Mokyr\nJoel Monegro\nJoel Spolsky\nJoey Burleson\nJohn China\nJohn Collison\nJohn Fawcett\nJohn Garcia\nJohn Gedmark\nJohn Hennessy\nJohn Koelliker\nJohn M. Jack\nJohn Markoff\nJohn Menna\nJohn O’Farrell\nJohn Riccitiello\nJohn Smesko\nJohn Stanfield\nJohn Thompson\nJohn William Hatfield\nJonah Peretti\nJonathan Bush\nJonathan Dotan\nJonathan Downey\nJonathan Lai\nJonathan Lim\nJonathan Lusthaus\nJonathan Weissman\nJonathan Wong\nJordan Mazer\nJordan Stankowski\nJorge Conde\nJorge Gomez\nJose Guardado\nJoseph Bonneau\nJoseph Okpaku\nJoseph Spisak\nJosh Arnold\nJosh Bloom\nJosh Kim\nJosh Williams\nJoshua Browder\nJoshua Gans\nJoshua Grimm\nJoshua Hix\nJoshua Levin\nJoshua Lu\nJoshua Schank\nJoshua Soto\nJosie Ma\nJoyce Park\nJR Rivers\nJT Evans\nJuan Benet\nJudene Small\nJudy Savitskaya\nJudy Smith\nJulia Grace\nJulia Kirby\nJulie Bornstein\nJulie Farnham\nJulie Johnson\nJulie Samuels\nJulie Yoo\nJuliet Grier\nJuliet Nyatta\nJuliette Morton\nJulius Zhang\nJustin Bailey\nJustin Bethune\nJustin Blau\nJustin Cunningham\nJustin Gregorius\nJustin Kahl\nJustin Kan\nJustin Larkin\nJustin Paine\nJustin Pettit\nJustin Roberts\nJustin Simcock\nJustin Thaler\nJustine Moore\nJutta Steiner\nJyoti Bansal\nJZ Young\nKabir Gill\nKabir Laroia\nKais Khimji\nKamala Harris\nKaren Dunn\nKaren Wooley\nKarina Sobieski\nKarl Floersch\nkarma (Daniel Reynaud)\nKarmacoma\nKarthik Rau\nKartik Nayak\nKate Darling\nKate Dellolio\nKate Kerames\nKatherine Boyle\nKatherine Minarik\nKatherine Rundell\nKatherine Schoebel\nKathryn McKinley\nKathy Liu\nKathy Yang\nKatia Ameri\nKatie Baynes\nKatie Haun\nKatie Hemmerling\nKaty DeWitt-Drew\nKaty Nelson\nKayvon Tehranian\nKeener Barnhorst\nKeller Medlin\nKeller Rinaudo\nKelly Cannon\nKelsey Chaplinsky\nKelsey Mellard\nKen Chong\nKen Coleman\nKen Kocienda\nKerry Ganim\nKesha Cash\nKevin Chou\nKevin Chu\nKevin Dulsky\nKevin Kelly\nKevin McKinley\nKevin Nishioka\nKevin O'Kane\nKevin Rose\nKevin Tan\nKevin Wu\nKevin Zollman\nKidSuper\nKieran Snyder\nKierston Gittens\nKiki Mavridis\nKim Enright\nKim Malone Scott\nKim Milosevich\nKim Stevenson\nKim Zetter\nKimberly Tan\nKindra Mason\nKira Poskanzer\nKira Song\nKirstin Arbide\nKirt McMaster\nKofi Ampadu\nKouki Harasaki\nKrista Anderson-Copperman\nKristen Fortney\nKristen Johansson\nKristen Kee\nKristin Sauchak\nKristin Thayer\nKristina Graci-deLuna\nKristina Shen\nKristine Lipscomb\nKristo Käärmann\nKrisztina Holly\nKunal Bahl\nKunle Olukotun\nKurt House\nKyle Russell\nLaird Hamilton\nLatasha\nLaura Arrillaga-Andreessen\nLaura Baller\nLaura Behrens Wu\nLaura Deming\nLaura Gravley\nLaura Johnson\nLaura Shores\nLaura Weidman Powers\nLauren Berson\nLauren Illovsky\nLauren Murrow\nLauren Richardson\nLauren Spragge\nLaurene Powell Jobs\nLawrence Levy\nLawrence Summers\nLeah Cassidy\nLee Kleinman\nLee Lefkowitz\nLeeAnn Caballero\nLeila Hay\nLeila Janah\nLenny Rachitsky\nLeslie Jaw\nLeslie Vosshall\nLester Chen\nLi Fan\nLi Fei-Fei\nLi Jin\nLiang Wu\nLilian King\nLily Liu\nLina Sergie Attar\nLinda Banuelos\nLinda Xie\nLinden Tibbets\nLing Ren\nLinlin Li\nLinxin Wen\nLioba Heimbach\nLisa Hawke\nLisa Lambert\nLisa Orr\nLisa Reilly\nLisa Rosano\nLizzy Anderson\nLJ Erwin\nLloyd Dean\nLoretta Sanchez\nLori Potter\nLuca Prosperi\nLuca Zanolini\nLuis Martinez\nLuis von Ahn\nLuke Wroblewski\nLydia Green\nLynda Gibson\nLynn Rudolph\nMadan Nagaldinne\nMaddison Masaeli\nMadeline Lancaster\nMaggie Hsu\nMaggie Leung\nMaggie Romero\nMahad Abedin\nMahesh Iyer\nMahesh Vellanki\nMahimna Kelkar\nMakiri Duckett\nMalinka Walaliyadde\nMallesh M. Pai\nMalloy Evans\nManas Punhani\nManny Luna\nMarc Andreessen\nMarc Andrusko\nMarc Benioff\nMarc Levinson\nMarci Barbera\nMarco Reuter\nMargaret Jen\nMargit Wennmachers\nMaria LaMagna Morales\nMarian Garvin\nMarianne Winkler\nMariano Sorgente\nMaricarmen Alvarez\nMariel Goldenstein\nMarigold Vu\nMarina Kusserow\nMario Gabriele\nMario Linares\nMarissa Bramlett\nMark Cranney\nMark Leslie\nMark McAndrew\nMark McClusky\nMárk Melczer\nMark Moore\nMark Regan\nMark Sendak\nMarkos Georghiades\nMarkus Covert\nMarkus Funk\nMartha Lane Fox\nMartin Casado\nMartin Fischer\nMarty Makary\nMarvin Ammori\nMarvin Zamora\nMary Pat Jordan\nMary-Catherine Lader\nMaryam Bahrani\nMason Hall\nMatei Zaharia\nMatt Abrahams\nMatt Billmann\nMatt Bornstein\nMatt Clifford\nMatt Flannery\nMatt Fleming\nMatt Gleason\nMatt Kaeberlein\nMatt Levine\nMatt Levy\nMatt Oberhardt\nMatt Shortal\nMatt Spence\nMatt Weinberg\nMatthew Colford\nMatthew Green\nMatthew Haughey\nMatthew McCullough\nMatthew Mills\nMatthew Olsen\nMatthew Rutter\nMatthew Stein\nMatthieu Hafemeister\nMaureen Lara\nMax Kesten\nMax Krohn\nMax Levchin\nMax Polyak\nMax Resnick\nMax Ventilla\nMaya Rahkonen\nMcPherson Moore\nMeaghan Hardy\nMeg Whitman\nMegan Holston-Alexander\nMegan Kristalyn\nMehdi Hasan\nMehul Mehta\nMel Williams\nMelanie Galang\nMelissa Liao\nMelissa Minor\nMelissa Wasser\nMellody Hobson\nMelody Latronico\nMeredith Donahue\nMia Gonzalez\nMia Mandich\nMicah Johnson\nMichael Beckerman\nMichael Blau\nMichael Brandt\nMichael Chan\nMichael Copeland\nMichael Dearing\nMichael Dell\nMichael Franklin\nMichael Garcia\nMichael J. Casey\nMichael J. Freedman\nMichael Killam\nMichael King\nMichael Lee\nMichael Leiter\nMichael Morell\nMichael Ostrovsky\nMichael Ovitz\nMichael Paulus\nMichael Raynor\nMichael Reed\nMichael Snyder\nMichael Temkin\nMichael Wee\nMichael Zhu\nMichel Del Buono\nMichel Feaster\nMichèle Flournoy\nMichele Griffin\nMichele Korver\nMichele Law\nMichelle Ervin\nMichelle Kelso\nMichelle Kung\nMichelle Mundy\nMichelle Shin\nMichelle Ufford\nMichelle Volz\nMichelle Wilson\nMichelle Winn\nMichelle You\nMike Curtis\nMike Haydon\nMike Hearn\nMike Jones\nMike Kasperzak\nMike Kelly\nMike King\nMike Lempres\nMike Manning\nMike Maples jr\nMike Masnick\nMike Matchett\nMike Paulus\nMike Sandwick\nMikeal Rogers\nMikey Dickerson\nMiles Jennings\nMilijana Curic\nMiller Whitehouse-Levine\nMinerva Munoz\nMinnie Ingersoll\nMinsun Pak\nMintu Turakhia\nMiranda Christ\nMo Shaikh\nMohammad Akbarpour\nMohsen Malayeri\nMolly Grace\nMonique McCambridge\nMorgan Beller\nMorgan Bender\nMurat Pak\nMuriel Bowser\nMurray Shanahan\nMy Pham\nNadia Asparouhova\nNadia Eghbal\nNaftali Harris\nNaithan Jones\nNanjira Sambuli\nNaomi Metzger\nNashid Braswell\nNassim Eddequiouaq\nNat Barling\nNatacha Crooks\nNatalia Carrera\nNatalie Bucher\nNatalie Taumoepeau\nNate Chang\nNate Lau\nNathalie Balaban\nNathan McCauley\nNathan Yoon\nNathaniel Gleicher\nNathaniel Popper\nNav Singh\nNazanin Daneshvar\nNeel Maitra\nNeha Narula\nNelson Perla-Ward\nNeveen Bader\nNicholas Christakis\nNicholas Pacilio\nNick Babaian\nNick McKeown\nNick Quah\nNick Tomaino\nNicki Locker\nNicole Conner\nNicole Forsgren\nNicole Irvin\nNicole Neuman\nNicole Stanners\nNiels Provos\nNigel Robinson\nNikhil Krishnan\nNina Suthers\nNir Eyal\nNitasha Tiku\nNitin Natarajan\nNitya Subramanian\nNkiru Balonwu\nNoah Citron\nNoah Feldman\nNoah Levine\nNoah Smith\nNoam Nisan\nNoemi Glaeser\nO’Shea Jackson Jr.\nOlaf Carlson-Wee\nOleg Rogynskyy\nOliver Hsu\nOlivia Moore\nOlivia Webb\nOmri Weinstein\nOoshma Garg\nOprah Winfrey\nOrion Hindawi\nOscar Menjivar\nP.J. Hasleton\nPablo Montagnes\nPacky McCormick\nPak\nPalmer Luckey\nPamela Anderson\nPamon Forouhar\nParag Khanna\nParijat Talkad\nParker Brown\nParker Conrad\nPatrice Peck\nPatrick Byrne\nPatrick Collison\nPatrick Conway\nPatrick McCorry\nPatrick McHenry\nPatrick O’Grady\nPatrick Rivera\nPatrick Sutton\nPaul Cafiero\nPaul Daugherty\nPaul Davison\nPaul Krugman\nPaul Vigna\nPaula Long\nPenny Pritzker\nPerri Chilton\nPete Buttigieg\nPeter Blackwood\nPeter Buisseret\nPeter Chan\nPeter Donnelly\nPeter Johnson\nPeter Lauten\nPeter Leeson\nPeter Levine\nPeter Ludwig\nPeter Rubin\nPeter Thiel\nPeter Wang\nPetra Garrett\nPhil Daian\nPhil Hathaway\nPhil Wong\nPhong Nguyen\nPorter Smith\npplpleasr\nPranav Garimidi\nPrasad Akella\nPrat Moghe\nPreethi Kasireddy\npunk6529\nPurnima Padmanabhan\nPyrs Carvolth\nQasar Younis\nQuang Dao\nQuinten Burgunder\nQuintus Kilbourn\nRachael Horwitz\nRachel Goslins\nRachel Jenkins\nRachel Kalmar\nRachel McIntyre\nRachel Steiner\nRahul Iyer\nRahul Vohra\nRajeev Singh\nRajeev Venkayya\nRam Palaniappan\nRamana Jonnala\nRati Gelashvili\nRaul Vazquez\nRavi Parimi\nRay Dalio\nRaymond Carreira\nRebecca Lewis\nRebecca Rettig\nReed Hastings\nRefik Anadol\nRegina Benjamin\nRenato Valdés Olmos\nReshma Saujani\nReshma Sohoni\nRex Salisbury\nRich Ezekiel\nRichard Green\nRichard Menger\nRichard Rosenblatt\nRick Young\nRidhima Ahuja\nRiyaz Faizullabhoy\nRob Goodman\nRob McElhenney\nRob Pardo\nRob Rhinehart\nRobbie Petersen\nRobbie Peterson\nRobert Alexander\nRobert Cottrell\nRobert Hackett\nRobert Kolker\nRobert Leshner\nRobert McNeely\nRobert Moreno\nRobert Siegel\nRobert Stromberg\nRobert Weber\nRobin Casey\nRobin Guo\nRobin Weisman\nRod Johnson\nRodrigo Ibarra Lopez\nRodrigo Pacheco\nRoger Dickey\nRoger Wattenhofer\nRoham Gharegozlou\nRohini Mukand\nRohit Bansal\nRoman Mars\nRoman Stanek\nRon Gill\nRon Lavi\nRon Rothblum\nRonald Evans\nRonnie Harris\nRosa Davila\nRosalind Rattan\nRose Legarda\nRoss Andersen\nRoss Shuel\nRostin Behnam\nRuben Gallego\nRuben Smith\nRuss Altman\nRuss Heddleston\nRuss Roberts\nRussell Davies\nRyan Allen\nRyan Caldbeck\nRyan Conde\nRyan Holloway\nRyan Hoover\nRyan McEntush\nRyan Petersen\nRyan Prescott\nRyan Sandler\nRyan Spoon\nRyan Tseng\nRyan Walsh\nRyan Ward\nRyan Wyatt\nSaar Tochner\nSachin Jain\nSafi Bahcall\nSagar Dhawan\nSaku Panditharatne\nSalem Vance\nSam Blackshear\nSam Broner\nSam Gerstenzang\nSam Ragsdale\nSam Thompson\nSam Williams\nSam Yam\nSamantha Gelt\nSamantha Langford\nSamantha Ludwig\nSamson Wu\nSamuel Arbesman\nSamuel Hammond\nSandra Samayoa\nSandy Jen\nSankaet Pathak\nSantiago Rodriguez\nSara Boesen\nSarah Fazal\nSarah Hamburg\nSarah Lumbard\nSarah Mascardo\nSarah Meiklejohn\nSarah Porter\nSarah Rebello\nSarah Wang\nSasha Stiles\nSatish Talluri\nSaurabh Ladha\nSavannah Cherry\nScott Clark\nScott Duke Kominers\nScott Gottlieb\nScott Hassan\nScott Kupor\nScott Rubin\nScott Shenker\nScott Tyler\nScott Walker\nScott Weiss\nSean Duffy\nSean Neville\nSebastian Oddo\nSeema Amble\nSeemay Chou\nSep Kamvar\nSergiu Pasca\nSeth Lobree\nSeth Sivak\nSeth Sternberg\nShai Bernstein\nShai Kopeld\nShaka Senghor\nShakil Khan\nShan Sinha\nShana Fisher\nShane Mac\nShane Parrish\nShangda Xu\nShannon (Stubo) Brayton\nShannon Barbour\nShannon Kelly\nShannon Schiltz\nShannon Snow\nShari Doherty\nSharon Chang\nShawn Conway\nSheela Krothapalli\nShellye Archambeau\nSherie James\nSherriAnn Cole\nShishir Mehrotra\nShonda Rhimes\nSid Gorham\nSigne Pierce\nSimon Denny\nSiqi Chen\nSonal Chokshi\nSophie Song\nSoubhik Deb\nSpencer Dinwiddie\nSpencer Howard\nSpencer Rascoff\nSreeram Kannan\nSreevidya Kasturil\nSri Kosuri\nSriram Krishnan\nSrivatsan Sridhar\nStacey Cunningham\nStacey Merrick\nStacia Murray\nStacy Brown-Philpot\nStacy D'Amico\nStacy Warner\nStefan McDonough\nSten Tamkivi\nStephane Bancel\nStephanie Anyanwu\nStephanie Cohen\nStephanie Doppelt\nStephanie Smith\nStephanie Watkins\nStephanie Zinn\nStephen Armanios\nStephen Wink\nStephenie Zhang\nSteve Buress\nSteve Cadigan\nSteve Cheney\nSteve Harvey\nSteve Kaczynski\nSteve McDermid\nSteve Smith\nSteve Zhao\nSteven Adair\nSteven Ebert\nSteven Johnson\nSteven Levy\nSteven Sinofsky\nStewart Butterfield\nStina Ehrensvärd\nStuart Luman\nStuart Russell\nSudip Chakrabarti\nSue Hager\nSuhail Doshi\nSukhinder Singh Cassidy\nSumeet Singh\nSumit Shah\nSungMo Park\nSunil Chokshi\nSurya Ganguli\nSusan B. Wilde\nSusan Mernit\nSusan Rice\nSusannah Fox\nSydney Paul\nTaavet Hinrikus\nTaggart Matthiesen\nTamzen Brewis\nTana Billingsley\nTarek Mansour\nTarun Chitra\nTauri Laws Phillips\nTawny Holguin\nTaylor McFadden\nTed Not Lasso\nTed Sarandos\nTed Ullyot\nTerell Sterling\nTerence Carroll\nTeresa Carlson\nTerry Angelos\nTerry Brown\nThan Nguyen\nThanh Nguyen\nThe 2015 Academic Roundtable Sessions\nThe TxO team\nTheresa DeMichele\nTheresa Dilley\nTheresa Fisher\nTheresa Walz\nTheresia Gouw\nThibaut Scholasch\nThomas Gjerde\nThomas Juenger\nThomas Long\nThomas Rando\nTiffany Vo\nTiffany Zhong\nTim Beiko\nTim O'Reilly\nTim Roughgarden\nTim Schafer\nTim Sullivan\nTimmu Tõke\nTina Anderson\nTina Bhatnagar\nTina Ferguson\nTina Wie\ntinawie\nTing Ni\nTobi Lütke\nTodd Cranney\nTodd Lutwak\nTodd McKinnon\nTodd Park\nTodd Young\nTolga Dizdarer\nTom Butta\nTom Coates\nTom Davenport\nTom Ellis\nTom Hammer\nTom Hofmann\nTom Lehman\nTom Mitchell\nTom Preston-Werner\nTom Rikert\nTom Standage\nTomicah Tillemann\nTony Blair\nTony Blinken\nTori Landrum\nTracy Chou\nTracy Young\nTren Griffin\nTrent Mayol\nTrevor Bedford\nTristan Handy\nTristan Walker\nTroy Kirwin\nTugce Erten\nTurner Novak\nTushar Garg\nTyler Cowen\nTyler Wilson\nTyson Clark\nUma Valeti\nUsman Azam\nUzi Dutta\nValentina Marzorati\nValeria Nikolaenko\nValerie Arboleda\nVan Jones\nVan Le-Gray\nVanessa Kropf\nVas Narasimhan\nVaughn Ferguson\nVenkat Mocherla\nVicente De Baca\nVickie Casillas-Smith\nVictor Liang\nVictor Shoup\nVictoria Butcher\nVijay Balasubramaniyan\nVijay Kedar\nVijay Pande\nVineeta Agarwala\nVinod Khosla\nVirginia Postrel\nVishal Amin\nVitalik Buterin\nVivian Brooks\nVoices Onchain\nW. Brian Arthur\nWahab Owolabi\nWei Luo\nWendy Drpic\nWerner Gerola\nWes Taylor\nWhitney Owens\nWill Brown\nWill Wong\nWillem Mulder\nWilliam Gifford\nWilliam Mougayar\nWing Cheng\nXian Zhang\nXiang-Dong Fu\nXingchen Zhou\nYannai A. Gonczarowski\nYehuda Lindell\nYevgeniy Dodis\nYinuo Zhang\nYogi Roth\nYohei Ishii\nYoko Li\nYoni Levy\nYoram Novick\nYuichi Kurosawa\nYujin Chung\nYun Fan\nYung Yung Sheung\nYuval Efron\nYuval Harari\nZac Bookman\nZach Abrams\nZach Cohen\nZach Dicker\nZach Haigney\nZachary Chen\nZachary Gray\nZack Weiner\nZahabiya Gabaji\nZak Doric\nZal Bilimoria\nZane Lackey\nZeta Avarikioti\nZeya Yang\nZooko Wilcox\nZoran Basich\n\nclear all Joshua Lu\n\n/\n\n/\n\n/\n\n/\n\nInitializing...\n\n09.21.23 / Chris Dixon and Joshua Lu\nInvesting in Proof of Play\nComposability is one of the most powerful forces enabled by blockchains: for the first time, users can take code, assets, and items from one application and use them with another. In previous eras of the web, this was impossible because every social network, marketplace, exchange, and game engine has its own system of closed servers,...\n\nannouncements & news\nannouncements\ngaming\ninvestments\n\nLoading more posts...\n\nNo more posts to load\n\nNo posts found","tokens":6879,"crawled_at":1791195992001}
+{"id":10584,"url":"https://docs.ethena.fi/video-guides/how-to-stake-ena","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"How to Stake ENA | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nUsers in permitted jurisdictions can stake & unstake ENA/sENA with Ethena via the UI.\nUsing the UI, the staking & unstaking ENA/sENA user workflow is:\n\nThe user requests to stake/unstake ENA/sENA via the dApp interface by clicking \"Stake\"/\"Unstake\", which pops up their selected wallet to sign the requested transaction.\n\nAfter the user signs the transaction with their wallet, the transaction is submit to the blockchain.\n\nUpon successful confirmation of the transaction, the user receives sENA/ENA as their ENA/sENA is atomically swapped.\n\nImportant to Note\n\nUsers do NOT need to do anything but hold sENA to receive incentive rewards.\n\nRewards aren’t earned directly by sENA holders; rather, it accumulates within the staking contract, which results in the \"value\" of sENA rising over time in ENA terms. Users are able to unstake their sENA at any time, at which point they receive an amount sENA reflecting the staked amount plus any increase in value of sENA in ENA terms from the time the user staked until unstaking.\n\nThe amount of sENA a user will receive when staking sENA will depend on the current value of sENA. At launch the value was 1 sENA = 1 ENA, but sENA is expected to slowly increase in value as distributions are transferred into the staking smart contract.\n\nThis is because sENA was implemented using a token vault mechanism to provide protocol level rewards to permitted users. This mechanic is similar to Rocketpool's rETH.\n\nTherefore, while a staker might receive less sENA than ENA staked, the value of the sENA will always be equal to or greater than the ENA you staked in ENA terms.\n\nThere is a cooldown period of 7 days after unstaking sENA, ENA will be available to withdraw after that period.\n\nDistributions of ENA to the sENA contract are purely discretionary. In late 2024 and early 2025, unclaimed ENA grants from Ethena's Season 1 airdrop were distributed to sENA. As of September 2025, however, no distributions are in effect or announced.\n\nLast updated 2 months ago\nWas this helpful?","tokens":529,"crawled_at":1791195995895}
+{"id":10585,"url":"https://docs.sui.io/develop/security/best-practices","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Security Best Practices | Sui Documentation","text":"Overview of security best practices on Sui.\n\nThis page describes a few recommended security best practices when developing applications on Sui. These recommendations are not comprehensive for all application types, use cases, or architectures. Do your own research and have production applications audited thoroughly.\n\nSmart contract security​\n\nAudit your contracts​\n\nEnsure transactions operate on smart contracts you trust and have audited. Sui packagesPackageSmart contracts on Sui. are immutable once published. If a package is upgradeable, the UpgradeCap controls publication of newer versions, so audit both the current package and its upgrade policy.\n\nGovern package upgrades​\n\nAn upgradeable package can publish a new onchain version at any time, and the new version controls all future behavior. Treat the UpgradeCap as a security-critical capability:\n\nProtect the UpgradeCap with the same care as an admin capability. Whoever holds it can change your package, as far as its upgrade policy allows.\n\nApply a custom upgrade policy, a multisigMultisigMulti-signature transactions that require multiple keys for authorization., or a timelock so that no single key can ship an upgrade silently.\n\nCall make_immutable on the UpgradeCap when you no longer need upgrades. This is irreversible: it permanently freezes the package, and you can never upgrade it again, so be certain before you do it.\n\nVerify packages and dependencies​\n\nBefore you trust a package, verify its exact onchain package ID, the IDs of its dependencies, and its upgrade policy. Do not rely on package names or frontend constants alone, because those can point anywhere. A dependency that is still upgradeable can change after your audit.\n\nRely on MoveMoveAn open source programming language used for all activity on Sui.'s safety as a foundation, not a guarantee​\n\nMove's type system, resource model, bytecode verifier, and checked arithmetic reduce entire classes of bugs. They do not replace business-logic review, invariant testing, access control checks, or economic analysis. Treat the language guarantees as a foundation, and still review the logic that sits on top of them.\n\nValidate invariants and objectObjectThe basic unit of storage on Sui. relationships​\n\nMany Sui bugs use a valid object in the wrong relationship. Inside every privileged function, validate amounts, object IDs, dynamic field keys, ownership expectations, and the relationships between objects, such as a capability matching the object it governs. Check zero and overflow edge cases even though Move arithmetic is checked, because an unexpected abort can still be a denial of service.\n\nEmit events for privileged actions​\n\nEmit events for admin changes, allowlist updates, mint and burn operations, denylist actions, configuration changes, oracle updates, and emergency pauses. Events make privileged activity auditable and let offchain monitoring detect unexpected behavior quickly.\n\nOnchain randomness​\n\nLimit what follows a random call in a PTBProgrammable transaction blocksDefine all user transactions on Sui.​\n\nSui restricts which commands can follow a MoveCall that consumes Random in the same programmable transaction block. Do not depend on post-random commands other than the allowed object transfers and coin merges. This prevents test-and-abort attacks, where an attacker inspects the result and aborts the transactionTransactionA number of commands that execute on inputs to define the result of the transaction. if the outcome is unfavorable.\n\nMark randomness-consuming functions as private entry​\n\nDeclare functions that consume randomness as private entry functions. A private entry function can be called directly from a transaction but not from another Move moduleModuleA component of a Move package that defines interaction with on-chain objects., which prevents other modules from composing your randomness-consuming function into a larger call that enables a test-and-abort attack. This is not optional: the Move compiler enforces it by rejecting public functions that take Random or RandomGenerator as an argument.\n\nNever accept RandomGenerator as a parameter​\n\nAlways create the generator internally to prevent manipulation.\n\nBalance gasGasThe computational cost of execution and object storage for a transaction. across outcome paths​\n\nDesign functions so that the outcome favorable to the transaction sender consumes the same amount of gas as, or more gas than, an unfavorable outcome. Otherwise an attacker can set a gas budget that has enough gas for the favorable outcome but not the unfavorable one, aborting the transaction whenever the result is not in their favor.\n\nConsider a two-transaction commit-reveal pattern​\n\nFor high-stakes applications, consider a two-transaction commit-reveal pattern to further reduce the influence a caller has over a random outcome.\n\nSeal (Encryption and Access Control)​\n\nChoose trusted key server operators and diversify across organizations, jurisdictions, and infrastructure providers.\n\nUse threshold encryption (for example, 2-of-3) to tolerate compromised servers while maintaining availability.\n\nUse envelope encryption for sensitive or large data: encrypt data with your own symmetric key, then use Seal to manage access to that key only.\n\nEnsure correct access policy​\n\nThe Move code in seal_approve* functions must accurately express your intended access rules. If the package containing seal_approve* remains upgradeable, whoever controls its upgrade path can change future access policy. Govern that upgrade path like a security-critical capability.\n\nNautilusNautilusSecure and verifiable off-chain computation on Sui.​\n\nMinimize enclave code​\n\nLess code means a smaller attack surface.\n\nAudit dependencies​\n\nReview all libraries used in the enclave.\n\nUse short timestamps​\n\nShort timestamps reduce the replay attack window.\n\nVerify and enforce expected PCRs​\n\nBefore you trust enclave output, verify that the platform configuration registers (PCRs) match the values you expect for your enclave image. Reject output from an enclave with unexpected PCRs, and alert on any drift.\n\nProtect signed enclave payloads​\n\nApply signed payload hygiene to every message the enclave signs. Use domain or intent separation so a signature for one purpose cannot be replayed for another. Check timestamp freshness, and include a nonce or request ID wherever replay matters.\n\nDon't rely solely on TEE guarantees​\n\nA trusted execution environment reduces risk but does not remove it. Combine it with the other practices on this page.\n\nCoin and capability security​\n\nProtect TreasuryCap​\n\nThe TreasuryCap controls minting and burning permissions.\n\nProtect MetadataCap​\n\nThe MetadataCap controls coin branding.\n\nProtect DenyCapV2​\n\nThe DenyCapV2 can restrict coin usage, which is a powerful compliance and centralization control. Whoever holds it can block addressesAddressA unique, anonymous identity on a blockchain network. from transacting with the coin. Govern it transparently, and document who can use it.\n\nSet supply model early​\n\nSet the supply model early, and understand the implications of a fixed, burn-only, or flexible supply.\n\nAccess control​\n\nAccess control determines who can call privileged functions in your package, such as minting, withdrawals, or configuration changes. Move gives you several mechanisms to enforce authorization. Choose them deliberately, because a missing or weak check can expose privileged operations to any caller.\n\nFor implementation patterns and code examples, see the Access control section of the Move best practices guide and the capability pattern example app.\n\nPrefer capability objects over address allowlists​\n\nA capability object is a struct with the key ability that acts as a permission token. Holding the object proves authorization, so a function can gate access by requiring a reference to the capability. This approach composes well, because another protocol can hold the capability on behalf of a user, and you avoid maintaining an onchain list of addresses. Use capability objects such as AdminCap or MintCap as your default access control mechanism.\n\nManage address allowlists deliberately​\n\nSome designs still need an address allowlist, for example a set of accounts that can claim an airdrop. When you use one, store it in a well-defined object, restrict updates to a privileged function, and emit an event whenever an entry changes. Consider adding a time-lock on updates so that membership changes take effect only after a delay, giving observers time to react to an unexpected change. Events give offchain services and auditors a record of every membership change. Without them, allowlist changes are difficult to monitor.\n\nDo not rely on tx_context::sender() alone​\n\ntx_context::sender() returns the address that signed the transaction. Using it as the only authorization check ties a function to a single signer and breaks composability, because another contract cannot call the function on behalf of a user. Prefer capability objects or explicit object ownership checks when composability matters. Reserve tx_context::sender() for cases where the signer is genuinely the only valid actor.\n\nRequire explicit capabilities for privileged functions​\n\nMake every privileged function take the relevant capability as a parameter, such as AdminCap for configuration, TreasuryCap for minting, or DenyCapV2 for usage restrictions. Move's type system enforces this at transaction construction time, because a caller cannot produce a &AdminCap reference without owning the object. Place the capability as the second parameter to keep method associativity, as described in the Admin capability section of the Move best practices guide.\n\nProtect and rotate admin capabilities​\n\nTreat admin capabilities as high-value assets:\n\nDo not transferTransferChanging the owner of an asset. admin capabilities casually. Each transfer grants full privileges to the recipient.\n\nHold admin capabilities in a multisig address or a dedicated custody setup rather than a single hot wallet.\n\nPlan a rotation path before you publish. If a capability holder is compromised, you need a way to issue a new capability and stop honoring the old one.\n\nInclude a revocation path​\n\nDesign a way to revoke a compromised or outdated capability before you publish the package. Common options include:\n\nAn onchain registry that records valid capability IDs, where privileged functions check the registry and reject revoked IDs.\n\nA version or epochEpochA period of time defined by the network. field that privileged functions check, which you can advance to invalidate older capabilities.\n\nA function that destroys a capability, which only helps when the holder still controls the capability and cooperates.\n\nFor a capability that is lost or held in someone else's custody after a compromise, you cannot rely on destroying it. A registry check or version check is the only revocation mechanism that works without the holder's cooperation. Without one, a leaked capability remains valid for the life of the package.\n\nValidate capability and object relationships​\n\nWhen a capability governs a specific object, store the object's ID in the capability (or the capability's ID in the object) and check that they match inside the function. For example, a capability that manages one vault should only operate on that vault. Without this check, a caller could pass a valid capability for a different object and act outside your intended scope.\n\nEnforce authorization on shared object functions​\n\nAnyone can submit a transaction that references a shared object. A public function that takes a shared object runs for any caller unless the function itself checks authorization. Never assume access to a shared object is restricted. Require a capability, validate the sender, or check object ownership inside every privileged function that touches shared state.\n\nOracle and offchain data​\n\nValidate offchain data before you use it​\n\nIf your contracts consume offchain data, such as price feeds, validate it before you act on it. Check the freshness of the data, confirm the source, and verify any signatures. Apply replay protection so an old data point cannot be submitted again. Define explicit failure behavior for when the data is missing, stale, or invalid, so a feed outage does not produce an unsafe result.\n\nEmergency controls​\n\nConsider pause and rate-limit mechanisms​\n\nFor high-value applications, consider a pause, kill-switch, or rate-limit mechanism that can contain an active incident. Document who can trigger each control and how you prevent abuse, because an emergency control is itself a privileged operation. Gate it with a capability, and emit an event whenever someone uses it.\n\nFrontend and transaction signing​\n\nShow human-readable transaction intent​\n\nShow users a human-readable description of what a transaction does before they sign it. Avoid blind signing, where the user approves opaque bytes. Dry-run or simulate the transaction when possible, so the user and your app can see the expected effects first.\n\nVerify package IDs in the client​\n\nVerify the exact package IDs your frontend calls. Do not trust a package only because of its name or a constant compiled into an older build. Pin the IDs you audited, and check them at runtime.\n\nDomain-separate offchain signed messages​\n\nWhen your app signs messages offchain, such as personal messages, include a domain separator and an intent so a signature created for one context cannot be replayed in another. See Intent Signing for how Sui separates signing domains.\n\nUser and operator key management​\n\nKeep your private signature key private​\n\nNo other party can operate on your owned assets without your private signature key.\n\nVerify recipient addresses carefully​\n\nSending objects to an incorrect address might have irrevocable effects.\n\nUse multisig or hardware custody for privileged keys​\n\nHold admin keys and capabilities in a multisig address, a hardware wallet, or a dedicated custody setup. Avoid keeping privileged keys in a single hot wallet.\n\nSeparate keys by role and network​\n\nUse separate keys for the deployer, the admin, and routine operations, so a compromise of one role does not grant the others. Keep TestnetTestnetStaging network for testing changes before production deployment. and MainnetMainnetProduction network for live transactions and real-value assets. keys separate, so a test key can never sign a production transaction.\n\nDocument recovery and rotation procedures​\n\nWrite down how to recover and rotate every privileged key before you launch. A documented procedure is what lets you respond quickly when a key is lost or compromised.\n\nGeneral network security​\n\nUnderstand the validatorValidatorResponsible for executing tasks like staking, gas price references, and tallying rules. trust assumption​\n\nSui maintains its security properties as long as more than 2/3 of validators by stake operate correctly. The network uses Byzantine fault tolerant broadcast and consensusConsensusThe process by which the majority of nodes agree on the current state of the network, so it tolerates a minority of faulty or malicious validators.\n\nTreat all onchain activity as public​\n\nEvery transaction and object on Sui is public and auditable, so anyone can inspect the activity of an address. To protect user privacy, consider using multiple addresses to separate unrelated activity.\nRelated topics\n\nUpgrading Packages\nUpgrade a published Move package on Sui using the Sui CLI, understand layout-compatibility requirements, manage UpgradeCap and UpgradeTicket, and apply custom upgrade policies to control what changes are permitted.\nCustom Upgrade Policies\nCustom upgrade policies are used to upgrade live packages while addressing the security risks of single key ownership upgrades.\nEmitting Events\nLearn how to define Move event structs, emit events from smart contracts, and process or query them using gRPC, the TypeScript SDK, or a custom indexer.\nWhat is a PTB?\nProgrammable transaction blocks are a group of commands that complete a transaction on Sui.\n\nSmart contract security\nOnchain randomness\nSeal (Encryption and Access Control)\nNautilus\nCoin and capability security\nAccess control\nOracle and offchain data\nEmergency controls\nFrontend and transaction signing\nUser and operator key management\nGeneral network security\n\nWas this page helpful?","tokens":4095,"crawled_at":1791195997336}
+{"id":10586,"url":"https://www.metaplex.com/docs/smart-contracts/bubblegum-v2/fetch-cnfts","domain":"www.metaplex.com","chapter":"docs","title":"Fetching Compressed NFTs - Bubblegum V2 - Metaplex","text":"Summary\nFetching compressed NFTs retrieves cNFT data and proofs using the Metaplex DAS API. This page covers the DAS API setup, asset IDs, fetching individual and multiple cNFTs, and retrieving proofs.\nInstall and configure the Metaplex DAS API SDK\nFetch individual cNFTs using getAsset and their proofs using getAssetProof\nFetch multiple cNFTs by owner or by collection\nDerive Leaf Asset IDs from merkle tree addresses and leaf indices\nAs mentioned in the Overview page, Compressed NFTs are not stored inside onchain accounts like regular NFTs but, instead, are logged in the transactions that created and updated them.\nAs such, a special indexer was created to facilitate the retrieval of Compressed NFTs. This indexed data is made available through an extension of the Solana RPC methods which we call the Metaplex DAS API. In fact, the DAS API allows us to fetch any Digital Asset. This can be a Compressed NFT, a regular NFT, or even a Fungible Asset.\nSince not all RPCs support the DAS API, you will need to choose your RPC provider carefully if you are planning to work with Compressed NFTs. Note that we maintain a list of all RPCs that support the Metaplex DAS API in a dedicated page.\nOn this page, we will learn how to fetch Compressed NFTs using the Metaplex DAS API.\nInstalling the Metaplex DAS API SDK\nOnce you have chosen an RPC provider that supports the Metaplex DAS API, you may simply send special RPC methods to fetch Compressed NFTs. However, our SDKs provide a more convenient way to get started with the DAS API by offering helper methods. Follow the instructions below to get started with the Metaplex DAS API using our SDK.\nGet started with the Metaplex DAS API\n\nWhen using Umi, the Metaplex DAS API plugin is automatically installed within the mplBubblegum plugin. So you are already be good to go!\nIf you wanted to use the DAS API plugin without importing the whole mplBubblegum plugin, you could do so by installing the Metaplex DAS API plugin directly:\nnpm install @metaplex-foundation/digital-asset-standard-api\n\nAfter that, register the library with your Umi instance:\nimport { dasApi } from '@metaplex-foundation/digital-asset-standard-api';\n\numi.use(dasApi());\n\nYou can find more information about the methods available on the Metaplex DAS API on its repository.\n\nAsset IDs\nIn order to fetch an NFT, compressed or not, we need to have access to a unique ID that identifies the NFT. We call this unique identifier the Asset ID.\nFor regular NFTs, we use the mint address of the NFT for that purpose since all other accounts simply derive from that address.\nFor compressed NFTs, we use a special PDA (Program Derived Address) that is derived from the address of the Merkle Tree and the leaf index of the Compressed NFT in the Merkle tree. We call this special PDA a Leaf Asset ID.\nYou typically shouldn't need to derive the Leaf Asset ID yourself since the DAS API methods will provide it for you when fetching Compressed NFTs in bulk — e.g. fetching all NFTs owned by a given address. However, if you had access to the address of the Merkle Tree and the leaf index of the cNFT, here's how you could use our SDKs to derive the Leaf Asset ID.\nFind the Leaf Asset ID PDA\n\nimport { findLeafAssetIdPda } from '@metaplex-foundation/mpl-bubblegum'\n\nconst [assetId, bump] = await findLeafAssetIdPda(umi, {\n\nmerkleTree,\n\nleafIndex,\n\n})\n\nFetching a Compressed NFT\nFetching a Compressed NFT is as simple as calling the getAsset method of the DAS API. This method will return an Rpc Asset object that contains the following information:\nId: The Asset ID as discussed above.\nInterface: A special value that defines the type of asset we are dealing with. E.g. V1_NFT OR ProgrammableNFT.\nOwnership: An object telling us who owns the asset. This includes any delegate that may have been set and whether or not the asset is marked as frozen.\nMutable: A boolean indicating whether the data of the asset is updatable or not.\nAuthorities: An array of authorities, each including a scope array indicating what operations the authority is allowed to perform on the asset.\nContent: An object containing the data of the asset. Namely, it includes its URI and a parsed metadata object.\nRoyalty: An object that defines the royalty model defined by the asset. Currently, there is only one royalty model supported which sends a percentage of the proceeds to the creator(s) of the asset.\nSupply: When dealing with printable assets, this object provides the current and max supply of printed editions.\nCreators: The list of creators of the asset. Each includes a verified boolean indicating whether the creator has been verified or not and a share number indicating the percentage of royalties that should be sent to the creator.\nGrouping: An array of key/value grouping mechanisms that can help index and retrieve assets in bulk. Currently, only one grouping mechanism is supported — collection — which allows us to group assets by collection.\nCompression: When dealing with Compressed NFTs, this object gives us various information about the leaf of the Bubblegum Tree. For instance, it provides the full hash of the leaf, but also partial hashes such as the Creator Hash and Data Hash which are used to verify the authenticity of the asset. It also gives us the Merkle Tree address, its root, sequence, etc.\nHere is how one can fetch an asset from a given Asset ID using our SDKs.\nFetch a Compressed NFT\n\nconst rpcAsset = await umi.rpc.getAsset(assetId)\n\nFetching the Proof of a Compressed NFT\nWhilst the getAsset RPC method returns a whole lot of information about the asset, it does not return the Proof of the asset. As mentioned, in the Overview page, the Proof of a Compressed NFT is a list of hashes that allow us to verify the authenticity of the asset. Without it, anyone could pretend that they have a Compressed NFT in a tree with any given data.\nAs such, many operations on Compressed NFTs — e.g. burning, transferring, updating, etc. — require the Proof of the asset before allowing us to perform them. Computing the Proof of an asset is possible but requires someone to know the hash of all Compressed NFTs that exist within a given tree. This is why the DAS API also keeps track of the Proof of all Compressed NFTs.\nIn order to access the Proof of a Compressed NFT, we may use the getAssetProof RPC method. This method will return an Rpc Asset Proof object containing the following information:\nProof: The proof of the Compressed NFT as promised.\nRoot: The root of the Merkle Tree that the asset belongs to. When verifying the asset using the provided Proof, we should end up with this root as the final hash.\nNode Index: The index of the asset in the Merkle Tree if we counted every single node in the tree from left to right, top to bottom. A more useful index called the Leaf Index can be inferred from this value by the following formula: leaf_index = node_index - 2^max_depth where max_depth is the maximum depth of the Merkle Tree. The Leaf Index is the index of the asset in the Merkle Tree if we counted only the leaves of the tree — i.e. the lowest row — from left to right. This index is requested by many instructions and is used to derive the Leaf Asset ID of the asset.\nLeaf: The full hash of the Compressed NFT.\nTree ID: The address of the Merkle Tree that the asset belongs to.\nAs you can see some of the information here is redundant from the getAsset RPC call but is provided here for convenience. However, the Proof and the Node Index of the asset can only be fetched through this method.\nHere is how we can fetch the Proof of an asset using our SDKs.\nFetch the proof of a Compressed NFT\n\nconst rpcAssetProof = await umi.rpc.getAssetProof(assetId)\n\nFetching Multiple Compressed NFTs\nThe DAS API also allows us to fetch multiple assets at once using the getAssetsByOwner and getAssetsByGroup RPC methods. These methods will return a paginated Rpc Asset List object containing the following information:\nItems: An array of Rpc Asset as described above.\nTotal: The total number of assets available based on the provided criteria.\nLimit: The maximum number of assets we are retrieving on a page.\nPage: When using numbered pagination, it tells us which page we are currently on.\nBefore and After: When using cursor pagination, it tells us after which and/or before which asset we are currently browsing assets. These cursors can be used to navigate to the previous and next pages.\nErrors: A potential list of errors returned by the RPC.\nHere is how we can use both of these RPC methods using our SDKs.\nBy Owner\nFetch Compressed NFTs by owner\n\nconst rpcAssetList = await umi.rpc.getAssetsByOwner({ owner })\n\nBy Collection\nFetch Compressed NFTs by collection\n\nconst rpcAssetList = await umi.rpc.getAssetsByGroup({\n\ngroupKey: 'collection',\n\ngroupValue: collectionMint,\n\n})\n\nNotes\nNot all RPC providers support the DAS API. Check the RPC Providers page for compatible options.\nThe DAS API plugin is automatically included when you install mplBubblegum — no separate installation needed.\nProofs fetched via getAssetProof may become stale if the tree is modified. Always fetch fresh proofs before performing write operations.\nFor Bubblegum V2 cNFTs that inherit seller fees from a collection, DAS puts the collection rate on royalty.basis_points / creators and the leaf sentinel on royalty.basis_points_raw / creators_raw. See Reading Inherited Royalties.\nFAQ\nWhich RPC providers support the DAS API?\nSee the RPC Providers page for a maintained list. Major providers like Helius, Triton, and Shyft support the DAS API.\nHow do I get the asset ID for a compressed NFT?\nIf you know the merkle tree address and leaf index, use findLeafAssetIdPda. Otherwise, use getAssetsByOwner or getAssetsByGroup to discover assets and their IDs.\nWhat is the difference between getAsset and getAssetProof?\ngetAsset returns the cNFT's metadata, ownership, and compression info. getAssetProof returns the merkle proof needed for write operations (transfer, burn, update, etc.).\nGlossary\nTermDefinition\nDAS API\nDigital Asset Standard API — an RPC extension for fetching compressed and standard NFT data\n\nAsset ID\nA unique identifier for an NFT. For cNFTs, it is a PDA derived from the merkle tree and leaf index\n\nLeaf Asset ID\nThe PDA-based identifier specific to compressed NFTs, derived from tree address and leaf index\n\ngetAsset\nDAS API method that returns metadata, ownership, and compression info for a digital asset\n\ngetAssetProof\nDAS API method that returns the merkle proof and root needed for write operations on a cNFT\n\ngetAssetsByOwner\nDAS API method that returns all assets owned by a given wallet address\n\ngetAssetsByGroup\nDAS API method that returns all assets in a given group (e.g., collection)","tokens":2679,"crawled_at":1791196048687}
+{"id":10587,"url":"https://docs.sui.io/develop/publish-upgrade-packages/upgrade","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Upgrading Packages | Sui Documentation","text":"Sui smart contracts are immutable package objects consisting of a collection of Move modules. Because packages are immutable, a transaction identifies a package version by its package ID rather than passing it as a versioned object input. If packages were mutable, they would be shared objects, and every call into a package would contend on that object.\n\nThe inability to change packages, however, becomes a problem when considering the iterative nature of code development. Builders require the ability to update their code and pull changes from other developers while keeping the properties that immutability provides. The Sui network provides a method for upgrading your packages while still retaining their immutable properties.\n\nUpgrade considerations​\n\nConsider the following details before upgrading your packages.\n\nModule initializers do not re-run with package upgrades. When you publish your initial package, Move runs the init function you define for the package once (and only once) at the time of the publish event. Any init functions you might include in subsequent versions of your package are ignored. See the module initializer section in The Move Book for more information.\n\nYou cannot delete old packages from the network. Nothing prevents other packages from accessing the methods and types defined in the old versions of your upgraded packages.\n\nUpgrade requirements​\n\nTo upgrade a package, your package must satisfy the following requirements:\n\nYou must have an UpgradeTicket for the package you want to upgrade. The Sui network issues UpgradeCaps when you publish a package, then you can issue UpgradeTickets as the owner of that UpgradeCap. The Sui Client CLI handles this requirement automatically.\n\nYour changes must be layout-compatible with the previous version.\n\nExisting public function signatures must remain the same.\n\nExisting struct layouts, including struct abilities, must remain the same.\n\nYou can add new structs and functions.\n\nYou can remove generic type constraints from existing functions (public or otherwise).\n\nYou can change function implementations.\n\nYou can change non-public function signatures, including public(package) and entry function signatures.\n\ninfo\nIf you have a package with a dependency, and that dependency is upgraded, your package does not automatically depend on the newer version. You must explicitly upgrade your own package to point to the new dependency.\n\nUpgrading​\n\nUse the sui client upgrade command to upgrade packages that meet the previous requirements, providing values for the following flags:\n\ntip\nBeginning with the Sui v1.24.1 release, the --gas-budget option is no longer required for CLI commands.\n\n--gas-budget: The maximum number of gas units that can be expended before the network cancels the transaction.\n\n--cap: The ID of the UpgradeCap. You receive this ID as a return from the publish command.\n\nDevelopers upgrading packages using Move code have access to types and functions to define custom upgrade policies. For example, a Move developer might want to disallow upgrading a package, regardless of the current package owner. The make_immutable function is available to them to create this behavior. More advanced policies using available types like UpgradeTicket and UpgradeReceipt are also possible. For an example, see this custom upgrade policy on GitHub.\n\nWhen you use the Sui client CLI, the upgrade command handles generating the upgrade digest, authorizing the upgrade with the UpgradeCap to get an UpgradeTicket, and updating the UpgradeCap with the UpgradeReceipt after a successful upgrade. To learn more about these processes, see the Move documentation for the package module.\n\nSecure upgrade checklist\nBefore you run an upgrade, verify the old and new package IDs and the upgrade digest, confirm your dependencies resolve to the expected package IDs, and confirm UpgradeCap custody (ideally multisig or timelock). When the upgrade changes shared object access, ensure the migrate function is authorized (for example, behind an AdminCap), emit a migration event for observability, and know when to call make_immutable to relinquish upgrade authority. See Security Best Practices for more.\n\nMigrating users to the latest version​\n\nBy default, users can choose to keep using the old version of a package, as well. As a package developer, you must be aware of and account for this possibility.\n\nFor example, you might define an increment function in your original package:\n\npublic fun increment(c: &mut Counter) {\nc.value = c.value + 1;\n}\n\nThen, your package upgrade might add an emit event to the increment function:\n\npublic struct Progress has copy, drop {\nreached: u64\n}\n\npublic fun increment(c: &mut Counter) {\nc.value = c.value + 1;\n\nif (c.value % 100 == 0) {\nevent::emit(Progress { reached: c.value });\n}\n}\n\nIf callers use both the old and upgraded increment function, the process fails because the old function is not aware of the Progress event.\n\nYou might also run into issues maintaining dynamic fields that need to remain in sync with a struct's original fields. To address these issues, you can introduce a new type as part of the upgrade and port users over to it, breaking backwards compatibility. For example, if you're using owned objects to demonstrate proof like proof of ownership, and you develop a new version of your package to address problematic code, you can introduce a new type in the upgraded package. You can then add a function to your package that trades old objects for new ones. Because your logic only recognizes objects with the new type, you effectively force users to update.\n\nAnother example: you discover a shared object in your package has flawed logic. You want users to use only the corrected object from the upgraded package, so you add a new type and migration function. This requires 2 transactions: 1 for the upgrade and 1 to set up the new shared object. Protect the setup function by creating an AdminCap object to ensure only you, as the package owner, can initiate it. You might also include a flag in the shared object to toggle its enabled state, preventing public access during migration. Create this flag proactively if you anticipate future migrations, not in response to flawed logic.\n\nVersioned shared objects​\n\nWhen you create packages that involve shared objects, think about upgrades and versioning from the start because all prior versions of a package still exist onchain. A useful pattern is to introduce versioning to the shared object and use a version check to guard access to functions in the package. This limits access to the shared object to the latest package version.\n\nUsing the earlier counter example:\n\nmodule example::counter;\n\npublic struct Counter has key {\nid: UID,\nvalue: u64,\n}\n\nfun init(ctx: &mut TxContext) {\ntransfer::share_object(Counter {\nid: object::new(ctx),\nvalue: 0,\n})\n}\n\npublic fun increment(c: &mut Counter) {\nc.value = c.value + 1;\n}\n\nTo ensure that upgrades to this package can limit access of the shared object to the latest version of the package, you must:\n\nTrack the current version of the module in a constant, VERSION.\n\nTrack the current version of the shared object, Counter, in a new version field.\n\nIntroduce an AdminCap to protect privileged calls, and associate the Counter with its AdminCap with a new field. You might already have a similar type for shared object administration, in which case you can reuse that. This cap is used to protect calls to migrate the shared object from version to version.\n\nGuard the entry of all functions that access the shared object with a check that its version matches the package VERSION.\n\nAn upgrade-aware counter module looks like the following:\n\nmodule example::counter;\n\n/// Not the right admin for this counter\nconst ENotAdmin: u64 = 0;\n\n/// Calling functions from the wrong package version\nconst EWrongVersion: u64 = 1;\n\n// 1. Track the current version of the module\nconst VERSION: u64 = 1;\n\npublic struct Counter has key {\nid: UID,\n// 2. Track the current version of the shared object\nversion: u64,\n// 3. Associate the `Counter` with its `AdminCap`\nadmin: ID,\nvalue: u64,\n}\n\npublic struct AdminCap has key {\nid: UID,\n}\n\nfun init(ctx: &mut TxContext) {\nlet admin = AdminCap { id: object::new(ctx) };\n\ntransfer::share_object(Counter {\nid: object::new(ctx),\nversion: VERSION,\nadmin: object::id(&admin),\nvalue: 0,\n});\n\ntransfer::transfer(admin, ctx.sender());\n}\n\npublic fun increment(c: &mut Counter) {\n// 4. Guard the entry of all functions that access the shared object\n// with a version check.\nassert!(c.version == VERSION, EWrongVersion);\nc.value = c.value + 1;\n}\n\nTo upgrade a module using this pattern requires making 2 extra changes on top of any implementation changes your upgrade requires:\n\nBump the VERSION of the package.\n\nIntroduce a migrate function to upgrade the shared object.\n\nThe following module is an upgraded counter that emits Progress events as originally discussed, but also provides tools for an admin (AdminCap holder) to prevent accesses to the counter from older package versions:\n\nmodule example::counter;\n\nuse sui::event;\n\n/// Not the right admin for this counter\nconst ENotAdmin: u64 = 0;\n\n/// Migration is not an upgrade\nconst ENotUpgrade: u64 = 1;\n\n/// Calling functions from the wrong package version\nconst EWrongVersion: u64 = 2;\n\n// 1. Bump the `VERSION` of the package.\nconst VERSION: u64 = 2;\n\npublic struct Counter has key {\nid: UID,\nversion: u64,\nadmin: ID,\nvalue: u64,\n}\n\npublic struct AdminCap has key {\nid: UID,\n}\n\npublic struct Progress has copy, drop {\nreached: u64,\n}\n\nfun init(ctx: &mut TxContext) {\nlet admin = AdminCap {\nid: object::new(ctx),\n};\n\ntransfer::share_object(Counter {\nid: object::new(ctx),\nversion: VERSION,\nadmin: object::id(&admin),\nvalue: 0,\n});\n\ntransfer::transfer(admin, ctx.sender());\n}\n\npublic fun increment(c: &mut Counter) {\nassert!(c.version == VERSION, EWrongVersion);\nc.value = c.value + 1;\n\nif (c.value % 100 == 0) {\nevent::emit(Progress { reached: c.value })\n}\n}\n\n// 2. Introduce a migrate function\nentry fun migrate(c: &mut Counter, a: &AdminCap) {\nassert!(c.admin == object::id(a), ENotAdmin);\nassert!(c.version < VERSION, ENotUpgrade);\nc.version = VERSION;\n}\n\nUpgrading to this version of the package requires performing the package upgrade and calling the migrate function in a follow-up transaction. The migrate function:\n\nIs an entry function and not public. This allows it to be entirely changed, including changing its signature or removing it entirely, in future upgrades.\n\nAccepts an AdminCap and checks that its ID matches the ID of the counter being migrated, making it a privileged operation.\n\nIncludes a sanity check that the version of the module is actually an upgrade for the object. This helps catch errors such as failing to bump the module version before upgrading.\n\nAfter a successful upgrade, calls to increment on the previous version of the package abort on the version check, while calls on the later version should succeed.\n\nExtensions​\n\nThis pattern forms the basis for upgradeable packages involving shared objects, but you can extend it in a number of ways, depending on your package's needs:\n\nThe version constraints can be made more expressive:\n\nRather than using a single u64, versions could be specified as a String, or a pair of upper and lower bounds.\n\nYou can control access to specific functions or sets of functions by adding and removing marker types as dynamic fields on the shared object.\n\nThe migrate function could be made more sophisticated by modifying other fields in the shared object, adding or removing dynamic fields, or migrating multiple shared objects simultaneously.\n\nYou can implement large migrations that need to run over multiple transactions in a 3 phase setup:\n\nDisable general access to the shared object by setting its version to a sentinel value (for example, U64_MAX), using an AdminCap-guarded call.\n\nRun the migration over the course of multiple transactions. For example, if a large volume of objects need to be moved, it is best to do this in batches, to avoid hitting transaction limits.\n\nSet the version of the shared object back to a usable value.\n\nExample​\n\nDevelop a package named sui_package. Its manifest (Move.toml) looks like the following:\n\n[package]\nname = \"sui_package\"\n\nWhen your package is ready, you publish it:\n\n$ sui client publish\n\nClick to openOutputINCLUDING DEPENDENCY Sui\nINCLUDING DEPENDENCY MoveStdlib\nBUILDING sui_package\nSuccessfully verified dependencies onchain against source.\nTransaction Digest: GPSpH264CjQPaXQPpMHpkzyGidZnQFvd1yUH5s9ncesi\n╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────╮\n│ Transaction Data │\n├──────────────────────────────────────────────────────────────────────────────────────────────────────────────┤\n│ Sender: PUBLISHER-ID │\n│ Gas Owner: PUBLISHER-ID │\n│ Gas Budget: 12298000 MIST │\n│ Gas Price: 1000 MIST │\n│ Gas Payment: │\n│ ┌── │\n│ │ ID: GAS-COIN-ID │\n│ │ Version: 2 │\n│ │ Digest: QDssxM4QKnhutWCYijiWWmYPtKWnHB9xVaLqPsDHiep │\n│ └── │\n│ │\n│ Transaction Kind: Programmable │\n│ ╭──────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │\n│ │ Input Objects │ │\n│ ├──────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │\n│ │ 0 Pure Arg: Type: address, Value: \"PUBLISHER-ID\" │ │\n│ ╰──────────────────────────────────────────────────────────────────────────────────────────────────────────╯ │\n│ ╭─────────────────────────────────────────────────────────────────────────╮ │\n│ │ Commands │ │\n│ ├─────────────────────────────────────────────────────────────────────────┤ │\n│ │ 0 Publish: │ │\n│ │ ┌ │ │\n│ │ │ Dependencies: │ │\n│ │ │ 0x0000000000000000000000000000000000000000000000000000000000000001 │ │\n│ │ │ 0x0000000000000000000000000000000000000000000000000000000000000002 │ │\n│ │ └ │ │\n│ │ │ │\n│ │ 1 TransferObjects: │ │\n│ │ ┌ │ │\n│ │ │ Arguments: │ │\n│ │ │ Result 0 │ │\n│ │ │ Address: Input 0 │ │\n│ │ └ │ │\n│ ╰─────────────────────────────────────────────────────────────────────────╯ │\n│ │\n│ Signatures: │\n│ 4NqP6CL1/LN1Ekr9NeL82PFGgVdEjrwsP82l/0mFvCd9TYO94CKBQAm8C/D6DsAuBrwu4cogQ3Mbh1huGc0yCg== │\n│ │\n╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────╯\n╭───────────────────────────────────────────────────────────────────────────────────────────────────╮\n│ Transaction Effects │\n├───────────────────────────────────────────────────────────────────────────────────────────────────┤\n│ Digest: GPSpH264CjQPaXQPpMHpkzyGidZnQFvd1yUH5s9ncesi │\n│ Status: Success │\n│ Executed Epoch: 285 │\n│ │\n│ Created Objects: │\n│ ┌── │\n│ │ ID: ORIGINAL-PACKAGE-ID │\n│ │ Owner: Immutable │\n│ │ Version: 1 │\n│ │ Digest: 4ZvhnDgehkRmzo3mtHjCc6aQkEz1SA87rDpDS6pGarFR │\n│ └── │\n│ ┌── │\n│ │ ID: 0xaa06f409af7a36c20a552e729eb985a9979149ae9ada5ce3ed413836fd12ed16 │\n│ │ Owner: Account Address ( PUBLISHER-ID ) │\n│ │ Version: 3 │\n│ │ Digest: 71G4PuCUoqx1KDTnt8zGMYUf6Qpf4CWgZsDxYN1d7mXE │\n│ └── │\n│ ┌── │\n│ │ ID: UPGRADE-CAP-ID │\n│ │ Owner: Account Address ( PUBLISHER-ID ) │\n│ │ Version: 3 │\n│ │ Digest: FNxdiGCk1fwXByda6Q2sx8RjuwUQBFYQk7C4Zr2H4qVw │\n│ └── │\n│ Mutated Objects: │\n│ ┌── │\n│ │ ID: GAS-COIN-ID │\n│ │ Owner: Account Address ( PUBLISHER-ID ) │\n│ │ Version: 3 │\n│ │ Digest: 9Fet6LPSBsjYjVMEQxkB4LRHfAJDFCQQ2iUAiUQ5eygF │\n│ └── │\n│ Gas Object: │\n│ ┌── │\n│ │ ID: GAS-COIN-ID │\n│ │ Owner: Account Address ( PUBLISHER-ID ) │\n│ │ Version: 3 │\n│ │ Digest: 9Fet6LPSBsjYjVMEQxkB4LRHfAJDFCQQ2iUAiUQ5eygF │\n│ └── │\n│ Gas Cost Summary: │\n│ Storage Cost: 10298000 MIST │\n│ Computation Cost: 1000000 MIST │\n│ Storage Rebate: 978120 MIST │\n│ Non-refundable Storage Fee: 9880 MIST │\n│ │\n│ Transaction Dependencies: │\n│ 3eHwwq6p2xQwBtXDE9KKNQwZFdHUGEKiJsR5LDmv4o7b │\n│ 7KAuWTJHCZmh2rMSAqobkhU5cuRBoVicwae78i9woDUK │\n╰───────────────────────────────────────────────────────────────────────────────────────────────────╯\n╭─────────────────────────────╮\n│ No transaction block events │\n╰─────────────────────────────╯\n\n╭────────────────────────────────────────────────────────────────────────────────────────────────────╮\n│ Object Changes │\n├────────────────────────────────────────────────────────────────────────────────────────────────────┤\n│ Created Objects: │\n│ ┌── │\n│ │ ObjectID: 0xaa06f409af7a36c20a552e729eb985a9979149ae9ada5ce3ed413836fd12ed16 │\n│ │ Sender: PUBLISHER-ID │\n│ │ Owner: Account Address ( PUBLISHER-ID ) │\n│ │ ObjectType: ORIGINAL-PACKAGE-ID::module::TYPE │\n│ │ Version: 3 │\n│ │ Digest: 71G4PuCUoqx1KDTnt8zGMYUf6Qpf4CWgZsDxYN1d7mXE │\n│ └── │\n│ ┌── │\n│ │ ObjectID: UPGRADE-CAP-ID │\n│ │ Sender: PUBLISHER-ID │\n│ │ Owner: Account Address ( PUBLISHER-ID ) │\n│ │ ObjectType: 0x2::package::UpgradeCap │\n│ │ Version: 3 │\n│ │ Digest: FNxdiGCk1fwXByda6Q2sx8RjuwUQBFYQk7C4Zr2H4qVw │\n│ └── │\n│ Mutated Objects: │\n│ ┌── │\n│ │ ObjectID: GAS-COIN-ID │\n│ │ Sender: PUBLISHER-ID │\n│ │ Owner: Account Address ( PUBLISHER-ID ) │\n│ │ ObjectType: 0x2::coin::Coin<0x2::sui::SUI> │\n│ │ Version: 3 │\n│ │ Digest: 9Fet6LPSBsjYjVMEQxkB4LRHfAJDFCQQ2iUAiUQ5eygF │\n│ └── │\n│ Published Objects: │\n│ ┌── │\n│ │ PackageID: ORIGINAL-PACKAGE-ID │\n│ │ Version: 1 │\n│ │ Digest: 4ZvhnDgehkRmzo3mtHjCc6aQkEz1SA87rDpDS6pGarFR │\n│ │ Modules: example │\n│ └── │\n╰────────────────────────────────────────────────────────────────────────────────────────────────────╯\n╭───────────────────────────────────────────────────────────────────────────────────────────────────╮\n│ Balance Changes │\n├───────────────────────────────────────────────────────────────────────────────────────────────────┤\n│ ┌── │\n│ │ Owner: Account Address ( PUBLISHER-ID ) │\n│ │ CoinType: 0x2::sui::SUI │\n│ │ Amount: -10319880 │\n│ └── │\n╰───────────────────────────────────────────────────────────────────────────────────────────────────╯\n\nThe result includes an Object Changes section with information you need for upgrading: an UpgradeCap ID and your package ID.\n\nYou can identify the different objects using the Object.objectType value in the response. The UpgradeCap entry has a value of String(\"0x2::package::UpgradeCap\") and the objectType for the package reads String(\"<PACKAGE-ID>::sui_package::<MODULE-NAME>\")\n\nAfter publishing, the package system automatically records the published address and upgrade capability in Published.toml. You do not need to manually edit Move.toml with addresses or published-at values. See Move Package Management for details on how publication tracking works.\n\nAfter a while, you decide to upgrade your sui_package to include some requested features.\n\nRun sui client upgrade command to upgrade your package. Pass the UpgradeCap ID (the <UPGRADE-CAP-ID> value from the example) to the --upgrade-capability flag.\n\n$ sui client upgrade --upgrade-capability <UPGRADE-CAP-ID>\n\nThe console alerts you if the new package doesn't satisfy the requirements, otherwise the compiler publishes the upgraded package to the network and returns its result.\n\nClick to openOutputTransaction Digest: 3NnJGryz2k2BJzjpndDVqVcdZmmefNMB8SJ9bCEQct22\n╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮\n│ Transaction Data │\n├──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤\n│ Sender: PUBLISHER-ID │\n│ Gas Owner: PUBLISHER-ID │\n│ Gas Budget: 9684740 MIST │\n│ Gas Price: 1000 MIST │\n│ Gas Payment: │\n│ ┌── │\n│ │ ID: GAS-COIN-ID │\n│ │ Version: 3 │\n│ │ Digest: D2rpccs7eSw8gtb4T1K2bSVzF5eApC68xiHDtNGQEcEb │\n│ └── │\n│ │\n│ Transaction Kind: Programmable │\n│ ╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │\n│ │ Input Objects │ │\n│ ├──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │\n│ │ 0 Imm/Owned Object ID: UPGRAD-CAP-ID │ │\n│ │ 1 Pure Arg: Type: u8, Value: 0 │ │\n│ │ 2 Pure Arg: Type: vector<u8>, Value: [49,208,61,255,107,134,136,221,231,35,60,2,248,17,234,236,64,76,71,188,57,104,46,113,67,94,232,236,64,59,144,112] │ │\n│ ╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ │\n│ ╭───────────────────────────────────────────────────────────────────────────────────────────╮ │\n│ │ Commands │ │\n│ ├───────────────────────────────────────────────────────────────────────────────────────────┤ │\n│ │ 0 MoveCall: │ │\n│ │ ┌ │ │\n│ │ │ Function: authorize_upgrade │ │\n│ │ │ Module: package │ │\n│ │ │ Package: 0x0000000000000000000000000000000000000000000000000000000000000002 │ │\n│ │ │ Arguments: │ │\n│ │ │ Input 0 │ │\n│ │ │ Input 1 │ │\n│ │ │ Input 2 │ │\n│ │ └ │ │\n│ │ │ │\n│ │ 1 Upgrade: │ │\n│ │ ┌ │ │\n│ │ │ Dependencies: │ │\n│ │ │ 0x0000000000000000000000000000000000000000000000000000000000000001 │ │\n│ │ │ 0x0000000000000000000000000000000000000000000000000000000000000002 │ │\n│ │ │ Current Package ID: ORIGINAL-PACKAGE-ID │ │\n│ │ │ Ticket: Result 0 │ │\n│ │ └ │ │\n│ │ │ │\n│ │ 2 MoveCall: │ │\n│ │ ┌ │ │\n│ │ │ Function: commit_upgrade │ │\n│ │ │ Module: package │ │\n│ │ │ Package: 0x0000000000000000000000000000000000000000000000000000000000000002 │ │\n│ │ │ Arguments: │ │\n│ │ │ Input 0 │ │\n│ │ │ Result 1 │ │\n│ │ └ │ │\n│ ╰───────────────────────────────────────────────────────────────────────────────────────────╯ │\n│ │\n│ Signatures: │\n│ nNJ8AiSAeV+NB3ayRTwcfaJHx3AzFHlZysbwda5e2jFBz5W9Z5EnzXV09xZMQYctUtW33jWpUFdK8hOJ9hZzDg== │\n│ │\n╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯\n╭───────────────────────────────────────────────────────────────────────────────────────────────────╮\n│ Transaction Effects │\n├───────────────────────────────────────────────────────────────────────────────────────────────────┤\n│ Digest: 3NnJGryz2k2BJzjpndDVqVcdZmmefNMB8SJ9bCEQct22 │\n│ Status: Success │\n│ Executed Epoch: 1 │\n│ │\n│ Created Objects: │\n│ ┌── │\n│ │ ID: 0x5d49966433ebb423f5b40bfcd0ecfdc67f1527e3b9e3a433c4ec87ae63d54ed4 │\n│ │ Owner: Immutable │\n│ │ Version: 2 │\n│ │ Digest: 6GmLYmCszFxbaLRLTyZdxTTfXG99iq8uVabfi2NaB5fQ │\n│ └── │\n│ Mutated Objects: │\n│ ┌── │\n│ │ ID: GAS-COIN-ID │\n│ │ Owner: Account Address ( PUBLISHER-ID ) │\n│ │ Version: 4 │\n│ │ Digest: G5PBJjLKJWL2J3rb8ZR4uLNgFPpyJNNXfXNoh3FDo1zK │\n│ └── │\n│ ┌── │\n│ │ ID: 0x562408a381f3f2fce9c5ea27da42953e001760aa35dbadb273dca24166657516 │\n│ │ Owner: Account Address ( PUBLISHER-ID ) │\n│ │ Version: 4 │\n│ │ Digest: 6B4pA1EcYek2pvrRoBv9jKhPmUGxhH1zZD3UcqPmxwDM │\n│ └── │\n│ Gas Object: │\n│ ┌── │\n│ │ ID: GAS-COIN-ID │\n│ │ Owner: Account Address ( PUBLISHER-ID ) │\n│ │ Version: 4 │\n│ │ Digest: G5PBJjLKJWL2J3rb8ZR4uLNgFPpyJNNXfXNoh3FDo1zK │\n│ └── │\n│ Gas Cost Summary: │\n│ Storage Cost: 9302400 MIST │\n│ Computation Cost: 1000000 MIST │\n│ Storage Rebate: 2595780 MIST │\n│ Non-refundable Storage Fee: 26220 MIST │\n│ │\n│ Transaction Dependencies: │\n│ 7MdLdLYBhP6LKGf6gvuona2EQJZ1W7k3kRisrapmzQ5m │\n│ 8etH8jq78aKDHwL9ZnmAMhra62Q9vcPfyAcKJyXNPWvi │\n╰───────────────────────────────────────────────────────────────────────────────────────────────────╯\n╭─────────────────────────────╮\n│ No transaction block events │\n╰─────────────────────────────╯\n\n╭──────────────────────────────────────────────────────────────────────────────────────────────────╮\n│ Object Changes │\n├──────────────────────────────────────────────────────────────────────────────────────────────────┤\n│ Mutated Objects: │\n│ ┌── │\n│ │ ObjectID: GAS-COIN-ID │\n│ │ Sender: PUBLISHER-ID │\n│ │ Owner: Account Address ( PUBLISHER-ID ) │\n│ │ ObjectType: 0x2::coin::Coin<0x2::sui::SUI> │\n│ │ Version: 4 │\n│ │ Digest: G5PBJjLKJWL2J3rb8ZR4uLNgFPpyJNNXfXNoh3FDo1zK │\n│ └── │\n│ ┌── │\n│ │ ObjectID: 0x562408a381f3f2fce9c5ea27da42953e001760aa35dbadb273dca24166657516 │\n│ │ Sender: PUBLISHER-ID │\n│ │ Owner: Account Address ( PUBLISHER-ID ) │\n│ │ ObjectType: 0x2::package::UpgradeCap │\n│ │ Version: 4 │\n│ │ Digest: 6B4pA1EcYek2pvrRoBv9jKhPmUGxhH1zZD3UcqPmxwDM │\n│ └── │\n│ Published Objects: │\n│ ┌── │\n│ │ PackageID: 0x5d49966433ebb423f5b40bfcd0ecfdc67f1527e3b9e3a433c4ec87ae63d54ed4 │\n│ │ Version: 2 │\n│ │ Digest: 6GmLYmCszFxbaLRLTyZdxTTfXG99iq8uVabfi2NaB5fQ │\n│ │ Modules: example │\n│ └── │\n╰──────────────────────────────────────────────────────────────────────────────────────────────────╯\n╭───────────────────────────────────────────────────────────────────────────────────────────────────╮\n│ Balance Changes │\n├───────────────────────────────────────────────────────────────────────────────────────────────────┤\n│ ┌── │\n│ │ Owner: Account Address ( PUBLISHER-ID ) │\n│ │ CoinType: 0x2::sui::SUI │\n│ │ Amount: -7706620 │\n│ └── │\n╰───────────────────────────────────────────────────────────────────────────────────────────────────╯\n\nThe result provides a new ID for the upgraded package. The package system automatically updates Published.toml with the new package address and version. You do not need to manually edit any manifest files after upgrading.\n\nUpgrade considerations\nUpgrade requirements\nUpgrading\nMigrating users to the latest versionVersioned shared objects\nExtensions\n\nExample\n\nWas this page helpful?","tokens":6341,"crawled_at":1791196026075}
+{"id":10588,"url":"https://www.metaplex.com/docs/smart-contracts/bubblegum-v2/reading-inherited-royalties","domain":"www.metaplex.com","chapter":"docs","title":"Reading Inherited Royalties - Bubblegum V2 - Metaplex","text":"Summary\nBubblegum V2 can store seller fees as an inherit sentinel (65535) on the leaf and resolve the effective rate from the MPL-Core collection's Royalties plugin. DAS puts collection-resolved values on the main fields (for display) and exposes leaf values on _raw fields (for hashing).\nUse main fields (royalty.basis_points, creators) for royalty UI and payout display\nUse _raw fields (royalty.basis_points_raw, creators_raw) for proofs, hashing, and write instructions\nNon-inherited assets are unchanged — _raw / inherited are omitted\nThis page is for any client that reads getAsset / DAS responses — wallets, marketplaces, indexers, analytics, and apps. For minting and updating inherited cNFTs, see Minting and Updating.\nWhen it applies\nA cNFT is using inherited royalties when:\nIt is a Bubblegum V2 asset in an MPL-Core collection with the Royalties plugin, and\nThe leaf seller fee is the inherit sentinel 65535 (0xffff)\nDAS signals this with royalty.inherited: true and royalty.basis_points_raw: 65535 when the collection royalty can be resolved onto the main fields.\nField map\nDisplay values and leaf values live on different DAS fields, and writes must use the leaf values.\nUse caseFields\nDisplay rate / royalty UI\nroyalty.basis_points, royalty.percent\n\nDisplay payees / payout splits\ncreators\n\nHashing, merkle proofs, write instructions\nroyalty.basis_points_raw, creators_raw\n\nDetect inherit mode\nroyalty.inherited (or basis_points_raw === 65535)\n\nExample DAS response (inherited)\nAn inherited asset returns the collection's resolved rate on basis_points and the 65535 sentinel on basis_points_raw.\n\"royalty\": {\n\n\"royalty_model\": \"creators\",\n\n\"target\": null,\n\n\"percent\": 0.075,\n\n\"basis_points\": 750,\n\n\"basis_points_raw\": 65535,\n\n\"inherited\": true,\n\n\"primary_sale_happened\": false,\n\n\"locked\": false\n\n},\n\n\"creators\": [\n\n{\n\n\"address\": \"CJkzXwVwqiaSvMuRb3obrZHdrPFjCMBJBDrjspn72tDv\",\n\n\"share\": 100,\n\n\"verified\": true\n\n}\n\n],\n\n\"creators_raw\": []\n\nbasis_points: 750 is the collection rate to show users (7.5%).\nbasis_points_raw: 65535 is the on-chain sentinel used in the leaf data hash — not a 655.35% royalty.\ncreators are collection Royalties plugin payees; creators_raw: [] is the leaf creators array for hashing.\nIf the collection cannot be resolved, basis_points may fall back while basis_points_raw remains 65535.\nDetection and display helpers\nThese three helpers cover the operations that differ for inherited royalties: detecting inheritance, recovering the leaf value for writes, and picking the right creator list.\nconst INHERIT = 0xffff // 65535\n\nfunction isInheritedRoyalty(royalty: {\n\nbasis_points: number\n\nbasis_points_raw?: number | null\n\ninherited?: boolean | null\n\n}): boolean {\n\nif (royalty.inherited === true) return true\n\nif (royalty.basis_points_raw != null) {\n\nreturn royalty.basis_points_raw === INHERIT\n\n}\n\n// Older DAS versions return neither field and surface the sentinel\n\n// directly in basis_points. Without this, 65535 reads as a 655.35% fee.\n\nreturn royalty.basis_points === INHERIT\n\n}\n\nfunction leafBasisPoints(royalty: {\n\nbasis_points: number\n\nbasis_points_raw?: number | null\n\ninherited?: boolean | null\n\n}): number {\n\nif (royalty.basis_points_raw != null) return royalty.basis_points_raw\n\nif (royalty.inherited) return INHERIT\n\nreturn royalty.basis_points\n\n}\n\nfunction leafCreators(asset: {\n\ncreators: Array<{ address: string; share: number; verified: boolean }>\n\ncreators_raw?: Array<{\n\naddress: string\n\nshare: number\n\nverified: boolean\n\n}> | null\n\n}) {\n\nreturn asset.creators_raw ?? asset.creators\n\n}\n\nWith @metaplex-foundation/digital-asset-standard-api:\nimport {\n\nSELLER_FEE_BASIS_POINTS_INHERIT,\n\nisInheritedSfbpRoyalty,\n\ngetRawSellerFeeBasisPoints,\n\ngetResolvedSellerFeeBasisPoints,\n\n} from '@metaplex-foundation/digital-asset-standard-api'\n\nconst royalty = asset.royalty\n\nif (isInheritedSfbpRoyalty(royalty)) {\n\nconst rate = getResolvedSellerFeeBasisPoints(royalty) // e.g. 750 (display)\n\nconst leaf = getRawSellerFeeBasisPoints(royalty) // 65535\n\nconst payees = asset.creators // collection payees\n\nconst leafCreators = asset.creators_raw ?? []\n\n}\n\nWhat not to do\nMost integration bugs come from showing a leaf value to users or hashing a display value into a write.\nDo not show 65535 or 6.5535% as the user-facing royalty rate — that value lives on basis_points_raw.\nDo not assume empty creators_raw means no royalty recipients; display payees are on creators.\nDo not use main basis_points / creators when recomputing leaf hashes or building Bubblegum write instructions — use basis_points_raw and creators_raw.\nOutdated DAS / marketplaces\nInherited royalties require a DAS indexer that resolves collection rates onto the main fields. On an outdated DAS endpoint, getAsset still returns the leaf as-is: royalty.basis_points ≈ 65535, creators: [], and no basis_points_raw / inherited / creators_raw.\nMarketplaces that only read those DAS asset fields for payouts may treat the asset as having no royalty recipients (or an invalid rate) and pay creators nothing. Prefer marketplaces that:\nUse an upgraded DAS that returns inherited / _raw and collection-resolved creators / basis_points, or\nRead the MPL-Core collection Royalties plugin directly for payouts\nRoyalty enforcement (who may transfer) is separate: configure the collection Royalties plugin ruleSet (ProgramAllowList / ProgramDenyList). Bubblegum does not escrow royalty payments on transfer.\n\nBubblegum SDK note\ngetAssetWithProof keeps reading compatible: metadata mirrors DAS main fields (basis_points, creators), so metadata.sellerFeeBasisPoints is the resolved collection rate when inherited. currentMetadata is leaf-canonical for writes (sentinel when inherited). Optional siblings sellerFeeBasisPointsRaw / creatorsRaw and inherited mirror DAS _raw / inherit detection. Spread ...assetWithProof into write instructions — use currentMetadata for leaf args, not display metadata. See the JavaScript SDK.\nNotes\nDAS support varies by provider. Upgraded indexers return basis_points_raw, creators_raw, and inherited; older ones omit all three and surface the 65535 sentinel directly on basis_points, so treat those fields as optional and fall back on the sentinel.\nInheritance is resolved at read time from the MPL-Core collection's Royalties plugin. Changing the collection's rate changes what DAS reports for every inheriting asset without touching any leaf.\nRoyalty enforcement is separate from royalty payment. The collection's ruleSet (ProgramAllowList / ProgramDenyList) governs which programs may transfer; Bubblegum does not escrow royalty payments on transfer.\nApplies to Bubblegum V2 (MPL-Bubblegum). V1 trees have no collection-level royalty inheritance.\nThe DAS fields on this page (basis_points_raw, creators_raw, inherited) need @metaplex-foundation/digital-asset-standard-api ≥ 2.1.0. getAssetWithProof exposes currentMetadata from @metaplex-foundation/mpl-bubblegum 5.1.0, but its sellerFeeBasisPointsRaw, creatorsRaw, and inherited siblings are not published yet — they arrive with mpl-bubblegum#173. Read them off rpcAsset until that ships.\nFAQ\nWhy does royalty.basis_points_raw show 65535?\nThat is the onchain inherit sentinel used for leaf hashing. royalty.basis_points already holds the collection rate for display.\nWhy is creators_raw empty on an inherited cNFT?\nLeaf creators must be empty when SFBP is inherited. Use creators for collection royalty payees.\nDo I need to change anything for non-inherited cNFTs?\nNo. When inheritance is not used, the _raw fields and inherited are omitted and the main royalty and creators fields behave as before.\nRelated\nFetching Compressed NFTs\nMinting — Inheriting royalties\nUpdating cNFTs — Inherited royalties\nHashing NFT Data\nDAS getAsset\nFAQ — Inherited royalties","tokens":1934,"crawled_at":1791196090966}
+{"id":10589,"url":"https://docs.sui.io/develop/testing-debugging/testing","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Testing Move Smart Contracts | Sui Documentation","text":"Sui includes a built-in test framework for MoveMoveAn open source programming language used for all activity on Sui. smart contracts. You write tests directly in your Move source files, run them with the sui move test CLI command, and use the test_scenario moduleModuleA component of a Move package that defines interaction with on-chain objects. to simulate multi-transactionTransactionA number of commands that execute on inputs to define the result of the transaction. flows. No external test runner or framework installation is required.\n\nUnit tests​\n\nA unit test is a Move function annotated with #[test]. The test runner executes each test function in isolation. If the function completes without aborting, the test passes.\n\n#[test]\nfun test_sword_create() {\nlet mut ctx = tx_context::dummy();\n\nlet sword = Sword {\nid: object::new(&mut ctx),\nmagic: 42,\nstrength: 7,\n};\n\nassert!(sword.magic() == 42 && sword.strength() == 7, 1);\n\nlet dummy_address = @0xCAFE;\ntransfer::public_transfer(sword, dummy_address);\n}\n\nKey points:\n\nCall tx_context::dummy() to create a transaction context for testing without a real transaction.\n\nObjects with the key ability contain a UID that must be created with object::new. TransferTransferChanging the owner of an asset. or destroy every objectObjectThe basic unit of storage on Sui. before the test ends to avoid resource safety errors.\n\nUse assert! to verify expected values. The second argument is an error code that appears in the test output if the assertion fails.\n\nTest-only code​\n\nUse the #[test_only] attribute to define helper functions or imports that exist only during testing. The compiler strips test-only code from production builds.\n\n#[test_only]\nuse sui::test_scenario;\n\n#[test_only]\nfun create_test_sword(ctx: &mut TxContext): Sword {\nSword {\nid: object::new(ctx),\nmagic: 10,\nstrength: 5,\n}\n}\n\nYou can also mark an entire module as test-only. Place test modules in a tests/ directory inside your packagePackageSmart contracts on Sui., or define them inline:\n\n#[test_only]\nmodule my_package::my_tests;\n\nuse my_package::my_module;\n\nNegative tests​\n\nUse #[expected_failure] to verify that a function aborts under specific conditions. This is essential for testing access control, input validation, and error handling.\n\n// Test that a specific abort code is raised\n#[test, expected_failure(abort_code = my_module::ENotAuthorized)]\nfun test_unauthorized_mint() {\n// Call a function that should abort because the sender lacks permission\nlet mut ctx = tx_context::dummy();\nmy_module::restricted_action(&mut ctx);\n}\n\nThe test passes only if the function aborts with the specified error code. If the function succeeds or aborts with a different code, the test fails.\n\nYou can also match on other failure types:\n\n#[expected_failure(abort_code = 1)]: Matches a numeric abort code.\n\n#[expected_failure(arithmetic_error, location = my_package::my_module)]: Matches an arithmetic error in a specific module.\n\n#[expected_failure] without arguments: Matches any abort (less precise, use sparingly).\n\nScenario testing with test_scenario​\n\nUnit tests execute in a single transaction context. Real Sui transactions involve multiple steps, multiple senders, and objects that move between addressesAddressA unique, anonymous identity on a blockchain network.. The test_scenario module simulates this by maintaining a virtual object store and advancing through transactions.\n\n#[test]\nfun test_sword_transactions() {\nuse sui::test_scenario;\n\nlet initial_owner = @0xCAFE;\nlet final_owner = @0xFACE;\n\n// First transaction: create a sword\nlet mut scenario = test_scenario::begin(initial_owner);\n{\nlet sword = sword_create(42, 7, scenario.ctx());\ntransfer::public_transfer(sword, initial_owner);\n};\n\n// Second transaction: transfer the sword\nscenario.next_tx(initial_owner);\n{\nlet sword = scenario.take_from_sender<Sword>();\ntransfer::public_transfer(sword, final_owner);\n};\n\n// Third transaction: verify the sword\nscenario.next_tx(final_owner);\n{\nlet sword = scenario.take_from_sender<Sword>();\nassert!(sword.magic() == 42 && sword.strength() == 7, 1);\nscenario.return_to_sender(sword);\n};\nscenario.end();\n}\n\nKey operations:\n\nOperationPurpose\ntest_scenario::begin(sender)\nStart a scenario with the given sender address\n\nscenario.next_tx(sender)\nAdvance to the next transaction with a new sender\n\nscenario.take_from_sender<T>()\nTake an owned object of type T from the current sender\n\nscenario.return_to_sender(obj)\nReturn an object to the current sender\n\ntake_shared<T>(&scenario)\nTake a shared object from the virtual store\n\nreturn_shared(obj)\nReturn a shared object to the virtual store\n\nscenario.ctx()\nGet the current transaction context\n\nscenario.end()\nEnd the scenario and clean up\n\nAlways pair take_shared with return_shared within the same transaction block. Owned objects taken with take_from_sender can be returned, transferred, or destroyed; they do not need to be returned to the sender.\n\nFor a complete walkthrough with access control, cross-module interactions, and transaction effects inspection, see the scenario testing example app.\n\nTest utilities​\n\nThe Sui framework provides several modules that simplify common testing tasks:\n\nModulePurpose\nstd::unit_test\ndestroy function for cleaning up objects in tests, plus assert_eq! and assert_ref_eq! macros for better error messages\n\nstd::debug\nprint function for debug output during test runs\n\nExample using std::unit_test::destroy to clean up an object without writing a custom destructor:\n\nuse std::unit_test;\n\n#[test]\nfun test_with_cleanup() {\nlet mut ctx = tx_context::dummy();\nlet obj = my_module::create(&mut ctx);\n\n// ... test assertions ...\n\nunit_test::destroy(obj);\n}\n\nRunning tests​\n\nRun all tests in your package with:\n\n$ sui move test\n\nThe output shows each test, its pass/fail status, and a summary:\n\nRunning Move unit tests\n[ PASS ] 0x0::example::test_sword_create\n[ PASS ] 0x0::example::test_sword_transactions\nTest result: OK. Total tests: 2; passed: 2; failed: 0\n\nFilter tests​\n\nRun a subset of tests by providing a filter string. Only tests whose fully qualified name contains the filter string run:\n\n$ sui move test sword\n\nDetailed output​\n\nUse --statistics to see gasGasThe computational cost of execution and object storage for a transaction. usage for each test:\n\n$ sui move test --statistics\n\nTest coverage​\n\nMeasure how much of your code the tests exercise:\n\n$ sui move test --coverage\n$ sui move coverage summary --test\n\n+-------------------------+\n| Move Coverage Summary |\n+-------------------------+\nModule 0000000000000000000000000000000000000000000000000000000000000000::example\n>>> % Module coverage: 92.81\n+-------------------------+\n| % Move Coverage: 92.81 |\n+-------------------------+\n\nTo see which lines are not covered, run:\n\n$ sui move coverage source --module <module_name>\n\nUncovered lines are highlighted, showing exactly where to add test coverage.\n\nFor the full list of CLI options, see the sui move CLI reference.\n\nDebugging test failures���\n\nWhen a test fails, the Move Trace Debugger lets you step through execution line by line in VS Code. Generate a trace and open it in the debugger:\n\n$ sui move test --trace\n\nThen open the trace file in VS Code with the Move extension installed. You can set breakpoints, inspect variables, and step through each instruction to find where the logic diverges from your expectations.\n\nApplication-level testing​\n\nMove tests validate contract logic in a package-local environment. For full application testing, add checks that exercise transactions, network state, client code, and deployment behavior:\n\nLocal network testing: Run a local Sui network to test transactions, object interactions, and gas costs against a real execution environment before deploying to TestnetTestnetStaging network for testing changes before production deployment..\n\nTestnet deployment: Deploy your packages to Testnet to verify behavior with real network conditions, indexing, and RPC queries.\n\nDry runs: Use sui client call --dry-run or devInspectTransactionBlock to simulate a transaction against the current network state without executing it. This catches issues like incorrect object versions or insufficient gas before you submit.\n\nSDK integration tests: Use the Sui TypeScript SDK to write integration tests that submit transactions, query state, and verify end-to-end flows from a client perspective. For an example of a full test matrix (Move contract tests, SDK unit/integration tests, and E2E tests), see the Sui Stack Messaging test suite.\n\nRelated topics\n\nSui Move CLI\nThe Sui CLI move command provides commands for working with Move source code directly from a terminal or console.\nMove Trace Debugger\nDebug Move execution traces directly in VS Code to understand how your code executes.\nConnecting to a Local Network\nConnect to a Sui local network using the Sui CLI. Use local networks to test your applications and prepare for launching them on Devnet or Testnet.\nConfigure a Sui Client\nConfigure the Sui CLI client to connect to Testnet, Devnet, or a custom network, and verify your setup is working.\n\nUnit testsTest-only code\nNegative tests\n\nScenario testing with test_scenario\nTest utilities\nRunning testsFilter tests\nDetailed output\nTest coverage\n\nDebugging test failures\nApplication-level testing\n\nWas this page helpful?","tokens":2323,"crawled_at":1791196071940}
+{"id":10590,"url":"https://forum.solana.com/t/proposal-for-introducing-a-programmatic-market-based-emission-mechanism-based-on-staking-participation-rate/3294","domain":"forum.solana.com","chapter":"governance_daos","title":"Proposal For Introducing a Programmatic, Market-Based Emission Mechanism Based on Staking Participation Rate - Governance - Solana Developer Forums","text":"Proposal For Introducing a Programmatic, Market-Based Emission Mechanism Based on Staking Participation Rate\n\nGovernance\n\nsimd\n\nkankanivishal\n\nFebruary 25, 2025, 12:03am\n\n1\n\nThis proposal is updated in Epoch 750 to change the full rollout of emissions formula from 10 epochs to 50 epochs based on community feedback. Based on rough consensus achieved on Discord, there won’t be any change to the discussion period and voting will continue as per the original schedule.\n\nAuthors: Tushar Jain, Vishal Kankani, Max Resnick\n\nBackground\n\nAs Solana matures, stakers increasingly earn SOL through mechanisms like MEV. This income stream reduces the network’s historical exclusive reliance on token emissions to attract stake and security. According to Blockworks (https://solana.blockworksresearch.com/), in Q4 2024 MEV, as measured by Jito Tips, was approximately $430M (2.1M SOL),representing massive quarter-over-quarter growth. In Q3 Jito Tips were approximately $86M (562k SOL), Q2 was approximately $117M (747k SOL), and Q1 was approximately $42M (300k SOL).\n\nGiven the level of economic activity the network has achieved and the subsequent revenue earned by stakers from MEV, now is a good time to revisit the network’s emission mechanism and evolve it from a fixed-schedule mechanism to a programmatic, market-driven mechanism.\n\nThe purpose of token emissions in Proof of Stake (PoS) networks is to attract stakers and validators to secure the network. Therefore, the most efficient amount of token issuance is the lowest rate possible necessary to secure the network.\n\nSolana’s current emission mechanism is a fixed, time-based formula that was activated on epoch 150, a year after genesis on February 10, 2021. The mechanism is not aware of network activity, nor does it incorporate that to determine the emission rate. Simply put, it’s “dumb emissions.” Given Solana’s thriving economic activity, it makes sense to evolve the network’s monetary policy with “smart emissions.”\n\nThere are two major implications of Smart Emissions:\n\n1. Smart Emissions dynamically incentivizes participation when stake drops to secure the network.\n\n2. Smart Emissions minimize SOL issuance to the Minimum Necessary Amount (MNA) to secure the network.\n\nThis is good for the Solana network and network stakers for four reasons:\n\nHigh inflation can lead to more centralized ownership. To illustrate the point, imagine a network with an exceedingly high inflation rate of 10,000%. People who do not stake are diluted and lose ~99% of their network ownership every year to stakers. The higher the inflation rate, the more network ownership is concentrated in stakers’ hands after compounding for years.\n\nReducing inflation spurs SOL usage in DeFi, which is ultimately good for the applications and stimulates new protocol development. Additionally, a high staking rate can be viewed as unhealthy for new DeFi protocols, since it means the implied hurdle rate is the inflation cost. Lowering the “risk free” inflation rate creates stimulative conditions and allows new protocols to grow.\n\nIf Smart Emissions function as designed, they will systematically reduce selling pressure as long as staking participation remains adequate. The inevitable side effect and primary downside to high token inflation is increased selling pressure. This is because some stakers in different jurisdictions have taken the interpretation that staking creates ordinary income, and therefore they must sell a portion of their staking rewards to pay taxes. This selling is a significant detriment to the network and does not benefit the network in any way. At today’s approximate 4.5% annualized inflation, at a $120 billion fully diluted valuation, new emissions amount to ~USD 5.5 billion per year.\n\nIn markets, sometimes perception is as important as reality. While SOL inflation is technically not cost to the network, others think it is, and that belief overall has a negative impact on the network. Inflation causes long-term, continual downward price pressure that negatively distorts the market’s price signal and hinders fair price comparison. To use an analogy from traditional financial markets, PoS inflation is equivalent to a publicly listed company doing a small share split every two days.\n\nHistorically, issuance curves have remained static due to Bitcoin’s immutability ethos—a “Bitcoin Hangover” so to speak. While immutability suits Bitcoin’s mission to become digital gold, it doesn’t map to Solana’s mission to synchronize the world’s state at light speed.\n\nIn summary, the current Solana emissions schedule is suboptimal given the current level of activity and fees on the network because it emits more SOL than is necessary to secure the network. An issuance curve set by diktat is not the right long-term approach for Solana. Markets are the best mechanism in the world to determine prices, and therefore, they should be used to determine Solana’s emissions.\n\nFor the sake of clarity, this proposal for SIMD-0228 is independent of other SIMDs under discussion currently. It can be executed standalone.\n\nTesting\n\nBased on our discussions with Anza and with core engineers the community call, there is an understanding that this is a straightforward technical update and poses no technical risks. Upon approval of the proposal, we will collaborate with Anza, the Solana Foundation, and the Jump/Firedancer teams on implementation.\n\nProposal\n\nWe propose updating the emissions rate formula to more accurately capture the market dynamics.\n\nList of variables:\n\nFraction of total supply staked: (s)\n\nIssuance Rate (i)\n\nValidator returns: v(s) = i/s + MEV\n\nr is the current emissions curve that automatically goes down every epoch at an annualized rate of 15% every year until it reaches 1.5% where it stops changing.\n\nThe suggested new formula and curve is:\n\nnew formula1044×436 38.3 KB\n\nnew issuance rate1044×614 37.3 KB\n\nWhen s > .5 the curve corresponds to just the first term: r(1 - sqrt(s)). This was the curve in the previous version of the SIMD. Based on community feedback, we have added the cmax(1-sqrt(2s),0) term to make the curve more aggressive when a smaller fraction of the network is staked. c is chosen such that the curve starts becoming more aggressive at s =.5, when half of the supply is staked, and surpasses the current static emission schedule of r when s = 1/3.\n\nThe derivation of c is provided in the appendix.\n\nThis yields a vote reward rate for validators with good performance of:\n\nstaking yield1044×166 11.1 KB\n\nstaking returns over time1376×812 62.1 KB\n\nTo ensure that the transition from the old static issuance schedule to this new schedule is smooth, we will interpolate between the old issuance rate and the new issuance rate over 50 epochs using the formula:\n\nnew phase-in formula1040×160 12.6 KB\n\nwhere “alpha” is a parameter that controls the speed of the transition, taking the values 1/50, 2/50, …, 49/50, 1, over the first 50 epochs before settling to the new issuance rate at = 1.\n\nissuance rate during rollout1920×1130 73.4 KB\n\nAlternatives Considered\n\nWe considered a few alternatives and decided to settle upon the above curve.\n\nAlternative Design 1: Pick another fixed curve. We rejected it because replacing one arbitrary curve with another arbitrary curve makes little sense.\n\nAlternative Design 2: Fix Target Staking Yield inclusive of emissions and MEV payments. We rejected this approach because it incentivizes MEV payments to move out of sight of the tracking mechanism, thereby rendering the design completely ineffective, and impossible to implement.\n\nAlternative Design 3: A controller function that increases or decreases inflation proportional to the magnitude of the difference between the actual staking participation rate and the target rate (for example, 50%). While this approach would have allowed for a more dynamic response to fluctuations in staking participation, it risks putting emissions back to current highs even if staking participation rate organically went below the target rate (for example, 50%)\n\nAlternative Design 4: We considered only the first term of the proposed formula above. But that left the specific edge case of existing emissions curve unaddressed. That edge case was if at a future date staking rate continues to drop, and the terminal inflation hits 1.5%, then how would the network be secure. Hence, we added the second term to let the inflation increase beyond what is implied by the current curve in such an edge case scenario.\n\nAfter considering all these options, we believe the proposed static curve is the most appropriate solution to address our inflation concerns as it is market-based, programmatic, and a function of a market variable.\n\nChanges in the spirit of this proposal\n\nShould any changes be necessary to ensure a safe and functioning implementation, such changes will be permitted without further governance requirements so long as the spirit of the proposal is maintained.\n\nVoting Process\n\nThe voting process will proceed as follows:\n\nDiscussion period: Validators are encouraged to participate in discussions to address any concerns.\n\nStake weight collection period: Stake weights will be captured and published for voting. Validators will have the opportunity to verify these weights.\n\nVote token distribution will require validators to utilize the adapted Jito Merkle Distributor tool (available at GitHub - laine-sa/solgov-distributor: A merkle-based token distributor for the Solana network that allows distributing a combination of unlocked and linearly unlocked tokens.) to claim the vote tokens corresponding to their stake weights.\n\nThree token destination accounts will be created for voting choices: Yes, No, and Abstain.\n\nValidators will have a designated period to vote by sending their tokens to the respective addresses.\n\nAfter the voting period, if the sum of Yes votes is equal to or greater than 2/3 of the total sum of Yes + No votes, the proposal will pass.\n\nThe proposal has a quorum threshold of 33%, abstentions count towards the quorum.\n\nAll announcements regarding this process will be made in the Governance category of the Solana Developer Forums.\n\nStake weights and a tally script will be available at solgov-distributor/votes at master · laine-sa/solgov-distributor · GitHub\n\nTimeline\n\nEpoch 747 - 751: Discussion period\n\nEpoch 752: Stake weights captured and published, discussion/confirmation of stake weights\n\nEpochs 753 - 755: Voting tokens available to claim, voting completes at the end of epoch 755\n\nDiscussion\n\nActive participation in discussions about this proposal is crucial. Discussions may also take place on the Solana Developer Forums or on Discord Governance channel. It’s encouraged to consolidate discussions to ensure broad participation and minimize redundancy.\n\nReferences\n\nSIMD-0228: solana-improvement-documents/proposals/0228-market-based-emission-mechanism.md at patch-1 · tjain-mcc/solana-improvement-documents · GitHub\n\n9 Likes\n\nLeapfrog\n\nFebruary 25, 2025, 5:58am\n\n2\n\nThis proposal will likely have disastrous effects on the confidence of Solana when needed most.\n\nIf inflation were to increase when investment confidence is low ie investors were destaking and selling this will magnify the panic. A volatile asset is no place for long term large investors no matter how great the staking reward … if anything the fundamental idea here should be exactly opposite of what has been proposed.\n\nAs a believer in the future of solana I’d try encourage stability of the asset price and steady market cap growth over staking rewards. There already are additional incentives to staking in solana like the transactional activity (Jito) rewards, so no need to add selling pressure and flight risk by escalating inflation in the moment stability and confidence are required most…\n\n3 Likes\n\nIceFrosTv2\n\nFebruary 25, 2025, 7:01am\n\n3\n\nThe more coins in staking, the more stable and higher the token price and the lower the inflation, and therefore the lower the APY that delegates receive.\n\nAt the same time, this does not affect competition among validators, giving an advantage to some over others, as the APY will be about the same for all.\n\nAs for doubts about capitalization and token price at critical moments, I don’t see a problem with that. Those investors who want to sell their coins in a moment of panic will do so regardless of the inflation rate at the time. But it may stop many other people from selling their coins in favor of staking. After all, if a person believes in the future of blockchain and thinks it will be a success, they are more likely to choose to make money from staking than to sell in the hope that they might be able to buy cheaper.\n\n3 Likes\n\nLeapfrog\n\nFebruary 25, 2025, 8:03am\n\n4\n\nYour assumption is that when inflation goes up people stake more. I would argue that when the inflation goes up as there is a lot of destaking - those who have yet to stake would rather just sell…\n\n3 Likes\n\nIceFrosTv2\n\nFebruary 25, 2025, 8:42am\n\n5\n\nTo each their own. I’m just speaking from my point of view. If I see 5% APY, I’m more likely to sell to avoid locking up funds. If I see 10-20% APY, I’m more likely to put it in staking, given that I can release the funds and sell within two or three days.\n\nBesides, there’s nothing stopping me from opening a hedge position. For example, even with an APY of 20%, I can throw coins into staking and open a short with the first leverage. This way I don’t care about the price fluctuations in the market, but I also take my percentage from farming\n\n2 Likes\n\nLeapfrog\n\nFebruary 25, 2025, 9:26am\n\n6\n\nSo I think the main point that we are missing is that as the system currently stands - if 300M sol staked went down to 150M sol staked (ie half) Then the inflation reward (say 5%) would suddenly be distributed to half the stake and so double the staking APY… so as it stands the reward already goes up with less stake.\n\nThe second point is that inflation rewards are often miss interpreted as earnings where as what is actually happening is a devaluing of the currency. So taking your scenario where you see 5% APY lets call it 5% inflation then you see 20%APY ie 10% inflation (as the rest is due to the inflation being distributed to less stake as pointed out above)… all that means is that every sol is decreasing in value by 10% per annum rather than 5% per annum (assuming stable market cap). So your new rewards are actually just there to keep what you had previously. The rest of the sol holders are losing money twice as fast.\n\n2 Likes\n\nbullmoosesystems\n\nFebruary 25, 2025, 2:20pm\n\n7\n\nI’ve been back and forth here, but ultimately I’m against this, mostly because I don’t think there’s a big impact, and the uncertainty created from changing the monetary policy to something that is floating is damaging for institutional investor confidence.\n\nAdditionally, it feels somewhat arbitrary here. Why is 50% stake the “pivot point”? Why not 66% or 75%? The issuance/inflation rate itself doesn’t impact price at all, it’s the 2nd order effect of stakers selling those inflation rewards. On the other hand, higher inflation rates might encourage buyers to step into the market.\n\nRegarding the tax question, those users (in many jurisdictions) can simply hold an LST to avoid the tax issue. I don’t think we should be optimizing for something that is a moving target and very different globally.\n\nThe market already naturally addresses the aim of Smart Emissions today:\n\nWhen activity is low during bear markets, stake % naturally increases. Go look at nearly every major PoS asset during any bear market and you’ll see that. When the bull market arrives, stake % naturally declines because there are more opportunities to do things with your SOL, so the “risk free” inflation rate from staking isn’t as attractive any more.\n\nWe have no clue what the “Minimum Necessary Amount” of stake is to secure the network. This proposal targets 50%, but that feels very arbitrary.\n\nUltimately, I think there’s significant value in having stable monetary policy. Once we change monetary policy once, it becomes more likely that we will change it again. Institutional investors do not like the uncertainty. Worse yet, if we change monetary policy to a floating target (albeit algo determined), then it becomes even more difficult for institutional investors to model returns and thus build valuation models. That uncertainty leads to increased discount rates and lower valuations in these valuation models.\n\nAlthough the initial, fixed monetary policy may not be “perfect”, there isn’t really a perfect monetary policy out there and there’s a real cost to the change. If we change from one thing that isn’t “perfect” to another thing that isn’t “perfect”, but incur the change cost, is it really worth it?\n\n2 Likes\n\nkankanivishal\n\nFebruary 25, 2025, 2:30pm\n\n8\n\nHi @bullmoosesystems Thanks for your response. We have updated the emissions formula to a static curve. It does not target 50% staking rate anymore. The updated formula was arrived after consulting many validators and community members in the space. It is updated in SIMD and also is above. Please let us know your thoughts on the new formula.\n\n2 Likes\n\n0x_zak\n\nFebruary 25, 2025, 4:56pm\n\n9\n\nAs a Staker, I am completely for this,\n\nBut I also understand that my faith is in the validators approving or rejecting this very important proposal. Given that the validators voted for SIMD 96, I hope this comes to pass as well, or I def. would start to get concerned about the optics and incentive alignment between stakers and validators, and yes I know I can just delegate to another validator who is in favour.\n\nbut just a general sentiment.\n\nIt is very important to not overpay for security, I really hope every validator thinks about that and the overall health of our blockchain.\n\nThanks\n\n4 Likes\n\nkankanivishal\n\nFebruary 25, 2025, 5:53pm\n\n10\n\nMain objective of this proposal is to reduce unnecessary emissions, not increase. So long as the staking rate is above 33%, SIMD-0228 proposed emissions are lower than today’s curve. At current staking participation rate of ~65%, they are ~80% lower. This increases investor confidence.\n\nOnly when staking rate starts dropping below 33% for whatever reasons, we have introduced the failsafe of incentivizing stakers. This feedback was directly sourced from community of validators looking out for network risks.\n\n3 Likes\n\nLeapfrog\n\nFebruary 25, 2025, 6:15pm\n\n11\n\nWhen staking drops below 33% the incentive is already there for the rewards naturally increase as I’ve pointed out above. No need to increase inflation at this point… or any point for that matter.\n\nkankanivishal\n\nFebruary 25, 2025, 9:45pm\n\n12\n\nit is not for just today. say 5-6 years out, if Solana inflation is at 1.5% and stake is at 33%, and activity is mild - in that edge case, it is a boost to stakers/validators to stay onboard.\n\n2 Likes\n\nXen\n\nFebruary 25, 2025, 10:28pm\n\n13\n\nThose unnecessary emissions are not that unnecessary for validators, as they must pay vote fees in SOL regardless of the network’s total stake. New or smaller validators that need to take a commission to supplement their vote fees are greatly affected.\n\nI think this will be disastrous for smaller validators and will raise the barrier to entry to a point where it excludes potential new entrants based on stricter criteria, reducing innovation and decentralization. The barrier to entry is already high, and the validator count is already low (in my opinion, of course). We could argue all day about decentralization, but I don’t think the current curve is bad or arbitrary it’s the curve Solana is succeeding on and the one the market has accepted.\n\nYou do not lose to inflation if you stake. And now, there are LSTs that remove the downsides of native staking, which, let’s be honest, are very few. Epochs are getting shorter and shorter as the network becomes faster. I am no math or market expert but I think this has negative effects on the validator ecosystem.\n\n6 Likes\n\nbusinessmngr\n\nFebruary 26, 2025, 6:21am\n\n14\n\nSIMD-0228’s dynamic emission model could unintentionally push small validators out of the network by raising the break-even threshold. With only Foundation delegation and stake pools delegation, and limited liquidity from the general public, many small validators may struggle to remain profitable as rewards decrease when staking participation exceeds the target. Unlike larger validators, small ones also lack significant independent delegations, making it even harder to attract stake and sustain operations. This will likely lead to further stake centralization, as larger validators can absorb reward reductions more easily, while smaller ones will be forced to shut down.\n\nThe primary goal of SIMD-0228 is to decrease inflation and adjust the amount of SOL staked to market equilibrium. With SIMD-0123 (sharing block rewards at protocol level), validators will race to zero by competing for the best APY, potentially directing almost all block rewards to stakers. This will concentrate liquidity around those offering the highest APY, making it difficult for smaller validators to cover costs and remain competitive, similar to the current challenge of LSTs competing with JupSOL in terms of APY. We likely won’t see a significant reduction in staking, as the race to zero rewards will keep APY high.\n\nAlso, I think LSTs will lose their edge over pure staking somehow. Right now, only LSTs can distribute premium yield by sharing back block rewards. If this is equalised, the APY will be the same as native staking, and most people will choose native staking since it is more secure and avoids the additional layer of LST risk.\n\n12 Likes\n\n123test\n\nFebruary 26, 2025, 7:07am\n\n15\n\nWill this result in fewer Validators? Probably yes.\n\nsolanacompass\n\nFebruary 26, 2025, 9:54am\n\n16\n\nOne thing I feel problematic about the inflation proposal is this:\n\nStakers delegate to us to act in their interests. This means ‘securing the network’ (presumably this includes voting for things that may make it better) but also ‘earning us yield’.\n\nIt’s not really clear how much they are influenced by one concern over the other, but you could argue the high staking rate (~70% of SOL) and low defi usage (~11% of stake is liquid) implies they like the status quo and are not that interested in defi\n\nDepending on where a validator stands on this SIMD, they may or may not feel it is a vote to improve the network for all users. But a vote in favor is still actively voting to decrease their own staker’s yield. If this is a staker’s main motivation in staking, a validator is voting against their stakers’ own interests.\n\n4 Likes\n\nc2yptic\n\nFebruary 26, 2025, 6:09pm\n\n18\n\nyes. mid-small level validators ( in terms of stake ) will have extreme difficulties operating if this change comes in to place and will likely close shop\n\ndiman\n\nFebruary 26, 2025, 8:06pm\n\n19\n\na copypasta from SIMD-0228: Market-Based Emission Mechanism by tjain-mcc · Pull Request #228 · solana-foundation/solana-improvement-documents · GitHub\n\nMotivation is very weak. There are questions about many statements.\n\nI see other issues that concern me more, such as the percentage inflation rate.\n\nYou start the motivation by mentioning MEV payouts, which are not part of the protocol at all. Validators themselves are customers/clients in this case, meaning they depend on a commercial project rather than the protocol, or they can act independently (i.e., validators extract MEV themselves, and it is distributed to stakers without intermediaries), or there is real competition among MEV proxy providers in the market. For me, the way MEV currently works on Solana is already a huge problem. So making protocol changes based on the MEV issue seems like the wrong move to me. The MEV issue needs to be solved first.\n\nAnd so on. Brian mentioned several points above and did not receive answers to them. I won’t repeat.\n\nAlso, for example, I see a completely opposite conclusion from the four points in the proposal.\n\nTo me, it is obvious that reducing the APY of native staking will lead to an outflow of small stakers from native staking. This means that the share of large stakers in active staking will increase. And active native staking controls the PoS network. So the network control by large stakers will grow.\n\nTechnically, finding the balance point involves delegating and undelegating. But the problem is that fees in liquid pools and skipping one epoch in native staking make this process less active. Due to restaking (not to be confused with the currently popular marketing term), up to a month of rewards can be lost. All of this combined will cause small stakes to shift under the control of liquid pools with additional yield.\n\nSo, I see why this is bad for the Solana network.\n\nMy conclusion: perhaps this proposal is ahead of its time.\n\n1 Like\n\nbullmoosesystems\n\nFebruary 27, 2025, 5:01am\n\n20\n\nAh I see now. Thank you.\n\nRegardless, that was only a minor point. I’m mostly not in favor because I don’t like the idea of drastically changing the monetary policy for an unclear set of tradeoffs/advantages/disadvantages and changing it to something that itself is constantly changing. I don’t feel like we have a major issue or imminent threat to address and there are likely to be unforeseen negative consequences to changing the policy.\n\n2 Likes\n\nMaxSherwoodH2O\n\nFebruary 27, 2025, 10:30am\n\n21\n\nFirstly I want to thank the authors for this well-constructed proposal.\n\nHowever, I disagree with this proposal.\n\nWhile it’s true that many validators are arguably earning “too much” at the moment, it’s also true that many of us operated at break-even or at a loss during the years of 2022 and 2023. Block rewards and MEV were non-existent, and we depended on commission on voting rewards to survive. When the bull market started, many of us moved to a 0% voting commission fee and a 0% MEV commission fee, earning just the block rewards. But block rewards vary extremely from epoch to epoch depending on volatility in the market day-to-day. MEV is the same. Once the bull market is over, I expect block rewards and MEV to significantly decrease, requiring many validators to raise commissions and once again depend on voting /inflation in order to stay profitable.\n\nSolana is one of the few networks with a large, permissionless set of validators. However, the distribution of stake is very long-tail.\n\nimage1448×623 78.8 KB\n\nIf you imagine that the break-even point (how much stake does a validator need to break even) depends on the current MEV, block rewards, and inflation / voting rewards, it’s not hard to image a scenerio where this proposal passes, reducing inflation by 80% as stated previously, then a bear market reduces MEV and block rewards by 80% or more, and suddenly we go from 1500+ profitable validators to 150. For me, one of Solana’s strengths is it’s decentralization, (despite what the nay-sayers would have you believe) and it would be hugely bearish for the validator set to reduce by 80% or more in the name of saving 3 or 4% per year in inflation.\n\nAdditionally, I also agree with the previous points that a “dumb” curve is actually much easier to understand and model, whereas a “smart” curve is more complicated and unpredictable.\n\nI do understand the reasoning behind this proposal, but I think it would be exceptionally poor timing to pass this during the height of the bull market. I am fully supportive of revisiting this in a year’s time when we can see evidence of persistent MEV and block rewards over more than a few quarters.\n\n6 Likes\n\nnext page →\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nSIMD-0550: Proposal to Double Disinflation\n\nGovernance\n\neconomics\n\n9\n\n1983\n\nAugust 18, 2026\n\nSIMD-0411: Proposal for Doubling the Disinflation Rate\n\nGovernance\n\neconomics\n\n1\n\n3388\n\nJune 4, 2026\n\nProposal for Enabling the Reward Full Priority Fee to Validator on Solana Mainnet-beta\n\nGovernance\n\nfeature\n,\ncore\n\n76\n\n12930\n\nDecember 25, 2024\n\nSIMD-0326: Proposal for the New Alpenglow Consensus Protocol\n\nGovernance\n\ncore\n\n117\n\n11686\n\nJune 13, 2026\n\nWho votes - three proposals\n\nGovernance\n\n24\n\n2936\n\nApril 16, 2025","tokens":7044,"crawled_at":1791196082939}
+{"id":10591,"url":"https://a16zcrypto.com/posts/article/investing-in-proof-of-play","domain":"a16zcrypto.com","chapter":"research","title":"Investing in Proof of Play - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nInvesting in Proof of Play\nChris Dixon and Joshua Lu\n09.21.23\n\nTags & Share Tags\nannouncements\nannouncements & news\ngaming\ninvestments\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nComposability is one of the most powerful forces enabled by blockchains: for the first time, users can take code, assets, and items from one application and use them with another. In previous eras of the web, this was impossible because every social network, marketplace, exchange, and game engine has its own system of closed servers, but in web3 everyone shares the same open database. On-chain developers can build new smart contracts which augment an existing protocol, artists can launch derivative works, and anyone can create new frontends that render code in different ways.\n\nThese benefits extend to on-chain games: permissionless extensions, new clients, forked code, and opportunities for artists are all possible. For decades, many of the world’s most popular games have benefitted from modding and user-created plugins: Counter-Strike initially started as a mod of the 1998 game Half-Life (which itself was developed on the 1997 Quake II game engine). Sid Meier, the creator of Civilization, has said that “the strength of the modding community is, instead, the very reason the series survived.”\n\nOn-chain games bring modding from the background to the foreground – something the entire community can own.\n\nThat’s why we’re excited to announce that we’re leading a Seed investment in Proof of Play, an on-chain game studio and technology company led by Amitt Mahajan. Amitt is a brilliant founder who is uniquely native to both games and crypto: he founded MyMiniLife (acquired by Zynga), co-created the Zynga game FarmVille and was the co-founder and CTO of early NFT marketplace Rare Bits.\n\nProof of Play is focused on building fun, complex, and innovative games that push the limits of modern blockchains. Its first on-chain game, Pirate Nation, is a social role-playing game (RPG) that went live in December. On the surface, Pirate Nation looks similar to other RPG games, but under the hood it’s very different. Its on-chain game contracts act as building blocks for developers to create their own games, or extend out from the core Pirate Nation world. If you want to build a RTS shooter game for the Pirate Nation NFTs, or a dynamic sim for one of the pirate characters, you’re able to.\n\nAmitt and the entire Proof of Play team are committed to a gaming future where composability, interoperability, and permanence are at the core of gameplay: you own your assets, and anyone can create their own game on top of another. They’re expanding their studio and technology team to create immersive new games, and build decentralized infrastructure that enables players to craft and scale autonomous worlds.\n\nWe’re thrilled to be backing Proof of Play as they build towards this vision. If you’re a gamer, give Pirate Nation a try, and if you’re interested in helping Proof of Play build the future, the team is currently hiring.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investment-list/.\n\nPast performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures/ for additional important information.","tokens":1416,"crawled_at":1791196116970}
+{"id":10592,"url":"https://docs.ethena.fi/resources/general-risk-disclosures","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"General Risk Disclosures | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nPlease consider information in this Risk Disclosure Statement (“Statement”) as a general overview of the risks associated with the services offered by Ethena Labs and its affiliates (the “Services”) made for your awareness only. We do not intend to provide investment or legal advice through this Statement and make no representation that the Services described herein are suitable for you or that information contained herein is reliable, accurate or complete. We do not guarantee or make any representations or assume any liability regarding financial results based on the use of the information in this Statement, and further do not advise to rely on such information in the process of making a fully informed decision whether or not to use the Services. The risks outlined in this Statement are not exhaustive and this Statement only outlines the general nature of certain risks associated with crypto assets, and does not discuss in detail all risks associated with holding or trading crypto assets. Users should undertake their own assessment as to the suitability of using crypto assets and associated Services based on their own investigations, research and based on their experience, financial resources, and goals. You should not deal with crypto assets unless you understand their nature and the extent of your exposure to risk.\nNote that specific disclosures and terms of service will apply with respect to various offerings of Ethena Labs, which will be published separately. Users should refer to those terms in addition to the disclosures herein when deciding whether to utilize the Services.\nFor the purpose of this Statement “you”, “your”, and “User” mean a user of our services and “we”, “us”, “our”, or “Ethena”, means Ethena (BVI) Limited. Users are strongly advised to read this Risk Disclosure Statement carefully before deciding to start using the Services.\nRISK OF LOSS IN TRADING CRYPTO ASSETS CAN BE SUBSTANTIAL AND YOU SHOULD, THEREFORE, CAREFULLY CONSIDER WHETHER SUCH ACTIVITY IS APPROPRIATE FOR YOU IN LIGHT OF YOUR CIRCUMSTANCES AND FINANCIAL RESOURCES. YOU SHOULD BE AWARE OF THE FOLLOWING:\nCrypto Assets Are Not Legal Tender In Most Jurisdictions\nMost crypto assets are not backed by any central government or legal tender (except in few, discrete cases), meaning each country has different standards. There is no assurance that a person who accepts crypto assets as payment today will continue to do so in the future. Holders of crypto assets put their trust in a digital, decentralized, and partially anonymous system that relies on peer-to-peer networks and cryptography to maintain its integrity, and neither vendors nor individuals have an obligation to accept crypto assets as payment in the future;\nLoss of value, Volatility and Uncertainty of Future Performance\nThere is typically limited or no fundamental reasoning behind the pricing of crypto assets, creating the risk of volatility and unpredictability in the price of crypto assets relative to fiat currencies. Crypto assets have had historically higher price volatility than fiat currencies, including irrational and extreme moves in price as the process for valuation can be speculative and uncertain.\nLiquidity Risk\nCrypto assets can have limited liquidity that can make it difficult or impossible to sell or exit a position when desired. This can occur at any time, especially during periods of high volatility.\nMarket forces\nTrading in crypto assets may be susceptible to irrational market forces, such as speculative bubbles, manipulation, scams, and fraud.\nFinancial Crime and Cyber Attacks\nCyber crime relating to crypto assets can be more prevalent than other financial crime as the ecosystem is totally digital and traditional governance and risk mitigants may be lacking. For example, a 51% attack is an attack on a blockchain by any person or group of persons who control more than 50% of the network. Attackers with majority control of a network can interrupt the recording of new blocks, alter payment history, and subvert funds. Users are susceptible to malware and fake/hijacked addresses and other forms of cyber-attacks and Users should always take care of passwords and double check the addresses and URLs before loading software or interacting with any platform, protocol, or service.\nAbsence of Control\nEthena is not a broker, agent or advisor and has no fiduciary relationship or obligation to Users in connection with any transaction or other decision or activity undertaken by you using the Services. We do not control whether your use of the Services is consistent with your financial goals. It is up to Users to assess whether their financial resources are appropriate for their respective activity with us and risk appetite in the products and services you use.\nAvailability of Services\nWe do not guarantee that the Services will be available at any given time or that the Services will not be subject to unplanned service interruptions or network congestion. You may not be able to buy, sell, store, transfer, redeem, send, or receive crypto assets when you want to.\nTechnology Risk\nThe risks of crypto assets being transacted via new technologies (including distributed ledger technologies) include, among other things, anonymity, irreversibility of transactions, accidental transactions, transaction recording, and settlement. Transactions in crypto assets on a blockchain relies on the proper functioning of complex software, which exacerbates the risk of access to or use of crypto assets being impaired or prevented. Moreover, there is risk of failures, defects, hacks, exploits, protocol errors, or unforeseen circumstances that might occur in connection with a crypto asset or the technologies on which the crypto asset is based.\nIrreversible Transactions\nTransactions in crypto assets are generally irreversible. As a result, losses due to fraudulent or accidental transactions may not be recoverable.\nThird Party Risk\nThird parties such as payment providers, custodians, exchanges, and banking partners may be involved in the provision of the Services. You may be subject to the terms and conditions of these third parties, and Ethena cannot be responsible for any losses these third parties may cause you.\nTaxation and Disclosure of Information\nYou are responsible for determining the taxes to which you may be subject and their application when using the Services. It is your responsibility to report and pay any taxes that may arise from transactions and you acknowledge that Ethena does not provide legal or tax advice regarding such transactions. If you have concerns about your tax treatment or obligations you may wish to seek independent advice.\nYou understand that when, where, and as required by applicable law, Ethena will disclose available information relating to transactions transfers, distributions or payments to the appropriate regulatory and tax authorities or other public authorities. Similarly, when, where and as required by applicable law, Ethena will withhold taxes related to your transactions, transfers, distributions or payments.\nNo Investment and Legal Advice\nCommunications or information provided by Ethena shall not be considered or construed as investment advice, financial advice, trading advice, or any other type of advice. The User is the only party who can determine whether an investment, investment strategy or related transaction is appropriate based on his or her personal investment objectives, financial situation and risk tolerance, and shall be solely responsible for any losses or liabilities that may result.\nRegulatory Risk\nThe regulation of crypto assets and platforms is uncertain in many jurisdictions and Ethena cannot be held responsible for compliance with legal rules of countries from which customers, on their own initiative, access the Services. Moreover, changes in rules applicable to crypto assets may considerably impact on the prices of those assets and are unpredictable. You further acknowledge the above list of risks is non- exhaustive and there may also be unpredictable risks.\n\nLast updated 1 year ago\nWas this helpful?","tokens":2054,"crawled_at":1791196140848}
+{"id":10593,"url":"https://blog.trailofbits.com/categories/compilers","domain":"blog.trailofbits.com","chapter":"security_audits","title":"compilers - The Trail of Bits Blog","text":"Trail of Bits engineers contributed over 375 merged pull requests to more than 90 open-source projects in 2025, including significant work on Sigstore rekor-monitor, the Rust compiler and Clippy, pyca/cryptography’s ASN.1 API, hevm performance optimizations, PyPI Warehouse, and pwndbg.\nWe’re releasing go-panikint, a modified Go compiler that turns silent integer overflows into explicit panics. We used it to find a live integer overflow in the Cosmos SDK’s RPC pagination logic, showing how this approach eliminates a major blind spot for anyone fuzzing Go projects.\nTrail of Bits developed constant-time coding support for LLVM that prevents compilers from breaking cryptographic implementations vulnerable to timing attacks, introducing the __builtin_ct_select family of intrinsics that preserve constant-time properties throughout compilation.\nWhile Trail of Bits is known for developing security tools like Slither, Medusa, and Fickling, our engineering efforts extend far beyond our own projects. Throughout 2024, our team has been deeply engaged with the broader security ecosystem, tackling challenges in open-source tools and infrastructure that security engineers rely on every day. This year, our engineers […]\nEuroLLVM is a developer meeting focused on projects under the LLVM Foundation umbrella that live in the LLVM GitHub monorepo, like Clang and—more recently, thanks to machine learning research—the MLIR framework. Trail of Bits, which has a history in compiler engineering and all things LLVM, sent a bunch of […]\nThis post will guide you through using AddressSanitizer (ASan), a compiler plugin that helps developers detect memory issues in code that can lead to remote code execution attacks (such as WannaCry or this WebP implementation bug). ASan inserts checks around memory accesses during compile time, and crashes the program […]\nYou’ve reached computer programming nirvana. Your journey has led you down many paths, including believing that God wrote the universe in LISP, but now the truth is clear in your mind: every problem can be solved by writing one more compiler. It’s true. Even our soon-to-be artificially intelligent overlords are nothing but […]\nDespite its use for refactoring and static analysis tooling, Clang has a massive shortcoming: the Clang AST does not provide provenance information about which CPP macro expansions a given AST node is expanded from; nor does it lower macro expansions down to LLVM Intermediate Representation (IR) code. This makes the construction of […]\nClang is a marvelous compiler; it’s a compiler’s compiler! But it isn’t a toolsmith’s compiler. As a toolsmith, my ideal compiler would be an open book, allowing me to get to everywhere from anywhere. The data on which my ideal compiler would operate (files, macros, tokens), their eventual interpretation (declarations, statements, types), […]\nIntermediate languages (IRs) are what reverse engineers and vulnerability researchers use to see the forest for the trees. IRs are used to view programs at different abstraction layers, so that analysis can understand both low-level code aberrations and higher levels of flawed logic mistakes. The setback is that bug-finding tools are often pigeonholed into choosing […]\nThe naive approach to searching for patterns in source code is to use regular expressions; a better way is to parse the code with a custom parser, but both of these approaches have limitations. During my internship, I prototyped an internal tool called Syntex that does searching on Clang ASTs to avoid […]\nRellic is a framework for analyzing and decompiling LLVM modules into C code, implementing the concepts described in the original paper presenting the Dream decompiler and its successor, Dream++. It recently made an appearance on this blog when I presented rellic-headergen, a tool for extracting debug metadata from LLVM modules and turning […]\nLast week, over 500 cryptographers from around the world gathered in Amsterdam for Real World Crypto 2022, meeting in person for the first time in over two years. As in previous years, we dispatched a handful of our researchers and engineers to attend the conference, listen to talks, and schmooze observe the […]\nHave you ever wondered how a compiler sees your data structures? Learn how rellic-headergen converts complex C++ types into plain C structs for analysis.\nIn the summer of 2020, we described our work fuzzing the Solidity compiler, solc. So now we’d like to revisit this project, since fuzzing campaigns tend to “saturate,” finding fewer new results over time. Did Solidity fuzzing run out of gas? Is fuzzing a high-stakes project worthwhile, especially if […]\nTL;DR: We’re open-sourcing a new framework, blight, for painlessly wrapping and instrumenting C and C++ build tools. We’re already using it on our research projects, and have included a set of useful actions. You can use it today for your own measurement and instrumentation needs: Why would you ever want to wrap a build tool? […]\nOver the last few months, we’ve been fuzzing solc, the standard Solidity smart contract compiler, and we’ve racked up almost 20 (now mostly fixed) new bugs. A few of these are duplicates of existing bugs with slightly different symptoms or triggers, but the vast majority are previously unreported bugs in the compiler. This has been […]\nThe Trail of Bits Assurance practice has received an influx of Go projects, following the success of our Kubernetes assessment this summer. As a result, we’ve been adapting for Go projects some of the security assessment techniques and tactics we’ve used with other compiled languages. We started by understanding the design of the language, identifying […]\nWith the release of C++14, the standards committee strengthened one of the coolest modern features of C++: constexpr. Now, C++ developers can write constant expressions and force their evaluation at compile-time, rather than at every invocation by users. This results in faster execution, smaller executables and, surprisingly, safer code. Undefined behavior has been the source […]\nEach year, Trail of Bits runs a month-long winter internship aka “winternship” program. This year we were happy to host 4 winterns who contributed to 3 projects. This project comes from Carson Harmon, a new graduate from Purdue interested in compilers and systems engineering, and a new full-time member of our research practice. I set […]\nTrail of Bits has released Indurative, a cryptographic library that enables authentication of a wide variety of data structures without requiring users to write much code. Indurative is useful for everything from data integrity to trustless distributed systems. For instance, developers can use Indurative to add Binary Transparency to a package manager — so users […]\nC++ programs using exceptions are problematic for binary lifters. The non-local control-flow “throw” and “catch” operations that appear in C++ source code do not map neatly to straightforward binary representations. One could allege that the compiler, runtime, and stack unwinding library collude to make exceptions work. We recently completed our investigation into exceptions and can […]\nToday, we’re going to talk about a hard problem that we are working on as part of DARPA’s Cyber Fault-Tolerant Attack Recovery (CFAR) program: automatically protecting software from 0-day exploits, memory corruption, and many currently undiscovered bugs. You might be thinking: “Why bother? Can’t I just compile my code with exploit mitigations like stack guard, […]\nThis is the second half of our blog post on the Meltdown an Spectre vulnerabilities, describing Spectre Variant 1 (V1) and Spectre Variant 2 (V2). If you have not done so already, please review the first blog post for an accessible review of computer architecture fundamentals. This blog post will start by covering the technical […]\nIn the past few weeks the details of two critical design flaws in modern processors were finally revealed to the public. Much has been written about the impact of Meltdown and Spectre, but there is scant detail about what these attacks are and how they work. We are going to try our best to fix […]","tokens":2045,"crawled_at":1791196143967}
+{"id":10594,"url":"https://a16zcrypto.com/posts/article/investing-in-bastion","domain":"a16zcrypto.com","chapter":"research","title":"Investing in Bastion - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nInvesting in Bastion\nArianna Simpson\n09.18.23\n\nTags & Share Tags\nannouncements\nannouncements & news\ninvestments\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nWeb3 users want either useful or engaging applications and generally care little about the underlying infrastructure, but the former can’t exist without the latter. The interplay between delightful consumer applications and robust infrastructure has been a core topic of conversation in web3 circles for many years.\n\nIn the first ten years of web3 development, it has been extremely difficult for a developer or business to build exceptional user experiences. Security and usability have often ended up on opposite ends of the tradeoff spectrum, and high gas fees, slow blockchain finality times, and challenges around user education have persisted. We’ve long believed that this wouldn’t always need to be the case and that, eventually great teams would build superior products by abstracting away this complexity.\n\nThis scale of problem can’t be tackled by just anyone. Nassim Eddequiouaq and Riyaz Faizullabhoy have a long, successful history of working closely together – they’ve been at it for over seven years.\n\nNass and Riyaz first worked together at Docker, which has since become a developer favorite for accelerating the time to launch consistent, secure, and reliable applications.\n\nThey later moved to Anchorage Digital, where, as founding engineers, they worked to build the hardware-backed private key storage platform that would eventually become the technology underpinning the first federally chartered crypto bank. Sometime later, they designed and spearheaded wallet infrastructure and custody at Meta’s cryptocurrency wallet, Novi.\n\nMost recently, Nass and Riyaz worked with us as CTO and CISO at a16z crypto, where we got to work closely with them. When they told us about their ambitions for Bastion, the decision to invest was easy.\n\nLaunching today, Bastion helps companies seamlessly integrate web3 infrastructure into enterprise technologies through a compliant, white-label platform. The Bastion platform focuses on three core pillars: ownership & monetization of digital goods, smart transaction routing, and customer analytics.\n\nWe believe in Nass and Riyaz’s vision of making web3 safe and accessible for companies in every industry and are extremely excited to support them in making it a reality.\n\nWelcome, Bastion!\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investment-list/.\n\nPast performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures/ for additional important information.","tokens":1261,"crawled_at":1791196156439}
+{"id":10595,"url":"https://docs.ethena.fi/resources/terms-of-service","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Terms of Service | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nLast Revised August 2025\nThese Terms of Service (these “Terms”) explain the terms and conditions by which you may access and use our website, www.ethena.fi (the “Website”), operated by or on behalf of Ethena (BVI) Limited (Registration number 2127704, Craigmuir Chambers, PO Box 71, Road Town, Tortola, VG1110, BVI, inclusive with its affiliates, the “Company”, “we” or “us”), our App (as defined below), and any other Services provided by the Company, including any related content, tools, documentation, features and functionality collectively the “Services”.\nThese Terms govern your access to and use of the Services. Please read these Terms carefully, as they include important information about your legal rights. By accessing and/or using the Services, you are agreeing to these Terms. If you do not understand or agree to these Terms, please do not use the Services.\nFor purposes of these Terms, “you” and “your” means you as the user of the Services. If you use the Services on behalf of a company or other entity then “you” includes you and that entity, and you represent and warrant that (a) you are an authorized representative of the entity with the authority to bind the entity to these Terms, and (b) you agree to these Terms on the entity's behalf.\nFor terms applicable to USDe, please refer to the relevant USDe Terms and Conditions.\n1. The Services\n1.1 Services. The Services provide an interface (the “App”) that displays data for the purpose of enabling users to interface, via a third-party wallet application (e.g., Metamask), with certain components of a set of open-sourced smart contracts deployed on decentralized blockchains, namely the “staking” mechanism inherent to the Ethena Protocol. The set of smart contracts maintained and operated by the Company and the Ethena Foundation and its affiliates, collectively with off-chain infrastructure (e.g., off-exchange custody solutions and exchange relationships) maintained and operated by the Company and its affiliates, are referred to herein as the “Protocol”. In addition, the App displays data for the purpose of enabling users to interface, via a third-party wallet application, with certain components of open-sourced smart contract systems deployed on decentralized blockchains, such as certain liquidity pools on Curve Finance and Uniswap (the “Third Party Protocols”).\nDocumentation relevant to the Services, the App, and the Protocol are available at docs.ethena.fi (the “Documentation”). The Protocol itself is not part of the Services, and your use of the Protocol is entirely at your own risk. Additionally, the third party technologies required to be used or interacted with in order to interact with the Protocol, including but not limited to a Wallet (as defined below, and collectively the “Third-Party Tools”), are not part of the Services, and your use of such Third-Party Tools are entirely at your own risk. The App is separate and distinct from the Protocol and any Third-Party Tools and is not essential for the purpose of accessing or otherwise interacting with the Protocol. The App merely displays blockchain data and provides a web application that reduces the complexity of using the Third-Party Tools to otherwise interact with the Protocol. Activity on the Protocol is conducted via permissionless smart contracts as well as certain aspects of off-chain infrastructure detailed in the Documentation and maintained by the Ethena Foundation and its affiliates, and users or other developers are free to create their own interfaces to interact with the Protocol.\nWhen you utilize any data inputs provided by the App to execute transactions, you are interacting with public blockchains, which provide transparency into your transactions. The Company does not control and is not responsible for any information you make public on any public blockchain by taking actions utilizing data provided by the App or the Services.\nDistributions of ENA Tokens, including but not limited to airdrops or other rewards programs displayed on the App (including, but not limited, to, smart contracts within which certain tokens may be locked, and the maintenance of rewards balances), are managed by Ethena OpCo Ltd., a wholly-owned subsidiary of the Ethena Foundation, and other independent third parties. The Company does not offer, manage, or distribute ENA Tokens and do not assume any responsibility for such programs. The App merely displays relevant data provided by Ethena OpCo Ltd. or third parties. You acknowledge and agree that such programs are separate from the Services and the Company expressly disclaims any warranties or liability related to the ENA Tokens, their distribution, or associated rewards programs.\nThe sUSDe staking smart contract, including the management and transfer of USDe rewards, is maintained by Ethena OpCo Ltd. The App displays relevant data provided by Ethena OpCo Ltd. pertaining to sUSDe, including any references to APY. The acquisition of sUSDe is not offered to persons with their habitual residence or registered office in the European Union or the European Economic Area.\nAny communications, whether via the App or other media, by Ethena Labs and its affiliates relating to sUSDe and ENA are done as a service provider to the Ethena Foundation and Ethena OpCo Ltd.\n1.2 Wallets. To use certain of the Services it may be necessary to connect a third-party digital wallet (“Wallet”) to the App. In such cases, by using a Wallet in connection with the Services, you agree that you are using the Wallet under the terms and conditions of the applicable third-party provider of such Wallet. Wallets are not associated with, maintained by, supported by or affiliated with the Company. You acknowledge and agree that we are not party to any transactions concluded while or after accessing our App, and we do not have possession, custody or control over any digital assets appearing on the App. When you interact with the App, you retain control over your digital assets at all times. The Company accepts no responsibility or liability to you in connection with your use of a Wallet or data provided by the App in consummating transactions using a Wallet, and makes no representations and warranties regarding how the Services will interact with any specific Wallet. The private keys and/or seed phrases necessary to access the assets held in a Wallet are not held by or known to the Company. The Company has no ability to help you access or recover your private keys and/or seed phrases for your Wallet, so please keep them in a safe place.\n1.3 Updates; Monitoring. We may make any improvements, modifications or updates to the Services, including but not limited to changes and updates to the underlying software, infrastructure, security protocols, documentation, technical configurations or service features (the “Updates”) from time to time. Your continued access to and use of the Services are subject to such Updates and you shall accept any patches, system upgrades, bug fixes, feature modifications, or other maintenance work that arise out of such Updates. We are not liable for any failure by you to accept and use such Updates in the manner specified or required by us. Although the Company is not obligated to monitor access to or participation in the Services, it has the right to do so for the purpose of operating the Services, to ensure compliance with the Terms and to comply with applicable law or other legal requirements.\n1.4 Fees. While the Company does not presently charge any fees for the Services or the App, transactions executed by you utilizing data provided by the App and your use of the Services may cause you to incur fees such as blockchain gas or similar network fees, as well as fees charged by the Protocol, if any, and Third Party Protocols. All such fees displayed within your Wallet utilizing data inputs provided by the App are merely estimates and may not reflect actual costs incurred in broadcasting a transaction for execution according to the applicable consensus mechanism. Additionally, your external Wallet provider may impose a fee. We are not responsible for any fees charged by a third party. Due to the nature of distributed, public blockchains, transactions executed by you utilizing data provided by the App and the Services are non-refundable and the Company is not able to alter or mitigate any such fees. You will be responsible for paying any and all taxes, duties and assessments now or hereafter claimed or imposed by any governmental authority associated with your use of the Services, the App, the Protocol, and Third-Party Protocols. In certain cases, your transactions may not be successful due to an error with the blockchain or the Wallet, or due to changes in the distributed blockchain environment (e.g., during a spike in demand for block space and/or activity on the relevant network). We accept no responsibility or liability to you for any such failed transactions, or any transaction or gas fees that may be incurred by you in connection with such failed transactions.\n2. Who May Use the Services. You must be 18 years of age or older and not be a Prohibited Person to use the Services. A “Prohibited Person” is any person or entity that is (a) listed on (i) any U.S. Government list of prohibited or restricted parties, including the U.S. Treasury Department's list of Specially Designated Nationals or the U.S. Department of Commerce Denied Persons List or Entity List; (ii) the EU consolidated list of persons, groups and entities subject to financial sanctions; (iii) the UK Consolidated List of Financial Sanctions Targets; or (iv) any of Switzerland's respective sanctions lists, (b) located or organized in any U.S. embargoed countries or any country that has been designated by the U.S. Government as “terrorist supporting”, (c) a citizen, resident, or organized in, the following jurisdictions (the “Prohibited Jurisdictions”): Abkhazia, Afghanistan, Angola, Belarus, Burundi, Central African Republic, Congo, Cuba, Crimea, Ethiopia, Guinea-Bissau, Iran, Ivory Coast (Cote D’Ivoire), Lebanon, Liberia, Libya, Mali, Burma (Myanmar), Nicaragua, North Korea, Northern Cyprus, Russia, Somalia, Somaliland, South Ossetia, South Sudan, Sudan, Syria, Ukraine (Donetsk and Luhansk regions), United States, Venezuela, Yemen, Zimbabwe; (d) otherwise a party with which the Company is prohibited to deal under the laws of the U.S., the EU (or any of its Member States), the UK, or any applicable foreign jurisdiction, or (e) owned or controlled by such persons or entities listed in (a)-(d). The Company may utilize certain tools, such as IP-based geofencing, to enforce the above restrictions. By using the Services and/or the App, you represent that you are not a Prohibited Person.\nYou acknowledge and agree that you are solely responsible for complying with all applicable laws of the jurisdiction you are located or accessing the Services from in connection with your use of the Services. By using the Services, you represent and warrant that you meet these requirements and will not be using the Services for any illegal activity or to engage in the prohibited activities in Section 5.3. We may require you to provide additional information and documents regarding your use of the Services, including in case of application of any applicable law or regulation, including laws related to anti-money laundering or for countering the financing of terrorism, or the request of any competent authority. We may also require you to provide additional information or documents in cases where we have reason to believe: (i) that your Wallet is being used for illegal money laundering or for any other illegal activity; or (ii) you have concealed or reported false identification information or other details.\n3. Location of Our Privacy Policy Our Privacy Policy describes how we handle the information you provide to us when you use the Services. For an explanation of our privacy practices, please visit our Privacy Policy located at https://docs.ethena.fi/resources/privacy-policy.\n4. Rights We Grant You\n4.1 Right to Use Services. We hereby permit you to use the Services for your personal non-commercial use only, provided that you comply with these Terms in connection with all such use. If any software, content or other materials owned or controlled by us are distributed to you as part of your use of the Services, we hereby grant you, a personal, non-assignable, non-sublicensable, non-transferrable, and non-exclusive right and license to access and display such software, content, and materials provided to you as part of the Services, in each case for the sole purpose of enabling you to use the Services as permitted by these Terms. Your access and use of the Services may be interrupted from time to time for any of several reasons, including, without limitation, the malfunction of equipment, periodic updating, maintenance or repair of the Service or other actions that Company, in its sole discretion, may elect to take.\n4.2 Restrictions On Your Use of the Services. You may not do any of the following in connection with your use of the Services, unless applicable laws or regulations prohibit these restrictions or you have our written permission to do so: (a) download, modify, copy, distribute, transmit, display, perform, reproduce, duplicate, publish, license, create derivative works from, or offer for sale any information contained on, or obtained from or through, the Services, except for temporary files that are automatically cached by your web browser for display purposes, or as otherwise expressly permitted in these Terms; (b) duplicate, decompile, reverse engineer, disassemble or decode the Services (including any underlying idea or algorithm), or attempt to do any of the same; (c) use, reproduce or remove any copyright, trademark, service mark, trade name, slogan, logo, image, or other proprietary notation displayed on or through the Services; (d) use automation software (bots), hacks, modifications (mods) or any other unauthorized third-party software designed to modify the Services; (e) exploit the Services for any commercial purpose, including without limitation communicating or facilitating any commercial advertisement or solicitation; (f) access or use the Services in any manner that could disable, overburden, damage, disrupt or impair the Services or interfere with any other party's access to or use of the Services or use any device, software or routine that causes the same; (g) attempt to gain unauthorized access to, interfere with, damage or disrupt the Services or the computer systems, wallets, accounts, protocols or networks connected to the Services; (h) circumvent, remove, alter, deactivate, degrade or thwart any technological measure or content protections of the Services or the computer systems, wallets, accounts, protocols or networks connected to the Services; (i) use any robot, spider, crawler or other automatic device, process, software or query that intercepts, “mines,” scrapes, or otherwise accesses the Services to monitor, extract, copy, or collect information or data from or through the Services, or engage in any manual process to do the same; (j) introduce any viruses, trojan horses, worms, logic bombs or other materials that are malicious or technologically harmful into our systems; (k) submit, transmit, display, perform, post or store any content that is inaccurate, unlawful, defamatory, obscene, lewd, lascivious, filthy, excessively violent, pornographic, invasive of privacy or publicity rights, harassing, threatening, abusive, inflammatory, harmful, hateful, cruel or insensitive, deceptive, or otherwise objectionable, use the Services for illegal, harassing, bullying, unethical or disruptive purposes, or otherwise use the Services in a manner that is obscene, lewd, lascivious, filthy, excessively violent, harassing, harmful, hateful, cruel or insensitive, deceptive, threatening, abusive, inflammatory, pornographic, inciting, organizing, promoting or facilitating violence or criminal or harmful activities, defamatory, obscene or otherwise objectionable; (l) violate any applicable law or regulation in connection with your access to or use of the Services; or (m) access or use the Services in any way not expressly permitted by these Terms.\n4.3 Interactions with Other Users on the Services. You are responsible for your interactions with other users on or through the Services. While we reserve the right to monitor interactions between users, we are not obligated to do so, and we cannot be held liable for your interactions with other users, or for any user's actions or inactions. If you have a dispute with one or more users, you release us (and our affiliates and subsidiaries, and our and their respective officers, directors, employees and agents) from claims, demands and damages (actual and consequential) of every kind and nature, known and unknown, arising out of or in any way connected with such disputes. In entering into this release you expressly waive any protections (whether statutory or otherwise) that would otherwise limit the coverage of this release to include only those claims which you may know or suspect to exist in your favor at the time of agreeing to this release.\n5. Ownership and Content\n5.1 Ownership of the Services. The Services, including their “look and feel” (e.g., text, graphics, images, logos), proprietary content, information and other materials, are protected under copyright, trademark and other intellectual property laws. You agree that the Company and/or its licensors own all right, title and interest in and to the Services (including any and all intellectual property rights therein) and you agree not to take any action(s) inconsistent with such ownership interests. We and our licensors reserve all rights in connection with the Services and its content, including, without limitation, the exclusive right to create derivative works.\n5.2 Ownership of Trademarks. The Company's name, trademarks and logos and all related names, logos, product and service names, designs and slogans are trademarks of the Company or its affiliates or licensors. Other names, logos, product and service names, designs and slogans that appear on the Services are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by us.\n5.3 Ownership of Feedback. We welcome feedback, bug reports, comments and suggestions for improvements to the Services (“Feedback”). You acknowledge and expressly agree that any contribution of Feedback does not and will not give or grant you any right, title or interest in the Services or in any such Feedback. All Feedback becomes the sole and exclusive property of the Company, and the Company may use and disclose Feedback in any manner and for any purpose whatsoever without further notice or compensation to you and without retention by you of any proprietary or other right or claim. You hereby assign to the Company any and all right, title and interest (including, but not limited to, any patent, copyright, trade secret, trademark, show-how, know-how, moral rights and any and all other intellectual property right) that you may have in and to any and all Feedback.\n6. Third Party Services and Materials. The Services, through the App, may provide data relevant to the Third-Party Protocols. The Services may display, include or make available content, data, information, applications or materials from third parties (“Third-Party Materials”) or provide links to certain third party websites. The Company does not endorse any Third-Party Materials or the use of any provider of any Third-Party Protocols. You agree that your access and use of such Third-Party Protocols and Third-Party Materials (e.g., services like Telegram or protocols like The Open Network (TON)) is governed solely by the terms and conditions of such Third-Party Protocols and Third-Party Materials, as applicable. The Company is not responsible or liable for, and make no representations as to any aspect of such Third-Party Materials and Third-Party Protocols, including, without limitation, their content, operation, or the manner in which they handle, protect, manage or process data or any interaction between you and the provider of such Third-Party Protocols. The Company is not responsible for examining or evaluating the content, accuracy, completeness, availability, timeliness, validity, copyright compliance, legality, decency, quality, risk, functionality, safety, or any other aspect of such Third Party Protocols or Third Party Materials or websites. You irrevocably waive any claim against the Company with respect to such Third-Party Protocols and Third-Party Materials. We are not liable for any damage or loss caused or alleged to be caused by or in connection with your enablement, access or use of any such Third-Party Protocols or Third-Party Materials, or your reliance on the privacy practices, data security processes or other policies of such Third-Party Protocols. Third-Party Protocols, Third-Party Materials and links to other websites are provided solely as a convenience to you.\n7. Disclaimers, Limitations of Liability and Indemnification\n7.1 Disclaimers. Your access to and use of the Services and the Protocol are at your own risk. You understand and agree that the Services are provided to you on an “AS IS” and ��AS AVAILABLE” basis. Without limiting the foregoing, to the maximum extent permitted under applicable law, the Company, its parents, affiliates, related companies, officers, directors, employees, agents, representatives, partners and licensors (the “Company Entities”), and Multisig Members (as defined below) DISCLAIM ALL WARRANTIES AND CONDITIONS, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING WITHOUT LIMITATION ANY WARRANTIES RELATING TO TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, USAGE, QUALITY, PERFORMANCE, SUITABILITY OR FITNESS OF THE SERVICES AND THE PROTOCOL FOR ANY PARTICULAR PURPOSE, OR AS TO THE ACCURACY, QUALITY, SEQUENCE, RELIABILITY, WORKMANSHIP OR TECHNICAL CODING THEREOF, OR THE ABSENCE OF ANY DEFECTS THEREIN WHETHER LATENT OR PATENT. The Company Entities and MultiSig Members make no warranty or representation and disclaim all responsibility and liability for: (a) the completeness, accuracy, availability, timeliness, security or reliability of the Services and the Protocol; (b) any harm to your computer system, loss of data, or other harm that results from your access to or use of the Services or the Protocol; (c) the operation or compatibility with any other application or any particular system or device, including any Wallets; and (d) whether the Services or the Protocol will meet your requirements or be available on an uninterrupted, secure or error-free basis.\nThe Company's affiliate in Italy, Ethena Italia S.r.l., holds a VASP registration with the Italian Organismo Agente E Mediatori as a service provider. Aside from this registration, the Company and its affiliates are not registered in any capacity with any other regulatory body in any jurisdiction. You understand and acknowledge that we do not broker trading orders on your behalf, match orders for buyers and sellers of securities or any other assets, or offer any products, financial or otherwise, for sale or distribution. We also do not facilitate the execution or settlement of your transactions, which occur entirely on public distributed blockchains. The App is strictly a means by which users may construct transaction data to be utilized by the individual user by executing transactions utilizing Wallets.\nNo advice or information, whether oral or written, obtained from the Company Entities or through the Services, will create any warranty or representation not expressly made herein. You agree and understand that all transfers, staking, or other actions you perform utilizing transaction data provided by the App are considered unsolicited, which means that you have not received any investment advice from us in connection with any such action, we have not actively solicited your use of the Services, and that we do not conduct a suitability review of any such action.\nAll information provided by the App and our Services is for informational purposes only and should not be construed as investment advice. You should not take, or refrain from taking, any action based on any information contained in the App or obtained via the Services. We do not make any investment recommendations to you or opine on the merits of any investment transaction or opportunity. You alone are responsible for determining whether any investment, investment strategy or related transaction is appropriate for you based on your personal investment objectives, financial circumstances, and risk tolerance.\n7.2 Limitations of Liability. TO THE EXTENT NOT PROHIBITED BY LAW, YOU AGREE THAT IN NO EVENT WILL THE COMPANY ENTITIES OR MULTISIG MEMBERS BE LIABLE (A) FOR DAMAGES OF ANY KIND, INCLUDING DIRECT, INDIRECT, SPECIAL, EXEMPLARY, INCIDENTAL, CONSEQUENTIAL OR PUNITIVE DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, LOSS OF USE, DATA OR PROFITS, BUSINESS INTERRUPTION OR ANY OTHER DAMAGES OR LOSSES, ARISING OUT OF OR RELATED TO YOUR USE OR INABILITY TO USE THE SERVICES), HOWEVER CAUSED AND UNDER ANY THEORY OF LIABILITY, WHETHER UNDER THESE TERMS OR OTHERWISE ARISING IN ANY WAY IN CONNECTION WITH THE SERVICES OR THESE TERMS AND WHETHER IN CONTRACT, STRICT LIABILITY OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) EVEN IF THE COMPANY ENTITIES HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE, OR (B) FOR ANY OTHER CLAIM, DEMAND OR DAMAGES WHATSOEVER RESULTING FROM OR ARISING OUT OF OR IN CONNECTION WITH THESE TERMS OR THE DELIVERY, USE OR PERFORMANCE OF THE SERVICES. THE COMPANY ENTITIES' TOTAL LIABILITY TO YOU FOR ANY DAMAGES FINALLY AWARDED SHALL NOT EXCEED ONE HUNDRED DOLLARS ($100.00). SOME JURISDICTIONS (SUCH AS THE STATE OF NEW JERSEY) DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE EXCLUSION OR LIMITATION MAY NOT APPLY TO YOU.\n7.3 Assumption of Risks.\n(a) By using the Services, you represent that you have sufficient knowledge and experience in business and financial matters, including a sufficient understanding of blockchain technologies, cryptocurrencies and other digital assets, storage mechanisms (such as Wallets), and blockchain-based software systems to be able to assess and evaluate the risks and benefits of the Services contemplated hereunder, and will bear the risks thereof, including loss of all amounts paid, and the risk that the cryptocurrencies and other digital assets may have little or no value. You acknowledge and agree that there are risks associated with purchasing and holding cryptocurrency, using blockchain technology and staking cryptocurrency. These include, but are not limited to, risk of losing access to cryptocurrency due to slashing, loss of private key(s), custodial error or purchaser error, risk of mining or blockchain attacks, risk of hacking and security weaknesses, risk of unfavorable regulatory intervention in one or more jurisdictions, risk related to token taxation, risk of personal information disclosure, risk of uninsured losses, volatility risks, and unanticipated risks. You acknowledge that cryptocurrencies and other similar digital assets are neither (i) deposits of or guaranteed by a bank nor (ii) insured by the FDIC or by any other governmental agency.\n(b) There are certain multi-signature crypto wallets (the “MultiSigs”, and the signatories to such MultiSigs, the “MultiSig Members”) that have certain controls related to the Protocol, that may include, but are not limited to, the ability to pause certain functionality of the Protocol, implement, or influence upgrades to the Protocol (or any aspect thereof) and certain other controls of the functionality of the Protocol as described in the Documentation or in public communications. While the MultiSigs may have MultiSig Members that are employed or engaged by the Company, they may be controlled partially or entirely by MultiSig Members that are unaffiliated third parties over which we have no or limited control. We will not be able to control the actions of such MultiSig Members if they are not employed or engaged by us and thus certain MultiSigs will be outside of our control. The Company therefore cannot be held liable for any action, or inaction, relating to such a MultiSig.\n(c) The regulatory regimes governing blockchain technologies, cryptocurrencies and other digital assets are uncertain, and new regulations or policies may materially adversely affect the potential utility or value of the Services, the Protocol, Third-Party Protocols, cryptocurrencies and other digital assets, or the ability of the Company to continue to provide or support such Services and/or the App. Additionally, taxation of activities and transactions in cryptocurrencies and other digital assets is uncertain in certain cases in certain jurisdictions. You are encouraged to consult with your own tax advisor with respect to potential tax implications associated with utilizing the Services, the App, and the Protocol.\n(d) We cannot control or influence market sentiment or liquidity or how third-party services or platforms support, quote, restrict or provide access to, or value cryptocurrencies and other digital assets and we expressly deny and disclaim any liability to you and deny any obligations to indemnify or hold you harmless for any losses you may incur as a result of fluctuations in the value of cryptocurrencies or other digital assets.\n(e) Smart contracts execute automatically when certain conditions are met. Transactions on blockchains or using smart contracts often cannot be stopped or reversed, so vulnerabilities in the programming, design, or implementation of a blockchain, the Protocol, any deployed smart contracts, or a Third-Party Protocol may arise due to hacking or other security incidents and could result in significant adverse effects, including but not limited to, significant volatility or loss of any digital assets elected into the Protocol.\n(f) The Documentation describes certain risks associated with the Protocol in detail. Please review the Documentation for additional risks associated with utilizing the Services or the App in conjunction with your use of, and access to, the Protocol. The Company hereby disclaims any and all liability associated with risks disclosed in the Documentation to the fullest extent provided by applicable law.\n7.4 Indemnification. By entering into these Terms and accessing or using the Services, you agree that you shall defend, indemnify and hold the Company Entities and MultiSig Members harmless from and against any and all claims, costs, damages, losses, liabilities and expenses (including attorneys' fees and costs) incurred by the Company Entities arising out of or in connection with: (a) your violation or breach of any term of these Terms or any applicable law or regulation; (b) your violation of any rights of any third party; (c) your misuse of the Services; or (d) your negligence or willful misconduct. If you are obligated to indemnify any Company Entity hereunder, then you agree that Company (or, at its discretion, the applicable Company Entity) will have the right, in its sole discretion, to control any action or proceeding and to determine whether Company wishes to settle, and if so, on what terms, and you agree to fully cooperate with Company in the defense or settlement of such claim.\n7.5 Third Party Beneficiaries. You and the Company acknowledge and agree that the Company Entities (other than the Company) and the MultiSig Members are third party beneficiaries of these Terms, including under Section 7 and 8.\n8. ARBITRATION AND CLASS ACTION WAIVER\n8.1 PLEASE READ THIS SECTION CAREFULLY – IT MAY SIGNIFICANTLY AFFECT YOUR LEGAL RIGHTS, INCLUDING YOUR RIGHT TO FILE A LAWSUIT IN COURT AND TO HAVE A JURY HEAR YOUR CLAIMS. IT CONTAINS PROCEDURES FOR MANDATORY BINDING ARBITRATION AND A CLASS ACTION WAIVER.\n8.2 Informal Process First. You and the Company agree that in the event of any dispute between you and the Company Entities or the MultiSig Members, either party will first contact the other party and make a good faith sustained effort to resolve the dispute before resorting to more formal means of resolution, including without limitation, any court action, after first allowing the receiving party 30 days in which to respond. Both you and the Company agree that this dispute resolution procedure is a condition precedent which must be satisfied before initiating any arbitration against you, any Company Entity or any MultiSig Members, as applicable.\n8.3 Arbitration Agreement and Class Action Waiver. After the informal dispute resolution process, any remaining dispute, controversy, or claim (collectively, “Claim”) relating in any way to the Services, including the App, any use or access or lack of access thereto, and any other usage of the Protocol even if interacted with outside of the Services or App, will be resolved by arbitration, including threshold questions of arbitrability of the Claim. You and the Company agree that any Claim including those not of a contractual nature - arising out of, related or connected to the Services, the App, or otherwise, shall be settled by arbitration under the BVI IAC Arbitration Rules (the Rules), by three arbitrators, appointed in accordance with the Rules, which are deemed to be incorporated by reference into this clause. The language of arbitration will be English. Any arbitration under these Terms will take place on an individual basis – class arbitrations and class actions are not permitted. You understand that by agreeing to these Terms, you and the Company are each waiving the right to trial by jury or to participate in a class action or class arbitration.\n8.4 Exceptions. Notwithstanding the foregoing, you and the Company agree that the following types of disputes will be resolved in a court of proper jurisdiction: (i) disputes or claims within the jurisdiction of a small claims court consistent with the jurisdictional and dollar limits that may apply, as long as it is brought and maintained as an individual dispute and not as a class, representative, or consolidated action or proceeding; (ii) disputes or claims where the sole form of relief sought is injunctive relief (including public injunctive relief); or (iii) intellectual property disputes.\n8.5 Costs of Arbitration. Payment of all filing, administration, and arbitrator costs and expenses will be governed by the Rules, except that if you demonstrate that any such costs and expenses owed by you under those rules would be prohibitively more expensive than a court proceeding, the Company will pay the amount of any such costs and expenses that the arbitrator determines are necessary to prevent the arbitration from being prohibitively more expensive than a court proceeding (subject to possible reimbursement as set forth below). Fees and costs may be awarded as provided pursuant to applicable law. If the arbitrator finds that either the substance of your claim or the relief sought in the Claim is frivolous, then the payment of all fees will be governed by the Rules. In that case, you agree to reimburse the Company for all monies previously disbursed by it that are otherwise your obligation to pay under the applicable rules.\n8.6 Opt-Out. You have the right to opt-out and not be bound by the arbitration provisions set forth in these Terms by sending written notice of your decision to opt-out to finance@ethenalabs.xyz. The notice must be sent to the Company within thirty (30) days of your first accessing the Services or agreeing to these Terms; otherwise you shall be bound to arbitrate disputes on a non-class basis in accordance with these Terms. If you opt out of only the arbitration provisions, and not also the class action waiver, the class action waiver still applies. You may not opt out of only the class action waiver and not also the arbitration provisions. If you opt-out of these arbitration provisions, the Company also will not be bound by them.\n8.7 WAIVER OF RIGHT TO BRING CLASS ACTION AND REPRESENTATIVE CLAIMS. TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW, YOU AND THE COMPANY EACH AGREE THAT ANY PROCEEDING TO RESOLVE ANY DISPUTE, CLAIM OR CONTROVERSY WILL BE BROUGHT AND CONDUCTED ONLY IN THE RESPECTIVE PARTY'S INDIVIDUAL CAPACITY AND NOT AS PART OF ANY CLASS (OR PURPORTED CLASS), CONSOLIDATED, MULTIPLE-PLAINTIFF, OR REPRESENTATIVE ACTION OR PROCEEDING (“CLASS ACTION”). YOU AND THE COMPANY AGREE TO WAIVE THE RIGHT TO PARTICIPATE AS A PLAINTIFF OR CLASS MEMBER IN ANY CLASS ACTION. YOU AND THE COMPANY EXPRESSLY WAIVE ANY ABILITY TO MAINTAIN A CLASS ACTION IN ANY FORUM. IF THE DISPUTE IS SUBJECT TO ARBITRATION, THE ARBITRATOR WILL NOT HAVE THE AUTHORITY TO COMBINE OR AGGREGATE CLAIMS, CONDUCT A CLASS ACTION, OR MAKE AN AWARD TO ANY PERSON OR ENTITY NOT A PARTY TO THE ARBITRATION. FURTHER, YOU AND THE COMPANY AGREE THAT THE ARBITRATOR MAY NOT CONSOLIDATE PROCEEDINGS FOR MORE THAN ONE PERSON'S CLAIMS, AND IT MAY NOT OTHERWISE PRESIDE OVER ANY FORM OF A CLASS ACTION. FOR THE AVOIDANCE OF DOUBT, HOWEVER, YOU CAN SEEK PUBLIC INJUNCTIVE RELIEF TO THE EXTENT AUTHORIZED BY LAW AND CONSISTENT WITH THE EXCEPTIONS CLAUSE ABOVE. IF THIS CLASS ACTION WAIVER IS LIMITED, VOIDED, OR FOUND UNENFORCEABLE, THEN, UNLESS THE PARTIES MUTUALLY AGREE OTHERWISE, THE PARTIES' AGREEMENT TO ARBITRATE SHALL BE NULL AND VOID WITH RESPECT TO SUCH PROCEEDING SO LONG AS THE PROCEEDING IS PERMITTED TO PROCEED AS A CLASS ACTION. IF A COURT DECIDES THAT THE LIMITATIONS OF THIS PARAGRAPH ARE DEEMED INVALID OR UNENFORCEABLE, ANY PUTATIVE CLASS, PRIVATE ATTORNEY GENERAL OR CONSOLIDATED OR REPRESENTATIVE ACTION MUST BE BROUGHT IN A COURT OF PROPER JURISDICTION AND NOT IN ARBITRATION.\n9. Additional Provisions\n9.1 Updating These Terms. We may modify these Terms from time to time in which case we will update the “Last Revised” date at the top of these Terms. If we make changes that are material, we will use reasonable efforts to attempt to notify you, such as by e-mail and/or by placing a prominent notice on the first page of the Website. However, it is your sole responsibility to review these Terms from time to time to view any such changes. The updated Terms will be effective as of the time of posting, or such later date as may be specified in the updated Terms. Your continued access or use of the Services after the modifications have become effective will be deemed your acceptance of the modified Terms. No amendment shall apply to a dispute for which an arbitration has been initiated prior to the change in Terms.\n9.2 Suspension; Termination. If you breach any of the provisions of these Terms, all licenses granted by the Company will terminate automatically. Additionally, the Company may, in its sole discretion, suspend or terminate your access to or use of any of the Services, with or without notice, for any or no reason, including, without limitation, (i) if we believe, in our sole discretion, you have engaged in any of the prohibited activities set forth in Section 4.2; (ii) if you provide any incomplete, incorrect or false information to us; (iii) if you have breached any portion of these Terms; (iv) if you are a Prohibited Person and/or reside in a Prohibited Jurisdiction; and/or (v) if we determine such action is necessary to comply with these Terms, any of our policies, procedures or practices, or any law rule or regulation. All sections which by their nature should survive the termination of these Terms shall continue in full force and effect subsequent to and notwithstanding any termination of this Agreement by the Company or you. Termination will not limit any of the Company's other rights or remedies at law or in equity.\n9.3 Injunctive Relief. You agree that a breach of these Terms will cause irreparable injury to the Company for which monetary damages would not be an adequate remedy and the Company shall be entitled to equitable relief in addition to any remedies it may have hereunder or at law without a bond, other security or proof of damages.\n9.4 Force Majeure. We will not be liable or responsible to you, nor be deemed to have defaulted under or breached these Terms, for any failure or delay in fulfilling or performing any of our obligations under these Terms or in providing the Services, when and to the extent such failure or delay is caused by or results from any events beyond our ability to control, including acts of God; flood, fire, earthquake, epidemics, pandemics, tsunami, explosion, war, invasion, hostilities (whether war is declared or not), terrorist threats or acts, riot or other civil unrest, government order, law, or action, embargoes or blockades, strikes, labor stoppages or slowdowns or other industrial disturbances, shortage of adequate or suitable Internet connectivity, telecommunication breakdown or shortage of adequate power or electricity, and other similar events beyond our control.\n9.5 Miscellaneous. If any provision of these Terms shall be unlawful, void or for any reason unenforceable, then that provision shall be deemed severable from these Terms and shall not affect the validity and enforceability of any remaining provisions. These Terms and the licenses granted hereunder may be assigned by the Company but may not be assigned by you without the prior express written consent of the Company. No waiver by either party of any breach or default hereunder shall be deemed to be a waiver of any preceding or subsequent breach or default. The section headings used herein are for reference only and shall not be read to have any legal effect. These Terms are governed by the laws of the British Virgin Islands, without regard to conflict of laws rules, and the proper venue for any disputes arising out of or relating to any of the same will be the courts in the British Virgin Islands.\n9.6 How to Contact Us. You may contact us regarding the Services or these Terms by e-mail at finance@ethenalabs.xyz.\n\nLast updated 1 year ago\nWas this helpful?","tokens":10607,"crawled_at":1791196160948}
+{"id":10596,"url":"https://blog.trailofbits.com/2024/03/08/out-of-the-kernel-into-the-tokens","domain":"blog.trailofbits.com","chapter":"security_audits","title":"Out of the kernel, into the tokens - The Trail of Bits Blog","text":"Page content\n\nWe’re digging up the archives of vulnerabilities that Trail of Bits has reported over the years. This post shares the story of two such issues: a denial-of-service (DoS) vulnerability hidden in JSON Web Tokens (JWTs), and an oversight in the Linux kernel that could enable circumvention of critical kernel security mechanisms (KASLR).\nUnraveling a DoS vulnerability in JOSE libraries\nJWT and JSON Object Signing and Encoding (JOSE) are expansive standards that describe the creation and use of encrypted and/or signed JSON-based tokens. While these standards are widely used and represent a significant improvement over previous solutions for identity claims, they are not without drawbacks, and have several well-known footguns, like the JWT “none” signature algorithm.\nOur finding concerns an attack that was part of a lineup of new JWT attacks presented by Tom Tervoort at BlackHat USA 2023: “Three New Attacks Against JSON Web Tokens.” The “billion hashes attack”, which results in denial-of-service due to a lack of validation in JWT key encryption, caught our colleague Matt Schwager’s attention. Upon further examination, he discovered it applied to several more libraries in the Go and Rust ecosystems: go-jose, jose2go, square/go-jose, and josekit-rs.\nThese libraries all support key encryption with PBES2, a feature meant to allow for password-based encryption of the Content Encryption Key (CEK) in JSON Web Encryption (JWE). A key is first derived from a password by using PBES2 schemes, which execute a number of PBKDF2 iterations. Then that key is used to encrypt and decrypt the token contents.\nThis wouldn’t normally be an issue, but unfortunately, the number of iterations is contained as part of the token, on the p2c header parameter, which an attacker can easily manipulate. Consider, for example, the token header shown below:\n\nFigure 1: A JWE token header indicating PBES2 key encryption with a large number of iterations\nBy using a very large iteration count in the p2c field, an attacker can cause a DoS on any application that attempts to process this token. Whoever receives and attempts to verify this token will first need to perform 2,147,483,647 PBKDF2 iterations to derive the CEK before they can even verify if the token is valid, costing significant amounts of compute time.\nWe reported the issue to the go-jose, jose2go, and josekit-rs library maintainers, and it has been fixed by limiting the maximum value usable for p2c in go-jose/go-jose on version 3.0.1 (commit 65351c27657d); on dvsekhvalnov/jose2go on version 1.6.0 (commits a4584e9dd712 and 8e9e0d1c6b39); and on hidekatsu-izuno/josekit-rs on version 0.8.5 (commits 1f3278a33f0e, 8b60bd0ea8ce, and 7e448ce66c1c). square/go-jose remains unfixed, as the library is deprecated, and users are encouraged to migrate to go-jose/go-jose.\nAlternatively, the risk can also be mitigated by not relying purely on the token’s alg parameter. After all, if your application does not expect to receive a token using PBES2 or any lesser-used algorithm, there is no reason to try to process one. jose2go allows implementing opt-in stricter validation of alg and enc parameters today, and go-jose’s next major version will require passing a list of acceptable algorithms when processing a token, allowing developers to explicitly list a set of expected algorithms.\nKASLR bypass in privilege-less containers\nNext is a vulnerability that has been fixed since 2020, but never got a CVE assigned by the Linux kernel maintainers. In the following paragraphs, we’ll go into the details of a previously unknown but fixed KASLR bypass.\nBack in 2020, Trail of Bits engineer Dominik Czarnota (aka disconnect3d) discovered a vulnerability in the Linux kernel that could expose internal pointer addresses within unprivileged Docker containers, allowing a malicious actor to bypass Kernel Address Space Layout Randomization (KASLR) for kernel modules.\nKASLR is an important defense mechanism in operating systems, primarily used to deter exploit attempts. It is a security technique that randomizes the kernel memory address locations between reboots. On top of that, kernel addresses must be hidden from userspace; otherwise, the mitigation would make no sense, as such kernel address disclosure would effectively bypass the KASLR mitigation.\nWhile there are places where kernel addresses are shown to userspace programs, on many systems they should be available only when the user has the CAP_SYSLOG Linux capability. (Capabilities split root user privileges so it is possible to be the root user, or a user with uid 0, while having a limited set of privileges.) In particular, the manual page for the CAP_SYSLOG capability reads: “View kernel addresses exposed via /proc and other interfaces when /proc/sys/kernel/kptr_restrict has the value 1.” This means that only processes that are executed with the capability CAP_SYSLOG should be able to read kernel addresses.\nHowever, Dominik discovered that this was not the case from within a Docker container where processes that are run from the root user without CAP_SYSLOG were able to observe kernel addresses. By default, Docker containers are unprivileged, which means that root users are restricted in what they can do (e.g., they cannot perform actions that require CAP_SYSLOG). This can also be demonstrated without Docker by using the capsh tool run from the root user to remove the CAP_SYSLOG capability:\n\nThe underlying cause of the issue was that the credentials were checked incorrectly. The sysctl toggle kernel.kptr_restrict indicates whether restrictions are placed on exposing kernel addresses: the value “2” means that the addresses are always hidden; “1” means that they are shown only if the user has CAP_SYSLOG; and “0” means that they are always shown. Instead of ensuring that the user had the CAP_SYSLOG capability before showing the addresses, only the value of kptr_restrict was being considered to decide whether to show or hide the addresses. The addresses were always exposed if kptr_restrict was 1, while they should have been hidden if the user did not have CAP_SYSLOG. The issue was fixed in commit b25a7c5af905.\nAfter discovering this vulnerability, we followed a coordinated disclosure process with Docker and Linux kernel security team. Dominik initially notified the Docker team about this, since he thought the vulnerability originated from Docker, and also reported other sysfs filesystem leaks (where other sysfs paths leaked information such as the names of services run outside of the container, other container IDs, and information about devices). The disclosure timeline is provided at the end of this post.\nAlthough we received only silence from Docker despite multiple requests for updates, the Linux community swiftly rectified the issue in the kernel. The KASLR bypass bug fix was backported to various Ubuntu LTS versions, while the other sysfs leaks from Docker were not fixed at all. However, Linux kernel releases before 4.19 are vulnerable to the KASLR bypass. Ubuntu 18, which uses kernel 4.15, is still vulnerable because the fix was not backported.\nDisclosure timeline for KASLR bypass in privilege-less containers\nJune 6, 2020: Reported the vulnerability to Docker.\nJune 11, 2020: Docker replied that they would probably block the sysfs paths that leaks information via the “masked paths” feature, and that the memory address disclosure should be reported to the Linux kernel developers.\nJune 11, 2020: Informed the intent to contact security@kernel.org about the kASLR bypass.\nJune 11 to June 18, 2020: Performed a deeper analysis of the kASLR bypass.\nJune 18, 2020: Reported the bug to security@kernel.org.\nJune 18, 2020: Bug confirmed by Kees Cook.\nJune 19 to June 21, 2020: Kernel developers discuss how to patch the issue.\nJune 30, 2020: Requested an update from Docker.\nJuly 3 to July 14, 2020: Patches that fix the issue land in the Linux kernel.\nJuly 11, 2020: Requested an update from Docker again about other sysfs leaks, and informed them that the KASLR bypass issue has been fixed in Linux 4.19, 5.4 and 5.7 kernels.\nDecember 3, 2020: Requested an update from Docker once again, and informed the intent to disclose the issues publicly. Docker did not reply.\nDo you need audits in 2024?\nThese two vulnerabilities are quite different: The DoS issue relates to parsing and interpreting user input, while the kernel vulnerability is an information leak (strictly speaking, it is an access control vulnerability). These differences affect the detectability of bugs: if you cause a DoS, you’ll likely notice right away because the availability of your service will be compromised. By contrast, if an attacker exploits an access control vulnerability, you probably won’t notice when your service is exploited.\nThis difference in detectability is important for automated testing. For instance, fuzzing, as showcased in the Trail of Bits Testing Handbook, typically requires the program to crash or hang. Therefore, we mostly find DoS bugs in the memory-safe programs we fuzz. Automatically finding access control bugs through fuzzing is more challenging because it requires the implementation of fuzzing invariants.\nSecurity audits are still indispensable tools for finding vulnerabilities, just like fuzzing is! Our audits integrate fuzzing whenever possible, and we look for opportunities to enforce invariants to catch nasty logic bugs.","tokens":2356,"crawled_at":1791196161985}
+{"id":10597,"url":"https://docs.sui.io/develop/transaction-payment","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Paying for Transactions | Sui Documentation","text":"Every Sui transactionTransactionA number of commands that execute on inputs to define the result of the transaction. pays for 2 things: computational execution and long-term objectObjectThe basic unit of storage on Sui. storage. How you source those funds (from coins, addressAddressA unique, anonymous identity on a blockchain network. balances, a sponsor, or at zero cost) depends on what the transaction does and who pays.\n\nMigrate to address balances​\n\nAddress balances replace UTXO-style coin selection with a single address-owned balance per coin type. Moving your app onto them is 3 steps, each covered by a section on this page and single-sourced from the canonical address-balance guides:\n\nSource funds automatically. Replace manual coin selection with coinWithBalance, which draws from address balances first and falls back to coin objects. See Coin selection with coinWithBalance.\n\nDrop gasGasThe computational cost of execution and object storage for a transaction. costs where you can. Peer-to-peer transfers of allowlisted stablecoins qualify for zero-gas execution. See Gasless stablecoin transfers.\n\nCompose multi-step flows atomically. Chain swaps, deposits, and transfers into one programmable transaction block. See Composing DeFi operations.\n\nYou do not have to migrate anything at once. Coin objects and address balances coexist, and the SDK selects between them for you. For what changes at the protocol level, balance-query fields, and backward compatibility, see Migrating from Coin to Address Balances. For the full send, withdraw, and gas API across TypeScript, Rust, CLI, and MoveMoveAn open source programming language used for all activity on Sui., see Using Address Balances.\n\nCoin selection with coinWithBalance​\n\nWhen you build a transaction with the TypeScript SDK, you rarely need to pick individual coin objects. The coinWithBalance helper (and the tx.coin() shorthand) resolves the required amount automatically:\n\nimport { Transaction, coinWithBalance } from '@mysten/sui/transactions';\n\n// Replace with a real coin type. For allowlisted stablecoins, see\n// /develop/transaction-payment/gasless-stablecoin-transfers#eligible-stablecoins\nconst USDC = '0xUSDC_PACKAGE::usdc::USDC';\n\nconst tx = new Transaction();\n\n// coinWithBalance draws from address balances first, then coin objects\nconst payment = coinWithBalance({ type: USDC, balance: 5_000_000n }); // 5 USDC\ntx.transferObjects([payment], recipient);\n\nUnder the hood:\n\nThe SDK checks the sender's address balance for the requested coin type.\n\nIf the address balance covers the amount, it creates a withdrawal, with no coin objects needed.\n\nIf the address balance is insufficient, it falls back to selecting and splitting coin objects.\n\nThis means you can build transactions without knowing which coin objects the sender owns.\n\nFor SUI gas specifically, passing an empty array to setGasPayment tells the network to draw gas from the address balance:\n\ntx.setGasPayment([]); // Gas paid from address balance — no coin lookup required\n\nsetGasPayment([]) alone is not enough for fully offline transaction building. You also need to set gasPrice, gasBudget, and ValidDuring expiration, and all transaction inputs must be resolvable without network queries (no unresolved coinWithBalance or tx.coin() intents that require balance lookups). See Paying for gas from address balances for the full set of requirements.\n\nSee Using Address Balances for the full API (TypeScript, Rust, CLI, and Move) and Gas Smashing for the legacy coin-merge approach.\n\nGas payment strategies​\n\nSui offers 4 ways to pay for gas, each suited to different use cases:\n\nStrategyWho paysUser holds SUI?Best for\nStandard gas\nUser\nYes\nGeneral transactions\n\nAddress balance gas\nUser\nYes (in address balance)\nOffline-built transactions, no coin lookup\n\nSponsored gas\nApp / relayer\nNo\nOnboarding, free-to-play, enterprise\n\nGasless stablecoin\nNobody (zero fee)\nNo\nPeer-to-peer stablecoin transfers\n\nStandard gas​\n\nThe sender provides one or more Coin<SUI> objects to cover execution and storage costs. The SDK resolves this automatically when you don't explicitly configure gas. See Gas Fees for the fee formula and budget rules.\n\nAddress balance gas​\n\nInstead of selecting coin objects, the network withdraws gas from the sender's SUI address balance. This removes the need for coin lookups at gas-selection time. To use it, set tx.setGasPayment([]) along with gasPrice, gasBudget, and ValidDuring expiration. When all other transaction inputs are also known at build time (no unresolved coinWithBalance intents), the transaction can be built fully offline. See Paying for gas from address balances for requirements.\n\nSponsored transactionsSponsored transactionWhen one address pays the gas fee for a transaction submitted by another address.​\n\nA third party (the sponsor) pays gas on behalf of the user. The user builds the transaction, and the sponsor provides gas payment. Both sign. This is ideal for onboarding new users who don't hold SUI. See Sponsored Transactions for the full flow, including data structures, sequence diagrams, and risk considerations.\n\nWith address balances, sponsored transactions become simpler: no gas coin locking risk, no coin inventory management, and the user can sign before the sponsor.\n\nGasless stablecoin transfers​\n\nPeer-to-peer transfers of allowlisted stablecoins (USDC, USDSUI, and others) execute at zero gas cost. Eligibility requires:\n\nThe PTBProgrammable transaction blocksDefine all user transactions on Sui. calls only allowlisted balance or coin operations (primarily balance::send_funds).\n\ngasPayment is empty and gasPrice = 0.\n\nNo objects are written.\n\nThe gRPCgRPC APIReplaces JSON-RPC on full nodes for data access. and GraphQL transports detect eligibility automatically during simulation and set gasBudget = 0. See Gasless Stablecoin Transfers for the full allowlist and integration guide.\n\nimport { SuiGrpcClient } from '@mysten/sui/grpc';\nimport { Transaction } from '@mysten/sui/transactions';\n\n// Replace with a real coin type. For allowlisted stablecoins, see\n// /develop/transaction-payment/gasless-stablecoin-transfers#eligible-stablecoins\nconst USDC = '0xUSDC_PACKAGE::usdc::USDC';\nconst client = new SuiGrpcClient({ network: 'mainnet', baseUrl: 'https://fullnode.mainnet.sui.io:443' });\n\nconst tx = new Transaction();\ntx.setSender(senderAddress);\ntx.moveCall({\ntarget: '0x2::balance::send_funds',\ntypeArguments: [USDC],\narguments: [tx.balance({ type: USDC, balance: 1_000_000n }), tx.pure.address(recipient)],\n});\n\n// SDK detects gasless eligibility and sets gasPrice = 0 and gasBudget = 0 automatically\nconst result = await client.signAndExecuteTransaction({ transaction: tx, signer: keypair });\n\nComposing DeFi operations​\n\nProgrammable transaction blocks (PTBs) let you chain multiple operations into a single atomic transaction. Outputs from earlier commands feed directly into later ones, with no intermediate state and no partial execution risk.\n\nSwap and transferTransferChanging the owner of an asset.​\n\nSplit a coin, swap part of it on a DEX, and transfer the result, all in one transaction:\n\nconst tx = new Transaction();\n\n// 1. Source funds using coinWithBalance (auto-selects from address balance or coins)\nconst [usdc] = tx.splitCoins(coinWithBalance({ type: USDC, balance: 200_000_000n }), [\ntx.pure.u64(200_000_000),\n]);\n\n// 2. Swap USDC → SUI through a DEX pool\nconst [sui] = tx.moveCall({\ntarget: '0xDEX_PACKAGE::router::swap_exact_input',\ntypeArguments: [USDC, '0x2::sui::SUI'],\narguments: [tx.object('0xPOOL_ID'), usdc, tx.pure.u64(0)], // 0 = min output (set real slippage)\n});\n\n// 3. Transfer the swapped SUI to the recipient\ntx.transferObjects([sui], recipient);\n\nSwap, save, and send​\n\nCompose 3 operations (a swap, a DeFi deposit, and a transfer) into one signed transaction:\n\nconst tx = new Transaction();\n\n// Source 2000 USDC\nconst [allUsdc] = tx.splitCoins(\ncoinWithBalance({ type: USDC, balance: 2_000_000_000n }),\n[tx.pure.u64(2_000_000_000)],\n);\n\n// 1. Split off 200 USDC and swap to SUI\nconst [swapPortion] = tx.splitCoins(allUsdc, [tx.pure.u64(200_000_000)]);\nconst [sui] = tx.moveCall({\ntarget: '0xDEX::router::swap',\ntypeArguments: [USDC, '0x2::sui::SUI'],\narguments: [tx.object('0xPOOL'), swapPortion, tx.pure.u64(0)],\n});\n\n// 2. Split 900 USDC and deposit into a yield protocol\nconst [savePortion] = tx.splitCoins(allUsdc, [tx.pure.u64(900_000_000)]);\ntx.moveCall({\ntarget: '0xYIELD::vault::deposit',\ntypeArguments: [USDC],\narguments: [tx.object('0xVAULT'), savePortion],\n});\n\n// 3. Split 100 USDC and send to Alice (splitCoins returns Coin<T>, so use coin::send_funds)\nconst [sendPortion] = tx.splitCoins(allUsdc, [tx.pure.u64(100_000_000)]);\ntx.moveCall({\ntarget: '0x2::coin::send_funds',\ntypeArguments: [USDC],\narguments: [sendPortion, tx.pure.address(aliceAddress)],\n});\n\n// Remaining 800 USDC stays with the sender\ntx.transferObjects([allUsdc, sui], tx.pure.address(senderAddress));\n\nIf any step fails (slippage breach, paused pool, invalid address), the entire transaction reverts. See Payment Intents for the Resolve, Plan, Execute pattern and more composition examples.\n\nKey composition rules​\n\nOutputs chain forward: The result of splitCoins or a moveCall can be passed as input to the next command.\n\nAll-or-nothing: If any command fails, the entire PTB reverts.\n\nOne gas payment: The whole batch shares a gas budget, and the sponsor (user, app, or relayer) pays once.\n\nUp to 1,024 commands: A single PTB can contain up to 1,024 commands.\n\nSee Building Transactions for the full PTB construction API.\n\nDecision flowchart​\n\nUse this to pick the right gas strategy for your transaction:\n\nIs the transaction a basic stablecoin transfer of an allowlisted token?\n\nYes: use gasless stablecoin transfer. Zero gas cost.\n\nNo: continue.\n\nDoes your app want to pay gas on behalf of the user?\n\nYes: use sponsored transactions. Consider address-balance sponsorship for simpler flows.\n\nNo: continue.\n\nDoes the user have a SUI address balance?\n\nYes: use address balance gas (tx.setGasPayment([])). No coin lookup needed.\n\nNo: use standard gas. The SDK auto-selects coin objects.\n\nFor most transactions, use coinWithBalance for non-gas coins, and the SDK handles coin-vs-balance selection for you. The exception is gasless stablecoin transfers, which use tx.balance() with balance::send_funds so the transaction stays eligible for zero gas.\nRelated topics\n\nAddress Balances\nAddress balances introduce a canonical balance system for fungible assets tied to Sui addresses, replacing coin-selection complexity with a single per-address accumulator value.\nMigrating from Coin to Address Balances\nWhat changes with address balances on Sui and what action to take for existing integrations.\nUsing Address Balances\nAddress balances introduce a canonical balance system for fungible assets tied to Sui addresses. Learn how to send, withdraw, and query address balances.\nGas Smashing\nGas smashing lets you pay transaction fees using multiple coins, which Sui combines into a single coin. Learn how gas smashing works, its interaction with address balance gas payment, and how to use it with programmable transaction blocks.\n\nMigrate to address balances\nCoin selection with coinWithBalance\nGas payment strategiesStandard gas\nAddress balance gas\nSponsored transactions\nGasless stablecoin transfers\n\nComposing DeFi operationsSwap and transfer\nSwap, save, and send\nKey composition rules\n\nDecision flowchart\n\nWas this page helpful?","tokens":2866,"crawled_at":1791196174480}
+{"id":10598,"url":"https://blog.trailofbits.com/authors/max-ammann","domain":"blog.trailofbits.com","chapter":"security_audits","title":"Max Ammann - The Trail of Bits Blog","text":"Fuzzing—a testing technique that tries to find bugs by repeatedly executing test cases and mutating them—has traditionally been used to detect segmentation faults, buffer overflows, and other memory corruption vulnerabilities that are detectable through crashes. But it has additional uses you may not know about: given the right invariants, we can use […]\nThis blog showcases five examples of real-world vulnerabilities that we’ve disclosed in the past year (but have not publicly disclosed before). We also share the frustrations we faced in disclosing them to illustrate the need for effective disclosure processes. Here are the five bugs: Undefined behavior in the borsh-rs Rust library Denial-of-service […]\nWe’re digging up the archives of vulnerabilities that Trail of Bits has reported over the years. This post shares the story of two such issues: a denial-of-service (DoS) vulnerability hidden in JSON Web Tokens (JWTs), and an oversight in the Linux kernel that could enable circumvention of critical kernel […]\nOur latest addition to the Trail of Bits Testing Handbook is a comprehensive guide to fuzzing: an essential, effective, low-effort method to find bugs in software that involves repeatedly running a program with random inputs to cause unexpected results.\nBehind Ethereum’s powerful blockchain technology lies a lesser-known challenge that blockchain developers face: the intricacies of writing robust Ethereum ABI (Application Binary Interface) parsers. Ethereum’s ABI is critical to the blockchain’s infrastructure, enabling seamless interactions between smart contracts and external applications. The complexity of data types and the need for precise encoding […]\nTrail of Bits is publicly disclosing four vulnerabilities that affect wolfSSL: CVE-2022-38152, CVE-2022-38153, CVE-2022-39173, and CVE-2022-42905. The four issues, which have CVSS scores ranging from medium to critical, can all result in a denial of service (DoS). These vulnerabilities have been discovered automatically using the novel protocol fuzzer tlspuffin. This blog post […]","tokens":518,"crawled_at":1791196182498}
+{"id":10599,"url":"https://docs.ethena.fi/resources/privacy-policy","domain":"docs.ethena.fi","chapter":"defi_protocols","title":"Privacy Policy | Ethena","text":"For the complete documentation index, see llms.txt. This page is also available as Markdown.\nLast Revised on August 2025\nThis Privacy Policy for Ethena (BVI) Limited (collectively with its affiliates, \"Company\", \"we\", \"us\" \"our\") describes how we collect, use and disclose information about users of the Company's websites (ethena.fi, the “Site”), and any related services, tools and features, including the Ethena service (collectively, the \"Services\"). For the purposes of this Privacy Policy, \"you\" and \"your\" means you as the user of the Services. Please read this Privacy Policy carefully. By using, accessing, or downloading any of the Services, you agree to the collection, use, and disclosure of your information as described in this Privacy Policy. If you do not agree to this Privacy Policy, please do not use, access or download any of the Services. ​\nUPDATING THIS PRIVACY POLICY\nWe may modify this Privacy Policy from time to time in which case we will update the \"Last Revised\" date at the top of this Privacy Policy. If we make material changes to the way in which we use information we collect, we will use reasonable efforts to notify you (such as by emailing you at the last email address you provided us, by posting notice of such changes on the Site, or by other means consistent with applicable law) and will take additional steps as required by applicable law. If you do not agree to any updates to this Privacy Policy please do not access or continue to use the Services. ​\nCOMPANY'S COLLECTION AND USE OF INFORMATION\n​When you access or use the Services, we may collect (directly or through third-party providers) certain categories of information about you from a variety of sources, which comprises: ​\n\nInformation provided during “Know Your Customer” (“KYC”) and Anti-Money Laundering (“AML”) processes, which includes personal identifying information. This may include:\n\nBasic Information: Name, Address, Date of Birth, Nationality, Country of Residence, Phone Number, Email Address.\n\nIdentification Information: Utility bills (or other proof of address), photographs, Government-issued identification (such as identification cards, passports, driver’s licenses, etc.), tax ID number, employment information, proof of residency, visa information, organizational documents, and information regarding ultimate beneficial owners.\n\nFinancial Information: Income/net assets/wealth verification statements.\n\nWe process the data provided and collected to provide the Services, personalize your experience with the Services, and improve the Services. Specifically, we use your data to:\n\nidentify you as a user in our system;\n\nidentify your place of residence, or registered office;\n\nprovide you with our Service;\n\nimprove the administration of our Service and quality of experience when you interact with our Service;\n\nprovide customer support and respond to your requests and inquiries;\n\ninvestigate and address conduct that may violate our Terms of Use;\n\ndetect, prevent, and address fraud, violations of our terms or policies, and/or other harmful or unlawful activity;\n\nsend you administrative notifications, such as security, support, and maintenance advisories;\n\nsend you newsletters, promotional materials, and other notices related to our Services or third parties' goods and services;\n\nrespond to your inquiries related to employment opportunities or other requests;\n\ncomply with applicable laws, cooperate with investigations by law enforcement or other authorities of suspected violations of law, and/or to pursue or defend against legal threats and/or claims; and\n\nact in any other way we may describe when you provide the Personal Data.\n\nHOW THE COMPANY SHARES YOUR INFORMATION\n​In certain circumstances, the Company may share your information with third parties for legitimate purposes subject to this Privacy Policy. Such circumstances comprise of: ​\n\nBlockchain analysis service providers, including TRM​ (TRM is a member of the EU-U.S. Data Privacy Framework as set forth by the U.S. Department of Commerce.)\n\nData analytics vendors, including Google Analytics ​\n\nTo comply with applicable law or any obligations thereunder, including cooperation with law enforcement, judicial orders, and regulatory inquiries ​\n\nIn connection with an asset sale, merger, bankruptcy, or other business transaction ​\n\nTo enforce any applicable terms of service ​\n\nTo ensure the safety and security of the Company and/or its users ​\n\nWith any parent companies, subsidiaries, joint ventures, or other companies under common control with us, in which case we will require such entities to honor this Privacy Policy\n\nIn connection with or during negotiation of any merger, financing, acquisition, or dissolution transaction or proceeding involving sale, transfer, divestiture, or disclosure of all or a portion of our business or assets. In the event of an insolvency, bankruptcy, or receivership, data may also be transferred as a business asset. If another company acquires our company, business, or assets, that company will possess the data collected by us and will assume the rights and obligations regarding your data as described in this Privacy Policy.\n\nWhen you request us to share certain information with third parties, such as through your use of login integrations ​\n\nWith professional advisors, such as auditors, law firms, accounting firms, or KYC service providers ​\n\nWith related companies, e.g. Ethena BVI Limited, to provide the Services\n\nLEGAL BASIS UNDER GDPR\nThe legal bases for the processing of personal data of natural persons in the European Economic Area (EEA) are detailled in the General data Protection Regulation (GDPR). The legal bases for processing your personal data are:\n\nIn the case of the initiation of a contract or an ongoing contractual relationship, the legal basis follows from Art. 6 (1) lit. b GDPR;\n\nWe are obliged by law to process Your data, e.g. by Financial Regulations (such as MiCAR Markets in Crypto Assets Regulation), Anti Money Laundering Laws, Tax Laws etc; the legal basis for such processing is Art. 6 (1) lit. c GDPR;\n\nOur legitimate interests under Art. 6 (1) lit. f GDPR; our legitimate interests are e.g. to safeguard the security and stability of our Services; to monitor the use of our Services in order to comply with all applicable laws; to detect, prevent, and address fraud, violations of our terms or policies, and/or other harmful or unlawful activity; to improve our Services; and for certain limited promotional purposes.\n\nIf You have given Your consent to process Your data, the legal basis is Art. 6 (1) lit. a GDPR.\n\nCOOKIES AND OTHER TRACKING TECHNOLOGIES\nDo Not Track Signals: ​ Your browser settings may allow you to transmit a \"Do Not Track\" signal when you visit various websites. Like many websites, our website is not designed to respond to \"Do Not Track\" signals received from browsers. To learn more about \"Do Not Track\" signals, you can visit http://www.allaboutdnt.com/. ​\nCookies and Other Tracking Technologies: ​ Most browsers accept cookies automatically, but you may be able to control the way in which your devices permit the use of cookies, web beacons/clear gifs, other geolocation tracking technologies. If you so choose, you may block or delete our cookies from your browser; however, blocking or deleting cookies may cause some of the Services, including any portal features and general functionality, to work incorrectly. If you have questions regarding the specific information about you that we process or retain, as well as your choices regarding our collection and use practices, please contact us using the information listed below. ​ You can opt out of tracking by Google Analytics. ​ Your browser settings may allow you to transmit a \"Do Not Track\" signal when you visit various websites. Like many websites, our website is not designed to respond to \"Do Not Track\" signals received from browsers. To learn more about \"Do Not Track\" signals, you can visit http://www.allaboutdnt.com/. ​\nThe legal bases for the setting of cookies are legitimate interests under Art. 6 para. 1 letter f) GDPR and, if applicable, Your consent in accordance with Art. 6 (1) (b) GDPR. In the case of the initiation of a contract or an ongoing contractual relationship, the legal basis also follows from Art. 6 para. 1 sentence 1 letter b) GDPR.\nSOCIAL NETWORKS AND OTHER THIRD PARTY WEBSITES AND LINKS\nWe may provide links to websites or other online platforms operated by third parties, including third-party social networking platforms, such as Twitter, Discord, Telegram or Medium as well as Curve Finance & Uniswap, operated by third parties (such platforms are \"Social Networks\" or “Decentralized Finance Applications”). If you follow links to sites not affiliated or controlled by us, you should review their privacy and security policies and other terms and conditions. We do not guarantee and are not responsible for the privacy or security of these sites, including the accuracy, completeness, or reliability of information found on these sites. Information you provide on public or semi-public venues, including information you share or post on Social Networks, may also be accessible or viewable by other users of the Services and/or users of those third-party online platforms without limitation as to its use by us or by a third party. Our inclusion of such links does not, by itself, imply any endorsement of the content on such platforms or of their owners or operators, except as disclosed on the Services. ​\nTHIRD PARTY WALLET EXTENSIONS\n​Certain transactions conducted via our Services, will require you to connect a Wallet to the Services. By using such Wallet to conduct such transactions via the Services, you agree that your interactions with such third party Wallets are governed by the privacy policy for the applicable Wallet. We expressly disclaim any and all liability for actions arising from your use of third party Wallets, including but without limitation, to actions relating to the use and/or disclosure of personal information by such third party Wallets.\nPUBLIC INFORMATION OBSERVED FROM BLOCKCHAINS\nWe collect data from activity that is publicly visible and/or accessible on blockchains. This may include blockchain addresses and information regarding holdings, purchases, sales, or transfers of tokens, which may then be associated with other data you have provided to us.\nCHILDREN'S PRIVACY\nChildren under the age of 18 are not permitted to use the Services, and we do not seek or knowingly collect any personal information about children under 13 years of age. If we become aware that we have unknowingly collected information about a child under 13 years of age, we will make commercially reasonable efforts to delete such information from our database. ​ If you are the parent or guardian of a child under 13 years of age who has provided us with their personal information, you may contact us using the below information to request that it be deleted. ​\nDATA ACCESS AND CONTROL\nYou can view, access, edit, or delete your data for certain aspects of the Service via your Settings page. You may also have certain additional rights:\n\nIf you are a user in the European Economic Area, you have certain rights under the European General Data Protection Regulation (“GDPR”). These include the right to\n\n(i) request access and obtain a copy of your personal data;\n\n(ii) request rectification or erasure;\n\n(iii) object to or restrict the processing of your personal data; and\n\n(iv) request portability of your personal data. Additionally, if we have collected and processed your personal data with your consent, you have the right to withdraw your consent at any time.\n\nIf you wish to exercise your rights under the GDPR, CCPA, or other applicable data protection or privacy laws, please contact us at the address provided herein, specify your request, and reference the applicable law. We may ask you to verify your identity, or ask for more information about your request. We will consider and act upon any above request in accordance with applicable law. We will not discriminate against you for exercising any of these rights.\nNotwithstanding the above, we cannot edit or delete any information that is stored on a blockchain, for example the Ethereum blockchain, as we do not have custody or control over any blockchains.\nDATA RETENTION\nWe may retain your data as long as you continue to use the Services, have an account with us, or for as long as is necessary to fulfill the purposes outlined in this Privacy Policy. We may continue to retain your data even after you deactivate your account and/or cease to use the Service if such retention is reasonably necessary to comply with our legal obligations, to resolve disputes, prevent fraud and abuse, enforce our Terms or other agreements, and/or protect our legitimate interests. Where your data is no longer required for these purposes, we will delete it.\nDATA SECURITY\nWe use appropriate technical and organizational measures to prevent accidental or intentional manipulation, partial or total loss, destruction or unauthorized access to your data by third parties. Our security measures are continuously improved in line with technological developments. Furthermore, all service providers commissioned by us are obliged by means of appropriate contractual agreements to take appropriate measures in accordance with the current state of the art to prevent the aforementioned risks.\nPlease be aware that, despite our reasonable efforts to protect your information, no security measures are perfect or impenetrable, and we cannot guarantee \"perfect security.\" Please further note that any information you send to us electronically, while using the Services or otherwise interacting with us, may not be secure while in transit. We recommend that you do not use unsecure channels to communicate sensitive or confidential information to us. ​You are responsible for the security of your digital wallet(s), and urge you to take steps to ensure it is and remains secure.\nIn the event that any information under our custody and control is compromised as a result of a breach of security, we will take steps to investigate and remediate the situation and, in accordance with applicable laws and regulations, notify those individuals whose information may have been compromised.\nRights of Data Subjects under GDPR\nThis section applies to you if you are able to avail yourself of certain rights under GDPR.\na) Right to information, rectification, deletion as well as rights to restriction of processing or transfer of your data to another body\nYou have the right to request information (Art. 15 GDPR) about your personal data and related information. In addition, you can request the correction (Art. 16 GDPR) and the deletion (Art. 17 para. 1 GDPR) of your personal data. You can also request that the processing of your personal data be restricted (Art. 18 GDPR). Furthermore, you have the right to receive your personal data from the responsible body or to have it transmitted to another responsible body (Art. 20 GDPR).\nb) Revocation of consent to data processing\nYou can revoke your consent in accordance with Art. 6 (1) sentence 1 (a) GDPR at any time with immediate effect in accordance with Art. 7 (3) sentence 1 GDPR. Please note that data processing that took place before the revocation is not affected by the revocation and is therefore lawful despite the revocation. If you would like to make use of your right of objection, a simple notification to the person listed under no. 1.\nc) Objection to profiling and direct marketing\nIn certain cases, you also have the right to object (Art. 21 GDPR) to the data processing.\nIn particular, you have the right to object at any time to the processing of your data (in particular in the case of so-called profiling) based on Art. 6 (1) sentence 1 (f) GDPR (data processing on the basis of a balancing of interests) or Art. 6 (1) sentence 1 (i) GDPR (data processing in the public interest) in accordance with Art. 21 (1) GDPR. We will then no longer process your personal data for these purposes, unless we can demonstrate compelling legitimate grounds for the processing which override the interests, rights and freedoms of the data subject, or the processing serves to establish, exercise or defend legal claims.\nIf your personal data is processed for direct marketing, you can also object to the processing of your data for the purpose of direct marketing at any time in accordance with Art. 21 para. 2 GDPR, including profiling, insofar as it is related to such direct marketing. If you object, your personal data will no longer be used for these direct marketing purposes.\nd) Right to lodge a complaint with the competent data protection supervisory authority\nIf you believe that we have not complied with data protection regulations when processing your data, you can submit a complaint to the supervisory authority responsible for us. The indication of the supervisory authority is not a mandatory part of the privacy policy.\n\nHOW TO CONTACT US\n​Should you have any questions about our privacy practices or this Privacy Policy, please email us at finance@ethenalabs.xyz.\n\n.\n\nLast updated 1 year ago\nWas this helpful?","tokens":4315,"crawled_at":1791196182954}
+{"id":10600,"url":"https://a16zcrypto.com/posts/article/investing-in-sound-xyz","domain":"a16zcrypto.com","chapter":"research","title":"Investing in Sound.xyz - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nInvesting in Sound.xyz\nAli Yahya and Jane Lippencott\n07.12.23\n\nTags & Share Tags\nannouncements\nannouncements & news\ninvestments\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nWhen social and music platforms started taking off in the 2000s, many musicians saw the huge potential of global distribution networks to showcase their artistic talent and connect with fans. Unfortunately, as they consolidated more power and leverage, the platforms acted more as gatekeepers – ceding little control and extracting large take rates from artists’ revenue.\n\nThankfully, a new movement has emerged in web3 music, led by platforms such as Sound.xyz. Sound is championing a future where artists and fans can reap the rewards of music creation and appreciation, so we’re excited to announce that we’ve doubled down on Sound.xyz by leading their Series A funding round.\n\nThe music industry has been more resistant to new digital business models than other entertainment mediums – most notably video games – and artists are suffering as a result. As Chris Dixon noted, the video game and music industries adapted to the internet in very different ways. Game makers embraced new models, and as online play became more pervasive, discovered they can earn more revenue by making their games free and selling virtual goods. The music industry filed lawsuits against innovators and eventually accepted today’s dominant model of bundled streaming platforms. Their algorithms direct 90% of streams to the top 1% of artists, making it extremely difficult for new artists to get discovered by potential fans.\n\nFurthermore, the industry is a labyrinth of intermediaries – from record labels to publishers to aforementioned streaming platforms – all taking a cut of the revenue generated by artists’ work. As a result, musicians earn a minuscule amount from each stream, typically around $0.003. This uneven distribution of attention and unfair dilution of income prevents nearly all independent artists from earning a living wage on their music.\n\nFans are also feeling disconnected from the artists they love. Current platforms impede genuine connection between artists and their fans, treating communities as a homogeneous blob where dedicated individuals fail to stand out. Artists are restricted from exporting their audience to reach them on their own terms, and reaching new fans requires paying the platform or becoming friends with their playlist editors.\n\nSound will help the music industry bridge this gap. Sound is music without the middleman: a suite of web3-native music and economic tools powering and empowering the next generation of artists and their communities. And as of today, its tools are available to all artists.\n\nOn Sound, songs stream for free and users curate their own playlists. Artists can debut songs along with a series of limited-edition NFTs, and listeners can collect directly from the creator and leave a public comment on the songs they own. Each artist (not the platform) sets the terms of their relationship with supporters through unique, customizable digital item drops powered by smart contracts. By unlocking new, web3-native revenue opportunities, Sound economically empowers artists to bypass traditional intermediaries and retain a majority of their earnings without sacrificing distribution.\n\nSince our initial investment in 2021, Sound has onboarded more than 500 artists who have earned over $5 million across primary sales and secondary royalties. Each dollar earned was paid out accurately, transparently, and instantly via the smart contracts that make up the Sound Protocol. In the traditional music industry, that equates to more than a billion streams.\n\nOn Sound’s mobile app, fans can stream music for free, collect Sounds from their favorite artists, and showcase their support to other listeners. Sound’s marketplace, available on web and mobile, enables liquidity for existing collectors and new fans.\n\nAlongside Sound’s frontend products, the Sound Protocol launched in 2022 as a new canvas for artists and developers alike. The Protocol facilitates the creation of composable, artist-owned song contracts, with permanent and decentralized metadata and modular architecture that allows for custom drop experiences. It gives artists the flexibility to customize their own experience without limiting themselves to a single listening destination.\n\nThe founder David Greenstein, and the seasoned team he’s assembled, are executing in a world-class way to bring Sound to life. We couldn’t be more excited to further our partnership with David, Vignesh, Kevin and the entire Sound team as they build the future of music.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nCharts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":1855,"crawled_at":1791196196350}
+{"id":10601,"url":"https://docs.sui.io/onchain-finance/asset-custody/address-balances/using-address-balances","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Using Address Balances | Sui Documentation","text":"AddressAddressA unique, anonymous identity on a blockchain network. balances provide a canonical balance for each coin type tied directly to a Sui address. Funds sent through sui::coin::send_funds and sui::balance::send_funds merge automatically into a single balance per coin type, with no objectObjectThe basic unit of storage on Sui. management required. For the conceptual model and a comparison with coin objects, see Address Balances overview. For the full specification, see SIP-58: Sui Address Balances.\n\nSending funds​\n\nUse send_funds to deposit directly into a recipient address balance. The recipient balance increases without creating new objects, and multiple deposits from different senders all merge into one balance.\n\nTypeScript SDK​\n\nTo deposit tokens into a recipient's address balance use tx.balance() with balance::send_funds instead of creating a coin object:\n\nconst tx = new Transaction();\n\ntx.moveCall({\ntarget: '0x2::balance::send_funds',\ntypeArguments: ['0x2::sui::SUI'],\narguments: [tx.balance({ balance: 1_000_000_000n }), tx.pure.address('0xRecipientAddress')],\n});\n\nTransactions built using only tx.balance() and eligible MoveMoveAn open source programming language used for all activity on Sui. calls like send_funds and redeem_funds might qualify for zero gasGasThe computational cost of execution and object storage for a transaction. fees when the network supports it.\n\nCLI​\n\nTo send funds using Sui CLI:\n\n# Send from gas coin to address balance\nsui client ptb \\\n--split-coins gas '[5000000]' \\\n--assign coin \\\n--move-call 0x2::coin::send_funds '<0x2::sui::SUI>' coin @<RECIPIENT_ADDRESS>\n\n# Send from another coin\nsui client ptb \\\n--split-coins @<COIN_ID> '[5000000]' \\\n--assign coin \\\n--move-call 0x2::coin::send_funds '<COIN_TYPE>' coin @<RECIPIENT_ADDRESS>\n\nThe CLI also provides a dedicated sui client send-funds command that does this without building a PTBProgrammable transaction blocksDefine all user transactions on Sui.:\n\n# Send 0.005 SUI to a recipient's address balance\nsui client send-funds --to <RECIPIENT_ADDRESS> --amount 5000000\n\n# Send another coin type, drawing from the sender's address balance\nsui client send-funds --to <RECIPIENT_ADDRESS> --amount 5000000 \\\n--coin-type <COIN_TYPE> --from-address-balance\n\nThe command takes the following flags:\n\nFlagDescription\n--to\nRecipient address.\n\n--amount\nAmount to send in MISTMISTThe smallest unit of SUI.. Required unless you pass --all-coins.\n\n--coin-type\nCoin type to send. Defaults to 0x2::sui::SUI.\n\n--all-coins\nSend all coin balance of the specified type. Cannot combine with --from-address-balance.\n\n--from-address-balance\nDraw the amount from the sender's address balance rather than their coins.\n\nBy default, the command selects coins first and falls back to address balance if coins are insufficient. With --from-address-balance, it draws exclusively from the address balance, and fails if that balance cannot cover the amount.\n\nThe network chooses gas independently of this flag: it pays gas from the sender's address balance whenever that balance covers the budget and the transactionTransactionA number of commands that execute on inputs to define the result of the transaction. does not use the gas coin, in which case the transaction carries no gas payment and gets a ValidDuring expiration for replay protection. Otherwise it pays gas from the sender's coins. So a --from-address-balance transferTransferChanging the owner of an asset. is usually, but not always, free of owned object inputs.\n\nMove functions​\n\nThe Sui framework provides send_funds in both the balance and coin modulesModuleA component of a Move package that defines interaction with on-chain objects.:\n\n// Send a Balance<T> to an address balance\npublic fun send_funds<T>(balance: Balance<T>, recipient: address)\n\n// Send a Coin<T> to an address balance (converts to balance internally)\npublic fun send_funds<T>(coin: Coin<T>, recipient: address)\n\nLearn more at sui-framework/sources/balance.move and sui-framework/sources/coin.move.\n\nWithdrawing funds​\n\nCreate a withdrawal input and redeem it to get a Coin<T>:\n\nconst tx = new Transaction();\n\nconst [coin] = tx.moveCall({\ntarget: '0x2::coin::redeem_funds',\ntypeArguments: ['0x2::sui::SUI'],\narguments: [tx.withdrawal({ amount: 1_000_000_000 })],\n});\n\ntx.transferObjects([coin], '0xRecipientAddress');\n\nGet a Balance<T> directly:\n\nconst [balance] = tx.moveCall({\ntarget: '0x2::balance::redeem_funds',\ntypeArguments: ['0x2::sui::SUI'],\narguments: [tx.withdrawal({ amount: 1_000_000_000 })],\n});\n\nFor coin types other than SUI, pass the type parameter:\n\nconst [coin] = tx.moveCall({\ntarget: '0x2::coin::redeem_funds',\ntypeArguments: ['0xPackageId::module::USDC'],\narguments: [tx.withdrawal({ amount: 1_000_000, type: '0xPackageId::module::USDC' })],\n});\n\nTo use address balance funds in a transaction, withdraw them and redeem them using Coin<T> or Balance<T>.\n\nTypeScript SDK​\n\nIf you are not explicitly selecting coin objects for gas or as transaction arguments, the TypeScript SDK automatically checks both coin objects and address balances and draws from the correct sources.\n\nimport { Transaction } from '@mysten/sui/transactions';\n\nconst tx = new Transaction();\ntx.transferObjects([tx.coin({ balance: requiredAmount })], recipient);\n\nTypeScript SDK: Manual withdrawals​\n\nFor explicit control over address balance withdrawals, use tx.withdrawal(). The withdrawal must be redeemed through redeem_funds to produce a usable Coin<T> or Balance<T>:\n\nimport { Transaction } from '@mysten/sui/transactions';\n\nconst tx = new Transaction();\n\n// Withdraw SUI from address balance and redeem to Coin\nconst [coin] = tx.moveCall({\ntarget: '0x2::coin::redeem_funds',\ntypeArguments: ['0x2::sui::SUI'],\narguments: [tx.withdrawal({ amount: 1_000_000_000 })], // 1 SUI in MIST\n});\n\n// Withdraw a custom coin type\nconst coinType = '0xPackageId::module::CoinType';\nconst [customCoin] = tx.moveCall({\ntarget: '0x2::coin::redeem_funds',\ntypeArguments: [coinType],\narguments: [tx.withdrawal({ amount: 1_000_000, type: coinType })],\n});\n\n// Transfer to recipient\ntx.transferObjects([coin], recipient);\n\ninfo\ntx.withdrawal() creates a Withdrawal<Balance<T>> capability that must be redeemed to create a coin or balance. Use 0x2::coin::redeem_funds() or 0x2::balance::redeem_funds() to do this. The coinWithBalance intent does this automatically.\n\nRust SDK: Manual withdrawals​\n\nUse FundsWithdrawalArg to withdraw from an address balance in Rust. The helper FundsWithdrawalArg::balance_from_sender(amount, balance_type) provides a convenient constructor:\n\nuse sui_types::transaction::{FundsWithdrawalArg, WithdrawalTypeArg, Reservation, WithdrawFrom};\n\nlet withdrawal_arg = FundsWithdrawalArg {\nreservation: Reservation::MaxAmountU64(amount),\ntype_arg: WithdrawalTypeArg::Balance(coin_type),\nwithdraw_from: WithdrawFrom::Sender,\n};\n\nIn your PTB, pass the withdrawal input to either:\n\n0x2::balance::redeem_funds<T>() to obtain a Balance<T>.\n\n0x2::coin::redeem_funds<T>() to obtain a Coin<T>.\n\nYou can have multiple FundsWithdrawalArg inputs in a PTB, even for the same coin type:\n\nlet mut builder = ProgrammableTransactionBuilder::new();\n\nlet withdraw_arg = FundsWithdrawalArg::balance_from_sender(\nwithdraw_amount,\nsui_types::gas_coin::GAS::type_tag(),\n);\nlet withdraw_input = builder.funds_withdrawal(withdraw_arg).unwrap();\n\n// Redeem to coin\nlet coin = builder.programmable_move_call(\nSUI_FRAMEWORK_PACKAGE_ID,\nIdentifier::new(\"coin\").unwrap(),\nIdentifier::new(\"redeem_funds\").unwrap(),\nvec![\"0x2::sui::SUI\".parse().unwrap()],\nvec![withdraw_input],\n);\n\nbuilder.transfer_arg(recipient, coin);\n\nLearn more at sui-types/src/programmable_transaction_builder.rs.\n\nSplitting and joining withdrawals​\n\nYou can split and merge withdrawals within a PTB:\n\n// Split a sub-withdrawal from an existing withdrawal\npublic fun withdrawal_split<T: store>(withdrawal: &mut Withdrawal<T>, sub_limit: u256): Withdrawal<T>\n\n// Join two withdrawals together (must have same owner)\npublic fun withdrawal_join<T: store>(withdrawal: &mut Withdrawal<T>, other: Withdrawal<T>)\n\nPaying for gas from address balances​\n\nWhen you pay gas from an address balance, you do not select or provide coin objects, so there is no gas coin selection or merge workflow. As a result, gas smashing does not apply, and the network resolves the gas fee as a withdrawal from your address balance.\n\nWith address balance gas payments, pass an empty array to setGasPayment. This enables fully offline transaction building because there are no coin object versions to look up:\n\nconst tx = new Transaction();\ntx.setGasPayment([]); // Empty array = use address balance for gas\n\nIn Rust, set gas_data.payment to an empty vector and use ValidDuring expiration:\n\nTransactionData::V1(TransactionDataV1 {\nkind: tx_kind,\nsender,\ngas_data: GasData {\npayment: vec![], // Empty - gas paid from address balance\nowner: sender,\nprice: rgp,\nbudget: 10_000_000,\n},\nexpiration: TransactionExpiration::ValidDuring {\nmin_epoch: Some(current_epoch),\nmax_epoch: Some(current_epoch + 1),\nmin_timestamp: None,\nmax_timestamp: None,\nchain: chain_identifier,\nnonce: unique_nonce,\n},\n})\n\nRequirements for address balance gas payments:\n\ngas_data.payment must be empty.\n\nexpiration must be ValidDuring with both min_epoch and max_epoch specified.\n\nmax_epoch must be at most min_epoch + 1 (single epochEpochA period of time defined by the network. or 1-epoch range).\n\nTimestamp-based expiration is not currently supported.\n\nThe transaction kind must be ProgrammableTransaction.\n\nThe nonce field differentiates otherwise identical transactions. Unlike EVM chains, the nonce has no semantic requirements. It does not need to be sequential, and there is no nonce gap problem. It simply allows you to submit two transactions that would otherwise have the same digest. For most use cases, generate the nonce randomly or use an incrementing counter in your application:\n\n// Random nonce\nlet nonce: u32 = rand::random();\n\n// Or incrementing counter\nlet nonce: u32 = self.next_nonce.fetch_add(1, Ordering::SeqCst);\n\nClick to openVerify that address balance gas payments are enabledBefore using address balance gas payments, you can verify that the feature is enabled on the network by checking the protocol configuration flag:\nconst network = 'testnet';\n\nconst networkUrls = {\nmainnet: 'https://fullnode.mainnet.sui.io:443',\ntestnet: 'https://fullnode.testnet.sui.io:443',\ndevnet: 'https://fullnode.devnet.sui.io:443',\n};\n\nconst client = new SuiGrpcClient({\nnetwork,\nbaseUrl: networkUrls[network],\n});\n\nconst { response } = await client.ledgerService.getEpoch({\nreadMask: {\npaths: ['protocol_config.feature_flags'],\n},\n});\n\nconst enabled =\nresponse.epoch?.protocolConfig?.featureFlags['enable_address_balance_gas_payments'] ?? false;\n\nconsole.log(`enable_address_balance_gas_payments on ${network}:`, enabled);\n\nSponsored transactionsSponsored transactionWhen one address pays the gas fee for a transaction submitted by another address.​\n\nAddress balances simplify sponsored transactions compared to coin-based sponsorship.\n\nNo gas coin locking risk.\n\nThe sponsor does not need to manage gas coin inventory.\n\nThe user can sign before the sponsor, enabling simpler async flows.\n\nEnables permissionless public gas stations.\n\ncaution\nThe GasCoin argument is still valid here, and usage should still be monitored in sponsored transactions even when using address balance gas payment.\n\nWith address balances, the user signs first and the sponsor signs afterward:\n\n// 1. User builds and signs the transaction first\nconst tx = new Transaction();\ntx.setSender(userAddress);\ntx.setGasOwner(sponsorAddress);\ntx.setGasPayment([]); // Empty array = sponsor pays from address balance\n// ... add commands ...\n\nconst bytes = await tx.build({ client });\nconst { signature: userSignature } = await userKeypair.signTransaction(bytes);\n\n// Option A: Send the transaction bytes and user signature to the sponsor service.\n// The sponsor signs and executes the transaction on their end.\n// Replace with your own sponsor communication logic (e.g., an API call).\nawait sendToSponsor(userSignature, bytes);\n\n// Option B: Get signature from sponsor and submit it ourselves. Sponsor signs (can happen asynchronously)\nconst { signature: sponsorSignature } = await sponsorKeypair.signTransaction(bytes);\n\nconst result = await client.executeTransaction({\ntransaction: bytes,\nsignatures: [userSignature, sponsorSignature],\n});\n\nBoth sender and sponsor must sign. Storage rebates are credited to the sponsor address balance.\n\nQuerying balances​\n\nTypeScript SDK​\n\nUse getBalance to see both coin objects and address balance:\n\nconst { balance } = await grpcClient.getBalance({\nowner: '0xMyAddress',\n});\n\nconsole.log(balance.balance); // total balance as string (coin objects + address balance)\nconsole.log(balance.coinBalance); // balance from coin objects only\nconsole.log(balance.addressBalance); // balance from address balance only\nconsole.log(balance.coinType); // e.g. \"0x2::sui::SUI\"\n\nAll balance values are returned as strings. Use BigInt(balance.balance) for numerical types.\n\ngRPCgRPC APIReplaces JSON-RPC on full nodes for data access.​\n\nUse GetBalance and ListBalances from StateService:\n\nbuf curl --protocol grpc https://fullnode.testnet.sui.io/sui.rpc.v2.StateService/GetBalance \\\n-d '{\n\"owner\": \"<ADDRESS>\",\n\"coin_type\": \"0x2::sui::SUI\"\n}'\n\n# List all balances\nbuf curl --protocol grpc https://fullnode.testnet.sui.io/sui.rpc.v2.StateService/ListBalances \\\n-d '{\"owner\": \"<ADDRESS>\"}'\n\nGraphQL​\n\nCopy the examples below into GraphQL IDE (Testnet) to try them out:\n\n# Single balance\n{\naddress(address: \"0xe4ee9c157b5eb185c2df885bd7dcb4be493630a913f4b0e0c7e8ecf77930a878\") {\nbalance(coinType: \"0x2::sui::SUI\") {\ncoinType {\nrepr\n}\naddressBalance\ncoinBalance\ntotalBalance\n}\n}\n}\n\n# All balances\n{\naddress(address: \"0xe4ee9c157b5eb185c2df885bd7dcb4be493630a913f4b0e0c7e8ecf77930a878\") {\nbalances {\nnodes {\ncoinType {\nrepr\n}\naddressBalance\ncoinBalance\ntotalBalance\n}\n}\n}\n}\n\nFor more details, see GraphQL Reference - IAddressable.balance.\n\nComputing balance changes from checkpointCheckpointCreated after transaction execution to provide a certified record of chain history. data​\n\nWith address balances, you must also process accumulator events from TransactionEffects when computing balance changes:\n\nuse sui_types::balance_change::{derive_balance_changes, BalanceChange};\n\nlet balance_changes: Vec<BalanceChange> = derive_balance_changes(\n&effects,\n&input_objects,\n&output_objects,\n);\n\nThe algorithm:\n\nSubtract input coins: For each input coin object, subtract its value from (owner, coin_type).\n\nAdd output coins: For each mutated or created coin object, add its value to (owner, coin_type).\n\nProcess accumulator events: For each accumulator event with a Balance<T> type:\n\nSplit operation: Subtract the amount (funds withdrawn from address balance).\n\nMerge operation: Add the amount (funds deposited to address balance).\n\nSee the reference implementation for the full algorithm.\n\nAccessing accumulator events​\n\nAccumulator events are embedded in TransactionEffects:\n\nuse sui_types::effects::TransactionEffectsAPI;\n\nlet events = effects.accumulator_events();\nfor event in events {\nlet address = event.write.address.address;\nlet balance_type = &event.write.address.ty;\n\n// Only Balance<T> types represent balance changes\nif let Some(coin_type) = Balance::maybe_get_balance_type_param(balance_type) {\nlet amount = match &event.write.value {\nAccumulatorValue::Integer(v) => *v as i128,\n_ => continue,\n};\n\nlet signed_amount = match event.write.operation {\nAccumulatorOperation::Split => -amount, // Withdrawal\nAccumulatorOperation::Merge => amount, // Deposit\n};\n\n// (address, coin_type, signed_amount) represents the balance change\n}\n}\n\nThe BalanceChange struct represents the result:\n\npub struct BalanceChange {\npub address: SuiAddress,\npub coin_type: TypeTag,\npub amount: i128, // Negative = spent, positive = received\n}\n\nConverting existing coins to address balances​\n\nMigration is optional. To consolidate coins into address balances using Sui CLI:\n\nsui client ptb \\\n--merge-coins @<COIN_1> '[@<COIN_2>, @<COIN_3>]' \\\n--move-call 0x2::coin::send_funds '<0x2::sui::SUI>' @<COIN_1> @<YOUR_ADDRESS>\n\nFor SUI coins, you can smash them as gas and use --move-call 0x2::coin::send_funds --gas-coin <COIN>.\n\nThe TypeScript SDK automatically selects coins or address balances as needed. Contracts that accept Coin<T> or Balance<T> remain callable. The redeem_funds function converts withdrawals to the expected types within the PTB.\n\nUsing the TypeScript SDK:\n\nimport { Transaction } from '@mysten/sui/transactions';\n\nconst tx = new Transaction();\ntx.moveCall({\ntarget: '0x2::coin::send_funds',\ntypeArguments: ['0x2::sui::SUI'],\narguments: [tx.coin({ balance: totalAmount }), tx.pure.address(yourAddress)],\n});\n\nThis might earn storage rebates from deleted coin objects.\nRelated topics\n\nAddress Balances\nAddress balances introduce a canonical balance system for fungible assets tied to Sui addresses, replacing coin-selection complexity with a single per-address accumulator value.\nSui Client PTB CLI\nThe Sui Client PTB CLI enables a user to construct a PTB and execute it from the command line or a file.\nGas Smashing\nGas smashing lets you pay transaction fees using multiple coins, which Sui combines into a single coin. Learn how gas smashing works, its interaction with address balance gas payment, and how to use it with programmable transaction blocks.\nSui Full Node gRPC Methods\nThe Sui full node gRPC protocol is available on all Sui Full nodes.\n\nSending fundsTypeScript SDK\nCLI\nMove functions\n\nWithdrawing fundsTypeScript SDK\nTypeScript SDK: Manual withdrawals\nRust SDK: Manual withdrawals\nSplitting and joining withdrawals\n\nPaying for gas from address balances\nSponsored transactions\nQuerying balancesTypeScript SDK\ngRPC\nGraphQL\n\nComputing balance changes from checkpoint dataAccessing accumulator events\n\nConverting existing coins to address balances\n\nWas this page helpful?","tokens":4495,"crawled_at":1791196202055}
+{"id":10602,"url":"https://a16zcrypto.com/posts/article/expanding-uk-andreessen-horowitz","domain":"a16zcrypto.com","chapter":"research","title":"Expanding to the UK - a16z crypto","text":"0 Results\n\nSearching...\nEXPLORE\nEngineering\nlearn more\n\nResearch\nlearn more\n\nPodcast\nlearn more\n\nPolicy\nlearn more\n\nExpanding to the UK\nChris Dixon\n06.11.23\n\nTags & Share Tags\nannouncements\nannouncements & news\nUK\n\nx\nlinkedin\nfacebook\nhacker-news\nwhatsapp\nflipboard\nreddit\n\nOver the last year it has become clear that blockchains and the software movement around them — usually called crypto or web3 — can only succeed with a clear regulatory regime that provides an open pathway for startups while also protecting consumers from fraud and manipulation. This regulation should be aimed at stamping out the “casino” culture that has developed around crypto, while also allowing constructive applications to reach their full potential.\n\nA common question we hear is: “What problems do blockchains solve?” Services built on blockchains solve the same problems that other digital services solve, but with better outcomes. They can connect people in social networks, while empowering users over corporate interests. They can underpin marketplaces and payment systems that facilitate commerce, but with persistently lower take rates. They can enable new forms of monetizable media, interoperable and immersive digital worlds, and artificial intelligence services that compensate — rather than cannibalize — creators and communities.\n\nTechnology takes decades to develop — we are just now seeing mainstream applications of AI after 80 years of development. We are in the early innings of crypto. Today there are tens of thousands of crypto developers, but the numbers are growing fast and we expect to see one million developers by 2030. The infrastructure will improve, increasing performance and lowering fees, and many more applications will be built across a wide range of categories.\n\nWe have been working with policymakers and regulators across the globe, and during our discussions it has become clear that the UK government sees the promise of web3, with Prime Minister Rishi Sunak suggesting the UK can become a hub of web3 innovation. UK authorities are also willing to work with the industry to create policies that incentivize startups to pursue decentralization.\n\nMore specifically, the UK policymakers and regulators are taking an approach that is uniquely tailored to blockchain and digital asset regulation. This includes:\n\nWorking constructively with industry to identify the unique attributes of blockchain technology and how those attributes shape the risk profile of decentralized services vs. centralized services.\n\nLaying the foundation for future applications of blockchain technology.\n\nPutting forth an innovative sandbox approach to regulation.\n\nFocusing on an outcomes-based approach.\n\nAll the while continuing to keep consumer protection front-and-center of any regulation.\n\nRecently, our General Counsel, Miles Jennings, published a piece on the importance of decentralization. I highly recommend reading it. The crux of the argument is that the benefits of web3 will only be achieved if the underlying infrastructure is decentralized. But it takes time and a runway for projects to grow from a centralized startup to a truly decentralized network. As a result, we need regulatory frameworks that facilitate decentralization, not impede it.\n\nAt a16z crypto, we live by these same rules – we have a team of experts that work with our portfolio companies in the pursuit of greater decentralization, we push for long lock up periods of multiple years for ourselves and founders, and we actively participate in decentralized governance.\n\nWhile there is still work to be done, we believe that the UK is on the right path to becoming a leader in crypto regulation. The UK also has deep pools of talent, world-leading academic institutions, and a strong entrepreneurial culture. It is home to more “unicorns” than Germany, France, and Sweden combined; to some of the world’s largest financial markets and pools of capital; and to highly-sophisticated, world-class regulators. All of these make the UK strongly positioned to lead in web3.\n\nBecause of this, we announced today that we will open a16z’s first office outside of the United States, in London. This new office, slated to open later this year, will be led by General Partner, Sriram Krishnan, who along with a team, will work to grow the crypto and startup ecosystem in the UK and Europe. We’ve invested in a number of UK-based crypto companies including Arweave, Aztec, and Improbable. And we are excited to announce our newest investment in UK-based Gensyn. Founded by computer science and machine learning research veterans Ben Fielding and Harry Grieve, Gensyn’s decentralized compute protocol will enable developers to build state-of-the-art AI systems on any connected hardware. Their novel cryptographic verification system allows users to trust that the protocol’s machine learning work was completed correctly.\n\nWe also plan to host our next Crypto Startup School in Spring 2024 in London – more to come about this. We had over 8,000 applications to our most recent CSS program based in Los Angeles, with the final 26 teams coming from a range of countries including the UK, U.S., India, Germany, France, Argentina, Ecuador, and Canada. By basing the next CSS in London, we hope to attract even more great teams from the UK, Europe and beyond to build web3 projects.\n\nThere are incredible universities that call the UK home. We have an active dialog with many blockchain clubs at universities in the US and now we are excited to expand these activities abroad. We will be reaching out to universities across the UK to support these clubs, helping them develop courses and building connections to industry.\n\nWe are excited to receive support in our efforts from UK leadership. The Prime Minister, Rishi Sunak, said today:\n\n“As we cement the UK’s place as a science and tech superpower, we must embrace new innovations like Web3, powered by blockchain technology, which will enable start-ups to flourish here and grow the economy.\n\n“That success is founded on having the right regulation and guardrails in place to protect consumers and foster innovation. While there’s still work to do, I’m determined to unlock opportunities for this technology and turn the UK into the world’s Web3 centre.\n\n“That’s why I am thrilled world-leading investor, Andreessen Horowitz, has decided to open their first international office in the UK — which is testament to our world-class universities and talent and our strong competitive business environment.”\n\nFinally, we will remain heavily invested in the U.S. We continue to be committed to working with U.S. policymakers and regulators to push for more regulatory clarity for crypto startups here.\n\nWe’re excited about what’s in store, and as always, we’re excited to keep building.\n\n***\n\nThe views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.\n\nThis content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investments/.\n\nCharts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.","tokens":2358,"crawled_at":1791196216437}
+{"id":10603,"url":"https://www.metaplex.com/docs/smart-contracts/bubblegum-v2/transfer-cnfts","domain":"www.metaplex.com","chapter":"docs","title":"Transferring Compressed NFTs - Bubblegum V2 - Metaplex","text":"Summary\nTransferring a compressed NFT moves ownership from one wallet to another using the transferV2 instruction. This page covers transfers by owner, delegate, permanent transfer delegate, and transferability checks.\nTransfer a cNFT to a new owner using transferV2\nAuthorize transfers via leaf owner, leaf delegate, or permanent transfer delegate\nCheck if a cNFT can be transferred using the canTransfer helper\nPass the coreCollection parameter when the cNFT belongs to a collection\nThe transferV2 instruction can be used to transfer a Compressed NFT from one owner to another. To authorize the transfer, either the current owner or the delegate authority — if any — must sign the transaction. The delegated authority can either be a leaf delegate or the permanentTransferDelegate of the collection.\nNote that this instruction updates the Compressed NFT and therefore replaces the leaf on the Bubblegum Tree. This means additional parameters must be provided to verify the integrity of the Compressed NFT. Since these parameters are common to all instructions that mutate leaves, they are documented in the following FAQ. Fortunately, we can use a helper method that will automatically fetch these parameters for us using the Metaplex DAS API.\nTransaction size\nIf you encounter transaction size errors, consider using { truncateCanopy: true } with getAssetWithProof. See the FAQ for details.\n\nTransfer a Bubblegum V2 Compressed NFT\nThe instruction accepts the following parameters:\nLeaf Owner: The current owner of the Compressed NFT. It defaults to the payer of the transaction.\nLeaf Delegate: The current owner of the Compressed NFT and its delegate authority if any. One of these must sign the transaction.\nAuthority: An optional authority that signs the transaction. It can be the Leaf Owner or the permanentTransferDelegate and defaults to the payer of the transaction.\nNew Leaf Owner: The address of the Compressed NFT's new owner\nMerkle Tree: The address of the Bubblegum Tree\nRoot: The current root of the Bubblegum Tree\nData Hash: The hash of the metadata of the Compressed NFT\nCreator Hash: The hash of the creators of the Compressed NFT\nNonce: The nonce of the Compressed NFT\nIndex: The index of the Compressed NFT\nCollection: The core collection of the Compressed NFT (if the cNFT is part of a collection)\nWhen using JavaScript we suggest to use the getAssetWithProof function first to fetch the parameters and then pass them to the transferV2 instruction.\nTransfer a Compressed NFT\n\nimport { getAssetWithProof, transferV2 } from '@metaplex-foundation/mpl-bubblegum';\n\nconst assetWithProof = await getAssetWithProof(umi, assetId, {\n\ntruncateCanopy: true,\n\n})\n\n// Then leafOwnerA can use it to transfer the NFT to leafOwnerB.\n\nconst leafOwnerB = generateSigner(umi)\n\nawait transferV2(umi, {\n\n// Pass parameters from the asset with proof.\n\n...assetWithProof,\n\nauthority: leafOwnerA,\n\nnewLeafOwner: leafOwnerB.publicKey,\n\n// If the cNFT is part of a collection, pass the core collection.\n\n//coreCollection: coreCollection.publicKey,\n\n}).sendAndConfirm(umi)\n\nTransferability Check for Compressed NFTs\nThe canTransfer function can be used to check if a Compressed NFT can be transferred. It will return true if the NFT can be transferred and false otherwise. Frozen and NonTransferable cNFTs cannot be transferred.\nimport { canTransfer } from '@metaplex-foundation/mpl-bubblegum'\n\nconst assetWithProof = await getAssetWithProof(umi, assetId, {\n\ntruncateCanopy: true,\n\n})\n\nconst canBeTransferred = canTransfer(assetWithProof)\n\nconsole.log(\"canBeTransferred\", canBeTransferred ? \"Yes\" : \"No\")\n\nNotes\nAfter a transfer, the leaf delegate is automatically reset to the new owner.\nFrozen cNFTs and soulbound (non-transferable) cNFTs cannot be transferred. Use canTransfer to check.\nThe permanent transfer delegate can transfer without the owner's signature if the PermanentTransferDelegate plugin is enabled on the collection.\nFAQ\nCan I transfer a frozen cNFT?\nNo. Frozen cNFTs cannot be transferred. You must thaw the cNFT first using the appropriate delegate authority.\nWhat happens to the delegate after a transfer?\nThe leaf delegate is automatically reset to the new owner after a successful transfer. The new owner must re-delegate if needed.\nHow do I check if a cNFT can be transferred?\nUse the canTransfer helper function. It returns true if the cNFT is not frozen and not marked as non-transferable (soulbound).\nGlossary\nTermDefinition\ntransferV2\nThe Bubblegum V2 instruction that transfers a cNFT from one owner to another\n\nPermanent Transfer Delegate\nA collection-level authority that can transfer any cNFT without owner consent\n\ncanTransfer\nA helper function that checks whether a cNFT can be transferred (not frozen or soulbound)\n\nLeaf Owner\nThe current owner of the compressed NFT\n\nNew Leaf Owner\nThe wallet address that will receive ownership of the cNFT after transfer","tokens":1222,"crawled_at":1791196238482}
+{"id":10604,"url":"https://docs.sui.io/onchain-finance/payments","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Payments | Sui Documentation","text":"Sui provides multiple primitives for building payment flows, from reading balances and constructing multi-step transactions to sponsoring gasGasThe computational cost of execution and object storage for a transaction. fees on behalf of your users. The approach you choose depends on your use case:\n\nReading balances: Query address balances to display a user's holdings or verify sufficient funds before processing a payment.\n\nConstructing payments: Use payment intents to compose multi-step payment workflows (split coins, transferTransferChanging the owner of an asset., merge) into a single atomic programmable transaction block.\n\nSponsoring gas: Use sponsored transactions so your users pay no gas fees. This is common for onboarding flows and stablecoin transfers where you want a Web2-like experience.\n\nGasless stablecoin transfers: Sui supports zero-fee stablecoin transfers for eligible transactions, removing gas costs entirely for supported assets.\n\nRecurring and delegated spending: Use allowances to let a service, agent, or team member pull from a user's addressAddressA unique, anonymous identity on a blockchain network. balance within limits the user sets and can revoke.\n\nPayment verification: The Payment Kit provides secure payment verification, receipt management, and duplicate prevention for production payment systems.\n\nChoosing a payment approach​\n\nUse caseApproachKey benefit\nDisplay user balances\nAddress Balances\nDirect balance reads without coin enumeration\n\nSend assets to a recipient\nPayment Intents\nAtomic multi-step transactions\n\nSubsidize user gas costs\nSponsored Transactions\nZero gas for the end user\n\nStablecoin payments\nGasless Stablecoin Transfers\nNo gas fees for eligible stablecoin transfers\n\nProduction payment processing\nPayment Kit\nReceipts, verification, duplicate prevention\n\nSubscriptions and agent budgets\nAllowances\nBounded, revocable pulls from a funder's balance without per-payment signatures\n\nRegulatory considerations\nPayment applications might be subject to KYC, AML, and money-transmitter licensing requirements depending on your jurisdiction and business model. These requirements are outside the scope of Sui documentation. Consult qualified legal counsel before launching a payment product.\n\nRelated topics\n\nAddress Balances\nAddress balances introduce a canonical balance system for fungible assets tied to Sui addresses, replacing coin-selection complexity with a single per-address accumulator value.\nPayment Intents\nUse programmable transaction blocks to compile multi-step payment workflows into a single atomic transaction.\nWhat is a PTB?\nProgrammable transaction blocks are a group of commands that complete a transaction on Sui.\nSponsored Transactions\nSponsored transactions let you pay gas fees on behalf of another user, reducing onboarding friction for users who don't own SUI.\n\nChoosing a payment approach\n\nWas this page helpful?","tokens":725,"crawled_at":1791196226129}
+{"id":10605,"url":"https://forum.solana.com/t/srfc-00004-native-events-program/32","domain":"forum.solana.com","chapter":"governance_daos","title":"sRFC 00004: Native Events Program - sRFC - Solana Developer Forums","text":"sRFC 00004: Native Events Program\n\nsRFC\n\nevent,\nlogging,\nsimd,\nindexing\n\nngundotra\n\nMarch 15, 2023, 3:52pm\n\n1\n\nSolana Events for Programs\n\nSummary\n\nThis RFC proposes a native “Event” program built into the Solana runtime to address the current limitations in log storage and validation. By implementing a standardized event interface, we aim to achieve the following goals:\n\nLogs should be available as long as Solana blocks are available.\n\nThere must be a way to validate that logs (or events) returned by the RPC operators are stored in the block and are truthful.\n\nThere must be a clear pricing curve for permanent log storage on Solana, either implicit or explicit.\n\nProblem Description\n\nCurrently, Solana logs are truncated to 10kb max per transaction, and there is no process to find “untruncated” logs stored in blocks or to validate the logs returned by RPC nodes. Solana applications work around log-truncation by calling another program (like a “no operation” program) and sending the desired log as instruction data. Such invocations are reliably returned by RPC operators, but they could maliciously (or accidentally) drop history of invocations, and nobody would be able to verify without replaying the historical transaction.\n\nIt’s worth noting that EVM chains index their programs only through events, since program data layout is theoretically unspecified. Indexing solana programs only through logs is currently not feasible until there is a reliable way to retrieve them.\n\nGoals\n\nDefine an “Event” interface for Solana programs that allows logs to be stored for as long as Solana blocks are available.\n\nImplement a mechanism to validate that the logs returned by RPC operators are accurate and stored in the block.\n\nEstablish a clear pricing curve for log storage on Solana.\n\nPossible Implementation\n\nHigh level summary\n\nExpose a new program built-in to the runtime, that merkelizes logs emitted over the course of a block and writes the merkle tree root to a read-only account via PDA (e.g. [block_number.to_le_bytes()]) at the end of the block. These are referred to as EventStorage accounts. This should allow dApps to reliably use this built-in program’s logs for app-critical needs such as indexing.\n\nEvent Instruction and Storage\n\nWe can define an event program for Solana that stores event data into a Solana block, hashes the event data in the whole block into a 32 byte hash, and stores the hash into an EventStorage account. This will allow logs to be recovered from block information, and allow downstream clients to reliably verify RPC responses.\n\n/// Event program instruction\nenum EventProgramInstruction {\n/// `LogEvent` instruction that takes an `Event` as input\n/// and logs the event to the on-chain storage.\nLogEvent(Vec<u8>)\n}\n\n/// EventStorage account\npub struct EventStorage {\npub block_id: u64,\npub events_hash: u32\n}\n\n/// Event struct returned by RPC operators\nstruct Event {\npub block_index: u16,\npub event_data: Vec<u8>\n}\n\nLog Validation\n\nTo validate that the logs returned by RPC operators are accurate and stored in the block, we can ask RPC nodes to return the Merkle proof along with the requested logs, allowing clients to verify the logs’ authenticity against the Merkle root stored in the EventStorage account.\n\nPricing Curve\n\nTo establish a clear pricing curve for log storage on Solana, we can implement the following:\n\nModify the LogEvent instruction to charge a storage fee, paid in native tokens, based on the size of the event data to the feePayer of the executing transaction.\n\nIntroduce a StorageFee struct that contains the base storage fee and the additional fee per byte of event data that can be modified via SIMD proposal.\n\nAlternative Solutions\n\nWe could instead just add a pricing mechanism for existing logs emitted via sol_log_data that requires RPC operates to store them permanently. This could be as simple as increasing the CU for log syscalls to reflect an explicit “price per byte” of a transaction. If transaction logs are usually capped at 10 KiB, and a single transaction has a flat cost of 5000 lamports (at minimum, for a single signer), then each byte of transaction execution record is implicitly priced at 0.5 lamports per byte.\n\nCurrently, this low cost of adding to the Solana ledger incentivizes applications to run their own validator to retrieve logs their programs have emitted. This can be both a time-expensive and financially-expensive operation for an application to run their own validator to simply index & debug their own program.\n\nPerhaps by introducing a separate fee schedule for logging that has price per byte > 0.5 lamports/byte, we can discourage the volume of logging per transaction, to less than 10 KiB. This would allow most currently existing RPC operators to comply with an SLA to consistently deliver complete logs for each transaction.\n\nRecommended Implementation\n\nWe recommend implementing the built-in event program and storage as described above. This approach would address the current limitations in log storage and validation while also providing clear pricing for writing data to the Solana ledger.\n\nThere are 2 issues with the alternative approach of simply adding explicit transaction fees for logging.\n\nOne, existing programs that perform logging will now have increased fees, which may cause unfair competitive disadvantage between DeFi dApps. Two, the only mechanism to validate transaction logs returned by RPC operators is to run your own validator & compare transaction logs after transaction replay.\n\nIn comparison, the built-in program also provides a new mechanism to define log storage, but provides a superior method to validate logs that reduces burden on dApps. Thus we recommend the built-in event program solution, and encourage further implementation research.\n\n6 Likes\n\njoec\n\nMarch 15, 2023, 7:18pm\n\n2\n\nCool!\n\nSo, just for clarity: you basically take all of the emitted logs for a block, hash them into a merkle tree, store the root in the account for that blockhash, and can verify all logs emitted during that block are valid via the merkle proof?\n\nSo with this implementation, one could get their program logs from their RPC provider, and the RPC provider can also provide the merkle proof to validate that those logs are represented in the stored account?\n\naka, “proof of logging”\n\nSince the suggested program is proposed to be embedded in the runtime, I’m curious how we could possibly expand/leverage this proposal to solve for the issue of truncating the logs as well.\n\nThinking about something like persistent logging or a logging retention pipeline, if an enterprise-scale large program wanted to retain lots of logs for a period of time and also have the validation proposed here that those logs are accurate and represented within the block, how can we possibly integrate un-truncating logs?\n\n2 Likes\n\nngundotra\n\nMarch 16, 2023, 2:20pm\n\n3\n\nYes and instead of logging, they’ll be executing a syscall to the event program, which does the hashing at the end of the block, and posts the merkle root to an EventStorage account on-chain. This should also increase the fee charged to the transaction feePayer, proportional to the amount of data that was emitted to the event program.\n\nIf an enterprise-scale large programs want to store “logs” (aka sol_log_data logs) then they should run their own validator & only trust the logs that are emitted from replaying their programs own transactions. This could potentially be a good business for RPC operators.\n\nI think it’s fine to make current “logs” a very transient & unreliable source of program metadata, and then encourage RPC operators to charge customers to serve program logs, since they are additional burden on RPC operation.\n\n1 Like\n\nsanthosh\n\nMarch 16, 2023, 3:02pm\n\n4\n\nI think it would be great if there was a reliable way to associate events with programs that emitted them!\n\n4 Likes\n\nngundotra\n\nMarch 25, 2023, 12:00am\n\n5\n\nHere’s a concrete example of program control flow that is uninterpretable without access to full logs for transaction history.\n\nThese two transaction look like they both have the same control flow, but the second inner instruction is actually different.\n\nProgram A → Program B\n\nProgram A → Program C\n\nProgram A → Program B\n\nProgram B → Program C\n\nWith full logs, we would be able to index the 2nd inner instruction properly, but when we only have access to truncated logs, like in the 2nd transaction, we cannot tell which program invoked program C.\n\nJust wanted to add this example to the discussion to emphasize the importance of this primitive for indexing programs. Personally I don’t think there are any RPC providers that offer “full logs” as a service, but having a few different ones offering that service would solve this problem entirely.\n\nCode for the repro transactions here: GitHub - ngundotra/solana-event-logging-repro: indexing is hard\n\n4 Likes\n\nRelated topics\n\nTopic\n\nReplies\nViews\nActivity\n\nsRFC 00013 - CPI Events\n\nsRFC\n\n5\n\n1006\n\nJune 16, 2023\n\nSteak Proposal - A Solana Proposal For Memecoins\n\nResearch\n\n0\n\n388\n\nJuly 2, 2026\n\nsRFC 00011: A smart contract that allows for easy storage and retrieval of data on-chain\n\nsRFC\n\n4\n\n2139\n\nOctober 1, 2023\n\nsRFC 00015: Interfaces\n\nsRFC\n\n10\n\n2947\n\nJune 9, 2023\n\nsRFC 00014: Rethinking SPL Token\n\nsRFC\n\n6\n\n2421\n\nJune 7, 2023","tokens":2328,"crawled_at":1791196244910}
+{"id":10606,"url":"https://docs.sui.io/onchain-finance/payment-intents","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Payment Intents | Sui Documentation","text":"A payment intent is a single atomic transactionTransactionA number of commands that execute on inputs to define the result of the transaction. that bundles multiple, heterogeneous payment operations. Rather than signing a separate transaction for each onchain action, you compose multiple operations into one batch: swaps, deposits, transfers, and balance reads. A payment intent is a form of programmable transaction block (PTB). All operations execute as a unit. If any operation fails, the entire batch reverts and no state changes onchain.\n\nA traditional payment flow on most chains requires one transaction per action. To swap, deposit, and transferTransferChanging the owner of an asset. in sequence, you sign three times, pay gasGasThe computational cost of execution and object storage for a transaction. three times, and risk partial completion if one transaction fails after another succeeds.\n\nA payment intent collapses the same flow into one signed transaction with the following properties:\n\nAtomic execution: All operations succeed together or none apply. There is no intermediate state to clean up.\n\nSingle signature: You approve the full intent once, not once per step.\n\nOne gas payment: The whole batch shares a gas budget. The transaction sponsor pays once. The sponsor can be your app, a relayer, or the user.\n\nParallel reads: Resolution steps that do not depend on each other run concurrently before the payment intent is built. These include balance lookups, route quotes, and contact resolution.\n\nThe underlying PTBProgrammable transaction blocksDefine all user transactions on Sui. gives a payment intent the following guarantees:\n\nDeterminism: The compiled payment intent is the source of truth. The natural-language intent is a convenience, but the bytes you sign describe the exact onchain effect.\n\nComposability: Outputs of earlier commands feed into later ones without leaving the transaction. You do not need to wait for one transaction to confirm before building the next.\n\nSponsored gas: Apps can pay gas on behalf of users. A three-operation payment intent that costs around 0.005 USD is sponsorable at scale, which removes the need for users to hold SUI just to pay fees.\n\nFast finalityFinalityThe state in which a transaction is permanently recorded and cannot be revoked.: Sui consensusConsensusThe process by which the majority of nodes agree on the current state of the network commits transactions in under a second, so a multi-step intent feels like a single action to the user.\n\nAnatomy of a payment intent​\n\nA payment intent moves through three phases:\n\nResolve. The app reads onchain and offchain context in parallel, including token balances, swap routes, pool yields, and contact addressesAddressA unique, anonymous identity on a blockchain network..\n\nPlan. The app arranges the resolved values into an ordered sequence of PTB commands. Order matters because later commands can consume outputs from earlier ones.\n\nExecute. The user signs once. The payment intent submits to the network and either commits all commands or reverts all of them.\n\nSwap, save, send example​\n\nConsider this request:\n\nSwap 10% into SUI, save 50% of my remaining USDC, then send 100 USDC to a contact named Alice.\n\nStarting balance: 2,000 USDC.\n\nResolution​\n\nThe app dispatches five reads in parallel:\n\nReadResult\nWallet balance\n2,000 USDC\n\nCetus route for USDC to SUI\n200 USDC swaps to 212.77 SUI at 0.03% slippage\n\nNAVI USDsui pool\n8.4% APY, 48M USD TVL\n\nContact resolution for Alice\n0xa4bb…b27c, verified\n\nGas estimate\n0.005 USD, sponsored\n\nPlan​\n\nThe planner orders the operations so that later math uses the correct inputs:\n\nSwap 200 USDC to SUI through Cetus. This is 10% of the starting balance.\n\nSwap 900 USDC to USDsui and deposit into the NAVI pool. This is 50% of the 1,800 USDC that remains after step 1, not 50% of the original 2,000.\n\nTransfer 100 USDC to 0xa4bb…b27c.\n\nIf you reorder these operations, you get a different result. Computing the 50% before the swap saves 1,000 USDC instead of 900. The planning phase makes the order explicit before signing.\n\nExecute​\n\nThe three operations compile into one payment intent. You sign once and the network commits the batch in roughly 0.6 seconds. The final balances are:\n\nAvailable USDC: 800 USD, instantly spendable.\n\nEarning USDsui: 900 USD in the NAVI pool at 8.4% APY, accruing from the next block.\n\nHeld SUI: 212.77 SUI at the executed price.\n\nBecause the payment intent is atomic, a failure in any leg reverts all three operations. Failures include a slippage breach on the swap, a paused pool, or an invalid recipient. You never end up in a state where the swap completes but the deposit does not.\n\nComparison with single-action chains​\n\nOn a chain that does not support transaction batching, the same swap, save, send flow requires three independent transactions. Each pays its own gas, each can fail independently, and the user signs three times. Mid-flow failure leaves you in a partial state that you have to detect and reconcile.\n\nA payment intent removes that class of bug from the application. The transaction either fully succeeds or fully reverts, and the user sees one outcome.\n\nAdditional examples​\n\nThe pattern generalizes to any chain of payment operations. The intents below each compile to a single payment intent.\n\nDeposit autosplit​\n\nWhen a deposit arrives, keep 1,000 USDC liquid, deposit 60% of the rest into a yield pool, and convert the remainder to SUI.\n\nThe trigger is an inbound transfer. The payment intent reads the new balance, subtracts the reserve, splits the remainder, and routes each portion. One signature covers the recurring rule.\n\nBill batch​\n\nPay rent, utilities, and my phone bill on the first of the month.\n\nThree transfers to three resolved contacts, batched atomically. If any recipient address fails validation, no payment goes out and you can fix the issue before retrying.\n\nRebalance​\n\nSell enough SUI to bring my portfolio back to 70% USDC, 30% SUI.\n\nThe payment intent reads current balances and prices, computes the delta, and executes a single swap. The read and the swap are part of the same atomic unit, so the price you swap at is the price you read.\n\nConditional send​\n\nIf my USDC balance is above 5,000, send 500 to savings.\n\nA balance check and a conditional transfer compose into one payment intent. The check runs onchain at execution time, not at planning time, so the decision uses fresh state.\nRelated topics\n\nWhat is a PTB?\nProgrammable transaction blocks are a group of commands that complete a transaction on Sui.\n\nAnatomy of a payment intent\nSwap, save, send exampleResolution\nPlan\nExecute\n\nComparison with single-action chains\nAdditional examplesDeposit autosplit\nBill batch\nRebalance\nConditional send\n\nWas this page helpful?","tokens":1695,"crawled_at":1791196252210}
+{"id":10607,"url":"https://www.metaplex.com/docs/smart-contracts/bubblegum-v2/freeze-cnfts","domain":"www.metaplex.com","chapter":"docs","title":"Freezing and Thawing Compressed NFTs - Bubblegum V2 - Metaplex","text":"Summary\nFreezing and thawing compressed NFTs controls transferability using Bubblegum V2's freeze instructions. This page covers freeze, delegate-and-freeze, thaw, thaw-and-revoke, and making cNFTs soulbound (non-transferable).\nFreeze a cNFT via a leaf delegate or permanent freeze delegate\nDelegate and freeze in a single transaction with delegateAndFreezeV2\nThaw a frozen cNFT and optionally revoke the delegate in one step\nMake a cNFT permanently non-transferable (soulbound) with setNonTransferableV2\nWith Bubblegum V2, we can freeze and thaw Compressed NFTs. This is useful for various use cases, such as staking.\nFreezing a Compressed NFT\nTo freeze a Compressed NFT that has been delegated to a leaf delegate before, we can use the freezeV2 instruction. If it has not been delegated yet, see delegateAndFreezeV2 below. The freezeV2 instruction can be used like this:\nFreeze a Compressed NFT as a leaf delegate\n\nimport {\n\ngetAssetWithProof,\n\nfreezeV2,\n\n} from '@metaplex-foundation/mpl-bubblegum';\n\nconst assetWithProof = await getAssetWithProof(umi, assetId);\n\nawait freezeV2(umi, {\n\n...assetWithProof,\n\nleafOwner: umi.identity.publicKey,\n\nauthority: leafDelegate, // this would default to the payer\n\nleafDelegate: leafDelegate.publicKey,\n\n// If the cNFT is part of a collection, pass the collection address.\n\n//coreCollection: collectionSigner.publicKey,\n\n}).sendAndConfirm(umi);\n\nDelegate and Freeze a Compressed NFT\nTo freeze a Compressed NFT, we can use the delegateAndFreezeV2 instruction. This instruction can be used like this:\nDelegate and Freeze a Compressed NFT\n\nimport {\n\ngetAssetWithProof,\n\ndelegateAndFreezeV2,\n\n} from '@metaplex-foundation/mpl-bubblegum';\n\n// newLeafDelegate should be a publicKey that will be able to thaw the cNFT later.\n\nconst assetWithProof = await getAssetWithProof(umi, assetId);\n\nawait delegateAndFreezeV2(umi, {\n\n...assetWithProof,\n\nleafOwner: umi.identity.publicKey,\n\nnewLeafDelegate,\n\n}).sendAndConfirm(umi);\n\nThawing a Compressed NFT\nTo thaw a Compressed NFT, we can use the thawV2 instruction. This instruction can be used like this:\nThaw a Compressed NFT as a leaf delegate\n\nimport {\n\ngetAssetWithProof,\n\nthawV2,\n\n} from '@metaplex-foundation/mpl-bubblegum';\n\nconst assetWithProof = await getAssetWithProof(umi, assetId);\n\n// delegateAuthority should be a Signer that has been approved as a delegate authority for the cNFT.\n\nawait thawV2(umi, {\n\n...assetWithProof,\n\nauthority: delegateAuthority,\n\n}).sendAndConfirm(umi);\n\nIf the cNFT has been delegated to a permanent freeze delegate, we can thaw it like this:\nThaw a Compressed NFT as a permanent freeze delegate\n\nimport {\n\ngetAssetWithProof,\n\nthawV2,\n\n} from '@metaplex-foundation/mpl-bubblegum';\n\nconst assetWithProof = await getAssetWithProof(umi, assetId);\n\nawait thawV2(umi, {\n\n...assetWithProof,\n\nauthority: permanentFreezeDelegate,\n\n}).sendAndConfirm(umi);\n\nThaw and Revoke a Delegate Authority\nTo thaw and revoke a Delegate Authority at the same time, we can use the thawAndRevokeV2 instruction. This instruction can be used like this:\nThaw and Revoke a Delegate Authority\n\nimport {\n\ngetAssetWithProof,\n\nthawAndRevokeV2,\n\n} from '@metaplex-foundation/mpl-bubblegum';\n\n// delegateAuthority should be a Signer that has been approved as a delegate authority for the cNFT.\n\nconst assetWithProof = await getAssetWithProof(umi, assetId);\n\nawait thawAndRevokeV2(umi, {\n\n...assetWithProof,\n\nauthority: delegateAuthority,\n\n}).sendAndConfirm(umi);\n\nMake a cNFT Soulbound\nTo make a cNFT Soulbound the cNFT has to be part of a mpl-core collection with the permanentFreezeDelegate Plugin. Using the setNonTransferableV2 instruction, we can make the cNFT non-transferable.\nMake a cNFT Soulbound\n\nimport {\n\ngetAssetWithProof,\n\nsetNonTransferableV2,\n\n} from '@metaplex-foundation/mpl-bubblegum';\n\nconst assetWithProof = await getAssetWithProof(umi, assetId);\n\nawait setNonTransferableV2(umi, {\n\n...assetWithProof,\n\nauthority, // The permanent freeze delegate on collection\n\ncoreCollection: collection.publicKey,\n\n}).sendAndConfirm(umi);\n\nNotes\nA cNFT must be delegated to a leaf delegate before it can be frozen with freezeV2. Use delegateAndFreezeV2 to do both in one transaction.\nThe permanent freeze delegate operates at the collection level and requires the PermanentFreezeDelegate plugin on the collection.\nSoulbound (non-transferable) status set by setNonTransferableV2 is permanent and cannot be reversed.\nFrozen cNFTs cannot be transferred or burned by the owner. Only the freeze authority can thaw them.\nFAQ\nHow do I freeze a compressed NFT?\nUse freezeV2 with a leaf delegate or permanent freeze delegate. If the cNFT hasn't been delegated yet, use delegateAndFreezeV2 to delegate and freeze in one transaction.\nWhat is the difference between a leaf delegate freeze and a permanent freeze?\nA leaf delegate freeze is asset-level — the owner must delegate first. A permanent freeze delegate is collection-level — it can freeze any cNFT in the collection without owner interaction, if the PermanentFreezeDelegate plugin is enabled.\nHow do I make a cNFT soulbound?\nUse setNonTransferableV2 with the permanent freeze delegate authority. The collection must have the PermanentFreezeDelegate plugin. This is permanent and cannot be reversed.\nCan a soulbound cNFT be made transferable again?\nNo. The non-transferable flag is permanent. Once a cNFT is made soulbound, it cannot be transferred to another wallet.\nGlossary\nTermDefinition\nfreezeV2\nInstruction that freezes a cNFT, preventing transfers until thawed\n\nthawV2\nInstruction that unfreezes a cNFT, allowing transfers again\n\ndelegateAndFreezeV2\nInstruction that delegates to a leaf delegate and freezes the cNFT in one transaction\n\nthawAndRevokeV2\nInstruction that thaws a cNFT and revokes the delegate authority in one transaction\n\nsetNonTransferableV2\nInstruction that permanently makes a cNFT non-transferable (soulbound)\n\nPermanent Freeze Delegate\nA collection-level authority that can freeze/thaw any cNFT without owner consent\n\nSoulbound\nA non-transferable cNFT permanently bound to its owner's wallet","tokens":1514,"crawled_at":1791196278050}
+{"id":10608,"url":"https://docs.sui.io/onchain-finance/choose-payments-model","domain":"docs.sui.io","chapter":"layer1_layer2","title":"Choose a Payment Model | Sui Documentation","text":"Sui supports a range of payment models, from direct transfers to structured checkout flows built on Payment Kit. The right choice depends on whether you need receipts, duplicate prevention, or custom spending logic. Most integrations start from one of the common models below, and many combine several in a single transactionTransactionA number of commands that execute on inputs to define the result of the transaction..\n\nBasic transferTransferChanging the owner of an asset.Payment Kit\nComplexity\nLow\nMedium\n\nBest for\nWallets, peer-to-peer sends, treasury moves\nMerchant checkout, invoicing, subscriptions\n\nReceipts\nNone, so read from events or effects\nBuilt-in PaymentReceipt objects\n\nDuplicate prevention\nNone\nBuilt-in through PaymentRegistry\n\nGasGasThe computational cost of execution and object storage for a transaction. sponsorship\nYes\nYes\n\nOnchain audit trail\nTransfer events only\nReceipt objects and events\n\nMoveMoveAn open source programming language used for all activity on Sui. code to write\nNone\nNone\n\nBasic transfer​\n\nA basic transfer moves value directly, with no receipt objectObjectThe basic unit of storage on Sui. and no onchain payment record. Read the outcome from transaction effects and events. There are two ways to deliver funds.\n\nSend to an addressAddressA unique, anonymous identity on a blockchain network. balance​\n\nThe address balance functions balance::send_funds and coin::send_funds deposit value into a canonical per-address balance. Deposits from different senders merge automatically, so the recipient manages no objects. This path also enables gasless stablecoin transfers.\n\nexamples/ptb-cookbook/src/coin-selection.ts\nconst tx = new Transaction();\n\n// Send 1 SUI to the recipient's address balance. The SDK selects the funding source.\ntx.moveCall({\ntarget: '0x2::balance::send_funds',\ntypeArguments: ['0x2::sui::SUI'],\narguments: [tx.balance({ balance: 1_000_000_000n }), tx.pure.address(recipientAddress)],\n});\n\nTransfer a coin object​\n\nTransfer a Coin<T> object when the recipient or an integrating contract expects a distinct object, such as a payment that a downstream Move call consumes:\n\nexamples/ptb-cookbook/src/coin-selection.ts\nconst tx2 = new Transaction();\n\n// Split from a specific coin object (not the gas coin).\nconst [coin] = tx2.splitCoins(tx2.object('0xSpecificCoinId'), [tx2.pure('u64', 500_000_000n)]);\ntx2.transferObjects([coin], tx2.pure.address(recipientAddress));\n\nLearn more in Using Address Balances and Building Programmable Transaction Blocks.\n\nPayment Kit​\n\nUse Payment Kit when you need structured receipts and duplicate prevention without writing custom Move. Payment Kit offers 2 processing modes:\n\nRegistry payments: Process the payment through a PaymentRegistry. The registry stores a PaymentRecord internally, rejects duplicates, and optionally accumulates funds for later withdrawal. Use this mode when compliance, accounting, or retry safety requires payment history.\n\nEphemeral payments: Process a one-time payment with no persistent record. The function transfers funds immediately, returns a receipt, and emits an event, at lower gas cost. Use this mode when an external system already tracks payments and duplicates are not a concern.\n\nProcess a registry payment​\n\nThe registry entry point takes a nonce, the expected amount, and the payment coin:\n\nmodule payment_kit::payment_kit;\n\npublic fun process_registry_payment<T>(\nregistry: &mut PaymentRegistry,\nnonce: String,\npayment_amount: u64,\ncoin: Coin<T>,\nreceiver: Option<address>,\nclock: &Clock,\nctx: &mut TxContext\n): PaymentReceipt\n\nThe function verifies that the coin value matches payment_amount, checks the composite key for a duplicate, records the payment, transfers funds to receiver or the registry, returns a PaymentReceipt, and emits an event. It aborts with EDuplicatePayment when the same key was already processed, and with EPaymentAmountMismatch when the coin value differs from the expected amount.\n\nDuplicate prevention relies on a PaymentKey derived from the nonce, amount, coin type, and receiver address. Generate the nonce as a UUIDv4 of at most 36 characters, and reuse the same nonce when you retry a payment so the retry cannot double-charge.\n\nEncode a payment request as a URI​\n\nPayment Kit defines a transaction URI format that wallets parse into a ready-to-sign payment. Include the registry parameter to route through a registry, or omit it to process an ephemeral payment:\n\nsui:pay?receiver=0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef\n&amount=1000000000\n&coinType=0x0000000000000000000000000000000000000000000000000000000000000002::sui::SUI\n&nonce=550e8400-e29b-41d4-a716-446655440000\n&label=Coffee%20Shop\n&registry=default-payment-registry\n\nPercent-encode every parameter value according to RFC 3986. The amount value is the native amount of the coin type, so 1000000000 MISTMISTThe smallest unit of SUI. represents 1 SUI.\n\ntip\nVerify the receiver, amount, coin type, and packagePackageSmart contracts on Sui. ID against your own expected values rather than trusting client-supplied or URI-supplied data, and confirm payment against onchain receipts and events rather than client state. For broader guidance, see Security Best Practices.\n\nCommon payment pitfalls​\n\nThese 4 mistakes account for most payment integration bugs:\n\nInteger math only: SUI has 9 decimals (1 SUI = 1,000,000,000 MIST). Never use floating-point arithmetic on token amounts. Always work in the smallest unit, MIST for SUI, and convert for display only.\n\nPer-coin-type decimals: Not all tokens use 9 decimals. USDC on Sui has 6 decimals. Always check CoinMetadata.decimals for the specific coin type before you convert between human-readable and onchain amounts.\n\nCoin selection and merging: A user might hold several Coin objects of the same type. If the payment requires more than any single coin holds, merge them first with tx.mergeCoins() in your transaction, or use tx.splitCoins() to extract the exact amount you need.\n\nGas coin reservation: If you pay gas in SUI and also transfer SUI in the same transaction, the transaction implicitly uses the gas coin for gas. Split the transfer amount from the gas coin rather than selecting a separate SUI coin object, which avoids insufficient gas errors.\n\nGas strategies​\n\nEvery payment transaction needs gas, except for qualifying stablecoin transfers. Choose a strategy based on your user experience goals.\n\nUser pays gas​\n\nThe sender pays in SUI. This option takes the least work to implement, but your users must hold SUI. See Gas Fees.\n\nGasless stablecoin transfer​\n\nFor allowlisted stablecoins sent through balance::send_funds, the network waives gas fees entirely, so the sender needs no SUI. Protocol configuration governs the allowlist, which currently includes USDC, USDsui, USDY, FDUSD, AUSD, USDB, and Ethena USDe. A transaction qualifies only when all of the following hold:\n\nThe transaction consists of allowlisted balance or coin operations, primarily 0x2::balance::send_funds<T>, on an allowlisted stablecoin type.\n\ngasPayment is empty and gasPrice is 0.\n\nThe transaction writes no objects, and it consumes or converts all input coins to address balances.\n\nBuild the transfer with SuiGrpcClient, which detects eligibility during simulation and sets the gas price and budget to 0 for you:\n\ngasless-transfer.ts\nimport { SuiGrpcClient } from '@mysten/sui/grpc';\nimport { Transaction } from '@mysten/sui/transactions';\n\nconst USDC = '0xdba34672e30cb065b1f93e3ab55318768fd6fef66c15942c9f7cb846e2f900e7::usdc::USDC';\n\nconst client = new SuiGrpcClient({\nnetwork: 'mainnet',\nbaseUrl: 'https://fullnode.mainnet.sui.io:443',\n});\n\nconst tx = new Transaction();\ntx.setSender(senderAddress);\n\ntx.moveCall({\ntarget: '0x2::balance::send_funds',\ntypeArguments: [USDC],\narguments: [\ntx.balance({ type: USDC, balance: 1_000_000n }), // 1 USDC\ntx.pure.address(recipient),\n],\n});\n\nconst result = await client.signAndExecuteTransaction({\ntransaction: tx,\nsigner: keypair,\n});\n\ncaution\nGasless stablecoin transfers require a minimum transfer of 0.01, and the network deprioritizes them against fee-paying transactions when it is congested. Any other Move call in the same transaction, including a swap, a mint, or a Payment Kit call, disqualifies the transfer and the transaction then requires a normal gas payment.\n\nSee Gasless Stablecoin Transfers for the full allowlist and the JSON-RPC fallback.\n\nSponsored transactionSponsored transactionWhen one address pays the gas fee for a transaction submitted by another address.​\n\nSponsored transactions pay gas on behalf of the sender, which works with any transaction type:\n\nexamples/ptb-cookbook/src/sponsored.ts\n// === User side ===\n\n// Build the transaction kind (no gas info yet).\nconst tx = new Transaction();\ntx.moveCall({\ntarget: '0xPACKAGE::module::do_something',\narguments: [tx.object('0xSomeObject')],\n});\n\n// Serialize only the transaction kind bytes for the sponsor.\nconst kindBytes = await tx.build({ client, onlyTransactionKind: true });\n\n// === Sponsor side ===\n\n// Reconstruct the transaction from the kind bytes.\nconst sponsoredTx = Transaction.fromKind(kindBytes);\n\n// Set the user as the sender, sponsor as the gas owner.\nsponsoredTx.setSender(userAddress);\nsponsoredTx.setGasOwner(sponsorAddress);\nsponsoredTx.setGasPayment(sponsorGasCoins); // Sponsor's coin objects\n\n// Build the full transaction bytes.\nconst txBytes = await sponsoredTx.build({ client });\n\n// === Both sign ===\n\n// The sponsor signs first.\nconst sponsorSig = await sponsorKeypair.signTransaction(txBytes);\n// The user signs second.\nconst userSig = await userKeypair.signTransaction(txBytes);\n\n// === Submit ===\n\nconst result = await client.executeTransaction({\ntransaction: txBytes,\nsignatures: [userSig.signature, sponsorSig.signature],\n});\nconst sponsoredTx2 = Transaction.fromKind(kindBytes);\nsponsoredTx2.setSender(userAddress);\nsponsoredTx2.setGasOwner(sponsorAddress);\n\n// Empty gas payment array tells the protocol to deduct gas from the\n// sponsor's SUI address balance. The SDK sets the ValidDuring expiration\n// and nonce automatically when you build with a connected client.\nsponsoredTx2.setGasPayment([]);\n\n// Building with a connected client resolves the expiration and nonce.\nconst txBytes2 = await sponsoredTx2.build({ client });\n\nSponsoring from an address balance removes the gas coin entirely. Pass an empty array to setGasPayment, which lets the user sign first and the sponsor sign afterward, and removes the risk that a competing transaction locks the gas coin:\n\nexamples/ptb-cookbook/src/sponsored.ts\nconst sponsoredTx2 = Transaction.fromKind(kindBytes);\nsponsoredTx2.setSender(userAddress);\nsponsoredTx2.setGasOwner(sponsorAddress);\n\n// Empty gas payment array tells the protocol to deduct gas from the\n// sponsor's SUI address balance. The SDK sets the ValidDuring expiration\n// and nonce automatically when you build with a connected client.\nsponsoredTx2.setGasPayment([]);\n\n// Building with a connected client resolves the expiration and nonce.\nconst txBytes2 = await sponsoredTx2.build({ client });\n\nSubmit dual-signed transactions directly to a full nodeFull nodeResponsible for validating blockchain activity. rather than through the sponsor, so the sponsor cannot delay or withhold them. See Sponsored Transactions for the full flow and risk considerations.\nRelated topics\n\nGasless Stablecoin Transfers\nGasless stablecoin transfers on Sui enable peer-to-peer payments of qualified stablecoins to execute without paying gas fees in SUI.\nUsing Address Balances\nAddress balances introduce a canonical balance system for fungible assets tied to Sui addresses. Learn how to send, withdraw, and query address balances.\nBuilding Transactions\nUsing the Sui TypeScript SDK, you can create programmable transaction blocks to perform multiple commands in a single transaction.\nPayment Kit Standard\nThe Sui Payment Kit is a robust, open-source payment processing toolkit that provides secure payment verification, receipt management, and duplicate prevention for applications built on the Sui blockchain.\n\nBasic transferSend to an address balance\nTransfer a coin object\n\nPayment KitProcess a registry payment\nEncode a payment request as a URI\n\nCommon payment pitfalls\nGas strategiesUser pays gas\nGasless stablecoin transfer\nSponsored transaction\n\nWas this page helpful?","tokens":3082,"crawled_at":1791196273596}