2/ Beta testers will be able to test our first product - ETH, WBTC and USDC "Holding Pools"
Holding Pools are yield aggregating vaults, similar to other projects, with a focus on longevity, and a professional, simple, clean experience.
This is a familiar DeFi primitive.
3/ Holding Pools at Vesper are scored with liquidity quality scores internally, resulting in a "conservative" or "aggressive" summary label. Conservative yield sources, such as @compoundfinance, @AaveAave and @MakerDAO are "seasoned", with time-in-market, real-money tested.
4/ Holding Pools follow a "Deposit X, Earn X" pattern. Deposit ETH, earn ETH. Deposit WBTC, earn WBTC. All using Vesper's pre-built yield strategies.
5/ Vesper also has several brand new #DeFi primitives that will be released in the coming days and weeks. We're keeping several under wraps, though our public GitHub has some hints.
6/ One new primitive is a "Directed Pools" This follows a "Deposit X, Earn Y" pattern for arbitrary ERC20 tokens, using our yield strategies. This enables microcap coins to have a brand new "earn $JEFFCOIN" yield option.
7/ A "Pool Factory" enables rapid creation of new pools, beyond our first 3 holding pools. The pool factory marries a yield strategy with an ERC20 token, creating a new pool
8/ NOTE: There is NO TOKEN for Vesper right now. The $VSP governance token, vVSP governance pool, and Compound-derived governance module will be deployed later, when Vesper leaves beta mode, and enters full production.
9/ For beta testers, there is still time for input into Vesper's foundational governance structure, that will be launched when VSP is created and minted ("V2").
As a result...
10/ NOTE: Still much #UnderConstruction. The smart contracts are built & audited - but you never know what beta test might turn up. The team is still working on UI and documentation.
1/ Yesterday: My L1 chain has better, faster tech than #Bitcoin or #Ethereum. It is not compatible with existing software or tooling, but will nevertheless overcome network effect and momentum to become the next Ethereum. Invest in my Ethereum killer.
2/ Today: My L2 rollup chain has better, faster tech than #Bitcoin or #Ethereum. It is not compatible with existing software or tooling, but will nevertheless overcome network effect and momentum to become... Invest in my...
3/ Investors routinely underestimate the value of iterative evolution - trial-and-error over time - sunk into software, tooling, auditing software libraries & the 1,000 other elements of a software ecosystem.
Smart competitors build on top of that, rather than starting from zero
2/ #Ethereum bot ecosystems often unintentionally evolve to single-bot-wins situations, where it is pointless & costly to run a bot that consistently comes in "2nd place"
3/ Bot 1 consistently wins liquidation auctions. It becomes unprofitable for others to play the game, resulting in a single player game. If the player (Bot 1) leaves or malfunctions, no other bots step up and take its place, due to incentives & deteriorated ecosystem.
Finally spent some time studying #Ethereum Merkle Patricia Tree github.com/ethereum/wiki/… 1. It is an elegant data structure for Eth, creating a cryptographically stable merkle root, no matter the data insertion order. 2. Oh boy, it really punishes your hard drive storage.
In my past life at Red Hat, I wrote the ATA (aka IDE) drivers for Linux, so I know a bit about data storage and hard drives.
Here is why Eth is so punishing on data storage, and why SSDs/NVMe are a field requirement for Eth:
Like Bitcoin, Eth has poor cache locality:
* Huge db, which means each Next Page is less likely to be in page/disk cache.
* Keys are hashes, which means each Next Query Key is uniformly random, and therefore equally unlikely to be “close” to any recent past query.