LEO34344086 (@leo34344086) • Hey

web3 worker

Stats

Following: 16
Followers: 7

Publications

I just voted "Yes" on "Add Metis Chain support for MAI Bridging" https://snapshot.org/#/stgdao.eth/proposal/0xf1274081c9f4db1db77f30f21b53f61dde8716f8d3f2aac7367709bd4af369b2 #Snapshot
I just voted "Yes" on "Re-Enable Fantom Pools" https://snapshot.org/#/stgdao.eth/proposal/0x3cb9430062af89937887e9d359e4765de4f138c6bcea49ee66225a8fa998e97b #Snapshot
I just voted "Yes" on "Deprecation of METIS Pool on BSC" https://snapshot.org/#/stgdao.eth/proposal/0x85c675f303a69df297e1fdcf6dc2845366a8672362e946150ba4a4d7928cc8ea #Snapshot
I just voted "Against" on "[Non-Constitutional] Fund the Arbitrum Grants Framework Proposal Milestone 1" https://snapshot.org/#/arbitrumfoundation.eth/proposal/0xa0e14b85197d73e825ac30f72b7d895d644ed06159a32a578f4efe47a2739b2f #Snapshot
I just voted "YAE" on "[TEMP CHECK] Treasury Management - Introducing StrategicAssetManager " https://snapshot.org/#/aave.eth/proposal/0x4ec24a25d7d3af6c4d1a9782d791fd1fe2323527d3d8cb23b7c8c41f38d7e462 #Snapshot
I just voted "1/10" on "Making Protocol Fees Operational: Fee options for V3" https://snapshot.org/#/uniswap/proposal/0xb471984c1daef6742be4d4983339af7ad140c3dfcfc883508fd975f5abe0e8c9 #Snapshot
I just voted "1/10" on "Making Protocol Fees Operational: Fee options for V3" https://snapshot.org/#/uniswap/proposal/0xb471984c1daef6742be4d4983339af7ad140c3dfcfc883508fd975f5abe0e8c9 #Snapshot
I just voted "Optimism" on "Making Protocol Fees Operational: Initial deployment chain" https://snapshot.org/#/uniswap/proposal/0xa47a49305ab418cb2ceb9da1290cbe022671d5feeb5e2a344bfcd1edbe0720d6 #Snapshot
I just voted "ETH" on "Making Protocol Fees Operational: Asset to be held in the treasury" https://snapshot.org/#/uniswap/proposal/0x4b362044000714197ab43d5f2155977976dcc7cf1cb28d945e1168ae7ac61f90 #Snapshot
I just voted "Yes ser 🙌" on "Do you like the Snapshot integration with Lenster?" https://snapshot.org/#/yoginth.eth/proposal/0x9287c40edcd68c362c7c4139fe3489bbaaa27cf4de68be5c218a82d0f252e718 #snapshotlabs
I just voted "Against" on "AIP 1.05: Return 700M $ARB to the DAO Treasury " https://snapshot.org/#/arbitrumfoundation.eth/proposal/0xe8bc33b7849bd1d7984a8d638444e2dd97b0dfa3f5f2c9dff28fcfe0247bdab3 #snapshotlabs
I just voted "Against" on "AIP 1.05: Return 700M $ARB to the DAO Treasury " https://snapshot.org/#/arbitrumfoundation.eth/proposal/0xe8bc33b7849bd1d7984a8d638444e2dd97b0dfa3f5f2c9dff28fcfe0247bdab3 #snapshotlabs
I just voted "For" on "AIP-1.2 - Foundation and DAO Governance" https://snapshot.org/#/arbitrumfoundation.eth/proposal/0x373dfa89fc9c5ccba8ed83fa3fa4f233edd270075b5f8f4f3902b408318d9d17 #snapshotlabs
I just voted "Yes" on "Create a Secure UniswapV3 Oracle for STG with Arrakis PALM" https://snapshot.org/#/stgdao.eth/proposal/0x9b511ccf8bd097176255da63725877de9f80caeea8a28256ff50dfad10a3820d #snapshotlabs
I just voted "Yes" on "Create a Secure UniswapV3 Oracle for STG with Arrakis PALM" https://snapshot.org/#/stgdao.eth/proposal/0x9b511ccf8bd097176255da63725877de9f80caeea8a28256ff50dfad10a3820d #snapshotlabs
I just voted on "[ARC] E-Mode Parameter Changes for V3 Avalanche, Optimism, Polygon, and Arbitrum " https://snapshot.org/#/aave.eth/proposal/0x84deca82139320b2570f04211b249e37b8a7602b4a0ed70e6fa772c9f6e94550 #snapshotlabs
I just voted "Yes - create new subdomain" on "[Temperature Check] Post-BSL cross-chain deployment process and creation of new uniswap.eth subdomain" https://snapshot.org/#/uniswap/proposal/0x0f8a85d90759acf3a6fdc018e20b991f3562847122a8142c4e166c71d0e755e3 #snapshotlabs
I just voted "Yes" on "Make Velodrome the STG Hub on Optimism" https://snapshot.org/#/stgdao.eth/proposal/0xd78c441994d140edde34131051113479651c593ab83badebc537a347ba86b705 #snapshotlabs
I trust consensys. I just voted on "[TEMP CHECK] Incentivized Delegate Campaign (3-month)" https://snapshot.org/#/aave.eth/proposal/0xf6da417983653f7e7f5560a8e16ad77d5e25533bba9157abfd222347b40d09d0 #snapshotlabs
I am looking for the launch of aave on starknet. I am sure this will bring huge tvl to stark I just voted "YEA" on "[TEMP CHECK] - Launch Aave V3 on Starknet" https://snapshot.org/#/aave.eth/proposal/0xde90f4d29c4c5dd55cba023b29bdde8c49e37f70c3398668a78e2f173a61b4e6 #snapshotlabs
I just voted "YAE" on "[TEMP CHECK] Add support for wstETH on Polygon v3" https://snapshot.org/#/aave.eth/proposal/0x9d7296b06a66d6d6b4c9e85051477a4d62d066e3f56c248bcc85cbea00f7c7a4 #snapshotlabs
I just voted "YAE" on "[TEMP CHECK] Polygon v2 to v3 Liquidity Migration " https://snapshot.org/#/aave.eth/proposal/0x478169c0840488588b31d7e23b889b5f9442057db9c7a5b9b6cfdd61fe7108ff #snapshotlabs
I just voted "YAE" on "[ARFC] - Configure Isolation Mode Borrowable Assets - V3 Ethereum" https://snapshot.org/#/aave.eth/proposal/0xef5eed1bdda3a7d6ea2b37b09c7de1960530bb54f24ddc6c7b002447251b6bb4 #snapshotlabs
I just voted "YAE" on "[TEMP CHECK] Aave V3 deployment on BNB Chain" https://snapshot.org/#/aave.eth/proposal/0x4579b562a4ea07c52871f724a8baf156514a97384e9427156d04fb6f0ae91515 #snapshotlabs
Ronnie uses Collateral Swaps. Available across all V3 markets on app.aave.com. Powered by ParaSwap.
I just voted "YAE" on "[TEMP CHECK] - Aave V1 Offboarding Plan" https://snapshot.org/#/aave.eth/proposal/0xb0bfe6dcf39287e5af18fcd0cc3ed80506314a2f89735379d597f430ae5bd5c7 #snapshotlabs
I just voted "YAE" on "[ARFC] - Chaos Labs Risk Parameter Updates - Aave V3 Optimism - 2023.03.22" https://snapshot.org/#/aave.eth/proposal/0x774c478f3adf4b238c73180b5adad589e008c6857b5e514ae5213ecf67c5c81f #snapshotlabs
I just voted on "[ARC] Community Preference for V3 Migration Levers" https://snapshot.org/#/aave.eth/proposal/0x2eca177d50449f541586d4816d27022b73417952f8c5996d99f500cf0c7ec1c3 #snapshotlabs
I just voted "For" on "AIP-1: Arbitrum Improvement Proposal Framework" https://snapshot.org/#/arbitrumfoundation.eth/proposal/0x3be7368a662d1cf12fa4da768d626edbc013be0dc7b994fef2e24d9a54e4033a #snapshotlabs
I just voted "Yes" on "Uniswap V3 Launch on zkEVM" https://snapshot.org/#/uniswap/proposal/0xdc3e034f9b7c876736f1b629c7c9ff9c466205dfe075607d70e69b6af2fa87ef #snapshotlabs
arb to da moon!!!
I just voted "For" on "AIP-1: Arbitrum Improvement Proposal Framework" https://snapshot.org/#/arbitrumfoundation.eth/proposal/0x3be7368a662d1cf12fa4da768d626edbc013be0dc7b994fef2e24d9a54e4033a #snapshotlabs
I just voted "YAE" on "[ARC] Gauntlet Risk Parameter Recommendations for V3 AVAX (2023-03-20)" https://snapshot.org/#/aave.eth/proposal/0x833eca942053ffcaecbedd6c3b0d5f2392f1ad868e57f1babe9b40a2afedaaa3 #snapshotlabs
I just voted "Conservative" on "[ARC] Isolation Mode Recommendations for Aave V3 Avalanche, Polygon, and Arbitrum" https://snapshot.org/#/aave.eth/proposal/0xb1f8b1814d9c09760daa4d7e9fa90d906b2c9ff5fbd20c8d0f5793c4f5cc4999 #snapshotlabs
I just voted "NAY" on "[TEMP CHECK] Aave Chan Initiative 6-Month Budget Proposal" https://snapshot.org/#/aave.eth/proposal/0x22eb6c5cdaf3731d4d6e0f4bb179e4cf6fa87470e87323f373f0bb01baceb9af #snapshotlabs
I just voted "Option 1" on "[ARC] E-Mode Parameter Changes for V3 Avalanche, Optimism, Polygon, and Arbitrum " https://snapshot.org/#/aave.eth/proposal/0xf6bc25809a931910ea490b86b3c847dc30e09fc0d278ebf0bcdd48f4868e35c1 #snapshotlabs
I just voted "YAE" on "[ARFC - Temp check] “MVP” V3 deployment on ZkEVM mainnet" https://snapshot.org/#/aave.eth/proposal/0x0777eb4701023508c03825e2779e6189326ed9b3d1eb6e187d1f6e0f8d154605 #snapshotlabs
I just voted "No" on "[Temperature Check] Deploy Uniswap V3 on Gnosis Chain" https://snapshot.org/#/uniswap/proposal/0x63f6c44e4245e5b90a0f30ebb6932506879f68b149a5f78fd2186125c9144535 #snapshotlabs
I just voted "yes" on "Proposal to Bootstrap liquidity for Stargate USDT pools on Pendle" https://snapshot.org/#/stgdao.eth/proposal/0xb89734985fddc3bc70404eaa6d62100ddeeea26c54c0ea55f66a089f79dde3ca #snapshotlabs
I just voted "YES" on "Safety Module upgrade to v1.5" https://snapshot.org/#/aave.eth/proposal/0x743ae6001bb0fdfa9a8c4475a2489c20917a79084725f0101ac7c1e7f0cf27c6 #snapshotlabs
I’ll never forget when @dragaan.lens put on chain that I was a curator 🙏🏻
gm ☀️ #bytes
*Mining* is a record-keeping service done through the use of computer processing power.[f] Miners keep the blockchain consistent, complete, and unalterable by repeatedly grouping newly broadcast transactions into a *block*, which is then broadcast to the network and verified by recipient nodes.[41] Each block contains a SHA-256 cryptographic hash of the previous block,[41] thus linking it to the previous block and giving the blockchain its name.
Regarding ownership distribution, as of 28 December 2022, 9.62% of bitcoin addresses own 98.51% of all bitcoins ever mined.[53] The largest of these addresses are thought to belong to exchanges, which are keeping their bitcoin in cold storage.
To ensure the security of bitcoins, the private key must be kept secret.[7]: ch. 10 If the private key is revealed to a third party, e.g. through a data breach, the third party can use it to steal any associated bitcoins.[51] As of December 2017, around ₿980,000 have been stolen from cryptocurrency exchanges
If the private key is lost, the bitcoin network will not recognize any other evidence of ownership;[42] the coins are then unusable, and effectively lost. For example, in 2013 one user claimed to have lost ₿7,500, worth $7.5 million at the time, when he accidentally discarded a hard drive containing his private key.[49] About 20% of all bitcoins are believed to be lost—they would have had a market value of about $20 billion at July 2018 prices
In the blockchain, bitcoins are registered to bitcoin addresses. Creating a bitcoin address requires nothing more than picking a random valid private key and computing the corresponding bitcoin address. This computation can be done in a split second. But the reverse, computing the private key of a given bitcoin address, is practically unfeasible.[7]: ch. 4 Users can tell others or make public a bitcoin address without compromising its corresponding private key. Moreover, the number of valid private keys is so vast that it is extremely unlikely someone will compute a key pair that is already in use and has funds. The vast number of valid private keys makes it unfeasible that brute force could be used to compromise a private key. To be able to spend their bitcoins, the owner must know the corresponding private key and digitally sign the transaction.[d] The network verifies the signature using the public key; the private key is never revealed.[7]: ch. 5
Though transaction fees are optional, miners can choose which transactions to process and prioritize those that pay higher fees.[45] Miners may choose transactions based on the fee paid relative to their storage size, not the absolute amount of money paid as a fee. These fees are generally measured in *satoshis per byte (sat/b)*. The size of transactions is dependent on the number of inputs used to create the transaction and the number of outputs.[7]: ch. 8 The blocks in the blockchain were originally limited to 32 megabytes in size. The block size limit of one megabyte was introduced by Satoshi Nakamoto in 2010.[*clarification needed*] Eventually, the block size limit of one megabyte created problems for transaction processing, such as increasing transaction fees and delayed processing of transactions.[46] Andreas Antonopoulos has stated Lightning Network is a potential scaling solution and referred to lightning as a second-layer routing network.[7]: ch. 8
Transactions are defined using a Forth-like scripting language.[7]: ch. 5 Transactions consist of one or more *inputs* and one or more *outputs*. When a user sends bitcoins, the user designates each address and the amount of bitcoin being sent to that address in an output. To prevent double spending, each input must refer to a previous unspent output in the blockchain.[45] The use of multiple inputs corresponds to the use of multiple coins in a cash transaction. Since transactions can have multiple outputs, users can send bitcoins to multiple recipients in one transaction. As in a cash transaction, the sum of inputs (coins used to pay) can exceed the intended sum of payments. In such a case, an additional output is used, returning the change back to the payer.[45] Any input *satoshis* not accounted for in the transaction outputs become the transaction fee.[45]
The bitcoin blockchain is a public ledger that records bitcoin transactions.[41] It is implemented as a chain of *blocks*, each block containing a cryptographic hash of the previous block up to the genesis block[c] in the chain. A network of communicating nodes running bitcoin software maintains the blockchain.[42]: 215–219 Transactions of the form *payer X sends Y bitcoins to payee Z* are broadcast to this network using readily available software applications. Network nodes can validate transactions, add them to their copy of the ledger, and then broadcast these ledger additions to other nodes. To achieve independent verification of the chain of ownership, each network node stores its own copy of the blockchain.[43] At varying intervals of time averaging to every 10 minutes, a new group of accepted transactions, called a block, is created, added to the blockchain, and quickly published to all nodes, without requiring central oversight. This allows bitcoin software to determine when a particular bitcoin was spent, which is needed to prevent double-spending. A conventional ledger records the transfers of actual bills or promissory notes that exist apart from it, but as a digital ledger, bitcoins only exist by virtue of the blockchain; they are represented by the unspent outputs of transactions.[7]: ch. 5 Individual blocks, public addresses, and transactions within blocks can be examined using a blockchain explorer.[44]