Hyperliquidthat conversation was a roller coaster from start to finish, I'm moving back to Postgres databases
that conversation was a roller coaster from start to finish, I'm moving back to Postgres databases
cosullivan参与话题 0消息总数 7
该用户的聊天记录定位。
聊天记录
共 7 条，显示第 1-7 条memecoin's were great for solana because that was the main source of revenue during that period.. hyperliquid has other forms of revenue and on-chain EVM activity is probably negligible in the overall scheme of revenue
memecoin's were great for solana because that was the main source of revenue during that period.. hyperliquid has other forms of revenue and on-chain EVM activity is probably negligible in the overall scheme of revenue
Not every app has to move to the HyperEVM.. if you are building a project you need to make your own evaluation on what you need from the chain.. some apps need gigagas and 1000's of transactions a second, some need programmatic access to liquidity and order books, some might have other needs. HyperCore also has an API that allows programmatic access, so EVM apps aren't the only type of apps building in the eco.
Not every app has to move to the HyperEVM.. if you are building a project you need to make your own evaluation on what you need from the chain.. some apps need gigagas and 1000's of transactions a second, some need programmatic access to liquidity and order books, some might have other needs. HyperCore also has an API that allows programmatic access, so EVM apps aren't the only type of apps building in the eco.
The chain as a whole can handle it, its just very opinionated about where the activity should lie. Perps + Spot on HyperCore, general purpose value capture on the EVM.
The chain as a whole can handle it, its just very opinionated about where the activity should lie. Perps + Spot on HyperCore, general purpose value capture on the EVM.
Yes, but EVM to HyperCore is not a bridge... it appears that way from the outside, but tecnnically is completely different. If you send a message on a bridge you have no way to know whether it actually arrives at the destination. With the CoreWriter, you know that your actions will arrive on HyperCore, you just dont know the success or failure and thats a very important distinction
Yes, but EVM to HyperCore is not a bridge... it appears that way from the outside, but tecnnically is completely different. If you send a message on a bridge you have no way to know whether it actually arrives at the destination. With the CoreWriter, you know that your actions will arrive on HyperCore, you just dont know the success or failure and thats a very important distinction
As to the issue on performance, it's not that they run on the same hl-node, but the EVM block is produced inside a HyperCore block which enables some level of guarantees on how the CoreWriter works.. so if there were 500 transactions runing inside a single EVM block and all of them were producing CoreWriter actions then that can be additional load on process the HyperCore blocks, however, I do think there is room to move on throughput, but not sure the demand for blockspace is really there.
As to the issue on performance, it's not that they run on the same hl-node, but the EVM block is produced inside a HyperCore block which enables some level of guarantees on how the CoreWriter works.. so if there were 500 transactions runing inside a single EVM block and all of them were producing CoreWriter actions then that can be additional load on process the HyperCore blocks, however, I do think there is room to move on throughput, but not sure the demand for blockspace is really there.
Atomicity is great, but it's also a rarity in large-scale systems. Atomicity just means developers can be lazy and not worry about side effects. The reality is that if you look at Facebook, X, or Netflix, they're built from independent components with no guarantees of atomicity between them. It's a mindset change in how you design things. And you do get certain guarantees when it comes to CoreWriter and how it operates. I personally think the lack of atomicity is more than made up for by the functionality that programmatic access to HyperCore unlocks.
Atomicity is great, but it's also a rarity in large-scale systems. Atomicity just means developers can be lazy and not worry about side effects. The reality is that if you look at Facebook, X, or Netflix, they're built from independent components with no guarantees of atomicity between them. It's a mindset change in how you design things. And you do get certain guarantees when it comes to CoreWriter and how it operates. I personally think the lack of atomicity is more than made up for by the functionality that programmatic access to HyperCore unlocks.